Database Develop

Mate S no OS Installed

hello,excuse me for my english but i have an problem with my mate s.firmware installed is b145 europe and after i unlock the bootloader and frp i have root and installed twrp.after this operation i have disable option developer in setting and i reboot in twrp for advanced wipe without internal storage.
my phone is in bootloop logo huawei.i have put the dload directory but not work in the recovery stock..return Always on twrp recovery.volume+ ,+ vol- and power go into fastboot mode but not accept command for flash boot.img recovery.img and etc etc because frp is locked!
i'm desperate...please help me..i have used twrp 2.8.7.0 and supersu 2.49..memory of internal storage is 24.7 gb free..i think the system is intact!!thanks

can you reach twrp?
if so, then reboot into bootloader through twrp..then in bootloader you can flash the stock boot.img and recovery.img of the b145..
after that you should be able to reboot normal..
Gesendet von meinem Mate S CRR-L09 B321

Thanks for your support..yes i can reach in twrp and in the bootloader..but My answer is :must i do flash of stock boot.img and recovery.img through fastboot e rescuemode?if so i made it yet and it doesnt work because frp is locked and i have return error with adb fasttool!!

SuperSU 2.42
frisko76 said:
hello,excuse me for my english but i have an problem with my mate s.firmware installed is b145 europe and after i unlock the bootloader and frp i have root and installed twrp.after this operation i have disable option developer in setting and i reboot in twrp for advanced wipe without internal storage.
my phone is in bootloop logo huawei.i have put the dload directory but not work in the recovery stock..return Always on twrp recovery.volume+ ,+ vol- and power go into fastboot mode but not accept command for flash boot.img recovery.img and etc etc because frp is locked!
i'm desperate...please help me..i have used twrp 2.8.7.0 and supersu 2.49..memory of internal storage is 24.7 gb free..i think the system is intact!!thanks
Click to expand...
Click to collapse
Try flashing SuperSU 2.42 from TWRP and see if you´re able to boot. When I installed versions newer than 2.45 I ended up in bootloop.
Edit: Sorry, I mean 2.62 is the right one and over 2.65 will end up in loop. Anyway, try 2.62.

ok..i try this way to install supesu 2.62..this screenshot is result when i reboot into bootloader trought twrp..i not understand because i have this error :command not allowed
C:\Users\frisko76\Desktop\huawei\Latest-Fastboot-Adb-Tool>fastboot flash boot bo
ot.img
target reported max download size of 471859200 bytes
sending 'boot' (23552 KB)...
OKAY [ 0.632s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.632s
C:\Users\frisko76\Desktop\huawei\Latest-Fastboot-Adb-Tool>fastboot flash recover
y recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (31372 KB)...
OKAY [ 0.855s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.865s
C:\Users\frisko76\Desktop\huawei\Latest-Fastboot-Adb-Tool>
excuse me but i not post an image!
i have tried to install supersu 2.62 but return message error no os install and the device not have supersu do you want to install??i already installed supersu and i have this message after?..i tried to install supersu 2.75 and i have only the message no os installed..but the phone are same in bootloop....can i search an tool for erase frp tool?for Samsung exist and for sony experia..for huawei?

hello,i verified only method for resume device is use dc unlocker for price 15credit... ...but i have an other idea..i have an other huawei mate s,original stock recovery..can i try to unlock bootloader and developer option , install twrp and try backup for use in the other device ???..is same firmware b145 eu...it could be right way for resume my device?thanks

Assistance with bricked phone

So I was trying to increase the headphone volume by editing /odm/etc/audio/hi6403/mixer_volumes_CHARLOTTE_ce.xml. After getting root I tried to edit the file through Solid Explorer but I just got an error that it failed. Afterwards it seemed like the config file was wiped but I thought a reboot would overwrite/resolve it. However during boot it gets stuck on the Huawei logo and eventually reverts to erecovery. Erecovery complains it can't get package info and ADB sideload fails.
Fastboot works and I have reflashed system, vendor, ramdisk and recovery_ramdis but it still gets stuck in boot. I thought maybe the ODM file needs to be reflashed as well but not sure if its possible via fastboot and what the command is?
Any ideas? Would flashing a customer ROm work, I'm not sure which files get replaced and which remain when changing, but I think it's the volume file that is the issue and needs to be set to default....

It's definitely the XML file that is the issue, if I cat the file through TWRP terminal it is empty. Unfortunately if I try to replace it with one of the other XML mixer files I get an error that says no space available. Reducing the reserved blocks doesn't help so one option is to increase the partition size but I'm weary of this and not sure if I can even achieve it through the terminal. The second is to flash the ODM file, but I might have the wrong command:
fastboot flash odm ODM.img
target reported max download size of 471859200 bytes
sending 'odm' (128686 KB)...
OKAY [ 2.900s]
writing 'odm'...
FAILED (remote: Command not allowed)
finished. total time: 2.912s

Saved by FunkyHuawei recovery

i have exactly the same issue i tried factory reset and everything nothing works any idea?

ShaKki said:
i have exactly the same issue i tried factory reset and everything nothing works any idea?
Click to expand...
Click to collapse
Bricked due to the file I mentioned in the first post?
If so then the issue is the ODM partition, which I don't think can be flashed via fastboot. Your options are Huawei erecovery (which didn't work for me) or Funky Huawei, which worked first time. You'll need 1 credit.
I followed this guide: https://funkyhuawei.club/static/instructions201710.pdf

i managed to do it myself, i got into TWRP and deleted all caches and all partitions in the advanced folder - after that i could reboot.

I bricked my OnePlus 7 Pro (was stuck and fastboot) and how I fixed it

Hi, I'm writing this to guide those who faced - and will face similar situation in the future - the problem of being stuck on the fastboot screen, where the recovery or booting in EDL is not available.
So, after failing to get root after upgrading to android 10 I was fiddling with TWRP to try to get it to recognize my storage so I can reflash it and flash Magisk, but I couldn't get it to mount the storage, so my stupid brain decided to go to the wipe page and wiped everything in the hope it might magically work!! well.. it didn't!! and I got stuck in the fastboot screen and I thought that I bricked my phone for good.
after hours of searching online and trying everything nothing helped... but finally I managed to fix it.
and btw when I tried to flash TWRP by (fasboot boot twrp.img) I got the following message:
"remote: Failed to load/authenticate boot image: Load Error"
So here is what I did to get my phone working again:
Download and install Tool All in One
Download Fastboot ROM for your phone from here
In the Tool All in One app click on the Flash Factory Images button.
Select the ROM and let it do its work,
hopefully this will work and your device will reboot into a fresh android.

Also it's good to know that the official TWRP of twrp.me does not support Android Q at the moment, that's why you couldn't decrypt and mount the storage. TWRP in Oneplus 7 Pro thread here on XDA does support Q, you just have to remember to boot into the inactive/upgraded slot before booting back to TWRP to flash Magisk as it only installs to the active slot and not the upgraded slot.
Skickat från min GM1913 via Tapatalk

vegatr0n said:
Hi, I'm writing this to guide those who faced - and will face similar situation in the future - the problem of being stuck on the fastboot screen, where the recovery or booting in EDL is not available.
So, after failing to get root after upgrading to android 10 I was fiddling with TWRP to try to get it to recognize my storage so I can reflash it and flash Magisk, but I couldn't get it to mount the storage, so my stupid brain decided to go to the wipe page and wiped everything in the hope it might magically work!! well.. it didn't!! and I got stuck in the fastboot screen and I thought that I bricked my phone for good.
after hours of searching online and trying everything nothing helped... but finally I managed to fix it.
and btw when I tried to flash TWRP by (fasboot boot twrp.img) I got the following message:
"remote: Failed to load/authenticate boot image: Load Error"
So here is what I did to get my phone working again:
Download and install Tool All in One
Download Fastboot ROM for your phone from here
In the Tool All in One app click on the Flash Factory Images button.
Select the ROM and let it do its work,
hopefully this will work and your device will reboot into a fresh android.
Click to expand...
Click to collapse
Or just use the MSM tool. Job done

All with varying levels of interpretation, steps, descriptions, and the solution. Not all are useful.

I had the same issue and this worked perfectly to get my device up and running again. Thanks again!!

Hi all!
Here is plan B!
First of all - BEFORE you do some upgrade - make OPSwitch backup and copy to PC !!!!!
If you stuck - it's mean that something is badly damaged and wrong. Some of the files reside in the areas where upgrade tools (including Fastboot!) can't change and repair them.
We don't have time, knowledge to sort out WHAT was damaged.
We make all straight from beginning:
1. MSM tools - make your phone like from the Factory with "clean" install (ver 9 for now)
2. "FlashAll" то ver 10E
3. If you need - install "global"
4. If you need - install TWRP and Magisk
5. Restore your backup from PC
At the end you will have "clean" phone with all programs working
EASY!!!

Same as OP, I wanted to flash twrp.img.
I had my OP7Pro stuck in 'fastboot mode', I thought. It wouldn't respond to any commands from console (device not found) and I couldn't turn it off with the power button any more.
For noobs, just like me, I learned that I just had to press the powerbutton + volume up button. My phone rebooted after this.
Now making a backup before rooting and such, phew.

vegatr0n
I was stuck in Fastboot after switching slots. Excelent stuf! 2,3 clicks , done! Thank you!

vegatr0n said:
Hi, I'm writing this to guide those who faced - and will face similar situation in the future - the problem of being stuck on the fastboot screen, where the recovery or booting in EDL is not available.
So, after failing to get root after upgrading to android 10 I was fiddling with TWRP to try to get it to recognize my storage so I can reflash it and flash Magisk, but I couldn't get it to mount the storage, so my stupid brain decided to go to the wipe page and wiped everything in the hope it might magically work!! well.. it didn't!! and I got stuck in the fastboot screen and I thought that I bricked my phone for good.
after hours of searching online and trying everything nothing helped... but finally I managed to fix it.
and btw when I tried to flash TWRP by (fasboot boot twrp.img) I got the following message:
"remote: Failed to load/authenticate boot image: Load Error"
So here is what I did to get my phone working again:
Download and install Tool All in One
Download Fastboot ROM for your phone from here
In the Tool All in One app click on the Flash Factory Images button.
Select the ROM and let it do its work,
hopefully this will work and your device will reboot into a fresh android.
Click to expand...
Click to collapse
Many people have found this problem. Thank you, I am working again.

i am not even able to flash the twrp in android 10 always getting stuck at fastbootlogo after flashing the recovery cmd

nitinvaid said:
i am not even able to flash the twrp in android 10 always getting stuck at fastbootlogo after flashing the recovery cmd
Click to expand...
Click to collapse
Then you have to use the MSM unbrick tool:
https://forum.xda-developers.com/oneplus-7-pro/how-to/op7pro-collection-unbrick-tools-t3956595/amp/

vegatr0n said:
Then you have to use the MSM unbrick tool:
https://forum.xda-developers.com/oneplus-7-pro/how-to/op7pro-collection-unbrick-tools-t3956595/amp/
Click to expand...
Click to collapse
Nope...
I was able to reboot holding both vol+ and - and power

I bricked my tmobile oneplus 7 pro and dont know which file is safe to try can anyone please point me in the right direction?

I already tried the steps using the tool and downloading the FASTBOOK os file and I get this error
"CreateProcess failed: %1 is not a valid Win32 application. (193)
fastboot: error: Cannot generate image for userdata"
Tried booting the device but boots to OOS recovery always.
---------- Post added at 11:54 PM ---------- Previous post was at 11:21 PM ----------
vegatr0n said:
Hi, I'm writing this to guide those who faced - and will face similar situation in the future - the problem of being stuck on the fastboot screen, where the recovery or booting in EDL is not available.
So, after failing to get root after upgrading to android 10 I was fiddling with TWRP to try to get it to recognize my storage so I can reflash it and flash Magisk, but I couldn't get it to mount the storage, so my stupid brain decided to go to the wipe page and wiped everything in the hope it might magically work!! well.. it didn't!! and I got stuck in the fastboot screen and I thought that I bricked my phone for good.
after hours of searching online and trying everything nothing helped... but finally I managed to fix it.
and btw when I tried to flash TWRP by (fasboot boot twrp.img) I got the following message:
"remote: Failed to load/authenticate boot image: Load Error"
So here is what I did to get my phone working again:
Download and install Tool All in One
Download Fastboot ROM for your phone from here
In the Tool All in One app click on the Flash Factory Images button.
Select the ROM and let it do its work,
hopefully this will work and your device will reboot into a fresh android.
Click to expand...
Click to collapse
I am getting the error
"Erasing 'userdata' OKAY [ 0.243s]
CreateProcess failed: %1 is not a valid Win32 application. (193)
fastboot: error: Cannot generate image for userdata"
I dont know how to proceed with this :crying:

moonbosques said:
I already tried the steps using the tool and downloading the FASTBOOK os file and I get this error
"CreateProcess failed: %1 is not a valid Win32 application. (193)
fastboot: error: Cannot generate image for userdata"
Tried booting the device but boots to OOS recovery always.
---------- Post added at 11:54 PM ---------- Previous post was at 11:21 PM ----------
I am getting the error
"Erasing 'userdata' OKAY [ 0.243s]
CreateProcess failed: %1 is not a valid Win32 application. (193)
fastboot: error: Cannot generate image for userdata"
I dont know how to proceed with this :crying:
Click to expand...
Click to collapse
Sounds like you're having problems with Windows Defender. I also got the same error messages suddenly once week ago. I did sfc /scannow and all that but all files were intact. After rebooting the PC two times the problem was gone, really strange.
Skickat från min GM1913 via Tapatalk

Anyone here know what fastboot rom i can use to fix my bricked tmobile oneplus 7 pro?

Can you explain this strange effect, please
pitrus- said:
Also it's good to know that the official TWRP of twrp.me does not support Android Q at the moment, that's why you couldn't decrypt and mount the storage. TWRP in Oneplus 7 Pro thread here on XDA does support Q, you just have to remember to boot into the inactive/upgraded slot before booting back to TWRP to flash Magisk as it only installs to the active slot and not the upgraded slot.
Skickat från min GM1913 via Tapatalk
Click to expand...
Click to collapse
After an update to Android Q twrp an root was lost.
I was going the normal way like this:
1. In fastboot boot twrp.img
2. In twrp install twrp.zip
3. Reboot to twrp
4. In twrp install magisk.zip
After this the phone stuck a while on this orange splash screen and then reboot to bootloader.
Reboot --> the same effect
Then:
1. Boot into twrp
2. install twrp.zip
3. Reboot system
Everything ok, but no root
Just one method is working for me:
1. Download the full package of OOS 10.x.x
2. Extract the boot.img
3. Patch boot.img with Magisk
4. Flash on fastboot boot magisk_patched.img
5. reboot
My phone is rooted now but without twrp.
Why can twrp an Magisk not work together?
And why I can´t find any information for this problem on the internet?

Well, since TWRP lives in the boot partition on this phone, you will have to boot TWRP using fastboot boot TWRP. Then you flash the unofficial TWRP build 74 installer zip downloaded from the link below (the one from twrp.me only works on OOS 9 and not 10). Reboot phone back into Magisk to switch slot, flash Magisk installer zip which will then install Magisk to both boot slot a and boot slot b. Reboot phone and you should have both Magisk root and working TWRP.
https://r.tapatalk.com/shareLink/to...2&share_fid=3793&share_type=t&link_source=app
Skickat från min GM1913 via Tapatalk

Fails anyway
Bricked my OnePlus and now I'm left with bootloader (no os, no twrp). Everything leads back to bootloader. Any attempts to apply fastboot boot lead to "Load Error". Now I tried with that tool and ended up with this:
Sending 'odm' (102400 KB) OKAY [ 2.576s]
Writing 'odm' FAILED (remote: '(odb_b) No such partition')
fastboot: error: Command failed
Press any key to exit...
P.S. Full log:
--------------------------------------------
Bootloader Version...:
Baseband Version.....:
Serial Number........: e434a4c8
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
android-info.txt syntax error: я╗┐require product=msmnile
Setting current slot to 'b' OKAY [ 0.002s]
extracting boot.img (96 MB) to disk... took 0.776s
archive does not contain 'boot.sig'
Sending 'boot_b' (98304 KB) OKAY [ 2.389s]
Writing 'boot_b' OKAY [ 0.406s]
extracting dtbo.img (16 MB) to disk... took 0.151s
archive does not contain 'dtbo.sig'
Sending 'dtbo' (16384 KB) OKAY [ 0.393s]
Writing 'dtbo' OKAY [ 0.047s]
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting vbmeta.img (0 MB) to disk... took 0.001s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta' (8 KB) OKAY [ 0.008s]
Writing 'vbmeta' OKAY [ 0.002s]
archive does not contain 'vbmeta_system.img'
archive does not contain 'super_empty.img'
archive does not contain 'boot_other.img'
extracting odm.img (100 MB) to disk... took 0.395s
archive does not contain 'odm.sig'
Sending 'odm' (102400 KB) OKAY [ 2.576s]
Writing 'odm' FAILED (remote: '(odm_b) No such partition')
fastboot: error: Command failed
Press any key to exit...

I am getting this error, any ideas what is going wrong? (please see attachment)
vegatr0n said:
Hi, I'm writing this to guide those who faced - and will face similar situation in the future - the problem of being stuck on the fastboot screen, where the recovery or booting in EDL is not available.
So, after failing to get root after upgrading to android 10 I was fiddling with TWRP to try to get it to recognize my storage so I can reflash it and flash Magisk, but I couldn't get it to mount the storage, so my stupid brain decided to go to the wipe page and wiped everything in the hope it might magically work!! well.. it didn't!! and I got stuck in the fastboot screen and I thought that I bricked my phone for good.
after hours of searching online and trying everything nothing helped... but finally I managed to fix it.
and btw when I tried to flash TWRP by (fasboot boot twrp.img) I got the following message:
"remote: Failed to load/authenticate boot image: Load Error"
So here is what I did to get my phone working again:
Download and install Tool All in One
Download Fastboot ROM for your phone from here
In the Tool All in One app click on the Flash Factory Images button.
Select the ROM and let it do its work,
hopefully this will work and your device will reboot into a fresh android.
Click to expand...
Click to collapse

custom recovery flash successful, but not working

Hi
I'm on a MI 8 global version with the latest miui (dipper_global_images_V11.0.3.0.QEAMIXM_20200118.0000.00_10.0_global_515bcbba58). I unlocked the phone, did a clean install (flash_all) and now i try to get twrp to work. So i went back to fastboot mode, run the commands:
Code:
fastboot flash recovery twrp-3.3.1-1-dipper.img
Sending 'recovery' (42044 KB) OKAY [ 1.166s]
Writing 'recovery' OKAY [ 0.121s]
Finished. Total time: 1.292s
fastboot boot twrp-3.3.1-1-dipper.img
Sending 'boot.img' (42044 KB) OKAY [ 1.134s]
Booting OKAY [ 0.064s]
Finished. Total time: 1.234s
and then... nothing. It reboots to android... next try flashing and manual reboot by holding power + volume up in fastboot mode until it vibrates and the mi logo is shown. Two seconds later the screen goes black, the device (seems to) reboot and android again.
Next try was a different image (using the lineage custom recovery)... same result. And if i try to boot to recovery when the device was off with power + volume up the original recovery is shown....
I'm out of ideas.

to-bu said:
Hi
I'm on a MI 8 global version with the latest miui (dipper_global_images_V11.0.3.0.QEAMIXM_20200118.0000.00_10.0_global_515bcbba58). I unlocked the phone, did a clean install (flash_all) and now i try to get twrp to work. So i went back to fastboot mode, run the commands:
Code:
fastboot flash recovery twrp-3.3.1-1-dipper.img
Sending 'recovery' (42044 KB) OKAY [ 1.166s]
Writing 'recovery' OKAY [ 0.121s]
Finished. Total time: 1.292s
fastboot boot twrp-3.3.1-1-dipper.img
Sending 'boot.img' (42044 KB) OKAY [ 1.134s]
Booting OKAY [ 0.064s]
Finished. Total time: 1.234s
and then... nothing. It reboots to android... next try flashing and manual reboot by holding power + volume up in fastboot mode until it vibrates and the mi logo is shown. Two seconds later the screen goes black, the device (seems to) reboot and android again.
Next try was a different image (using the lineage custom recovery)... same result. And if i try to boot to recovery when the device was off with power + volume up the original recovery is shown....
I'm out of ideas.
Click to expand...
Click to collapse
Obviously, you did something wrong.
Try renaming the recovery that you downloaded to "recovery" with no quotation marks
Place the file in the platform tools directory
For example: C:\Android\platform-tools\
Then use these commands.
fastboot flash recovery recovery.img
fastboot boot recovery.img
The commands above will flash the recovery.image to the recovery partition, then reboot then phone to recovery, you will then need to flash root.
If that doesn't work just use the Tool all in One

It seems that i "holding it wrong" but in fact it doesn't work eather.
I'm original on linux but to ensure that it's working i switched to the windows system:
* downloaded and installed "Tool all in One"
* choose correct device
* ensure device allows ADB Access to PC
* ensure unlock status in tool
* use "Recovery Flasher and Rooter"
* selected "TWRP 3.3.1 mauronofrio XMI8" with "Automatic TWRP MD5 Check" and "And boot it" options
* flashed... and nothing again....
So i downloaded the and unpacked "dipper_global_images_V11.0.3.0.QEAMIXM_20200118.0000.00_10.0_global" to C:\ and used the "Flash Factory Images" to reset the device to a clean state (again.) After the flash and the automatic reboot of the device i went manual Fastboot mode and repeat "Recovery Flasher and Device Router"... with the same result....
So definitly something is wrong

to-bu said:
It seems that i "holding it wrong" but in fact it doesn't work eather.
I'm original on linux but to ensure that it's working i switched to the windows system:
* downloaded and installed "Tool all in One"
* choose correct device
* ensure device allows ADB Access to PC
* ensure unlock status in tool
* use "Recovery Flasher and Rooter"
* selected "TWRP 3.3.1 mauronofrio XMI8" with "Automatic TWRP MD5 Check" and "And boot it" options
* flashed... and nothing again....
So i downloaded the and unpacked "dipper_global_images_V11.0.3.0.QEAMIXM_20200118.0000.00_10.0_global" to C:\ and used the "Flash Factory Images" to reset the device to a clean state (again.) After the flash and the automatic reboot of the device i went manual Fastboot mode and repeat "Recovery Flasher and Device Router"... with the same result....
So definitely something is wrong
Click to expand...
Click to collapse
Are you sure that you have developer options setup? ADB debugging is enabled?
If you plan on staying on the stock rom that you are currently using you may need to flash DM verity. personally I prefer to use Orange Fox because it has DM verity built in.
once you are finally successful flash TWRP you might consider switching it. But be warned the layout takes some getting used to.
The latest Orange Fox is here: https://files.orangefox.tech/OrangeFox-Beta/dipper/OrangeFox-R10.1_002-Beta-dipper.zip
Worst case scenario; If you are located in the US, I can do it for you. ( just send me a PM if you want me to do it)
I have provided this service for a lot of people, you pay shipping and buy me a beer. This will take no more than 10 minutes.
If that is not an option:
A lot of people have trouble flashing TWRP, so dont get discouraged. After flashing recovery you must immediately boot to recovery and flash root then choose reboot to recovery. You may see check boxes asking to install TWRP manager, choose yes and reboot to TWRP.
A Lot of times when things fail it is due to some silly such as forgetting to rename the file to twrp or recovery when your adb command looks like this: 1. fastboot flash recovery recovery.img or 2. fastboot flash recovery twrp.img my guess that this is your issue or its developer options not setup correctly. Again : ADB debugging must be enabled?
If your phone doesn't reboot in TWRP it may be overwritten by the ROM's recovery.
Unplug Your phone then Manually boot it into recovery
PS: Welcome to XDA, good manners when someone takes their time helping is to give thanks by clicking the thanks button. Don't say thanks click the button. See the signature. good luck.

Hi,
tsongming said:
Are you sure that you have developer options setup? ADB debugging is enabled?
Click to expand...
Click to collapse
Yes, I am. This is not the first time i switched to lineage /cyanogen mod. I already customized a Nexus 4 (mako), Motorola Moto G (falcon), Samsung Galaxy S4 (jfltexx), Samsung Galaxy Tab S2 (gts210vewifi)
and LG V20 (h990ds). So I'm not new to this.
tsongming said:
If you plan on staying on the stock rom that you are currently using you may need to flash DM verity. personally I prefer to use Orange Fox because it has DM verity built in.
once you are finally successful flash TWRP you might consider switching it. But be warned the layout takes some getting used to.
Click to expand...
Click to collapse
I see this in this subsection and i marked it already, since you suggest it i will try it as soon the flashing is working.
tsongming said:
Worst case scenario; If you are located in the US, I can do it for you. ( just send me a PM if you want me to do it)
I have provided this service for a lot of people, you pay shipping and buy me a beer. This will take no more than 10 minutes.
Click to expand...
Click to collapse
Sorry, Germany
tsongming said:
A Lot of times when things fail it is due to some silly such as forgetting to rename the file to twrp or recovery when your adb command looks like this: 1. fastboot flash recovery recovery.img or 2. fastboot flash recovery twrp.img my guess that this is your issue or its developer options not setup correctly. Again : ADB debugging must be enabled?
Click to expand...
Click to collapse
I don't see the point why the image must have a name with only characters, but i renamed the image to twrp.img and tried:
In Android with developer options enabled (and pc allowed):
Code:
adb reboot fastboot
Now i'm in fastboot and using my zsh on linux, im on my home directory located the twrp.img:
Code:
~ fastboot flash recovery twrp.img
Sending 'recovery' (42044 KB) OKAY [ 1.279s]
Writing 'recovery' OKAY [ 0.118s]
Finished. Total time: 1.402s
Now the command to upload and boot to the same image:
Code:
~ fastboot boot twrp.img
Sending 'boot.img' (42044 KB) OKAY [ 1.236s]
Booting OKAY [ 0.067s]
Finished. Total time: 1.341s
On device: bank screen (about 5 sec) > mi logo with unlocked symbol/text (about 3 sec) > mi logo with android symbol/text/animation (again about 3 sec) => I'm back on android.
Second try manual:
Code:
adb reboot fastboot
Flashing...
Code:
~ fastboot flash recovery twrp.img
Sending 'recovery' (42044 KB) OKAY [ 1.248s]
Writing 'recovery' OKAY [ 0.107s]
Finished. Total time: 1.360s
Unplug the phone, pressing now together VOLUME-UP and POWER until device going black and mi logo showing and devices vibrates. => mi logo with android symbol/text/animation (again about 3 sec) => I'm back on android.

Similar issue
I have the exact same issue. Did you manage to find a solution?

dojabato said:
I have the exact same issue. Did you manage to find a solution?
Click to expand...
Click to collapse
Sorry for the REALLY LATE REPLY. But no..... nothing worked... currently i also don't try either.

I found the solution
to-bu said:
Sorry for the REALLY LATE REPLY. But no..... nothing worked... currently i also don't try either.
Click to expand...
Click to collapse
Hello,
I was in the same case like you, to resolve this issue you must install this TWRP : TWRP-3.3.1-1031-XIAOMI8-Q+Version-CN
Sorry I'm new and can't post links...
I installed with the TOOL ALL IN ON => Erase all data => recovery flasher (check only automatic TWRP...) => POWER+Volume down => POWER+Volume up very quickly => Enjoy it !

cant patch Zip file.

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