• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

One SV K2_cl frustration

N

Nuttsy711

Newbie
Ok I bought this phone a month back with JB 4.4.2 Hboot 2.21 on it. I took me a few days to get this thing rooted with SU and TWRP Recovery. Now lies the problems. I cant flash anything. kernels act like there flashing then I reboot the phone and its back to stock. I tried deleting bloatware then it reboots then back to stock. I tried using rumrunner to get s-off wont work and that's the same for moonshine. I love this phone but cant do anything with it as it seems. I was able to get viper rom 1.6 on it but it crashed after a min or two running it then I flashed my backup. so I know I can flash roms. what am I doing wrong? ADB & Fastboot are working fine so I know its not that... this phone have a exercist kernel I need to know about?
 
Anyone? Have any method that I'm not doing right? Any suggestion? How about a .img or .zip of a stock Rom without this write protection kernel?
 
Because you are S-On the write protection found in the stock kernel will only allow you to temporarily delete system files. Upon reboot they are restored. A custom kernel with this write protection removed is required. Otherwise you must be S-Off or remove the system files from within the TWRP recovery. It will stick then because the kernel used for our custom recovery has write protection removed so when you reboot it will actually stick ;-).

As for flashing a kernel/boot.img you must use fastboot. Only those who are S-Off can install a kernel/boot.img from within their device.

Code: 
fastboot flash boot boot.img

The same applies when restoring with a TWRP/CWM backup. You must rename the boot backup to boot.img and apply it using fastboot. As well as with your recovery. System, data, cache, etc can be applied from within your device while S-On but the above mentioned cannot. You have limitations.
 
ModdingMyMind said:
Because you are S-On the write protection found in the stock kernel will only allow you to temporarily delete system files. Upon reboot they are restored. A custom kernel with this write protection removed is required. Otherwise you must be S-Off or remove the system files from within the TWRP recovery. It will stick then because the kernel used for our custom recovery has write protection removed so when you reboot it will actually stick ;-).

As for flashing a kernel/boot.img you must use fastboot. Only those who are S-Off can install a kernel/boot.img from within their device.

Code: 
fastboot flash boot boot.img

The same applies when restoring with a TWRP/CWM backup. You must rename the boot backup to boot.img and apply it using fastboot. As well as with your recovery. System, data, cache, etc can be applied from within your device while S-On but the above mentioned cannot. You have limitations.
Click to expand...

Took me a good while but finally got it ty Mr. Nodding my mind! Im s-off and been trying out a few kernels to see what I like. Really wish there were custom tons out there for this phone been very happy with it.
 
Nuttsy711 said:
Took me a good while but finally got it ty Mr. Nodding my mind! Im s-off and been trying out a few kernels to see what I like. Really wish there were custom tons out there for this phone been very happy with it.
Click to expand...

How did you get s-off? I have root with twrp but my attempts to get s-off have failed.
 
did anyone notice he also said 4.4.2 the k2_cl only goes up to 4.2.2 so did you somehow flash the wrong ruu file? thru soff maybe.not wise as the only ruu thats really compatiable is the one it comes with.other ruus are gsm this is a cdma phone.this could be part of the problem,unless you typoed what your on,and most kernals are outdated and dont do any good.you flash a kernal for say ics or 4.1.2 on something higher your gonna have more problems than its worth
 
You must log in or register to reply here.
Back
Top Bottom