btw tell me before the midnight if it fixed it or not, I want to make sure to merge change before tomorrow's build ^.^
Last edited:
[ROM][OFFICIAL][pioneer][9] LineageOS 16.0
- Thread starter LuK1337
- Start date
Yup, I'll let you know. I'm testing it to see if it reboots again or not, but so far so good
Uhh, so you didn't flash stock FW before? Actually, can you msg me on irc (see my signature), it may be bit convenient for me to guess stuff there instead of refreshing xda every few mins?
I bought the phone new - started it - rooted it and flashed it to los 16
Then come irc ^.^
Slots and installs
In my case, yes. Installed LineageOS from Slot B, after the 2nd reboot into TWRP, it was in Slot B and then installed gapps.
Agree that this should not be necessary, but in my case things got messed up when trying to install TWRP as the recovery and from then on it was necessary to handle the A/B slot problem.
In my case, yes. Installed LineageOS from Slot B, after the 2nd reboot into TWRP, it was in Slot B and then installed gapps.
Agree that this should not be necessary, but in my case things got messed up when trying to install TWRP as the recovery and from then on it was necessary to handle the A/B slot problem.
flash stock oreo via newflasher, boot and verify that wifi works. then follow post #2 on this thread and then flash stuff
P
Petezza
Guest
Got my phone back from repair (h3113 - new mainboard, yay... android 9 preinstalled... damn).
Is there any way to get LOS 16 on my device?
XperiFirm shows only the android P.
Emma (Sony Flashtool) might be able to downgrade my device to Oreo. But will I get the vertical-line error again, if I downgrade to Oreo and use TWRP 3.3.1.0? Also, is the procedure described in post #2 needed in my case? (If I downgrade via Emma, I'll get Oreo .123 anyway).
Any advice?
Is there any way to get LOS 16 on my device?
XperiFirm shows only the android P.
Emma (Sony Flashtool) might be able to downgrade my device to Oreo. But will I get the vertical-line error again, if I downgrade to Oreo and use TWRP 3.3.1.0? Also, is the procedure described in post #2 needed in my case? (If I downgrade via Emma, I'll get Oreo .123 anyway).
Any advice?
I flashed LOS 16 on my XA2 and started using it and then realized that no sensors are working. Accelerometer (phone does not rotate automatically), light sensor. What to do? Steps from second post? I flash oreo stock before with emma..
When I try to do steps from #2, after flash to B, when I disconnect usb cable, phone tries to boot it (and does not work obviously). I was trying to turn it off but I cannot, it always start booting again.. Impossible to set A..
When I try to do steps from #2, after flash to B, when I disconnect usb cable, phone tries to boot it (and does not work obviously). I was trying to turn it off but I cannot, it always start booting again.. Impossible to set A..
Thanks, no permissions.. So adb root did not worked :/. But unfortunatelly, the screen or motherboard on my xperia just died. I had unlocked it, saw the unlock screen and then blink and a few vertical lines ands all, nothing else. Phone is in warranty but bootloader is unlocked so I really do not know if they will fix it
.Dead too
Have a similar situation. Saw the same behavior as above and then put the phone into flash mode. Was able to flash an image with Emma and then go to flashboot mode. In flashboot set the active_slot to b. After that, the phone is entirely unresponsive. None of the normal button commands work (Pwr + Volume up/dwn and usb cable connect, or Pwr+Volume Up to simulate a battery disconnect). Hard to believe that it is a motherboard problem, but it could be. With a bricked phone the next alternative may be to open it up and physically disconnect the battery...
Thanks, no permissions.. So adb root did not worked :/. But unfortunatelly, the screen or motherboard on my xperia just died. I had unlocked it, saw the unlock screen and then blink and a few vertical lines ands all, nothing else. Phone is in warranty but bootloader is unlocked so I really do not know if they will fix it
Have a similar situation. Saw the same behavior as above and then put the phone into flash mode. Was able to flash an image with Emma and then go to flashboot mode. In flashboot set the active_slot to b. After that, the phone is entirely unresponsive. None of the normal button commands work (Pwr + Volume up/dwn and usb cable connect, or Pwr+Volume Up to simulate a battery disconnect). Hard to believe that it is a motherboard problem, but it could be. With a bricked phone the next alternative may be to open it up and physically disconnect the battery...
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
36
LineageOS is a free, community built, aftermarket firmware distribution of Android 9 (Pie), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Instructions :
- Download the latest build and gapps
- Boot to recovery
- Flash the latest build
- Boot to recovery again
- Flash gapps
- Reboot
- Builds : https://download.lineageos.org/pioneer
- Root addon : https://download.lineageos.org/extras
- Google Apps : https://wiki.lineageos.org/gapps.html
- DO NOT Report bugs if you're running a custom kernel or you installed Xposed
- Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
- If it is a random reboot, grab /sys/fs/pstore/console-ramoops and /sys/fs/pstore/dmesg-ramoops-0. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
- If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Code:What is your-- LineageOS version: LineageOS Download url: Gapps version: Did you-- wipe: restore with titanium backup: reboot after having the issue: Are you using-- a task killer: a non-stock kernel: other modifications: Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
XDA:DevDB Information
[ROM][OFFICIAL][pioneer][9] LineageOS 16.0, ROM for the Sony Xperia XA2
Contributors
LuK1337
Source Code: https://github.com/LineageOS
ROM OS Version: Windows 8 Mobile
ROM Kernel: Linux 4.x
Version Information
Status: Testing
Created 2018-08-30
Last Updated 2020-02-2814How to flash latest firmware
[ protip: 20191010+ builds require 50.2 FW (at least bluetooth, dsp, modem from it) If you're still running 50.1 you can flash this package in TWRP: https://androidfilehost.com/?fid=4349826312261716572 unless you're fine with having partially broken audio and broken Egistec fingerprint sensor ;3 ]
However if you want to flash whole firmware package onto both slots, you can follow the guide below:
1. Download latest firmware with XperiFirm.
NOTE: When using mono XperiFirm will fail to unpack the firmware, you can do it manually using following commands:
2. Go to the directory where the firmware got downloaded to and remove following files:Code:for f in FILE_*; do unzip $f; done unzip boot.zip -d boot
- boot_X-FLASH-ALL-18AE_0x00.hash
- boot_X-FLASH-ALL-18AE.sin
- persist_X-FLASH-ALL-18AE_0x00.hash
- persist_X-FLASH-ALL-18AE.sin
- system_other_X-FLASH-ALL-18AE_0x00.hash
- system_other_X-FLASH-ALL-18AE.sin
- system_other_X-FLASH-ALL-9B8D_0x00.hash
- system_X-FLASH-ALL-18AE_0x00.hash
- system_X-FLASH-ALL-18AE.sin
- system_X-FLASH-ALL-9B8D_0x00.hash
- userdata_X-FLASH-CUST-18AE.sin
- vendor_X-FLASH-ALL-18AE_0x00.hash
- vendor_X-FLASH-ALL-18AE.sin
- vendor_X-FLASH-ALL-9B8D_0x00.hash
3. Turn off your phone, hold vol dn and plug in the USB cable, the screen should be off and green LED lit.
4. Run Newflasher, it'll flash entire FW to your current slot then unplug the USB cable and power on your phone.
5. Turn off your phone, hold vol up and plug in the USB cable, the screen should be off and blue LED lit.
6. Enter this command: `fastboot getvar current-slot`, it should return something like this:
current-slot: _b
Finished. Total time: 0.001s
7. Now switch to the opposite slot by entering command: `fastboot set_active a` if the current slot is `_b` or `fastboot set_active b` if its `_a`, you should see this:
Setting current slot to 'a'...
OKAY [ 0.012s]
Finished. Total time: 0.014s
or
Setting current slot to 'b'...
OKAY [ 0.012s]
Finished. Total time: 0.014s
8. Unplug usb cable and repeat steps: 3, 4
9. Profit?7@Marteng69 here is what i did -> i was stucked on pie + flickering screen (model h3113):
1. i used emma (https://developer.sony.com/develop/open-devices/get-started/flash-tool), just install and run it, boot your phone in flash mode (vol down + usb connect = green light). then the app will recognize your phone (assuming you have drivers installed) and give you phone info. on the right side download and flash offered firmware (at the moment there is the uk oreo one, download it and you'll have it in case it's replaced with pie). flash the complete firmware (the "Software Update Content Erase" image) and reboot after flashing completed
2. boot the phone, let it boot up for a few minutes then turn it off with holding power + vol up for a few secs (let it vibrate 3 times to make sure it's off)
3. then boot it in fastboot mode (vol up + usb connect = blue light) and then via cmd run "fastboot boot 1d66175c6ce8e04865d041cbcac8ba3013a02b1e.img" (please check your exact .img name)
4. that's it, the phone should boot (normal looking) twrp and then reboot your phone and... say thanks to @LuK13377
Until 50.2.* kernel source is out I'm not planning to do anything.
btw see https://talk.sonymobile.com/t5/Kernel/50-2-A-0-400-kernel-source/td-p/1390917 ^^6
...yeah I booted some old ass kernel HEAD and it works there. Looks like i'm going to have fun time finding the change that broke it...
EDIT: Should be working again in next builds ^.^
