Database Users

Error 7 while flashing new rom

I've had many roms flashed on my op2 through twrp, but now whenever i try to flash any rom(cm, exodus, aicp etc.) I get error 7. I tried deleting asserts line on "updater-script" but no luck...
Current rom: Resurrection remix 5.6.9

shahark86 said:
I've had many roms flashed on my op2 through twrp, but now whenever i try to flash any rom(cm, exodus, aicp etc.) I get error 7. I tried deleting asserts line on "updater-script" but no luck...
Current rom: Resurrection remix 5.6.9
Click to expand...
Click to collapse
Hi, If you already have twrp recovery and you can boot into twrp recovery, then you need to download stock oxygen os 2.2.1 ota.
when you download oxygen os 2.2.1 ota, flash it via twrp recovery, after that wipe factory data reset, then you flash your custom roms later. this will bypass the error 7 and you will have to resume enjoying your custom roms.
Here's what happens, when u totally erases the system, data, and formats everything with twrp recovery, custom roms don't run again, i think they kinda need some basic files from the stock rom to enable them to run. i experienced this myself with aicp and this is how i fixed it. so go on, look for the oxygen 2.2.1 ota.zip, download, flash, then wipe data fastory reset, then you can now have your custom roms flashed and working. again.

Right!! but oos 3.0 official is also working

shahark86 said:
I've had many roms flashed on my op2 through twrp, but now whenever i try to flash any rom(cm, exodus, aicp etc.) I get error 7. I tried deleting asserts line on "updater-script" but no luck...
Current rom: Resurrection remix 5.6.9
Click to expand...
Click to collapse
It's there to protect you from flashing a ROM incompatible with your current bootloader (there's two of them, pre oos3 and oos3 bootloader/fastboot).
So if you want to flash a ROM which is Lollipop (or using Lollipop bootloader like easier versions of Graraks and Seraph08s builds) you will have to restore your phone to oos2.x.x first. Same goes the other way around, and also your recovery system must be compatible with respective bootloader.
This info should be force-feeded to every noob checking in on this forum hoping for an easy swapping of ROMs on this phone, which is not gonna happen because of this.

can somebody explain flashing roms on a/b devices?

I'm no stranger to rooting and ROM'ing I've been doing it for years now. However I've never had an a/b device and it's confusing me I have a T-Mobile variant switched to international the bootloader is unlocked I'm rooted with magisk 18.1, and TWRP 3.3.0-2 and I have OOS 9.0.12 installed. I don't understand having OOS as a base ROM for other custom ROMs, some people say to flash OOS twice because apparently it goes into both slot a and b but then twrp encrypts data forcing you to msmtool. I know to take any password and finger print off the phone before switching ROMs and to change the lock screen to none.
My understanding of the steps to follow are
Reboot into TWRP
Wipe like you normally would
Flash custom ROM if your choosing
Flash TWRP (so you don't lose TWRP)
Reboot into the ROM
Reboot into recovery and flash magisk and gapps if needed
Reboot and everything should be good
If that's correct please let me know and I appreciate the help

Joe199799 said:
I'm no stranger to rooting and ROM'ing I've been doing it for years now. However I've never had an a/b device and it's confusing me I have a T-Mobile variant switched to international the bootloader is unlocked I'm rooted with magisk 18.1, and TWRP 3.3.0-2 and I have OOS 9.0.12 installed. I don't understand having OOS as a base ROM for other custom ROMs, some people say to flash OOS twice because apparently it goes into both slot a and b but then twrp encrypts data forcing you to msmtool. I know to take any password and finger print off the phone before switching ROMs and to change the lock screen to none.
My understanding of the steps to follow are
Reboot into TWRP
Wipe like you normally would
Flash custom ROM if your choosing
Flash TWRP (so you don't lose TWRP)
Reboot into the ROM
Reboot into recovery and flash magisk and gapps if needed
Reboot and everything should be good
If that's correct please let me know and I appreciate the help
Click to expand...
Click to collapse
First you need to flash OOS stable because of vendor and second to avoid the bugs. If you flash open beta u will face alot of face issues that why stable is always recommend to flash before flashing ROM and it's also must to flash before flashing ROM again same thing to avoid bugs but it's personal choice if u flash Rom and face any Issue flash OOS stable and then flash Rom. If u don't flash OOS and u didn't face any Issue you are fine that's my experience so far if I flash issue I repeat but stable first then custom and 99% bugs fixed that I "Only" face ..
And method yes that is correct for flashing ROM at least for me I followed always and nothing happens!

farhan20 said:
First you need to flash OOS stable because of vendor and second to avoid the bugs. If you flash open beta u will face alot of face issues that why stable is always recommend to flash before flashing ROM and it's also must to flash before flashing ROM again same thing to avoid bugs but it's personal choice if u flash Rom and face any Issue flash OOS stable and then flash Rom. If u don't flash OOS and u didn't face any Issue you are fine that's my experience so far if I flash issue I repeat but stable first then custom and 99% bugs fixed that I "Only" face ..
And method yes that is correct for flashing ROM at least for me I followed always and nothing happens!
Click to expand...
Click to collapse
I flashed OOS 9.0.12 yesterday because I switched ROMS with 9.0.11 and it resulted in a msm flash, turns out switching roms from 9.0.11 is a bad idea. But after updating I flashed havoc OS and everything is all good. We appreciate the answer I understand it a little better now

A/B slotting implies having a pair of partitions for most partition types (eg., Boot, System, etc...). This does not include the Data partition, however. The purpose was never to allow the coexistence of multiple ROMs but to install an OTA stock update into the unused slot while you're already using the ROM. That way if there's an error during the update process, the OS can choose not to switch over to the updated partition on reboot and continue using the current one. This redundancy is why they were able and willing to scrap the Recovery partition, too.
When flashing a ROM for an A/B device, it actually flashes to the slot you are currently not using. Then upon reboot, it switches to that slot. This is why to maintain TWRP, you need to run TWRP installer after flashing the ROM but before the reboot. Otherwise, restarting into recovery would restart into the ROMs recovery or stock recovery. The TWRP installer unconditionally patches tho Boot partition of both slots. Note that other installers like Magisk and GApps do not. If you were to install Magisk before rebooting, it would install to the currently active slot, not the one the ROM was installed to.
After flashing the ROM and TWRP and rebooting into recovery, the slot would then be set to the newly installed ROM's slot and you can finish installing Magisk and/or GApps. You would wipe data unless you're dirty flashing an updated ROM. If you've removed security password/pin/pattern before flashing it's safe to flash before rebooting in recovery. In situations where I still had such security on, I had to wipe data after rebooting into recovery to maintain working decryption. Taking off the password/pin/pattern before flashing effectively disables the encryption of files on the data partition making it easier to transition to another ROM without any decryption problems.
Whether you need to flash OOS before flashing a ROM, I presume, would depend on whether the ROM, itself, is OOS based. It's not necessary for a non-OOS ROMs. There is a nasty problem that creeps up with OOS based ROMs in which it might boot-loop into recovery. I assume the double flashing might prevent that, though my experience with that problem is after a TWRP restore of OOS stock. You could use msmtool in such a situation as stated, but I always get rid of it by flashing stock Boot partition in fastboot, booting into stock recovery, and factory reset + erase sdcard.
Reboot into TWRP
Wipe like you normally would
Flash custom ROM if your choosing
Flash TWRP (so you don't lose TWRP)
Reboot into the ROM
Reboot into recovery and flash magisk and gapps if needed
Reboot and everything should be good.
Click to expand...
Click to collapse
Don't reboot into ROM before reboot into recovery and make sure to take off Pin/Password/Pattern/Fingerprints before booting into TWRP. Otherwise, this should be fine. For the wipe stage, you don't even need to wipe System or Boot (never Boot), in my experience. Just Data and Dalvik, if not dirty flashing the same ROM type.

Nsane457 said:
A/B slotting implies having a pair of partitions for most partition types (eg., Boot, System, etc...). This does not include the Data partition, however. The purpose was never to allow the coexistence of multiple ROMs but to install an OTA stock update into the unused slot while you're already using the ROM. That way if there's an error during the update process, the OS can choose not to switch over to the updated partition on reboot and continue using the current one. This redundancy is why they were able and willing to scrap the Recovery partition, too.
When flashing a ROM for an A/B device, it actually flashes to the slot you are currently not using. Then upon reboot, it switches to that slot. This is why to maintain TWRP, you need to run TWRP installer after flashing the ROM but before the reboot. Otherwise, restarting into recovery would restart into the ROMs recovery or stock recovery. The TWRP installer unconditionally patches tho Boot partition of both slots. Note that other installers like Magisk and GApps do not. If you were to install Magisk before rebooting, it would install to the currently active slot, not the one the ROM was installed to.
After flashing the ROM and TWRP and rebooting into recovery, the slot would then be set to the newly installed ROM's slot and you can finish installing Magisk and/or GApps. You would wipe data unless you're dirty flashing an updated ROM. If you've removed security password/pin/pattern before flashing it's safe to flash before rebooting in recovery. In situations where I still had such security on, I had to wipe data after rebooting into recovery to maintain working decryption. Taking off the password/pin/pattern before flashing effectively disables the encryption of files on the data partition making it easier to transition to another ROM without any decryption problems.
Whether you need to flash OOS before flashing a ROM, I presume, would depend on whether the ROM, itself, is OOS based. It's not necessary for a non-OOS ROMs. There is a nasty problem that creeps up with OOS based ROMs in which it might boot-loop into recovery. I assume the double flashing might prevent that, though my experience with that problem is after a TWRP restore of OOS stock. You could use msmtool in such a situation as stated, but I always get rid of it by flashing stock Boot partition in fastboot, booting into stock recovery, and factory reset + erase sdcard.
Don't reboot into ROM before reboot into recovery and make sure to take off Pin/Password/Pattern/Fingerprints before booting into TWRP. Otherwise, this should be fine. For the wipe stage, you don't even need to wipe System or Boot (never Boot), in my experience. Just Data and Dalvik, if not dirty flashing the same ROM type.
Click to expand...
Click to collapse
That was a very well written and insightful answer thank you. The way you wrote makes everything much easier to understand

I think with the new TWRP recovery flashing is about to be less of a d**k. TWRP 3.3.0-0

Moto g5 plus encryption problems

So my problem is the encryption every time i try to install a pie rom my phone ask me for a password in the recovery they say "encrytion sucesfull" so i try to wipe the rom and the same problem, i flashed the rom with a clean flash but all the pie roms for me are having the same problem, i know theres an option to remove encryption on the TWRP but when i type yes my phone automatically says me unable to mount storage unable to mount anything and basicly is dead i tryed to fix that changing the phone file contexts but nothing and to recover i need to reflash the stock firmware ands its likea a loop i revive my phone later install the recovery next install a pie rom then the pie rom not working (All the new pie roms) and later come back to the stock firmware, so im really frustated for that problem so im asking for a solution please help me:crying: . (Sorry for my bad english)

RealDogeMx said:
So my problem is the encryption every time i try to install a pie rom my phone ask me for a password in the recovery they say "encrytion sucesfull" so i try to wipe the rom and the same problem, i flashed the rom with a clean flash but all the pie roms for me are having the same problem, i know theres an option to remove encryption on the TWRP but when i type yes my phone automatically says me unable to mount storage unable to mount anything and basicly is dead i tryed to fix that changing the phone file contexts but nothing and to recover i need to reflash the stock firmware ands its likea a loop i revive my phone later install the recovery next install a pie rom then the pie rom not working (All the new pie roms) and later come back to the stock firmware, so im really frustated for that problem so im asking for a solution please help me:crying: . (Sorry for my bad english)
Click to expand...
Click to collapse
Go to recovery, DON'T decrypt data (click in cancel when the dots shows up), go to wipe and format data. You shouldn't see any errors formating data if you don't deprypt it first.
As far as I know the only roms that support encryption is Bootleggers and Havoc, but with Havoc I lose mobile internet after some time and with Bootleggers gcam doesn't work for me.

Flashed TWRP and Lineage OS but getting error while booting

Hi All,
I was able to successfully install TWRP and get Lineage OS installed but when I am booting initially I get an error message, it waits 5 seconds and then boots into the O/S.
https://i.imgur.com/qTzytc5.jpg
Is this because it's a custom rom? If not can someone let me know what I did wrong? Also I noticed that the phone dialer isn't working and see others having a similar issue. Are there any custom roms where this is working? If not and I want to go back to the stock rom, can I just apply the update.zip via TWRP?
Thanks for the help,
Nick

npolite said:
Hi All,
I was able to successfully install TWRP and get Lineage OS installed but when I am booting initially I get an error message, it waits 5 seconds and then boots into the O/S.
https://i.imgur.com/qTzytc5.jpg
Is this because it's a custom rom? If not can someone let me know what I did wrong? Also I noticed that the phone dialer isn't working and see others having a similar issue. Are there any custom roms where this is working? If not and I want to go back to the stock rom, can I just apply the update.zip via TWRP?
Thanks for the help,
Nick
Click to expand...
Click to collapse
if you can apply update.zip from twrp and the phone dialing does not work "only in some mobile operators" and on that adventecia of the screen in image that you uploaded, that error is because you started twrp for the first time without flashing root and rom, why root and rom has integrated dm-verity disabled
dm-verity boot: is responsible for verifying the first boot system partitions, such as boot, data, system etc ...
there is a file with name no-verity-opt-encrypt-6.0.zip that serves to deactivate dm-verity boot, but the adventecia the only way to remove it is with stock rom, back flashing the stock rom.

Can't install any custom ROM. But why?

I wanted to upload a new rom to my phone (pine, 16GB), but it will never boot. Always after rebooting, TWRP will be loaded again. I'm tried multiple ROMs (LineageOS, DotOS, MokeeOS ), but the problem occurs for all rom. TWRP says, flash succed for every one system, but not booting after reboot.
I'm used twrp-3.5.0_9-20210101-pine-arm64 version. Only I can do flash a stock rom using MiFlash, but no custom rom via TWRP.
Mi device is correctly unlocked via Official Unlock Tool app.
Can you tell me why?
Thanks

Maybe try another twrp version or another completely like OrangeFox can't really tell you why i don't have as much knowledge in why or how it works but i have tried a lot on mine so this should be ur first troubleshooting step from my point of view also have you flashed the ROMs with their instructions some say the sequence you should format or wipe ur data etc...

Working for now,
The problem was that I didn't choose to Format data