Related
All,
I've used custom recoveries and Magisk for a long time and it has been awesome - except for when I need to apply OTA system updates. I've been playing with the new method for Magisk installation, but it requires a stock boot.img, then you flash the patched img from fastboot. But I've hit a snag. I have a LG Stylus 3 Plus with an unlocked bootloader and I extracted a stock boot img like this:
Download the latest KDZ (45010d) on LG's site.
Use a KDZ extraction tool to get DZ
Use the same tool to extract the DZ to get the boot.bin file
Rename the boot.bin file to boot.img
This seems to work for Magisk using the method I outlined above. However, 45010d is Oct security patch, and there is a newer OTA from LG (45010e) with the Dec security patch - but there is no KDZ for it. If I apply the update, the system fails to complete the flash, so I trust that I need to restore the stock boot before flashing it, then go through the Magisk patching process again. Unfortunately at that point I'd have no root to start, and thus no way to get the stock boot.img for 45010e.
So.......I've got the OTA file (update.zip) and I see it has a boot.img.p file in it. I'm thinking I need to take that file and use some tool to apply that patch to the 45010d boot.img and then I'd have my 45010e boot.img to apply Magisk to the latest version available, and to keep for the next OTA cycle.
Am I on the right track? If so, can someone help me understand how to do the patch? This applypatch tool looks promising, but I'm not sure about the checksum values I'm supposed to add to the command line.
Thanks for any help.
Oh, I also meant to add that unlock my previous devices this phone, at least when the bootloader is unlocked, can't use fastboot boot to launch TWRP without installing it. That was going to be one approach I tried to use to pull an updated boot.img, but I guess it's a nogo. That, and the irritating requirement to actually press a button to continue to boot an unlocked device so it can show the unlocked warning are my only two major gripes.
Hi,
I am trying to install an OTA using Magisk and the method johnw has outlined. (start Magisk, uninstall and replacing the modded image/boot with the stock ones, then install the OTA, before it asks for a reboot and you reboot - install Magisk on the other boot slot.) this works up to the point where it reboots the phone - then it gets caught in a bootloop for about five times, and then a message appears that it couldn't install the OTA.
Has anyone been able to install the OTA using the outline method?
Basically same Problem here with the non-XL Pixel 2. However after the I think 5 times boot loop I ended up in the Google Logo screen with the Progress bar. However after over 50 minutes it wasn't gone. Hard reset didn't help - stuck again at the same Situation. Will now reflash the phone.
Would be also interested in Feedback from others on how to install the OTA successfully.
srynoname said:
Basically same Problem here with the non-XL Pixel 2. However after the I think 5 times boot loop I ended up in the Google Logo screen with the Progress bar. However after over 50 minutes it wasn't gone. Hard reset didn't help - stuck again at the same Situation. Will now reflash the phone.
Would be also interested in Feedback from others on how to install the OTA successfully.
Click to expand...
Click to collapse
I have run into similar issues in the past. I wasn't sure if I was not getting the sequence of steps correct or not. In the end, I decided that the more straightforward and easiest method for me was just to flash the full factory update (removing the -w to preserve my data). Once upgraded to the latest release successfully, I just fastboot boot TWRP (don't install TWRP), then flash Magisk zip from there. This has worked for me the last several updates with no issues and the entire process takes less than 30 minutes. Perhaps not as elegant as the method recommended in this forum, but less moving parts and steps that can go wrong in my experience.
Good luck!
sb1893 said:
I have run into similar issues in the past. I wasn't sure if I was not getting the sequence of steps correct or not. In the end, I decided that the more straightforward and easiest method for me was just to flash the full factory update (removing the -w to preserve my data). Once upgraded to the latest release successfully, I just fastboot boot TWRP (don't install TWRP), then flash Magisk zip from there. This has worked for me the last several updates with no issues and the entire process takes less than 30 minutes. Perhaps not as elegant as the method recommended in this forum, but less moving parts and steps that can go wrong in my experience.
Good luck!
Click to expand...
Click to collapse
Thanks for your feedback.
Here's another way that I just tested successfully:
E.g. for updating from April to May:
- Still being on April patch Level, patch boot.img from May using MagiskManager, transfer to Computer
- Boot into Bootloader. Flash stock boot Image from April
- Boot into the stock recovery and install the OTA, e.g. using adb sideload
- After the OTA is installed, select to boot into the Bootloader again
- In the Bootloader Flash the patched boot.img from May that was created in the first step
- Reboot phone and enjoy the May update
@sb1893: I think your way is more comfortable though as one doesn't need to prepare a boot Image file.
@srynoname and @sb1893, thanks for the workarounds. I am doing what srynoname suggested, and while it works without any hiccups, I was really really hoping to be able to install either the OTA or a full factory image (without wiping the data) but with preserving magisks and root *without* having to connect my phone to a computer
So if you have any other ideas...
And to be honest... I am more than surprised that we're the only ones struggling with the update process.
@topjohnwu
Do you habe any hints about what we're doing wrong?
I posted this on GitHub but not sure which is the right place to post. Mods feel free to delete whichever one is inappropriate.
I don't think there is an issue with Magisk, however I am having trouble.
I just got my P3aXL brand new from Google. Here are the steps I took once I got my phone:
I updated to the latest October security patches using stock Android.
Once it was on the latest, enabled OEM unlocking inside android.
Rebooted to bootloader and unlocked.
Booted back into Android, setup my account.
Installed latest magisk manager (7.3.5)
Downloaded October system image (bonito-qp1a.191005.007).
Extracted boot.img from the large zip file
Copied boot.img to phone.
Inside magisk manager, clicked install, selected boot.img from phone.
Copied magisk_patched.img from download directory on phone back to my PC.
Rebooted to bootloader and ran fastboot flash boot magisk_patched.img.
From fastboot, ran fastboot reboot
At this point the system bootloops like 3 or 4 times, then stays in bootloader mode saying no valid boot slot. I can fix it by reflashing the factory image (removing the -w from flash-all.bat).
Not sure where to go from here.
I am on the latest version of the sdk tools (v29).
Any help debugging this issue would be great!
I am not new to rooting at all, so I'm comfortable with almost any tool/command line things I can try.
I just received my direct from Google Pixel 4 XL running the June 2020 update and proceeded to root it using the instructions found here https://www.xda-developers.com/google-pixel-4-root-magisk/ after flashing the patched boot.img and rebooting the phone doesn't boot past the G logo; the status bar just loops indefinitely. Is there something I'm missing? Any help would be much appreciated.
I have no modules loaded, no custom kernel or ROM.
Go to recovery and reset the phone,
And reboot the phone in each steps
The guide looks mostly like what I do every month, though I haven't done June yet.
I don't think this will solve your issue, but usually I flash the patched boot image to both slots as Magisk in-place updates seem to fail if I don't...
Code:
fastboot flash boot magisk_patched.img --slot=all
I assume you didn't have any obvious issues with the guide steps aside from not booting after Step 5?
Make sure your platform tools are the newest you can get. Also make sure that you didn't get the Telstra variant of the June update.
If all else fails, try to revert by dirty flashing the (correct) June 2020 stock ROM. You'll only lose root if you do it correctly. (you don't have working root anyways)
Take the giant ZIP file you downloaded to get the boot image, merge it with platform tools and edit the flash-all.bat file... near the bottom, remove the "-w " from the command so it reads
Code:
fastboot update image-coral-qq3a.200605.001.zip
Save the changes and run the .bat file after booting the phone to fastboot and making sure its visible to platform tools.
jljtgr said:
The guide looks mostly like what I do every month, though I haven't done June yet.
I don't think this will solve your issue, but usually I flash the patched boot image to both slots as Magisk in-place updates seem to fail if I don't...
Code:
fastboot flash boot magisk_patched.img --slot=all
I assume you didn't have any obvious issues with the guide steps aside from not booting after Step 5?
Make sure your platform tools are the newest you can get. Also make sure that you didn't get the Telstra variant of the June update.
If all else fails, try to revert by dirty flashing the (correct) June 2020 stock ROM. You'll only lose root if you do it correctly. (you don't have working root anyways)
Take the giant ZIP file you downloaded to get the boot image, merge it with platform tools and edit the flash-all.bat file... near the bottom, remove the "-w " from the command so it reads
Code:
fastboot update image-coral-qq3a.200605.001.zip
Save the changes and run the .bat file after booting the phone to fastboot and making sure its visible to platform tools.
Click to expand...
Click to collapse
Your first suggestion results in the phone booting, but ending up on a black screen with only the power menu
dirty flashing results in a successful unrooted boot, but rooting seems to not be possible for some users including myself. No clue why
Try flashing the patched boot to both boots but don't use the all slots command, do them one at a time, A, then B. See if that gets it.
So I am a fool.
I didn't run these commands using the latest "platform-tools"
but I will remember this instructions if I have issues in the future!
I am on latest platform tools and have tried all options presented and still get black screen with adb access and power menu. Other thoughts?
I just downloaded the full image and was getting ready to patch the boot image and flash it on my 2 day old Pixel 4xl. Maybe I will wait unless others have had success with this. I am on the June update. I made sure I didn't download the Telstra version.
Is there any reason to not just use the "Download Zip" option in Magisk? That always worked fine for me on my last phone.
Thanks, Chris
---------- Post added at 06:27 PM ---------- Previous post was at 06:12 PM ----------
I took the plunge and it booted just fine. I am on a G020J if that help. Hardware MP1.0.
I did not realize that TWRP was not available for the Pixel 4xl yet. What is everyone using for a custom recovery?
reedc83 said:
I just downloaded the full image and was getting ready to patch the boot image and flash it on my 2 day old Pixel 4xl. Maybe I will wait unless others have had success with this. I am on the June update. I made sure I didn't download the Telstra version.
Is there any reason to not just use the "Download Zip" option in Magisk? That always worked fine for me on my last phone.
Thanks, Chris
---------- Post added at 06:27 PM ---------- Previous post was at 06:12 PM ----------
I took the plunge and it booted just fine. I am on a G020J if that help. Hardware MP1.0.
I did not realize that TWRP was not available for the Pixel 4xl yet. What is everyone using for a custom recovery?
Click to expand...
Click to collapse
I feel like the options inside Magisk are for phones that are already rooted to update Magisk. I guess what your edit is saying is that you used to use TWRP with the ZIP?
Anyways, there are no custom recoveries for the same reason there is not TWRP. The partition scheme for Pixel phones that come with Android 10 pre-installed is too different for TWRP to live on it. I don't know enough about this subject, but I thought I read there was no separate recovery partition that could be made custom.
Everyone has been doing it all along, when people have issues it's usually the wrong boot image, wrong complete image, flashed boot image to wrong slot, used the factory cable (yes, it's a thing, don't use it or flashing), don't have the correct and/or latest tools. There was an issue with windows 8.1 and flashing, I don't remember what that was but those of you flashing and still on 8.1 you'll want to do a search for that.
@Brakiss, you may want to try the whole smash if all else has failed... THIS WILL DELETE YOUR DATA!
Start by going over to Goog ---> https://developers.google.com/android/images and getting the full factory image and the latest tools; even if you already did it do it again being careful to verify you have the correct image. While you're grabbing goods get the Magisk APK so you can install it after the image is flashed. For the flashing portion please follow the directions on that page to the letter. Do not use the factory cable; use an A to C. Before you flash run these commands one at a time
fastboot erase system_a
fastboot erase system_b
fastboot erase boot_a
fastboot erase boot_b
fastboot reboot-bootloader
After flashing get the boot image directly from the factory image you downloaded and not any other source and move it over to your phone along with the Magsik APK. Install magisk manager and then use it patch the boot image. You'll take that over to your PC and flash it as usual but do it to both slots and do them separately, do not use the all slots.
jljtgr said:
I feel like the options inside Magisk are for phones that are already rooted to update Magisk. I guess what your edit is saying is that you used to use TWRP with the ZIP?
Anyways, there are no custom recoveries for the same reason there is not TWRP. The partition scheme for Pixel phones that come with Android 10 pre-installed is too different for TWRP to live on it. I don't know enough about this subject, but I thought I read there was no separate recovery partition that could be made custom.
Click to expand...
Click to collapse
Correct, there is no recovery partition anymore. That has been a thing for a while now and not specific to the Pixel. My Moto x4 that I used prior to the Pixel 4xl had the recovery in the boot image but there was still TWRP for it. Whenever rooting that phone you have to boot a custom recovery image then from in there flash the separate custom recovery image/zip installer. It would modify the recovery that is embedded into the boot image.
I really hope that devs smarter than myself will figure it out and make a way to get TWRP on there.
On Android 11 Beta 2.5, I patch the original boot image, I then send it via fastboot, I tried flashing all partitions, manually _a and _b and stuck on Google logo ... When I put back the original boot.img, everything works properly. Miss my root but haven't seen any help on this :| Worked until I switched to 11 Beta ...
I have the problem too
Just as Chronos300 reported, I got stuck on the G logo. Some of my problem may be self-inflicted since I was not careful enough in following the directions: evidently it's important to finish the process for unlocking the bootloader before going to fastboot again to flash the Magisk boot image. I got stuck on the G logo but thought that I would have my way out by flashing the July factory image.
Most of that process worked out: things were good until the end when I saw a lot of messages about files that aren't present in image-coral-qq3a.200805.001.zip like boot.sig or recovery.img. I guess these are optional: the *.sig files may be intended to contain a checksum or hash and the recovery.img may just have gone away with the recovery partitions. Finally was an error that was fatal:
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
Click to expand...
Click to collapse
That's awful cheery. I see that the difference between flash-all.sh and flash-base.sh is that the former has the "fastboot -w update" that Shayded talks about. I tried running the update command as Shaded recommends, without the -w switch. This time it got farther, but this time the final message was "failed to extract 'product.img': I/O error"
Sure enough, image-coral-qq3a.200805.001.zip contains no product.img file. Is this my problem, or is the solution somewhere else? Would an older factory image have the missing file?
Sigh of relief
My phone's back in the land of the living. I had noticed the links on the factory-image page for the flash tool. Thinking that maybe these were better maintained, I thought to try out the August update for coral.
The flash tool downloaded whatever big image it grabs and then started into the installation. After a few minutes the fastbootd screen came up and the progress bar went to about 80%--and then everything hung. Hoping on hope, I decided I could leave it like this all night if I had to.
It might have taken half an hour, but it did finally come up with the screen saying everything had updated. Sure enough, it made it through the boot and came up to the setup screens.
Enabled developer mode, saw that the bootloader was indeed unlocked, and went about setting some settings. Haven't tried root yet, but it's sure great to be back in business!
epic_task said:
{...}
Sure enough, image-coral-qq3a.200805.001.zip contains no product.img file. Is this my problem, or is the solution somewhere else? Would an older factory image have the missing file?
Click to expand...
Click to collapse
Personally, I don't understand how you ended up without product.img... it's literally half of the internal ZIP file. (you're not supposed to extract this ZIP, anyways)
jljtgr said:
Personally, I don't understand how you ended up without product.img... it's literally half of the internal ZIP file. (you're not supposed to extract this ZIP, anyways)
Click to expand...
Click to collapse
No, I never altered that zip file and was not trying to extract individual files from it when making that final run of fastboot update.
What I can tell you is that I was sleepy by the time I was doing that. There were two things I missed noting at the time but see this morning: product.img is indeed in the internal zip file and a message a couple of lines above the final error message (I had left the terminal window open):
extracting product.img (2102 MB) to disk...ziparchive W 08-18 00:00:43 31524 31524 Zip: unable to allocate 2204832024 bytes at offset 0: No space left on device
Click to expand...
Click to collapse
I would think that my failing to wait for a complete boot with an unlocked bootloader before attempting to flash magisk_patched.img did something unfortunate to the partitioning scheme. Evidently the web-based flash tool cleared it up.
Maybe I'm suggesting the obvious... but do you have 2-4GB available on every drive? It's complaining there's no available space. Typically product.img is split into 500MB parts and sent separately... so you'd need at least 2x the space available for the parts.
The flash-all is generic and looks for some files which are not used by these phones. This failure described is usually the wrong cord, you must use a USB A to USB C rather than a C to C. If not that it's going to be a tools/driver issue. There are a number of guides which can show how to find and delete old drivers and reinstall new drivers. Removing the W gets rid of the wipe but doesn't otherwise affect the flashing and will have nothing to do with it's success or failure; you are in effect dirty flashing when you remove it from the flash-all.
I successfully flashed my European oneplus 10 pro using the instructions - see link below.
Everything worked VERY WELL, except texts/sms I could'nt receive but could send.
I spend hours and hours making it perfect.
I had the perfect phone.
So if someone wants to know how to use lineageos with full GAPS, just follow the link below.
Then being so STUPID, for no need and no reason I continued following the same instructions and tried to root the phone.
And then this disaster happened that boot is looping and I cannot run: fastboot reboot fastboot.
Meaning that I cannot repair my phone.
All I can do is push the volume down and go to recovery mode. That's all.
My PC can send fastboot commands but I cannot go to the menu where it's chinese and english and from which I could run commands to flash my phone properly back to where it was.
I don't care loosing the data and loosing so many hours of effort, but I REALLY need my phone back to work.
This is the link from this forum to the instructions that really helped me with my Oneplus 10 pro (that I bought by mistake).
LINK THAT WORKS WITH ONEPLUS 10 PRO AND LINEAGE 19.
How to flash a GSI on Oneplus 10 PRO/T
MAKE A BACKUP THIS WILL WIPE ALL YOUR DATA! Check your warrenty> IF YOU BRICK IS YOUR OWN RESPONSIBILIT! What does not work? Fingerprint face unlock native camera app(Use gcam) no notification slider no modular refresh rate no auto...
forum.xda-developers.com
and this is where I CRUSHED down by running this:
The rootingget you latest magisk here
Install it on your phone
transfer the boot.img you extracted to your phone
open magisk and install it on the boot.img
the patched boot img will be in the download folder move it to your pc
open the fastboot tools folder and open a terminal
adb reboot bootloader fastboot flash boot magisk_patched.img
when your booted open magisk and direct install magisk.
than just reboot
Modules you'll need
BootloopSaver
safetynet-fix
Shamiko
and enable zygisk in the magisk settings.
THANK YOU FOR YOUR HELP !!!
This should work for you
Note: You are already in FastbootD (Recovery).
Follow the steps on this site to Flash A stock ROM above using the Fastboot Enhance Tool
https://www.droidwin.com/flash-stoc...-brick/#STEP_1_Download_Fastboot_Enhance_Tool
Feel free to download Fastboot Enhance Tool.zip (backup location)
yedashare said:
I successfully flashed my European oneplus 10 pro using the instructions - see link below.
Everything worked VERY WELL, except texts/sms I could'nt receive but could send.
I spend hours and hours making it perfect.
I had the perfect phone.
So if someone wants to know how to use lineageos with full GAPS, just follow the link below.
Then being so STUPID, for no need and no reason I continued following the same instructions and tried to root the phone.
And then this disaster happened that boot is looping and I cannot run: fastboot reboot fastboot.
Meaning that I cannot repair my phone.
All I can do is push the volume down and go to recovery mode. That's all.
My PC can send fastboot commands but I cannot go to the menu where it's chinese and english and from which I could run commands to flash my phone properly back to where it was.
I don't care loosing the data and loosing so many hours of effort, but I REALLY need my phone back to work.
This is the link from this forum to the instructions that really helped me with my Oneplus 10 pro (that I bought by mistake).
LINK THAT WORKS WITH ONEPLUS 10 PRO AND LINEAGE 19.
How to flash a GSI on Oneplus 10 PRO/T
MAKE A BACKUP THIS WILL WIPE ALL YOUR DATA! Check your warrenty> IF YOU BRICK IS YOUR OWN RESPONSIBILIT! What does not work? Fingerprint face unlock native camera app(Use gcam) no notification slider no modular refresh rate no auto...
forum.xda-developers.com
and this is where I CRUSHED down by running this:
The rootingget you latest magisk here
Install it on your phone
transfer the boot.img you extracted to your phone
open magisk and install it on the boot.img
the patched boot img will be in the download folder move it to your pc
open the fastboot tools folder and open a terminal
adb reboot bootloader fastboot flash boot magisk_patched.img
when your booted open magisk and direct install magisk.
than just reboot
Modules you'll need
BootloopSaver
safetynet-fix
Shamiko
and enable zygisk in the magisk settings.
THANK YOU FOR YOUR HELP !!!
Click to expand...
Click to collapse
Savio Dantes said:
This should work for you
Note: You are already in FastbootD (Recovery).
Follow the steps on this site to Flash A stock ROM above using the Fastboot Enhance Tool
https://www.droidwin.com/flash-stoc...-brick/#STEP_1_Download_Fastboot_Enhance_Tool
Feel free to download Fastboot Enhance Tool.zip (backup location)
Click to expand...
Click to collapse
Thank you Savio, but this is my main issue, I cannot enter fastbootD.
Whether using the tool "fastboot enhance" or using the command line. I cannot reach FastboodD.
When I try to reach this using the tool, it's looping with no error log.
And when I try from CMS:
C:\Users\me\Downloads\from dumper> fastboot reboot fastboot
Rebooting into fastboot OKAY [ 0.000s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
It also still sounds like your recovery.img and/r boot.img still may be corrupted.
this needs to MATCH in BOTH slots A & B
Try this:
https://forum.xda-developers.com/t/...e-rom-root-and-recovery.4525451/post-87806713
Also, fastboot reboot fastboot
is only telling your device to reboot BACK into fast boot
This list should help you navigate things a bit better:
-- Find & Validate Device Post Startup--
adb devices
-- Reboot Device to Fastboot mode (Bootloader) --
adb reboot bootloader
-- Root device with Magisk patched boot image --
fastboot flash boot magisk_patched.img
-- Reboot to system --
fastboot reboot
-- Flash Recovery --
fastboot flash recovery twrp.img
-- Reboot to system --
fastboot reboot
-- Boot to Recovery | FastbootD from ADB--
adb reboot recovery
-- Boot to Recovery | FastbootD from FASTBOOT--
fastboot reboot recovery
yedashare said:
and this is where I CRUSHED down by running this:
The rootingget you latest magisk here
Install it on your phone
transfer the boot.img you extracted to your phone
open magisk and install it on the boot.img
the patched boot img will be in the download folder move it to your pc
open the fastboot tools folder and open a terminal
adb reboot bootloader fastboot flash boot magisk_patched.img
when your booted open magisk and direct install magisk.
than just reboot
Click to expand...
Click to collapse
This is where your fatal mistake was.... the red line above is incorrect !
It should have been, "adb reboot bootloader" THEN "fastboot boot magisk_patched.img"
you never want to straight FLASH any modified boot image when working with an a/b partition device.. or pretty much ANY device running the dynamic partition scheme. This is because of the way the partitions are laid out. Something about flashing a modified boot.img directly breaks things... BUT you had a DOUBLE FLAW in yours because you not only flashed a modified boot img directly, you ALSO flashed "magisk_patched.img" to android, which does not have a file named "magisk_patched.img" in its manifest.... android has "boot.img" in its manifest. Understand?? I have seen this flaw ALL OVER the place and no one seems to notice that, so im hoping several ppl finally realize the MAJOR error that they are making.
The android manifest has the EXACT names of every file to be loaded into the system, and any deviations to that list must be incorporated into the BUILD structure when making the os. In other words, say you wanted to build a custom flavor of android from scratch, and have the recovery be installed as a homemade "TWRP" build. Now im talking about FULL BUILD not a port, or remake of an already built OS... I am meaning "1st install... everything from the ground, up.... similar to what lineage does" ... THAT is where the origin android manifest is built... and all updates/custom mods/roms that are made from the original that you created, MUST FOLLOW the exact same file structure, and naming scheme that is in your original manifest. recovery.img needs to be named recovery.img .... system.img needs to be named system.img .... in the case of most of these boot loop issues (BUT NOT ALL) alot of ppl either find some guide written by a person who has never rooted a device in their life, but felt inclined to serve up some untested set of steps that had a fatal flaw they overlooked. THAT is what happened here.
Whoever wrote those steps obviously never tried them before writing them, or they would have had the same result as you. You CANNOT have a completely different named boot image FLASHED to the boot partition! Those steps are instructing you to FLASH, "magisk_patched.img" to the boot partition, where android is expecting "boot.img" ... if those steps were at all to be taken to be the real intention of the author then he would have needed to add a line prior instructing the reader to "rename the file from "magisk_patched.img" and make it "boot.img" ... then in the next step it would have been "fastboot flash boot boot.img" ... but i still DO NOT recommend that, as like i said it can cause errors. If at all possible you always want to BOOT the patched boot.img file 1st, because if there is any problems with it or android rejects it, all you have to do is restart the phone, and it will boot back up to the UNMODIFIED boot.img ! ... but if you FLASH it, then it has no old boot.img to revert to... thus the boot loop..... (bad boot.img ..... reset ..... bad boot.img ..... reset ... bad boot.img ..... reset...) <-Bootloop.
When you BOOT the patched image, though and it loads into the OS with no problems, then you have confirmation that the file was patched properly and is compatible with your OS. NOW you can simply open the Magisk app, and it will see your phone as already rooted, so you can then tap the install button, and then MAGISK will install itself correctly to the right partition, AND make a backup of the file that is from your stock os.
hope that sheds some light and also more ppl take time to read this! Ill make a regular post about it shortly for more visibility.
cheers
u can try to fix sms mms problem using this thread
xiaomi 12/moto edge x30(or any device with sm8450) sms＆ims error · Issue #2246 · phhusson/treble_experimentations
Now gsi is able to boot on devices with sm8450.But sms doesn't work.And ims settings shows "not supported" .I tried to install q-ims.apk or ims.apk from the stock rom.Still ,ims does work at all. A...
github.com
@yedashare
@dladz maybe we can share it groups ?
beatbreakee said:
This is where your fatal mistake was.... the red line above is incorrect !
It should have been, "adb reboot bootloader" THEN "fastboot boot magisk_patched.img"
you never want to straight FLASH any modified boot image when working with an a/b partition device.. or pretty much ANY device running the dynamic partition scheme. This is because of the way the partitions are laid out. Something about flashing a modified boot.img directly breaks things... BUT you had a DOUBLE FLAW in yours because you not only flashed a modified boot img directly, you ALSO flashed "magisk_patched.img" to android, which does not have a file named "magisk_patched.img" in its manifest.... android has "boot.img" in its manifest. Understand?? I have seen this flaw ALL OVER the place and no one seems to notice that, so im hoping several ppl finally realize the MAJOR error that they are making.
The android manifest has the EXACT names of every file to be loaded into the system, and any deviations to that list must be incorporated into the BUILD structure when making the os. In other words, say you wanted to build a custom flavor of android from scratch, and have the recovery be installed as a homemade "TWRP" build. Now im talking about FULL BUILD not a port, or remake of an already built OS... I am meaning "1st install... everything from the ground, up.... similar to what lineage does" ... THAT is where the origin android manifest is built... and all updates/custom mods/roms that are made from the original that you created, MUST FOLLOW the exact same file structure, and naming scheme that is in your original manifest. recovery.img needs to be named recovery.img .... system.img needs to be named system.img .... in the case of most of these boot loop issues (BUT NOT ALL) alot of ppl either find some guide written by a person who has never rooted a device in their life, but felt inclined to serve up some untested set of steps that had a fatal flaw they overlooked. THAT is what happened here.
Whoever wrote those steps obviously never tried them before writing them, or they would have had the same result as you. You CANNOT have a completely different named boot image FLASHED to the boot partition! Those steps are instructing you to FLASH, "magisk_patched.img" to the boot partition, where android is expecting "boot.img" ... if those steps were at all to be taken to be the real intention of the author then he would have needed to add a line prior instructing the reader to "rename the file from "magisk_patched.img" and make it "boot.img" ... then in the next step it would have been "fastboot flash boot boot.img" ... but i still DO NOT recommend that, as like i said it can cause errors. If at all possible you always want to BOOT the patched boot.img file 1st, because if there is any problems with it or android rejects it, all you have to do is restart the phone, and it will boot back up to the UNMODIFIED boot.img ! ... but if you FLASH it, then it has no old boot.img to revert to... thus the boot loop..... (bad boot.img ..... reset ..... bad boot.img ..... reset ... bad boot.img ..... reset...) <-Bootloop.
When you BOOT the patched image, though and it loads into the OS with no problems, then you have confirmation that the file was patched properly and is compatible with your OS. NOW you can simply open the Magisk app, and it will see your phone as already rooted, so you can then tap the install button, and then MAGISK will install itself correctly to the right partition, AND make a backup of the file that is from your stock os.
hope that sheds some light and also more ppl take time to read this! Ill make a regular post about it shortly for more visibility.
cheers
Click to expand...
Click to collapse
Thank you, BB, for the clear explanations about respecting the structure of the partitions and not messing directly with the boot partition using a modified img.
Do I need to reach the conclusion that my phone is broken forever and there is nothing I can do to fix it?
I thought that as long as I reach the recovery mode, I can still fix it.
If you have a brilliant solution just as brilliant as your teaching, could you please help me restoring my phone to a functional state?
And BTW, it was a TRIPLE FLAW, because I had a wonderful lineageos 19 working like a charm with GAPS and I just wanted to root it for no reason.
Many thanks for your efforts.
Damn. Nice to know Lineage works well on this phone with extensive tweaking. GSI's can be pretty unstable from what I've seen, missing cell reception and the like.
Yeah, flashing that image killed the phone. I've seen some people recover by flipping their boot slot to the other one and forcing the phone to boot the stock boot there. But if you've flashed to both slots, you're most likely SOL and need a MSM flash. In which case, you could try flashing the complete stock boot image for your OOS version you were on before moving to GSI to both slots as sort of a last resort, but even then I've only seen minimal success.
Savio Dantes said:
Also, fastboot reboot fastboot
is only telling your device to reboot BACK into fast boot
This list should help you navigate things a bit better:
-- Find & Validate Device Post Startup--
adb devices
-- Reboot Device to Fastboot mode (Bootloader) --
adb reboot bootloader
-- Root device with Magisk patched boot image --
fastboot flash boot magisk_patched.img
-- Reboot to system --
fastboot reboot
-- Flash Recovery --
fastboot flash recovery twrp.img
-- Reboot to system --
fastboot reboot
-- Boot to Recovery | FastbootD from ADB--
adb reboot recovery
-- Boot to Recovery | FastbootD from FASTBOOT--
fastboot reboot recovery
Click to expand...
Click to collapse
I appreciate your help a lot.
I tried all the commands you showed, but I keep going back to this error:
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
I guess it is like a computer. The BIOS move to the Master Boot Record and it moves to the operating system.
It my case, the boot record or boot loader is broken.
Someone suggested to use
Savio Dantes said:
Also, fastboot reboot fastboot
is only telling your device to reboot BACK into fast boot
This list should help you navigate things a bit better:
-- Find & Validate Device Post Startup--
adb devices
-- Reboot Device to Fastboot mode (Bootloader) --
adb reboot bootloader
-- Root device with Magisk patched boot image --
fastboot flash boot magisk_patched.img
-- Reboot to system --
fastboot reboot
-- Flash Recovery --
fastboot flash recovery twrp.img
-- Reboot to system --
fastboot reboot
-- Boot to Recovery | FastbootD from ADB--
adb reboot recovery
-- Boot to Recovery | FastbootD from FASTBOOT--
fastboot reboot recovery
Click to expand...
Click to collapse
I appreciate your help a lot.
I tried all the commands you showed, but I keep going back to this error:
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
I guess it is like a computer. The BIOS move to the Master Boot Record and it moves to the operating system.
It my case, the boot record or boot loader is broken.
Someone suggested to use MSM.
I understand that MSM is no longer available.
Any other direction how I can just fix the booting process?
And this is another error I received which gets closer to the source of the problem:
FAILED (remote: 'Failed to load/authenticate boot image: Bad Buffer
I’m assuming Adb does not work?
why don't we get boot_debug and vendor_boot_debug images to debug and then boot into fastbootd and flash it again, why waste time researching these unrelated things.
Arealhooman said:
I’m assuming Adb does not work?
Click to expand...
Click to collapse
Yes right, adb doesn't work, only fastboot is still alive
TuLy2702 said:
why don't we get boot_debug and vendor_boot_debug images to debug and then boot into fastbootd and flash it again, why waste time researching these unrelated things.
Click to expand...
Click to collapse
Thanks for taking time to answer.
Could you be more specific?
I SAVED MY PHONE
BACK ONLINE
THANKS TO THIS POST:
[TOOL] Oppo/Realme Flash .OFP File on Bootloader
A tool to flash .ofp files in bootloader mode without needing MSM Tool, an alternative to official realme tool. THE DEVICE MUST HAVE THE BOOTLOADER UNLOCKED Features soft unbrick install stock firmware switch device region Credits...
forum.xda-developers.com
WHICH BROUGHT ME BACK TO FASTBOOTD
AND FROM THERE I USED FASTBOOT ENHANCED AND FLASHED PAYLOAD.BIN
AND MY PHONE IS BACK EXACTLY AS IT WAS WHEN I PURCHASED IT
YES!!!!!!!!!!!!!!!!!
One of the reasons why I decided to wipe this stupid oxygen os is because they limited my notifications to 5 seconds WTF ?!!
I didn't mention that I have previously bricked my first OnePlus 10 pro completely, so much so that I received a new one from the provider.
I flashed it successfully using Lineageos 19 and brickED it again trying to root it.
Now, I'll be looking for a solution to remove this stupid f%#$%# limit for Whatsapp notification. Any suggestion?
And I'll wait for an advanced modified ROM for OnePlus 10 PRO.
That's true that it worked very well using Lineageos 19, but text/sms didn't work and I saw that ROAMING was greyed out, so I cannot say if it works or not.
A BIG THANK TO ANYBODY WHO TRIED TO HELP ME.
BOTTOM LINE, ALWAYS HELP YOURSELF FIRST AND NEVER GIVE UP.
I spent over 100 hours on this phone, and here I am back from scratch, but at least with a WORKING PHONE.
yedashare said:
I SAVED MY PHONE
BACK ONLINE
THANKS TO THIS POST:
[TOOL] Oppo/Realme Flash .OFP File on Bootloader
A tool to flash .ofp files in bootloader mode without needing MSM Tool, an alternative to official realme tool. THE DEVICE MUST HAVE THE BOOTLOADER UNLOCKED Features soft unbrick install stock firmware switch device region Credits...
forum.xda-developers.com
WHICH BROUGHT ME BACK TO FASTBOOTD
AND FROM THERE I USED FASTBOOT ENHANCED AND FLASHED PAYLOAD.BIN
AND MY PHONE IS BACK EXACTLY AS IT WAS WHEN I PURCHASED IT
YES!!!!!!!!!!!!!!!!!
One of the reasons why I decided to wipe this stupid oxygen os is because they limited my notifications to 5 seconds WTF ?!!
I didn't mention that I have previously bricked my first OnePlus 10 pro completely, so much so that I received a new one from the provider.
I flashed it successfully using Lineageos 19 and brickED it again trying to root it.
Now, I'll be looking for a solution to remove this stupid f%#$%# limit for Whatsapp notification. Any suggestion?
And I'll wait for an advanced modified ROM for OnePlus 10 PRO.
That's true that it worked very well using Lineageos 19, but text/sms didn't work and I saw that ROAMING was greyed out, so I cannot say if it works or not.
A BIG THANK TO ANYBODY WHO TRIED TO HELP ME.
BOTTOM LINE, ALWAYS HELP YOURSELF FIRST AND NEVER GIVE UP.
I spent over 100 hours on this phone, and here I am back from scratch, but at least with a WORKING PHONE.
Click to expand...
Click to collapse
THIS WAS TOO GOOD TO BE TRUE !
After I thought everything was back, I noticed that the battery stopped charging.
I flashed again Lineageos and it worked but yet the battery didn't charge.
I re run the python script but this time using another OFP and it showed successful.
And yet it successfully killed my phone. Completely dead for the second time.
Hundreds of $ and of hours for a F^&& phone.
Huge lesson to learn here about choices.
EoS
yedashare said:
THIS WAS TOO GOOD TO BE TRUE !
After I thought everything was back, I noticed that the battery stopped charging.
I flashed again Lineageos and it worked but yet the battery didn't charge.
I re run the python script but this time using another OFP and it showed successful.
And yet it successfully killed my phone. Completely dead for the second time.
Hundreds of $ and of hours for a F^&& phone.
Huge lesson to learn here about choices.
EoS
Click to expand...
Click to collapse
you make me laugh
yedashare said:
EoS
Click to expand...
Click to collapse
Damn. I think what happened is you lost your persist.img when initially flashing the first ofp, that thing controls low level stuff like fingerprint unlock and charger cable auth I've seen on these forums. I'm not sure there's a way to get it back either outside of a MSM Flash, certainly haven't seen one here.
Prant said:
Damn. I think what happened is you lost your persist.img when initially flaahing the first ofp, that thing controls low level stuff like fingerprint unlock and charger cable auth I've seen on these forums. I'm not sure there's a way to get it back either outside of a MSM Flash, certainly haven't seen one here.
Click to expand...
Click to collapse
It's okay to spend a little money. It's very risky to do it yourself
Did you managed to get fingerprint working on gsi ?