{
"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"
}
Hello everybody,
first I have to inform you that this thread is to be regarded as highly experimental. I would like to warn all users, and advise against using this guide, who are not yet fully familiar with Treble A/B devices, and do not know how to debug problems!
If you continue, you are doing so on your own responsibility. I cannot accept any liability and/or responsibility for any problems that might occur during the process, such as bricks and other incidents. If you proceed from here on, you agree to personally take full responsibility for everything you do!
Prerequisites
You are familiar with the Universal HTC RUU/ROM Decryption Tool and know how to use it.
You have a current RUU.zip for your device downloaded onto your PC (ATTENTION software version has to be the same as on your currently activ full stock slot!)
Your bootloader has to be Unlocked/S-ON
You don't panic when something goes wrong.
Guide
First: Start from scratch! What I'm saying is that the first thing you have to do is RUUing back to Stock.
Second: Never, I repeat, never use a PIN/password for the boot! Of course you can use a PIN, a password, or a screen lock pattern, but never for the boot process as long as you want to use a dual boot!
Okay, let's get started:
Use the Universal HTC RUU/ROM Decryption Tool to extract the system.img and the boot.img using the -sf command.
Copy system.img and boot.img to your fastboot/adb folder on your PC (NOT system_other.img, NOT boot_signed.img).
Rename the RUU to 2Q55IMG.zip, and copy it to the root directory of your extSD
Flash your RUU to restore a full stock system to your primary slot, slot A.
Power off your device
Reboot to download mode
Hold the power button pressed to power up your U12+.
Keep the Power button pressed and wait for the very first vibration.
In this very moment you got to release the Power button, press the Volume Up button immediately and hold it until the bootloader shows up.
If you did everything correctly, you'll now see the bootloader mode.
Navigate with the Volume Down key, until "DOWNLOAD MODE" is shown on the top of the screen.
Press Power once to enter it.
Flash your stock /boot and /system images to inactive second slot
flash boot.img to current inactive slot, using
Code:
fastboot flash boot_b boot.img
flash system.img to current inactive slot, using
Code:
fastboot flash system_b system.img
(this one takes a while to start, and will be flashed in three steps, so give it some time! It'll show an error first, so let's hang it on that very error for some seconds - see post #2 for further details.)
Reboot your device to active slot A, and set everything up
Activate Developer Options and check USB Debugging
Reboot to bootloader using adb reboot bootloader
Change active slot to slot B unsing
Code:
fastboot --set-active=b
Reboot to now active slot B once, and let it settle
Now you can start to modify slot B according to your wishes. So I run slot A as full stock system, while I have installed ViperU12+ in my slot B CleanSlate kernel, Magisk and Magisk, having a custom slot and a stock slot.
If an OTA update is offered, you only have to switch the active slot back to slot A, use the
Code:
fastboot --set-active=a
, reboot the device and install the update.
DISCLAIMER: the modified slot will be completely overwritten during this update process, so you should only install the OTA update when a new RUU is available, if you want to keep the "dual boot" option. If an OTA arrives and there is already a RUU for it, you have to install it after changing the slots as just described, and carry out the steps 1 - 12 for the now inactive slot again to realize a second modified slot.
XDA:DevDB Information
HTC U12+ (IME) - „Dual-Boot” Slots A & B
Contributors
@5m4r7ph0n36uru,
Created 2018-09-08
Last Updated 2017-10-17
Error handling during flashes
Error #1: "Cannot load system.img"
What can I do, if fastboot doesn't flash the system image, but throws an error stating
Code:
fastboot flash system_b system.img
Invalid sparse file format at header magic
Sending sparse 'system_b' 1/3 (1041175 KB)
OKAY [ 34.445s]
Writing sparse 'system_b' 1/3
(bootloader) HOSD CL#1050003
(bootloader) [email protected]
(bootloader) [email protected]%
FAILED ()
Finished. Total time: 131.327s
Solution: Well, let the device stay in this state for tiny seconds (in fact, it can be up to 25 seconds), and DO NOT interrupt the process of flashing! This is a fastboot problem that prevents images as large as system.img from being flashed in one step, or rather as a single file. Therefore, fastboot will start splitting system.img into three parts after a certain waiting time, and flashing each part separately, but one after the other. Patience is called for here. Don't panic, because it will have been flashed successfully in the end!
Reserved #2: just in case!
this is smart.
does it mean that I have an untouched 1.15. system on slot a ,cause I ve run that OTA 1.21. with magisk? so I can "downgrade" and can recieve updates again?
wiQbold said:
this is smart.
does it mean that I have an untouched 1.15. system on slot a ,cause I ve run that OTA 1.21. with magisk? so I can "downgrade" and can recieve updates again?
Click to expand...
Click to collapse
Didn't test to switch slot when running to different versions like you do. But in theory this should work, as long as 1.15. is still pristine, as that's what Treble is meant for - having a fallback solution once the first update hit. Maybe you could try and let us know here, for me to add a separate post regarding that very fact.
Sent from my HTC U12+ using XDA Labs
I read somewhere, I think in one of your threads, that there is a trigger on a partition (dont know the name now) that will be triggerd if I root.
thought it is systemwide. so I will try it at next update if I could recieve an OTA, with slot a.
@5m4r7ph0n36uru
This was a great write up. I had the same idea in mind yesterday, but you know this stuff and I don't. So you don't need to install the OS(you know what I mean) in slot-b? Only boot + system? Didn't know that.
Also was thinking what @wiQbold posted regarding switching slots for OTA. Of course that'll only work for the next OTA, will require RUU-ing afterwards. Good for one OTA with the switching.
P.S. - Just want to say THANK YOU for your time, patience and effort with everything you're doing!!!
P.P.S. - Allow just a small, very small token of my appreciation: 7S360226N84122301
k_l_o said:
P.P.S. - Allow just a small, very small token of my appreciation: 7S360226N84122301
Click to expand...
Click to collapse
Thanks a million mate. Really much appreciated! Time for a good and well done Gin I guess
I am asking you to question or deny that my reasoning is correct.
I had v1.15, I made flash Magisk, root. When it was released v1.21 I could not do OTA, so I threw a full RUU.
Without any slots, I uploaded Magiska, root and when it was made public - ViperU12 +
I have an active "slot-A".
And now clou:
If next week HTC will provide v1.25.401.3 (for DUGL) then I will be able to download OTA without a problem after changing the active "slot-A" to "slot-B"?
Now, when writing, I thought I was thinking about "slot-A" when I have ViperU12, Magisk - can I change the active slot on "slot-B" and use STOCK system?
I suspect that user applications will not be on "slot-B"?
regards
q.
qriozum said:
I am asking you to question or deny that my reasoning is correct.
I had v1.15, I made flash Magisk, root. When it was released v1.21 I could not do OTA, so I threw a full RUU.
Without any slots, I uploaded Magiska, root and when it was made public - ViperU12 +
I have an active "slot-A".
And now clou:
If next week HTC will provide v1.25.401.3 (for DUGL) then I will be able to download OTA without a problem after changing the active "slot-A" to "slot-B"?
Now, when writing, I thought I was thinking about "slot-A" when I have ViperU12, Magisk - can I change the active slot on "slot-B" and use STOCK system?
I suspect that user applications will not be on "slot-B"?
regards
q.
Click to expand...
Click to collapse
No you can't as after a RUU slot_b is empty imho. It is used for the first OTA after RUUing, as the update patches all files and copies them onto alot_b. So I'm afraid that, regarding your situation you got to RUU yet again to take the OTA.
That's exactly why I wrote to keep both slots at the same version of dual booting, and to setup the inactive slot_b right after RUUing, and modify that very slot. That way you can run modified on slot_b, and switch to the unmodified still freshly RUU'd slot_a as soon as the update arrives.
The will patch up all files, and copies them over to slot_b overwriting it completely. So the tinkered slot gets lost and replaced by the pristine, updated software version, making slot_b the now active slot. Thus you'd have to wait for the RUU to drop, decrypt it to obtain system and boot image, flash them to the now inactive slot_a, and start modifying slot_a, while you still kept all your apps that'd mean some work to be done after every update, like flashing Magisk and so on to your inactive slot.
That's why I wrote my warnings in the OP, that this one's actually really finicky and should only be done with proper knowledge. You always need to know which ones your pristine slot, as you never ever may boot TWRP if on that very slot to keep the ability to take further OTA. You should only boot TWRP if on the inactive slot, that you ser up as dual boot to tinker with it.
Sent from my HTC U12+ using XDA Labs
Hi, I have followed all of your directions I believe, Have stock ROM on Slot A and fastboot flashed decrypted boot.img and system.img on slot B but cannot get the "fastboot -set-active=b" command to work. Any suggestions? All I get is the usual list of commands when a command doesn't work. Thanks for all you do Buddy.
I noticed as shown in my screenshot that the set active slot commands for a and b are slightly different, with the a slot having a comma at the end. I was just wondering if these commands were accurate?
I can't get either command to be recognized, I've also tried the other similar command from your other thread.
Sorry for the trouble but I am stuck.
LibertyMonger said:
I noticed as shown in my screenshot that the set active slot commands for a and b are slightly different, with the a slot having a comma at the end. I was just wondering if these commands were accurate?
I can't get either command to be recognized, I've also tried the other similar command from your other thread.
Sorry for the trouble but I am stuck.
Click to expand...
Click to collapse
As it turns out, I had an outdated fastboot.exe and that was the issue. But I think the commands in the o.p. are a little off and need corrected? Sorry for the posts.
Anyway, the commands for changing slots that are shown in the O.P. are a little off. They should be
fastboot --set-active=b
fastboot --set-active=a
And if these commands do not work, it is most likely your fastboot.exe (platform-tools) is out of date, needs updated.
LibertyMonger said:
Anyway, the commands for changing slots that are shown in the O.P. are a little off. They should be
fastboot --set-active=b
fastboot --set-active=a
And if these commands do not work, it is most likely your fastboot.exe (platform-tools) is out of date, needs updated.
Click to expand...
Click to collapse
It's correctlly shown when opened on the webview. XDA labs app is the problem here. It tends to not show several lines and mix up code and none code environments. Same applies for multiple quotes, which aren't shown correctly on the Labs App.
Sent from my HTC U12+ using XDA Labs
5m4r7ph0n36uru said:
It's correctlly shown when opened on the webview. XDA labs app is the problem here. It tends to not show several lines and mix up code and none code environments. Same applies for multiple quotes, which aren't shown correctly on the Labs App.
Sent from my HTC U12+ using XDA Labs
Click to expand...
Click to collapse
It was showing the same on my Windows PC as my XDA app but it shows fixed now so no big deal. My main issue was the fastboot .exe but now I can't get "fastboot flash system_b system.img" to work. boot.img flashes fine but I get this error with system.img
Invalid sparse file format at header magic
Sending sparse 'system_b' 1/3 (1046655 KB) OKAY [ 44.078s]
Writing sparse 'system_b' 1/3
(bootloader) HOSD CL#1044991
(bootloader) [email protected]
(bootloader) [email protected]% FAILED () Finished. Total time: 223.063s
I guess it means the image is too big? I don't know but I been trying to figure this out for 3 days now.
I tried everything I could find to fix my slot b and finally resorted to last resort, I ran Sunshine S-Off and reverted back to the 1.15 ROM so I could take the 1.21 OTA and that fixed it. I am currently booted on Slot b. Just in case anyone runs into this issue, S-Off and flashing an older ROM zip in download mode fixes it. Seamless update still worked even though it seemed I had no ROM on slot b.
---------- Post added at 01:33 PM ---------- Previous post was at 01:15 PM ----------
So now I have stock 1.25 on slot a and just set slot b to active and booted up and have stock 1.21 on slot b. So I am thinking for this Dual-Boot to work to customize slot b, would I need to take the OTA on slot b? Kind of confused at this point. But I guess I will figure it out. At least I can boot both slots now.
---------- Post added at 01:47 PM ---------- Previous post was at 01:33 PM ----------
Taking the OTA on slot b didn't work, slot b is still on the 1.21 OTA. This is a little too confusing so I may give up for a while until I learn something. I could try fastboot flashing boot.img and system.img to boot b now I guess. Does it matter in what I order I flash them? Since boot.img was working and system.img was failing, I could try flashing system.img first to see if it is successful and then flash boot.img. Just to be safe. We will see...
---------- Post added at 02:07 PM ---------- Previous post was at 01:47 PM ----------
Fastboot flashing system.img failed again and now can't boot slot b so I am giving up for now. Gonna temp. S-Off and revert back to 1.15 to fix it again and just leave it be for a while. I either have a corrupt decrytped system.img or I have done something else wrong. At least it was a learning experience.
LibertyMonger said:
So now I have stock 1.25 on slot a and just set slot b to active and booted up and have stock 1.21 on slot b. So I am thinking for this Dual-Boot to work to customize slot b, would I need to take the OTA on slot b? Kind of confused at this point. But I guess I will figure it out. At least I can boot both slots now.
Click to expand...
Click to collapse
Actually that's the way it works if you take all OTAs up to the latest. You'll be on 1.25. on Slot A and shouldn't tinker with that very slot, as that's the one to switch to, as soon as the next OTA arrives.
So you'd switch to Slot B for tinkering which is on 1.21. Best would be to have a 1.25. boot.img and system.img at hand. Both can be flashed using fastboot. BUT flashing the system image, fastboot tries to flash it as one large image, which will end in a command prompt output, that the process failed. If you now just leave it there and wait - lets say 30 seconds - fastboot will restart the flashing proceedure and flash the system.img in three parts, one after another.
So you'll be on 1.25 on both slots and not receiving the OTA availability message for 1.25 on Slot B any longer.
Now you can tinker with Slot B, flashing Magisk, a Magisk ROM and the like.
As soon as the next OTA drops, it'll notify you, and you'd have to switch back to Slot A, download the OTA and let it patch up Slot B. After the OTA it'll swith to Slot B and you'll be greated by an updated, full stock system, with software > 1.25. If you want to start tinkering again it is important to backup stock boot.img and system.img from the now active stock Slot B, switch to Slot A, and repeat the procedure written above in italic letters.
Hope that clears things up a bit.
5m4r7ph0n36uru said:
Actually that's the way it works if you take all OTAs up to the latest. You'll be on 1.25. on Slot A and shouldn't tinker with that very slot, as that's the one to switch to, as soon as the next OTA arrives.
So you'd switch to Slot B for tinkering which is on 1.21. Best would be to have a 1.25. boot.img and system.img at hand. Both can be flashed using fastboot. BUT flashing the system image, fastboot tries to flash it as one large image, which will end in a command prompt output, that the process failed. If you now just leave it there and wait - lets say 30 seconds - fastboot will restart the flashing proceedure and flash the system.img in three parts, one after another.
So you'll be on 1.25 on both slots and not receiving the OTA availability message for 1.25 on Slot B any longer.
Now you can tinker with Slot B, flashing Magisk, a Magisk ROM and the like.
As soon as the next OTA drops, it'll notify you, and you'd have to switch back to Slot A, download the OTA and let it patch up Slot B. After the OTA it'll swith to Slot B and you'll be greated by an updated, full stock system, with software > 1.25. If you want to start tinkering again it is important to backup stock boot.img and system.img from the now active stock Slot B, switch to Slot A, and repeat the procedure written above in italic letters.
Hope that clears things up a bit.
Click to expand...
Click to collapse
Thanks a lot buddy, much appreciated. I ended up with 1.21 on slot a cause I reverted back to 1.21, therefore when I took the OTA, it put 1.25 on slot b. So if 1.25 must be on slot a, I will have to revert back to 1.15 so that I will get two OTA's, ultimately leaving me with 1.25 on slot a and 1.21 on slot b. I noticed, trying to flash the RUU on slot b caused my slot b to be unbootable. It bootloops about 10 times before it gives up and returns to boot on slot a.
Thanks again for all your work buddy. I just post my experience to help just in case others run into my issues. Learning from mistakes and experience.
Curiosity, at least for me.
I had a clean system (after RUU) prepared according to your tutorial. On the "B" partition, I applied ViperU12 +, but I had a problem with the weather clock widget (it did not refresh the time after the screen went out under NovaLauncher). Full wipe did not do anything.
I decided to upload a full RUU. I followed the tutorial - I uploaded RUU, I made a flash boot and system on the "B" partition. I checked the active partition (it was "A"), so I started the system to configure it and then change the active partition to "B".
What is my surprise when after the initial configuration, the wizard informs me that I have to enter my Google account information because the account (FRP) was assigned to this device.
I have never met such a message after the RUU. RUU always cleaned the device "to the very bottom".
Hmmm ... what do you think about it?
regards
q.
{
"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.