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 ?
Related
So I tried to install LineageOS on my Honor 8. I unblocked the Bootloader and I am currently able to get into TWRP and Fastboot Mode. I did change the filesystem for the cache system and data as described in this video: w w w. youtube.com /watch?v=X7yDPszoQ5s to enable the encrypted folders.
When I try to install any ROM I am getting the following Errors in red:
E: unknown command (log)
Updater process ended with ERROR: 7
Error installing zip file 'romname'
Also:
Skipping MD5 check: no MD5 file found
could not detect filesystem for /dev/block/bootdevice/by-name/system at /system: No such file or directory
unmount of /system failed; no such volume
patching system image uncoditionally...
E1001: Failed to update system image.
I had LinegeOS installed on my xperia. But don't have root. I wanted to install root addon, but didn't have TWRP because previous time I just temporary boot with
fastboot boot twrp.img
Now I do the same fastboot boot twrp.img
and flash the root addon. I got this error Failed to mount /data invalid argument but also got successful flashed or something like that.
When I press Reboot > System it reboots in TWRP
I tried to flash LineageOS but I get error:
Code:
detected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/system could not detect filesystem for /dev/block/platform/msm_sdcc.1/by-name/userdata, asuming f2fs
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/userdata at /date: No such device unmount of /data failed: no such volume
Patching system image unconditionally
Updater process ended with signal: 7
Error installing
Failed to mount /data
Is there a way to fix that without losing data ?
In TWRP file manager I see the system folders
try to boot on the latest twrp by fastboot boot twrp.img then wipe system then try to install the rom again.
copy the twrp.img to the internal memory
After booting download and flash the latest SuperSU then install terminal then type "su" then grant root access, then flash the TWRP on the FOTAKernel PArtition by
dd if=/sdcard/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
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
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
Hi,
I've a Pixel (sailfish) that I'm trying to load TWRP and Magisk, and I'm unable to flash the recovery image as the bootloader page shows "Device is LOCKED", even though I've already enabled OEM unlock in Developer Settings. How do I unlock the bootloader?
goister said:
Hi,
I've a Pixel (sailfish) that I'm trying to load TWRP and Magisk, and I'm unable to flash the recovery image as the bootloader page shows "Device is LOCKED", even though I've already enabled OEM unlock in Developer Settings. How do I unlock the bootloader?
Click to expand...
Click to collapse
Enabling the OEM Unlock option is the first step but it doesn't unlock the phone. It merely enables unlocking the phone. You have to use a specific adb command to unlock the phone. Since the command varies with models and I am not familiar with your phone, please search for the correct command on Google.
Thanks. I'm following this page - https://www.xda-developers.com/how-to-install-twrp/
I managed to unlock it with fastboot, but I can't seem to flash the recovery. I downloaded the TWRP image from https://dl.twrp.me/sailfish/twrp-3.7.0_9-0-sailfish.img.html and renamed it to twrp.img. I then performed the following steps as per the instructions from xda above:
booted to bootloader with adb reboot bootloader
Temporarily booted to TWRP with fastboot boot twrp.img
Copied TWRP image file to device with adb push twrp.img /sdcard
Go to Advanced->Install Recovery Ramdisk, select twrp.img and swipe to install
I get the following error
Updating partition details...
Failed to mount '/system_root' (Invalid argument)
Failed to mount '/vendor' (Invalid argument)
...done
Unpacking Boot...
Backing up Boot...
Unpacking /sdcard/twrp.img...
Repacking Boot...
/sbin/magiskboot decompress /tmp/repakorig/ramdisk.cpio /tmp/repackorig/ramdisk-1.cpio process ended with ERROR: 1
Error repacking image.
I tried to mount vendor partition, wipe and format the device and retry step 4 and made it a bit further (no more failed to mount '/system_root' and '/vendor' errors, as below, but still fails.
Updating partition details...
Failed to mount '/vendor' (Invalid argument)
...done
Unpacking Boot...
Backing up Boot...
Unpacking /sdcard/twrp.img...
Repacking Boot... /sbin/magiskboot decompress /tmp/repakorig/ramdisk.cpio /tmp/repackorig/ramdisk-1.cpio process ended with ERROR: 1 Error repacking image.
Any suggestions?
goister said:
Go to Advanced->Install Recovery Ramdisk, select twrp.img and swipe to install
Click to expand...
Click to collapse
You can download both the .img and the .zip files. After booting using the .img file, instead of step 4 above, you can try Install from the booted TWRP and navigate to where the .zip file is and simply install it. That is what the TWRP page for Pixel recommends:
fastboot boot path/to/twrp.img
This will temporarily boot TWRP on your device. If you are using a lockscreen pin/pattern/password and do not get prompted to enter your passord, reboot to the bootloader and try again. Go to install and browse to the zip and install the zip. The zip will install TWRP to both boot slots. Installing TWRP at this time will remove root if you are currently rooted.
Click to expand...
Click to collapse
Damn...why did the xda instructions say otherwise?
OK so I managed to reflash to stock image again after the boot loop, and then I followed the TWRP instructions. I was prompted to enter the device password when booting up to TWRP temporarily, and was able to get to TWRP once I entered my device PIN.
After I installed the zip file, I get the following screen:
Installing zip file '/sdcard/twrp.zip'
Updating partition details...
...done
Attempting to decrypt FBE for user 0...
User 0 Decrypted successfully
Data successfully decrypted
Updating partition details...
...done
Full SELinux support is present.
MTP Enabled
Failed to mount '/system root' (Invalid argument)
Failed to mount '/vendor' (Invalid argument)
Failed to mount '/system root' (Invalid argument)
Failed to mount '/system root' (Invalid argument)
Failed to mount '/system root' (Invalid argument)
Installing zip file '/sdcard/twrp.img'
Unmounting system...
########################################
# TWRP Installer for A/B devices #
########################################
Unpacking the installer...
Running image patcher on boot_a...
Running image patcher on boot_b...
Image patching complete!
Done installing TWRP!
*** NOTE: You are now unrooted! ***
Updating partition details...
Failed to mount '/system root' (Invalid argument)
Failed to mount '/vendor' (Invalid argument)
...done
After this, it reboots to Android fine, but whenever I try to reboot to recovery, it goes to the white screen with the Google logo, then reboots to Android.
I'm using the latest TWRP for sailfish - twrp-installer-3.7.0_9-0-sailfish.zip.
Any ideas why?