Develop Bugs

Stuck at Logo after flashing rom [fixed] > solution!

Edit: solution added
problem:
after flashing a rom (in my case OP3lite or FreedomOS) you can't get past the boot logo
you have access to TWRP, so you can restore nandroid or flash flashable stock OxygenOS packages (tutorial here)
solution:
wipe: Dalvik /ART Cache, Cache, Data, System
flash your rom
try to boot (most likely will get stuck at boot logo)
boot into TWRP > Advanced > Fix Contexts, and swipe to Fix Contexts
Reboot
(wait a while, it might take a few minutes till it boots)
___________________________________________
original post:
hi,
I'm running official OxygenOS 3.1.3.
Rooted (systemless) , TWRP installed.
I don't have any problems on my rom, but everytime I flash a rom I get stuck at the boot logo.
I can just force reboot, goto twrp and restore my nandroid backup, and my phone works fine again.
But I can't flash any rom.
tried this:
Dirty flash OP3Lite rom - stuck at boot logo
wipe and install OP3Lite rom - stuck at boot logo
Restored nandroid backup, factory format, wipe and install OP3Lite rom - stuck at boot logo
wipe and install FreedomOS - stuck at boot logo
Restored nandroid backup, factory format, wipe and install FreedomOS - stuck at boot logo
wipe, Format userdata throught fastboot, install FreedomOS - stuck at boot logo
update to OxygenOS 3.2.1 (flashable zip throught twrp)
wipe and install FreedomOS - stuck at boot logo
Both roms I tried are OxygenOS 3.2.1 stock based, my problem is most likely not due to the rom I want to flash.
Anyone knows a solution for this?
is it possible that systemless root causes this problem?

are you encrypted? that might be the issue.
backup your internal sd data then go to fastboot and fastboot format userdata then flash the rom you want

Abaddon said:
are you encrypted? that might be the issue.
backup your internal sd data then go to fastboot and fastboot format userdata then flash the rom you want
Click to expand...
Click to collapse
I never did format my userdata throught fastboot, so I might be encrypted.
I'll try tomorrow and let you know if that was the solution.

@Abaddon I format my userdata throught fastboot (fastboot format userdata), but still roms wont go past the Logo . any other idea?

did you full wipe?
wiped /system too before flashing a rom then u go and flash the rom + gapps if needed
how long was it at the boot logo? no animation correct?

did u advance wipe - data, caches, system instead of factory wipe, try it 3 times

I did a few wipe 3 times, still stuck at logo.
I get stuck on this logo, never reboot, just get stuck there.
I noticed that it does flash the rom, cause if I restore my nanodroid backup layers and adblock is added.
I also get zero error while flashing in twrp.

I fixed it .
did a fill whipe, then flashed feedomOS, then tried to boot, didnt get past the logo, booted into recovery, selected "fix Contexts" and then rebooted, started without any problem .

doesent work for me..!! any help

Same here this issue keeps occuring again and again. then i always have to follow mega unbrick guide

Resurrection ROM 7.1.1 stuck at logo after every restore
nikhilsnigam said:
Same here this issue keeps occuring again and again. then i always have to follow mega unbrick guide
Click to expand...
Click to collapse
Faced this issue every time I restore any nandroid on one plus 3. It stucks at rotating resurrection logot . Even tried fix contents from TWRP, no output. Please help without a functional TWRP backup and restore - phone is useless. Only everytime mega unbrick guide needs to be repeated with painful reinstall of apps

hello guys. sorry if I'm a bit slow on this topic. I'm using the the op3t A3010 version (not dure whether I'm at the right forum or not lol) Recently I updated my phone to the new 4.1.7, in which I had already rooted the phone before with magisk v12. But right after the update, as usual, the phone will unroot and yes I did root the phone back by using the magisk v13.0 version. But it failed the safety net. So after a few 'research', I installed the superuser just in case that the safety net will work this time. But this is when it all went wrong. The phone did restart back to factory settings, but the phone is not rooted (checked by using the rootchecker app) So again, I'm back to the twrp recovery, clean wipe all the data, with hope that I can start from scratch which is from installing the magisk all over again. But after this step, it stuck at the boot logo for like more than half an hour. Than at this moment, I restart my phone back to recovery mode by long pressing the power button, and when I try to install both the magisk 12 and 13 version, there is a line of error code on the screen. There's a site that says simply go to the advance setting on the twrp interface, check fix contents and ur phone will be as good as new. After done doing that, I'm now stuck with a phone with no os installed and about 38% battery left. Can anyone help me here? This is the only phone that I had :crying: Urgent help needed here guys

Unless your original installation is without storage encryption (no dm-verity) this will happen. So next time install custom rom after flashing OB22 firmware+modem, then boot patch for dm-verity followed with custom rom and gapps then boot without wipe

i have the same problem but with p9 lite : when i tried a flash lineageOS or ResurrectionRemix my phone stucks at boot logo and when i flash the original os my phone works perfectly
sorry for my english

washichi said:
I fixed it .
did a fill whipe, then flashed feedomOS, then tried to boot, didnt get past the logo, booted into recovery, selected "fix Contexts" and then rebooted, started without any problem .
Click to expand...
Click to collapse
How long did you wait?

washichi said:
Edit: solution added
boot into TWRP > Advanced > Fix Contexts, and swipe to Fix Contexts
Reboot
(wait a while, it might take a few minutes till it boots)
Click to expand...
Click to collapse
What is the work around for CWM v6.0.5.1 Philz Touch6; it does not have Fix contexts under Advanced Functions
My issue: Tecno Spark K7 stuck at boot logo after flashing with ported ROM from Infinix XOS Chameleon . Both kernels match

This is EXACTLY my issue with the galaxy s9 plus. Gonna try the solution you wrote tommorow.

i have the same problem with galaxy s5 and the solution mentioned in the thread did not work with me.

im having the same issue but in lenovo z5 pro gt

PauloVillaflor said:
im having the same issue but in lenovo z5 pro gt
Click to expand...
Click to collapse
Search for answers HERE and if not successful, create a thread in the Q&A forum there.
You may not get any help here since this is the OP 3 forum.

Anyone having trouble installing TWRP on build NBD90W?

Greetings!
After installing the October security updates (bringing my device to NBD90W) I decided to unlock my bootloader and install TWRP. However, I can't seem to get TWRP to "stick" - flashing seems fine, and rebooting into bootloader and into TWRP recovery all proceeds fine. However, as soon as I reboot my system, TWRP seems to disappear and the stock recovery reappears.
Am I doing something wrong here? This is the exact process I followed on my Nexus 7, without any problems.

jerethi said:
Greetings!
After installing the October security updates (bringing my device to NBD90W) I decided to unlock my bootloader and install TWRP. However, I can't seem to get TWRP to "stick" - flashing seems fine, and rebooting into bootloader and into TWRP recovery all proceeds fine. However, as soon as I reboot my system, TWRP seems to disappear and the stock recovery reappears.
Am I doing something wrong here? This is the exact process I followed on my Nexus 7, without any problems.
Click to expand...
Click to collapse
You should be able to run twrp-2.8.7 without any problems. I believe if you want one higher you might need to format data (decrypt is what I do).
Also, here is what instructions on TWRP say to make it stick.
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.

Tulsadiver said:
You should be able to run twrp-2.8.7 without any problems. I believe if you want one higher you might need to format data (decrypt is what I do).
Also, here is what instructions on TWRP say to make it stick.
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
Click to expand...
Click to collapse
Thanks for your response. I am following the directions on TWRP's website, so it must be another issue.
I will try the version you suggest to see if that works. Why would I need to format data to install a later version?

jerethi said:
Thanks for your response. I am following the directions on TWRP's website, so it must be another issue.
I will try the version you suggest to see if that works. Why would I need to format data to install a later version?
Click to expand...
Click to collapse
I believe it requires you to be decrypted. Formatting userdata will wipe your data so make a backup first.
http://forum.xda-developers.com/nexus-5x/general/guide-how-to-install-custom-recovery-t3231143

jerethi said:
Greetings!
After installing the October security updates (bringing my device to NBD90W) I decided to unlock my bootloader and install TWRP. However, I can't seem to get TWRP to "stick" - flashing seems fine, and rebooting into bootloader and into TWRP recovery all proceeds fine. However, as soon as I reboot my system, TWRP seems to disappear and the stock recovery reappears.
Am I doing something wrong here? This is the exact process I followed on my Nexus 7, without any problems.
Click to expand...
Click to collapse
Flash TWRP from bootloader.
While within bootloader use vol down to select recovery and press power to boot into recovery.
Install SuperSU.
TWRP will stick.
If you boot with stock recovery even once, TWRP will get replaced.

sfhub said:
Flash TWRP from bootloader.
While within bootloader use vol down to select recovery and press power to boot into recovery.
Install SuperSU.
TWRP will stick.
If you boot with stock recovery even once, TWRP will get replaced.
Click to expand...
Click to collapse
Thank you. What is the difference between rooting and using the method that TulsaDiver suggests above?

Tulsadiver said:
I believe it requires you to be decrypted. Formatting userdata will wipe your data so make a backup first.
http://forum.xda-developers.com/nexus-5x/general/guide-how-to-install-custom-recovery-t3231143
Click to expand...
Click to collapse
So, just to clarify, I can either flash a modified boot.img (as described in the post you linked) or I could simply flash an older version of TWRP?
Thanks again for your assistance!

jerethi said:
So, just to clarify, I can either flash a modified boot.img (as described in the post you linked) or I could simply flash an older version of TWRP?
Click to expand...
Click to collapse
If you are using NBD90W I suggest you use the unofficial TWRP 3.0.2-3 that was posted a few pages back from the last post on the TWRP thread.
TWRP 3.0.2-0 won't decrypt Android N (will decrypt MM)
TWRP 3.0.2-1 has a major EFS bug that will brick your phone on restore
TWRP 3.0.2-2 has that EFS problem fixed, but has another problem where larger parttitions don't get backed up correctly.
TWRP 3.0.2-3 has both previous problems fixed.
---------- Post added at 10:19 AM ---------- Previous post was at 10:16 AM ----------
jerethi said:
Thank you. What is the difference between rooting and using the method that TulsaDiver suggests above?
Click to expand...
Click to collapse
I didn't read the whole post but decrypted user partition isn't directly related to why your TWRP is disappearing.
When you boot with a stock image, it will replace your recovery with stock.
If there is just 1 byte change with your boot.img, it won't do that.
Installing SuperSU will patch your boot.img, thus it will no longer replace your recovery with stock.
You could flash a modified boot.img instead of SuperSU, but then you are depending on someone else creating a modified boot.img for you (or you creating it yourself). If your goal is to have root installed, then SuperSU will patch boot.img on the fly during install so no need for extra step.
Again, the overwriting of TWRP with stock recovery is not directly related to the modifications done to boot.img either by someone else or by SuperSU install. If you had done any change to boot.img even if it is off by 1 byte, TWRP won't be replaced by stock recovery.
IMO there is no reason to run decrypted with latest OS, but if you wanted to, the only requirement is you have dm-verity disabled in the boot.img. Both the custom boot.img and the SuperSU install would do this for you.
After you have dm-verity disabled (either by SuperSU install or installing custom boot.img), boot back into bootloader and do
fastboot format userdata
From that point on, as long as you *never* boot using stock boot.img your userdata will remain decrypted. If you ever boot with stock boot.img, by mistake, it will proceed to encrypt your userdata. Then you'd have to go through the same procedure again the decrypt (losing your userdata in the format step)
The proper way to upgrade is to flash boot.img, system.img, vendor.img in fastboot, then immediately (from bootloader menu) boot into TWRP recovery, and install SuperSU. Then everything will be preserved.

jerethi said:
So, just to clarify, I can either flash a modified boot.img (as described in the post you linked) or I could simply flash an older version of TWRP?
Thanks again for your assistance!
Click to expand...
Click to collapse
Listen to this guy. You can start with the old one if you want then upgrade to the new one later but Supersu modifies your boot.img for you. Like he said, after Fastboot flashing them, Fastboot reboot and before your phone boots up, boot right back into recovery. This will make TWRP stick.

Wow, this post was SO HELPFUL.... Haven't rooted in a while, recently replaced our Nexus 5's with 5x's (on NBD90W) and hadn't felt the need to root. Plus it's gotten so much trickier even with Nexuses.
Anyway totally familiar with ADB/fastboot etc to flash stuff.
I still need to oem unlock and wipe still (bleh).
But after, one thing that's confusing me, to then root is a *custom* kernel (boot.img) needed now? Made specifically for (at this point in time) NBD90W? Or can stock boot.img be flashed then boot straight into TWRP and flash whatever is the latest SuperSU? Are all SuperSI "systemless" now?
Also you stated "IMO there is no reason to run decrypted with latest OS". I have noticed VAST performance improvement with Nougat. Is this why you feel no reason? Would we not still gain even more speed back? (it was so sad watching my wife's old Nexus 5 booting 6.0.1 faster than my 5X).
sfhub said:
If you are using NBD90W I suggest you use the unofficial TWRP 3.0.2-3 that was posted a few pages back from the last post on the TWRP thread.
TWRP 3.0.2-0 won't decrypt Android N (will decrypt MM)
TWRP 3.0.2-1 has a major EFS bug that will brick your phone on restore
TWRP 3.0.2-2 has that EFS problem fixed, but has another problem where larger parttitions don't get backed up correctly.
TWRP 3.0.2-3 has both previous problems fixed.
---------- Post added at 10:19 AM ---------- Previous post was at 10:16 AM ----------
I didn't read the whole post but decrypted user partition isn't directly related to why your TWRP is disappearing.
When you boot with a stock image, it will replace your recovery with stock.
If there is just 1 byte change with your boot.img, it won't do that.
Installing SuperSU will patch your boot.img, thus it will no longer replace your recovery with stock.
You could flash a modified boot.img instead of SuperSU, but then you are depending on someone else creating a modified boot.img for you (or you creating it yourself). If your goal is to have root installed, then SuperSU will patch boot.img on the fly during install so no need for extra step.
Again, the overwriting of TWRP with stock recovery is not directly related to the modifications done to boot.img either by someone else or by SuperSU install. If you had done any change to boot.img even if it is off by 1 byte, TWRP won't be replaced by stock recovery.
IMO there is no reason to run decrypted with latest OS, but if you wanted to, the only requirement is you have dm-verity disabled in the boot.img. Both the custom boot.img and the SuperSU install would do this for you.
After you have dm-verity disabled (either by SuperSU install or installing custom boot.img), boot back into bootloader and do
fastboot format userdata
From that point on, as long as you *never* boot using stock boot.img your userdata will remain decrypted. If you ever boot with stock boot.img, by mistake, it will proceed to encrypt your userdata. Then you'd have to go through the same procedure again the decrypt (losing your userdata in the format step)
The proper way to upgrade is to flash boot.img, system.img, vendor.img in fastboot, then immediately (from bootloader menu) boot into TWRP recovery, and install SuperSU. Then everything will be preserved.
Click to expand...
Click to collapse

jb0ne said:
Wow, this post was SO HELPFUL.... Haven't rooted in a while, recently replaced our Nexus 5's with 5x's (on NBD90W) and hadn't felt the need to root. Plus it's gotten so much trickier even with Nexuses.
Anyway totally familiar with ADB/fastboot etc to flash stuff.
I still need to oem unlock and wipe still (bleh).
But after, one thing that's confusing me, to then root is a *custom* kernel (boot.img) needed now? Made specifically for (at this point in time) NBD90W? Or can stock boot.img be flashed then boot straight into TWRP and flash whatever is the latest SuperSU? Are all SuperSI "systemless" now?
Also you stated "IMO there is no reason to run decrypted with latest OS". I have noticed VAST performance improvement with Nougat. Is this why you feel no reason? Would we not still gain even more speed back? (it was so sad watching my wife's old Nexus 5 booting 6.0.1 faster than my 5X).
Click to expand...
Click to collapse
I've always decrypted but that is my personal choice. All I do to root afterwards is flash SuperSU-v2.7.8. That is it. You can adb sideload it (i use twrp for that) or flash it in twrp if you have it already on your phone).

jb0ne said:
But after, one thing that's confusing me, to then root is a *custom* kernel (boot.img) needed now? Made specifically for (at this point in time) NBD90W? Or can stock boot.img be flashed then boot straight into TWRP and flash whatever is the latest SuperSU? Are all SuperSI "systemless" now?
Click to expand...
Click to collapse
You must have a customized boot.img now for root. What customizations you absolutely need to have in boot.img is dependent on how you want root installed, but since you are modifying boot.img, you might as well just stick all the changes you need in boot.img and leave /system untouched.
The default install for SuperSU will make the required changes to whichever boot.img you currently have installed on your system. Generally that consists of disabling dm-verity (integrity check), making encryption optional (not absolutely required), making sepolicy security changes, and adding init script support to load SuperSU binaries later in the boot process.
There are configuration parameters you can feed into SuperSU install to force it to install root on /system instead of systemless, but I would just suggest systemless. It is a cleaner install IMO.
So install the stock boot.img and boot directly into TWRP from the bootloader menu, then install SuperSU and it will modify the boot.img you have installed (and back up original)
The only requirement to keep TWRP (and/or decrypted userdata) is to NEVER boot the phone using a stock boot.img. If you always immediately install SuperSU after flashing the stock boot.img that will satisfy that requirement.
jb0ne said:
Also you stated "IMO there is no reason to run decrypted with latest OS". I have noticed VAST performance improvement with Nougat. Is this why you feel no reason? Would we not still gain even more speed back? (it was so sad watching my wife's old Nexus 5 booting 6.0.1 faster than my 5X).
Click to expand...
Click to collapse
http://forum.xda-developers.com/nexus-5x/general/unencrypted-faster-real-world-usage-t3365660

for some reason, when i fastboot installed twrp (after usb debug/unlocking bootloader) I kept getting mount errors when starting twrp. I tried flashing purenexus rom, wipes dalvic, system, data. then my data partition was 0. couldn't mount data part. to copy purenexus or system stock image. I ended up having to use my windows pc to wugfresh it back to life. has been a crazy night. I need coffee.
On coast of SC here, in Charleston. Wishing everybody best of luck with the hurricane.

trentag1988 said:
for some reason, when i fastboot installed twrp (after usb debug/unlocking bootloader) I kept getting mount errors when starting twrp. I tried flashing purenexus rom, wipes dalvic, system, data. then my data partition was 0. couldn't mount data part. to copy purenexus or system stock image. I ended up having to use my windows pc to wugfresh it back to life. has been a crazy night. I need coffee.
On coast of SC here, in Charleston. Wishing everybody best of luck with the hurricane.
Click to expand...
Click to collapse
Did you reboot after unlocking or go ahead and install TWRP right after unlocking?

I tried, but I kept getting the " cannot check for corrupt system because bootloader is unlocked" message, and it never fully booted. I managed to fix the 0data partition by fastboot format userdata, but pure Nexus never worked. It tried to boot, but it stuck on the spinning Google logo thing

Update: followed pure Nexus instruction; unlocked bootloader, then let it boot once to device setup. Restarted in fast boot, flashed twrp. Rebooted, went into twrp, formatted dalvic, system, user data and cache. Flashed pure Nexus from then gapps according to pure Nexus download page. Reformated dalvic and cache. Rebooted, stuck on Google logo, this time did not do its spinning thing. Have I missed a step??
---------- Post added at 03:33 PM ---------- Previous post was at 03:32 PM ----------
Update: followed pure Nexus instruction; unlocked bootloader, then let it boot once to device setup. Restarted in fast boot, flashed twrp. Rebooted, went into twrp, formatted dalvic, system, user data and cache. Flashed pure Nexus from twrp then gapps according to pure Nexus download page. Reformated dalvic and cache. Rebooted, stuck on Google logo, this time did not do its spinning thing. Have I missed a step??

trentag1988 said:
Update: followed pure Nexus instruction; unlocked bootloader, then let it boot once to device setup. Restarted in fast boot, flashed twrp. Rebooted, went into twrp, formatted dalvic, system, user data and cache. Flashed pure Nexus from then gapps according to pure Nexus download page. Reformated dalvic and cache. Rebooted, stuck on Google logo, this time did not do its spinning thing. Have I missed a step?
---------- Post added at 03:33 PM ---------- Previous post was at 03:32 PM ----------
Update: followed pure Nexus instruction; unlocked bootloader, then let it boot once to device setup. Restarted in fast boot, flashed twrp. Rebooted, went into twrp, formatted dalvic, system, user data and cache. Flashed pure Nexus from twrp then gapps according to pure Nexus download page. Reformated dalvic and cache. Rebooted, stuck on Google logo, this time did not do its spinning thing. Have I missed a step?
Click to expand...
Click to collapse
What firmware are you on?

Latest nrd90w(?) I believe
---------- Post added at 04:04 PM ---------- Previous post was at 04:04 PM ----------
NBD90W

sfhub said:
If you are using NBD90W I suggest you use the unofficial TWRP 3.0.2-3 that was posted a few pages back from the last post on the TWRP thread.
TWRP 3.0.2-0 won't decrypt Android N (will decrypt MM)
TWRP 3.0.2-1 has a major EFS bug that will brick your phone on restore
TWRP 3.0.2-2 has that EFS problem fixed, but has another problem where larger parttitions don't get backed up correctly.
TWRP 3.0.2-3 has both previous problems fixed.
---------- Post added at 10:19 AM ---------- Previous post was at 10:16 AM ----------
I didn't read the whole post but decrypted user partition isn't directly related to why your TWRP is disappearing.
When you boot with a stock image, it will replace your recovery with stock.
If there is just 1 byte change with your boot.img, it won't do that.
Installing SuperSU will patch your boot.img, thus it will no longer replace your recovery with stock.
You could flash a modified boot.img instead of SuperSU, but then you are depending on someone else creating a modified boot.img for you (or you creating it yourself). If your goal is to have root installed, then SuperSU will patch boot.img on the fly during install so no need for extra step.
Again, the overwriting of TWRP with stock recovery is not directly related to the modifications done to boot.img either by someone else or by SuperSU install. If you had done any change to boot.img even if it is off by 1 byte, TWRP won't be replaced by stock recovery.
IMO there is no reason to run decrypted with latest OS, but if you wanted to, the only requirement is you have dm-verity disabled in the boot.img. Both the custom boot.img and the SuperSU install would do this for you.
After you have dm-verity disabled (either by SuperSU install or installing custom boot.img), boot back into bootloader and do
fastboot format userdata
From that point on, as long as you *never* boot using stock boot.img your userdata will remain decrypted. If you ever boot with stock boot.img, by mistake, it will proceed to encrypt your userdata. Then you'd have to go through the same procedure again the decrypt (losing your userdata in the format step)
The proper way to upgrade is to flash boot.img, system.img, vendor.img in fastboot, then immediately (from bootloader menu) boot into TWRP recovery, and install SuperSU. Then everything will be preserved.
Click to expand...
Click to collapse
Thanks very much for the detailed assistance. If I wanted to install a custom ROM, do I have to decrypt my user data first? Or can I just install TWRP and then flash?

trentag1988 said:
Latest nrd90w(?) I believe
---------- Post added at 04:04 PM ---------- Previous post was at 04:04 PM ----------
NBD90W
Click to expand...
Click to collapse
I do not believe Pure Nexus is a Nougat Rom. Try starting over and flashing a Rom compatible with your firmware.

Strange issue with mi5s not booting flashed rom

Hi,
My Mi5s was in a bootloop between recovery mode and Mi logo.
I was able to get to fastboot via cmd, phone is unlocked, and I also flashed TWRP, then Vol + and power to load TWRP.
From there Ive tried installing multiple roms, but each time I reboot system it goes back into TWRP.
I've tried many ways of installing new roms, like wiping all data/factory reset/formatting before flashing supersu + lineage os or cm13 and then gapps, after flashing it says flash was successul...
I've also been able to use xiaomiflash to flash official latest global stable which puts phone back into bootloop.
I also flashed latest chinese dev which loads Mi Recovery 3.0, from there I'm still unable to install the rom, after showing the rom loading, just a few seconds in, the phone reboots.
Quite confused and unsure of what to do now... New to forum, not sure where to post this.

goatlad said:
Hi,
My Mi5s was in a bootloop between recovery mode and Mi logo.
I was able to get to fastboot via cmd, phone is unlocked, and I also flashed TWRP, then Vol + and power to load TWRP.
From there Ive tried installing multiple roms, but each time I reboot system it goes back into TWRP.
I've tried many ways of installing new roms, like wiping all data/factory reset/formatting before flashing supersu + lineage os or cm13 and then gapps, after flashing it says flash was successul...
I've also been able to use xiaomiflash to flash official latest global stable which puts phone back into bootloop.
I also flashed latest chinese dev which loads Mi Recovery 3.0, from there I'm still unable to install the rom, after showing the rom loading, just a few seconds in, the phone reboots.
Quite confused and unsure of what to do now... New to forum, not sure where to post this.
Click to expand...
Click to collapse
I had the same issue when I first installed some ROMs for this phone and it got me really confused since I was doing everything right. This is what worked for me
MAKE SURE YOU HAVE OFFICIAL TWRP FIRST BEFORE ANYTHING
Go into fastboot and type
fastboot format userdata
Go back to TWRP and go into wipe/advanced wipe.
Select data and then select repair or change partition
Then go into change filesystem and choose either F2FS or ext4. If one gives an error try the other one, after that format to which ever
If you're on AOSP/LOS ROMs I'd recommend F2FS since its a bit faster and makes your storage last way longer

crzykiller said:
I had the same issue when I first installed some ROMs for this phone and it got me really confused since I was doing everything right. This is what worked for me
MAKE SURE YOU HAVE OFFICIAL TWRP FIRST BEFORE ANYTHING
Go into fastboot and type
fastboot format userdata
Go back to TWRP and go into wipe/advanced wipe.
Select data and then select repair or change partition
Then go into change filesystem and choose either F2FS or ext4. If one gives an error try the other one, after that format to which ever
If you're on AOSP/LOS ROMs I'd recommend F2FS since its a bit faster and makes your storage last way longer
Click to expand...
Click to collapse
tried official twrp 3.1.1-0, did these steps only, maybe I've missed something:
installed twrp 3.1.1-0 then went into fastboot and typed fastboot format userdata
rebooted into TWRP, i was promted whether to keep system read only, I tried first swiping to allow mods, and also keep read only then proceeded:
changed data to F2FS (didn't wipe or factory reset anything else)
rebooted system
copied lineage and gapps zip files to phone
installed latest lineage then gapps 7.1 arm64
rebooted system, back into twrp

OnePlus 5t Bricked, Help?

I just got my 5t a couple of days back. Unlocked the bootloader and used Blu spark twrp and magisk beta for root.
On restart phone would boot up to one plus logo, and then just go black. The notification light goes on. But nothing else.
Help please?
Edit FIXED(No data loss)
1. Boot into TWRP, clear cache. Hard reset(Volume up + Power from a switched off state).
2. Boot back into twrp.
3. Adb push full zip(Found here - Signed Flashable Zip)(Adb push follows this syntax - adb push /(filename).zip /storage/
4. On twrp goto the install menu, navigate to storage and install the file.
5. Optionally you may clear the cache and then install magisk. I couldn't get it to work without magisk but YMMW

Do a hard reset if you still can...

Manish54 said:
Do a hard reset if you still can...
Click to expand...
Click to collapse
Already did that, multiple times. No success.

Same happened to me. It eventually forced into a fastboot bootloop. I had to flash and boot twrp from fastboot again, and then flash the full ota zip and essentially start over.
Decided to skip the root though, until there is a solid ROM release or a stable magisk.

imatts said:
Same happened to me. It eventually forced into a fastboot bootloop. I had to flash and boot twrp from fastboot again, and then flash the full ota zip and essentially start over.
Decided to skip the root though, until there is a solid ROM release or a stable magisk.
Click to expand...
Click to collapse
I tried a similar approach. Cleared dalvik, hard reset then booted into Blu twrp. Flashed Full zip and then magisk again. Booted right up.

therock12123 said:
I tried a similar approach. Cleared dalvik, hard reset then booted into Blu twrp. Flashed Full zip and then magisk again. Booted right up.
Click to expand...
Click to collapse
Yes that was one of my many troubleshooting steps as well, didn't work for me.

Can you help me with this, having a similar issue when I tried to unroot and screwed everything up.

Can anyone help me with this? I'm trying to push via adb the stock os and it looks successful but I don't see it in TWRP.

It's not a big issue, you just flashed the wrong magisk, just boot into recovery and re flash the stock OS

With this type of brick, if u r able to access recovery just go amd reflash, this is not a major brick

MI 9 SE - fastboot bootloop after flashing paranoid android

Hi
After sitting on xiaomi.eu for a while I decided to change things up and go back to Paranoid Android Quartz 4. I flashed Global fastboot rom (V11.0.6.0.QFBEUXM which I had from a while ago) via MiFlash, booted the phone, went back to fastboot, flashed twrp and booted into it. Twrp didnt decrypt data on the phone, but I didn't think much of it and just formatted data. Then I flashed shrp, formatted cache, dalvik, system, data and internal storage, and using shrp I flashed firmware that was included with the rom, and then the rom itself. After that I tried booting the system, but after showing Mi logo it justs boots info fastboot. Even if I try to flash recovery and boot into it, it still reboots to bootloader. I don't really know what am i doing wrong.
Does anyone know what might be wrong?
Thanks in advance

fejlip said:
Hi
After sitting on xiaomi.eu for a while I decided to change things up and go back to Paranoid Android Quartz 4. I flashed Global fastboot rom (V11.0.6.0.QFBEUXM which I had from a while ago) via MiFlash, booted the phone, went back to fastboot, flashed twrp and booted into it. Twrp didnt decrypt data on the phone, but I didn't think much of it and just formatted data. Then I flashed shrp, formatted cache, dalvik, system, data and internal storage, and using shrp I flashed firmware that was included with the rom, and then the rom itself. After that I tried booting the system, but after showing Mi logo it justs boots info fastboot. Even if I try to flash recovery and boot into it, it still reboots to bootloader. I don't really know what am i doing wrong.
Does anyone know what might be wrong?
Thanks in advance
Click to expand...
Click to collapse
Hi
Try flashing vbmeta it might help you to boot

Sounds like you will have to start from scratch and flash the fastboot ROM and proceed from there.
However, after formatting data in TWRP, reboot into recovery before flashing SHRP and PA.
If after this it reboots into recovery rather than system, you can try flashing vbmeta.
Peace
---------- Post added at 01:37 PM ---------- Previous post was at 01:32 PM ----------
Also, TWRP won't ask for a password to decrypt data if you went straight back to fastboot after flashing the stock ROM as you won't have set up a decryption password without setting up the phone.
Also, I'm not sure that you have to format any other partition other than data, just a wipe should be enough. But definitely reboot recovery after formatting data. The PA thread should say whether partitions need to be formatted or simply "wiped"
Peace.

I tried doing it again a few more times but with no luck. So instead I tried to flash xiaomi.eu weekly rom, but that also doesn't work for me. I downloaded newest Global Fastboot Rom (V12.0.1.0.QFBMIXM), flashed it with MiFlash and then proceeded to set up the phone as a new device. After setup I turned on usb debugging, went into fastboot and flashed redispade TWRP 3.3.1 (rebooted into TWRP and got asked for decryption password). Then I wiped data, cache and dalvik and flashed xiaomi.eu. After I flashed the rom, I installed magisk (without rebooting the device). Then when I tried to boot into system I got stuck in recovery bootloop (files where encrypted, did not get asked for password). I also tried to flash vbmeta after that but the phone was still bootlooping. I honsetly have no clue what I am doing wrong at this point
Edit: I tried it again this time without flashing magisk and the results are exactly the same - twrp bootloop even after flashing vbmeta

I personally don't use miflash to flash fastboot ROMs, I prefer to do it via fastboot. Could miflash be causing issues? Have you replicated the steps you took to originally flash xiaomi.eu ROM?
Peace.