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...
Related
I am unable update my HTC One with MaximusHD 32.0.0 to 33.0.0. I have TWRP 2.6.3.3 and I am trying to flash the OTA 32.0.0-33.0.0 zip, but my phone reboots before the installation completes. The whole aroma installer process works, it gets me to choose a language and select a mod, but when it gets to the screen that says the process of the installation, it reboots. It stays at 0%, then just turns on without me touching anything. Does anyone know what I can do? I want to update it to the newest version, but I don't want to wipe my device. Thanks in advance.
Here is the link to the custom ROM: http://forum.xda-developers.com/showthread.php?t=2189373
*EDIT* I was finally able to figure out how to update my ROM without wiping my device. I just had to download the MaximusHD 33.0.0 zip that wasn't an OTA one and it gave me an option to update only and not wipe the device.
So today I received a XT 1056. I then proceeded to unlock the bootloader and flash SU.
So I then tried flashing a CM 12 nightly build and all went well. I was able to setup the device until the screen was locked and then the phone instantly starts looping through the "Unfortunately, system UI has stopped." error. I've tried flashing an older version of the ROM, and I've tried numerous other 5.0 ROM's but each one will crash as soon as the screen is locked.
And it would not seem like a great idea to revert to an older version of Android and risk bricking the device.
So if someone could advise me how to get rid of the loop error it would be much appreciated.
I have TWRP 2.8.3 currently flashed if that makes any sort of difference....
Install the gApps...
690sid said:
Install the gApps...
Click to expand...
Click to collapse
I tried a fresh install of this CM12 with the gapps it says to use and once again I can setup the phone and as soon I get to the home screen the system UI loop happens. http://forum.xda-developers.com/moto-x/development/rom-unofficial-nightly-lollipop-5-0-t2960768
I also saw your post in that thread to try flashing with these instructions, but it still has the same error.
1 - Download an earlier version of the ROM that booted on you phone along with the gapps.
2 - Flash the ROM and gapps with a suitable recovery... CWM or TWRP 2.6.
3 - Download the latest release that you want to install.
4 - Flash the latest release over the pre - installed ROM without wiping anything.
Is it possible to just flash 4.4.4 or do I risk bricking the device?
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.
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!
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.