Hello, I have a Redmi 2 with CM13 and TWRP 3.0.2-0. I'm trying to flash MIUI stock and MIUI8 roms and it's giving me an "Error 7" message. The funny thing is, these are all ROMs that I installed before. The device identification is "HM2014819", and the error informs me that those images are for "HM2014811" and "wt88047", but I've double-checked and those are all for my cellphone model.
khaotik said:
Hello, I have a Redmi 2 with CM13 and TWRP 3.0.2-0. I'm trying to flash MIUI stock and MIUI8 roms and it's giving me an "Error 7" message. The funny thing is, these are all ROMs that I installed before. The device identification is "HM2014819", and the error informs me that those images are for "HM2014811" and "wt88047", but I've double-checked and those are all for my cellphone model.
Click to expand...
Click to collapse
I have had this error before. The thing is Lollipop + TWRP 3.0.2 is a bad combination together. I was able to resolve the problem by flashing Kitkat based MiUI 7 in Fastboot mode and then installed TWRP 2.8.6. Now everything works like a charm!
Let me know if you need any help.
Related
Whenever I am flashing Roms (Cm 14, AOSP, R.Remix) or any other rom, TWRP is showing STATUS 7 error for each and every rom. I tried modifying script file too but then TWRP fails to detect binary-script file and installation gets abort. What to do?
It means you have the wrong version of firmware package installed. For CM14 and all it's derivatives you must have OOS 3.0.2 installed before to get the compatible TZ.
Should I install This?
pitrus- said:
It means you have the wrong version of firmware package installed. For CM14 and all it's derivatives you must have OOS 3.0.2 installed before to get the compatible TZ.
Click to expand...
Click to collapse
Should I Install this one?
I am using OnePlus 2 (INDIA)
https://s3.amazonaws.com/oxygenos.o...4_OTA_019_all_1606041303_bd42fc5cc5cc4ab2.zip
Did you made a proper "Wipe" of the device before an installation of each rom?
piyushmodi01 said:
Whenever I am flashing Roms (Cm 14, AOSP, R.Remix) or any other rom, TWRP is showing STATUS 7 error for each and every rom. I tried modifying script file too but then TWRP fails to detect binary-script file and installation gets abort. What to do?
Click to expand...
Click to collapse
Use HybridRecovery v3.4
Same issue with Hybrid Recovery V. 3.4
Updater Process Ended with ERROR 7.
Weird.... I would use fastboot to return to stock
Sent from my ONE A2005 using Tapatalk
I can't
I can't install that ROM, have the same error with TRWP.. my OP is A2005
Hi, I have this problem that it's driving me crazy, everytime I flash a ROM TWRP gives me this error:
Code:
Updater process ended with ERROR: 7
Error installing zip file: etc
My phone is a SM-J500FN with TWRP Recovery 3.1.0-0 by Zonik, so far I tried LineageOs (both 13.1 and 14.0) and Resurrection Remix, I get always the same error.
edit: also tried with AospExtended, no luck whatsoever.
Odin Eidolon said:
Hi, I have this problem that it's driving me crazy, everytime I flash a ROM TWRP gives me this error:
Code:
Updater process ended with ERROR: 7
Error installing zip file: etc
My phone is a SM-J500FN with TWRP Recovery 3.1.0-0 by Zonik, so far I tried LineageOs (both 13.1 and 14.0) and Resurrection Remix, I get always the same error.
edit: also tried with AospExtended, no luck whatsoever.
Click to expand...
Click to collapse
You need to be on Lollipop + TWRP 5.1.1 to flash the available Marshmallow/Nougat roms which are based on AOSP/Lineage (cm).
TWRP 5.1.1: https://forum.xda-developers.com/galaxy-j5/development/recovery-samsung-galaxy-j5-t3468844.
If you still have errors when flashing, then choose in TWRP "Copy log to sdcard" (something like that) and post the recovery.log .
#Henkate said:
You need to be on Lollipop + TWRP 5.1.1 to flash the available Marshmallow/Nougat roms which are based on AOSP/Lineage (cm).
TWRP 5.1.1: https://forum.xda-developers.com/galaxy-j5/development/recovery-samsung-galaxy-j5-t3468844.
If you still have errors when flashing, then choose in TWRP "Copy log to sdcard" (something like that) and post the recovery.log .
Click to expand...
Click to collapse
So first I need to downgrade my stock ROM then I can flash Lineage/whatsoever ROM?
Odin Eidolon said:
So first I need to downgrade my stock ROM then I can flash Lineage/whatsoever ROM?
Click to expand...
Click to collapse
Yes. Just like i told you in my previous post, you have to be on Lollipop + TWRP 5.1.1 to flash the available Marshmallow/Nougat roms based on AOSP/Lineage (cm).
#Henkate said:
Yes. Just like i told you in my previous post, you have to be on Lollipop + TWRP 5.1.1 to flash the available Marshmallow/Nougat roms based on AOSP/Lineage (cm).
Click to expand...
Click to collapse
Bad news, it doesn't work.
Downgraded to 5.1.1, installed the TWRP linked by you, but still error 7 when I try to flash a ROM.
edit: ok, this time I tried to flash LineageOS 13.1 and it worked. Now I have to figure out how to flash Lineage 14
Odin Eidolon said:
Bad news, it doesn't work.
Downgraded to 5.1.1, installed the TWRP linked by you, but still error 7 when I try to flash a ROM.
edit: ok, this time I tried to flash LineageOS 13.1 and it worked. Now I have to figure out how to flash Lineage 14
Click to expand...
Click to collapse
I've told you:
If you still have errors when flashing, then choose in TWRP "Copy log to sdcard" (something like that) and post the recovery.log.
Click to expand...
Click to collapse
In recovery.log you can see what's the problem.
#Henkate said:
I've told you:
In recovery.log you can see what's the problem.
Click to expand...
Click to collapse
Yeah, you're right, sorry.
But good news, flashed LOS 14 on the old 13.1, everything works fine.
Thanks for your help!
[SOLVED; MOD PLS DELETE]
Hello guys,
Well, short story: had an oneplus one, today i woke up with the usb port melted and a very dizzy burnt smoke. The replacement phone i got is a Redmi 2. Since i'm a "pure" Android fan, can not stand with the MIUI.
I used the "Newbie" guide here to unlock bootloader and install twrp(i'm pretty used to it and know the basics).
After that, i installed AOKP 8, it boots correctly and it work, but a message keeps poping up every boot:
"A vendor image mismatch has been detected. Typically this means your vendor image is out of date. Please ensure your vendor image matches LMY47V".
Any help with this? Any fix? Anything that i did not notice?
THANKS!
I think (just think, not sure) it's about the firmware. If you got a Redmi 2, it's probably that it runned KitKat before you flash a custom ROM.
As you didn't mention flashing Lollipop firmware, my suggestion is: If you want to use a ROM that is Lollipop or higher, you need to flash Lollipop firmware before flashing ROM. You can find it in the third post in Lineage thread for Redmi 2.
I say I'm not sure, because I've flashed Lollipop firmware a while ago, but last week when I flashed AOKP, the same message came every boot.
Maybe you can try wiping everything, flash Lollipop firmware and then flash ROM and Gapps.
If that works for you (or not), then you can confirm here and help someone else having that same issue.
Good luck!
Destrocamil said:
"A vendor image mismatch has been detected. Typically this means your vendor image is out of date. Please ensure your vendor image matches LMY47V".
THANKS!
Click to expand...
Click to collapse
that's just mismatch error nothing serious
first flash this firmware via twrp https://androidfilehost.com/?fid=673368273298919092 and then flash any ROM
Hello to both,
First sorry for the delay, i was travelling and internet connection , you know, meeehh!
I did notice that after a few minutes searching and flashed the firmware and it is running butter smoth!!
Thanks to everyone, guys!
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 tried to install a custom rom on a a6000. I installed the lolipop stock rom on top of the KitKat stock rom, and managed to boot to it without a problem. I then installed TWRP installed is: 3.3.1-0, and tried to install a custom rom (more specifically I tried this unofficial Lineage). For some reason, the installation fails with:
e3004: This package is for device: Kraft-T, a6000, K30-T,A6000, Kraft-W, Kraft-C, k30t, msm8916,Kraft-A6000,wt86518; this device is .
Updated process ended with ERROR 7
Click to expand...
Click to collapse
when booting into the stock lolipop rom installed I can see that the device is the A6000. I find it strange how the recovery doesn't write which device it is on this error message.
What am I missing here? Usually with other phones, as long as you manage to install a custom recovery then it's a breeze. I cannot figure out how the custom roms don't get installed. Any help appreciated
Managed to flash it in the end. The flash files contain assertions checking if the zip is okay to be flashed on the device (whether the model is the one intended for example).
I found it strange that the error message did not show the model of my device as I was 100% sure it is a A6000 and that is a ROM intended for it.
I ended up overriding the assertion in the file, which seemed to be straightforward to do and the image was flashed without any issues.
DO NOT TRY THIS AT HOME unless you are 10000% sure the image is intended for the device. ?
runningdap said:
I tried to install a custom rom on a a6000. I installed the lolipop stock rom on top of the KitKat stock rom, and managed to boot to it without a problem. I then installed TWRP installed is: 3.3.1-0, and tried to install a custom rom (more specifically I tried this unofficial Lineage). For some reason, the installation fails with:
when booting into the stock lolipop rom installed I can see that the device is the A6000. I find it strange how the recovery doesn't write which device it is on this error message.
What am I missing here? Usually with other phones, as long as you manage to install a custom recovery then it's a breeze. I cannot figure out how the custom roms don't get installed. Any help appreciated
Click to expand...
Click to collapse
Hi... Actually you can flash custom ROM on Lenovo a6000.
Im also using Lenovo a6000 and I'm running custom ROM.... feel free to Reply if u need any help..I'm glad to see that you will.?