[Guide][Root] Lenovo Vibe P1M - Lenovo Vibe P1m Guides, News, & Discussion

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

Related

[Q] flashed clockwork-touch now no recovery console?

Hi, i have an unlocked tf201 and tried to install recovery-clockwork-touch-5.8.1.8-tf201.img which seemd to go fine:
Code:
sudo ./fastboot -i 0x0b05 flash recovery recovery-clockwork-touch-5.8.1.8-tf201.img
sending 'recovery' (5380 KB)...
OKAY [ 2.432s]
writing 'recovery'...
OKAY [ 7.011s]
finished. total time: 9.443s
hamlet:Console_Connection michael$ ./fastboot reboot
rebooting...
finished. total time: 0.001s
Thing is the recovery console will not load, after i select it (RCK) nothing happens? The message at top of screen says
Code:
Booting into recovery kernel image
If power off and on again it will boot fine into latest Asus jelly bean rom.
I have tried to re-flash, but now i can no longer find the device in OSX?
Code:
adb devices
List of devices attached
This is the same in both fastboot and when booted normally?
Any ideas?
many thanks
Seems i can find it as a device with adb when booted normally, but not when in fastboot?
ah seems it does not matter if not seen as device when in fastboot as i tried flash again it it seems to work
Code:
sudo ./fastboot -i 0x0b05 flash recovery recovery-clockwork-touch-5.8.1.8-tf201.img
Password:
sending 'recovery' (5380 KB)...
OKAY [ 2.427s]
writing 'recovery'...
OKAY [ 6.286s]
finished. total time: 8.713s
but still it will not boot into recovery?
Thanks
Even tried flashing openrecovery-twrp for jb, but still won't boot into recovery?
any help here would very much appriciated
carperman said:
Even tried flashing openrecovery-twrp for jb, but still won't boot into recovery?
any help here would very much appriciated
Click to expand...
Click to collapse
You are not saying what we need to know.
What bootloader are you on ? Where is the "NVIDIA" logo when you first power on the device? Bottom center or bottom right ?
flumpster said:
You are not saying what we need to know.
What bootloader are you on ? Where is the "NVIDIA" logo when you first power on the device? Bottom center or bottom right ?
Click to expand...
Click to collapse
flumpster said:
You are not saying what we need to know.
What bootloader are you on ? Where is the "NVIDIA" logo when you first power on the device? Bottom center or bottom right ?
Click to expand...
Click to collapse
Sorry thought i had made it clear?
Thanks for the reply i will try and be clearer.
In answer to your question about nvidia logo, it is bottom right.
What i have:
New TF201
unlocked when running ICS
Updated to latest Asus Jelly Bean rom
What i want to achieve:
I wish to root tablet (super user) and eventually install a custom rom.
What i need to do:
Flash clockwork-touch
install superuser.zip via recovery console
Results:
adb devices - report device
fastboot devices - shows no devices
boot to fastboot with 'power/vol ok
fastboot -i 0x0b05 flash recovery *.img - seems to work, see OP
fastboot reboot-bootloader works though recovery never loads
boot to recovery with 'power/vol never loads
For the last 2 it just says
Booting into recovery kernel image
I tried installing rtr_recovery-clockwork-touch which patched version, which again seems to work
Code:
fastboot -i 0x0b05 flash recovery rtr_recovery-clockwork-touch-5.8.1.8-tf201/recoveryblob
sending 'recovery' (5398 KB)...
OKAY [ 2.387s]
writing 'recovery'...
OKAY [ 6.398s]
finished. total time: 8.785s
Code:
fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
This worked, but as before nothing happens it just sits at B]
Booting into recovery kernel image[/B]
The two issue i have are:
fastboot cannot see devices (seem to work though)
recovery is not loading
I can only assume that even though fastboot seems to flashing device, blue load bar appears on tablet and reboot-bootloader commands works, it is not actually flashing the device?
thanks
carperman said:
Sorry thought i had made it clear?
Thanks for the reply i will try and be clearer.
In answer to your question about nvidia logo, it is bottom right.
What i have:
New TF201
unlocked when running ICS
Updated to latest Asus Jelly Bean rom
What i want to achieve:
I wish to root tablet (super user) and eventually install a custom rom.
What i need to do:
Flash clockwork-touch
install superuser.zip via recovery console
Results:
adb devices - report device
fastboot devices - shows no devices
boot to fastboot with 'power/vol ok
fastboot -i 0x0b05 flash recovery *.img - seems to work, see OP
fastboot reboot-bootloader works though recovery never loads
boot to recovery with 'power/vol never loads
For the last 2 it just says
Booting into recovery kernel image
I tried installing rtr_recovery-clockwork-touch which patched version, which again seems to work
Code:
fastboot -i 0x0b05 flash recovery rtr_recovery-clockwork-touch-5.8.1.8-tf201/recoveryblob
sending 'recovery' (5398 KB)...
OKAY [ 2.387s]
writing 'recovery'...
OKAY [ 6.398s]
finished. total time: 8.785s
Code:
fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
This worked, but as before nothing happens it just sits at B]
Booting into recovery kernel image[/B]
The two issue i have are:
fastboot cannot see devices (seem to work though)
recovery is not loading
I can only assume that even though fastboot seems to flashing device, blue load bar appears on tablet and reboot-bootloader commands works, it is not actually flashing the device?
thanks
Click to expand...
Click to collapse
First off, awesome report. Far more than I needed but I won't have to ask you another question along the way from now on.
You are on the jellybean bootloader. You should not even be flashing CWM while on that because that is how so many people hard brick their devices.
Can you please try downloading the custom TWRP I have in the following link that I have installed myself and made for the jellybean bootloader so I know this is where we are both at. The zip file has a bat file and you just run it and follow onscreen instructions.
http://forum.xda-developers.com/showpost.php?p=26595675&postcount=2
You want Hairybean TWRP Updater (normal).
Please do not try to install CWM at any point from now on.
flumpster said:
First off, awesome report. Far more than I needed but I won't have to ask you another question along the way from now on.
You are on the jellybean bootloader. You should not even be flashing CWM while on that because that is how so many people hard brick their devices.
Can you please try downloading the custom TWRP I have in the following link that I have installed myself and made for the jellybean bootloader so I know this is where we are both at. The zip file has a bat file and you just run it and follow onscreen instructions.
http://forum.xda-developers.com/showpost.php?p=26595675&postcount=2
You want Hairybean TWRP Updater (normal).
Please do not try to install CWM at any point from now on.
Click to expand...
Click to collapse
Thanks, will give it a try.
Must have done something as cannot get adb to find device when in fastboot now?
Tried rebooting workstation and tablet a few times, but no joy
and your bat file did not find device either?
carperman said:
Must have done something as cannot get adb to find device when in fastboot now?
Tried rebooting workstation and tablet a few times, but no joy
and your bat file did not find device either?
Click to expand...
Click to collapse
adb does not work in fastboot. Only the fastboot command does. The only places you can use adb is either while in the OS or while in recovery.
The .bat file would have tried to run a fastboot flash command.
Here is odd thing though, even though adb devices shows nothing and the .bat can't find connection the command fastboot reboot-bootloader works?
Note the error i get with .bat is
./HairyBean TWRP Recovery Flasher.bat: line 1: @echo: command not found
************************************************
HairyBean TWRP Jelly Bean Recovery Flasher
: command not foundcovery Flasher.bat: line 4: echo.
1. Turn OFF the device
./HairyBean TWRP Recovery Flasher.bat: line 6: syntax error near unexpected token `('
'/HairyBean TWRP Recovery Flasher.bat: line 6: `echo 2. Turn ON the device (hold power + vol down)
hamlet:HairyBean TWRP Updater 2.4.1.0 (normal) michael$ ./HairyBean\ TWRP\ Recovery\ Flasher.bat
./HairyBean TWRP Recovery Flasher.bat: line 1: @echo: command not found
************************************************
HairyBean TWRP Jelly Bean Recovery Flasher
: command not foundcovery Flasher.bat: line 4: echo.
1. Turn OFF the device
./HairyBean TWRP Recovery Flasher.bat: line 6: syntax error near unexpected token `('
'/HairyBean TWRP Recovery Flasher.bat: line 6: `echo 2. Turn ON the device (hold power + vol down)
hamlet:HairyBean TWRP Updater 2.4.1.0 (normal)
Just noticed that fastboot now find device though
fastboot devices
015d0787bf2fee07 fastboot
thanks
carperman said:
Here is odd thing though, even though adb devices shows nothing and the .bat can't find connection the command fastboot reboot-bootloader works?
Note the error i get with .bat is
./HairyBean TWRP Recovery Flasher.bat: line 1: @echo: command not found
************************************************
HairyBean TWRP Jelly Bean Recovery Flasher
: command not foundcovery Flasher.bat: line 4: echo.
1. Turn OFF the device
./HairyBean TWRP Recovery Flasher.bat: line 6: syntax error near unexpected token `('
'/HairyBean TWRP Recovery Flasher.bat: line 6: `echo 2. Turn ON the device (hold power + vol down)
hamlet:HairyBean TWRP Updater 2.4.1.0 (normal) michael$ ./HairyBean\ TWRP\ Recovery\ Flasher.bat
./HairyBean TWRP Recovery Flasher.bat: line 1: @echo: command not found
************************************************
HairyBean TWRP Jelly Bean Recovery Flasher
: command not foundcovery Flasher.bat: line 4: echo.
1. Turn OFF the device
./HairyBean TWRP Recovery Flasher.bat: line 6: syntax error near unexpected token `('
'/HairyBean TWRP Recovery Flasher.bat: line 6: `echo 2. Turn ON the device (hold power + vol down)
hamlet:HairyBean TWRP Updater 2.4.1.0 (normal)
Just noticed that fastboot now find device though
fastboot devices
015d0787bf2fee07 fastboot
thanks
Click to expand...
Click to collapse
I see a michael subfix in there. Are you running this zip from desktop or a link? Can you please try extracting the zip to a physical drive (e.g. make a folder on d: and call it wookie then extract the zip in it.
I have seen before this script failing on desktop.
edit... I have just looked back at your earlier outputs. Are you in linux because I presumed you was on windows when I started? The .bat file is for windows and it will probably not even work in linux because of the links.
ok sorted, checked the .bat and is for windows i am on OSX so did
fastboot -i 0x0B05 flash recovery fastboot/recoveryTWRP.blob
and it works
great many thanks, now to try your custom rom
carperman said:
ok sorted, checked the .bat and is for windows i am on OSX so did
fastboot -i 0x0B05 flash recovery fastboot/recoveryTWRP.blob
and it works
great many thanks, now to try your custom rom
Click to expand...
Click to collapse
Cool, glad you got it sorted.
Just know that you don't need to root first. Root is built into the roms and is not needed to flash.
Also please never try CWM again... From now on if you grab the official TWRP as needed make sure you get the JB version.
gl mate.
Awesome man this worked fine for me, had the same problem I guess koush needs to do his homework on the devices, or I do one..

[SOLVED] Flash recovery RELOCKED S-OFF LATEST OTA (FAILED (remote: not allowed)

Try this at your own risk. I do not take any responsibility, read on if you accept the risks.
I have discovered a working solution for people that have S-OFF RELOCKED and took the latest/last OTA update but cant flash a recovery via fastboot and cant re-unlock.
When i tried the following in fastboot
fastboot flash recovery recovery.img (place your favorite recovery into platform-tools folder)
< waiting for device >
sending 'recovery' (8758 KB)...
OKAY [ 1.018s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.049s
It errors out by using TWRP and CWM FAILED (remote: not allowed)
INSTRUCTIONS:
download the attached recovery.zip and place it into platform-tools (TWRP recovery)
fastboot oem rebootRUU
---wait for black HTC logo--
fastboot flash zip recovery.zip
--it will show a progress bar on your phone, and finished in the CMD window--
fastboot reboot bootloader
select recovery
profit
Can someone confirm that flashing recovery works with the method above. Also post what version software you are running. Someone with S-ON LOCKED please try this, possible new way to flash ROMS without S-OFF/unlock?
Awesome
I know it's been a while since you posted this, but THANK YOU. Worked a charm on my S-OFF Relocked 3.06. I even modified the zip file, removed the older version of TWRP, inserted a new version (renamed as recovery.img) and now have the most recent TWRP.
Droidel said:
Try this at your own risk. I do not take any responsibility, read on if you accept the risks.
I have discovered a working solution for people that have S-OFF RELOCKED and took the latest/last OTA update but cant flash a recovery via fastboot and cant re-unlock.
When i tried the following in fastboot
fastboot flash recovery recovery.img (place your favorite recovery into platform-tools folder)
< waiting for device >
sending 'recovery' (8758 KB)...
OKAY [ 1.018s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.049s
It errors out by using TWRP and CWM FAILED (remote: not allowed)
INSTRUCTIONS:
download the attached recovery.zip and place it into platform-tools (TWRP recovery)
fastboot oem rebootRUU
---wait for black HTC logo--
fastboot flash zip recovery.zip
--it will show a progress bar on your phone, and finished in the CMD window--
fastboot reboot bootloader
select recovery
profit
Can someone confirm that flashing recovery works with the method above. Also post what version software you are running. Someone with S-ON LOCKED please try this, possible new way to flash ROMS without S-OFF/unlock?
Click to expand...
Click to collapse
not working on my htc droid dna firmware version 4.09.605.5
Droidel said:
Try this at your own risk. I do not take any responsibility, read on if you accept the risks.
I have discovered a working solution for people that have S-OFF RELOCKED and took the latest/last OTA update but cant flash a recovery via fastboot and cant re-unlock.
When i tried the following in fastboot
fastboot flash recovery recovery.img (place your favorite recovery into platform-tools folder)
< waiting for device >
sending 'recovery' (8758 KB)...
OKAY [ 1.018s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.049s
It errors out by using TWRP and CWM FAILED (remote: not allowed)
INSTRUCTIONS:
download the attached recovery.zip and place it into platform-tools (TWRP recovery)
fastboot oem rebootRUU
---wait for black HTC logo--
fastboot flash zip recovery.zip
--it will show a progress bar on your phone, and finished in the CMD window--
fastboot reboot bootloader
select recovery
profit
Can someone confirm that flashing recovery works with the method above. Also post what version software you are running. Someone with S-ON LOCKED please try this, possible new way to flash ROMS without S-OFF/unlock?
Click to expand...
Click to collapse
Thank you thank you thank you so much.
luis181193 said:
Thank you thank you thank you so much.
Click to expand...
Click to collapse
aminebigboss said:
not working on my htc droid dna firmware version 4.09.605.5
Click to expand...
Click to collapse
Mine work!!
htc droid dna firmware version 4.09.605.5

[Q] cant flash TWRP h830

this is the first time i have owned an LG phone. I have the bootloaded unlocked and usb debugging enabled. I have read just about every guide i could find but i still cant manage to flash twrp.
i am trying to flash the latest twrp-3.2.1-0-h830.img
i am showing build number NRD90U and software version H83020a.
i am getting this error message trying to flash thru either adb or minimal adb and fastboot programs:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp.img
target reported max download size of 536870912 bytes
sending 'recovery' (18700 KB)...
OKAY [ 0.511s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.531s
any suggestions would be appreciated. thanks
https://forum.xda-developers.com/tmobile-lg-g5/development/root-h830-20a-nougat-lg-g5-hard-t3542496 this should show you how
tensux said:
this is the first time i have owned an LG phone. I have the bootloaded unlocked and usb debugging enabled. I have read just about every guide i could find but i still cant manage to flash twrp.
i am trying to flash the latest twrp-3.2.1-0-h830.img
i am showing build number NRD90U and software version H83020a.
i am getting this error message trying to flash thru either adb or minimal adb and fastboot programs:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp.img
target reported max download size of 536870912 bytes
sending 'recovery' (18700 KB)...
OKAY [ 0.511s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.531s
any suggestions would be appreciated. thanks
Click to expand...
Click to collapse
If you already have TWRP before just use the app.
If its the first time you flash twrp using the Recowvery method, make sure you have a copy of the recovery.img on your internal memory. :good:
rflores said:
https://forum.xda-developers.com/tmobile-lg-g5/development/root-h830-20a-nougat-lg-g5-hard-t3542496 this should show you how
Click to expand...
Click to collapse
cheeze.keyk said:
If you already have TWRP before just use the app.
If its the first time you flash twrp using the Recowvery method, make sure you have a copy of the recovery.img on your internal memory. :good:
Click to expand...
Click to collapse
Hi thanks for the replies.
I finally got it to work after a couple days of a soft brick at lg firmware update. i used Easyrecowery and and for some reason needled to toglle between file transfer and phot transfer while getting stuck while the scripts were processing
https://forum.xda-developers.com/tmobile-lg-g5/how-to/guide-root-twrp-lg-g5-using-t3580264
now to flash lineageos

Bricked my Mate 10 lite (RNE-L21) with wrong twrp

I am new here and this was my first time actually trying any of this. I have my bootloader code, if that helps.
Phone turns on to erecovery mode if powered on normally. Running erecovery downloaded and installed RNE-L21 8.0.0.355(C185). It then asked me to Factory reset, after which it booted back in to erecovery. I can put phone in FASTBOOT&RESCUE MODE by plugging it in to PC and holding power + vol. down.
About Phone
-code
DC-unlocker:
manufacturer - Huawei phones
model - Huawei phone in fastboot mode
Found Phone : RNE-L21
Model : Huawei phone in fastboot mode
IMEI : 868859036054492
Serial NR. : FFY5T18224032295
Firmware : RNE-L21 8.0.0.355(C185
IMEI1:868859036074508
FB LockState: LOCKED
I wanted to downgrade from Oreo to Nougat.
To unlock bootloader, I used Potatonv:
GitHub - mashed-potatoes/PotatoNV: Unlock bootloader of Huawei devices on Kirin 960/95х/65x/620
Unlock bootloader of Huawei devices on Kirin 960/95х/65x/620 - GitHub - mashed-potatoes/PotatoNV: Unlock bootloader of Huawei devices on Kirin 960/95х/65x/620
github.com
I installed the TWRP in this post:
TWRP For Mate 10 lite 8.0 Oreo Version For RNE-L21C185
Here is twrp for HUAWEI MATE 10 LITE. Who want? Comment Here. :p
forum.xda-developers.com
I booted in to TWRP with
-code
adb reboot recovery
I made a backup using TWRP but I lost it and couldn't make another one because of some error in TWRP.
I then installed magisk .zip file through TWRP.
The phone would boot in TWRP no matter which option I chose in the Reboot menu of TWRP. Being really impatient, I decided to flash another version of TWRP on recovery partition, with SD card, through TWRP itself. I got this 2nd TWRP from:
How to Install TWRP Recovery and Root Huawei Mate 10 Lite
In this article, we will guide you on how to root Huawei Mate 10 Lite and Install TWRP Recovery.
clickitornot.com
The new TWRP doesn't work and phone does not show bootloader unlocked warning anymore. Upon rebooting after new TWRP, phone showed this error first few times.
I'm not really sure what to do but I figured I'd run some commands that might help someone figure out what I should do.
fastbootoem get-product-model:
(bootloader) RNE-L21
OKAY [ 0.025s]
finished. total time: 0.026s
fastboot getvar vendorcountry:
vendorcountry: hw/meafnaf
finished. total time: 0.025s
fastboot oem get-build-number:
(bootloader) :RNE-L21 8.0.0.355(C185)
OKAY [ 0.026s]
finished. total time: 0.027s
fastboot getvar rescue_enter_recovery:
getvar:rescue_enter_recovery FAILED (remote: FAIL:need all image flashed!)
finished. total time: 0.063s
fastboot oem oeminforead-SYSTEM_VERSION:
(bootloader) :RNE-L21 8.0.0.348(C185CUSTC185D1)
OKAY [ 0.031s]
finished. total time: 0.031s
I believe the rom for my phone is
RNE-L21 8.0.0.348(C185CUSTC185D1)​I have downloaded it from https://gsmfreehelperteam.blogspot.com/2020/04/rne-l21-800348c185custc185d1-file-by.html but I really don't know what to do with it and I don't want to mess it up any further. Sorry for the long read, any help would be great.
brokenpotato said:
Upon rebooting after new TWRP, phone showed this error first few times.
Click to expand...
Click to collapse
- Flash stock Recovery from fastboot using command
fastboot flash recovery_ramdisk (....).img
- enter stock recovery and do factory reset
- Running OREO use this TWRP
brokenpotato said:
I wanted to downgrade from Oreo to Nougat
Click to expand...
Click to collapse
You can downgrade to Nougat using two methods :
1. Via HiSuite
2. Using HuRupdater tool & TWRP. Unfortunately, this method needs Firmware Finder and Huawei servers are offline. So via HiSuite only.
Don't try downgrade to the lower android version via dload method flashing service ROM (aka full stock firmware), it may brick your phone.
-Alf- said:
- Flash stock Recovery from fastboot using command
fastboot flash recovery_ramdisk (....).img
- enter stock recovery and do factory reset
- Running OREO use this TWRP
You can downgrade to Nougat using two methods :
1. Via HiSuite
2. Using HuRupdater tool & TWRP. Unfortunately, this method needs Firmware Finder and Huawei servers are offline. So via HiSuite only.
Don't try downgrade to the lower android version via dload method flashing service ROM (aka full stock firmware), it may brick your phone.
Click to expand...
Click to collapse
"fastboot flash recovery RECOVERY_RAMDISK330.img" gives:
target reported max download size of 471859200 bytes
sending 'recovery' (32768 KB)...
OKAY [ 1.055s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 1.067s
brokenpotato said:
Command not allowed
Click to expand...
Click to collapse
= Locked bootloader or FRP lock
-Alf- said:
= Locked bootloader or FRP lock
Click to expand...
Click to collapse
IT does say "FRP Unlock" in red on fastboot&rescue screen. Should i try fastboot oem unlock?
brokenpotato said:
Should i try fastboot oem unlock?
Click to expand...
Click to collapse
Why not?
Fastboot oem unlock *************** worked, the phone booted up in to android and is working normally. Thank you so much!!
brokenpotato said:
Fastboot oem unlock *************** worked, the phone booted up in to android and is working normally. Thank you so much!!
Click to expand...
Click to collapse
No problem.
-Alf- said:
- Flash stock Recovery from fastboot using command
fastboot flash recovery_ramdisk (....).img
- enter stock recovery and do factory reset
- Running OREO use this TWRP
You can downgrade to Nougat using two methods :
1. Via HiSuite
2. Using HuRupdater tool & TWRP. Unfortunately, this method needs Firmware Finder and Huawei servers are offline. So via HiSuite only.
Don't try downgrade to the lower android version via dload method flashing service ROM (aka full stock firmware), it may brick your phone.
Click to expand...
Click to collapse
When trying to flash the TWRP, I get:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery TWRP-oreo-smart.img
target reported max download size of 471859200 bytes
sending 'recovery' (24790 KB)...
OKAY [ 0.794s]
writing 'recovery'...
FAILED (remote: partition length get error)
finished. total time: 0.809s
brokenpotato said:
fastboot flash recovery TWRP-oreo-smart.img
Click to expand...
Click to collapse
Read carefully.
brokenpotato said:
When trying to flash the TWRP, I get:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery TWRP-oreo-smart.img
target reported max download size of 471859200 bytes
sending 'recovery' (24790 KB)...
OKAY [ 0.794s]
writing 'recovery'...
FAILED (remote: partition length get error)
finished. total time: 0.809s
Click to expand...
Click to collapse
Just realized I had to flash twrp on recovery_ramdisk and not on recovery. It works like a charm

Error on fastboot boot/flash TWRP

Hi everyone!
I want to install TWRP on a P20 Lite with the main goal to install LOS16 and possible other custom ROMs. Therefore I was following the official guide on LOS.
However when I try to boot/flash the TWRP image-file with fastboot i receive the following error:
Problem
Code:
$>fastboot flash recovery twrp.img
Sending 'recovery' (14946 KB) OKAY [ 0.396s]
Writing 'recovery' FAILED (remote: 'partition length get error')
fastboot: error: Command failed
$>fastboot boot twrp.img
Sending 'boot.img' (14946 KB) OKAY [ 0.376s]
Booting FAILED (remote: 'invalid command')
fastboot: error: Command failed
Error is shown in admin command line as well.
Furthermore I get the following error which let me think that it is more of a fastboot problem.
Code:
$>fastboot getvar version
getvar:version FAILED (remote: 'invalid command')
$>fastboot oem device-info
FAILED (remote: 'invalid command')
fastboot: error: Command failed
Specs
Phone: Huawei P20 Lite ANE-LX1
Build:9.1.0.377(C432E7R1P7)
EMUI-Version 9.1.0
Bootloader unlocked - PHONE Unlocked, FRP unlocked (via PotatoNV method with same adb/fastboot installation).
Adb:
Android Debug Bridge version 1.0.41
Version 30.0.5-6877874
Info
Same error with adb/fastboot from two different PCs (Win10). Adb and fastboot seem to work in general. For example both show the device in List of devices attached and i can reboot and boot via adb and fastboot.
As I understand this post it is not possible to flash twrp directly on android 9.
However I tried the twrp file linked in the mentioned post and several images linked in this forum (this, this) + the one from twrp-anne and got the same error fastboot: error: Command failed on all.
Does anybody know or has a hint what might be the problem? Any help appreciated.
Best regards
I had the same issue.
You have to use the command: fastboot flash recovery_ramdisk twrp.img
yellowzebra said:
As I understand this post it is not possible to flash twrp directly on android 9.
Click to expand...
Click to collapse
Hello, please read carefully :
-Alf- said:
flash TWRP , run command
fastboot flash recovery_ramdisk (TWRP's_name).img
Click to expand...
Click to collapse
-Alf- said:
Since A8 and above you can not install TWRP over eRecovery from fastboot, only from TWRP:
Click to expand...
Click to collapse
- eRecovery and Recovery are two different things .
That worked!
Thank you very much. Both of you for the fast answer
I am currently researching before asking more noob questions. Have some thoughts. Especially on difference between eRecovery and Recovery and why commands as fastboot oem device info where not working before the recovery_ramdisk. Might return later.
Thx!

Categories

Resources