Soft-locked my phone? - Honor 6X Questions & Answers

Help me out here.
Basically, my situation is like this:
Recovery: Doesn't work, when i boot to recovery an error message like this appeared:
ERROR MODE
Attention!
Please update system again
*green android guy*
Error!
Func NO: 11 (recovery image)
Error NO: 2 (load failed)
Fastboot:
works, but flashing anything but openkirin's lineage os and the kernel results into this error:
FAILED (remote partition length get error)
Normal boot: goes to erecovery
i dont know what to do now, someone help me

Related

Stuck on HTC black screen.

Can't boot into stock ROM after RUU 1.56 and getting the 110 error. I am able to boot if I use fastboot oem boot however. I've been able to get to the Ramon-recovery and I've attempted to flash a new ROM several times. I have downloaded new copies of the RUU and the ROMs and still a no go. After it flashes it starts to reboot but then just shuts off and I have to take the battery out. I've followed the guide to fix the 110 error in thread by dfbonney. Of course I never did a nandroid backup, but when following the guide I can't flash the boot section I get
Code:
#
flash_image boot /sdcard/boot.img
mtd: erase failure at 0x000a0000 (I/O error
mtd: erase failure at 0x000a0000 (I/O error
mtd: skipping write block at 0x000a0000
error writing boot: No space left on device
Help?

help me

Rescue-mode
Attention, please update System again.
Func No: 9 (FUNC_BOOT_KERNEL)
Error NO : 2
When I want to enter the recovery with power button and volume up, there is also a error message as following:
Func No : 10 (FUNC_BOOT_RECOVERY)
Error No: 2
mate 7
iopen boot loder

failed (status malformed (1 bytes) srk tool

i have a problem when i use srk tool to unlock bootloader on my mate 8 nxt-l29
it fail and write " failed (status malformed (1 bytes) "
how can i solve it ?
and another thing was happen to me ... when i installed twrp it Requests password when i open twrp to install nougat update.zip

ERROR: LoadImageAndAuth Failed: Load Error on slot b

Whenever I boot on slot b it restarts to boot loader and ERROR: LoadImageAndAuth Failed: Load Error message appears. I have tried a full flash with factory image and deuces boot-loop script. I am on Oreo 8.1 opm2.171026.006.g1. Is slot b bootable or is it just for updates ? I also have a ph-1 is the slot system same or a little different ?

Question Stock recovery error: SamMobile firmware footer is wrong; signature verification failed

Samsung recovery
Code:
samsung a12zh/a12
10/QP1A.190711.020/A125FZHU1AYC3
user/release/keys
Install /sdcard/A12/stock/A125FXXU1AUC3_A125FOLM1AUC3_XSA.zip ...
Finding update package ...
Opening update package ...
Verifying update package ...
E: Footer is wrong
Update pkacage verification took 0.1s (result 1).
E: Signature verification failed
E: Error 21
Install from SD card completed with status 2.
Installation aborted. #1
PNG and TGY were also failed like is, but if reflashing stock ROM using Heimdall, which partitions are to be flashed accoring to the PIT on my A12? And which partitions should never be touched?
Even with successful flashes using Heimdall, it still always reports to me SW REV check failed
Now my device is still being boot-looped, and on either YouTube or online text tutorials nothing is about solving the boot loops for my A12
And have also retried to flash my own builds of TWRP instead, https://sourceforge.net/p/twrp-samsung-a12/code/ci/master/tree/out/target/product/a12, however also unfortunately somewhy,
Code:
Heimdall mode (High speed)
Product name: SM-A125F
...
Warranty void: 0x1 (0x500)
RP SWREV: B1 NS1 K1 S1
...
SW REV check fail: [recovery] Fused 1 > Binary 2
SW REV check fail: [boot]Fused 1 > Binary 0
Me again.. Ive obtained the same problem and solved it just reflashing my whole firmware with Odin u_u
I’ve just flashed the full firmware.
The SW REV check failures were fixed, but my device is still being boot looped
What to do next?
My A12 has MTK chipsets (according to my CPU-Z), hence also their ‘‘secure’’ boot locks, now going to unlock it by their SPFlashTool
speedmetal444 said:
Me again.. Ive obtained the same problem and solved it just reflashing my whole firmware with Odin u_u
Click to expand...
Click to collapse
Heimdall flashes are always by PIT partitions; PIT means partitioning informative tables
Odin flashes, on the other hand, are instead more by tar packages, namely BL, AP, CP, and CSC
* BL = BootLoaders; AP = Android PDA’s i.e. systems with also recoveries; CP = Core PDA’s i.e. modems; CSC = Country support codes or Consumer software customizations
I’m still being boot looped due to sth in unknown errors named PDP
Code:
Android recovery
samsung/a12nsxx/a12
11/RP1A.200720.012/A125FXXU1BUE3
...
Supported API: 3
# MANUAL MODE v1.0.0#
No commands specified
-- Wiping data ...
Formatting /data ...
E: [PDP] lstat /c___/pdp_b__: 0 - No PDP scenario
Formatting /cache ...
Formatting /metadata ...
Formatting /keydata ...
Formatting /keyrefuge ...
Data wipe complete.
hd_scania said:
Samsung recovery
Code:
samsung a12zh/a12
10/QP1A.190711.020/A125FZHU1AYC3
user/release/keys
Install /sdcard/A12/stock/A125FXXU1AUC3_A125FOLM1AUC3_XSA.zip ...
Finding update package ...
Opening update package ...
Verifying update package ...
E: Footer is wrong
Update pkacage verification took 0.1s (result 1).
E: Signature verification failed
E: Error 21
Install from SD card completed with status 2.
Installation aborted. #1
PNG and TGY were also failed like is, but if reflashing stock ROM using Heimdall, which partitions are to be flashed accoring to the PIT on my A12? And which partitions should never be touched?
Even with successful flashes using Heimdall, it still always reports to me SW REV check failed
Now my device is still being boot-looped, and on either YouTube or online text tutorials nothing is about solving the boot loops for my A12
And have also retried to flash my own builds of TWRP instead, https://sourceforge.net/p/twrp-samsung-a12/code/ci/master/tree/out/target/product/a12, however also unfortunately somewhy,
Code:
Heimdall mode (High speed)
Product name: SM-A125F
...
Warranty void: 0x1 (0x500)
RP SWREV: B1 NS1 K1 S1
...
SW REV check fail: [recovery] Fused 1 > Binary 2
SW REV check fail: [boot]Fused 1 > Binary 0
Click to expand...
Click to collapse
The error at the last is probably because the firmware you are trying to flash has older bootloader than what it is currently and it looks like you cannot downgrade bootloader.
I

Categories

Resources