• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!
  • Fill out your device list and let everyone know which phones you have!    Edit Your Device Inventory

[ROM][8.0.0][AOSP][SUZU] Oreo Builds

Search This thread

Anton2365

Member
Feb 4, 2015
20
7
20
Tirol
can't flash SW_Binaries...

Yo guys... :)
I want to try out the latest build - but there is a big problem: I cannot flash the oem image, as fastboot exits with this message:

Code:
fastboot flash oem .\SW_binaries_for_Xperia_AOSP_O_MR0_4.4_v05_loire\SW_binaries_for_Xperia_AOSP_O_MR0_4.4_v05_loire.img
target reported max download size of 536870912 bytes
sending 'oem' (217313 KB)...
OKAY [  6.876s]
writing 'oem'...
FAILED (remote: Command not allowed)
finished. total time: 6.876s

:confused:

I already unlocked my BL (duh - I can install custom ROMs on it). Also I do have an OEM partition.
I even tried reinstalling drivers, reinstalling Minimal ADB & Fastboot and also tried to re-download that image from Sony directly...

If anyone knows a solution to that, that would be great... :D

Thx in advance!
 

cyanides13

Senior Member
Jun 25, 2017
273
54
You can use my build with 4.4 kernel. After flashing zip don't forget flash OEM binary for Android N

Thanks alot man I'll save this and flash stock with EMMA when I have time.

I was looking for AOSP 7.1.2 because Oreo dont support xposed and gravitybox yet may ill try your Oreo build when xposed for oreo is out thanks again.
 

cyanides13

Senior Member
Jun 25, 2017
273
54
Well this sucks turns out my usb port is broken computer cant detect my device but I can still recharge my device.

I'll need to wait for my replacement usb port before I can start to flash the oem...
 

policepooh

Senior Member
Jul 18, 2016
69
5
I have error when i flash SW_binaries_for_Xperia_AOSP_O_MR0_4.4_v05_loire.img file is there any other way i tried both with flash tool and command prompt
i really wants to try with F5122
please advice
 

cyanides13

Senior Member
Jun 25, 2017
273
54
I have error when i flash SW_binaries_for_Xperia_AOSP_O_MR0_4.4_v05_loire.img file is there any other way i tried both with flash tool and command prompt
i really wants to try with F5122
please advice

Make sure you have unlocked bootloader

Flash latest stock rom for your device using Sony emma

Boot device, intall TWRP

Flash oreo repo zip in TWRP

Flash sw binaries thru fastboot

Boot phone.

Enjoy Oreo
 
  • Like
Reactions: Meloferz

policepooh

Senior Member
Jul 18, 2016
69
5
Make sure you have unlocked bootloader

Flash latest stock rom for your device using Sony emma

Boot device, intall TWRP
Flash oreo repo zip in TWRP
Flash sw binaries thru fastboot
Boot phone.
Enjoy Oreo

thanks for your reply
when i try to flash the binaries through fastboot it says failed

25/030/2017 10:30:17 - INFO - FAILED (remote: size too large)
25/030/2017 10:30:17 - INFO - finished. total time: 6.820s
25/030/2017 10:30:17 - INFO - FASTBOOT Output:
target reported max download size of 536870912 bytes
sending 'boot' (217313 KB)...
OKAY [ 6.818s]
writing 'boot'...
FAILED (remote: size too large)
finished. total time: 6.820s

even when i flash with TWRP it says
size of image is larger than target device
is there any other way to do this
please advice
 

cyanides13

Senior Member
Jun 25, 2017
273
54
thanks for your reply
when i try to flash the binaries through fastboot it says failed

25/030/2017 10:30:17 - INFO - FAILED (remote: size too large)
25/030/2017 10:30:17 - INFO - finished. total time: 6.820s
25/030/2017 10:30:17 - INFO - FASTBOOT Output:
target reported max download size of 536870912 bytes
sending 'boot' (217313 KB)...
OKAY [ 6.818s]
writing 'boot'...
FAILED (remote: size too large)
finished. total time: 6.820s

even when i flash with TWRP it says
size of image is larger than target device
is there any other way to do this
please advice


Did you flash sony stcok ROM first using EMMA?
 

Anton2365

Member
Feb 4, 2015
20
7
20
Tirol
thanks for your reply
when i try to flash the binaries through fastboot it says failed

