Right now i'm on @phhusson 8.1 ASOP. And i must say, it works very good. There are a few minor issues. But it's still way better then stock emui
I want to try an 9.0 gsi. But no matter witch one I try ,they all won't boot.
When the device boots it stays forever on the splash screen (device unlocked ). Therefore I can't generate any logs because ADB doesn't detect the phone a that time of booting.
Could there be a solution for this problem?
Related
Hey guys,
i have a screen issue with my xa2, android 8.0:
I followed the steps from wiki.lineageos.org/devices/pioneer/install until subtopic ''Installing LineageOS from recovery, point 8 (optional step)'' and used ''adb reboot sideload'' to install gapps nano.
After the successful installation my phone rebooted not into TWRP but Lineage OS recovery.
I chose ''reboot system'' and since this step, my screen is all black aside from occasional vertical lines and flickering.
The screen occassionally shows white background with flickering and switches to black again.
Somehow i can still take screenshots and switch into flashmode.
I tried to run sonys flashtool ''Emma'' and try to reset it to a android stock ROM, but even after this successful step the black screen and flickering continues.
Can anyone help me?
[EDIT:]
My PC still recognizes my phone in adb devices and fastboot devices and i can still execute respective commands with cmd, but its mainly the screen which is black and hinders my work.
same here, still looking for a solution...
eviv-bulgroz said:
same here, still looking for a solution...
Click to expand...
Click to collapse
Does it matter which android version was installed on your devices prior to the LineageOS setup?
I had android 8.0.
same issue here. i stupidly upgraded my xa2 to android 8.0 then downgraded via sonys emma tool before following the procedure from the lineage wiki. all went well, i was able to boot and do stuff, although the camera was making problems, but all of sudden the screen turned flickery. maybe it has something to do with propietary drivers getting lost in the android 8.0 update process? now emma doesn't recognize the device. any ideas?
dooom808 said:
same issue here. i stupidly upgraded my xa2 to android 8.0 then downgraded via sonys emma tool before following the procedure from the lineage wiki. all went well, i was able to boot and do stuff, although the camera was making problems, but all of sudden the screen turned flickery. maybe it has something to do with propietary drivers getting lost in the android 8.0 update process? now emma doesn't recognize the device. any ideas?
Click to expand...
Click to collapse
I have the same problem...
Version Number of xa2: H3113
No luck with anything I tried (emma, newflasher, any twrp) with fastboot on linux mint or win 7 tools (emma newflasher).
Hope with time will come some solution...
Best regards,
tencarsb
Check this post: https://forum.xda-developers.com/showpost.php?p=79799244&postcount=930
it should solve your problem.
I guess the title already says it all, but just in case:
I tried to put LineageOS on this used XZ2 I bought a few days ago, everything went fine until side loading the Lineage image. Appaerently there as some data corruption and the installation failed halfway through... unfortunately the phone dropped out of recovery mode and has been stuck in a boot-loop ever since.
I can still access the phone via fastboot after the battery runs out and before it goes into its bootloop again, even managed to flash the recovery image (in boot_b if that's important) - but somehow seem unable to actually boot into recovery... given that I have still access via fastboot, the situation might still be salvageable?
also tried booting the phone-specific twrp via fastboot boot <twrp>.img but that sadly also sent me back into the boot loop.
fastboot reboot recovery also sends me to the bootloop
any other ideas?
Did you format (not wipe!) /data before booting LOS?
Thanks for the reply!
I followed these instructions but something failed at the end:
Install LineageOS on xz2c | LineageOS Wiki
wiki.lineageos.org
but later yesterday I was able to find somewhat of a work around. Since from browsing this forum many people seemed to have had similar issues, here is what worked for me:
- break out of the reboot-loop and shut down the phone by pressing and holding volume up + volume down + power button
- the phone should vibrate about 3 times to confirm
- download your phones standard firmware via xperifirm
[TOOL] XperiFirm ~ Xperia Firmware Downloader [v5.6.5]
[TOOL] XperiFirm ~ Xperia Firmware Downloader [v5.6.5] NOTE: This thread is the only official source of XperiFirm! Websites like xperifirm.com and xperifirmtool.com were not authorized to redistribute my software! XperiFirm... Allows you to...
forum.xda-developers.com
- download new flasher
[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
- put the phone into flashmode - press and hold volume down, connect the usb cable, and then also press and hold power, the phone should go into flash mode indicated by a green led
- follow the instructions (basically put the newflasher executable into the firmwarefolder created by xperifirm and execute
if everything goes well you should recieve a functioning (but wiped) device. still better than a paper weight
---------------------------------------------------------------
edit: tried to flash LOS again, but same error as first time (Error applying update: 28 (kdowloadoperationexecutionerror)
which prevents me from successfully installing LOS... I only found this:
[GUIDE][HOW TO FIX] 28 (ErrorCode::kDownloadOperationExecutionError) | 5 (ErrorCode::kPostInstallRunnerError)
In this short guide, I will explain to you how to easily fix the recovery error, the name of which can be found in the title. This guide is only a collection of information found on the Internet and a simple explanation of the problem. It was...
forum.xda-developers.com
which kinda explains the issue, but not how to fix it in my case on my device... any suggestions?
edit2:
tried over 10 different firm wars ranging from the latest 18.1 to some older 17.1, tried via the official lineageos recovery image and also via twrp.. always the same result... installation failed
I have been trying for over 3 hours now... but I just can't find (nor fix) the issue)
Hey so I was having this same issue and seem to have resolved it by doing a firmware upgrade using the oxygen firmware located here. I already have twrp installed and had no issues logging into the recovery, but i could never get logged into the system. Using twrp i just moved the oxygen file onto the phone and flashed it directly from the recovery. I then switched to the partition i installed it to and it booted up. It looks like i had everything right except for the firmware. Good luck!
[Download] Stable OxygenOS 11 For OnePlus 6/6T Based on Android 11
Stable OxygenOS 11 For OnePlus 6 and 6T just rolled out for OnePlus 6 and 6T. Download Android 11 based on OxygenOS 11 for OnePlus 6/6T.
www.androidsage.com
iitzzMalice said:
Hey so I was having this same issue and seem to have resolved it by doing a firmware upgrade using the oxygen firmware located here. I already have twrp installed and had no issues logging into the recovery, but i could never get logged into the system. Using twrp i just moved the oxygen file onto the phone and flashed it directly from the recovery. I then switched to the partition i installed it to and it booted up. It looks like i had everything right except for the firmware. Good luck!
[Download] Stable OxygenOS 11 For OnePlus 6/6T Based on Android 11
Stable OxygenOS 11 For OnePlus 6 and 6T just rolled out for OnePlus 6 and 6T. Download Android 11 based on OxygenOS 11 for OnePlus 6/6T.
www.androidsage.com
Click to expand...
Click to collapse
Hmmm.. I just realized you're using a different phone than me. My bad. Hopefully it helps that i had the same issue and resolved it by using oxygen firmware. Good luck to you!
thanks for the response
I think I identified the issue, which might be very much firmware related.
Essentially because my phone has the wrong stock firmware and LOS refuses to install on that despite being the same hardware as the "supported" firmware.
so what I probably need is a way to install H8314 firmware on an SO-05K model... there's a thread about that, but so far I have not been successful
(alternatively altering the LOS firmware itself to install on the SO-05K...)
Hi
I flashed XQ-BT52 on AOSP 12 from stock
After some time after use and multiple reboots, device begins to show this message when loading
Code:
Your device is corrupt.
It can't be trusted and will not boot.
Your device will be powered off in 5 seconds.
and goes in bootloop.
I tried various firmware except AOSP (for example LinageOS) - the result is the same.
Fix it can be rewriting the boot sector (boot.img), but not long, through time a message is repeated.
Please help me solve this problem. i really want this device with root and custom android 12.
use NewFlasher to flash last firmware from XperiFirm
Download XperiFirm Tool v5.6.1
The XperiFirm Tool is something that can help you download all new firmware which is officially released by Sony. This is made possible by connecting to the official Sony servers.…
droidfilehost.com
And after that I can flash custom firmware?
silvandover said:
Hi
I flashed XQ-BT52 on AOSP 12 from stock
After some time after use and multiple reboots, device begins to show this message when loading
Code:
Your device is corrupt.
It can't be trusted and will not boot.
Your device will be powered off in 5 seconds.
and goes in bootloop.
I tried various firmware except AOSP (for example LinageOS) - the result is the same.
Fix it can be rewriting the boot sector (boot.img), but not long, through time a message is repeated.
Please help me solve this problem. i really want this device with root and custom android 12.
Click to expand...
Click to collapse
I am in exactly the same boat with my Xperia 5 III. Trying to get AOSP 12 on it but exactly the same place. Have tried so many versions of flashing and rebuilding but no luck.
Would be really appreciative to know if and how you get this working
Thanks!
after flash original firmware and device booting, unlock boot loader from this link
https://developer.sony.com/develop/open-devices/get-started/unlock-bootloader
I flash 62.0.A.3.163 firmware and reflash to linage os.
No problems for about day.
Apparently in the update there was a firmware for the hardware.
I switched from dotOS to Pixel Experience because I wanted to get a taste of A12. After the change my phone started behaving strangely. It doesn't turn up on Windows File Explorer anymore and ADB doesn't detect my phone unless I set it to USB charge only. Plus the biggest problem of them all- TWRP doesn't work anymore. Whenever I reboot my phone it boots into TWRP, and the screen keeps flashing at the TWRP logo. The only way to boot to A12 is to enter fastboot and hit fastboot continue in the CMD. I'm at my wits end here and honestly a bit desperate. I have attached the logs from when the TWRP screen kept flashing. I wiped my device completely before installing Pixel Experience and I think that may be the problem. I fear that I may have sort of permanently damaged my phone or something. Any help would be appreciated. Thank you.
Pixel Experience A12 has it's own recovery u need to use that twrp or orangefox won't work on that rom same as los has it's own recovery
Unfortunately, I already did open TWRP by CMD: C:\fastboot boot TWRP.img and I didn't understand at all because there were no partitions in there, plus I already did flash TWRP 3 times. So itself, TWRP won't take to OS itself (stuck boot loop), and it was awful because there was no way I could flash it back to where it was because of NO partitions in TWRP at ALL!... I do NOT UNDERSTAND at ALL!!! So I had to force it to do MsmDownloadTool V4.0 because there is only one way to restore it to my phone because it seems to work fine, but... I am still puzzled about what is going on because this is my first time. It never happened to me before, this is NOT NORMAL because I knew I had my phone U11 and M8 with that TWRP, and it worked fine until now with OP9P, those very different designs I never had before!
Model: LE2127
Android Version: 12 (LE2127_11_C.17) - - April 2022 update
(OP9P = OnePlus 9 Pro)
TWRP doesn't work with A12.
ffejy462 said:
TWRP doesn't work with A12.
Click to expand...
Click to collapse
This, decryption isn't supported AT ALL by any recovery running on A12. I've seen modified recoveries for A12 for other devices and it seems they try to disable forced encryption which is a BAD idea!
If you want to decrypt, would recommend either staying with OOS 11 or a custom ROM on A11. Bear in mind there have been numerous reported issues with TWRP hence why most custom ROMs for the OP9P choose to stick to LineageOS recovery.
cat139lyleb said:
Unfortunately, I already did open TWRP by CMD: C:\fastboot boot TWRP.img and I didn't understand at all because there were no partitions in there, plus I already did flash TWRP 3 times. So itself, TWRP won't take to OS itself (stuck boot loop), and it was awful because there was no way I could flash it back to where it was because of NO partitions in TWRP at ALL!... I do NOT UNDERSTAND at ALL!!! So I had to force it to do MsmDownloadTool V4.0 because there is only one way to restore it to my phone because it seems to work fine, but... I am still puzzled about what is going on because this is my first time. It never happened to me before, this is NOT NORMAL because I knew I had my phone U11 and M8 with that TWRP, and it worked fine until now with OP9P, those very different designs I never had before!
Model: LE2127
Android Version: 12 (LE2127_11_C.17) - - April 2022 update
(OP9P = OnePlus 9 Pro)
Click to expand...
Click to collapse
It's because you flashed an incompatible TWRP (not compatible with Android 12 ROMS)
Okay, maybe TWRP is already aware of this problem with 12 ROMS, plus I already did tried a few times with OEM unlock in 11, but no luck. So that's why OEM unlocked in 12... very weird...
The bootloader won't unlock until OEM unlocks in any android versions. So first, that's why.
I have a question about that. Do you think it's why -> SECURE BOOT - YES?
Then how do we make it say NO?
Because we are aware that it is FULLY unlocked as DEVICE STATE - UNLOCKED, correct?