I've got a T-Mobile phone with stock updated to the last version, with TWRP 2.6.3.0 and root. Everything worked fine for a couple of months.
A month ago the phone started to boot loop with no apparent reason. I've wiped everything, re installed stock, rooted and used the phone again. I've thought it might be an app updated that screwed something.
Anyway, I've only got the basic apps on the phone and today it happened again. I've read that I need to boot into bootloader and selecr "CLEAR STORAGE", I've tried that but it goes into recovery and there I can only wipe the data. I've did that and rebooted and it didn't help.
Any other ways to fix this without re installing the rom?
I think that if you use the clear storage option, you will have to reinstall the rom. I believe it wipes the system partition as well.
If you want to do this, you should flash the stock recovery (get it here)
Go into the bootloader and select the clear storage option.
Then you can flash CWM or TWRP recovery again and install the ROM.
Hi,
I recently tried to install a custom rom (Resurrection Remix) on the latest EMUI version which resulted in my device not booting anymore.
After several tries I gave up and wanted to simply use stock with root.
I installed SuperSU, but that did not show up in the application menu.
After that I recovered system and boot from a recent full backup and installed magisk.
That resulted in the device not booting anymore at all. This condition stays now.
I then reinstalled the stock rom via dload method, with a factory reset after, but it then started to be stuck in the blue screen with the honor logo.
Is there anything I can do? TWRP is gone, I only get the stock EMUI recovery.
This happened to mee too. You should try a wipe data and cache from recovery, then reboot. It worked for me.
P.s i flashed a stock recovery don't know if TWRP will work the same, try.
After the dload update the stock recovery is installed again, I wiped data and cache already, but that didnt make it work too :/
EDIT: Found the error: The /data partition is unusable in it's current state (f2fs). Is F2FS the default filesystem for /data or do I need to change it to ext4 or something?
I was running lineage-16.0-20181203_184022-UNOFFICIAL-enchilada just fine with open gapps nano and Magisk 17.1.
I attempted to upgrade to lineage-16.0-20181208_183559-UNOFFICIAL-enchilada, but I ran into issues with gapps force closing.
I attempted to restore my TWRP nandroid backups, but the attempts at restoring them just put me in a bootloop into TWRP.
Therefore, I am attempting to get back to OOS 9.0.2, OnePlus6Oxygen_22_OTA_027_all_1810260000_d46787d2c9, with a clean flash, following the process:
Fastboot into TWRP with fastboot boot twrp-3.2.3-x_blu_spark_v9.86_op6.img
Wipe -> Advanced Wipe -> Cache, System, Data, Internal Storage
adb push OnePlus6Oxygen_22_OTA_027_all_1810260000_d46787d2c9.zip and twrp-3.2.3-x_blu_spark_v9.86_op6.zip
Install -> OOS 9.0.2 and then TWRP
Reboot into System
No matter how many times I try this, the first boot fails with a vibration from the phone and it reboots into the blu_spark TWRP.
I have also tried the above process from inside the installed TWRP instead of from a fastbooted TWRP. I have also tried the above process with lineage-16.0-20181203_184022-UNOFFICIAL-enchilada.zip instead of OOS.
What could possibly be wrong? Isn't this a completely clean install?
MaxRabbit said:
I was running lineage-16.0-20181203_184022-UNOFFICIAL-enchilada just fine with open gapps nano and Magisk 17.1.
I attempted to upgrade to lineage-16.0-20181208_183559-UNOFFICIAL-enchilada, but I ran into issues with gapps force closing.
I attempted to restore my TWRP nandroid backups, but the attempts at restoring them just put me in a bootloop into TWRP.
Therefore, I am attempting to get back to OOS 9.0.2, OnePlus6Oxygen_22_OTA_027_all_1810260000_d46787d2c9, with a clean flash, following the process:
Fastboot into TWRP with fastboot boot twrp-3.2.3-x_blu_spark_v9.86_op6.img
Wipe -> Advanced Wipe -> Cache, System, Data, Internal Storage
adb push OnePlus6Oxygen_22_OTA_027_all_1810260000_d46787d2c9.zip and twrp-3.2.3-x_blu_spark_v9.86_op6.zip
Install -> OOS 9.0.2 and then TWRP
Reboot into System
No matter how many times I try this, the first boot fails with a vibration from the phone and it reboots into the blu_spark TWRP.
I have also tried the above process from inside the installed TWRP instead of from a fastbooted TWRP. I have also tried the above process with lineage-16.0-20181203_184022-UNOFFICIAL-enchilada.zip instead of OOS.
What could possibly be wrong? Isn't this a completely clean install?
Click to expand...
Click to collapse
Try installing magisk too.
mikex8593 said:
Try installing magisk too.
Click to expand...
Click to collapse
Thanks for the suggestion. Tried installing magisk in between OOS and the TWRP, and then also tried installing OOS, TWRP, rebooting, and installing magisk. No luck either way.
Well, this was a nightmare. Finally fixed it by:
fastbooting into twrp
wiping everything in twrp
flashing oos 9.0.2
NOT installing twrp
bootlooping into oneplus recovery
clearing ALL data through oneplus recovery (after backing up via ADB)
reboot
phone booted up just fine
Wow. Never seen those particular steps mentioned.
After that, I was able to flash OOS 9.0.2 again, then flash lineage-16.0-20181203_184022-UNOFFICIAL-enchilada & TWRP, boot LOS, reboot into TWRP, wipe everything, flash lineage-16.0-20181203_184022-UNOFFICIAL-enchilada again, boot into LOS, reboot into TWRP, restore my system, data, and boot backups from TWRP, and I'm finally back up and running with a fully working backup.
MaxRabbit said:
Well, this was a nightmare. Finally fixed it by:
fastbooting into twrp
wiping everything in twrp
flashing oos 9.0.2
NOT installing twrp
bootlooping into oneplus recovery
clearing ALL data through oneplus recovery (after backing up via ADB)
reboot
phone booted up just fine
Wow. Never seen those particular steps mentioned.
After that, I was able to flash OOS 9.0.2 again, then flash lineage-16.0-20181203_184022-UNOFFICIAL-enchilada & TWRP, boot LOS, reboot into TWRP, wipe everything, flash lineage-16.0-20181203_184022-UNOFFICIAL-enchilada again, boot into LOS, reboot into TWRP, restore my system, data, and boot backups from TWRP, and I'm finally back up and running with a fully working backup.
Click to expand...
Click to collapse
this could have been done in twrp. all you had to do was format data
the correct way is this.
fastbooting into twrp
flashing oos 9.0.2
flashing twrp, to keep twrp.
format data.
install any mod you want, like root.
reboot
this is require only when going from aosp to oos again.
MrSteelX said:
this could have been done in twrp. all you had to do was format data
the correct way is this.
fastbooting into twrp
flashing oos 9.0.2
flashing twrp, to keep twrp.
format data.
install any mod you want, like root.
reboot
this is require only when going from aosp to oos again.
Click to expand...
Click to collapse
How come that would have worked, but wiping system and data and then installing OOS 9.0.2 doesn't? Shouldn't you end up at the same point either way, with a clean OOS 9.0.2 in system and wiped data?
Format is the answer.
MaxRabbit said:
How come that would have worked, but wiping system and data and then installing OOS 9.0.2 doesn't? Shouldn't you end up at the same point either way, with a clean OOS 9.0.2 in system and wiped data?
Click to expand...
Click to collapse
just simply flash oss9.0.2 two time using twrp then get hold of 9.0.2 boot img go back to twrp and the select flash image flash the image and let it boot.
if it works toss a thanks.
MaxRabbit said:
Well, this was a nightmare. Finally fixed it by:
fastbooting into twrp
wiping everything in twrp
flashing oos 9.0.2
NOT installing twrp
bootlooping into oneplus recovery
clearing ALL data through oneplus recovery (after backing up via ADB)
reboot
phone booted up just fine
Wow. Never seen those particular steps mentioned.
After that, I was able to flash OOS 9.0.2 again, then flash lineage-16.0-20181203_184022-UNOFFICIAL-enchilada & TWRP, boot LOS, reboot into TWRP, wipe everything, flash lineage-16.0-20181203_184022-UNOFFICIAL-enchilada again, boot into LOS, reboot into TWRP, restore my system, data, and boot backups from TWRP, and I'm finally back up and running with a fully working backup.
Click to expand...
Click to collapse
Thank you for this. I was trying to dirty flash 9.0.2 to fix a notification issue and ended up in the same situation as you. Format ended up fixing it. Only crappy part is I lost about all my text messages with my SO. Google said it has a 2mb backup for SMS so I'm hoping it got all 30k+ of it
MrSteelX said:
this could have been done in twrp. all you had to do was format data
the correct way is this.
fastbooting into twrp
flashing oos 9.0.2
flashing twrp, to keep twrp.
format data.
install any mod you want, like root.
reboot
this is require only when going from aosp to oos again.
Click to expand...
Click to collapse
Tried this and it ended up causing the exact same problem. The folks installing the new OB8/9 seems to be having similar issues. Not sure what's going on.
its because of security patch. 9.0.2 has nov sec patch, lineage you flashed has dec sec patch. i have experienced this in pixel rom. just flash lineage Nov build, then wipe data and system and flash OOS 9.0.2 and twrp.
do a clean flash
MaxRabbit said:
I was running lineage-16.0-20181203_184022-UNOFFICIAL-enchilada just fine with open gapps nano and Magisk 17.1.
I attempted to upgrade to lineage-16.0-20181208_183559-UNOFFICIAL-enchilada, but I ran into issues with gapps force closing.
I attempted to restore my TWRP nandroid backups, but the attempts at restoring them just put me in a bootloop into TWRP.
Therefore, I am attempting to get back to OOS 9.0.2, OnePlus6Oxygen_22_OTA_027_all_1810260000_d46787d2c9, with a clean flash, following the process:
Fastboot into TWRP with fastboot boot twrp-3.2.3-x_blu_spark_v9.86_op6.img
Wipe -> Advanced Wipe -> Cache, System, Data, Internal Storage
adb push OnePlus6Oxygen_22_OTA_027_all_1810260000_d46787d2c9.zip and twrp-3.2.3-x_blu_spark_v9.86_op6.zip
Install -> OOS 9.0.2 and then TWRP
Reboot into System
No matter how many times I try this, the first boot fails with a vibration from the phone and it reboots into the blu_spark TWRP.
I have also tried the above process from inside the installed TWRP instead of from a fastbooted TWRP. I have also tried the above process with lineage-16.0-20181203_184022-UNOFFICIAL-enchilada.zip instead of OOS.
What could possibly be wrong? Isn't this a completely clean install?
Click to expand...
Click to collapse
You know if all else fails you could always download the Qualcomm MSM tool and boot into Qualcomm mode (with the phone off hold vol down button for about 10-15 seconds and plug into computer), you won't see anything on the screen, load up the tool and it shall put u back to full stock. This will solve all and any sort of bricking which if you flash alot you will by default probably learn how to use
fastboot into twrp
Flash TWRP within twrp
Format all data.
Reboot recovery
transfer OOS
Flash OOS
Flash TWRP
Reboot recovery
Flash OOS
Flash TWRP
Reboot recovery
Flash kernel/magisk/etc
Reboot system.
I just want to tell you that I love you. The format data finally fixed this for me.
MrSteelX said:
this could have been done in twrp. all you had to do was format data
the correct way is this.
fastbooting into twrp
flashing oos 9.0.2
flashing twrp, to keep twrp.
format data.
install any mod you want, like root.
reboot
this is require only when going from aosp to oos again.
Click to expand...
Click to collapse
heelo guys
im having a problems flashiing roms. i tryed Paranandroid, RR and crDroid...
after i flash them i get bootloop into TWRP. whac can i be doing wrong?
the steps i do are this:
flash ROM -Flash TWRP - REBOOT to TWRP - Flash Gapps - Flash Magisk - Then bootloop
can anyone please help me?
anyone? please?
first install OOS 10 on both slots (i have open beta 4)..than boot to OOS 10, not setup! Then boot TWRP and factory reset, not FORMAT DATA!!! Then reboot TWRP and install ROM, TWRP, reboot, install Gapps and Magisk (optional)
mcboums said:
first install OOS 10 on both slots (i have open beta 4)..than boot to OOS 10, not setup! Then boot TWRP and factory reset, not FORMAT DATA!!! Then reboot TWRP and install ROM, TWRP, reboot, install Gapps and Magisk (optional)
Click to expand...
Click to collapse
hello mate
and when i install Rom, do i need to install on both slots or i can have one has backup (its what i have been doing till now)?
and when i factory reset, what will i lose?
Well, it is difficult to say. Usually, every ROM has its thread, its instructions and its community that helps with problems related to installing that ROM.
It could be a few things:
1) I do not see any mention about wiping data. Usually you need to wipe data and wipe system partition in twrp before you install a new ROM. Maybe that is the issue. However, what you need to wipe is ROM specific.
2) Check prerequisites, what ROM version you need to be running before you flash. Sometimes that matters.
3) OnePlus 6 has these A/B slots that I do not fully understand. From what I have read, if you are running on slot A, update installs on slot B, and then you reboot to slot B and cycle continues. BUT DO NOT TRUST ME ON THIS. You should read yourself. Anyway, sometimes people recommend flashing both slots A and B. For some ROMs. For LineageOS, for example, that is not necessary.
oh, factory reset damn i would want to configure everything again
I think first.
You have to WIPE data, all. Factory wipe option.
Then boot into twrp
First, flash OOS, followed by TWRP
Reboot to Recovery using twrp itself.
And then again flash OOS and TWRP.
Reboot to recovery again (using the option in twrp itself)
Finally, then install your rom followed by gapps etc etc
Then it should work....
is there anyway to do this without factory reset?
no