Problem Flashing Omni Rom - Sony Xperia XZ Questions & Answers

Hello,
Since a few days I try to flash the actually Omni Rom on my Xperia XZ.
It didn´t work.
Actually FW: F8331_41.2.A.7.35 (Flash with flashtool)
My method:
- flash AndroPlus v26
- flash twrp
- flash supersu
- flash omni rom
I have the following problems and questions:
- When I use twrp 3.0.2.0 and flash omni rom I have bootloop at omni rom logo (wait>20 min) when I start twrp again it wants a decryption code at start
- When I use twrp 3.0.2.4 --> twrp wants a decryption code at start
- When I use twrp 3.1.0.0 --> twrp wants a decryption code at start
- When I use twrp 3.1.1.0 --> no descryption code is required but I can not wipe dalvik etc.
It is required to flash AndroPlus? It is required to root before flash?
I have no idea what method I have to use to flash omni rom successful.
Please can you help me.
THX

Now I try another Method:
I Flash Androplus kernel and Twrp 3.0.2.4
Than I Flash carbon Rom 5.1.
Flash and wipe success. At the First boot i have to enter a Pin Code for my device.
I didnt set any pin code. When i try a Pin randomly
It says that Pin is correct but dates are corrupted.
Then I Can make a reset but landing finally at the screen with pin Code.
Anyone any Ideas?

You have to wipe internal storage in twrp recovery. Wipe -> erase -> yes. Then flash rom again

Related

Error 18 when trying to flash custom roms with Twrp

Hey all,
I unlocked the bootloader, flashed the latest bootloader, radio and vendor from april factory image, to both the slots with fastboot, booted into the twrp 3.2.3-0 (also tried booting into 3.3.0 version) and tried to flash the latest official DU 13.1 rom but I get the Error 18 kDownloadPayloadPubkeyVerificationError at the STEP 2 every damned time! I did a factory reset before flashing, and tried to start all over again many times, flashing factory image with the flash all script, rebooting and then flashing the A/B slots again, but I get that error when I try to flash the rom zip every time. I really don't know how to solve, can someone help me please?
EDIT: thanks to this thread https://forum.xda-developers.com/pixel-3/development/twrp-3-2-3-0-pixel-3-t3861622/post79346061#post79346061 I solved by doing this:
- fastboot boot twrp-3.3.0.0.img
- advanced->Install Recovery Ramdisk and choose the 3.3.0.0 image
- reboot to recovery
- factory reset
- flash the zip
- done

Can't install LineageOS

Hi
I have problems to install LineageOS on my new OnePlus6. I tried to install LineageOS with the guide on https://wiki.lineageos.org/devices/enchilada/install. If I follow the guide exactly step by step no OS is starting and I can't boot into recovery because (I think) twrp isn't installed (just black screen with blue led). But also if I first boot twrp with fastboot boot 'twrp.img' and after install the twrp.zip, no OS is starting after sideload or flash the 'lineageos.zip'. I think, the install doesn't finish correct. In the terminal on my debian I can see, that the installprocess ends at 47%. But I'm not really shure if this is the problem and if it is, how I can solve it. Probably in this thread the same problem is described: https://forum.xda-developers.com/oneplus-6/help/lineage-doesnt-boot-black-screen-light-t3958351 Unfortunately no solution is available in the thread.
Now I flashed the stockrom (https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665) and have done all updates but don't know how I can install twrp and after LineageOS. I hope somebody can help me. Thanks
Do you have the latest ADB version? Instead of sideloading you can try just transferring the zip files (with e.g. "adb push lineageos.zip /sdcard/") and then installing directly from TWRP.
Make sure you do all the wipes / formats mentioned in the guide. Transfer and flash the lineageos.zip. Then directly after you should flash the twrp.zip Then reboot back into recovery and flash Magisk / Gapps etc if needed. Then finally reboot to system.
Also read this guide if you haven't already as it explains a lot about how flashing ROMs on OnePlus 6 is different to many other older phones.
Hi and thank you makeyourself
I tried the following steps:
1. starting fastboot
2. fastboot boot twrp-3.3.1-2-enchilada.img -> twrp starting up
3. adb push twrp-installer-3.3.1-2-enchilada.zip /sdcard/ -> transfer ok
4. adb push lineage-16.0-20190922-nightly-enchilada-signed.zip /sdcard/ -> transfer ok
5. in twrp Wipe -> Format Data
6. in twrp Advanced Wipe -> System
7. in twrp install lineage-16.0-20190922-nightly-enchilada-signed.zip
8. in twrp install twrp-installer-3.3.1-2-enchilada.zip
9. reboot to recovery
After this steps I got the same problem as before. Before the reboot to recovery, twrp showed the message "no OS installed". So I think, the zip weren't installed correctly. Now, I have the black screen with the blue led. Can you find out what I did wrong?
Edit: Now, I can't also boot twrp. Also if I do a fastboot boot twrp-3.3.1-2-enchilada.img nothing happens.
Fastboot to twrp (newest blu spark should be fine, or black twrp)
Flash twrp zip
Reboot to twrp
Wipe data, cache.
Flash recommended oos
Flash twrp
Reboot to twrp
Flash recommended twrp (yes...... Again)
Flash twrp (yes... Again, recovery is lost after rom Flash ALWAYS)
Reboot to twrp
Flash LOS or any other custom rom
Flash twrp (rom Flash, so twrp is lost like I said)
Reboot to twrp
Flash magisk (IF ypu want magisk)
Flash gapps (IF ypu want gapps)
Flash kernel (IF I like to run another custom kernel)
Boot
Enjoy
Thank you whizeguy, I'll try this. But just one question about "Flash recommended oos". Which OxygenOS can I flash (this full OTA? https://www.xda-developers.com/oneplus-6-oneplus-6t-oxygenos-9014-906/) and why I have to do this? Sorry if it is a bad question.
You Flash The oxygen OS version that is recommended in Los thread, simple as that.
You have an a/b device, vendor partition (could be other files needed aswell, not 100 % sure) is needed to Flash custom, IF you did Amy research you'd finns some good info. Also for faster answers in The future: post your issue in the thread for LOS, that way you would get help from People Who uses it, knows The exact version you should use and what not
Hey whizeguy, thank you very much. Everything works perfect now. But why for heaven's sake do I have to flash oos and why the guide on the LineageOS site don't tell me this way?
Wow idk what happened here. Mistakenly replied to this thread. Apologies.

