twrp-3.3.1-0-mido.img installation error - Xiaomi Redmi Note 4 Questions & Answers

Hi, on this phone there was a Lineage 16 9.0, but for a problem I had to reset everything and miflash the rom again mido_global_images_V10.2.3.0.NCFMIXM_20190128.0000.00_7.0_global. It was to put the Gcam. Now I'm trying to start over and get the recovery twrp, but it always fails.
I've tried with Fastboot Tool and with platform-tools, but it always fails.
At the command 'fastboot devices' sees the phone, instead at the command 'fastboot flash recovery recovery.img' sees the recovery ok, but when it has to write it says 'FAILED (remote: 'Partition flashing is not allowed')'
How do I solve it?

Unlock bootloader after flashing MIUI stock ROM.
After that again attempt to install TWRP.

Related

When getting OTA for 5.0.1 showing error

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.

Soft brick while trying to flash TWRP

Hello to all !
In order to install Lineage OS on my Xiaomi Redmi Note 5, I was trying to flash TWRP as recovery. I was able to run successfully command 'fastboot flash antirbpass dummy.img' to skirt anti rollback, then i execute successfully 'fastboot flash recovery recovery.img' command to flash TWRP, but no way to boot on TWRP.
I tried also to run command 'fastboot boot recovery.img' but while booting it stays stucked on MI logo.
While searching for a solution I inconveniently run command 'fastboot flash boot recovery.img', so now I'm in a bootloop on fastboot mode if I press volume down and power button, or MI logo if I start in normal mode.
I still have access to fastboot commands, do you know how I can do to fix it (and maybe a way to install TWRP correctly) ?
And I can not stop my phone, does it exist a command which allows to do this in fastboot or I have to wait for my phone to be without battery ?
Thanks in advance for your help !
Ivanov93 said:
Hello to all !
In order to install Lineage OS on my Xiaomi Redmi Note 5, I was trying to flash TWRP as recovery. I was able to run successfully command 'fastboot flash antirbpass dummy.img' to skirt anti rollback, then i execute successfully 'fastboot flash recovery recovery.img' command to flash TWRP, but no way to boot on TWRP.
I tried also to run command 'fastboot boot recovery.img' but while booting it stays stucked on MI logo.
While searching for a solution I inconveniently run command 'fastboot flash boot recovery.img', so now I'm in a bootloop on fastboot mode if I press volume down and power button, or MI logo if I start in normal mode.
I still have access to fastboot commands, do you know how I can do to fix it (and maybe a way to install TWRP correctly) ?
And I can not stop my phone, does it exist a command which allows to do this in fastboot or I have to wait for my phone to be without battery ?
Thanks in advance for your help !
Click to expand...
Click to collapse
I guess you have Redmi note 5 - codename: Whyred (Snapdragon 636 and with dual rear camera) so Redmi 5 plus doesn´t have ARB.
If the next recommendation doesn´t work you will find better guidance in the thread for your specific device https://forum.xda-developers.com/redmi-note-5-pro so is slightly different.
Flash again your stock boot image , reboot and check that USB debugging is enabled and start again the process:
Put TWRP in your sdcard and a copy with this name in your adb folder into pc, reboot to fastboot and first just boot to TWRP, don´t flash it in fastboot, use code
Code:
fastboot boot TWRP.img
then in TWRP flash TWRP file and flash dummy.img ARB. In the case that your counter is up to 4 here you will find the file to enable again fastboot mode https://forum.xda-developers.com/redmi-note-5-pro/how-to/index-everything-anti-roll-t3816219
Ivanov93 said:
I still have access to fastboot commands, do you know how I can do to fix it (and maybe a way to install TWRP correctly) ?
Click to expand...
Click to collapse
I will assume that you have the correct TWRP build for your device (do you have vince, or whyred?).
If you have the correct TWRP, then did you flash magisk or lazyflasher after installing TWRP?
MAAAN
Do like this: once you flashed type
Fastboot boot recoveryname.img

H932 messed up TWRP restore HELP

