Lenovo K6 Power - Rooting,Unlock bootloader,Install TWRP and use Xposed on Stock Rom - Lenovo K6 / K6 Power / K6 Note Guides, News, & Dis

Hello guys,
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Lenovo K6 Power k33a42 is a new device released by lenovo on Dec 16, as many of you have bought this phone i would like to share how this phone can be rooted and how we can install twrp on this phone
UNLOCKING BOOT-LOADER : ​
Unlocking your Android phones bootloader is the first step to rooting and flashing custom ROMs
WARNING: UNLOCKING YOUR BOOTLOADER VOIDS YOUR WARRANTY.PROCEED AT YOUR OWN RISK.
NOTE: Unlocking the bootloader will Wipe/ factory reset your device, and will delete all personal data from your device such as apps, photos, messages, and settings.
INSTRUCTIONS:
1) Download the View attachment K33a42_bootloader_unlock.zip and View attachment drivers.zip zip archive attached here
2) On your device, turn on USB debugging and allow OEMunlocking
if there is no developer options in settings - go to the " Settings -> Device Info " and click on the item " Build number " until the display shows that " you became a developer
go back to the device's main Settings menu and go to Developer options tick "OEM unlocking " and " USB debugging'
when you connect for the first time using debugging via USB you will need to confirm the RSA fingerprint key to trust the PC
3) Extract the Unlock bootloader zip to any directory
4) Connect the device (K33a42) to a PC via USB-cable.
5. Go to the extracted directory and execute Unlock_Bootloader.bat and expect to complete the unlock process.
after the process is completed the boot loader will be unlocked.
INSTALLING TWRP :​
1) Extract the folder View attachment TWRP.zip archive to any drive.
2)On your phone, turn on USB debugging (drivers for ADB must be installed).
Connect your phone to a PC via usb-cable
3) You have 2 options either you can try the TWRP (only run one time) or else you can replace the stock recovery with twrp
Use accordingly
run Flash-TWRP.bat (replace stock recovery) or
run Run-TWRP.bat (for one time only).
4) Wait for the phone to boot into TWRP.
You can now disconnect the usb-cord.
Installation is finished.
and also at the starting of the twrp recovery the language will be in Russian because the creator in SevenMaxs from lenovo-forums.ru (I'am looking forward to modify default lang to english)
here is the video which shows how to do so
https://www.youtube.com/watch?v=KOhR92EKD7A
* In the stock firmware Secure Boot is enabled by default , so any changes made to the system partiton lead to a bootloop. Therefore, when you first start TWRP set the system mode to Read Only !
So in order to proceed we need to disable the secure booting in the kernel
Now to disable Secure Boot verification in the boot.img
1. Extract boot.img using twrp backup of boot partition
(you can use android image kitchen for extracting)
2. Make changes in the ramdisk \ default.prop file
change the following line:
ro.secure = 1
to
ro.secure = 0
3. repacked boot.img and flash into the device using twrp.
I know this part may be tough for some uses hence voila i have the secure boot disabled boot image , flash this to boot partition using twrp​
ROOTING​
Flashing SuperSU zip via TWRP Recovery
Download and transfer the View attachment SuperSU-v2.79-201612051815.zip zip file attached here to your device’s storage.
Boot your device into TWRP recovery.
Tap on Install and select the SuperSU zip file that you transferred to your device in Step 1.
After selecting the .zip file, do Swipe to Confirm Flash on the bottom of screen to begin the flashing process.
Once SuperSU is flashed, you’ll get Reboot System option, select it.
Congratulations! Your device should be rooted now. Look for the SuperSU app in app drawer.
INSTALLING XPOSED​
1)Install the xposed installer from playstore
2)Open the installer, and tap the ‘Install/Update’ button. Don’t worry if the app seems stuck here; just give it time and it will eventually show you a Superuser request, which you should make sure to grant and click reboot
Almost all the modules should work on stock rom as it is close to Aosp
modules which i can confirm to work are
: Android N-ify
; Gravitybox
: Bootmanager
:fingers-crossed:

---

All the credit goes to SevenMaxs
for creating the recovery
and for his guides for proper installation
orginal forum thread
please thank him :fingers-crossed::fingers-crossed:

---

Thank you

---

Thankzz.
Sent from my CAM-L21 using Tapatalk

---

When i try to flash SuperSU-v2.79-201612051815.zip, it says that is corrupt. What can i do ?

---

Plzz, fix it
Sent from my CAM-L21 using Tapatalk

---

I found another SuperSU, that worked for me: https://www.androidfilehost.com/?fid=385035244224405790
Thank you again ArjunrambZ and SevenMaxs!

---

LoverOfLife said:
When i try to flash SuperSU-v2.79-201612051815.zip, it says that is corrupt. What can i do ?
Click to expand...
Click to collapse
i will take a look at the zip, may be upload problem, well any super su zip will work,, this was thw one that i tried
Sent from my VIBE K6 Power using XDA Labs

---

LoverOfLife said:
Thank you
Click to expand...
Click to collapse
taweng7 said:
Thankzz.
Click to expand...
Click to collapse
taweng7 said:
Plzz, fix it
Click to expand...
Click to collapse
will uplpad today
also the secure boot disabled boot img also
:laugh:
Sent from my VIBE K6 Power using XDA Labs

---

I'll add adb/fastboot instruction for those who don't use Windows:
Of course you have to enable developer options, adb debug, oem unlocking
UNLOCK:
> adb reboot bootloader
> fastboot oem device-info
> fastboot oem unlock-go
(and... yes you can lock it back with fastboot oem lock)
TWRP:
> fastboot flash recovery /path/to/your/twrp.img
> fastboot oem reboot-recovery
BOOT.IMG:
> fastboot flash boot /path/to/your/ro.secure=0/boot.img
> fastboot reboot
P.S. (to manipulate your boot.img and change the default.prop file under linux you can use abootimg)

---

ilfastidio said:
I'll add adb/fastboot instruction for those who don't use Windows:
Of course you have to enable developer options, adb debug, oem unlocking
UNLOCK:
> adb reboot bootloader
> fastboot oem device-info
> fastboot oem unlock-go
(and... yes you can lock it back with fastboot oem lock)
TWRP:
> fastboot flash recovery /path/to/your/twrp.img
> fastboot oem reboot-recovery
BOOT.IMG:
> fastboot flash boot /path/to/your/ro.secure=0/boot.img
> fastboot reboot
P.S. (to manipulate your boot.img and change the default.prop file under linux you can use abootimg)
Click to expand...
Click to collapse
you seems to be working on linux, do u have the sources synced on ur pc?
meanwhile i will update the thread to include these to the topic
Sent from my VIBE K6 Power using XDA Labs

---

ArjunrambZ said:
you seems to be working on linux, do u have the sources synced on ur pc?
meanwhile i will update the thread to include these to the topic
Click to expand...
Click to collapse
I only work on linux. Windows is evil.
I have a big question: why in the default.prop of the russian TWRP.img there is ro.secure=1 ?????
It should be set to 0.
I guess that's why I bricked exactly after flashing Supersu from TWRP...

---

ilfastidio said:
I only work on linux. Windows is evil.
I have a big question: why in the default.prop of the russian TWRP.img there is ro.secure=1 ?????
It should be set to 0.
I guess that's why I bricked exactly after flashing Supersu from TWRP...
Click to expand...
Click to collapse
as far as i know.. having ro.secure enabled on recovery wont have any effect as we aren't changing anything withrespect to recovery.. but when we change something in system partition with a secure boot enabled kernel we get boot loops
Sent from my VIBE K6 Power using XDA Labs

---

ArjunrambZ said:
as far as i know.. having ro.secure enabled on recovery wont have any effect as we aren't changing anything withrespect to recovery.. but when we change something in system partition with a secure boot enabled kernel we get boot loops
Click to expand...
Click to collapse
Certainly I'm wrong, but I keep on not understanding. When you are in recovery mode you are loading the kernel inside the recovery and, of course, the default.prop inside the recovery.
That means that you flashed, or are going to flash, a boot.img with ro.secure=0 but running a recovery with ro.secure=1
From recovery you can manipulate system... but with a r0.secure=1 . I don't see a sense in this. But I'm a donkey.
I checked other official releases of twrp, and they all have ro.secure=0 in the default.prop

---

ilfastidio said:
Certainly I'm wrong, but I keep on not understanding. When you are in recovery mode you are loading the kernel inside the recovery and, of course, the default.prop inside the recovery.
That means that you flashed, or are going to flash, a boot.img with ro.secure=0 but running a recovery with ro.secure=1
From recovery you can manipulate system... but with a r0.secure=1 . I don't see a sense in this. But I'm a donkey.
I checked other official releases of twrp, and they all have ro.secure=0 in the default.prop
Click to expand...
Click to collapse
okay, firstly im also ain't any expert, but i get your point
i dont know why secure boot was enabled in recovery
but when i tried the procedure as explained in the thread i didnt get bootloop ( keeping secure boot in recovery) hence i came to the conclusion that it may not be valid.,, and i may be completely wrong here, if some one could clarify if would be better
Sent from my VIBE K6 Power using XDA Labs

---

Rooting panasonic eluga note 32GB ROM
Please provide rooting mothod for panasonic eluga note

---

amnv said:
Please provide rooting mothod for panasonic eluga note
Click to expand...
Click to collapse
sorry i dont have the device
Sent from my VIBE K6 Power using XDA Labs

---

ArjunrambZ said:
sorry i dont have the device
Sent from my VIBE K6 Power using XDA Labs
Click to expand...
Click to collapse
Its ok brother.. Thanks

---

My wifi is not working can someone help me? I did this process and after that it's not working

---

foRgaK said:
My wifi is not working can someone help me? I did this process and after that it's not working
Click to expand...
Click to collapse
i havent experienced this issue
but if u can attach a log file of turning on tbw wifi ,we can help
Sent from my VIBE K6 Power using XDA Labs