flash rom after boot into twrp - OnePlus 5T Questions & Answers

hi i bought op5t few days ago.
and now i have serious problem.
i flashed the5tos. and custom kernel
but my phone booted on recovery.
can't boot 5tos rom.
only can boot official oos rom.
and after rom flashing twrp always has problem
'failed to mount cache (no such file or directory)
and i flashed noverity op5.zip and no_verity_op5_v2.zip too
it can't boot. boot on recovery mode again
can you solve this critical problem?
and i use official twrp 3.2.1-2

I have been having the same problem. I have tried lineageos 16, los17, pixel experience 9 and 10 and they all softbrick. Only oos boots fine.

Related

Can't flash any Custom Recovery on OP3

Hi everyone,
I've a little problem with my OP3, Yesterday I removed my OOS 3.2.6 with TWRP, I flashed the stock recovery back and then I've sideloaded the last OOS 3.5.3 Community Build. Today i'd like to flash the TWRP, i launched the Fastboot menu, nothing seems to go wrong by flashing but when i tried to boot into the recovery, the "1+ powered by android" appears for 5 sec and then a black screen, no TWRP screen... Same problem by trying to restore the OnePlus stock recovery..
I tried "fastboot -w" (wipe) this bring back the stock recovery.
I tried to sideload, OOS 3.5.3, OOS 3.5.3, ResurectionRemix 2.7.4 and CM14 but all of them failed at 47% of work...
I'm thinking that there is a problem caused by an encryption...
"fastboot format userdata" didn't solve the problem..
I'd like to know wich partition i can format/erase to remove this encryption (Loss of data is not a problem for me)
Thanks in advance
Have you tried to flash the modified TWRP ?
Dushaine said:
Have you tried to flash the modified TWRP ?
Click to expand...
Click to collapse
Yes, same problem as TWRP
Same thing happened to me on flashing twrp after sideloading CB 3.5.2 through stock recovery. But flashing the modified twrp 3.0.2-19 solved the issue.
It is newer firmware that won't let you boot into TWRP.
Flash modified TWRP 3.0.2-19 recovery through fast boot.
Then flash <=3.5.0 firmware from here using TWRP.
Then flash this TWRP 3.0.2-0 image again from fast boot.
Then flash a ROM of your liking.
If all else fails, you can try this (flash stock recovery and 3.2.4 FW) WITHOUT relocking and then flash TWRP 3.0.2-0 from the above link to see if that works.
AJay27 said:
Same thing happened to me on flashing twrp after sideloading CB 3.5.2 through stock recovery. But flashing the modified twrp 3.0.2-19 solved the issue.
Click to expand...
Click to collapse
kgs1992 said:
It is newer firmware that won't let you boot into TWRP.
Flash modified TWRP 3.0.2-19 recovery through fast boot.
Then flash 3.5.0 firmware from here using TWRP.
Then flash this TWRP 3.0.2-0 image again from fast boot.
Then flash a ROM of your liking.
If all else fails, you can try this (flash stock recovery and 3.2.4 FW) without relocking and then flash TWRP 3.0.2-0 from the above link to see if that works.
Click to expand...
Click to collapse
I've been able to Flash the Modified recovery, and it booted. By flashing the patch, no problem detected, but after flashing the 3.0.2-0 same black screen as earlier...
So I flashed the modified back, and by trying to flash ResurectionRemix for exemple, no error happenned but, when boot begin, same problem as twrp ...
EDIT : Sorry guys, i didn't read correctly.. I was flashing the same patch ! The 3.5.3 and not the 3.5.0 !!! Normal TWRP is booting corectly now, i'll see for ROM !
Thank you very much to you !!
EDIT 2 : RR 2.7.4 BOOT !!! Thank you so much !

Oneplus 5T root problem

Hello all If any one can help me ,
I was rooted running rooted stock oxygen os before on my Oneplus 5T
after flashing Oxygen OS 5.1.4 Full Zip my phone is not rooting it gets in initial oneplus logo and freeze there without loading OS
Phone is working fine after Flashing Oxygen OS 5.1.4 Full Zip without any issue its not booting after flashing either SuperSu or Magisk
Steps which I follow are
1 Flash custom recovery I have tried both Codeworkx TWRP | Blu_Spark
2 after flashing recovery boot in to recovery flash Supersu or magisk
3 reboot
when I reboot if i Flash supersu it stuck on oneplus logo, If i flash magisk it reboot itself to fastboot so Os is not loading at all.
I have to flash full Zip again every time to get it working but then I dont have root access.
I have tried at least 10 times with different even old versions of magisk and supersu with out any success.
Is there any particular recovery or different version of magisk or superuse I need to flash?
your help will be really appreciated.
Try a different approach. Instead of installing recovery, just get phone rooted first. There is a way where you can boot into twrp (without installing it), and then flash magisk/supersu zip. If your phone is rooted, then you can install twrp later (or keep oem recovery)
This is how you boot into twrp (or any recovery): fastboot boot recovery recovery.img
Let me know how it goes.
As you said boot to recovery without installing it.
One problem currently I am installing recovery and flashing root. After that phone is not booting up in to OS it stuck on oneplus logo. Then I have to force off phone boot in to recovery and flash full os zip to get it working. I can boot in to TWRP because my os didn't load. Now if I use your method and flash root file and if phone won't boot to os that means I won't be able to boot in to TWRP again to flash full os zip to get phone working atleast without root. Any idea?
Huh, frankly I have no idea why you are facing this menace. I can just give two suggestions.
1. Try with older, more stable versions of TWRP and Magisk
2. Get yourself a custom ROM, most ROM's will work flawlessly after flashing root files
Hope for the best!
I usually switch from OpenBeta to LOS and back again. Here's how I switch back to OpenBeta (steps should work for official OOS):
1) Back everything on internal storage up. This one's important
2) Boot into official OOS recovery
3) Wipe EVERYTHING (this is why you need to follow Step 1)
4) Sideload the version of OOS you want. The instructions will be right there on the recovery screen
5) Boot into Fastboot and flash TWRP
6) Flash Magisk and (optional) Xposed

stuck in bootloader/recovery, can't flash ROMs.

Hello,
i'm stuck in a particular situation: i can use fastboot and i can flash recoveries but none of them can succesfully flash a rom. i want to go back to the stock Realme UI, my device is RMX1993.
i tried to follow the guide (https://forum.xda-developers.com/realme-x2/how-to/to-stock-rom-howto-t4014773) but the last recovery (rmx1993-sde20-stock_recovery-c05) can't flash neither RMX1993EX_11_OTA_1040_all_tSZ3Sf5A77NS nor RMX1993EX_11_OTA_1050_all_loALrMDyMrbs.
tried to flash trough orangefox or the last twrp that support ozip decription but the result is a "succesful flash" but a phone that does not go over the boot screen and it reboot.
i succesfully installed color os trough the proper old stock recovery and it said the installation was succesfull, but the problem was the same.
someone know where could be the problem?
You need to successfully flash Android 10 (Realme UI 1.0) before you can flash custom Android 10 roms.
Have you tried this guide: https://forum.xda-developers.com/realme-x2/help/how-to-flash-q-firmware-based-roms-t4115987
As for why your colorOS back up is not working i'm not quite sure...have you wiped your cache before booting to the color os backup?

Problems with recovery.

After the firmware Lineage 18.0 flew recovery, stupidly stopped opening.Flashing through adb recovery img does not give anything, can someone tell me something? Now I can't restore the TWRP backup or flash the custom firmware and Magisk.
I installed the service firmware via the computer and everything worked out.
In my case i boot on fastboot and flashed twrp img without booting into Lineage OS 18.1 and i could install another rom, Lineage OS 18.1 sadly has the bug that deletes TWRP recovery on rom boot, doesn't matter if you install again TWRP recovery

Can't install any rom

Hello,
Just after unlocked the bootloader, I flashed Orange Fox recovery and tried to install the last Pixel Experience, but I was stuck on boot animation.
Same for previous Pixel Experience rom.
Then, I tried LineageOS 19.1, and successfully booter on it. But, I got screen that said "Your data may be corrupter" and can't do anything but reboot into recovery.
I'm out of option, now... Did I forgot something ?
PS: I also tried to flash Chikori Kernel but I got error "New image is larger than targeted partition"
shim80 said:
Hello,
Just after unlocked the bootloader, I flashed Orange Fox recovery and tried to install the last Pixel Experience, but I was stuck on boot animation.
Same for previous Pixel Experience rom.
Then, I tried LineageOS 19.1, and successfully booter on it. But, I got screen that said "Your data may be corrupter" and can't do anything but reboot into recovery.
I'm out of option, now... Did I forgot something ?
PS: I also tried to flash Chikori Kernel but I got error "New image is larger than targeted partition"
Click to expand...
Click to collapse
Try to flash V12.5.3.0.QFLCNXM with Twrp/O.f (TWRP is newer than this OF.)
then
reboot Twrp/O.F
Wipe/format data type yes
reboot Twrp/O.F
Flash rom
Sometimes the flashing of the recovery ROM does not work with the Twrp/O.F in this case use Miflash with a fastboot rom.
If you're still trying to figure this one out, I think I know how to solve your issue installing LOS.
You most likely used TWRP v3.70, am I right?
You should use TWRP v3.61 coz that was the last stable version that worked, the only thing is that you might need to find another custom recovery other than the official TWRP after installing an Android 12 custom ROM like LOS 19.1.
Lineage OS has their own recovery so you'd probably need to use that if you want to update it.
Same issue with me. yesterday. Though mine is fixed.
My workaround was: I installed the official 12.5.3 MIUI using OrangeFox. After boot, I tried installing PixelExperience using Pixel recovery. There I got successfully installed a custom ROM. Alhough I am not sure if the mounting/encryption of Internal SD is the cause.

Categories

Resources