Hi guys.
I've already did some research but only found an image file I could flash to fix this Rotation problem so I sincerely hope that some of you could help me.
I've got the nice Redmi 4x with the V5.8.5 20170927 santoni final ROM and it works really great except the screen rotation. It's activated but simply don't work. Read some topics that more people have the problem but didn't find any solution yet. Only found an img file with some other files in an meta-inf and Firmware-Update folded but I am not able to flash this.
Besides that I have the question if you provide me a flashable image whether I will lose all my apps and settings of simply can flash it over my current image?
Is there someone who has the saving answer?
Thank you!!
Its the rom itself bug. try to calibrate sensors , hope it will work
Abhijitlucky3 said:
Its the rom itself bug. try to calibrate sensors , hope it will work
Click to expand...
Click to collapse
Hi, thanks for the reply! Too bad there is no fix for this... could you tell me in which menu setting I can calibirate the sensors?
Maybe any idea if the first one will fix it?
https://xiaomifirmware.com/guides-and-tips/fix-gyro-sensor-proximity-redmi-4x/
Tried it, but no luck:
C:\Fastboot>fastboot erase persist
erasing 'persist'...
FAILED (remote: 'erase' operation on partition persist is not allowed)
finished. total time: 0.004s
C:\Fastboot>fastboot flash persist persist.img
target reported max download size of 535822336 bytes
sending 'persist' (4716 KB)...
OKAY [ 0.163s]
writing 'persist'...
FAILED (remote: 'flash' operation on partition persist is not allowed)
finished. total time: 0.185s
Related
Hi,
Can someone help me with this error? While flashing Amon's recovery I get the below error.
sending 'recovery' (33 KB)... OKAY
writing 'recovery'... FAILED (remote: image error! (BootMagic check fail))
I have successfully unlocked my bootloader and rooted my Nexus One. Any help is appreciated.
vishalashah said:
sending 'recovery' (33 KB)... OKAY
Click to expand...
Click to collapse
Your download is corrupt. The recovery partition is far bigger than 33k
I recently had the same problem, hence why I found this post...
I had right clicked on Amon's link to download and also had a 33kb file. Make sure to follow the link and download from RapidShare.
Hope this helps
hello, i did get more than 33kb (24960 KB to be exact) but still get the same message
writing 'recovery' ... FAILED remote: image error! (BootMagic check fail))
thanks for the help in advance.
sorry...found the problem...please ignore. thanks
ergotune said:
hello, i did get more than 33kb (24960 KB to be exact) but still get the same message
writing 'recovery' ... FAILED remote: image error! (BootMagic check fail))
thanks for the help in advance.
sorry...found the problem...please ignore. thanks
Click to expand...
Click to collapse
But I can't find my problem....please help ~_~
---------------------------------------------------------------------------
C:\Program Files (x86)\Android\android-sdk-windows\platform-tools>fastboot flash
recovery radio.img
sending 'recovery' (26112 KB)... OKAY [ 3.682s]
writing 'recovery'... FAILED (remote: image error! (BootMagic check
fail))
finished. total time: 3.825s
Quoted from your post. Watch:
C:\Program Files (x86)\Android\android-sdk-windows\platform-tools>fastboot flash
recovery radio.img
Look closely at the 2 parts I've underlined. I hope you'll see the error. In case you don't - just look if they're the same word.
Wow. That is a huge and scary mistake, what if they had it the other way around and flashed the recovery to the radio. Yikes! Instant broken phone, and all because of a lack of understanding of what is actually going on.
I once saw a guy get hit by a car. I tried to put him in the recovery position, but put him in the radio position instead. Needless to say, he wasn't pleased... xD
Sent from my Nexus One using XDA App
The good thing is that fastboot checks for image integrity, and it would probably stop and not allow overwriting radio with different partition.
Jack_R1 said:
Quoted from your post. Watch:
C:\Program Files (x86)\Android\android-sdk-windows\platform-tools>fastboot flash
recovery radio.img
Look closely at the 2 parts I've underlined. I hope you'll see the error. In case you don't - just look if they're the same word.
Click to expand...
Click to collapse
Hi Guys, im having the same issue with my HOXL.
I read ur post and see the file should be bigger?
I downloaded TWRP from their download page, from the link on an XDA thread.
And its actually the same place i got it from last time, and that time it worked.
C:\Users\Compaq\Downloads\Android\PC Apps\OneXRoot>fastboot flash recovery openr
ecovery-twrp-2.2.2.0-endeavoru.img
sending 'recovery' (0 KB)...
OKAY [ 0.142s]
writing 'recovery'...
FAILED (remote: image error! (BootMagic check fail))
finished. total time: 0.175s
Click to expand...
Click to collapse
Any ideas?
Just another mirror: https://imagen.click/i/3def70.img
I tried to update my moto XT1097 AT&T locked version and it did not complete the update successfully. It goes until flashing the boot.img, failed and don't go any further. I supposed it is because it is a locked phone. After this, the phone went to a fastboot mod loop. Even If I tried to sideload the orignial rom or use the fsaboot comandts to restore the original rom it remains in this mode.
It generates a first error when I tried to issue the command "fastboot flash partition gpt.bin" returning this:
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.004s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.013s
And the phone display shows "hab check failed for primary_gpt"
I am issuing this command from the folder where the files of the original rom are located.
I tried to use a different gpt.bin file, from other ROMs and the same thing happen. I also tried another Lollipop ROM and not luck at all.
What I understand is that the gpt is the partion table that indicates where begins and where finish the diferent partitions into the phone, so I guess the problem could be resolve if I can change the gpt file into the phone for the original one.
I have tried to follow with the rest of the instalation but the motoboot and the boot files also are rejected and the system files are denied due an authentication problem.
The roms I have tried are:
ATT_XT1097_4.4.4_KXE21.187-38_cid1_CFC.xml
TMO_21.21.42.victara_tmo.tmo.en.US
4.4.4_to_5.0-11OTA
And the first one I used, which reach the same stage every time is:
RETBR_XT1097_5.0_LXE22.46-17_cid12_CFC.xml
I really appreciate any help and ideas you can give me to get my phne back to kitkat. I am not an expert but I am willing to do and learn what it takes
Did you solve this? How?
I am into this problem too. Any news?
I am leaving house for 2 weeks in 7 hours i realluy need help in flashing my phone I cant flash Vendor in fastboot
and i think it doesnt boot becxause of error flashing and erasing vendor
C:\Users\Matas Niewulis\Desktop\Pulpit>fastboot flash recovery twrp-3.1.1-2-v1-prague.img
target reported max download size of 471859200 bytes
sending 'recovery' (24468 KB)...
OKAY [ 0.855s]
writing 'recovery'...
OKAY [ 0.313s]
finished. total time: 2.042s
C:\Users\Matas Niewulis\Desktop\Pulpit>
C:\Users\Matas Niewulis\Desktop\Pulpit>fastboot flash erase vendor
error: cannot load 'vendor'
C:\Users\Matas Niewulis\Desktop\Pulpit>fastboot erase vendor
erasing 'vendor'...
FAILED (remote: Command not allowed)
finished. total time: 0.016s
C:\Users\Matas Niewulis\Desktop\Pulpit>fastboot reboot
rebooting...
finished. total time: 0.341s
C:\Users\Matas Niewulis\Desktop\Pulpit>
please help me fix my device.. sorry for a mess in this post, im in a hurry
ooooh **** i restored my device to working oreder by doing fix vendor partition in twrp..
but i still have the problem with fingerprint, security, dev options etc
Vendor you can flash only by twrp/ restoring.
Which firmware do you have?
Please see below, could someone please explain why I'm unable to flash vbmeta? -My understanding is that the 'FAILED (remote: Flashing is not allowed for partition
)' is due to a locked bootloader however mine is not.
[g-pc XZ2 setup]# fastboot devices
QV700SWU1B fastboot
[g-pc XZ2 setup]# fastboot oem unlock
FAILED (remote: Device already unlocked)
Finished. Total time: 0.023s
[g-pc XZ2 setup]# fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
target reported max download size of 536870912 bytes
Sending 'vbmeta' (2 KB)...
OKAY [ 0.003s]
Writing 'vbmeta'...
FAILED (remote: Flashing is not allowed for partition
)
Finished. Total time: 0.009s
[g-pc XZ2 setup]#
Click to expand...
Click to collapse
spirit-eh said:
Please see below, could someone please explain why I'm unable to flash vbmeta? -My understanding is that the 'FAILED (remote: Flashing is not allowed for partition
)' is due to a locked bootloader however mine is not.
Click to expand...
Click to collapse
Try to flash the newest pie firmware via newflasher on both sluts.
i have another huawei device, but not honor play.
Now the display can't show me anything even if I press the power button.
Then i connected my phone to my computer and i found that my phone had automatically booted bootloader without showing me anything on its display
i entered fastboot flash recovery recovery.img
it said failed remote command not allowes
i entered fastboot oem relock (password)
it said OKAY
i entered fastboot oem unlock (password)
it said OKAY
i entered fastboot flah boot boot.img
it said failed remote partition length get erro
i used hisuit but it failed when flashing recovery
So i can hardly do anything
how to deal with the problem?
pls help me
thank u
Post proper log.
Bootloader lock or unlock?
It seens that you are tring to flash wrong boot.img cause it shows that length error means boot.img size is higher than the actual partion is
Can you enter erecovery??
Nwereonye said:
Can you enter erecovery??
Click to expand...
Click to collapse
No. the phone cant show me anything. if i try to turn it off, it will restart.(according to my computer)
rajit said:
Post proper log.
Bootloader lock or unlock?
It seens that you are tring to flash wrong boot.img cause it shows that length error means boot.img size is higher than the actual partion is
Click to expand...
Click to collapse
I'm busy these days. I'll post the log some days later
rajit said:
Post proper log.
Bootloader lock or unlock?
It seens that you are tring to flash wrong boot.img cause it shows that length error means boot.img size is higher than the actual partion is
Click to expand...
Click to collapse
Today I download a package for my device from Firmware finder for Huawei. Then I used Huawei Update Extractor to extract some of the files and tried to flash them to my phone. But failed.
Here's the log
PS C:\WINDOWS\system32> fastboot devices
3CG4C16817019572 fastboot
PS C:\WINDOWS\system32> fastboot flash boot C:\Users\yyche\Desktop\update\BOOT.img
target reported max download size of 471859200 bytes
sending 'boot' (15494 KB)...
OKAY [ 0.400s]
writing 'boot'...
FAILED (remote: partition length get error)
finished. total time: 0.430s
PS C:\WINDOWS\system32> fastboot flash crc C:\Users\yyche\Desktop\update\CRC.img
target reported max download size of 471859200 bytes
sending 'crc' (161 KB)...
OKAY [ 0.006s]
writing 'crc'...
FAILED (remote: Command not allowed)
finished. total time: 0.017s
PS C:\WINDOWS\system32> fastboot flash fastboot C:\Users\yyche\Desktop\update
error: cannot load 'C:\Users\yyche\Desktop\update'
PS C:\WINDOWS\system32> fastboot flash fastboot C:\Users\yyche\Desktop\update\FASTBOOT.img
target reported max download size of 471859200 bytes
sending 'fastboot' (3128 KB)...
OKAY [ 0.081s]
writing 'fastboot'...
FAILED (remote: Command not allowed)
finished. total time: 0.092s
PS C:\WINDOWS\system32> fastboot flash recovery C:\Users\yyche\Desktop\update\RECOVERY.img
target reported max download size of 471859200 bytes
sending 'recovery' (35540 KB)...
OKAY [ 0.914s]
writing 'recovery'...
FAILED (remote: partition length get error)
finished. total time: 0.946s
PS C:\WINDOWS\system32> fastboot oem unlock 1**************4
...
FAILED (remote: already fastboot unlocked)
finished. total time: 0.004s
Do not flash the latest version, it seems u r tying to flash Android Pie. Try to flash Oreo (8.0) version of rom or the one that comes factory installed.