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
Related
Current state:
Hboot 1.50 Unlocked S-ON
Boots into stock ROM
I was stuck in a boot loop and couldn't get into recovery so I relocked my phone and ran RUU_Shooter_S_Sprint_WWE_2.17.651.5_Radio_1.06.00.1216_NV_NV_spcs_1.42_release_233304_signed.
Phone booted correctly after the RRU and was able to unlock the device. I went back and followed the instructions HERE to flash TWRP recovery. The exact same way that I had originally flashed.
When I was trying to Flash my recovery I received this:
Code:
C:\Android>fastboot flash recovery recovery.img
sending 'recovery' (5068 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 0.011s
1. Am I screwed?
2. What can I do to prevent this in the future?
3. How do I fix it?
franciumgoesboom said:
Current state:
Hboot 1.50 Unlocked S-ON
Boots into stock ROM
I was stuck in a boot loop and couldn't get into recovery so I relocked my phone and ran RUU_Shooter_S_Sprint_WWE_2.17.651.5_Radio_1.06.00.1216_NV_NV_spcs_1.42_release_233304_signed.
Phone booted correctly after the RRU and was able to unlock the device. I went back and followed the instructions HERE to flash TWRP recovery. The exact same way that I had originally flashed.
When I was trying to Flash my recovery I received this:
Code:
C:\Android>fastboot flash recovery recovery.img
sending 'recovery' (5068 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 0.011s
1. Am I screwed?
2. What can I do to prevent this in the future?
3. How do I fix it?
Click to expand...
Click to collapse
1. No.
2. Nothing, it happens sometimes.
3. Maybe a corrupt download? Try again with a new copy of recovery.
If that doesn't work, try a different recovery.
I receive that error no matter which recovery I try.
The first file I tried in the OP was the same file that I had used when I originally started flashing. I just tried with twrp 2.0 and the same thing happens.
Code:
C:\Android>fastboot flash recovery twrp-shooter-2.0.0RC0.img
sending 'recovery' (5122 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 0.012s
Maybe it is time to start looking at the downgrade process.
Hello!
I installed Munjeni's special hboot partition (to increase usable space) and wanted to update the phone back to stock (to take back to att).
The RUU utility failed with code of 152.
The partition failed.
Now the phone is "stuck" at the black HTC screen with four warning triangles in each corner.
Any ideas?
I can fastboot and issue some commands...
I am s-on, hboot 1.02.
Thanks in advance!
DanGeorges said:
Hello!
I installed Munjeni's special hboot partition (to increase usable space) and wanted to update the phone back to stock (to take back to att).
The RUU utility failed with code of 152.
The partition failed.
Now the phone is "stuck" at the black HTC screen with four warning triangles in each corner.
Any ideas?
I can fastboot and issue some commands...
I am s-on, hboot 1.02.
Thanks in advance!
Click to expand...
Click to collapse
If the bootloader is accessible, you can try grabbing the rom.zip out of the RUU (run it & let it load, then search in Windows' temporary folder for "rom.zip". If not there's probably a download somewhere), and rename it to "LIBEIMG.zip" on the root of the SD card.
Then boot into the bootloader (vol down) and it should pick it up and start flashing (might be a confirmation before it does)
Edit: Well I looked at the title again... does this mean its not accessible?
It should be if fastboot is, but I've never had the bad triangles so not completely sure..
If not, alternate option that may work: extract the hboot image from rom.zip and flash it with fastboot (if its allowed)
This is the RUU zip: http://www.mediafire.com/?tay1j415ymvukh5
drumist said:
This is the RUU zip: http://www.mediafire.com/?tay1j415ymvukh5
Click to expand...
Click to collapse
Thank you for the link. I'm downloading it now.
I can fastboot, but I'm S-on (from one of my flashes).
What's the fastboot command for flashing the hboot? Will this even let me?
I'll give this a try. Thanks again!
When I try to fastboot flash a recovery, here's what I get:
C:\Mobile\Android\Fastboot and ADB Tool>fastboot flash recovery recovery.img
sending 'recovery' (3716 KB)... OKAY [ 0.875s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 1.578s
C:\Mobile\Android\Fastboot and ADB Tool>
For hboot - does anyone have an idea which hboot I can try flashing?
WinSuk said:
If the bootloader is accessible, you can try grabbing the rom.zip out of the RUU (run it & let it load, then search in Windows' temporary folder for "rom.zip". If not there's probably a download somewhere), and rename it to "LIBEIMG.zip" on the root of the SD card.
Then boot into the bootloader (vol down) and it should pick it up and start flashing (might be a confirmation before it does)
Edit: Well I looked at the title again... does this mean its not accessible?
It should be if fastboot is, but I've never had the bad triangles so not completely sure..
If not, alternate option that may work: extract the hboot image from rom.zip and flash it with fastboot (if its allowed)
Click to expand...
Click to collapse
I'll try the hboot image and see what happens.
What's the fastboot command?
I tried:
fastboot flash hboot
and
fastboot flash boot
Both gave me an invalid signature:
C:\>fastboot flash hboot hboot_liberty_7227_1.02.0000_101104.nb0
sending 'hboot' (512 KB)... OKAY [ 0.234s]
writing 'hboot'... INFOsignature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 0.328s
C:\>fastboot flash boot hboot_liberty_7227_1.02.0000_101104.nb0
sending 'boot' (512 KB)... OKAY [ 0.234s]
writing 'boot'... INFOsignature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 0.328s
Hi
I want Going back to stock for official Jelly Bean update and I followed this tutorial:
http://forum.xda-developers.com/showthread.php?p=36138808 # post36138808
I try to flash the recovery with the attached file: http://forum.xda-developers.com/showpost.php?p=35031493&postcount=25
fastboot flash recovery recovery.img
sending 'recovery' (4272 KB)...
OKAY [ 1.813s]
writing 'recovery'...
OKAY [ 1.609s]
finished. total time: 3.422s
fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.531s]
finished. total time: 0.531s
fastboot erase cache
erasing 'cache'...
OKAY [ 0.266s]
finished. total time: 0.266s
When I returned to the fastboot and I select "recovery" the phone gets stuck on the following picture: http://s13.postimage.org/6hy5sfs2f/IMG_20120530_193934_1.jpg (photo found on google on another device)
This is my configuration :
Desire X
--> Bootloader unlocked
PROTO PVT SHIP S-ON RL
HBOOT-1.24.0000
RADIO-1.12.40.03
eMMC-boot
Oct 30 2012,20:09:09
Android : 4.0.4
HTC sense 4.1
N° 1.18.401.3
API HTC SDK : 4.24
HTCExtension_403_1_GA_24
Kernel :
3.0.21-g6c11713
[email protected]#1
Radio : 10.21.40.06U_1.12.40.03
Build : 1.18.401.3 CL128557 release-keys
Anyone know why my recovery doesn't work ?
Have you tried another another links for recovery? or the one from hansoons kit?
you could have just bad luck and flash buggy one
btw your question is wrong, from what you said, recovery was flashed in ok way, so there must be something wrong with recovery you flashed
Eliastux said:
I want Going back to stock for official Jelly Bean update
I try to flash the recovery with the attached file: http://forum.xda-developers.com/showpost.php?p=35031493&postcount=25
When I returned to the fastboot and I select "recovery" the phone gets stuck on the following picture: http://s13.postimage.org/6hy5sfs2f/IMG_20120530_193934_1.jpg (photo found on google on another device)
Anyone know why my recovery can not be flashed?
Click to expand...
Click to collapse
Your recovery is flashed fine.
But why do you need to go to fastboot and recovery again when your aim is getting the JB update ?
Thank you for this quick answer !
mindlesSheep said:
Have you tried another another links for recovery? or the one from hansoons kit?
you could have just bad luck and flash buggy one
Click to expand...
Click to collapse
Okey I have tried this one :
http://forum.xda-developers.com/attachment.php?attachmentid=1618686&d=1357387592
fastboot.exe flash recovery stock_recovery.img
sending 'recovery' (4272 KB)...
OKAY [ 1.297s]
writing 'recovery'...
OKAY [ 1.641s]
finished. total time: 2.938s
fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.250s]
finished. total time: 0.250s
fastboot erase cache
< waiting for device >
erasing 'cache'...
OKAY [ 0.648s]
finished. total time: 0.650s
--> When I returned to the fastboot and I select "recovery" and now I see the same picture : http://s13.postimage.org/6hy5sfs2f/I...0_193934_1.jpg
And after 5 sec the phone reboot : Is it normal ?
mindlesSheep said:
btw your question is wrong, from what you said, recovery was flashed in ok way, so there must be something wrong with recovery you flashed
Click to expand...
Click to collapse
Ok I will edit my first post
mindlesSheep said:
or the one from hansoons kit?
Click to expand...
Click to collapse
Ok I try this immediately
ckpv5 said:
Your recovery is flashed fine.
But why do you need to go to fastboot and recovery again when your aim is getting the JB update ?
Click to expand...
Click to collapse
When I want to apply the Jelly Bean 2.20.401.5 update the phone reboot on the buggy recovery and the phone gets stuck on the same picture
ckpv5 said:
Your recovery is flashed fine.
But why do you need to go to fastboot and recovery again when your aim is getting the JB update ?
Click to expand...
Click to collapse
I thought I had to go back to stock recovery for the update of Jelly Bean I'm wrong?
Am I also wrong about the fact that we can apply the update without relock the bootloader?
Eliastux said:
I thought I had to go back to stock recovery for the update of Jelly Bean I'm wrong?
Am I also wrong about the fact that we can apply the update without relock the bootloader?
Click to expand...
Click to collapse
1. Must have stock recovery installed
2. Must have a complete stock ROM (nothing is deleted)
3. Not necessary to flash a stock boot.img but it is advisable to have one
4. Not necessary to relock bootloader
5. If no.4 still brings problem then relock the bootloader but you will lose all data when unlocking again.
Eliastux said:
Okey I have tried this one :
http://forum.xda-developers.com/attachment.php?attachmentid=1618686&d=1357387592
fastboot.exe flash recovery stock_recovery.img
sending 'recovery' (4272 KB)...
OKAY [ 1.297s]
writing 'recovery'...
OKAY [ 1.641s]
finished. total time: 2.938s
fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.250s]
finished. total time: 0.250s
fastboot erase cache
< waiting for device >
erasing 'cache'...
OKAY [ 0.648s]
finished. total time: 0.650s
--> When I returned to the fastboot and I select "recovery" and now I see the same picture : http://s13.postimage.org/6hy5sfs2f/I...0_193934_1.jpg
And after 5 sec the phone reboot : Is it normal ?
Click to expand...
Click to collapse
--> When I apply the update with this recovery, the phone boot on the recovery and I see the same picture and after 5 sec the phone shut down (no picture on the screen)... and the only way to boot after this is to remove/put the battery.
ckpv5 said:
1. Must have stock recovery installed
2. Must have a complete stock ROM (nothing is deleted)
3. Not necessary to flash a stock boot.img but it is advisable to have one
4. Not necessary to relock bootloader
5. If no.4 still brings problem then relock the bootloader but you will lose all data when unlocking again.
Click to expand...
Click to collapse
1 --> NOK
2 --> OK
3 --> I have to install first a stock recovery if I want to flash a stock boot.img...
4,5 --> OK not necessary
Thanks for your reply
Eliastux said:
or the one from hansoons kit?
Ok I try this immediately
Click to expand...
Click to collapse
I've tried to install TWRP 2.4.3.0 from the HTC Desire X All-In-One Kit (Hasoons kit) :
(I made it with command line because v2.1 of this tool is a little buggy :
astboot.exe flash recovery TWRP.img
< waiting for device >
sending 'recovery' (6158 KB)...
OKAY [ 5.680s]
writing 'recovery'...
OKAY [ 6.375s]
finished. total time: 12.055s
fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.563s]
finished. total time: 0.563s
fastboot erase cache
< waiting for device >
erasing 'cache'...
OKAY [ 1.834s]
finished. total time: 1.874s
--> When I returned to the fastboot and I select "recovery" and now I see the same picture !! ( the phone gets stuck ! )
Is the recovery of my phone bricked ?
Ok guys I found the solution ( after 4hours of research ! ) flashing my phone with this RUU : RUU_PROTO_U_ICS_40A_HTC_Europe_1.18.401.1_Radio_10.21.40.06U_1.10.40.23_release_295191_signed.exe
Unfortunately (grr) I was not able to use the RUU normally (maybe because my recovery was buggy, I had a signature error) and I follow theses steps to install it :
1) fastboot erase cache
2) fastboot oem rebootRUU
3) fastboot flash zip rom.zip --> the rom.zip was extracted from the RUU.exe
4) fastboot reboot-bootloader
5) fastboot reboot
After that I could make two consecutive updates ( 1.18.401.3 and Jelly Bean update )
I hope it can help others who have the same problem :good:
Hey folks,
I'm trying to install a recovery image using fastboot, as per the directions presented here:
http://wiki.cyanogenmod.org/w/Install_CM_for_fireball
When I try flashing the recovery, I get the following error message:
Code:
sudo fastboot flash recovery recovery-clockwork-6.0.4.6-fireball.img
sending 'recovery' (7784 KB)...
OKAY [ 1.117s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.149s
I was able to obtain S-OFF following the directions presented in this thread:
http://forum.xda-developers.com/showthread.php?t=2664460
but I am now currently in "relocked" state because I followed step 5 and tried running DirtyRacun.
Phone: HTC incredible 4g lte.
hboot: 1.15.0000
radio: 1.53.06.0919
OpenDSP-v29.1.0.45.0622
Thanks in advance!
in other news ...
My phone is in an unusable state. I still have access to the bootloader, and when it's plugged into my computer, I have access to it through adb, but otherwise, I can't send or receive phone calls from it.
stringedonbass said:
My phone is in an unusable state. I still have access to the bootloader, and when it's plugged into my computer, I have access to it through adb, but otherwise, I can't send or receive phone calls from it.
Click to expand...
Click to collapse
Apparently shutting down and pulling the battery "fixes" that problem.
Step 5 was not to run dirty racoon it was to flash the engineering hboot from the DirtyRacun webpage, but with S-off you should still be able to flash the hboot and recovery.
I find this page useful when I am working in ADB to keep the ideas fresh. http://forum.xda-developers.com/showthread.php?t=2141817
stringedonbass said:
Hey folks,
I'm trying to install a recovery image using fastboot, as per the directions presented here:
http://wiki.cyanogenmod.org/w/Install_CM_for_fireball
When I try flashing the recovery, I get the following error message:
Code:
sudo fastboot flash recovery recovery-clockwork-6.0.4.6-fireball.img
sending 'recovery' (7784 KB)...
OKAY [ 1.117s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.149s
I was able to obtain S-OFF following the directions presented in this thread:
http://forum.xda-developers.com/showthread.php?t=2664460
but I am now currently in "relocked" state because I followed step 5 and tried running DirtyRacun.
Phone: HTC incredible 4g lte.
hboot: 1.15.0000
radio: 1.53.06.0919
OpenDSP-v29.1.0.45.0622
Thanks in advance!
Click to expand...
Click to collapse
Re: adb guide
wmuflyer said:
Step 5 was not to run dirty racoon it was to flash the engineering hboot from the DirtyRacun webpage, but with S-off you should still be able to flash the hboot and recovery.
I find this page useful when I am working in ADB to keep the ideas fresh. http://forum.xda-developers.com/showthread.php?t=2141817
Click to expand...
Click to collapse
That's a nice guide on the Android Debug Bridge (abd). As a side note, I was pleased to find that fastboot and adb can be found in Ubuntu's repositories.
Update: flashed DirtyRacun's HBOOT
My phone now says
-- DirtyRacun --
at the top of the bootloader. No need to "unlocking" the phone because it was already in S-OFF state. After downloading the HBOOT file from unlimited's fireball website, I typed these commands, also available from their website:
Code:
sudo ./fastboot erase cache
sudo ./fastboot oem rebootRUU
sudo ./fastboot flash zip [file name]
sudo ./fastboot reboot
Happily rooted with CyanogenMOD installed
I'm happily rooted and have CyanogenMOD up and running.
After flashing the engineering hboot onto my phone using unlimited's directions, I was able to install ClockworkMod Recovery for fireball following the directions posted on their website.
Code:
sudo fastboot flash recovery recovery-clockwork-6.0.4.6-fireball.img
sending 'recovery' (7784 KB)...
OKAY [ 1.141s]
writing 'recovery'...
OKAY [ 2.129s]
finished. total time: 3.271s
I then was able to install CyanogenMod from recovery like "clockwork". Of course, "abd reboot-bootloader" is much faster than the crazy key combinations they ask you do to. When asked to install from sdcard, there were two locations to look at.
Cheers everyone! :victory:
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