Related
This is a dev thread. Do not install this release unless you know what you're doing. Do not post if you have nothing to contribute.
This is very early build, we're behind other qsd8k devices but will eventually catch up
Big thanks to all qsd8k developers working on this (N1, Desire, HD2, X10).
[KERNEL]
- ol' good 2.6.29-SEMC
- fixed touchscreen driver (now backward-compatibile with Gingerbread)
[ROM]
- partially based on drewis release (thanks!) - currently I don't have access to PC that could handle compilation of the whole thing
If someone could compile clean es209ra build and upload it would be awesome.
[WORKING]
- it boots
- radio, calls, txt (sms)
- audio partially working (in-call is fine, playing mp3/ringtones leads to WLOD)
- bluetooth, GPS seem to work
- wifi almost working ("can't find wlan0 device")
- mobile data (it gets IP but disconects afterwards, needs investiagtion)
[NOT WORKING]
- most of the stuff does not work
- quite unstable
[SOURCES]
Will upload all of the useful code/fixes here.
- ICS + GB compatibile touch driver: es209ra_touch_mt.c
- compatibile ramdisk (props FXP): http://www.mediafire.com/?1n51pn1upwv79ur
[DOWNLOAD]
Alpha1 ROM (for CWM5) + corresponding kernel (flashtool) is here:
http://www.mediafire.com/?ht6p6tbpj2988d4
Cheers,
z
Just did a major clean up on this thread mates....no more "thanks" posts please. If thankful... click the thanks button.
Regards,
M_T_M
Finally we get it. aZuZu is working on ASOP ICS 4.0.1. This may help him work easier. So with locked bootloader, can we flash cause' you wrote there CWM5?
VIDEO
here's a video for ics on x10 alpha build 1
http://www.youtube.com/watch?v=bsOFn4YLvZU
@frosty666 please kindly include this on your ics discussion thread.
thankz
hi zdzihu, its great to see you back! is this only temporary or, are you going to be more active, like before?
mmmkay, I'm not dev, but I want to ask if you're compiling this from ground up (like Jerpelea's CM7), or you're like just mashup of current SE and ICS sources. if its a mashup, I can help. but I do very little design from ground up things.
Sent from my X10i using xda premium
if you have fixed audio hw sources i could recompile..
altho i have complete es209ra compile with ics hw, old cm gralloc / copybit sources and generic audio..
So for me doesn't even boot
As i came from night shift i will try later on more...
Here you are libhardware.so, libhardware_legacy.so & wpa_supplicant from my compiled ICS build so if someone can boot z rom maybe it could test this too
p.s.
it is searching ar6000.ko as normal stock one not wifi.ko as sdk port
aZuZu said:
So for me doesn't even boot
As i came from night shift i will try later on more...
Here you are libhardware.so, libhardware_legacy.so & wpa_supplicant from my compiled ICS build so if someone can boot z rom maybe it could test this too
p.s.
it is searching ar6000.ko as normal stock one not wifi.ko as sdk port
Click to expand...
Click to collapse
Hi Azuzu, I am able to compile single libs and binaries (libhw_legacy, supplicant), it's just dex and stuff causing problems (1GB of ram + 1.6GHz). As for libaudio, I will take a look soon
Cheers,
z
I help if u want
Hello guys, I'm new to the forum and I hope to see well with you.
I would be willing to help compile the source since EXCLUSIVELY use only Linux operating system and is much easier to work on programming because most of the libraries are already installed by default, I hope I was clear.
greetings
Joseph
zdzihu said:
Hi Azuzu, I am able to compile single libs and binaries (libhw_legacy, supplicant), it's just dex and stuff causing problems (1GB of ram + 1.6GHz). As for libaudio, I will take a look soon
Cheers,
z
Click to expand...
Click to collapse
yaay Z!!!
glad to see back!
now i feel so bad & depressed that i dont have a working x10 with me
hope that service center guy is able to repair it again...
@aZuZu
can u please upload ur work-in-progress sources to git... i know how much fixing u have done... it might help other too
aZuZu said:
So for me doesn't even boot
As i came from night shift i will try later on more...
Here you are libhardware.so, libhardware_legacy.so & wpa_supplicant from my compiled ICS build so if someone can boot z rom maybe it could test this too
p.s.
it is searching ar6000.ko as normal stock one not wifi.ko as sdk port
Click to expand...
Click to collapse
so good
I will try to build ICS this weekend!
I have no time this weekday
Zdzihu, if the wifi still reports the same error (can't find wlan0 device), it probably means that the kernel refers to wlan interface as eth0. Try changing the wifi.interface entry in build.prop to eth0.
little help for folks that compile ICS on weak pc
make: *** [out/target/common/obj/JAVA_LIBRARIES/framework_intermediates/noproguard.classes-with-local.dex] Killed << if processes during compile get killed try this script > Fix Swap
Well to me helped so maybe it helps other ppl.
Has anyone pulled this Kernel apart, i'm trying to lock down some of the touch screen info but I can't gunzip the ICS ramdisk...not even sure if i should be able to.
I GPIO the main files out, can't see anything pertinent in there, so I can only assume its in this ramdisk...biggest problem is that if it is a corrupted archive I can't get ubuntu to open a recovery tool cos it's implementation of the Zlib system sucks dice
WHAT IS IT WITH SOME OF YOU GUYS, IT IS DEV ONLY THREAD AT THE REQUEST OF THE DEVELOPER, IF YOU CAN'T FOLLOW SIMPLE RULES THEN INFRACTIONS WILL BE HANDED OUT, YOU HAVE NOW BEEN WARNED!
wbbigdave said:
Has anyone pulled this Kernel apart, i'm trying to lock down some of the touch screen info but I can't gunzip the ICS ramdisk...not even sure if i should be able to.
I GPIO the main files out, can't see anything pertinent in there, so I can only assume its in this ramdisk...biggest problem is that if it is a corrupted archive I can't get ubuntu to open a recovery tool cos it's implementation of the Zlib system sucks dice
Click to expand...
Click to collapse
gunzip -c <ramdisk.gz> | cpio -i
Cheers,
z
The next member who disregards a developers request and posts in a non helpful way will be banned for a week.
i encourage any dev or helpful member to pm me or any other mod with the offending post and the user will be dealt with
Please don't reply tp them to tell them they are breaking th rules as you post will then also be rule break worthy
Hugs and kisses
PiLoT
http://review.cyanogenmod.com/#q,status:merged+project:CyanogenMod/android_frameworks_base,n,z
sorry for posting here. but is for development. for ICS, can we used modified 2.6.29, and modify, like what zdzihu did, it so it 100% or do we have to use 3.x (or whatever) becuase I'm starting to do kernel mods and I want to see what I can contribution.
so in all, does the newest kernel have to be ported? or can we continue using good old 2.6.29 and keep Modding it? (hopefully camera will work, drivers have to be rewritten for kernel. and no one likr to write drivers)
Sent from my X10i using xda premium
In case, we can see here how they get the SD Card working
http://forum.xda-developers.com/showthread.php?p=19774268#post19774268
This rom is a port of the Stock Touchwiz Marshmallow beta build
Code:
#include <std/disclaimer.h>
/*
* I am not responsible for bricked devices, dead SD cards, thermonuclear
* war, or the current economic crisis caused by you following these
* directions. YOU are choosing to make these modificiations, and
* if you point your finger at me for messing up your device, I will
* laugh at you.
*/
I'm searching for Contributors, if you are interested, please send me a PM
Current Status: Released first Alpha (v0.1a)
Next Release ETA: ~ January 2016
Known Issues:
Stuck On Boot Logo
Click to expand...
Click to collapse
Install Guide:
Download the compressed file
Decompress the file
Reboot phone in download mode
Open the folder called "Odin + flash files"
Open Odin, flash the pit file (i9100-3GB) and the kernel (i9100-kernel)
Copy the continuingM flashable zip file into an sd card
Insert the SD card in the phone
reboot the phone in recovery mode
Wipe data/factory reset
Flash the continuingM Zip
Fix permission
reboot phone
Click to expand...
Click to collapse
Changelog:
v0.1a
Initial Release
Click to expand...
Click to collapse
Downloads:
Alpha 1
Click to expand...
Click to collapse
XDA:DevDB Information
ContinuingM Touchwiz Edition, ROM for the Samsung Galaxy S II
Contributors
firepenguin
ROM OS Version: 6.0.x Marshmallow
Version Information
Status: Testing
Created 2015-12-29
Last Updated 2015-12-29
Interesting project. Keep it up!
I'm having troubles with the Note 5 Update zip, it have only patch files, Someone have a dump, not update zip of the Note 5 / S6 Marshmallow beta?
firepenguin said:
I'm having troubles with the Note 5 Update zip, it have only patch files, Someone have a dump, not update zip of the Note 5 / S6 Marshmallow beta?
Click to expand...
Click to collapse
hi,
something like this ?
http://forum.xda-developers.com/showpost.php?p=63855358&postcount=122
http://forum.xda-developers.com/showpost.php?p=63854846&postcount=113
wel wel wel... rely intersting project keep up
Interesting,
I am waiting to test your rom.You know if we gonna have this function available ?
Call record
Code:
Voice call uplink + downlink audio source
Constant Value: 4 (0x00000004)
Interesting .......
Note 5 ported to s2 but with marshmallow.. interesting one.
@Senthil360 Maybe you have note 4 but check it.
GreekDragon said:
Note 5 ported to s2 but with marshmallow.. interesting one.
@Senthil360 Maybe you have note 4 but check it.
Click to expand...
Click to collapse
Yes bro but I guess device needs official marshmallow, Because i don't have much faith in Touchwiz when it comes to updates
And personally i believe stockis better than port in Touchwiz ROMs
Placeholders aren't allowed on XDA.
edi194 said:
Placeholders aren't allowed on XDA.
Click to expand...
Click to collapse
Actually, since this thread is clearly labeled "WIP" this is allowed. Ongoing development.
Thanks for your concern.
The_Merovingian
Forum Moderator
I will test to help development
I'm currently deodexing the dump and removing all arm64 libs/binaries. I think that the first alpha will be ready for the 2nd January
I've done the first build, Now i'm uploading it. It won't boot, it gets stuck on Galaxy SII logo, I don't know why. To flash it you need to repartition the phone. The file i will upload is a 7z file, so you need to decompress it to flash. The file contains odin, the pit file and the rom
Clean CM13 kernel can't boot TouchWiz rom. You need to modify it.
Wow nice & interesting Rom. Waiting for some screenshots!
But is this based on CM13 or a port from original TouchWiz FW?
I mean if this is a real port and would really boot you as a dev would have done the impossible to be possible. So i am a bit unsure if this rom will really boot. @arter97 and @Blekota gave already their best to get the newest touchwiz (4.4.4) feeling for our S3, but they could not get a port from a newer device running android 5 or 6, as there is no device with similar hardware. So I think there is no chance for a port to the Galaxy S2.
firepenguin said:
I've done the first build, It won't boot, it gets stuck on Galaxy SII logo, I don't know why.
Click to expand...
Click to collapse
This shows me that the rom will never boot. See my upper explanation.
But still good luck in this project, will keep following it, as when you would make this really possible you would have made a really big thing in the Galaxy S2 Android Life!
i confirm , no boot , sorry for s2.
I think S2 would be ported on S3 JB 4.3 stock firmware rather than this.
This is almost impossible... 64bit firmware is not compatible with 32bit device.
FaserF said:
Wow nice & interesting Rom. Waiting for some screenshots!
But is this based on CM13 or a port from original TouchWiz FW?
I mean if this is a real port and would really boot you as a dev would have done the impossible to be possible. So i am a bit unsure if this rom will really boot. @arter97 and @Blekota gave already their best to get the newest touchwiz (4.4.4) feeling for our S3, but they could not get a port from a newer device running android 5 or 6, as there is no device with similar hardware. So I think there is no chance for a port to the Galaxy S2.
This shows me that the rom will never boot. See my upper explanation.
But still good luck in this project, will keep following it, as when you would make this really possible you would have made a really big thing in the Galaxy S2 Android Life!
Click to expand...
Click to collapse
I don't own I9100 but porting stock firmware (like official JB 4.3 or ported FW like KK TW 4.4.4) from international I9300 should be possible and with good results.
Why? Of course because its similar hardware (Exynos/GPU Mali etc.)
But I'm not talking about porting with AOSP base like CM, this is long, long way to changing smali code in framework etc. Just trying adapt kernel (exactly ramdisk) to be able boot this official firmware, and changing device blobs - Mali libs/egl/audio libs/camera/av decoders and encoders libs/ril libs...this is possible.
I don't know if you will get "useful" ROM, but you should be able to boot it.
Like I ported just for fun one of official JB for S2 to Ace 2 (where hardware is really different), audio, video, camera wasn't working but ROM booting anyway...
Maybe it does not may any sense (I spent on this 2 hours), but I just wanna say its possible and results are good as hardware is close.
Good luck.
PolishVodka said:
I don't own I9100 but porting stock firmware (like official JB 4.3 or ported FW like KK TW 4.4.4) from international I9300 should be possible and with good results.
Why? Of course because its similar hardware (Exynos/GPU Mali etc.)
But I'm not talking about porting with AOSP base like CM, this is long, long way to changing smali code in framework etc. Just trying adapt kernel (exactly ramdisk) to be able boot this official firmware, and changing device blobs - Mali libs/egl/audio libs/camera/av decoders and encoders libs/ril libs...this is possible.
I don't know if you will get "useful" ROM, but you should be able to boot it.
Like I ported just for fun one of official JB for S2 to Ace 2 (where hardware is really different), audio, video, camera wasn't working but ROM booting anyway...
Maybe it does not may any sense (I spent on this 2 hours), but I just wanna say its possible and results are good as hardware is close.
Good luck.
Click to expand...
Click to collapse
Thank you so much. I will try your method
NEED HELP
Hello guys, I'm working on a generic tree for our beloved device Honor 7, but not getting enough success, so each and every of you are invited to help me create a new device tree for AOSP 5.1 ROM or CM 12.1, so that we can taste the Stock Android too.
The benefits of these ROMs are that the device will get more fast and stable as there will be minimum apps and bloatwares installed.
So, it is a humble request, that whosoever have any knowledge about creating a tree from scratch please help me.
I have created a skeleton of the tree but it is not a success too as there are many things we still have to consider.
@sminki and @kenshiwara, we will setup an organization on GitHub so everyone can contribute there only.
Hi,
It will be wonderfull to have CM on our honor7.
Sorry mate. You haven't seen my troubles over the last few weeks then
After my H7 'died', I got a warranty replacement phone, and unlocking was proving impossible, each day was bringing more frustration and anger so i've sold it!
That's it, i'm out of the "honor" business for good (hence the "unsupported" bit on the recovery and kernel threads), but as a parting "gift", here's a few things that may help "the cause".
Sorry, the length of this post got out of control! :silly:
device tree starting point:
https://github.com/TeamWin/android_device_huawei_p8 - it's similar enough, that with a little editing and boom, we had our recovery*
https://github.com/debbiche/android_device_huawei_p8 - another fuller "tree" (wip), again the p8 is similar enough to use as a base
https://github.com/Gibbon99/android_device_huawei_hwgemini - mediapad x2 - another kirin
if you're insane, you could get the dtb files (iirc - i got these from compiling the source) and decompile, but this contains EVERYTHING, theses files are huge, many hundred kb and would take days to get the info out you need (if there is any!)
cm
have a look at codeworkx H6 git, it's the closest device you'll find that has CM actually running on it, albeit CM11 (and abandoned!)
https://github.com/codeworkx/proprietary_vendor_huawei
https://github.com/codeworkx/android_device_huawei_h60-common
other things:
osm0sis' kitchen out of the many boot image unpack/repack tools, this worked the best with huawei boot/recovery images
* with this in mind, anyone running Linux can pull apart my recovery, fix the issues in default.prop, add extra partitions to fstab and repack it. then post it for everyone else to use.
with the sh!tty way fastboot is on these phones, and the way modem binaries get patched, you're going to have to look for a way to write these in recovery (scripted with dd i imagine) so that everyone can use without having the ballache that is B100,B121,B140 etc etc to get to a version that will work with your ROM. this for me is where it's all going to hurt! (and end with bricks!)
final thing - the kernel source is terrible, it is so far removed from AOSP that simple things that you could normally just drop in, like cpu governors won't work. unless you really know C++ and how to debug it's gonna be near stock (like mine funnily enough!)
Good luck chaps :good: it's gonna be a hell of a ride!
sminki said:
Sorry mate. You haven't seen my troubles over the last few weeks then
After my H7 'died', I got a warranty replacement phone, and unlocking was proving impossible, each day was bringing more frustration and anger so i've sold it!
That's it, i'm out of the "honor" business for good (hence the "unsupported" bit on the recovery and kernel threads), but as a parting "gift", here's a few things that may help "the cause".
Sorry, the length of this post got out of control! :silly:
device tree starting point:
https://github.com/TeamWin/android_device_huawei_p8 - it's similar enough, that with a little editing and boom, we had our recovery*
https://github.com/debbiche/android_device_huawei_p8 - another fuller "tree" (wip), again the p8 is similar enough to use as a base
https://github.com/Gibbon99/android_device_huawei_hwgemini - mediapad x2 - another kirin
if you're insane, you could get the dtb files (iirc - i got these from compiling the source) and decompile, but this contains EVERYTHING, theses files are huge, many hundred kb and would take days to get the info out you need (if there is any!)
cm
have a look at codeworkx H6 git, it's the closest device you'll find that has CM actually running on it, albeit CM11 (and abandoned!)
https://github.com/codeworkx/proprietary_vendor_huawei
https://github.com/codeworkx/android_device_huawei_h60-common
other things:
osm0sis' kitchen out of the many boot image unpack/repack tools, this worked the best with huawei boot/recovery images
* with this in mind, anyone running Linux can pull apart my recovery, fix the issues in default.prop, add extra partitions to fstab and repack it. then post it for everyone else to use.
with the sh!tty way fastboot is on these phones, and the way modem binaries get patched, you're going to have to look for a way to write these in recovery (scripted with dd i imagine) so that everyone can use without having the ballache that is B100,B121,B140 etc etc to get to a version that will work with your ROM. this for me is where it's all going to hurt! (and end with bricks!)
final thing - the kernel source is terrible, it is so far removed from AOSP that simple things that you could normally just drop in, like cpu governors won't work. unless you really know C++ and how to debug it's gonna be near stock (like mine funnily enough!)
Good luck chaps :good: it's gonna be a hell of a ride!
Click to expand...
Click to collapse
Thanks, this will help enough and I was not aware of your troubles
I got a device tree working with CM12.1 and USB debugging, but Mali was a showstopper. Now I'm fighting with CM13 instead... Generally, the B313 ROM is far less hacky, but we lose the open source kernel for a while until they release one.
I will set up a GitHub tree with what I have when I get CM13 compiling again, however keep in mind that you need to patch the boot.img manually to use the closed-source B313 kernel until Huawei releases the source for that, which probably won't happen at the very least until it's fully in OTA. I'd love some help from someone who is more experienced, especially with the Mali drivers which are the worst of pains.
EDIT: I got CM13 compiling again. Let's hope for the best.
EDIT2: Mali works! Sadly, that currently depends on Huawei's libgui.so which brings in a huge chunk of Huawei's patched libraries - otherwise, it segfaults in strange places. Any ideas?
Is there any whatsapp group of honor 7.I want to join it.
udayraj99 said:
Is there any whatsapp group of honor 7.I want to join it.
Click to expand...
Click to collapse
Stop spamming
Omg I think I will never receive a Custom ROM for PLK-UL00 as they didn't release source code for that and device tree is way far
Mee too
omkarpranavxxx said:
Omg I think I will never receive a Custom ROM for PLK-UL00 as they didn't release source code for that and device tree is way far
Click to expand...
Click to collapse
As an indian user evwn i feel i made wrong choice....should have gone for one plus x
asiekierka said:
I got a device tree working with CM12.1 and USB debugging, but Mali was a showstopper. Now I'm fighting with CM13 instead... Generally, the B313 ROM is far less hacky, but we lose the open source kernel for a while until they release one.
I will set up a GitHub tree with what I have when I get CM13 compiling again, however keep in mind that you need to patch the boot.img manually to use the closed-source B313 kernel until Huawei releases the source for that, which probably won't happen at the very least until it's fully in OTA. I'd love some help from someone who is more experienced, especially with the Mali drivers which are the worst of pains.
EDIT: I got CM13 compiling again. Let's hope for the best.
EDIT2: Mali works! Sadly, that currently depends on Huawei's libgui.so which brings in a huge chunk of Huawei's patched libraries - otherwise, it segfaults in strange places. Any ideas?
Click to expand...
Click to collapse
Hello, did any of the CM compiled fully to be a flashable zip? if yes, then have you flashed it and took logcat?
Nishadan said:
As an indian user evwn i feel i made wrong choice....should have gone for one plus x
Click to expand...
Click to collapse
Yup lesson learnt snapdragon or nothing frm now on
maybe you know
I post link - http://download-c.huawei.com/downlo...oadId=62086&version=204465&siteCode=worldwide
Honor 7 Open Source（PLK-L01_Android5_0_2_EMUI3_1_kernel_EN)
Any progress?
I hope I can do something,it is nice to see cm for honor 7.
Since it has been a while that any Info came out of this thread I have to ask.. Is anyone still working the tree?
I normaly do not ask for etas but in this case it would be useful if the thread is abandoned that we could know the reasons and Problems so maybe someone else could join in with a different approach
cycovision said:
Since it has been a while that any Info came out of this thread I have to ask.. Is anyone still working the tree?
I normaly do not ask for etas but in this case it would be useful if the thread is abandoned that we could know the reasons and Problems so maybe someone else could join in with a different approach
Click to expand...
Click to collapse
I'm a bit busy to continue my work on the tree, but after my exams I will continue to work on tree with Android 6.0 source. Hope it goes well.
DigiGoon said:
I'm a bit busy to continue my work on the tree, but after my exams I will continue to work on tree with Android 6.0 source. Hope it goes well.
Click to expand...
Click to collapse
good luck with your exams
Until then you can use this
New ROM for Honor 7 PLK-L01.
DigiGoon said:
Until then you can use this
New ROM for Honor 7 PLK-L01.
Click to expand...
Click to collapse
Can we get a kitkat rom if your work with the device tree is done ? I really do miss kitkat[emoji20]
Sent from my PLK-TL01H using XDA-Developers mobile app
muhammad Shohayeb said:
Can we get a kitkat rom if your work with the device tree is done ? I really do miss kitkat[emoji20]
Sent from my PLK-TL01H using XDA-Developers mobile app
Click to expand...
Click to collapse
I will be developing AOSP 6.0, if others can give it a try then maybe we can get it.
Hi guys, does anyone know where I can get stock ROM for ZTE Obsidian?
plectr said:
Hi guys, does anyone know where I can get stock ROM for ZTE Obsidian?
Click to expand...
Click to collapse
Or any custom ROM? Just any ROM?
The source code was published on http://opensource.ztedevice.com/. Is it "too hard" to make ROM out of this? Can I do it without special skills, just following a tutorial?
+1 ...
plectr said:
Hi guys, does anyone know where I can get stock ROM for ZTE Obsidian?
Click to expand...
Click to collapse
+1 any provider T-mobile or metroPcs...
Any luck? I'm in need of this myself.
Me, too! (+1)
Please, will someone with a proper kit dump the ROM? I, uh... over-rooted mine. But all is not lost! I still can get to recovery mode and it has flashing options! (With device in OFF state, hold VOL. UP + POWER + HOME. Navigate to RECOVERY MODE with VOL. UP, then VOL. DN to select. The green "sick Android" logo with a "!" appears. Press VOL. UP + POWER for approx. 5 seconds, then release both simultaneously. This should display all the recovery options.) We would be eternally grateful, and I promise lots of :good:'s! Because really, let's be honest: we're all here because we want one of those nifty "SENIOR MEMBER" badges. When I get one, I'm gonna have it tatooed on my arm. (Everyone knows chicks dig rooting skills.) In the meantime, I'll be trying to learn how to compile the source code from the link another member posted above...
Hey you guys... Really need this too... any progress?
Any news???
i have it but? how do y get it out of the phone
help do that and there y will have it
thanks mark
I'm a little concerned with the compile effort after carefully reading ZTE's Open-Source policies... It seems the "ROM" download for the Z820 found on their website contains only the open-source portions of the firmware. Not only am I having difficulty getting a "good" download with my backwoods Internet connection (3 attempts-all bad,) I'm afraid after compiling that I'll only have a partial OS ROM. Does anyone skilled (read: not a junior member like me) know if there's proprietary first or third party code in most OEM stock ROM's? If so, would those portions be available online to download and place in the proper partitions? ZTE's very specific wording spooked me... I mean, I ain't scared to give 'er a go as-is, but I'm curious. The thing's just collecting dust now...
Sent from my C6740 using XDA-Developers mobile app
Now I'm curious. I might have the ability to grab this little device. Let me have a look at the source code first, get my bearings, and I'll see what I can find. I've got a lot going on, so I might need a reminder or two... Hope you guys like android forums though, that's where I tend to linger
---------- Post added at 06:10 AM ---------- Previous post was at 06:05 AM ----------
Right, so I just found the sources. Downloading both the TMO and MPCS sources and will diff them tomorrow. That being said; they have only released the kernel source. Which is AMAZING considering, but not everything for a ROM. With this, I could make a custom ROM, figure out root (bootloader is covered luckily), and more! What I'm saying is; I'll give it a shot. I'll update this thread with developments as they come
I need this also!!!! PLEASE HELP ME!!! LOL THANK YOU!
crutchcorn said:
Now I'm curious. I might have the ability to grab this little device. Let me have a look at the source code first, get my bearings, and I'll see what I can find. I've got a lot going on, so I might need a reminder or two... Hope you guys like android forums though, that's where I tend to linger
---------- Post added at 06:10 AM ---------- Previous post was at 06:05 AM ----------
Right, so I just found the sources. Downloading both the TMO and MPCS sources and will diff them tomorrow. That being said; they have only released the kernel source. Which is AMAZING considering, but not everything for a ROM. With this, I could make a custom ROM, figure out root (bootloader is covered luckily), and more! What I'm saying is; I'll give it a shot. I'll update this thread with developments as they come
Click to expand...
Click to collapse
Just to keep you guys informed; I tried downloading both of the sources and couldn't get their tar.gz to extract completely in Linux - meaning we're totally stuck and that's it.
Kidding.
E-mailed the guys over there and after a few days they finally got back to me letting me know the site was down for maintenance and to try again in a few days. Doesn't sound too promising, sure, but at least we know that we don't have to post a formal legal request like the guys over at the Fire Phone threads had to do. I'll get that source for ya.
crutchcorn said:
Just to keep you guys informed; I tried downloading both of the sources and couldn't get their tar.gz to extract completely in Linux - meaning we're totally stuck and that's it.
Kidding.
E-mailed the guys over there and after a few days they finally got back to me letting me know the site was down for maintenance and to try again in a few days. Doesn't sound too promising, sure, but at least we know that we don't have to post a formal legal request like the guys over at the Fire Phone threads had to do. I'll get that source for ya.
Click to expand...
Click to collapse
FYI I already have a CWM Recovery compiled and ready to go for this device however thanks to Securelock and the 101 error any attempts at flashing via dd and no access to fastboot (tried zero'ing out the recovery partition to try to force bootloader) there is no way currently to flash to the device... I've already got a CM 12.1 build ported over also... Gonna work on a custom kernel next but only if we can get past this Securelock issue
I may be a junior member but trust I am a seasoned developer and have worked on roms such as the CM 10 port for the LG Optimus and F3 / F6.
BBQ Linux all the way!
xerolath said:
FYI I already have a CWM Recovery compiled and ready to go for this device however thanks to Securelock and the 101 error any attempts at flashing via dd and no access to fastboot (tried zero'ing out the recovery partition to try to force bootloader) there is no way currently to flash to the device... I've already got a CM 12.1 build ported over also... Gonna work on a custom kernel next but only if we can get past this Securelock issue
I may be a junior member but trust I am a seasoned developer and have worked on roms such as the CM 10 port for the LG Optimus and F3 / F6.
BBQ Linux all the way!
Click to expand...
Click to collapse
I'm out! Xero got y'all covered
xerolath said:
FYI I already have a CWM Recovery compiled and ready to go for this device however thanks to Securelock and the 101 error any attempts at flashing via dd and no access to fastboot (tried zero'ing out the recovery partition to try to force bootloader) there is no way currently to flash to the device... I've already got a CM 12.1 build ported over also... Gonna work on a custom kernel next but only if we can get past this Securelock issue
I may be a junior member but trust I am a seasoned developer and have worked on roms such as the CM 10 port for the LG Optimus and F3 / F6.
BBQ Linux all the way!
Click to expand...
Click to collapse
I can't wait for you to fix the z820 .thanks bro
xerolath said:
FYI I already have a CWM Recovery compiled and ready to go for this device however thanks to Securelock and the 101 error any attempts at flashing via dd and no access to fastboot (tried zero'ing out the recovery partition to try to force bootloader) there is no way currently to flash to the device... I've already got a CM 12.1 build ported over also... Gonna work on a custom kernel next but only if we can get past this Securelock issue
I may be a junior member but trust I am a seasoned developer and have worked on roms such as the CM 10 port for the LG Optimus and F3 / F6.
BBQ Linux all the way!
Click to expand...
Click to collapse
We're fortunate to have your expertise, zerolath! That's why I love XDA! This thing's driving me nuts! It's the only 64-bit device I have until my Raspberry Pi 3 arrives, and I hate that I was careless and didn't back it up first! Rookie error. But I have learned: my LG Leon is backed up and well rooted! I had the same issue as crutchcorn did with the kernel source code DL. Got a unexpected zero bit at #### error with multiple DL's. I'm not experienced enough to attempt flashing just the kernel anyway. I hope there's a way around the SecureLock protection!
Back-up EVERYTHING. Compulsively! ?
Cruise Elroy said:
We're fortunate to have your expertise, zerolath! That's why I love XDA! This thing's driving me nuts! It's the only 64-bit device I have until my Raspberry Pi 3 arrives, and I hate that I was careless and didn't back it up first! Rookie error. But I have learned: my LG Leon is backed up and well rooted! I had the same issue as crutchcorn did with the kernel source code DL. Got a unexpected zero bit at #### error with multiple DL's. I'm not experienced enough to attempt flashing just the kernel anyway. I hope there's a way around the SecureLock protection!
Back-up EVERYTHING. Compulsively! ?
Click to expand...
Click to collapse
Aye mate. XDA and programmer centric forums and such are pretty snazzy. Great place for people of all walks of life to learn, laugh, and grow.
I hope you can solve this... I too have this phone bricked at home, after flashing official update from ZTE...
Thank you so much for helping us!
Hey guys,
i'll try to get an Ubuntu Touch port running on my Tablet.
I've taken UbPorts 5-1 branch and synced it with cm12-1 cm sony source. The cm files build fine.
For the ubuntu files i removed ant-wirless to build the files.
After build finished sucessfully i added the ubuntu specific kernel configs and build again. Without any erros
Now i want to boot that baby but i don't get past the Xperia Bootloader screen.
I can't enable last_kmsg to debug the deivce because i get build errors otherwise.
So what i think of at the moment is that there are some wrong parameter for the sony boot.img ... but not sure about that.
Maybe somone of you can help me bring up that baby for us all.
Cheers
Moritz
Hey, did you get any luck with this? I am currently trying to port it to the Z3
CedArctic said:
Hey, did you get any luck with this? I am currently trying to port it to the Z3
Click to expand...
Click to collapse
no not really
Hahaha I posted before I found you on freenode xD