25/030/2017 10:30:17 - INFO - FAILED (remote: size too large)
25/030/2017 10:30:17 - INFO - finished. total time: 6.820s
25/030/2017 10:30:17 - INFO - FASTBOOT Output:
target reported max download size of 536870912 bytes
sending 'boot' (217313 KB)...
OKAY [ 6.818s]
writing 'boot'...
FAILED (remote: size too large)
finished. total time: 6.820s

even when i flash with TWRP it says
size of image is larger than target device
is there any other way to do this
please advice

It said "writing 'boot'...", so you chose to flash that image to boot partition. (I guess you probably wrote "fastboot flash boot [...].img")
If so, you have to change "boot" to "OEM", as it belongs to the OEM partition. So the command should be:
Code:
fastboot flash oem xyz.img
(replace "xyz.img" with the actual name/path...) ;)

---------- Post added at 16:25 ---------- Previous post was at 16:16 ----------

Also @lubik1 I managed to updade to the latest stock ROM, reflashed root & TWRP (BL still unlocked), and I get the same Fastboot error again... :/

I also went a bit "crazy" and tried to flash that thing with dd, after doing so it said "mount: error: unknown filesystem" and I restored my backup. So I guess I will give up and wait if either another custom ROM upgrades to Oreo or just stay at stock for now and wait for the official update... :(

But thanks anyway! :)
 
  • Like
Reactions: policepooh

policepooh

Senior Member
Jul 18, 2016
69
5
[/COLOR]Also @lubik1 I managed to updade to the latest stock ROM, reflashed root & TWRP (BL still unlocked), and I get the same Fastboot error again... :/

I also went a bit "crazy" and tried to flash that thing with dd, after doing so it said "mount: error: unknown filesystem" and I restored my backup. So I guess I will give up and wait if either another custom ROM upgrades to Oreo or just stay at stock for now and wait for the official update... :(

But thanks anyway! :)[/QUOTE]

thanks man you are right all this time i was doing it wrong ill try and let you know
 

cyanides13

Senior Member
Jun 25, 2017
273
54
You can use my build with 4.4 kernel. After flashing zip don't forget flash OEM binary for Android N

Got it to work with my device also got Google camera to work but I have a problem when watching videos in YouTube or any streaming apps the speaker crackles and sometimes just hangs and buzzes very loudly.

Lots of random restarts too.
 
Last edited:

cyanides13

Senior Member
Jun 25, 2017
273
54
I was able to install Oreo 8.0.0 by lubik.

It's a great ROM works very smooth but not perfect.

Pros
-Smooth and fast.
-Google camera 5.1 by BSG works but not perfect yet.
-Stock experience.

Cons
-Can't detect my sim card. F122 ( I don't use simcard 2 I have memory card)
-Fingerprint is buggy / slow
 

Top Liked Posts

  • There are no posts matching your filters.
  • 24
    [ROM][8.0.0][AOSP][SUZU] Oreo Builds
    SUZU F5121 and F5122

    Just builded AOSP from source for test. Not develop, only for testing new futures, so now you can try Oreo AOSP

    i'm not responsible for any damage caused with your device after flashing this ROM. Flash only on your own risk.

    Download (GDrive repo)
    AOSP Drive
    Install:
    1) Copy to SD card and flash with recovery
    2) Download SW_binaries_for_Xperia_AOSP_O_MR0_4.4_v05_loire.img and flash it via fastboot with:
    Code:
    fastboot flash oem SW_binaries_for_Xperia_AOSP_O_MR0_4.4_v05_loire.img
    3) Flash SuperSU
    4) Reboot.


    Feature

    Working:

    - Wi-Fi
    - Bluetooth
    - Fingerprint (partially)
    - Gapps included
    - GPS
    - Sensors
    - Dual Sim (need testers)
    - Camera

    Not working for now:
    - You tell me

    Builded with
    Code:
    https://github.com/SonyAosp
    sources

    Screenshots:
    Screenshot_20171005-100126.pngScreenshot_20171005-100155.pngScreenshot_20171005-100309.jpg
    7
    today i have build new version AOSP 8.0.0 ROM with This repo
    and call speaker worked now. camera still not working.

    Screenshot_20171008-102559.pngScreenshot_20171008-102703.pngScreenshot_20171008-103534.jpg
    4
    yes got it i tried to make it by the way is your rom is having random restart i face this issue
    and is there any update near by

    i'm building new builds right now.
    4
    upload a new builds with working camera.
    for now we have only fingerprint problems and some times a random reboots

    for working video camera - install open camera and enable API v2.0 on settings.
    4
    updated build to 14.10.17 for single and later for dual (compiling now)