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.
Related
Hey everyone!!
My device is stuck at boot logo.
If i try to open the recovery it also stuck on teamwin logo.
My device is totally unusable now.
please help!!
Thanks in advance.
shubhm said:
Hey everyone!!
My device is stuck at boot logo.
If i try to open the recovery it also stuck on teamwin logo.
My device is totally unusable now.
please help!!
Thanks in advance.
Click to expand...
Click to collapse
Try reflashing the TWRP recovery using fastboot. You can find the steps here.
LijoDXL said:
Try reflashing the TWRP recovery using fastboot. You can find the steps here.
Click to expand...
Click to collapse
Gives Mismatched partition size(recovery) error.
shubhm said:
Gives Mismatched partition size(recovery) error.
Click to expand...
Click to collapse
Mismatched partition size(recovery) should not be a problem, it just saying that your recovery is smaller in size than the stock recovery. Did you got this problem after downgrading from lollipop? As a trial and error thing, try to flash stock recovery and see if it boots.
LijoDXL said:
Mismatched partition size(recovery) should not be a problem, it just saying that your recovery is smaller in size than the stock recovery. Did you got this problem after downgrading from lollipop? As a trial and error thing, try to flash stock recovery and see if it boots.
Click to expand...
Click to collapse
Flashed stock recovery.
got this error in cmd
C:\Users\MOHIT\Desktop\ooo\mfastboot>mfastboot flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (10280 KB)...
OKAY [ 0.341s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 10.929s
and on booting in recovery same teamwin logo appears.
Try this command mfastboot flash partition gpt.bin (you must have the stock firmware in the directory)
shubhm said:
Flashed stock recovery.
got this error in cmd
C:\Users\MOHIT\Desktop\ooo\mfastboot>mfastboot flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (10280 KB)...
OKAY [ 0.341s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 10.929s
and on booting in recovery same teamwin logo appears.
Click to expand...
Click to collapse
try flashing whole stock 4.4.4 rom. and you didn't mention what you did (upgraded to lollipop/downgraded/ flashed any specific rom) which led to this problem.
zeshan94 said:
try flashing whole stock 4.4.4 rom. and you didn't mention what you did (upgraded to lollipop/downgraded/ flashed any specific rom) which led to this problem.
Click to expand...
Click to collapse
i had put my phone on charging. Then it itself got off. On pressing power button it was stuck on bootlogo.
I did a reset to factory using twrp with lollipop and the phone is stuck at moto logo... help please
LijoDXL said:
Mismatched partition size(recovery) should not be a problem, it just saying that your recovery is smaller in size than the stock recovery. Did you got this problem after downgrading from lollipop? As a trial and error thing, try to flash stock recovery and see if it boots.
Click to expand...
Click to collapse
i got the problem while downgrading from lollipop ...i tried flashing cm12.1 from 4.4.4 stock....but now i am stuck with the boot logo...help please!
Long story short, I managed to brick my Moto G when it was updated a rooted SuperSU app, by rebooting it when it became non-responsive.
At first after this, I couldn't get it to boot into TWRP, just fastboot. No factory reset, either.
Now, I can force it into TWRP, but still can't flash stock firmware, or factory reset.
When flashing stock firmware, it fails on the first command
Code:
mfastboot flash partition gpt.bin
With a
(bootloader) Preflash validation failed
FAILED (remote failure)
error, or something very similar. I can't remember the exact wording.
Is there anything I can do?
I am trying to get back to EMUI but so far everythig i tried has failed, so turning to you guys for advice.
this is for a Honor 9 (not lite)
I unlocked bootloader after paying 5 credits to DC unlocker
I flashed RR custom ROM from openKirin
I now want to get back to stock but all methods are failing
Tried dload method but getting error "update failed"
Tried recovery and downloading the firmware with firmware finder and messing with the DNS settings
Tried ADB method but getting the following error
(bootloader) Necessary to unlock FRP!
(bootloader) Navigate to Developer options, and enable "OEM unlock"!
FAILED (remote: 'Command not allowed')
Finished. Total time: 0.024s
my frp in bootloader is showing as locked and my OEM lock status is unlocked
Any help would be grately appreciated.
Have you tried installing the factory recovery rom B368 .. instructions are in the zip file
http://androidhost.ru/6er
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:
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?