Database Users

[ROM][5.0.2][TEST][LOLLIPOP][n7000]RESURRECTION REMIX LP 5.2.5

I Have opened this thread for test purposes only
THIS is a thread of Ressurection Remix 5.2.5 android 5.0.2
LINK to rom here
LINK TO gapps Here
Link to raw kernel here
FIRST YOU NEED the compaitble recovery and kernel ,the same one that cm12 uses
Refer THIS Thread
installing:
copy Rom+Google Apps to sdcard
boot into recovery
(factory reset) (if you get fc's or bootloops after updating from an older rom)
flash the rom and gapps zip file
reboot
now remember always take a nadroid backup of previous rom
some users report this error
Code:
error status 7
assert failed: package_extract_file("boot.img", "/tmp/boot.img")
somebody knows how to fix this error please feel free to share here and test the ROM

status 7 error as I have always seen is related to incompatible recovery.
People got it while trying to flash kk ROMs coming from JB using a non SE Linux recovery.
Maybe try raw kernel?
remember not to boot system after flashing that kernel but reboot to recovery.
REVENGE SOLVES EVERYTHING

Help needed
Hi developers, testers, and community members
@bauner
@TouchLeclouds
@tysonraylee
@01000010
@Dekuki
sorry for mentioning you guys here,
hopefully we can create varieties for Lollipop, :angel:
and probably with this development, we can also helping each other, sharing knowledge and such :highfive:
here's my workaround for attempting flashing this rom,
#method 1
1. reboot into recovery, flash forest v5 cm11 philz -based kernel/recovery
2. do wipes (everything),
3. flash the rom,
4. failed with status 7 error,
#method 2
1. reboot into recovery, flash bauner's cwm-based kernel/recovery v1.2.1
2. do wipes (everything),
3. flash the rom,
4. failed with status 7 error,
#method 3
1. reboot into recovery, flash raw kernel v7 for cm11 twrp-based kernel/recovery
2. do wipe (everything),
3. flashed the rom,
4. failed with status 7 error,
#method 4
1. redownload zips,
2. apply recovery method #1, #2, #3,
3. flashed the rom,
4. still failed with status 7
#method 5
1. redownload zips, replaced bauner's NightOwl boot.img into Ress.Remix 5.0
2. apply reovery method #1, and #2,
3. flashed the rom,
4. failed with status 7, as well
that's my report, tester : me and @nitangle17

please post a screenshot of the error
----------------
update : according to my findings this "status 7 assert" error is either because
1) you trying to flash a different model/variant ROM on device i.e S2 ROM on S3
2) incompatible recovery i.e non se Linux compatible.
there is a workaround for the issue 1 but we need to make sure that this ROM file IS for N7000 or it WILL BRICK the device.

tysonraylee said:
please post a screenshot of the error
----------------
update : according to my findings this "status 7 assert" error is either because
1) you trying to flash a different model/variant ROM on device i.e S2 ROM on S3
2) incompatible recovery i.e non se Linux compatible.
there is a workaround for the issue 1 but we need to make sure that this ROM file IS for N7000 or it WILL BRICK the device.
Click to expand...
Click to collapse
I have compiled this from bauners sources so its 100% for n7000 ..come on :-/
And even the updater script says so

varund7726 said:
I have compiled this from bauners sources so its 100% for n7000 ..come on :-/
And even the updater script says so
Click to expand...
Click to collapse
well in that case take a look here http://forum.xda-developers.com/showthread.php?t=2522762
and I think you should have the idea what's going on and how to solve it
REVENGE SOLVES EVERYTHING

tysonraylee said:
well in that case take a look here http://forum.xda-developers.com/showthread.php?t=2522762
and I think you should have the idea what's going on and how to solve it
REVENGE SOLVES EVERYTHING
Click to expand...
Click to collapse
Thw cauae of the status 7 error here is becauae of the SE linux disabled recovery
I dont think removing lines like assert is recommented but i will ask my testers to give it a try.
But the cm12 dev uses the exact same updater script as mine
And some users are able to flash it and some arent (getting this same error)

