Database Develop

[GUIDE][REDMI 7A] Root with Magisk on Miui 11.0.7 Global

Well, a lot of people wanting to root global miui 11.0.7 and not being able to... So I did it on my Global redmi 7a - MIUI 11.0.7 Global.
Simple though. Apart from whats being said, u can update Magisk to v20.+ after flashing
the 19 version, through the app Magisk Manager automatically installed after flashing.
Prerequisites & Downloads:
- Your bootloader must be unlocked (https://en.miui.com/unlock/)
- ADB and Fastboot -> I did on windows version, maybe can be done on linux...
- patched boot.img for miui 11.0.7 global
- vbmeta.img
- Magisk v19.3 zip -> place it on the root of your external sdcard
This is basically copied from cg730620's post [Guide][Redmi 7A] TWRP, Root with Magisk, Custom ROM [GSI][Pie] and Avedroid's vid
1 - Unlock bootloader and flash stock miui 11.0.7 recovery rom, using miflash 2017
CAREFUL! On the lower right corner check the first option, "clean all", or you may end up with a locked bootloader.
-> exactly the same from the quoted post from now on, what differs is the files and we are only flashing magisk v19.3
"2. Install Minimal ADB and Fastboot
3. Rename patched boot file to boot.img
4. Rename custom recovery file to recovery.img
5. Place boot.img, recovery.img, vbmeta.img in Program Files (x86)/Minimal ADB and Fastboot/ folder
6. Turn off your phone.
7. Reboot phone to fastboot mode by holding Volume-down button while pressing On/Off-button. You know you are in fastboot mode when you see a cartoon bunny.
8. Connect the phone to your PC via USB.
9. On your PC open command prompt and nagivate to ADB folder, or open command prompt window directly from right-click menu in ADB folder; just right-click on empty space and choose 'Open command prompt here'
10. In command prompt, enter the following commands:
Code:
Code:
fastboot flash boot boot.img
Code:
Code:
fastboot flash vbmeta vbmeta.img
Code:
Code:
fastboot flash recovery recovery.img
11. Now reboot to recovery: Press Volume-Up button on your phone and enter the following in command prompt:
or just turn off the phone and reboot by holding Volume-Up and On/Off button (release On/Off when phone turns on, keep holding Volume-Up until you see screen of TWRP recovery)
12. Swipe to allow modifications. If TWRP asks for PIN, enter the PIN code you set for your unlock screen.
13. In TWRP choose Wipe > Advanced Wipe. Select 'Dalvik / ART cache', 'System', 'Data', 'Cache'. Then Swipe to Wipe.
18. In TWRP choose Install. Select the Magisk zip-file on your phone and then Swipe to confirm flash.
Reboot to system, open Magisk, update and there u go.
Same steps of the beginning of Avedroid's video, only with modified boot.img and Magisk Version
https://www.youtube.com/watch?v=NSs08O6uGVI&t=324s
After 16:30 of the video he flashes a custom gsi rom which is not of the interest of this thread, just flash magisk.
Thanks to all who made it possible, especially Avedroid and cg730620
Post questions and answers here, please, NOT in PM.
Good luck!

Thank's it's work fine on custom gsi too, i just flash patch boot, vbmeta, finally install magisk success

I did everything right, however, when it came to installing Magisk, the following error occurred: "Updater process ended with ERROR: 1".
So I redid the whole process, but before installing Magisk I did the following: I went to Mount, I deselected the System partition and after that the installation proceeded normally.
Well, I don’t know if this is the best way to fix this problem, I don’t understand much of these things, but it ended up working for me.
Thanks for the post
I will do some tests to see if everything is working.

Can I just do this on MIUI 11.0.5 Global?

Omborkar said:
Can I just do this on MIUI 11.0.5 Global?
Click to expand...
Click to collapse
Download patched boot.img for ur rom instead of 11.0.7 boot.img I uploaded. Or patch it yourself.

I have a problem. Everytime I do the wipe it says only: "Failed to mount "vendor"(invalid argument)"
What to do?

Google play not certified... after flashing and installed magisk... Got solution??? Thanks

I've rooted my MoKee OS Android 10 rom. Can somebody help me change the system font? The font changer module in Magisk is not appearing in the search bar.

vincecabalan said:
I've rooted my MoKee OS Android 10 rom. Can somebody help me change the system font? The font changer module in Magisk is not appearing in the search bar.
Click to expand...
Click to collapse
I Tried To Root Mokee But Failed. Can You Please Tell Me How You Root Mokee

Hello, what files do I need to rename to boot.img and recovery.img? I'm lost
3. Rename the patched boot file to boot.img
4. Rename the custom recovery to recovery.img

RsAbubokor4 said:
I Tried To Root Mokee But Failed. Can You Please Tell Me How You Root Mokee
Click to expand...
Click to collapse
Extract boot.img of installer mokee.zip Patch boot image https://patcher.yaalex.xyz/ select include magisk Expect to do uploud after downloading rename boot.img sdcard Go twrp flash boot install magisk manager apk
Credit to @idcamper

vincecabalan said:
Extract boot.img of installer mokee.zip Patch boot image https://patcher.yaalex.xyz/ select include magisk Expect to do uploud after downloading rename boot.img sdcard Go twrp flash boot install magisk manager apk
Credit to @idcamper
Click to expand...
Click to collapse
I did according to this advice, uploaded boot.img to this site. Magisk works, but Wifi won't work . When I uploaded boot.img, Wifi works, then it shows that Magisk is not installed, but it was installed.

speed_cars said:
I did according to this advice, uploaded boot.img to this site. Magisk works, but Wifi won't work . When I uploaded boot.img, Wifi works, then it shows that Magisk is not installed, but it was installed.
Click to expand...
Click to collapse
try this process after flash zip of the last magisk from reset factory

Can i do this on miui 11.0.3.0 indian rom based on Android 10. If yes then i need recovery.img pls help.

4. Rename custom recovery file to recovery.img
- where i can download this?, or this is the outcome of step 1?

Everything works fine, exept password. When i set new password, let's say it is 1234, i set the password in the setting, then i press the power button for lock screen, i put the password in as usual, but it just says try again over and over, im pretty sure that it is not my fault. Thanks for reply.

Anyone have patched boot 11.0.4?

jurubebaamarga said:
Well, a lot of people wanting to root global miui 11.0.7 and not being able to... So I did it on my Global redmi 7a - MIUI 11.0.7 Global.
Simple though. Apart from whats being said, u can update Magisk to v20.+ after flashing
the 19 version, through the app Magisk Manager automatically installed after flashing.
Prerequisites & Downloads:
- Your bootloader must be unlocked (https://en.miui.com/unlock/)
- ADB and Fastboot -> I did on windows version, maybe can be done on linux...
- patched boot.img for miui 11.0.7 global
- vbmeta.img
- Magisk v19.3 zip -> place it on the root of your external sdcard
This is basically copied from cg730620's post [Guide][Redmi 7A] TWRP, Root with Magisk, Custom ROM [GSI][Pie] and Avedroid's vid
1 - Unlock bootloader and flash stock miui 11.0.7 recovery rom, using miflash 2017
CAREFUL! On the lower right corner check the first option, "clean all", or you may end up with a locked bootloader.
-> exactly the same from the quoted post from now on, what differs is the files and we are only flashing magisk v19.3
"2. Install Minimal ADB and Fastboot
3. Rename patched boot file to boot.img
4. Rename custom recovery file to recovery.img
5. Place boot.img, recovery.img, vbmeta.img in Program Files (x86)/Minimal ADB and Fastboot/ folder
6. Turn off your phone.
7. Reboot phone to fastboot mode by holding Volume-down button while pressing On/Off-button. You know you are in fastboot mode when you see a cartoon bunny.
8. Connect the phone to your PC via USB.
9. On your PC open command prompt and nagivate to ADB folder, or open command prompt window directly from right-click menu in ADB folder; just right-click on empty space and choose 'Open command prompt here'
10. In command prompt, enter the following commands:
Code:
Code:
fastboot flash boot boot.img
Code:
Code:
fastboot flash vbmeta vbmeta.img
Code:
Code:
fastboot flash recovery recovery.img
11. Now reboot to recovery: Press Volume-Up button on your phone and enter the following in command prompt:
or just turn off the phone and reboot by holding Volume-Up and On/Off button (release On/Off when phone turns on, keep holding Volume-Up until you see screen of TWRP recovery)
12. Swipe to allow modifications. If TWRP asks for PIN, enter the PIN code you set for your unlock screen.
13. In TWRP choose Wipe > Advanced Wipe. Select 'Dalvik / ART cache', 'System', 'Data', 'Cache'. Then Swipe to Wipe.
18. In TWRP choose Install. Select the Magisk zip-file on your phone and then Swipe to confirm flash.
Reboot to system, open Magisk, update and there u go.
Same steps of the beginning of Avedroid's video, only with modified boot.img and Magisk Version
After 16:30 of the video he flashes a custom gsi rom which is not of the interest of this thread, just flash magisk.
Thanks to all who made it possible, especially Avedroid and cg730620
Post questions and answers here, please, NOT in PM.
Good luck!
Click to expand...
Click to collapse
I wish to obtain root / access to magisk,
Wanting to know if I can do this without losing data (having to delete system data)
Thank you

Hello.
So I was trying to root my Redmi 7A - v10.2.1 with TWRP 3.3.1 but now I am stuck in a bootloop.
What I did:
1. Flash boot.img
2. Flash recovery.img
3. Flash vbmeta.img
4. reboot
Phone rebooted to system and TWRP was installed.
Then I booted to TWRP to install Magisk-v23.0.zip,
I went to Advanced Wipe, then wiped 'Dalvik / ART cache', 'System', 'Data', 'Cache'.
When I rebooted, it went into a bootloop, when I go to TWRP it says 'No OS INSTALLED".
What did I do wrong? And how to recover?
Thanks.

Cinox said:
I did everything right, however, when it came to installing Magisk, the following error occurred: "Updater process ended with ERROR: 1".
So I redid the whole process, but before installing Magisk I did the following: I went to Mount, I deselected the System partition and after that the installation proceeded normally.
Well, I don’t know if this is the best way to fix this problem, I don’t understand much of these things, but it ended up working for me.
Thanks for the post
I will do some tests to see if everything is working.
Click to expand...
Click to collapse
Im also getting the same error,, but what do you mean by "deselected the System partition". I see "system_root" in Mount but not "System"

[Guide] [GSI] Install Lineage OS 17.x [Q] Redmi 7A

WARNING:
You need to backup your data before installing. I am not responsible for any damage or loss that might occur. Proceed at your own risk.
Tested with MIUI version 10.2.5.0 Global.
Bootloader must be unlocked (https://en.miui.com/unlock/)
1. Unpack Minimal ADB and Fastboot to C:\ drive of your PC
2. Rename patched boot to boot.img. Rename recovery file to recovery.img. Place boot.img, recovery.img, vbmeta.img in ADB folder.
3. Enable USB-debugging in developer options on your phone.
4. Connect phone with PC via USB. Reboot phone to fastboot mode (Volume-down + Power).
5. On your PC open command prompt and nagivate to ADB folder.
6. Enter the following commands:
Code:
fastboot flash boot boot.img
Code:
fastboot flash vbmeta vbmeta.img
Code:
fastboot flash recovery recovery.img
7. Reboot to recovery (Volume-Up + Power; release Power when phone turns on, keep holding Volume-Up until you see screen of TWRP). If TWRP asks for PIN, enter the PIN of your unlock screen.
8. Wipe Dalvik / ART cache, System, Data, Cache. Format Data > Yes
Do not wipe Internal Storage!
9. Unpack the downloaded GSI Rom and move it to your phone.
10. Flash the Rom (Install image).
11. Reboot to Recovery.
12. Move files Magisk, Permissiver, FM-Radio fix, GApps to your phone.
13. Flash Magisk (optional)
14. Flash Permissiver
15. Flash GApps (optional).
If you get 'insufficient space' error, first resize System partition.
16. Flash FM-Radio fix:
In TWRP, Mount System. Then flash fix.
17. Reboot system and enjoy.
-----------------------
Downloads:
Minimal ADB and Fastboot
https://forum.xda-developers.com/showthread.php?t=2317790
GSI Rom:
https://forum.xda-developers.com/pr...lopment/gsi-lineageos-17-0-gsi-archs-t4004673
You need to get a64_bvN version from folder lineage-17.x.
Patched boot img file:
http://www.mediafire.com/folder/zx0167qqaknc3/Redmi_7a_patched_boot
Check your MIUI version in System, so that you download the correct boot img file.
TWRP recovery
https://www.mediafire.com/file/irntn5ccdiguuuu/TWRP-20191023-3.3.1.0-pine.img/file
vbmeta file
http://www.mediafire.com/file/bgpn9b87b4t8yye/vbmeta.img/file
Magisk
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Permissiver
https://androidfilehost.com/?fid=6006931924117940902
GApps (choose 'ARM' & '10.0')
https://opengapps.org/
FM Radio fix:
https://androidfilehost.com/?fid=8889791610682885147

After installing Gsi
After installing Gsi, can I get the fast boot mode later

Ts40 said:
After installing Gsi, can I get the fast boot mode later
Click to expand...
Click to collapse
Yes, you can still get into fastboot mode.

TWRP recovery
https://www.mediafire.com/file/irntn5ccdiguuuu/TWRP-20191023-3.3.1.0-pine.img/file
- is this the recovery.img?

Hi! I'm on Lineage 17.1 March 2020.
If I want to try out Lineage 18 - do I have do go back to MIUI global first before flashing Lineage with fastboot?
Other question:
Actually the internal storage seems to be encrypted. It is shown if I attached it to my PC but only some cryptical filenames are there - no chance to load anything to the internal storage for flashing it with TWRP. Any chances to "decrypt" it or make it "visible"?

kra_ppo said:
Hi! I'm on Lineage 17.1 March 2020.
If I want to try out Lineage 18 - do I have do go back to MIUI global first before flashing Lineage with fastboot?
Other question:
Actually the internal storage seems to be encrypted. It is shown if I attached it to my PC but only some cryptical filenames are there - no chance to load anything to the internal storage for flashing it with TWRP. Any chances to "decrypt" it or make it "visible"?
Click to expand...
Click to collapse
i would recommend you to flash MIUI global first, because if somethings goes wrong you can't say whats the reason for the error.
and the encrypted folders can be deleted in twrp by format data -->yes

raijinlee said:
TWRP recovery
https://www.mediafire.com/file/irntn5ccdiguuuu/TWRP-20191023-3.3.1.0-pine.img/file
- is this the recovery.img?
Click to expand...
Click to collapse
thats the one i'm using and never had problems with this, so yes

Not allowed to flash recovery anymore?

I am trying to flash the LineageOS recovery for LineageOS 18. I have previously already installed LineageOS 17 on my phone with no issues like 2 or 3 weeks ago. However, I am now trying to update to LineageOS 18 and I am now not allowed to flash the new recovery to my phone. Nothing has changed since I was last able to flash a recovery to my phone except I just changed my battery out today (since the old one was faulty), but I doubt that would interfere with the software or firmware, right? I have verified my phone is unlocked, I have verified my ADB and Pixel drivers are all up to date, and I have tried flashing on two computers, Linux and Windows. An additional thing to note that may or may not give you a clue as to what is going on is that I am able to boot into a TWRP img, but it no longer prompts me for a decryption password, and when I go to mount > decrypt and enter my pin, it says the password is incorrect.
You guys got any clue how I can fix this?
EDIT:
Here is my terminal output:
Code:
[[email protected] ~]$ sudo fastboot flash recovery /home/chris/Downloads/lineage-18.1-20210409-microG-coral-recovery.img
[sudo] password for user:
Sending 'recovery' (65536 KB) OKAY [ 1.710s]
Writing 'recovery' FAILED (remote: 'Not allowed to flash (recovery)')
fastboot: error: Command failed
I have to use sudo because it doesnt detect my device when I dont use sudo for some dumbass reason...

Deleted

cray12399 said:
I am trying to flash the LineageOS recovery for LineageOS 18. I have previously already installed LineageOS 17 on my phone with no issues like 2 or 3 weeks ago. However, I am now trying to update to LineageOS 18 and I am now not allowed to flash the new recovery to my phone. Nothing has changed since I was last able to flash a recovery to my phone except I just changed my battery out today (since the old one was faulty), but I doubt that would interfere with the software or firmware, right? I have verified my phone is unlocked, I have verified my ADB and Pixel drivers are all up to date, and I have tried flashing on two computers, Linux and Windows. An additional thing to note that may or may not give you a clue as to what is going on is that I am able to boot into a TWRP img, but it no longer prompts me for a decryption password, and when I go to mount > decrypt and enter my pin, it says the password is incorrect.
You guys got any clue how I can fix this?
EDIT:
Here is my terminal output:
Code:
[[email protected] ~]$ sudo fastboot flash recovery /home/chris/Downloads/lineage-18.1-20210409-microG-coral-recovery.img
[sudo] password for user:
Sending 'recovery' (65536 KB) OKAY [ 1.710s]
Writing 'recovery' FAILED (remote: 'Not allowed to flash (recovery)')
fastboot: error: Command failed
I have to use sudo because it doesnt detect my device when I dont use sudo for some dumbass reason...
Click to expand...
Click to collapse
There is no "recovery" partition anymore, it is in the boot.img. The "recovery" is a virtual partition that doesnt exist as its own partition. Review the steps in LOS 18.1 and it points out to flash the boot.img, then reboot to recovery once you have flashed boot.img and rebooted
Reboot to bootloader
Flash the provided boot.img to both slots (fastboot flash --slot all boot boot.img)
Reboot into recovery and factory reset for initial install
Sideload the latest build of Lineage OS (adb sideload lineage.zip)
I will also note that you seem to be using the MicroG (no GAPPs) version so I dont know if the steps are different than official LOS, but I dont think so. I would follow the dev steps to the T and not try older methods (I did the same thing I am warning against), I used my old and trusty, time tested steps, that always worked in previous devices, but do not anymore on Pixels.
It sounds like whatever happened broke your decryption of /data (but its a guess without knowing more). You might be stuck and need to format /data, or you can try to sideload the update and see if it works. Without enough info, I am guessing so provide more info and we can try to help better.
Also to note, if you use the boot.img / sideload method, you do not need TWRP, nor to mount anything. Its all done from the "native recovery" provided by LOS but you might have screwed up the/data decryption, IDK.
If this were me, and in your shoes, I would restore a FULL FACTORY image (not an OTA) with the -W left intact on BOTH slots so it rewrites my partition layout and undoes whatever funkiness' happened. You would lose everything, but it would get you back into working shape.
If you do not want to start over (and I dont disagree, it sucks), then follow the TWRP forum for coral (PX4):
TWRP Coral [Official]
[RECOVERY] TWRP 3.5.0_10-0 - TeamWin Recovery Project [/B] Introduction: Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP...
forum.xda-developers.com

GROOVYJOSHCLARK said:
There is no "recovery" partition anymore, it is in the boot.img. The "recovery" is a virtual partition that doesnt exist as its own partition. Review the steps in LOS 18.1 and it points out to flash the boot.img, then reboot to recovery once you have flashed boot.img and rebooted
Reboot to bootloader
Flash the provided boot.img to both slots (fastboot flash --slot all boot boot.img)
Reboot into recovery and factory reset for initial install
Sideload the latest build of Lineage OS (adb sideload lineage.zip)
I will also note that you seem to be using the MicroG (no GAPPs) version so I dont know if the steps are different than official LOS, but I dont think so. I would follow the dev steps to the T and not try older methods (I did the same thing I am warning against), I used my old and trusty, time tested steps, that always worked in previous devices, but do not anymore on Pixels.
It sounds like whatever happened broke your decryption of /data (but its a guess without knowing more). You might be stuck and need to format /data, or you can try to sideload the update and see if it works. Without enough info, I am guessing so provide more info and we can try to help better.
Also to note, if you use the boot.img / sideload method, you do not need TWRP, nor to mount anything. Its all done from the "native recovery" provided by LOS but you might have screwed up the/data decryption, IDK.
If this were me, and in your shoes, I would restore a FULL FACTORY image (not an OTA) with the -W left intact on BOTH slots so it rewrites my partition layout and undoes whatever funkiness' happened. You would lose everything, but it would get you back into working shape.
If you do not want to start over (and I dont disagree, it sucks), then follow the TWRP forum for coral (PX4):
TWRP Coral [Official]
[RECOVERY] TWRP 3.5.0_10-0 - TeamWin Recovery Project [/B] Introduction: Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP...
forum.xda-developers.com
Click to expand...
Click to collapse
Where are you getting the boot.img for lineage? I don't see one anywhere. All I've seen is recovery.img as me the rom zip.
Thanks in advance Josh.

flash713 said:
Where are you getting the boot.img for lineage? I don't see one anywhere. All I've seen is recovery.img as me the rom zip.
Thanks in advance Josh.
Click to expand...
Click to collapse
If using the official, it's provided in the download section. If not, and it's unofficial, then usually the devs of that ROM provide it. If that's not being done by the devs of the version you are using, then you need to use python and dumper script. It uses python and script (dumper) to pull out the boot.img from the payload.bin (within the zip).
Just keep in mind that I do not use the MicroG version so it's possible the steps vary but I doubt it. What I stated above is usually the method for custom, LOS, even official firmware versions to pull out the boot.img.
Send me the link to download what you're using to try and reproduce it so I can advise better (ROM/recovery/ETC).

Magisk and TWRP not working as aspected

H there,
TWRP and Magisk are not wot working as aspected.
First I tried to flash TWRP by
Code:
fastboot flash recovery recovery.img
but received
Code:
(bootloader) Invalid partition name recovery
So I had to just boot it
Code:
fastboot boot recovery.img
After that I "installed recory image" in TWRP itself. But when I try to boot into recovery it get stuck. So i had to do
Code:
fastboot boot recovery.img
again.
Any ideas what i did wrong or how to solve this?
Then I installed Magisk. To do that I had to drop an boot.img file, let the Magisk-App creates an pahteched version of it and than, back in bootloader
Code:
fastboot boot magisk_patched...img
Now i have root access. But when rebooting regularly the Magisk-App has no root and so all the other apps also not. So i had to boot that img again.
That CAN'T be the right way.
Thx in advance!

It's probably because you have A/B partitions on your device. To flash it successfully you'll need TWRP 3.5.0+. You can learn more about why is it so different from this XDA article.
You can check if your device supports A/B partitions through this app.
Follow this guide on how to flash it on A/B partitions, you can get TWRP from here (Beckham) or here (Addison).
Goodluck.

Best custom ROM for OnePlus Nord 100.

Hi guys, Lineage has just launched an amazing GSI custom rom, here is a link
https://sourceforge.net/projects/andyyan-gsi/files/latest/download
The installation process is simple just go to
How to install GSI ROM on OnePlus n100.
Good morning guys.
forum.xda-developers.com
This rom is on the latest Android version (12), very stable, battery friendly and very customizable and backed with the latest security patches (February 05 2022)
To enjoy double tape anywhere on the screen to sleep just download those two files
APKs - Google Drive
drive.google.com
install them and set lawnchair as a default launcher, activate device administrator for it , go to launcher settings gestures double tap, that's it.

Well, I managed to finally install ... you are correct. Runs completely smooth. Is the partition large enough to install gapps ... and of course, how to install. I would like to use 12.

Unfortunately not, because the ultimate size of the system partition is 2.6gb
If you want to install the Gapps there is another ROM
caos-v224-201029-arm64-bgN.img.xz
You can find it on xda
Notice this ROM ends with bgN.img.xz
If it's g it's full (with gapps)
If it's v it's vanilla (without gapps).
Generally if the xz file exceeds 740mb, then the extracted file will surpass 2.6gb
You can verify this with 7zip the size of the extracted file will be on the right hand of the window of the 7zip program.
I forgot to to tell you that the Gapps will be included on the xz file.

bentalebnordine said:
Unfortunately not, because the ultimate size of the system partition is 2.6gb
If you want to install the Gapps there is another ROM
caos-v224-201029-arm64-bgN.img.xz
You can find it on xda
Notice this ROM ends with bgN.img.xz
If it's g it's full (with gapps)
If it's v it's vanilla (without gapps).
Generally if the xz file exceeds 740mb, then the extracted file will surpass 2.6gb
You can verify this with 7zip the size of the extracted file will be on the right hand of the window of the 7zip program.
I forgot to to tell you that the Gapps will be included on the xz file.
Click to expand...
Click to collapse
I will give it a try, but it is not A12, correct?

It's not, I think it's A10
By the way to activate audio and d2w go to phh settings

bentalebnordine said:
It's not, I think it's A10
By the way to activate audio and d2w go to phh settings
Click to expand...
Click to collapse
I just checked -- the *.img file is 2.2. I will give it a try, though I wish it were a12.

I'm trying to flash a Lineage ROM that's 2.438 GB, but it says "Not enough space to resize partition". You said under 2.6 GB is fine so am i doing something wrong? I assume it's "fastboot flash system" to install.
Edit: Just now tried the one from your post and it's the same problem.

thomaskmaagaard said:
I'm trying to flash a Lineage ROM that's 2.438 GB, but it says "Not enough space to resize partition". You said under 2.6 GB is fine so am i doing something wrong? I assume it's "fastboot flash system" to install.
Edit: Just now tried the one from your post and it's the same problem.
Click to expand...
Click to collapse
Are you coming from Android 11 oxygen OS?

bentalebnordine said:
Are you coming from Android 11 oxygen OS?
Click to expand...
Click to collapse
I am, yes.

thomaskmaagaard said:
I am, yes.
Click to expand...
Click to collapse
Then you should switch to the a slot by running the command
fastboot --set-active=a
And start all over again.

bentalebnordine said:
Then you should switch to the a slot by running the command
fastboot --set-active=a
And start all over again.
Click to expand...
Click to collapse
I did that the first time. Also tried erasing system and product (didn't expect it to make a difference..). Can't seem to get it to flash anything. I can flash stock vbmeta and system and it boots fine again...

thomaskmaagaard said:
I did that the first time. Also tried erasing system and product (didn't expect it to make a difference..). Can't seem to get it to flash anything. I can flash stock vbmeta and system and it boots fine again...
Click to expand...
Click to collapse
I think you should reboot fastboot after switching to slot a. and flash vbmeta and vbmeta_system and run the command
fastboot reboot fastboot.
Then the command
fastboot flash system <your system>.img
Then the command
fastboot - w
Then the command
fastboot reboot
That's it.

bentalebnordine said:
I think you should reboot fastboot after switching to slot a. and flash vbmeta and vbmeta_system and run the command
fastboot reboot fastboot.
Then the command
fastboot flash system <your system>.img
Then the command
fastboot - w
Then the command
fastboot reboot
That's it.
Click to expand...
Click to collapse
I've been trying that, but i don't get past flashing system since it throws that error. It is a be2013 so it shouldn't have any issues. I've never had problems flashing recoveries and boot images.

thomaskmaagaard said:
I've been trying that, but i don't get past flashing system since it throws that error. It is a be2013 so it shouldn't have any issues. I've never had problems flashing recoveries and boot images.
Click to expand...
Click to collapse
Try booting in TWRP for Android 10 that you can find on the roms and recoveries section, if it boots you are correct, if not just boot in TWRP Android 11 click reboot and click reboot in a slot if the courent slot is b.
To boot on TWRP just run the command
fastboot boot twrp.img

So.. I'm thinking, maybe the problem is that I have OOS11 on both slots? Don't ask me why, it's a long story, but I do. Is it only possible to flash over OOS10?

thomaskmaagaard said:
I'm trying to flash a Lineage ROM that's 2.438 GB, but it says "Not enough space to resize partition". You said under 2.6 GB is fine so am i doing something wrong? I assume it's "fastboot flash system" to install.
Edit: Just now tried the one from your post and it's the same problem.
Click to expand...
Click to collapse
yea i was tryna do the same exact thing and i messed around bricked my phone!! recovery.img doesnt even work to fix it,with the exception of twrp flashed in recovery i dont get a dang thing except either a complete black screen or "qualcomm crash dump". im stumped. even got another n100, same exact model, and everything i did before to unlock the network and bootloader isnt working anymore.

fastboot delete-logical-partition product
That command will allow for resizing of system partition and you can flash GAPPS, although its better to find a GSI with GAPPS baked in, as you'll have errors with GAPPS otherwise
Also, anyone with the flash issue of "system partition not big enough" ... the 2.6GB isn't the ROM.img, but after install. Use a GSI ROM that's around 1.9GB at largest, and it should fit. IMG files are compressed, similar to something like a ZIP file
Although every GSI I've tried causes either a bootloop or CrashDump

Your saying, OP, Lineage launched GSI custom rom - what it means? Unofficial fork?
No Gapps? Can't you flash gapps after GSI is flashed?
Caos Rom for with Gapps? What is Caos and GSI difference?

Best gsi rom until now is
https://github.com/ponces/treble_build_pe/releases/download/v413/PixelExperience_arm64-ab-12.1-20220516-UNOFFICIAL.img.xz

The best custom rom for OnePlus n100 until now is
https://github.com/ponces/treble_build_pe/releases/download/v413.1-plus/PixelExperience_Plus_arm64-ab-12.1-20220518-UNOFFICIAL.img.xz
To successfully install it on your device, and the bootloader of your device is already unlocked than read the text file attached.
You will also need these files
OnePlus-USB-Drivers.zip
drive.google.com
Universal ADB Drivers
one_plus_nord_sdk.zip
drive.google.com
And also you need to extract the system image using 7zip program and put it on the one_plus_nord_sdk folder.