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
Related
So after much flailing, I think I understand how to manage updates... but I'm not sure. I currently have root and Xposed installed on 5.1.1.
My plan when the next update comes:
get the factory image from google
Unzip the zip.
Inside that, there is the image-shamu zip, which I'll also unzip.
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery twrp-xxx-shamu.img
from twrp
Reroot and reboot
boot back to recovery and install Xposed again.
Is that about right? what am I missing here?
ninjaaron said:
So after much flailing, I think I understand how to manage updates... but I'm not sure. I currently have root and Xposed installed on 5.1.1.
My plan when the next update comes:
1. get the factory image from google
Unzip the zip.
Inside that, there is the image-shamu zip, which I'll also unzip.
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery twrp-xxx-shamu.img
from twrp
Reroot and reboot
boot back to recovery and install Xposed again.
Is that about right? what am I missing here?
Click to expand...
Click to collapse
That would work though no need to flash recovery if you already have it.. But yes, other than that, probably the best way.
Edit, also no need to reboot between flashing SuperSU zip and Xposed zip
Thanks. The last time I tried to flash system.img, twrp was bork'd, but maybe it was just a fluke. I did a lot of weird things today to figure this stuff out, and maybe it was something else.
Hi! So a little while ago I unlocked my bootloader, rooted my device, enabled camera2api and installed gcam and modules. Is there any way I can go back to the original 8.1.0 in order to get the OTA updates and get the November patch that comes with andoid 9? Then unlock the bootloader again, enable camera2api and install gcam and modules?
I soft bricked my phone in my first attempt to unlock the bootloader so I decided to ask here for help first
mirunaa said:
Hi! So a little while ago I unlocked my bootloader, rooted my device, enabled camera2api and installed gcam and modules. Is there any way I can go back to the original 8.1.0 in order to get the OTA updates and get the November patch that comes with andoid 9? Then unlock the bootloader again, enable camera2api and install gcam and modules?
I soft bricked my phone in my first attempt to unlock the bootloader so I decided to ask here for help first
Click to expand...
Click to collapse
You don't need to lock bootloader to get OTA updates. Keep it unlocked if you want to get back to stock android.
First uninstall all the Magisk modules you've downloaded. Then flash stock boot.img and system.img (If you've edited build.prop without adb shell). After this you'll be on stock android and you'll get OTA updates.
Where do I find stock boot.img and system.img?
Also, will my phone factory reset after this procedure?
mirunacont said:
Where do I find stock boot.img and system.img?
Also, will my phone factory reset after this procedure?
Click to expand...
Click to collapse
Which version of Oreo are you on? Tell me the build number.
And your phone won't factory reset after this.
---------- Post added at 07:31 PM ---------- Previous post was at 07:23 PM ----------
[email protected] said:
Which version of Oreo are you on? Tell me the build number.
And your phone won't factory reset after this.
Click to expand...
Click to collapse
Download this - https://android.googleapis.com/pack.../f9b27203a7d6dd2c6709f238d9953c6d4e18c04b.zip
Then extract the files and then find the boot.img and system.img. Flash the images from fastboot using -
Code:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash system_a system.img
fastboot flash system_b system.img
Extract the Images & Flash Them Individually
you have to flash the system images individually. This method takes some extra work, but it can be used to un-root, update, or un-brick your device without losing existing data.
Start by extracting any additional archives from the factory images package. Sometimes, factory images packages can contain a series of three or four nested archives, so make sure to unzip all of them. From there, copy all of the image files to the main platform-tools folder—in other words, don't leave them in any sub-folders. From here, there are two images that you can get rid of: cache.img and userdata.img. These are the images that will overwrite your data and cache with blank space, so if you don't flash them, your existing data will remain intact.
Of the remaining images, six make up the core elements of Android: boot, bootloader, radio, recovery, system, and vendor.
The boot image contains the kernel, so if you just want to get rid of a custom kernel that's causing issues with your device, you only have to flash this one. To do that, type the following command into the ADB shell window:
fastboot flash boot <boot image file name>.img
Next is the bootloader image—this is the the interface that you're using to flash images with Fastboot commands. So to update your bootloader, type:
fastboot flash bootloader <bootloader image file name>.img
Once you've done that, you should reload the bootloader so that you can continue flashing images on the newer version. To do that, type:
fastboot reboot-bootloader
After that, we have the radio image. This one controls connectivity on your device, so if you're having problems with Wi-Fi or mobile data, or if you just want to update your radio, type:
fastboot flash radio <radio image file name>.img
Then there's recovery. This is something you may or may not want to flash, depending on the modifications you've made. For example, if you've installed TWRP custom recovery, flashing this image will overwrite your modification and replace it with the stock recovery interface. So if you're just updating your modded device, you should skip this one. Otherwise, if you plan to keep your phone stock and want the newer version of stock recovery, type:
fastboot flash recovery <recovery file name>.img
Next up is the big one: The system image. This one contains all of the files that make up the actual Android OS. As such, it's the most essential part of any update.
However you may not be updating your phone. You may just be re-flashing the stock firmware to recover from a soft brick. If this is the case, the system image is often the only image you need to flash in order to fix everything, because it contains the entirety of Android. In other words, if you flash this image and nothing else, it will undo any changes you made with root access and put everything back the way it was.
So as a cure-all in most soft brick situations, or as a method for getting the core part of an Android update, type:
fastboot flash system <system file name>.img
Finally, there's the vendor image. This is only present on newer phones, so don't worry if it's not in your factory images package. But if it's there, it contains a few important files, so type the following line to get this partition updated:
fastboot flash vendor <vendor file name>.img
After you've sent any or all of the above commands, you'll be ready to restart your device and boot into Android. To do that, type:
fastboot reboot.
At this point, your device should be fully updated, or if you were trying to recover from a soft brick, it should be running flawlessly.
Hello everyone
Please i'm in France and would like to upgrade to Pie
When i try nby updater no update appear
i'm on 8.1 with Nov Sec Patch
It all started when I tried to temporarily boot into the TWRP img file. It didn't work so I tried flashing the file to boot_a. Then I installed TWRP through the installer (stupidly didn't wipe the caches) and... Well. When I try to boot into System through TWRP, it gets COMPLETELY stuck at the powered by Android logo screen. No amount or combination of button holding will shut it off and I actually had to let the battery (thank you SO MUCH for non-removable batteries by the way, smartphone manufacturers >_>) drain before it would actually boot again. Rebooting it into Download mode will get it stuck in there too where every time I hold the power button and shut it off, it will just reboot right back into Download mode again. And now, here's probably the worst part. I CAN'T UNLOCK the critical partition to flash when in Download mode, so I can't use the OST tool! When I try to unlock it, it just complains that flashing unlock is not allowed even though the rest of the bootloader is completely unlocked.
TL;DR - When I power the phone up it goes straight into TWRP. Booting to System totally freezes it and the Bootloader puts it in a loop when I try to power it off. Critical partition is locked for some reason. I CAN get around the bootloader loop though and get back to TWRP by switching active slots and rebooting.
Did you flash the TWRP installer to your active boot partition or your inactive one? If you flashed it to the active one, you can't get into system anymore because TWRP is your boot partition.
If you are on Oreo, and you flashed to the inactive slot, and then patched the active slot, you have to reboot into the active slot recovery and flash the Magisk installer to disable verification of the partitions.
If you can get into the bootloader, and you still have the unlock key from nokia, do fastboot flash unlock <unlock.key>, and then fastboot oem unlock_critical. Then you should be able to flash using OST.
THMSP said:
do fastboot flash unlock <unlock.key>, and then fastboot oem unlock_critical. Then you should be able to flash using OST.
Click to expand...
Click to collapse
This unlocked it! Thank you! <3
I also did have an issue with the OST tool complaining that the updater was out of date, but changing the .mlf file and leaving it unpacked when I opened it in OST seemed to make it work perfectly. My phone is now booting just fine and back to stock!
Now I just need to solve the original problem I had. How can I install TWRP to recovery since the img file wouldn't temporarily boot last time?
EDIT: Apparently unlocking the critical partition seemed to solve the problem of the TWRP image file not temporarily booting as well!
S5Guy said:
EDIT: Apparently unlocking the critical partition seemed to solve the problem of the TWRP image file not temporarily booting as well!
Click to expand...
Click to collapse
No, thats because you flashed back the May firmware, where fastboot boot was still working properly. It only broke after the august update. If you want TWRP on newer security patch versions, you can get it here: https://bit.ly/nokia-nb1 in the folder "Boot Images". Those images are prepatched, you can safely flash them to your active boot partition. It also contains stock images for restoring before updating.
THMSP said:
No, thats because you flashed back the May firmware, where fastboot boot was still working properly. It only broke after the august update. If you want TWRP on newer security patch versions, you can get it here: https://bit.ly/nokia-nb1 in the folder "Boot Images". Those images are prepatched, you can safely flash them to your active boot partition. It also contains stock images for restoring before updating.
Click to expand...
Click to collapse
Yeah looks like you're right. Letting it update back to Android 9 deleted TWRP and made fastboot boot for TWRP nonfunctional again.
Wait, so can I use that TWRP boot image you specified to boot temporarily to TWRP and then run the installer zip? Or will that not work and I'll have to flash the img directly from the bootloader?
S5Guy said:
Wait, so can I use that TWRP boot image you specified to boot temporarily to TWRP and then run the installer zip? Or will that not work and I'll have to flash the img directly from the bootloader?
Click to expand...
Click to collapse
You have to flash it directly to your boot partition. fastboot boot will work for nothing (and even if it worked those images would just send you directly into the system)
THMSP said:
No, thats because you flashed back the May firmware, where fastboot boot was still working properly. It only broke after the august update. If you want TWRP on newer security patch versions, you can get it here: https://bit.ly/nokia-nb1 in the folder "Boot Images". Those images are prepatched, you can safely flash them to your active boot partition. It also contains stock images for restoring before updating.
Click to expand...
Click to collapse
Alright! fastboot flash boot_a (TWRP image) worked! Thank you so much for all the help. <333
When a patched boot.img is booted it always enters fastboot mode even if system is targeted. However, if the stock boot.img is patched again, everything works as usual. Any ideas on how to fix this?
Did you type on your pc fastboot reboot as a final step? Maybe you have to repair or reflash the stock rom using miflash and try again (you cant clear cache without twrp) as a way to get the system prepared to Flash a modified boot image
I have the exact same problem. I tried older versions of Magisk, then the Canary build, but nothing helped..
Bilihh said:
When a patched boot.img is booted it always enters fastboot mode even if system is targeted. However, if the stock boot.img is patched again, everything works as usual. Any ideas on how to fix this?
Click to expand...
Click to collapse
Found a solution! It's right here:
How to flash twrp recovery and root redmi note 10s?
I can't install a twrp recovery if I tried A message appears (remote : this partition doesn't exist)
forum.xda-developers.com
Before, you ask, I must use fastboot since no one built TWRP for my device.
On my Alldocube KPad, when flashing my Magisk patched boot.ig file, it always goes into a bootloop.
Can anyone help me on how to fix this? I'm tired of flashing stock firmware over and over.
Thanks in advance.