Related
Hey guys been trying to work this out for the last 20 hours.
Now i followed the very good guides to put TWRP on the phone that worked fine tried to load cm10 latest nightly rom on kept bootlooping. so decided to give another rom ago.
used viper and it worked fine.
wanted to try and get cm10 working
So i have twrp 2.3.1
And latest cm-10-20121102-NIGHTLY-evita.zip
i wipe system, factory default cache. and the other cache.
go and install the rom all looks good, wipe caches and reboot.. than goes to the cool cm10 logo and loops there for AGES like 30 mins than i power cycled it and tried over.
with no working cm10 there i looked around and followed a guide to fastboot a new boot.img on from out of the cm10 zip.
this looked like it was going to work but still reboot and bootlooping.
can anyone help please.
AnThraXau said:
Hey guys been trying to work this out for the last 20 hours.
Now i followed the very good guides to put TWRP on the phone that worked fine tried to load cm10 latest nightly rom on kept bootlooping. so decided to give another rom ago.
used viper and it worked fine.
wanted to try and get cm10 working
So i have twrp 2.3.1
And latest cm-10-20121102-NIGHTLY-evita.zip
i wipe system, factory default cache. and the other cache.
go and install the rom all looks good, wipe caches and reboot.. than goes to the cool cm10 logo and loops there for AGES like 30 mins than i power cycled it and tried over.
with no working cm10 there i looked around and followed a guide to fastboot a new boot.img on from out of the cm10 zip.
this looked like it was going to work but still reboot and bootlooping.
can anyone help please.
Click to expand...
Click to collapse
Can't help you but I'm in the same situation. Even tried flashing back to 10/27, which had previously worked for me, and still stuck. Hmmm...
---------- Post added at 09:37 AM ---------- Previous post was at 09:00 AM ----------
OK, got it working.
For now, flash the boot.img from the 10/27 experimental.
Then you can flash the 1102 nightly.
After flashing the ROM, wipe cache, then dalvik. Reboot.
If still stuck, reboot to recovery, wipe cache then dalvik again and reboot.
Hope that works for you too.
I'm on try number two with this after recovering. I'm thinking I may not have downloaded the file properly. If it freezes up again, I'll try installing the 11-01-2012 experimental. Think that would work?
Edit: Same problem with 11-1-2012 Nightly. Annoying.
GuyIncognito721 said:
Can't help you but I'm in the same situation. Even tried flashing back to 10/27, which had previously worked for me, and still stuck. Hmmm...
---------- Post added at 09:37 AM ---------- Previous post was at 09:00 AM ----------
OK, got it working.
For now, flash the boot.img from the 10/27 experimental.
Then you can flash the 1102 nightly.
After flashing the ROM, wipe cache, then dalvik. Reboot.
If still stuck, reboot to recovery, wipe cache then dalvik again and reboot.
Hope that works for you too.
Click to expand...
Click to collapse
Method didn't work. Any other ideas?
I'm in the exact same boat... CM10, aokp, nokturnal... all bootooping. The only one that works is the 540mb nokturn xi40, which is 4.0.4 and not really what i'm trying to do here...
I tried the CM updater, like I have been for the nightlies, except, now I'm stuck and a bootloop and I can't get into recovery. I go from the bootloader and select recovery and it takes me to the same screen that the updater days where it says:
Updating partition details....
Running boot script....
Finished running boot script.
Installing zip file '/sdcard/cmupdater/cm-10-20121110-NIGHTLY-evita.zip
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
This is the screen I get every time I flash nightlies, then I reboot and it usually comes up. Now when I do this, it puts me in a bootloop (HTC screen comes up, goes dark, no Cyanogen screen, then reboots to the HTC screen)...any thoughts on what I need to do to get my phone to work again?
I upgraded to CM10 from the original OS and I am using the latest version to root my phone, I am using TWRP. Anyway, Everything worked fine, I rooted the phone, I upgraded to CM10. I want to go back to the original OS. I downloaded [ROM][8/3] - Stock Rooted AT&T 2.20.502.7 - Android 4.0.4 - Odex or De-Odex, I got the ODEX version, I flashed it to my phone but its just hangs at the HTC One X Splash screen with the red lettering. What am I missing here? I can get back into recovery and I backed up my old ROM just in case.
How long are you letting it hang for? Try 2 more power downs and power ons. The first few times it took about 5 min to load.
mgutierrez87 said:
How long are you letting it hang for? Try 2 more power downs and power ons. The first few times it took about 5 min to load.
Click to expand...
Click to collapse
It just shuts off and turns back on again, it basically loops. Did I download the wrong file maybe? Is there a specific ROM I need other than the one I mentioned earlier?
Boot into recovery and wipe your cache and dalvik cache again
mgutierrez87 said:
Boot into recovery and wipe your cache and dalvik cache again
Click to expand...
Click to collapse
Factory reset, wipe system, flash ROM, wipe cache and delvik.
Any time you go from non sense to sense or vise versa you have to wipe the system and factory reset.
Sent from my One X using xda app-developers app
This was the ROM that worked when i did it.
http://forum.xda-developers.com/showthread.php?t=1872842
---------- Post added at 04:53 AM ---------- Previous post was at 04:46 AM ----------
Myrder said:
Factory reset, wipe system, flash ROM, wipe cache and delvik.
Any time you go from non sense to sense or vise versa you have to wipe the system and factory reset.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
He mentioned in another thread that he did those steps. The only other thing I would try is to flash the boot.IMG from the ROM you want to use
I still want to keep my phone rooted. This wont kill the root right?
No the ROM posted above is stock rooted
But if you made a backup as you said in the first post why are you not just restoring the backup?
Sent from my Nocturnalized One XL using Forum Runner
Basically where I am right now. I downloaded the original OS, by following instructions, I have managed to delete my backed up rom of CM10 that i backed up earlier. I was able to FLASH the OS I wanted, I flashed the boot.img file using fastboot. I restarted the phone and now its just stuck on the HTC Quietly Brilliant screen with the red lettering at the bottom. It doesn't restart or anything, it just hangs there. What am I missing here guys? ):
I'm going to install cm10 right now them go back to stock rooted and see what's up with this
There's no issues going back and forth. You probably flashed a bad ROM
yea, your most likely just doing it wrong. you need to do a full wipe and flash boot.img
answer: oh yea cant flash the stock rom using twrp 2.3.1.0 you will need to flash twrp 2.2.2.0 then flash stock rom. that is actually most likely your problem.
What hboot are you on? If you separately flashed boot.img from CM10 via fastboot, you might need to again separately flash the boot.img from the stock ROM. Also remember that the procedure employed to root 2.20 is substantially different from the root procedure to root the previous build of stock. Not sure what software you rooted, or whether this would pose a problem, but it's a consideration.
Another option is to just restore to stock via RUU and re-unlock, re-root, if nothing else works. Getting stuck on HTC splash screen sounds like a boot.img issue. Good luck.
DvineLord said:
answer: oh yea cant flash the stock rom using twrp 2.3.1.0 you will need to flash twrp 2.2.2.0 then flash stock rom. that is actually most likely your problem.
Click to expand...
Click to collapse
Really? Why is that?
Just curious, I haven't heard this before. Is this a known issue with flashing the 2.20 stock ROM? I haven't seen any cases of ROMs (stock rooted or otherwise) being sensitive to version of TWRP. At least not the case of having to use an older version (keeping TWRP updated is usually the recommendation).
Of course, just because I haven't heard of it, doesn't mean it didn't happen!
Did you fastboot flash boot boot.img?
Sent from my HOX running Cyanogenmod 10
redpoint73 said:
Really? Why is that?
Just curious, I haven't heard this before. Is this a known issue with flashing the 2.20 stock ROM? I haven't seen any cases of ROMs (stock rooted or otherwise) being sensitive to version of TWRP. At least not the case of having to use an older version (keeping TWRP updated is usually the recommendation).
Of course, just because I haven't heard of it, doesn't mean it didn't happen!
Click to expand...
Click to collapse
im assuming the age of the stock rooted would have conflicts with the new twrp. i have had problems with roms not flashing with newest twrp. it is also a known problem since twrp 2.3.1.0 release.
[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"...
Ok... As you can see from this thread,
https://forum.xda-developers.com/on...en-restore-t3804734/post76832485#post76832485
I soft bricked my phone after trying to restore a backup in official TWRP.
I followed this tutorial https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-unlock-bootloader-flash-twrp-t3792643
And jumped over to this tutorial https://forum.xda-developers.com/oneplus-6/how-to/guide-how-to-install-official-twrp-t3801558 per this post in the tutorial https://forum.xda-developers.com/showpost.php?p=76564290&postcount=5 note that this post points to another way of getting TWRP. The link I went to is how to install OFFICIAL TWRP.
And jumped back to the original tutorial for the rest. I'm scared to death now to try and test the restore functionality in TWRP. Has anyone successfully restored a backup? If so, what steps did they take to get the backup and what steps did they take restoring backup? What partitions did the check.mark during backup and what partitions did they check mark during restore? And do you need to do anything with changing the a/b slots????
Edited to add correct link to install official TWRP.
vinnievegas said:
Ok... As you can see from this thread,
https://forum.xda-developers.com/on...en-restore-t3804734/post76832485#post76832485
I soft bricked my phone after trying to restore a backup in official TWRP.
I followed this tutorial https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-unlock-bootloader-flash-twrp-t3792643
And jumped over to this tutorial per this post in the tutorial https://forum.xda-developers.com/showpost.php?p=76564290&postcount=5
And jumped back to the original tutorial for the rest. I'm scared to death now to try and test the restore functionality in TWRP. Has anyone successfully restored a backup? If so, what steps did they take to get the backup and what steps did they take restoring backup? What partitions did the check.mark during backup and what partitions did they check mark during restore? And do you need to do anything with changing the a/b slots????
Click to expand...
Click to collapse
Flash stock ROM in TWRP, flash TWRP again. It won't touch data partition but you can restore just your data partition from your TWRP backup. Boot into system once, then reboot recovery and flash magisk if you want root. All modules you have will be back and active after that.
---------- Post added at 01:34 AM ---------- Previous post was at 01:33 AM ----------
On the off chance TWRP says there is no OS after flashing stock ROM and TWRP, ignore messages and boot anyway. It will restore your phone without losing all data.
mikex8593 said:
Flash stock ROM in TWRP, flash TWRP again. It won't touch data partition but you can restore just your data partition from your TWRP backup. Boot into system once, then reboot recovery and flash magisk if you want root. All modules you have will be back and active after that.
---------- Post added at 01:34 AM ---------- Previous post was at 01:33 AM ----------
On the off chance TWRP says there is no OS after flashing stock ROM and TWRP, ignore messages and boot anyway. It will restore your phone without losing all data.
Click to expand...
Click to collapse
I'll try this and if this works and is in deed the process we need to follow until TWRP can just do what it's supposed to, then shouldn't this stuff be in the tutorials or have the OPs actually pulled this off like it's supposed to be?
vinnievegas said:
I'll try this and if this works and is in deed the process we need to follow until TWRP can just do what it's supposed to, then shouldn't this stuff be in the tutorials or have the OPs actually pulled this off like it's supposed to be?
Click to expand...
Click to collapse
Just too lazy to make an official thread, I guess. It will work.
mikex8593 said:
Flash stock ROM in TWRP, flash TWRP again. It won't touch data partition but you can restore just your data partition from your TWRP backup. Boot into system once, then reboot recovery and flash magisk if you want root. All modules you have will be back and active after that.
---------- Post added at 01:34 AM ---------- Previous post was at 01:33 AM ----------
On the off chance TWRP says there is no OS after flashing stock ROM and TWRP, ignore messages and boot anyway. It will restore your phone without losing all data.
Click to expand...
Click to collapse
mikex8593 said:
Just too lazy to make an official thread, I guess. It will work.
Click to expand...
Click to collapse
So to be clear, I get the roms from here under signed flashable zips?
https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-mirrors-official-oxygen-os-t3792244
vinnievegas said:
So to be clear, I get the roms from here under signed flashable zips?
https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-mirrors-official-oxygen-os-t3792244
Click to expand...
Click to collapse
Yep. You can use the method with any of those zips.
I restored boot, system and data and ended in twrp loop. Flashing magisk revived it.
Sent from my ONEPLUS A6003 using Tapatalk
tdamocles said:
I restored boot, system and data and ended in twrp loop. Flashing magisk revived it.
Sent from my ONEPLUS A6003 using Tapatalk
Click to expand...
Click to collapse
Did you do it like he instructed above?
Flash rom
Flash TWRP
Restore boot, system, and data
Reboot?
vinnievegas said:
Did you do it like he instructed above?
Flash rom
Flash TWRP
Restore boot, system, and data
Reboot?
Click to expand...
Click to collapse
To tell you the truth I didn't even see the other post and was trying to get the renovate magisk module working in the process. It was the first time for me trying to restore a twrp backup because I borked something in the renovate magisk install. Like I said, I tried restoring boot, system and data and ended in a bootloop twrp situation. I figured what the heck, let's try flashing magisk root again and see what happens, and voila it work.
Yes me too twrp on oneplus 6 are buggy when I had restore all system part my Phone enter in bootloop [emoji58]
Actual Device : OnePlus 6 Past Devices : Galaxy S6, Xperia Z2, Huawei P7, Nokia 620
mikex8593 said:
Flash stock ROM in TWRP, flash TWRP again. It won't touch data partition but you can restore just your data partition from your TWRP backup. Boot into system once, then reboot recovery and flash magisk if you want root. All modules you have will be back and active after that.
---------- Post added at 01:34 AM ---------- Previous post was at 01:33 AM ----------
On the off chance TWRP says there is no OS after flashing stock ROM and TWRP, ignore messages and boot anyway. It will restore your phone without losing all data.
Click to expand...
Click to collapse
Ok. Worked like a charm. Thank you so much. I tested all this without any lock screen security. Now I'm wondering if this procedure works with backups with lock screen security.
mikex8593 said:
Flash stock ROM in TWRP, flash TWRP again. It won't touch data partition but you can restore just your data partition from your TWRP backup. Boot into system once, then reboot recovery and flash magisk if you want root. All modules you have will be back and active after that.
---------- Post added at 01:34 AM ---------- Previous post was at 01:33 AM ----------
On the off chance TWRP says there is no OS after flashing stock ROM and TWRP, ignore messages and boot anyway. It will restore your phone without losing all data.
Click to expand...
Click to collapse
black_file said:
Yes me too twrp on oneplus 6 are buggy when I had restore all system part my Phone enter in bootloop [emoji58]
Actual Device : OnePlus 6 Past Devices : Galaxy S6, Xperia Z2, Huawei P7, Nokia 620
Click to expand...
Click to collapse
tdamocles said:
To tell you the truth I didn't even see the other post and was trying to get the renovate magisk module working in the process. It was the first time for me trying to restore a twrp backup because I borked something in the renovate magisk install. Like I said, I tried restoring boot, system and data and ended in a bootloop twrp situation. I figured what the heck, let's try flashing magisk root again and see what happens, and voila it work.
Click to expand...
Click to collapse
Ok. Just tried what tdamocles did. But I've been wiping before restore. I then just restore and select system, boot, and data. I did not reflash TWRP. Rebooted and everything was good. Still had root and didn't need to reflash magisk. Was also able to reboot back into TWRP, so there was no need to reflash TWRP. But.... I think that is due to not flashing the stock room first. I'm assuming that if you reflash stock that you will indeed have to reflash TWRP. So, conclusion... If you restore system, boot, and data then no need to reflash TWRP and in my case no need to reflash magisk. Again, this is without lock screen security. My next test will be with lock screen security unless someone posts a negative result before I do.
vinnievegas said:
Ok. Just tried what tdamocles did. But I've been wiping before restore. I then just restore and select system, boot, and data. I did not reflash TWRP. Rebooted and everything was good. Still had root and didn't need to reflash magisk. Was also able to reboot back into TWRP, so there was no need to reflash TWRP. But.... I think that is due to not flashing the stock room first. I'm assuming that if you reflash stock that you will indeed have to reflash TWRP. So, conclusion... If you restore system, boot, and data then no need to reflash TWRP and in my case no need to reflash magisk. Again, this is without lock screen security. My next test will be with lock screen security unless someone posts a negative result before I do.
Click to expand...
Click to collapse
You will not be able to get past encrption if you decrypt in TWRP and restore. It essentially forgets encryption key.
mikex8593 said:
You will not be able to get past encrption if you decrypt in TWRP and restore. It essentially forgets encryption key.
Click to expand...
Click to collapse
Update...
Just performed a backup with lock screen security and was able to restore the backup choosing system, boot, and data. No reflashing of TWRP or magisk. Not sure if needed but I've been performing basic wipe before all my restores. Still able to boot back into TWRP and still had root.
mikex8593 said:
You will not be able to get past encrption if you decrypt in TWRP and restore. It essentially forgets encryption key.
Click to expand...
Click to collapse
Check my post above. I edited it to quote you.
I must also note that I'm using official TWRP. I edited my first post to reflect the link I used when jumping out if the tutorial and back.
vinnievegas said:
Update...
Just performed a backup with lock screen security and was able to restore the backup choosing system, boot, and data. No reflashing of TWRP or magisk. Not sure if needed but I've been performing basic wipe before all my restores. Still able to boot back into TWRP and still had root.
Click to expand...
Click to collapse
Nice.
I have restored from twrp a couple times now with no problem.. I did get the message saying can't mount system or something like that, ok I went into the mount options and mounted system after that the restore worked perfectly and I could boot back into the rom and back into twrp after.
Restored mine yesterday too, all files checked when backup, deleted lockscreen settings before, few bootloops at the beginning, until phone changed slot, then booted into system. Cheers!
primus19 said:
Restored mine yesterday too, all files checked when backup, deleted lockscreen settings before, few bootloops at the beginning, until phone changed slot, then booted into system. Cheers!
Click to expand...
Click to collapse
Not necessary to check all partitions. This only results in a huge nandroid file.
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.