Hi there.
I screwed up my MediaPad M5 Lite (Wifi edition: BAH2-W19, EMUI 8 installed. It's a treble compatible device) yesterday and need help.
I did the following steps before it all went down the gutter:
1. I successfully unlocked the bootloader using the DC Unlocker method
2. I downloaded the latest a-only AOSP release of "phhusson AOSP 9.0 v119": system-arm64-aonly-vanilla-nosu.img.xz (https://github.com/phhusson/treble_experimentations/releases)
3. I rebooted into bootloader and flashed the unzipped .img file to the device. The flash was successful as all 4 steps of copieing stuff tot he system partition said "OKAY"
4. now I used "fastboot reboot" and the trouble started. The tablet froze in fastboot mode. It just didn't restart.
5. I turned it of using a long push on the power button. Then it restarted and got stuck at the start screen. I'll attach a screenshot so you know what I am seeing.
6. From now on I was only able to boot into fastboot mode and into the stock recovery. There I did factory reset and cache formatting several times but with no effect.
7. Only thing that still worked was the eRecovery function in the EMUI stock recovery. With this I was able to download some official firmware from Huawei automatically and the tablet was back to stock
8. This night the OS did an auto update to v215.
9. So this morning I repeated the step 2. from above but with a different a-only custom rom and again it didn't work out
10. I tried to use the eRecovery function to get back to stock, but now the recovery is broken and throws an error "Getting package info failed".
I also tried to download older firmware from https://androidhost.ru/ and flash it with the dload method. Without success of course. While doing it I receive an error "Software install failed!". I will attach a screenshot.
Can anybody give me a hint what I could do next to approach the problem?
Best
rob
Well, you didn't had TWRP as recovery, so no nandroid backup available. From one of my experiences with flashing a stock rom for acer, I had to delete some lines of code from the meta inf folder relating the version of the phone, in order to successfully flash it. Maybe the stock ROM you are trying has some lines of code detecting if bootloader unlocked.
Im also having trouble getting a good tutorial for getting rid of the os or just to have magisk on the tablet
You dowoad latest rom and flash stock via hru and. Twrp search xda
unbrick Huawei MediaPad M5 Lite
r0b said:
Hi there.
I screwed up my MediaPad M5 Lite (Wifi edition: BAH2-W19, EMUI 8 installed. It's a treble compatible device) yesterday and need help.
I did the following steps before it all went down the gutter:
1. I successfully unlocked the bootloader using the DC Unlocker method
2. I downloaded the latest a-only AOSP release of "phhusson AOSP 9.0 v119": system-arm64-aonly-vanilla-nosu.img.xz (https://github.com/phhusson/treble_experimentations/releases)
3. I rebooted into bootloader and flashed the unzipped .img file to the device. The flash was successful as all 4 steps of copieing stuff tot he system partition said "OKAY"
4. now I used "fastboot reboot" and the trouble started. The tablet froze in fastboot mode. It just didn't restart.
5. I turned it of using a long push on the power button. Then it restarted and got stuck at the start screen. I'll attach a screenshot so you know what I am seeing.
6. From now on I was only able to boot into fastboot mode and into the stock recovery. There I did factory reset and cache formatting several times but with no effect.
7. Only thing that still worked was the eRecovery function in the EMUI stock recovery. With this I was able to download some official firmware from Huawei automatically and the tablet was back to stock
8. This night the OS did an auto update to v215.
9. So this morning I repeated the step 2. from above but with a different a-only custom rom and again it didn't work out
10. I tried to use the eRecovery function to get back to stock, but now the recovery is broken and throws an error "Getting package info failed".
I also tried to download older firmware from https://androidhost.ru/ and flash it with the dload method. Without success of course. While doing it I receive an error "Software install failed!". I will attach a screenshot.
Can anybody give me a hint what I could do next to approach the problem?
Best
rob
Click to expand...
Click to collapse
Unbrick using Huawei Multi tool .
---------- Post added at 03:14 PM ---------- Previous post was at 03:10 PM ----------
r0b said:
Hi there.
I screwed up my MediaPad M5 Lite (Wifi edition: BAH2-W19, EMUI 8 installed. It's a treble compatible device) yesterday and need help.
I did the following steps before it all went down the gutter:
1. I successfully unlocked the bootloader using the DC Unlocker method
2. I downloaded the latest a-only AOSP release of "phhusson AOSP 9.0 v119": system-arm64-aonly-vanilla-nosu.img.xz (https://github.com/phhusson/treble_experimentations/releases)
3. I rebooted into bootloader and flashed the unzipped .img file to the device. The flash was successful as all 4 steps of copieing stuff tot he system partition said "OKAY"
4. now I used "fastboot reboot" and the trouble started. The tablet froze in fastboot mode. It just didn't restart.
5. I turned it of using a long push on the power button. Then it restarted and got stuck at the start screen. I'll attach a screenshot so you know what I am seeing.
6. From now on I was only able to boot into fastboot mode and into the stock recovery. There I did factory reset and cache formatting several times but with no effect.
7. Only thing that still worked was the eRecovery function in the EMUI stock recovery. With this I was able to download some official firmware from Huawei automatically and the tablet was back to stock
8. This night the OS did an auto update to v215.
9. So this morning I repeated the step 2. from above but with a different a-only custom rom and again it didn't work out
10. I tried to use the eRecovery function to get back to stock, but now the recovery is broken and throws an error "Getting package info failed".
I also tried to download older firmware from https://androidhost.ru/ and flash it with the dload method. Without success of course. While doing it I receive an error "Software install failed!". I will attach a screenshot.
Can anybody give me a hint what could do next to approach the problem?
dnrob
Click to expand...
Click to collapse
You can install these roms only if you can downgrade to update v177 and lower
Like me you need to Unbrick your mediapad m5 lite
First place need to go back in Fastboot mode.
So UNPLUG , turn off , wait a second and turn on with volume Down , when screen blink release power button and keep volume down pressed a second until Fastboot mode
Or, try to boot in Fastboot with volume down + power AND USB plugged in goes into fastboot, or TWRP if you flashed TWRP to RECOVERY2 instead to RECOVERY.
If doesnt work try the same plug or unplug cuz we have Recovery_ramdisk , eRecovery and eRecovery2
WHEN its okay and you can turn on fastboot mode
Second prepair the img's for unbricking
The LEGIT methods its come back stock rom , then you'll be able to do what you want.
Download Huawei Multi-Tools , Huawei Update Extractor and update.zip of your stock ROM and update_data_full
Then use Huawei Update Extractor to extract
system.img ramdisk.img recovery_ramdisk.img From update.app\update.zip and
Cust.img from update.app\update_full_public.zip.
If you have backup of your userdata.img its the time to put all together in the same directory before go futher.
If all its good , you just need to click unbrick.
Maybe i'll soon do a guide for unbrick and prevent brick , and how install twrp without losing data or encryption data
helmuth said:
And just for the complete list:
Volume up + power AND USB plugged in goes into eRecovery (or TWRP, if you flashed TWRP to RECOVERY2 instead to RECOVERY)
Volume up and down + power and USB plugged in forces update via USB (indicated by a little USB-like icon in the recovery circle. The progess bar goes to 5% and waits for input from your PC)
Click to expand...
Click to collapse
RAMDISK238.img, Disable_Dm-Verity_ForceEncrypt_12.21.2019.zip and twrp8.img you will find at
android-hilfe.de->forum huawei-mediapad-m5-lite -> custom-roms-mediapad page-5
Theese custom roms should work:
Andy Yan's LineageOS 17 (Android 10) -> lineage-17.0-20191231-UNOFFICIAL-treble_arm_avN.img.xz
Pierre-Hugues Husson AOSP 10.0 v209 -> system-quack-arm64-aonly-vanilla.img.xz
Following this guide you will loose all your data so be sure to have a backup
This should work for a Mediapad M5 lite BAH2-W19OCEC432-238
Precondition: Unlocked Bootloader / OEM Unlocked / USB Debugging active
1. if you brick your device don`t blame me
2. check, if the version B238 is installed
3. back up your data
4. copy Disable_Dm-Verity_ForceEncrypt_12.21.2019.zip on SD card
Fastboot:
5. boot into Fastboot Mode.
6. flash TWRP -> fastboot flash recovery_ramdisk twrp8.img
7. fastboot reboot recovery (the first time booting should show up the twrp menu)
if the boot message "2. Press Volume up for 3 seconds" appears must do a Factory Reset in the Stock Recovery. After a reboot the TWRP menu shows up. In lineageos you can activate advanced reboot in developer settings to boot in TWRP menu by pressing recovery mode
TWRP:
8. Wipe -> Advanced Wipe -> select data + cache + dalvik-cache -> Swipe to wipe -> back to start menu
9. Install -> Select Storage -> select Mircro SD card -> OK -> select Disable_Dm-Verity_ForceEncrypt_12.21.2019.zip -> Swipe to confirm Flash
10. Reboot -> Bootloader (not System!!!)
Fastboot:
11. fastboot flash ramdisk RAMDISK238.img
12. fastboot flash system lineage-17.0-20191231-UNOFFICIAL-treble_arm64_avN.img
(or AOSP 10.0 v209)
13. fastboot reboot
LineageOS should start.
other custom roms could work as well.......
Edit:
There´s a new version of LineageOS available:
https:######sourceforge.net###projects###andyyan-gsi###files###lineage-17.x###lineage-17.1-20200111-UNOFFICIAL-treble_arm64_avN.img.xz###download
replace ### with /
It works well on my m5lite
It did not work on B239
I am trying now to get back to the stock rom.
I think the problem is with RAMDISK238.img :/
Do you know how to get one for 239?
Thanks !
BesterTrainer said:
RAMDISK238.img, Disable_Dm-Verity_ForceEncrypt_12.21.2019.zip and twrp8.img you will find at
android-hilfe.de->forum huawei-mediapad-m5-lite -> custom-roms-mediapad page-5
Theese custom roms should work:
Andy Yan's LineageOS 17 (Android 10) -> lineage-17.0-20191231-UNOFFICIAL-treble_arm_avN.img.xz
Pierre-Hugues Husson AOSP 10.0 v209 -> system-quack-arm64-aonly-vanilla.img.xz
Following this guide you will loose all your data so be sure to have a backup
This should work for a Mediapad M5 lite BAH2-W19OCEC432-238
Precondition: Unlocked Bootloader / OEM Unlocked / USB Debugging active
1. if you brick your device don`t blame me
2. check, if the version B238 is installed
3. back up your data
4. copy Disable_Dm-Verity_ForceEncrypt_12.21.2019.zip on SD card
Fastboot:
5. boot into Fastboot Mode.
6. flash TWRP -> fastboot flash recovery_ramdisk twrp8.img
7. fastboot reboot recovery (the first time booting should show up the twrp menu)
if the boot message "2. Press Volume up for 3 seconds" appears must do a Factory Reset in the Stock Recovery. After a reboot the TWRP menu shows up. In lineageos you can activate advanced reboot in developer settings to boot in TWRP menu by pressing recovery mode
TWRP:
8. Wipe -> Advanced Wipe -> select data + cache + dalvik-cache -> Swipe to wipe -> back to start menu
9. Install -> Select Storage -> select Mircro SD card -> OK -> select Disable_Dm-Verity_ForceEncrypt_12.21.2019.zip -> Swipe to confirm Flash
10. Reboot -> Bootloader (not System!!!)
Fastboot:
11. fastboot flash ramdisk RAMDISK238.img
12. fastboot flash system lineage-17.0-20191231-UNOFFICIAL-treble_arm64_avN.img
(or AOSP 10.0 v209)
13. fastboot reboot
LineageOS should start.
other custom roms could work as well.......
Edit:
There´s a new version of LineageOS available:
https:######sourceforge.net###projects###andyyan-gsi###files###lineage-17.x###lineage-17.1-20200111-UNOFFICIAL-treble_arm64_avN.img.xz###download
replace ### with /
It works well on my m5lite
Click to expand...
Click to collapse
sasuke988 said:
It did not work on B239
I am trying now to get back to the stock rom.
I think the problem is with RAMDISK238.img :/
Do you know how to get one for 239?
Thanks !
Click to expand...
Click to collapse
https://
pro-teammt.ru/
en/
online-firmware-database/
?firmware_model=BAH2-W19&firmware_page=0
Check out your model (C432C431/...)
Use the huawei extractor to extract the images
Can someone check if this is legit? https://romprovider.com/2019/09/9-1-0-151-b151-firmware-jordan2-l09b/amp/
Raresh T said:
Can someone check if this is legit? https://romprovider.com/2019/09/9-1-0-151-b151-firmware-jordan2-l09b/amp/
Click to expand...
Click to collapse
It's for the 8" screen variant. It won't work on our 10.1"
is there any current custom house for this model because no links work. And on the stock, I have a problem with 5ghz Wi-Fi
You'd better install TWRP,flash FBE-disabler and format data partition
Anyway,firmware can be found at professorjtj.github.io and I recommend you rebrand and update it to EMUI9 to get better treble compatibility
SkipM4 said:
You'd better install TWRP,flash FBE-disabler and format data partition
Anyway,firmware can be found at professorjtj.github.io and I recommend you rebrand and update it to EMUI9 to get better treble compatibility
Click to expand...
Click to collapse
thats an interesting suggestion. could you post some guides on how could someone rebrand their device ?
Code:
#include "std_disclaimer.h"
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this Recovery
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Requirements
Unlocked bootloader
working ADB/fastboot on a PC
the TWRP image downloaded
Pie firmware on the active slot
Installation guide (pre metadata encryption):
Copy the twrp image to your phones storage and/or micro sdcard
Start cmd/powershell/terminal with working adb/fastboot
Reboot to bootloader
adb reboot bootloader OR
turn off the phone (or reboot), as soon as it turns on, hold volume down while USB cable is connected
If youre unofficially bootloader unlocked, and you nuked laf, its volume up and USB for you
fastboot boot TWRP-judypn-boot.img
Confirm allow system modifications if asked
Press cancel if asked for a password (aka when youre encrypted, could also be that it doesnt show you /data at all and no password screen)
Go to Advanced -> Install Recovery Ramdisk
Select the TWRP image which you copied to your phone/sdcard earlier
TWRP will now be installed to both slots (boot_a and boot_b)
Go to Reboot -> Recovery to make sure TWRP is successfully installed
Features:
Install recovery ramdisk:
Selecting this, and then an image (e.g. of TWRP) allows you to install the ramdisk (where TWRP resides for example) into both currently installed kernels/boot images
Inject TWRP after install:
Automatically injects current installed TWRP into the boot image of the ROM/zip youre installing when ticked
Broken:
LGs encryption on Stock
encryption on other ROMs(?)
How to flash ROMs (PRE metadata encryption):
Reboot to TWRP
Make a backup
Install -> select the ROM zip -> tick Inject TWRP -> Swipe for install
wait... ROM will be installed into the NON ACTIVE slot (if youre on a, it will be installed to b, and vice versa)
Reboot system
for gapps, magisk or other mods:
DO NOT REBOOT TO SYSTEM from last step
Go back -> Reboot -> select the non active slot (to where the rom got installed to) -> select recovery
Install gapps, magisk, and whatever else you want
Reboot system
How to initially flash ROMs (metadata encryption):
Reboot to existing TWRP
Make a backup of everything you want to keep
Copy backup to PC (or another external medium)
Flash the ROM
Do NOT inject TWRP (this will break recovery otherwise)
Go to reboot -> Select opposite slot
Reboot to recovery
Perform factory reset (this is to setup encryption)
Apply update (from ADB) with adb sideload for gapps/magisk
reboot to bootloader
fastboot boot judypn_TWRP_bootable-metadata.img
Use as usual
Reboot system
How to update ROMs (metadata encryption):
Reboot to bootloader
fastboot boot judypn_TWRP_bootable-metadata.img
Install -> Select ROM zip
do NOT inject TWRP
Reboot -> select opposite slot (it will tell you even which it installed the ROM to)
Reboot bootloader
fastboot boot judypn_TWRP_bootable-metadata.img
Install gapps/magisk
Or
reboot recovery
apply update -> from adb (in e.g. Lineage recovery)
On PC: adb sideload <new version zip>
(Advanced -> ) Reboot recovery
adb sideload gapps/magisk
reboot system
Warnings:
Updating a ROM means reflashing the mods you flashed too (e.g. Gapps), addon.d doesnt work properly
Be aware of the slot you are currently on
If youre flashing a ROM to a slot, make sure you also have the required firmware (abl, modem, and so on) in that slot
Infos:
System image/Vendor image and system/vendor are redundant, the image variants are direct copies of the partition (and also their size) while the others are "simply" files copied and repacked
How to use decrypted stock by @Xsavi : https://forum.xda-developers.com/lg-v40/how-to/guide-twrp-data-access-stock-t3970149
Metadata encryption TWRP requires 10 firmware to use properly, no guarantee for it to work on Pie firmware!
Download:
Metadata bootable: https://drive.google.com/file/d/1hdzeH3AIQVf3siQNsI27IS_vmghPESEG/view?usp=sharing + Install zip: https://drive.google.com/file/d/1CQUfg54zD838detcIJqdRiKXdVNtd6Iy/view?usp=sharing
Bootable: https://drive.google.com/open?id=1UnIFbJlXHl6x4azq6H6yS-PRfk-omdTP
Old: https://drive.google.com/open?id=1p3IrbeOxM4ay01JccyifWDuxqqrE0_Dl
Sources:
device tree: https://github.com/SGCMarkus/android_device_lge_judypn-twrp/tree/android-9.0
kernel: https://github.com/SGCMarkus/android_kernel_lge_sdm845/tree/lge-pie-v409-20a
XDA:DevDB Information
TWRP for Judypn, ROM for the LG V40
Contributors
SGCMarkus
ROM OS Version: 9.x Pie
Version Information
Status: Alpha
Created 2019-09-20
Last Updated 2019-09-20
Hmm interesting I see ?
Wow. The V40 got TWRP too. Awesome.
Wooo new twrp! Great work Markus!
How hard would it be to get this working on the V35? I can get it to install and boot into recovery, but it does not register touch input.
Well, having a big issue. I installed TWRP, Install custom rom w/ twrp inject, reboot menu, selected the slot where the rom, restarted, no TWRP, No root, but custom rom and now it comes up as unknown in LG UP so I can try to fix it. I think its mostly a brick since I can't do anything. No Fastboot either because im in slot b and cant switch because no root or fastboot.
lowridincrew said:
Well, having a big issue. I installed TWRP, Install custom rom w/ twrp inject, reboot menu, selected the slot where the rom, restarted, no TWRP, No root, but custom rom and now it comes up as unknown in LG UP so I can try to fix it. I think its mostly a brick since I can't do anything. No Fastboot either because im in slot b and cant switch because no root or fastboot.
Click to expand...
Click to collapse
did you have pie firmware also in the slot where you installed LOS to?
otherwise.... nothing is ever really a brick, you still have 9008 mode as last option
Fixed. Case of the bad drivers. LGUP didn't wanna read so I went to a different computer. Read it through LGUP, flashed Stock, rebooted to recovery, TWRP popped up.
How do the two slots work? I thought that these were for current ROM in one and then new ROM in the other, alternating with each ROM update. Why is one for the ROM and the other holding system partition additions? I would expect gapps to integrate into both A and B sides at once on top of each ROM...
Is there documentation on this?
So I'm bootloader unlocked, rooted on pie and cannot access fastboot. How do I go about installing twrp?
EDIT: tried different USB-C cables and one worked like a charm.
seacrow01 said:
So I'm bootloader unlocked, rooted on pie and cannot access fastboot. How do I go about installing twrp?
Click to expand...
Click to collapse
What happens if you try and access the bootloader aka the fastboot...
Ainz_Ooal_Gown said:
What happens if you try and access the bootloader aka the fastboot...
Click to expand...
Click to collapse
Nothing, phone just reboots like nothing is there. neither the button combo nor the "adb reboot bootloader" command works.
So I got on of the US models unlocked bootloader Verizon I got fastboot can I flash this one to my 405ua verizon?
In fastboot i see Judypn But I believe they flashed a open Korean on mine Im trying to get back to US firmware twrp and magisk if at all possible
Well I can confirms this works for pie on a 405ua unlocked bootloader...Nice work mate...
After reading through a bit and playing around. I got recovery installed on ramdisk recovery. Got out of my bootloop by fastboot flashing stock boot img from my current firmware. I did notice slot b I still have stock recovery which helped getting out of the failed encryption loop. And I also have download mode there.
How to unlock bootloader in indian firmware????
why i cannot enter fastboot mode on my lg v40 v405UM with android pie. When i command adb reboot bootloader it goes to restart phone.Not enter fastboot mode. Please help me.Sorry for my english
Hi anyone can help me after flashing twrp my phone doesnt reboot or does it take long to boot after flashing twrp
lowridincrew said:
Fixed. Case of the bad drivers. LGUP didn't wanna read so I went to a different computer. Read it through LGUP, flashed Stock, rebooted to recovery, TWRP popped up.
Click to expand...
Click to collapse
What drivers did you use? I can't get my LGUP to recognize the device. I'm trying to flash stock back to a working copy of Lineage 16 with twrp.
Broken:
LGs encryption on Stock
encryption on other ROMs(?)
exFat for external SDs
Does this mean just within recovery or within Pie?.... The exFat part, that is
xaxxelous said:
Broken:
LGs encryption on Stock
encryption on other ROMs(?)
exFat for external SDs
Does this mean just within recovery or within Pie?.... The exFat part, that is
Click to expand...
Click to collapse
Both, as pie uses the same kernel as TWRP when booted
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 10, which is designed to increase performance and reliability over stock Android for your device.
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
NOTE
Should you ever face any issues, capture logs. I also need to know what build you're on (build number or at least a date).
Hint: "It doesn't work" is not a bug report and posts like this will be ignored.
KNOWN ISSUEs
The Sony stock camera does not work at the moment.
INFO
This ROM does not use the device trees/kernel from sonyxperiadev (aka SODP). The device tree was made from scratch, and the stock kernel (based off 52.1.A.x.y) has been used.
DOWNLOAD
Official builds
NOTE: Since the official builds are signed, you can't simply upgrade from my unofficial builds -- you can either migrate to an official build using a script or do a clean install.
All unofficial builds
INSTRUCTIONS
Just flash the builds as usual. Make sure to be on the latest stock firmware.
SOURCE
LineageOS
Kernel
CHANGELOG
20210516:
- fixed WiFi display/screen casting
- addressed performance issues and lags
20210515:
- updated to 18.1
- fixed remaining most of the bugs
- set SELinux to enforcing
20201128:
- fixed NFC
20201127:
- initial public release.
Thanks a lot. Great to know you are working on LOS18.
I tried sideloading with the latest LOS17.1 recovery (and LOS 17.1 on the phone, naturally). I get an error. Do I absolutely have to be on stock?
Are you still working on this one?
I am trying to flash a LOS image onto a single SIM Phone, but it always fails with error "unknown fuse request opcode 2016" in the recovery.log, and the system image is empty after the flash.
I am using the latest STOCK TWRP 2020-06-14_21-07-37_twrp_apollo.tar.gz.
It fails on all LOS images I have tried, 18.0 17.1 etc. So far I haven't been able to flash a LOS image at all successfully.
The flash performs normally, but fails with an error after 2-3 minutes, and afterwards the system partition is empty.
The unit is a SONY XZ2 Compact Single SIM.
After discussion with someone, this maybe due to the LOS image having an incorrect System partition size(?). Why does it flash correctly on most people's units, but not on this one?
Anyone has an idea? I am attaching the twrp.log files.
Garfield24 said:
I am trying to flash a LOS image onto a single SIM Phone, but it always fails with error "unknown fuse request opcode 2016" in the recovery.log, and the system image is empty after the flash.
I am using the latest STOCK TWRP 2020-06-14_21-07-37_twrp_apollo.tar.gz.
It fails on all LOS images I have tried, 18.0 17.1 etc. So far I haven't been able to flash a LOS image at all successfully.
The flash performs normally, but fails with an error after 2-3 minutes, and afterwards the system partition is empty.
The unit is a SONY XZ2 Compact Single SIM.
After discussion with someone, this maybe due to the LOS image having an incorrect System partition size(?). Why does it flash correctly on most people's units, but not on this one?
Anyone has an idea? I am attaching the twrp.log files.
Click to expand...
Click to collapse
Hi!
I'got the same situation, with a bad downloaded los.zip file. Maybe it's the problem.
But what i saw in your description, the used twrp. If i known good, for Android 11 the working twrp for coming from stock to los is here what works for me ( apollo ):
" https://androidfilehost.com/?w=files&flid=318609 " ;
And don't flash it to the recovery or boot partitiom, just temperoraly boot it with fastboot.
lba810701 said:
Hi!
I'got the same situation, with a bad downloaded los.zip file. Maybe it's the problem.
But what i saw in your description, the used twrp. If i known good, for Android 11 the working twrp for coming from stock to los is here what works for me ( apollo ):
" https://androidfilehost.com/?w=files&flid=318609 " ;
And don't flash it to the recovery or boot partitiom, just temperoraly boot it with fastboot.
Click to expand...
Click to collapse
Nope, not working.
I flashed a stock image with newflasher and booted to the apps. Original image boots fine.
Then I rebooted into fastboot and did: fastboot boot twrp.img like you suggested.
TWRP runs fine, I wipe the partitions, and flash LOS. No operating system installed afterwards.
I don't think it's a corrupt .zip file, since I tried about 5 different ones.
When flashing I get a message: "Unable to find partition for path /cache" in red colour.
Anyone knows what that means?
Garfield24 said:
Nope, not working.
I flashed a stock image with newflasher and booted to the apps. Original image boots fine.
Then I rebooted into fastboot and did: fastboot boot twrp.img like you suggested.
TWRP runs fine, I wipe the partitions, and flash LOS. No operating system installed afterwards.
I don't think it's a corrupt .zip file, since I tried about 5 different ones.
When flashing I get a message: "Unable to find partition for path /cache" in red colour.
Anyone knows what that means?
Click to expand...
Click to collapse
H
Garfield24 said:
Nope, not working.
I flashed a stock image with newflasher and booted to the apps. Original image boots fine.
Then I rebooted into fastboot and did: fastboot boot twrp.img like you suggested.
TWRP runs fine, I wipe the partitions, and flash LOS. No operating system installed afterwards.
I don't think it's a corrupt .zip file, since I tried about 5 different ones.
When flashing I get a message: "Unable to find partition for path /cache" in red colour.
Anyone knows what that means?
Click to expand...
Click to collapse
Do you disabled the verified boot before rhe whole twrp process?
" fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img "
lba810701 said:
H
Do you disabled the verified boot before the whole twrp process?
" fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img "
Click to expand...
Click to collapse
Yes, I have tried that, too, just now again. As before, not working. I have tried so many things by now. The flash of the LOS image completes, but in step 2/2 I get "Unable to find partition for path /cache" , and it says completed. In the recovery log, there is an error "unknown fuse request opcode 2016" . The system partition is empty after the flash (7MB used).
I wonder, if there is a difference in the partitions on this specific phone. I am attaching the output of the following command:
cat /proc/partitions > /external_sd/partlog.txt
It writes an overview of partitions and their sizes to a file on the SD Card. There are 74 partitions on /sda. I wonder why anybody needs 74 partitions?
Can someone run the same command on their phone with a working and installed LOS and compare it to my file, if there is any difference to a phone that is working (partitions-sizes/-ordering?)?
I run the command from TWRP. Start up recovery TWRP and go to Advanced -> Terminal. There you can run the command.
cat /proc/partitions > /external_sd/partlog.txt
I would appreciate if someone could run that command on a phone where the LOS image works, and compare the file to my file, if there are any differences in the partitioning scheme or sizes. Sizes are important.
Any other suggestions also welcome.
Garfield24 said:
Yes, I have tried that, too, just now again. As before, not working. I have tried so many things by now. The flash of the LOS image completes, but in step 2/2 I get "Unable to find partition for path /cache" , and it says completed. In the recovery log, there is an error "unknown fuse request opcode 2016" . The system partition is empty after the flash (7MB used).
I wonder, if there is a difference in the partitions on this specific phone. I am attaching the output of the following command:
cat /proc/partitions > /external_sd/partlog.txt
It writes an overview of partitions and their sizes to a file on the SD Card. There are 74 partitions on /sda. I wonder why anybody needs 74 partitions?
Can someone run the same command on their phone with a working and installed LOS and compare it to my file, if there is any difference to a phone that is working (partitions-sizes/-ordering?)?
I run the command from TWRP. Start up recovery TWRP and go to Advanced -> Terminal. There you can run the command.
cat /proc/partitions > /external_sd/partlog.txt
I would appreciate if someone could run that command on a phone where the LOS image works, and compare the file to my file, if there are any differences in the partitioning scheme or sizes. Sizes are important.
Any other suggestions also welcome.
Click to expand...
Click to collapse
I attached it, but I'm on 17.1. Maybe help? But first round, it's seems the same except the last two line of the logs... In yours, there are "mcblk0" and "mmcblk0p1" what's missing from mine, but I haven't got sdcard so, maybe thats why.
lba810701 said:
I attached it, but I'm on 17.1. Maybe help? But first round, it's seems the same except the last two line of the logs... In yours, there are "mcblk0" and "mmcblk0p1" what's missing from mine, but I haven't got sdcard so, maybe thats why.
Click to expand...
Click to collapse
Yes, that definitely helps. Thank you. The last two lines is the SDCard, that's correct.
That means my phone has the same ROM size and partition size than yours, so the System partition is the same size.
I find an additional partition in your file in line 19:
254 0 1048576 zram0
I don't have a zram0 partition in my file and my phone.
The question now is: does that make any difference? Can that missing partition on my phone can cause the flash to fail?
After a LOT of trial and error I am making a description, how to get a running LOS on your SONY XZ2 Compact Single SIM (and probably Dual SIM). This is not a description for people, who got it running the easy way. It's for people that tried everything, and can't get it running, and are in desperation and lost.
General description first: The SONY XZ2 Compact is a phone with 2 slots. These phones don't have a recovery partition, so you cannot meaningfully boot into a recovery partition like on old phones. It now has a boot partition (2 of them - slot A and slot B), and you can boot an operating system from these slots. These slots are completely separate, you can boot an operating system in slot A and another separate one in slot B. These slots (from a user perspective) are separate, and there is very little interchange between them (or more or less none).
Prerequisits: TWRP, I used the Version from MartinX 2020-06-14_21-07-37_twrp_apollo.tar.gz , link is here: https://androidfilehost.com/?w=files&flid=306949
Use a STOCK TWRP
Extract the .img files with 7-zip (7-zip.org), until you have the .img file separate.
Newflasher:
[TOOL] Newflasher (xperia command line flasher)
Disclaimer: newflasher tool was made for testing and educational purposes, ME is not responsible for what you do on/with your device using newflasher, you must agree that you using newflasher on your own risk, I am not responsible if you brick...
forum.xda-developers.com
I used v42, probably newer versions work, too, try not to use an older version
Booting into fastboot: hold Volume-UP and then plugging a USB cable to the computer. The blue light should be lit, if fastboot is active, screen stays blank.
Booting into flash mode: hold Volume-DOWN and then plugging a USB cable to the computer. The green light should be lit, if flash mode is active, screen stays blank.
Now let's get to the process of flashing LOS:
Step 1 - Flash an original working SONY image into Slot A:
Boot into fastboot mode, so the blue light is on.
Type:
fastboot reboot bootloader
(Sometimes the computer doesn't recognise the phone after this command, then just unplug the USB, wait until the phone is off, and try again beginning Step 1. It can fail a couple of times, but it will also work in between).
fastboot --set-active=a
fastboot reboot bootloader
You can check that Slot A is active by typing the command
fastboot getvar all
in the output check the line current slot active: a
Run Newflasher (how to use Newflasher is beyond the scope of this post, google it) to flash an original stock SONY image. You need to be in flash mode for Newflasher with the green light lit.
Answer the first question what to do when done with Newflasher with 'p'=Power Off, and all others with 'n'=No.
When Newflasher completes, check the last few lines output, it should say setting slot A active and OKAY. That confirms that you flashed the original SONY image in Slot A.
You now have a fully working operating system in Slot A. However there is a bug in Newflasher and that bug destroys the boot process in Slot B, which means you'll be only able to boot Slot A, booting Slot B will fail.
Should you decide to boot the operating system (you don't have to), make sure you don't set up authentication (pin code, fingerprint), skip setting that up, so your data partition doesn't get encrypted.
Step 2 - Flash an original working SONY image into Slot B:
Boot into fastboot mode, so the blue light is on.
Type (similar to Step 1):
fastboot reboot bootloader
fastboot --set-active=b
fastboot reboot bootloader
You can check that Slot B is active by typing the command
fastboot getvar all
in the output check the line current slot active: b
WARNING: DO NOT BOOT Slot B, as it will fail 2-3 times (you'll notice the phone vibrating upon crash and reboot), because the phone will then put you back on Slot A, and you'll flash Slot A again. Make sure YOU DON'T BOOT the operating system in Slot B, or you'll end up in Slot A again.
Run Newflasher (how to use Newflasher is beyond the scope of this post, google it) to flash an original stock SONY image. You need to be in flash mode for Newflasher with the green light lit.
Answer the first question what to do when done with Newflasher with 'p'=Power Off, and all others with 'n'=No.
When Newflasher completes, check the last few lines output, it should say setting slot B active and OKAY. That confirms that you flashed the original SONY image in Slot B.
You now have a fully working operating system in Slot B. However there is a bug in Newflasher and that bug destroys the boot process in Slot A, which means you'll be only able to boot Slot B.
At this point in time, if you would try to boot into Slot A, it will boot up to the SONY logo, and then crash, and reboot up to the SONY logo, and then crash. Should you get stuck in that loop, insert a USB cable and hold Volume-UP, it'll catch the crashing loop, and you'll end up in fastboot.
Step 3 - Boot the original SONY image up to the home screen where the apps show:
Actually you should be in Slot B already, but if you are not:
Boot into fastboot mode, so the blue light is on.
Type (similar to Step 2):
fastboot reboot bootloader
fastboot --set-active=b
fastboot reboot bootloader
You can check that Slot B is active by typing the command
fastboot getvar all
in the output check the line current slot active: b
Boot the phone's operating original stock image in Slot B, until you are at the home screen with the apps. This sets up all the defaults for your phone, and updates any ROM images in the chips (like modem etc.).
Make sure you don't set up authentication (pin code, fingerprint), skip setting that up, so your data partition doesn't get encrypted.
Power off your phone.
Step 4 - Flash twrp into Slot B
Type (similar to Step 2):
fastboot reboot bootloader
fastboot --set-active=b
fastboot reboot bootloader
fastboot flash boot twrp.img
This will flash TWRP as boot in Slot B. Make sure in the screen output it was flashed in boot_b.
Should you make an error here, start with Step 1. The reason here is, we want LOS in Slot A, and not TWRP.
Boot your TWRP in Slot B.
WARNING: DO NOT flash VBMETA, it'll break the boot process, and you can start from Step 1.
Step 5 - Flash LOS into Slot A
Once TWRP is running, go to Wipe.
WARNING: DO NOT perform factory reset.
Go to Advanced Wipe, and ONLY WIPE 'Data' and 'Dalvic Cache'
WARNING: DO NOT WIPE System or Internal Storage. You'll loose mount points under Linux, and the LOS image flash will fail.
Go back to TWRP home screen.
From there go to Advanced and from there to ADB Sideload.
From the computer start installing your LOS image (sideload).
On the computer type:
adb sideload <Your LOS image>.zip.
ATTENTION: During flashing, the phone will show, which slot it flashes. It should flash and show: "flashing inactive Slot A". If you accidentally flash Slot B, start from the beginning Step 1.
Best results I had with the image from the LOS homepage https://download.lineageos.org/xz2c
Download the zip file, don't unpack it, use adb sideload to upload the zip file.
Forget about the Recovery image on the LOS homepage. You don't need it.
When flashing completes, you can wipe Delvic Cache.
WARNING: DO NOT WIPE 'cache', since a 2 slot phone doesn't have a cache partition, and it will fail to wipe it.
Do NOT install the TWRP app, skip this step.
Reboot
Step 6 - Boot LOS
LOS is in Slot A, TWRP is in Slot B.
You can alternate between the slots from fastboot.
fastboot reboot bootloader
fastboot --set-active=a
fastboot reboot bootloader
A reboot should boot LOS.
ATTENTION: When the LOS image has finished booting and you get to the date/time screen, the LOS will hang a while (30s). Just let it do it's job, I think (not sure), it's creating the data in the user partition. After 30s or so use the back key, and try setting the time again. This only happens on the very first boot.
Let me know as feedback, if I can clarify better or if this description is ok.
Hello,
if there is anything I can help with getting official support for LineageOS 18.1 pls let me know.
Garfield24 said:
After a LOT of trial and error I am making a description, how to get a running LOS on your SONY XZ2 Compact Single SIM (and probably Dual SIM). This is not a description for people, who got it running the easy way. It's for people that tried everything, and can't get it running, and are in desperation and lost.
General description first: The SONY XZ2 Compact is a phone with 2 slots. These phones don't have a recovery partition, so you cannot meaningfully boot into a recovery partition like on old phones. It now has a boot partition (2 of them - slot A and slot B), and you can boot an operating system from these slots. These slots are completely separate, you can boot an operating system in slot A and another separate one in slot B. These slots (from a user perspective) are separate, and there is very little interchange between them (or more or less none).
Prerequisits: TWRP, I used the Version from MartinX 2020-06-14_21-07-37_twrp_apollo.tar.gz , link is here: https://androidfilehost.com/?w=files&flid=306949
Use a STOCK TWRP
Extract the .img files with 7-zip (7-zip.org), until you have the .img file separate.
Newflasher:
[TOOL] Newflasher (xperia command line flasher)
Disclaimer: newflasher tool was made for testing and educational purposes, ME is not responsible for what you do on/with your device using newflasher, you must agree that you using newflasher on your own risk, I am not responsible if you brick...
forum.xda-developers.com
I used v42, probably newer versions work, too, try not to use an older version
Booting into fastboot: hold Volume-UP and then plugging a USB cable to the computer. The blue light should be lit, if fastboot is active, screen stays blank.
Booting into flash mode: hold Volume-DOWN and then plugging a USB cable to the computer. The green light should be lit, if flash mode is active, screen stays blank.
Now let's get to the process of flashing LOS:
Step 1 - Flash an original working SONY image into Slot A:
Boot into fastboot mode, so the blue light is on.
Type:
fastboot reboot bootloader
(Sometimes the computer doesn't recognise the phone after this command, then just unplug the USB, wait until the phone is off, and try again beginning Step 1. It can fail a couple of times, but it will also work in between).
fastboot --set-active=a
fastboot reboot bootloader
You can check that Slot A is active by typing the command
fastboot getvar all
in the output check the line current slot active: a
Run Newflasher (how to use Newflasher is beyond the scope of this post, google it) to flash an original stock SONY image. You need to be in flash mode for Newflasher with the green light lit.
Answer the first question what to do when done with Newflasher with 'p'=Power Off, and all others with 'n'=No.
When Newflasher completes, check the last few lines output, it should say setting slot A active and OKAY. That confirms that you flashed the original SONY image in Slot A.
You now have a fully working operating system in Slot A. However there is a bug in Newflasher and that bug destroys the boot process in Slot B, which means you'll be only able to boot Slot A, booting Slot B will fail.
Should you decide to boot the operating system (you don't have to), make sure you don't set up authentication (pin code, fingerprint), skip setting that up, so your data partition doesn't get encrypted.
Step 2 - Flash an original working SONY image into Slot B:
Boot into fastboot mode, so the blue light is on.
Type (similar to Step 1):
fastboot reboot bootloader
fastboot --set-active=b
fastboot reboot bootloader
You can check that Slot B is active by typing the command
fastboot getvar all
in the output check the line current slot active: b
WARNING: DO NOT BOOT Slot B, as it will fail 2-3 times (you'll notice the phone vibrating upon crash and reboot), because the phone will then put you back on Slot A, and you'll flash Slot A again. Make sure YOU DON'T BOOT the operating system in Slot B, or you'll end up in Slot A again.
Run Newflasher (how to use Newflasher is beyond the scope of this post, google it) to flash an original stock SONY image. You need to be in flash mode for Newflasher with the green light lit.
Answer the first question what to do when done with Newflasher with 'p'=Power Off, and all others with 'n'=No.
When Newflasher completes, check the last few lines output, it should say setting slot B active and OKAY. That confirms that you flashed the original SONY image in Slot B.
You now have a fully working operating system in Slot B. However there is a bug in Newflasher and that bug destroys the boot process in Slot A, which means you'll be only able to boot Slot B.
At this point in time, if you would try to boot into Slot A, it will boot up to the SONY logo, and then crash, and reboot up to the SONY logo, and then crash. Should you get stuck in that loop, insert a USB cable and hold Volume-UP, it'll catch the crashing loop, and you'll end up in fastboot.
Step 3 - Boot the original SONY image up to the home screen where the apps show:
Actually you should be in Slot B already, but if you are not:
Boot into fastboot mode, so the blue light is on.
Type (similar to Step 2):
fastboot reboot bootloader
fastboot --set-active=b
fastboot reboot bootloader
You can check that Slot B is active by typing the command
fastboot getvar all
in the output check the line current slot active: b
Boot the phone's operating original stock image in Slot B, until you are at the home screen with the apps. This sets up all the defaults for your phone, and updates any ROM images in the chips (like modem etc.).
Make sure you don't set up authentication (pin code, fingerprint), skip setting that up, so your data partition doesn't get encrypted.
Power off your phone.
Step 4 - Flash twrp into Slot B
Type (similar to Step 2):
fastboot reboot bootloader
fastboot --set-active=b
fastboot reboot bootloader
fastboot flash boot twrp.img
This will flash TWRP as boot in Slot B. Make sure in the screen output it was flashed in boot_b.
Should you make an error here, start with Step 1. The reason here is, we want LOS in Slot A, and not TWRP.
Boot your TWRP in Slot B.
WARNING: DO NOT flash VBMETA, it'll break the boot process, and you can start from Step 1.
Step 5 - Flash LOS into Slot A
Once TWRP is running, go to Wipe.
WARNING: DO NOT perform factory reset.
Go to Advanced Wipe, and ONLY WIPE 'Data' and 'Dalvic Cache'
WARNING: DO NOT WIPE System or Internal Storage. You'll loose mount points under Linux, and the LOS image flash will fail.
Go back to TWRP home screen.
From there go to Advanced and from there to ADB Sideload.
From the computer start installing your LOS image (sideload).
On the computer type:
adb sideload <Your LOS image>.zip.
ATTENTION: During flashing, the phone will show, which slot it flashes. It should flash and show: "flashing inactive Slot A". If you accidentally flash Slot B, start from the beginning Step 1.
Best results I had with the image from the LOS homepage https://download.lineageos.org/xz2c
Download the zip file, don't unpack it, use adb sideload to upload the zip file.
Forget about the Recovery image on the LOS homepage. You don't need it.
When flashing completes, you can wipe Delvic Cache.
WARNING: DO NOT WIPE 'cache', since a 2 slot phone doesn't have a cache partition, and it will fail to wipe it.
Do NOT install the TWRP app, skip this step.
Reboot
Step 6 - Boot LOS
LOS is in Slot A, TWRP is in Slot B.
You can alternate between the slots from fastboot.
fastboot reboot bootloader
fastboot --set-active=a
fastboot reboot bootloader
A reboot should boot LOS.
ATTENTION: When the LOS image has finished booting and you get to the date/time screen, the LOS will hang a while (30s). Just let it do it's job, I think (not sure), it's creating the data in the user partition. After 30s or so use the back key, and try setting the time again. This only happens on the very first boot.
Let me know as feedback, if I can clarify better or if this description is ok.
Click to expand...
Click to collapse
So this works for 17.1 - but have you tried it on 18.1?
Asking because 17.1 works well for me following the official install method (via stock LOS recovery), whereas 18.1 fails.
landsome said:
So this works for 17.1 - but have you tried it on 18.1?
Asking because 17.1 works well for me following the official install method (via stock LOS recovery), whereas 18.1 fails.
Click to expand...
Click to collapse
It works on my phone, however:
I only have a 18.0 image from Olivier. Link is here: https://androidfilehost.com/?w=files&flid=320371
Use the 700MB image, the 200MB image (dated 20201206) probably won't work, the file size is too small. Not sure what the 200MB image is for. At the time of this post the image that worked was dated 20201205.
Anybody working on a 18.1 image, please post it here? I don't have the expertise to help with 18.1 image.
Directly flashing 18.0 image by Olivier crashed my phone, I am not sure why. There is no real reason I know of, but it did.
I first flashed official LOS 17.1 image from LOS homepage using the method above, and it worked. Boot the image to the home screen to intialise everything on LOS. Should it fail, you have a corrupt LOS image. I only had nightly builds available at the time of this post. Maybe that changes soon...
I then went back to slot B and booted TWRP again. I then sideloaded the LOS 18.0 .zip image from Olivier with adb sideload <imagefile.zip> without wiping anything. Don't wipe any partitions, just flash the 18.0 LOS image over the existing installation in Slot A.
When booting the LOS 18.0 image, it says data corrupt (I don't know why), and it boots into the LOS recovery and asks for a factory reset. Do a factory reset, you'll loose all data on the phone, so backup what needs to be backed up first. You probably need to install the apps again as well.
After the factory reset, the phone boots LOS 18.0 just fine.
I noticed there is no email client in the LOS 18.0 image from Olivier. Should you need it, the following tip:
IMPORTANT: When in TWRP (before you flash LOS 18.0), MOUNT System and Data in the mount menu.
You can then find the apk for the LOS email client in the LOS 17.1 image:
/system/system/product/app/Email/Email.apk
/system/system/product/app/Exchange2/Exchange.apk
Copy these apk in the TWRP file manager to /data/media/downloads
Boot LOS 17.1 and backup these apk files to your PC to install on LOS 18.0. The apk files are in your phone's download directory after the copy operation in TWRP.
The Exchange.apk is an extension package to the Email.apk to add Exchange client functionality.
IMPORTANT: After installing the apk on LOS 18.0, and even before you start them for the first time, go to Settings, and give "Email" and "Exchange" all permissions on your phone. Just allow everything. If you don't do that, the applications will crash upon start.
Hope that helps. Any questions, please ask.
A new build is up, please check the OP. Feel free to test and report bugs - we'd like to enable official 18.1 weekly builds soon.
Olivier said:
A new build is up, please check the OP. Feel free to test and report bugs - we'd like to enable official 18.1 weekly builds soon.
Click to expand...
Click to collapse
Thanks. We appreciate this.
Hi,
I have a problem with Wire application.
Microphone is not working on call and video call.
Microphone is working to record a message. Permissions are OK.
I had the same problem on LOS 17 so I thought upgrade will resolve it. NO.
Did anyone experience the same problem?
Raphos said:
Hi,
I have a problem with Wire application.
Microphone is not working on call and video call.
Microphone is working to record a message. Permissions are OK.
I had the same problem on LOS 17 so I thought upgrade will resolve it. NO.
Did anyone experience the same problem?
Click to expand...
Click to collapse
I have the exact same problem with LOS 17, and with 18 too!
Wire is not only the affected program, skype has for example the exact same issue.
And unfortunately I do not know how to fix it.
Thanks for your reply.
Ok, good to know. I have a Z3 compact on LOS 17 and a Z5 Compact on LOS 15, Wire is working fine.
Microphone is working with whatsapp calls. Maybe Devs are whatsapp shareholders
Raphos said:
Ok, good to know. I have a Z3 compact on LOS 17 and a Z5 Compact on LOS 15, Wire is working fine.
Click to expand...
Click to collapse
I can confirm to that LOS 17 and 18 on other devices have no issues, thus it seems xz2c specific
Мy bootloader is unlocked. My device is Le2127. I reboot into bootloader mode, switch the active slot, then reboot and get back into the bootloader. How to load firmware from another slot? Thanks.
OxygenOS 13.0 Stable F.17 GL
Android 13
stranger75 said:
Мy bootloader id unlocked. My device is Le2127. I reboot into bootloader mode, switch the active slot, then reboot and get back into the bootloader. How to load firmware from another slot?
Click to expand...
Click to collapse
What is your active slot now?
A (B not loaded) if I flash the firmware into another slot (B), then only B is loaded
In the installer script, the firmware commands write to both slots, but only the active one is loaded
stranger75 said:
A (B not loaded) if I flash the firmware into another slot (B), then only B is loaded
In the installer script, the firmware commands write to both slots, but only the active one is loaded
Click to expand...
Click to collapse
Then I don't truly understand what you are trying to do or what problem you are having.
I would like to boot from any slots, for example, if the system is damaged on one slot. As far as I know they have a common userdate section
here is a related article:
Installation of Stock ROM on both slots.
Hello friends, I have read in the threads about installation of oxygen OS on both slots to be safe to install custom ROM to avoid any error. I want to know the step by step procedure to install the stock ROM on both slots. Thanks.
forum.xda-developers.com
But it doesn't work here
stranger75 said:
I would like to boot from any slots, for example, if the system is damaged on one slot. As far as I know they have a common userdate section
here is a related article:
Installation of Stock ROM on both slots.
Hello friends, I have read in the threads about installation of oxygen OS on both slots to be safe to install custom ROM to avoid any error. I want to know the step by step procedure to install the stock ROM on both slots. Thanks.
forum.xda-developers.com
But it doesn't work here
Click to expand...
Click to collapse
Check into the "copyslot" script. Might be an answer for you
Where can you find it for os 13 ?
In that script, support only android 11
stranger75 said:
Where can you find it for os 13 ?
In that script, support only android 11
Click to expand...
Click to collapse
"fastboot getvar all" will tell you active slot while in fastboot.
fastboot --set-active=a
&
fastboot --set-active=b
is changing active slot
I know it and have done it. But loading from another slot does not happen.
Instead of loading the system, I get into Bootloader
stranger75 said:
I know it and have done it. But loading from another slot does not happen.
Instead of loading the system, I get into Bootloader
Click to expand...
Click to collapse
I have heard some say flash firmware twice to get same on both slots...otherwise I am out of ideas!
I tried several times when switching the slot via fastboot, but each time only the one installed in the current slot is loaded
@stranger75
I am not sure that it is still possable to have two seperate system levels installed since the intoduction of Dynamic Partitions.
Implementing Dynamic Partitions - [source.android] - [website] - Link
Cheers.