Drm error in custom roms - Lenovo K6 / K6 Power / K6 Note Questions & Answers

Pls help after installing rom many apps are showing drm error and i also reverted back to stock rom this error remains. Pls tell me what's this and how to fix it.

Related

[URGENT]Yureka turned off suddenly and went on bootloop while normal usage

Hello everyone,
Im using my yureka since more than a year...I hav rooted, changed roms, kernels, softbricked, hardbricked and debricked and got rid of such sort of problems by following the posts in xda.
A month ago, i flashed stock rom cm11, rooted and flashed twrp recovery.. It worked good with no problems, but today while iam chatting, my phone freezed all of a sudden and switched off with no cause and thats it...ENDLESS BOOTLOOP!! :crying:
I tried flashing stock rom and other roms too...but same condition...bootloop continues...!! anyone expert or who know how to overcome this problem please help me in reviving my phone back to working...!! :crying: :crying:
anybody please share your knowledge regarding this issue...please suggest me any solution if you can...do what really these forums are meant for...!!
ravi44teja said:
anybody please share your knowledge regarding this issue...please suggest me any solution if you can...do what really these forums are meant for...!!
Click to expand...
Click to collapse
just wipe data,cache,system,dalvik and flash any rom...
or try flashing stock recovery via fastboot and install stock rom
if u are on cm11 use stock recovery for cm11 and flash cm12 rom via cm11 recovery
let me knw if this wrkd
Abhi_569 said:
just wipe data,cache,system,dalvik and flash any rom...
or try flashing stock recovery via fastboot and install stock rom
if u are on cm11 use stock recovery for cm11 and flash cm12 rom via cm11 recovery
let me knw if this wrkd
Click to expand...
Click to collapse
thanks for ur reply buddy...i tried ur suggestion...but didnt work..
actually, when no procedures worked, i myslf hardbricked phone by flashing cm12.1 using kitkat flashtools, its screen gone blank and bricked and then i used the sd card method of debricking mentioned here http://forum.xda-developers.com/yureka/help/guide-unbrick-hard-bricked-yureka-t3303112
it then came upto cyanogen logo and hanging there, i tried flashing cm12.0 and same stuck at cyanogen logo..then i flashed cm11 stock rom, it booted up and switched on...
but now,
(1) wifi not switching on,
(2)Internal memory corrupted and showing error while opening file explorer as "there is no information available for the file system" , "the file or folder was not found" and internal memory not showing in pc..
(3) while opening camera it shows "revert to default file location", "insert SD card before using the camera" and unable to capture photos
(4) while trying to take screenshot, in notification panel it shows "couldnt capture screenshot, couldnt save screenshot, storage may be in use"
(5)sim cards not detecting at all
in cm 12.0 and 12.1, its nomore beyond cyanogen logo...:crying:
Fixied ?
Hell7 said:
Fixied ?
Click to expand...
Click to collapse
not yet bro

Error in executing updater binary in zip on lenovo a6000plus

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.

Stock Rom giving error in application pop-up

Stock Rom giving error in application pop-up
Plz help me
Or
Suggest me a good ROM which can be used as a daily driver coz I don't like frequently changing ROMs
My device is redmi note 4g Dior
Plz help
Do I have to unlock bootloader before flashing twrp via updater app of miui
Someone plz help me
Suggest a daily driver type ROM
Should I unlock the bootloader to install twrp zip via updater app
I'm new to this device

Can't Install Custom Roms

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.

[FIXED] Can't install any custom rom, but stock Lolipop is ok

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.?

Categories

Resources