Phone boots to CrashDump mode, cannot enter Fastboot Mode and stuck in TWRP splash

Hi guys,
I have made a bad decision in trying to clean install Lineage OS 17 and now my phone only goes to QUALCOMM CrashDump Mode or gets stuck in the TWRP splash screen.
I cannot even make it start in Fastboot mode.
What I did was:
- Install TWRP 3.3.1-4
- Wipe EVERYTHING from the advanced wipe option
- Sideload Lineage OS 17
- Reboot into recovery to discover that I had the OnePlus recovery back
- Install TWRP 3.3.1-4 again
- Reboot into recovery
- Install GApps
- Restart phone
- Get into infinite boot load of Lineage OS which after a couple of auto restart would take me to TWRP
- Panic
- Wipe EVERYTHING again
- By mistake sideload TWRP 3.3.1-4 instead of Lineage OS 17
- Reboot into recovery
- Get stuck in the splash screen of TWRP
- Reboot into Fastboot
- Get stuck in the OnePlus logo Fastboot Mode
- Somehow turned off the phone
Is there anyone that can help me please?
Flash fastboot stock ROMs
or
Use MSM Download Tool
Look here!
https://forum.xda-developers.com/oneplus-6/how-to/op6-collection-unbrick-tools-t3914109
What do you think about starting with reading the flashing instructions before you attempt flashing ROM's. That would've prevented all the troubles you are experiencing.
Mr.FREE_Bird said:
What do you think about starting with reading the flashing instructions before you attempt flashing ROM's. That would've prevented all the troubles you are experiencing.
Click to expand...
Click to collapse
I managed to reset the device following the guide linked above but I am not able to have a Custom ROM yet.
It doesn't look like there is any "official" guide as I've seen many and each of them gives different instructions!
Ultimately what I found (and tried with no success) is:
- Have the phone automatically update to stock (Oxygen OS 9.0.9) after the reset mentioned above
- Boot into TWRP 3.3.1-14
- Wipe => Format Data: "yes"
- Reboot into TWRP 3.3.1-14
- Flash Stock ROM Oxygen 22 OTA 040 (android 10)
- Flash TWRP 3.3.1-14 installer
- Reboot to recovery
- Flash Stock ROM Oxygen 22 OTA 040 (android 10)
- Flash TWRP 3.3.1-14 installer
- Wipe => Advanced Wipe => Data and Dalvik/ART Cache
- Flash TWRP 3.3.1-14 installer
- Reboot to recovery
- Flash OpenGApps arm64 10
- Reboot to system
After this the phone automatically boots into Fastboot Mode, there is no way to make it try and load the OS.
If you have any better guide, can you please tell me where I can find it?
Thanks
NamingIT said:
I managed to reset the device following the guide linked above but I am not able to have a Custom ROM yet.
It doesn't look like there is any "official" guide as I've seen many and each of them gives different instructions!
Ultimately what I found (and tried with no success) is:
- Have the phone automatically update to stock (Oxygen OS 9.0.9) after the reset mentioned above
- Boot into TWRP 3.3.1-14
- Wipe => Format Data: "yes"
- Reboot into TWRP 3.3.1-14
- Flash Stock ROM Oxygen 22 OTA 040 (android 10)
- Flash TWRP 3.3.1-14 installer
- Reboot to recovery
- Flash Stock ROM Oxygen 22 OTA 040 (android 10)
- Flash TWRP 3.3.1-14 installer
- Wipe => Advanced Wipe => Data and Dalvik/ART Cache
- Flash TWRP 3.3.1-14 installer
- Reboot to recovery
- Flash OpenGApps arm64 10
- Reboot to system
After this the phone automatically boots into Fastboot Mode, there is no way to make it try and load the OS.
If you have any better guide, can you please tell me where I can find it?
Thanks
Click to expand...
Click to collapse
Hold on, what exactly do you want to achieve?
You want to flash LineageOS 17.0 right? I see, just like your first attempt, a couple of things going wrong.
This should work.
● Backup all your data.
● Make sure you have the latest OOS Pie Stable installed on both A and B slots.
● Download the latest LineageOS 17.0 build and Gapps for Android 10.
● Boot to TWRP.
● Wipe data and dalvik cache.
● Flash the ROM zip followed by the TWRP installer zip.
● Reboot to recovery.
● Flash Gapps (if you need Google Services etc).
● Reboot to system.
● Go trough the setup and after that you can reboot to TWRP again to flash Magisk if you need root.
This should work. :good:
Mr.FREE_Bird said:
Hold on, what exactly do you want to achieve?
You want to flash LineageOS 17.0 right? I see, just like your first attempt, a couple of things going wrong.
This should work.
● Backup all your data.
● Make sure you have the latest OOS Pie Stable installed on both A and B slots.
● Download the latest LineageOS 17.0 build and Gapps for Android 10.
● Boot to TWRP.
● Wipe data and dalvik cache.
● Flash the ROM zip followed by the TWRP installer zip.
● Reboot to recovery.
● Flash Gapps (if you need Google Services etc).
● Reboot to system.
● Go trough the setup and after that you can reboot to TWRP again to flash Magisk if you need root.
This should work. :good:
Click to expand...
Click to collapse
I have done exactly what you said. This time I was able to make the Lineage OS load but shortly after it gave me an error saying that "Android Setup keeps stopping" without that the wizard even starts.
I read online that in some cases you need to do a minimal setup before installing the GApps so I will try like that.
Definitely I got 1 step further though, thanks!

