So Im trying to flash stock unroted kernel to update to 12L.
I use Minimal ADB&Fastboot, newer had problem with it. And now I cannot flash boot image. I can boot it, but when flashing I get FAILED (remote: Error flashing partition : Device Error)...
Any one had problem like this?
Related
Hi, I do not know what to do. The system starts when I press "Start" from the bootloader.
Besides this, when I try to flash a stock rom I get this message:
"(bootloader) Preflash validation failed
FAILED (remote failure)"
thanks!!
Download a custom rom like CyanogenMod & flash it.
I have no idea what to do...
I was running July 18th's version of Cyanogen's Mod, my TZ Firmware was outdated, so I was not able to update to the new version of Cyanogen Mod 13 which supports the fingerprint scanner. So in order to update it, I would have to revert to EMUI, and the stock recovery. By mistake, before restoring to the stock OS, I restored to the stock recovery. In order to actually use the firmware update, I must have EMUI installed. So now I'm stuck, I can't install TWRP and revert because the FRP is locked. I have no idea how to unlock it. I don't have GApps installed so I can't add a google account (I believe I read that's what FRP lock is).
I'm a newbie when it comes to this and I'm in huge need of assistance, thank you all for your time.
i made the same mistake.....
you have to reinstall twrp , save stock recovery and stock rom on the external sd card .
fist you install the stock recovery , without restarting install the stock rom , wipe cache then restart phone
I am in a similar mess. I flashed the wrong build for my phone (KIW-UL00) and the FRP lock appeared (although the phone is rooted).
At this point adb does not recognize the device and fastboot cannot flash in stock recovery:
./fastboot flash recovery ~/Downloads/split_updata.pl/output/recovery.img
target reported max download size of 266338304 bytes
erasing 'system'...
ERROR: usb_read failed with status e00002e8
FAILED (status read failed (Undefined error: 0))
finished. total time: 0.001s
Huge mistake by HUAWEI - the 'forced upgrade' option they describe in the docs must never depend on the what is currently in the phone (system, boot or recovery).
I would like to flash the original recovery on my C432 with .120 on it.
I tried the .104 file but this does not work.
I am getting the ADB error
FAILED (remote: partition length get error)
who can help?
Solved myself adb command is now fastboot flash recovery_ramdisk !!!!
boris03 said:
I would like to flash the original recovery on my C432 with .120 on it.
I tried the .104 file but this does not work.
I am getting the ADB error
FAILED (remote: partition length get error)
who can help?
Click to expand...
Click to collapse
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:
Trying to build a custom TWRP for my phone using this guide, but pulling files from /system is locked behind root perms.
Attempting to use the magisk root method, yet I'm unable to write to the boot partition (even when using the stock image) whatsoever. Each attempt giving this error:
Writing 'boot' FAILED (remote: 'sparse image size span overflow.')
Tried specifying size (using -S), as well as erasing the partition before flashing (both with and without specifying size), each time giving the same error (wouldn't even work with the stock image, so i had to reflash using SP flash tool). Trying to flash from fastbootd instead gives:
Writing 'boot' FAILED (remote: 'Operation not permitted.')