Database Develop

M2004J19AG with boot loop. Want to install TWRP and custom ROM

Hello.
I tried to install TWRP but no luck, only managed to have a constant bootloop. I can enter the menus (vol+ and power pushed, vol- and power pushed).
I tried different roms, no luck.
I managed to install TWRP from this: {Mod edit}
I tried to install different roms:
{Mod edit}
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
I installed vbmeta
[ROM][10.0][LANCELOT] PixelExperience [AOSP]
PixelExperience for Redmi 9 [lancelot] What is this? PixelExperience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, boot animation) Our mission is to offer the maximum possible...
forum.xda-developers.com
fastboot --disable-verity --disable-verification flash vbmeta vbmetaredmi9.img
I tried XiaoMiTool V2, unable to unbrick.
Now I have a brick. No TWRP. No ROM. Bootloop.
7 days waiting for bootloader unlocking? I'm very upset with Xiaomi, really.
ColdIce tried to help me. No luck.
Any hope? Any help? I always wipe partitions. I don't know what to do with this.

Something is happening
Tried flashing my favourite custom rom right now, same recovery,same rom, same kernel , same version,older miui version,same flashing steps
Gets stuck in bootloop now while it didnt before
Something actually bad is hapenning
have been stuck on this:
rom boots into setup
setup works partily
system reboots after getting into the set up
rom tries booting again but something prevents it from booting and just reboots
(i can see it finishes booting but doesnt start)
this seems to be a thing with all custom roms???
why is this happening now
might be the case with the stock rom also my god why the ****

What's happening?
I see there's MiFlashPro tool...
Redmi 9 brick problem solution.
1.if you are above v11.0.8.0 then go and follow below link... https://forum.xda-developers.com/t/disable-authorization-and-unbrick-your-redmi-9.4228213/ ================================== 2.Else follow it...
forum.xda-developers.com

I am ColdICe and i dont understand this?
Nothing changed, there shouldnt be anything stopping it from working, but it doesnt
work
This seems to be a problem with all custom roms and does not include stock roms
The custom roms i know worked couple of days ago, i truly dont know why this is
happening
I was able to reflash the stock rom through a "recovery rom" with no issues
seems like you will have suck it up and enjoy using stock miui
(other than the first boot being a bootloop)
I was using miui 11.0.4 before flashing a custom rom
If any of the guys that port the custom roms want to look into this i would be greatful
Ive tried using "eOS" which has a boot animation which says "my data is MY data" when it finishes booting, so you can tell when it boots
when i boot into the rom it works until i enter the set up , after i do it crashes into a bootloop, i can see that it boots (due to animation) , but just keeps rebooting
If anybody is willing to test this, because i am not anymore, try flashing the vanilla build of arrow OS (link) since it does not include a set up screen
Does this rom also bootloop?, since it seems to be related to a set-up screen (???)
Also do GSI ROMs also have the same issue? If you try theese, please post your findings in the comments
edit: formatting and a small remark

Whats your phone Redmi 9/9 prime/9 power/9T/9C/9A

MRBLYAT said:
Whats your phone Redmi 9/9 prime/9 power/9T/9C/9A
Click to expand...
Click to collapse
This is a thread about redmi 9 lancelot, we both have the same phone

Try this Recovery and modded vbmeta. Still can access fastboot or not????
MRBLYAT said:
Try this Recovery and modded vbmeta. Still can access fastboot or not????
Click to expand...
Click to collapse
while flasing vbmeta need --disable-verity and --disable-verification
flash guide
Recovery : fastboot flash recovery recoveryname.img/ c:\file directory/recoveryname.img
vbmeta : fastboot --disable-verity --disable-verification flash vbmeta vbmeta name.img
use platform tools by android

MRBLYAT said:
flash guide
Recovery : fastboot flash recovery recoveryname.img/ c:\file directory/recoveryname.img
vbmeta : fastboot --disable-verity --disable-verification flash vbmeta vbmeta name.img
use platform tools by android
Click to expand...
Click to collapse
Hello, sorry for the late post, however its detailed in the post that this was already done

