I recently ported MultiROM to Xperia M and I have the sources up and I am willing not to waste them.
Disclaimer : I am not responsible for anything that happens to you or your device after flashing this mod. Though, nothing generally happens when you do it right. Make backup, always.
I have ported it xperia M
Here are some files for testing
You need CM-12.1 installed to test this.
Links removed
RECOVERY.IMG - To be flashed on fota partition
XL_CM-kexec-xx-xx-xxxx.zip - To be flashed in recovery
multirom-xxxxxxxx-v31x-UNOFFICIAL-taoshan.zip - To be flashed in recovery
Next boot should come up with multirom menu
If it does, post screens, if doesn't , post last_kmsg.
Due to lack of my knowledge, I have dismissed this project.
aweosomeabhijeet said:
I recently ported MultiROM to Xperia M and I have the sources up and I am willing not to waste them.
I have ported it xperia M
Here are some files for testing
You need CM-12.1 installed to test this.
TEST 1
RECOVERY.IMG - To be flashed on fota partition
XL_CM-kexec-xx-xx-xxxx.zip - To be flashed in recovery
multirom-xxxxxxxx-v31x-UNOFFICIAL-taoshan.zip - To be flashed in recovery
Next boot should come up with multirom menu
If it does, post screens, if doesn't , post last_kmsg.
Click to expand...
Click to collapse
May i have a look on sourcecode? Im mainly interested in where the rom+ kernel of second rom are saved
Sent from my Xperia T using XDA Free mobile app
SdtBarbarossa said:
May i have a look on sourcecode? Im mainly interested in where the rom+ kernel of second rom are saved
Sent from my Xperia T using XDA Free mobile app
Click to expand...
Click to collapse
Here you go
https://github.com/XperiaMultiROM/multirom/
https://github.com/XperiaMultiROM/android_bootable_recovery
aweosomeabhijeet said:
Here you go
https://github.com/XperiaMultiROM/multirom/
https://github.com/XperiaMultiROM/android_bootable_recovery
Click to expand...
Click to collapse
Ok seems like it goes from sd_ext .... What kernel you used? Varuns Caf? (The official one) and varuns device tree? If yes you may get wrong device errors while flashing
Sent from my Xperia T using XDA Free mobile app
SdtBarbarossa said:
Ok seems like it goes from sd_ext .... What kernel you used? Varuns Caf? (The official one) and varuns device tree? If yes you may get wrong device errors while flashing
Sent from my Xperia T using XDA Free mobile app
Click to expand...
Click to collapse
I used sources and device tree from CM's repo
Doesn't matter, because I had removed assert from updater-script and no ROM flashing is required in here.
So all files must be good and compatible.
Hey, great job in compiling this. I want to try this out but what are the risks? Can I get hardbricked?
The recovery included in the recovery.img is Cyanogen Recovery.
So cannot able to flash those zips.
I heard MultiROM uses modded TWRP.
Please check
corphish said:
The recovery included in the recovery.img is Cyanogen Recovery.
So cannot able to flash those zips.
I heard MultiROM uses modded TWRP.
Please check
Click to expand...
Click to collapse
Maybe the recovery is faulty and therefor cm recovery was loaded?
Sent from my Xperia T using XDA Free mobile app
SdtBarbarossa said:
Maybe the recovery is faulty and therefor cm recovery was loaded?
Sent from my Xperia T using XDA Free mobile app
Click to expand...
Click to collapse
Nope..I was on TWRP flashed on FOTA from your app.
Then flashed this img, voila, CM Recovery.
corphish said:
Nope..I was on TWRP flashed on FOTA from your app.
Then flashed this img, voila, CM Recovery.
Click to expand...
Click to collapse
Yes that what i.meaned ^^ you flashed this im in FOTAKernel dont you? Then my recovery will be overrided and if his recovery fails to load the kernelinbuild (cm) will be loaded....
The common cm device tree is not able to build a twrp properly... Im building with omnirom and a "changed" varun tree
Sent from my Xperia T using XDA Free mobile app
SdtBarbarossa said:
Yes that what i.meaned ^^ you flashed this im in FOTAKernel dont you? Then my recovery will be overrided and if his recovery fails to load the kernelinbuild (cm) will be loaded....
The common cm device tree is not able to build a twrp properly... Im building with omnirom and a "changed" varun tree
Sent from my Xperia T using XDA Free mobile app
Click to expand...
Click to collapse
Ohk I did not know about invalid recovery in fota partition would result in loading recovery from boot partition.
And its really a nice idea of you compiling modded TWRP, as soon as you are done, feel free to share as I am ready with other zips
corphish said:
Ohk I did not know about invalid recovery in fota partition would result in loading recovery from boot partition.
And its really a nice idea of you compiling modded TWRP, as soon as you are done, feel free to share as I am ready with other zips
Click to expand...
Click to collapse
i did have a look at this recovery.img ... its definitly a TWRP build... but its damn wrong.... wrong qcom.fstab and recovery.fstab ... NO twrp.fstab ... healthhd seems to have wrong size (ok im not 100% with that but experience says it must be bigger) ... the Size of theme images is wrong.... AND the ramdisk size is totally above the size the kernel will load... thats why it leads to a "broken" recovery-load .... that will lead to a emergency load of kernel-inbuild recovery....
@ OP didnt you got make errors? after seeing this im sure you have build with -i -k
---------- Post added at 08:36 AM ---------- Previous post was at 08:22 AM ----------
ok without any kind of warranty that this will work... i have manipulated this recovery.img (NOT BUILD FROM SOURCE! MANUALLY REPAIR! ) ... maybe this works maybe not....
like you know my device is gone atm.... so maybe if my device is back i will have a deeper look into this...
aweosomeabhijeet said:
I recently ported MultiROM to Xperia M and I have the sources up and I am willing not to waste them.
Click to expand...
Click to collapse
By making blind builds, you do "waste" the source code.
aweosomeabhijeet said:
I used sources and device tree from CM's repo
Click to expand...
Click to collapse
And you seriously expect a working build?
adil089 said:
Hey, great job in compiling this.
Click to expand...
Click to collapse
No, definitely not. He just used my sources (XperiaMultiROM) to compile it, which is a piece of cake. Honestly, if porting MultiROM was just a matter of compiling, monkeys could do it too.
OP: Blind builds are not encouraged on XDA. Especially when they're untested and broken.
And no, this shouldn't hardbrick your phone. You'll need to reflash your kernel and the system partition in the worst case.
Sent from my Xperia Z using XDA Free mobile app
Olivier said:
By making blind builds, you do "waste" the source code.
And you seriously expect a working build?
No, definitely not. He just used my sources (XperiaMultiROM) to compile it, which is a piece of cake. Honestly, if porting MultiROM was just a matter of compiling, monkeys could do it too.
OP: Blind builds are not encouraged on XDA. Especially when they're untested and broken.
And no, this shouldn't hardbrick your phone. You'll need to reflash your kernel and the system partition in the worst case.
Sent from my Xperia Z using XDA Free mobile app
Click to expand...
Click to collapse
Thank you for response thats exactly what i thought... He blind builded (see my comment above... Im not good in rom building but recoverys im good in... )
BTW maybe you let a word down on cm12.1 thread? Its a while ago now as varun said you will maintain our device... It would be nice to have a word from yourself about if its true or not
Sent from my Xperia T using XDA Free mobile app
Olivier said:
By making blind builds, you do "waste" the source code.
And you seriously expect a working build?
No, definitely not. He just used my sources (XperiaMultiROM) to compile it, which is a piece of cake. Honestly, if porting MultiROM was just a matter of compiling, monkeys could do it too.
OP: Blind builds are not encouraged on XDA. Especially when they're untested and broken.
And no, this shouldn't hardbrick your phone. You'll need to reflash your kernel and the system partition in the worst case.
Sent from my Xperia Z using XDA Free mobile app
Click to expand...
Click to collapse
Thank You.
Please apply for closure of the thread
Sent from my HTC One
To everyone:
I am sorry for doing it all wrong and blindly. I just had ported to a similar device and had it working perfectly.
Never knew CM sources wouldn't work for XL. Basically I trusted on CM people for device tree and kernel, which I shouldn't have definitely.
If anyone feels to, can apply for closing down the thread. I have other devices, I'll try getting it to work on them.
Thank you
Sent from my HTC One
Pls can someone else build MultiRom for Xperia L? Maybe you @SdtBarbarossa?
Sent from my C2105 using XDA Free mobile app
Xperia_L said:
Pls can someone else build MultiRom for Xperia L? Maybe you @SdtBarbarossa?
Sent from my C2105 using XDA Free mobile app
Click to expand...
Click to collapse
Sorry i am out of device... Maybe ask Olivier nice
Sent from my Xperia T using XDA Free mobile app
Thread closed upon request
Forum moderator,
matt4321
Related
I saw that Canonical added new branch phablet-4.4_r1 https://wiki.kubuntu.org/Touch/AOSPBuild
so I compiled it for FLO
Download
system http://d-h.st/sXM
kernel http://d-h.st/mSc
but we must flash also ubuntu files but I don't know which files
http://cdimage.ubuntu.com/ubuntu-touch/daily-preinstalled/
any help would be appreciated
Also curious what other files are needed to work. Will wait to try
I think it is a step in the right direction but i think we would still need the hardware specific package (trusty-preinstalled-touch-armel+flo.zip) to make it work
nikr123 said:
I think it is a step in the right direction but i think we would still need the hardware specific package (trusty-preinstalled-touch-armel+flo.zip) to make it work
Click to expand...
Click to collapse
nope. I think that we must flash this trusty-preinstalled-touch-armhf.zip
DevSwift1 said:
nope. I think that we must flash this trusty-preinstalled-touch-armhf.zip
Click to expand...
Click to collapse
... if you check the official guide on Ubuntu's website ( https://wiki.ubuntu.com/Touch/Install#Manual_Download_.26_Installation ) they say you don't need that one... but I'm not sure.
Sent from my W8 beyond using Tapatalk
nikr123 said:
... if you check the official guide on Ubuntu's website ( https://wiki.ubuntu.com/Touch/Install#Manual_Download_.26_Installation ) they say you don't need that one... but I'm not sure.
Sent from my W8 beyond using Tapatalk
Click to expand...
Click to collapse
I compiled it already you can download it
DevSwift1 said:
I compiled it already you can download it
Click to expand...
Click to collapse
That is not what I'm talking bout... I'm saying that I think we would need "saucy-preinstalled-touch-armel+flo.zip" as the say on the website " Get the hardware specific zip and img files for your device from the Ubuntu cdimage server here, i.e. for a Nexus7 this is saucy-preinstalled-touch-armel+grouper.zip".
Sent from my W8 beyond using Tapatalk
nikr123 said:
That is not what I'm talking bout... I'm saying that I think we would need "saucy-preinstalled-touch-armel+grouper.zip" as the say on the website " Get the hardware specific zip and img files for your device from the Ubuntu cdimage server here, i.e. for a Nexus7 this is saucy-preinstalled-touch-armel+grouper.zip".
Sent from my W8 beyond using Tapatalk
Click to expand...
Click to collapse
you don't understand me too.
saucy-preinstalled-touch-armel+grouper.zip in this zip package we have system files for grouper
We don't have official support for flo so I compiled it (system.img) and you can download it from first post
Does anyone know if this is a daily driver or not.
mcteague said:
Does anyone know if this is a daily driver or not.
Click to expand...
Click to collapse
Read all the posts above yours and decide for yourself.
Sent from my Nexus 7 using Tapatalk 4
how can we flash this :3 i see only boot.img and system.img
bogii4 said:
how can we flash this :3 i see only boot.img and system.img
Click to expand...
Click to collapse
If I am not mistaken, it should just be:
Code:
fastboot flash boot boot.img
fastboot flash system system.img
Personally, I would wait for someone else to try it, first.
Perhaps its a bit harder to brick devices, nowadays, but I wouldn't want to risk it, myself.
techn0crat said:
If I am not mistaken, it should just be:
Code:
fastboot flash boot boot.img
fastboot flash system system.img
Personally, I would wait for someone else to try it, first.
Perhaps its a bit harder to brick devices, nowadays, but I wouldn't want to risk it, myself.
Click to expand...
Click to collapse
It should be buggy but my question is does it fully boot and have the main things working like - WiFi, BT, Camera, Sound etc..
Would this be flashable via TWRP MultiROM?
Sent from my Nexus 7 using XDA Premium 4 mobile app
its not a zip you cant flash it with recovery.
Can someone report what work and what not
*$M3RT$* said:
its not a zip you cant flash it with recovery.
Can someone report what work and what not
Click to expand...
Click to collapse
I couldn't get it to boot with multirom. Installed without issue then pushed system.IMG and boot.IMG. every time I tried to boot off it everything would just revert back to the internal rom
Sent from my Nexus 7 using Tapatalk 4
Please read the important sentence:
Currently you can try either the phablet-4.2.2_r1 or phablet-4.4_r1 branches. The latter builds and boots but only the adb shell works, there still are bugs preventing Android and Ubuntu communicating (WIP as of Nov 21 2013)
Click to expand...
Click to collapse
"Work in progress (WIP)" is a funny way to describe this achievement...
@DevSwift1 Any progress? Not asking for ETA, I just want to know if I can look forward to this!
Sent from my Nexus 7 using XDA Premium 4 mobile app
StrangerWeather said:
@DevSwift1 Any progress? Not asking for ETA, I just want to know if I can look forward to this!
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It seems that we must wait until ubuntu will fix problem with communicating between android and ubuntu
So has anyone installed this? does it boot atleast?
I am very interested in porting Xperia L to OmniRom and had starting work on it. The kitkat sources is already available anyway(see here). Compiling it is easy, just follow the instructions. I now have a working kitkat rom which unfortunately seem to have a serious bug of unable to go into deep sleep(dropped >40% over a night).
I have started work on the kernel sources and wish to invite all developers who are interested to work together.
For those of you with wifi issue, make sure that you are on stock rom 15.3.A.x.x
Extracted from Sony opensource
Most of the AOSP for Xperia L device configurations are cloned from the official Xperia L software version 15.3.A.0.x, so please make sure that you upgrade the phone software to, for example 15.3.A.0.26, before flashing the AOSP for Xperia L images, or certain functions like WiFi may not work.
Known issues/workaround:
1. There are some missing KLOG information that prevent building of the kernel( fix by disabling CCI_KLOG)
2. Deep sleep issue seem to be caused by wait_for_irsc_completion timeout(workaround by disabling
MSM_IPC_ROUTER_SECURITY)
3. Enable reboot recovery
Sources
Kernel 3.4 from Sony
Github version by me
Modified from Holofied Red Holo Theme (http://forum.xda-developers.com/showthread.php?t=2405512)
Count me IN
Count me in PM me more info your status and are you planing to make CAF based kernel ?
Heres's my GitHUB Account : Navneet-Suresh
Best of luck mate! @ Ghostfreak NB see if you can help this guy in this project!!
Navneet Suresh said:
Count me in PM me more info your status and are you planing to make CAF based kernel ?
Heres's my GitHUB Account : Navneet-Suresh
Click to expand...
Click to collapse
Have not worked with CAF kernel before. Moreover, the most important thing now is to get a stable working kernel for kitkat before embarking on anything else.
I will update my progress here in this thread. Its good to keep the communication open here so that others can also contribute/help. Right now, I can successfully compiled the zImage. Going to test it out later on.
update: notice that you have the 15.3.A.1.14 sources. Where did you get it from? My phone was running on this build before I flashed the AOSP 4.4 rom. Dont you have the CCI_KLOG compilation error on 15.3.A.1.14?
I got playing with kit kat for few days and when the phone try to go in deep sleep there is QSEECOM errors that stopped the freezing...
Im not a pro dev,so I might be wrong.
Sent from my C2105 using xda app-developers app
siankatabg said:
I got playing with kit kat for few days and when the phone try to go in deep sleep there is QSEECOM errors that stopped the freezing...
Im not a pro dev,so I might be wrong.
Sent from my C2105 using xda app-developers app
Click to expand...
Click to collapse
Which ROM did you test from? I just flashed the one I compiled from source last night so did not get to test much. What I did noticed was that the battery dropped >40% overnight. I suspect that it might not have gone into deep sleep.
@KillerKink getting the zimage is easy you will have to make certain changes to kernel/ramdisk to make it compatible to KK
Sent from my C2104 using xda app-developers app
Count me in for starters... I'm very interested in getting this done as well..
Sent from my C2104 using XDA Premium 4 mobile app
Navneet Suresh said:
@KillerKink getting the zimage is easy you will have to make certain changes to kernel/ramdisk to make it compatible to KK
Sent from my C2104 using xda app-developers app
Click to expand...
Click to collapse
This is not an issue for me. What I would like to know is where did you get the A.1.14 sources from? Dont you have compilation errors from the sony sources
I guess. 14 sources aren't published by Sony yet right? At least I couldn't find it.. Where did you get that from?
Sent from my C2104 using XDA Premium 4 mobile app
Ghostfreak NB said:
Count me in for starters... I'm very interested in getting this done as well..
Sent from my C2104 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Wonderful. Did you manage to compile from sony sources with the sa77_defconfig without any change?
I had to disable CCI_KLOG.
Ghostfreak NB said:
I guess. 14 sources aren't published by Sony yet right? At least I couldn't find it.. Where did you get that from?
Sent from my C2104 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I dont have the .14 sources. Its .12 that I am working on.
KillerKink said:
Which ROM did you test from? I just flashed the one I compiled from source last night so did not get to test much. What I did noticed was that the battery dropped >40% overnight. I suspect that it might not have gone into deep sleep.
Click to expand...
Click to collapse
I use some version from General section, pure 4.4.2 AOSP and kernel compiled by me and patched to 3.4.79.
Sent from my C2105 using xda app-developers app
siankatabg said:
I use some version from General section, pure 4.4.2 AOSP and kernel compiled by me and patched to 3.4.79.
Sent from my C2105 using xda app-developers app
Click to expand...
Click to collapse
Cool! Did the kernel have deep sleep issue？ Do you have git for your work?
How did you resolved the CCI_KLOG compilation errors?
KillerKink said:
Cool! Did the kernel have deep sleep issue？ Do you have git for your work?
How did you resolved the CCI_KLOG compilation errors?
Click to expand...
Click to collapse
Ye it have that issue, I saw that QSEECOM error on it. And sorry,I don't know how to use git and don't have kernel uploaded there.I'm using this as kernel base and don't have compiling errors.
https://github.com/uberlaggydarwin/taoshan-tracking/tree/warningless-stock-kernel
See the commits and you will find how to solve that problem.And better use whole commit
P.s. Credits to uberlaggydarwin
Sent from my C2105 using xda app-developers app
siankatabg said:
Ye it have that issue, I saw that QSEECOM error on it. And sorry,I don't know how to use git and don't have kernel uploaded there.I'm using this as kernel base and don't have compiling errors.
https://github.com/uberlaggydarwin/taoshan-tracking/tree/warningless-stock-kernel
See the commits and you will find how to solve that problem.And better use whole commit
P.s. Credits to uberlaggydarwin
Sent from my C2105 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the site. Yup, he did the pretty much the same as me.
Update: Kernel compiled via source is bootable.
KillerKink said:
Update: Kernel compiled via source is bootable.
Click to expand...
Click to collapse
Count me in for help. BTW I just saw your screenshot in OP in which you've booted kernel successfully on AOSP, can you link me to that kernel source which you used? I would really like to investigate on it.
The Dark Knight said:
Count me in for help. BTW I just saw your screenshot in OP in which you've booted kernel successfully on AOSP, can you link me to that kernel source which you used? I would really like to investigate on it.
Click to expand...
Click to collapse
feel free to work on it. The sources is the same one that I posted in the first post. btw it seem that there are many working kernels around. Guess I will work on porting Philz Touch recovery first.
KillerKink said:
feel free to work on it. The sources is the same one that I posted in the first post. btw it seem that there are many working kernels around. Guess I will work on porting Philz Touch recovery first.
Click to expand...
Click to collapse
I really can't believe my eyes.
You booted stock kernel on AOSP.
Q&A for [5.0.2][08-03-2015] AOSPA Legacy 5.0 ALPHA2 [UN/OFFICIAL]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [5.0.2][08-03-2015] AOSPA Legacy 5.0 ALPHA2 [UN/OFFICIAL]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
cm theme engine
I guess cm theme engine is not there in this ROM bcoz that's the speciality of aosp
Prafulrox said:
I guess cm theme engine is not there in this ROM bcoz that's the speciality of aosp
Click to expand...
Click to collapse
It's on the way.
corphish said:
Always been a fan of AOSPA, thanks!!
A question-
1. As this is based on AOSP, what changes you did in the kernel or ramdisk to get ROM to boot to homescreen?
Because, if kernels like ThunderZap (until 4.15) is flashed on AOSP based ROMs, results in bootloop.
Click to expand...
Click to collapse
Isn't EuphoriaOS also AOSP based? Then how does it boot fine with Tz 4.15? Just asking coz I'm curious.
notification drawer setting
there's unavailable to setting notification drawer ???
primemonitor said:
Isn't EuphoriaOS also AOSP based? Then how does it boot fine with Tz 4.15? Just asking coz I'm curious.
Click to expand...
Click to collapse
I don't know, some user said TZ gives bootlopp when flashed on AOSP based ROMs.
cacaparuq said:
there's unavailable to setting notification drawer ???
Click to expand...
Click to collapse
There isn't. Its not like CyanogenMod, different features on different ROMs.
Notification drawer is not one of the features of AOSPA.
Hi,
I tried to flash the zip on a recently unlocked device with TWRP but I have this error message: "error executing updater binary in zip".
Does it work if I flash the boot.img with flashtool? Or should I do differently?
Sitel said:
Hi,
I tried to flash the zip on a recently unlocked device with TWRP but I have this error message: "error executing updater binary in zip".
Does it work if I flash the boot.img with flashtool? Or should I do differently?
Click to expand...
Click to collapse
it seems like you are using twrp 2.8.4.0 ....please use philz or twrp v2.8.6.0
Sent from my C2105 using XDA Free mobile app
SdtBarbarossa said:
it seems like you are using twrp 2.8.4.0 ....please use philz or twrp v2.8.6.0
Sent from my C2105 using XDA Free mobile app
Click to expand...
Click to collapse
Ok !!! I will try tonight with with the correct version, thank you for the advice. (I hope it will work, otherwise my GF will kill me! )
Sitel said:
Ok !!! I will try tonight with with the correct version, thank you for the advice. (I hope it will work, otherwise my GF will kill me! )
Click to expand...
Click to collapse
dont panic
Sent from my C2105 using XDA Free mobile app
SdtBarbarossa said:
dont panic
Sent from my C2105 using XDA Free mobile app
Click to expand...
Click to collapse
The same with TRWP 2.8.6.0 and I don't find a link for PhilZ! ^^
There he has another way?
Sitel said:
The same with TRWP 2.8.6.0 and I don't find a link for PhilZ! ^^
There he has another way?
Click to expand...
Click to collapse
http://sdtbarbarossa.bplaced.de/tz4-16-boot.img
Sent from my C2105 using XDA Free mobile app
SdtBarbarossa said:
Link
Sent from my C2105 using XDA Free mobile app
Click to expand...
Click to collapse
I flashed the thunderzap image with fastboot (fastboot flash boot tz4-16-boot.img) but it shows me a black screen.
So I flashed the 15.3.A.117 build of sony with flashtool and I rooted until tomorrow.
I hope I will be able to install your ROM, it makes me want!
I look a little more tomorrow if you still agree to help me
Thanks.
Hi all,
I have a great news
http://developer.sonymobile.com/201...for-a-range-of-unlocked-xperia-devices-video/
Bootloader is compatible with open devices roms and also enables real recovery (Volume Down + Power)
to flash recovery partition on device you have to
fastboot flash recovery recovery.img
Happy Cooking
J
PS.
in case latest software does not appear just press "all Services"
flash latest software available and on top new loader
Just tested, and it works good.
Not having separated recovery is probably the thing that bothered me most in Sony development.
And can confirm PM on 3.10 is working now.
Thanks jerpelea!
When I download this recovery?
Sent from my Xperia M2 LTE using XDA Free mobile app
AssoDiPicche said:
When I download this recovery?
Sent from my Xperia M2 LTE using XDA Free mobile app
Click to expand...
Click to collapse
You pick a recovery you want yourself.
@jerpelea good news
Verstuurd vanaf mijn GT-I9505 met Tapatalk
How Can i verify bootloader version?
What's old one?
What's New one?
ImArlet said:
How Can i verify bootloader version?
What's old one?
What's New one?
Click to expand...
Click to collapse
Bootloader version you can see in EMMA after you plug in the phone, about certain versions, I don't know.
@galaxyfreak
I managed to flash New bootloader and then "recovery.img" on it!
So is that recovery stays there no matter what firmware/kernel i put on the phone?
ImArlet said:
@galaxyfreak
I managed to flash New bootloader and then "recovery.img" on it!
So is that recovery stays there no matter what firmware/kernel i put on the phone?
Click to expand...
Click to collapse
Yes!
@galaxyfreak
I dont really know who's make recovery'es but if you make
Can you make CWM because "CM Recovery" does not allow flash 3rd party zips!
ImArlet said:
@galaxyfreak
I dont really know who's make recovery'es but if you make
Can you make CWM because "CM Recovery" does not allow flash 3rd party zips!
Click to expand...
Click to collapse
I'll upload CM Recovery with signature checking disabled in a few hours.
To
galaxyfreak said:
I'll upload CM Recovery with signature checking disabled in a few hours.
Click to expand...
Click to collapse
Why "CM Recovery"?
CWM is all the time being the Best and popular recovery and have a backup option!
Maybe wrong thread to ask such questions?
ImArlet said:
To
Why "CM Recovery"?
CWM is all the time being the Best and popular recovery and have a backup option!
Maybe wrong thread to ask such questions?
Click to expand...
Click to collapse
It is a wrong thread but screw it.
Because I build CM ROMs and CM recovery is default there.
I do agree that they've dropped CWM way too early, but I think it's not compatible with 5.0 zip layout, so it's either this or TWRP (which is kind of an OmniROM thing).
No matching service for my phone
using D2305.
Any help?
Sent from my D2305 using Tapatalk
pradhana said:
No matching service for my phone
using D2305.
Any help?
Sent from my D2305 using Tapatalk
Click to expand...
Click to collapse
Only for lte single sim phones...
Sent from my D2403 using XDA Free mobile app
@galaxyfreak
Hello I like to ask you is the new recovery that you provided in your CM12.1 thread compatible with stock official kitkat roms?
I like to thank you for the work you put into to cm12.1 and previous versions.
and looking forward to the true recovery soon
HatchetEgg said:
@galaxyfreak
Hello I like to ask you is the new recovery that you provided in your CM12.1 thread compatible with stock official kitkat roms?
Click to expand...
Click to collapse
It should work.
@galaxyfreak
OK thanks for the reply. I have used the fastboot method to flash the recovery and found no change to that part of the system.
Just flashed new bootloader and yes: PM is working now with latest kernel/AOSP.
Thank you!!
Further testing will be done and posted in other M2 forums.
Konstantinosj77 said:
Only for lte single sim phones...
Sent from my D2403 using XDA Free mobile app
Click to expand...
Click to collapse
Well...
Thank you
Sent from my D2305 using Tapatalk
Only built by me, all the thanks go to the developers who work on the source code for the Xperia phones.
https://onedrive.live.com/redir?resid=A8E8D2CE3C5C608!14981&authkey=!AI6uJgVWtjw3jG8&ithint=file,zip
Great!
is there any bugs?, its just 300mb
leel55 said:
Great!
is there any bugs?, is it flashable?
Click to expand...
Click to collapse
I flashed it just 30 minutes ago, in TWRP, standard procedure, wipe data/system/dalvik, flash the zip. It looks good so far (had only one crash, the phone rebooted)
Camera is not working of course.
The bugs are the same as in every other 6.0 ROM. (I'm building a few other ROMs for 2303)
Wifi and calls work. Bluetooth, I only turned it on/off, didnt test connectivity. Gps, i think it works too. The light sensor works. Proximity switch doesnt.
It has root.
quake73 said:
, i need camera work ,until your fixing it should use the same rom then
Click to expand...
Click to collapse
leel55 said:
quake73 said:
, i need camera work ,until your fixing it should use the same rom then
Click to expand...
Click to collapse
I know, it has bugs but nobody has shared any rom for a long time and I thought I'd share a few.
As for the camera, we'll have to wait for the developers to find a way and make it work in 6.0.
Click to expand...
Click to collapse
how to install this rom ,it cannot be flashed with twrp or philz
Good work bro wait until you fix the camers and I will try to use it if it's not lagging I will make it as my daily driver. Keep it up.
Xperia m2,xposed,modded,cam 2.0,xreality,deodexed,z5style,themes,tweaked buildprop for better battery and performance and more..
great work..to be continued to fix all bug
Good work bro I've been try this rom inside my d2305 after 2 hour all is work perfectly without camera work but inside my phone mobile data may not working can you help me to fix this ?
Sent from my D2305 using XDA-Developers mobile app
I only have tried the rom on my d2303. Try changing the network type on your phone, LTE<->3G.
I admit, the rom is not for daily use. I'm trying to build a few other roms based on lollipop, DU too. If i succeed, I will post them.
vinz156 said:
How did you flash it
Click to expand...
Click to collapse
Simple install i do wipe data cache dalvik and system after that i install the room
Sent from my D2305 using XDA-Developers mobile app
---------- Post added at 12:28 PM ---------- Previous post was at 12:26 PM ----------
quake73 said:
I only have tried the rom on my d2303. Try changing the network type on your phone, LTE<->3G.
I admit, the rom is not for daily use. I'm trying to build a few other roms based on lollipop, DU too. If i succeed, I will post them.
Click to expand...
Click to collapse
Can you make ressurection or pac rom ?
Sent from my D2305 using XDA-Developers mobile app
Yes, those, too. Learnt how to build roms, got excited and filled my pc with source code of aokp, du 5&6, slim 5&6, pac 5&6, rr 5&6 and cm 12/13
My plan is to try and build them. Will share any success here of course.
vinz156 said:
Simple install i do wipe data cache dalvik and system after that i install the room
Sent from my D2305 using XDA-Developers mobile app
---------- Post added at 12:28 PM ---------- Previous post was at 12:26 PM ----------
Can you make ressurection or pac rom ?
Sent from my D2305 using XDA-Developers mobile app
Click to expand...
Click to collapse
Did same thing but failed, update binary, build prop issue ,here is a screenshot
Sent from my XPERIA M2 using XDA-Developers mobile app
open the zip file........
go to META-INF\com\google\android\.........
open 'updater-script'........
delete the first line (see the pic)........
save the file when the zip program asks (just to be sure that you did everything right, reopen the file 'updater-script' and check to be sure that the line that says "....eagle...." is gone.)
copy the new zip to your phone and try flashing it again
use twrp 3.0.2 from linuxct
Sent from my D2305 using XDA-Developers mobile app
Congratulations! It's great that new developers appears in this device. The Xperia M2 needs developing. Will try in my D2403 Aqua shortly
quake73 said:
oops ,hard bricked, flashed successfully ,but now no sony logo nothing
Click to expand...
Click to collapse
leel55 said:
quake73 said:
oops ,hard bricked, flashed successfully ,but now no sony logo nothing
Click to expand...
Click to collapse
Did you update your bootloader? Flashed the right twrp recovery?
Look around the forums for instructions
Click to expand...
Click to collapse
Mobile data is not working for me
settings continuously stops