tysonraylee said:
please post a screenshot of the error
----------------
update : according to my findings this "status 7 assert" error is either because
1) you trying to flash a different model/variant ROM on device i.e S2 ROM on S3
2) incompatible recovery i.e non se Linux compatible.
there is a workaround for the issue 1 but we need to make sure that this ROM file IS for N7000 or it WILL BRICK the device.
Click to expand...
Click to collapse
unfortunately I can't this the only phone I had, my S plus are not with me currently,
anyway, I'm not sure any of this issue causing the error are appear to be mine only, but I'm sure it is
status 7 error failed to write..bla..bla "/tmp/boot.img.."
I already forgot how's the error,
I'll try again in some time, currently at work and kinda busy, :crying:
so sorry guys,
hopefully others help too, :highfive:
please :good:

varund7726 said:
Thw cauae of the status 7 error here is becauae of the SE linux disabled recovery
I dont think removing lines like assert is recommented but i will ask my testers to give it a try.
But the cm12 dev uses the exact same updater script as mine
And some users are able to flash it and some arent (getting this same error)
Click to expand...
Click to collapse
you are right I too think we should not try it. Maybe bauner could look into it. I will see if I am able to flash it later
REVENGE SOLVES EVERYTHING

tysonraylee said:
you are right I too think we should not try it. Maybe bauner could look into it. I will see if I am able to flash it later
REVENGE SOLVES EVERYTHING
Click to expand...
Click to collapse
goodluck buddy! :highfive: :victory: :highfive:
I heard 4.2.2 is going to landed on our device by old sammy, seems nice for forest kernel development! :victory:

kazuna69 said:
Hi developers, testers, and community members
@bauner
@TouchLeclouds
@tysonraylee
@01000010
@Dekuki
sorry for mentioning you guys here,
hopefully we can create varieties for Lollipop, :angel:
and probably with this development, we can also helping each other, sharing knowledge and such :highfive:
here's my workaround for attempting flashing this rom,
#method 1
1. reboot into recovery, flash forest v5 cm11 philz -based kernel/recovery
2. do wipes (everything),
3. flash the rom,
4. failed with status 7 error,
#method 2
1. reboot into recovery, flash bauner's cwm-based kernel/recovery v1.2.1
2. do wipes (everything),
3. flash the rom,
4. failed with status 7 error,
#method 3
1. reboot into recovery, flash raw kernel v7 for cm11 twrp-based kernel/recovery
2. do wipe (everything),
3. flashed the rom,
4. failed with status 7 error,
#method 4
1. redownload zips,
2. apply recovery method #1, #2, #3,
3. flashed the rom,
4. still failed with status 7
#method 5
1. redownload zips, replaced bauner's NightOwl boot.img into Ress.Remix 5.0
2. apply reovery method #1, and #2,
3. flashed the rom,
4. failed with status 7, as well
that's my report, tester : me and @nitangle17
Click to expand...
Click to collapse
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,
Back up your things
Flash DU 8.1 (Because it have Latest TWRP recovery)
Reboot into recovery
Clear cache, Factory rest
Flash the Rom + Gapps

TouchLeclouds said:
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,
Back up your things
Flash DU 8.1 (Because it have Latest TWRP recovery)
Reboot into recovery
Clear cache, Factory rest
Flash the Rom + Gapps
Click to expand...
Click to collapse
Status 7 here is due to se linux recovery

varund7726 said:
Status 7 here is due to se linux recovery
Click to expand...
Click to collapse
I had the same issue before, my problem was solved by changing the update script

TouchLeclouds said:
I had the same issue before, my problem was solved by changing the update script
Click to expand...
Click to collapse
So can we change bauner update script and check the possibility

mjrifath said:
So can we change bauner update script and check the possibility
Click to expand...
Click to collapse
you can try that, but also keep in mind that this issue could be caused anything else. i just gave the solution that worked for me

Ok i got it to boot.thanks for the help guys.ill open a thread in the dev section and close this one