MRBLYAT said:
Try this Recovery and modded vbmeta. Still can access fastboot or not????
Click to expand...
Click to collapse
I would try but now i am honestly quite scared to flash any custom roms
Also yes the device can boot into the recovery and fastboot

i
pleasehelpmeiamscared said:
I would try but now i am honestly quite scared to flash any custom roms
Also yes the device can boot into the recovery and fastboot
Click to expand...
Click to collapse
its ok it don't have any virus or ransomware

pleasehelpmeiamscared said:
I would try but now i am honestly quite scared to flash any custom roms
Also yes the device can boot into the recovery and fastboot
Click to expand...
Click to collapse
Hey how your phone, its good or not.....

MRBLYAT said:
flash guide
Recovery : fastboot flash recovery recoveryname.img/ c:\file directory/recoveryname.img
vbmeta : fastboot --disable-verity --disable-verification flash vbmeta vbmeta name.img
use platform tools by android
Click to expand...
Click to collapse
Hi I have a M2004J19AG and this does not work I still have the original recovery.

mispela said:
Hi I have a M2004J19AG and this does not work I still have the original recovery.
Click to expand...
Click to collapse
Are you use platform tools from android

MRBLYAT said:
Are you use platform tools from android
Click to expand...
Click to collapse
Yes I using fastboot and adp but I can flash my recovery but just allways for onces and after I reboot my phone its is gone again. Do u know maybe why this happens?

mispela said:
Yes I using fastboot and adp but I can flash my recovery but just allways for onces and after I reboot my phone its is gone again. Do u know maybe why this happens?
Click to expand...
Click to collapse
How like your recovery is return to stock recovery or no recovery

MRBLYAT said:
How like your recovery is return to stock recovery or no recovery
Click to expand...
Click to collapse
I have no idea how maybe it is just running on the RAM but I dont unterstand why because I flashed it like allways with "fastboot flash recovery".

mispela said:
I have no idea how maybe it is just running on the RAM but I dont unterstand why because I flashed it like allways with "fastboot flash recovery".
Click to expand...
Click to collapse
You can try this
Redmi 9 brick problem solution.
1.if you are above v11.0.8.0 then go and follow below link... https://forum.xda-developers.com/t/disable-authorization-and-unbrick-your-redmi-9.4228213/ ================================== 2.Else follow it...
forum.xda-developers.com

Moderator Announcement
I've removed all references to Telegram from this thread. As an exemption from the last bullet of rule no. 5 of the XDA Forum Rules, we grant only developers the privilege to share references to their social media in their own development threads. These conditions obviously don't apply to this thread. Please refrain from sharing of social media in future. Thanks for your cooperation!
Additionally, unless you already know Telegram is not accepted on XDA as a filehost because a download of a ROM would require a registration on Telegram.
Regards
Oswald Boelcke
Senior Moderator

Magisk patched boot image for A11 beta

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

How to install GSI ROM on OnePlus n100.

Good morning guys.

