Hi, I need help in installing Recovery.
I unlocked the bootloader, installed TWRP and then CyanogenMod 13 ROM.
After this, Oxygen Os 3 got released. I downloaded the zip file and flashed through TWRP.
Oxygen OS got installed but after this, I couldn't go back in TWRP recovery.
I tried everything. I use "fastboot flash recovery twrp.img"
everything works
but when I boot in recovery, phone gets stuck on the LOGO and nothing happens.
Is there any way to solve this issue.
Almost the same for me.
When I flash oOS 3.0.2, unable to reboot using Grarak'sTWRP or TWRP-3.0.2-1.
Always stuck on boot logo without animation.
I reverted to old TWRP and oOS 2.2.1
piyushmodi01 said:
Hi, I need help in installing Recovery.
I unlocked the bootloader, installed TWRP and then CyanogenMod 13 ROM.
After this, Oxygen Os 3 got released. I downloaded the zip file and flashed through TWRP.
Oxygen OS got installed but after this, I couldn't go back in TWRP recovery.
I tried everything. I use "fastboot flash recovery twrp.img"
everything works
but when I boot in recovery, phone gets stuck on the LOGO and nothing happens.
Is there any way to solve this issue.
Click to expand...
Click to collapse
Try to install OOS recovery or Hybrid recovery.
Nobody ever learns or reads nowadays....
Read up on bootloader versions on Oneplus 2 and you will find the explanation perfectly understandable.
Thank You So much for your help. Finally it worked but I lost my data! Anyways, no issues.
Can you give us the way you fixed your problem .
Thanks
Hi,
My OP5 worked like a charm with Resurrection Remix 5.8.5, but recently my pin was randomly unrecognised, and I solved it with lock key files suppression. I ended up to restore a backup but got a bootloop, that occured with every rom I tried.
I had bootloader unlocked and magisk flashed.
I finally managed to flash and boot Resurrection Remix 6.0 (after wiping every partition), but at every reboot, when in twrp 3.2.1.0 (also tried on 3.1.1), I'm unable to mount data partition. Also it doesn't ask for my pin as it did before all those reflashing. The rom seems to have no issue (except some bugs).
I tried reflashing twrp without result and deleting internal storage is working so far as long as I don't reboot. I found some threads with similar problems about Oreo's related roms but I don't know if they are related to my issue.
I'm currently on RR6.0, bootloader unlocked, twrp 3.2.1.0 and no root, and encrypted by default.
Do you have any idea on this ?
Thanks for your help.
nonnaryplayer said:
Hi,
My OP5 worked like a charm with Resurrection Remix 5.8.5, but recently my pin was randomly unrecognised, and I solved it with lock key files suppression. I ended up to restore a backup but got a bootloop, that occured with every rom I tried.
I had bootloader unlocked and magisk flashed.
I finally managed to flash and boot Resurrection Remix 6.0 (after wiping every partition), but at every reboot, when in twrp 3.2.1.0 (also tried on 3.1.1), I'm unable to mount data partition. Also it doesn't ask for my pin as it did before all those reflashing. The rom seems to have no issue (except some bugs).
I tried reflashing twrp without result and deleting internal storage is working so far as long as I don't reboot. I found some threads with similar problems about Oreo's related roms but I don't know if they are related to my issue.
I'm currently on RR6.0, bootloader unlocked, twrp 3.2.1.0 and no root, and encrypted by default.
Do you have any idea on this ?
Thanks for your help.
Click to expand...
Click to collapse
Are you using the twrp from twrp.me or a modded recovery like codeworkx or blu spark? The original recoveries from twrp.me don't work on oreo.
Try using these recoveries:
Codeworkx: https://sourceforge.net/projects/cheeseburgerdumplings/files/15.1/cheeseburger/recovery/
Blue spark: https://forum.xda-developers.com/devdb/project/dl/?id=28224
Zohair.ul.hasan said:
Are you using the twrp from twrp.me or a modded recovery like codeworkx or blu spark? The original recoveries from twrp.me don't work on oreo.
Try using these recoveries:
Codeworkx: https://sourceforge.net/projects/cheeseburgerdumplings/files/15.1/cheeseburger/recovery/
Blue spark: https://forum.xda-developers.com/devdb/project/dl/?id=28224
Click to expand...
Click to collapse
It worked Thanks ! I flashed codeworkx and all went fine : data is mounted at every boot, encryption unlock in recovery, flashing and restore.
I should have waited to flash oreo but this rom is the first to get me out of my bootloop hell so I'll stick with it for now.
Thanks again !
No problem Glad to see your issue got fixed.
Hi there folks!
Sorry if i open a thread, probably you've discussed somewhere before about this problem that i'm experiencing.
My OnePlus 5 basically works only with omniROM, it doesn't boot at all when i try to install another one.
I tried with this:
https://forum.xda-developers.com/oneplus-6/development/rom-aospextended-rom-v5-7-t3825642
and this one:
https://forum.xda-developers.com/oneplus-5/development/rom-crdroid-android-5-0-t3836886
I followed every step (About CRAndroid), radio firmware 5.1.5 + TWRP 3.2.3 + Gapps + Magisk 17.1 and No Verity v3 (First try without noverity, second using it)
and i followed also every step neeeded in AOSPExtended rom.
When i try to boot the phone, after the OnePlus logo, nothing happens. The phone reboots in recovery mode, that's it.
If i repeat the same steps with OmniROM it works all fine, except Magisk. If i flash Magisk on the Omni it doesn't boot, if i flash SU it works.
Could it be something related to the encryption/Decription of the device?
When i go into TWRP it doesn't ask me for a pattern or a code. It should be decrypted, right? (i'm a bit confused about that).
I purchased the phone on Gearbest, could it be a particular version of the phone that doesn't allow me to work properly with roms?
Help
did you tried old stock ROMs, 4.* versions ? then 5.0.0 and then the others
Sometimes the partitions need to be wiped. Try a fastboot format userdata; fastboot format system.
azretier said:
did you tried old stock ROMs, 4.* versions ? then 5.0.0 and then the others
Click to expand...
Click to collapse
Actually when the phone arrived i've just unlocked the bootloader and installed a custom rom....what's the purpose of this?
moffa~ said:
Sometimes the partitions need to be wiped. Try a fastboot format userdata; fastboot format system.
Click to expand...
Click to collapse
You....you're a good guy.
I did the command you said, then i booted into TWRP, flashed AospExtended, Gapps Pico and Magisk 17.1 - after reboot it has been stuck @ 1+ logo, then it rebooted again (as always when it doesn't work) and i said "ok here we go again in the TWRP-loop" and INSTEAD it booted rom! Yes!
Hey guys,
I just oem unlocked my new 6T and have access to the bootloader. As I try to install TWRP with
HTML:
fastboot boot imagename.img
my computer says that it pushes the image just fine, but my phone restarts and then never makes it past the fastboot splash screen instead of loading up TWRP.
I was following the fajita (6T) instructions from the lineage OS website.
The first time I did it it worked, but following the instructions on installing lineage and telling me to wipe and format data, both the recovery seems to be gone and i cannot fastboot boot into TWRP.
Can you help?
Seems the same with what i experienced. Have you tried installing a fastboot rom? I had my oneplus 6t bootlooped into fastboot mode even if i try to turn it off, it just boots back automatically to fastboot mode. Last resort was to flash a fastboot rom. That worked for me.
thalesian2020 said:
Hey guys,
I just oem unlocked my new 6T and have access to the bootloader. As I try to install TWRP with
HTML:
fastboot boot imagename.img
my computer says that it pushes the image just fine, but my phone restarts and then never makes it past the fastboot splash screen instead of loading up TWRP.
I was following the fajita (6T) instructions from the lineage OS website.
The first time I did it it worked, but following the instructions on installing lineage and telling me to wipe and format data, both the recovery seems to be gone and i cannot fastboot boot into TWRP.
Can you help?
Click to expand...
Click to collapse
What TWRP version are you trying to install?
jp0469 said:
What TWRP version are you trying to install?
Click to expand...
Click to collapse
I tried 3.3.1.1. and 3.2.3.0.
What you are describing, I'm going to assume you are trying to install Lineage 17. You can't install TWRP if you are going Android 10, at least that's the conclusion I've come to at this point in time. It will fail to boot or end up in crash dump mode every time you try and enter recovery if you are on a custom ROM. If you are on Android 9, it's not an issue. I believe it's OK stock as well, but I don't know haven't tried, haven't been stock in a long time.
For LOS 17, only boot the TWRP image, never boot to recovery, never run the TWRP installer. You will likely still have to format data.
I have a post here, from when I had a similar issue. (instructions)
You'll notice the OmniRom instructions don't mention installing TWRP, only booting it.
Once I was in your spot, I always went back to stock using the fastboot ROM, installed TWRP, updated (still using TWRP), then started over with my install.
Well no, i was actually trying to install Lineage 16, which is Android 9 I believe.
The problem for me is that I do not get to the point where TWRP opens after "fastboot boot"ing it. So I understand, I should use a fastboot stock ROM? Is there such a thing? Where would I find it? Or would it be an OnePlus Oxygen ROM that I can fastboot?
Quickest way to start over:
To get back straight your gonna need to access a Windows PC, and run the MSM tool. Make sure you install both OnePlus and Qualcomm drivers. ( Don't wait for Windows, just pre install the drivers) here are some links. Not my work. Please be sure to thank the developers for creating and hosting these tools ?
MSM Tool:
https://forum.xda-developers.com/oneplus-6t/how-to/tool-6t-msmdownloadtool-v4-0-oos-9-0-5-t3867448
OnePlus Drivers:
https://androidfilehost.com/?fid=11410963190603879743
Qualcomm drivers:
https://androidfilehost.com/?fid=11410963190603879743
thalesian2020 said:
Well no, i was actually trying to install Lineage 16, which is Android 9 I believe.
The problem for me is that I do not get to the point where TWRP opens after "fastboot boot"ing it. So I understand, I should use a fastboot stock ROM? Is there such a thing? Where would I find it? Or would it be an OnePlus Oxygen ROM that I can fastboot?
Click to expand...
Click to collapse
Were you on Android 10 before (OOS)? That will do that. LOS 16 is Android 9 and should have no problems installing TWRP or booting to it.. For LOS 16 I'd go back to 9.0.17, then install LOS 6T.
I posted these LOS install instructions a long time ago for another user.
Remember the MSM Tool will relock your bootloader so if something goes wrong the MSM Tool is your only choice. That is why it is always the last thing I resort to.
Thread to get Fastboot stock Roms if you want to try that route first.
Hey guys,
thank you so much for all your help. I've managed to use mauronofrios workaround here on xda to put my phone in a 9.0.17 state again (no idea what i had originally), and this way i could fastboot the twrp image again. so that worked fine, but so far flashing lineage hasnt worked, for whatever reason it seems to boot into a lineageos kind of recovery only (which i didnt even know existed).
So i guess in terms of this thread the problem is solved. Thank you again!
thalesian2020 said:
Hey guys,
thank you so much for all your help. I've managed to use mauronofrios workaround here on xda to put my phone in a 9.0.17 state again (no idea what i had originally), and this way i could fastboot the twrp image again. so that worked fine, but so far flashing lineage hasnt worked, for whatever reason it seems to boot into a lineageos kind of recovery only (which i didnt even know existed).
So i guess in terms of this thread the problem is solved. Thank you again!
Click to expand...
Click to collapse
Did you see my Lineage install instructions above? LOS installs its on Recovery when you flash the ROM. When om Android 9, boot TWRP, flash the TWRP installer, reboot to Recovery, install LOS 16, flash the TWRP installer again (replaces the LOS recovery that was installed), reboot to Recovery, install gapps / magisk if desired, reboot.
Read my instructions post though, the first time install is different, as you need LOS on both slots. Updating is different as well, its much easier.
It should go smoothly.
OhioYJ said:
Did you see my Lineage install instructions above? LOS installs its on Recovery when you flash the ROM. When om Android 9, boot TWRP, flash the TWRP installer, reboot to Recovery, install LOS 16, flash the TWRP installer again (replaces the LOS recovery that was installed), reboot to Recovery, install gapps / magisk if desired, reboot.
Read my instructions post though, the first time install is different, as you need LOS on both slots. Updating is different as well, its much easier.
It should go smoothly.
Click to expand...
Click to collapse
Do I need to be on Android 9 Stock when I start that process? What I did was boot into TWRP, flash TWRP installer, reboot into recovery, then format and wipe ALL partitions (except USB), then reboot into recovery again and then flash LOS, flash TWRP, reboot into recovery, flash LOS, flash TWRP, reboot system. Still no luck...
thalesian2020 said:
Do I need to be on Android 9 Stock when I start that process? What I did was boot into TWRP, flash TWRP installer, reboot into recovery, then format and wipe ALL partitions (except USB), then reboot into recovery again and then flash LOS, flash TWRP, reboot into recovery, flash LOS, flash TWRP, reboot system. Still no luck...
Click to expand...
Click to collapse
Wiping, Dalvik / ART, System, and Vendor is generally a bad idea. You can do them in certain situations, this isn't one of those situations you should be wiping those though. Factory reset, means the slider on the main page of the wipe screen that says swipe to factory reset, format data is the button that says format data. Don't do anything extra. If you did, yeah I would go back to 9.0.17 using the fastboot rom again, that will put everything back on both slots.
like OhioYJ stated, don't use advanced wipe. re-run the msm tool. Then follow his instuctions. You shouldn't need to preform any manual data wiping. The process of flashing will do everything required. looks like you're almost there
Thanks guys. I will try it out and let you know.
Edit: So I finally managed to properly install LOS - OhioYJ, your instructions worked! I installed 9.0.17 and went from there without wiping any additional partitions.
One questions remains: in your instructions you mention that after installing LOS once, you can update LOS as normal and you mention doing it via the recovery with flashing TWRP or GAPPS later again. Is it possible to do the update via the normal update function of LOS as well? Or will that overwrite TWRP?
You guys are awesome. Thank you so much for your help!
I seem to be stuck on the fastboot screen as well. Being on a MAC, anytime i try to do something in fastboot it goes straight back to the fastboot screen. I Thought I was on Android 10.0 trying to install recovery for that lead to bootloop of fastboot, tried using the Pie recovery and same thing. I am open to suggestions.
Thanks.
OhioYJ said:
What you are describing, I'm going to assume you are trying to install Lineage 17. You can't install TWRP if you are going Android 10, at least that's the conclusion I've come to at this point in time. It will fail to boot or end up in crash dump mode every time you try and enter recovery if you are on a custom ROM. If you are on Android 9, it's not an issue. I believe it's OK stock as well, but I don't know haven't tried, haven't been stock in a long time.
For LOS 17, only boot the TWRP image, never boot to recovery, never run the TWRP installer. You will likely still have to format data.
I have a post here, from when I had a similar issue. (instructions)
You'll notice the OmniRom instructions don't mention installing TWRP, only booting it.
Once I was in your spot, I always went back to stock using the fastboot ROM, installed TWRP, updated (still using TWRP), then started over with my install.
Click to expand...
Click to collapse
Twrp is working fine with Android 10, using mauronofrio version and magisk 20.2
callumbr1 said:
Twrp is working fine with Android 10, using mauronofrio version and magisk 20.2
Click to expand...
Click to collapse
Yeah it starting to seem like it maybe isolated to Lineage. You cant install TWRP with LOS 17. Someone else mentioned in the Omni thread that it worked. This thread is about Lineage, but that should be clarified, or clearer.
I installed TWRP 3.1.1 using the ODIN patched version and was successful. I had let the system boot into the samsung original stock from where you see "HI" then I rebooted it into TWRP to attempt flashing and I got the /data partition couldn't be wiped. So I ran some of the other repair functions in TWRP and that appear to have fixed it. I then flashed with the latest LineageOS, Gsap, and Magistk20. When it boots up the LineageOS I'm stuck on the Lineage Splash screen. I've let it run over night and it has't changed anything. Any advice?
I recommend trying to wipe the system and reinstall LineageOS with flashing Magisk. If the same problem occurs. Just wipe the system and flash LineageOS without installing Magisk.
secretwolf98 said:
I recommend trying to wipe the system and reinstall LineageOS with flashing Magisk. If the same problem occurs. Just wipe the system and flash LineageOS without installing Magisk.
Click to expand...
Click to collapse
Here's how I think I fixed it.
booted into TWRP
advanced wipe, Factory reset
booted it into TWRP
Flashed the LineageOS
boot into LineageOS
boot it into TWRP
flashed the Gapps.
I'm up and running now. I tried different iterations and It really bothered me because it worked fine on another one. I was also at time flashing it with SuperSU and other times with Magisk. It didn't matter which one I used it got stuck on the LineageOS splash screen.
dizzymon said:
Here's how I think I fixed it.
booted into TWRP
advanced wipe, Factory reset
booted it into TWRP
Flashed the LineageOS
boot into LineageOS
boot it into TWRP
flashed the Gapps.
I'm up and running now. I tried different iterations and It really bothered me because it worked fine on another one. I was also at time flashing it with SuperSU and other times with Magisk. It didn't matter which one I used it got stuck on the LineageOS splash screen.
Click to expand...
Click to collapse
By the way, it's called the boot animation. The splash screen is like the Samsung screen that says powered by Android.
Possible corrupted file
secretwolf98 said:
By the way, it's called the boot animation. The splash screen is like the Samsung screen that says powered by Android.
Click to expand...
Click to collapse
So far you're quite correct I personally have three SM-T580's and they all seem to work just a little bit different. Might I suggest doing an MD5 Sumcheck? The device shouldn't be getting into a bootloop unless there was something wrong with the files, or the device.