Related
SEtweak kernel for Xperia S.
Intro:
I know I failed last time (with Play - it was stolen) and left development. But let's be serious this time.
Since it'll take a bit to set up everything again, I've taken DooM's ramdisk (hope you don't mind) for the first test.
Note: I don't have the device so I can't test it. If you want to, you can donate via Donate button on the left.
Sony finally published everything we need to build kernel.
Due to some possible bootloader problems, kernel might not work.
Features:
Codepage 852 (purely selfish reasons )
NLS UTF-8 (Native Language Support)
NTFS support
TUN/CIFS support
Default governor set to 'ondemand'
Prerooted
init.d support
Coming soon:
More governors
Recovery
Download: be patient
Best regards,
Blagus
Cool.
Ive unlocked my bootloader already so ill test it for you.
Im not rooted yet tho. I did have the rooted rom installed form another thread but i was having issues with app crashes so i flashed the stock .67
Hi there,
I hope the kernel wil be pre rooted and have some nice features....
I will try it
I need someone to send me kernel.sin of 6.0.A.3.62 firmware.
Hi there,
You can download it here : https://github.com/DooMLoRD/Xperia-2012-Official-Kernel-Sources and if its not there you can find it here http://eddy.uni-duisburg.de/bin4ry/L...1257-3921).ftf
Blagus said:
I need someone to send me kernel.sin of 6.0.A.3.62 firmware.
Click to expand...
Click to collapse
Im uploading it now for you
Edit:
Done
https://rapidshare.com/files/1187401250/kernel.sin
Don't bother Blagus. At this point, you can't really use a custom boot image due to a bootloader bug.
deovferreira said:
Don't bother Blagus. At this point, you can't really use a custom boot image due to a bootloader bug.
Click to expand...
Click to collapse
Really? Any more info on that?
It seems to affect some units at this point, I know of others which can boot just fine though using the instructions provided by Sony. This is the one thing preventing CM9 porting at this point.
deovferreira said:
It seems to affect some units at this point, I know of others which can boot just fine though using the instructions provided by Sony. This is the one thing preventing CM9 porting at this point.
Click to expand...
Click to collapse
hi defer,
what is the bug exactly?
i faced some issues yesterday when testing out kernels on a users device...
whenever we tried hotbooting the kernel (fastboot boot kernel.elf) the bootloader always returned "Wrong range" even though i used exactly the same ranges as given by Sony....
the test kernels are posted here:
http://forum.xda-developers.com/showthread.php?p=23868276#post23868276
if anyone wants to try them
I don't know the specifics of the bug, but it's in the bootloader it might be anything really, no way to know. However, what happens is that the bootloader is able to boot signed kernel.sin files but not the unsigned kernel.elf
This isn't another one of those 'can somebody port Sense' threads.
Please note that this thread is for developer-oriented discussion. If you don't have anything to say to help development, please refrain from posting here.
Also note that ideas are welcome. Just check if the idea you're about to post has already been posted by somebody else.
Right now, it's just multiple people working on this. No team, just individuals.
As of the last edit of this post, there has been little to no progress:
I'm constantly working on builds. The current, and the only goal I'll be striving towards as of now is using a T-Mo HTC One X ROM in combination with RaymanFX's CM10.1 RC2 build.
XDA RC @abcdjdj has reported that he has fixed a lot of errors in his build, and is now stuck at the bootanimation. If you can help him in any way, here is what's wrong with his build. He's using FXP's CM9 as a base and a 4.0 HTC One X with Sense 4 ROM as a port.
The OP will constantly be updated with any progress anyone makes.
We're currently using this XDA thread to help us port the ROM.
--------------------------------
Here's everything I have to share on my build:
PORT: HTC One X, T-Mobile Edition| Android 4.2.2
BASE: Sony Xperia S, nozomi | Android 4.2.2
------------------------
ITesters needed. If you can work through adb commands and can provide me with logcats, please leave a post about it in the thread.
And finally, a note to anyone that may be cursing me for working so very slow (because I admit, this is very slow):
Please understand that all this isn't easy for me. I have painfully slow internet, making each download at least one hour, and thus a pain. My time on this project is limited every day, so progress is slow.
Reserved.
someone755 said:
Okay, so this is the work that has already been done and some of the mysteries that puzzle me right now:
I've edited the CM9 kernel's ramdisk, like stated in the tutorial I'm using (see post 1). As of now, the kernel itself is broken and even if the ROM was complete, not even the booting would work. (Well, booting works as far as showing the boot logo (the green FXP one) goes. But the LED notification light for entering recovery doesn't light. Bootloop over and over...)
Many of the lib files intended to be copied from one lib folder to the other are missing on our Nozomis... My question is, what are the consequences...?
My main issue here is that the zip won't flash. The recovery (no matter which I choose) just returns an 'ERROR' and refuses to flash the file...
Another question would be how to repack an .elf kernel into a boot.img. Because now, I'm trying with letting the CM9 kernel in the zip (since it is an .img) and then flash the modified .elf kernel that I repacked with Flashtool. Inefficient, but at least there's a way.
So currently, the priority list would be:
1.Get zip to flash
2.Fix kernel
...Not necessarily in that order. We could fix the kernel first, but there isn't much gain to it if the ROM zip can't even be flashed to test if it truly works...
Click to expand...
Click to collapse
Bro, it may be possible to get Sense on our devices. Even I have been working on getting Sense booted on our device. My status:-
PORTED FROM - HTC ONE X
BASE - FXP 215 CM9
STATUS - Gets past kernel and even loads bootanimation. Fixed many errors in the logcat. Gets stuck at bootanimation and even displays a message saying that System is not responding, would you like to close it.
I couldn't manage to fix any more errors in the logcat so I gave up but you have rekindled my spirit to get Sense booting on out device. I will upload my rom soon along with the logcat.
Cheers,
abcdjdj
Wow, you actually got the thing to boot?
The only question is how did you manage that based off of a tegra CPU? Would be very interested in seeing that...
On a not-so-very related note, your port was of ICS and Sense 4 , correct?
Am I the only one around here that favors old software?
someone755 said:
Wow, you actually got the thing to boot?
The only question is how did you manage that based off of a tegra CPU? Would be very interested in seeing that...
On a not-so-very related note, your port was of ICS and Sense 4 , correct?
Am I the only one around here that favors old software?
Click to expand...
Click to collapse
Not fully booting but I think close to booting. I followed the guide mentioned by you in the OP and one by one eliminated all errors that I could eliminate. I had been working on Sense for around a month during my school holidays but now I am not getting any free time. And yes it is Sense 4 (Android 4.0.4).
Sent from my LT26i using xda app-developers app
But isn't the Tegra3 completely different than our FUJI board?
Especially the graphics, those must be out of control on your ROM...
If I were you, I'd at least take the AT&T version of the HOX.
Oh yeah, I forgot to ask: is it the same if I try and port from a MSM8260 board (the same as the Xperia) and the later S4 Qualcomm versions (used in the Xperia T, AT&T One X etc.)? Because porting from a CDMA phone (HTC Rezound) seems to make the work harder...
Thankfully, my summer holidays have just begun, so I have plenty of free time (that's also the reason I started my project).
P.S.
Yeah, maybe that's exactly what I should do. Ditch the CDMA phone and start with the Snapdragon S4 One X!
I would prefer Sense 3.x, but oh well, at least Sense4 is also Sense
http://www.xda-developers.com/android/sense-4-ported-to-sony-xperia-devices/
I just found this. It's not even that old...
Anyways, I've been thinking if the devs of this would be able to help us.
This development stuff gets boring pretty quick when you do it for the 10th time
@samuel2706, could you give these guys a little hand?
But he's a HTC Dev... Wouldn't we need something more like a nexus or better yet a Xperia developer?
someone755 said:
But he's a HTC Dev... Wouldn't we need something more like a nexus or better yet a Xperia developer?
Click to expand...
Click to collapse
Yes,, maybe, but he also could give a little help. Can't he?
Sent From my LT26i using Tapatalk 4
Contact the guy who did this http://forum.xda-developers.com/showthread.php?t=2184706
Well, I thought I'd make this thread so that devs could help each other to actually work together and create a working Sense ROM. So naturally, all help is welcome from anyone.
Anyways, I'm on my way to finishing yet another try, this time with the AT&T One X. Fingers crossed that it at least makes it to the bootanimation.
EDIT: I see that the easiest way to get Gapps is with including the default /data folder from the original HTC ROM (with vending, youtube etc.). But I have to add that to the updater-script. So, I want to ask, is /dev/block/mmcblk0p14 the data partition on the Nozomi?
What's happening?
samuel2706 said:
What's happening?
Click to expand...
Click to collapse
Hi,
I am porting [or trying to port] Sense 4 from HTC One X to Xperia S. I used FXP 214 CM9 as a base. I followed this guide - http://forum.xda-developers.com/showthread.php?t=2245786
Then I fixed as many errors as I could by checking the logcat and got it till the Bootanimation. But now I need help to get it to boot. So, I have attached the logcat from my latest build.
Thanks for your help,
abcdjdj
Maybe copying a few more files could help. Maybe act like your xperia is a HTC device? http://forum.xda-developers.com/showthread.php?t=1222746
Could be worth a try and play with this copying a bit...
Seems to be failing at dalvik; very strange, it doesn't show any major errors on first glance however I'll take a longer look at when I can, however I can link you to this thread that may help you in the meantime Porting
What about this one? http://forum.xda-developers.com/showthread.php?t=2276871
Nice and automated, but the question is, will it work?
I'm trying it with the HOX, just need to wait for it to copy to the phone...
All this seems like a big race -- who will get it working first? Hyped!
Kinda makes me wish I still had my xperia S I could have given this a real good go at; but instead I have a galaxy s4, so it's going to be mostly logcats and such I can help with, I don't like blind building things; made that mistake before.
A blind build is better than no build. Unless it makes bricks...
Thanks a lot for helping out.
Though I'll never understand how a pro HTC dev can go to Sony and then Samsung. ;P
I just hope THIS time my kernel will boot... Cause if it doesn't ... [censored]...
EDIT: Okay, [censored] is happening... Why can't I make this zip flash? I've done it a million times, but all I get is ERROR... ;-;
unfotunatly, i'm not a dev. but i really like the idea. specially if considering porting htc one sense version to our nozomi. i think it would fit like a glove
http://forum.xda-developers.com/showpost.php?p=56292388&postcount=15
http://forum.xda-developers.com/showpost.php?p=56292388&postcount=15
http://forum.xda-developers.com/showpost.php?p=56292388&postcount=15
:highfive: somebody test it & say howz it? will try then..
thanx @Ashwin Prabhunerurkar for CM
brother you a killer
finally feeding to dead devices
waited a long for this
thanks thanks thanks a lot
Finally CM
Thanks A Lot Developers
Sorry But I won't be Flashing It Until the Bugs gets Sorted Out.
I want to Use it as My Daily Driver
surely the best diwali gift for t2 owners
Great Job Man!!!! Big THANKS to ALL the developers!!!!:thumbup:
I would love to test it, but, unfortunately camera is a must for me. I'll wait till the bug gets sorted !!!
Sent from my D5322 using XDA Premium 4 mobile app
Camera Fix
Glad to see the first (nonstock) basec custom ROM. Couple of noob questions - does the bootloader needs to be unlocked for this. I have a rooted phone with dual recovery.
What are the camera files you have tried copying to this ROM from the Ultra Dual. I am presuming you have already done it but thought i could chime in. Have you copied libcameracustom.so and libcameraservice.so?
kan_ranga said:
Glad to see the first (nonstock) basec custom ROM. Couple of noob questions - does the bootloader needs to be unlocked for this. I have a rooted phone with dual recovery.
What are the camera files you have tried copying to this ROM from the Ultra Dual. I am presuming you have already done it but thought i could chime in. Have you copied libcameracustom.so and libcameraservice.so?
Click to expand...
Click to collapse
to have CyanogenMod you have to flash a custom kernal and to flash custom kernal you have to unlock the bootloader
this i my understanding
abt camera its my observation in CyanogenMod camera is always issue in early built but getting fixed later on
so i am sure in next built it will get fixed
THANK YOU SO MUCH FOR THIS!!! If not for the camera and led issues, I would gladly test it for you right away!
Super ninja edit: I think this belongs in original android development.
Sent from my D5322 using XDA Premium 4 mobile app
Can't Thank you enough for this...
P.S please fix the camera, and consider the feature request I have submitted in the panel, since that (feature request) is one the biggest flaws with the Stock ROM
Thanks again
This is not cool. You have published a ROM based on unmodified sources of other people's work, which is still incomplete, and is in fact worse than the current status of that work.
This is (probably) against the rules of XDA and has been reported.
Not only that but you explicitly state that you have no idea how to fix the issues present in this ROM. Anyone who installs this ROM risks damaging their device.
We didn't released the ROM for a reason. Do not use the sources to build the ROM without permissions and act like dev when you didn't contribute even one bit. These sources were not meant for a public release yet. AdFad did all the major work on this so atleast ask him before doing such stuff. Reported the thread, proper action will be taken soon.
Moreover you are asking for thanks for such kang
AJ
Thread closed. The OP of this thread hasn't taken part in the development and released it without credits. You should all wait for original developers to release it.
I'm really disappointed to see such situations on XDA.
Thank you,
Tom
Since lollipop is out now for the z1 compact there are a lot of threads about upgrading, rooting, xposed working - not working.
Just as many of you I'm running on kitkat / unlocked / rooted and I make use of xposed modules.
I've been looking through some of those threads but once you think you know the way to go there will be somebody else experiencing problems with that specific method.
I'm looking for a broader perspective.
Just as there are threads about how to upgrade there are also a lot of bugs mentioned but not everybody seems to be impacted by them.
And there are of course the custom roms, some kitkat based some lollipop based.
Before switching to the xperia I used a HTC One and there was a custom rom developer who would stick to the options foreseen in the original one but he changed the code for speed and reliability, it was also based on a aroma installer that gave the choice to leave some bloatware out at installation time.
This is something I would like to see happening for the z1c, not just adding new features but streamlining the existing rom.
As of now I'm running on the xzdualrecovery on a rooted and unlocked kitkat and I'm using some xposed modues.
I consider upgrading if I knew more about the bugs, will I be impacted and I'm looking for a complete guide on how to.
As far as I know the Italian customized rom is the one with the least bloatware in it, so that is he one I'd like to use as a start
Some people already have reported zip files you can flash from recovery and they seem to be pre-rooted. Do I need to use one of them or is it possible to
flash a rom
unlock or do I need the unlocked bootloader from the beginning?
root it
make sure xposed runs, xposed seems to need deodexed roms, are they available?
So I like to see a plan on how to
Unlock
root
upgrade
make xposed running
have a correct bootloader
and have a recovery (xzdualrecovery or something else)
I know this is a list of questions but such a guide would help a lot of people like me, I'm not a complete newbie but I'm neither a rom developer so I like a guide on how to accomplish things.
If the stock rom is bugfree and stable enough that's the one I'd stick to, otherwise I need to have a look at custom roms and then I think I need to consult the custom rom developer on how to install his/her custom rom.
All the above mentioned questions will be related to installing / unlocking / rooting a stock rom.
Eagerly checking this post for replies ?
bumjrah said:
Eagerly checking this post for replies
Click to expand...
Click to collapse
At least I have one guide
http://techbeasts.com/2015/04/20/root-xperia-z1-compact-d5503-14-5-a-0-242-5-0-2-firmware-plus-recovery/
This seems enough for unlocking and rooting, don't know about xposed, they don't mention it.
Even then they talk about how to unlock your bootloader.
I've done it this way in the past but I'm unsure if the bootloader for KK is the same as for Lollipop, I have no idea if this is changed. There is a thread about an unlocked bootloader, I'll ask over there if they know about differences between LP and KK, if there are none then we have guide explaining all the steps
I do not have any info yet on the bootloader but I do have some more news on Xposed.
It's not only the Xperia that's having problems with xposed on lollipop, other phones are impacted as well.
Once a certain number of apps is installed the bootlooping starts.
Xposed seems to open too many files at boot time.
A solution is to find out how many apps may be installed on your phone before it gets into a bootloop.
Another (and better) solution is to increase the upper limit of open files at boot time, but this is only available on an unlocked bootlader since it requires a modified kernel to be installed.
A lot of posts can be found at Xposed for lollipop.
Since xposed is still in an alpha phase I think rovo89 will fix this in a future release of xposed.
If you want to fix this right now you can have a look at this thread
The post about the changed kernel is this one
I am on stock RU version, heard it was the best I have also had some bootloop experiences with xposed. Some guys have reported success but their method requires a "bloatware" script that removes ****load of useful apps. Bleh!
Right now it's just wait and see. I miss xposed but am also really enjoying this lollipop update, the performance (too soon?) looks better than the custom roms available. IMO
Hello XDA, I have been working on an Aosp-ish nougat rom for our beloved trltetmo. It has nearly no features yet, since it's an AOSP ROM. I'm a Nexus dev, and just recently started working on the trltetmo because I bought one. I had a marshmallow rom and kernel(but tend not to release stuff to anyone to avoid drama and the eta requests).
Downloads: https://www.androidfilehost.com/?a=show&w=files&flid=111459
I have uploaded my work to GitHub: http://github.com/TrlteNougat
For now until I get my gpu back, you have to flash this kernel for MM bootloader support: https://www.androidfilehost.com/?fid=529152257862667083
Known issues:
- Camera is wonky. It's going to be difficult to fix
- The phone acts like it's a dual sim phone, no usability is sacrificed, it just shows two APN settings and the carrier on Dialer
Features:
None yet, it's AOSPish
What is being worked on:
Bluetooth
Call audio (mixer_path issues)
The kernel source is up: https://github.com/TrlteNougat/kernel_samsung_trlte/commits/n7.0
Manifest located here: https://github.com/TrlteNougat/manifest
Nice! Subscribed.
Test build
https://www.androidfilehost.com/?fid=24723757092306996
This one doesn't reboot randomly. Still has ril and Bluetooth errors. Sound doesn't work. Camera does.
I m not dev. But great to see work on 7 ...cheers to all devs...hoping for a stable one soon thx again
I'm keeping my eye on this thank you
Sent from my SM-N910T using Tapatalk
Ril is now partially working. I can send and receive texts. Calls cause a soft reboot, but shouldn't be hard to fix. Still no data connection yet, but that'll be fixed soon enough. Wifi connects but doesn't access internet for some reason. I haven't looked into that any.
Because why not
improper bootloader and in some cases modem can cause Wi-Fi to behave similar to how you have described. I'm not a TMO user but I think there should be several versions newer than OK2
if you have any desire to return to 5.1.1 or keep the option open to do it in the future, you may want to steer clear of the newest 2 or so bootloaders as they may prohibit further downgrading. if TMO is anything like Sprint, anything PE2 and older should still permit downgrades. newer versions I have not tested or seen any info on the topic.
[QRCODE][/QRCODE]ok I did a quick check and you are in fact on a 5.1.1 modem. I don't know if you've updated your bootloader but I get the feeling you would know if you have or not lol
all TMO MM firmware is newer than the Sprint firmwares (PB5, PC1, PD1, PE1, PE2) that I know to not prohibit downgrades, so you're on your own there.
if you believe the test builds to be compatible with the Sprint model, I'd be happy to help test as time allows for it
Sterist said:
[QRCODE][/QRCODE]ok I did a quick check and you are in fact on a 5.1.1 modem. I don't know if you've updated your bootloader but I get the feeling you would know if you have or not lol
all TMO MM firmware is newer than the Sprint firmwares (PB5, PC1, PD1, PE1, PE2) that I know to not prohibit downgrades, so you're on your own there.
if you believe the test builds to be compatible with the Sprint model, I'd be happy to help test as time allows for it
Click to expand...
Click to collapse
910T can be downgradable to DOK2 but not below that (unless you use work around and flash 910T2 firmware, which will allow you to go to 4.4.4 BL , and still can come back to latest) but thats a different story, regardless of that , however , you can anytime switch among DOK2 to PE3 to PG2 in any order. I think android N for 910T should be tested on EPG2 and not on DOK2 , atleast should give it a try on EPG2. I think the dev @USA-RedDragon , already must have tried all bootloaders and basebands , i m just replying to above posts.
Manan79 said:
910T can be downgradable to DOK2 but not below that (unless you use work around and flash 910T2 firmware, which will allow you to go to 4.4.4 BL , and still can come back to latest) but thats a different story, regardless of that , however , you can anytime switch among DOK2 to PE3 to PG2 in any order. I think android N for 910T should be tested on EPG2 and not on DOK2 , atleast should give it a try on EPG2. I think the dev @USA-RedDragon , already must have tried all bootloaders and basebands , i m just replying to above posts.
Click to expand...
Click to collapse
I tried EPE3 on mm but got too frustrated with the issues. So I've been weary to try it again. But you do have a point that I should try with newer bl/modem combos. I've got a mm rom compatible with epe3, so I might as well flash that. The Odin files are on my desktop staring me down
Side note, the logs point to something bring wrong wkth the code and not a bl/modem -> rom compatibility. But I could be wrong. Never hurts to try
USA-RedDragon said:
I tried EPE3 on mm but got too frustrated with the issues. So I've been weary to try it again. But you do have a point that I should try with newer bl/modem combos. I've got a mm rom compatible with epe3, so I might as well flash that. The Odin files are on my desktop staring me down
Click to expand...
Click to collapse
to make it easier ,why dont you just flash EPG2 BL and CP using odin (as opposed to entire MM rom) .and see if it fixes any of the issues with current N build.
Manan79 said:
to make it easier ,why dont you just flash EPG2 BL and CP using odin (as opposed to entire MM rom) .and see if it fixes any of the issues with current N build.
Click to expand...
Click to collapse
I'll do that. Progress is still ongoing with all this. But this week I've been busy with an Android Dev's biggest bane: a full-time job ?
USA-RedDragon said:
Side note, the logs point to something bring wrong wkth the code and not a bl/modem -> rom compatibility. But I could be wrong. Never hurts to try
Click to expand...
Click to collapse
sure ,i do understand that I do want to ask , how about xda devs who work for CM14 unofficial? i dont see much active devs on this thread, i would have thought all the note 4 devs who worked on CM13 unofficial would jump on this to help you out
Manan79 said:
sure ,i do understand that I do want to ask , how about xda devs who work for CM14 unofficial? i dont see much active devs on this thread, i would have thought all the note 4 devs who worked on CM13 unofficial would jump on this to help you out
Click to expand...
Click to collapse
Eh. I have other devs at my disposal. Most don't use XDA, and I tend to not either, but this(like any major version bump on a Samsung) is a big endeavor, so I made the thread for people to jump in if they wanted
USA-RedDragon said:
Eh. I have other devs at my disposal. Most don't use XDA, and I tend to not either, but this(like any major version bump on a Samsung) is a big endeavor, so I made the thread for people to jump in if they wanted
Click to expand...
Click to collapse
got it thx, let me know if you want me to test 910T builds, however i do need sim to be working for incoming/outgoing calls , cant live without that rest all i can test.