Hello
I've installed a couple of ROMs via TWRP. Some work, some don't.
But now, even when I try to install ROMs I had already installed previously, the installation fails.
I get a message "Update process ended with signal 7
Error installing file"
What to do ?
I guess this happens if you not wipe data and reboot before installing. But only if TWRP version installed on your phone and the TWRP version from the phone that made the backup are different.
You van use this http://forum.xda-developers.com/showthread.php?t=2522762
It helped me.
Related
Hi,
when I try to install the unofficial CM cwm recovery quits with status 7 and says something about installing on top of invalid data.
The official OTA Update to KitKat failed too. This was why I unlocked the bootloader and installed cwm . Any suggestions?
I already tried to remove the device checks from the update script in the cm rom like suggested many times to solve status 7, didn't work for me.
EDIT: Updatet CWM to v6.0.5.1, still not working
EDIT2: After trying the OTA Update again with CWM 6.05.1 the device is in a bootloop now.
CWM says that the signature verification failed and asks to install anyway. If I do it files with status 7 and reboots, reboots again. and tries to install again. If i don't it reboots, reboots again...
Have you done the wipe/factory reset directly before flashing the cm11 rom?
check hazous initial post for cm11 rom
Well, I did a factory reset, but I did't it not immediately before rom installation.
Anyway, it worked now. Thanks for the rtfm pointsatme...
So I recently tried to upgrade to S433 rom. I had taken a Nanadroid backup but my recovery was old cwm so I flashed TWRP 2.8 and now TWRP doesn't show my backup but even although old CWM was able to restore the backup it never booted it just went into boot loop.
So I tried flashing a new ROM through TWRP but it's always getting zip verification failed although I think that those are proper signed Roms. Ive tried two Roms and both are giving the same error.
Nothing happens when I use SP flash so I am assuming that there's some problem with drivers on Win 7.
So what should or could I do now?
I can boot into the TWRP recovery.
If I turn off zip verification, it just goes into TWRP instantly.
Flash SP is your best bet..Did SP tools see your phone? If not then try searching for drivers
Try Androium rom flashed with 3.0.2 twrp. Format data, cache, dalvik, system before flashing. Never gave me a problem.
So, I recently installed TWRP on my SM-T813. I then flashed LineageOS 14.1 successfully, but didn't like it, so I reflashed stock ROM. Everything was working fine, until I tried to install SuperSU on my stock ROM.
Now, my tablet is stuck into booting recovery mode, and cannot boot into the ROM (although Download Mode is still usable, more on that later). Upon trying to reflash the backup again, and attempting to reboot, TWRP states "No OS installed!" SO I tried reflashing the LineageOS ROM, same thing. Upon trying to restore a firmware with Odin, I get an error saying "SW REV CHECK FAIL aboot Fused 2 Binary 1." After finding no answers, I delved into my SD card and found that I had flashed the WRONG version of SuperSU, although it had been cleared when reformatting with TWRP. I then tried using the CORRECT SuperSU, and I am still stuck in recovery bootloop.
Can someone analyze what's going on and see what the problem is?
(SM-T813 - USA)
Lucarje said:
So, I recently installed TWRP on my SM-T813. I then flashed LineageOS 14.1 successfully, but didn't like it, so I reflashed stock ROM. Everything was working fine, until I tried to install SuperSU on my stock ROM.
Now, my tablet is stuck into booting recovery mode, and cannot boot into the ROM (although Download Mode is still usable, more on that later). Upon trying to reflash the backup again, and attempting to reboot, TWRP states "No OS installed!" SO I tried reflashing the LineageOS ROM, same thing. Upon trying to restore a firmware with Odin, I get an error saying "SW REV CHECK FAIL aboot Fused 2 Binary 1." After finding no answers, I delved into my SD card and found that I had flashed the WRONG version of SuperSU, although it had been cleared when reformatting with TWRP. I then tried using the CORRECT SuperSU, and I am still stuck in recovery bootloop.
Can someone analyze what's going on and see what the problem is?
(SM-T813 - USA)
Click to expand...
Click to collapse
This has been posted a million times all over the forum. A quick search here or Google would have revealed the answer
You need to flash a revision 2 firmware. So that would be something like t813xxu2 in the firmware build number.
Sorry for being late with reply. Your advice helped me fix my tablet! Thanks so much!
I unlocked the bootloader, installed twrp 3.2.1 nicklaus. The higher version didn't work.
The problem is that I can't install roms, no zip packages from twrp, because after selecting "swipe to confirm flash", the display turns off and takes me back to the twrp startup screen.
I'm trying to install LineageOS 15.0 Nicklaus. Same problem with other custom roms. I was cleaning cookies, etc. As a last resort, I reinstalled the rom, but that didn't help either.
I have run out of ideas about what went wrong.
I noticed that if I restart my phone then I can't enter TWRP. I have "No command" message. I have to reinstall TWRP every time. Maybe that's the problem ...
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.