Android 10 & Custom ROM & Slot A + B

Hello Android developers and enthusiasts,
I've been installing ROM since 2011 so I would not call myself a n00b however I seemingly cannot install an Android 10 ROM without issues. So this is a plea for help and advice!
I know you need to have OOS installed before you install a custom ROM so I use Auto Flash ROM to install OOS with Android 9 via System Update. I then boot and set up phone, install update, reboot and then install the OOS android 10 via the System Update. I then have a OOS installed with Android 10.
Why would I use such an elaborate method you may ask? Well, I tried to download latest OOS from OnePlus site and wipe phone and then install OOS but that fails (didn't record the error I'm afraid).
I then download all the ROM + dependencies on an USB stick and use fastboot to flash Mauronofrio TWRP. I then follow the steps in the ROM instructions. For EvolutionX these were:
First Time Install / Clean Flash
- Have OOS 10.3 flashed to both slots!!
- Boot to recovery
- Flash BUILD.zip (TWRP built-in)
- Wipe Cache
- Format data
- Reboot to recovery (optional)
- Flash Magisk.zip (optional)
- Reboot to system & #KeepEvolving
Click to expand...
Click to collapse
I followed these to the letter but when i rebooted system I got a snapdragon error and it wouldn't even boot into TWRP until I used fastboot to flash boot into TWRP. I also tried HavocROM and same happened.
I did manage to install Syberia using above method but I didn't like the ROM that much unfortunately.
Finally, I've also read up a lot on Slot A and B but it still is not very clear to me. I think I understand it but what happens does not confirm my theories
I therefore have some questions:
- Should I be able to wipe my phone and install OOS on a wiped phone and then install a custom ROM?
- When I install ROM and it says "Reboot Recovery" and then install ROM again. But if I check what slot is being used the reboot doesn't seem to change the slot. My assumption was that booting recovery was to install ROM in the other slot. Is that correct?
Any other tips you can give me?
Again, I like to stress I am not new to installing custom ROMs so I am a bit disappointed that this is causing me such grief.
Following some answers I will retry tomorrow so I can give some more details if needed. For now, appreciate any help.
roel1976 said:
Hello Android developers and enthusiasts,
I've been installing ROM since 2011 so I would not call myself a n00b however I seemingly cannot install an Android 10 ROM without issues. So this is a plea for help and advice!
I know you need to have OOS installed before you install a custom ROM so I use Auto Flash ROM to install OOS with Android 9 via System Update. I then boot and set up phone, install update, reboot and then install the OOS android 10 via the System Update. I then have a OOS installed with Android 10.
Why would I use such an elaborate method you may ask? Well, I tried to download latest OOS from OnePlus site and wipe phone and then install OOS but that fails (didn't record the error I'm afraid).
I then download all the ROM + dependencies on an USB stick and use fastboot to flash Mauronofrio TWRP. I then follow the steps in the ROM instructions. For EvolutionX these were:
I followed these to the letter but when i rebooted system I got a snapdragon error and it wouldn't even boot into TWRP until I used fastboot to flash boot into TWRP. I also tried HavocROM and same happened.
I did manage to install Syberia using above method but I didn't like the ROM that much unfortunately.
Finally, I've also read up a lot on Slot A and B but it still is not very clear to me. I think I understand it but what happens does not confirm my theories
I therefore have some questions:
- Should I be able to wipe my phone and install OOS on a wiped phone and then install a custom ROM?
- When I install ROM and it says "Reboot Recovery" and then install ROM again. But if I check what slot is being used the reboot doesn't seem to change the slot. My assumption was that booting recovery was to install ROM in the other slot. Is that correct?
Any other tips you can give me?
Again, I like to stress I am not new to installing custom ROMs so I am a bit disappointed that this is causing me such grief.
Following some answers I will retry tomorrow so I can give some more details if needed. For now, appreciate any help.
Click to expand...
Click to collapse
Hi!
I had this exact same problem a couple months ago. Rebooting to recovery used to change slots for me, but then it stopped.
What you can do is change active slot manually on Reboot section. By doing this, you don't even have to reboot to recovery in other to flash the other slot (altough I do it just to be safe).
And remember: the rom is flashed on the inactive slot, so after the final flash you gotta change slots one more time.
When you flash one ROM on top of another different ROM, particularly OOS to custom, always wipe data and not format data, because some custom ROMs do not support being unencrypted in the first time and then encrypt on the first boot. So do it like this:
Flash OOS
Flash TWRP
Reboot recovery
Flash OOS
Flash TWRP
Reboot system
Complete initial setup
Reboot to recovery
Wipe (not format) data
Flash custom ROM (start here for dirty flashing ROM update)
Flash TWRP
Reboot recovery
Flash custom ROM
Flash TWRP
Reboot recovery
Flash Magisk
Reboot system
I don't like built-in TWRP in custom ROMs. I always use @mauronofrio's TWRP. So regardless if the custom ROM I'm using has TWRP built-in or not, I always use the method above. I didn't have a problem with installing ROMs using his TWRP. Slots always switch when flashing ROM.
Thanks for the info, it really helps.
One question: in your experience can you wipe your phone and then installl OOS on the wiped phone?
So I just booted into TWRP, did standard wipe action: Data, Cache, and Dalvik. I then try to flash the latest OOS zip and I then get this error:
Error applying update: 7 (ErrorCode::kInstallDeviceOpenError)
Updater process ended withL ERROR: 1.
Error installing zip file: '/usbstorage/00, INSTALL/OnePlus6Oxygen_22_OTA_044_all_2002220042_a46425f1bfe43d2.zip
FIXED: I was using TWRP 3.3.1.11 and I then found out there was a newer version: 3.3.1.18 which you can get here: https://sourceforge.net/projects/mauronofrio-twrp/files/Enchilada/
I am now able to install OOS from scratch (ie wiped phone).
remewer said:
When you flash one ROM on top of another different ROM, particularly OOS to custom, always wipe data and not format data, because some custom ROMs do not support being unencrypted in the first time and then encrypt on the first boot. So do it like this:
Flash OOS
Flash TWRP
Reboot recovery
Flash OOS
Flash TWRP
Reboot system
Complete initial setup
Reboot to recovery
Wipe (not format) data
Flash custom ROM (start here for dirty flashing ROM update)
Flash TWRP
Reboot recovery
Flash custom ROM
Flash TWRP
Reboot recovery
Flash Magisk
Reboot system
I don't like built-in TWRP in custom ROMs. I always use @mauronofrio's TWRP. So regardless if the custom ROM I'm using has TWRP built-in or not, I always use the method above. I didn't have a problem with installing ROMs using his TWRP. Slots always switch when flashing ROM.
Click to expand...
Click to collapse
I tried this method and everytime I can't seem to flash oos onto the other slot because when it reboots to recovery the folder is encrypted so I can't see which file is the zip. How do I flash the seccond OOS if it shows up encrypted in TWRP.
I have a OnePLus 6 with the latest OOS now because I got into boot loop and i used a flash-all.bat to get back to stock. I also use maronofrio's twrp because that works.
harshybar said:
I tried this method and everytime I can't seem to flash oos onto the other slot because when it reboots to recovery the folder is encrypted so I can't see which file is the zip. How do I flash the seccond OOS if it shows up encrypted in TWRP.
I have a OnePLus 6 with the latest OOS now because I got into boot loop and i used a flash-all.bat to get back to stock. I also use maronofrio's twrp because that works.
Click to expand...
Click to collapse
If you can boot OOS fine, try to do a local update so that both slots have OOS. Then try to flash a custom ROM again using the method I've mentioned.
remewer said:
If you can boot OOS fine, try to do a local update so that both slots have OOS. Then try to flash a custom ROM again using the method I've mentioned.
Click to expand...
Click to collapse
When you say local update you mean while I am running the rom, go to settings then do update from local source?
harshybar said:
When you say local update you mean while I am running the rom, go to settings then do update from local source?
Click to expand...
Click to collapse
Exactly
GuestD2559 said:
When you flash one ROM on top of another different ROM, particularly OOS to custom, always wipe data and not format data, because some custom ROMs do not support being unencrypted in the first time and then encrypt on the first boot. So do it like this:
Flash OOS
Flash TWRP
Reboot recovery
Flash OOS
Flash TWRP
Reboot system
Complete initial setup
Reboot to recovery
Wipe (not format) data
Flash custom ROM (start here for dirty flashing ROM update)
Flash TWRP
Reboot recovery
Flash custom ROM
Flash TWRP
Reboot recovery
Flash Magisk
Reboot system
I don't like built-in TWRP in custom ROMs. I always use @mauronofrio's TWRP. So regardless if the custom ROM I'm using has TWRP built-in or not, I always use the method above. I didn't have a problem with installing ROMs using his TWRP. Slots always switch when flashing ROM.
Click to expand...
Click to collapse
@Cypher_01, Try this guide. This worked for me. I did not reinstall Nikgapps. Maybe that's where the problem lies? Don't forget to change the update slot at the end before you restart.​

