Hey guys,
I am having issues updating to February update. I already tried all the guides on how to uninstall the patched boot through Magisk as well as manually trying to flash through fastboot 10.03 (January update) boot.img but everytime i end up in bootloop which i resolve after flashing 10.03 patched img. Uninstalling it through Magisk managers shows that I do not have root but the update still fails.
Any one has a link for the full 10.0.03 boot.img as I have a suspicion that the ones I am using might be partial from the ota and that is why they fail to boot.
Or let me know if you have any other idea how to fix this without wiping the data or restoring through mi tool
If someone from xiaomi read this "fix your s...t "
Thank you in advance,
aliensk said:
Hey guys,
I am having issues updating to February update. I already tried all the guides on how to uninstall the patched boot through Magisk as well as manually trying to flash through fastboot 10.03 (January update) boot.img but everytime i end up in bootloop which i resolve after flashing 10.03 patched img. Uninstalling it through Magisk managers shows that I do not have root but the update still fails.
Any one has a link for the full 10.0.03 boot.img as I have a suspicion that the ones I am using might be partial from the ota and that is why they fail to boot.
Or let me know if you have any other idea how to fix this without wiping the data or restoring through mi tool
If someone from xiaomi read this "fix your s...t "
Thank you in advance,
Click to expand...
Click to collapse
Try with this:
https://forum.xda-developers.com/showpost.php?p=78757162&postcount=12
lept_2014 said:
Try with this:
https://forum.xda-developers.com/showpost.php?p=78757162&postcount=12
Click to expand...
Click to collapse
Thank you but that one didnt work I already tried it. Bootloop when using that one. I have not done any mods to system files except using e patched boot to get root.
Hey guys,
I managed to resolve the bootloop issue. If anyone has the same issue use the following untouched boot.img
https://xiaomifirmware.com/download/11657/
As I was suspecting, the ones I was using the from the links provided in the forum were too small and this one is 64 mb. After flashing it boots perfectly.
However, unfortunately again I get errors during the update. At least no bootloop
aliensk said:
Thank you but that one didnt work I already tried it. Bootloop when using that one. I have not done any mods to system files except using e patched boot to get root.
Click to expand...
Click to collapse
That Stock BOOT works fine for me. Remember flash it into the right slot for you.
I did flash to to slot B as the getvar current-slot was B but it was still bootlooping until i tried the last one from the link I provided. However, since I am still unable to update, is there a link to download the system.img for 10.0.3.0 just in case i have somehow modified my system? I dont remember to have done anything but just in case.
Thank you.
How will you solve it
Plz...tell me with boot file how fill solve your problem
Varshithpoudala said:
Plz...tell me with boot file how fill solve your problem
Click to expand...
Click to collapse
have not resolved it yet. In fact after trying to fix now it went into full brick mode no button reactions and nothing on the screen must have done something really wrong so be careful
aliensk said:
have not resolved it yet. In fact after trying to fix now it went into full brick mode no button reactions and nothing on the screen must have done something really wrong so be careful
Click to expand...
Click to collapse
Did you find any way to fix it?
Hi,
I'm coming from a rooted November image for my Pixel 4XL and am having trouble getting the December magisk_patched.img to take. I've successfully applied google stock December image, rebooted to Android, patched boot.img with magisk, but when I try to flash magisk_patched.img in fastboot, it flashes, but reboots to fastboot with "error boot prepare" displayed. Flashing stock boot.img gets back to Android without issue (but no root).
I've tried flashing with both cmd and powershell. I've tried "fastboot flash boot magisk_patched.img" (and also fastboot flash boot_a magisk_patched.img and fastboot flash boot_b magisk_patched.img). I'm using Magisk Manager 7.4.
Not sure what else to try. I'd rather not do a factory reset at this point.
Any suggestions?
DoughMucker said:
Hi,
I'm coming from a rooted November image for my Pixel 4XL and am having trouble getting the December magisk_patched.img to take. I've successfully applied google stock December image, rebooted to Android, patched boot.img with magisk, but when I try to flash magisk_patched.img in fastboot, it flashes, but reboots to fastboot with "error boot prepare" displayed. Flashing stock boot.img gets back to Android without issue (but no root).
I've tried flashing with both cmd and powershell. I've tried "fastboot flash boot magisk_patched.img" (and also fastboot flash boot_a magisk_patched.img and fastboot flash boot_b magisk_patched.img). I'm using Magisk Manager 7.4.
Not sure what else to try. I'd rather not do a factory reset at this point.
Any suggestions?
Click to expand...
Click to collapse
Just a couple things to try.
1. Did you fastboot the factory image to both slots? If not I would try that first, without the -w of course.
2. When you patched the boot.img, was dm-verity checked off? If not, enable it, then patch it again.
3. Have you tried from a cmd....
fastboot flash boot magisk_patched.img --slot=all
Whatever it is, I hope you get it working :good:
Badger50 said:
Just a couple things to try.
1. Did you fastboot the factory image to both slots? If not I would try that first, without the -w of course.
2. When you patched the boot.img, was dm-verity checked off? If not, enable it, then patch it again.
3. Have you tried from a cmd....
fastboot flash boot magisk_patched.img --slot=all
Whatever it is, I hope you get it working :good:
Click to expand...
Click to collapse
Thanks for the suggestions. I tried each one. Unfortunately, no luck.
DoughMucker said:
Thanks for the suggestions. I tried each one. Unfortunately, no luck.
Click to expand...
Click to collapse
Bummer man! How about different 2.0 USB A to USB C cables and ports??
Badger50 said:
Bummer man! How about different 2.0 USB A to USB C cables and ports??
Click to expand...
Click to collapse
Just tried that too. :crying:
DoughMucker said:
Just tried that too. :crying:
Click to expand...
Click to collapse
Sheesh! You using canary or stable magisk? Either way, I'd switch to the other one and try that as well. If that doesn't work, then you may have no choice but to either factory reset, or remove all your drives, platform-tools, redownload everything, and start over. I can't think of many other things to try
Badger50 said:
Sheesh! You using canary or stable magisk? Either way, I'd switch to the other one and try that as well. If that doesn't work, then you may have no choice but to either factory reset, or remove all your drives, platform-tools, redownload everything, and start over. I can't think of many other things to try
Click to expand...
Click to collapse
I was stable before, but had just tried canary. Same situation.
I'm reading https://forum.xda-developers.com/pixel-3-xl/help/december-update-rootable-t4013605/page6 and wondering if it's related to systemless hosts for adaway which i did not disable.
DoughMucker said:
I was stable before, but had just tried canary. Same situation.
I'm reading and wondering if it's related to systemless hosts for adaway which i did not disable.
Click to expand...
Click to collapse
I don't think so, but I suppose anything is possible. I've left magisk modules intact before, but never had the trouble like your having. Shoot, you might even try flashing a different factory image image other than what was recommended by google. People seem to have had the best luck with the .012.A1 version which is supposedly for AT&T only.
Badger50 said:
I don't think so, but I suppose anything is possible. I've left magisk modules intact before, but never had the trouble like your having. Shoot, you might even try flashing a different factory image image other than what was recommended by google. People seem to have had the best luck with the .012.A1 version which is supposedly for AT&T only.
Click to expand...
Click to collapse
I'm using 012.A1. Google updated their factory image/OTA site and removed the reference to ATT. I had double checked someone else's phone here that got the Dec OTA update and she had 012.A1 after being on 007.A3.
Going to take a break from trying things for a day or so because it's frustrating. Arrghh.
And thanks for the help!
Badger50 said:
I don't think so, but I suppose anything is possible. I've left magisk modules intact before, but never had the trouble like your having. Shoot, you might even try flashing a different factory image image other than what was recommended by google. People seem to have had the best luck with the .012.A1 version which is supposedly for AT&T only.
Click to expand...
Click to collapse
I did one final thing and it worked...I flashed your patched boot.img from here and it worked. Was it .012.A1? What version of Magisk Manager are you using?
DoughMucker said:
I did one final thing and it worked...I flashed your patched boot.img from here and it worked. Was it .012.A1? What version of Magisk Manager are you using?
Click to expand...
Click to collapse
Yep, that was from the .012.A1 factory image. I'm using stable magisk. Question, did you have dm-verity checked off before you patched the boot.img, and, did you disable all magisk modules before you patched and flashed the boot.img? Either way, I'm glad you got it to boot up :good::good:
Badger50 said:
Yep, that was from the .012.A1 factory image. I'm using stable magisk. Question, did you have dm-verity checked off before you patched the boot.img, and, did you disable all magisk modules before you patched and flashed the boot.img? Either way, I'm glad you got it to boot up :good::good:
Click to expand...
Click to collapse
The first time I successfully patched the November boot.img I did not check off dm-verity. I didn't either for the first time(s) I tried the December image. I only tried, unsuccessfully, with dm-verity checked after you mentioned it here.
I did have the Systemless Hosts module enabled when patching the December image. This is what I was referring to earlier when I mentioned I thought it was related to systemless hosts for adaway. I actually didn't realize that when you enabled that in Magisk Manager, that it installed a module. So I never thought I had a module active, but I did.
To end this saga...after getting root again, I did a Titanium Backup, Factory Reset, and re-rooted by patching boot.img again with Magisk Manager canary. It went smoothly, as it should have originally. Now to restore....
This error seems to occur when you flash a boot.img that doesn't match the exact firmware version.
=> Download the correct, currently installed full firmware package, extract the boot.img and flash it.
Solution
This occurs when you're on Android 11 build and try to install the Android 10 build.
There's a simple fix though, thankfully.
Download the Android 10 ota image for Pixel 4 XL from google, and extract the dtbo.img from it. Flash it using
fastboot flash dtbo_a dtbo.img
fastboot flash dtbo_b dtbo.img
If that doesn't work, you can flash the whole stock Android 10 build and then you can boot whatever you were trying to.
Please click "Thanks" if this worked for you so that others can see.
Same Issue on Pixel 3a XL - please Help
DoughMucker said:
Hi,
I'm coming from a rooted November image for my Pixel 4XL and am having trouble getting the December magisk_patched.img to take. I've successfully applied google stock December image, rebooted to Android, patched boot.img with magisk, but when I try to flash magisk_patched.img in fastboot, it flashes, but reboots to fastboot with "error boot prepare" displayed. Flashing stock boot.img gets back to Android without issue (but no root).
I've tried flashing with both cmd and powershell. I've tried "fastboot flash boot magisk_patched.img" (and also fastboot flash boot_a magisk_patched.img and fastboot flash boot_b magisk_patched.img). I'm using Magisk Manager 7.4.
Not sure what else to try. I'd rather not do a factory reset at this point.
Any suggestions?
Click to expand...
Click to collapse
Pixel 3aXL with LineageOS 17
I tried to install Magisk following this guide https://magisk.download/root-pixel-3a-3a-xl/
I am stuck in Fastboot now. No ADB Connection.
How can I get out of that?
I used the boot.img from the firmware I built Lineage on. Should I use a boot.img from LineageOS .zip?
What is dm-verity?
Can I get to my previous unrooted device?
''bootslot: b
enter reason: error boot prepare''
dadu1257 said:
Pixel 3aXL with LineageOS 17
I tried to install Magisk following this guide https://magisk.download/root-pixel-3a-3a-xl/
I am stuck in Fastboot now. No ADB Connection.
How can I get out of that?
I used the boot.img from the firmware I built Lineage on. Should I use a boot.img from LineageOS .zip?
What is dm-verity?
Can I get to my previous unrooted device?
''bootslot: b
enter reason: error boot prepare''
Click to expand...
Click to collapse
Post your question on the Pixel 3a XL 'Question and Answer' thread, not the Pixel 4 XL 'Question and Answer' thread.
or
Post your question on the LineageOS 17 thread.
I have installed Lineage OS 18 Android 11 Rom from below thread,
https://forum.xda-developers.com/realme-x2-pro/development/rom-lineageos-18-0-realme-x2-pro-t4177291
I have used the OrangFox R11 Recovery for the installation.
Now I can not go back to stock C.33 firmware. I have tried installing OZIP both with TWRP and OrangeFox but no luck so far. Whenever the installation completes and I reboot the device, it shows boot/recovery damaged error message.
I have tried OZIP installation followed by vbmeta.img flashing as well. But no luck. Still the same error message.
I have tried flashing fastboot rom with all files (but no recovery img was inside) as well but still the same error.
I have tried RealMe Flash Tool with Firmware OFP but still the same error.
I'm simply stuck on this LineagOS 18 rom and I badly wanna go back to the Stock rom. :crying:
Please help!
P.S : If this thread needs to be moved somewhere elsle please be kind enough to do so. I'm not so familiar with thread openings. Sorry about it. :fingers-crossed:
Format data after flashing Ozip thats important . try that with twrp
Anask3444 said:
Format data after flashing Ozip thats important . try that with twrp
Click to expand...
Click to collapse
Already tried bro.. no luck
ImperoDroider said:
Already tried bro.. no luck
Click to expand...
Click to collapse
Did you try the fastboot flashable images?
https://forum.xda-developers.com/re...ock-fastboot-flashable-images-realme-t4003107
ImperoDroider said:
I have installed Lineage OS 18 Android 11 Rom from below thread,
https://forum.xda-developers.com/realme-x2-pro/development/rom-lineageos-18-0-realme-x2-pro-t4177291
I have used the OrangFox R11 Recovery for the installation.
Now I can not go back to stock C.33 firmware. I have tried installing OZIP both with TWRP and OrangeFox but no luck so far. Whenever the installation completes and I reboot the device, it shows boot/recovery damaged error message.
I have tried OZIP installation followed by vbmeta.img flashing as well. But no luck. Still the same error message.
I have tried flashing fastboot rom with all files (but no recovery img was inside) as well but still the same error.
I have tried RealMe Flash Tool with Firmware OFP but still the same error.
I'm simply stuck on this LineagOS 18 rom and I badly wanna go back to the Stock rom. :crying:
Please help!
P.S : If this thread needs to be moved somewhere elsle please be kind enough to do so. I'm not so familiar with thread openings. Sorry about it. :fingers-crossed:
Click to expand...
Click to collapse
If it says "boot/recovery damaged" and you're still able to use your phone, you should consider yourself lucky. I had to send mine in warranty for repair. I too am trying to go back to stock ROM after installing LOS 18.
Schumanzuar said:
Did you try the fastboot flashable images?
https://forum.xda-developers.com/re...ock-fastboot-flashable-images-realme-t4003107
Click to expand...
Click to collapse
These images have bricked my phone! Error message:
The current image(boot/recovery) have been destroyed and can not boot.
Please flash the correct image or contact customer service to fix it.
Tried flashing TWRP, no luck. Cannot boot.
do you have flash again the vbmeta.bin
I do that and after the rom start again for me
rpfe26 said:
do you have flash again the vbmeta.bin
I do that and after the rom start again for me
Click to expand...
Click to collapse
I didn't try that, however I did manage to get my phone up and working again after having destroyed the boot/recovery
I used Realme Flash Tool in combination with TWRP to get the phone up and running.
ImperoDroider said:
I have installed Lineage OS 18 Android 11 Rom from below thread,
https://forum.xda-developers.com/realme-x2-pro/development/rom-lineageos-18-0-realme-x2-pro-t4177291
I have used the OrangFox R11 Recovery for the installation.
Now I can not go back to stock C.33 firmware. I have tried installing OZIP both with TWRP and OrangeFox but no luck so far. Whenever the installation completes and I reboot the device, it shows boot/recovery damaged error message.
I have tried OZIP installation followed by vbmeta.img flashing as well. But no luck. Still the same error message.
I have tried flashing fastboot rom with all files (but no recovery img was inside) as well but still the same error.
I have tried RealMe Flash Tool with Firmware OFP but still the same error.
I'm simply stuck on this LineagOS 18 rom and I badly wanna go back to the Stock rom. :crying:
Please help!
P.S : If this thread needs to be moved somewhere elsle please be kind enough to do so. I'm not so familiar with thread openings. Sorry about it. :fingers-crossed:
Click to expand...
Click to collapse
I managed to get my phone up and running. Did you manage to get yours?
Milan-XDA said:
I managed to get my phone up and running. Did you manage to get yours?
Click to expand...
Click to collapse
You mean you got it back to stock from lineage os 18 by flashing through realme flash tool?
adimegarocker said:
You mean you got it back to stock from lineage os 18 by flashing through realme flash tool?
Click to expand...
Click to collapse
Yes, that is correct.
Here ya go, couldn't find it anywhere so I figured I would save people some time.
I was trying to get Magisk to work on A11 Beta, but I can't even get into TWRP because Im getting Quallcom Crash Dump when I try to boot into TWRP.
Could you give some info how to flash this (fastboot ?) to get Magisk working?
And will I have to reflash once OOS hits stable or gets an update?
Thanks!
Yeah, same issue here. Install magisk 23 apk, then reboot to fastboot. Now, fastboot flash boot_a "patched boot image attached" then fastboot flash boot_b with the same img. Fastboot reboot
Hopefully we will have a working TWRP soon so by the time the next release is out everything can be done with the oxygen updater app or through TWRP itself
Yeedatoy said:
Here ya go, couldn't find it anywhere so I figured I would save people some time.
Click to expand...
Click to collapse
can this work for oneplus 6 too?
deeptanshuB said:
can this work for oneplus 6 too?
Click to expand...
Click to collapse
I don't think so, unfortunately
hello evryone i need to root my phone sm a202f i tried evrythimg if i try to flash twrp odin says complete write operation failed on my bootloader custom binary blocked i also tried with ADB but no so can someone tell me how to root it please Android 11
I was trying to install a GSI, I flashed vbmeta and did all the steps i was told to do thats i tried to boot into the system and it kept rebooting to fastboot now it wont even let me flash stock rom can someone please help me?
TedFin said:
I was trying to install a GSI, I flashed vbmeta and did all the steps i was told to do thats i tried to boot into the system and it kept rebooting to fastboot now it wont even let me flash stock rom can someone please help me?
Click to expand...
Click to collapse
soo, its now saying couldnt find flash script