Root Lenovo Vibe P1M
This guide will help you to root Lenovo Vibe P1M without bricking it.
Check this first.
Take backup of your important data at safe place.
Device must adequately charged.
Install USB drivers of your device PC.
Enable USB Debugging from Developer Options in Settings.
Enable Unknown Sources from Security in Settings.
Install TWRP
Follow the steps below.
Download ADB fastboot drivers [from here] and install it on PC.
Download TWRP recovery for Lenovo Vibe P1M from here.
Extract the zip file and find recovery.img file. Copy this file to your PC where you installed ADB fastboot drivers.
Now open Command Prompt.
Go to directory where you have installed ADB fastboot drivers.
Now enter the following commands.
Code:
adb reboot bootloader
fastboot oem unlock
fastboot flash recovery.img [B]OR[/B] fastboot boot recovery.img
fastboot reboot
After first command your device will reboot in fastboot mode. The second command will flash recovery image on your device. The third command will reboot your phone.
Now TWRP recovery is get installed on your Lenovo Vibe P1M.
Root Lenovo Vibe P1M
After installing TWRP on Lenovo Vibe P1M, follow the given steps to root it.
Download SuperSU from here.
Place the downloaded SuperSu zip in your extetnal SD card.
Now go to command prompt again and type the following command.
adb reboot recovery
Now your device will reboot in recovery mode. Flash supersu.zip from TWRP.
Reboot your device.
process completed.
Warning: I am not responsible if anything goes wrong, bricked device.
Does this method work with firmware ver S029. I am already rooted with kingoapp. But Flashfire app shows boot loader partitions to be protected . I suspect bootloader to be Locked. In such senario will this method work or will it brick my phone.
I also have another question if flash TWRP recovery on locked bootloader anyway, will it only fail to boot into recovery mode or will device fail to boot normally altogether
and it does boot normally then if i reflash stock recovery back on locked bootloader will that fix the issue of booting into recovery mode.
junkhunzai said:
Does this method work with firmware ver S029. I am already rooted with kingoapp. But Flashfire app shows boot loader partitions to be protected . I suspect bootloader to be Locked. In such senario will this method work or will it brick my phone.
I also have another question if flash TWRP recovery on locked bootloader anyway, will it only fail to boot into recovery mode or will device fail to boot normally altogether
and it does boot normally then if i reflash stock recovery back on locked bootloader will that fix the issue of booting into recovery mode.
Click to expand...
Click to collapse
This method will work ver S029 also. To flash recovery you need unlocked bootloader.
Well, I'm getting an error - (remote: not allowed), every time I try to boot the recovery.
ᵀᴴᴱ HUИTΞR said:
Well, I'm getting an error - (remote: not allowed), every time I try to boot the recovery.
Click to expand...
Click to collapse
Have you unlocked it?
1st command may be this
Fastboot oem unlock
Sent from my Redmi Note 3 using XDA-Developers mobile app
prajj said:
Have you unlocked it?
1st command may be this
Fastboot oem unlock
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock
...
OKAY [ 7.103s]
finished. total time: 7.105s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 1.075s]
booting...
FAILED (remote: unknown command)
finished. total time: 1.081s
C:\Program Files (x86)\Minimal ADB and Fastboot>
P.S: And now I have reboot loop... Reboot> Logo> Reboot > Logo...to infinity with a non-removable battry - just perfekt
P.S.: I can't get to recovery anymore...
ᵀᴴᴱ HUИTΞR said:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock
...
OKAY [ 7.103s]
finished. total time: 7.105s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 1.075s]
booting...
FAILED (remote: unknown command)
finished. total time: 1.081s
C:\Program Files (x86)\Minimal ADB and Fastboot>
P.S: And now I have reboot loop... Reboot> Logo> Reboot > Logo...to infinity with a non-removable battry - just perfekt
P.S.: I can't get to recovery anymore...
Click to expand...
Click to collapse
Have you extracted the zip file and copied recovery.img file from zip to your PC where you installed ADB fastboot drivers?? And use following command to flash recovery.img
Code:
fastboot flash recovery.img
Also take a look at this thread for reference --> http://forum.xda-developers.com/nexus-4/help/solved-fastboot-boot-recovery-img-t2380675
bravonova said:
Have you extracted the zip file and copied recovery.img file from zip to your PC where you installed ADB fastboot drivers?? And use following command to flash recovery.img
Code:
fastboot flash recovery.img
Also take a look at this thread for reference --> http://forum.xda-developers.com/nexus-4/help/solved-fastboot-boot-recovery-img-t2380675
Click to expand...
Click to collapse
Hi Bravo
fastboot flash recovery.img gives ->
unkown partition 'recovery.img'
error : cannot determine image filename for 'recovery.img'
and have the exact errors as Hunter but no loopboot until now
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 1.075s]
booting...
FAILED (remote: unknown command)
finished. total time: 1.081s
finguers croosed
Edit :
some sites with roms are pointing to CPU MT6735M only , like needrom.com and techolite.com, mine is MT6735P, is there a difference ?
Nabil99 said:
Hi Bravo
fastboot flash recovery.img gives ->
unkown partition 'recovery.img'
error : cannot determine image filename for 'recovery.img'
and have the exact errors as Hunter but no loopboot until now
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 1.075s]
booting...
FAILED (remote: unknown command)
finished. total time: 1.081s
finguers croosed
Edit :
some sites with roms are pointing to CPU MT6735M only , like needrom.com and techolite.com, mine is MT6735P, is there a difference ?
Click to expand...
Click to collapse
Hey bro use flashify app to flash recovery through phone...
Stock Recovery backup deleted.
Hi, my vibe p1m now is running twrp recovery, but i accidentally deleted my backup of stock recovery yeah i know im dumb, but if someone can provide a link.. please help me....
Can anyone share a boot.img plz.? I forgot to back up mine.. Thanks a ton!
mikkel19 said:
Hi, my vibe p1m now is running twrp recovery, but i accidentally deleted my backup of stock recovery yeah i know im dumb, but if someone can provide a link.. please help me....
Click to expand...
Click to collapse
http://firmwarefile.com/lenovo-vibe-p1m/
This link gives you stock firmware. I too have deleted my backup but used it to get it back. But however I faced problems like boot loop many times and even IMEI turned 000000000000000 for both sim slots but still it was recovered by using "MTK Engineering Mode" app which you can get from "Play Store" and follow the following steps.
Step 1) Open the the MTK Engineer mode app and swipe left side to go into Connectivity.
Step 2) In the Connectivity click on the CDS information.
Step 3) And then Tap on the Radio information.
Step 4) Then you will be able to see Phone 1 and Phone 2
Step 5) Just click on Phone 1 first. then enter the Command as AT +EGMR=1,7,"your first imei" (Put a Space between AT and +, Like AT +EGMR=1,10,"your imei") and then tap on SEND AT COMMAND it will show you that command sent,
Step 6) Now press back button and Tap on Phone 2 (if you have a Dual Sim phone) and Type AT +EGMR=1,10,"second imei" and tap on send at command.
Step 7) Now Just Restart you device and enjoy now Sim Card will Display the Network in the status bar.
And you are done!!!!!!!!!
You can see your IMEI by pressing *#06#
If you face boot loop problems again and again please inform me.
Just the problems I faced. They are the solutions. Please do reply to this message.
Okay thank you. I will try it. Thanks a lot
mikkel19 said:
Okay thank you. I will try it. Thanks a lot
Click to expand...
Click to collapse
Please do ask if you get any problems coz my device is same and I've tried with 3-4 different ROMs including stock so can help you with many problems.
---------- Post added at 04:42 PM ---------- Previous post was at 04:39 PM ----------
You can also root Lenovo Vibe P1m using SP Flash Tool. I've done the same and changed recovery from stock to TWRP easily without using any commands. Device works flawlessly and currently have installed MiUI 8 custom ROM.
mikkel19 said:
Okay thank you. I will try it. Thanks a lot
Click to expand...
Click to collapse
Oh and one more thing that zip file isn't for installing. You have to first extract it then you will get the instructions for flashing stock ROM. Happy flashing!!!!!
Sharath Guddad said:
Oh and one more thing that zip file isn't for installing. You have to first extract it then you will get the instructions for flashing stock ROM. Happy flashing!!!!!
Click to expand...
Click to collapse
Thank you, My vibe p1m is running on stock rom now, many thanks )))
Nabil99 said:
Hi Bravo
fastboot flash recovery.img gives ->
unkown partition 'recovery.img'
error : cannot determine image filename for 'recovery.img'
and have the exact errors as Hunter but no loopboot until now
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 1.075s]
booting...
FAILED (remote: unknown command)
finished. total time: 1.081s
finguers croosed
Edit :
some sites with roms are pointing to CPU MT6735M only , like needrom.com and techolite.com, mine is MT6735P, is there a difference ?
Click to expand...
Click to collapse
Fastboot command given for flash recovery is wrong.
The right command is
Fastboot flash recovery recovery.img
Second recovery is the name of your recovery. If your recovery name is twrp then command is
Fastboot flash recovery twrp.img
Guys... If your device is new version (s036 pre installed) , use TWRP3 only.
Ashwinrg said:
Fastboot command given for flash recovery is wrong.
The right command is
Fastboot flash recovery recovery.img
Second recovery is the name of your recovery. If your recovery name is twrp then command is
Fastboot flash recovery twrp.img
Click to expand...
Click to collapse
C:\Fastboot>fastboot flash recovery recovery.img
target reported max download size of 134217728 bytes
sending 'recovery' (10642 KB)...
OKAY [ 1.063s]
writing 'recovery'...
FAILED (remote: download for partition 'recovery' is not allowed
)
finished. total time: 1.078s
cuci8202 said:
C:\Fastboot>fastboot flash recovery recovery.img
target reported max download size of 134217728 bytes
sending 'recovery' (10642 KB)...
OKAY [ 1.063s]
writing 'recovery'...
FAILED (remote: download for partition 'recovery' is not allowed
)
finished. total time: 1.078s
Click to expand...
Click to collapse
use TWRP3 only.. or install via sp flash tool.. it's very easy.. check this.. u can also get TWRP 3 here..
http://forum.xda-developers.com/android/general/how-to-install-twrp-root-lenovo-vibe-t3538088/page1
Hi all,
I have an LG G5 H850. I'm trying to install TWRP using ADB. I've had it previously and it worked fine. I'm pretty sure the bootloader is unlocked. Anyway, when I do "fastboot flash recovery twrp-3.1.1.1-0-h850.img" I get the following output:
target reported max download size of 536870912 bytes
sending 'recovery' (19076 KB)...
OKAY [ 0.431s]
writing 'recovery'...
OKAY [ 0.345s]
finished. total time: 0.781s
To me, that looks as though thats worked fine. Now when I try fastboot boot twrp-3.1.1.1-0-h850.img I get the following:
downloading 'boot.img'...
OKAY [ 0.432s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.456s
Has anyone got any ideas on this?
Same here
I am having the same problem, please help
Had this issue a while back. I resorted to doing complete flash with LGUP to the latest version and then it worked. I had been messing around with various ROMS on different android versions.
lywyn said:
Had this issue a while back. I resorted to doing complete flash with LGUP to the latest version and then it worked. I had been messing around with various ROMS on different android versions.
Click to expand...
Click to collapse
Don't happen to know where I could get a rom that it would work with do you?
Managed to solve this. Flashed the TWRP image using fastboot flash recovery <img> via adb. Then I unplugged from USB, and got into recovery mode by doing power + volume down buttons and quickly release and repress ont he LG logo. Answered yes to both questions and got into TWRP.
Barsbeh said:
Managed to solve this. Flashed the TWRP image using fastboot flash recovery <img> via adb. Then I unplugged from USB, and got into recovery mode by doing power + volume down buttons and quickly release and repress ont he LG logo. Answered yes to both questions and got into TWRP.
Click to expand...
Click to collapse
That is the required way of doing it. You have to boot into recovery after flashing the recovery or it gets reset.
Hi,
Having a similar problem since trying to update my ROM ... and the Magisk install failed. Now I can only get to fastboot, can't get to recovery. And, tried this,
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp-3.1.1-0-h830.img
target reported max download size of 536870912 bytes
sending 'recovery' (18644 KB)...
OKAY [ 0.439s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.461s
Help!?! ... and thanks!
Could someone help my device is brick and currently stuck in fastboot attempted to flash TWRP error message
fastboot flash recovery twrp-2.8.7.1-v500.img
target reported max download size of 536870912 bytes
sending 'recovery' (12492 KB)...
OKAY [ 0.396s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.402s
highgrade said:
Could someone help my device is brick and currently stuck in fastboot attempted to flash TWRP error message
fastboot flash recovery twrp-2.8.7.1-v500.img
target reported max download size of 536870912 bytes
sending 'recovery' (12492 KB)...
OKAY [ 0.396s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.402s
Click to expand...
Click to collapse
Well this is a v521 forum. So if you have a v521, then trying to flash twrp for the v500 would be your first mistake.
Can you kdz back to stock?
I have the 521 I trying to Restoring kdz lg tool not seeing my device detected
highgrade said:
I have the 521 I trying to Restoring kdz lg tool not seeing my device detected
Click to expand...
Click to collapse
Yeah you tried to flash twrp for the v500 which could probably mean a hard brick.
Read the last couple pages of this thread to see if it will work for you. Good luck. https://forum.xda-developers.com/g-...-v521-guide-to-update-v521-lg-t3533338/page28
So I just followed the steps to unlock the bootloader for my Mate 10 pro and wanted to continue installing TWRP and then Magisc, but after I unlocked it, it refuses to show up in my adb devices. Any suggestions? I also tried to list the device on Ubuntu with no success When I try to run the fastboot flash recovery_ramdisk twrp.img this msg come up:
target reported max download size of 471859200 bytes
sending 'recovery_ramsik' (8622 KB)...
OKAY [ 0.188s]
writing 'recovery_ramsik'...
FAILED (remote: partition length get error)
finished. total time: 0.203s
Try reinstalling the drivers
Bowserman16162 said:
Try reinstalling the drivers
Click to expand...
Click to collapse
I did it several times without success.
Bowserman16162 said:
Try reinstalling the drivers
Click to expand...
Click to collapse
Its listed as an Android Bootloader Interface if that helps...
Then maybe try using fastboot instead of adb you can install stuff from that.
Before:
I just unlocked the bootloader and installed a custom ROM (LineageOS 15.1: https://forum.xda-developers.com/huawei-y6/development/lineageos-15-1-huawei-y6-2018-t3832278) on my Huawei but it won't let me flash the TWRP from adb. I tried before flashing the custom ROM and also after but no progress. I tried with 'fastboot flash recovery recovery.img' as well as 'fastboot flash boot recovery.img' because I knew some smartphones include the recovery in the boot.img but I am always getting the same error:
Code:
fastboot flash recovery recovery.img
target reported max download size of 535822336 bytes
sending 'recovery' (16544 KB)...
OKAY [ 0.522s]
writing 'recovery'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.553s
I am not an expert but I understood that 'recovery' partition doesn't exist. I found some possible solutions online such as writing 'fastboot flash RECOVERY recovery.img' or 'fastboot flash erecovery recovery.img' (because Huawei calls the stock one 'erecovery') but they both gave me another error:
Code:
fastboot flash RECOVERY recovery.img
target reported max download size of 535822336 bytes
sending 'RECOVERY' (16544 KB)...
OKAY [ 0.522s]
writing 'RECOVERY'...
FAILED (remote: Command not allowed)
finished. total time: 0.528s
UPDATE: I found, maybe, the correct name of the recovery partition and it seems to work:
Code:
fastboot flash recovery_ramdisk twrp.img
< waiting for device >
target reported max download size of 535822336 bytes
sending 'recovery_ramdisk' (14026 KB)...
OKAY [ 0.443s]
writing 'recovery_ramdisk'...
OKAY [ 0.323s]
finished. total time: 0.767s
BUT it actually doesn't work properly because when I boot into recovery it boots the stock one. I tried other solutions found on the net like instantly unplug the phone after the flash and reboot it into recovery immediately but again it boots into stock one...
OTHER UPDATE: I managed to find and flash a TWRP that can boot up but it shows the internal storage 0MB not allowing me to install any .zip file. Because of that, I cannot install SuperSU to get root access.
I tried installing TWRP also with stock ROM but still showing 0MB because the phone is encrypted. To disable encryption I need to install the bluspark TWRP (As I found online), the problem is that bluspark won't boot and gets immediately overwritten by the stock ROM as it happened with the one I mentioned in the first update of the post.
Now I will try buying a microSD card and see if it shows right so that I can still flash .zip from the microSD card.
Now:
LATEST UPDATE: The SD card is working properly and I see it as around 60 GB instead of 64 but that's not the problem. I can see the .zip files I'd want to flash but when I try to do it it says me that it failed to mount every single partition and after some research I discovered that my Huawei has all the data encrypted. After other research I found that there are some TWRPs like blu_spark that could decrypt the data but every version I tried doesn't work and gets immediately overwritten by the stock recovery.
Does anyone know other methods to decrypt all the data on Huawei? Otherwise it's impossible to flash any .zip. Actually it flashes it but it fails to update the partitions state so the system doesn't recognize the changes.
Rooting Huawei is so difficult.. I will buy an OP5t as soon as I have the money XD.
Y6 2018 twrp
Any progress? I'm also looking for a version of TWRP that works with the Y6 2018.