Hello, I recently decided to flash Havoc OS on my Oneplus 6T. All went well but after realising you can't use the fingerprint reader i decided to go back to stock OOS. so i wiped everything (including internal storage because i wanted a fresh start) and tried to flash. It all appeared to work fine, no errors, but it did NOTHING, made absolutely no changes to the phone. Any ideas as what could be causing this? Ive tried multiple versions of TWRP and different Roms, even Havoc OS again, still nothing.
Use the MSM Tool to get you back to stock OS. [emoji106]
Sent from my ONEPLUS A6013 using Tapatalk
Did you flash both slots A/B?
But yeah, the MSM tool is your friend.
Sent from my ONEPLUS A6013 using Tapatalk
Related
Encryption used to be broken for OPT.
Some time passed since the last time I was looking for ROMs for the OPT - are there any ROMs (OxygenOS?) with working encryption?
Also, in CM13 there used to be a bug where you weren't able to call emergency numbers, is that still the case with CM14.1?
And last question, do I still have to use a special version of TWRP & Android 6.0 or can I use the official sources?
I also have this question
Few weeks back started testing with device encryption started with last OxygenOS 2.x.x encrypted worked fine but little laggy on some task.
The twrp I had didn't decrypted so I was stuck on this ROM, some days ago I read about official oos3.1 has encryption working... But how to flash if I didn't had a working decryption on twrp tried hybrid recovery but they didn't boot to recovery.
Reverted to official twrp-3.0.0-2oneplus2.img using fastboot and decryption of data was successful, now the flash process begins.
Backup.
Flash latest signed official OnePlus2Oxygen_14_OTA_020_all_1608262242.zip
Flashed especial supersu.zip for oos3
Flashed official twrp-3.0.2-2-oneplus2.img
Rebooted to recovery and decryption was successful.
Rebooted device... Input password for decryption couple of times some reboots, Android starting and then it booted fine.
Now I'm on encrypted oos3 coming from oos2 with a working recovery.
I'll test some N Roms today.
Sent from my ONE A2005 using Tapatalk
Tried Tesla and slim nougat have a warning about successfully decryption but data is corrupt and reset is necessary, restored oos3 and working fine
Sent from my ONE A2005 using Tapatalk
Latest halogenOS (xos) and cm14 encryption works
Sent from my ONE A2005 using Tapatalk
My first install is success but after I setting all and add fingerprint and pin code, after few reboot, it show my pin code is wrong and can't fix it, dont know where is the problem :crying:
Second time I reinstall the official 9.0.17, then when I wipe darik cache and install havoc 3.0 + twrp, when reboot to system, it is oxygen os also, why? It works at first time
So have anyone can give me the step for installation?
Based on 9.0.17 op6t international
ArlenCheng said:
My first install is success but after I setting all and add fingerprint and pin code, after few reboot, it show my pin code is wrong and can't fix it, dont know where is the problem :crying:
Second time I reinstall the official 9.0.17, then when I wipe darik cache and install havoc 3.0 + twrp, when reboot to system, it is oxygen os also, why? It works at first time
So have anyone can give me the step for installation?
Based on 9.0.17 op6t international
Click to expand...
Click to collapse
Same thing happened to me except that I didn't change the pin code that was there before I flashed it. It just went bad and then things went downhill from there.
What did you end up using?
ArlenCheng said:
Second time I reinstall the official 9.0.17, then when I wipe darik cache and install havoc 3.0 + twrp, when reboot to system, it is oxygen os also, why? It works at first time
Click to expand...
Click to collapse
iconoclasthero said:
What did you end up using?
Click to expand...
Click to collapse
Fair warning, up front, I don't use Havoc. To the OP, the 6T is a A/B device, since it booted back into OOS, it means you didn't have Havoc on both slots. Havoc was only on one, OOS on the other. Havoc failed to boot, so the Phone booted the other slot, which was OOS. Having different operating systems on the two slots generally will cause issues. Different versions is not an issue (But they should both be OOS, or both Havoc).
This is how I flash ROMs.
Hey, I have a Delaware TJ!
OhioYJ said:
Fair warning, up front, I don't use Havoc. To the OP, the 6T is a A/B device, since it booted back into OOS, it means you didn't have Havoc on both slots. Havoc was only on one, OOS on the other. Havoc failed to boot, so the Phone booted the other slot, which was OOS. Having different operating systems on the two slots generally will cause issues. Different versions is not an issue (But they should both be OOS, or both Havoc).
This is how I flash ROMs.
Click to expand...
Click to collapse
Thanks for the tip on the A/B. I was eventually walked through it by someone very helpful...and sent me some files.
Hi All
So I decided to try a custom ROM on my 6T the other day, but am having no end of trouble trying to get it to work.
To start, I was running 10.3.1 on my phone, and was Unlocked, but not Rooted, since i lost TWRP+Magisk after installing the last OS update.
So I go into fastboot, boot up the latest TWRP-Q image, and try to install magisk, but all my sdcard folders are just garbage text - can't do anything with them. I assume this is some sort of encryption thing, so i reboot to go back to the OS and see if a can disable it.
However - the phone won't boot now - just loops back into Recovery everytime. Tried everything i can think of, nothing seems to work, so I cut my losses and reboot to fastboot and flash the fastboot 10.3.1
let that start up and everything seems fine, so i reboot to fastboot, boot up TWRP again, and then "install recovery ramdisk" like the instructions say t, and then reboot to recovery. all good so far.
Next, i copy on the 10.3.1 flashable ZIP, and the PixeN OS zip. instructions there say to flash 10.3.1 followed by TWRP twice, so i do that, rebooting to recovery between each, and then install the PixeN OS zip and TWRP as well.
Reboot after that, and phone just loops back into TWRP, and all my sdcard folders are garbage again!
I've no idea what I'm doing wrong, but i've tried the same process with 3 different custom roms so far and get the same result every time.
Flash the OOS fastboot image, boot and install TWRP, install OOS flashable and TWRP twice, then the ROM zip and TWRP, and then everytime after that, my phone just loops into recovery every time - and shows the same garbled folder names.
I'm at a loss as to what's going wrong - can anyone help?
The only thing I can come up with is what they all keep saying in the topics; have you disabled the lockscreen? I haven't yet tried to flash a custom rom but that's what I am missing in your story.
You have backed up your phone?
Then reinstall OxygenOS 10.3.1 in all slots, and reinstall TWRP, and finally do factory reset and data wipe, and reboot back into TWRP. And, copy the files you want installed back on the phone (TWRP will mount the phone as a MTP storage drive on the computer, of course) and then install your favorite OS and TWRP in both slots then reboot back into recovery one final time. Finally install Magisk and gapps (if you want to), and reboot (then install any Magisk add-ons once you get back into your phone).
That's because OxygenOS' SSD encryption is a bit strict for our liking.
Sent from my ONEPLUS A6013 using Tapatalk
Dr. Mario said:
You have backed up your phone?
Then reinstall OxygenOS 10.3.1 in all slots, and reinstall TWRP, and finally do factory reset and data wipe, and reboot back into TWRP. And, copy the files you want installed back on the phone (TWRP will mount the phone as a MTP storage drive on the computer, of course) and then install your favorite OS and TWRP in both slots then reboot back into recovery one final time. Finally install Magisk and gapps (if you want to), and reboot (then install any Magisk add-ons once you get back into your phone).
That's because OxygenOS' SSD encryption is a bit strict for our liking.
Sent from my ONEPLUS A6013 using Tapatalk
Click to expand...
Click to collapse
OK thanks - that's pretty much what I did, but I'll try again following your exact steps - thanks for the help!
Be sure whatever you installed is in both slots or the SSD will keep corrupting. I had to do that on both slots so I don't keep bricking it - I have bricked the converted T-Mobile OnePlus 6T about eight to ten times figuring out why I wasn't able to install anything atop OxygenOS 10.3.1 ROM.
Sent from my ONEPLUS A6013 using Tapatalk
Got it working?
Sent from my ONEPLUS A6013 using Tapatalk
It worked! yesssss
Thanks so much - Pixen is booting up on my phone right now
Good. I am glad you got it running.
Sent from my ONEPLUS A6013 using Tapatalk
Hey all,
Are Oneplus 6T T-Mobile users able to flash custom roms?
A few months ago I tried everything to flash Xtended or Lineage, but I was getting the bootloop/reboots. I tried converting to international, among other things, but nothing worked, and if it did, it was very buggy (managed to flash MIUI, but couldn't use it as a daily driver. Updated to Android 10 after International, but a lot of weird bugs like missing emojis, etc.)
I haven't seen anyone mention or talk about it, but if you have a T-Mobile OP6T, can you still flash a custom rom?
From what I've read and I've read just about everything there is for this device as long as you covert to international and move to 10.3.4 firmware then custom roms should work at this time.
Sent from my ONEPLUS A6013 using XDA Labs
I've flashed just about everything onto mine with no issues.. Ended up going back to oos 10 just because of certain features I couldn't live without though, however i ditched the t-mobile version for the international and modified a few things with magisk and twrp. The only time I have been caught in a bootloop is when I didn't want to wipe the data partition and something didn't play nice. Or going from andriod 9 to a 10 rom or 10 back to 9 without completely wiping everything and starting with the stock 9 or 10 before flashing. Was kind of weird and this is just how i got it to work for me, after lots of retrys
cwtechshiz said:
I've flashed just about everything onto mine with no issues.. Ended up going back to oos 10 just because of certain features I couldn't live without though, however i ditched the t-mobile version for the international and modified a few things with magisk and twrp. The only time I have been caught in a bootloop is when I didn't want to wipe the data partition and something didn't play nice. Or going from andriod 9 to a 10 rom or 10 back to 9 without completely wiping everything and starting with the stock 9 or 10 before flashing. Was kind of weird and this is just how i got it to work for me, after lots of retrys
Click to expand...
Click to collapse
ya flash international then upgrade to 10 unlock bootloader
im on tmobel flash to international and now running linage works great
@oooscasianooo No issues on my end. I converted my tmo 6t to international then upgraded to 10.3.4 then flashed RR rom first attempt all booted no issues on 10.3.4 or RR at all.
How I installed rom:
boot twrp (by mauronofrio) , flash oos 10.3.4,, flash twrp installer zip, reboot recovery, flash oos 10.3.4, flash twrp installer zip, reboot recovery, flash rom, (if rom has gapps included) format data, wipe data & cache,flash twrp installer zip, reboot system.
Or with finalize zip that copies firmware to other slot for you...
Boot twrp, flash OOS 10.3.4, flash rom w/gapps included, flash twrp installer zip, flash finalize zip, format data, wipe data & cache, reboot system.
If rom does not have included gapps you just have to reboot recovery before you flash your gapps package then reboot system afterwards.. Evo X has twrp and gapps so it's even a shorter time frame for installation.. just boot twrp, flash OOS 10.3.4, flash Evo X rom, flash finalize zip, format data, wipe data & cache , reboot system.
(Edited)
hi
Does Dual Sim with the Tmo OP6T after swapping out the simtray to a dual one ?
I plan to use Lineage 17.1 with dual-sim's on a used tmo-op6t
G
ghatothkach said:
hi
Does Dual Sim with the Tmo OP6T after swapping out the simtray to a dual one ?
I plan to use Lineage 17.1 with dual-sim's on a used tmo-op6t
G
Click to expand...
Click to collapse
I was going to ask the same question, as I am also planning to install Lineage on my Tmo 6T. Did you ever find the answer?
A lot of Android 10 ROM's for Nexus 6P is using "twrp-3.3.1.0-FBE-10-angler.img". But the problem is that with that TWRP, back-up fails with an error message. I don't think it is because of the ROM, because it was the same for multiple different ROM's. Not being able to back up the storage makes it difficult to test a new ROM, because I cannot go back. Is there a newer version that fixed this, or a way to fix the problem?
yourrealking said:
A lot of Android 10 ROM's for Nexus 6P is using "twrp-3.3.1.0-FBE-10-angler.img". But the problem is that with that TWRP, back-up fails with an error message. I don't think it is because of the ROM, because it was the same for multiple different ROM's. Not being able to back up the storage makes it difficult to test a new ROM, because I cannot go back. Is there a newer version that fixed this, or a way to fix the problem?
Click to expand...
Click to collapse
No, AFAIK backups don't work on this particular TWRP, you can try other method of backup tho e.g : titanium
Sent from my angler using XDA Labs
back in 2019 i was running lineageos for a few years. one day it would no longer boot, just stuck on the google logo. i tried to install a twrp backup with the same result. i re installed lineage which loaded and booted. phew! right-WRONG, after several reboots it returned to logo stall. i put the phone aside and tried several other roms over time, same result, boots several times and then logo stalls. i was looking for a phone to leave on my bicycle with the mapmyride app installed. i did a factory install, which loaded booted and after a few boots asks for the encryption password. is there a workaround for this condition?
dr1445 said:
back in 2019 i was running lineageos for a few years. one day it would no longer boot, just stuck on the google logo. i tried to install a twrp backup with the same result. i re installed lineage which loaded and booted. phew! right-WRONG, after several reboots it returned to logo stall. i put the phone aside and tried several other roms over time, same result, boots several times and then logo stalls. i was looking for a phone to leave on my bicycle with the mapmyride app installed. i did a factory install, which loaded booted and after a few boots asks for the encryption password. is there a workaround for this condition?
Click to expand...
Click to collapse
Bro, thats BLOD! flash patched boot.img and it'll boot
Sent from my angler using XDA Labs
boot.img
Ata Ur Rehman said:
Bro, thats BLOD! flash patched boot.img and it'll boot
Sent from my angler using XDA Labs
Click to expand...
Click to collapse
hi; i searched for the patched boot.img, all i could find was the twrp with core 4 and the workaround. all i can find is the last factory boot.img, can you provide a link to the patch? many thanks for your time.