Im using twrp 3.0.3-0. i get error 7 When i flash lineageos but other roms dont. How can i fix it?
S7 edge with exynos
did you find the fix?
When installing certain custom ROMs on rooted Android smartphones or tablets, you will encounter “Status 7″ error issues once in awhile with ClockworkMod (CWM) Recovery.
Status 7 error is caused while the ROM’s updater script file checks to see if the phone model of your phone is compatible with the ROM you are installing, called “asserts”.
Click to expand...
Click to collapse
More info here: https://forum.xda-developers.com/showthread.php?t=2522762
Ty. I fixed it by wiping everything the second time, tho.
I have seen some people suggesting to update the firmware(bootloader?)(not quite sure) as an alternative to removing the asserts. What is your opinion on that?
Related
I just got a I9505. I was able to successfuly root it using CF-Auto, and also install TWRP. However, when booting into the recovery to install the latest nightly build, I get this error:
Finding update package...
Opening update package...
Installing update...
set_perm: some changes failed
(status 7)
Installation aborted.
I'm not able to mount the system after doing so, which forces me to flash the stock ROM via Odin. Anybody else who encountered this problem?
re: flashing issues
jorel000 said:
I just got a I9505. I was able to successfuly root it using CF-Auto, and also install TWRP. However, when booting into the recovery to install the latest nightly build, I get this error:
Finding update package...
Opening update package...
Installing update...
set_perm: some changes failed
(status 7)
Installation aborted.
I'm not able to mount the system after doing so, which forces me to flash the stock ROM via Odin. Anybody else who encountered this problem?
Click to expand...
Click to collapse
This should fix the problem, here is CWM Recovery for the i9505 phone,
You will need to Odin flash this recovery: http://downloadandroidrom.com/file/GalaxyS4/GT-i9505/recovery/CWM/i9505-cwm-recovery-6.0.3.2-4.tar
I would suggest that instead of flashing those nighties flash the so called "stable" ones.
Sometimes with CM10 CWM recovery works a lot better than twrp if flashing with CM10.
Be sure that the rom zip file is in your internal sdcard before flashing.
I still cannot see why anyone would want to flash CM10/AOSP/AOKP roms......
By doing that most all the bells and whistles which normally come with the
Galaxy S4 phones will no longer be found after flashing any of those roms..
Sadly, instead of bells and whistles there will be many issues with those roms like the audio
during video playback will be so quiet that you will need a headset to hear it, that's if you
have good hearing.
Other issues will arise like bluetooth not working properly and the camera in general will be
degraded not only in the quality of the photos and videos but in the actual user interface it
will look like some home made app which does not even resemble the stock camera + you
will find it only has about one half as many options for picture taking and video recording.
Good luck!
Misterjunky said:
This should fix the problem, here is CWM Recovery for the i9505 phone,
You will need to Odin flash this recovery: http://downloadandroidrom.com/file/GalaxyS4/GT-i9505/recovery/CWM/i9505-cwm-recovery-6.0.3.2-4.tar
Sometimes with CM10 CWM recovery works a lot better than twrp if flashing with CM10.
Be sure that the rom zip file is in your internal sdcard before flashing.
I still cannot see why anyone would want to flash CM10/AOSP/AOKP roms......
By doing that most all the bells and whistles which normally come with the
Galaxy S4 phones will no longer be found after flashing any of those roms..
Click to expand...
Click to collapse
I hope flashing using CWM would resolve the issue. The so called bells and whistles are the ones that annoy me most about Samsung. But then again, it's just my personal preference.
I was able to successfully install CM10.1 by flashing it repeatedly until it installed. Dunno if this is a bug in the ROM or recovery, but I do hope that this gets settled soon.
jorel000 said:
I was able to successfully install CM10.1 by flashing it repeatedly until it installed. Dunno if this is a bug in the ROM or recovery, but I do hope that this gets settled soon.
Click to expand...
Click to collapse
Had the same thing too, did you use the official release?
I had it with official, but it was fixed in hazanwars unofficial release just so you know
I rooted my phone and installed TWRP recovery. When i try to flash a cm 10.1 (LOKI) i get the error: Error executing binary in zip ' /external_sd/cm-10.1 -20130524-N
What am i doing wrong?
This error sometimes occurs while flashing a custom ROM on new devices. i dont know why but i know i've seen it happen to phones, tablets, etc of all brands. it is commonly fixed by downgrading to the previous/an older version of twrp. in this case, i dont know if an earlier version for the s4 exists as i use cwm only. i would imagine it would flash in cwm, but i would also imagine you would prefer to stay on twrp. just passing on what i know. cheers
Help? Every rom seems to give me boot loop after install and a couple of roms get to 50 percent installing then TWRP reboots (mostly pixel rom and rr does this)
I also tried nougat and marshmellow stock roms and they both give drk check error, I flash super su like I used to do to fix drk check error and it just boot loops now
All the roms I used to be able to install fine now just boot loop
Pixel rom
Fast and famous rom
Infinity rom
Lineage os
Resurrection remix
All of these roms above I have had on my phone at some point and all worked fine now I just get boot loop after installing them.
14 views and no one can help me?
Still have no phone as I still cannot boot.
are you using a correct kernel or twrp for your device
blackbravo said:
are you using a correct kernel or twrp for your device
Click to expand...
Click to collapse
I'm not sure my device is G928F Can you link me to the correct kernel? And I think the TWRP is 2.7.8 or something like that
download twrp here: https://twrp.me/samsung/samsunggalaxys6edgeplus.html
flash over odin
and choose one rom with kernel included, because you must have the correct kernel for the rom you install
blackbravo said:
download twrp here: https://twrp.me/samsung/samsunggalaxys6edgeplus.html
flash over odin
and choose one rom with kernel included, because you must have the correct kernel for the rom you install
Click to expand...
Click to collapse
Okay so tried a couple roms and they all crash like sometimes at 10 percent sometimes around 50 but they always crash and TWRP restarts. Something to do with the aroma installer roms, tried multiple different TWRP versions and nothing likes the aroma installer roms, any suggestions? Also tried multiple nougat and marshmellow roms and I get drk check failed everytime.
I used to be able to flash SuperSU zip and it would fix drk check failed but it no longer does
Can someone please give me any suggestions at all as I would like to use my phone again
jacksskinz said:
Okay so tried a couple roms and they all crash like sometimes at 10 percent sometimes around 50 but they always crash and TWRP restarts. Something to do with the aroma installer roms, tried multiple different TWRP versions and nothing likes the aroma installer roms, any suggestions? Also tried multiple nougat and marshmellow roms and I get drk check failed everytime.
I used to be able to flash SuperSU zip and it would fix drk check failed but it no longer does
Can someone please give me any suggestions at all as I would like to use my phone again
Click to expand...
Click to collapse
And install stock ROM via Odin? Not working ?
blackbravo said:
And install stock ROM via Odin? Not working ?
Click to expand...
Click to collapse
It works but when booting I get DRK CHECK FAILED
blackbravo said:
And install stock ROM via Odin? Not working ?
Click to expand...
Click to collapse
Okay I've narrowed it down to system
When installing any rom it seems to crash when it gets to installing system and then TWRP reboots
I've checked that system is mounted which it is
Also it seems system is at EXT4 file system
Dunno if that's good or bad but either way every rom is crashing when it gets to installing system
Any ideas?
jacksskinz said:
Okay I've narrowed it down to system
When installing any rom it seems to crash when it gets to installing system and then TWRP reboots
I've checked that system is mounted which it is
Also it seems system is at EXT4 file system
Dunno if that's good or bad but either way every rom is crashing when it gets to installing system
Any ideas?
Click to expand...
Click to collapse
Can someone help please before I buy a new motherboard? Roms crash when it starts installing system
Download stock nougat, and flash it, but make sure csc is selected, and not home_csc, because csc will put phone to real stock settings.
Flash the latest stock firmware for your *correct variant*. Sammobile's downloads are kind of slow, but I've never had issues with any of their firmwares. Install that with Odin and your phone on download mode. I would recommend to use HOME CSC, just to make sure it is completely clean. After you set it up, flash your *correct variant's* TWRP via Odin. To save yourself some time, you can boot straight into TWRP when it finishes installing by pressing home + power + volume up when the screen goes out. From here you can load ROMs from a PC via USB. Good Luck and Happy Flashing!
Hello,
Firstly, my device is the Asus Zenfone Max Pro M1 6GB Ram variant.
I was using the Pixel Experience rom as my daily ROM (I don't remember which build), it worked fabulously. But I hadn't updated it in a few months. So after enough procrastination I decided to update. I tried the regular software update method where you go to settings and check for updates, when it booted to TWRP recovery, it failed with an error. I thought it was because the update was the latest one and I was on an older build. So I tried doing a clean install by booting into recovery and wiping everything except internal storage. But the same error popped up again
I don't remember the exact error but it was an Error 7 and said something about the 'firmware version' required is 15.2016.1901.339 or newer. At first I didn't really get it and I kept trying again.
But after spending some hours it started making some sense and so I tried to install the required firmware. Even after doing so, the error kept showing up.
I thought it might be a ROM specific error. So I also tried Resurrection Remix (Pie version) but it yielded the same Error 7. This is the phone I use on a daily basis so I had to get it working somehow. So I flashed the stock ROM, the one that comes out the box. I flashed it using the flashall_AFT.cmd, I'm on the stock ROM now and it's obviously nothing like a custom ROM.
I also tried editing the updater script from the ROMs and deleting the part that was about the error (the first few lines). That didn't work either. The Error 7 was gone but another Error 6 popped up which said it failed to install.
I'd love to go back to using a custom ROM. It bugs me because I couldn't find any way to fix the error.
I'd greatly appreciate it if you can guide me step-by-step on how to install the custom ROM from where I am now i.e from the stock and fix the error.
I hope the above information suffices.
Thanks.
Azyaan124 said:
Hello,
Firstly, my device is the Asus Zenfone Max Pro M1 6GB Ram variant.
I was using the Pixel Experience rom as my daily ROM (I don't remember which build), it worked fabulously. But I hadn't updated it in a few months. So after enough procrastination I decided to update. I tried the regular software update method where you go to settings and check for updates, when it booted to TWRP recovery, it failed with an error. I thought it was because the update was the latest one and I was on an older build. So I tried doing a clean install by booting into recovery and wiping everything except internal storage. But the same error popped up again
I don't remember the exact error but it was an Error 7 and said something about the 'firmware version' required is 15.2016.1901.339 or newer. At first I didn't really get it and I kept trying again.
But after spending some hours it started making some sense and so I tried to install the required firmware. Even after doing so, the error kept showing up.
I thought it might be a ROM specific error. So I also tried Resurrection Remix (Pie version) but it yielded the same Error 7. This is the phone I use on a daily basis so I had to get it working somehow. So I flashed the stock ROM, the one that comes out the box. I flashed it using the flashall_AFT.cmd, I'm on the stock ROM now and it's obviously nothing like a custom ROM.
I also tried editing the updater script from the ROMs and deleting the part that was about the error (the first few lines). That didn't work either. The Error 7 was gone but another Error 6 popped up which said it failed to install.
I'd love to go back to using a custom ROM. It bugs me because I couldn't find any way to fix the error.
I'd greatly appreciate it if you can guide me step-by-step on how to install the custom ROM from where I am now i.e from the stock and fix the error.
I hope the above information suffices.
Thanks.
Click to expand...
Click to collapse
Most pie roms are base on the latest stock pie firmware, you probably need to flash that. Plus Ur twrp version is probably not the newest, all the links are available in the telegram group, and I'm not going to put them here out of respect for the devs. But .339 firmware is the Oreo firmware, I think the one u need to flash is the .050 firmware.
The telegram groups have them all and a little searching can give you all the links you need.
Azyaan124 said:
Hello,
Firstly, my device is the Asus Zenfone Max Pro M1 6GB Ram variant.
I was using the Pixel Experience rom as my daily ROM (I don't remember which build), it worked fabulously. But I hadn't updated it in a few months. So after enough procrastination I decided to update. I tried the regular software update method where you go to settings and check for updates, when it booted to TWRP recovery, it failed with an error. I thought it was because the update was the latest one and I was on an older build. So I tried doing a clean install by booting into recovery and wiping everything except internal storage. But the same error popped up again
I don't remember the exact error but it was an Error 7 and said something about the 'firmware version' required is 15.2016.1901.339 or newer. At first I didn't really get it and I kept trying again.
But after spending some hours it started making some sense and so I tried to install the required firmware. Even after doing so, the error kept showing up.
I thought it might be a ROM specific error. So I also tried Resurrection Remix (Pie version) but it yielded the same Error 7. This is the phone I use on a daily basis so I had to get it working somehow. So I flashed the stock ROM, the one that comes out the box. I flashed it using the flashall_AFT.cmd, I'm on the stock ROM now and it's obviously nothing like a custom ROM.
I also tried editing the updater script from the ROMs and deleting the part that was about the error (the first few lines). That didn't work either. The Error 7 was gone but another Error 6 popped up which said it failed to install.
I'd love to go back to using a custom ROM. It bugs me because I couldn't find any way to fix the error.
I'd greatly appreciate it if you can guide me step-by-step on how to install the custom ROM from where I am now i.e from the stock and fix the error.
I hope the above information suffices.
Thanks.
Click to expand...
Click to collapse
The latest Pixel Experience works great!
So you are on the Stock Firmware then.
1) Unlock the bootloader by Unofficial method (It will help when you want to relock it in future.)
2) Flash the latest TWRP Recovery.
3) Download whatever ROM you want to install and read all the requirements first! The error 7 you mentioned was the Firmware issue and could have been fixed by flashing the Firmware first and then the ROM.
GApps are not required for Pixel Experience as it comes with all the necessary Google Apps.
I’ve tried looking for solutions online, but to no avail I can’t seem to fix by myself I have recently installed LineageOS 16 , been using it for months until recently it started to slow down, and die down what i mean is the booting process takes time and after booting there is some random crashes and it reboots , I was able to solve the problem using TWRP by wiping out the cache and resetting back to factory settings, but it was taking so long to boot after and then I decided to flash it once again, started from scratch and it worked for some time until it crashed once again leaving me to unfixable bootloop, it stays on LineageOS logo, then screen dims and then just bootloops, so i decided to flash the STOCK ROM using odin which apparently worked It booted and the process was painful because every boot im doing it got slower and slower until it would be stuck at Samsung Logo and then reboots once again, so I reflashed it once again and when it booted, I was bombarded by system apps not reponsing properly, icon like ‘System UI has stopped’ and then most of the In-built app would do the same and it crashed this time, this time when it booted it is stuck to samsung logo, so i tried wiping the cache and formatting data on stock recovery and it is still stuck on boot-loop, if lucky it goes to samsung logo and just literally in that state forever, i left it for hours and it is still the same. and then when i tried booting to stock rom there was a message below that says (dm-verity verification failed), I googled it and it is a cause for tampering system files and I just couldn’t get to work it out and find a proper solution. I hope you all can help me out. Every-time i try to flash the stock rom the message is , (Installing system updates, error, goes to recovery then it has the problem below) If anyone has encountered the same problem, or has a solution I would appreciate it. Thank you.
Samsung Galaxy Note 4 (SM-N910C) treltex
A dm-verity (device mapper verification) is most likely related to a DRK (device root key) fail as well. Contrary to popular belief, flashing the Samsung official factory firmware does not fix all. As I'm sure you have already come to realize nite even flashing a previous nandroid backup resolves the issues.
There are many YouTube vids of fixing dm-verity but the comments are mixed. Some recommend using 4files with and additional file in the pit (partition information table) but that is also very risky and you could wind worse off than you already are.
Your best bet is to flash a "no opt encryt .zip" and follow the introductions. If this is successful you will need to flash the .zip with every no rom or you'll get dm-verity error. The .zip is not a permanent fix but more like a patch, so to speak. The link below is for general info and I can't vouch for the downloads provided from the site. Its best to download your .zips from XDA.
https://www.androidinfotech.com/no-verity-opt-encrypt-versions/
https://www.google.com/search?ie=UT...e=android-browser&q=xda+no-verity-opt-encrypt
There is also a force encrip .zip you could look into. Good luck
Thank you. I hope this fixes my problem.. But where do I flash it through odin or TWRP??
I tried flashing the zip i got error 1
Mr. JAVI said:
A dm-verity (device mapper verification) is most likely related to a DRK (device root key) fail as well. Contrary to popular belief, flashing the Samsung official factory firmware does not fix all. As I'm sure you have already come to realize nite even flashing a previous nandroid backup resolves the issues.
There are many YouTube vids of fixing dm-verity but the comments are mixed. Some recommend using 4files with and additional file in the pit (partition information table) but that is also very risky and you could wind worse off than you already are.
Your best bet is to flash a "no opt encryt .zip" and follow the introductions. If this is successful you will need to flash the .zip with every no rom or you'll get dm-verity error. The .zip is not a permanent fix but more like a patch, so to speak. The link below is for general info and I can't vouch for the downloads provided from the site. Its best to download your .zips from XDA.
https://www.androidinfotech.com/no-verity-opt-encrypt-versions/
https://www.google.com/search?ie=UT...e=android-browser&q=xda+no-verity-opt-encrypt
There is also a force encrip .zip you could look into. Good luck
Click to expand...
Click to collapse
I tried flashing the zip file in TWRP after installing the stock rom, and I got a Error 1 code
kenesuuu said:
I tried flashing the zip file in TWRP after installing the stock rom, and I got a Error 1 code
Click to expand...
Click to collapse
Try this, read threw the entire tread, follow the instructions. I'd alsoblike to add dm-verity and drk are some of the most difficult to solve, at least in my experience. Furthermore, I would highly recommend making a nandroid backup of all your partitions, especially EFS, boot. I'll see if I can find the no opt encrypt .zip in the meantime. I believe it was 6.0 or 6.1 .
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
Error 1
https://forum.xda-developers.com/galaxy-s7/help/error-installing-verity-opt-encrypt-zip-t3436385
scroll down to
JUST WANT TO DISABLE VERITY/ENCRYPTION
https://www.google.com/amp/s/forum....azyflasher-tool-flashing-custom-t3549210/amp/
read threw the rest of the thread.
I don't believe you'll have any success on pure stock firmware. Chances are you'll need to flash a custom kernel for your specific device and/or root package. Unfortunately, theres no one size fits all when it comes to dm-verity or drk.