I'm on 11.2.2.2 global, successfully rooted with Magisk. When I follow the OTA update procedure -- uninstall Magisk, install the OTA update but don't reboot, install Magisk to inactive slot, and reboot -- everything appears to work and I don't get any errors, but when the phone boots up afterwards, it's still on 11.2.2.2.
I've tried with the both of the recent OTA updates and the result is the same. Am I doing something wrong, or is this expected when rooted, and I need to wait for the full ROM to be released by 1+?
Oxygen Updater - Apps on Google Play
Skip staged rollout queues and update your OnePlus device ASAP!
play.google.com
Okay, I see you can't install incremental OTAs with an unlocked bootloader. Disappointing. Guess I am waiting for full updates.
It is written in a lot of guides. It works when you do it correctly. I got a oneplus 8 and it works without a problem.
0No said:
It is written in a lot of guides. It works when you do it correctly. I got a oneplus 8 and it works without a problem.
Click to expand...
Click to collapse
Well I followed the same procedure when I flashed the full zip of 11.2.2.2, and it worked. So I don't see how I am doing it incorrectly.
Slikkster2k said:
I'm on 11.2.2.2 global, successfully rooted with Magisk. When I follow the OTA update procedure -- uninstall Magisk, install the OTA update but don't reboot, install Magisk to inactive slot, and reboot -- everything appears to work and I don't get any errors, but when the phone boots up afterwards, it's still on 11.2.2.2.
I've tried with the both of the recent OTA updates and the result is the same. Am I doing something wrong, or is this expected when rooted, and I need to wait for the full ROM to be released by 1+?
Click to expand...
Click to collapse
My suggestion is to uninstall magisk (restore the stock image) and reboot. Then do the update and reboot. The use the 11.2.2 modified boot image in fastboot do: fastboot boot boot.img and when it boots let magisk install which will backup then modify the new boot image from 11.2.4.4 and voila you now have root and a backup of the newest boot image which will let you be able to update to the next Ota using this same method
toyanucci said:
My suggestion is to uninstall magisk (restore the stock image) and reboot. Then do the update and reboot. The use the 11.2.2 modified boot image in fastboot do: fastboot boot boot.img and when it boots let magisk install which will backup then modify the new boot image from 11.2.4.4 and voila you now have root and a backup of the newest boot image which will let you be able to update to the next Ota using this same method
Click to expand...
Click to collapse
Well I tried this and I'm really hosed now... phone will only boot to recovery after uninstalling Magisk and rebooting. I tried flashing the stock 11.2.2.2 boot.img from fastboot, and that didn't help either. I'm kinda stuck unless I can flash the full 11.2.2.2 from fastboot or recovery? I don't know how to do that.
Slikkster2k said:
Well I tried this and I'm really hosed now... phone will only boot to recovery after uninstalling Magisk and rebooting. I tried flashing the stock 11.2.2.2 boot.img from fastboot, and that didn't help either. I'm kinda stuck unless I can flash the full 11.2.2.2 from fastboot or recovery? I don't know how to do that.
Click to expand...
Click to collapse
What version OP9 are you using and what OS version and phone version boot images are you using?
Instructions are here for how to do a manual flash via fastboot. Basically extract with payload dumper and flash each image manually like in the example in the link.
toyanucci said:
What version OP9 are you using and what OS version and phone version boot images are you using?
Instructions are here for how to do a manual flash via fastboot. Basically extract with payload dumper and flash each image manually like in the example in the link.
Click to expand...
Click to collapse
Not sure what you mean by what version OP9?
I have 11.2.2.2AA installed, I've tried flashing the matching stock boot image, the magisk patched version of it, and even the stock 11.2.3.3AA boot image.
I found those instructions and I'm trying it, but I'm running into problems with the payload dumper (FileNotFoundError when attempting to dump).
Slikkster2k said:
Not sure what you mean by what version OP9?
I have 11.2.2.2AA installed, I've tried flashing the matching stock boot image, the magisk patched version of it, and even the stock 11.2.3.3AA boot image.
I found those instructions and I'm trying it, but I'm running into problems with the payload dumper (FileNotFoundError when attempting to dump).
Click to expand...
Click to collapse
And you're sure the boot images you've tried are for the global version? If all you've messed with is the boot image I don't see why the phone won't boot Before flashing any boot image it's best to do fastboot boot boot.img. It doesn't overwrite the boot image so in case it doesn't work a simple reboot will get you back up ad running.
Re payload dumber make sure you've CD'd to the right folder? I had the same error when I was trying to do it yesterday and it was because I hadn't CD'd to the right folder.
Have you got the files extracted?
toyanucci said:
And you're sure the boot images you've tried are for the global version? If all you've messed with is the boot image I don't see why the phone won't boot Before flashing any boot image it's best to do fastboot boot boot.img. It doesn't overwrite the boot image so in case it doesn't work a simple reboot will get you back up ad running.
Re payload dumber make sure you've CD'd to the right folder? I had the same error when I was trying to do it yesterday and it was because I hadn't CD'd to the right folder.
Have you got the files extracted?
Click to expand...
Click to collapse
I found them in the root thread in this forum, the user who posted them said they were for global, yes.
I did try using fastboot boot first, but I get this error:
Code:
FAILED (remote: 'Failed to load/authenticate boot image: Load Error')
So I just tried to flash instead, which flashes successfully, but then it fails to boot after and dumps me back into fastboot or recovery.
I know my way around the command line pretty well, so yes I'm in the right directory. Here's the full error when running extract_android_ota_payload.py:
Code:
Extracting 'abl.img'
Traceback (most recent call last):
File "E:\extract_android_ota_payload-master\extract_android_ota_payload.py", line 142, in <module>
main(filename, output_dir)
File "E:\extract_android_ota_payload-master\extract_android_ota_payload.py", line 121, in main
parse_payload(payload, p, out_f)
File "E:\extract_android_ota_payload-master\extract_android_ota_payload.py", line 95, in parse_payload
r = decompress_payload('xzcat', data, e.num_blocks * BLOCK_SIZE, operation.data_sha256_hash)
File "E:\extract_android_ota_payload-master\extract_android_ota_payload.py", line 78, in decompress_payload
p = subprocess.Popen([command, '-'], stdout=subprocess.PIPE, stdin=subprocess.PIPE)
File "C:\Program Files\Python39\lib\subprocess.py", line 947, in __init__
self._execute_child(args, executable, preexec_fn, close_fds,
File "C:\Program Files\Python39\lib\subprocess.py", line 1416, in _execute_child
hp, ht, pid, tid = _winapi.CreateProcess(executable, args,
FileNotFoundError: [WinError 2] The system cannot find the file specified
I believe it's failing because it can't find xzcat. I am trying to install MinGW in an effort to resolve that.
The only boot image I haven't tried yet so far is 11.2.4.4 as I haven't been able to find a copy of that. I don't know why that would work when nothing else has though.
Slikkster2k said:
I found them in the root thread in this forum, the user who posted them said they were for global, yes.
I did try using fastboot boot first, but I get this error:
Code:
FAILED (remote: 'Failed to load/authenticate boot image: Load Error')
So I just tried to flash instead, which flashes successfully, but then it fails to boot after and dumps me back into fastboot or recovery.
I know my way around the command line pretty well, so yes I'm in the right directory. Here's the full error when running extract_android_ota_payload.py:
Code:
Extracting 'abl.img'
Traceback (most recent call last):
File "E:\extract_android_ota_payload-master\extract_android_ota_payload.py", line 142, in <module>
main(filename, output_dir)
File "E:\extract_android_ota_payload-master\extract_android_ota_payload.py", line 121, in main
parse_payload(payload, p, out_f)
File "E:\extract_android_ota_payload-master\extract_android_ota_payload.py", line 95, in parse_payload
r = decompress_payload('xzcat', data, e.num_blocks * BLOCK_SIZE, operation.data_sha256_hash)
File "E:\extract_android_ota_payload-master\extract_android_ota_payload.py", line 78, in decompress_payload
p = subprocess.Popen([command, '-'], stdout=subprocess.PIPE, stdin=subprocess.PIPE)
File "C:\Program Files\Python39\lib\subprocess.py", line 947, in __init__
self._execute_child(args, executable, preexec_fn, close_fds,
File "C:\Program Files\Python39\lib\subprocess.py", line 1416, in _execute_child
hp, ht, pid, tid = _winapi.CreateProcess(executable, args,
FileNotFoundError: [WinError 2] The system cannot find the file specified
I believe it's failing because it can't find xzcat. I am trying to install MinGW in an effort to resolve that.
Click to expand...
Click to collapse
Try the instructions here to get payload dumper working
toyanucci said:
Try the instructions here to get payload dumper working
Click to expand...
Click to collapse
Okay that worked. I should've just tried that version first instead of the 'newer' one I found.
Now when I try to flash I'm getting
Code:
FAILED (remote: 'Flashing is not allowed for Critical Partitions')
I have found that I can use 'fastboot flashing unlock-critical' to unlock these, but it will wipe the phone.
I really don't want to wipe my device if I can avoid it.
Maybe try just flashing the boot partition
Slikkster2k said:
Now when I try to flash I'm getting
Code:
FAILED (remote: 'Flashing is not allowed for Critical Partitions')
I have found that I can use 'fastboot flashing unlock-critical' to unlock these, but it will wipe the phone.
I really don't want to wipe my device if I can avoid it.
Click to expand...
Click to collapse
Maybe try just flashing the boot partition
toyanucci said:
Maybe try just flashing the boot partition
Maybe try just flashing the boot partition
Click to expand...
Click to collapse
Yeah that was the first thing I tried, no dice.
You have 11.2.4.4 global on your phone right? Would you be able to retrieve the stock boot.img and upload it for me so I can try booting with that? It's a long shot but I'm desperate.
Slikkster2k said:
Yeah that was the first thing I tried, no dice.
You have 11.2.4.4 global on your phone right? Would you be able to retrieve the stock boot.img and upload it for me so I can try booting with that? It's a long shot but I'm desperate.
Click to expand...
Click to collapse
Uploaded to mega here
I found 2 backed up images and I wasn't sure which is 4.4 so I uploaded both to the link for you to try
So I tried fastboot flashing unlock_critical just now, and it fails and says Device already : unlocked!
I am finding that these instructions for restoring the OnePlus 8T do not work at all for the OnePlus 9. My phone boots straight to fastboot on slot a, and if I try fastboot reboot fastboot, it fails to boot to fastboot userspace.
On slot b, it will boot to fastboot userspace, which allows me to flash the partitions I extracted from the payload.bin, BUT the list of files is not the same as for the 8T. I flashed the ones that were in list, and a couple more that had similar names as missing ones, but it's still not a complete list. At no point have I done 'fastboot -w' as I don't want to wipe userspace.
I'm also not sure if I should try to flash every file it extracted to the equivalent partition name, as the instructions for the 8T don't do that.
toyanucci said:
Uploaded to mega here
I found 2 backed up images and I wasn't sure which is 4.4 so I uploaded both to the link for you to try
Click to expand...
Click to collapse
Thanks, didn't work unfortunately.
Slikkster2k said:
So I tried fastboot flashing unlock_critical just now, and it fails and says Device already : unlocked!
I am finding that these instructions for restoring the OnePlus 8T do not work at all for the OnePlus 9. My phone boots straight to fastboot on slot a, and if I try fastboot reboot fastboot, it fails to boot to fastboot userspace.
On slot b, it will boot to fastboot userspace, which allows me to flash the partitions I extracted from the payload.bin, BUT the list of files is not the same as for the 8T. I flashed the ones that were in list, and a couple more that had similar names as missing ones, but it's still not a complete list. At no point have I done 'fastboot -w' as I don't want to wipe userspace.
I'm also not sure if I should try to flash every file it extracted to the equivalent partition name, as the instructions for the 8T don't do that.
Click to expand...
Click to collapse
I had a similar situation with the 7T (and 8T lol) and used the info from the link as a guide to flashing every partition. I did have to wipe the phone though but in the end it booted up which was the biggest concern I had
Related
So I got a pixel recently. I unlocked the bootloader, installed TWRP, and rooted it. However, it's been a few years since I had an unlocked and rooted phone so I forgot that the OTA updates can't be applied. So I decided to go back to the factory image. A quick google search lead me to an article where they said I could select the Full Unroot option in the settings of SuperSU and it would attempt to restore the stock boot image and recovery image. So I did that, and ended up in a boot loop.
Well, then I decided to try flashing the entire factory images from google, using the flash-all.bat file they provide. It seems to flash the bootloader and the radio fine, but when it comes to the part where it flashes everything in the "image-sailfish-nde63l.zip" (I picked this build because it was the one I was on when the pixel arrived) folder it says "Error: failed to load 'image-sailfish-nde63l.zip': not enough space."
I can still get to the TWRP recovery, and I can get to the bootloader, but currently nothing else seems to work. Please, can anyone help me?
UPDATE: The issue was outdated adb and fastboot. I had 1.0.32, once I had the latest versions (1.0.36 right now) I could fix everything.
UPDATE: So I extracted boot and system from the zip file and manually flashed those. It boots now, but when it does it says there are errors with the device and to contact the manufacturer, also a lot of dialog boxes pop up saying various processes have stopped.
I think that if I manually flash the rest of the contents of the zip folder it will work, but there are a lot of files and I'm not sure which partition to flash them too, or which one's are needed. Does anyone know how to manually do what the flash-all.bat script does? Flashing bootloader, radio, system, and boot are not enough it seems. If you read the script it's just doing a 'fastboot -w update' on the zip file.
I hope what I'm saying makes sense. Thanks.
Did you try flashing the stock boot.img to both slots before going back to stock?
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
This is what chainfire recommended in his supersu post when he was talking about flashing twrp. Maybe try doing that and then try using the flashall script. Also make sure your download is not corrupt or something. https://plus.google.com/+Chainfire/posts/CBL8pnKtA8F
Evo_Shift said:
Did you try flashing the stock boot.img to both partitions before going back to stock?
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
This is what chainfire recommended in his supersu post when he was talking about flashing twrp. Maybe try doing that and then try using the flashall script. Also make sure you download is not corrupt or something.
Click to expand...
Click to collapse
No, I didn't do any flashing myself before going back to stock. I selected the "Full unroot" option in SuperSU, based on the first result when googling "unroot pixel".
As soon as I did that I was stuck in a bootloop and I tried to restore the factory images according to the google webpage, but that's when I get the error.
Doing what you said doesn't work either, not even redownloading the image.
Actually, now it's worse. When I select recovery from fastboot menu it shows "No command" with a broken android. So twrp is gone now too.
If anyone can help me at all, that would be amazing, thanks.
UPDATE: So I extracted boot and system from the zip file and manually flashed those. It boots now, but when it does it says there are errors with the device and to contact the manufacturer, also a lot of dialog boxes pop up saying various processes have stopped.
I think that if I manually flash the rest of the contents of the zip folder it will work, but there are a lot of files and I'm not sure which partition to flash them too, or which one's are needed. Does anyone know how to manually do what the flash-all.bat script does? Flashing bootloader, radio, system, and boot are not enough it seems. If you read the script it's just doing a 'fastboot -w update' on the zip file.
I hope what I'm saying makes sense. Thanks.
th3p3r50n said:
Actually, now it's worse. When I select recovery from fastboot menu it shows "No command" with a broken android. So twrp is gone now too.
If anyone can help me at all, that would be amazing, thanks.
Click to expand...
Click to collapse
This happened to me too. That's my current situation. Have adb and fastboot still but can't figure out what steps to fix it.
I think you should focus on why the flash all didn't work. Do you have the latest fastboot? Did you check the md5 of the downloaded rom image? What OS it's your computer running?
How do we verify latest fastboot. I thought that was my issue but don't see where this can be found. I have latest minimal adb and fastboot installed.
fracman said:
How do we verify latest fastboot. I thought that was my issue but don't see where this can be found. I have latest minimal adb and fastboot installed.
Click to expand...
Click to collapse
The commands <adb version> and <fastboot --version> seem to return version numbers. My setup returns:
Android Debug Bridge version 1.0.36
Revision fd9e4d07b0f5-android
and
fastboot version fd9e4d07b0f5-android
respectively
Thank you cntryby429. I assumed I was using the latest versions because I had just installed them through the SDK Manager, turns out I was using version 1.0.32. I found the latest version of Minimal ADB and Fastboot and the flash-all script worked fine. I still had a few issues though, so I did a factory reset and then ran the flash-all script again. Now everything works perfectly again. Thanks so much!
Hi,
I am incredibly new to this and I think I might have managed to destroy this google pixel I just bought. I had attempted to root the phone using magisk after unlocking the bootloader and installing TWRP though I had a little bit of trouble, I was following instructions here https://www.xda-developers.com/google-pixel-3-unlock-bootloader-root-magisk/. I managed to unlock the bootloader but after signing in to the phone again and attempting to install TWRP to get magisk It wouldn't let me access most of my downloads on the phone because TWRP was asking for a password for my user. I tried the passcode I had set but I didn't work I tried rebooting the phone and removing the lock but many apps on the phone once I booted it back no longer worked, specifically settings which is how I was planning on removing the password. I also tried using adb commands to wipe the lock but nothing really seemed to be working so I found a factory reset setting on TWRP and now I have been stuck at the google reset screen for about 5 hours now. Any help is appreciated.
Thanks
ajg32 said:
Hi,
I am incredibly new to this and I think I might have managed to destroy this google pixel I just bought. I had attempted to root the phone using magisk after unlocking the bootloader and installing TWRP though I had a little bit of trouble, I was following instructions here https://www.xda-developers.com/google-pixel-3-unlock-bootloader-root-magisk/. I managed to unlock the bootloader but after signing in to the phone again and attempting to install TWRP to get magisk It wouldn't let me access most of my downloads on the phone because TWRP was asking for a password for my user. I tried the passcode I had set but I didn't work I tried rebooting the phone and removing the lock but many apps on the phone once I booted it back no longer worked, specifically settings which is how I was planning on removing the password. I also tried using adb commands to wipe the lock but nothing really seemed to be working so I found a factory reset setting on TWRP and now I have been stuck at the google reset screen for about 5 hours now. Any help is appreciated.
Thanks
Click to expand...
Click to collapse
What do you mean by "remove the lock" and "wipe the lock"? If you relocked the bootloader, your recovery options are limited. Can you access the phone with adb and/or fastboot? If the bootloader is still unlocked, flash a stock factory image available at https://developers.google.com/android/images. Instructions for flashing are at that URL.
If your bootloader is now locked, can you get to fastboot? If not, I don't know of anything you can do. If you can get to fastboot, you can try to sideload a full OTA image from https://developers.google.com/android/ota. Instructions are at that URL.
If you can recover, forget rooting with TWRP - those instructions are outdated. Just install the Magisk app, and use it to patch boot.img, then flash the patched boot.img. If you need TWRP for other purposes, do not install it, just boot it with "fastboot boot twrp.img".
Never lock the bootloader unless you have a completely stock device. Even then, you risk bricking the phone.
dcarvil said:
What do you mean by "remove the lock" and "wipe the lock"? If you relocked the bootloader, your recovery options are limited. Can you access the phone with adb and/or fastboot? If the bootloader is still unlocked, flash a stock factory image available at https://developers.google.com/android/images. Instructions for flashing are at that URL.
If your bootloader is now locked, can you get to fastboot? If not, I don't know of anything you can do. If you can get to fastboot, you can try to sideload a full OTA image from https://developers.google.com/android/ota. Instructions are at that URL.
If you can recover, forget rooting with TWRP - those instructions are outdated. Just install the Magisk app, and use it to patch boot.img, then flash the patched boot.img. If you need TWRP for other purposes, do not install it, just boot it with "fastboot boot twrp.img".
Never lock the bootloader unless you have a completely stock device. Even then, you risk bricking the phone.
Click to expand...
Click to collapse
Sorry for the lack of clarity. The bootloader was still unlocked I was simply trying to access files in the TWRP menu but I had to enter the pin I put on the phone. When I mentioned that I was trying to remove the lock it was so that I could use the file manager to install through the TWRP menu. I believe the bootloader is still unlocked but I simply cannot really communicate with the phone. It is on, but its suck on a google logo with a loading bar. Aside from adb commands which don't seem to be working as the phone is not being detected Is there any sort of combination of clicking the power button or something similar that may shake the phone out of the resetting loop?
ajg32 said:
Sorry for the lack of clarity. The bootloader was still unlocked I was simply trying to access files in the TWRP menu but I had to enter the pin I put on the phone. When I mentioned that I was trying to remove the lock it was so that I could use the file manager to install through the TWRP menu. I believe the bootloader is still unlocked but I simply cannot really communicate with the phone. It is on, but its suck on a google logo with a loading bar. Aside from adb commands which don't seem to be working as the phone is not being detected Is there any sort of combination of clicking the power button or something similar that may shake the phone out of the resetting loop?
Click to expand...
Click to collapse
Try these instructions - https://www.hardreset.info/devices/google/google-pixel-3/fastboot-mode/
If you can get to fastboot mode, flash a stock image from the URL in my previous post.
If that does not work, google "plxel 3 recovery mode" or "pixel 3 fastboot mode" to try to find something that works. If you can get to fastboot mode, you have a good chance of recovering the phone. Don't try to do anything with TWRP.
dcarvil said:
Try these instructions - https://www.hardreset.info/devices/google/google-pixel-3/fastboot-mode/
If you can get to fastboot mode, flash a stock image from the URL in my previous post.
If that does not work, google "plxel 3 recovery mode" or "pixel 3 fastboot mode" to try to find something that works. If you can get to fastboot mode, you have a good chance of recovering the phone. Don't try to do anything with TWRP.
Click to expand...
Click to collapse
Thank you very much for all the help, I managed to restore the phone pre-TWRP mess. You mentioned rooting by only installing magisk. Would that method be similar to the one described here https://www.rootdroids.com/guides/how-to-root-google-pixel-3-with-magisk-without-twrp/?
ajg32 said:
Thank you very much for all the help, I managed to restore the phone pre-TWRP mess. You mentioned rooting by only installing magisk. Would that method be similar to the one described here https://www.rootdroids.com/guides/how-to-root-google-pixel-3-with-magisk-without-twrp/?
Click to expand...
Click to collapse
Yes, that is the method. Those instructions don't really tell you how to get boot.img though. Unzip the factory image you downloaded. Inside that zip is another zip. Unzip that second zip and boot.img will be extracted.
dcarvil said:
Yes, that is the method. Those instructions don't really tell you how to get boot.img though. Unzip the factory image you downloaded. Inside that zip is another zip. Unzip that second zip and boot.img will be extracted.
Click to expand...
Click to collapse
I believe I got the correct boot.img although now when I try to flash boot the patched img file I get an error. Specifically,
Warning: skip copying boot_a image avb footer (boot_a partition size: 67108864, boot_a image size: 100663296).
Sending 'boot_a' (98304 KB) OKAY [ 2.286s]
Writing 'boot_a' (bootloader) Image missing cmdline or OS version
FAILED (remote: 'Failed to write to partition Bad Buffer Size')
fastboot: error: Command failed
Looking it up it seems like the most common fix is to boot from TWRP
ajg32 said:
I believe I got the correct boot.img although now when I try to flash boot the patched img file I get an error. Specifically,
Warning: skip copying boot_a image avb footer (boot_a partition size: 67108864, boot_a image size: 100663296).
Sending 'boot_a' (98304 KB) OKAY [ 2.286s]
Writing 'boot_a' (bootloader) Image missing cmdline or OS version
FAILED (remote: 'Failed to write to partition Bad Buffer Size')
fastboot: error: Command failed
Looking it up it seems like the most common fix is to boot from TWRP
Click to expand...
Click to collapse
"boot_a image size: 100663296" is the wrong size. How are you transferring boot.img and the patched image between your phone and PC? You should be using adb push/pull. If you did use adb push/pull, I'd need to see all the commands you used, and a directory listing of all the files to see if I can spot something wrong. Also, what version of Magisk?
You could try renaming magisk.apk to magisk.zip and installing the zip with TWRP, but I don't know if that method still works on the Pixel 3. I've never tried that method. Make sure you just boot TWRP (fastboot boot twrp.img), and do not install TWRP. If that breaks things, at least you know how to recover now.
Hopefully I'm in the correct forum. I'm having issues rooting my OnePlus 8 with android 13. I had it rooted when it was still android 11 then tried out the colorOS and switched back. I followed the steps to flash the patched image and I keep getting the error failed remote: no such file or directory. Am I doing something wrong? Thanks in advance
I figured out what I did wrong and it finished...but now it won't boot. I press start and it goes to the boot screen then bad to the bootloader.
Kerrylee1738$$$ said:
Hopefully I'm in the correct forum. I'm having issues rooting my OnePlus 8 with android 13. I had it rooted when it was still android 11 then tried out the colorOS and switched back. I followed the steps to flash the patched image and I keep getting the error failed remote: no such file or directory. Am I doing something wrong? Thanks in advance
Click to expand...
Click to collapse
Did you follow the instruction below:
1. Download zip rom and extract payload.bin
2. Use Fastboot Enhance export boot.img from payload.bin
3. Install Magisk Manager on your phone
4. Copy boot.img to your phone storage
5. Patch boot.img by Magisk Manager
6. Copy Patched file (in Download folder) to your PC and reboot phone to Bootloader Mode
7. Open Windows Power Shell at folder has Patched file and run command
fastboot flash boot patched_file_name.img
There is a guide to clarify and mitigate the error.
Kerrylee1738$$$ said:
I figured out what I did wrong and it finished...but now it won't boot. I press start and it goes to the boot screen then bad to the bootloader.
Click to expand...
Click to collapse
The boot file that you patched is corrupted or invalid.
-- Try to repatch again after you MSM back to stock.
you sure you are in fastboot mode and not fastbootd mode? While bootloader and fastbootd both are different, I believe you know the difference. Next time use command adb reboot bootloader and then flash patched_boot.img
Hi,
I've tried to flash a new magisk-boot img, following this guide, after downloading the signed flashable zip LE2113_11_F.75.
I've patched the boot.img with my magisk app, and after flashing it,my OnePlus 9 doesn't boot anymore.
I've got this error : QUALCOMM CrashDump Mode. dm-verity device corrupted. verity-ctr
I can't boot to TWRP, I tried a fastboot boot and a fastboot flash recovery, but I always get a Qualcomm dump error.
Can someone help me to fix this issue ?
Thanks !
this refrence might help-
Help needed! Qualcomm Crash dump after trying to reinstall magisk upon upgrade to Android 11
Hi, Lost root access after updating my OnePlus 6T to Android 11 a few days back, hence decided to flash magisk_patched image that I had created around 2 months back. Phone didn't like it ofcourse and gave me a QualComm Crash Dump error. After...
forum.xda-developers.com
"The update to [Insert Version Here] does not agree with Magisk which causes it to either fail to complete the update or to die at early boot depending on how bad things were messed up. You can reapply root once the update to [Insert Version Here] is finished though, so you can still have root.
In your case manually upgrading to [Insert Version Here], letting it finish the upgrade, and then installing Magisk again is your best bet, in which case you would either have to find something that understands the update format or manually extract the updated partitions from the payload, iirc"
Hi, thanks for your answer.
I've managed to gain access back to my phone, using the payload.bin from the signed flashable zip, and the fastboot enhance tool.
I've had to flash it on the a slot, as I have errors when trying to flash it on the b slot.
I've managed to boot on TWRP using this one for the encryption support.
I still got the dm-verify error when booting on the b slot, can't flash the payload.bin on it, can't backup it... I'm not sure if it's normal neither how to fix it, as even trying to fastboot flash boot crashes.
I've tried to flash the signed flashable zip in TWRP, and got this :
Flashing A/B zip to inactive slot : B
Step 1/2
Error applying update: 23 (ErrorCode:: kDownloadManifestParseError)
Updater process ended with ERROR: 1
Click to expand...
Click to collapse
AutruiP said:
Hi, thanks for your answer.
I've managed to gain access back to my phone, using the payload.bin from the signed flashable zip, and the fastboot enhance tool.
I've had to flash it on the a slot, as I have errors when trying to flash it on the b slot.
I've managed to boot on TWRP using this one for the encryption support.
I still got the dm-verify error when booting on the b slot, can't flash the payload.bin on it, can't backup it... I'm not sure if it's normal neither how to fix it, as even trying to fastboot flash boot crashes.
I've tried to flash the signed flashable zip in TWRP, and got this :
Click to expand...
Click to collapse
It's not a problem if one slot is broken, it will probably fix itself on the next update.
Hi, thanks for your answer.
The fact that you talked about the next update made me try to locally install the update with the signed flashable zip, using the system updater. It worked and fixed everything !
Thanks
It was posted about 2 hours ago on Asus website, here is the direct link: https://dlcdnets.asus.com/pub/ASUS/...300-2304-user.zip?model=rog phone 5 （zs673ks）
I just updated and phone runs smooth, no data loss during upgrade, magisk and lsposed works.
MarekPietrzak said:
It was posted about 2 hours ago on Asus website, here is the direct link: https://dlcdnets.asus.com/pub/ASUS/ZenFone/ZS673KS/UL-ASUS_I005_1-ASUS-33.0210.0210.200-1.1.300-2304-user.zip?model=rog phone 5 （zs673ks）
I just updated and phone runs smooth, no data loss during upgrade, magisk and lsposed works.
Click to expand...
Click to collapse
hey Marek, i was on android 12, i flashed twrp recovery then i relocked the bootloader!
so i was stuck in bootloader infinity loop, then i downgraded my phone to an very old firmware it is begin with 18 and ends with .raw archive format and mine was beginn 31 and ends wtih zip archive format (it has payload.bin) inside.
so i get failed flashing manuelly the last update of android 12 also the last update (android 13). OTA can nothing getting. what should i do now if you don't mind!?
Edit: the phone doesnt charging and loops now at logo
Hello, you should incrementally update from your version by downloading each upgrade package from Asus site which is newer then your current version and flash them one by one. Or you can find the newest package which you are able to install and repeat this procedure until you can flash the newest Android 13 package. Your current old firmware cannot unpack newest package so you need update by steps.
Check this post: https://forum.xda-developers.com/t/warning-read-before-locking-bootloader.4327977/post-87808387
Other method (untested): Extract latest payload.bin and flash all partitions to inactive slot than change it to active using fastboot
rami88436 said:
hey Marek, i was on android 12, i flashed twrp recovery then i relocked the bootloader!
so i was stuck in bootloader infinity loop, then i downgraded my phone to an very old firmware it is begin with 18 and ends with .raw archive format and mine was beginn 31 and ends wtih zip archive format (it has payload.bin) inside.
so i get failed flashing manuelly the last update of android 12 also the last update (android 13). OTA can nothing getting. what should i do now if you don't mind!?
Edit: the phone doesnt charging and loops now at logo
Click to expand...
Click to collapse
MarekPietrzak said:
Hello, you should incrementally update from your version by downloading each upgrade package from Asus site which is newer then your current version and flash them one by one. Or you can find the newest package which you are able to install and repeat this procedure until you can flash the newest Android 13 package. Your current old firmware cannot unpack newest package so you need update by steps.
Check this post: https://forum.xda-developers.com/t/warning-read-before-locking-bootloader.4327977/post-87808387
Other method (untested): Extract latest payload.bin and flash all partitions to inactive slot than change it to active using fastboot
Click to expand...
Click to collapse
MarekPietrzak said:
Hello, you should incrementally update from your version by downloading each upgrade package from Asus site which is newer then your current version and flash them one by one. Or you can find the newest package which you are able to install and repeat this procedure until you can flash the newest Android 13 package. Your current old firmware cannot unpack newest package so you need update by steps.
Check this post: https://forum.xda-developers.com/t/warning-read-before-locking-bootloader.4327977/post-87808387
Other method (untested): Extract latest payload.bin and flash all partitions to inactive slot than change it to active using fastboot
Click to expand...
Click to collapse
hey, Thanks for replay, i am facing now another messeges.
1- the phone does not charging at all
2- when i plug in into chrage its reboot again and again.
3- the bootloader is open, but when i try to flash any files through bootloader i get:
FAILED (Status read failed (Too many links))
or
FAILED (remote: 'Warning: battery's capacity is very low
to recovery mode i am unable to go there
i tried boot or flash the twrp.img also only boot.img also flash_raw_and_wipe_data.cmd
nothing helps me!!!
Hello, can you try to keep phone on charger for a few hours? Maybe it will charge enough to enter recovery mode. You should never flash twrp by fastboot on a/b devices as they don't have recovery partition. Please restore stock boot.img extracted from payload.bin and after this try booting into fastbootD, not fastboot and then attempt flashing complete firmware package (raw). To boot into fastbootD, keep holding volume keys, when you see a bootloader screen use volume keys to select option "recovery mode". You should now enter stock recovery. Ussing vol keys select option "enter fastboot". You should be now in fastbootD. This is possible only with boot.img without twrp installed as fastbootD is a part of stock recovery, magisk is fine.
Remember to perform all flashing operations with usb port on the left side, the bottom one does not work in bootloader. And make sure you are using latest adb/fastboot binaries, these from popular auto-installers are usually outdated and may cause errors during flashing.
MarekPietrzak said:
Hello, can you try to keep phone on charger for a few hours? Maybe it will charge enough to enter recovery mode. You should never flash twrp by fastboot on a/b devices as they don't have recovery partition. Please restore stock boot.img extracted from payload.bin and after this try booting into fastbootD, not fastboot and then attempt flashing complete firmware package (raw). To boot into fastbootD, keep holding volume keys, when you see a bootloader screen use volume keys to select option "recovery mode". You should now enter stock recovery. Ussing vol keys select option "enter fastboot". You should be now in fastbootD. This is possible only with boot.img without twrp installed as fastbootD is a part of stock recovery, magisk is fine.
Remember to perform all flashing operations with usb port on the left side, the bottom one does not work in bootloader. And make sure you are using latest adb/fastboot binaries, these from popular auto-installers are usually outdated and may cause errors during flashing.
Click to expand...
Click to collapse
I've tried leaving it on overnight and it never charges, there's even no charging lights.
Yesterday I tried flashing via Bugjeager and it didn't work either (betwenn to android devices)
Although the bootloader is unlocked, it gives me a Not Allowed In Lock State message!
the current version of the installed firmware is that old that i flashed WW_ZS673KS_18.0810.2101.95_M2.13.24.9-ASUS_1.1.46_Phone-user.raw, it is non extractable so i cant get the boot.img of it!
I am attaching here the matching boot.img for your 2101.95 firmware. Your phone boots to bootloader as I can see on the video but cannot enter recovery as you have corrupted your boot partition. Can you pm me output of fastboot getvar all command? Please do not post it publicly as it may contain private data such as serial numbers. Good luck!
Are you sure that you have unlocked bootloader? I understand that you have relocked your bootloader and since then your phone never booted into working system. It is not possible to unlock bl with fastboot, only with asus app which requires working Android system
MarekPietrzak said:
I am attaching here the matching boot.img for your 2101.95 firmware. Your phone boots to bootloader as I can see on the video but cannot enter recovery as you have corrupted your boot partition. Can you pm me output of fastboot getvar all command? Please do not post it publicly as it may contain private data such as serial numbers. Good luck!
Are you sure that you have unlocked bootloader? I understand that you have relocked your bootloader and since then your phone never booted into working system. It is not possible to unlock bl with fastboot, only with asus app which requires working Android system
Click to expand...
Click to collapse
wow you are alive haha i thought you not gonna answer me again. ok just 1 second
rami88436 said:
wow you are alive haha i thought you not gonna answer me again. ok just 1 second
Click to expand...
Click to collapse
Sometimes I can be a bit slow to respond as I am on the university during day. Hopefully your issue seems to be possible to be solved just by flashing raw firmware and wiping data partition.
so i was rooted on 12 when update was done i did the usual and hit "later" went into magisk did thr ota to keep root once it booted i was stuck on logo forever, so i flashed original boot.img and booted up good with no root. so then i patched boot in magisk and flashed it and stuck on logo again unless i flash original boot.img. this never happened before. how did you keep root?
rami88436 said:
hey Marek, i was on android 12, i flashed twrp recovery then i relocked the bootloader!
so i was stuck in bootloader infinity loop, then i downgraded my phone to an very old firmware it is begin with 18 and ends with .raw archive format and mine was beginn 31 and ends wtih zip archive format (it has payload.bin) inside.
so i get failed flashing manuelly the last update of android 12 also the last update (android 13). OTA can nothing getting. what should i do now if you don't mind!?
Edit: the phone doesnt charging and loops now at logo
Click to expand...
Click to collapse
if youre still stuck, try to fastboot flash raw firmware and reroot and re update again. twrp only works for me with the magisk twrp installer but then you'll have to re flash patched image as it will remove root
chairman011 said:
so i was rooted on 12 when update was done i did the usual and hit "later" went into magisk did thr ota to keep root once it booted i was stuck on logo forever, so i flashed original boot.img and booted up good with no root. so then i patched boot in magisk and flashed it and stuck on logo again unless i flash original boot.img. this never happened before. how did you keep root?
Click to expand...
Click to collapse
try root your phone through kirnal su
chairman011 said:
if youre still stuck, try to fastboot flash raw firmware and reroot and re update again. twrp only works for me with the magisk twrp installer but then you'll have to re flash patched image as it will remove root
Click to expand...
Click to collapse
hahaha, the owner of this thread had helps me a lot but no way and yesterday i have been lost my imei and isn and the rest.., that was because i tried using miflash.
I did it in the same way as you, just after OTA i installed magisk to inactive slot and rebooted. Maybe you have some incompatible magisk modules which caused bootloop on A13.
chairman011 said:
so i was rooted on 12 when update was done i did the usual and hit "later" went into magisk did thr ota to keep root once it booted i was stuck on logo forever, so i flashed original boot.img and booted up good with no root. so then i patched boot in magisk and flashed it and stuck on logo again unless i flash original boot.img. this never happened before. how did you keep root?
Click to expand...
Click to collapse
MarekPietrzak said:
I did it in the same way as you, just after OTA i installed magisk to inactive slot and rebooted. Maybe you have some incompatible magisk modules which caused bootloop on A13.
Click to expand...
Click to collapse
Oh ok ok makes sense. I had curl module installed. I loved android 13 but I'ma stay on 12 cause the modified read/write script only works on Android 12 and 11 and I need it to uninstall bloatware. Disabling them isn't good enough for me lol I gotta uninstall them completely. I can only do that if system is read/write and this script flashed through two works great to have read/write system. Thank you though
rami88436 said:
hahaha, the owner of this thread had helps me a lot but no way and yesterday i have been lost my imei and isn and the rest.., that was because i tried using miflash.
Click to expand...
Click to collapse
Oh ok ok makes sense. Usually when I face a brick problem I just flash raw firmware fastboot
Actually you can debloat fully systemless, just create magisk module which replaces bloatware directories with empty folders. Or even better use this: https://forum.xda-developers.com/t/module-terminal-debloater-v17-3-2-debloat-systemlessly.3584163/
It is an automated way to make packages fully disappear without remounting system as rw. This module replaces them with empty folders, just like in the manual solution. The packages disappear from system completely and if you install any debloated app from play store or apk it will be installed as user (non-system) app.
chairman011 said:
Oh ok ok makes sense. I had curl module installed. I loved android 13 but I'ma stay on 12 cause the modified read/write script only works on Android 12 and 11 and I need it to uninstall bloatware. Disabling them isn't good enough for me lol I gotta uninstall them completely. I can only do that if system is read/write and this script flashed through two works great to have read/write system. Thank you though
Click to expand...
Click to collapse
MarekPietrzak said:
Actually you can debloat fully systemless, just create magisk module which replaces bloatware directories with empty folders. Or even better use this: https://forum.xda-developers.com/t/module-terminal-debloater-v17-3-2-debloat-systemlessly.3584163/
It is an automated way to make packages fully disappear without remounting system as rw. This module replaces them with empty folders, just like in the manual solution. The packages disappear from system completely and if you install any debloated app from play store or apk it will be installed as user (non-system) app.
Click to expand...
Click to collapse
Oh wow thank you man I'll give it a shot.
I found a gui-based app on github to systemlessly debloat, it is easier to use than this script I posted link to. Here is the link: https://github.com/sunilpaulmathew/De-Bloater
Does anyone have the full RAW firmware, flashed via fastboot? Thank you all
ThienAn2023 said:
Does anyone have the full RAW firmware, flashed via fastboot? Thank you all
Click to expand...
Click to collapse
Mod. edit: private link removed. alecxs