Related
I tried to manually flash back to stock 4.4.2 (so I can upgrade to 4.4.3) on my moto x but whenever I type the command "mfastboot flash system system.img" I get "invalid sparse image chunk count. The rest of the commands worked. Now my phone is stuck in the unlocked bootloader screen and I don't know what else to do. Help please?
Try the latest mfastboot see if it helps
Sent from my XT1053 using XDA Free mobile app
serophia said:
Try the latest mfastboot see if it helps
Sent from my XT1053 using XDA Free mobile app
Click to expand...
Click to collapse
Where would I get the latest version?
http://mark.cdmaforums.com/X-STUFF/mfastboot-442.zip
KidJoe said:
http://mark.cdmaforums.com/X-STUFF/mfastboot-442.zip
Click to expand...
Click to collapse
Thanks for the link. I used it and I still got the same error.
Make sure you are using the system.img from the correct firmware. Below is a link to the Moto model firmwares. Download the right one, unzip the files until you get to the .img files and use that system.img.
Motorola Firmwares
I've used different zip extractors and it always says the system.img file is broken. =O!
Thanks for the help guys! Appreciated
n0obpr0 said:
I've used different zip extractors and it always says the system.img file is broken. =O!
Thanks for the help guys! Appreciated
Click to expand...
Click to collapse
Try the steps listed in this post:
http://forum.xda-developers.com/showpost.php?p=53228057&postcount=148
Basically, the idea here is to flash gpt (partition) and motoboot ONLY, then reboot back into bootloader. Then it should allow you to flash the rest of the items without error. Let us know if it works for you.
samwathegreat said:
Try the steps listed in this post:
http://forum.xda-developers.com/showpost.php?p=53228057&postcount=148
Basically, the idea here is to flash gpt (partition) and motoboot ONLY, then reboot back into bootloader. Then it should allow you to flash the rest of the items without error. Let us know if it works for you.
Click to expand...
Click to collapse
I followed the steps but I still get the same error. In CMD window I get:
mfastboot flash system system.img
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'system' (57163 KB)...
OKAY [ 3.868s]
writing 'system'...
(bootloader) Sparse image is malformatted
FAILED (remote failure)
finished. total time: 6.680s
n0obpr0 said:
I followed the steps but I still get the same error. In CMD window I get:
mfastboot flash system system.img
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'system' (57163 KB)...
OKAY [ 3.868s]
writing 'system'...
(bootloader) Sparse image is malformatted
FAILED (remote failure)
finished. total time: 6.680s
Click to expand...
Click to collapse
And we have your answer. 57MB is WAY too small for a system partition....it is indeed 'malformatted'/corrupt.
Two possibilities:
1. Either your download of the SBF somehow got corrupted. If so, re-download the entire SBF, and do the steps in the post I linked.
2. You are trying to flash the system.img from the OTA for some reason?? The images contained in the official OTA don't contain the entire system - just an incremental update to the existing system. If this is the case, ditch that idea, and download the official SBF from here:
http://sbf.droid-developers.org/phone.php?device=0
samwathegreat said:
And we have your answer. 57MB is WAY too small for a system partition....it is indeed 'malformatted'/corrupt.
Two possibilities:
1. Either your download of the SBF somehow got corrupted. If so, re-download the entire SBF, and do the steps in the post I linked.
2. You are trying to flash the system.img from the OTA for some reason?? The images contained in the official OTA don't contain the entire system - just an incremental update to the existing system. If this is the case, ditch that idea, and download the official SBF from here:
http://sbf.droid-developers.org/phone.php?device=0
Click to expand...
Click to collapse
That's what I thought. I actually downloaded the SBF from the link you provided. When I open the zip file, system.img is 873,450,540. I'm gonna download it from my laptop.
Edit: Thank you!!! I downloaded the file in my laptop and extracted the file and I had the right size this time. I flashed it and it worked =) Thank you everybody! Y'all made my day =)
n0obpr0 said:
That's what I thought. I actually downloaded the SBF from the link you provided. When I open the zip file, system.img is 873,450,540. I'm gonna download it from my laptop.
Edit: Thank you!!! I downloaded the file in my laptop and extracted the file and I had the right size this time. I flashed it and it worked =) Thank you everybody! Y'all made my day =)
Click to expand...
Click to collapse
That's what were here for to help others xD
Sent from my XT1053 using XDA Free mobile app
hi i have a sprint htc one m7 hboot 1.57 s-on and i was trying to get it s-off using firewater,rumrunner, so i installed a cm11 rom with the kernel and my problems began, i decided to relock bootloader to install the stock RUU but everything wiped fom my phone (including sd card, showed can't mount sd) except the twrp recovery, can't use sideload from the recovery because my phone is not recognized from my computer (only fastboot mode (though i can hear the plug in sound on windows), after a long search i found a way to format the sd card partition and my computer recognized the phone so i copied a TWRP backup i made earlier and that way i was able to have a "functional" phone again...but now i have a reboot loop, phone works around 2 min and then reboots and so on... Adb works when phone starts but since its just for a couple of min i can't do much.
i've downloaded the RUU.exe but my computer wont run it (don't know why) so i downloaded the firmware RUU too and copied it to the sd card(when it was working) and flashed it but the loop continues. I once again relocked the bootloader to try to flash the RUU via fastboot, but i get this error:
C:\Users\User\Desktop\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fast
boot flash zip Stock_Rom_m7wls_5.05.651.2_kk442_sense60.zip
target reported max download size of 1514139648 bytes
sending 'zip' (1202900 KB)...
OKAY [ 47.328s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 150.761s
any suggestions? do i have to flash this firmware RUU too? http://forum.xda-developers.com/showthread.php?t=2795856
Thanks
**Edit**
i just flashed the firmware RUU from the above link and got this error:
C:\Users\User\Desktop\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fast
boot flash zip 5.05.651.2_full_firmware.zip
target reported max download size of 1514139648 bytes
sending 'zip' (39656 KB)...
OKAY [ 3.026s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 7.940s
Since you are s-on, you cannot flash the firmware. From the thread you linked, you have two options to try:
1. You already tried this, but it's the best option. Download the encrypted RUU (first link of OP) and run it.
2. In the OP, find the previous RUUs link and click the Show Content button. Download the first link below the screenshot (old RUU zip) and follow instructions.
Hopefully one of those should work and you'll be up and running (fingers crossed).
I ended up running the RUU.exe and now I'm back to stock. Thanks
Sent from my HTC One_M8 using XDA Free mobile app
Hello,
At the moment, my phone has an unlocked bootloader and trwp recovery installed.
When I want to flash the stock system (because I have removed it completely just like I did months ago) via fastboot, I always get this error "failed <remote: sparse flash write failure>" while I can install the stock recovery, stock boot.
I also noticed that I can't erase nor format ANY partition, it gives me "command not allowed".
When I check devices in fastboot it shows mine.
In the past, I have installed the same file that I'm trying to install right now and it worked like a charm, but now I don't know what is wrong
Can you tell me what I have done?
I read somewhere it is a hardware issue
Can you at least tell me what caused it?
I have removed cache, dalvik cache and data but nothing happened. I also used another pc to flash the system still didn't work.
What I haven't tried is using sd card ( which I don't have at the moment)
Here is a sample:
C:\Users\HP\Desktop\phone\img\fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' (430551 KB)...
OKAY [ 15.525s]
writing 'system'...
FAILED (remote: sparse flash write failure)
finished. total time: 15.562s
Thank you for reading, appreciate it
IDontKnowAnythingAtAll said:
Hello,
At the moment, my phone has an unlocked bootloader and trwp recovery installed.
When I want to flash the stock system (because I have removed it completely just like I did months ago) via fastboot, I always get this error "failed <remote: sparse flash write failure>" while I can install the stock recovery, stock boot.
I also noticed that I can't erase nor format ANY partition, it gives me "command not allowed".
When I check devices in fastboot it shows mine.
In the past, I have installed the same file that I'm trying to install right now and it worked like a charm, but now I don't know what is wrong
Can you tell me what I have done?
I read somewhere it is a hardware issue
Can you at least tell me what caused it?
I have removed cache, dalvik cache and data but nothing happened. I also used another pc to flash the system still didn't work.
What I haven't tried is using sd card ( which I don't have at the moment)
Here is a sample:
C:\Users\HP\Desktop\phone\img\fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' (430551 KB)...
OKAY [ 15.525s]
writing 'system'...
FAILED (remote: sparse flash write failure)
finished. total time: 15.562s
Thank you for reading, appreciate it
Click to expand...
Click to collapse
I'm having the same issue on my P9 Plus. Did you manage to fix it somehow?
Command not allowed = bootloader is NOT unlocked. But maybe the bootloader shows "unlocked" but it isnt.
WHat you should try:
Rollback to Marshmallow via Dload method (sdcard needed)
xtcislove said:
Command not allowed = bootloader is NOT unlocked. But maybe the bootloader shows "unlocked" but it isnt.
WHat you should try:
Rollback to Marshmallow via Dload method (sdcard needed)
Click to expand...
Click to collapse
I don't think this would work since all of this happened because I tried to overwrite both recovery and recovery2 with twrp which ended up soft bricking my phone. So basically the only thing that would flash is the recovery, recovery2 and boot images.
felroric said:
I'm having the same issue on my P9 Plus. Did you manage to fix it somehow?
Click to expand...
Click to collapse
Yes, I did.
You have to flash the same version of Android you wiped before.
It happened with me when I wiped N system then I tried to install MM, the solution was just flash N system.
IDontKnowAnythingAtAll said:
Hello,
At the moment, my phone has an unlocked bootloader and trwp recovery installed.
When I want to flash the stock system (because I have removed it completely just like I did months ago) via fastboot, I always get this error "failed <remote: sparse flash write failure>" while I can install the stock recovery, stock boot.
I also noticed that I can't erase nor format ANY partition, it gives me "command not allowed".
When I check devices in fastboot it shows mine.
In the past, I have installed the same file that I'm trying to install right now and it worked like a charm, but now I don't know what is wrong
Can you tell me what I have done?
I read somewhere it is a hardware issue
Can you at least tell me what caused it?
I have removed cache, dalvik cache and data but nothing happened. I also used another pc to flash the system still didn't work.
What I haven't tried is using sd card ( which I don't have at the moment)
Here is a sample:
C:\Users\HP\Desktop\phone\img\fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' (430551 KB)...
OKAY [ 15.525s]
writing 'system'...
FAILED (remote: sparse flash write failure)
finished. total time: 15.562s
Thank you for reading, appreciate it
Click to expand...
Click to collapse
What is your BULID NUMBER?
---------- Post added at 05:29 PM ---------- Previous post was at 05:28 PM ----------
IDontKnowAnythingAtAll said:
Hello,
At the moment, my phone has an unlocked bootloader and trwp recovery installed.
When I want to flash the stock system (because I have removed it completely just like I did months ago) via fastboot, I always get this error "failed <remote: sparse flash write failure>" while I can install the stock recovery, stock boot.
I also noticed that I can't erase nor format ANY partition, it gives me "command not allowed".
When I check devices in fastboot it shows mine.
In the past, I have installed the same file that I'm trying to install right now and it worked like a charm, but now I don't know what is wrong
Can you tell me what I have done?
I read somewhere it is a hardware issue
Can you at least tell me what caused it?
I have removed cache, dalvik cache and data but nothing happened. I also used another pc to flash the system still didn't work.
What I haven't tried is using sd card ( which I don't have at the moment)
Here is a sample:
C:\Users\HP\Desktop\phone\img\fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' (430551 KB)...
OKAY [ 15.525s]
writing 'system'...
FAILED (remote: sparse flash write failure)
finished. total time: 15.562s
Thank you for reading, appreciate it
Click to expand...
Click to collapse
You get error every time cause your frp is lock
Rafa Mistry said:
What is your BULID NUMBER?
---------- Post added at 05:29 PM ---------- Previous post was at 05:28 PM ----------
You get error every time cause your frp is lock
Click to expand...
Click to collapse
My build number before wiping was L19C185B385
Yes, I know that but it wasn't because of Locked FRP it was because of installing MM software without installing the rollback package
IDontKnowAnythingAtAll said:
My build number before wiping was L19C185B385
Yes, I know that but it wasn't because of Locked FRP it was because of installing MM software without installing the rollback package
Click to expand...
Click to collapse
Your twrp is installED?
Rafa Mistry said:
Your twrp is installED?
Click to expand...
Click to collapse
Well, My phone is working now. But yeah I had twrp
IDontKnowAnythingAtAll said:
Well, My phone is working now. But yeah I had twrp
Click to expand...
Click to collapse
I have the same problem. How did you fix it?
Hi All,
So this morning I got 2 nags on my phone... 1) for the Android February Security Update to 9.0, and 2) for the Magisk Manager Update to 7.0.0
I followed this procedure (newbie alert!) to update both of them...
1. Magisk Manager → Uninstall → Restore Images. Do not reboot or you will have Magisk uninstalled.
2. Update the system and let it install completely. Do not press the reboot button.
3. Magisk Manager → Update → Install to Inactive Slot for OTA.
4 Once Magisk installation is done, press the reboot button in Magisk Manager.
When I did this, I got the white boot screen with the G Google logo, and then the screen went black.
I waited, and waited.
I used the fingerprint to unlock the screen... nothing.
I pressed the power button to turn on the screen... nothing.
I waited.
I then held the power butoon for freaking ages and then it rebooted back to the usual unlocked bootloader warning and did the same thing again.
HELP! please!
Paully
Pixel (sailfish) stock Android 9.0 with Magisk and Titanium Backup Pro root
OK, I have managed to get the phone up-and-running by ...
1. Hold buttons (Power + VOL DOWN) to get in to the bootloader.
2. USB cable > fastboot devices
3. USB cable > fastboot boot twrp-3.2.3-1-sailfish.img
4. TWRP > Reboot > Slot A
...and the phone seems fine.
I can reboot it as normal.
However, I cannot reboot to Recovery... seem to have lost TWRP, which I can reinstall again.
However, I am going to wait until I get a reply first.
Paully
I know that Magisk has OTA support.
As a sailfish owner too, I remember when Pixels were not supported by Magisk OTA system, I just get used to flash it manually in a 5 minutes procedure.
All I always do is flash the new factory image (removing the "-w" at the bottom line of the flash-all script, so it will upgrade without wiping) and then simply fastboot boot twrp and reflash magisk.
Never had a single problem doing this. I don't know what guide you followed, but the procedure you did looks like correct.
If you prefer this automatic way, try follow the official guide that topjohnwu made.
Hope it helps
As far as I know (I don't own a device where this is applicable), it's still recommended to not install TWRP at the same time as Magisk on A/B devices. Since they both alter the boot image, you might end up with issues like bootloops. Only boot TWRP...
It's not certain that this was the source of your issue, but it's one possibility. Other possibilities might include modules that are incompatible with the update, etc.
Other than that, the official docs linked above should work fine.
TENN3R said:
I know that Magisk has OTA support.
As a sailfish owner too, I remember when Pixels were not supported by Magisk OTA system, I just get used to flash it manually in a 5 minutes procedure.
All I always do is flash the new factory image (removing the "-w" at the bottom line of the flash-all script, so it will upgrade without wiping) and then simply fastboot boot twrp and reflash magisk.
Never had a single problem doing this. I don't know what guide you followed, but the procedure you did looks like correct.
If you prefer this automatic way, try follow the official guide that topjohnwu made. Hope it helps
Click to expand...
Click to collapse
Thank for the tip about editing the ./flash-all script to remove the -w ... neat.
More research is required, as am new to Magisk, but the second poster to reply to this has mentioned that TWRP and Magisk do not sit well together, and it never occurred to me that I don't really need TWRP actually installed, if I can always get to a laptop and USB cable!
Thanks for your reply... I dunno, the things we do to keep stuff "easier".
Paully
Didgeridoohan said:
As far as I know (I don't own a device where this is applicable), it's still recommended to not install TWRP at the same time as Magisk on A/B devices. Since they both alter the boot image, you might end up with issues like bootloops. Only boot TWRP. It's not certain that this was the source of your issue, but it's one possibility. Other possibilities might include modules that are incompatible with the update, etc. Other than that, the official docs linked above should work fine.
Click to expand...
Click to collapse
Thanks for your reply.
Now I think about it, as long as I can get to my laptop and a USB cable, I don't need to _install_ TWRP if I need to do stuff.
So, the Pixel with 9.0 is currently in this state...
* SLOT A with Security Patch level: 5 December 2018
* Magisk patched boot image not installed
* TWRP not installed?
* Magisk Manager app installed
I think SLOT B is broken?
How do I do this properly? Are there STEP BY STEP instructions somewhere?
Do I uninstall TWRP, or is it already hosed when Magisk 'restored images' and then 'patched'???!
Yours, a bit worried...
Paully
plittlefield said:
Thank for the tip about editing the ./flash-all script to remove the -w ... neat.
More research is required, as am new to Magisk, but the second poster to reply to this has mentioned that TWRP and Magisk do not sit well together, and it never occurred to me that I don't really need TWRP actually installed, if I can always get to a laptop and USB cable!
Thanks for your reply... I dunno, the things we do to keep stuff "easier".
Paully
Click to expand...
Click to collapse
That's right, since december (I think?) looks like Magisk and TWRP have some incompatibilities, before I always flashed them together with no problems at all.
A useful "trick" about flashing without a pc would be using Franco Kernel manager, as he added support for a flasher even without having twrp installed. Just select the zip and tap on flash. That's kinda magical.
Of course for this you need to buy his app, but as of today it's a pretty universal kernel manager, not only restricted for his kernel. I find it very useful.
TENN3R said:
That's right, since december (I think?) looks like Magisk and TWRP have some incompatibilities, before I always flashed them together with no problems at all.
Click to expand...
Click to collapse
OK, so what do I do now to remove Magisk, TWRP and then start again?
plittlefield said:
OK, so what do I do now to remove Magisk, TWRP and then start again?
Click to expand...
Click to collapse
Seriously, a web page on this very problem!
https://magiskroot.net/uninstall-magisk-module-twrp/
plittlefield said:
Seriously, a web page on this very problem!
https://magiskroot.net/uninstall-magisk-module-twrp/
Click to expand...
Click to collapse
That particular link is for removing modules through TWRP, so not anything to do with your problem (or have I misunderstood you completely)...
But, I mainly wanted to give a warning: be very wary of any site that has to do with Magisk and isn't directly mentioned by @topjohnwu in the release thread. There are some really scammy sites and take apps out there trying to benefit from Magisk's popularity.
Thanks. I'll not use that site then.
I could do with some help on how to remove both TWRP and Magisk then start again but not installing TWRP.
Cheers anyone!
plittlefield said:
Thanks. I'll not use that site then.
I could do with some help on how to remove both TWRP and Magisk then start again but not installing TWRP.
Cheers anyone!
Click to expand...
Click to collapse
From my understanding (again, remember I have no experience with A/B devices), all you need to do is to flash the stock boot image. Possibly to both slots, but someone that has experience with A/B devices would be a better source of information, or better yet: check your devices forum for info.
Once you have the stock image installed all you need to do is to boot TWRP and flash the Magisk zip.
Understood, that sounds reasonable.
Cheers everyone.
Yep, going back to stock boot image on Pixel are just 2 commands. Extract the boot.img from the stock factory image, then in fastboot:
- fastboot flash boot_a boot.img
- fastboot flash boot_b boot.img
Then reboot
TENN3R said:
Yep, going back to stock boot image on Pixel are just 2 commands. Extract the boot.img from the stock factory image, then in fastboot:
- fastboot flash boot_a boot.img
- fastboot flash boot_b boot.img
Then reboot
Click to expand...
Click to collapse
OK, so I am currently running PQ1A.181205.002.A1, Dec 2018 in Slot A (it won't boot from Slot B)
Do I download the OTA image or the FULL image? I guess they contain the same bootloader image...?
bootloader-sailfish-8996-012001-1811131534.img
Thanks in advance.
Paully
Images are only in the full factory image, not ota.
If you wanna stay on december update, download the december factory image otherwise grab the latest february, edit the script to keep data and flash so it will upgrade everything with no wipes.
If you wanna flash only the december boot image, you can find it in the zip, which is inside another zip in the factory image.
Pay attention, the boot is exactly called "boot.img", I tell you because inside that zip there is another file called "boot-a" or something similar, this is NOT the one you wanna flash
OK, so that worked.
I flashed the February factory image without wipe...
Code:
Sending 'bootloader_a' (32424 KB) OKAY [ 1.401s]
Writing 'bootloader_a' (bootloader) Valid bootloader version.
(bootloader) Flashing active slot "_a"
(bootloader) Flashing active slot "_a"
OKAY [ 13.421s]
Finished. Total time: 14.934s
rebooting into bootloader OKAY [ 0.042s]
Finished. Total time: 0.193s
Sending 'radio_a' (57140 KB) OKAY [ 2.403s]
Writing 'radio_a' OKAY [ 1.102s]
Finished. Total time: 3.625s
rebooting into bootloader OKAY [ 0.042s]
Finished. Total time: 0.343s
extracting android-info.txt (0 MB) to RAM...
--------------------------------------------
Bootloader Version...: 8996-012001-1811131534
Baseband Version.....: 8996-130181-1811270246
Serial Number........: FA69M0304045
--------------------------------------------
Checking product OKAY [ 0.050s]
Checking version-bootloader OKAY [ 0.050s]
Checking version-baseband OKAY [ 0.050s]
extracting boot.img (29 MB) to disk... took 0.178s
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
archive does not contain 'dtbo.img'
archive does not contain 'dt.img'
archive does not contain 'odm.img'
archive does not contain 'product.img'
archive does not contain 'product-services.img'
archive does not contain 'recovery.img'
archive does not contain 'super.img'
extracting system.img (1944 MB) to disk... took 14.619s
archive does not contain 'system.sig'
extracting system_other.img (312 MB) to disk... took 3.222s
archive does not contain 'system.sig'
archive does not contain 'vbmeta.img'
extracting vendor.img (259 MB) to disk... took 1.987s
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
Sending 'boot_a' (29761 KB) OKAY [ 1.301s]
Writing 'boot_a' OKAY [ 0.655s]
Sending sparse 'system_a' 1/4 (524284 KB) OKAY [ 23.023s]
Writing sparse 'system_a' 1/4 OKAY [ 4.642s]
Sending sparse 'system_a' 2/4 (524284 KB) OKAY [ 22.421s]
Writing sparse 'system_a' 2/4 OKAY [ 4.345s]
Sending sparse 'system_a' 3/4 (524284 KB) OKAY [ 22.368s]
Writing sparse 'system_a' 3/4 OKAY [ 4.341s]
Sending sparse 'system_a' 4/4 (418060 KB) OKAY [ 17.867s]
Writing sparse 'system_a' 4/4 OKAY [ 3.545s]
Sending 'system_b' (319668 KB) OKAY [ 13.160s]
Writing 'system_b' OKAY [ 3.048s]
Sending 'vendor_a' (265748 KB) OKAY [ 10.768s]
Writing 'vendor_a' OKAY [ 2.838s]
Setting current slot to 'a' OKAY [ 0.404s]
Rebooting
Finished. Total time: 156.038s
Should I be able boot from Slot B because it doesn't do anything if I try?
Paully
Do I need to worry about using Slot B?
plittlefield said:
Do I need to worry about using Slot B?
Click to expand...
Click to collapse
I never changed slots after a flash, neither selected to which slot flash zips, I think it's all manager by the installer scripts, same for magisk, twrp, kernel, ...
Once you flash and reboot you're ok
TENN3R said:
I never changed slots after a flash, neither selected to which slot flash zips, I think it's all manager by the installer scripts, same for magisk, twrp, kernel. Once you flash and reboot you're ok
Click to expand...
Click to collapse
OK, thanks
Hi,
When I download I cant find it on my downloads. I have to go into my files app then I can find the zip there. And when I try patch it, it says "unknown image format". Therefore the installation fails.
How can I fix this. I also haven't been able to install TWRP.
thanks
What zip file? Do you mean the Magisk installation zip? You can't use that unless you're already rooted (and then you need to install it from the modules section of the Manager) or through TWRP. But if you're already rooted it's easier to just do a direct install from the Manager anyway.
The patch file option in the Manager is for a boot or recovery image (depending on what device you have, see the installation instructions).
twrp
thanks for your reply.
Im also having trouble with installing twrp. I have unlocked the bootloader on my huawei p8 lite 2017 and have downloaded all the tools and flash img needed to flash it. However when use command " fastboot flash recovery twrp-3.4.0-0-prague.img" it says:
Sending 'recovery' (13458 KB) OKAY [ 0.532s]
Writing 'recovery' OKAY [ 0.340s]
Finished. Total time: 0.909s
then when I use " fastboot boot twrp-3.4.0-0-prague.img" it says
Sending 'boot.img' (13458 KB) OKAY [ 0.500s]
Booting FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
How can i fix this. Thanks in advance.
The recovery seems to have installed correctly, so instead of running the command to boot the image, try just using the option directly in the bootloader (usually navigated to by using the volume keys) to boot into recovery.
Didgeridoohan said:
The recovery seems to have installed correctly, so instead of running the command to boot the image, try just using the option directly in the bootloader (usually navigated to by using the volume keys) to boot into recovery.
Click to expand...
Click to collapse
Hi,
When i boot into recover I get another error which is as follows:
ERROR MODE
ATTENTION!
PLEASE UPDATE SYSTEM AGAIN
(Green android bot image)
ERROR!
Func NO : 11 (recovery image)
Error NO : 2(load failed!)
Thanks
You need to take this to your device's forum. That's the best way to get help with stuff like this...
Judging by this thread, you're using the wrong command:
https://forum.xda-developers.com/p8...nt/recovery-twrp-huawei-p8-lite-2017-t4113153