TWRP seems to keep crashing when installing any rom it never gets to full 100%
Whenever it hits 'system' while installing TWRP just reboots completely
Any ideas?
Bump
I've never ran into that Issue & I have used every version of TWRP that has been available to date. Helps to know what model you have & what you were trying to flash.
Related
Hello there!
I’m currently the newest Nougat image (7.0.0 NBD90Z). Before flashing to this version I was on the latest marshmallow image (6.0.1 MOB31H). Initially I dirty-flashed the image, keeping the data partition intact.
However, after I tried to root the phone with SuperSU 3.78 SR1 via TWRP recovery I got into a bootloop. After restoring stock again, I backed up my data partition (nandroid backup) and did a clean flash. On the clean ROM rooting works just fine - when I tried restoring my data partition after root was up the phone got into a bootloop again.
I repeated my experiments with SuperSU 3.78 (non-SR) and 3.76 - same results.
It seems the phone gets stuck quite late into the booting process since it is detected by my PC and listed under adb (as offline, mind you).
I don't even know how to begin to analyze or debug this problem since rooting and even dirty-flashing between major versions has been working for me since Nexus 4 / KiteKat times.
Letting go of all my userdata (at least entirely) is not an option.
Any ideas or directions how I could proceed into tracking down the problem?
The newest TWRP 3.2.3.-1 does not let me boot into ROM, just brings me back to TWRP again. I have to restore a backed up boot image (with 3.2.3-0) to boot normally. Even flashing TWRP 3.2.3-0 in TWRP does not bring me back.
Anyone else having experiencing this? I have attached my recovery logs.
I was on stock ...and just install los16 without problem... So i dont have problems with TWRP.
Resolved.
After dirty flashing the ROM zip/GAPPs and flashing TWRP, I was able to boot successfully. I Then just saved a new backup including the newest TWRP.
It is strange that just flashing TWRP would make the OS unbootable.
jhedfors said:
Resolved.
After dirty flashing the ROM zip/GAPPs and flashing TWRP, I was able to boot successfully. I Then just saved a new backup including the newest TWRP.
It is strange that just flashing TWRP would make the OS unbootable.
Click to expand...
Click to collapse
There is always a risk when flashing your device. One of the reasons why I prefer to flash using Linux was that Windows would have so much going on in the background that I risked the data transfer being corrupt. That said, if you're using Windows, I'd close all programs and especially disable any anti-virus running in the background. Sure, Linux may have a few things running, but I have always found it did a better job multitasking resources than Microsoft Windows with a fewer chance of data loss.
It is probably because after installing Google Apps, your /data partition gets corrupted.
So after installing Google Apps, go to TWRP > Wipe > "Format Data" & reboot.
I've the same problem & this resolves the issue for me.
For me, this did not help. I had to reflash everything from bootloader.
Funny thing is: it just has downloaded and installed an OTA update. With open bootloader.
I ran into this issue yesterday when a bad flash caused the infamous "no bootable A/B" error. After I resolved it and install TWRP I kept being rebooted back into TWRP. The 3.2.3-0 version resolved everything. I really do believe 3.2.3-1 is a bit buggy. I mean it works, but once you really start to use it more than the average user, you start to notice little things.
I too had this same issue. Eventually realized that updating TWRP by flashing zip from TWRP caused it. I had to flash stock boot partition, then follow the process for flashing TWRP as if you are flashing it for the first time (first boot into TWRP and then flash the corresponding zip). This resolved the issue.
Hello to all.
So, I have the N950F (international Exynos) which generally works fine, but It started being weird for some reason. I installed TWRP on day one, used IronMan ROM since day one and everything worked. I still use IronMan 2.0 (Oreo) since I don't really like the One UI, and I debloated the ROM piece by piece until I overdid it and the Contacts app stopped working properly. When I tried reinstalling (with a full wipe), TWRP crashed and the device would bootloop, so, as usual, I redownloaded the zip (and verified checksums), and the exact same thing happened. As it turns out I can't install anything on the device, TWRP crashes on installation every time and the ROMs bootloop.
Observed hint: the installation always crashes on steps related to the boot image, regardless of bootloader version installed.
Steps taken: tried every available TWRP version (including unofficial ones), tried different bootloaders, tried different ROMs (Oreo and Pie), tried flashing with full wipe and dirty. The problem persists.
After the installation crash I sometimes get "E:Legacy property environment did not initialize successfully. Properties will not be detected.". Subsequent attempt results in Aroma claiming the ROM is for greatlte and current device is "" and stopping immediately.
backup/restore in TWRP works fine which turned out to be my saving grace.
Enclosed are TWRP logs including a large last_log from /cache/recovery and a screenshot of current system version (but the problem persists on every bootloader/system configuration). I went through them, but couldn't find anything relevant, so any help will be greatly appreciated. I might be just dim and missing something obvious.
TalkingChicken said:
Hello to all.
So, I have the N950F (international Exynos) which generally works fine, but It started being weird for some reason. I installed TWRP on day one, used IronMan ROM since day one and everything worked. I still use IronMan 2.0 (Oreo) since I don't really like the One UI, and I debloated the ROM piece by piece until I overdid it and the Contacts app stopped working properly. When I tried reinstalling (with a full wipe), TWRP crashed and the device would bootloop, so, as usual, I redownloaded the zip (and verified checksums), and the exact same thing happened. As it turns out I can't install anything on the device, TWRP crashes on installation every time and the ROMs bootloop.
Observed hint: the installation always crashes on steps related to the boot image, regardless of bootloader version installed.
Steps taken: tried every available TWRP version (including unofficial ones), tried different bootloaders, tried different ROMs (Oreo and Pie), tried flashing with full wipe and dirty. The problem persists.
After the installation crash I sometimes get "E:Legacy property environment did not initialize successfully. Properties will not be detected.". Subsequent attempt results in Aroma claiming the ROM is for greatlte and current device is "" and stopping immediately.
backup/restore in TWRP works fine which turned out to be my saving grace.
Enclosed are TWRP logs including a large last_log from /cache/recovery and a screenshot of current system version (but the problem persists on every bootloader/system configuration). I went through them, but couldn't find anything relevant, so any help will be greatly appreciated. I might be just dim and missing something obvious.
Click to expand...
Click to collapse
Some solutions:
> Firmware reset via Odin. There's a few guides on how to do that, it should fix your issues.
> If you get into TWRP, wipe your directories, mainly ones like /data, and reboot back to TWRP. Not system.
> Try a different rom/zip.
> Try older versions of TWRP if you can. TWRP is recovery.img, not boot.img, so it shouldn't be crashing unless you bonked up recovery.img. You could try flashing the stock one, or flash stock via odin again.
After installing at least one Magisk module the phone bootloops every 2nd reboot and it is consistent. Flashing a no-verity zip gives a few more reboots before bootlooping but the issue is quite annoying because I need to restore a backup from TWRP every time a bootloop occurs, so I have to reinstall everything again.
Maybe returning to full stock firmware (I have the original boot image, but not the original recovery) can help, but the lolinet mirrors do not have the latest firmware available.
Apparently, wiping data after restoring backup helped a lot, phone has survived 5 reboots so far with 2 Magisk modules flashed
Nevermind, latest reboot was a bootloop, but I think the culprit here is the Magisk Manager for Recovery Mode, I will restore backup again and see if that module is the cause of it
If it helps, TWRP showed an error before cleaning caché:
"E:Error creating fstab"
Hi, I got a situation here. I had to reinstall the rom in my Note 7 Pro after nearly 2 years from teh last time I had to do it.
Unfortunately, I had no idea that the new Magisk version can't be flashed by custom recoveries anymore. I simply flashed my rom using Orange Fox, restarted to the system, used the cell for 2 days, installed everything I needed, and yesterday I downloaded the latest 24310 Magisk version, flashed it using my custom recovery, and restarted in the system again.
Magisk greeted me with a message that it needed extra setup to be fully functional. I restarted in recovery, nothing happened, restarted to system, Maghisk still stuck in the need extra setup to be functional. I resolved to uninstall it using the app, got an error message in the console, tried restoring images, another error. Tried to reboot to recovery to try to reflash magisk, no more recovey, gone. Used adb to reflash recovery, rebooted to it, now I have a message that says Error opening: 'data/adb/magisk' (operation not permitted). Tried to use the Orange Fox option to remove Magisk, got some error messages Error opening: 'data/adb/magisk' (operation not permitted), but it said it was done. Tried to reboot, stuck in boot loop, back in recovery, dirty flashed my actual ROM, still stuck in boot load.
Any way to delete this locked magisk folder to try to completely remove magisk and try to reinstall it the correct way now? Or the only solution is a complete reinstallation of the ROM formatting all partitions? I haven't tried it yet because after 2 years of doing this procedure I barely remember how to do a clean install correctly.
Blackdragonbird said:
Hi, I got a situation here. I had to reinstall the rom in my Note 7 Pro after nearly 2 years from teh last time I had to do it.
Unfortunately, I had no idea that the new Magisk version can't be flashed by custom recoveries anymore. I simply flashed my rom using Orange Fox, restarted to the system, used the cell for 2 days, installed everything I needed, and yesterday I downloaded the latest 24310 Magisk version, flashed it using my custom recovery, and restarted in the system again.
Magisk greeted me with a message that it needed extra setup to be fully functional. I restarted in recovery, nothing happened, restarted to system, Maghisk still stuck in the need extra setup to be functional. I resolved to uninstall it using the app, got an error message in the console, tried restoring images, another error. Tried to reboot to recovery to try to reflash magisk, no more recovey, gone. Used adb to reflash recovery, rebooted to it, now I have a message that says Error opening: 'data/adb/magisk' (operation not permitted). Tried to use the Orange Fox option to remove Magisk, got some error messages Error opening: 'data/adb/magisk' (operation not permitted), but it said it was done. Tried to reboot, stuck in boot loop, back in recovery, dirty flashed my actual ROM, still stuck in boot load.
Any way to delete this locked magisk folder to try to completely remove magisk and try to reinstall it the correct way now? Or the only solution is a complete reinstallation of the ROM formatting all partitions? I haven't tried it yet because after 2 years of doing this procedure I barely remember how to do a clean install correctly.
Click to expand...
Click to collapse
Reflash the stock unrooted boot.img of your room in bootloader. Use adb
Fastboot flash boot boot.img
Similar problem here...
I tried reflashing stock recovery and stock boot.img - now whenever I reboot it just boots into recovery! I don't seem to be able to boot into system any more...
Any ideas?
I'm running AOSIP on a Xiami Mix Mi 3 - I hadn't updated to the latest Magisk in quite some time (since before the app could do it automatically). I have to use the recovery method.
Steps I took are:
Get recovery.zip from my ROM, patched it through the app, then flashed through fastboot. I rebooted while holding down the up arrow to reboot into recovery, then released for the phone to boot.
I got an error after booting that said "there's an internal error with your device" - and it was super buggy, couldn't tap the screen, super slow to load stuff, etc.... I figured it was a magisk issue, so tried to reflash recovery and boot... Not I'm stuck booting into recovery!
Help.
Edit: so - I think it turns out I have one of those RARE xiaomi devices that DOES have ramdisk even though the app doesn't detect it... Go figure. A clean install of the ROM, followed by patching the BOOT image rather than the recovery image - and we're up and running.