We need a fix for the /system write protected phones. Can anyone help!

[Guest lunario]

Problem is not bootloader itself we have custom recovery and cm 12 bugged so bootloader is sort of unlocked. Problem is newer su6 have system write protected

[Guest lunario]

Like konstat says zte crippled the bootloader

[Guest Textman]

On 05/12/2015 at 5:47 PM, lunario said:

boot_cpus=0 androidboot.earlyboot_cpus=2,4,6 sched_enable_hmp=1 console=ttyHSL0,115200,n8 androidboot.console=ttyHSL0 androidboot.selinux=permissive androidboot.hardware=qcom user_debug=30 msm_rtb.filter=0x3F ehci-hcd.park=3 androidboot.bootdevice=7824900.sdhci lpm_levels.sleep_disabled=1 androidboot.emmc=true androidboot.serialno=**** androidboot.baseband=msm mdss_mdp.panel=1:dsi:0:qcom,mdss_dsi_nt35596_lead_otp_1080p_video:1:none androidboot.mode=normal loglevel=4 serial_status=0

root@msm8916_32:/

 

boot_cpus=0 androidboot.earlyboot_cpus=2,4,6 sched_enable_hmp=1 console=ttyHSL0,115200,n8 androidboot.console=ttyHSL0 androidboot.selinux=permissive androidboot.hardware=qcom user_debug=30 msm_rtb.filter=0x3F ehci-hcd.park=3 androidboot.bootdevice=7824900.sdhci lpm_levels.sleep_disabled=1 androidboot.emmc=true androidboot.serialno=******** androidboot.baseband=msm mdss_mdp.panel=1:dsi:0:qcom,mdss_dsi_nt35596_lead_otp_1080p_video:1:none androidboot.mode=normal loglevel=4 serial_status=0 kpdpwr_warm_reset=0
root@msm8916_32:/ #

 

 I can't help but notice the kpdpwr_warm—reset=0 missing from your code. 

Could this be a clue, or did an app modify this thing?  

[Guest lunario]

No just normal root

[Guest lunario]

Don't know what that means maybe Konstat knows