Database Info

[SOLVED] OnePlus One - Bootloop after flashing any ROM with TWRP

I've installed TWRP 3.1.1-0 using fastboot but every time I try to flash a rom using it, I enter a bootloop ([1+] logo, the phone vibrate and reboot).
I've tried with AOSiP 6.3, AOSPlusOne 250817 and AOSPExtended 4.5. (With and without OpenGapps).
With the following procedure:
-Wipe Dalvik, Data, cache, system.
-Flash ROM
-Flash OpenGapps
-Wipe caches
-Reboot.
Am I doing something wrong ? Skipped a step ? Should I use another Rom/Recovery ?
EDIT: Solved ! Before flashing rom, you need to flash the latest official CM13 and then wipe /system before flashing anything else.

Wanted to say thanks. Your post helped me install a good rom again after unbricking my phone. Surprisingly I couldn't find this simple info elsewhere and also Cyanogenmod 13 is also hard to find cause the whole ROM landscape has changed! For instance Using a latest Lineage OS ROM didn't help either. I had to use TWRP from TugaPower and an outdated CM13 from a shady link to get it to work. Not sure which one did the trick but between one of them
Hatomike said:
I've installed TWRP 3.1.1-0 using fastboot but every time I try to flash a rom using it, I enter a bootloop ([1+] logo, the phone vibrate and reboot).
I've tried with AOSiP 6.3, AOSPlusOne 250817 and AOSPExtended 4.5. (With and without OpenGapps).
With the following procedure:
-Wipe Dalvik, Data, cache, system.
-Flash ROM
-Flash OpenGapps
-Wipe caches
-Reboot.
Am I doing something wrong ? Skipped a step ? Should I use another Rom/Recovery ?
EDIT: Solved ! Before flashing rom, you need to flash the latest official CM13 and then wipe /system before flashing anything else.
Click to expand...
Click to collapse

Glad I could help you, I didn't find anything else for this too.
From what I heard, it have something to do with some kind of drivers that are installed with OTA update. Since I disabled them I needed to install the latest official rom from Oneplus

Hatomike said:
I've installed TWRP 3.1.1-0 using fastboot but every time I try to flash a rom using it, I enter a bootloop ([1+] logo, the phone vibrate and reboot).
I've tried with AOSiP 6.3, AOSPlusOne 250817 and AOSPExtended 4.5. (With and without OpenGapps).
With the following procedure:
-Wipe Dalvik, Data, cache, system.
-Flash ROM
-Flash OpenGapps
-Wipe caches
-Reboot.
Am I doing something wrong ? Skipped a step ? Should I use another Rom/Recovery ?
EDIT: Solved ! Before flashing rom, you need to flash the latest official CM13 and then wipe /system before flashing anything else.
Click to expand...
Click to collapse
have to register just say THANK YOU!

saba.ahang said:
Wanted to say thanks. Your post helped me install a good rom again after unbricking my phone. Surprisingly I couldn't find this simple info elsewhere and also Cyanogenmod 13 is also hard to find cause the whole ROM landscape has changed! For instance Using a latest Lineage OS ROM didn't help either. I had to use TWRP from TugaPower and an outdated CM13 from a shady link to get it to work. Not sure which one did the trick but between one of them
Click to expand...
Click to collapse
gottdamm this may be my issue, I've tried a new battery without success, see my thread in this forum.
I'm using the latest TWRP and latest Lineage.
Could you, or anybody, post the links to the Tugapower TWRP and CM13 you used?
edit: I flashed CM13 but still boot looping, as per my other thread. Wondering what the hardware issue is.

[UMIDIGI F1] Project Treble?

EDIT: This is specifically for the Umidigi F1.
This is not my work, but I discovered this post in one of the hacking forums. I don't know how accurate it is yet (and given the publish date, I may be a fool), but I figured it was worth sharing.
https://forum.xda-developers.com/android/development/psa-project-treble-t3917284?nocache=1

LOL! Sorry man thats my thread I honestly didn't even realize yesterday was april fools! It's for real 100% legit .

That looks SO cool! Unfortunately I'm still struggling with TWRP as it simply cannot read anything (to be able to do step #9 on the OP). When I solve this, I'll post here as maybe it'll be good to update the steps

Well, in the end I was able to boot some SOs, but only after patching a different force encryption disable zip file (from here: https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389) but anyway, no custom ROM worked properly - I faced a huge amount of lag, crashes and sudden loss of input recognition. So, in the end I went back to stock Pie + Magisk to try solving the RAM issue this way. Thanks all!

Leo_Freitas said:
Well, in the end I was able to boot some SOs, but only after patching a different force encryption disable zip file (from here: https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389) but anyway, no custom ROM worked properly - I faced a huge amount of lag, crashes and sudden loss of input recognition. So, in the end I went back to stock Pie + Magisk to try solving the RAM issue this way. Thanks all!
Click to expand...
Click to collapse
Please tell me which ROMs did you try and what problems did you face ?

I tried the 3 mentioned in the OP:
Resurrection Remix
Descendant
Bliss ROM
But had no luck with them. Bliss seemed to be the best among them (at least I was able to boot from that haha) but after a reboot I got stuck on bootloop again (looks like the system could not see the OS anymore).

Leo_Freitas said:
I tried the 3 mentioned in the OP:
Resurrection Remix
Descendant
Bliss ROM
But had no luck with them. Bliss seemed to be the best among them (at least I was able to boot from that haha) but after a reboot I got stuck on bootloop again (looks like the system could not see the OS anymore).
Click to expand...
Click to collapse
That's a shame about the bootloop thank you for your post this helps me a lot.

Leo_Freitas said:
I tried the 3 mentioned in the OP:
Resurrection Remix
Descendant
Bliss ROM
But had no luck with them. Bliss seemed to be the best among them (at least I was able to boot from that haha) but after a reboot I got stuck on bootloop again (looks like the system could not see the OS anymore).
Click to expand...
Click to collapse
Maybe a A/B partition problem? Could maybe flash rom on both partition slots.

Leo_Freitas said:
I tried the 3 mentioned in the OP:
Resurrection Remix
Descendant
Bliss ROM
But had no luck with them. Bliss seemed to be the best among them (at least I was able to boot from that haha) but after a reboot I got stuck on bootloop again (looks like the system could not see the OS anymore).
Click to expand...
Click to collapse
A few questions:
1. How did you flash them? Did you use the SP Flash Tool?
2. After installing them, did you run the DM-Verity tool to disable encryption?

riceboyler said:
A few questions:
1. How did you flash them? Did you use the SP Flash Tool?
2. After installing them, did you run the DM-Verity tool to disable encryption?
Click to expand...
Click to collapse
hello
i bought Umidigi F1 Play for more than 1 months
and i test a lot of treble project (Havoc OS,Ressurection Remix,Blissrom,Lineage OS,Omnirom) all android 9 and it did boot up
so this my method to boot up
first :
-Unlock your Bootloader
-Download TWRP Recovery​- Download Any Rom You Want to try And copy it to internal memory as .img file
-Download Magisk
-Flash TWRP Using SP Flash Tool and go to Recovery
-Make a Backup For your System if something go Wrong
-Wipe Data, Cache, System, Dalvik Cache
-go to install, press Install Image , Select your Rom File , select System Image As the partition to Flash Image
-Swipe and Wait
-Back to install and Flash Magisk
- Reboot and Enjoy
for People using gapps there is a problem with twrp is doesnt support a/b so opengapps doesnt detect if the phone is a normal or a/b device but i manage to fix a temporary opengapps to work on our device waiting for the twrp developer to fix this bug
this is the working gapps https://drive.google.com/open?id=1-Dguq8rs4k4W7eZKA2KnJxB5fKXCw2Y-

Shadow Of Leaf said:
hello
i bought Umidigi F1 Play for more than 1 months
and i test a lot of treble project (Havoc OS,Ressurection Remix,Blissrom,Lineage OS,Omnirom) all android 9 and it did boot up
so this my method to boot up
first :
-Unlock your Bootloader
-Download TWRP Recovery​- Download Any Rom You Want to try And copy it to internal memory as .img file
-Download Magisk
-Flash TWRP Using SP Flash Tool and go to Recovery
-Make a Backup For your System if something go Wrong
-Wipe Data, Cache, System, Dalvik Cache
-go to install, press Install Image , Select your Rom File , select System Image As the partition to Flash Image
-Swipe and Wait
-Back to install and Flash Magisk
- Reboot and Enjoy
for People using gapps there is a problem with twrp is doesnt support a/b so opengapps doesnt detect if the phone is a normal or a/b device but i manage to fix a temporary opengapps to work on our device waiting for the twrp developer to fix this bug
this is the working gapps https://drive.google.com/open?id=1-Dguq8rs4k4W7eZKA2KnJxB5fKXCw2Y-
Click to expand...
Click to collapse
Boot and recovery only options i get in twrp

Sd card not used

Hello,
I am running PixysOS rom on my Honor 6X (BLN-AL20) since some months and I am actually satisfied of the stability and usability of the Rom.
Actually I can't convince the device to use the installed as card to store pictures, videos etc.
The SD card is recognised and listed under memory but the system is not using it.
Is there any workaround to fix this problem?
Thanks,
Andrea.
Sent from my BLN-AL20 using Tapatalk

Anybody out there?
Sent from my BLN-AL20 using Tapatalk

Sephiroth79 said:
Anybody out there?
Sent from my BLN-AL20 using Tapatalk
Click to expand...
Click to collapse
for me my internal storage is not detected. only sd card is main storage. seems like its a bug and never gonna fixed. there is no perfect android 9 os out there. so better go to emui 8 and use cyclox kernel.

Sephiroth79 said:
Hello,
I am running PixysOS rom on my Honor 6X (BLN-AL20) since some months and I am actually satisfied of the stability and usability of the Rom.
Actually I can't convince the device to use the installed as card to store pictures, videos etc.
The SD card is recognised and listed under memory but the system is not using it.
Is there any workaround to fix this problem?
Thanks,
Andrea.
Click to expand...
Click to collapse
By what I read in the thread of DotOS, that's a bug that should had be fixed in latest builds... Are you using latest version or not?
Anyway every Pie ROM/GSI I tried seems to read microSD, eject it and re-read once again immediately after booting to OS, on every single boot. Then, there are systems that keep reading the microSD (as AEX, Descendant...) and allows modifications, reading files, basically everything you should be able to do with a microSD, and systems that just keep it ejected (like DotOS did on old builds). Saw other users reporting that on the thread. Look for "microSD" in DotOS thread to read latest comments about, there you could find a solution. By how things sound at the moment, my only advice is to move on another system.

Thanks for your reply. Could you suggest me a proper and stable rom?

Sephiroth79 said:
Thanks for your reply. Could you suggest me a proper and stable rom?
Click to expand...
Click to collapse
Nothing hard to do man. We use to thank others with the appropriate button, for next times.
Anyway since that we're not talking 'bout different devices but we share the same phone, i feel to strongly recommend ya the Descendant GSI project by Dil3mm4.. It's a fork of Phh AOSP project but with sone very good extras. I never used a system smooth like this one, really impressive. It has a decent amount of customizations options (not at levels like RROS in example, but too much is too much IMHO), great battery management, fluid transitions and great compatibility with Huawei devices (it's a GSI, but the dev has a P8 Lite at the moment, so he knows how to make things working on Huawei).
Give it a shot, you can always go back to stock with HuRUpdater in just 5 minutes. And in case you'd like to try more, remember to take a look into Treble section here on XDA. Every arm64 a-only GSI is good to be flashed on our device, but before flashing just look if other users owning a Huawei device have already tried it or not. I say this simply because many GSIs are actually not working thanks to our vendor compatibility, so make things without hurry and nothing can go wrong

Used appropriate "thanks button" this time...eheh
Any tutorial on how to install the Descendant GSI rom starting from PixysOs with Askuccio's TWRP?

Sephiroth79 said:
Used appropriate "thanks button" this time...eheh
Any tutorial on how to install the Descendant GSI rom starting from PixysOs with Askuccio's TWRP?
Click to expand...
Click to collapse
Well there isn't a dedicated tutorial for every ROM/GSI you're starting from, overall because a clean flash is strongly recommended (especially when you switch from a ROM to a GSI) - you can dirty flash Descendant updates or other GSIs based on phhusson trees without problems, but in this case you've already modified your device kernel and other stuff with a custom ROM, so it's better to start from scratch in way to avoid useless wastes of time running to repairs with hurry.
The faster and safest way to do this is:
1) restore stock OS with HuRUpdater and let it boot (i saw that you already own Askuccio's TWRP, i always had to use Elemental TWRP from KingOfMezi in way to use HuRU without errors, but apart this Askuccio's TWRP works for flashing everything you'd need);
2) following steps listed in Descendant OP, flash the system image through fastboot or through TWRP, then reboot to TWRP once again and wipe ONLY /cache and /dalvikART partitions;
3) factory reset through stock recovery and let the system boot (yeah, you'll have to reflash stock recovery once again before reflashing TWRP - again.
4) flash all the rest you'd like to flash (GApps, Magisk, ecc.)
By default, /data partition remains encrypted after performing factory reset with stock recovery, and so with TWRP you won't be able to perform full backups, but you can also choose to run with /data decrypted. The method isn't supported by the developer, but works like a charm (personally tested about 3 versions of the GSI ago, worked). You just have to flash "disable dm verity" script during the process, but you can know more by reading about it here.
Happy flashing

RedSkull23 said:
Well there isn't a dedicated tutorial for every ROM/GSI you're starting from, overall because a clean flash is strongly recommended (especially when you switch from a ROM to a GSI) - you can dirty flash Descendant updates or other GSIs based on phhusson trees without problems, but in this case you've already modified your device kernel and other stuff with a custom ROM, so it's better to start from scratch in way to avoid useless wastes of time running to repairs with hurry.
The faster and safest way to do this is:
1) restore stock OS with HuRUpdater and let it boot (i saw that you already own Askuccio's TWRP, i always had to use Elemental TWRP from KingOfMezi in way to use HuRU without errors, but apart this Askuccio's TWRP works for flashing everything you'd need);
2) following steps listed in Descendant OP, flash the system image through fastboot or through TWRP, then reboot to TWRP once again and wipe ONLY /cache and /dalvikART partitions;
3) factory reset through stock recovery and let the system boot (yeah, you'll have to reflash stock recovery once again before reflashing TWRP - again.
4) flash all the rest you'd like to flash (GApps, Magisk, ecc.)
By default, /data partition remains encrypted after performing factory reset with stock recovery, and so with TWRP you won't be able to perform full backups, but you can also choose to run with /data decrypted. The method isn't supported by the developer, but works like a charm (personally tested about 3 versions of the GSI ago, worked). You just have to flash "disable dm verity" script during the process, but you can know more by reading about it here.
Happy flashing
Click to expand...
Click to collapse
Point 1: I have to download stock fw using Huawei firmware finder and I have to use Askuccio's TWRP to flash HuRupdater on the device. Do I have to choose a custom recovery or I have to let HuRupdater flash stock recovery too?
Point 2: you are saying I have to wipe cache/dalviw partitions using TWRP so I have to flash TWRP after flashing and booting stock fw?

Sephiroth79 said:
Point 1: I have to download stock fw using Huawei firmware finder and I have to use Askuccio's TWRP to flash HuRupdater on the device. Do I have to choose a custom recovery or I have to let HuRupdater flash stock recovery too?
Point 2: you are saying I have to wipe cache/dalviw partitions using TWRP so I have to flash TWRP after flashing and booting stock fw?
Click to expand...
Click to collapse
To me flashing HuRU with Askuccio TWRP never worked, as said above, so i'd suggest you to look for ElementalTWRP in way to have a custom recovery that can flash HuRU with no problems. Secondarily, in way to avoid confusion, just start from stock and do a fastboot flash of Descendant, reboot to OS and let it boot. Once set, flash TWRP and flash GApps, then wipe just /cache and /dalvik and reboot one last time. Then you can do anything you want.

RedSkull23 said:
To me flashing HuRU with Askuccio TWRP never worked, as said above, so i'd suggest you to look for ElementalTWRP in way to have a custom recovery that can flash HuRU with no problems. Secondarily, in way to avoid confusion, just start from stock and do a fastboot flash of Descendant, reboot to OS and let it boot. Once set, flash TWRP and flash GApps, then wipe just /cache and /dalvik and reboot one last time. Then you can do anything you want.
Click to expand...
Click to collapse
Ok, I'll put elemental TWRP recovery in the same directory in order to let HuRU flash it together with the stock firmware.
Edit: can't find elemental twrp download link

Sephiroth79 said:
Ok, I'll put elemental TWRP recovery in the same directory in order to let HuRU flash it together with the stock firmware.
Edit: can't find elemental twrp download link
Click to expand...
Click to collapse
Good, i usually do that later just in case the system prompts to factory reset before booting, but it's up to you. Here's the link anyway https://mega.nz/#!a81EDZAR!2-9yPFh3reghkGcfSl3nRIJhHGkP8fqDsgUG66ewjkk

Using fw finder I downloaded the fw named: BLN-AL30C00B541 (8.0.0.541) FULLOTA-MF 2018.12.27
Clicking on download give me some choices:
- update.zip (1.74 GB)
- BLN-Al20_all_cn/update_full_BLN-AL20_all_cn.zip (643 MB)
Already downloaded both of them and can't find any of the files required from HurUpdater to run. Do I have to use an extractor?
EditOne: used Huawei Update Extractor gives an error on the update.app extracted from the update.zip archive and works on the same file extracted from BLN-Al20_all_cn/update_full_BLN-AL20_all_cn.zip
Edit2: just realized I don't need to extract anything but still can't find update_data_public and update_all_hw files

That is because it's Chinese build and as you just noticed some update packages are assembled in a slightly different manner, so some package misses one if not two useful zips. Would you mind to switch to India variant? Nothing changes in performance nor in features, plus if you'd only use the firmware as a base to get to other ROMs/GSIs, it really doesn't matter (but i can offer better assistance since that i'm more experienced with India variant other than China). FYI in this thread https://forum.xda-developers.com/honor-6x/how-to/french-language-t3938592/ i've already guided an user to obtain India variant, but it's really simple:
in TEAM MT site (google for "team mt online firmware database", the first result you get is what you need), look for build "BLN-L22HNC675CUSTC675D1B510" - you'll obtain 4 results. Download the package dated 2018.07.19, it is the better one. From here you just have to follow instructions in HwOTA thread, renaming the three packages as suggested in OP and choosing to debrand during the process to BLN-L22 region/variant (don't remember if it happens anyway since that the firmware is India variant but it's a thing that doesn't give hassles).

[Help Thread][Oneplus 7] Ask Any Question, Noob Friendly

This thread has been created
for
Questions & Answers/Troubleshooting
Specific to
Oneplus 7
Please feel free to share issues, questions and offer help. Noob questions are welcomed.
It is always best to use the Thanks button , in lieu of simply posting "Thank you".
{
"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"
}
Please keep discussion focused, on questions pertaining to this Device
List of supporters​​@strongst​​​
To those seeking help: Please don't bombard the supporters with PMs asking for help. Instead, ask your question here in the thread so others can benefit from the solution to your problem as well. If you want to be sure someone particular gets notified of your question, put his / her username directly after an @.​If you have ROM related questions, post in the relevant ROM Q&A thread (if there is one) or directly in the ROM development thread. Thank you!​​Supporters: If you want to be put on or off the list, just make a request here in the thread!​Before posting anything, I strongly advise you to read​
XDA Forum Rules
[GUIDE] - XDA New User Guide - Getting started on XDA
XDA Tour
​Specific Threads and Guides for Oneplus 7​
[GUIDE][OP7][9.0/10.0] Unlock Bootloader | TWRP | Root with Magisk | Update
Repository of Oneplus 7 Stock Roms(use in search function too)
Oneplus 7 TWRP Recovery
Oneplus 7 MSM Tool OxygenOS(Unbrick tool)
Oneplus 7 MSM Tool HydrogenOS(Unbrick tool)
Extract boot.img from Rom zip to get stock recovery and kernel
Feedback towards Oneplus over OP7 pro thread(builds are nearly identical)
OnePlus 7 & 7 Pro Cross Device Development
​​Please look for a similar thread when visiting another device forum.
If you would like to create a [Help Thread] please Click Here. ​

Hello, I'm coming from several years of closed source Exynos Samsung. Struggle to get custom roms is a real pain. In addition, my love for bloatware, including big bro G apps/framework, is notoriously plunging to zero. So OP7 is gonna be my soon next phone.
Q: has anyone performed any deep clean of bloat and/or Google apps/framework on this model? Can it be done? In what %? Does it break anything natively working on OP7?
I know about the Tomatot, just what experience gives this process.
ps: I have a really bad OCD when reading com.google.abcdx
Nah, I'm good, just hate big brothers who spy on us.

w41ru5 said:
Hello, I'm coming from several years of closed source Exynos Samsung. Struggle to get custom roms is a real pain. In addition, my love for bloatware, including big bro G apps/framework, is notoriously plunging to zero. So OP7 is gonna be my soon next phone.
Q: has anyone performed any deep clean of bloat and/or Google apps/framework on this model? Can it be done? In what %? Does it break anything natively working on OP7?
I know about the Tomatot, just what experience gives this process.
ps: I have a really bad OCD when reading com.google.abcdx
Nah, I'm good, just hate big brothers who spy on us.
Click to expand...
Click to collapse
You can freeze/debloat nearly everything on OxygenOS without any impact compared to Samsung. I'm also debloat nearly everything from Google which comes pre-installed. But it's only minor compared to other OS.
Oneplus is one of the cleanest OS around and near to stock.

strongst said:
You can freeze/debloat nearly everything on OxygenOS without any impact compared to Samsung. I'm also debloat nearly everything from Google which comes pre-installed. But it's only minor compared to other OS.
Oneplus is one of the cleanest OS around and near to stock.
Click to expand...
Click to collapse
Right, thanks.
Steps: unlock bootloader, twrp, root Magisk, Tomatot, test.

w41ru5 said:
Right, thanks.
Steps: unlock bootloader, twrp, root Magisk, Tomatot, test.
Click to expand...
Click to collapse
Yeah, exactly. You can also have a look at xXx https://forum.xda-developers.com/on...agisk-rom-xxx-nolimits-7-0-speed-ram-t3933927 :good:

strongst said:
Yeah, exactly. You can also have a look at xXx https://forum.xda-developers.com/on...agisk-rom-xxx-nolimits-7-0-speed-ram-t3933927 :good:
Click to expand...
Click to collapse
Interesting concept. Thanks!

Hi guys. it would be good to add the two threads of MsmDownloadTool. The original that installs HydrogenOS and the other thread of a partner that puts OOS.
MsmDownloadTool HydrogenOS: https://forum.xda-developers.com/oneplus-7/how-to/unbrick-tool-oneplus-7-msmtool-hydrogen-t3953240
MsmDownloadTool OOS: https://forum.xda-developers.com/oneplus-7/how-to/op7-unbrick-tool-to-restore-device-to-t3954325
---------- Post added at 04:57 PM ---------- Previous post was at 04:53 PM ----------
Another question, when using MsmDownloadTool you have to start the phone in EDL mode. This mode has a duration of 10 seconds, then the phone restarts. Any user who has used this tool can claim to restart in EDL mode after 10 seconds, but if you press Start, do you keep EDL mode by installing the ROM Stock?

Hello friends, I have a doubt, in other phones, when I wanted to put a clean ROM, even if it was the Stock, I always did it from TWRP:
1. Wipe / Advanced Wipe / and marked: Dalvik / ART Cache, System and Data.
2. Flash ROM OOS.
My questions are:
a) Has anyone tried to do that Wipe System? and can you confirm if you can then install the OOS ROM or cause problems and make brick ?.
b) Can you also do Wipe Vendor with Wipe System without causing brick?
Thank you and see if someone has done those steps and takes me out of doubt.

tURkOsANsE said:
Hello friends, I have a doubt, in other phones, when I wanted to put a clean ROM, even if it was the Stock, I always did it from TWRP:
1. Wipe / Advanced Wipe / and marked: Dalvik / ART Cache, System and Data.
2. Flash ROM OOS.
My questions are:
a) Has anyone tried to do that Wipe System? and can you confirm if you can then install the OOS ROM or cause problems and make brick ?.
b) Can you also do Wipe Vendor with Wipe System without causing brick?
Thank you and see if someone has done those steps and takes me out of doubt.
Click to expand...
Click to collapse
Why should you brick the phone when you wipe system /vendor and then flashing those partitions again when flashing OxygenOS?

strongst said:
Why should you brick the phone when you wipe system /vendor and then flashing those partitions again when flashing OxygenOS?
Click to expand...
Click to collapse
I have already read it several times in the forum, and they say that then you have to install ROM by fastboot. That's why I ask, in case a partner did it and it worked. when I updated on other ROM phones, instead of directly flashing the new ROM, first to wipe system and cache and then install the ROM update. to make a "semi-clean" installation. And now I don't know if it could be done by doing wipe system and vendor before installing.

Hello,
I ran into an issue today.
1- I downloaded the update through the phones updater. (9.5.8 BA. Full ZIP (2Go))
2- I went into TWRP and flashed latest twrp unofficial installer.
3- I flashed magisk
4- I rebooted into twrp, latest unofficial
5- Flashed OTA file from .OTA folder.
6- Flashed latest TWRP unofficial installer
7- Flashed magisk
=> stuck in bootloop.
Only fix was to go into twrp and manually select the other Slot, which worked thank god.
Anyone has a clue what I did wrong?

Nobody07 said:
Hello,
I ran into an issue today.
1- I downloaded the update through the phones updater. (9.5.8 BA. Full ZIP (2Go))
2- I went into TWRP and flashed latest twrp unofficial installer.
3- I flashed magisk
4- I rebooted into twrp, latest unofficial
5- Flashed OTA file from .OTA folder.
6- Flashed latest TWRP unofficial installer
7- Flashed magisk
=> stuck in bootloop.
Only fix was to go into twrp and manually select the other Slot, which worked thank god.
Anyone has a clue what I did wrong?
Click to expand...
Click to collapse
Hi guys, I put the steps I did to update when it is in OOS Stock with TWRP and Magisk, I did it from version 9.5.7 to 9.5.8 without problems, I do the method of installing everything in both slots, although there are people who only do it in a slot. I put what I did and it worked for me:
1. Backup with TWRP
2. Go to TWRP Reboot and see which slot you are in (then install it in the other slot).
3. In the first slot:
3.1. Go to Wipe Advanced and do Wipe Cache / Dalvik
3.2. OOS flashing
3.3. TWRP flashing
3.4. Flashing Magisk
4. Reboot TWRP
5. Change to second slot (go to Reboot and select the other slot:
5.1. Go to Wipe Advanced and do Wipe Cache / Dalvik
5.2. OOS flashing
5.3. TWRP flashing
5.4. Flashing Magisk
6. OPTIONAL: Change from Slot to the first (to go to Reboot and click on the other), I like to always work in the A, but that is a taste.
7. Reboot System.
PD: I use TWRP Blu_Spark:
https://github.com/engstk/android_device_oneplus_guacamole_unified_TWRP/releases/tag/v9.103
TWRP dev message: https://forum.xda-developers.com/showpost.php?p=79905872&postcount=29

tURkOsANsE said:
Hi guys, I put the steps I did to update when it is in OOS Stock with TWRP and Magisk, I did it from version 9.5.7 to 9.5.8 without problems, I do the method of installing everything in both slots, although there are people who only do it in a slot. I put what I did and it worked for me:
1. Backup with TWRP
2. Go to TWRP Reboot and see which slot you are in (then install it in the other slot).
3. In the first slot:
3.1. Go to Wipe Advanced and do Wipe Cache / Dalvik
3.2. OOS flashing
3.3. TWRP flashing
3.4. Flashing Magisk
4. Reboot TWRP
5. Change to second slot (go to Reboot and select the other slot:
5.1. Go to Wipe Advanced and do Wipe Cache / Dalvik
5.2. OOS flashing
5.3. TWRP flashing
5.4. Flashing Magisk
6. OPTIONAL: Change from Slot to the first (to go to Reboot and click on the other), I like to always work in the A, but that is a taste.
7. Reboot System.
PD: I use TWRP Blu_Spark:
https://github.com/engstk/android_device_oneplus_guacamole_unified_TWRP/releases/tag/v9.103
TWRP dev message: https://forum.xda-developers.com/showpost.php?p=79905872&postcount=29
Click to expand...
Click to collapse
Sooooo what you are saying is you flash on both slots so that both are ****ed if there is an issue?
Very smart.
With my issue I couldn't flash second slot anyway since I lose access to data.
Edit: Same issue with local update followed by twrp install through magisk.

Nobody07 said:
Sooooo what you are saying is you flash on both slots so that both are ****ed if there is an issue?
Very smart.
With my issue I couldn't flash second slot anyway since I lose access to data.
Edit: Same issue with local update followed by twrp install through magisk.
Click to expand...
Click to collapse
I put what I did and I had no problem. something you would do differently so that I don't let you install it:good:

Is there any news of pixel experience for oneplus 7??

Nobody07 said:
Sooooo what you are saying is you flash on both slots so that both are ****ed if there is an issue?
Very smart.
With my issue I couldn't flash second slot anyway since I lose access to data.
Edit: Same issue with local update followed by twrp install through magisk.
Click to expand...
Click to collapse
SO following on my issue, my suspicion is that there is something wrong on my slot A.
Slot B is where my current usable setup is. When installing an update it goes into slot A and it fails whatever I try.
My question would be, how can I copy my exact configuration of slot B to slot A, to try updating again?
Thank you !

Nobody07 said:
SO following on my issue, my suspicion is that there is something wrong on my slot A.
Slot B is where my current usable setup is. When installing an update it goes into slot A and it fails whatever I try.
My question would be, how can I copy my exact configuration of slot B to slot A, to try updating again?
Thank you !
Click to expand...
Click to collapse
Not sure what do you try there. Its much easier and safe to factory reset the whole phone and try to update it. Maybe you should also use MSMTool to go stock if nothing works.
Trust me it's a lot faster to backup your data and reset your phone before trying to copy slots.:good:

Kollachi said:
Not sure what do you try there. Its much easier and safe to factory reset the whole phone and try to update it. Maybe you should also use MSMTool to go stock if nothing works.
Trust me it's a lot faster to backup your data and reset your phone before trying to copy slots.:good:
Click to expand...
Click to collapse
I'm not going to share my whole life here, but that is not an option for now. I can't copy to my phone, and I can't install any tool on the computer I use.
Also it was stock before I flashed the actual 9.5.6. So chances are going back to stock would trigger the exact same thing. It had H2O on slot A when it arrived and OOS on slot B if I recall.
Whatever I am not able to do any of this right now, so copying over from slot B to A would be a good option if it was possible.

Nobody07 said:
I'm not going to share my whole life here, but that is not an option for now. I can't copy to my phone, and I can't install any tool on the computer I use.
Also it was stock before I flashed the actual 9.5.6. So chances are going back to stock would trigger the exact same thing. It had H2O on slot A when it arrived and OOS on slot B if I recall.
Whatever I am not able to do any of this right now, so copying over from slot B to A would be a good option if it was possible.
Click to expand...
Click to collapse
So you rather risk to lose all your data if you play with partitions and slots?
If there is no chance to backup data and reset the phone I wouldn't do anything for now. Hope you'll find a way to fix your problem.:good:

Kollachi said:
So you rather risk to lose all your data if you play with partitions and slots?
If there is no chance to backup data and reset the phone I wouldn't do anything for now. Hope you'll find a way to fix your problem.:good:
Click to expand...
Click to collapse
I guess I will just have to wait then.
What is your advice to be the more effective when it comes to backing up everything and putting it back again?
Can I just restore data + Internal storage + all the other partitions and it will be the exact same? If so should I first restore the data and then flash the ROM, or the other way around?
Thanks
Edit: Is there a possibility to only "reset" one slot?

[Xiaomi POCO X3 NFC surya] Wi-Fi stuck with "Turning on..."

I have successfully installed LineageOS what feels like a hundred times now. I followed every single piece of advice and best practice. In total frustration I gave up LineageOS and followed every single step for an OctaviOS installation. I even flashed the newest Global stock firmware successfully, just to follow every recommended step.
I boot into OctaviOS, after successful installation and...
Wi-Fi still won't turn on.
I am completely out of ideas and I have no idea what to do about it. Going back to stock and using this in production is not an option.
I have installed TWRP 3.4.0-0 By mahajant99 and every ROM flash and partition wipe, worked as expected and I never encountered a serious error. All flashes went fine and everything was done exactly step by step, as the guides recommended. Still, no Wi-Fi.
What can I do to fix this?
P.S.: Wi-Fi works through stock ROM. So no hardware issue.

Please, before flashing a custom ROM, make sure you installed the MIUI 12.0.4.0 Firmware Only because it is an essential to make WIFI and Calling Works...
Please be guided here on the tutorial created by @ManoloRey... It works smooth, no problems...
Better use OrangeFox as a recovery image...
How to install Poco x3 ROM
Clean Flash 1. Flash recovery (latest Ofox 11.0 Beta - "Download" ). This is very important. 2. Reboot to recovery. 3. Dont wipe or format anything.. 4. Flash any custom roms you want. e.g. PE+. etc. Wait until complete. 5. Format data -> Yes. 6. Reboot to System. 7. Complete initial setup. 8...
telegra.ph

Please, before flashing a custom ROM, make sure you installed the MIUI 12.0.4.0 Firmware Only because it is an essential to make WIFI and Calling Works...
Please be guided here on the tutorial created by @ManoloRey... It works smooth, no problems...
Better use OrangeFox as a recovery image...
https://telegra.ph/How-to-http://http://
Disregard this...

yan2xme said:
Please, before flashing a custom ROM, make sure you installed the MIUI 12.0.4.0 Firmware Only because it is an essential to make WIFI and Calling Works...
Please be guided here on the tutorial created by @ManoloRey... It works smooth, no problems...
Better use OrangeFox as a recovery image...
How to install Poco x3 ROM
Clean Flash 1. Flash recovery (latest Ofox 11.0 Beta - "Download" ). This is very important. 2. Reboot to recovery. 3. Dont wipe or format anything.. 4. Flash any custom roms you want. e.g. PE+. etc. Wait until complete. 5. Format data -> Yes. 6. Reboot to System. 7. Complete initial setup. 8...
telegra.ph
Click to expand...
Click to collapse
To test, I followed the guide and installed this precise FW+Vendor image. Doing this, I cannot boot into a custom ROM (e.g. OctaviOS), at all. I repeated this test several times, to exclude possible installation errors. I did CLEAN flashes and installations. Still, it makes things worse. As already said, I can't even boot into the ROM.

Aki-to said:
To test, I followed the guide and installed this precise FW+Vendor image. Doing this, I cannot boot into a custom ROM (e.g. OctaviOS), at all. I repeated this test several times, to exclude possible installation errors. I did CLEAN flashes and installations. Still, it makes things worse. As already said, I can't even boot into the ROM.
Click to expand...
Click to collapse
Better just try another rom... They are all still AOSP and uses same kernel as NitrogenOS does. Better use EvoX or RR or Pixel Experience ROM... They're more polished and expect to also have great updates... Just wait for more stable Android 11 Custom Roms or just contact the OP of the OctaviOS for surya...
@id.agung17

yan2xme said:
Better just try another rom... They are all still AOSP and uses same kernel as NitrogenOS does.
Click to expand...
Click to collapse
Even IF another ROM would work -- why doesn't this ROM work on my phone? What's so special about my phone? I have a plain brandnew POCO X3 NFC, like most others here. So why wouldn't it work? Does the firmware version have anything to do with it?
Every guide I read, explicitly recommends version "12.0.3". However, the newest version is already at version "12.0.4". Maybe this is causing the issue?

Aki-to said:
Even IF another ROM would work -- why doesn't this ROM work on my phone? What's so special about my phone? I have a plain brandnew POCO X3 NFC, like most others here. So why wouldn't it work? Does the firmware version have anything to do with it?
Every guide I read, explicitly recommends version "12.0.3". However, the newest version is already at version "12.0.4". Maybe this is causing the issue?
Click to expand...
Click to collapse
Maybe, have you also even tried installing fw 12.0.3? Because at the meantime, no developer has compiled the public kernel of poco x3 to their respective roms... They still use the kernel from the first miui rom... Idk whats really the difference on stock kernel vs the released kernel for surya because in my situation, everything works fine on installing roms. My device is surya, 6/64gb... Plain just like you... Idk why devs couldnt even fix this thing...
Sorry bro I can't help you with this, I'm just an ordinary kid being new to this stuff and have a little experience with this (still I'm a fast learner) because I only experienced much more customization on the Poco X3 than even other phones I have owned previously. I did not also learned coding (i was a rookie HTML coder past years but i forgotten it) like Java or scripts on Linux to compile and make compatible custom roms for phones... Peace

I did the following steps:
Flash "surya_global_images_V12.0.3.0.QJGMIXM_20200925.0000.00_10.0_global" with "MiFlash 2020.3.14.0".
Wipe Cache, Dalvik.
Flash "OctaviOS-v1.2-surya-20201109-2033-VANILLA-Official".
Flash "Magisk-v21.1".
Format Data.
Reboot into System.
Wi-Fi is working!!
Now only NikGapps is missing, but that is just booting into Recovery, flashing and booting back into System, so no problem here, anymore.
Thank you, @yan2xme! You say you are noob, but you had the right guess, too! Anyway, thanks for your help, I appreciate it!
P.S.: Boot-up is additionally much faster, smoother and without SystemUI crash on startup. This 12.0.4 firmware really sucks!

Aki-to said:
I did the following steps:
Flash "surya_global_images_V12.0.3.0.QJGMIXM_20200925.0000.00_10.0_global" with "MiFlash 2020.3.14.0".
Wipe Cache, Dalvik.
Flash "OctaviOS-v1.2-surya-20201109-2033-VANILLA-Official".
Flash "Magisk-v21.1".
Format Data.
Reboot into System.
Wi-Fi is working!!
Now only NikGapps is missing, but that is just booting into Recovery, flashing and booting back into System, so no problem here, anymore.
Thank you, @yan2xme! You say you are noob, but you had the right guess, too! Anyway, thanks for your help, I appreciate it!
P.S.: Boot-up is additionally much faster, smoother and without SystemUI crash on startup. This 12.0.4 firmware really sucks!
Click to expand...
Click to collapse
Ohhh... ok thanks for the appreciation too... Hehe
Resurrection Remix Rom Developer also pointed out that you should flash 12.0.3 even theres the newer version... So maybe.... Haha