[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

ASUS ZENFONE 5 A501CG usb logo problem

Need help Urgent!!!!!!!!
I had rooted my phone successfully 1 year ago but while installing xposed privacy it asked unlock bootloader and changed to twrp recovery 2.8.7.0 but some problem occured i can not go after asus logo so i visited customer care and he installed kitkat 2.22.40.54 version with out locking that bootloader. After succesful usage of 1 year my settings option not opened it always show "unfortunately. com.android settings has stopped" so i tried to flash a new rom i wiped cache and data unfortunately system also.
so that im not able to flash new rom errors occurs are
1. E:unknown file system: 'osip'
E:unknown file system: 'osip'
E:unknown file system: 'osip'
E: Invalid block device on '/dev/block/zram0one......................................
2. E: Unable to locate page (system_readonly)
3. no MD5 file found even i downloaded the firmware from asus support (2.22.40.540 as well as 2.21.40.44)
4. assert failed: getprop("ro.build.asus.sku")=="ww" return code 8
5. E: Error executing updater binary in zip '/external_sd/.....................zip
(** note: i had not enabled usb debugging
when i try to flash rom using adb sideload it is not showing in the list even it is connecting as media transfer
through otg also not going i dont know it is not showing in the recovery)
thats the problem guys please help me out of this

ajay019 said:
Need help Urgent!!!!!!!!
I had rooted my phone successfully 1 year ago but while installing xposed privacy it asked unlock bootloader and changed to twrp recovery 2.8.7.0 but some problem occured i can not go after asus logo so i visited customer care and he installed kitkat 2.22.40.54 version with out locking that bootloader. After succesful usage of 1 year my settings option not opened it always show "unfortunately. com.android settings has stopped" so i tried to flash a new rom i wiped cache and data unfortunately system also.
so that im not able to flash new rom errors occurs are
1. E:unknown file system: 'osip'
E:unknown file system: 'osip'
E:unknown file system: 'osip'
E: Invalid block device on '/dev/block/zram0one......................................
2. E: Unable to locate page (system_readonly)
3. no MD5 file found even i downloaded the firmware from asus support (2.22.40.540 as well as 2.21.40.44)
4. assert failed: getprop("ro.build.asus.sku")=="ww" return code 8
5. E: Error executing updater binary in zip '/external_sd/.....................zip
(** note: i had not enabled usb debugging
when i try to flash rom using adb sideload it is not showing in the list even it is connecting as media transfer
through otg also not going i dont know it is not showing in the recovery)
thats the problem guys please help me out of this
Click to expand...
Click to collapse
Ok so as per my understanding , you have unlocked bootloader .
You also have custom recovery twrp 2.8.7 installed . Right ?
Since you wipe system , your phone is without any os right now .
So now what you do is download any stock modified rom for your device .
Download latest twrp by xanwar . Flash the twrp zip (by xanwar)from twrp 2.8.7 (already installed ).
Voila ! Now you can flash any custom rom or stock based modified roms .
I don't know this is what you asking

Boomshiva said:
Ok so as per my understanding , you have unlocked bootloader .
You also have custom recovery twrp 2.8.7 installed . Right ?
Since you wipe system , your phone is without any os right now .
So now what you do is download any stock modified rom for your device .
Download latest twrp by xanwar . Flash the twrp zip (by xanwar)from twrp 2.8.7 (already installed ).
Voila ! Now you can flash any custom rom or stock based modified roms .
I don't know this is what you asking
Click to expand...
Click to collapse
yes i unlocked bootloader and i have custom recovery twrp 2.8.7.0 installed but here the problem is i didnt enabled usb debugging mode so that i'm not able to flash and the errors are as above mentioned. modified rom you are saying means i'm using 2.22.40.54 kitkat so may i able to install lollipop or higher version.one more thing i dont know what these errors mean..

ajay019 said:
yes i unlocked bootloader and i have custom recovery twrp 2.8.7.0 installed but here the problem is i didnt enabled usb debugging mode so that i'm not able to flash and the errors are as above mentioned. modified rom you are saying means i'm using 2.22.40.54 kitkat so may i able to install lollipop or higher version.one more thing i dont know what these errors mean..
Click to expand...
Click to collapse
Ok . I understand now .
1)donwlaod latest twrp by xanwar . And flash it. So now you have latest recovery installed on your device .:fingers-crossed:
2)download gecko premium rom from Android development section here on xda . Place it on SD card .
3)reboot to recovery , wipe everything except SD card . (You will lose everything from your phone .)
4)if step 3 gives error then format data not wipe .
5)repeat step 3
6)reboot to recovery now .
Flash the rom that you downaoded (gecko premium )
7)reboot system .
8) do this first then report back .

