SOLVED So I booted, not flash TWRP and went pushed the open gapps Aroma zip to my external sd. Then I flash AROMA, went through the process there, then executed it. But I don't think it did anything. I manually exited Aroma only find myself stuck in TWRP. I cannot reboot to system. Ive erased data,system, everything, and the phone keeps booting into TWRP, Wtf? Any ideas how to get to my bootloader, let alone the system??
theburrus1 said:
SOLVED So I booted, not flash TWRP and went pushed the open gapps Aroma zip to my external sd. Then I flash AROMA, went through the process there, then executed it. But I don't think it did anything. I manually exited Aroma only find myself stuck in TWRP. I cannot reboot to system. Ive erased data,system, everything, and the phone keeps booting into TWRP, Wtf? Any ideas how to get to my bootloader, let alone the system??
Click to expand...
Click to collapse
How did you solve it?
Related
Hi,
I was running Oxygen 4.0.0 and a beta build of TWRP 3.0.3 which works with new encryption. I used the android update mechanics to get the 4.0.1 OTA. System rebooted to recovery, recovery threw an error (zip file corrputed) and since then I am not able to boot the system. Whatever I do I land in TWRP recovery.
Things I did so far:
- Tried installing the full 4.0.1 zip. Install worked without errors, device still boots to recovery.
- Tried to get stock recovery, since another post (https://forum.xda-developers.com/oneplus-3t/help/stuck-recovery-mode-t3532524) indicates stock recovery might fix the problem
--> stock recovery is not obtainable anymore. Seems deleted from all the download links I could find. Example is here: https://forum.xda-developers.com/oneplus-3t/how-to/zip-flashable-firmware-modem-t3509015
- Wipe cache and dalvik cache in the hopes, the instruction to boot to recovery is there somewhere.
I did not do the unbrick tool, since I run linux and didnt want to fiddle with windows yet.
I did make a nandroid backup, so once my system boots again I should be fine.
Any Idea where to either get a mirror of stock recovery or how to fix this problem otherwise?
I had this same problem, and I solved downloading the unbrick tool and extracting the recovery from there. Here is the file
https://drive.google.com/file/d/0BwaafKaXbak3d1RFblFOWVd5eGs/view?usp=sharing
Also locking the bootloader worked for me. Booted into system then unlocked again.
Thanks a lot for the stock recovery. That worked!
Once it booted, installing TWRP and SuperSU again.
mad-murdock said:
Thanks a lot for the stock recovery. That worked!
Once it booted, installing TWRP and SuperSU again.
Click to expand...
Click to collapse
Does your TWRP boot correctly? I flashed it and when I restarted I still had the stock recovery, so I used fastboot boot and it booted, but it is stuck in the loading screen.
Edit: After rebooting and reflashing totally random, it worked.
mariospizza said:
Does your TWRP boot correctly? I flashed it and when I restarted I still had the stock recovery, so I used fastboot boot and it booted, but it is stuck in the loading screen.
Edit: After rebooting and reflashing totally random, it worked.
Click to expand...
Click to collapse
Yeah, worked totally normal as it should.
My educated guess about this whole dilemma is, the system sets a flag to boot to recovery which TWRP doesn't clear and only stock recovery clears. Usually those flags should be in cache partition, but in this case isn't.
Tldr: don't use build in update mechanisms if you modified Rom and recovery.
So I tried reinstalling LOS, but I got an error: failed to update system image. So I wiped EVERYTHING. the internal storage, data, cache, everything. Then I reinstalled it. Same error but it said success. So I tried rebooting to the system, NOPE, straight to TWRP. Now I was scared. Why is this happening?? So I tried reinstalling twrp, changing the rom, but nothing fixed it. Now, nothing will boot other than TWRP. I try the bootloader, straight to twrp. I try system, straight to twrp. I try fastboot, straight to twrp. Please help, I need to keep my snapchat streaks alive :crying::crying:
I would try to install lg stock rom and then root, unlock bootloader, twrp and finally lineageos.
I'm having a similar nightmare. I have a D415 running running LineageOS 14.1. I downloaded the February 24th update and clicked on it. That booted me into TWRP. I wasn't sure what to do next, so I tried to reboot into the system but it send me straight back to TWRP. Then I booted into recovery, I think, and figured out how to install the update. However, I still couldn't boot the system. Then, I tried to restore the system . Everything seemed to go fine, but TWRP just looped me back to TWRP.
Just to be clear, is the correct method of booting to the system to select "reboot", then "system"? Is there any other method?
On the main screen, there's a selection called "Mount". If I click on it, I see "Select Partitions to Mount" . The top selection, "System", is unticked. I tried ticking it and rebooting, but was still returned to TWRP.
I was in the same boat....
Hey everyone, I'm hoping this works for you like it did for me. I'm a avid fan of the Linage OS and TWRP-- I donate to them like they're a charity! Lol....
Any who, I constantly check weekly for my "nightly" fix; however dread the update due to the TWRP loop. So, I decided to download the update via my phone browser to the SD card, and update manually.
What do you know, no TWRP loop! I use to have to go thru a 4 line script I found online to boot up to the system. So basically, go to recovery and install the update manually. Don't let the updater do it for you. If you are using Linage SU and Xposed, remember to reinstall.
---------- Post added at 03:12 AM ---------- Previous post was at 02:58 AM ----------
I found the script on Reddit under Linage OS: "How to fix TWRP boot loop after OTA. The article says it's only for MAKO devices; however, due desperation I tried it and it worked.
Use the l90 repartion tool
If u have a custom recovery use LG optimus l90 Reparation tool . Pick the stock option. It'll reboot then start again to finish. When it's done you'll be in clockwork recovery. Don't worry if u had twrp. Mount system then flash a cm based rom plus apps. See if it works.
I got distracted by life, but this weekend I put in some hours working on the phone again. The phone is stuck in TWRP 3.1.1-0. After endless misery, it seems it had a corrupted SD card. I've got a new 32gb SDHC in FAT32. I put lineage-14.1-20181007-nightly-w7-signed.zip on the card and put the card in the phone. Then I browsed to "install" and selected "sdcard (29648mb)". However, the zip file doesn't appear. There's just a folder that says "(Up A Level)". If I click that, there's a ton of empty folders.
How come the zip file doesn't appear? How can I install Lineage?
Here's more stuff I've tried:
installed Java (necessary for ADB, I think) for Windows 7
Installed universal ADB drivers
Plugged in phone
Followed instructions on https://www.xda-developers.com/install-adb-windows-macos-linux/ "Microsoft Windows ADB Setup”
Opened ADB, typed "ADB Devices"
My phone not detected.
Windows sees it as "target_device=w7"
Tried installing LG drivers. No love.
Hi,
I unlocked the bootloader on my Oneplus 3T, then flashed TWRP. Unfortunately I misread and tapped on the read-only bit, and since then I am not able to boot into TWRP after the first time.
These are my steps (which I am trying over and over)
- fastboot;
- flash TWRP with fastboot flash recovery recovery.img
- disconnect the phone and shutdown
- boot into recovery with power/vol-
- twrp boots; I reboot into system
- system boots; i shut down
- boot into recovery with power/vol-
- the default recovery loads instead of TWRP.
I tried ticking and unticking the checkbox for read only under Mount in TWRP; I tried restoring the full backup. Every time it keeps going into the default recovery
from TWRP, I can shut down and boot into recovery and I'll get TWRP. I can reboot into recovery and I'll get TWRP. But as soon as I reboot into system, TWRP is gone
any ideas?
https://forum.xda-developers.com/on...elp-thread-t3509641/post75240034#post75240034
eLcTrOn said:
https://forum.xda-developers.com/on...elp-thread-t3509641/post75240034#post75240034
Click to expand...
Click to collapse
hm, ok thanks; I must have missed that bit.
I flashed TWRP again, then installed SuperSU from it. It went fine, then it prompts me to reboot. upon reboot I am using root checker and it says it's not done. I reboot into recovery and I get the default one again...
edit: nevermind, I used another zip for supersu and it worked. now it boots into twrp, many thanks.
Wouldn't it be better to use Magisk?
przemcio510 said:
Wouldn't it be better to use Magisk?
Click to expand...
Click to collapse
I flashed FreedomOS with Magisk at the end.
I was trying to root my phone and had already unlocked by bootloader, flashed TWRP, and made a NANDroid backup. I had the Magisk zip from Magisk Manager on my SD card. I booted into TWRP using the commands
Code:
adb reboot bootloader
Code:
fastboot flash recovery twrp-3.2.3-0-ali.img
and
Code:
fastboot boot twrp-3.2.3-0-ali.img
Once in TWRP, I mounted the cache, vendor and micro SD card partitions. I unmounted them immediately afterwards and then installed the Magisk zip file. The reason that I mounted and unmounted the SD card was because, based on me trying random things, it was the only way for TWRP to show the zip file. Afterwards, I rebooted the system, the "Your device has been unlocked and can't be trusted" screen came up as normal, except that where it said "bad key" before, it said "N/A". The device did not move past this screen and instead stayed at that screen. I managed to turn it off by holding the power button for far longer than normal. I then booted my phone into TWRP and restored a previous backup. Is there a potential cause for this? Is there an alternative method of rooting that I'm not aware of?
did you install the no verity boot for your variant?
The only thing I installed was the zip. If it wasn't in the zip, then I didn't install it. How would I install that and where would I get it?
lucror said:
The only thing I installed was the zip. If it wasn't in the zip, then I didn't install it. How would I install that and where would I get it?
Click to expand...
Click to collapse
Check this thread
https://forum.xda-developers.com/mo...oot-magisk-installation-t3816569/post77074751
Will the fact that I have already tried to install Magisk affect the process? I did flash my TWRP backup, so would that have any bearing on the process? Sorry if these are basic questions, I haven't rooted a phone before and I'm trying to be very cautious.
lucror said:
Will the fact that I have already tried to install Magisk affect the process? I did flash my TWRP backup, so would that have any bearing on the process? Sorry if these are basic questions, I haven't rooted a phone before and I'm trying to be very cautious.
Click to expand...
Click to collapse
Nope, you're overwriting the boot image when flashing no-verity so Magisk would be gone anyways.
Okay. Thank you for your help everyone. I'll try that when I get the chance.
Tried a bunch of things to make the TWRP installation persistent, but it just goes back to MIUI recovery when i reboot from the system.
I'm using TWRP 3.5.2 by Nebrassy.
USB debugging turned on
Correct drivers installed
fastboot devices work Using minimal ADB and fastboot
I have the file renamed as TWRP.img.
Steps i followed:
fastboot boot "TWRP.img" - Correctly boots into TWRP
install the TWRP image to the recovery partition - Happens with no errors
Reboot to system - No errors there as well
Reboot to recovery - Goes back to MIUI recovery.
Can someone please tell me what i should do?
PS: Tried with TWRP 3.6.0 as well just now. Same issue.
Helhound0 said:
Tried a bunch of things to make the TWRP installation persistent, but it just goes back to MIUI recovery when i reboot from the system.
I'm using TWRP 3.5.2 by Nebrassy.
USB debugging turned on
Correct drivers installed
fastboot devices work Using minimal ADB and fastboot
I have the file renamed as TWRP.img.
Steps i followed:
fastboot boot "TWRP.img" - Correctly boots into TWRP
install the TWRP image to the recovery partition - Happens with no errors
Reboot to system - No errors there as well
Reboot to recovery - Goes back to MIUI recovery.
Can someone please tell me what i should do?
PS: Tried with TWRP 3.6.0 as well just now. Same issue.
Click to expand...
Click to collapse
Try again to flash TWRP dirty and if it's started don't boot with software. You have to boot TWRP again by pressing volume + and power button until you'll get vibration , afterwards you'll be in TWRP again, clear dalvik and cache and restart system via TWRP menu
Laptapper said:
Try again to flash TWRP dirty and if it's started don't boot with software. You have to boot TWRP again by pressing volume + and power button until you'll get vibration , afterwards you'll be in TWRP again, clear dalvik and cache and restart system via TWRP menu
Click to expand...
Click to collapse
Sorry mate that didn't work. Still going back to stock recovery...
Since i didn't find a solution to make the installation presistant, i went ahead and flashed Elixir with the temporarily booted TWRP. Then wiped cache and dalvik, flashed the TWRP image, formatted data and then rebooted. Now it works.
Edit: This method did something to my recovery. I can boot to system and recovery fine but TWRP isn't able to mount the data partition. So i'm not able to flash anything or root the device anymore.
I tried formatting data, no luck.
Then tried repairing the data partition. No luck.
Changed the file system to EX2 and then EX4... Nothing.
Anyone know a solution for this?
Helhound0 said:
Sorry mate that didn't work. Still going back to stock recovery...
Click to expand...
Click to collapse
Then you've got to do a flash with stock ROM and miflash via pc
Laptapper said:
Then you've got to do a flash with stock ROM and miflash via pc
Click to expand...
Click to collapse
Would that re-lock the bootloader? And if so do i have to wait 7 more days for it to be unlocked?
I used the Disable-Dm-Verity-Zip directly in TWRP after installation. Worked without a problem.
romuser87 said:
I used the Disable-Dm-Verity-Zip directly in TWRP after installation. Worked without a problem.
Click to expand...
Click to collapse
I read that somewhere too but that didn't help me at all... Maybe i have a bad zip file..
Can you share the zip you flashed?
Also, any idea how i could get this fixed:
Helhound0 said:
Since i didn't find a solution to make the installation presistant, i went ahead and flashed Elixir with the temporarily booted TWRP. Then wiped cache and dalvik, flashed the TWRP image, formatted data and then rebooted. Now it works.
Edit: This method did something to my recovery. I can boot to system and recovery fine but TWRP isn't able to mount the data partition. So i'm not able to flash anything or root the device anymore.
I tried formatting data, no luck.
Then tried repairing the data partition. No luck.
Changed the file system to EX2 and then EX4... Nothing.
Anyone know a solution for this?
Click to expand...
Click to collapse
Helhound0 said:
I read that somewhere too but that didn't help me at all... Maybe i have a bad zip file..
Can you share the zip you flashed?
Also, any idea how i could get this fixed:
Click to expand...
Click to collapse
The attached file worked for me
Helhound0 said:
Would that re-lock the bootloader? And if so do i have to wait 7 more days for it to be unlocked?
Click to expand...
Click to collapse
1. With MiFlash there is an option at the bottom of the screen to lock bootloader. Just make sure it is NOT checked, and you will be safe to use MiFlash without relocking bootloader.
2. When installing TWRP for first time, it is essential that your first reboot is straight back to TWRP - then it becomes persistent, and future reboots to recovery will be to TWRP. If you do not do the first reboot back to TWRP, the stock MIUI ROM recovery reinstalls itself.
HiQual said:
1. With MiFlash there is an option at the bottom of the screen to lock bootloader. Just make sure it is NOT checked, and you will be safe to use MiFlash without relocking bootloader.
2. When installing TWRP for first time, it is essential that your first reboot is straight back to TWRP - then it becomes persistent, and future reboots to recovery will be to TWRP. If you do not do the first reboot back to TWRP, the stock MIUI ROM recovery reinstalls itself.
Click to expand...
Click to collapse
The first ever twrp install i did, i rebooted to system by mistake but i reflashed twrp and made sure to reboot to recovery.... That was the second try. I think i may have tried at least two dozen times since that but it just kept booting back to stock recovery...
I think I'll run with this until the end of Jan and then redo everything from scratch...
Helhound0 said:
Since i didn't find a solution to make the installation presistant, i went ahead and flashed Elixir with the temporarily booted TWRP. Then wiped cache and dalvik, flashed the TWRP image, formatted data and then rebooted. Now it works.
Edit: This method did something to my recovery. I can boot to system and recovery fine but TWRP isn't able to mount the data partition. So i'm not able to flash anything or root the device anymore.
I tried formatting data, no luck.
Then tried repairing the data partition. No luck.
Changed the file system to EX2 and then EX4... Nothing.
Anyone know a solution for this?
Click to expand...
Click to collapse
I'm stuck at this stage. Have you found any solution yet?