Please help me how to back from Oxygen to CM11s or CM12 ? Oxygen is't better. i've root my Oneplus and have twr
I HAVE NOT TRIED THIS MYSELF:
I would say make a back up, wipe all partitions except for your internal storage, and then try flashing cm12 via twrp.
I went from oxygen back to stock rooted CM11s no problem. I heard Oxygen installs a modified TWRP, though, so you could reinstall the latest version just to be safe before re-flashing CM.
Edit: I didn't have to reinstall the recovery.
The hard is if you got no partition backups. If that is the case you will have to download stock cm11s XNPH05Q latest signed build. Unzip put OPO into fastboot mode. Find the file flash-radio.sh open it and manual flash every command that starts with fastboot. Then flash boot,cache,system, and depending on which data amount you have flash userdata images. Don't worry with the recovery you have twrp. Be ready to start over. Remember friends don't let friends flash CO2 OS. Good luck.
I've read this thread and I'm a bit confused really. Oxygen/color/cm are all the same. So to swap between them just make sure you format system/data/cache before you flash....simple as that,no need to format SD! Also None of these install a different recovery so don't worry about that but do have cm11 and cm12 firmware file's somewhere on you're SD card as color will need cm11 firmware file's and let's say cm12 will or course need cm12 firmware file's.
I state this as I've used all of the above in the past week and have returned back to cm12 without a problem. But I did have to work through SD to clear rubbish installed by color and oxygen that's not needed.
Sent from my A0001
andrewwright said:
I've read this thread and I'm a bit confused really. Oxygen/color/cm are all the same. So to swap between them just make sure you format system/data/cache before you flash....simple as that,no need to format SD! Also None of these install a different recovery so don't worry about that but do have cm11 and cm12 firmware file's somewhere on you're SD card as color will need cm11 firmware file's and let's say cm12 will or course need cm12 firmware file's.
I state this as I've used all of the above in the past week and have returned back to cm12 without a problem. But I did have to work through SD to clear rubbish installed by color and oxygen that's not needed.
Sent from my A0001
Click to expand...
Click to collapse
The oxygenOS zip installs a boot loader version that doesn't play well with CM11. If a person were to attempt to flash CM11 or restore a CM11 nandroid with that boot loader present it could cause serious complications.
To go back using recover one would need to flash a file that contained a good firmware/bootloader. CM12 from the CM website contains such a configuration. There are other files around that also apply non-bricking firmware. Fastboot flashing CM11S also would work if the device isn't bricked yet.
Once "bricked", recovery is possible but problematic and frustrating.
Flashing via TWRP straight from OxygenOS is not a good idea without preparation.
Hastily spouted for your befuddlement
xdoncam said:
Please help me how to back from Oxygen to CM11s or CM12 ? Oxygen is't better. i've root my Oneplus and have twr
Click to expand...
Click to collapse
You need to flash the right firmware and modem first and then you can flash whatever you like.
andrewwright said:
I've read this thread and I'm a bit confused really. Oxygen/color/cm are all the same. So to swap between them just make sure you format system/data/cache before you flash....simple as that,no need to format SD! Also None of these install a different recovery so don't worry about that but do have cm11 and cm12 firmware file's somewhere on you're SD card as color will need cm11 firmware file's and let's say cm12 will or course need cm12 firmware file's.
I state this as I've used all of the above in the past week and have returned back to cm12 without a problem. But I did have to work through SD to clear rubbish installed by color and oxygen that's not needed.
Sent from my A0001
Click to expand...
Click to collapse
Not the same at all. Oxygen uses completely different firmware, if you fail to flash the right firmware before going back to CM you'll fail dismally.
Transmitted via Bacon
If you want oxygen you use cm12 firmware
For cm11 you use cm11 firmware
For cm12 you use cm12 firmware.
Formatting system and data and not using tb would help to. I did state this in my first post. Also the bootloader...turns first boot screen red....it works OK on cm12. Had no problems booting
Sent from my A0001
---------- Post added at 01:28 AM ---------- Previous post was at 01:23 AM ----------
But I did get what you two are saying but people on xda should know this already really. Flashing is easy...fixing is not
Sent from my A0001
andrewwright said:
If you want oxygen you use cm12 firmware
Click to expand...
Click to collapse
Oxygen doesn't use CM12 firmware, it uses firmware specific to Oxygen. This is why there are countless posts from people (who tried flashing CM12 after Oxygen without first flashing the right firmware) complaining that CM won't flash and their ROM won't boot, or that they're bricked.
Transmitted via Bacon
SAFE way move back from oxygenos to CM11s
For those who havnt shifted back to cm11s.(and still on oxygenos) and want to move back to CM11s ofcourse not hardbricked your phone. THIS GUIDE Is FOR ONEPLUS ONE 64GB VARIANT . (ALSO VALID FOR INDIAN USERS)
This guide will happily and SAFELY get you back to cm11s(XNPH05Q. OTA Safe).
people have hardbricked their phone by simply flashing cm11s through fastboot, which ofcourse is not the appropriate procedure.
NOTE: MY PHONE WAS NOT ROOTED BUT I WAS RUNNING OXYGENOS WITH TWRP RECOVERY INSTALLED(BUT I PREFERRED FASTBOOT METHOD). ONLY DRAWBACK IS YOU NEED TO TAKE BACKUP FIRST . ELSE THIS METHOD IS SAFE.
You need to have the following files:
1. mediafire.com/download/78r7kes21exsnbh/Calkulin's_Stock_OPO_XNPH05Q_ROM_v1.0.zip
2. mediafire.com/download/94o0lb0pzdg1drw/XNPH05Q_Extras.zip
-Extract the first zip. Again extract the zip from the extracted folder.
-Extract the XNPH05Q in the same folder where the all above files were extracted .
-The folder should have fastboot cmd. and you should have fastboot drivers installed .
-put your device in fastboot mode by turning the phone off and pressing volume up+power key simultaneously .
-open cmd in the folder where all of the above files were extracted . press shift and right click in the flder and open command prompt .
- look whether your device is detected by fastboot. type fastboot devices
-You need to have unlocked bootloader.(if not, type fastboot oem unlock)
-TYPE THE FOLLOWING COMMANDS IN THE COMMANDS IN THE ORDER AS GIVEN :
IMP: DONT REBOOT IN BETWEEN COMMANDS
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot flash boot boot.img
fastboot flash userdata userdata_64G.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot reboot
You are all done. Sit back and relax.
Lock the bootloader again. After you are done with setting up. type fastboot oem lock
timmaaa said:
Oxygen doesn't use CM12 firmware, it uses firmware specific to Oxygen. This is why there are countless posts from people (who tried flashing CM12 after Oxygen without first flashing the right firmware) complaining that CM won't flash and their ROM won't boot, or that they're bricked.
Transmitted via Bacon
Click to expand...
Click to collapse
People are getting "stuck" not a hardbrick. because they won't wipe system and data. That's my only thought here as oxygen bootloader boots cm12. Also cm12 bootloader flashes/boots oxygen without issue my end...but I formatted system/data. If people want to mess about with fastboot when recovery does the same thing is up to them. People just need to use recovery in the right way for a successful flash.
Sent from my A0001
andrewwright said:
People are getting "stuck" not a hardbrick. because they won't wipe system and data. That's my only thought here as oxygen bootloader boots cm12. Also cm12 bootloader flashes/boots oxygen without issue my end...but I formatted system/data. If people want to mess about with fastboot when recovery does the same thing is up to them. People just need to use recovery in the right way for a successful flash.
Sent from my A0001
Click to expand...
Click to collapse
CM boots because the firmware is built in to the ROM zip, so it overwrites the firmware that Oxygen previously flashed. You're not booting CM with the Oxygen firmware, that's impossible. The Oxygen firmware is being overwritten. For every ROM other than CM you need to first flash the right firmware zip because the firmware isn't built into those ROM zips. Not one did I mention fastboot either, it isn't needed. I'm talking about the recovery flashable firmware zip.
And of course you should wipe system and data (along with cache and dalvik cache) when flashing a ROM, that's standard procedure for any ROM flash.
Where can I obtain the needed flashable zip files to revert back to cm11s?
Sent from my A0001 using XDA Free mobile app
Here:
https://mega.co.nz/#F!ooViWJYB!DWSVZpEJRQb-zpurGyM-mg
Both cm11 and 12 are in there. Flash in recovery then reboot recovery then flash ROM/gapps
Sent from my A0001
andrewwright said:
Here:
https://mega.co.nz/#F!ooViWJYB!DWSVZpEJRQb-zpurGyM-mg
Both cm11 and 12 are in there. Flash in recovery then reboot recovery then flash ROM/gapps
Sent from my A0001
Click to expand...
Click to collapse
I actually had it done already by the time I saw this but very much appreciated. I am sure it will come in handy for others.
timmaaa said:
CM boots because the firmware is built in to the ROM zip, so it overwrites the firmware that Oxygen previously flashed. You're not booting CM with the Oxygen firmware, that's impossible. The Oxygen firmware is being overwritten. For every ROM other than CM you need to first flash the right firmware zip because the firmware isn't built into those ROM zips. Not one did I mention fastboot either, it isn't needed. I'm talking about the recovery flashable firmware zip.
And of course you should wipe system and data (along with cache and dalvik cache) when flashing a ROM, that's standard procedure for any ROM flash.
Click to expand...
Click to collapse
Just to clear this up I had to find out why this is happening. Okay so my home brew cm12 builds don't compile firmware file's. I didn't know this but now I do. So this must have been the reason why I was able to keep oxygen bootloader on cm.
Sent from my A0001
somehow I could just revert to cm12.1
FYI,
In case it helps someone, I tried out OxygenOS last night and while it is stable I dislike many things (email client, text client) and the biggest beef of all is neither text nor email show on my Mazda.
Soooo this is a nono I believe, but I could restore CM12.1.
I just did a backup in TWRP of OxygenOS> then I did a clean wipe> then was able to restore CM12.1 nightlies from June1 I think it was and it seems just fine.
I believe it is because the modem etc in 12.1 is the same as OxygenOS had all along?
Related
I recently wiped (sys/data/cache/dav) my opo and tried flashing the aosp .zip OnePlus released.
I completely failed to see it was an .ota and it would not flash. I restored nandroid and its a mess.
The phone boots fine to vanir/ak restore, but no lock screen, radio, etc.
Checked settings and all looks good, except "Firmware Unknown".
Should I just backup my onboard storage and use a factory image to restore?
Reflash the Vanir ROM that u restored from to see what missing elements get restored. If u have no radio though, use fastboot to flash or one of the flashable zips. You shouldn't have to completely wipe depending on which partitions are jacked, if any.
From my N5 or OPO
truckroot said:
Reflash the Vanir ROM that u restored from to see what missing elements get restored. If u have no radio though, use fastboot to flash or one of the flashable zips. You shouldn't have to completely wipe depending on which partitions are jacked, if any.
From my N5 or OPO
Click to expand...
Click to collapse
Thanks for the post. I tried flashing a Vanir nightly from Twrp and it was a real mess. It would boot to OS, but constant settings, etc. fail to launch windows popping up.
No radio on nandroid and on twrp zip flashes in any case.
Had a feeling it would take a fastboot flash of a zip.
Thinking stock cm 11s .zip fastboot flash then?
[SOLVED ]"Patching system image unconditionally..." - can't install CM at all.
my device (moto G (falcon) XT1032) is a GPE device.
in the last 2 days i tried to install CM 13 on my device.
i tried 3 different recoveries** - CWM, TWRP and CM recovery - to install cm-13.0-20160206-NIGHTLY-falcon (and yes, i checked before flashing, the SHA1).
in all those tryouts i always get into the sentence in the headline - Patching system image unconditionally... - and it just stays there forever.
one time i waited 40 minutes, and it still stayed on this message, and do nothing.
every time before flashing the rom, i wiped the device (dalvik cache, cache, system, Data).
i also try to flash the latest snapshot (cm-12.1-20151117-SNAPSHOT-YOG7DAO1K9-falcon) because i thought maybe there is a problem with the latest nightly.
i still stuck in the same stage(Patching system image unconditionally...).
i also try to flash stock rom 4.4.4 from motorola (from here: http://goo.gl/xAomMi) which succeeded, and then wipe device(factory reset and wipe dalvik cache, cache, system, Data) and install again cm-13.0-20160206-NIGHTLY-falcon, and it also didn't work.
i'm still get into the same message and stay there forever.
thanks for any help
** EDIT: http://forum.xda-developers.com/showpost.php?p=65237469&postcount=3
papandreoos said:
my device (moto G (falcon) XT1032) is a GPE device.
in the last 2 days i tried to install CM 13 on my device.
i tried 3 different recoveries - CWM, TWRP and CM recovery - to install cm-13.0-20160206-NIGHTLY-falcon (and yes, i checked before flashing, the SHA1).
in all those tryouts i always get into the sentence in the headline - Patching system image unconditionally... - and it just stays there forever.
one time i waited 40 minutes, and it still stayed on this message, and do nothing.
every time before flashing the rom, i wiped the device (dalvik cache, cache, system, Data).
i also try to flash the latest snapshot (cm-12.1-20151117-SNAPSHOT-YOG7DAO1K9-falcon) because i thought maybe there is a problem with the latest nightly.
i still stuck in the same stage(Patching system image unconditionally...).
i also try to flash stock rom 4.4.4 from motorola (from here: http://goo.gl/xAomMi) which succeeded, and then wipe device(factory reset and wipe dalvik cache, cache, system, Data) and install again cm-13.0-20160206-NIGHTLY-falcon, and it also didn't work.
i'm still get into the same message and stay there forever.
thanks for any help
Click to expand...
Click to collapse
Use Philz recovery and make sure you unlocked boot loader cleanly, if this Doesn't help try to flash some other ROM.
Best Of Luck
i also used philz_touch_6.58.7-falcon recovery.
still i got into the same problem i described in my first post.
p.s.
i forgot to mention this recovery in my first post, but after you suggested it, i remembered i used it already.
papandreoos said:
i also used philz_touch_6.58.7-falcon recovery.
still i got into the same problem i described in my first post.
p.s.
i forgot to mention this recovery in my first post, but after you suggested it, i remembered i used it already.
Click to expand...
Click to collapse
Try installing some other ROM.
[email protected] said:
Try installing some other ROM.
Click to expand...
Click to collapse
do you have a suggestion for good ROM (everything works) for moto g (xt1032), which has marshmallow in it?
papandreoos said:
do you have a suggestion for good ROM (everything works) for moto g (xt1032), which has marshmallow in it?
Click to expand...
Click to collapse
May be this helps
http://forum.xda-developers.com/showthread.php?t=3284323
Or
http://forum.xda-developers.com/showthread.php?t=3250449
---------- Post added at 01:17 AM ---------- Previous post was at 01:14 AM ----------
If you can't install this flash stock and check if you can flash any Zip (try SuperSU zip in my word) if this ain't successful try to type unlock boot loader commands again.
Best of luck.
[email protected] said:
May be this helps
http://forum.xda-developers.com/showthread.php?t=3284323
Or
http://forum.xda-developers.com/showthread.php?t=3250449
---------- Post added at 01:17 AM ---------- Previous post was at 01:14 AM ----------
If you can't install this flash stock and check if you can flash any Zip (try SuperSU zip in my word) if this ain't successful try to type unlock boot loader commands again.
Best of luck.
Click to expand...
Click to collapse
i tried now the AOSP rom in one of your links.
i wiped cache, dalvik cache, system and data and then continue to install the rom, but again it stuck in the same line as before and does nothing.
papandreoos said:
i tried now the AOSP rom in one of your links.
i wiped cache, dalvik cache, system and data and then continue to install the rom, but again it stuck in the same line as before and does nothing.
Click to expand...
Click to collapse
Flash back to stock and try to flash supersu zip from here if this doesn't work the problem must be while unlocking bootloader ,anyways was bootloader unlocked normally or you had any problems ?
https://download.chainfire.eu/696/SuperSU/
Flash via fast boot not some other flash able Zip
Best of luck.
[email protected] said:
Flash back to stock and try to flash supersu zip from here if this doesn't work the problem must be while unlocking bootloader ,anyways was bootloader unlocked normally or you had any problems ?
https://download.chainfire.eu/696/SuperSU/
Flash via fast boot not some other flash able Zip
Best of luck.
Click to expand...
Click to collapse
my bootloader is unlocked already.
before i tried to flash CM couple of days ago, i follow steps from CM wiki, and part of them is to unlock the bootloader.
here are the orders i followed(although it's for a different device (moto g 4g)), it worked great:
https://wiki.cyanogenmod.org/w/Install_CM_for_peregrine#Unlocking_the_device
if i get into fastboot mode (volume down + power) it tells me in yellow line: Device is UNLOCKED. Status Code: 3.
i also have root access.
papandreoos said:
my bootloader is unlocked already.
before i tried to flash CM couple of days ago, i follow steps from CM wiki, and part of them is to unlock the bootloader.
here are the orders i followed(although it's for a different device (moto g 4g)), it worked great:
https://wiki.cyanogenmod.org/w/Install_CM_for_peregrine#Unlocking_the_device
if i get into fastboot mode (volume down + power) it tells me in yellow line: Device is UNLOCKED. Status Code: 3.
i also have root access.
Click to expand...
Click to collapse
The metod sound the same...........Have you tried to flash stock ROM via Fast boot again?
[email protected] said:
The metod sound the same...........Have you tried to flash stock ROM via Fast boot again?
Click to expand...
Click to collapse
i forgot to mention that after every failure of flashing, i always get back to lollipop 5.1 GPE version with this helpfull tool:
http://forum.xda-developers.com/moto-g/general/gpe-lollipop-5-1-1click-installer-t3075522
so everything is OK in my phone.
i'm just frustrated i can't install newer OS.
papandreoos said:
i forgot to mention that after every failure of flashing, i always get back to lollipop 5.1 GPE version with this helpfull tool:
http://forum.xda-developers.com/moto-g/general/gpe-lollipop-5-1-1click-installer-t3075522
so everything is OK in my phone.
i'm just frustrated i can't install newer OS.
Click to expand...
Click to collapse
Try to flash KitKat for a while then flash CM 11 then any CM 12 then CM 13 I have have an similar error, whenever I try to flash another ROM the data partition doesn't format and then I have to do is to flash KitKat Stock then CM 11 then CM 12 then CM 13 .
Best Of Luck this should work.
---------- Post added at 08:25 AM ---------- Previous post was at 08:16 AM ----------
The tool isn't a good Idea I use to make an bat file and not customized a bit file of firmware if you don't know what it is I will give it to you .
Here , download the untouched version and flash via Fast boot if not completed find KitKat version :-
http://www.gimmickmag.com/restore-moto-g-xt1032-xt1033-xt1034-back-stock-firmware/
If you can't find there wait for FileFactory server to come up again it has all firmwares
[email protected] said:
Here , download the untouched version and flash via Fast boot if not completed find KitKat version :-
http://www.gimmickmag.com/restore-moto-g-xt1032-xt1033-xt1034-back-stock-firmware/
If you can't find there wait for FileFactory server to come up again it has all firmwares
Click to expand...
Click to collapse
i flashed 4.4.4 stock from here:
http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-rom-collection-t2854688
i used the untouched version:
Retail EU 4.4.4 Stock ROM (Untouched) (457mb)
https://docs.google.com/uc?id=0B6RNTe4ygItBVFlwN2pqWmV1VXc&export=download
so far it's working.
i boot into the stock and it's 4.4.4.
the screen is flickering but it's stock 4.4.4.
now i'm gonna try flash this latest snapshot of CM11:
cm-11-20140504-SNAPSHOT-M6-falcon.zip
from here:
https://download.cyanogenmod.org/?device=falcon
i now into fastboot mode, installing TWRP 3.0.0.0:
fastboot flash recovery twrp-3.0.0.0-falcon.img
success!
get into recovery now.
sha1 verified.
copy CM11 into phone
i'm still on TWRP.
i now wipe data, cache, dalvik cache and system.
done.
now i'll try flash CM11
WOW!!!
after couple of seconds (maybe 30-40) it's done.
i reboot into CM11 without a problem (just the flickering screen again, but never mind. i'm not planing to stay in CM11).
the android version in latest CM11 is 4.4.2
now i'm gonna try to flash CM12
get into recovery again.
sha1 verified.
copy cm-12.1-20151117-SNAPSHOT-YOG7DAO1K9-falcon into device.
wiping data, cache, dalvik cache and system again.
flashing!
not working
i again stuck in " "Patching system image unconditionally..." forever.
(going back to GPE 5.1)
Flash via Fast Boot it might be the problem.
[email protected] said:
Flash via Fast Boot it might be the problem.
Click to expand...
Click to collapse
you mean "adb sideload rom.zip"?
if yes, i already did that and it was stopped in 47 percent and sometime in 45 percent.
it stays there forever.
papandreoos said:
you mean "adb sideload rom.zip"?
if yes, i already did that and it was stopped in 47 percent and sometime in 45 percent.
it stays there forever.
Click to expand...
Click to collapse
No Flash Stock KitKat From Firmware via boot loader .
i think i'll pass.
i already flash kitkat and after that CM11 and it didn't help me to get into CM13.
i'm tired of flashing and restoring again and again.
thanks a lot for your help
As you wish...
I followed your steps too and i am exactly facing your problems, i am stuck in "patching system image unconditionally"...
Hey guys I'm new to owning this device and just wanted to know if I have to reflash my firmware after clean flash?
This is what I do
Wipe System/Data/Art/Cache
From there I Flash Firmware/ROM/gapps
Is the firmware step required? Or can I just skip that step once I alreday flashed it previously?
I'm asking this question because I've been having some major issues flashing roms where they flash successfully but frankly just don't boot. I'm just not sure if I'm doing this correctly.
ChainFires Son said:
Hey guys I'm new to owning this device and just wanted to know if I have to reflash my firmware after clean flash?
This is what I do
Wipe System/Data/Art/Cache
From there I Flash Firmware/ROM/gapps
Is the firmware step required? Or can I just skip that step once I alreday flashed it previously?
I'm asking this question because I've been having some major issues flashing roms where they flash successfully but frankly just don't boot. I'm just not sure if I'm doing this correctly.
Click to expand...
Click to collapse
Clean flash involves wiping
/system /data /dalvik /cache
Then flash ROM + gapps
If you flash current firmware it should show 241 baseband in About Phone. Only need to do it once. No need to do every time you flash. CM nightlies do include firmware in their zips so by default will flash the firmware or at least check if its updated every nightly.
Use TWRP 2.8.6.0 or 3.0.0-1 which are versions known to flash firmware correctly.
If you flashed COS12.1.1 fastboot zip at any point in time your data and cache partitions will be F2FS and only certain ROMs will work with that. AOSP based ROMs most likely won't boot.
Sent from my A0001 using Tapatalk
Renosh said:
Clean flash involves wiping
/system /data /dalvik /cache
Then flash ROM + gapps
If you flash current firmware it should show 241 baseband in About Phone. Only need to do it once. No need to do every time you flash. CM nightlies do include firmware in their zips so by default will flash the firmware or at least check if its updated every nightly.
Use TWRP 2.8.6.0 or 3.0.0-1 which are versions known to flash firmware correctly.
If you flashed COS12.1.1 fastboot zip at any point in time your data and cache partitions will be F2FS and only certain ROMs will work with that. AOSP based ROMs most likely won't boot.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Appreciate the the reply! I'm going to restore to stock, and do it all over and update the baseband/firmware from there. Just to be safe ?
It's been a while since I've touched my OPO since I've been using my OPT as my daily. I'm still on YNG1TAS2I3 on my OPO running stock everything. At the moment it is not rooted, with no custom recovery, but the bootloader IS unlocked. I also had xposed installed with some modules but I ran the xposed uninstaller arm.zip version in TWRP and removed the modules.
Is it possible to dirty flash YNG4PAS1N0 which is CM12.1 onto my OPO? I've tried installing TWRP and then fastbooting CM12.1 but it causes a bootloop. I had to re-fastboot flash CM12.0 to get out of it. I've tried it with TWRP 3.0.2.0 and TWRP 2.8.6.0. I also tried sideloading it but again-- bootloop. Reflashing CM12.0 causes CM recovery to rewrite TWRP even though I don't flash the recovery partition. So it took me a LONG time to get TWRP installed again for all these trials.
At this point is my only option to do a complete wipe and then flash? Even trying to run the OTA update for YNG4PAS1N0 causes a bootloop.
I think fastboot wipe the partition then flash it, else upgrade incrementally (I know it'd suck)
Transmitted via BACON
MZO said:
I think fastboot wipe the partition then flash it, else upgrade incrementally (I know it'd suck)
Transmitted via BACON
Click to expand...
Click to collapse
Well the problem is even incrementally updating it is kicking it into bootloop like I said.
crazykidguy said:
Well the problem is even incrementally updating it is kicking it into bootloop like I said.
Click to expand...
Click to collapse
Then
Instead of normal flashing you should fastboot erase <partition> and then flash it.
Transmitted via BACON
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.