Boomshiva said:
Ok . I understand now .
1)donwlaod latest twrp by xanwar . And flash it. So now you have latest recovery installed on your device .:fingers-crossed:
2)download gecko premium rom from Android development section here on xda . Place it on SD card .
3)reboot to recovery , wipe everything except SD card . (You will lose everything from your phone .)
4)if step 3 gives error then format data not wipe .
5)repeat step 3
6)reboot to recovery now .
Flash the rom that you downaoded (gecko premium )
7)reboot system .
8) do this first then report back .
Click to expand...
Click to collapse
one more mistake bro i didnt find xanwar twrp 3.0.2.0 so i browsed for another one which is 3.0-m-4.0 and flashed it successfully but reboot in recovery is not going then powered off the phone and started to go into recovery mode but in recovery mode touch is not working so only hanged i repeatedly switched off and on but same result. so what to do now.....? i think im having no other choices than using droidboot but adb side load is not working bz i didnt enabled usb debugging mode. in pc it is showing connected to pc until i started adb when i started it disappearing.

ajay019 said:
one more mistake bro i didnt find xanwar twrp 3.0.2.0 so i browsed for another one which is 3.0-m-4.0 and flashed it successfully but reboot in recovery is not going then powered off the phone and started to go into recovery mode but in recovery mode touch is not working so only hanged i repeatedly switched off and on but same result. so what to do now.....? i think im having no other choices than using droidboot but adb side load is not working bz i didnt enabled usb debugging mode. in pc it is showing connected to pc until i started adb when i started it disappearing.
Click to expand...
Click to collapse
I don't understand the logic behind not enabling usb debugging !
No need for all that .
If using windows then make sure the all driver shows up when you enter into fastboot mode .
Check from control panel of your PC . If not then reinstall the drivers . It must show asus composite ...........Blah Blah blah ...Android bridge interface .(well i use Linux so dont recall properly ).
Once the desired drivers are present you are good to go ahead .And flash proper twrp .And do the rest .
Bottom line :check drivers
Flash the latest twrp (24 July build) link below
https://www.androidfilehost.com/?w=files&flid=52033

Boomshiva said:
I don't understand the logic behind not enabling usb debugging !
No need for all that .
If using windows then make sure the all driver shows up when you enter into fastboot mode .
Check from control panel of your PC . If not then reinstall the drivers . It must show asus composite ...........Blah Blah blah ...Android bridge interface .(well i use Linux so dont recall properly ).
Once the desired drivers are present you are good to go ahead .And flash proper twrp .And do the rest .
Bottom line :check drivers
Flash the latest twrp (24 July build) link below
https://www.androidfilehost.com/?w=files&flid=52033
Click to expand...
Click to collapse
thank you bro successfully flashed new rom GECKO-premium-ROM-3.24.40.87-v1.0. problem solved. may i know how to install and activate xposed installer for this version and one more thing may i change the recovery any time with out disturbing os?

ajay019 said:
thank you bro successfully flashed new rom GECKO-premium-ROM-3.24.40.87-v1.0. problem solved. may i know how to install and activate xposed installer for this version and one more thing may i change the recovery any time with out disturbing os?
Click to expand...
Click to collapse
Flash xposed zip . Sdk21 v86 works flawlessly ,
Then download the apk for xposed and install it as normal apk you can change recovery anytime but be sure that you flash your devices twrp only not others .

NEW KERNEL /FIX FOR BOOTLOOP/Magisk installation in nougat z3+/z4

