This was compiled by me from Sony's AOSP branch for the Z3 Compact. My bootloader is not unlocked so these have not been tested yet. Why no flashable zip? Before I go through the trouble of making one I want to make sure it at least boots. There has been no modifications what so ever.
If it boots then we can make it into a flashable zip.
instructions:
Have an unlocked bootloader
do a full back up or have a way to get back to stock in case something goes wrong
boot into recovery and do a factory reset
boot into fastboot
flash the images in fastboot
fastboot flash boot boot.img
fastboot flash system system.img
flash Gapps (search xda for them)
reboot
pray it boots...
What works?
It boots...
no idea.. you tell me
What's broken?
No idea.. you tell me..
Images can be downloaded on my website:
http://graffixnyc.com/z3compact.php
Disclaimer: I am not responsible if you use this and brick your device or if your device blows up, implodes, flames start shooting from it or it kills your neighbor's dog. Flash at your own risk. Again, I am not responsible.... It was the other guy... I swear....
I'll take this one...
one more for good luck
The system.img seems corrupt?
C:\adt\sdk\platform-tools>fastb..
sending 'system' (264722 KB)...
OKAY [ 8.289s]
writing 'system'...
FAILED (remote: Unknown chunk type)
finished. total time: 27.345s
NisseGurra said:
The system.img seems corrupt?
C:\adt\sdk\platform-tools>fastb..
sending 'system' (264722 KB)...
OKAY [ 8.289s]
writing 'system'...
FAILED (remote: Unknown chunk type)
finished. total time: 27.345s
Click to expand...
Click to collapse
Did you check the md5? It seems like yours didn't fully download. it should be like 394MB. I created and uploaded it from my linux machine and got the md5 from that file. Uploaded to my ftp server then downloaded it from a windows machine and checked the md5 and it matched (just to make sure the upload went ok)
graffixnyc said:
Did you check the md5? It seems like yours didn't fully download. it should be like 394MB. I created and uploaded it from my linux machine and got the md5 from that file. Uploaded to my ftp server then downloaded it from a windows machine and checked the md5 and it matched (just to make sure the upload went ok)
Click to expand...
Click to collapse
Yes, u correct, download was cut somehow, trying again
Edit: Booting
Booted up nicely, no wifi, network tho
Edit2: Needed to back to old kernel to be able to wipe data. (no recovery in lolipop kernel?)
Edit 3: some reboots, no usb storage, no external sd, no sound or camera
But its very snappy, looking forward to a functional aosp
NisseGurra said:
Yes, u correct, download was cut somehow, trying again
Edit: Booting
Click to expand...
Click to collapse
Anxious to know if it boots and what does and doesn't work
NisseGurra said:
Yes, u correct, download was cut somehow, trying again
Booted up nicely, no wifi, network tho
Edit2: Needed to back to old kernel to be able to wipe data. (no recovery in lolipop kernel?)
Edit 3: some reboots, no usb storage, no external sd, no sound or camera
But its very snappy,
Click to expand...
Click to collapse
good to hear. im going to try it later
Wow,thanksss
I hope someone can find root for locked-bl cos I want aospppp.
Damn this sh!TTY DRM malarky.
If anyone flashes it, can they take a video of the device running it?
I did not install the system.img, but I installed the launcher
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Could you maybe make a zip of it?
If so we could then copy the vendor folder from the phone into the zip and check if that fixes any of the bugs.
Here are all the folders being in system.img
Ah sorry I meant as a flashable zip
It's a quick and dirty way to test for problems with the binaries but it works quite well.
I would need the file Meta.inf to realize the zip flashable
Edit: Could use me to build Meta.inf?
@_MutantX_ can you please share the wonderful wallpaper?
thanks
moly82 said:
@_MutantX_ can you please share the wonderful wallpaper?
thanks
Click to expand...
Click to collapse
Hello,
If you speak about the wallpaper of my screenshots, you can find him in the theme : Тема eXPERIAnZ - Azuro
_MutantX_ said:
Hello,
If you speak about the wallpaper of my screenshots, you can find him in the theme : Тема eXPERIAnZ - Azuro
Click to expand...
Click to collapse
thanks my friend. unfortunately I can't download it as it says my device is not compatible (don't have a sony phone).. maybe you could share only the wallpaper? otherwise, never mind and thanks in any case! (and sorry for ot!)
moly82 said:
thanks my friend. unfortunately I can't download it
Click to expand...
Click to collapse
http://goo.gl/rQHnx9
Related
I hate to be a newbie but I really read through the entire troubleshooting guide and didn't really understand how to proceed.
I have a rooted Evo 4G LTE with latest stock ROM and TWRP recovery installed (2.5).
This morning my device was pissing me off so I thought it would be a good idea to flash it with CyanogenMod. I went into TWRP, wiped EVERYTHING. loaded the CYanogen Zip on the SD Card, and flashed. Device went right into soft brick.
Tried to flash a couple of other ROMS, also didn't work. in the mean time I discovered BeanStalk which I think is the ROM I want to use.
I have ADB / Fastboot / Latest drivers installed on my computer but when I try to do anything it acts like the device is not connected.
Any advice how to proceed?
From the troubleshooting guide I think my problem might be:
Missing ROM Due to a misunderstanding, you have already wiped all ROM data from phone (cache, dalvik, and system) and fastboot flashed the kernel. Now phone hangs on HTC boot screen and will not load Android. Only the kernel has been flashed, the screen hangs because there is no OS to load. Fear not, return to recovery and flash the ROM package that your boot.image originated from. Now select reboot to system and wait for your phone to restart. The kernel will boot, your OS will load, and all will be right with the world.
Click to expand...
Click to collapse
But I already tried to flash the rom package ( I think).
Help would be much appreciated! thank you!
yoerz said:
I hate to be a newbie but I really read through the entire troubleshooting guide and didn't really understand how to proceed.
I have a rooted Evo 4G LTE with latest stock ROM and TWRP recovery installed (2.5).
This morning my device was pissing me off so I thought it would be a good idea to flash it with CyanogenMod. I went into TWRP, wiped EVERYTHING. loaded the CYanogen Zip on the SD Card, and flashed. Device went right into soft brick.
Tried to flash a couple of other ROMS, also didn't work. in the mean time I discovered BeanStalk which I think is the ROM I want to use.
I have ADB / Fastboot / Latest drivers installed on my computer but when I try to do anything it acts like the device is not connected.
Any advice how to proceed?
From the troubleshooting guide I think my problem might be:
But I already tried to flash the rom package ( I think).
Help would be much appreciated! thank you!
Click to expand...
Click to collapse
If you are s-on you have to fastboot flash or use Flash Image GUI to flash the boot.img/kernel first then flash the rom from twrp
bigdaddy619 said:
If you are s-on you have to fastboot flash or use Flash Image GUI to flash the boot.img/kernel first then flash the rom from twrp
Click to expand...
Click to collapse
Thanks for the help man, I'm just not sure HOW to flash the boot.img/kernel first then flash the rom from twrp
1. Where do I get the Boot.img/kernel? is it just a file I download?
2. What's the command to flash it to the device?
THANK U
You can get a copy of Flash Image GUI here to flash the kernel or pull the boot.img from the rom zip and put it in the folder you have adb and fastboot in and fastboot flash from there.
Here is a guide you can look at to show you how to do the whole process
http://forum.xda-developers.com/showthread.php?p=40848479#post40848479
bigdaddy619 said:
You can get a copy of Flash Image GUI here to flash the kernel or pull the boot.img from the rom zip and put it in the folder you have adb and fastboot in and fastboot flash from there.
Here is a guide you can look at to show you how to do the whole process
http://forum.xda-developers.com/showthread.php?p=40848479#post40848479
Click to expand...
Click to collapse
Well, clearly "Flash Image GUI" isn't going to help me because as I stated before, my device is in boot loop.
I've placed boot.img in my C:\ROOT folder where I keep all my root related files (like ADB and FASTBOOT) but when I run the command:
fastboot flash boot.img
I get the error: unknown partition 'boot.img' error cannot determine image filename for boot.img
Should be
fastboot flash boot boot.img
at this point it just goes < WAITING FOR DEVICE >
I think this is part of the problem. Even though I installed the latest HTC Drivers it seems the computer isn't recognizing the device. When I'm in TWRP and I mount it - it DOES show up in My computer. But not when I'm at that first boot menu.
yoerz said:
at this point it just goes < WAITING FOR DEVICE >
I think this is part of the problem. Even though I installed the latest HTC Drivers it seems the computer isn't recognizing the device. When I'm in TWRP and I mount it - it DOES show up in My computer. But not when I'm at that first boot menu.
Click to expand...
Click to collapse
Try this
On your PC go to device manager and find your phone, right click and select properties
Select the driver tab
Select update driver
Select browse my comp
Let me pick
Look for ADB USB device or similar should be one of the first couple choices
Select MyHTC install and you should be good
Whats next
OK! turns out I just needed a restart. I ran the command:
C:\ROOT>fastboot flash boot boot.img
sending 'boot' (5770 KB)...
OKAY [ 0.899s]
writing 'boot'...
OKAY [ 1.461s]
finished. total time: 2.360s
Now what? what's the next command? do I flash the rom? the recovery?
yoerz said:
OK! turns out I just needed a restart. I ran the command:
C:\ROOT>fastboot flash boot boot.img
sending 'boot' (5770 KB)...
OKAY [ 0.899s]
writing 'boot'...
OKAY [ 1.461s]
finished. total time: 2.360s
Now what? what's the next command? do I flash the rom? the recovery?
Click to expand...
Click to collapse
Choose recovery from the bootloader then flash the rom like you normally would
ALL GOOD
NEVER MIND! That totally did it! Wonderful! Thank you so much for your help man!
I REALLY appreciate it!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hi xda !
As the title says, my Prime can't get into recovery, and I can't factory reset it from within Android's settings either for some reason. How or why this happened, I don't know. I wish I knew, but it's as if everything related to recovery has just disappeared.
It can boot into Android no problem and I can connect to it via fastboot, which in my eyes just make this whole thing seem even weirder.
The tablet is running stock rooted Android 4.1.1, bootloader version is, I think - not completely sure, US_epad-10.4.2.15-20120917. I am not sure if that is the right number, so here you go:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
When selecting the recovery option it just hangs there until I reboot the tablet.
So far I've tried flashing TWRP 2.6.3.0-JB through fastboot, which finished successfully (at least according to fastboot, anyway) with no errors. But still recovery is nowhere to be found.
Does anyone have any idea how to solve this problem and get recovery back on my Prime ? Or at least factory reset it without recovery ?
Tricky547 said:
Hi xda !
As the title says, my Prime can't get into recovery, and I can't factory reset it from within Android's settings either for some reason. How or why this happened, I don't know. I wish I knew, but it's as if everything related to recovery has just disappeared.
It can boot into Android no problem and I can connect to it via fastboot, which in my eyes just make this whole thing seem even weirder.
The tablet is running stock rooted Android 4.1.1, bootloader version is, I think - not completely sure, US_epad-10.4.2.15-20120917. I am not sure if that is the right number, so here you go:
When selecting the recovery option it just hangs there until I reboot the tablet.
So far I've tried flashing TWRP 2.6.3.0-JB through fastboot, which finished successfully (at least according to fastboot, anyway) with no errors. But still recovery is nowhere to be found.
Does anyone have any idea how to solve this problem and get recovery back on my Prime ? Or at least factory reset it without recovery ?
Click to expand...
Click to collapse
You have unlocked the bootloader ?
Thx Josh
lj50036 said:
You have unlocked the bootloader ?
Thx Josh
Click to expand...
Click to collapse
If the "bootloader is unlocked" text while booting the tablet is to be believe, yes, the bootloader is unlocked and the tablet is rooted. Recovery worked fine a couple years ago when I was using CM nightlies on it, then it just stopped working out of nowhere sometime after I got the current stock pre-rooted Jellybean rom on it.
I don't know if flashing Jellybean is what triggered this whole problem in the first place or if it's something that happened afterwards.
What really puzzles me though, is how I can flash TWRP through fastboot "successfully", and it just keeps on not working as if nothing happened.
Tricky547 said:
If the "bootloader is unlocked" text while booting the tablet is to be believe, yes, the bootloader is unlocked and the tablet is rooted. Recovery worked fine a couple years ago when I was using CM nightlies on it, then it just stopped working out of nowhere sometime after I got the current stock pre-rooted Jellybean rom on it.
I don't know if flashing Jellybean is what triggered this whole problem in the first place or if it's something that happened afterwards.
What really puzzles me though, is how I can flash TWRP through fastboot "successfully", and it just keeps on not working as if nothing happened.
Click to expand...
Click to collapse
Post the exact input and out put of flashing a recovery....
Thx Josh
lj50036 said:
Post the exact input and out put of flashing a recovery....
Thx Josh
Click to expand...
Click to collapse
Alright, just flashed recovery, here you go.
Code:
C:\>fastboot -i 0x0b05 flash recovery openrecovery-twrp-2.6.3.0-tf201-JB.blob
sending 'recovery' (7934 KB)...
OKAY [ 2.915s]
writing 'recovery'...
OKAY [ 7.228s]
finished. total time: 10.145s
Exactly the same input and output as the other times I've tries this, but somehow it got me a working recovery this time around. I've no idea what changed for it to suddenly work, but I guess that's it for this thread.
Thanks for your help !
Tricky547 said:
Alright, just flashed recovery, here you go.
Code:
C:\>fastboot -i 0x0b05 flash recovery openrecovery-twrp-2.6.3.0-tf201-JB.blob
sending 'recovery' (7934 KB)...
OKAY [ 2.915s]
writing 'recovery'...
OKAY [ 7.228s]
finished. total time: 10.145s
Exactly the same input and output as the other times I've tries this, but somehow it got me a working recovery this time around. I've no idea what changed for it to suddenly work, but I guess that's it for this thread.
Thanks for your help !
Click to expand...
Click to collapse
You can always hit the thx button .......
Great to see you up and running.....
Can you add 'SOLVED' to the thread title ...
Thx Josh
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
OFFICIAL DOWNLOADS FOR SUZU:
https://twrp.me/sony/sonyxperiax.htmltwrp-3.x.x_x-x-suzu.img: Official TWRP image
DEVELOPMENT DOWNLOADS FOR SUZU:
Folder: https://sourceforge.net/projects/loire-development/files/twrp-recovery/suzu/twrp-3.x.x_x-x-YYYYMMDD-suzu.zip: Flashable unofficial TWRP to FOTAKerneltwrp-3.x.x_x-x-YYYYMMDD-suzu.img: Unofficial TWRP image
INSTALLATION
MANUALLY TO FOTAFastboot: Adapt the image name and install this way:fastboot flash recovery twrp-3.x.x_x-x-suzu.imgfastboot rebootFROM EXISTING RECOVERY
Enter to the current recovery
Install flashable TWRP
Reboot/Power off
HOW TO ENTER TO THE RECOVERY:
Power off your phone
Press Power and Vol- buttons at the same time until vibration
Wait for TWRP load
Sources:
TWRP device tree: https://github.com/TeamWin/android_device_sony_suzu/tree/android-9.0Kernel: https://github.com/Chippa-a/kernel-copyleft/tree/34.4.A.2.xxxThanks to the TWRP Team!
Backup-Restore function working fine so far, only issue I am seeing is phone is heating up pretty faster than before while backing up in compression mode.
Another minor thing is that earlier when entering recovery mode a purple light used to blink, now its missing.
Just saw this now and I'm really grateful. Big ups to you, man. Great work.
And I was afraid there would be no 3.2.1 for this device;
@Chippa_a makes it possible - intensified thanks! :highfive::good::good:
Thank you!!
I can't flash the zip because twrp does not give access to that part of the storage, weird.
fusk said:
I can't flash the zip because twrp does not give access to that part of the storage, weird.
Click to expand...
Click to collapse
Weird. Try using flash tool to fastboot the image if the flashable zip doesn't work for you.
Updated from TWRP, backup/restore works, no problems so far apart from it needs more than a minute till TWRP GUI appears after boot. Thanks for update.
Do you use the stock kernel? I installed the recovery built by oshmoun in the omnirom thread. It uses the aosp kernel. It starts faster, has a better sdcard naming and can flash oem images. Maybe you could try this kernel.
I use stock kernel (Pexorom 4.5) so this may be the reason for the delay.
I mean the kernel used with the recovery, not the rom kernel.
I_am_Blackford said:
Weird. Try using flash tool to fastboot the image if the flashable zip doesn't work for you.
Click to expand...
Click to collapse
This is what i did. Download img, place file on phone. Download twrp app, pick choose a file, browse to recovery.img, flash. Power off, boot to recovery = win.
Reboot to system, retry installing new update = great success.
mase76 said:
I mean the kernel used with the recovery, not the rom kernel.
Click to expand...
Click to collapse
Sorry, I didn't get it... kernels everywhere.
However, flashing with fastboot leads to the same delayed start. Strange.
privatim said:
Sorry, I didn't get it... kernels everywhere.
However, flashing with fastboot leads to the same delayed start. Strange.
Click to expand...
Click to collapse
I dont know if there is a connection, but i've tested the recovery with OmniROM 7.1.2, where display is not responding. It can be installed, shows 3.2.1, but display remains dead 4 touch.
Give this one a try:
https://forum.xda-developers.com/showpost.php?p=76440401&postcount=333
mase76 said:
Give this one a try:
https://forum.xda-developers.com/showpost.php?p=76440401&postcount=333
Click to expand...
Click to collapse
Same result, whether fastboot or flashtool, display is dead.
Certainly missed ODM LOIRE v12, v11 is installed.
Not really sure is the latest bootloader.
Does restoring a backup change the bootloader as well?
Edit: Solved: the answer is 'yes'.
3.2.1 does not work @7.1.2 restore because of outdated bootloader.
privatim said:
I use stock kernel (Pexorom 4.5) so this may be the reason for the delay.
Click to expand...
Click to collapse
Moved to XGEN ROM and now TWRP starts without delay. :good:
privatim said:
Moved to XGEN ROM and now TWRP starts without delay. :good:
Click to expand...
Click to collapse
What I do not understand, maybe bootloader or encryption, but why is 3.2.1 not backwards compatible on Suzu?
Is Omni 7.1.2 kernel (more I have not tried) or not current boot loader the reason?
Installed on last nougat internal storage 0 help
Inviato dal mio F5121 utilizzando Tapatalk
I'm glad that you finally managed to crack this damn decryption. I felt really bad with my broken promise of delivering the working build. I'm sorry, guys. @Chippa_a congratulations on your hard work
Code:
/*
Your warranty now goes to /dev/null
*/
Pure AOSP built from Sony's sources.
Flavor: aosp_f5121-userdebug
Branch: android-9.0.0_r1
Kernel verion: 4.9
Required blobs version: 8.1.0_4.9_loire_v15
What's working:
Booting
Bluetooth
Audio
3D
LED
Flashlight
What's broken:
Bootsplash
WiFi
ADB
Encryption
Camera
Fingerprint
What's not tested:
RIL (Can call to emergency, but other doesn't tested)
NFC
GPS
Insructions:
Flash boot.img and system.img through fastboot.
Erase userdata and cache partitions.
Flash oem from https://developer.sony.com/file/dow...s-for-aosp-oreo-android-8-1-kernel-4-9-loire/ (ro.odm.version=8.1.0_4.9_loire_v15)
Downloads:
NOTE: As a builder, I completely forbid posting my builds on Russian 4PDA site. Don't discuss it, it's personal.
Google Drive: https://drive.google.com/file/d/1QvoHQP-jys_rnIw3SVDC_nMf2ljpAomn/view?usp=sharing
f5122 can flash ???
we can flash for Xperia X DUAL ????? just 1 sim dosent work ?
i installed this rom in xperia x dual ( F5122 ) worked fine
Experience flashing this ROM? Faster performance, usability? If possible as much screenshots as possible? Great work in building this for our device, OP. :victory:
Moved to Linux 4.4 kernel, as it seems to be more stable. WiFi is now working. Also solved issue with ADB.
Screenshots are coming, as I can now connect to device.
LongLiveRem said:
Moved to Linux 4.4 kernel, as it seems to be more stable. WiFi is now working. Also solved issue with ADB.
Screenshots are coming, as I can now connect to device.
Click to expand...
Click to collapse
Can I give the kernel 4.4?
[email protected] said:
Can I give the kernel 4.4?
Click to expand...
Click to collapse
You can try it out and give feedback on your experience.
If anyone on the ROM could upload some screenshots, it'd be appreciated as well.
i_am_blackford said:
you can try it out and give feedback on your experience.
If anyone on the rom could upload some screenshots, it'd be appreciated as well.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Nice... I can see you uploaded the fingerprint scanner manager and based on the OP, it doesn't work. Can you confirm that? How's the ROM speed, fluidity compared to others (8.1) and battery life? Any standout frustrations?
Hopefully my questions aren't too much.
@LongLiveRem thank you so much !!! good job
tested RIL OK
how to do this: Flash oem from.
???? pls I flashed boot boot.img and system system.img
how to flash oem from sony?
butler007 said:
how to do this: Flash oem from.
???? pls I flashed boot boot.img and system system.img
how to flash oem from sony?
Click to expand...
Click to collapse
1- fastboot flash boot boot.img and system system.img
2- fastboot erase userdata and erase cache
3- flash oem download from https://developer.sony.com/file/dow...s-for-aosp-oreo-android-8-1-kernel-4-9-loire/ and extract it
4- then flash fastboot flash oem SW_binaries_for_Xperia_Android_8.1.6.4_r1_v15_loire.img
Xperia Mini said:
1- fastboot flash boot boot.img and system system.img
2- fastboot erase userdata and erase cache
3- flash oem download from https://developer.sony.com/file/dow...s-for-aosp-oreo-android-8-1-kernel-4-9-loire/ and extract it
4- then flash fastboot flash oem SW_binaries_for_Xperia_Android_8.1.6.4_r1_v15_loire.img
Click to expand...
Click to collapse
It worked!
---------- Post added at 04:19 AM ---------- Previous post was at 04:17 AM ----------
Calls doesn't work for me (No audio when connected with someone else)
2018-09-14: Update of Beta AOSP Pie binaries (Android 9.0 – Kernel 4.9) for Xperia X and Xperia X Compact (Loire):
https://developer.sony.com/file/dow...es-for-aosp-pie-android-9-0-kernel-4-9-loire/
hello look good news Software binaries for AOSP Pie (Android 9.0) – Kernel 4.9 – Loire https://developer.sony.com/file/dow...es-for-aosp-pie-android-9-0-kernel-4-9-loire/
Could you re-compile the Rom on new Android Pie Code Source Kernel?
I could not boot it on my device
New https://developer.sony.com/file/dow...es-for-aosp-pie-android-9-0-kernel-4-9-loire/
When I try to flash system.img through fastboot I get following error:
02/054/2019 01:54:09 - INFO - FASTBOOT Output:
target reported max download size of 536870912 bytes
sending sparse 'boot' 1/3 (524284 KB)...
OKAY [ 18.812s]
writing 'boot' 1/3...
FAILED (remote: size too large)
finished. total time: 18.812s
I dont understand this since size of image it is sending is clearly less than max download size.
So, I flashed the system Image using twrp recovery but when I go for reboot, I get a message that no system is found. Even if I persist, the phone just boots up back into recovery. Can somebody help.
Hi, so I successfully installed TWRP from here, everything went well until this point. I flashed a more stable EU rom and then tried to flash Magisk, but when I rebooted it just went to fastboot mode.
Now everytime I try to turn it off or go back into TWRP it just goes to fastboot mode.
I have tried to flash using MiFlash but I can't seem to get the right thing to flash apparently.
When trying to reinstall TWRP
fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 4.498s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Device Error)
finished. total time: 4.503s
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Zelyric said:
View attachment 5448807
Click to expand...
Click to collapse
Getting Mismatched image error in fastboot when trying to flash stable/developer ROM.
Hello.. Which fastboot rom is correct for my mido Device.. i downloaded Both Stable and Developer version both giving mismatched image error.. tried flashing from mi flash tool, flashed in 1sec issue.. Please help , how am i suppose to flash...
forum.xda-developers.com
I hope it helps.
akins0405 said:
Getting Mismatched image error in fastboot when trying to flash stable/developer ROM.
Hello.. Which fastboot rom is correct for my mido Device.. i downloaded Both Stable and Developer version both giving mismatched image error.. tried flashing from mi flash tool, flashed in 1sec issue.. Please help , how am i suppose to flash...
forum.xda-developers.com
I hope it helps.
Click to expand...
Click to collapse
Reading on that post I saw that there are issues with Ryzen powered computers, and I indeed have a Ryzen CPU. Really hopes this helps, thanks for showing me regardless - ill keep you updated!
@akins0405
Zelyric said:
@akins0405
Click to expand...
Click to collapse
Try flashing you stock boot img
akins0405 said:
Try flashing you stock boot img
Click to expand...
Click to collapse
Where do I find that?
Zelyric said:
Where do I find that?
Click to expand...
Click to collapse
You have it in fastboot stock rom
Zelyric said:
Where do I find that?
Click to expand...
Click to collapse
Try to transfer the rom to the system partition
akins0405 said:
Try flashing you stock boot img
Click to expand...
Click to collapse
adb doesn't show my device under adb devices but fastboot devices does show it..
MTP also is disabled
Zelyric said:
adb doesn't show my device under adb devices but fastboot devices does show it..
Click to expand...
Click to collapse
Flash in fastboot stock boot img, can you do it
akins0405 said:
Flash in fastboot stock boot img, can you do it
Click to expand...
Click to collapse
fastboot flash b boot.img
Sending 'b' (196608 KB) OKAY [ 4.817s]
Writing 'b' FAILED (remote: '(b_a) No such partition')
fastboot: error: Command failed
nevermind, i understood the partition wrong.
fastboot flash boot boot.img
Sending 'boot_a' (196608 KB) OKAY [ 4.558s]
Writing 'boot_a' OKAY [ 0.707s]
Finished. Total time: 6.103s
what now?
Zelyric said:
@akins0405
Click to expand...
Click to collapse
Try firstly erasing your recovery partition with fastboot erase recovery
Somehow I have managed to fix it on my own, thank you for your response regardless @akins0405 @SubwayChamp.
Here's how I fixed it for the people wanting to know:
I flashed boot.img via fastboot, I have no clue if it had effect on what I did afterwards but I think it might.
I moved the folder of all the files to my main C:\ directory, and then tried to flash using MiFlash and it worked.
I'm trilled to have it back in a ''working'' state
Zelyric said:
Somehow I have managed to fix it on my own, thank you for your response regardless @akins0405 @SubwayChamp.
Here's how I fixed it for the people wanting to know:
I flashed boot.img via fastboot, I have no clue if it had effect on what I did afterwards but I think it might.
I moved the folder of all the files to my main C:\ directory, and then tried to flash using MiFlash and it worked.
I'm trilled to have it back in a ''working'' state
Click to expand...
Click to collapse
I'm glad you made it, hello