Hey guys, I can't seem to flash a kernel via fastboot.
Here's my info
Phone : Xperia Mini Pro
Root : Rooted
Bootloader : Unlocked
Android Version : 2.3.4 (but have tried with 4.0.4 too)
USB debugging on
MSC mode activated
Unknown souces : checked
LOG :
17/012/2012 14:12:13 - INFO - FASTBOOT Output:
sending 'boot' (4926 KB)...
FAILED (remote: Unrecognized command, bork!)
finished. total time: 0.000s
I'm trying to install CM9, I extracted boot.img
fastboot detects device but fails when trying to flash
Any ideas please?
(if you need more info, more than welcome)
Try to redownload the kernel,Maybe that will work Or try to use Flashtool to flash the kernel
Sent from my Xperia Mini using XDA Premium
Singgih4050 said:
Try to redownload the kernel,Maybe that will work Or try to use Flashtool to flash the kernel
Sent from my Xperia Mini using XDA Premium
Click to expand...
Click to collapse
I've tried several different kernels and I've tried with flashtool and Command Prompt
Mikeboss71 said:
I've tried several different kernels and I've tried with flashtool and Command Prompt
Click to expand...
Click to collapse
Do you have tried to install other kernel?
Sent from my Xperia Mini using XDA Premium
Singgih4050 said:
Do you have tried to install other kernel?
Sent from my Xperia Mini using XDA Premium
Click to expand...
Click to collapse
yeah i've tried to flash different kernels but still the same problem :/
which method you are using?
Try with my tool' in my signature
Sent from my WT19a using xda app-developers app
Did you unlock your bootloader via sony or via testpoint method?
Have you checked *#*#7378423#*#* and then Service info > Configuration > Rooting Status. If Bootloader unlock allowed says Yes, it's another problem...
To all the ppl who replied before - Did you even read the log?
Mikeboss71 said:
17/012/2012 14:12:13 - INFO - FASTBOOT Output:
sending 'boot' (4926 KB)...
FAILED (remote: Unrecognized command, bork!)
finished. total time: 0.000s
Click to expand...
Click to collapse
"Unrecognized command"
You need to use the following command:
Code:
fastboot flash boot boot.img
or
Code:
fastboot -i 0x0fce flash boot boot.img
Someguyfromhell said:
To all the ppl who replied before - Did you even read the log?
"Unrecognized command"
You need to use the following command:
Code:
fastboot flash boot boot.img
or
Code:
fastboot -i 0x0fce flash boot boot.img
Click to expand...
Click to collapse
But normally it should have worked, cause with flashtool it should work. Doesn't flashtool do same command like
Code:
fastboot flash boot boot.img
?
Mikeboss71 said:
Hey guys, I can't seem to flash a kernel via fastboot.
Here's my info
Phone : Xperia Mini Pro
Root : Rooted
Bootloader : Unlocked
Android Version : 2.3.4 (but have tried with 4.0.4 too)
USB debugging on
MSC mode activated
Unknown souces : checked
LOG :
17/012/2012 14:12:13 - INFO - FASTBOOT Output:
sending 'boot' (4926 KB)...
FAILED (remote: Unrecognized command, bork!)
finished. total time: 0.000s
I'm trying to install CM9, I extracted boot.img
fastboot detects device but fails when trying to flash
Any ideas please?
(if you need more info, more than welcome)
Click to expand...
Click to collapse
I believe it is a problem with your controller manager kernel. This can occur because of a problem with the remote connections with the driver files. Try flashing your ROM STOCK then do root and then try to apply the kernel
Sorry guys I've been away for a while so I've kinda had to put this on the back burner. but I'm back now
@daydu19
I've tried both methods, Flashtool and through Command Prompt using
Code:
fastboot flash boot boot.img
&
Code:
fastboot -i 0x0fce flash boot boot.img
but no joy
EDIT: I can't unlock my phone with testpoint because of the new securities, my phone is "12W27" :/
@mihahn
I'm not quite sure how I unlocked it I tried several ways, testpoint & sony, the weird thing is that I didn't think that either of them worked but I'm able to flash FTF files with flashtool and also Flashtool says that my bootloader is already unlocked...
Code:
Loader : S1_Loader_Root_773f - Version : R4A066 / Bootloader status : ROOTED
And lastly
Have you checked *#*#7378423#*#* and then Service info > Configuration > Rooting Status. If Bootloader unlock allowed says Yes, it's another problem...
Click to expand...
Click to collapse
It says that it is allowed
@xdevilium
Thanks, I'll try this out and let you know if that helps
EDIT: Nope, doesn't work either
@eltonpestana
I've flashed my device multiple times back to stock to 2.3.4 and 4.0.4, they're FTF files that I found on here but that was the only way I managed to get my phone to work again, When I tried flashing the kernels through fastboot, it came up the errors I mentioned and by so Bricked my phone...
The one thing I haven't tried yet is to use Sony PC companion to "reset" my phone (mainly due to my painfully slow internet connection) but I'm not sure that will do much good seeing as it will restore it to 4.0.4 making it impossible to root and I'll end up having to flash the other FTF again.. no?
is it possible to download a custom kernel as a FTF file and then flash it rather than going through fastboot?
because I can flash the stock kernels (that are in the FTF files) that I got
Worst case scenario are there any good ICS ROMS that will work with the stock kernel?
Try flashing stock ftf and then it should get work done.
Sent from my WT19i using xda app-developers app
---------- Post added at 05:58 PM ---------- Previous post was at 05:51 PM ----------
Apparently not . But cm 7.2 works with stock kernel.
Sent from my WT19i using xda app-developers app
I've already tried :/
thanks, CM 7.2 is gingerbread though, ICS is nicer
anyone?
Heres the new log
C:\Users\Mike\Desktop\fastboot>fastboot devices
YT9001KGWM&ZLP fastboot
C:\Users\Mike\Desktop\fastboot>fastboot -i 0xfce flash boot boot.img
sending 'boot' (4926 KB)...
FAILED (remote: Unrecognized command, bork!)
finished. total time: 0.001s
C:\Users\Mike\Desktop\fastboot>fastboot -i 0xfce flash boot boot.img
sending 'boot' (4926 KB)...
(bootloader) USB download speed was 2505kB/s
OKAY [ 2.030s]
writing 'boot'...
FAILED (remote: Unrecognized command, bork!)
finished. total time: 2.032s
C:\Users\Mike\Desktop\fastboot>fastboot -i 0xfce flash boot boot.img
sending 'boot' (4926 KB)...
(bootloader) Flash of partition 'boot' requested
(bootloader) S1 partID 0x00000003, block 0x00000280-0x000002e3
(bootloader) Erase operation complete, 0 bad blocks encountered
(bootloader) Flashing...
(bootloader) Flash operation complete
FAILED (unknown status code)
finished. total time: 1.005s
mihahn said:
But normally it should have worked, cause with flashtool it should work. Doesn't flashtool do same command like
Code:
fastboot flash boot boot.img
?
Click to expand...
Click to collapse
I wonder can anyone help me with this? I recently unlocked my bootloader (with wotanserver.com - test point method) and have since been trying out new kernels.
Unfortunately, I've had some problems with Sirkay's Advanced Stock .587 Kernel when I flash it. http://forum.xda-developers.com/showthread.php?t=1544513
I followed his flashing with flashtool instructions (standard procedure). My phone appears to boot up as normal at first, (the kernel's preinstalled CWM recovery works too) but after the initial boot logo & brightening screen that indicates CWM is present - the screen then just goes black with white LED on (with screen backlight v. slightly on) and nothing else happens, i.e. the phone is well and truly stuck.
The end result is that I have to flash back to the kernel I was previously using. There's nothing in the Flashtool log to suggest any problem with the flashing either, and there's been no problem flashing any .img or .sin files until now - so I assume I have all the correct drivers etc.
Am I overlooking something obvious here? Would be very glad to someone's opinion, this is driving me nuts!
Device: ST18i (unlocked bootloader)
ROM version: Iced Bean 2.1 [.587] - Can be used with any kernel (according to the author)
Baseband version: .77
Related
Hello,
i used insecure boot and root trying to root my phone, which was a huge mistake as i noticed a few minutes later since i cant startup anymore and only get into bootloader.
Now I'm trying to flash my stock rom back.
My CID is VODAP102 and my Version is 3.14.161.27 so i downloaded the rom and tried "fastboot flash boot boot.img" the result is:
sending 'boot' <8192 KB>...
FAILED <data transfer failure <Unknown error>>
finished. total time: 0.158s
So well yeah, can anyone tell me why I get this error and how to fix it?
anyone?
push
so this is a rather rare problem it seems?
Ok try flashing rom using android download tool.
Sent from moon to earth........
Not working, which is probably no suprise since it works with the normal files.
I have an xperia ray (ST18i) and it is stuck on sony/sony ericsson logo forever. I already flashed many versions of stock roms (using flashtool) and nothing worked. If I flash an old rom (4.0.2.A.0.62) it will display sony ericsson and if I install a newer rom (4.1.B.0.587) or update vita pc companion/sus it will display the sony logo and hang there until the battery is removed or dead.
My device has a locked bootloader and is not rooted and I want to install a custom kernel/pre rooted kernel to install custom roms via CWM hoping it would solve my problem. So I unlocked my bootloader booted into fastmode and attempted to flash a pre rooted kernel but it says:
Flashing selected kernel
sending 'boot' (5760 KB)...
FAILED (remote: The Device must be rooted first)
finished. total time: 0.001s
FASTBOOT Output: sending 'boot' (5760 KB)...
FAILED (remote: The Device must be rooted first)
finished. total time: 0.001s
Please check the log before rebooting into system
Am I doing it wrong? Please help...
Kirizu said:
I have an xperia ray (ST18i) and it is stuck on sony/sony ericsson logo forever. I already flashed many versions of stock roms (using flashtool) and nothing worked. If I flash an old rom (4.0.2.A.0.62) it will display sony ericsson and if I install a newer rom (4.1.B.0.587) or update vita pc companion/sus it will display the sony logo and hang there until the battery is removed or dead.
My device has a locked bootloader and is not rooted and I want to install a custom kernel/pre rooted kernel to install custom roms via CWM hoping it would solve my problem. So I unlocked my bootloader booted into fastmode and attempted to flash a pre rooted kernel but it says:
Flashing selected kernel
sending 'boot' (5760 KB)...
FAILED (remote: The Device must be rooted first)
finished. total time: 0.001s
FASTBOOT Output: sending 'boot' (5760 KB)...
FAILED (remote: The Device must be rooted first)
finished. total time: 0.001s
Please check the log before rebooting into system
Am I doing it wrong? Please help...
Click to expand...
Click to collapse
are you sure that you have unlocked bootloader?
type *#*#7378423#*#* ( *#*#service#*#* )and see what it says.
if it is bootloader unlocked : yes then continue
if it is bootloader unlock allowed : yes then go unlock the bootlaoder first
mnishamk said:
are you sure that you have unlocked bootloader?
type *#*#7378423#*#* ( *#*#service#*#* )and see what it says.
if it is bootloader unlocked : yes then continue
if it is bootloader unlock allowed : yes then go unlock the bootlaoder first
Click to expand...
Click to collapse
My device is stuck at the boot logo so i can't enter those..
I unlocked my bootloader by using the flashtool and entering a code which I think is the official way of unlocking..
Kirizu said:
My device is stuck at the boot logo so i can't enter those..
I unlocked my bootloader by using the flashtool and entering a code which I think is the official way of unlocking..
Click to expand...
Click to collapse
Are you sure you tried to flash a kernel made for your device? And are you sure the bootloader got unlocked?
I guess your phone has a major problem and you can't solve it by flashing stuff/etc
Sent from my Nexus 4 running Android 4.2.2
Yes i am sure that the kernels/roms that I flash are compatible with my device, I got it from the help threads on xperia ray android development.
Already downloaded 4+ stock roms and kernels.. Tried sus/pc companion..
Now I am having doubts if I really unlocked my bootloader, because all the threads I read requires the device to be on for ticking/activating some things like usb debugging, and I did unlock mine while it is only one flash mode as I cant get past sony logo..
I am starting to think of bringing my phone to a service center, but i dont know if they are accepting repairs for phones not covered in service warranty..
Oky so i have xperia u with root(obviously ) and eXperience rom installed.
I tried flashing many kernal(boot.img) but every time i do that its the same (Uanble to flash root required)
Plz help
lols21.10 said:
Oky so i have xperia u with root(obviously ) and eXperience rom installed.
I tried flashing many kernal(boot.img) but every time i do that its the same (Uanble to flash root required)
Plz help
Click to expand...
Click to collapse
You mean with fastboot mode? Root is not enough, bootloader must be unlocked.
ChikeD said:
You mean with fastboot mode? Root is not enough, bootloader must be unlocked.
Click to expand...
Click to collapse
+1
Open flashtool, enter fastboot, look for the .iso file, and flash it.
If it doesn't work, you should try to do it with adb.
manudo said:
+1
Open flashtool, enter fastboot, look for the .iso file, and flash it.
If it doesn't work, you should try to do it with adb.
Click to expand...
Click to collapse
My bootloader is unlocked
lols21.10 said:
My bootloader is unlocked
Click to expand...
Click to collapse
Great, so you can flash custom kernels.
Try to flash with the method at the right side (three buttons) in the kernel flashing screen in flashtool.
manudo said:
Great, so you can flash custom kernels.
Try to flash with the method at the right side (three buttons) in the kernel flashing screen in flashtool.
Click to expand...
Click to collapse
I did't really understand what you saying.
But man its irritating me so much i also tried a " Xperia u tool " to flash kernal but still no successsss
:crying::crying::crying::crying:
AlexDroid00\Kernels\boot.img
30/002/2013 23:02:51 - INFO - Flashing selected kernel
30/002/2013 23:02:51 - INFO - sending 'boot' (9112 KB)...
30/002/2013 23:02:51 - INFO - FAILED (remote: The Device must be rooted first)
30/002/2013 23:02:51 - INFO - finished. total time: 0.002s
30/002/2013 23:02:51 - INFO - FASTBOOT Output:
sending 'boot' (9112 KB)...
FAILED (remote: The Device must be rooted first)
finished. total time: 0.002s
Its shows this error everytime even with rooted and unlocked bootloader
AlexDroid00\Kernels\boot.img
30/002/2013 23:02:51 - INFO - Flashing selected kernel
30/002/2013 23:02:51 - INFO - sending 'boot' (9112 KB)...
30/002/2013 23:02:51 - INFO - FAILED (remote: The Device must be rooted first)
30/002/2013 23:02:51 - INFO - finished. total time: 0.002s
30/002/2013 23:02:51 - INFO - FASTBOOT Output:
sending 'boot' (9112 KB)...
FAILED (remote: The Device must be rooted first)
finished. total time: 0.002s
Its shows this error everytime even with rooted and unlocked bootloader
lols21.10 said:
AlexDroid00\Kernels\boot.img
30/002/2013 23:02:51 - INFO - Flashing selected kernel
30/002/2013 23:02:51 - INFO - sending 'boot' (9112 KB)...
30/002/2013 23:02:51 - INFO - FAILED (remote: The Device must be rooted first)
30/002/2013 23:02:51 - INFO - finished. total time: 0.002s
30/002/2013 23:02:51 - INFO - FASTBOOT Output:
sending 'boot' (9112 KB)...
FAILED (remote: The Device must be rooted first)
finished. total time: 0.002s
Its shows this error everytime even with rooted and unlocked bootloader
Click to expand...
Click to collapse
Are you sure bootloader is unlocked?
Root does not matter, does it show Bootloader unlocked: yes, in service configuration?
YES!
lols21.10 said:
YES!
Click to expand...
Click to collapse
Did you try doing it via cmd?
"fastboot flash boot boot.img"
Anthrax said:
Did you try doing it via cmd?
"fastboot flash boot boot.img"
Click to expand...
Click to collapse
Need the Google USB Drivers first.
Sent from my Xperia Sola using xda premium
manudo said:
Need the Google USB Drivers first.
Sent from my Xperia Sola using xda premium
Click to expand...
Click to collapse
need fastboot drivers and you are good to go...
This dude has the same problem as I did, I just turn off the phone and connect in fastboot mode.
But in cmd it's easier.
Sent from my Xperia Sola using xda premium
No fastboot is also not working(i have fastboot drivers installed)
But My problem is now fixed
I installed kernal via terminal emulator
and it installed it
Anyway thanks for your advice
lols21.10 said:
No fastboot is also not working(i have fastboot drivers installed)
But My problem is now fixed
I installed kernal via terminal emulator
and it installed it
Anyway thanks for your advice
Click to expand...
Click to collapse
You mean, cmd, right?
Sent from my Xperia Sola using xda premium
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
Hello first time here
i am stuck on fastboot
i was following this guide
My complete bootloader unlock and root guide.
So I just got this phone just for fun, it was 75 USD, and went straight to XDA to root it so i can remove some bloat etc. but holy moly i ended up have 10 tabs with different guides open, i have compiled what I did to get this phone rooted. I...
forum.xda-developers.com
i flashed magisk from fastboot after that i fastboot into recovery ...nothink happen its just say the unlock waring and never boot i tried boot into bootloader too didnt fix it .
Please help me its my daily phone
Thank you
deadweiler said:
Hello first time here
i am stuck on fastboot
i was following this guide
My complete bootloader unlock and root guide.
So I just got this phone just for fun, it was 75 USD, and went straight to XDA to root it so i can remove some bloat etc. but holy moly i ended up have 10 tabs with different guides open, i have compiled what I did to get this phone rooted. I...
forum.xda-developers.com
i flashed magisk from fastboot after that i fastboot into recovery ...nothink happen its just say the unlock waring and never boot i tried boot into bootloader too didnt fix it .
Please help me its my daily phone
Thank you
Click to expand...
Click to collapse
Try to flash from fastboot kernel, ramdisk and recovery_ramdisk (EMUI 8.0, right?)
https://mega.nz/file/4w9SWAxS#WlHTqaQBGk31Wi6qohVgwbOEubiS2fnKhHTlMBWe2CY
https://mega.nz/file/4h9wGKIa#VMNFjHk0IfyHBWT5JjiJGKveN4jMt9dCXmyl84D7vlE
https://mega.nz/file/BklwBb6Z#S0ZrfWNik5Wd5R_MO7wmmn9432uAcV8qyyvqxy9VwqU
thanks for fast response i ll try it now
yes i am on 8.0.0
C:\platform-tools>fastboot flash recovery RECOVERY_RAMDISK-ANE-8.0.img
Sending 'recovery' (32768 KB) OKAY [ 0.961s]
Writing 'recovery' FAILED (remote: 'partition length get error')
fastboot: error: Command failed
deadweiler said:
yes i am on 8.0.0
C:\platform-tools>fastboot flash recovery RECOVERY_RAMDISK-ANE-8.0.img
Sending 'recovery' (32768 KB) OKAY [ 0.961s]
Writing 'recovery' FAILED (remote: 'partition length get error')
fastboot: error: Command failed
Click to expand...
Click to collapse
Wrong command
fastboot flash recovery_ramdisk RECOVERY_RAMDISK-ANE-8.0.img
iflash all u send .my device is trying to boot now but its just shows the huawei logo and then again it say the device is unlocked warning
After a lot of bootloops it gave me an option to download latest recovery and firmware so i am downloading it ... You are the best !
Null.