Related
Hi all I'm having hard time time in finding a way to restore back to stock.
I'm on OOS 5.1.8 with twrp official and Magisk
Can you please share how to format the phone completely and again install 5.1.8 or 5.1.6 oos?
Reason for this is poor battery life after last few iteration of updates. Need to see whether it fixes it.
leonalewis said:
Hi all I'm having hard time time in finding a way to restore back to stock.
I'm on OOS 5.1.8 with twrp official and Magisk
Can you please share how to format the phone completely and again install 5.1.8 or 5.1.6 oos?
Reason for this is poor battery life after last few iteration of updates. Need to see whether it fixes it.
Click to expand...
Click to collapse
Here you go,this will restore the phone back to 5.1.5:
https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892
leonalewis said:
Hi all I'm having hard time time in finding a way to restore back to stock.
I'm on OOS 5.1.8 with twrp official and Magisk
Can you please share how to format the phone completely and again install 5.1.8 or 5.1.6 oos?
Reason for this is poor battery life after last few iteration of updates. Need to see whether it fixes it.
Click to expand...
Click to collapse
Make sure you have your full ROM zip files on your phone. Disable secure lock screen in OS. Boot TWRP, backup data only. Wipe everything (data is optional) install ROM zip file, reflash TWRP zip, reboot. You can always restore data at any time after wiping it and it will be as you have it set up to your preferences. There aren't major differences in OOS versions so erroes shouldn't occur with data on any of them. If you want root, you can boot back into recovery and install magisk.
mikex8593 said:
Make sure you have your full ROM zip files on your phone. Disable secure lock screen in OS. Boot TWRP, backup data only. Wipe everything (data is optional) install ROM zip file, reflash TWRP zip, reboot. You can always restore data at any time after wiping it and it will be as you have it set up to your preferences. There aren't major differences in OOS versions so erroes shouldn't occur with data on any of them. If you want root, you can boot back into recovery and install magisk.
Click to expand...
Click to collapse
can someone confirm this procedure is valid which mikex has confirmed? Since on this post https://forum.xda-developers.com/oneplus-6/help/help-flashing-oos-5-1-8-zip-via-twrp-t3814614 he did the same and got BootLoop
stavros67 said:
Here you go,this will restore the phone back to 5.1.5:
https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892
Click to expand...
Click to collapse
Just use this, let OTA update run and you're done. There's no easier solution.
leonalewis said:
can someone confirm this procedure is valid which mikex has confirmed? Since on this post https://forum.xda-developers.com/oneplus-6/help/help-flashing-oos-5-1-8-zip-via-twrp-t3814614 he did the same and got BootLoop
Click to expand...
Click to collapse
You shouldn't get a bootloop if you flash stock firmware via TWRP unless the file itself is messed up. Bootloop can occur if you flash magisk right away, I think. You have to reboot recovery before flashing magisk.
New OP6 owner, quite bugged with how this thing works when flashing stuff..
it was a breeze on my 6p, anyways.
i decided to do a "Clean" flash and wiped data/system/dalvik etc.
then tried to flash the Full zip of 5.1.8 (it is a 1.2gb file) and i flashed via TWRP then flashed twrp zip and rebooted recovery/flashed magisk.
but there is no OS installed it says, boots me back into twrp.
my question now is how do i get it back to load up OOS, do i have to use fastboot now .. ?
i dont want it to wipe my whole SD
what do i do, and how do i stop this from happening for next time?
i thought flashing was normal that way, are we not supposed to wipe system with the op phones..?
i had a MOD installed (xXx) and wanted it removed so that i could install another mod ,thus i wiped system/data etc.
please let me know how to fix this, thx !
leondestiny said:
New OP6 owner, quite bugged with how this thing works when flashing stuff..
it was a breeze on my 6p, anyways.
i decided to do a "Clean" flash and wiped data/system/dalvik etc.
then tried to flash the Full zip of 5.1.8 (it is a 1.2gb file) and i flashed via TWRP then flashed twrp zip and rebooted recovery/flashed magisk.
but there is no OS installed it says, boots me back into twrp.
my question now is how do i get it back to load up OOS, do i have to use fastboot now .. ?
i dont want it to wipe my whole SD
what do i do, and how do i stop this from happening for next time?
i thought flashing was normal that way, are we not supposed to wipe system with the op phones..?
i had a MOD installed (xXx) and wanted it removed so that i could install another mod ,thus i wiped system/data etc.
please let me know how to fix this, thx !
Click to expand...
Click to collapse
You need to make sure you are booting the slot you flashed the rom on, A or B.
sting5566 said:
You need to make sure you are booting the slot you flashed the rom on, A or B.
Click to expand...
Click to collapse
how do i do this? i only flashed zip from the root of my SD , there was no option to select either A or B :C
i went into advanced or seomthing and saw SLot a and B i tapped a and reboot sytem now it is stuck on twrp logo.
f** this ab ****.
When u flashed the rom and rebooted it should let u know which one u r flashing on when u flash magisk, the xXx should have been a magisk module so should have been deleted when u wiped data, I would re-download 5.1.8
Wipe all again.
Flash OS
Flash twrp installer
Reboot to twrp
Flash magisk and reboot
---------- Post added at 01:23 PM ---------- Previous post was at 01:22 PM ----------
Did u have the magisk module version of xXx, if so all u had to do was uncheck it and reboot
OnePlus 6 has two partitions like the Pixel 2. For seamless OTA updates. In TWRP go to the Reboot menu and you'll see your currently active slot. It's either A or B. Switch to the other one and reboot. That should do it if you did flash the ROM.
Bradl79 said:
When u flashed the rom and rebooted it should let u know which one u r flashing on when u flash magisk, the xXx should have been a magisk module so should have been deleted when u wiped data, I would re-download 5.1.8
Wipe all again.
Flash OS
Flash twrp installer
Reboot to twrp
Flash magisk and reboot
---------- Post added at 01:23 PM ---------- Previous post was at 01:22 PM ----------
Did u have the magisk module version of xXx, if so all u had to do was uncheck it and reboot
Click to expand...
Click to collapse
man screw this ab partition shet, i will be forced to do a userdata reset..
can you please advise me what not to do to get into this mess again..?
its not fun recopying my data back and forth.
all i tried to do was clean flash and flash the latest rom via twrp..
why does this thing has to be so complex, please tell me if a clean wipe does this mess ?
cant we safely clean wipe this thing or what?
i love the phone, but the flashing stuff is a huge mess imo.
leondestiny said:
man screw this ab partition shet, i will be forced to do a userdata reset..
can you please advise me what not to do to get into this mess again..?
its not fun recopying my data back and forth.
all i tried to do was clean flash and flash the latest rom via twrp..
why does this thing has to be so complex, please tell me if a clean wipe does this mess ?
cant we safely clean wipe this thing or what?
i love the phone, but the flashing stuff is a huge mess imo.
Click to expand...
Click to collapse
You can always just keep a backup of userdata in TWRP but you don't have to wipe data. If you wipe system and flash the full zip, you will get the no os error but you can boot to system anyway. It just thinks there is no os. The bootloop to TWRP is probably related to magisk.
mikex8593 said:
You can always just keep a backup of userdata in TWRP but you don't have to wipe data. If you wipe system and flash the full zip, you will get the no os error but you can boot to system anyway. It just thinks there is no os. The bootloop to TWRP is probably related to magisk.
Click to expand...
Click to collapse
took me an hour or so to get this thing booting up again..
without the need to wipe SD , this is so strange.
i honestly have no idea how i did it, but i am afraid to use twrp now..
this thing is messed up
leondestiny said:
took me an hour or so to get this thing booting up again..
without the need to wipe SD , this is so strange.
i honestly have no idea how i did it, but i am afraid to use twrp now..
this thing is messed up
Click to expand...
Click to collapse
It's relatively easy. Just always remember to flash TWRP and magisk after flashing full ROM zip. It's always a safe bet to erase your lock screen before messing with TWRP as well so it can just decrypt with no password. If you use a magisk ROM, it's all systemless so the only changes that would stay are the ones that would debloat apps or remove system files. Everything would revert back to normal after you uncheck the ROM module in magisk manager.
mikex8593 said:
It's relatively easy. Just always remember to flash TWRP and magisk after flashing full ROM zip. It's always a safe bet to erase your lock screen before messing with TWRP as well so it can just decrypt with no password. If you use a magisk ROM, it's all systemless so the only changes that would stay are the ones that would debloat apps or remove system files. Everything would revert back to normal after you uncheck the ROM module in magisk manager.
Click to expand...
Click to collapse
hmm okay thx, someone suggested me omni rom, but i will need to erase data right?
but my issue is, if in case i wanted to go back to OOS, would i need to erase data again? :l
and also about flashing roms, must they be flashed on both slots..? a and b ?
i have no clue how i got OOS back booting to be honest.. :l
leondestiny said:
hmm okay thx, someone suggested me omni rom, but i will need to erase data right?
but my issue is, if in case i wanted to go back to OOS, would i need to erase data again? :l
and also about flashing roms, must they be flashed on both slots..? a and b ?
i have no clue how i got OOS back booting to be honest.. :l
Click to expand...
Click to collapse
Switching ROMs, it is best to erase data or keep separate data backups for each ROM and restore the associated ones. As far as flashing on both slots, it wouldn't hurt, but it's not necessary unless instructions dictate. The whole reason for the slots is to allow seamless updates while the os is still active. If you experience any issues with bugs that aren't stated to be in the ROM thread, a clean install is always recommended.
mikex8593 said:
Switching ROMs, it is best to erase data or keep separate data backups for each ROM and restore the associated ones. As far as flashing on both slots, it wouldn't hurt, but it's not necessary unless instructions dictate. The whole reason for the slots is to allow seamless updates while the os is still active. If you experience any issues with bugs that aren't stated to be in the ROM thread, a clean install is always recommended.
Click to expand...
Click to collapse
thx mate, so for next time if i were to flash some oos through twrp, i only need to wipe data/cache etc.
then flash the oos zip ? i dont think i had the option to select which Slot to flash it to, so i guess i just have to reboot to the slot that it has it flashed on..?
and also flashing procedure must be like Rom then twrp then reboot twrp then flash magisk yes?
leondestiny said:
took me an hour or so to get this thing booting up again..
without the need to wipe SD , this is so strange.
i honestly have no idea how i did it, but i am afraid to use twrp now..
this thing is messed up
Click to expand...
Click to collapse
No sheet
This is what happened to me LOL and I soft bricked phone. Never ever bricked a phone before.
I tried to flash havoc os, OOS was originally on both A and B.
This process wiped slot B clean (even tho was booting on slot A), and OOS stayed on slot A.
I went to the reboot screen to reboot recovery on slot B and BAM I was bricked locked into fastboot mode.
And people say its easy.
Now I am in msmdownloadtool, I have managed to get it connected, and I can start the recovery but it fails, so I think the phone may be proper bricked.
Anyone getting a oneplus6 I would say these phones seem to have a genuine risk of brick, all I did was try to boot of a slot which TWRP says had no OS and now I have this problem.
---------- Post added at 01:59 ---------- Previous post was at 01:25 ----------
mikex8593 said:
It's relatively easy. Just always remember to flash TWRP and magisk after flashing full ROM zip. It's always a safe bet to erase your lock screen before messing with TWRP as well so it can just decrypt with no password. If you use a magisk ROM, it's all systemless so the only changes that would stay are the ones that would debloat apps or remove system files. Everything would revert back to normal after you uncheck the ROM module in magisk manager.
Click to expand...
Click to collapse
Havoc OS requires Oxygen OOS in both slots.
So I need to somehow get this to work.
I can unbrick the phone now with msmdownloadtool.
After ubricked the bootloader is locked again so I have to start from scratch.
Unlock oem loader in OS
Unlock bootloader in fastboot
Copy zips to phone.
Boot into TWRP and install TWRP, it says it installs to both slots but B bricks phone.
At this point I have oxygen OOS installed via recovery tool on slot A, twrp installed.
If I try to boot in slot B, phone bricks, fastboot loop which doesnt allow you to boot back into twrp so cannot switch back to slot A without msmdownload tool.
So the question is after I have recovered the phone how do I get oxygen OOS onto slot B as well, given I Cannot boot from slot B?
The solution is probably easy to those who know how but seems it isnt documented.
chrcol said:
No sheet
This is what happened to me LOL and I soft bricked phone. Never ever bricked a phone before.
I tried to flash havoc os, OOS was originally on both A and B.
This process wiped slot B clean (even tho was booting on slot A), and OOS stayed on slot A.
I went to the reboot screen to reboot recovery on slot B and BAM I was bricked locked into fastboot mode.
And people say its easy.
Now I am in msmdownloadtool, I have managed to get it connected, and I can start the recovery but it fails, so I think the phone may be proper bricked.
Anyone getting a oneplus6 I would say these phones seem to have a genuine risk of brick, all I did was try to boot of a slot which TWRP says had no OS and now I have this problem.
---------- Post added at 01:59 ---------- Previous post was at 01:25 ----------
Havoc OS requires Oxygen OOS in both slots.
So I need to somehow get this to work.
I can unbrick the phone now with msmdownloadtool.
After ubricked the bootloader is locked again so I have to start from scratch.
Unlock oem loader in OS
Unlock bootloader in fastboot
Copy zips to phone.
Boot into TWRP and install TWRP, it says it installs to both slots but B bricks phone.
At this point I have oxygen OOS installed via recovery tool on slot A, twrp installed.
If I try to boot in slot B, phone bricks, fastboot loop which doesnt allow you to boot back into twrp so cannot switch back to slot A without msmdownload tool.
So the question is after I have recovered the phone how do I get oxygen OOS onto slot B as well, given I Cannot boot from slot B?
The solution is probably easy to those who know how but seems it isnt documented.
Click to expand...
Click to collapse
Fastboot boot recovery. Img
Flash oos full ROM zip
Flash recovery. Zip
Reboot recovery
Flash oos full ROM zip AGAIN
flash twrp. Zip AGAIN
Reboot recovery
Flash magisk if you want root.
Make sure your using the correct twrp aswell. I recommend bluespark v86
chrcol said:
And people say its easy.
Click to expand...
Click to collapse
it is not easy, i make backups of my whole phone every 2weeks because i am a flashaholic i see myself switching from aosp back to oos and vice versa (i love oos) i actually gave up on flashing roms some weeks ago tried to stick to oos only so that i wont be bothered with bricks for whatver reason (and not being forced to use msmtool) , it is frustrating.
you always have to make sure you are not flashing a rom that has an older security patch , e.g november build of oos if you flash aosp rom with october build you might brick, so the rom has to be either on november security patch or newer e.g december.
it is so confusing as you even have to use the latest twrp always or else you can mess it up again..
always make backups is my advice.
leondestiny said:
it is not easy, i make backups of my whole phone every 2weeks because i am a flashaholic i see myself switching from aosp back to oos and vice versa (i love oos) i actually gave up on flashing roms some weeks ago tried to stick to oos only so that i wont be bothered with bricks for whatver reason (and not being forced to use msmtool) , it is frustrating.
you always have to make sure you are not flashing a rom that has an older security patch , e.g november build of oos if you flash aosp rom with october build you might brick, so the rom has to be either on november security patch or newer e.g december.
it is so confusing as you even have to use the latest twrp always or else you can mess it up again..
always make backups is my advice.
Click to expand...
Click to collapse
If you're installing havoc os, make sure you're using latest bluespark TWRP first. Reboot recovery, flash oos, flash TWRP, reboot recovery, flash havoc gapps and magisk then reboot. The only difference in a/b partition is that there's a few extra steps in the flashing process. You don't have to flash to both slots to have havoc, but you also shouldn't be manually changing the slot in TWRP to try to boot a specific slot unless you know what you're doing.
First I have an admission - I'm 82 so my memory is not as good as it was. I have been using smartphones for some years now including flashing recoveries and operating systems. This time, however, I have got myself into a real mess.
I have a OnePlus 6 and just recently there was an OxygenOS update from OnePlus which I installed in the normal OTA way. It was only a little later that I realised that I'd updated from Oreo (8.1) to Pie (9) and there was not a version of Xposed for Pie. I want Xposed so I decided that I wanted to downgrade to Oreo. It didn't occur to me that it would be any more difficult than re-flashing the previous version of OxygenOS. I now realise it isn't that easy or, at least, it doesn't appear to be.
Having flashed Oreo the phone wouldn't boot. It got as far as the boot animation and stayed there. I thought the best thing then would be to try and get back to Pie so I reflashed that. At least the phone now booted but I soon realised that some things weren't right. For example if I turn on wifi it turns off again after about two seconds so I can't use wifi at all.
I'm not sure what to do now. I do have a TWRP backup for both Pie and the previous Oreo. Would it be possible to restore one of those (preferable Oreo)? I'm a bit nervous about trying that as I'm not sure how much wiping/restore I'd need to do. There is the Vendor partition (I've not seen that before) and I would be very nervous about wiping and restoring the boot partition which now, I believe, contains the recovery.
I hoping that some kind person will offer some advice to put me on the road to recovery (No pun intended).
First of all, I'm impressed that you have done as much as you have (or even wanted to for that matter) at 82. Most older people I know (I'm 42 btw)barely know how to use there phones in the os, much less know what recovery is, lol.
Anyway, I'm pretty sure I've read that with you go backwards to Oreo from pie, you need to do a full wipe including storage. Did you do that?
BarrySamuels said:
First I have an admission - I'm 82 so my memory is not as good as it was. I have been using smartphones for some years now including flashing recoveries and operating systems. This time, however, I have got myself into a real mess.
I have a OnePlus 6 and just recently there was an OxygenOS update from OnePlus which I installed in the normal OTA way. It was only a little later that I realised that I'd updated from Oreo (8.1) to Pie (9) and there was not a version of Xposed for Pie. I want Xposed so I decided that I wanted to downgrade to Oreo. It didn't occur to me that it would be any more difficult than re-flashing the previous version of OxygenOS. I now realise it isn't that easy or, at least, it doesn't appear to be.
Having flashed Oreo the phone wouldn't boot. It got as far as the boot animation and stayed there. I thought the best thing then would be to try and get back to Pie so I reflashed that. At least the phone now booted but I soon realised that some things weren't right. For example if I turn on wifi it turns off again after about two seconds so I can't use wifi at all.
I'm not sure what to do now. I do have a TWRP backup for both Pie and the previous Oreo. Would it be possible to restore one of those (preferable Oreo)? I'm a bit nervous about trying that as I'm not sure how much wiping/restore I'd need to do. There is the Vendor partition (I've not seen that before) and I would be very nervous about wiping and restoring the boot partition which now, I believe, contains the recovery.
I hoping that some kind person will offer some advice to put me on the road to recovery (No pun intended).
Click to expand...
Click to collapse
grab this file. http://oxygenos.oneplus.net.s3.amazonaws.com/OnePlus6Oxygen_22_OTA_007_all_1805131952_O_MR1.zip flash that to be back on Oreo 5.1.5. this is the special roll back firmware.
also, this will wipe all data as well as internal storage. just putting that out there so you know before doing it.
b.huss2 said:
Anyway, I'm pretty sure I've read that with you go backwards to Oreo from pie, you need to do a full wipe including storage. Did you do that?
Click to expand...
Click to collapse
No, it was something I was trying to avoid. I was working on the assumption that as going from Oreo to Pie didn't involve any loss of data/internal storage then going from Pie to Oreo wouldn't either.
MrSteelX said:
grab this file. http://oxygenos.oneplus.net.s3.amazonaws.com/OnePlus6Oxygen_22_OTA_007_all_1805131952_O_MR1.zip flash that to be back on Oreo 5.1.5. this is the special roll back firmware.
also, this will wipe all data as well as internal storage. just putting that out there so you know before doing it.
Click to expand...
Click to collapse
As I said above I was trying to avoid wiping data/internal storage but if that is the only way then I'll have to do it. I do have a backup of my internal storage so I can replace that easily enough. Would my Oreo backup be of any use after the wipe to restore my original data setup? That version of OxygenOS was 5.1.11 so could I get back to that?
I thank you both for your very timely help.
P.S. Can you see anything wrong with this plan?
1. Flash the roll back firmware.
2. Install TWRP using Fastboot
3. Flash, using TWRP, OxygenOS v5.1.11 over the roll back firmware
4. Restore 'data' from my previous TWRP backup.
5. Restore internal storage from backup.
BarrySamuels said:
1. Flash the roll back firmware.
2. Install TWRP using Fastboot
3. Flash, using TWRP, OxygenOS v5.1.11 over the roll back firmware
4. Restore 'data' from my previous TWRP backup.
5. Restore internal storage from backup.
Click to expand...
Click to collapse
I would think that should get you back to where you were. I have not personally been through these specific steps, but seems logical. It's def worth a try.
b.huss2 said:
I would think that should get you back to where you were. I have not personally been through these specific steps, but seems logical. It's def worth a try.
Click to expand...
Click to collapse
going from oreo to pie, no data loss.
going from pie to oreo, data loss.
that is how it is done. after coming back to 5.1.5 then you can go to 5.1.11
MrSteelX said:
going from oreo to pie, no data loss.
going from pie to oreo, data loss.
that is how it is done. after coming back to 5.1.5 then you can go to 5.1.11
Click to expand...
Click to collapse
I think that's kind of understood at this point. However, I see no problem with restoring a Oreo backup once he's back on Oreo.
BarrySamuels said:
No, it was something I was trying to avoid. I was working on the assumption that as going from Oreo to Pie didn't involve any loss of data/internal storage then going from Pie to Oreo wouldn't either.
As I said above I was trying to avoid wiping data/internal storage but if that is the only way then I'll have to do it. I do have a backup of my internal storage so I can replace that easily enough. Would my Oreo backup be of any use after the wipe to restore my original data setup? That version of OxygenOS was 5.1.11 so could I get back to that?
I thank you both for your very timely help.
P.S. Can you see anything wrong with this plan?
1. Flash the roll back firmware.
2. Install TWRP using Fastboot
3. Flash, using TWRP, OxygenOS v5.1.11 over the roll back firmware
4. Restore 'data' from my previous TWRP backup.
5. Restore internal storage from backup.
Click to expand...
Click to collapse
Almost. You are missing one thing.
1. Flash the roll back firmware
2. Install TWRP using fastboot
3. Flash, using TWRP, OxygenOS 5.1.11
4. Before rebooting, FLASH TWRP IN TWRP (This is important, as flashing 5.1.11 will overwrite recovery)
5. Use your TWRP backup
6. Do what you need for files you want on internal storage.
Don't forget to flash TWRP after you update to 5.1.11.
Not having much luck. I flashed the roll back firmware, and twrp, then rebooted but I got the boot animation again and it wouldn't go any further. I re-downloaded the firmware again, in case there was any corruption, and re-flashed it without flashing twrp but got as far as the boot animation again but no further.
Whilst in TWRP I used the file manager to look at internal storage and nothing had been wiped from that.
I'm not sure what to do now so any suggestions would be very welcome.
BarrySamuels said:
Not having much luck. I flashed the roll back firmware, and twrp, then rebooted but I got the boot animation again and it wouldn't go any further. I re-downloaded the firmware again, in case there was any corruption, and re-flashed it without flashing twrp but got as far as the boot animation again but no further.
Whilst in TWRP I used the file manager to look at internal storage and nothing had been wiped from that.
I'm not sure what to do now so any suggestions would be very welcome.
Click to expand...
Click to collapse
Fastboot working correctly - try flashing the fastboot Rom. Hopefully that will put you back to square one where you start over. Complete wipe though!
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
Use the fastboot ROM recovery. It works (I've used it twice) no data wipe.
chazey2 said:
Fastboot working correctly - try flashing the fastboot Rom. Hopefully that will put you back to square one where you start over. Complete wipe though!
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
Click to expand...
Click to collapse
That does sound rather hairy especially as I don't know which one I'd need to use. It does mention that it should not be used to upgrade or downgrade and I'm not sure that I, or my phone, knows which version is currently installed.
ADDENDUM:
I decided to try one more thing of my own. I wiped data and re-flashed the Pie version of OxygenOS then rebooted.
:laugh: It booted and seemed to be working properly i.e. I could use wifi and the time doesn't keep being lost.
I have now installed Blu Spark TWRP and restored my 'data' backup and I am now back to where I was before all this started. It isn't really where I want to be because I have no Xposed but it is significantly better than a non-booting phone. I'll just have to wait for a new version of Xposed (if such ever appears).
I really don't know why those other suggestions didn't work.
Very many thanks to all those who offered support; it certainly does give a morale boost.
BarrySamuels said:
That does sound rather hairy especially as I don't know which one I'd need to use. It does mention that it should not be used to upgrade or downgrade and I'm not sure that I, or my phone, knows which version is currently installed.
ADDENDUM:
I decided to try one more thing of my own. I wiped data and re-flashed the Pie version of OxygenOS then rebooted.
:laugh: It booted and seemed to be working properly i.e. I could use wifi and the time doesn't keep being lost.
I have now installed Blu Spark TWRP and restored my 'data' backup and I am now back to where I was before all this started. It isn't really where I want to be because I have no Xposed but it is significantly better than a non-booting phone. I'll just have to wait for a new version of Xposed (if such ever appears).
I really don't know why those other suggestions didn't work.
Very many thanks to all those who offered support; it certainly does give a morale boost.
Click to expand...
Click to collapse
Your welcome good luck
Here's my question.
I'm curious to check out the Android 11 Developer preview. Currently, my TMobile phone has been converted to global with root and such. What I want to know is, if I install the Dev 3 Android 11 preview, and then want to go back to where I was on global, will I be able to get into TWRP to restore my backup of the Global? Will that work? Or would I basically have to start over?
Thanks everyone!
Probably would just have to download and flash the revert files listed on the developer page.
Yes android 11 is meant for global so is the downgrade
Right but that wipes the device. Does it also wipe recovery? I'm wondering if once I revert, if I can boot into TWRP and just restore from backup on Android 10
InsaneJester17 said:
Right but that wipes the device. Does it also wipe recovery? I'm wondering if once I revert, if I can boot into TWRP and just restore from backup on Android 10
Click to expand...
Click to collapse
Backup for TWRP doesn't work fully. I wouldn't rely on it.
Upgrade didnt wipe mine, downgrade does. As far as TWRP, i dunno. (IN2017)
InsaneJester17 said:
Right but that wipes the device. Does it also wipe recovery? I'm wondering if once I revert, if I can boot into TWRP and just restore from backup on Android 10
Click to expand...
Click to collapse
TWRP is not fully functional yet so I wouldn't try to restore from there. Upgrading wouldn't wipe phone but downgrading would. I would move all files from phone and copy to computer then restore after downgrade. Also TWRP is saved on your sd card so I think it would not delete the folder or contents since it's not a data file. Happy modding!
D'oh! I'm guilty and moved too fast. I got caught in a boot loop trying to wipe dalvik/cache in twrp. No biggie. MSM'ed back to stock.
TWRP isn't available for A11 yet so I doubt you'll be able to flash it while on DP3. Plus (I'm pretty any backup made on a newer OS won't work on older OS versions due to system changes unless you're only backing up and restoring data.
hello i was upgrading from stock 9.0.7 to 9.0.9, my bootloader is unlocked and twrp is a permanent one, the phone is also rooted. i wiped system then flashed the 9.0.9 then flashed the 4.0.4 twrp, rebooted into twrp, flashed latest magisk, rebooted into twrp and then pressed reboot into system. the phone is encrypted. the booting animation has been on for 20-30 minutes at this point. is it a bootloop? why what did i do wrong? thanks
@seth wellington
Try formatting data them reboot system. That should get you booted up.
Never wipe system or vendor on these devices and always when flashing a rom flash TWRP installer zip or you won't have twrp because of where recovery is located which is same place as boot.img and it has to be installed when flashing a rom or update to a rom or it won't be present.
How I flash OOS on my once T-Mobile now converted international/global OnePlus 6t.
Boot TWRP
Flash OOS global 10.3.6
Flash TWRP installer
Flash finalize
Format data
Reboot system
How I install a rom on my converted OnePlus 6t. This installation process varies depending on whether or not whatever rom I'm installing comes with gapps and or TWRP and of course you don't want to install global OOS on another model device. Since I converted my T-Mobile OnePlus 6t using guide and msm tool I now use global or international OnePlus 6t roms, firmware... Example Pixel Experience rom installation:
Boot TWRP
Flash OOS 10.3.6 global from repo xda thread
Flash Pixel Experience rom
Flash TWRP installer zip
Flash finalize zip
Format data
Reboot system.
Start to set up device then at some point enable developer options and usb debugging and doable any lock screen and boot twrp and flash magisk for root and reboot system. That is how I install a rom that has gapps but not twrp included in rom zip. Finalize can he found with a quick search on xda. It copies firmware to other slot on your AB partition device so that you don't have to. Saves 5-6 minutes and works great.
Edit
What you could have done is just flash your updated OOS , flash TWRP installer zip, reboot recovery, flash magisk, reboot system. That's what I would have done updating OOS ..
Hope this helps.
Sent from my OnePlus6T using XDA Labs
flash713 said:
@seth wellington
Try formatting data them reboot system. That should get you booted up.
Never wipe system or vendor on these devices and always when flashing a rom flash TWRP installer zip or you won't have twrp because of where recovery is located which is same place as boot.img and it has to be installed when flashing a rom or update to a rom or it won't be present.
How I flash OOS on my once T-Mobile now converted international/global OnePlus 6t.
Boot TWRP
Flash OOS global 10.3.6
Flash TWRP installer
Flash finalize
Format data
Reboot system
How I install a rom on my converted OnePlus 6t. This installation process varies depending on whether or not whatever rom I'm installing comes with gapps and or TWRP and of course you don't want to install global OOS on another model device. Since I converted my T-Mobile OnePlus 6t using guide and msm tool I now use global or international OnePlus 6t roms, firmware... Example Pixel Experience rom installation:
Boot TWRP
Flash OOS 10.3.6 global from repo xda thread
Flash Pixel Experience rom
Flash TWRP installer zip
Flash finalize zip
Format data
Reboot system.
Start to set up device then at some point enable developer options and usb debugging and doable any lock screen and boot twrp and flash magisk for root and reboot system. That is how I install a rom that has gapps but not twrp included in rom zip. Finalize can he found with a quick search on xda. It copies firmware to other slot on your AB partition device so that you don't have to. Saves 5-6 minutes and works great.
Edit
What you could have done is just flash your updated OOS , flash TWRP installer zip, reboot recovery, flash magisk, reboot system. That's what I would have done updating OOS ..
Hope this helps.
Sent from my OnePlus6T using XDA Labs
Click to expand...
Click to collapse
Thank you very much for your reply. Unfortunately I couldn't wait for that long and I had to do something right then. After some attempts I also lost my twrp and was left without a functioning recovery, so I had to look for help and some people helped me go through unbricking through the msm tool.
The thing is i just really want to always flash clean so that the phone doesn't lag and works properly, I had no idea you shouldn't wipe system... The guide that I followed said that when updating oxygen manually you have to wipe system so I thought nothing would go wrong. I still don't know what caused a bootloop since that guide was a verified one. Thanks a lot for your help. So if I'm reading it correctly, you have to do the wipes after you've installed the system, not before?
seth wellington said:
Thank you very much for your reply. Unfortunately I couldn't wait for that long and I had to do something right then. After some attempts I also lost my twrp and was left without a functioning recovery, so I had to look for help and some people helped me go through unbricking through the msm tool.
The thing is i just really want to always flash clean so that the phone doesn't lag and works properly, I had no idea you shouldn't wipe system... The guide that I followed said that when updating oxygen manually you have to wipe system so I thought nothing would go wrong. I still don't know what caused a bootloop since that guide was a verified one. Thanks a lot for your help. So if I'm reading it correctly, you have to do the wipes after you've installed the system, not before?
Click to expand...
Click to collapse
Quit a few pretty well known developers here on xda (AOSiP op is one and there are more) say not to wipe system or vendor in their first posts of their custom rom threads. The way I describe how I install works 100% always and is the cleanest possible installation. Formatting data when installing a new rom at the end of install process does all the wiping needed to make sure nothing is left from the past and everything is clean. I used to wipe various partitions but on other devices. The install directions I use are originally from the PiXeN rom developers op. I've been flashing roms since the Nexus S days. Not saying that means anything other than I'm kinda old now. ? But that install process has never failed me once and I've flashed I'm sure hundreds of times on this device.. When I update i just flashing the updated rom over current and don't wipe anything then flashing twrp installer zip, reboot recovery flash magisk reboot system or if gapps are needed when I reboot recovery flash gapps..Unless it's a major OS update that's always worked for me.
Possibly not formatting data caused boot loop.. I know when going from OOS to AOSP rom format data is mandatory or it won't boot system.. I never flash magisk during initial flash. I always boot system first then at some point boot twrp and flash magisk. Try that next round and see if it turns out better. The whole AB partition deal made me feel like I was really old and retarded.
If I was updating OOS I would boot recovery, flash OOS, flash twrp installer zip reboot recovery, flash magisk, reboot system. Check out the finalize script xda thread. There are two here. The original person who made finalize has a thread and another user has another finalize thread. I believe in guides section of OnePlus 6t. With Android there are always more than a few ways to achieve something you know ... But what I post here is what I've been doing and I've flashed 400-500 times at least on this device.
Sent from my OnePlus6T using XDA Labs
@flash713
I totally trust you and respect anything you say and recommend me to do. Thanks a lot for all the instructions and clarification. I've been into android far less time than you — only since oneplus one. I'm extremely bad with tech but even with that phone j somehow managed to get bootloops or half-bricks ten times less than with the oneplus 6. And back then in 2015 I was way more enthusiastic: flashing twice a month loads and loads of roms. Of course it wasn't my personal achievement, I was still simply following detailed and carefully written instructions on forums on how to flash a particular rom in a particular way, but hey, at least I somehow managed it.
Now in this case I'm assuming it's the a/b partitions they've introduced that have completely changed the process and ways of flashing to the point that I stick to the guides and still get bootloops lol. That unbricking process was a huge stress for me, I don't think I'm going to touch anything in my phone for a while now. And I'm on the latest 10.3.6 oxygen so it's alright. Thank you for your help buddy
seth wellington said:
@flash713
I totally trust you and respect anything you say and recommend me to do. Thanks a lot for all the instructions and clarification. I've been into android far less time than you — only since oneplus one. I'm extremely bad with tech but even with that phone j somehow managed to get bootloops or half-bricks ten times less than with the oneplus 6. And back then in 2015 I was way more enthusiastic: flashing twice a month loads and loads of roms. Of course it wasn't my personal achievement, I was still simply following detailed and carefully written instructions on forums on how to flash a particular rom in a particular way, but hey, at least I somehow managed it.
Now in this case I'm assuming it's the a/b partitions they've introduced that have completely changed the process and ways of flashing to the point that I stick to the guides and still get bootloops lol. That unbricking process was a huge stress for me, I don't think I'm going to touch anything in my phone for a while now. And I'm on the latest 10.3.6 oxygen so it's alright. Thank you for your help buddy
Click to expand...
Click to collapse
Np. My real first name is Seth. Haha. Cool name btw. I just installed OOS 10.3.7 on my 6t. I was notified of the update yesterday via oxygen updater app from play store. Good handy app to have. I would have never known 10.3.7 was out or at least not so soon if it wasn't for that app. I believe it auto notified me too. I don't remember setting it up. Android has changed soooo much you know.. I love my OnePlus 6t though. Definitely one of my most favorite devices I've ever used. What's new today is gone at some point and replaced with "better.." lol. Not always better imo anyway. Glad I could help. Feel free to message me any time. Good day to you.