-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AOSP Xperia 1 IV XQ-CT54 - Switch to Partition "B" hard-brickes device #824
Comments
What a timing, had the same 2 days ago with my Xperia 1 IV. Is there any way to access the PINs for serial communication in order to debug where the phone hangs ? |
You can’t even get into fastboot/flashmode? |
No. No reaction of the phone at all. 2 phones completely bricked. Maybe UART Ports could give some indication, but the thread regarding this bug report was not answered by Sony. |
hm, this shouldn't happen. I'll make a build and try to reproduce |
Thanks. But be aware that the phone is non-usable afterwards. Happy to provide you with any info you need. |
I took the following steps and my device is still alive. It seems the reason lies elsewhere... Spoiler
|
Check. Will compare the steps and come back. Thanks. |
But my build is based on the 5.15 kernel. I'll rebuild it using a prebuilt 5.10 kernel and try again |
Okay. I was using the prebuilt 5.10 kernel. Thanks! |
Hi bartcubbins, |
boot.img is not a bootloader. This is the partition that contains the Linux kernel and ramdisk. UART pinout is the same as on previous devices. |
Ahh thought there's some magic and bootloader is put into boot.img somehow since I didn't find it and I did not see abl_a or abl_b partition. But that makes sense when you say I cannot flash it. Anyway newflasher flashes it with an original image:
|
Is it possible that the bootloader is still locked for B partition ? |
I was able with a small hack in newsflasher to flash B partition on a new phone with it. Now the phone is not bricked any more but is in a boot loop after the SONY logo |
I understand what is happening to your devices, you have a more recent version of the bootloader on one of the slots and after switching to a slot with an older version, very bad things happen that turn your device into a brick. In the current situation, I can only advise you to make sure that both slots have the same version of the bootloader. Regarding the new flasher, most likely it only flashes the active slot (need to look at the source code to confirm). |
Hi Pavel, yes indeed I had the same impression. I have another new device here and did the follow, not bricked any more: |
I'll try something when I have time and get back to you with an answer |
I've built otapackage and successfully installed it on each slot, so the problem is probably on your customization side. I'll take a look at the provided log in the very first message and point out a possible problem. |
Hi Pavel, this is awesome to hear. We still are not successful and stuck in a bootloop (on Partition B - Partition A works fine). Could you please provide us the exact setup for the official AOSP build as provided by Sony for the Xperia 1 Mk 4? I am looking for: This would help us a lot - thanks! PS. |
Where can I download a 64.1.xxx stock rom to flash to both partitions ? |
64.1.A.0.857 is available in flashtool |
Use Sony flash tool (Emma) or if you want to use third-party software, you can download the firmware using XperiFirm. Flash the first slot, then change it to another with |
Platform: Nagara
Device: XQ-CT54
Kernel version: latest provided
Android version: 13
Software binaries version: latest
Previously working on
From my point of view, this has never worked before.
Description
After building official AOSP for Sony Xperia 1 IV (following the build guide) flashing the (successfully built) image on the phone via fastboot flash leads to a fully bricked device if flashed to partition "B". (Active Partition "A"). Phone does not boot anymore and is not visible in ADB devices after the flash.
The image itself is not the problem. If flashed to partition "A" specifically (like: fastboot flash oem_a odm.img), the image boots and AOSP is ready to use with the same image.
If the AOSP built-in updater is used to flash the device (no full image flash via fastboot, but using an OTA) while the device is active in partition A, partition B is required to use.
Therefore: The main problem is: Partition B seems to be broken on the phones (tested it with 2 Xperia 1 IV XQ-CT54 and setting it active bricks the device completely. No (known) way to recover the device.
Symptoms
If partition is switched from A to B the device is completely dead. Hard-Bricked.
How to reproduce
Build AOSP according to Build Guide. Flash AOSP on Partition A. Everything works. Flash the same build on Partition B and change active partition to B. Device is bricked.
Additional context
Logcat attached. AOSP built-in updater confirmes successful flash of the image to partition B, but after reboot command device is completely dead. Timestamp: 01-07 14:23:42.709 1185 1185 I update_engine: [INFO:update_attempter_android.cc(580)] Update successfully applied, waiting to reboot.
logcat_Sony_XperiaIV_OTA_does_not_reboot.txt
The text was updated successfully, but these errors were encountered: