[appeal][p]z3 dual D6633 patch for running z3 roms - Xperia Z3 General

hi guys
i need a patch for z3 dual that would be able to run z3 single-sim roms on z3 dual in android 9 pie
can any develpoer make it for me?please
thanks

please
somebody help meeeeeee

I found some patch on old oreo Z3 thread.
Also, I read the LOS 15 thread today. You need a specific TWRP for D6633. But I can't find this file.
This patch only tested on oreo ROMs so I don't know if it will work on pie.
Anyway, there you go.
You'll need a clean flash. The steps are:
- Flash TWRP 3.3.1 (if you want to install LOS 16.0, flash the boot.img from the .zip)
- reboot to TWRP, wipe everything (system, cache, dalvik, data, internal storage. BUT if you store the ROM and gapps file on internal storage, DO NOT wipe internal storage)
- flash ROM, Gapps, reboot to TWRP
- flash this dualsim patch, reboot to system
Good luck.

Zerikwan said:
I found some patch on old oreo Z3 thread.
Also, I read the LOS 15 thread today. You need a specific TWRP for D6633. But I can't find this file.
This patch only tested on oreo ROMs so I don't know if it will work on pie.
Anyway, there you go.
You'll need a clean flash. The steps are:
- Flash TWRP 3.3.1 (if you want to install LOS 16.0, flash the boot.img from the .zip)
- reboot to TWRP, wipe everything (system, cache, dalvik, data, internal storage. BUT if you store the ROM and gapps file on internal storage, DO NOT wipe internal storage)
- flash ROM, Gapps, reboot to TWRP
- flash this dualsim patch, reboot to system
Good luck.
Click to expand...
Click to collapse
thanks man appreciate that
problem still exist
ive got another problem too
after flashing a rom i want to boot to recovery but recovery doesnt load i mean it just reboots again and again
i tried many wayz but still cant go to TWRP after flashing rom

foli2 said:
thanks man appreciate that
problem still exist
ive got another problem too
after flashing a rom i want to boot to recovery but recovery doesnt load i mean it just reboots again and again
i tried many wayz but still cant go to TWRP after flashing rom
Click to expand...
Click to collapse
Sorry, I forgot to mention that.
The TWRP 3.3.1 from the link is only work on LOS 16.0. If you flash another ROM with TWRP 3.3.1, the TWRP will break.
In other word, you must flash the correct TWRP for the ROM. Also, in the past, there is a specific TWRP for Z3 dual but the link is dead.

Zerikwan said:
Sorry, I forgot to mention that.
The TWRP 3.3.1 from the link is only work on LOS 16.0. If you flash another ROM with TWRP 3.3.1, the TWRP will break.
In other word, you must flash the correct TWRP for the ROM. Also, in the past, there is a specific TWRP for Z3 dual but the link is dead.
Click to expand...
Click to collapse
i got frustrated completely

Related

Cant install LineageOS 14.1 on G2 D802 (TWRP deletes root)

Heyy,
as i had some problems with my g2 i had to flash stock rom kitkat 4.4.2.
I rooted with ioroot, downloaded lineage and gapps files, flashed custom recovery with autorec but if i then go to twrp and install lineage os and gapps, i always get "your device does not appear to have root. do u want to install supersu?", althoug ive checked root with "root checker" before... i cant find the mistake
I WANT LINEAGE OS
Quicka said:
Heyy,
as i had some problems with my g2 i had to flash stock rom kitkat 4.4.2.
I rooted with ioroot, downloaded lineage and gapps files, flashed custom recovery with autorec but if i then go to twrp and install lineage os and gapps, i always get "your device does not appear to have root. do u want to install supersu?", althoug ive checked root with "root checker" before... i cant find the mistake
I WANT LINEAGE OS
Click to expand...
Click to collapse
Autorec is just the first step to twrp. Go to https://forum.xda-developers.com/lg-g2/development/twrp-twrp-2-8-0-0-kernel-f2fs-tools-t2898705 and get the bumped version 3.1.0-1.
Then put it in your phones memory, boot into twrp you got from autorec and flash the new version.
Jan Philipp said:
Autorec is just the first step to twrp. Go to https://forum.xda-developers.com/lg-g2/development/twrp-twrp-2-8-0-0-kernel-f2fs-tools-t2898705 and get the bumped version 3.1.0-1.
Then put it in your phones memory, boot into twrp you got from autorec and flash the new version.
Click to expand...
Click to collapse
i have done it... but after i wiped data,... etc. flashed lineage os and gapps and reboot system, phone screen gets black... and i can only go to download mode to flash again stock rom ive tried it about 5 times
Problem fixed
problem fixed: flashed lollipop firmware, then rooted with LGoneClickRoot and installed TWRP with autorec
Quicka said:
problem fixed: flashed lollipop firmware, then rooted with LGoneClickRoot and installed TWRP with autorec
Click to expand...
Click to collapse
How did you flashed your phone? Your display have been black and you haven't seen anything. How did you entered into download mode?
djsasha78 said:
How did you flashed your phone? Your display have been black and you haven't seen anything. How did you entered into download mode?
Click to expand...
Click to collapse
just held the volume up button and then connected with pc. then using lg flash tool to flash lollipop stock rom
1. Root + TWRP : https://www.dropbox.com/s/2shvozzbu29xjfu/LGG2-D802-OneClickRootRecoveryV1.1.zip?dl=0
2. Update TWRP to 3.1 by flashing zip file and then rebooting recovery: http://www.gregtwallace.com/lgg2-projects/twrp/?version=3.1.0-1
3. LineageOS by flashing rom zip file and gapps: https://download.lineageos.org/d802 + http://opengapps.org/ (ARM + Android 7.1)
easiest method to flash lineageOS on LG G2 https://www.youtube.com/watch?v=BoPjGM0nrak (Video tutorial)
Hi,
It seems I have the same issue :
I tried to install LineAge, using TWRP 3.2.1 (from CM12.1), but nothing is working (I tried 20180425 and 20180404 nightly versions). After reboot I can see the backlight on the lcd screen but nothing else. Then I tested the installation of a CM12 version, all is right, normal boot. No error message written in the console. i tried also a CM13 install, same as Lineage.
Do you think I have to flask back to LG "OS" ?
JackSparreau said:
Hi,
It seems I have the same issue :
I tried to install LineAge, using TWRP 3.2.1 (from CM12.1), but nothing is working (I tried 20180425 and 20180404 nightly versions). After reboot I can see the backlight on the lcd screen but nothing else. Then I tested the installation of a CM12 version, all is right, normal boot. No error message written in the console. i tried also a CM13 install, same as Lineage.
Do you think I have to flask back to LG "OS" ?
Click to expand...
Click to collapse
Are you clean flashing? Make sure to factory reset, wipe system, data and cache before flash. Never wipe internal storage. Swipe factory reset again after flash. Try flashing gapps later after confirming that Rom boots fine.
cropsroth said:
Are you clean flashing? Make sure to factory reset, wipe system, data and cache before flash. Never wipe internal storage. Swipe factory reset again after flash. Try flashing gapps later after confirming that Rom boots fine.
Click to expand...
Click to collapse
Hi,
yes I wiped Dalvik, system, data & cache through TWRP, before flash. But I don't wipe after, I rebooted without GApps...
Maybe, because I read that somewhere, I need to flash a bootstack. I don't know when I have to di it, if I have to do.
Thanks
JackSparreau said:
Hi,
yes I wiped Dalvik, system, data & cache through TWRP, before flash. But I don't wipe after, I rebooted without GApps...
Maybe, because I read that somewhere, I need to flash a bootstack. I don't know when I have to di it, if I have to do.
Thanks
Click to expand...
Click to collapse
Yes, you don't wipe after flash, but you swipe the factory reset, it does not wipe but resets the flashed Rom. Give it a clean shot again. Check MD5 of the all files you downloaded with original MD5 to confirm the file didn't get corrupt.
Boot stack flash not needed. Please read the first post thoroughly in lineage thread
"""
Requirements:
Custom recovery (TWRP or any other)
KitKat (KK) bootloader (included in the lg-devs LP bootstack)
KitKat (KK) bootstack minimum; Please read the entire FAQ for important bootstack information. Installation of bootstacks is NOT recommended.
Clean flash if coming from another ROM or CM 13 (no dirty flash, wipe system too check you bootstack(needen bump support)
"""
crophs said:
... but you swipe the factory reset, it does not wipe but resets the flashed Rom. Give it a clean shot again. ...
Click to expand...
Click to collapse
Hi,
what do you mean by "you swipe the factory reset", I'm not sure what it is, either "give it a clean shot again".
Sorry I'm not very aware of all those processes ^_^, and I'm french so not very aware of some vocabulary words
Thank you

Going back to stock OOS -> stock recovery?

Hello there ^^
I want to completely revert my OnePlus 5 to stock. I found some guides that could help me through this, but I have one problem/question:
Where can I download the latest Stock recovery (that works with Treble)? I've searched through some threads and although some users post download links, their posts are often quite old and thus the download also seems outdated.
Do I actually need to flash the latest version of the stock OOS recovery? Or is it sufficient to install just any version and then flash the stock OOS zip file?
Anf if I need the latest one, can someone provide me with a download link or tell me where I can find it?
Thank you so much!
GoldenPants said:
Hello there ^^
I want to completely revert my OnePlus 5 to stock. I found some guides that could help me through this, but I have one problem/question:
Where can I download the latest Stock recovery (that works with Treble)? I've searched through some threads and although some users post download links, their posts are often quite old and thus the download also seems outdated.
Do I actually need to flash the latest version of the stock OOS recovery? Or is it sufficient to install just any version and then flash the stock OOS zip file?
Anf if I need the latest one, can someone provide me with a download link or tell me where I can find it?
Thank you so much!
Click to expand...
Click to collapse
Direct link to download the latest stock OnePlus 5 recovery: https://oxygenos.oneplus.net.s3.amazonaws.com/recovery.img (also available on the OnePlus 5 Software Upgrade page on the OnePlus website here)
Also, in case you need it, you can download the complete zip of any version of OxygenOS version from this post.
It worked, I'm back to stock now.
Thanks!^^
Hi
Thanks for the post Shadowstep.
The OOS zip files that is on your ports, can I just use TWRP? Or does it basically wipe out everything and does a complete install, or does it just use TWRP, and do a system/data/cache wipe and I can use nandroid restore if it doesn't work? I have been looking for just a flashable image of OOs 8.1
Regards
Heeter said:
Hi
Thanks for the post Shadowstep.
The OOS zip files that is on your ports, can I just use TWRP? Or does it basically wipe out everything and does a complete install, or does it just use TWRP, and do a system/data/cache wipe and I can use nandroid restore if it doesn't work? I have been looking for just a flashable image of OOs 8.1
Regards
Click to expand...
Click to collapse
Yes, you can flash the complete zip via TWRP and it'll install just fine. For a clean install, I suggest you boot to TWRP, wipe all the partitions (except internal storage), including system, vendor, cache, dalvik-cache and data. Once done, flash the full OOS zip and you will have a fresh, clean install of stock OOS with encryption.
shadowstep said:
Yes, you can flash the complete zip via TWRP and it'll install just fine. For a clean install, I suggest you boot to TWRP, wipe all the partitions (except internal storage), including system, vendor, cache, dalvik-cache and data. Once done, flash the full OOS zip and you will have a fresh, clean install of stock OOS with encryption.
Click to expand...
Click to collapse
Great, Thank you sooooo much for your response, shadowstep. Great work on the other thread you have going. I have to move on from this one week fresh install lineage 15.1 because the GPS just refuses to work
i have a oneplus 5 , which while updating got crashed and the power button now is not responding. i did custom root via candy rom (twrp). but the issue still persist. THe power button can be used to switch on and off the phone but is not waking up the device. please guide me.
thanks in advance
rohit787898 said:
i have a oneplus 5 , which while updating got crashed and the power button now is not responding. i did custom root via candy rom (twrp). but the issue still persist. THe power button can be used to switch on and off the phone but is not waking up the device. please guide me.
thanks in advance
Click to expand...
Click to collapse
Please post your question here https://forum.xda-developers.com/oneplus-5/help/qa-help-thread-newbies-post-t3624656 or in a new thread cause your issue isn't related to that topic discussed here
I on pie this recovery work on pie os
I want stock everything
lalit kandpal said:
I on pie this recovery work on pie os
I want stock everything
Click to expand...
Click to collapse
Yes, the recovery linked in the previous posts is compatible with OOS Pie.

flashing custom rom on A/B device

