3T
Root, with last twrp, with a pie custom rom, Havoc Pie.
Everything normal, then, my wifi option was not switching on.
I tried do flash another rom's, many, same issue. Then I tried to flash stock and don't boot.
Tried the metod of unbrick and a android marshmallow version of stock boot. Tried install a new stock, and bootloop. Tried flash with ADS sideload and bootloop,
nor the white ball is spinning, only a red dot of the logo.
I can flash other rom's, my mac address was 02: 00: 00: 00: 00: 00. Maybe that's why the wi-fi does not activate anymore. And install the stock to see if it returns to normal, does not start, happening what I described
Michael R said:
3T
Root, with last twrp, with a pie custom rom, Havoc Pie.
Everything normal, then, my wifi option was not switching on.
I tried do flash another rom's, many, same issue. Then I tried to flash stock and don't boot.
Tried the metod of unbrick and a android marshmallow version of stock boot. Tried install a new stock, and bootloop. Tried flash with ADS sideload and bootloop,
nor the white ball is spinning, only a red dot of the logo.
I can flash other rom's, my mac address was 02: 00: 00: 00: 00: 00. Maybe that's why the wi-fi does not activate anymore. And install the stock to see if it returns to normal, does not start, happening what I described
Click to expand...
Click to collapse
Hello, when you have twrp installed, everything is ok. don´t panic.
You have Havoc Pie on the phone, right? Good, when you want to install sstock Rom, you "downgrade" the phone now.
Here we go: go to twrp, make a factory reset, wipe everything, then install the stock rom and make a clean install - done.
Good luck, reinipic:fingers-crossed:
reinipic said:
Hello, when you have twrp installed, everything is ok. don´t panic.
You have Havoc Pie on the phone, right? Good, when you want to install sstock Rom, you "downgrade" the phone now.
Here we go: go to twrp, make a factory reset, wipe everything, then install the stock rom and make a clean install - done.
Good luck, reinipic:fingers-crossed:
Click to expand...
Click to collapse
I can install any rom except the stock. And this problem is occurring since wi-fi no longer activates, and I realized that the MAC address was also modified (not by me)
I already tried to install the Stock, the Beta, already tried with TWRP and the ADB. After the flash, recovery hangs, goes pro boot and it does not start. Get bugged on OnePlus's red ball.
With other rom's the boot is normal. Using the unbrick process, the Marshmallow stock who comes in the package installs, until it starts normal. But when you try to install the most current stock, it will not start. And I'm using the most current blu_spark twrp.
Another strange thing is that even installing, even partially, passing the latest firmware, Wi-Fi does not activate at all.
Michael R said:
I can install any rom except the stock. And this problem is occurring since wi-fi no longer activates, and I realized that the MAC address was also modified (not by me)
I already tried to install the Stock, the Beta, already tried with TWRP and the ADB. After the flash, recovery hangs, goes pro boot and it does not start. Get bugged on OnePlus's red ball.
With other rom's the boot is normal. Using the unbrick process, the Marshmallow stock who comes in the package installs, until it starts normal. But when you try to install the most current stock, it will not start. And I'm using the most current blu_spark twrp.
Another strange thing is that even installing, even partially, passing the latest firmware, Wi-Fi does not activate at all.
Click to expand...
Click to collapse
Try using newest official twrp for our device from here: https://eu.dl.twrp.me/oneplus3/
It could help perhaps. I just did today unbrick process and after flashing MM stock you need to start it, and allow OEM unlock from developer settings, and then unlock bootloader (this is a must because the process of unbricking lock the BL), flash twrp from link, and finally flash stock rom (I flashed this one: https://forum.xda-developers.com/oneplus-3t/development/rom-theone3tos-v1-0-t3730932 and it works fine).
Try it and report
-CRO-Maher said:
Try using newest official twrp for our device from here: https://eu.dl.twrp.me/oneplus3/
It could help perhaps. I just did today unbrick process and after flashing MM stock you need to start it, and allow OEM unlock from developer settings, and then unlock bootloader (this is a must because the process of unbricking lock the BL), flash twrp from link, and finally flash stock rom (I flashed this one: https://forum.xda-developers.com/oneplus-3t/development/rom-theone3tos-v1-0-t3730932 and it works fine).
Try it and report
Click to expand...
Click to collapse
I'll try follow this steps. Thank you for the link. Soon I'll report.
Michael R said:
3T
Root, with last twrp, with a pie custom rom, Havoc Pie.
Everything normal, then, my wifi option was not switching on.
I tried do flash another rom's, many, same issue. Then I tried to flash stock and don't boot.
Tried the metod of unbrick and a android marshmallow version of stock boot. Tried install a new stock, and bootloop. Tried flash with ADS sideload and bootloop,
nor the white ball is spinning, only a red dot of the logo.
I can flash other rom's, my mac address was 02: 00: 00: 00: 00: 00. Maybe that's why the wi-fi does not activate anymore. And install the stock to see if it returns to normal, does not start, happening what I described
Click to expand...
Click to collapse
wen u switch wifi toggle you will get sometime that mac id i.e 02: 00: 00: 00: 00: 00. , after toggle wifi switch u get desired mac address.
uttam.ace said:
wen u switch wifi toggle you will get sometime that mac id i.e 02: 00: 00: 00: 00: 00. , after toggle wifi switch u get desired mac address.
Click to expand...
Click to collapse
The wifi does not even activate. Automatically, the switch pulls off
-CRO-Maher said:
Try using newest official twrp for our device from here: https://eu.dl.twrp.me/oneplus3/
It could help perhaps. I just did today unbrick process and after flashing MM stock you need to start it, and allow OEM unlock from developer settings, and then unlock bootloader (this is a must because the process of unbricking lock the BL), flash twrp from link, and finally flash stock rom (I flashed this one: https://forum.xda-developers.com/oneplus-3t/development/rom-theone3tos-v1-0-t3730932 and it works fine).
Try it and report
Click to expand...
Click to collapse
I tried, I followed step by step. When I installed the rom in the twrp, the phone vibrated for almost 5 seconds without stopping and nothing else after that.
Michael R said:
I tried, I followed step by step. When I installed the rom in the twrp, the phone vibrated for almost 5 seconds without stopping and nothing else after that.
Click to expand...
Click to collapse
Did you update your OxygenOS to the latest version? I updated my firmware cause I got error 7 from TWRP. If you're TWRP is the latest version: https://dl.twrp.me/oneplus3/ then I would look at your firmware: https://www.oneplus.com/support/softwareupgrade/details?code=6
Once you download that, connect your phone to your PC with USB debugging enabled on your phone. Make sure you have ADB installed: https://www.xda-developers.com/install-adb-windows-macos-linux/
Then open a command prompt (type CMD in "Search Programs and Files") and type without quotes "adb sideload filename.whatever" where "filename.whatever" is the name and extension of the OxygenOS file. Then do the same command again with the ROM file. That's how I got my ROM on my phone after I had some problems with decryption.
Related
Hi all,
Recently I got a P10 (VTR-L09C432) which I unlocked and flashed with TWRP-3.1.1-0-VTR. I made a full backup on the SD card and tried to run Lineage 15.1, unfortunatly this didnt work so I had to revert back to the backup. Sadly this isnt working properly either, the phone boots to Nougat but keeps telling me to setup my phone. When the phone lets me choose if I want to go for a fresh install or login with an existing account the setup process just restarts.
Weird thing is that the phone has gone back to the stock recovery without flashing the recovery, this shouldnt be in the TWRP backup, right? I cant seem to flash it back to TWRP either. When I flash it with fastboot and try to go into TWRP recovery it just loads Emui.
What to do?
Thanks!
Try doing a factory reset in the EMUI recovery and see if that fixes your set up problem
SeanTho said:
Try doing a factory reset in the EMUI recovery and see if that fixes your set up problem
Click to expand...
Click to collapse
Unfortunatly that is impossible, when I boot EMUI the only option I have is to 'download update and recover' or to reboot. The download option fails every time, even with connected WIFI.
This morning however I got the device to load TWRP again. Dont ask me why, but it seems to work now. I could load another ROM, but which?
88-BLUE-88 said:
Unfortunatly that is impossible, when I boot EMUI the only option I have is to 'download update and recover' or to reboot. The download option fails every time, even with connected WIFI.
This morning however I got the device to load TWRP again. Dont ask me why, but it seems to work now. I could load another ROM, but which?
Click to expand...
Click to collapse
You can check out the custom room section of the P10 as there are some stock roms that have added customization but I think they require you to rebrand to a certain model. You can always try another Treble rom such as RR. It's probably the most stable Treble rom for the P10. If you are to go along the lines of RR make sure your phone is on Oreo firmware and once the system.img has been flashed to do a factory reset without wilign the system so it boots. Hope this helps ?
I am kind of lost now. Tried AICP, but this gives me errors on flashing. (Failed to mount /system: No such volume).
I tried to go back to my recovery image again (that I made with TWRP), but no cigar. Same weird problem with looping through the initial phone cq. account setup.
I guess I am missing something here. =)
Allright, just installed Nougat (from this source) and now this seems to be working allright. Will make a new backup and try to go from there.
Hi.
A while ago I installed lineage 14 on my p9 because my son who uses the phone did want to have an experience a little closer to aosp.
Today he wanted to go back to stock emui. I thought I use the dload method. But I couldn't enter the recovery. Every time I ended up back at twrp.
Then I installed magic rainbow 4. The installation went OK but not all apps where available. Camera etc not installed.
Again I tried to use de dload method but still the same issue.
The I tried to reinstall lineage 14. Because in magic rainbow I couldn't enter the the developers option to activate oem unlock or USB debugging.
I thought that the problem for dload was an frp lock. In bootloader there is everything unlocked. But I wanted to check it.
After reinstall of lineage I wanted to reboot but I always ended up in TWRP....
I seems that there wasn't a system installed?
Then I found a tutorial that said to wipe all partitions and manually flash boot.img and system.img
But the flashing failed of both img.
So now I have a phone with all wiped....
Anyone an idea about this?
curtricias said:
Hi.
A while ago I installed lineage 14 on my p9 because my son who uses the phone did want to have an experience a little closer to aosp.
Today he wanted to go back to stock emui. I thought I use the dload method. But I couldn't enter the recovery. Every time I ended up back at twrp.
Then I installed magic rainbow 4. The installation went OK but not all apps where available. Camera etc not installed.
Again I tried to use de dload method but still the same issue.
The I tried to reinstall lineage 14. Because in magic rainbow I couldn't enter the the developers option to activate oem unlock or USB debugging.
I thought that the problem for dload was an frp lock. In bootloader there is everything unlocked. But I wanted to check it.
After reinstall of lineage I wanted to reboot but I always ended up in TWRP....
I seems that there wasn't a system installed?
Then I found a tutorial that said to wipe all partitions and manually flash boot.img and system.img
But the flashing failed of both img.
So now I have a phone with all wiped....
Anyone an idea about this?
Click to expand...
Click to collapse
If you were installing MR v4, didn't you read also the OP post #3 about HWOTA method for going back to stock from custom Nougat ROMs
https://forum.xda-developers.com/showpost.php?p=75787156&postcount=3
zgfg said:
If you were installing MR v4, didn't you read also the OP post #3 with HWOTA method for going back to stock from custom Nougat ROMs
https://forum.xda-developers.com/showpost.php?p=75787156&postcount=3
Click to expand...
Click to collapse
Forgot to mention. Yes. I tried that but software install failed.
curtricias said:
Forgot to mention. Yes. I tried that but software install failed.
Click to expand...
Click to collapse
You had to use the proper TWRP (from MR v4 thread) and flash by HWOTA the same stock you were before going to custom.
You can try HWOTA7
https://forum.xda-developers.com/p9/development/rebrand-update-tool-hwota7-p9-eva-t3820849
or even HuRUpdater
https://forum.xda-developers.com/ho...lash-official-firmware-recovery-t3769279/amp/
zgfg said:
You had to use the proper TWRP (from MR v4 thread) and flash by HWOTA the same stock you were before going to custom.
You can try HWOTA7
https://forum.xda-developers.com/p9/development/rebrand-update-tool-hwota7-p9-eva-t3820849
Already tried this to. Script ended with more than one device emulator.
or even HuRUpdater
https://forum.xda-developers.com/ho...lash-official-firmware-recovery-t3769279/amp/
Click to expand...
Click to collapse
And tried this also. Software installation failed.
I tried to install magic rainbow 4 again and it worked!
First I flashed TWRP from the MR4 topic.
But...
still various apps are missing. When I want to enter developer settings I automatically go back to home screen.
What can I do from there.
@Tecalote I'm gonna quote you here. Maybe you have an idea?
FYI
I managed to solve the problem!
Started over again.
In TWRP full wiped.
Tried HuRUpdater again. Flashed successfully the latest stock EMUi (C432-B505).
Factory reset in stock recovery.
Complete setup.
Rooted with latest Magisk (patched boot.img)
Hi guys, I have a OnePlus 3T which I have been using since 2017 and it worked perfectly. But a few months ago it updated to Android 9 Pie and ever since then my phone has gotten far slower, keeps hanging on certain things and sometimes I can't even make a call directly from contacts. I have to click call then it seems like the call is starting up but then just freezes and cuts off. Afterward, I have to go to call history and make the call again and it works.
I waited a while to see if a newer update will fix this slowdown and issues but after 2 or 3 more Pie updates it's still unresponsive and crashes the dialer. So I just want to know if anyone can tell me where I can find a ROM for final Oreo version that is compatible with OnePlus 3T and the best way I can downgrade.
I tried following a guide already but I ran into issues simply flashing TWRP. I Installed the ABD drivers, unlocked bootloader and rebooted.
Then in fastboot mode, I tried to flash it and it seemed to work because in the ABD PowerShell windows it said "Okay" after I used the cmd to flash.
But when I reboot and go into recovery, I still have the default recovery options.
This is the first time I am trying to flash my phone and I'm only doing it because it went from a phone that ran super smooth to one that is barely usable...I mean Contacts and the actual Phone apps are hanging and crashing. It even crashes when I try to answer incoming calls sometimes. The phone keeps ringing and I get a message saying the program is unresponsive, giving me options to "wait" or "close"
TT-Twister said:
...
I tried following a guide already but I ran into issues simply flashing TWRP. I Installed the ABD drivers, unlocked bootloader and rebooted.
Then in fastboot mode, I tried to flash it and it seemed to work because in the ABD PowerShell windows it said "Okay" after I used the cmd to flash.
But when I reboot and go into recovery, I still have the default recovery options.
...
Click to expand...
Click to collapse
Something you need to know: stock OOS will always reinstall the stock recovery when the phone boots into system.
So if you
1. Booted into fastboot
2. Flashed TWRP
3. Booted your phone
4. Booted into recovery
then TWRP got overwritten in step 3.
What you should have done after flashing TWRP was boot into recovery directly (use the volume keys while in fastboot mode to select that option then press the power button).
Sent from my OnePlus 3T using XDA Labs
BillGoss said:
Something you need to know: stock OOS will always reinstall the stock recovery when the phone boots into system.
So if you
1. Booted into fastboot
2. Flashed TWRP
3. Booted your phone
4. Booted into recovery
then TWRP got overwritten in step 3.
What you should have done after flashing TWRP was boot into recovery directly (use the volume keys while in fastboot mode to select that option then press the power button).
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
Thanks for the reply...and it got me a step further. But when it got to TWRP it starts at "Mount Decrypt Data" I assumed this was my phone pin...and when I tried that it opens up a cmd window which said "unable to mount storage" then says "updating partition details" but it sort of freezes then the phone turns off and powers on with the notification LED being "white" but the screen is black and the phone just stays like this for ages. Only thing I could do is hold down the power button to power down the phone and restart it. At least TWRP seems to have flashed because even when I go into recovery from the boot menu it goes to TWRP.
TT-Twister said:
Thanks for the reply...and it got me a step further. But when it got to TWRP it starts at "Mount Decrypt Data" I assumed this was my phone pin...and when I tried that it opens up a cmd window which said "unable to mount storage" then says "updating partition details" but it sort of freezes then the phone turns off and powers on with the notification LED being "white" but the screen is black and the phone just stays like this for ages. Only thing I could do is hold down the power button to power down the phone and restart it. At least TWRP seems to have flashed because even when I go into recovery from the boot menu it goes to TWRP.
Click to expand...
Click to collapse
Personally I would not downgrade to Oreo. Pie works fine. The problems your were having could have probably been solved by simply doing a factory reset.
Since you've unlocked your bootloader, you've effectively done a factory reset. So try just booting the system and set up your phone again. It'll probably be fine now that you're doing a clean install.
Sent from my OnePlus 3T using XDA Labs
BillGoss said:
Personally I would not downgrade to Oreo. Pie works fine. The problems your were having could have probably been solved by simply doing a factory reset.
Since you've unlocked your bootloader, you've effectively done a factory reset. So try just booting the system and set up your phone again. It'll probably be fine now that you're doing a clean install.
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
Yea...I have done several factory resets in the process of unlocking the bootloader and flashing twrp. So it didn't fix the issue. The main issue is linked to "contacts" which basically freezes most times I try to make a call. It makes the call but crashes contacts and the "Phone" app. Which is stupid because that's the main purpose of a phone.
Also, another key reason for wanting to downgrade to Oreo is the ability to record phone calls. This is very useful to me and those apps stopped working with Pie I think.
TT-Twister said:
Yea...I have done several factory resets in the process of unlocking the bootloader and flashing twrp. So it didn't fix the issue. The main issue is linked to "contacts" which basically freezes most times I try to make a call. It makes the call but crashes contacts and the "Phone" app. Which is stupid because that's the main purpose of a phone.
Also, another key reason for wanting to downgrade to Oreo is the ability to record phone calls. This is very useful to me and those apps stopped working with Pie I think.
Click to expand...
Click to collapse
If I was to go back to Oreo I would:
Download the full Oreo OOS ROM and backup everything you need onto your PC. Then in TWRP:
1. Do a factory reset
2. Flash OOS 5.0.4
3. Wipe>format data (to get rid of encryption)
4. Reboot system, which will also encrypt the data again and replace TWRP with the stock recovery
5. Use ADB to restore the data on your phone
6. Flash TWRP and restore your Oero backup.
Sent from my OnePlus 3T using XDA Labs
BillGoss said:
If I was to go back to Oreo I would:
Download the full Oreo OOS ROM and backup everything you need onto your PC. Then in TWRP:
1. Do a factory reset
2. Flash OOS 5.0.4
3. Wipe>format data (to get rid of encryption)
4. Reboot system, which will also encrypt the data again and replace TWRP with the stock recovery
5. Use ADB to restore the data on your phone
6. Flash TWRP and restore your Oero backup.
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
Did you read what I said? I did what you said and manage to boot into TWRP but I told you the issue about encryption and my phone freezing.
So I don't know how I'm supposed to flash any OS if I can't get TWRP to work in the first place.
TT-Twister said:
Did you read what I said? I did what you said and manage to boot into TWRP but I told you the issue about encryption and my phone freezing.
So I don't know how I'm supposed to flash any OS if I can't get TWRP to work in the first place.
Click to expand...
Click to collapse
In that case, I hope you've got backups on your PC because you're going to have to format your phone. TWRP>Wipe>Format data. You'll need to cancel out of the password screen to do the wipe.
Then reboot into recovery and use ADB to copy the files to your phone and flash Oreo.
Sent from my OnePlus 3T using XDA Labs
BillGoss said:
In that case, I hope you've got backups on your PC because you're going to have to format your phone. TWRP>Wipe>Format data. You'll need to cancel out of the password screen to do the wipe.
Then reboot into recovery and use ADB to copy the files to your phone and flash Oreo.
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
I got my data backed up using some software called "dr.fone" but how do I use ADB to copy files to the phone?
As I said at the start, this is literally the first time I'm trying to do this. I never flashed my phone before and never used ADB or TWRP before.
I'm literally just following instructions in guides and forums. So please don't assume I know how all of this works.
Hmm. I've been thinking about your problem and I have some questions/suggestions.
1. What version of TWRP are you using? (I would use the latest one from https://dl.twrp.me/oneplus3/ )
2. Can you boot your phone normally? If so, try setting a new password and say Yes for secure start up. Then verify that when you reboot you are prompted for a password (Starting Android screen, not just the lock screen). If that works, boot into TWRP. Does the new password work?
BillGoss said:
Hmm. I've been thinking about your problem and I have some questions/suggestions.
1. What version of TWRP are you using? (I would use the latest one from https://dl.twrp.me/oneplus3/ )
2. Can you boot your phone normally? If so, try setting a new password and say Yes for secure start up. Then verify that when you reboot you are prompted for a password (Starting Android screen, not just the lock screen). If that works, boot into TWRP. Does the new password work?
Click to expand...
Click to collapse
I'm using the latest version of TWRP (top one on that list)
I can boot the phone, and it works obviously. But I was having serious issues and slowdowns after updating to Pie.
Changing the password didn't work...but doing what you said before and formatting the device and rebooting into TWRP seems to have worked.
It's recognizing the storage and I can choose zip files to install.
Do you know the last version of Oreo that was compatible with the 3T? I think it's either 5.0.8 but they may have released 5.1.8 for it...I can't remember and can't seem to find the info anywhere.
TT-Twister said:
I'm using the latest version of TWRP (top one on that list)
I can boot the phone, and it works obviously. But I was having serious issues and slowdowns after updating to Pie.
Changing the password didn't work...but doing what you said before and formatting the device and rebooting into TWRP seems to have worked.
It's recognizing the storage and I can choose zip files to install.
Do you know the last version of Oreo that was compatible with the 3T? I think it's either 5.0.8 but they may have released 5.1.8 for it...I can't remember and can't seem to find the info anywhere.
Click to expand...
Click to collapse
Glad you can now get into TWRP.
5.0.8 was the last stable Oreo version (I never used betas).
Sent from my OnePlus 3T using XDA Labs
I would second the suggestion that you don't downgrade to Oreo. I was having the same issues you mentioned on Pie, but have since sorted them out. Pie is now running very nicely for me.
A good deep cleaning did it for me, even after a previous factory reset had failed to fix it.
ataft said:
I would second the suggestion that you don't downgrade to Oreo. I was having the same issues you mentioned on Pie, but have since sorted them out. Pie is now running very nicely for me.
A good deep cleaning did it for me, even after a previous factory reset had failed to fix it.
Click to expand...
Click to collapse
Well, it seems like downgrading to Oreo is going to be a huge task. Because my research I need to flash some stock firmware before being able to flash Oreo again.
Which I tried, but for some reason, it's not flashing it. So now I need to download the latest stable version of Pie for 3T again?
Can any of you tell me what version that is?
TT-Twister said:
Well, it seems like downgrading to Oreo is going to be a huge task. Because my research I need to flash some stock firmware before being able to flash Oreo again.
Which I tried, but for some reason, it's not flashing it. So now I need to download the latest stable version of Pie for 3T again?
Can any of you tell me what version that is?
Click to expand...
Click to collapse
What is the latest stable of Pie? 9.0.5
But Bill has already given you the steps for downgrading if you want.
TT-Twister said:
Well, it seems like downgrading to Oreo is going to be a huge task. Because my research I need to flash some stock firmware before being able to flash Oreo again.
Which I tried, but for some reason, it's not flashing it. So now I need to download the latest stable version of Pie for 3T again?
Can any of you tell me what version that is?
Click to expand...
Click to collapse
I decided to test downgrading to Oreo from Pie. And I learnt that it's basically the same process as upgrading from Oreo to Pie. Since my phone is unlocked and encrypted I had to remove the encryption using TWRP>Wipe>Format data: yes when going from Oreo to Pie and the same when going from Pie to Oreo.
So my process to downgrade is:
- Backup everything I want to keep from my phone.
- Flash OOS 5.0.8 full stock zip in TWRP. This completely overwrites the 9.0.5 firmware and system.
- Remove encryption: TWRP>Wipe>Format data: yes. (You'll lose everything on your phone)
- Reboot system (it re-encrypts the phone and replaces TWRP with stock recovery).
- Restored phone data, and so on.
Sent from my OnePlus 3T using XDA Labs
One more thing that I'd forgotten about: you can run OOS Oreo on the Pie firmware. So if you still have the Pie firmware installed, just restore an Oreo backup and you should be ok.
See point at the end of https://forum.xda-developers.com/on...ageos-16-0-oneplus-3-3t-t3866517/post79378447
Sent from my OnePlus 3T using XDA Labs
BillGoss said:
I decided to test downgrading to Oreo from Pie. And I learnt that it's basically the same process as upgrading from Oreo to Pie. Since my phone is unlocked and encrypted I had to remove the encryption using TWRP>Wipe>Format data: yes when going from Oreo to Pie and the same when going from Pie to Oreo.
So my process to downgrade is:
- Backup everything I want to keep from my phone.
- Flash OOS 5.0.8 full stock zip in TWRP. This completely overwrites the 9.0.5 firmware and system.
- Remove encryption: TWRP>Wipe>Format data: yes. (You'll lose everything on your phone)
- Reboot system (it re-encrypts the phone and replaces TWRP with stock recovery).
- Restored phone data, and so on.
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
Do you have a link for the OOS 5.0.8 full stock zip with the firmware?
I downloaded files from these links:
https://www.getdroidtips.com/oxygenos-5-0-8-oneplus-3-3t/
https://www.androidjungles.com/oneplus-3t-flash-file/
But neither of them are flashing in TWRP.
TT-Twister said:
Do you have a link for the OOS 5.0.8 full stock zip with the firmware?
I downloaded it from here https://www.getdroidtips.com/oxygenos-5-0-8-oneplus-3-3t/ but it's not flashing in TWRP.
Click to expand...
Click to collapse
https://otafsg1.h2os.com/patch/amaz...n_28_OTA_070_all_1812060053_d75f3be1db2be.zip
Sent from my OnePlus 3T using XDA Labs
ataft said:
I would second the suggestion that you don't downgrade to Oreo. I was having the same issues you mentioned on Pie, but have since sorted them out. Pie is now running very nicely for me.
A good deep cleaning did it for me, even after a previous factory reset had failed to fix it.
Click to expand...
Click to collapse
What do you mean by deep cleaning?. I tried hard reset but after using apps phone again became dead slow.
I unlocked the bootloader using fastboot.
Then i erased previous recovery.
Flashed TWRP.
Rebooted System.
Rebooted Recovery.
Installed Custom ROM (RR & ViperOS even AOSPEx)
After that i can't set lockscreen.
Tried installing fingerSecurity App. It says no fingerprint sensor.
Settings crash as i try to register pattern , pin or password.
I went back to complete stock and then did same process over and over with every ROM but none worked. While i'm on stock both finger and lockscreem works perfectly.
my device is xt1771.
Tried following alot of tutorials online which made me delete alot of internal files on data partition related to lockscreen but none worked.
I would be really thankful for your assistance.
Flash stock again with sp flashtools and dont get any update, then repeat all proccess (unlock bootloader, flash twrp and custom)
This is a Common bug, dont worry, doing this fp and lockscreen will work
PaleF4CE said:
Flash stock again with sp flashtools and dont get any update, then repeat all proccess (unlock bootloader, flash twrp and custom)
This is a Common bug, dont worry, doing this fp and lockscreen will work
Click to expand...
Click to collapse
Something funny happened. After SP Flash Tool flashing thing i got unknown baseband error(unknown nvram) issue. tried solving it for hours but couldn't achieve much because the tutorial on moto e4 plus is damn difficult to follow. i thought let's just install custom rom and see what happens. The unknown baseband and fingerprint issue both got away. But after a reboot i got the issue back. now i'm trying to write imei using mkt tools. let's see where it gets me. Thanks for helping buddy.
So i recently got the prompt to install zui 11.5 on my phone and got it installed relatively fine. Download took around 15 minutes and required 1 gb of storage. After downloading, i installed the OTA update and my phone did its thing. After around 3 minutes, the installation was done and my phone is now stuck at the lenovo logo. I have been waiting for around 30 minutes but it does not boot up properly yet? I have a CN rom and is the not a custom rom whatsoever so im not sure what caused the problem. Any help would be greatly appreciated.:crying:
Before the update, does your phone show a warning screen? If so, the bootloader was unlocked previously.
You might need to unlock the bootloader again as some OTAs relock the bootloader. However if you unlock the bootloader, it will factory reset the phone.
No i did not see any warning before. My phone previously came with an unlocked bootloader and had a global rom. I flashed a CN rom to receive OTA and it worked fine as I was able to receive updates. But when I received the Zui 11.5 update, it told me that my bootloader was locked whenever i booted into fastboot.
batgoon said:
My phone previously came with an unlocked bootloader and had a global rom. I flashed a CN rom to receive OTA and it worked fine as I was able to receive updates. But when I received the Zui 11.5 update, it told me that my bootloader was locked whenever i booted into fastboot.
Click to expand...
Click to collapse
Expected behavior, this is also reported in the 4PDA thread. That's why the update from 11.1.021 to 11.5.xxx relocks bootloader.
5.134/5.141/5.223 can be done directly from 1.021, while 1.021 -> 5.141 -> 5.182 -> 5.199 can be done sequentially. But all will have the effect of relocking the bootloader.
Well what would do you suggest that I do ? Sorry I am not much of a techie or know that much when it comes to these sort of things. I was able to remove the bootloop by flashing the stock firmware again thus i am back on Zui 10.5. Currently not receiving any updates for Zui 11 or Zui 11.5 as it shows there are no updates available.
batgoon said:
Well what would do you suggest that I do ? Sorry I am not much of a techie or know that much when it comes to these sort of things. I was able to remove the bootloop by flashing the stock firmware again thus i am back on Zui 10.5. Currently not receiving any updates for Zui 11 or Zui 11.5 as it shows there are no updates available.
Click to expand...
Click to collapse
Do you have a solution?
batgoon said:
Well what would do you suggest that I do ? Sorry I am not much of a techie or know that much when it comes to these sort of things. I was able to remove the bootloop by flashing the stock firmware again thus i am back on Zui 10.5. Currently not receiving any updates for Zui 11 or Zui 11.5 as it shows there are no updates available.
Click to expand...
Click to collapse
From 4PDA: http://fmdl.ota.lenovomm.com/dls/v6...145.1_Q_ZUI_11.5.223_ST_200401_WC1D538160.zip
Haven't tested so am not sure if stock recovery would allow this. I myself am still on 5.182 because I don't want an update to relock the bootloader and I don't want to reformat my phone when I unlock the bootloader again.
I have finally fixed the problem. With the file you have provided, I flashed the Zui 11 and got my phone to the said version. After flashing the update, my phone got a prompt for Zui 11.5 again and I proceeded to install it again. The update now works and my phone booted in around 2 minutes. I am now in Zui 11.5.223 ST. Thank you so much for you help:laugh::good:
How the steps you done?
How the Steps you've done already?
batgoon said:
I have finally fixed the problem. With the file you have provided, I flashed the Zui 11 and got my phone to the said version. After flashing the update, my phone got a prompt for Zui 11.5 again and I proceeded to install it again. The update now works and my phone booted in around 2 minutes. I am now in Zui 11.5.223 ST. Thank you so much for you help:laugh::good:
Click to expand...
Click to collapse
I just flashed the Zui 11 rom onto my phone and got the update from the Zui Update. ( Settings)
I followed the steps stated in here but instead of using the stock firmware, I used the update that was provided above
https://forum.xda-developers.com/z5-pro-gt/how-to/guide-unbrick-guide-lenovo-z5-pro-gt-t3915945
Ps: If you're not sure with how this work, I would advise against it as it may completely brick your phone if you do not know what you are doing.
I just flashed the Zui 11 rom onto my phone and got the update from the Zui Update. ( Settings)
I followed the steps stated in here but instead of using the stock firmware, I used the update that was provided above
https://forum.xda-developers.com/z5-pro-gt/how-to/guide-unbrick-guide-lenovo-z5-pro-gt-t3915945
Ps: If you're not sure with how this work, I would advise against it as it may completely brick your phone if you do not know what you are doing (E.G like flashing the wrong rom or unsupported rom)
Try so many times but not helped
I try so many times using thats tutorial but I stucked in Sahara Fail,
How to resolve this? I have tried so many times.
batgoon said:
I just flashed the Zui 11 rom onto my phone and got the update from the Zui Update. ( Settings)
I followed the steps stated in here but instead of using the stock firmware, I used the update that was provided above
https://forum.xda-developers.com/z5-pro-gt/how-to/guide-unbrick-guide-lenovo-z5-pro-gt-t3915945
Ps: If you're not sure with how this work, I would advise against it as it may completely brick your phone if you do not know what you are doing (E.G like flashing the wrong rom or unsupported rom)
Click to expand...
Click to collapse
Standard QFIL Troubleshooting
Adapted from 4PDA using Google Translate
0) Check if Qualcomm drivers are properly installed
1) QFIL must be run in Administrator mode
2) The path to the folder with the firmware is too long/contains special characters -- unzip the firmware in C: /
3) Use the original cable
4) Change the USB port
5) Redownload QFIL version 2.7.453 from another site, uninstall existing QFIL , clean Program Files (x86) \ Qualcomm, ProgramData \ Qualcomm, AppData \ Roaming \ Qualcomm folders, install QFIL
6) In Device Manager, the hardware item may have a triangle with an exclamation mark. Reinstall drivers using the "Disable driver signing enforcement" mode and try QFIL again without rebooting
7) The file system type in QFIL is by default on emmc. Change to ufs, restart QFIL and try again
8) Turn on flight mode
9) Turn off antivirus
10) In the Configuration check “Use verbose”
Some steps need some more Googling. Hope this helps.
Same problem here
Bailey00 said:
I try so many times using thats tutorial but I stucked in Sahara Fail,
How to resolve this? I have tried so many times.
Click to expand...
Click to collapse
I cant get out of sahara fail too the first time i did it 2 months ago it worked first time. someone have any ideas how to make it work again ? edit: Factory reset would help? edit2:after unlock the bootloader again he did boot normaly and now I have android 10 hope it helps anyone.
I also got the sahara error on my first time. If you got the sahara error, you just have to make sure you press the volume Up, Down and Power button all at the same time. Afterwards, it is very important to quickly connect your phone to the cable attached to the Pc. The sahara error occurs when you are too slow at that process.
I've done this around 5 times and successfully flashed other firmware on my phone. You could also try changing the cable or port that you are using. Checking if you installed the drivers correctly and followed the options in Qfil.
But from what I saw from other threads, sahara error mostly occurs if you are not fast enough at connecting the cable after pressing the buttons.
batgoon said:
I have finally fixed the problem. With the file you have provided, I flashed the Zui 11 and got my phone to the said version. After flashing the update, my phone got a prompt for Zui 11.5 again and I proceeded to install it again. The update now works and my phone booted in around 2 minutes. I am now in Zui 11.5.223 ST. Thank you so much for you help:laugh::good:
Click to expand...
Click to collapse
Can you give me the steps to update zui 11.5 like you did, pls...
I followed the steps stated in here but instead of using the stock firmware, I used the Zui 11 stock firmware.
https://forum.xda-developers.com/z5-...ro-gt-t3915945
After flashing the Zui 11, check your system update again and it should prompt you to install Zui 11.5. If you got into a boot loop again, I would recommend to reflash the Zui 11 stock firmware again. Flashing it again fixed the bootloop. Goodluck:good: