how to root lenovo vibe k5 note ?

[romsurfer]

Guys keep working please we need root and recovery

Just keep working guys we need root y'all Saying to sell phone or something but some of us like me can't replace phone because I just bought recently

 

[momamman]

I think it has something to do with international variants of a phone... im not sure

My past 3 phones have all been internationally launched (in India) but i noticed the dev team for them never came through .

Recently, HTC ONE ME gave me that problem. HTC devs just did not give a crap about the phone nor its users

 

[atf2m4]

can we Magisk to root this phone?. Any idea.

 

[syndromtr]

"To use Magisk, you'll need a device with an unlocked bootloader that is running Android 5.0+."

 

[archer queen]

Flash lollipop stock ROM and root using kingroot app

Here is complete support for k5 note
vibek5note.blogspot.in

 

[archer queen]

This videos explains everything

youtu.be/zpauf6NtxNo

 

[romsurfer]

Guys I got something on my mind..

So if this guy ported working TWRP ​ why not anyone port a marshmallow or nougat ROM for Lenovo k5 note so we can flash it and get root by superSU zip... (I just thought that Sorry if it's dumb idea)

 

[atf2m4]

Downgrading is an option. But we have a serious bottleneck in Lollipop, VOLTE is not available.

 

[ananthuthilakan]

After rooting at lolipop try flashing ota using flashfire app (by chainfire) to update without losing root
Its worth a try

https://forum.xda-developers.com/general/paid-software/flashfire-t3075433

 

[PrestigioManSK]

Cant get it work

Im trying to flash twrp but keep getting "FAILED (remote: download for partition 'recovery' is not allowed)" so i think thats not how it is supposed to work am i missing something?

 

[comprocks]

Guys... Please read the previous pages of the thread before attempting something. All of this has been tried and has not worked.

So if this guy ported working TWRP ​ why not anyone port a marshmallow or nougat ROM for Lenovo k5 note so we can flash it and get root by superSU zip... (I just thought that Sorry if it's dumb idea)

We can't flash a new ROM because the preloader and kernel have boot, system and recovery image verification. If any of the images cannot be verified, the device does not boot! When you reflash the stock ROM, you would end up losing NVRAM data (IMEIs, WiFi MAC Address). A version of TWRP had been ported to this but it caused verification errors and didn't allow the device to go even into recovery.

After rooting at lolipop try flashing ota using flashfire app (by chainfire) to update without losing root
Its worth a try
https://forum.xda-developers.com/general/paid-software/flashfire-t3075433

If you downgrade, root and then upgrade, the image verification does not let it boot.

Im trying to flash twrp but keep getting "FAILED (remote: download for partition 'recovery' is not allowed)" so i think thats not how it is supposed to work am i missing something?

Remote download (fastboot flash recovery) is not allowed due to the image verification and fastboot restrictions.

The only way is to decompile the preloader and kernel files and remove the image verification from them (which is what I am working on). Only then we would be able to flash recoveries/ROMs/SuperSU as we please.

If you still want to go ahead and flash something, use the SP Flash Tool but be warned: Flashing anything root related will render the device un-bootable! Be sure to write down your IMEIs and WiFi MAC Address if you must continue.

 

[ananthuthilakan]

Guys... Please read the previous pages of the thread before attempting something. All of this has been tried and has not worked.


We can't flash a new ROM because the preloader and kernel have boot, system and recovery image verification. If any of the images cannot be verified, the device does not boot! When you reflash the stock ROM, you would end up losing NVRAM data (IMEIs, WiFi MAC Address). A version of TWRP had been ported to this but it caused verification errors and didn't allow the device to go even into recovery.


If you downgrade, root and then upgrade, the image verification does not let it boot.


Remote download (fastboot flash recovery) is not allowed due to the image verification and fastboot restrictions.

The only way is to decompile the preloader and kernel files and remove the image verification from them (which is what I am working on). Only then we would be able to flash recoveries/ROMs/SuperSU as we please.

If you still want to go ahead and flash something, use the SP Flash Tool but be warned: Flashing anything root related will render the device un-bootable! Be sure to write down your IMEIs and WiFi MAC Address if you must continue.

PLs understand that its not direct upgrade
But via flashfire which allows to upgrade by skipping those verification

And its not been triedby anybody for k5 note
And its true that , that guy has ported and succesfully flashed twrp
See his tutorial in youtube
He has not flashed twrp via spflash tool bcz of this verification it fails but via flashify or something

So the point is these things are not already tried things but new
Read and understand carefully before dumbing the new feeds

Thanks

 

[comprocks]

PLs understand that its not direct upgrade
But via flashfire which allows to upgrade by skipping those verification

And its not been triedby anybody for k5 note
And its true that , that guy has ported and succesfully flashed twrp
See his tutorial in youtube
He has not flashed twrp via spflash tool bcz of this verification it fails but via flashify or something

So the point is these things are not already tried things but new
Read and understand carefully before dumbing the new feeds

Thanks

I'm sorry. I misspoke and I did not mean to offend you. What I wanted to say was, you have already recommended this method before and nobody had rooted Lollipop to try it out. I still think it is a good idea, just as I thought back then, and if anybody can try it out, it would be great.

 

[kathanpatel1001]

I have found the file called DIGEST.MD5 in zip for 6.0 ".\A7020a48_S259_160721_ROW.7z\A7020a48_S259_160721_ROW\SW\target_bin\ DIGEST.MD5" which contains all the md5 of the file system. So what if we modify the system to get root and recovery then recalculate the md5 of the modified files and insert them into the DIGEST.MD5. Will it pass verification of recovery.img?

 

[atf2m4]

I have found the file called DIGEST.MD5 in zip for 6.0 ".\A7020a48_S259_160721_ROW.7z\A7020a48_S259_160721_ROW\SW\target_bin\ DIGEST.MD5" which contains all the md5 of the file system. So what if we modify the system to get root and recovery then recalculate the md5 of the modified files and insert them into the DIGEST.MD5. Will it pass verification of recovery.img?

Nice idea. someone should throw more light on it.

 

[Ankur.D521]

I have found the file called DIGEST.MD5 in zip for 6.0 ".\A7020a48_S259_160721_ROW.7z\A7020a48_S259_160721_ROW\SW\target_bin\ DIGEST.MD5" which contains all the md5 of the file system. So what if we modify the system to get root and recovery then recalculate the md5 of the modified files and insert them into the DIGEST.MD5. Will it pass verification of recovery.img?

But then wouldn't we have to repeat this everytime after modifying system files like editing build.prop etc ?

 

[kathanpatel1001]

But then wouldn't we have to repeat this everytime after modifying system files like editing build.prop etc ?

But atleast we would acquire root and recovery once the root and recovery is achieved we can think of further modifications. Unfortunately i don't have enough skill to apply this tweaks to the device also this phone is my daily driver cant afford to brick it.

 

[Ankur.D521]

But atleast we would acquire root and recovery once the root and recovery is achieved we can think of further modifications. Unfortunately i don't have enough skill to apply this tweaks to the device also this phone is my daily driver cant afford to brick it.

I agree with you.

 

[romsurfer]

Some hopes restored

Anyone working on this method??

 

[comprocks]

What if we modify the system to get root and recovery then recalculate the md5 of the modified files and insert them into the DIGEST.MD5. Will it pass verification of recovery.img?

Sounds like a great idea, mate. I will try this out today and let you guys know whether it works!

EDIT: We aren't really flashing the DIGEST.MD5 file onto the phone through the flash tool and I can't find it in the system or boot images. It is probably only there for the SP Flash Tool to verify (just like the Checksum.ini file). I don't think editing that would solve the issue.