NOTE :I AM NOT A DEVELOPER.THIS IS JUST THE FINAL RESULT OF MY "HIT & TRIAL" FOR OVER A WEEK.PLEASE MAKE A BACKUP IN TWRP OF UR SYSTEM BEFORE DOING THIS.
INSTALLING FULLY FUNCTIONAL MAGISK WAS REALLY TROUBLESOME FOR ME(E6533)
sometimes it was showing error while flashing
SOMETIMES it was flashed without error but system failed to reboot/bootlooped​credits:
@topjohnwu for magisk
I have tested this and is working fine in my xperia z3+ dual(E6533)...but m sure it will work with all models of z3+/z4.so try it & let others know it.
PREREQUISITES:
1.ur firmware/rom must be nougat 7.1. [please dont try on MM/LP]
2.USB DEBUGGING AND INSTALLATION OF UNKNOWN SOURCE MUST B ENABLED.
2.FIRMWARE should be un-rooted[ if u have installed supersu/tried magisk earlier/failed/erronous attempt of installing magisk.........then use unsu.zip /magisk uninstaller before proceeding]
3.the boot image(new_kernel) over which magisk will be installed is stock nougat 7.1.1 so this method will work in any rom which can be booted via stock boot image.eg.it will work on m-rom and stock (m sure of it)
4.twrp must be installed
5.basic knowledge of fastboot commands for flashing kernel
lets start....
1.in twrp first of all clean any traces of supersu/failed magisk installation by flashing "unsu.zip or magisk uninstaller"
2.power off ur device and then flash the "new_kernel.img via fastboot....use these commands
a.imp to check whether the kernel will boot in ur device or not (if this step shows any error,plz dont proceed to b.
in cmd window : fastboot boot new_kernel.img
b.to flash the kernel
in cmd window :fastboot flash boot new_kernel.img
IMP:steps 1 & 2 are can also be used when u have met with an unexpected bootloop/restart problem at any time( if u don't want to flash the complete stock ftf,this boot image will help u in letting ur device come out of bootloop.
3.proceeding to our main thread....now boot into recovery & flash "magisk.zip"
4.wipe cache & dalvik.and reboot.
PROPERTIES OF THE KERNEL (new_kernel.img:---
Build 32.4.A.1.54
1. Sony RIC- disabled.
2. DM-Verity- disabled.
3. TWRP- disabled.
4. DRM Fix- enabled.
5. Superuser / root- Not present. ( flash magisk its better)
6. Busybox- Not present
7.many more tweaks to reduce heat & increase battery backup
LINK TO THE CONTENT
https://drive.google.com/drive/folders/1ic9zsMi576s1P9H6s1z4_g0ofSJJktIs?usp=sharing

I just want stock rooted rom with magiks
doctorsworld99 said:
NOTE :I AM NOT A DEVELOPER.THIS IS JUST THE FINAL RESULT OF MY "HIT & TRIAL" FOR OVER A WEEK.PLEASE MAKE A BACKUP IN TWRP OF UR SYSTEM BEFORE DOING THIS.
INSTALLING FULLY FUNCTIONAL MAGISK WAS REALLY TROUBLESOME FOR ME(E6533)
sometimes it was showing error while flashing
SOMETIMES it was flashed without error but system failed to reboot/bootlooped​credits:
@topjohnwu for magisk
I have tested this and is working fine in my xperia z3+ dual(E6533)...but m sure it will work with all models of z3+/z4.so try it & let others know it.
PREREQUISITES:
1.ur firmware/rom must be nougat 7.1. [please dont try on MM/LP]
2.USB DEBUGGING AND INSTALLATION OF UNKNOWN SOURCE MUST B ENABLED.
2.FIRMWARE should be un-rooted[ if u have installed supersu/tried magisk earlier/failed/erronous attempt of installing magisk.........then use unsu.zip /magisk uninstaller before proceeding]
3.the boot image(new_kernel) over which magisk will be installed is stock nougat 7.1.1 so this method will work in any rom which can be booted via stock boot image.eg.it will work on m-rom and stock (m sure of it)
4.twrp must be installed
5.basic knowledge of fastboot commands for flashing kernel
lets start....
1.in twrp first of all clean any traces of supersu/failed magisk installation by flashing "unsu.zip or magisk uninstaller"
2.power off ur device and then flash the "new_kernel.img via fastboot....use these commands
a.imp to check whether the kernel will boot in ur device or not (if this step shows any error,plz dont proceed to b.
in cmd window : fastboot boot new_kernel.img
b.to flash the kernel
Click to expand...
Click to collapse
I don't want to use any new kernel .can I flash the magiks.zip directly in twrp

Sumantomar1709 said:
I don't want to use any new kernel .can I flash the magiks.zip directly in twrp
Click to expand...
Click to collapse
u can try flashing magisk over stock.but whenever i did that my device used to go into bootloop.thats why i've to experiment with different twrps,kernels to detect the culprit.
finally i got this awesome kernel which helped me to come out of bootloops everytime.so i will suggest to use this [near to stock ] kernel .
but u can try flashing magisk over stock.....if anything goes wrong ,,,just flash the new_kernel,,and ua fine to go with magisk.

Thnx. I will try & let u know.

thank u sirThis kernel help me from bootloop .how did u make this kernel

Champsingh909 said:
thank u sirThis kernel help me from bootloop .how did u make this kernel
Click to expand...
Click to collapse
i didn't make it buddy....i tried kernels from stock /m-rom /kryptonian /LOS & one i found in generall section .its one of them .....i don't know exactly which one is it.but with this one i was able to boot evertime

This kernel really working in bootloop.thnx

doctorsworld99 said:
i didn't make it buddy....i tried kernels from stock /m-rom /kryptonian /LOS & one i found in generall section .its one of them .....i don't know exactly which one is it.but with this one i was able to boot evertime
Click to expand...
Click to collapse
it is really a good kernel but wondeering why it was not posted anywhere before.u should post this in kernel section so many users will be benefitted.btw thanks alot

Champsingh909 said:
it is really a good kernel but wondeering why it was not posted anywhere before.u should post this in kernel section so many users will be benefitted.btw thanks alot
Click to expand...
Click to collapse
creating a separate thread isn't a good idea ,i'll update the details of the kernel in this thread itself,plz give me some time.

Kernel properties added.

Wait... Installing Magisk caused a bootloop for you? Never happened to me tho.

LoaderFabi said:
Wait... Installing Magisk caused a bootloop for you? Never happened to me tho.
Click to expand...
Click to collapse
i got frequent bootloops on installing it over stock kernel and also over m-rom .i think the kernel was the culprit.

Recently I unlocked the bootloader of my Z4 single sim (E6553), but I accidentally lost the TA partition backup. Now I have LOS 14.1 but it's not good at all, I want to return to the stock firmware.
I read here that this kernel have the "DRM Fix- enabled." , what means? If I flash this kernel I can use again every features like BionZ, Bravia Engine, etc ?

chrnodroid said:
Recently I unlocked the bootloader of my Z4 single sim (E6553), but I accidentally lost the TA partition backup. Now I have LOS 14.1 but it's not good at all, I want to return to the stock firmware.
I read here that this kernel have the "DRM Fix- enabled." , what means? If I flash this kernel I can use again every features like BionZ, Bravia Engine, etc ?
Click to expand...
Click to collapse
Hopefully yes,flash it as instructed.best of luck:good:

Anyone tested if the Kernel is "DRM FiX ready"? Im planning to root my Z3+ (E6533) without backing up my TA, but if this Kernel is equipped with DRM Fix I would go with this one.

MrHands0m3 said:
Anyone tested if the Kernel is "DRM FiX ready"? Im planning to root my Z3+ (E6533) without backing up my TA, but if this Kernel is equipped with DRM Fix I would go with this one.
Click to expand...
Click to collapse
confirmed!! this kernel is the ****!.. try it... (don't blame me if you brick your device)

The link to download the kernel won't work anymore, is there a mirror?

Please HELP ME LENOVO COMMUNITY ??

I am having some issues when its in download mode my pc shows alot of drives n asking me to format it n the downloder is not reading my phone n the fastboot is showing the remote error n adb doesnt detect my phone at all......i need helppp*
I tried installing the stock os several times before but my phone boots to the 'lenovo for those who do' part n then reboots....it reboots before even the logo completes......it booted once n there is no sound no readings for sim at all......I NEED SERIOUS HELP
:crying:
:crying:
:crying:

Which version os did you have when the phone got bricked? I suppose you have twrp installed. First try to wipe data partition in twrp and reboot.
If that won't work then try installing a custom rom same as the android version you had on your phone (for example, if you had marshmallow os the find a marshmallow custom rom).
You can also try the same with any latest stock firmware. Make sure it is a flashable zip.
Hope this helps.