Why,in custom ROMs section on 6t forum,every one of custom rom developer in his OP states DIFFERENT "Flashing instructions"?
Not a single rom dev,in his OP have same flashing instructions as some other dev! As I read more,it looks like half of them are wrong instructions,or that they don't have this device,or they don't know.
- flashing on both slots a&b?
flash OOS rom,them twrp.zip,reboot to TWRP (to any of slots),and internal will be encrypted and unreadable.Theres no way to flash on both slots in one take in TWRP or in two takes in row(with in TWRP,reboot to TWRP different slot).There's need for at least one full boot to Operating System,then back to TWRP,and internal will be visible and decrypt ed.
Many custom ROMs need OOS on both slots to be able to make them run,but this looks like nonsense to me.
- changing slots in TWRP?
let's say you flash magisk while in slot A,go to "reboot" and change slot to B, but dont reboot to TWRP.Now flash magisk.it will flash on same slot as first time,there was no slot changing.
- delete wipe "system" in TWRP,or worse "factory reset"?
it's mistake that costs me a lot of time,Ill never do it again.As all custom ROMs now have script that wipes all unnecessary files,there's no need to wipe system and screw your phone for few hours until you fix it.For me,a big No No.
best way of flashing custom os over OOS?
for me,I go into TWRP,flash custom rom,flash TWRP zip,then I reboot into TWRP and flash gapps and magisk.if internal is crypted and I can't flash gapps and magisk,I do a boot into rom,and back to TWRP to finish my flashing.wiola,it boots and works,clean rom and all is fine.
Flash back to OOS?I just go into TWRP,flash OOS ,flash twrp.zip,reboot to twrp and flash magisk.if internal is crypted,I boot into OOS,them back to TWRP,and flash everything else what I need(like magisk and kernel)
a/b devices are nothing new,but it looks to me Like on 6t is all overcomplicated.
So,tell me how you guys do it and what are yours ways of doing it right?
shawek said:
Why,in custom ROMs section on 6t forum,every one of custom rom developer in his OP states DIFFERENT "Flashing instructions"?
Not a single rom dev,in his OP have same flashing instructions as some other dev! As I read more,it looks like half of them are wrong instructions,or that they don't have this device,or they don't know.
- flashing on both slots a&b?
flash OOS rom,them twrp.zip,reboot to TWRP (to any of slots),and internal will be encrypted and unreadable.Theres no way to flash on both slots in one take in TWRP or in two takes in row(with in TWRP,reboot to TWRP different slot).There's need for at least one full boot to Operating System,then back to TWRP,and internal will be visible and decrypt ed.
Many custom ROMs need OOS on both slots to be able to make them run,but this looks like nonsense to me.
- changing slots in TWRP?
let's say you flash magisk while in slot A,go to "reboot" and change slot to B, but dont reboot to TWRP.Now flash magisk.it will flash on same slot as first time,there was no slot changing.
- delete wipe "system" in TWRP,or worse "factory reset"?
it's mistake that costs me a lot of time,Ill never do it again.As all custom ROMs now have script that wipes all unnecessary files,there's no need to wipe system and screw your phone for few hours until you fix it.For me,a big No No.
best way of flashing custom os over OOS?
for me,I go into TWRP,flash custom rom,flash TWRP zip,then I reboot into TWRP and flash gapps and magisk.if internal is crypted and I can't flash gapps and magisk,I do a boot into rom,and back to TWRP to finish my flashing.wiola,it boots and works,clean rom and all is fine.
Flash back to OOS?I just go into TWRP,flash OOS ,flash twrp.zip,reboot to twrp and flash magisk.if internal is crypted,I boot into OOS,them back to TWRP,and flash everything else what I need(like magisk and kernel)
a/b devices are nothing new,but it looks to me Like on 6t is all overcomplicated.
So,tell me how you guys do it and what are yours ways of doing it right?
Click to expand...
Click to collapse
I agree with you!!! This is a mess
even though I have flashed thousands of roms over the years, since I got rid of my Nexus 6, I havent had a phone that I could flash roms on, so, after dumping my Note 8 for this great phone, I was very hesitant to flash a custom rom, for all the reasons you have mentioned..
So, my question is, can you flash ANY of these custom roms by using the clear method that you mentioned in the OP?
If on one of the beta releases, is the procedure the same as I am showing below, or, do you always have to first return to stock OOS?
In my years of flashing dozens of phones, you never had to go back to "stock" if you wiped everything before flashing, but, it seems like on several of these roms, you are instructed to first return to "stock", THEN flash the new custom rom...
Plus, some roms say to wipe everything before you flash, and others say not to wipe system, or not to wipe data...
Unless I am nuts, I always thought that you wipe everything before converting to a totally new rom, but, maybe I am wrong here too..
"for me,I go into TWRP,flash custom rom,flash TWRP zip,then I reboot into TWRP and flash gapps and magisk.if internal is crypted and I can't flash gapps and magisk,I do a boot into rom,and back to TWRP to finish my flashing.wiola,it boots and works,clean rom and all is fine."
These instructions seem pretty clear and concise, hopefully, they are correct, and we can just use this exact method and be done with it!
No mention of wiping in your directions...what do YOU wipe before flashing a new custom rom?
Hopefully, this gets cleared up once and for all, and we can ask the MODS to make a sticky of the ACTUAL CORRECT INSTRUCTIONS>>
thanks
wase4711 said:
"for me,I go into TWRP,flash custom rom,flash TWRP zip,then I reboot into TWRP and flash gapps and magisk.if internal is crypted and I can't flash gapps and magisk,I do a boot into rom,and back to TWRP to finish my flashing.wiola,it boots and works,clean rom and all is fine."
These instructions seem pretty clear and concise, hopefully, they are correct, and we can just use this exact method and be done with it!
No mention of wiping in your directions...what do YOU wipe before flashing a new custom rom?
Hopefully, this gets cleared up once and for all, and we can ask the MODS to make a sticky of the ACTUAL CORRECT INSTRUCTIONS>>
thanks
Click to expand...
Click to collapse
-if on custom rom,probably it's good to first go to stock OOS and then to another custom rom.but this is also strange to me,as I don't understand what are benefits of this.i also read this,Google heh.i tried going from AOSCP to PixelEcpirince without flashing OOS in-between process,all was fine.
-I haven't been on Beta OOS yet,only stable.But that thing bout "before flashing custom rom,flash stable OOS even if your on Beta OOS" is also a big question to me.they are practically the same,both are latest OOS,one maybe more stable them other,but this also can be discussed hehe
-i don't wipe anything!! when my custom rom boots,I go into it's settings, without setting my Google account and other stuff, and I do "factory reset"( not in TWRP,in custom rom's settings!).Phone reboots,and all is fine,clean beginning,TWRP works,root works.About unwantedFolders in internal storage,I delete them manualy.
Only thing in my experience to wipe in TWRP is DATA,but this is also questionable,as I run into problems also doing data wipe I TWRP.
Now ROMs(maybe only for a/b devices) have scripts that wipe previous System during flashing new rom,so we don't have to do a Clean Flash anymore.
I'm also confused,more I read,less I understand ?
I like the idea of wiping via factory reset, once the rom boots, but, if it does NOT boot, then you wouldnt be able to do it that way..
I guess flashing an OOS based rom over an OOS based rom would always allow you to boot, if done right..
But, roms like RR, Carbon, AICP, and a couple others that have shown up here recently were never really OOS based roms, but AOSP based, at least I thought so..
the more I think about this, the more confusing it seems to get..
wase4711 said:
I like the idea of wiping via factory reset, once the rom boots, but, if it does NOT boot, then you wouldnt be able to do it that way..
I guess flashing an OOS based rom over an OOS based rom would always allow you to boot, if done right..
But, roms like RR, Carbon, AICP, and a couple others that have shown up here recently were never really OOS based roms, but AOSP based, at least I thought so..
the more I think about this, the more confusing it seems to get..
Click to expand...
Click to collapse
This is from the pixel 2 xl forum another a/b device
First time installing Pixel Dust ROM, or coming from another ROM:
As mentioned above, you are required to flash stock ROM before installing this custom ROM.
1. Flashing Stock ROM:
Follow these instructions: https://developers.google.com/android/images#taimen
2. Flashing PixelDust ROM:
Reboot to twrp
Wipe Dalvik cache and Data partitions
Flash ROM
Flash twrp zip
Reboot to System and enjoy the Pixel Dust Goodness!
Flashing Magisk:
You cannot flash Magisk during the initial install. You must boot into PixelDust ROM at least once!
Reboot to Recovery
Flash Magisk-v17.x.zip
Reboot to System
shawek said:
Why,in custom ROMs section on 6t forum,every one of custom rom developer in his OP states DIFFERENT "Flashing instructions"?
Not a single rom dev,in his OP have same flashing instructions as some other dev! As I read more,it looks like half of them are wrong instructions,or that they don't have this device,or they don't know.
- flashing on both slots a&b?
flash OOS rom,them twrp.zip,reboot to TWRP (to any of slots),and internal will be encrypted and unreadable.Theres no way to flash on both slots in one take in TWRP or in two takes in row(with in TWRP,reboot to TWRP different slot).There's need for at least one full boot to Operating System,then back to TWRP,and internal will be visible and decrypt ed.
Many custom ROMs need OOS on both slots to be able to make them run,but this looks like nonsense to me.
- changing slots in TWRP?
let's say you flash magisk while in slot A,go to "reboot" and change slot to B, but dont reboot to TWRP.Now flash magisk.it will flash on same slot as first time,there was no slot changing.
- delete wipe "system" in TWRP,or worse "factory reset"?
it's mistake that costs me a lot of time,Ill never do it again.As all custom ROMs now have script that wipes all unnecessary files,there's no need to wipe system and screw your phone for few hours until you fix it.For me,a big No No.
best way of flashing custom os over OOS?
for me,I go into TWRP,flash custom rom,flash TWRP zip,then I reboot into TWRP and flash gapps and magisk.if internal is crypted and I can't flash gapps and magisk,I do a boot into rom,and back to TWRP to finish my flashing.wiola,it boots and works,clean rom and all is fine.
Flash back to OOS?I just go into TWRP,flash OOS ,flash twrp.zip,reboot to twrp and flash magisk.if internal is crypted,I boot into OOS,them back to TWRP,and flash everything else what I need(like magisk and kernel)
a/b devices are nothing new,but it looks to me Like on 6t is all overcomplicated.
So,tell me how you guys do it and what are yours ways of doing it right?
Click to expand...
Click to collapse
You make it overcomplicated.
To flash both slots you only need to do a complete reboot to make sure the OS is not hosed.
You do that so if it is you can use the other slot. This is not necessary.
You flash in TWRP, change the slot and reboot into TWRP and flash the other slot.
It could be easier if TWRP allowed flashing on the inactive slot.
But, even if you are rooted and want to upgrade it is suggested to upgrade both slots.
I think it's just a minor pain. There are bigger problems.
tech_head said:
You make it overcomplicated.
To flash both slots you only need to do a complete reboot to make sure the OS is not hosed.
You do that so if it is you can use the other slot. This is not necessary.
You flash in TWRP, change the slot and reboot into TWRP and flash the other slot.
It could be easier if TWRP allowed flashing on the inactive slot.
But, even if you are rooted and want to upgrade it is suggested to upgrade both slots.
I think it's just a minor pain. There are bigger problems.
Click to expand...
Click to collapse
it's not a minor pain if most of time that I go to flash custom rom,I lost all my 60-80gigs of internal data, cuz of failed decryption,or failed rom flash,or failed TWRP flash.There were times when I did Factory reset in TWRP,flashed OOS,flashed TWRP.zip,did reboot to recovery,and I lost recovery.I was left with bootloader (fastboot) and had to fastbooting OOS few times(which led to full wipe of internal storage).OOS wasn't even flashed,or TWRP wanst even flashed.And I just followed instructions.
this are the things that I'm talking about.Even if I follow instructions, instructions are not detailed.
now I probably know how to do it right,,but still...I learned it hard way,and still learning
thanks for your opinion and answer:good:
shawek said:
it's not a minor pain if most of time that I go to flash custom rom,I lost all my 60-80gigs of internal data, cuz of failed decryption,or failed rom flash,or failed TWRP flash.There were times when I did Factory reset in TWRP,flashed OOS,flashed TWRP.zip,did reboot to recovery,and I lost recovery.I was left with bootloader (fastboot) and had to fastbooting OOS few times(which led to full wipe of internal storage).OOS wasn't even flashed,or TWRP wanst even flashed.And I just followed instructions.
this are the things that I'm talking about.Even if I follow instructions, instructions are not detailed.
now I probably know how to do it right,,but still...I learned it hard way,and still learning
thanks for your opinion and answer:good:
Click to expand...
Click to collapse
I understand now.
The instructions are not clear for most of this stuff and you can screw up.
If something fails to flash, there are very few reasons to ever completely wipe. Even a factory reset does not require a complete wipe of data.
I would suggest at all times keeping a boot image of the current OS you are using.
I would also suggest keeping a TWRP.img on your computer. You can always boot from a TWRP image even if it's not the one you want to install.
That will at least get decryption and the ability to flash.
I don't flash custom ROMs, because the stock one with root does what I need. Also the fingerprint sensor is not guaranteed under custom ROMs and I need that to work.
no verify opt on most after data wipe or that brands version of it, then reboot to twrp verify is still not there because twrp will say no os installed the avb changed things every phone is different depending on their security Samsung for one
Try this guide. Read the first paragraph if you have problems with decryption.
Boot twrp
Wipe dalvik and data
Flash rom+twrp
Reboot SYSTEM!
Boot back to recovery
Factory reset
Flash gapps+magisk
Reboot and done
No data loss or PC needed...
So here's some food for thought. I read somewhere that when you install a ROM zip via TWRP it actually Installs to the Inactive Slot. And when you reboot to TWRP after reflashing the Installer it Switches Slots and then you can Flash GAPPS etc. But what if someone were to flash the ROM twice ; once to each slot? Would be noice if We can use this to Multi-Boot Two ROMs at once....
Mannan Qamar said:
So here's some food for thought. I read somewhere that when you install a ROM zip via TWRP it actually Installs to the Inactive Slot. And when you reboot to TWRP after reflashing the Installer it Switches Slots and then you can Flash GAPPS etc. But what if someone were to flash the ROM twice ; once to each slot? Would be noice if We can use this to Multi-Boot Two ROMs at once....
Click to expand...
Click to collapse
I think that question was asked in one of the threads in here "can use this to Multi-Boot Two ROMs at once" and I don't think it's possible. I'm sorry I don't remember the thread it was in. You might try Google.
It's wise to do the oos in both slots which you can switch slots without rebooting fyi because when you flash a custom ROM no matter if you switch back to a it'll flash magisk and probably gapps in the inactive slot. If you try to return the custom ROM to slot a after it flashes it will say insufficient room for gapps and such. So to me it seems this makes it a clean slate so it can flash to inactive slot. Hope that clears up why they encourage the double oos flash
Everyone, I think you have almost helped me figure out how I screwed up my 6T. I made a post needing help but this thread I believe is the answer. I wanted to install lineage16 but opted for Resurrection Remix since that dev claimed the fingerprint reader worked. To make a long story short, I flashed the latest .15 OxyOS update first, switched partitions via TWRP and flashed it again, them flashed TWRP and rebooted to recovery. Flashed Remix then TWRP again and rebooted to Remix. Now I have no room for anything in storage although it's only 25% full and my file explorer cannot access any storage not can I update apps through play store or anything. I have the latest OxyOS on my OTG flash drive as well as TWRP and magisk, but every time I find a thread on hope to do an installation, it varies and I keep coming back to this storage issue. Can someone PLEASE link me out tell me where to find the correct process to now start from the beginning and get my phone back working on the OxyOS .15 stock rom? Thank you very much and I'm glad I found this thread because it finally makes sense as to how misinformation is causing many people to have issues.
SuperUnkn0wn0ne said:
Everyone, I think you have almost helped me figure out how I screwed up my 6T. I made a post needing help but this thread I believe is the answer. I wanted to install lineage16 but opted for Resurrection Remix since that dev claimed the fingerprint reader worked. To make a long story short, I flashed the latest .15 OxyOS update first, switched partitions via TWRP and flashed it again, them flashed TWRP and rebooted to recovery. Flashed Remix then TWRP again and rebooted to Remix. Now I have no room for anything in storage although it's only 25% full and my file explorer cannot access any storage not can I update apps through play store or anything. I have the latest OxyOS on my OTG flash drive as well as TWRP and magisk, but every time I find a thread on hope to do an installation, it varies and I keep coming back to this storage issue. Can someone PLEASE link me out tell me where to find the correct process to now start from the beginning and get my phone back working on the OxyOS .15 stock rom? Thank you very much and I'm glad I found this thread because it finally makes sense as to how misinformation is causing many people to have issues.
Click to expand...
Click to collapse
You may have solved this by now, but I found that using the MSM Download Tool has enabled me to return to stock OxygenOS even after getting stuck in a boot loop. I've not been able to successfully flash RR or LineageOS however, still getting stuck in said boot loop...

flashing 10.3

Hey guys
I made a post and got no replies but have been looking into it more and remember I need adb to flash the 10.3 update, I've got all the files ready but from reading I'm confused as to how to flash via adb.
I've read you need the phone in twrp while doing flashing you need to flash the other slot blah blah blah , doesn't make sense to me...
Can anyone help me out? I've seen stuff has changed since the 10 update and I'm at a loss right now..
Thanks for any help in advance
CptUnicorns said:
Hey guys
I made a post and got no replies but have been looking into it more and remember I need adb to flash the 10.3 update, I've got all the files ready but from reading I'm confused as to how to flash via adb.
I've read you need the phone in twrp while doing flashing you need to flash the other slot blah blah blah , doesn't make sense to me...
Can anyone help me out? I've seen stuff has changed since the 10 update and I'm at a loss right now..
Thanks for any help in advance
Click to expand...
Click to collapse
You nearly never need adb to update.... Dable in some circumstances with fastboot.
Just...update. You don't specify what OS you run now, rooted , twrp etc...
Read my thread about OOS stable in Guide News section and ask there if it's not clear
Striatum_bdr said:
You nearly never need adb to update.... Dable in some circumstances with fastboot.
Just...update. You don't specify what OS you run now, rooted , twrp etc...
Read my thread about OOS stable in Guide News section and ask there if it's not clear
Click to expand...
Click to collapse
Cheers. I've read to much and watch to many videos and I've just completely confused myself buddy. I'll check your post out now someone else linked me to a proper guide I was unable to use.
I'm on havoc right, magisk 20 and twrp 3.2.3-2
CptUnicorns said:
Cheers. I've read to much and watch to many videos and I've just completely confused myself buddy. I'll check your post out now someone else linked me to a proper guide I was unable to use.
I'm on havoc right, magisk 20 and twrp 3.2.3-2
Click to expand...
Click to collapse
You're seriously late in versions of TWRP and Magisk. Update twrp with latest installer.
Then in twrp flash OOS, then twrp installer again
Reboot to recovery to switch slots
Flash again OOS and TWRP installer again
Reboot to twrp and flash Magisk then reboot system
If there's issues with encryption in recovery you can eventually use an OTG disk if you have one or ADB sideload
Last possibility is fastbooting oos ROM
Striatum_bdr said:
You're seriously late in versions of TWRP and Magisk. Update twrp with latest installer.
Then in twrp flash OOS, then twrp installer again
Reboot to recovery to switch slots
Flash again OOS and TWRP installer again
Reboot to twrp and flash Magisk then reboot system
If there's issues with encryption in recovery you can eventually use an OTG disk if you have one or ADB sideload
Last possibility is fastbooting oos ROM
Click to expand...
Click to collapse
Brilliant thanks! I've updated twrp and magisk now, had no internet so couldn't update. Do I not need to wipe the internal storage at all when flashing stock oos ontop of havoc?
And for the slot just so I know for certain;
I flash slot A with oos, twrp.
Now I reboot go to slot B, do the exact same.
Reboot again, flash new ROM , twrp/magisk.
Profit? I read you post detailing the slots, that's the part that confuses me. I'm going to have another read so I fully understand what I am actually doing instead of doing everything blind.
CptUnicorns said:
Brilliant thanks! I've updated twrp and magisk now, had no internet so couldn't update. Do I not need to wipe the internal storage at all when flashing stock oos ontop of havoc?
And for the slot just so I know for certain;
I flash slot A with oos, twrp.
Now I reboot go to slot B, do the exact same.
Reboot again, flash new ROM , twrp/magisk.
Profit? I read you post detailing the slots, that's the part that confuses me. I'm going to have another read so I fully understand what I am actually doing instead of doing everything blind.
Click to expand...
Click to collapse
Anytime you go from AOSP to OOS, or back you generally have to wipe DATA. If you don't OOS will dump you off at recovery, wipe data and then it will boot generally.
As for the slots, when flashing a ROM it always flashes to the opposite slot. So if you are currently on Slot A and you flash a ROM, it will flash to Slot B. The ROM will also overwrite install it's own recovery. So you install TWRP again if you want. Then you reboot to recovery, it will automatically switch to the new slot since you installed a new ROM. Now on the slot where the new ROM is installed, we could install Magisk or Gapps, things like that if needed. If we wanted to update the original slot (A) we would install the ROM again. As well as TWRP again. Reboot to recovery again, Magisk, etc.
ROMs install to opposite slots. After a ROM installation, rebooting to recovery will switch slots for you. Most other items install to the current slot (that is why you need to reboot before install things like Magisk, Gapps, etc). Hopefully that helps clarify things? If not ask.
OhioYJ said:
Anytime you go from AOSP to OOS, or back you generally have to wipe DATA. If you don't OOS will dump you off at recovery, wipe data and then it will boot generally.
As for the slots, when flashing a ROM it always flashes to the opposite slot. So if you are currently on Slot A and you flash a ROM, it will flash to Slot B. The ROM will also overwrite install it's own recovery. So you install TWRP again if you want. Then you reboot to recovery, it will automatically switch to the new slot since you installed a new ROM. Now on the slot where the new ROM is installed, we could install Magisk or Gapps, things like that if needed. If we wanted to update the original slot (A) we would install the ROM again. As well as TWRP again. Reboot to recovery again, Magisk, etc.
ROMs install to opposite slots. After a ROM installation, rebooting to recovery will switch slots for you. Most other items install to the current slot (that is why you need to reboot before install things like Magisk, Gapps, etc). Hopefully that helps clarify things? If not ask.
Click to expand...
Click to collapse
That does clear up things for me, I've either mis-read or not read that when on slot A you are actually flashing slot B and Visa versa.
I'll be flashing both my slots to 10.3.1 just so they're fully updated. ( A is my main)
Finally part from me, when I'm going to flash my custom ROM (havoc again) I've just got to repeat said steps but flashing havoc instead of OOS then on the last reboot, recovery and magisk?
CptUnicorns said:
Finally part from me, when I'm going to flash my custom ROM (havoc again) I've just got to repeat said steps but flashing havoc instead of OOS then on the last reboot, recovery and magisk?
Click to expand...
Click to collapse
Fair warning, I don't use Havoc. I use Lineage, here is how I install AOSP ROMs, (link) However, yes, on the final reboot would be when you install Magisk (Gapps as well if you need them). In theory recovery should already be installed, but installing it again won't hurt anything (installing recovery wipes out Magisk, so install Magisk after recovery if you do that). Remember you need Havoc on both slots (you don't want OOS on one and Havoc on another). So flash it twice.
OhioYJ said:
Fair warning, I don't use Havoc. I use Lineage, here is how I install AOSP ROMs, (link) However, yes, on the final reboot would be when you install Magisk (Gapps as well if you need them). In theory recovery should already be installed, but installing it again won't hurt anything (installing recovery wipes out Magisk, so install Magisk after recovery if you do that). Remember you need Havoc on both slots (you don't want OOS on one and Havoc on another). So flash it twice.
Click to expand...
Click to collapse
Great stuff. Thought I understood from how you explained it. I'll check that guide as well and have it to hand just incase.
OhioYJ said:
Fair warning, I don't use Havoc. I use Lineage, here is how I install AOSP ROMs, (link) However, yes, on the final reboot would be when you install Magisk (Gapps as well if you need them). In theory recovery should already be installed, but installing it again won't hurt anything (installing recovery wipes out Magisk, so install Magisk after recovery if you do that). Remember you need Havoc on both slots (you don't want OOS on one and Havoc on another). So flash it twice.
Click to expand...
Click to collapse
Something didnt want to play when I was flashing... Got to flashing gapps and magisk, gapps flash gave me a error 64 and i got magisk installed, booted, now I've got no twrp and when I use fastboot it just softbricks then restarts after about 5 minutes, I'm gonna try booting from 3.2.3-2 as that was fine and hope I can boot into recovery and just go lineage I think for something new
EDIT
So I used fastboot --set-active=a, managed to get back to twrp so now its flashed on both again. In the process of flashing lineage now, hopefully this wont chuck another error at me for gapps

OnePlus 6t Wifi Issue on custom roms

Okay so I've tried Pixel experience, lineage os , omni rom treskmod and couple of other custom android 10 roms, all stable and official and also updated ones, the wifi just simply doesn't work, wifi hotspot won't turn on either. I've tried every solution on the internet. I've even factory reset my phone using msm download tool and no luck(did this countless times).
I'm back in OOS 10.3.2 and there's no issue apparently.
At one point , i flashed a custom rom and the wifi didn't work, so I flashed OOS in the two slots and checked , the wifi works in OOS apparently, and never in custom roms.
Has anyone got this issue before and knows a solution?
How is your installation procedure?
onliner said:
How is your installation procedure?
Click to expand...
Click to collapse
I flash OOS and twrp on both slots, reboot recovery,
And then flash the rom and twrp, reboot recovery,then format data and factory reset, reboot recovery, if needed for some gapps, then reboot system
ivanthomas said:
I flash OOS and twrp on both slots, reboot recovery,
And then flash the rom and twrp, reboot recovery,then format data and factory reset, reboot recovery, if needed for some gapps, then reboot system
Click to expand...
Click to collapse
That's a lot of unnecessary steps. OOS on both slots, reboot to bootloader, boot twrp, format data and flash the custom rom, reboot bootloader, boot twrp and flash gapps, don't install twrp permanently if you are not going to install Magisk.
onliner said:
That's a lot of unnecessary steps. OOS on both slots, reboot to bootloader, boot twrp, format data and flash the custom rom, reboot bootloader, boot twrp and flash gapps, don't install twrp permanently if you are not going to install Magisk.
Click to expand...
Click to collapse
I need magisk too, I usually permanently install twrp
Also you think it's the way I'm installing at fault here? Or the rom? Or is it something wrong with my device?
ivanthomas said:
it's the way I'm installing at fault here?
Click to expand...
Click to collapse
This.
I always install roms with the procedure i said above and have never had any problems.
onliner said:
This.
I always install roms with the procedure i said above and have never had any problems.
Click to expand...
Click to collapse
Alright so got one doubt, I used OOS 10.3.2 to flash, should it be oos 10.0 only?
Thought that didn't make a difference.
I am also facing the same issue. Were you able to find any solution ?
So I found out treskmod omni rom and Paranoid android quartz 2 work perfectly , try those out, it still doesn't solve the problem in the other roms though. So not exactly a solution.

Categories

Resources