bentalebnordine said:
Recently I installed lineage os 11 gsi rom on my OnePlus n100 and I wanted to share this experience with you guys :
Click to expand...
Click to collapse
- First you need to download This mini sdk
one_plus_nord_sdk.zip
drive.google.com
It is necessary for the cmd commands to work
- you need also to install the drivers , just go to
Universal ADB Drivers
OnePlus-USB-Drivers.zip
drive.google.com
You need to install both drivers clockworkmod and one plus drivers.
- To unlock the bootloader of your oneplus device just connect it to a Windows computer with USB debugging on and run the following commands from the mini sdk folder that just downloaded
adb devices
Then check your device for confirmation. Then
adb reboot bootloader
Then run the command
fastboot oem unlock
A factory screen will pop-up asking for confirmation, you need to confirm using the volume buttons and the power button.
The phone will reboot into recovery and wipe the data. Please do not interrupt this process or the device will not boot anymore.
So just be patient until the phone finishes booting and set it up and turn the USB debugging on.
bentalebnordine said:
2: after that you need to boot your device on fastboot mode, simply by running the code
adb reboot bootloader
And run the command
fastboot --disable-verity flash vbmeta vbmeta.img
Then this command
fastboot --disable-verity flash vbmeta_system vbmeta_system.img
Click to expand...
Click to collapse
Note that you need to flash both files only once, unless you returned to stock rom.
bentalebnordine said:
Then run the command
fastboot reboot fastboot
Then flash the system of your choice by visiting
Treble-Enabled Device Development A/AB ROMS
Treble-Enabled Device Development A/AB ROMS
forum.xda-developers.com
Note that the file downloaded would be in Xz format, so you need to extract it with 7zip or beanzip and put it on sdk folder.
The file downloaded must end with arm64_bvS.img. Xz and not with arm64_avS.img.xz (bvS not avS) or the phone will stuck on bootloop.
And the file extracted must not exceed 2.6 gB or you will get an error of resizing the system partition.
After flashing the system with the command
fastboot flash system <your system >.img
Run the command
fastboot -w
And finely the command
fastboot reboot
And good luck.
Click to expand...
Click to collapse
If you updated to Android 11 Oxygen OS 11 you need to switch slots by running the command
fastboot --set-active=a
Because android 11 were installed in the b slot.
If you have a problem booting into fastboot mode try extracting the mini sdk provided in the tmp folder on your desktop computer.
The working Android versions are 10,11,12. Now I am running Resurrection Remix ROM android 10 just amazing
NAMING
Some information you should know about knowing what type of gsi it is
<ARCH>_xyZ
<ARCH> can either be arm, a64 (arm32_binder64) or arm64
x can either be a or b
y can either be v, o, g or f
Z can be N or S
b = a/b
a = a-only
g = gapps
o = gapps-go
v = vanilla (no gapps included)
f = floss (free & open source apps instead gapps)
N = no superuser
S = superuser included
Z = dynamic superuser included
-lite = for VNDK Lite vendors (also can help with broken camera even on normal VNDK vendors)
so in most common example "arm64_avZ" is ARM64 A-only vanilla with dynamic superuser
you can simply look to the attached text file.

I am unable to flash any of the .bvs.img gsi files on a Metropcs (11) phone -- BE2015 following the guide. Bootloader is unlocked.
Any help is appreciated.

joegib said:
I am unable to flash any of the .bvs.img gsi files on a Metropcs (11) phone -- BE2015 following the guide. Bootloader is unlocked.
Any help is appreciated.
Click to expand...
Click to collapse
Me I have a BE2013 variant and I was able to flash it with gsi roms using just this guide. I should mention that I am not an expert on rom development.

If I am not mistaken, the BE2013 variant is the global factory unlocked. If so, then maybe these carrier devices will not work with your excellent guide. That being said, I was able to get the DSU to work fine -- AOSP 12.

If you're on the Metro firmware it's a bit tricky. You'll most likely have to still be running Android 10 but you can decrypt the data partition and mount system r/w. After you've accomplished that then it's a piece of cake. Follow this thread, I've been able to remount the system partition read/write on both my Google Pixel running Android 11 and Metro Firmware of OnePlus Nord n100. https://forum.xda-developers.com/t/...-superrw-featuring-makerw-read-write.4247311/

Is GSI for nord n100 updated?

VPH20 said:
Is GSI for nord n100 updated?
Click to expand...
Click to collapse
I'm running Project Arcana Android 12 GSI on my n100 without any issues. I've flashed serval different GSI ROMS but it's by far the best. There's a few things you need to know to successfully flash it but if the steps are followed exactly it's not a problem at all. Here are a few screenshots. It passes safety net basically out the gate with Magisk installed. You'll definitely have to flash the Global firmware to the Metro variant If you happen to be on that version. Luckily, if that's the case someone has already created a modified MSM flash tool that works without any other modifications.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Thanks, the link please.

