Related
New OP6 owner, quite bugged with how this thing works when flashing stuff..
it was a breeze on my 6p, anyways.
i decided to do a "Clean" flash and wiped data/system/dalvik etc.
then tried to flash the Full zip of 5.1.8 (it is a 1.2gb file) and i flashed via TWRP then flashed twrp zip and rebooted recovery/flashed magisk.
but there is no OS installed it says, boots me back into twrp.
my question now is how do i get it back to load up OOS, do i have to use fastboot now .. ?
i dont want it to wipe my whole SD
what do i do, and how do i stop this from happening for next time?
i thought flashing was normal that way, are we not supposed to wipe system with the op phones..?
i had a MOD installed (xXx) and wanted it removed so that i could install another mod ,thus i wiped system/data etc.
please let me know how to fix this, thx !
leondestiny said:
New OP6 owner, quite bugged with how this thing works when flashing stuff..
it was a breeze on my 6p, anyways.
i decided to do a "Clean" flash and wiped data/system/dalvik etc.
then tried to flash the Full zip of 5.1.8 (it is a 1.2gb file) and i flashed via TWRP then flashed twrp zip and rebooted recovery/flashed magisk.
but there is no OS installed it says, boots me back into twrp.
my question now is how do i get it back to load up OOS, do i have to use fastboot now .. ?
i dont want it to wipe my whole SD
what do i do, and how do i stop this from happening for next time?
i thought flashing was normal that way, are we not supposed to wipe system with the op phones..?
i had a MOD installed (xXx) and wanted it removed so that i could install another mod ,thus i wiped system/data etc.
please let me know how to fix this, thx !
Click to expand...
Click to collapse
You need to make sure you are booting the slot you flashed the rom on, A or B.
sting5566 said:
You need to make sure you are booting the slot you flashed the rom on, A or B.
Click to expand...
Click to collapse
how do i do this? i only flashed zip from the root of my SD , there was no option to select either A or B :C
i went into advanced or seomthing and saw SLot a and B i tapped a and reboot sytem now it is stuck on twrp logo.
f** this ab ****.
When u flashed the rom and rebooted it should let u know which one u r flashing on when u flash magisk, the xXx should have been a magisk module so should have been deleted when u wiped data, I would re-download 5.1.8
Wipe all again.
Flash OS
Flash twrp installer
Reboot to twrp
Flash magisk and reboot
---------- Post added at 01:23 PM ---------- Previous post was at 01:22 PM ----------
Did u have the magisk module version of xXx, if so all u had to do was uncheck it and reboot
OnePlus 6 has two partitions like the Pixel 2. For seamless OTA updates. In TWRP go to the Reboot menu and you'll see your currently active slot. It's either A or B. Switch to the other one and reboot. That should do it if you did flash the ROM.
Bradl79 said:
When u flashed the rom and rebooted it should let u know which one u r flashing on when u flash magisk, the xXx should have been a magisk module so should have been deleted when u wiped data, I would re-download 5.1.8
Wipe all again.
Flash OS
Flash twrp installer
Reboot to twrp
Flash magisk and reboot
---------- Post added at 01:23 PM ---------- Previous post was at 01:22 PM ----------
Did u have the magisk module version of xXx, if so all u had to do was uncheck it and reboot
Click to expand...
Click to collapse
man screw this ab partition shet, i will be forced to do a userdata reset..
can you please advise me what not to do to get into this mess again..?
its not fun recopying my data back and forth.
all i tried to do was clean flash and flash the latest rom via twrp..
why does this thing has to be so complex, please tell me if a clean wipe does this mess ?
cant we safely clean wipe this thing or what?
i love the phone, but the flashing stuff is a huge mess imo.
leondestiny said:
man screw this ab partition shet, i will be forced to do a userdata reset..
can you please advise me what not to do to get into this mess again..?
its not fun recopying my data back and forth.
all i tried to do was clean flash and flash the latest rom via twrp..
why does this thing has to be so complex, please tell me if a clean wipe does this mess ?
cant we safely clean wipe this thing or what?
i love the phone, but the flashing stuff is a huge mess imo.
Click to expand...
Click to collapse
You can always just keep a backup of userdata in TWRP but you don't have to wipe data. If you wipe system and flash the full zip, you will get the no os error but you can boot to system anyway. It just thinks there is no os. The bootloop to TWRP is probably related to magisk.
mikex8593 said:
You can always just keep a backup of userdata in TWRP but you don't have to wipe data. If you wipe system and flash the full zip, you will get the no os error but you can boot to system anyway. It just thinks there is no os. The bootloop to TWRP is probably related to magisk.
Click to expand...
Click to collapse
took me an hour or so to get this thing booting up again..
without the need to wipe SD , this is so strange.
i honestly have no idea how i did it, but i am afraid to use twrp now..
this thing is messed up
leondestiny said:
took me an hour or so to get this thing booting up again..
without the need to wipe SD , this is so strange.
i honestly have no idea how i did it, but i am afraid to use twrp now..
this thing is messed up
Click to expand...
Click to collapse
It's relatively easy. Just always remember to flash TWRP and magisk after flashing full ROM zip. It's always a safe bet to erase your lock screen before messing with TWRP as well so it can just decrypt with no password. If you use a magisk ROM, it's all systemless so the only changes that would stay are the ones that would debloat apps or remove system files. Everything would revert back to normal after you uncheck the ROM module in magisk manager.
mikex8593 said:
It's relatively easy. Just always remember to flash TWRP and magisk after flashing full ROM zip. It's always a safe bet to erase your lock screen before messing with TWRP as well so it can just decrypt with no password. If you use a magisk ROM, it's all systemless so the only changes that would stay are the ones that would debloat apps or remove system files. Everything would revert back to normal after you uncheck the ROM module in magisk manager.
Click to expand...
Click to collapse
hmm okay thx, someone suggested me omni rom, but i will need to erase data right?
but my issue is, if in case i wanted to go back to OOS, would i need to erase data again? :l
and also about flashing roms, must they be flashed on both slots..? a and b ?
i have no clue how i got OOS back booting to be honest.. :l
leondestiny said:
hmm okay thx, someone suggested me omni rom, but i will need to erase data right?
but my issue is, if in case i wanted to go back to OOS, would i need to erase data again? :l
and also about flashing roms, must they be flashed on both slots..? a and b ?
i have no clue how i got OOS back booting to be honest.. :l
Click to expand...
Click to collapse
Switching ROMs, it is best to erase data or keep separate data backups for each ROM and restore the associated ones. As far as flashing on both slots, it wouldn't hurt, but it's not necessary unless instructions dictate. The whole reason for the slots is to allow seamless updates while the os is still active. If you experience any issues with bugs that aren't stated to be in the ROM thread, a clean install is always recommended.
mikex8593 said:
Switching ROMs, it is best to erase data or keep separate data backups for each ROM and restore the associated ones. As far as flashing on both slots, it wouldn't hurt, but it's not necessary unless instructions dictate. The whole reason for the slots is to allow seamless updates while the os is still active. If you experience any issues with bugs that aren't stated to be in the ROM thread, a clean install is always recommended.
Click to expand...
Click to collapse
thx mate, so for next time if i were to flash some oos through twrp, i only need to wipe data/cache etc.
then flash the oos zip ? i dont think i had the option to select which Slot to flash it to, so i guess i just have to reboot to the slot that it has it flashed on..?
and also flashing procedure must be like Rom then twrp then reboot twrp then flash magisk yes?
leondestiny said:
took me an hour or so to get this thing booting up again..
without the need to wipe SD , this is so strange.
i honestly have no idea how i did it, but i am afraid to use twrp now..
this thing is messed up
Click to expand...
Click to collapse
No sheet
This is what happened to me LOL and I soft bricked phone. Never ever bricked a phone before.
I tried to flash havoc os, OOS was originally on both A and B.
This process wiped slot B clean (even tho was booting on slot A), and OOS stayed on slot A.
I went to the reboot screen to reboot recovery on slot B and BAM I was bricked locked into fastboot mode.
And people say its easy.
Now I am in msmdownloadtool, I have managed to get it connected, and I can start the recovery but it fails, so I think the phone may be proper bricked.
Anyone getting a oneplus6 I would say these phones seem to have a genuine risk of brick, all I did was try to boot of a slot which TWRP says had no OS and now I have this problem.
---------- Post added at 01:59 ---------- Previous post was at 01:25 ----------
mikex8593 said:
It's relatively easy. Just always remember to flash TWRP and magisk after flashing full ROM zip. It's always a safe bet to erase your lock screen before messing with TWRP as well so it can just decrypt with no password. If you use a magisk ROM, it's all systemless so the only changes that would stay are the ones that would debloat apps or remove system files. Everything would revert back to normal after you uncheck the ROM module in magisk manager.
Click to expand...
Click to collapse
Havoc OS requires Oxygen OOS in both slots.
So I need to somehow get this to work.
I can unbrick the phone now with msmdownloadtool.
After ubricked the bootloader is locked again so I have to start from scratch.
Unlock oem loader in OS
Unlock bootloader in fastboot
Copy zips to phone.
Boot into TWRP and install TWRP, it says it installs to both slots but B bricks phone.
At this point I have oxygen OOS installed via recovery tool on slot A, twrp installed.
If I try to boot in slot B, phone bricks, fastboot loop which doesnt allow you to boot back into twrp so cannot switch back to slot A without msmdownload tool.
So the question is after I have recovered the phone how do I get oxygen OOS onto slot B as well, given I Cannot boot from slot B?
The solution is probably easy to those who know how but seems it isnt documented.
chrcol said:
No sheet
This is what happened to me LOL and I soft bricked phone. Never ever bricked a phone before.
I tried to flash havoc os, OOS was originally on both A and B.
This process wiped slot B clean (even tho was booting on slot A), and OOS stayed on slot A.
I went to the reboot screen to reboot recovery on slot B and BAM I was bricked locked into fastboot mode.
And people say its easy.
Now I am in msmdownloadtool, I have managed to get it connected, and I can start the recovery but it fails, so I think the phone may be proper bricked.
Anyone getting a oneplus6 I would say these phones seem to have a genuine risk of brick, all I did was try to boot of a slot which TWRP says had no OS and now I have this problem.
---------- Post added at 01:59 ---------- Previous post was at 01:25 ----------
Havoc OS requires Oxygen OOS in both slots.
So I need to somehow get this to work.
I can unbrick the phone now with msmdownloadtool.
After ubricked the bootloader is locked again so I have to start from scratch.
Unlock oem loader in OS
Unlock bootloader in fastboot
Copy zips to phone.
Boot into TWRP and install TWRP, it says it installs to both slots but B bricks phone.
At this point I have oxygen OOS installed via recovery tool on slot A, twrp installed.
If I try to boot in slot B, phone bricks, fastboot loop which doesnt allow you to boot back into twrp so cannot switch back to slot A without msmdownload tool.
So the question is after I have recovered the phone how do I get oxygen OOS onto slot B as well, given I Cannot boot from slot B?
The solution is probably easy to those who know how but seems it isnt documented.
Click to expand...
Click to collapse
Fastboot boot recovery. Img
Flash oos full ROM zip
Flash recovery. Zip
Reboot recovery
Flash oos full ROM zip AGAIN
flash twrp. Zip AGAIN
Reboot recovery
Flash magisk if you want root.
Make sure your using the correct twrp aswell. I recommend bluespark v86
chrcol said:
And people say its easy.
Click to expand...
Click to collapse
it is not easy, i make backups of my whole phone every 2weeks because i am a flashaholic i see myself switching from aosp back to oos and vice versa (i love oos) i actually gave up on flashing roms some weeks ago tried to stick to oos only so that i wont be bothered with bricks for whatver reason (and not being forced to use msmtool) , it is frustrating.
you always have to make sure you are not flashing a rom that has an older security patch , e.g november build of oos if you flash aosp rom with october build you might brick, so the rom has to be either on november security patch or newer e.g december.
it is so confusing as you even have to use the latest twrp always or else you can mess it up again..
always make backups is my advice.
leondestiny said:
it is not easy, i make backups of my whole phone every 2weeks because i am a flashaholic i see myself switching from aosp back to oos and vice versa (i love oos) i actually gave up on flashing roms some weeks ago tried to stick to oos only so that i wont be bothered with bricks for whatver reason (and not being forced to use msmtool) , it is frustrating.
you always have to make sure you are not flashing a rom that has an older security patch , e.g november build of oos if you flash aosp rom with october build you might brick, so the rom has to be either on november security patch or newer e.g december.
it is so confusing as you even have to use the latest twrp always or else you can mess it up again..
always make backups is my advice.
Click to expand...
Click to collapse
If you're installing havoc os, make sure you're using latest bluespark TWRP first. Reboot recovery, flash oos, flash TWRP, reboot recovery, flash havoc gapps and magisk then reboot. The only difference in a/b partition is that there's a few extra steps in the flashing process. You don't have to flash to both slots to have havoc, but you also shouldn't be manually changing the slot in TWRP to try to boot a specific slot unless you know what you're doing.
Since a lot of people have had trouble flashing Custom ROMs, I decided to create a guide that should work on every device (whether A/B partition or not) except on Samsung devices. For bypassing Decryption Issues, adb sideload the .zip files.
GUIDE
I am assuming you have unlocked your Bootloader, flashed TWRP and have some knowledge on ADB.
[This is known as a clean install or clean flash]
Turn off Lockscreen Security
Reboot to Recovery
Factory Reset
Format Data
Copy the .zip files from your PC to your phone / Plug in your USB OTG
Flash the ROM and then the Recovery Installer (No Magisk/SuperSU after)
Reboot to Recovery
Flash GApps and Magisk/SuperSU
Reboot to System
[This is known as a dirty flash]
To update the custom ROM or fix a error (Bootloop after successful first boot, No Service, etc.)
I am assuming you used my guide to flash the custom ROM
These are basically the same steps but without wiping or formatting data
Turn off Lockscreen Security
Reboot to Recovery
Flash the ROM (has to be the same ROM, updated is recommended, older versions may cause issues) and then the Recovery Installer (No Magisk/SuperSU after)
Reboot to Recovery
Flash GApps and Magisk/SuperSU
Reboot to System
LINKS:
Official GApps Website - GApps Github
Official TWRP Website - TWRP Github
Magisk Forum - Magisk Thread - Magisk Github
Official SuperSU Website - SuperSU Forum - SuperSU Thread - SuperSU Github
I recommend the Nano variant of GApps since I have had no error with it.
Enjoy!
[Disabler-ONLY]
`This is basically the same guide just if you want to flash Zackptg5's "Universal DM-Verity, ForceEncrypt, Disk Quota Disablers" or any other disabler which requires different steps.
[This is known as a clean install or clean flash]
Turn off Lockscreen Security
Reboot to Recovery
Format Data
Copy the .zip files from your PC to your phone / Plug in your USB OTG
Flash the ROM and then the Recovery Installer (No Magisk after)
Reboot to Recovery
Flash the Disabler, Magisk and then GApps
Reboot to System
Profit
Dirty Flash? You can't. Usually when using a Disabler you have to clean install your custom ROM.
To update use the method in the first post but for step number 5 Flash the Disabler, Magisk and then GApps
This is a bit much to do. Just use twinnfamous' twrp and you can flash a custom easily. Plus, I flash havoc over crdroid, then back and forth again. So you can flash over. Just have to wipe data and cache after ROM flash and twrp flash then reboot to recovery.
Basically:
Fastboot boot twrp (twinnfamous' 0.7)
Be on 9.0.7 firmware as most custom ROMs use this base right now I think..
Anyway, then flash twrp (twinnfamous' 0.7 installer zip)
Reboot to recovery
Now flash custom ROM
Flash twrp zip
Reboot to recovery
(You'll now be on the opposite slot as before, which means you are on the slot which your new custom ROM was installed)
Wipe > custom > data and cache wipe
Install opengapps nano and magisk 18.0
Reboot system
You'll boot right into the ROM setup screen with no decryption issues along the way as long as you do exactly as I said.
Have fun flashing!
dpryor88 said:
This is a bit much to do. Just use twinnfamous' twrp and you can flash a custom easily. Plus, I flash havoc over crdroid, then back and forth again. So you can flash over. Just have to wipe data and cache after ROM flash and twrp flash then reboot to recovery.
Basically:
Fastboot boot twrp (twinnfamous' 0.7)
Be on 9.0.7 firmware as most custom ROMs use this base right now I think..
Anyway, then flash twrp (twinnfamous' 0.7 installer zip)
Reboot to recovery
Now flash custom ROM
Flash twrp zip
Reboot to recovery
(You'll now be on the opposite slot as before, which means you are on the slot which your new custom ROM was installed)
Wipe > custom > data and cache wipe
Install opengapps nano and magisk 18.0
Reboot system
You'll boot right into the ROM setup screen with no decryption issues along the way as long as you do exactly as I said.
Have fun flashing!
Click to expand...
Click to collapse
You wasted that post just for this? I assure you that my tutorial guarantees success when using a official or unofficial version of TWRP or custom ROM, I also used the method you posted about but it did not work. Also what do you mean by "9.0.7"?
The GApps version you use doesn't have to be Nano and Magisk doesn't have to be v18.0. I'm sure you just copy-pasted this, my method should always succeed. The TWRP doesn't have to be from @twinnfamous , it can be from any developer. This is not a OnePlus 6T only guide.
This flashing process is difficult in my view. Why are you making the simple custom rom flashing process so difficult for the noobs.
_Masked_ said:
You wasted that post just for this? I assure you that my tutorial guarantees success when using a official or unofficial version of TWRP or custom ROM, I also used the method you posted about but it did not work. Also what do you mean by "9.0.7"?
The GApps version you use doesn't have to be Nano and Magisk doesn't have to be v18.0. I'm sure you just copy-pasted this, my method should always succeed. The TWRP doesn't have to be from @twinnfamous , it can be from any developer. This is not a OnePlus 6T only guide.
Click to expand...
Click to collapse
Why are you angry? Haha.
And you linked this from the op6t forums so I'm commenting on that phone. And that's how it's done on that phone. And it does matter which twrp you use for THAT phone because one doesn't decrypt correctly.
Copy and paste? No... And nano is always best if you read xda basically anywhere. Not that I said you HAVE to use nano anyway.. it was just in my steps. And that works for me with any/every ROM. So don't be so opposed to other suggestions. Your method is really weird and involves way too much use of a computer/fastboot. Kind of defeats the purpose of using twrp, don't you think?
Ashwinrg said:
This flashing process is difficult in my view. Why are you making the simple custom rom flashing process so difficult for the noobs.
Click to expand...
Click to collapse
What is making it difficult is encryption/decryption not working right in twrp yet (just a guess). I was having a hell of a time getting anywhere myself and kept getting my storage all jumbled from encryption until I found this thread which put it together for me with the adb sideload part, that bypasses encryption or at least lets you flash what you want when the folder names get all wonky.
Thanks OP for laying it out so clearly for me, I am an old dinosaur that was hesitating on messing with this a/b nonsense until I got my 6T and got the itch again. My trusty dusty nexus 6 is so much easier but it's also been around and has one system and a solid twrp for it.
Cheers! :good:
raiderep said:
What is making it difficult is encryption/decryption not working right in twrp yet (just a guess). I was having a hell of a time getting anywhere myself and kept getting my storage all jumbled from encryption until I found this thread which put it together for me with the adb sideload part, that bypasses encryption or at least lets you flash what you want when the folder names get all wonky.
Thanks OP for laying it out so clearly for me, I am an old dinosaur that was hesitating on messing with this a/b nonsense until I got my 6T and got the itch again. My trusty dusty nexus 6 is so much easier but it's also been around and has one system and a solid twrp for it.
Cheers! :good:
Click to expand...
Click to collapse
Sorry for the late reply, but yes this is for bypassing TWRP Decryption issues.
_Masked_ said:
Since a lot of people have had trouble flashing Custom ROMs, I decided to create a guide that should work on every device (whether A/B partition or not) except on Samsung devices.
GUIDE
I am assuming you have unlocked your Bootloader, flashed TWRP and have some knowledge on ADB.
[This is known as a clean install or clean flash]
Turn off Lockscreen Security
Reboot to Recovery
Format Data (Wipe)
Flash ROM and then the Recovery Installer (No Magisk after)
Reboot to Recovery
Go to Advanced, ADB Sideload then sideload GApps, the Recovery Installer and Magisk
Reboot to System
Profit
I recommend the Nano variant of GApps since I have had no error with it.
Enjoy
Click to expand...
Click to collapse
this step means need do with pc not by twrp
ayed78 said:
this step means need do with pc not by twrp
Click to expand...
Click to collapse
This is to bypass Decryption issues.
Ashwinrg said:
This flashing process is difficult in my view. Why are you making the simple custom rom flashing process so difficult for the noobs.
Click to expand...
Click to collapse
I mean I could make a tool for flashing a custom ROM but I'm sure that there's a tool for that already.
bump. (ignore)
_Masked_ said:
Turn off Lockscreen Security
Reboot to Recovery
Factory Reset
Format Data
Copy the .zip files from your PC to your phone / Plug in your USB OTG
Flash the ROM and then the Recovery Installer (No Magisk/SuperSU after)
Reboot to Recovery
Flash GApps and Magisk/SuperSU
Reboot to System
Click to expand...
Click to collapse
So when are we required to wipe system in addition to just a factory reset? And when do we need to format data?
Krullendhaar said:
So when are we required to wipe system in addition to just a factory reset? And when do we need to format data?
Click to expand...
Click to collapse
Just follow the steps, in order.
Hi.
What if I want to flash a custom kernel on a clean Rom flash? When should I do it? Together with Magisk and Gapps?
What do you mean by "Recovery Installer"? That's the only thing I don't understand.
Thank you for this guide.
Santi3598 said:
What do you mean by "Recovery Installer"? That's the only thing I don't understand.
Thank you for this guide.
Click to expand...
Click to collapse
Same here, I do not understand why I should flash a recovery img when twrp does seem to stay installed after flashing everything. Maybe the custom rom I use does include twrp ?
Custom rom means bugs, possible privacy leak and overall less polished. Developer that are working on them are fantastic but they are most of the time nowhere near as what offer the stock one.
What you need is to check adb, doesn't need root but you can still remove apps (even system one) and do more tweaks.
If needed, check how to patch boot image with magisk, it works on all phone and get you root.
With that, you're free to debloat your device.
Hey just one little question: is it ok to dirty flash with encrypted data folder ?
Santi3598 said:
What do you mean by "Recovery Installer"? That's the only thing I don't understand.
Click to expand...
Click to collapse
Me neither, is it safe to assume that the step can be left out if TWRP is already there and I use it to flash the ROM?
Santi3598 said:
Thank you for this guide.
Click to expand...
Click to collapse
+1
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).
Please forgive my ignorance here. It's been 4 or 5 years since I last flashed a recovery. AB wasn't a thing back then, but it sounds like it obsoleted everything I used to know. Meanwhile, it seems like everyone around here has long since digested the changes and is carrying on conversations premised on a lot of background information I don't know. In short, I'm confused, and I need help.
What I Want to Do:
Flash the microG fork of LineageOS
Flash Magisk
Flash the Asus camera app
Install the unofficial port of the GCam app
Encrypt and divorce the boot password from the lockscreen as per this post (which I can't link to our XDA rejects my post, so I'm copy-pasting instead: https COLON SLASH SLASH forum.xda-developers.com/showpost.php?p=78699812&postcount=58 )
Question 1
Which recovery should I use? It sounds like there are three and each has problems. Is the following correct?
It sounds like the LineageOS has trouble flashing things other than LineageOS -- or is it just OpenGApps that's a problem? Can it flash the microG fork of LineageOS?
It sounds like mauronofrio's unofficial TWRP works generally, but can't flash LineageOS and can't decrypt the data partition if LineageOS encrypted it.
It sounds like bigbiff's official TWRP works generally, but there seem to be differing opinions about whether it can flash LineageOS; it can decrypt a data partition encrypted by LineageOS, but not if a password is set; and its permanent installation feature is currently buggy and might break the boot partition.
Question 2
Some posts suggest using different recoveries to flash different things. Is that advisable?
Question 3
Do I even need to install a recovery permanently? It sounds like it should be possible to boot a recovery using "fastboot boot something.img" and do everything I need to do. Is that right?
Are there any strong reasons why I should have a recovery installed permanently even if it's not necessary?
Question 4
What's the correct install order? LineageOS (microG fork), then Magisk, then Asus Camera?
Question 4b
How do I deal with the A/B thing?
Do I have to install everything to both partitions, or does the recovery install to both partitions automatically, or is stuff installed to just one partition and then somehow magically handled with the next update?
In particular, how do I get Magisk and Asus Camera to carry over to the other partition?
The instructions for the LineageOS recovery include an extra reboot right after installing LineageOS so that the remaining stuff ends up in the same partition. Does TWRP also need the same extra reboot?
Question 5
Do I understand correctly that the GCam port is just a regular apk that can be installed later through normal means -- no flashing required?
Question 6
About divorcing the boot password from the lockscreen:
Does that post apply to LineageOS?
Does the A/B thing complicate the instructions in any way? It sounds like the files to be backed up and restored are in the data partition, so I'm guessing not.
Do I need to remove the boot password to make a recovery work? It sounds like the LineageOS recovery can handle the password; the unofficial TWRP can't even handle the encryption format; and the official TWRP is currently bugged and needs the password removed. Is that right?
Question 7
So, OTA updates for Lineage OS are a thing now? Could someone explain how that works?
q1
- Just opengapps has problems but you can use lucas own opengapps build or mindthegapps. No idea about microG.
- True. There is some difference of opinion where it should be fixed (in lin or twrp).
- It played around with it a lot before giving up. In its current state i would not use it for any rom. As soon as pin/pattern/fp/stock rom/nandroid comes into play there will be problems.
q2
For convenience or if you have problems with stock lineage recovery it makes sense at the current time. Since there is currently no twrp out that fully supports lineage flashing + nandroid and encryption i would either not use twrp at all or wait for the official twrp to be fixed.
q3
This depends on your needs. Most recovery/rom combinations won't decrypt while only fastbooted. Especially when nandroid comes into play you will encounter problems.
q4
Depending on the weather, the build you use and the already installed build/addons you get different results. In general the order of those 2 should not matter but in my experience i get different/unexpected results/problems without beeing able to reliably reproduce the behavior.
q4b
I was in your shoes a year ago I'll try to keep it short. You have 2 slots. some partitions like boot exist in both slots (you will have them twice) while data only exists once. One slot is active. The phone boots from the active slot. You can manually change the active slot from fastboot and twrp so the next reboot will boot from the previously inactive slot (but you should rarely need to do that). Ah yes the most important change is there no longer is a persistent recovery partition. Recovery is embedded as a ramdisk in the boot partition.
Assuming the rom or whatever you are flashing is done right and the recovery you are using works correctly:
- flashing a rom from recovery will flash it to the inactive slot
- flashing an addon like magisk or asuscam or gapps will flash to the active slot (thats why you need to reboot after flashing a rom, so gapps will be flashed to your new rom)
- flashing a recovery installer flashes both boot partitions (at least that is the current state) and remove magisk
- flashing a recovery will install it on the active slot be it from twrp or fastboot
Due to this behavior you will have to install twrpinstaller + gapps+ magisk + asus cam every time you install a new rom (unless the rom has it already like asus cam in the next omnirom weekly) and you will have to reboot to recovery from twrp and lin recovery (active slot change to newly installed rom).
q5 yes
q6 no clue what that even does In general i had problems/errors with so many different combinations of roms/encryption/recovery and nandroid that currently i would advise to disable
pin/pattern/fp if you want to flash a rom and or take/restore a nandroid and reenable it after.
q7 It downloads the newest build and installs it in the backgroud but you still have to manage magisk, twrp etc. manually. So i prefer to just flash everythin from recovery.
hello i was upgrading from stock 9.0.7 to 9.0.9, my bootloader is unlocked and twrp is a permanent one, the phone is also rooted. i wiped system then flashed the 9.0.9 then flashed the 4.0.4 twrp, rebooted into twrp, flashed latest magisk, rebooted into twrp and then pressed reboot into system. the phone is encrypted. the booting animation has been on for 20-30 minutes at this point. is it a bootloop? why what did i do wrong? thanks
@seth wellington
Try formatting data them reboot system. That should get you booted up.
Never wipe system or vendor on these devices and always when flashing a rom flash TWRP installer zip or you won't have twrp because of where recovery is located which is same place as boot.img and it has to be installed when flashing a rom or update to a rom or it won't be present.
How I flash OOS on my once T-Mobile now converted international/global OnePlus 6t.
Boot TWRP
Flash OOS global 10.3.6
Flash TWRP installer
Flash finalize
Format data
Reboot system
How I install a rom on my converted OnePlus 6t. This installation process varies depending on whether or not whatever rom I'm installing comes with gapps and or TWRP and of course you don't want to install global OOS on another model device. Since I converted my T-Mobile OnePlus 6t using guide and msm tool I now use global or international OnePlus 6t roms, firmware... Example Pixel Experience rom installation:
Boot TWRP
Flash OOS 10.3.6 global from repo xda thread
Flash Pixel Experience rom
Flash TWRP installer zip
Flash finalize zip
Format data
Reboot system.
Start to set up device then at some point enable developer options and usb debugging and doable any lock screen and boot twrp and flash magisk for root and reboot system. That is how I install a rom that has gapps but not twrp included in rom zip. Finalize can he found with a quick search on xda. It copies firmware to other slot on your AB partition device so that you don't have to. Saves 5-6 minutes and works great.
Edit
What you could have done is just flash your updated OOS , flash TWRP installer zip, reboot recovery, flash magisk, reboot system. That's what I would have done updating OOS ..
Hope this helps.
Sent from my OnePlus6T using XDA Labs
flash713 said:
@seth wellington
Try formatting data them reboot system. That should get you booted up.
Never wipe system or vendor on these devices and always when flashing a rom flash TWRP installer zip or you won't have twrp because of where recovery is located which is same place as boot.img and it has to be installed when flashing a rom or update to a rom or it won't be present.
How I flash OOS on my once T-Mobile now converted international/global OnePlus 6t.
Boot TWRP
Flash OOS global 10.3.6
Flash TWRP installer
Flash finalize
Format data
Reboot system
How I install a rom on my converted OnePlus 6t. This installation process varies depending on whether or not whatever rom I'm installing comes with gapps and or TWRP and of course you don't want to install global OOS on another model device. Since I converted my T-Mobile OnePlus 6t using guide and msm tool I now use global or international OnePlus 6t roms, firmware... Example Pixel Experience rom installation:
Boot TWRP
Flash OOS 10.3.6 global from repo xda thread
Flash Pixel Experience rom
Flash TWRP installer zip
Flash finalize zip
Format data
Reboot system.
Start to set up device then at some point enable developer options and usb debugging and doable any lock screen and boot twrp and flash magisk for root and reboot system. That is how I install a rom that has gapps but not twrp included in rom zip. Finalize can he found with a quick search on xda. It copies firmware to other slot on your AB partition device so that you don't have to. Saves 5-6 minutes and works great.
Edit
What you could have done is just flash your updated OOS , flash TWRP installer zip, reboot recovery, flash magisk, reboot system. That's what I would have done updating OOS ..
Hope this helps.
Sent from my OnePlus6T using XDA Labs
Click to expand...
Click to collapse
Thank you very much for your reply. Unfortunately I couldn't wait for that long and I had to do something right then. After some attempts I also lost my twrp and was left without a functioning recovery, so I had to look for help and some people helped me go through unbricking through the msm tool.
The thing is i just really want to always flash clean so that the phone doesn't lag and works properly, I had no idea you shouldn't wipe system... The guide that I followed said that when updating oxygen manually you have to wipe system so I thought nothing would go wrong. I still don't know what caused a bootloop since that guide was a verified one. Thanks a lot for your help. So if I'm reading it correctly, you have to do the wipes after you've installed the system, not before?
seth wellington said:
Thank you very much for your reply. Unfortunately I couldn't wait for that long and I had to do something right then. After some attempts I also lost my twrp and was left without a functioning recovery, so I had to look for help and some people helped me go through unbricking through the msm tool.
The thing is i just really want to always flash clean so that the phone doesn't lag and works properly, I had no idea you shouldn't wipe system... The guide that I followed said that when updating oxygen manually you have to wipe system so I thought nothing would go wrong. I still don't know what caused a bootloop since that guide was a verified one. Thanks a lot for your help. So if I'm reading it correctly, you have to do the wipes after you've installed the system, not before?
Click to expand...
Click to collapse
Quit a few pretty well known developers here on xda (AOSiP op is one and there are more) say not to wipe system or vendor in their first posts of their custom rom threads. The way I describe how I install works 100% always and is the cleanest possible installation. Formatting data when installing a new rom at the end of install process does all the wiping needed to make sure nothing is left from the past and everything is clean. I used to wipe various partitions but on other devices. The install directions I use are originally from the PiXeN rom developers op. I've been flashing roms since the Nexus S days. Not saying that means anything other than I'm kinda old now. ? But that install process has never failed me once and I've flashed I'm sure hundreds of times on this device.. When I update i just flashing the updated rom over current and don't wipe anything then flashing twrp installer zip, reboot recovery flash magisk reboot system or if gapps are needed when I reboot recovery flash gapps..Unless it's a major OS update that's always worked for me.
Possibly not formatting data caused boot loop.. I know when going from OOS to AOSP rom format data is mandatory or it won't boot system.. I never flash magisk during initial flash. I always boot system first then at some point boot twrp and flash magisk. Try that next round and see if it turns out better. The whole AB partition deal made me feel like I was really old and retarded.
If I was updating OOS I would boot recovery, flash OOS, flash twrp installer zip reboot recovery, flash magisk, reboot system. Check out the finalize script xda thread. There are two here. The original person who made finalize has a thread and another user has another finalize thread. I believe in guides section of OnePlus 6t. With Android there are always more than a few ways to achieve something you know ... But what I post here is what I've been doing and I've flashed 400-500 times at least on this device.
Sent from my OnePlus6T using XDA Labs
@flash713
I totally trust you and respect anything you say and recommend me to do. Thanks a lot for all the instructions and clarification. I've been into android far less time than you — only since oneplus one. I'm extremely bad with tech but even with that phone j somehow managed to get bootloops or half-bricks ten times less than with the oneplus 6. And back then in 2015 I was way more enthusiastic: flashing twice a month loads and loads of roms. Of course it wasn't my personal achievement, I was still simply following detailed and carefully written instructions on forums on how to flash a particular rom in a particular way, but hey, at least I somehow managed it.
Now in this case I'm assuming it's the a/b partitions they've introduced that have completely changed the process and ways of flashing to the point that I stick to the guides and still get bootloops lol. That unbricking process was a huge stress for me, I don't think I'm going to touch anything in my phone for a while now. And I'm on the latest 10.3.6 oxygen so it's alright. Thank you for your help buddy
seth wellington said:
@flash713
I totally trust you and respect anything you say and recommend me to do. Thanks a lot for all the instructions and clarification. I've been into android far less time than you — only since oneplus one. I'm extremely bad with tech but even with that phone j somehow managed to get bootloops or half-bricks ten times less than with the oneplus 6. And back then in 2015 I was way more enthusiastic: flashing twice a month loads and loads of roms. Of course it wasn't my personal achievement, I was still simply following detailed and carefully written instructions on forums on how to flash a particular rom in a particular way, but hey, at least I somehow managed it.
Now in this case I'm assuming it's the a/b partitions they've introduced that have completely changed the process and ways of flashing to the point that I stick to the guides and still get bootloops lol. That unbricking process was a huge stress for me, I don't think I'm going to touch anything in my phone for a while now. And I'm on the latest 10.3.6 oxygen so it's alright. Thank you for your help buddy
Click to expand...
Click to collapse
Np. My real first name is Seth. Haha. Cool name btw. I just installed OOS 10.3.7 on my 6t. I was notified of the update yesterday via oxygen updater app from play store. Good handy app to have. I would have never known 10.3.7 was out or at least not so soon if it wasn't for that app. I believe it auto notified me too. I don't remember setting it up. Android has changed soooo much you know.. I love my OnePlus 6t though. Definitely one of my most favorite devices I've ever used. What's new today is gone at some point and replaced with "better.." lol. Not always better imo anyway. Glad I could help. Feel free to message me any time. Good day to you.