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.?
Related
Hi there,
my 802 is running on TWRP after I updated to the latest stock ROM (30D Europe Open). Unfortunately due to problems mentioned in another thread I cannot install a custom ROM currently. Does anyone here have a mirror for me where I can download a TWRP backup of the stock ROM?
Thank you in advance
If you can't install a custom rom, what makes you think you can install a stock? It's pretty easy.
Very helpful... I flashed the latest KDZ on the G2, rooted it and installed TWRP 3.0.2.0, so far so good (believe it or not I flashed a dozen other android devices before). However when I try to install a Marshmallow ROM it gives me Error 7, so that means that getprop.device or so doesnt bring the correct value up. Now when I tried to switch to an older TWRP which is supposed to not have that Error 7 issue (2.7.0.0) I get an error saying I am missing the Loki files in the tmp folder. Now I do not know how to get around the Error 7 (the fix that is mentioned on here didnt work for me, brings up Error 6 instead) I would like to return to a stock backup.
How about giving me actual advice or leaving and letting other people help?
Edit: Booted in Download Mode and flashed v30D KDZ with the 2014 LG Flashtool. Works with Stock ROM for now
hi everybody
i'm new at lenovo development thread ,and as i'am bored of laggy a6000 firmware especially after updates i decided to do root and flash custom roms so i did root successfully and installed TWRP recovery and then downloaded Carbon rom and placed it on memory and flashed "CM11 MoStock v1.48 .img"Kernel ,after flashing kernel system couldn't start and stucked on Lenovo logo and i think it's normal as the kernel not compatible with the stock rom so on TWRP i did wipe for data ,cach and dalvik cach and flashed the rom but i'm not sure if it was flashed properly or not it always says at the start of installation "not found MD5 " and after 2 minutes it say successful
after rebooting system it goes on bootloop and now i don't no what i have to do to please help me
http://forum.xda-developers.com/lenovo-a6000/help/unbrick-lenovo-a6000-plus-lenovo-a6000-t3137247
You can read my guide on how to fix nearly all software sided problems HERE.
I'd appreciate a Thanks! thrown my way!
try this tutorial
my phone lenovo a6000 once was bricked, and solved with follow those tutorial.
thnx every body i tried to flash another rom "MIUI 8" via recovery and finally it worked well
miz0ooo0 said:
thnx every body i tried to flash another rom "MIUI 8" via recovery and finally it worked well
Click to expand...
Click to collapse
Try using CM 12.1 by ED300.
if we are in any custom rom then how to flash different kernel.
if we directly flash through recovery then phone stuck on lenovo logo.
While i am trying install custom roms on my lenovo a6000plus through latest/old TWRP versions i am facing the above error ie Error in executing updater binary in zip in spite of many attempts. But before that i have installed many customs roms on my lenovo a6000plus without any error, now i have flashed stock rom (Lollipop) using QPST/QFIL software. and now i am succeeding in backup and restore the current rom through TWRP recovery but failing to install the customs roms as i am getting the above error. Pls need help to fix it.
Thanking you
K.M.M said:
While i am trying install custom roms on my lenovo a6000plus through latest/old TWRP versions i am facing the above error ie Error in executing updater binary in zip in spite of many attempts. But before that i have installed many customs roms on my lenovo a6000plus without any error, now i have flashed stock rom (Lollipop) using QPST/QFIL software. and now i am succeeding in backup and restore the current rom through TWRP recovery but failing to install the customs roms as i am getting the above error. Pls need help to fix it.
Thanking you
Click to expand...
Click to collapse
Also happened with me then i googled it and it is mainly due to broken rom download or error in ur rom u then u should download the rlm again and try to flash then hope it will work. It worked for me :good:
---------- Post added at 06:27 AM ---------- Previous post was at 06:27 AM ----------
Using latest version of flashable twrp available here
I am able to install 32 bit roms but when tried to install 64 bit roms the error occurred. unable to install 64 bit roms on Lenovo a6000plus instead of using latest recovery. Any way to fix it?
K.M.M said:
I am able to install 32 bit roms but when tried to install 64 bit roms the error occurred. unable to install 64 bit roms on Lenovo a6000plus instead of using latest recovery. Any way to fix it?
Click to expand...
Click to collapse
https://www.androidfilehost.com/?fid=889764386195915509
Use this.
Hi Guys,
I have a N910F Device , so I have yesterday worked on Rooting the Rom and Install Custom Rom.
I have using a Tutorial from Saarliner Rom Devloper and his Rom N4Rom but after I have flashing TWRP over Odin and get in Odin and erase all and install Rom there were Bootloop.
After I have flashed Remix Rom Project or other Rom ever and ever the Same ever Bootloop
My Question what I have make wrong?
- Download Mode
-TWRP Recover flashing
- Erease all up to Point Micro SD
- Flashing New Rom
Isn´t Correct that?
I knowing from S2/S3/S4/S5
First Root stock Rom then TWRP then Custom Rom or was it right?
1. 910F is known to have an eMMC problem - read about it
2. when you flash an 910F it is advised to do it in a cool environment - no joke, get a fan to blow on it or something - because heat produce the damage from point 1
3. it looks ok what you did, but did you updated to the ROM required BL and Modem ? did you respected all the instructions? why don't you try to talk with the saarliner rom creator/developer?
To 1. isn´t present , because Stock Rom are working fine and without any Reboots or Errors.
To 2. yes it was very hot.
To 3. Yes i did and yes i have read it 2 times, so my Question is when I would like to install a Custom Rom, i must have a rooted Stock then Recovery TWRP flash then Custom Rom isn´t it?
Because the Way from Saarliner look like not complete, i can´t imagen that it work so in the Tutorials. The Developer self has a Broken N4.
bluedesire said:
Question is when I would like to install a Custom Rom, i must have a rooted Stock then Recovery TWRP flash then Custom Rom isn´t it?
Click to expand...
Click to collapse
Not obligatory to have a rooted stock. After flashing TWRP, you can root it also - my advice is to use Magisk for root.
Also as advice - if saarliner rom is not working, try some other rom. The snapdragon forum has some roms, both touchwiz based and AOSP.
I will try it out.
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.