Related
Hello forum, a little question......
This is my 2nd time of owning the 3t, now the first time owning a one plus 3t, I used a CM13/marshmallow roms., They were extremely stable, but now my question is.....
Using twrp for the Oreo, I have gone through many many custom roms, Oreo and nougat, oos and lineage etc, but what's the process going back to marshmallow?
Is it just a case of flashing the rom zip like I been doing for last month or so..... or some other way? i.e downgrading something?
I'm currently on Audax 4.0
Just take a Titanium Backup of all your apps first,
Then boot into TWRP, follow the procedure for a clean flash.
Just on a curious note, why would you want to go back to MM?
And also make sure you flash the matching firmware package for the ROM you're planning to run, unless your going for OxygenOS as this does that for you.
Firmware packages can be found in a separate thread in this forum.
thes3usa said:
Just take a Titanium Backup of all your apps first,
Then boot into TWRP, follow the procedure for a clean flash.
Just on a curious note, why would you want to go back to MM?
Click to expand...
Click to collapse
Marshmallow is very stable and battery friendly.
So here's the deal, I had lost my LTE awhile back with something and saw the opportunity to fix it by taking the 8.1 soak OTA. Works wonderfully. But I do want to possibly go back a custom ROM, and have tried a few already that all work fine, except the lack of the fingerprint scanner working properly. This isn't really a big deal for now, but I'm starting a convo just to brainstorm.
Any ideas as to what's causing this, or possible solutions?
You may have to wait till the official hits the streets and the devs here tear it apart to bring that sensor up to date with the Bootloader I'm guessing. But hell, if you don't mind it. Dig in playa.
Sent from my Moto G (5S) Plus using Tapatalk
treyweez11 said:
You may have to wait till the official hits the streets and the devs here tear it apart to bring that sensor up to date with the Bootloader I'm guessing. But hell, if you don't mind it. Dig in playa.
Click to expand...
Click to collapse
That's kinda what I'm thinking, which again, I'm not worried or in a hurry, just curious.
Only whit a custom kernel
mrchman said:
That's kinda what I'm thinking, which again, I'm not worried or in a hurry, just curious.
Click to expand...
Click to collapse
In the stock version, it will only work with a custom kernel, just like in 7.1, it only works with custom kernel
guineks said:
In the stock version, it will only work with a custom kernel, just like in 7.1, it only works with custom kernel
Click to expand...
Click to collapse
Would you think any of the current custom kernels here would do the job with a custom ROM?
mrchman said:
Would you think any of the current custom kernels here would do the job with a custom ROM?
Click to expand...
Click to collapse
Using custom roms, all of which I tested, all worked using the xposed framework material, and using the magisk module corresponding to the version of android used (8.0 - 8.1)
As for stock rom 8.1, I do not know compatible kernel, for version 7.1, there is custom kernel available, and you should proceed xposed in the same way.
sorry for my english from google translate
1>Take EFS backup from oreo soak test {with 4G and VOLTE working}
2>Flash Stock NPSS26.116-61-8 in full
3>Install TWRP and custom ROM
4>Restore EFS from oreo backup
This is working perfectly for me; fingerprint (incl gestures), VOLTE both work; I'm using AOSP Extended ROM
guineks said:
Using custom roms, all of which I tested, all worked using the xposed framework material, and using the magisk module corresponding to the version of android used (8.0 - 8.1)
As for stock rom 8.1, I do not know compatible kernel, for version 7.1, there is custom kernel available, and you should proceed xposed in the same way.
sorry for my english from google translate
Click to expand...
Click to collapse
Yes, this is what I thought, but I tried several custom ROMs hoping for one to work like you say, and none did.
febin92 said:
1>Take EFS backup from oreo soak test {with 4G and VOLTE working}
2>Flash Stock NPSS26.116-61-8 in full
3>Install TWRP and custom ROM
4>Restore EFS from oreo backup
This is working perfectly for me; fingerprint (incl gestures), VOLTE both work; I'm using AOSP Extended ROM
Click to expand...
Click to collapse
Perfect! I do have a question, how can I move my twrp backup to my desktop or so, and move it back to the phone after the firmware flash so I can restore my efs?
I tried something like that before and my backup was corrupted or unrecognizable.
mrchman said:
Perfect! I do have a question, how can I move my twrp backup to my desktop or so, and move it back to the phone after the firmware flash so I can restore my efs?
I tried something like that before and my backup was corrupted or unrecognizable.
Click to expand...
Click to collapse
Just copy the entire TWRP folder from sdcard/internal memory
febin92 said:
1>Take EFS backup from oreo soak test {with 4G and VOLTE working}
2>Flash Stock NPSS26.116-61-8 in full
3>Install TWRP and custom ROM
4>Restore EFS from oreo backup
This is working perfectly for me; fingerprint (incl gestures), VOLTE both work; I'm using AOSP Extended ROM
Click to expand...
Click to collapse
It's safe to flash nougat bootloader image to oreo soak 8.1 bootloader (downgrade)?
arni664 said:
It's safe to flash nougat bootloader image to oreo soak 8.1 bootloader (downgrade)?
Click to expand...
Click to collapse
I was wondering this same thing, it doesn't give some kind of error message when downgrading?
mrchman said:
I was wondering this same thing, it doesn't give some kind of error message when downgrading?
Click to expand...
Click to collapse
Hmm, flashing the April 2018 7.1.1 firmware should give a security version downgrade if you've downgraded to Nougat from Oreo (though like yourself, I await some confirmation).
If you do see that error, I would advise against flashing or installing the June 2018 7.1.1 security update OTA, I do not know if flashing the 7.1.1 June 2018 OTA onto a device previously updated with the Oreo soak test would result in a hard brick (as the June 2018 OTA may or may not corrupt the Oreo bootloader). Be careful.
So if I were to attempt to flash it via fastboot, it would give me an error and ask for confirmation before proceeding, correct?
And if I see said error, stay away.
mrchman said:
So if I were to attempt to flash it via fastboot, it would give me an error and ask for confirmation before proceeding, correct?
And if I see said error, stay away.
Click to expand...
Click to collapse
If you flash a stock firmware, you'll see the error, but it won't ask you for confirmation. It'll just display 'security version downgrade' if your bootloader is actually newer than the firmware you're flashing. Thus, fastboot should block you from downgrading the bootloader and GPT, so you'd likely still have the Oreo bootloader on your device (unless something's changed with Motorola's enforcement of bootloader versions).
The only time you may be okay is if the subsequent OTA is the same as the newest firmware that you had on your device. E.g. if you applied the soak test OTA (OPS28.49-2), then downgraded to the April 2018 firmware, if the next OTA you use is OPS28.49-2 or a newer Oreo OTA (as you have an Oreo bootloader), then you should be okay. If you however get a Nougat OTA (like the June 2018 security patch), I'd honestly stay away unless you want to risk it. Again, I do not know if the June 2018 7.1.1 would brick your device, but you've got no way of recovering your device besides paying for an expensive motherboard replacement. If you're on the soak test, try to stay on the soak test please.
mrchman said:
Yes, this is what I thought, but I tried several custom ROMs hoping for one to work like you say, and none did.
Click to expand...
Click to collapse
After installation of the xposed framework using magisk, it may be necessary to wipe cache dalvik, and cache
guineks said:
After installation of the xposed framework using magisk, it may be necessary to wipe cache dalvik, and cache
Click to expand...
Click to collapse
I don't use xposed. I use magisk only, and I wipe cache/dalvik, and data every time I flash something.
febin92 said:
1>Take EFS backup from oreo soak test {with 4G and VOLTE working}
2>Flash Stock NPSS26.116-61-8 in full
3>Install TWRP and custom ROM
4>Restore EFS from oreo backup
This is working perfectly for me; fingerprint (incl gestures), VOLTE both work; I'm using AOSP Extended ROM
Click to expand...
Click to collapse
Question. I've restored efs before after downgrading and it's worked. I would flash the custom rom of choice and if finger print and volte didn't work I would go back and restore efs from soaktest. I'm returning from soaktest again and that method doesn't seem to work. My question is, do you restore efs before you flash custom rom or do you wait till after the rom has flashed and reboot to check first?
Sent from my XT1806 using Tapatalk
NVM clearly I can't read cause you put it all there. Thanks
So I have spent a lot of time messing around with roms and roots on nougat but I have recently restored my device to factory to use the recent official 8.0 OTA update and I now want to root the device. However with the new kernel Im not sure if I should use a different twrp or I just install the same as I used before with the modified flash command (recovery_ramdisk).
I used to use twrp-3.1.1-0-vtr.img or twrp-3.1.0-0-vtr.img, can I just flash this or do I need an oreo version?
If so what new twrp should I be using?
Jyndon said:
So I have spent a lot of time messing around with roms and roots on nougat but I have recently restored my device to factory to use the recent official 8.0 OTA update and I now want to root the device. However with the new kernel Im not sure if I should use a different twrp or I just install the same as I used before with the modified flash command (recovery_ramdisk).
I used to use twrp-3.1.1-0-vtr.img or twrp-3.1.0-0-vtr.img, can I just flash this or do I need an oreo version?
If so what new twrp should I be using?
Click to expand...
Click to collapse
Bump!
no one knows what recovery works on 8.0???
Jyndon said:
Bump!
no one knows what recovery works on 8.0???
Click to expand...
Click to collapse
I guess you should go for 3.2.1-0
I use this since @espaciosalter20 posted it and it works very good, I never noticed any issues. Data encryption works well.
After a long long wait its finally here. The oneplus 3T gets android pie. Install it and share your experience here
https://9to5google.com/2019/05/22/oneplus-3-android-pie/
I'm downloading using oxygen updater app
Anything to share? Any issues?
ptoner said:
Anything to share? Any issues?
Click to expand...
Click to collapse
Using this since past 2 days. I am completely stock with locked bootloader, unrooted and stock recovery.
No issues till now. Feels good to be back to stock oxygen OS for a change from all these custom roms.
affection788 said:
Using this since past 2 days. I am completely stock with locked bootloader, unrooted and stock recovery.
No issues till now. Feels good to be back to stock oxygen OS for a change from all these custom roms.
Click to expand...
Click to collapse
You installed it on a locked bootloader. So you factory reset the phone before updating. Or did you just flash and lose no data
Sent from my ONEPLUS A6003 using Tapatalk
ptoner said:
You installed it on a locked bootloader. So you factory reset the phone before updating. Or did you just flash and lose no data
Click to expand...
Click to collapse
I installed it on a unlocked bootloader. I was previously on Skydragon. Flashed stock OS in twrp. Lost all data in internal storage after reset.
Sounds good have been avoiding on my work phone for fear that it'll become unstable or slow. Seems thats not the issue
affection788 said:
I installed it on a unlocked bootloader. I was previously on Skydragon. Flashed stock OS in twrp. Lost all data in internal storage after reset.
Click to expand...
Click to collapse
I'm running rooted Skydragon OS with twrp and unlocked bootloader. Can I directly flash oos via twrp? Will there be any issues?
Does the stock recovery replace twrp after flashing oos?
Darkweb_182 said:
I'm running rooted Skydragon OS with twrp and unlocked bootloader. Can I directly flash oos via twrp? Will there be any issues?
Does the stock recovery replace twrp after flashing oos?
Click to expand...
Click to collapse
Yes you can flash it over twrp on skydragon and yes it will replace twrp with stock recovery. But keep in mind you will also have to format your internal storage completely because it will give a decryption failed error.
So after you flash stock and when the phone boots up it will ask you to format the internal storage so backup everything if you want to go this way.
affection788 said:
Yes you can flash it over twrp on skydragon and yes it will replace twrp with stock recovery. But keep in mind you will also have to format your internal storage completely because it will give a decryption failed error.
So after you flash stock and when the phone boots up it will ask you to format the internal storage so backup everything if you want to go this way.
Click to expand...
Click to collapse
Do you know if it will be the same if you are not encrypted, and want to stay not encrypted? Is there a way to do that without formatting (maybe using the patched firmware or theone3os)?
groshnack said:
Do you know if it will be the same if you are not encrypted, and want to stay not encrypted? Is there a way to do that without formatting (maybe using the patched firmware or theone3os)?
Click to expand...
Click to collapse
mine is decrypted and installed fine and is still decrypted,sorry wrong thread
Just installed it, the initial look seems good. The phone spent some time optimizing the apps but after that it seems smoother and much cooler looking.
Ok so if i still on android n 7.1.1 and rooted and magisk installed ohh and twrp is there too, is it going to be safe to install android pie oos 9.0.2 and to keep the root and magisk and the twrp without loosing my data?
If its safe pleas do till.
ml700 said:
Ok so if i still on android n 7.1.1 and rooted and magisk installed ohh and twrp is there too, is it going to be safe to install android pie oos 9.0.2 and to keep the root and magisk and the twrp without loosing my data?
If its safe pleas do till.
Click to expand...
Click to collapse
It is not. You will have to factory reset/format data for getting OOS Pie. That is going to delete your data, Magisk and in the process, you may have to reflash TWRP also.
I'm on open beta 39 OnePlus 3 with twrp bluspark.
So can I download the update or the full ROM? I'm a little confused as to where it is on the forums.
Then do I just flash it in twrp (wipe first I know but should I wipe data as well?) While flashing does it tell you to wipe, format or do I do that all myself?
What are the s steps?
I'm happy to wipe everything as I want to clean up my device anyway.
Thank you so much for the help.
affection788 said:
Yes you can flash it over twrp on skydragon and yes it will replace twrp with stock recovery. But keep in mind you will also have to format your internal storage completely because it will give a decryption failed error.
So after you flash stock and when the phone boots up it will ask you to format the internal storage so backup everything if you want to go this way.
Click to expand...
Click to collapse
How's the performance and battery on Oxygen OS 9. 0.2?
Can you root it?
Does Google camera work?
Darkweb_182 said:
How's the performance and battery on Oxygen OS 9. 0.2?
Can you root it?
Does Google camera work?
Click to expand...
Click to collapse
Performance is good and smooth. Good battery life as well. I haven't rooted it yet, wanna keep it stock for the time being but I am sure it can be rooted. Yes Gcam works. I am using one of the stable Arnova based Gcam.
affection788 said:
Performance is good and smooth. Good battery life as well. I haven't rooted it yet, wanna keep it stock for the time being but I am sure it can be rooted. Yes Gcam works. I am using one of the stable Arnova based Gcam.
Click to expand...
Click to collapse
I wasn't able to root Oxygen OS oreo firmware that's why I was asking
Darkweb_182 said:
How's the performance and battery on Oxygen OS 9. 0.2?
Can you root it?
Does Google camera work?
Click to expand...
Click to collapse
Battery life is not as good as Oreo OOS. I have disabled OnePlus's advanced battery optimizations, you should know.
Performance on stock kernel is mostly fine with stutters in phone app mainly. But i think that's phone app's fault. Performance with the custom kernel I am using right now is great and the ROM feels smooth.
Yes, I am running it rooted with a custom kernel.
I haven't used Google camera as I hardly use my phone's camera. Maybe once a week.
abhibnl said:
Battery life is not as good as Oreo OOS. I have disabled OnePlus's advanced battery optimizations, you should know.
Performance on stock kernel is mostly fine with stutters in phone app mainly. But i think that's phone app's fault. Performance with the custom kernel I am using right now is great and the ROM feels smooth.
Yes, I am running it rooted with a custom kernel.
I haven't used Google camera as I hardly use my phone's camera. Maybe once a week.
Click to expand...
Click to collapse
How did you root it?
Which custom kernel are you on?
Also does the bootloader get locked after flashing oos?
Darkweb_182 said:
How did you root it?
Which custom kernel are you on?
Also does the bootloader get locked after flashing oos?
Click to expand...
Click to collapse
Those are pretty basic questions actually. I assume you haven't rooted your phone in recent time?
I just flashed the magisk zip before first boot into system to keep twrp and one restart settled things and magisk is now working fine.
I am using mcd kernel build r27 but it has broken Hotspot functionality, which I don't care much about.
Why would the bootloader get locked after flashing OOS? You need to manually go into fastboot mode and manually enter some commands to lock/unlock bootloader. It can't be done via recovery afaik.
I got my device yesterday and today i have been trying to flash legion os 2.11 but i always keep getting error 7 even tried by installing global rom through mi flash tool but still got error 7 from twrp and oxfox both.
Can someone just guide me clearly on flashing roms on this k20 pro.
Currently i using global miui 11 11.0.4.0 rom but want to try other custom roms as well..
Ezio553 said:
I got my device yesterday and today i have been trying to flash legion os 2.11 but i always keep getting error 7 even tried by installing global rom through mi flash tool but still got error 7 from twrp and oxfox both.
Can someone just guide me clearly on flashing roms on this k20 pro.
Currently i using global miui 11 11.0.4.0 rom but want to try other custom roms as well..
Click to expand...
Click to collapse
Try the latest TWRP from here.
https://forum.xda-developers.com/k2...icial-twrp-xiaomi-redmi-t3944363/post79823568
If you still get the same problem, report back in this thread.
Robbo.5000 said:
Try the latest TWRP from here.
https://forum.xda-developers.com/k2...icial-twrp-xiaomi-redmi-t3944363/post79823568
If you still get the same problem, report back in this thread.
Click to expand...
Click to collapse
yeah finally the twrp 3.4 unofficial worked fine from global miui 11 rom i wiped everything and flashed indian vendor-firmware file and then flashed rom with fcrypt zip file nd worked fine...
Thanks for suggesting this file i was using youtube videos as guide and everyone was using oxfox or older twrp..
Ezio553 said:
yeah finally the twrp 3.4 unofficial worked fine from global miui 11 rom i wiped everything and flashed indian vendor-firmware file and then flashed rom with fcrypt zip file nd worked fine...
Thanks for suggesting this file i was using youtube videos as guide and everyone was using oxfox or older twrp..
Click to expand...
Click to collapse
I've got a bit more time to reply now.
OFox is really designed to be used with MIUI. The majority of it's extra features are specific to running MIUI. I would only recommend it if you decide to stick with MIUI in the long run.
The TWRP I pointed to is from the dev who maintains the official TWRP for our device. The unofficial version you've installed is identical to the official version, but with the TWRP app removed. If you intend to stick with custom ROMs, I recommend you stick with TWRP from mauronofrio.
If you prefer to have your phone encrypted, then there was no need to flash fcrypt/DFE. There are a small number of users that continue to insist that we need to disable encryption, but it is not needed.
Having the phone unencrypted does make life a little easier when flashing, but if you prefer the security and want to know about living with an encrypted phone, reply back and I'll give you more details.
Robbo.5000 said:
I've got a bit more time to reply now.
OFox is really designed to be used with MIUI. The majority of it's extra features are specific to running MIUI. I would only recommend it if you decide to stick with MIUI in the long run.
The TWRP I pointed to is from the dev who maintains the official TWRP for our device. The unofficial version you've installed is identical to the official version, but with the TWRP app removed. If you intend to stick with custom ROMs, I recommend you stick with TWRP from mauronofrio.
If you prefer to have your phone encrypted, then there was no need to flash fcrypt/DFE. There are a small number of users that continue to insist that we need to disable encryption, but it is not needed.
Having the phone unencrypted does make life a little easier when flashing, but if you prefer the security and want to know about living with an encrypted phone, reply back and I'll give you more details.
Click to expand...
Click to collapse
I tried Legion Os which is Aosp based and it installed fine but then i tried Masik X 16 which again said this isn't for your device so had to make changes in updater script then it flashed fine.
Also i would like to know about decryption of storage and would it cause any issues in flashing roms again nd again..
Ezio553 said:
I tried Legion Os which is Aosp based and it installed fine but then i tried Masik X 16 which again said this isn't for your device so had to make changes in updater script then it flashed fine.
Also i would like to know about decryption of storage and would it cause any issues in flashing roms again nd again..
Click to expand...
Click to collapse
If you want to be permanently decrypted, then you will not have any problems flashing ROMs. However, whenever you need to update the vendor and firmware, you will also need to flash the DFE script again.
If you want to be encrypted, then the best thing to do, every time you flash, is to temporarily remove encryption by removing all lockscreen security just before flashing, then once you've finished, restore encryption by adding back lockscreen security. However, if you restore MIUI, then choose to go to another custom ROM, you will need to format the data partition when flashing over MIUI, even if you've removed lockscreen security first.
Robbo.5000 said:
If you want to be permanently decrypted, then you will not have any problems flashing ROMs. However, whenever you need to update the vendor and firmware, you will also need to flash the DFE script again.
If you want to be encrypted, then the best thing to do, every time you flash, is to temporarily remove encryption by removing all lockscreen security just before flashing, then once you've finished, restore encryption by adding back lockscreen security. However, if you restore MIUI, then choose to go to another custom ROM, you will need to format the data partition when flashing over MIUI, even if you've removed lockscreen security first.
Click to expand...
Click to collapse
Ok that means going from miui to aosp & vice versa - format data needed.
So this should similarly apply to all Miui based roms like xiaomi.eu or masik x or it is just for stock miui.
Ezio553 said:
Ok that means going from miui to aosp & vice versa - format data needed.
So this should similarly apply to all Miui based roms like xiaomi.eu or masik x or it is just for stock miui.
Click to expand...
Click to collapse
As far as I know, you only need to format data when flashing over official MIUI. I don't know the details, but it is my understanding that encryption on MIUI does not follow standard practice, which is why it it's necessary to format data when flashing over MIUI. I don't believe this issue exists with MIUI based custom ROMs, or when reverting back to MIUI.
Though, there may be occasions, when flashing from one AOSP ROM to another, and the phone is encrypted, when you may get a bootloop. In this case booting to TWRP and formatting data, will fix the problem. This is why I earlier recommended temporarily removing lockscreen security, if you choose to have an encrypted phone, even though this is a rare occurrence.
Robbo.5000 said:
As far as I know, you only need to format data when flashing over official MIUI. I don't know the details, but it is my understanding that encryption on MIUI does not follow standard practice, which is why it it's necessary to format data when flashing over MIUI. I don't believe this issue exists with MIUI based custom ROMs, or when reverting back to MIUI.
Though, there may be occasions, when flashing from one AOSP ROM to another, and the phone is encrypted, when you may get a bootloop. In this case booting to TWRP and formatting data, will fix the problem. This is why I earlier recommended temporarily removing lockscreen security, if you choose to have an encrypted phone, even though this is a rare occurrence.
Click to expand...
Click to collapse
Thanks for the info.
I tried custom miui rom and well flashing dfe worked fine so i think its just for official miui.