bentalebnordine said:
Thanks, the link please.
Click to expand...
Click to collapse
There's no verified instructions on this but I took the liberty to upload the necessary files to my Google drive that I used to successfully flash this GSI. First and foremost you'll need to revert back to the global stock firmware 10.5.5 using the msm tool. If you're on the the European firmware then I'm not sure if this will work for you or not and it definitely won't work on the Metropcs version but if you happen to be on the Metro version then you can flash the Global firmware to that device which is what I did. Once you're on stock 10.5.5 enable debugging and oem unlock in developer options and reboot to bootloader. If your bootloader isn't already unlocked enter the command fastboot flashing unlock_critical and use the volume keys to select unlock the bootloader. Your device will be wiped. Wait for the system to reboot then go back into developer options and enable debugging again. Once again reboot to the bootloader. Once there enter the command fastboot -w and wait for it to finish. Once it's complete enter fastboot reboot fastboot and wait to enter fastbootd mode. Use the vendor.img that's included in the zip file I have linked and enter fastboot flash vendor_a (name of vendor).img. Once it's complete enter fastboot reboot bootloader. Once you're back into the bootloader interface enter fastboot -w and wait for it to complete. Then with the twrp file I've supplied enter fastboot boot twrp10.img to boot to recovery (Don't flash only boot!!) When you enter recovery choose wipe, then format data and type yes. Reboot to the bootloader once again. Enter fastboot reboot fastboot and wait to enter fastbootd mode. Once there enter fastboot flash product_a product_gsi.img. Then enter fastboot erase system_a. Next enter fastboot resize-logical-partition system_a 4210000000. Once that's complete enter fastboot reboot bootloader. Once you're in the bootloader enter fastboot -w once again. Once complete boot back to twrp with fastboot boot twrp10.img. This is when you'll flash the GSI and it has to be loaded on your sdcard. Flash it to the system partition and reboot to the bootloader once it's complete. Your next move is important if you want it to boot. Again with the images I've supplied enter fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img then fastboot --disable-verity --disable-verification flash vbmeta_system vbmeta_system.img. Now you can reboot to the system. For some reason twrp won't boot anymore once this GSI is flashed so I've also included the stock boot.img you can patch with Magisk and flash via fastboot to root and pass safety net.
Oneplus_files.zip
drive.google.com
https://xiaomemeindex.com/treble/Arcana/20220226/ProjectArcana_v402-arm64-bgS_20220226.img.xz

sdflowers32 said:
There's no verified instructions on this but I took the liberty to upload the necessary files to my Google drive that I used to successfully flash this GSI. First and foremost you'll need to revert back to the global stock firmware 10.5.5 using the msm tool. If you're on the the European firmware then I'm not sure if this will work for you or not and it definitely won't work on the Metropcs version but if you happen to be on the Metro version then you can flash the Global firmware to that device which is what I did. Once you're on stock 10.5.5 enable debugging and oem unlock in developer options and reboot to bootloader. If your bootloader isn't already unlocked enter the command fastboot flashing unlock_critical and use the volume keys to select unlock the bootloader. Your device will be wiped. Wait for the system to reboot then go back into developer options and enable debugging again. Once again reboot to the bootloader. Once there enter the command fastboot -w and wait for it to finish. Once it's complete enter fastboot reboot fastboot and wait to enter fastbootd mode. Use the vendor.img that's included in the zip file I have linked and enter fastboot flash vendor_a (name of vendor).img. Once it's complete enter fastboot reboot bootloader. Once you're back into the bootloader interface enter fastboot -w and wait for it to complete. Then with the twrp file I've supplied enter fastboot boot twrp10.img to boot to recovery (Don't flash only boot!!) When you enter recovery choose wipe, then format data and type yes. Reboot to the bootloader once again. Enter fastboot reboot fastboot and wait to enter fastbootd mode. Once there enter fastboot flash product_a product_gsi.img. Then enter fastboot erase system_a. Next enter fastboot resize-logical-partition system_a 4210000000. Once that's complete enter fastboot reboot bootloader. Once you're in the bootloader enter fastboot -w once again. Once complete boot back to twrp with fastboot boot twrp10.img. This is when you'll flash the GSI and it has to be loaded on your sdcard. Flash it to the system partition and reboot to the bootloader once it's complete. Your next move is important if you want it to boot. Again with the images I've supplied enter fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img then fastboot --disable-verity --disable-verification flash vbmeta_system vbmeta_system.img. Now you can reboot to the system. For some reason twrp won't boot anymore once this GSI is flashed so I've also included the stock boot.img you can patch with Magisk and flash via fastboot to root and pass safety net.
Oneplus_files.zip
drive.google.com
https://xiaomemeindex.com/treble/Arcana/20220226/ProjectArcana_v402-arm64-bgS_20220226.img.xz
Click to expand...
Click to collapse
Thank you very much my friend for the help, I have the E2013 and it worked.

Awesome, I'm glad to hear it boots on the E2013. If you're on the the Metro version as I was it's difficult but not impossible. Unfortunately for myself I had no guide, just a few pieces of information I picked up here and there that I was able to bundle together into one long process. The great thing about OnePlus is the MSM flash tool. I've flashed firmware from just about every Android manufacturer but it's by far the easiest if you happen to brick your device. So easy even someone with no prior experience wouldn't have an issue using it.
I'd also like to mention that if you're into theming your device, the infamous dev kdragOn has developed an app called repainter that's quite amazing and works really well on this device and ROM. I'm in no way affiliated with him or the advertisement of his app but just making an honest recommendation

sdflowers32 said:
Awesome, I'm glad to hear it boots on the E2013. If you're on the the Metro version as I was it's difficult but not impossible. Unfortunately for myself I had no guide, just a few pieces of information I picked up here and there that I was able to bundle together into one long process. The great thing about OnePlus is the MSM flash tool. I've flashed firmware from just about every Android manufacturer but it's by far the easiest if you happen to brick your device. So easy even someone with no prior experience wouldn't have an issue using it.
Click to expand...
Click to collapse
Exactly.

bentalebnordine said:
Exactly.
Click to expand...
Click to collapse
I sent you a PM if that's okay please and thank you.

sdflowers32 said:
Awesome, I'm glad to hear it boots on the E2013. If you're on the the Metro version as I was it's difficult but not impossible. Unfortunately for myself I had no guide, just a few pieces of information I picked up here and there that I was able to bundle together into one long process. The great thing about OnePlus is the MSM flash tool. I've flashed firmware from just about every Android manufacturer but it's by far the easiest if you happen to brick your device. So easy even someone with no prior experience wouldn't have an issue using it.
I'd also like to mention that if you're into theming your device, the infamous dev kdragOn has developed an app called repainter that's quite amazing and works really well on this device and ROM. I'm in no way affiliated with him or the advertisement of his app but just making an honest recommendation
Click to expand...
Click to collapse
Can I ask a stupid question most likely. I have the BE2015 variant and I followed your instructions to a T and they worked so thank you very much for that.
However if I wish to use another ROM as myself I personally like Android 10 which ROM would you recommend works with our devices? I tried using LineageOS but the Gapps file does not want to install each time I get error.
Edit: Might be time I update my signature lol

Markus214 said:
Can I ask a stupid question most likely. I have the BE2015 variant and I followed your instructions to a T and they worked so thank you very much for that.
However if I wish to use another ROM as myself I personally like Android 10 which ROM would you recommend works with our devices? I tried using LineageOS but the Gapps file does not want to install each time I get error.
Edit: Might be time I update my signature lol
Click to expand...
Click to collapse
Go to this page you will find extra details about how to resize system partition and install larger system files.
https://forum.xda-developers.com/conversations/gsi-roms.14701453/#convMessage-15038845

Okay I just want to say thank you first and foremost to @bentalebnordine and @sdflowers32 because without your both helpful and informative guides I would have taken much longer lol! I can get a guide going completely. With the above guide that sdflowers posted make sure you follow this to a T or you won't boot trust me. Also the GSI images that work best for our device must be the following
system-arm64-ab-img.xz and they will work with no issues I'll put up a cleaned up guide as well to hopefully help others but again this is all only possible with the help of you two first and foremost so thank you!

Markus214 said:
Can I ask a stupid question most likely. I have the BE2015 variant and I followed your instructions to a T and they worked so thank you very much for that.
However if I wish to use another ROM as myself I personally like Android 10 which ROM would you recommend works with our devices? I tried using LineageOS but the Gapps file does not want to install each time I get error.
Edit: Might be time I update my signature lol
Click to expand...
Click to collapse
DOT (Droid on Time) is another GSI that works beautifully on this device but it's Android 11. I personally haven't tried any 10 GSI'S. If you want to update to 11 through stock firmware I already have a DOT super.img I repacked that I'm pretty sure can be flashed without issues with the Android 11 twrp for this device and I'm certain can be flashed via fastbootd mode. Other than project arcana it's the only one I've been impressed with and I've flashed 7 or 8. At least 3 of them I could never get to completely boot after trying every trick of the trade. Arcana is by far the best but DOT runs a tight race. If interested let me know and I'll upload the super.img. I packed it myself so if I ever get bored and just want to go back it would be a much less painless process to flash and I've tested it and it works perfectly.

sdflowers32 said:
DOT (Droid on Time) is another GSI that works beautifully on this device but it's Android 11. I personally haven't tried any 10 GSI'S. If you want to update to 11 through stock firmware I already have a DOT super.img I repacked that I'm pretty sure can be flashed without issues with the Android 11 twrp for this device and I'm certain can be flashed via fastbootd mode. Other than project arcana it's the only one I've been impressed with and I've flashed 7 or 8. At least 3 of them I could never get to completely boot after trying every trick of the trade. Arcana is by far the best but DOT runs a tight race. If interested let me know and I'll upload the super.img. I packed it myself so if I ever get bored and just want to go back it would be a much less painless process to flash and I've tested it and it works perfectly.
Click to expand...
Click to collapse
Thank you very much that would be great! I just downloaded DOT to try it out. I used it before on my 7T and it's great. I just am stubborn I'll say where I like Android 10 the most and 11 not bad but 12 I just don't like the interface and magisk 24 especially for what I do with the phones. I ideally would love to be able to use lineage but when it came time to flash Gapps I kept getting storage error even with resizing. I just want to again say seriously thank you so much without your guide I'd still be screwed

Instructions for flashing DOT GSI
(Start by flashing to stock 10.5.5 with the MSM tool for the device and follow the previous instructions to unlock the bootloader but only to this point)
I decided to edit this because it's been so long since I've removed encryption on this device I completely left out the steps to do so which are imperative. It's much easier to remove encryption on Android 10 than 11 with this device but as far as I know this is the sure fire way to flash an Android 11 GSI on this device. Maybe it can be flashed from 10 but I can't guarantee it as I can with this so here is the revised instructions.
1. Use the MSM tool to revert back to stock and unlock the bootloader
2. Upgrade OTA as far as you can up until version 11.0.4 (Most likely you'll have to use the file I've included in the attachment and perform a local upgrade by placing the zip file in your internal storage to get on this version) Remember this is only for the global firmware but it can be cross flashed with a modded MSM tool.
3. Once you're on 11.0.4 you'll need to format an SD card to exfat which can be done easily with windows because you're going to have to place the super.img on it to be flashed in TWRP. Android supports exfat but for reasons beyond my understanding when you purchase an SD card for Android it comes formatted as fat32 which has a 4 gig limitation.
4. Unzip the 11.0.4 super.img and load it on the SD card along with Magisk.apk. You can either rename the extension from Magisk.apk to Magisk.zip and keep just the one file on your card or copy it and place them both on but nevertheless you'll need the zip file to flash in TWRP after flashing the super partition. Use the TWRP11.img provided in this devices thread and have it placed in your platform-tools folder on PC. Reboot to the bootloader and enter fastboot boot twrp11.img (Or whatever the name of the image happens to be). Once you're in recovery choose wipe, format data and enter yes. Go back and choose install image then select the super11.0.4.img and flash to the super partition. Go back and flash Magisk.zip.
5. Now boot to the bootloader and with the volume keys enter stock recovery.
6. Wipe Data, Cache and System and reboot. I usually reboot back to the bootloader then boot TWRP again just to make sure I can mount all partitions assuring that the device is decrypted.
7. Now all you have to do is place the DOT_SUPER.img on your SD just as you previously did, wipe and format data, then flash it to the super partition just as you did with the stock 11.0.4 super. The boot image is provided as well but I wouldn't advise uninstalling Magisk. Upgrade if you like but it may not boot if you flash the stock boot.img
DOT Files

How To Guide Rooted my Pixel 7

Posting my findings here on how I rooted my p7, no links ,,as always do your homework before attempting . Plus I did a complete factory image reset via adb flashall.bat, I hope I didn't miss a step, Iam coming from a pixel 4a so it's almost the same
1, install latest adb platform tools on computer
2, unlock bootloader on p7
3, Download latest release of pixel 7 factory image on computer
4, unzip and copy init_boot.img to folder in phone
5, install latest Magisk 25.2 on phone
6, patch the init_boot.img with magisk
7, transfer patched file back to adb platform tools folder
8, enter bootloader do a "fastboot flash init_boot magskpatchedfile.img.
9, reboot and test,
I have removed the _a in the cmd line as it appears its not needed
This is what finally worked for me after much testing and reading in the p7p forum. There may be additional steps to get safety net and such to work there is a lot of info on the p7p forum.
Ok,, this how I flashed ,and will flash, the new updates coming out so as not to lose data ,this will NOT do a wipe plus it's faster ,,,,, I know there are multiple other ways but for now I choose this,, hth
1. Download the correct ota file here
https://developers.google.com/android/ota and copy to adb folder
2. Place phone in factory recovery and toggle to apply update from adb,,
3. Open cmd prompt in adb folder type adb sideload factoryota.zip ,,,takes 5-10 minutes to complete, reboot ,,
if rooted,
1 download correct full image zip here
https://developers.google.com/android/images. That matches ota you just flashed,
2 extract the ini.boot.img , patch with magisk and reflash in adb for root

JimJamer8 said:
i tried these steps and now i have your device is corrupt and cannot be trusted, now my phone wont turn on or boot into recovery mode, its not detected by fastboot or adb
Click to expand...
Click to collapse
Does the screen come on at all? In your other post you said it was black. If there's nothing at all on the screen, your phone is probably bricked.

JimJamer8 said:
it doesnt turn on at all
Click to expand...
Click to collapse
Have you tried a hard reset - hold the power button down for 10 seconds or so until the phone vibrates?

JimJamer8 said:
i tried these steps and now i have your device is corrupt and cannot be trusted, now my phone wont turn on or boot into recovery mode, its not detected by fastboot or adb
Click to expand...
Click to collapse
You didn't try the steps I listed as I never said to flash a rooted bootloader

JimJamer8 said:
i tried these steps and now i have your device is corrupt and cannot be trusted, now my phone wont turn on or boot into recovery mode, its not detected by fastboot or adb
Click to expand...
Click to collapse
You may need to disable Verity and Verification. I flashed my stock image back to the phone using the tool here: https://flash.android.com/ and checked the boxes to disable verity and verification, then followed the steps above. Important to note that booting to Bootloader tells you which slot is active, and running the command fastboot flash init_boot magisk_patched_25205_GUID.img automatically patches the active boot slot. From there you just need to run the Universal Safety net fix from KDrag0n and the latest MagiskHide and you should be good to go

hammered58 said:
Posting my findings here on how I rooted my p7, no links ,,as always do your homework before attempting . Plus I did a complete factory image reset via adb flashall.bat, I hope I didn't miss a step, Iam coming from a pixel 4a so it's almost the same
1, install latest adb platform tools on computer
2, unlock bootloader on p7
3, Download latest release of pixel 7 factory image on computer
4, unzip and copy init_boot.img to folder in phone
5, install latest Magisk 25.2 on phone
6, patch the init_boot.img with magisk
7, transfer patched file back to adb platform tools folder
8, boot to bootloader do a " fastboot getvar all " to see which slot is active it tells u somewhere at the top of the list
9, still in fastboot do a "fastboot flash init_boot_a magskpatchedfile.img. The _a is the active slot
10, reboot and test,
This is what finally worked for me after much testing and reading in the p7p forum. There may be additional steps to get safety net and such to work there is a lot of info on the p7p forum
Click to expand...
Click to collapse
Thank you for the help, turned out the _a was screwing me over, works great now!

mnemonical said:
Thank you for the help, turned out the _a was screwing me over, works great now!
Click to expand...
Click to collapse
I know ,,that was messing me up too, it did not work untill I put that part in,, don't ask me why! Lol

Has anyone been able to get the root version of Vanced Youtube to install? I'm getting an error saying that stock app is too new and it can't be downgraded.

googletermsofservice said:
Has anyone been able to get the root version of Vanced Youtube to install? I'm getting an error saying that stock app is too new and it can't be downgraded.
Click to expand...
Click to collapse
I imagine if you can uninstall the stock youtube app you'd be able to install Vanced from there.

atom_jack said:
I imagine if you can uninstall the stock youtube app you'd be able to install Vanced from there.
Click to expand...
Click to collapse
I'll give it a try

googletermsofservice said:
Has anyone been able to get the root version of Vanced Youtube to install? I'm getting an error saying that stock app is too new and it can't be downgraded.
Click to expand...
Click to collapse
Use the non replace version of revanced and disable stock YT

Hitman478™ said:
Use the non replace version of revanced and disable stock YT
Click to expand...
Click to collapse
Revanced Manager app is just going to black screen after install

hammered58 said:
Posting my findings here on how I rooted my p7, no links ,,as always do your homework before attempting . Plus I did a complete factory image reset via adb flashall.bat, I hope I didn't miss a step, Iam coming from a pixel 4a so it's almost the same
1, install latest adb platform tools on computer
2, unlock bootloader on p7
3, Download latest release of pixel 7 factory image on computer
4, unzip and copy init_boot.img to folder in phone
5, install latest Magisk 25.2 on phone
6, patch the init_boot.img with magisk
7, transfer patched file back to adb platform tools folder
8, boot to bootloader do a " fastboot getvar all " to see which slot is active it tells u somewhere at the top of the list
9, still in fastboot do a "fastboot flash init_boot_a magskpatchedfile.img. The _a is the active slot
10, reboot and test,
This is what finally worked for me after much testing and reading in the p7p forum. There may be additional steps to get safety net and such to work there is a lot of info on the p7p forum
Click to expand...
Click to collapse
Question: What did this command do? "fastboot flash init_boot_a magskpatchedfile.img" does it flash or just boot? Would it also be possible to do: "fastboot boot init_boot_a magskpatchedfile.img" and than install in inactive slot with magisk?

AxelM said:
Question: What did this command do? "fastboot flash init_boot_a magskpatchedfile.img" does it flash or just boot? Would it also be possible to do: "fastboot boot init_boot_a magskpatchedfile.img" and than install in inactive slot with magisk?
Click to expand...
Click to collapse
I don't know ,,I just posted what worked for me, your mileage may very!! The "fastboot boot" cmd was usually used for something like twrp afaik

googletermsofservice said:
Revanced Manager app is just going to black screen after install
Click to expand...
Click to collapse
I've it installed and it's working without any issue

AxelM said:
Question: What did this command do? "fastboot flash init_boot_a magskpatchedfile.img" does it flash or just boot? Would it also be possible to do: "fastboot boot init_boot_a magskpatchedfile.img" and than install in inactive slot with magisk?
Click to expand...
Click to collapse
Use fastboot flash init_boot "image.img" without quotes and without specific the partition, it will goes on the active one, for me it has working at first try

hammered58 said:
I don't know ,,I just posted what worked for me, your mileage may very!! The "fastboot boot" cmd was usually used for something like twrp afaik
Click to expand...
Click to collapse
THX, in fact the "fastboot boot" command was used a lot with OnePlus devices because it is safer to boot in the rooted os and when there is an error you can just reboot without the command...and when you install it afterwards with magisk you know it will work

Does Universal Safetynet Fix work?

Just wanted to thank OP. My Pixel 7 arrived about an hour ago, got the bootloader unlocked no problem, then actually I flashed the latest System Image first, then had Magisk patch init_boot.img, flashed that, easy peasy.

hammered58 said:
I don't know ,,I just posted what worked for me, your mileage may very!! The "fastboot boot" cmd was usually used for something like twrp afaik
Click to expand...
Click to collapse
It's usually used to temporarily boot a patched boot image and then you can do direct install in magisk manager

Question soft bricked oneplus 10 pro that worked great with lineage os

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 rooting​get 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 rooting​get 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 rooting​get 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 ?