AOSP Q for Suzu/f5121
DISCLAIMER
As always use it at your own risk.
Build it in my spare time to test how the development is proceeding.
Installation instructions
NB: This is a full software update in the sense that will replace everything, recovery included, with aosp version. You need to reflash twrp afterwards.
Clean Install
enter twrp and factory reset
format data partition (only if coming from Pie or below)
flash the rom
flash GApps (optional)
reboot
Updating from previous version
enter TWRP and wipe dalvik/cache
flash ROM
reboot
Alternative way to install
You can also unzip the file and flash via flashboot only what you need:
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash system system.img
fastboot flash userdata userdata.img (only if not updating or coming from Pie or below)
fastboot flash oem xxxx.img
Now you can boot into TWRP and flash gapps and other stuff if you want.
First boot will get stuck on Sony logo for 30/40 seconds, and maybe reboot itself one or two time. Just have patience and everything will be all right
Downloads:
ROM: Latest Build
OEM: Binaries for 4.9 kernel
TWRP: Official TWRP for Suzu
BitGapps: Suggested GApps
What's works:
RIL
Bluetooth
Wifi
Fingerprint
NFC
Camera
USB tethering
Everything else?
What doesn't:
Random reboots (should be solved in latest build)
WiFi Hotspot
Expected the same bugs for Pie ROM since the kernel and binaries are the same, but let me know if you find anything else, will do my best to try to fix it.
Click to expand...
Click to collapse
Changelogr41
Update sources to r41
Overvolt BIG processor to improve stability on higher frequencies (should fix random reboots)
r33
Update sources to r33
r32.v1b
Reverted patch to enable developer option by default
r32.v1
Removed default searchbar from Launcher3
Enabled developer settings by default
Add MicroG support (testing)
r32:
Initial booting build
Click to expand...
Click to collapse
ROM Version: r41
ROM Status: Stable
Created: 2019-12-04
Last Update: 2020-09-20
Thanks to:
@twain55 for the screenshot and testing
@dslul to help in the bug fixing
@ix5 for the initial patches
sonyxperiadev project for providing sources
and last but not least thanks to all that will test this.
Screenshots
flashed with fastboot and stuck at splash screen
Adi_OP said:
flashed with fastboot and stuck at splash screen
Click to expand...
Click to collapse
Still testing and had the same results. Can you try to use the old OEM IMG for pie and report if boots? If not I'll try It during the weekend and let you know.
EDIT
Tried with the pie OEM IMG and doesn't boot. Will rebuild the boot image this weekend and see how to fix
Stuck at splash screen too, using fastboot!
Same here with twrp..try with and w/o gapps,stuck at sony logo.It seem the problem is at boot image
lookmanns14 said:
Same here with twrp..try with and w/o gapps,stuck at sony logo.It seem the problem is at boot image
Click to expand...
Click to collapse
It seems to me too. I'm trying to find where is the issue. Building another image today and tested on my device but didn't worked either.
Does it work for F5122?
Thank you for your try.
Does it work for F5122 as well.
Hope you to fix this rom as a stable.
Good luck
Sorry for the waiting, I've had a lot of work to do lately. Hope to have news/a new build (at least for boot.img) this weekend.
New images are up. I'll try them this afternoon (out now) but if someone would take the leap before me here it is the link
https://mega.nz/#F!vNtx2QZZ!GuV1qwYXjLk3ajd3xoaPPA
Let me know. And thanks again for helping me testing.
Unfortunately, still stuck at Sony logo... I used the latest OEM released on December 10th, SW_binaries_for_Xperia_Android_10.0.7.1_r1_v2C_loire, will try with SW_binaries_for_Xperia_Android_10.0.7.1_r1_v2B_loire, but I doubt this will change anything!
Iscariah said:
Unfortunately, still stuck at Sony logo... I used the latest OEM released on December 10th, SW_binaries_for_Xperia_Android_10.0.7.1_r1_v2C_loire, will try with SW_binaries_for_Xperia_Android_10.0.7.1_r1_v2B_loire, but I doubt this will change anything!
Click to expand...
Click to collapse
I doubt it too sadly but if still stuck I'm at a loss right now. I've to try to see if I can catch some log even if stuck at Sony. Thanks for the report
Any update on this ROM? Is it still in development?
GOrMHATRe said:
Any update on this ROM? Is it still in development?
Click to expand...
Click to collapse
It is. Latest build still doesn't boot. I'm debugging to see if I can find the problem.
Have we wait for next weekends till any further update?
Any good news
[email protected] said:
Any good news
Click to expand...
Click to collapse
Sadly not yet. Having trouble with the building of r15. I think that could be some changes in Q building system because pie build correctly. Hope to fix in this holidays.
ParanoidNemo said:
Sadly not yet. Having trouble with the building of r15. I think that could be some changes in Q building system because pie build correctly. Hope to fix in this holidays.
Click to expand...
Click to collapse
Cheers
Any good news
Are there still this random reboots and homescreen freezes we have with Pie and the 4.9 kernel?
mase76 said:
Are there still this random reboots and homescreen freezes we have with Pie and the 4.9 kernel?
Click to expand...
Click to collapse
Right now the ROM doesn't boot. The issue is upstream and as far as I know this should be fixed when the v3 of the binaries is released (right now we are at v2c). Hopefully the reboot issue will be fixed but we have to wait sadly.
@ParanoidNemo
Which kernel did you use?
Related
TL;DR: Nexus 9 bootloops with every ROM other than stock.
My Nexus 9 will bootloop whenever any custom ROM is installed on it. I follow the usual steps in TWRP (downloading ROM and Gapps, wiping factory reset, flashing the zips and wipe dalvik/cache) will not get any error during installation and regardless of the ROM, I will get my nexus stuck on Google logo. Then I will have to unroot and install stock again and it'll work.
Ive also tried Wugfresh Nexus Root Toolkit and it won't work either. As long as Im on stock, I can root as well and everything is fine.
Any idea what could be happening? I wanna get rid of the damn lag. Have tried Cyanogenmod, Slimrom6 and Pure Nexus Project. All with their recommended gapps and will always end up with my tablet stuck in the Google logo.
Any help is very appreciated.
Sounds like you are doing everything right..
How long are you waiting for the device to start up ? Is it possible you aren't simply waiting long enough ? I'd give it a good 10 - 20 minutes on 1st boot before deciding it's hung in a boot loop.
I am having the exact same problem. I have tried so many roms that install correctly and then when flashing gapps and rebooting it is stuck on the Google logo. And I left my tablet on for a few hours so its definitely bootlooping.
The only thing that comes to mind is bootloader... If you coming to androind 7.x from android 6.x, you need to flash new bootloader (for example via ADB), otherwise you'll end up in a bootloop.
yup, happening to me too. so, how can i flash the factory image now? thanks.
It's in the stickies. http://forum.xda-developers.com/nexus-9/general/guide-how-to-unlock-bootloader-flash-t3035153
Sent from my Nexus 5X using XDA-Developers mobile app
links to 7.x compatible bootloader where?
maelfilk said:
If you coming to androind 7.x from android 6.x, you need to flash new bootloader (for example via ADB), otherwise you'll end up in a bootloop.
Click to expand...
Click to collapse
I understand that i'll have to use adb (actually fastboot) to flash the bootloader. But where do i get the right one for android 7.x and flpunder device?
Could you please post the links for that?
Thanks in advance!
nexacan said:
I understand that i'll have to use adb (actually fastboot) to flash the bootloader. But where do i get the right one for android 7.x and flpunder device?
Could you please post the links for that?
Thanks in advance!
Click to expand...
Click to collapse
You can download the necessary image here: https://developers.google.com/android/images
Inside the archive you'll find bootloader and vendor
bootloader flashing process: enough to "fastboot flash bootloader boot*.img"?
maelfilk said:
You can download the necessary image here: https://developers.google.com/android/images
Inside the archive you'll find bootloader and vendor
Click to expand...
Click to collapse
I assume i need the latest 7.0.0 (NRD91N, Nov 2016) bootloader which is inside the latest build?
Then i will need to go through the process like:
Code:
fastboot flash bootloader bootloader-flounder-3.48.0.0141.img
Or do i have to do more like described here (Steps 8-9)?
Your help is appreciated, thanks again!
ps: for others who got stuck in the bootloop and don't know how to stop it or turn off the device:
1. reboot into recoverymode in case you have twrp
2. open a terminal
3. type in
Code:
poweroff
an hit enter
Yes, NRD91N
Well , all i did was simple
fastboot flash bootloader bootloader-flounder-3.48.0.0141.img
once complete
fastboot reboot-bootloader
That's it
Still not booting...
maelfilk said:
Yes, NRD91N
fastboot flash bootloader bootloader-flounder-3.48.0.0141.img
fastboot reboot-bootloader
...
That's it
Click to expand...
Click to collapse
Thanks for clarifying that. Unfortunately i still can't boot into AOSP_flounder_11-18-2016.zip
which i flashed afterwards. The bootloader is shown correctly though. But when i start the
Nexus 9 the message https://g.co/ABH is shown in red.
Which rom are you running? A CM build or AOSP?
ps: trying with cm-14.1-20161027-UNOFFICIAL-flounder.zip now, but boot seems to hang too and the upper part
of the Nexus 9 is getting really warm. I will leave it for 15 more minutes to wait and see what happens.
nexacan said:
Thanks for clarifying that. Unfortunately i still can't boot into AOSP_flounder_11-18-2016.zip
which i flashed afterwards. The bootloader is shown correctly though. But when i start the
Nexus 9 the message https://g.co/ABH is shown in red.
Which rom are you running? A CM build or AOSP?
Click to expand...
Click to collapse
Hmm sorry i don't knwo why this is happening.
Currently i reverted back to marshmallow roms, i find them more stable.
Do you have twrp? After flashing bootloader i go to twrp and do complete wipe and format data, then flash new rom. I had no problems booting.
maelfilk said:
Do you have twrp?
Click to expand...
Click to collapse
Sure, the latest from TWRP
twrp-3.0.2-1-flounder.img 13M 2016-08-24 16:30:03 EDT
maelfilk said:
After flashing bootloader i go to twrp and do complete wipe and format data, then flash new rom. I had no problems booting.
Click to expand...
Click to collapse
I will try it again - exactly as you describe it. Maybe i missed a step.
How long did you wait after reboot for the system to start up?
nexacan said:
Sure, the latest from TWRP
twrp-3.0.2-1-flounder.img 13M 2016-08-24 16:30:03 EDT
I will try it again - exactly as you describe it. Maybe i missed a step.
How long did you wait after reboot for the system to start up?
Click to expand...
Click to collapse
About 10-15 minutes
It works now!
Thank you maelfilk, i got i running now.
CM boots properly now - though i cannot configure it. During the Setup process
in the first step of selecting the language it crashes. I am sure this will be fixed
with a later version of CM-14.1.
Does someone know any other source for CM-14.1 for flounder?
Meanwhile i will try AOSP again.
Edit: AOSP boots properly but unfortunately WLAN does not work in the AOSP_flounder_11-18-2016.zip build.
I guess this is why you stick to the 6.x builds maelfilk.
большое спасибо
nexacan said:
большое спасибо
Click to expand...
Click to collapse
Glad it works
As for wlan problem, did you flash the vendor as well? If not it might be the problem
link to the "vendor"
maelfilk said:
Glad it works
As for wlan problem, did you flash the vendor as well? If not it might be the problem
Click to expand...
Click to collapse
Man, you are so helpfull! Where do i find the "vendor" (drivers?) please?
I guess i will find it as it is described here
nexacan said:
Man, you are so helpfull! Where do i find the "vendor" (drivers?) please?
I guess i will find it as it is described here
Click to expand...
Click to collapse
In the archive with bootloader is another archive with vendor and other images. Just flash it in twrp as in the instructions in the link you gave. If you have trouble with wlan or camera it usually means that vendor is outdated.
Black bootscreen and hanging after flashing vendor.img (only vendor.img)
maelfilk said:
In the archive with bootloader is another archive with vendor and other images. Just flash it in twrp as in the instructions...
Click to expand...
Click to collapse
I did that and now there is no bootscreen, and the Nexus 9 does not boot up
Maybe i am missing something again? I did a wipe and fresh install, but that did not help.
Also TWRP disappears after flashing vendor.img
nexacan said:
I did that and now there is no bootscreen, and the Nexus 9 does not boot up
Maybe i am missing something again? I did a wipe and fresh install, but that did not help.
Also TWRP disappears after flashing vendor.img
Click to expand...
Click to collapse
Are you sure you chose to flash vendor.img in vendor partition in twrp?
TeamWin's TWRP Touch Recovery for LG G3 - currently available only for F400 variantshttps://twrp.me/
TWRP is an open source, community project. TWRP development is done by roughly 4 people at this point. We also have a large support community with many people who are willing to answer questions and help people with their devices either through our IRC channel or on forums like xda-developers.
Team Win was originally formed to work on porting WiMAX to CM7 for the HTC EVO 4G. After our work on the EVO 4G we wanted to work on a project that would work on more devices than just the EVO 4G and we settled on working on a recovery. Today TWRP is the leading custom recovery for Android phones.
A custom recovery is used for installing custom software on your device. This custom software can include smaller modifications like rooting your device or even replacing the firmware of the device with a completely custom “ROM” like OmniROM
You can find the source code for TWRP at github.com/omnirom/android_bootable_recovery/
Flashing Instructions
To install recovery images use Flashify / Rashr from Play Store or flash in your current recovery. Otherwise do the following:
1. Go to install, find and select the Images... button.
2. Browse to the image that you downloaded and select it.
3. Choose recovery and swipe to flash.
OR
1. Move recovery.img to internal storage.
2. Open terminal window/command prompt to execute following commands
Code:
adb shell
su
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/recovery
dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
exit
exit
adb reboot recovery
About this TWRP
compiled on LineageOS-14.1 source
always up-to-date
fixed screen brightness
permissive selinux
disabled logd/logcat in recovery
fuse exfat, ntfs-3g, jpeg, usb-otg support
external storage as default storage
touch to wake
backup of all partitions including modem, efs
crypto/decryption may work or not..
Changelog
* 170430
- Initial Build
- Disabled HW crypto due to build fails
* 170501
- Deleted unused flags
- Add back HW crypto
- exfat support
* 170507
- Disabled logd/logcat (fix for "device or resource busy", hopefully)
* 170519
- Updated to v3.1.1
- Fix Aroma Installer crash (hopefully)
Known issues
ZIP files with date check assert can't be installed (eg. crDroid) - Users should delete date check assert in binary by themselves.
AROMA Installer stucks at loading - will be fixed soon..
Download Links
Unofficial | Official
Sources
https://github.com/TheNoFace/android_device_lge_g3-common-TWRP/tree/twrp
(Based on https://review.lineageos.org/#/c/160056/)
Remember to do backup of your current recovery before installing
Any plans for suporting other G3 variants in future?
@fprhqkrtk303: Now have 2 version twrp to flash. Which one to choose to flash? Unofficial or official? Thanks!
Official TWRP for D855 is so bad... sorry to say that. It doesn't work properly and even if LineageOS recommends it it's just not able to flash LOS builds.
When you want to reboot in recovery it hangs in a bootloop and when you want to shut the device off it just turns on back. So far we only have the unofficial version for D855 fully working.
ahk31 said:
Any plans for suporting other G3 variants in future?
Click to expand...
Click to collapse
Planning to support more devices when F400 version is stable.
You can build your own TWRP using my source.
@chuyennho184 @andrewKode Official version from TWRP uses older device tree and actually no one maintains. Recommend using unofficial version.
@fprhqkrtk303: I saw update firmware on March 22th for F400 variants but I don't have a link. Do you have a link? Thanks for bother you.
Updated to v3.1.1 (170519)
fprhqkrtk303 said:
Updated to v3.1.1 (170519)
Click to expand...
Click to collapse
Is aroma bootloop problem fixed in this new version?
MESA said:
Is aroma bootloop problem fixed in this new version?
Click to expand...
Click to collapse
Not tested yet. Can you check?
fprhqkrtk303 said:
Not tested yet. Can you check?
Click to expand...
Click to collapse
Yes. Tried it yesterday. Bootloop problem is still present.
andrewKode said:
Official TWRP for D855 is so bad... sorry to say that. It doesn't work properly and even if LineageOS recommends it it's just not able to flash LOS builds.
When you want to reboot in recovery it hangs in a bootloop and when you want to shut the device off it just turns on back. So far we only have the unofficial version for D855 fully working.
Click to expand...
Click to collapse
LoL i maintain twrp for d855 i don't have any issue with that recovery(3.1.1) fully tested..
and this problem cause by bootloader..
or you mean this
Fixed rebooting when no OS is present (Dees_Troy)
"unofficial version for D855 fully working."
Nope dadi11 twrp encrypt no work.. ;]
ZjemCiKolege said:
LoL i maintain twrp for d855 i don't have any issue with that recovery(3.1.1) fully tested..
and this problem cause by bootloader..
or you mean this
Fixed rebooting when no OS is present (Dees_Troy)
"unofficial version for D855 fully working."
Nope dadi11 twrp encrypt no work.. ;]
Click to expand...
Click to collapse
Dude, Idk what you're maintaining but this is what happens:
- TWRP sometimes does not reboot back in recovery (it hangs on LG screen)
- hangs on flashing LineageOS
- When chosed to turn off the device from the recovery it turns back ON right after it shuts down.
andrewKode said:
Dude, Idk what you're maintaining but this is what happens:
- TWRP sometimes does not reboot back in recovery (it hangs on LG screen)
- hangs on flashing LineageOS
- When chosed to turn off the device from the recovery it turns back ON right after it shuts down.
Click to expand...
Click to collapse
1. I try but did not happen.
2. Build of lineage?(i flash each version from february to 21.04) no any issue.
3. Issue of custom rom(problem with turn on charger and boot same issue..) ;]
MESA said:
Is aroma bootloop problem fixed in this new version?
Click to expand...
Click to collapse
Hello, apparently no...
https://twrp.me/site/update/2017/05/19/twrp-3.1.1-0-released.html
If it's a software problem, it would be the problem of AROMA devs, but if it's related to software keys incompatibility it's will be the work of TWRP devs.
DisclaimerThis software comes wth no warranty,XDA staff ,myself or TeamWin stuff can't be hold responsible for any damage it may cause to your device.
Note: Currently Oreo 8.1 custom roms are supported only on BKL-L04 with EMUI 8.1
Download and Installation
* Download twrp recovery
* Start your device in fastboot mode
* Install the recovery using the following command:
Code:
fastboot flash recovery_ramdisk [name of the file].img --> ex: fastboot flash recovery_ramdisk twrp_blanc_0.1.img
* Restart with this command:
Code:
fastboot reboot
* As soon as you execute the restart command,remove the USB cable and keep pressing Volume UP,so the device will boot to TWRP.This is to avoid that the device boot to OS,overwritting TWRP recovery.
Features
Internal storage decryption = working
MTP and OTG connection = working
Backup&Restore = working
Note: There are no sources for this yet,because is based on the work of @zxz0O0 ,from Honor 9 forum.
Credits
**** @zxz0O0 - This wouldn't be possible without this guy,so big big thank to him.I used his base to make this recovery work ,so in sign of respect his nick will also be on the TWRP boot screen.Thank again buddy!
**** TeamWin project ,obviously.
Download links
twrp_blanc_0.1.img - initial test release
twrp_bkl_0.2.img - OEMinfo partition is available for backup
twrp_bkl_0.3.img - /cache mounting is fixed,backup /vendor as image (vendor still can't be mounted)
twrp_bkl_0.4.img - /vendor mounting/unmounting is now fixed (thx @ante0 for the script)
twrp_bkl_0.5.img - mounting/unmounting issues shound be fixed , added a new option to exclude OEM path from wiping with Factory Reset and can be enabled/disabled in settings (thx Team OpenKirin for this), this version will work even with newer updates that bump security patch version.
twrp_bkl_0.6.img - Cache wiping issue is now fixed
twrp_bkl_0.7.img - fixed decryption on EMUI 8.1 (now you can use the same password/pin/pattern to decrypt in TWRP), /recovery_ramdisk no longer available for backup./vendor no longer available for backup (use /vendor_image instead),/system and /data can be unmounting issue with 8.1 devices is now fixed.
Pretoriano80 said:
Internal storage decryption = working
MTP and OTG connection = working
Backup&Restore = working
Click to expand...
Click to collapse
Thanks man! :laugh: Need to test this!
IcipherPT said:
Thanks man! [emoji23] Need to test this!
Click to expand...
Click to collapse
No problem! Please report back if it's working or not.
Pretoriano80 said:
No problem! Please report back if it's working or not.
Click to expand...
Click to collapse
wipe everything to decrypt?
ngoralph said:
wipe everything to decrypt?
Click to expand...
Click to collapse
Nope, just decrypting, like you do when your phone is starting and asks for PIN! [emoji6]
Pretoriano80 said:
No problem! Please report back if it's working or not.
Click to expand...
Click to collapse
Just tested on my honor view 10. It was asking for a password to decrypt. I entered my lockscreen pass and everything was decrypt.
so TWRP CAN decrypt
@youtuber123
did you try a nandroid backup?
youtuber123 said:
Just tested on my honor view 10. It was asking for a password to decrypt. I entered my lockscreen pass and everything was decrypt.
so TWRP CAN decrypt
Click to expand...
Click to collapse
Ok, so it's working!Great,please let me know if something it's broken (backup, restore, MicroSD mounting, etc).
Pretoriano80 said:
Ok, so it's working!Great,please let me know if something it's broken (backup, restore, MicroSD mounting, etc).
Click to expand...
Click to collapse
nandroid (backup and restore) is working
mtp is working too
and micro usb mounting is working
didn't tested to flash something using twrp
youtuber123 said:
nandroid (backup and restore) is working
mtp is working too
and micro usb mounting is working
didn't tested to flash something using twrp
Click to expand...
Click to collapse
There's not much stuff to flash for this device! [emoji16]
Good, finally a useful twrp....
Can we flash LOS using this now?
@Pretoriano80
tried your recovery at my view 10. flashed it via fastboot. had no success. your twrp is hanging at the start screen. tried to flash it via the twrp of dees_troy, the same result. recovery is not booting completely, remains at the twrp start screen. any ideas?
kurvenmeister said:
@Pretoriano80
tried your recovery at my view 10. flashed it via fastboot. had no success. your twrp is hanging at the start screen. tried to flash it via the twrp of dees_troy, the same result. recovery is not booting completely, remains at the twrp start screen. any ideas?
Click to expand...
Click to collapse
Which version? Another user reported that is working.
Edit: More details about your device?Which version do you have exactly?
the twrp_blanc_0.1.img
the dl-link of twrp_bkl_0.2.img is not working
kurvenmeister said:
the twrp_blanc_0.1.img
the dl-link of twrp_bkl_0.2.img is not working
Click to expand...
Click to collapse
Ok thank,link is fixed .but if the initial one didn't booted ,i don't think this will do.Which version of Honor 10 do you have (european,usa,etc)?I'm not sure it will work on the US version or any other version which is based on Oreo 8.1.
@Pretoriano80
dl-link worked. tried the second version of your recovery. still no success. it is hanging at the start screen. nothing else happend. european bkl-l09, resurrection remix, oreo 8.1
kurvenmeister said:
@Pretoriano80
dl-link worked. tried the second version of your recovery. still no success. it is hanging at the start screen. nothing else happend. european bkl-l09, resurrection remix, oreo 8.1
Click to expand...
Click to collapse
The custom rom might be the culprit!I didn't tested on custom roms.
Pretoriano80 said:
Ok thank,link is fixed .but if the initial one didn't booted ,i don't think this will do.Which version of Honor 10 do you have (european,usa,etc)?I'm not sure it will work on the US version or any other version which is based on Oreo 8.1.
Click to expand...
Click to collapse
Hey mate nice to see you here
Nice job with the recovery! I've been handed out an US View 10 a couple weeks ago (with Android 8.1 pre-release stuff), I'll test it out for you.
twrp-3.2.1-0-berkeley.img didn't boot on BKL-L04 (dark screen and reboot), but Ethan made some changes and twrp-3.2.1-1-berkeley.img does work fine.
I've been told that some selinux changes were needed to boot 8.1 stuff, some critical service that fails to run because it can't find the right policy, something related to recovery_vendor partition that runs it.
It will work in 8.0 setups also just fine.
I'll let you know how it goes :fingers-crossed:
Hope we get 8.1 kernel sources soon so I blu_spark this blue beauty
Rommco05 said:
I succesfuly make full backup (except data) and flashed busybox. I dont need decrypted data all seems to be fine. In backup section just missing OEM
Click to expand...
Click to collapse
Latest version should have Oeminfo available for backup! Did you tested that version?
eng.stk said:
Hey mate nice to see you here
Nice job with the recovery! I've been handed out an US View 10 a couple weeks ago (with Android 8.1 pre-release stuff), I'll test it out for you.
twrp-3.2.1-0-berkeley.img didn't boot on BKL-L04 (dark screen and reboot), but Ethan made some changes and twrp-3.2.1-1-berkeley.img did.
I've been told that some selinux changes were needed to boot 8.1 stuff, some critical service that fails to run because it can't find the right policy, something related to recovery_vendor partition that runs it.
It will work in 8.0 setups also jsut fine.
I'll let you know how it goes :fingers-crossed:
Click to expand...
Click to collapse
Hi! My favourite kernel developer is here, nice!
I have a guess on what may be wrong, but i'm not sure. Let me know if you figure out! [emoji6]
Sekiyama-Kernel for Oneplus N200 5G
Features:
Main Features:
- Based on latest kernel sources from OnePlus for Android 11
- Upstreamed against latest kernel-common (android12-5.4-lts)
- Linux-Stable-Upstream included to latest 5.4.179
- compiled with Clang 13.0.1 prebuilt from Google
- built with -O3 speed optimizations
- Link-Time-Optimization (ThinLTO)
- Link the kernel with LLD and use RELR-Relocation
- fix several coding issues detected by newer Clang-Toolchains
- include important fixes/improvements from kernel/common
- Supports ALL variants, NA/TMO/OEM
- Wireguard Support
- If you want magisk, you must patch first!!!
Downloads:
https://github.com/ArtiicPanda/oneplus-sm4350/releases
Requirements
- Unlocked Bootloader
- USB Debugging in developer options enabled
- Latest adb and fastboot
How to flash the Kernel:
Boot to fastboot/bootloader to flash boot.img:
Either select Reboot to bootloader option via buttons
or type:
Code:
adb reboot-bootloader
Now in fastboot flash boot.img
Commands:
Code:
fastboot flash boot boot.img
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
Reboot either via buttons
or by typing
Code:
fastboot reboot
@Freak07 for his kernel thread from which I drew inspiration.
Source Code: https://github.com/ArtiicPanda/oneplus-sm4350
reserved
reserved
Any updates?
blowtorchhonor said:
Any updates?
Click to expand...
Click to collapse
Need some time to create a great OP
Tests builds are available here:
Join «Nord N200 Testers» on Telegram: https://t.me/OnePlusNordN2005G
Released. Thank you to all that helped test prior to release. Enjoy!
I can vouch that this kernel really helps this device run faster. I already tested many things from bluetooth to phone calls and everything works. Enjoy everyone!
11.0.2 Update posted, changelog on github
Wonderful work to you and @Travisholt92. Really surprised how far everyone has gotten in such a small amount of time.
Wivioo said:
Wonderful work to you and @Travisholt92. Really surprised how far everyone has gotten in such a small amount of time.
Click to expand...
Click to collapse
Apparently all it took to kick things off was me extracting the defconfig from the stock kernel and showing it could be built (partially) and then @ArtiicPanda being awesome decided to get in on the action
Travisholt92 said:
Apparently all it took to kick things off was me extracting the defconfig from the stock kernel and showing it could be built (partially) and then @ArtiicPanda being awesome decided to get in on the action
Click to expand...
Click to collapse
definitely was a team effort. again thanks to the testers as well. @blowtorchhonor @TheLoonyRebel
Just flashed 11.0.1 (couldn't find a binary for 11.0.2) and it successfully booted on my TMO/metropcs flashed to unlocked firmare running latest Pixel Experience A12 GSI
cognitoinc566 said:
Just flashed 11.0.1 (couldn't find a binary for 11.0.2) and it successfully booted on my TMO/metropcs flashed to unlocked firmare running latest Pixel Experience A12 GSI
Click to expand...
Click to collapse
I think they forgot to post 11.0.2
edit: they forgot to compile the source to a .img
No, there were some minor issues with 11.0.2 so it's being reworked, just use 11.0.1 until then.
Update posted, change log on GitHub
I have this notification that says serial console enabled performance is impacted to disable check bootloader and I have no idea how to disable it. I'm also unable to use usb debugging for more than 2 seconds as it goes away and stops
Tyreethetruth said:
I have this notification that says serial console enabled performance is impacted to disable check bootloader and I have no idea how to disable it. I'm also unable to use usb debugging for more than 2 seconds as it goes away and stops
Click to expand...
Click to collapse
Same here. I installed 11.0.2.1, the most recent one on T-Mobile stock 11.0.1.9 and the same notification shows up.
After reboot, the screen got darker, and can't control brightness anymore.
Going back to stock boot...
lentm said:
Same here. I installed 11.0.2.1, the most recent one on T-Mobile stock 11.0.1.9 and the same notification shows up.
After reboot, the screen got darker, and can't control brightness anymore.
Going back to stock boot...
Click to expand...
Click to collapse
I fixed it, you just have to reflash magisk via fastboot
Tyreethetruth said:
I fixed it, you just have to reflash magisk via fastboot
Click to expand...
Click to collapse
I patched kernel image via magisk then flashed magisk patched kernel image via fastboot and it happened.
lentm said:
I patched kernel image via magisk then flashed magisk patched kernel image via fastboot and it happened.
Click to expand...
Click to collapse
Try flashing the kernal via fastboot then fully boot the phone then flash the magisk patched image again via fastboot and it will get rid of the notification
Android Open Source Project android-11.0.0_r46Disclaimer:* Your warranty is now void.
* We are not responsible for anything that may happen to your phone by installing any custom ROMs and/or kernels.
* You do it at your own risk and take the responsibility upon yourself and you are not to blame us or XDA and its respected developers.
Instruction:
Unlock boot loader
Connect the device to your computer in Fastboot mode (by pressing volume up while inserting the USB cable)
Download and extract the vendor image provided by Sony
Flash the vendor image provided by Sony
Code:
fastboot flash oem SW_binaries_for_Xperia_Android_11_4.14_v8a_yoshino.img
Download and extract AOSP image android-11.0.0_r46.zip
Flash the boot, recovery, system, vendor and userdata images
Code:
fastboot flash boot boot.img
Code:
fastboot flash recovery recovery.img
Code:
fastboot flash system system.img
Code:
fastboot flash vendor vendor.img
Code:
fastboot flash userdata userdata.img
Code:
fastboot reboot
DONE!
If you have any problem with this recovery image, then download and flash the latest TWRP recovery release.
What's working:
Wifi
Hotspot
Bluetooth
GPS
4G/3G/2G
Camera
Fingerprint sensor (work without press the button)
BUGS:
TWRP recovery goes into bootloop, so start twrp again you need to flash the userdata.img (factory reset) via fastboot. There is this twrp recovery here on xda link.
Screen lag
After each start / restart the screen must be turned off and on again get to the homescreen
Credits:
Sony Xperia Developer World
Source code:
GitHub
Info:
ROM OS Version: Android 11
ROM Release: android-11.0.0_r46
ROM Kernel: Linux 4.14
Based On: AOSP
Status: Testing
Created 2022-02-14
Last Updated 2022-02-17
Reserved
bugs?
nathankaunang said:
bugs?
Click to expand...
Click to collapse
I am currently testing the build, as soon as I find bugs I will report them. If you have specific requests to test, please propose them. At the moment everything seems to be working fine.
D_Riccardo said:
I am currently testing the build, as soon as I find bugs I will report them. If you have specific requests to test, please propose them. At the moment everything seems to be working fine.
Click to expand...
Click to collapse
I mean, are the laggy screen bug or the green camera, or the signal drops bugs fixed?
JimKatsanos said:
I mean, are the laggy screen bug or the green camera, or the signal drops bugs fixed?
Click to expand...
Click to collapse
The screen lags slightly, the camera work perfect and for now I did not see any signal drops
Hi, the bugs I found:
- after each start / restart the screen must be turned off and on again get to the homescreen
- SIM card is not detected at all
hihiman1 said:
Hi, the bugs I found:
- after each start / restart the screen must be turned off and on again get to the homescreen
- SIM card is not detected at all
Click to expand...
Click to collapse
Thank you, I have also encountered that problem of the screen at startup. The sim card not detected it's strange I tested the data traffic and it works. I think this kernel 4.14 has more problems than the 4.4.
D_Riccardo said:
...The sim card not detected it's strange I tested the data traffic and it works. I think this kernel 4.14 has more problems than the 4.4.
Click to expand...
Click to collapse
Maybe it's linked to the latest version of SW_binaries_for_Xperia_Android_11_4.14_v9a_yoshino.zip (released 15.02.2022) v8a is no longer available
hihiman1 said:
Maybe it's linked to the latest version of SW_binaries_for_Xperia_Android_11_4.14_v9a_yoshino.zip (released 15.02.2022) v8a is no longer available
Click to expand...
Click to collapse
Yes, I see they updated the .zip file on the official site, luckily I didn't delete the file I used, I uploaded the v8a version here: https://www.udrop.com/6n1x/SW_binaries_for_Xperia_Android_11_4.14_v8a_yoshino.zip
Let me know if at least solved the problem with the sim card, so I will update the link in the post.
D_Riccardo said:
Yes, I see they updated the .zip file on the official site, luckily I didn't delete the file I used, I uploaded the v8a version here: https://www.udrop.com/6n1x/SW_binaries_for_Xperia_Android_11_4.14_v8a_yoshino.zip
Let me know if at least solved the problem with the sim card, so I will update the link in the post.
Click to expand...
Click to collapse
Yes now it works - please add the link to SW_binaries also in the 1st post
Wouldn't it be said to install the rom on the g8343?
Ramfisrd said:
Wouldn't it be said to install the rom on the g8343?
Click to expand...
Click to collapse
I would not risk to install to g8343, it could work as not