Question TWRP Bootloop after flashing ArrowOS 12.0 GAPPS for POCO X3 Pro

I was installing the custom ROM but after the flashing there was an error about "Android Rescue Party trigger!" and when i tried rebooting twrp said there was no os. How do i fix this? Is it the custom ROM that is causing this problem or is it because the custom ROM and GAPPS is combined together in a single ZIP file?
I did yesterday exactly same without any issues, with offical TWRP gapps included
Did you follow al the steps for 100%? (for me the FORMAT DATA after flash was new)
FIRST INSTALL?:
Remove any fingerprint, PIN, or password in MIUI
Unlock the bootloader
Transfer ROM to internal storage
Install any suitable recovery
Flash ROM zip file
Do a data wipe in recovery (format data)
Reboot to the system, wait, and enjoy
Kenshe said:
I was installing the custom ROM but after the flashing there was an error about "Android Rescue Party trigger!" and when i tried rebooting twrp said there was no os. How do i fix this? Is it the custom ROM that is causing this problem or is it because the custom ROM and GAPPS is combined together in a single ZIP file?
Click to expand...
Click to collapse
because twrp can't decrypt on android 12 roms right now. use the recommended recovery provided by the rom's maintainer
solution 1 format data in twrp after installing rom
solution 2 flash stock fastboot rom
easy fix : install "lazyflasher-no-verity-opt-encrypt.zip"

Categories

Resources