No improvements as far as I saw, still no full modem, camera and sd support.
[FreeXperia Project] AOSP Android 5.1.x
- Thread starter freexperia
- Start date
-
- Tags
- development
Has anyone tried this build:
AOSP_L_MR1_151205_seagull.zip
213.3MB Dec 05, 2015 | 04:06PM
?
theres also this one:
AOSP_L_MR1_151203_seagull.zip
213.3MB Dec 04, 2015 | 04:27AM
can someone test it? i dont have recovery installed at the moment
AOSP_L_MR1_151205_seagull.zip
213.3MB Dec 05, 2015 | 04:06PM
?
theres also this one:
AOSP_L_MR1_151203_seagull.zip
213.3MB Dec 04, 2015 | 04:27AM
can someone test it? i dont have recovery installed at the moment
I think it was with with recovery.
In the first por it says:
btw, wich recovery are u using?
have u tried the method in first post?
EDIT:
So, i tried the most recent version (AOSP_L_MR1_151205_seagull), the problem is i was with low battery, and now I cant understand if im having bootloop because of battery or because of ROM.
Anyway, I will try the previous version and the 5.0 versions...
I noticed that our build (seagull) had 50 download, so I would like if some of you tested it....
Last edited:
EDIT:
So, i tried the most recent version (AOSP_L_MR1_151205_seagull), the problem is i was with low battery, and now I cant understand if im having bootloop because of battery or because of ROM.
Anyway, I will try the previous version and the 5.0 versions...
I noticed that our build (seagull) had 50 download, so I would like if some of you tested it....
So, i tried the most recent version (AOSP_L_MR1_151205_seagull), the problem is i was with low battery, and now I cant understand if im having bootloop because of battery or because of ROM.
Anyway, I will try the previous version and the 5.0 versions...
I noticed that our build (seagull) had 50 download, so I would like if some of you tested it....
Hey guys, today I had my first experience flashing Sony Xperia T3.
I tried AOSP_L_MR1_160129_seagull.zip.
I unlocked bootloader and did
All I got is black screen, so I used an ftf image to restore the original image.
Anybody had success with it?
I tried AOSP_L_MR1_160129_seagull.zip.
I unlocked bootloader and did
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img # this failed with a message like "partition not found"
fastboot flash system system.img
fastboot flash userdata userdata.imgAnybody had success with it?
so, did you ugrade the bootloader with Emma ? if not, you can't start any custom ROM.
Well, now I clicked "Apply Service" in Emma, but almost nothing changed. Now I see the Sony logo, and it bootloops. I tried:
1) AOSP_L_MR1_160129_seagull.zip - using "fastboot flash"
2) FXP-cm-12.1-20150811-UNOFFICIAL-seagull.zip - using PhilzRecovery and installing zip via "adb sideload".
Neither of them worked.
I finally booted a custom kitkat rom, but had to compile from sources. I followed kitkat build instructions but instead of original boot.img used PhilZ recovery.
No camera and wifi though. I will soon try to build 5.1 and see how it works.
If anyone is interested, here is my built-from-sources rom with PhilZ recovery instead of standard boot.img. Flash using fastboot.
So, my attempts to build AOSP 5.1 and CyanogenMod failed. Build process was painful, and all I got is bootloop.
I ended up with a linux script which removes bloatware from the stock rom.
In case anyone is interested. You have to have linux and adb installed. Probably cygwin will work as well, but I didn't test. I did the following:
1) flash the stock rom
2) flash the PhilZ recovery right after that
3) first boot: to the recovery so adb server works
4) mount /system partition
5) run the attached script
6) reboot phone normally
You may want to check/modify the script commenting out the packages you actually need (wikipedia, hangouts, or whatever).
I ended up with a linux script which removes bloatware from the stock rom.
In case anyone is interested. You have to have linux and adb installed. Probably cygwin will work as well, but I didn't test. I did the following:
1) flash the stock rom
2) flash the PhilZ recovery right after that
3) first boot: to the recovery so adb server works
4) mount /system partition
5) run the attached script
6) reboot phone normally
You may want to check/modify the script commenting out the packages you actually need (wikipedia, hangouts, or whatever).
You are lucky, because i succeed today to flashed back the new bootloader. one month ago, i made a wrong flash, and i destroied the bootloader. i was allways able to flash KK, but no longer Lollipop or Mashmallow.
so, if you dont' see the new TA with Emma, here is the way i did it this morning !
I dont' know why, but the problem is with the newest versions of Emma! i reinstalled the Emma V6 (fortunately, i have always the old archive), and what a surprise to see the two services : the last firmware AND the new TA.
As it's an old version, Emma failed to load the update, but it's not a problem. i ran Emma V6, tried to flash the TA, but it failed too.
so, before closing Emma, i went to the Emma\db\279242523\blob_fs folder and found three files. i decryped these 3 files with Flashtool and bundle a simple ftf, with only the new TA and the loader.
I flashed this new ftf with Flashtool, and that's it ; i have recovered the good new bootloader : 1274-7024 S1_Boot_MSM8x26_LA1.0_1027 !
for the time beeing, i just flash a Marshallow build and i am waiting for the boot process, in order to test it
and as i'm a good boy, you can find the ftf to flash with flashtool in the rar joined. Enjoy!
Wait, so youre building Marshmallow for t3?You are lucky, because i succeed today to flashed back the new bootloader. one month ago, i made a wrong flash, and i destroied the bootloader. i was allways able to flash KK, but no longer Lollipop or Mashmallow.
so, if you dont' see the new TA with Emma, here is the way i did it this morning !
I dont' know why, but the problem is with the newest versions of Emma! i reinstalled the Emma V6 (fortunately, i have always the old archive), and what a surprise to see the two services : the last firmware AND the new TA.
As it's an old version, Emma failed to load the update, but it's not a problem. i ran Emma V6, tried to flash the TA, but it failed too.
so, before closing Emma, i went to the Emma\db\279242523\blob_fs folder and found three files. i decryped these 3 files with Flashtool and bundle a simple ftf, with only the new TA and the loader.
I flashed this new ftf with Flashtool, and that's it ; i have recovered the good new bootloader : 1274-7024 S1_Boot_MSM8x26_LA1.0_1027 !
for the time beeing, i just flash a Marshallow build and i am waiting for the boot process, in order to test it
and as i'm a good boy, you can find the ftf to flash with flashtool in the rar joined. Enjoy!
Dan15, have you success?You are lucky, because i succeed today to flashed back the new bootloader. one month ago, i made a wrong flash, and i destroied the bootloader. i was allways able to flash KK, but no longer Lollipop or Mashmallow.
so, if you dont' see the new TA with Emma, here is the way i did it this morning !
I dont' know why, but the problem is with the newest versions of Emma! i reinstalled the Emma V6 (fortunately, i have always the old archive), and what a surprise to see the two services : the last firmware AND the new TA.
As it's an old version, Emma failed to load the update, but it's not a problem. i ran Emma V6, tried to flash the TA, but it failed too.
so, before closing Emma, i went to the Emma\db\279242523\blob_fs folder and found three files. i decryped these 3 files with Flashtool and bundle a simple ftf, with only the new TA and the loader.
I flashed this new ftf with Flashtool, and that's it ; i have recovered the good new bootloader : 1274-7024 S1_Boot_MSM8x26_LA1.0_1027 !
for the time beeing, i just flash a Marshallow build and i am waiting for the boot process, in order to test it
and as i'm a good boy, you can find the ftf to flash with flashtool in the rar joined. Enjoy!
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone