I got the OTA for 5.01 but when it go through the reboot process , it shows a error. I don;t know what it is so I try to flash the sys and boot img but I can't flash them either..........
Can anyone help........
What happens when you try to manually flash them? Does fastboot devices show tablet connected?
di11igaf said:
What happens when you try to manually flash them? Does fastboot devices show tablet connected?
Click to expand...
Click to collapse
When I try to flash the boot img I got this "FAILED (remote: image error! (BootMagic check fail))"
And also when I try to flash sys img it shows
" fastboot: ../libsparse/sparse.c:143: write_all_blocks: Assertion `pad >= 0' failed.
Aborted "
Weird...
Me too
I'm having the same error as you. When I tried to update the Standart way the error appeared. I tried via sideload and It didn't work either. I tried Rooted, unrooted, both ways fail.
Anybody help please
Hi, I just got the OTA and after make a complete unroot with supersu I have the same problem, OTA error with the lay android and a red triangle.
Any ideas?
Thanks
Jarvia_STGL said:
When I try to flash the boot img I got this "FAILED (remote: image error! (BootMagic check fail))"
Click to expand...
Click to collapse
With latest version of fastboot and lrx22c rom completely unzipped I did the following and it fixed my stuck at "Google" Nexus 9 that also had the bootmagic issue:
fastboot flash bootloader bootloader-flounder-3.43.0.0114.img
fastboot reboot-bootloader
fastboot erase system
fastboot erase recovery
fastboot erase cache
fastboot erase boot
fastboot erase userdata
fastboot erase vendor
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash boot boot.img
fastboot flash vendor vendor.img
fastboot flash userdata vendor.img
select hboot
factory reset
Not sure the 'fastboot flash userdata vendor.img' is needed here, but it worked so do with this info what you will.
Thank you this helped me get mine running again.
Related
Hello,
I have problem with flashing stock firmware on my atrix 4g.
RSD -lite return error:
Failed flashing process. Unable to retrieve interface handle. (0x7027).
Thats happens when I would go back to stock firmware from CM7.
Before running RSD flashing, I was execute following fastboot commands:
fastboot erase boot
fatsboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot erase cache
fastboot erase osh
fastboot erase logo
fastboot erase radio
Before 2-3 times mentioned above method without erase radio commands not return any errors with RSD flashing. And have not any problem.
Can anybody advice and help me ?
Thanks for help and advice.
Solved
alcpis said:
Hello,
I have problem with flashing stock firmware on my atrix 4g.
RSD -lite return error:
Failed flashing process. Unable to retrieve interface handle. (0x7027).
Thats happens when I would go back to stock firmware from CM7.
Before running RSD flashing, I was execute following fastboot commands:
fastboot erase boot
fatsboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot erase cache
fastboot erase osh
fastboot erase logo
fastboot erase radio
Before 2-3 times mentioned above method without erase radio commands not return any errors with RSD flashing. And have not any problem.
Can anybody advice and help me ?
Thanks for help and advice.
Click to expand...
Click to collapse
Solved !
1. Copy Radio image (baseband) to the folder where located fastboot.
2. Power on phone and select fastboot
3. execute: fastboot flash radio bp.img, Where bp.img baseband image files
4. execute: fastboot reboot
5. Phone automatically boot on the android recovery mode
6. Wipe userdata/cache
7. Reload in RSD mode
8. on the RSD lite browse appropriate .sbf file and puch Start
Thats all.
Thanks.
alcpis said:
Solved !
1. Copy Radio image (baseband) to the folder where located fastboot.
2. Power on phone and select fastboot
3. execute: fastboot flash radio bp.img, Where bp.img baseband image files
4. execute: fastboot reboot
5. Phone automatically boot on the android recovery mode
6. Wipe userdata/cache
7. Reload in RSD mode
8. on the RSD lite browse appropriate .sbf file and puch Start
Thats all.
Thanks.
Click to expand...
Click to collapse
Can you be a bit more specific on syntax used. I have the atrix baseband img in the fastboot folder and all is good but I get a "cannot load" error. The name of the baseband img file is baseband_OTA.img So with that in mind how would my commands look? I have typed fastboot flash radio baseband.img. I get the error saying it cannot load the file.
EDIT: Noob to flashing stock images here. Need help on how to get the image to install on the device. This is my first ever Nexus device
So there's a new 5.0.1 system image out. I'm rooted, and I remember reading somewhere that the official OTA process won't work if you have modifications to the System partition.
So, I just want to check what I should do. Thanks.
Fastboot flash the images. Then reroot.
Awesome. I'm new to fastboot, and this is my first Nexus device. What is the procedure for flashing an official System image with fastboot?
TenderloinShadow said:
Awesome. I'm new to fastboot, and this is my first Nexus device. What is the procedure for flashing an official System image with fastboot?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=56921581&postcount=33
That post left out flashing recovery. The download should have 6 files. I flashed recovery at the end (but I don't think it matters how you flash the files, I could be wrong though).
See link above, then you might as well just flash twrp recovery instead of factory recovery, then flash this SuperSU zip through recovery and you'll be rooted and updated.
Order of flash doesn't matter, and I wouldn't flash boot loader unless necessary.
di11igaf said:
See link above, then you might as well just flash twrp recovery instead of factory recovery, then flash this SuperSU zip through recovery and you'll be rooted and updated.
Order of flash doesn't matter, and I wouldn't flash boot loader unless necessary.
Click to expand...
Click to collapse
I had TWRP installed before loading up these images. I decided to not flash recovery.img thinking I would be okay; but when I tried to reboot into twrp, I soft bricked. So I would still install the recovery.img first and then twrp. Everything is working properly now.
ericplatham said:
I had TWRP installed before loading up these images. I decided to not flash recovery.img thinking I would be okay; but when I tried to reboot into twrp, I soft bricked. So I would still install the recovery.img first and then twrp. Everything is working properly now.
Click to expand...
Click to collapse
You're right, now that I think about it, I believe I had to do that as well last time I flashed a factory image.
I am unlocked, rooted and have custom recovery.... what is the procedure? Is fastboot the only way?
GatorsUF said:
I am unlocked, rooted and have custom recovery.... what is the procedure? Is fastboot the only way?
Click to expand...
Click to collapse
maybe I'll write up a guide, but download the factory image, extract it. In there is a zip file, extract it too. Then Google 15 second adb install xda. That'll set up fastboot on your pc. Then boot into the bootloader and in a command window opened in the folder where the bootloader image is located run the commands:
fastboot flash bootloader bootloader.img. Note, use the full name of the bootloader.img
fastboot reboot-bootloader
fastboot -w
Open the folder where the boot, system, cache, system, and vendor images are located. Open a command window in that folder and run the commands:
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash vendor vendor.img
fastboot flash system system.img
Then you're done
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Then you're done
Click to expand...
Click to collapse
He will still have to reroot and flash custom recovery... but you got 95% of the process :laugh:
So we have to go through this for updates rather than flashing a modified firmware, eh? damn
rank78 said:
So we have to go through this for updates rather than flashing a modified firmware, eh? damn
Click to expand...
Click to collapse
Since its a small update you could probably get by just flashing the system and boot images. But I haven't tried it
Sent from my Nexus 5 using XDA Free mobile app
I'd flash everything as described to be safe, I just prefer simply flashing a zip and moving on.
Will updating thru adb wipe my device?
GatorsUF said:
Will updating thru adb wipe my device?
Click to expand...
Click to collapse
You're using thru fastboot, not adb. They're different. But to answer your question the command fastboot -w does wipe your device. You could try it without that command but it may cause problems. Back your device up to Google first. Google had gotten really good at restoring the device after a flash.
You could also try just flashing the system and boot images, run those fastboot commands only and not the other ones. It should update to 5.0.1 without a problem.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
You're using thru fastboot, not adb. They're different. But to answer your question the command fastboot -w does wipe your device. You could try it without that command but it may cause problems. Back your device up to Google first. Google had gotten really good at restoring the device after a flash.
You could also try just flashing the system and boot images, run those fastboot commands only and not the other ones. It should update to 5.0.1 without a problem.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks, I have actually flashed a few times thru fastboot in the past so I'm not totally lost on the idea. I've always used tibu in the past, will Google restore my data too?
TenderloinShadow said:
EDIT: Noob to flashing stock images here. Need help on how to get the image to install on the device. This is my first ever Nexus device
So there's a new 5.0.1 system image out. I'm rooted, and I remember reading somewhere that the official OTA process won't work if you have modifications to the System partition.
So, I just want to check what I should do. Thanks.
Click to expand...
Click to collapse
Drag and Drop or Copy/Paste Images to {}
STEP #1
fastboot flash bootloader {bootloader.img}
fastboot reboot-bootloader
Step #2
fastboot erase recovery
fastboot format system
fastboot erase boot
fastboot format vendor
fastboot format cache
fastboot erase userdata {optional}
Step#3
fastboot flash recovery {recovery.img}
fastboot flash system {system.img}
fastboot flash boot {boot.img}
fastboot flash vendor {vendor.img}
fastboot flash cache {cache.img}
fastboot reboot-bootloader
Step #4
fastboot erase recovery
fastboot flash recovery {TWRP.img}
Step #5
got to TWRP recovery flash latest super su
reboot done enjoy
thanks @prdog1
fhem said:
Drag and Drop or Copy/Paste Images to {}
STEP #1
fastboot flash bootloader {bootloader.img}
fastboot reboot-bootloader
Step #2
fastboot erase recovery
fastboot format system
fastboot erase boot
fastboot format vendor
fastboot format cache
fastboot erase userdata {optional}
Step#3
fastboot flash recovery {recovery.img}
fastboot flash system {system.img}
fastboot flash boot {boot.img}
fastboot flash vendor {vendor.img}
fastboot flash cache {cache.img}
fastboot reboot-bootloader
Step #4
fastboot erase recovery
fastboot flash recovery {TWRP.img}
Step #5
got to TWRP recovery flash latest super su
reboot done enjoy
thanks @prdog1
Click to expand...
Click to collapse
Why erase recovery twice?
Just dont flash stock recovery
fhem said:
STEP #1
fastboot flash bootloader {bootloader.img}
Click to expand...
Click to collapse
Help, I'm getting the folllowing error message: error: cannot determine image filename for bootloader-flounder-3.43.0.0114.img
and now I'm stuck. I've not done this in ages but couldn't wait and now I don't know what to do.
Double_U said:
Help, I'm getting the folllowing error message: error: cannot determine image filename for bootloader-flounder-3.43.0.0114.img
and now I'm stuck. I've not done this in ages but couldn't wait and now I don't know what to do.
Click to expand...
Click to collapse
Hi, Double_U...
Are you sure you've typed the EXACT command..?
Code:
fastboot flash bootloader bootloader-flounder-3.43.0.0114.img
Reboot the bootloader, enter fastboot, and try again.
Rgrds,
Ged.
Hello. I wanted to flash a stock ROM on my Xiaomi Mi3 (Not Mi3W) and I downloaded an official stock ROM and flashed it using Fastboot.
Here's where I think I messed up. I used the "fastboot erase userdata" on the phone and when it booted up, The system storage is showing fine when I go to settings > storage but the internal storage is showing up as 0.00b and I cannot install any applications.
I've tried reflashing but nothing is working. Any ideas on how I can get it to work? Thanks.
Try to flash again with fastboot but with following comands:
Enter the following commands below by order:
fastboot erase cache
fastboot erase userdata
fastboot erase system
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot reboot-bootloader
boot.img ,recovery.img and system.img it should be inside your stock firmware.
Teddy Lo said:
Try to flash again with fastboot but with following comands:
Enter the following commands below by order:
fastboot erase cache
fastboot erase userdata
fastboot erase system
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot reboot-bootloader
boot.img ,recovery.img and system.img it should be inside your stock firmware.
Click to expand...
Click to collapse
After much Googling, I was finally able to 'reset' the whole android partition system by flashing a CWM recovery, booting into it, and using ADB to fix it all.
Thank you for bothering to reply my at all. You're amazing.
You Welcome
Hi, Android 9.0 for Albus is available here >> Direct Download <<
Just install with ADB Fastboot
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash system system.img_sparsechunk.12
fastboot flash oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase carrier
fastboot erase DDR
fastboot reboot
Ps: Clean Install is recommend
(Retail version)
Enjoy!!!
I'AM NOT RESPONSIBLE IF YOUR CELLPHONE TURNS IN A BRICK AFTER THIS PROCESS
I think you have to do a twrp backup and then restore it.it's strange but works
Inviato dal mio GT-N5120 utilizzando Tapatalk
can we use this update for the Indian version of Z2play, software channel: RETIN. Bootloader: locked. if yes, then is there any problem with the mobile network?
JulioCeesarC said:
Hi, Android 9.0 for Albus is available here >> Direct Download <<
Just install with ADB Fastboot
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash system system.img_sparsechunk.12
fastboot flash oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase carrier
fastboot erase DDR
fastboot reboot
Ps: Clean Install is recommend
(Retail version)
Enjoy!!!
I'AM NOT RESPONSIBLE IF YOUR CELLPHONE TURNS IN A BRICK AFTER THIS PROCESS
Click to expand...
Click to collapse
I blindly flashed the above mentioned pie rom on my moto z2 play xt1710-02 it flashed gpt and bootloader and failed the rest of the commands returned with errors
Now stuck at fastboot mode warning of startup failed @JulioCeesarC
Please help me get out of here
Bootloader is locked and i was at latest oreo update probably ods27.12-42-14
I also tried to flash above oreo image but it returns with error saying security downgrade
junejo46726 said:
I blindly flashed the above mentioned pie rom on my moto z2 play xt1710-02 it flashed gpt and bootloader and failed the rest of the commands returned with errors
Now stuck at fastboot mode warning of startup failed @JulioCeesarC
Please help me get out of here
Bootloader is locked and i was at latest oreo update probably ods27.12-42-14
I also tried to flash above oreo image but it returns with error saying security downgrade
Click to expand...
Click to collapse
try to install 8.0 again and after that unlock bootloader and try to install 9.0 again with bootloader unlocked
ghost.deathrider said:
can we use this update for the Indian version of Z2play, software channel: RETIN. Bootloader: locked. if yes, then is there any problem with the mobile network?
Click to expand...
Click to collapse
I recomend bootloader unlocked for this process
junejo46726 said:
Hi, Android 9.0 for Albus is available here >> Direct Download <<
Just install with ADB Fastboot
I blindly flashed the above mentioned pie rom on my moto z2 play xt1710-02 it flashed gpt and bootloader and failed the rest of the commands returned with errors
Now stuck at fastboot mode warning of startup failed @JulioCeesarC
Please help me get out of here
Bootloader is locked and i was at latest oreo update probably ods27.12-42-14
I also tried to flash above oreo image but it returns with error saying security downgrade
Click to expand...
Click to collapse
Before you unlock:
Try fastboot "Boot" TWRP, if you can, it might be possible to use one of the TWRP backups to fix your phone. There is another thread with TWRP backups of stock.
If successful boot, restore system partition last and separately.
XT1710-09 bootloader unlocked, installed 9.0 without any issue! Everything ok with twrp-3.2.3-0-albus recovery, but got bootloop trying to root with Magisk 20.0. Any tip?
kain83 said:
XT1710-09 bootloader unlocked, installed 9.0 without any issue! Everything ok with twrp-3.2.3-0-albus recovery, but got bootloop trying to root with Magisk 20.0. Any tip?
Click to expand...
Click to collapse
did you try cleaning your cache? I used 19.3.
kewlzter said:
did you try cleaning your cache? I used 19.3.
Click to expand...
Click to collapse
I didn't indeed. I'm gonna give it a try, thanks
EDIT: it works!! So installed 19.3 version and wiped cache/dalvik, then reboot. So far so good, many thanks!!
keeps saying waiting for device
hindraftv said:
keeps saying waiting for device
Click to expand...
Click to collapse
Phone is either not connected, or in the wrong mode.
Make sure the phone is in Boot Loader. Unplug and replug USB.
ghost.deathrider said:
can we use this update for the Indian version of Z2play, software channel: RETIN. Bootloader: locked. if yes, then is there any problem with the mobile network?
Click to expand...
Click to collapse
Yes, i tried both the US version and the Brazil version and the Brazil version works. I'm on Vodafone India and everything works perfectly fine on android pie.
However, after several trials and errors, I realized there are two commands that you shouldn't run when flashing pie on the Indian variant. They are:
1) flashboot erase userdata
2) flashboot erase carrier
Special Thanks to @Junior Passos
reallydan said:
Yes, i tried both the US version and the Brazil version and the Brazil version works. I'm on Vodafone India and everything works perfectly fine on android pie.
However, after several trials and errors, I realized there are two commands that you shouldn't run when flashing pie on the Indian variant. They are:
1) flashboot erase userdata
2) flashboot erase carrier
Special Thanks to @Junior Passos
Click to expand...
Click to collapse
Clean flash or dirty flash?
rayudu123 said:
Clean flash or dirty flash?
Click to expand...
Click to collapse
Clean flash
reallydan said:
Clean flash
Click to expand...
Click to collapse
Is it possible to flash indian pie version after release of pie in india??? Or do we face any problem in flashing??
Everything works except dark theme. Any fix?
kewlzter said:
Phone is either not connected, or in the wrong mode.
Make sure the phone is in Boot Loader. Unplug and replug USB.
Click to expand...
Click to collapse
It is connected.. I have Moto Z2 Play - Build Number OPSS27.76.12-42-13 (Baseband M8953P_50.59.07.96 ALBUS_NA_CUST_
are you able to provide step by step guide, if you don't mind
hindraftv said:
It is connected.. I have Moto Z2 Play - Build Number OPSS27.76.12-42-13 (Baseband M8953P_50.59.07.96 ALBUS_NA_CUST_
are you able to provide step by step guide, if you don't mind
Click to expand...
Click to collapse
Why sure...
Step 1: you get yourself a usb cable.
Step 2: you plug one end into your computer.
Step 3: plug the other end into your phone..
glad to help
kewlzter said:
Before you unlock:
Try fastboot "Boot" TWRP, if you can, it might be possible to use one of the TWRP backups to fix your phone. There is another thread with TWRP backups of stock.
If successful boot, restore system partition last and separately.
Click to expand...
Click to collapse
I also tried but fastboot saying can not load twrp @JulioCeesarC
I would like to share my experienced how to unbricked my phone that stock on fastboot mode.why my phone is brick? The reason why my phone brick just because i restore the wrong system with the other vendor from china to miuimix and after restore it, it stock on fastboot mode unable to recover backup or to load in recovery mode. It didn't also turn off. l try to use miflash tool but it didn't work because of authorization not match to my phone, i tried other fastboot rom but it didnt work.. Try to boot twrp using fastboot boot but it didn't show any. I came up with the idea to flash. Img using cmd into the system that i restore, begin with the boot.img nothing will happen. Until i flash the vbmeta.img, then it begin to show boot img and eventually access twrp. I wiped everything and flash again a brandnew rom miui12 and it works well now.. Hope it will help to others to have an idea to unbrick there phone. ☺☺☺
flamedrops said:
I would like to share my experienced how to unbricked my phone that stock on fastboot mode.why my phone is brick? The reason why my phone brick just because i restore the wrong system with the other vendor from china to miuimix and after restore it, it stock on fastboot mode unable to recover backup or to load in recovery mode. It didn't also turn off. l try to use miflash tool but it didn't work because of authorization not match to my phone, i tried other fastboot rom but it didnt work.. Try to boot twrp using fastboot boot but it didn't show any. I came up with the idea to flash. Img using cmd into the system that i restore, begin with the boot.img nothing will happen. Until i flash the vbmeta.img, then it begin to show boot img and eventually access twrp. I wiped everything and flash again a brandnew rom miui12 and it works well now.. Hope it will help to others to have an idea to unbrick there phone.
Click to expand...
Click to collapse
Could you explain? My phone is stuck at fastboot and my pc doesn't detect the phone.
if u could access your phone via fastboot / adb then it wasn't a hardbrick , just a softbrick
TahmidZee said:
Could you explain? My phone is stuck at fastboot and my pc doesn't detect the phone.
Click to expand...
Click to collapse
You should check first the driver of your computer. Make sure you have the driver of your phone to your computer. After that you can check your device via adb by using commnd on cmd "adb devices".
instructions to flash:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot erase recovery
fastboot flash recovery twrp-3.3.1-0-davinci.img
link: https://dl.twrp.me/davinci/twrp-3.3.1-0-davinci.img
w595shubham said:
instructions to flash:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot erase recovery
fastboot flash recovery twrp-3.3.1-0-davinci.img
link: https://dl.twrp.me/davinci/twrp-3.3.1-0-davinci.img
Click to expand...
Click to collapse
VERY VERY THANX A LOT MAN...THX THX THX:highfive:
flamedrops said:
I would like to share my experienced how to unbricked my phone that stock on fastboot mode.why my phone is brick? The reason why my phone brick just because i restore the wrong system with the other vendor from china to miuimix and after restore it, it stock on fastboot mode unable to recover backup or to load in recovery mode. It didn't also turn off. l try to use miflash tool but it didn't work because of authorization not match to my phone, i tried other fastboot rom but it didnt work.. Try to boot twrp using fastboot boot but it didn't show any. I came up with the idea to flash. Img using cmd into the system that i restore, begin with the boot.img nothing will happen. Until i flash the vbmeta.img, then it begin to show boot img and eventually access twrp. I wiped everything and flash again a brandnew rom miui12 and it works well now.. Hope it will help to others to have an idea to unbrick there phone.
Click to expand...
Click to collapse
Can u please explain it. I am stuck with the same problem. I got success in flashing fastboot rom via miflash tool but it's still stuck in fastboot.
Thanks God Bless You.
---------- Post added at 05:01 PM ---------- Previous post was at 04:36 PM ----------
Deaddo6 said:
VERY VERY THANX A LOT MAN...THX THX THX:highfive:
Click to expand...
Click to collapse
This Helped You guys are angel
w595shubham said:
instructions to flash:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot erase recovery
fastboot flash recovery twrp-3.3.1-0-davinci.img
link: https://dl.twrp.me/davinci/twrp-3.3.1-0-davinci.img
Click to expand...
Click to collapse
I have the same problem. I tried also this one, but nothing.
Everything goes ok in CMD, but when I type:
fastboot boot twrp.img
I get:
FAILED (remote: Failed to load/authenticate boot image: Load Error)
I still can't go in Recovery, neither turn off the phone. How solve this?!
dix93 said:
I have the same problem. I tried also this one, but nothing.
Everything goes ok in CMD, but when I type:
flash boot twrp.img
I get:
FAILED (remote: Failed to load/authenticate boot image: Load Error)
I still can't go in Recovery, neither turn off the phone. How solve this?!
Click to expand...
Click to collapse
flash boot twrp.img?
What do you wanna do?
If you want to boot into TWRP it should be
Code:
fastboot boot recovery "name-of- recovery.img"
If you want to flash TWRP it should be
Code:
fastboot flash recovery "name-of-recovery.img"
Your command
fastboot flash boot twrp.img should flash the recovery image over the boot image?
If you want to boot into twrp you should use the command above.
As far as I know not every device/firmware is able to boot into TWRP. It seems other users were able to do so with a mi 9t so my advice would be:
- Try another usb port / cable.
- Check twice if you renamed the twrp image correctly
- Try another twrp version (older one or unofficial)
w595shubham said:
instructions to flash:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot erase recovery
fastboot flash recovery twrp-3.3.1-0-davinci.img
link: https://dl.twrp.me/davinci/twrp-3.3.1-0-davinci.img
Click to expand...
Click to collapse
Wolfcity said:
flash boot twrp.img?
What do you wanna do?
If you want to boot into TWRP it should be
Code:
fastboot boot recovery "name-of- recovery.img"
If you want to flash TWRP it should be
Code:
fastboot flash recovery "name-of-recovery.img"
Your command
fastboot flash boot twrp.img should flash the recovery image over the boot image?
If you want to boot into twrp you should use the command above.
As far as I know not every device/firmware is able to boot into TWRP. It seems other users were able to do so with a mi 9t so my advice would be:
- Try another usb port / cable.
- Check twice if you renamed the twrp image correctly
- Try another twrp version (older one or unofficial)
Click to expand...
Click to collapse
Thank you. Actually I was confused in the transcript here, I meant fast boot instead of flash.
But I figured out to use XiaomiFlash Tool to install a ROM via fastboot, and then reinstall a recovery.
The popup camera is not working good with the XIAOMI official rom (It tries to close the cam even if it is already closed). Now I'm trying to install Havoc OS to try to solve those problem, but it demands me the miui v11.0.4 or new (error in twrp), even if I have the miui v12.... trying to figure out why
for the guys whome are stuck on fastboot, you may try "XiaoMiTool V2". this bought my Mi9T from fastboot to life.
make sure all the drivers are installed as well. what's better is install usb drivers, reboot computer, enable usb debugging, connect the phone to computer, select transfer data, wait till the computer completely setup your phone, turn off phone and connect to computer, wait till computer detects and setup, put the phone on fastboot mode and connect, check whether computer shows android device... once everything are confirmed then proceed with flasing.. :good::good:
w595shubham said:
instructions to flash:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot erase recovery
fastboot flash recovery twrp-3.3.1-0-davinci.img
link: https://dl.twrp.me/davinci/twrp-3.3.1-0-davinci.img
Click to expand...
Click to collapse
This command - fastboot flash vbmeta worked.
(using a version from Redispade for Grus - mi9se)
Unbricked my bootloop (recovery) after upgrading from miui 12 (android 10) to 12.5 android 11.
thanks!