H932 with Havok Pie, I don't use Gapps but wanted to get Gcam working so I flashed Open Gapps Pico. Decided I didn't want Gapps on the phone so I went to TWRP to restore a backup I made the previous day. I had backed up all partitions except the largest personal files partition. After running the restore it gave an error about /system (did not realize it may have just needed noverity or the other file flashed?). Did some searching and found that I could change the file system and that cleared it up for one person. Changed /system to FAT but then realized that would not support all the internal memory, so then went to EXT3 (couldn't find what it should be formatted to) it threw an error, so then I tried exFAT, that seemed to work BUT it then got stuck on "updating partitions" and would never finish, waited 10-15min. Only way to get out of TWRP was to hold all 3 buttons and it would power down the device.
So here I am now, I have TWRP in recovery and laf, except it's stuck on the teamwin boot logo. ADB does see the phone. Just read I can grab the twrp log file, attached.
hlp
"adb fastboot recovery" has not effect.
You could try fastboot boot TWRP.img
stays at "waiting for devices".
Doesn't H932 have little or no fastboot.
How is it that both twrp installs don't work (laf + recovery).
So it looks like there is some fastboot. When shutting down from the failed start of twrp, I'm given the options to Power Off or Restart at Fastboot Mode. "fastboot boot twrp.img" says downloading, then failed, says (remote: unknown command). "fastboot getvar unlocked" gives "unlocked: yes".
LGUP says "there is no handset".
Another guy had a similar (or exactly the same) problem, he used "fastboot oem lock", then "fastboot oem unlock". But didn't work for me.
Tried "fastboot erase system",
returns:
"Did you mean to fastboot format this ext4 partition?
erasing 'system'...
FAILED (remote: unknown command)
finished. total time: -0.000s"
tried: "fastboot format:ext4 system"
returns:
"CreateProcess failed: The system cannot find the file specified. (2)
error: Cannot generate image for system"
Is that because there are limited or no fastboot commands on the H932?
Would a battery disconnect do anything? Would going through the lafploit FUWL section help?
Don't have the phone anymore. Can anyone confirm, was noverity needed to get flashed after using twrp restore?

My son killed xiaomi mi a3

So I bought a son new phone.
As he told he installed magisk first, flashing "magisk_patched.img" through windows shell, everything was fine. Then He flashed twrp and magisk, everything was almost fine, he noticed that he cant play audio. He was trying to fix it first through installing magisk audio mods like viper and sauron. It didn't fixed anything, he unistalled it, everything was still in the same state, so he decided to flash stock frimware. He flashed through mi flashing tool, unfortunetaly It was image for "global xiaomi version" I mean "PFQMIXM" when as far as I know It should be "PFQEUXM". It didn't work and he was stuck in a bootloop. He found "MiUi 11 " image and for still unknown to me reason thought that it is going to fix everything. He flashed It again through mi flashing tool. It didn't work. He did that second time but at last he just closed the flashing tool while it was doing its thing.
At last he found eu firmware but now after all of that when i try to flash it or single files like crc list i get this:
flash crclist "E:\ModCR\adb\images\crclist.txt"
Sending 'crclist' (0 KB) FAILED (Write to device failed (Unknown error))
fastboot: error: Command failed
Device only boots to fastboot (no recovery/twrp either).
I tried erasing cache:
./fastboot erase cache
Erasing 'cache' FAILED (Write to device failed (Unknown error))
fastboot: error: Command failed
I tried to check slots:
./fastboot getvar active-slot
getvar:active-slot FAILED (Write to device failed (Unknown error))
Finished. Total time: 5.003s
I tried to change slot:
./fastboot set_active b
fastboot: error: Device does not support slots
When i typed "fastboot devices" It appeared as "??????"
./fastboot devices
???????????? fastboot
I don't know how to fix it, If anyone knows or has any kind of even small idea please write it down. I would be very greatfull.
Install custom recovery twrp
Install custom rom
Reboot
Download firmware EU
Install a firmware witch miflash
Restore Factory
Walaaaaa
xt610 said:
Install custom recovery twrp
Install custom rom
Reboot
Download firmware EU
Install a firmware witch miflash
Restore Factory
Walaaaaa
Click to expand...
Click to collapse
What i understand from op post is that fastboot commands are not working. So how will he flash twrp?
The firmware version doesn't matter at all you can flash EU on global and vice versa it doesn't matter.
What I think happened was your son never switched to slot 'a' before using mi flash.
Xiaomi's install script for miflash requires you to be on slot 'a' before flashing.
The only way to recover from this is edl mode which requires a xiaomi verified account to fix.
MOD EDIT: Part removed
Please do not advertise/recommend remote unlock services on XDA. Please read the FORUM RULES especially those:

Facing System Partition not found when flash OOS rom or GSI rom via fastboot

Hi, I'm trying to flash OOS rom on my phone, Curtana. But I got an error when flash it.
The Terminal facing System: (REMOTE: Partition not found).
And I'm stuck at fastboot, can't not boot system or to recovery.
Thanks for your help.
nhokloz105 said:
Hi, I'm trying to flash OOS rom on my phone, Curtana. But I got an error when flash it.
The Terminal facing System: (REMOTE: Partition not found).
And I'm stuck at fastboot, can't not boot system or to recovery.
Thanks for your help.
Click to expand...
Click to collapse
OOS ?!?!? is there OxygenOS for curtana?
where did you get it?
can i have a link or adress please...
javidman said:
OOS ?!?!? is there OxygenOS for curtana?
where did you get it?
can i have a link or adress please...
Click to expand...
Click to collapse
You can get here https://t.me/curtanacloud/472
I have found a solution. I flashed stock rom via MiFlash to have fastbootd (not fastboot). Then reboot to Bootloader and type 'fastboot reboot fastboot' to boot to fastbootd. Then I can flash any system.img I want.
Another method, but I've try yet.
1. Unlock bootloader
2. Flash LOS recovery
3. Boot bootloader
In CMD
4. Enter: 'fastboot reboot fastboot'
5. Then you will see 'fastbootd', enter 'fastboot flash system system.img' (system.img = gsi img)
6. enter 'fastboot reboot recovery'
In recovery
7. go to factory reset
8. select format data/factory reset then format data
9. then select reboot system

Categories

Resources