BEFORE DOING ANY OF THESE, KEEP IT IN MIND THAT IF YOU BRICK YOUR PHONE I'M NOT RESPONSIBLE FOR IT!!
Hi guys this is a tutorial on how to port roms for Xperia E1
Search for a phone that has the same motherboard, as the Xperia E1 MSM8210(MSM8610)
In this case, I downloaded an Andromax C2 CarbonROM
Phones with MSM8210/8610 chipset: Motorola Moto E, Andromax C2, ZTE Open C, ZTE Concord II
First you have to backup your current ROM using nandroid in the Recovery.
Without this step you won't be able to access the files which are needed to port
Not necessary to backup your ROM, but It is recommended, just in case If your E1 bootloops.
If you somehow bricked your phone, use XperiFirm to download the Stock rom and flash It.
1. Go to the PORT Rom and navigate to /system/framework/
2. Find and drop framework-res.apk to the Desktop
3. Rename the framework-res.apk to framework-res.rar (or framework-res.zip If you don't have WinRaR)
4. Open the framework-res and navigate to /res/xml/
5. Copy and paste the storage_list.xml you downloaded from here
6. Close the rar/zip and rename it to framework-res.apk and put it back to /system/framework/
7. Go tohttp://forum.xda-developers.com/xperia-j-e/general/philz-touch-recovery-xperia-e1-t2941831 and download the Recovery (If you already have it skip this step)
8. Put the boot.img in the root of the port's directory
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
9. Go to recovery and wipe cache, dalvik, media, data (everything)
10. Flash the zip
If you did it correctly, by now you should see the CM/AOSP logo
Enjoy! Hit Thanks If it was helpful!
Video tutorial: <work in progress>
Note: If the ROM won't boot, It is because the PNGs are too big for the phone, so you either need to resize them, or give up.
Or you messed something up. Re-check everything before flashing the .zip.
What's not working:
Bluetooth, GPS, Wi-Fi, VPN, everything releated to Internet; Sound
Xperia E1 Spec:
CPU: Cortex-A7 1,19GHz r0p3 (2 core)
GPU: Adreno 305 400MHz (300MHz by default)
Chipset: Qualcomm MSM8210/MSM8610
DPI: 240
Total RAM: 423mb (Physically 512mb)
You chose CM for porting ?
Where is the base ? MODIFIED RAMDISK FOR KERNEL, HAL(S), ETC !
Cm has to be build on a Linux system with source as a base.
:/
Simple Tutorial..
Sent from my D2105 using XDA Free mobile app
kaustubh.rockstar said:
You chose CM for porting ?
Where is the base ? MODIFIED RAMDISK FOR KERNEL, HAL(S), ETC !
Cm has to be build on a Linux system with source as a base.
:/
Click to expand...
Click to collapse
Yep, but If you found a phone that has similar motherboard to your device, it is easy to port stuff, but not 100% guraanted to work
Building from source is much better .. !
kaustubh.rockstar said:
Building from source is much better .. !
Click to expand...
Click to collapse
Without the source files it is impossible
Also, I'm a noob compared to you, I don't know how to begin
Oh please sir don't say like that.
wtf
Kizoky said:
Hit Thanks If it was helpful!
Click to expand...
Click to collapse
you mean : "helpful to brick the E1 phone ?"
mai77 said:
you mean : "helpful to brick the E1 phone ?"
Click to expand...
Click to collapse
Unexperienced user will brick E1 ofc
If there is any nandroid backup in the SD Card then there is no problems
@Kizoky
As far as I know, there is no nadroid available for the E1.
Also, I really think that we should make like a "dev team" and focus on working on CM11 (CM12?) for the E1.
It's not impossible, but WILL take a lot of time and work.
Hell, I'm in.
zeteny.nagy.20 said:
@Kizoky
As far as I know, there is no nadroid available for the E1.
Also, I really think that we should make like a "dev team" and focus on working on CM11 (CM12?) for the E1.
It's not impossible, but WILL take a lot of time and work.
Hell, I'm in.
Click to expand...
Click to collapse
There is Nandroid for the Xperia E1, it's the part of CWM. And it is working, it just needs more than 2 GB available space on SD card. Also, none of the developers have this phone and I don't think they will ever consider buying it just to develop CyanogenMod for it. If we could get a display driver for the E1 that works (Adreno 305 or whatever the E1 has) we could compile CM, according to Kizoky. Or maybe if we could get drivers working on the ROM that has been ported from the Andromax C2's CM. We tried, I managed to get sound working, but no WiFi or Service or anything. Otherwise, it was waaaay more smoother than stock... If we could get CyanogenMod 12 even if it's broken I'm sure I would get it even without WiFi or Service, I don't care. If I will get an 8GB SD card I will attempt to get things working on this CM11, as I found new files that may be able to get WiFi working. Also an interesting note, the stock kernel that comes with the stock firmware is working with this CyanogenMod, which also means that it's possible to get CM on Locked Bootloader and it may also be possible on other devices. It's really handy, especially because I cannot unlock my BL because it is from a career. Oh my that's a long message lol
xezrunner said:
There is Nandroid for the Xperia E1, it's the part of CWM. And it is working, it just needs more than 2 GB available space on SD card. Also, none of the developers have this phone and I don't think they will ever consider buying it just to develop CyanogenMod for it. If we could get a display driver for the E1 that works (Adreno 305 or whatever the E1 has) we could compile CM, according to Kizoky. Or maybe if we could get drivers working on the ROM that has been ported from the Andromax C2's CM. We tried, I managed to get sound working, but no WiFi or Service or anything. Otherwise, it was waaaay more smoother than stock... If we could get CyanogenMod 12 even if it's broken I'm sure I would get it even without WiFi or Service, I don't care. If I will get an 8GB SD card I will attempt to get things working on this CM11, as I found new files that may be able to get WiFi working. Also an interesting note, the stock kernel that comes with the stock firmware is working with this CyanogenMod, which also means that it's possible to get CM on Locked Bootloader and it may also be possible on other devices. It's really handy, especially because I cannot unlock my BL because it is from a career. Oh my that's a long message lol
Click to expand...
Click to collapse
That was a fast reply
So the thing is that the E1 uses the Adreno 302, exactly the same as the Moto E. Which means there are drivers floating around in the CM11 builds for the Moto E. It uses the same connection boards, too - DRIVERS EVERYWHERE.
Only if I had the knowledge to do all this alone, the thing is that I can't
EDIT: Could you give me a link for CWM? I only found Philz Touch and I don't really like that, I prefer CWM
zeteny.nagy.20 said:
@Kizoky
As far as I know, there is no nadroid available for the E1.
Also, I really think that we should make like a "dev team" and focus on working on CM11 (CM12?) for the E1.
It's not impossible, but WILL take a lot of time and work.
Hell, I'm in.
Click to expand...
Click to collapse
There is. There's already a recovery for E1, which has built-in Nandroid backup, available to use.
@Kizoky
I'm going to dig around in Moto E CM11 files, maybe I can extract some display drivers.
@Kizoky
I managed to get some Qualcomm-made .APK-s from various ROMs. Does that help at all?
zeteny.nagy.20 said:
@Kizoky
I managed to get some Qualcomm-made .APK-s from various ROMs. Does that help at all?
Click to expand...
Click to collapse
I don't think they would, but maybe they do. (maybe one of them manages WiFI connectivity) Try to install them onto CM and see what happens (reboot too)
xezrunner said:
I don't think they would, but maybe they do. (maybe one of them manages WiFI connectivity) Try to install them onto CM and see what happens (reboot too)
Click to expand...
Click to collapse
I managed to get GPS / Location services up and running. There are still tons of .APK-s that I haven't tried yet.
EDIT: I think I found the WiFi driver.
EDIT 2: @Kizoky Did you check the ROM made by @ramdanzs ? It probably contains the display drivers you needed.
EDIT 3: I managed to get telephony working but now it doesn't function.
zeteny.nagy.20 said:
I managed to get GPS / Location services up and running. There are still tons of .APK-s that I haven't tried yet.
EDIT: I think I found the WiFi driver.
EDIT 2: @Kizoky Did you check the ROM made by @ramdanzs ? It probably contains the display drivers you needed.
EDIT 3: I managed to get telephony working but now it doesn't function.
Click to expand...
Click to collapse
Wi-Fi and Bluetooth? Those 2 bastards that are always idling and don't do anything at all.
zeteny.nagy.20 said:
I managed to get GPS / Location services up and running. There are still tons of .APK-s that I haven't tried yet.
EDIT: I think I found the WiFi driver.
EDIT 2: @Kizoky Did you check the ROM made by @ramdanzs ? It probably contains the display drivers you needed.
EDIT 3: I managed to get telephony working but now it doesn't function.
Click to expand...
Click to collapse
If you get any drivers working, please let us know immidiately.
xezrunner said:
If you get any drivers working, please let us know immidiately.
Click to expand...
Click to collapse
Told ya, GPS is fine
---------- Post added at 05:50 PM ---------- Previous post was at 04:51 PM ----------
@Kizoky
I just found this tool called FTF Extractor can be used to decompress .FTF firmware files of Sony Xperia phones, just as listed in this article/tutorial on how to decompile .FTF files.
Is it possible to grab some drivers from the stock firmware and port it to CM11? Just askin'.
AFAIK .FTF files are just "renamed" flashable .zips so, their structure is the same.
Related
MTK 6575 STAR N8000 GUIDE AND BEST CUSTOM ROM INSTALLATION GUIDE.
<ul>
<li>First off I started this thread to seperate the current thread for this phone that is riddled with question and answeres and it is super difficult to find what you need to find in the thread. I am writing this guide and thread to give back to the forum for the many days and hours I spent finding everything I needed to find, to root, flash and mod this phone properly. My hopes are with my knowledge on the subject you wont have to spend hours of fruitless searching like I did to find what you need. I'd like this thread to stay uncluddered with multitude of questions if you have them, message me or go to this thread here and post please: http://forum.xda-developers.com/showthread.php?t=1695210&page=96
<li>I would like for anyone finding new ROMS, making custom firmwares for this phone to please add them here to begin a nice list of ROMS custom or official for people to be able to find them in one place.
<li>First off i'd like to give credit were credit is due. Shout outs to;
angelobiz
Bruno Martins
Kyrie1965
sas007
and anyone else I may be forgeting I appologize
The Guide
<li>Follow Bruno Martins guide for setting up sp flasher here: http://bm-smartphone-reviews.blogspot.it/2012/05/mt6575-flashing-tutorial.html#comment-form
<li>Just some notes and observations that were not mentioned in his guide that will help. In order to install the drivers try right clicking the driver for your system and selecting install. If that doesn't work here is what you do. Turn off your phone, take the battery out, put it back in (if you don't do this it will just show a charging symbol) now plug it in, it should attempt to install the drivers and fail, at this point go to your start button, search programs and files and type device manager, when it comes up select the one with an exclamation point and right click it, select update drivers, point it to the driver folder and then your operating system folder, i.e. vista, windows 7. If the attempt to install does not work download http://narod.ru/disk/57204199001.bb08022cc3658b67af84bc83bd330b0c/20120705_e1808_v75_jbl1.zip.html extract the folder.
<li>Download http://www.mediafire.com/download.php?htx4lkktne1jmzg recovery image and place and replace the recovery in the folder above.
<li>Do not have your phone connected to your computer, open sp flashtool downloaded from Bruno martins guide select scatter-loading on the right select the scatter file in the extracted folder, deselect everything but the recovery i.e. only have recovery selected! Click the download button.
<li>Turn off your phone, remove the battery, put the battery back in plug in your phone, it should now attempt to install drivers, again it will fail, start, search programs and files, device manager, right click the one with the exclamation mark, select update, select driver folder, select your windows version, yes on any warnings, now installed.
<li>NOTE: I recommend never plugging in your phone until you hit the download button and it says searching with sp flashtool. It doesn't react if it's plugged in before then.
<li>O.K. So at this point you should have your drivers installed and recovery as well. Almost there.
So next download http://www.sendspace.com/file/oj1fv2 2 gb internal memmory and 500 mb external. Essentially what this zip does is make your phone have 2 gigs of internal space and 500 mb external instead of 500 mb internal and 2 gigs external, super cool.
Don't do anything yet though.
<li>Next download http://www.sendspace.com/file/uj3jqx This is the ultimate rom I spent some time on for our phones, it's android 4.06 while it's not orriginally mine I fixed a lot of issues and made it much, much, better and pre-rooted with buisy box.
<li>Next download http://www.sendspace.com/file/7yfizd That's right GOOGLE NOW fully working, really cool, works perfect you'll love it!
<li>Now that you have them downloaded put them on your SD card. Here is were people kept telling me if your external doesn't work you can just put it on your internal Sd card. DON”T DO IT! If your external doesn't work you put a smaller one in a 2 gig works nicely, I had a 16 gig and it wouldn't read, had an old 2 gigger laying around and read it just fine. Heres why you don't use the internal, your flashing the internal memmory!! It will mess everything up!
<li>That said, files on the sd card put it in your phone.
<li>Press power while holding the up or + volume, release power continue to hold the volume and you'll eventually go into recovery menu.
<li>Use volume to navigate power to select.
<li>Select wipe data/factory reset, confirm.
<li>Select wipe cache partition, confirm
<li>select advanced, select wipe dalvik cache, confirm.
<li>Now select install zip from sd card, choose zip from sd card and select the custom rom file, confirm.
<li>Go back and reboot, let the phone reboot to system, as a side note screen will be moving white, its just the wallpaper. After full boot up let system settle then hold power and select recovery.
<li>Once back in recovery select install zip from sdcard, choose zip from sdcard and select the 2 gig zip, install.
<li>Select choose zip from sd card and select the google now zip and install, now reboot your phone, and love the awesomeness. By the way it's just google in your app dawer or choosable when you select the microphone on your home screen.
FLASHING OTHER ROMS
<li>There are two different types of ROMS you can flash.
<li>Official-These are official builds and releases made for your phone. These will be flashed by using sp flashtool. Now our phones also have unique hadware sometimes different from phone to phone. Chinese are pretty infamous for mixing and matching hardware. That being said you need to have software settings set for your particular hardware. You do this by using a particular software called SP MDT which you can download here: http://www.sendspace.com/file/6kee8d When you download the file run it. Select your scatter file, then select the button with the question marks, select unlock, the first one on the left is for your rear camera, middle is for front and finally right is for your screen setting which most people have trouble with and think they bricked their phone. The only way to truly test this is trial and error, if your screens normal you''ve selected the right screen setting, if your cameras work they are also on the right setting. Now close SP MDT and it auto saves the settings for you and use sp flashtool as normal.
<li>Custom-These are modded and themed developer ROMS, these are installed by flashing from recovery and generally do not effect your screen and camera settings because the do not contain uboot data.
Troubleshooting
<li>Don't flash NVRAM and UBOOT if your phone already works fine with cameras and LCD screen!
<li>My phone will not connect to install drivers- Many methods have been mentioned, but the one that works is-power your phone off, take out the battery wait 5 sec, put battery back in, now plug in your phone to the pc, it should attempt to install drivers and fail, go to start then type in the search box device manager, select it, right click the one with the exclamation mark, choose update. If that doesn't work, run sp flashtool select your scatter file choose what you want to install, select download button, now follow the steps provided above and plug in your phone. Also The cord that you use to pluggin to your computer may be the issue, if it does not transfere files when you plug it in normally then it wont work for the drivers, some of them are charge only I found that out myself when two of mine didn't work.
<li>My sd card can't mount in recovery-Most likely cause SD card is incompatible i.e. too big, use a smaller 2 gig card, do not use internal memmory as others suggest, it can mess things up and I advise against it.
<li>SCREEN PROBLEMS! Psychedelic colors, black, white, gray and others. CAMERA PROBLEMS! No camera, wont focus etc. Etc.... You need two programs spflashtool found here: http://www.sendspace.com/file/bh81se and SP_MDT found here: http://www.sendspace.com/file/6kee8d You also need an official firmware. Open SP_MDT go to the box that says scatter file, point it to your official firmware scatter file, then click the box with all the question marks, press unlock, the first option is your rear camera, the second option is your front facing camera, the last option is your lcd settings which make it look normal (not phsychedelic and wacky). Now these settings vary from phone to phone so you just have to trial and error them, basically if your screen is right, the seting is right, if your camera works the setting is correct. Now you can close the SP_MDT don't worry it saves your settings for you even though you just close it. Go into SP Flash tool Now you can flash the whole ROM but you don't have too, you only need to select UBOOT it will give you a warning it's perfectly fine, thats all you need to flash to fix your settings, and it wont mess up your current ROM.
Official Roms
<li>Flash With SP Flash tool, Do Not Check UBOOT or NVRAM Unless you have already messed up camera and LCD settings in which case you need to follow the troubleshooting section.
Firmware Stock
Latest (05.07.2012) official firmware for N8000 - 20120705_e1808_v75_jbl1l THANKS TO Kyrie1965
http://narod.ru/disk/57204199001.bb08022cc3658b67af84bc83bd330b0c/20120705_e1808_v75_jbl1.zip.html
stock firmware 9 May:
http://115.com/file/dpnafvtw
stock firmware 19 may
new firmware with better wireless signal
http://115.com/file/e7jyi2dv
N8000-root-wifi-20120519.zip
click on green box for download
*20120612_e1808_v75_jbl1
Latest (05.07.2012) official firmware for N8000 -*20120705_e1808_v75_jbl1l http://narod.ru/disk/57204199001.bb08022cc3658b67af84bc83bd330b0c/20120705_e1808_v75_jbl1.zip.html
Custom ROMS
<li>Flashed with recovery, wont mess with display and camera settings already set, wont fix them either.
My Favorite Also There Are UPDATES
http://www.sendspace.com/file/uj3jqx
UPDATED To 2.1 http://www.sendspace.com/file/k5uwoh
More Live Wallpapers http://www.sendspace.com/file/yuelii
</ul>
SCREENSHOTS
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
A 4.03 custom rom
http://www.sendspace.com/file/2pwtc6
Feel Free to add more, as will I. If you like this thread feel free to thank me if you really like it please DONATE thanks.
NICE
Wow, thanks for putting the time into making a comprehensible thread. Cant wait to get some free time to root my n8000. How's the battery life in the ROM and are there any bugs? will report back if i run into any issues.
Hello
what is the point of having two threads for the same device.?
why did you not just post this there in the correct place?
surly it is much better to have one place to go to for all the answers and to ask, the N8000 thread has developed as the device has
you will just be adding to others confusion
good luck.
If you visit any of the other threads Of different phones they actually contain multiple threads which keep things uncluttered, so that people can find what they need that was my goal with this thread. They don't just contain one huge single thread.
Sent from my N8000 using xda app-developers app
thanks for your work!one question: your rom is good with battery? is it ondemand or performance dispatcher?
Incompatible apps
Thanks for the guide I've now got the 4.0.6 Rom on my phone. one problem, the play store says a lot of apps aren't compatible with my phone. I'm assuming this is because its a 4.0.6 Rom is there anyway to make the play store think you have 4.0.4 so it will let you download them or any other way to download these supposedly incompatible apps?
there is no android 4.0.6 this rom is based on android 4.0.3
lewisqpr said:
Thanks for the guide I've now got the 4.0.6 Rom on my phone. one problem, the play store says a lot of apps aren't compatible with my phone. I'm assuming this is because its a 4.0.6 Rom is there anyway to make the play store think you have 4.0.4 so it will let you download them or any other way to download these supposedly incompatible apps?
Click to expand...
Click to collapse
pjrollo2000 said:
there is no android 4.0.6 this rom is based on android 4.0.3
Click to expand...
Click to collapse
Okay I've now tried a 4.0.4 Rom and its still saying loads of apps are not compatible when downloading from google play? These apps worked fine when I was on the stock 4.0.3 Rom.
sendspace.com/file/uj3jqx was 4.0.6 is a moded version of android 4.0.3 the build.prop file has been edited 4.0.6 there is a build.prop file somewhere that lets google play compatible with all apps.
lewisqpr said:
Okay I thought this one here sendspace.com/file/uj3jqx was 4.0.6. Are other people having problems with apps not being compatible with there phones when downloading from google play?
Click to expand...
Click to collapse
---------- Post added at 06:49 PM ---------- Previous post was at 06:29 PM ----------
I have tried all of the moded roms from the Russian and Chinese sites where all these roms come from if the dpi is set to anything over than 240 google play most apps are not compatible check your build.prop file /system there will be something like this ro.sf.lcd_density=190 delete it then try google play again if you want a different dpi you need a moded google play apk
pjrollo2000 said:
sendspace.com/file/uj3jqx was 4.0.6 is a moded version of android 4.0.3 the build.prop file has been edited 4.0.6 there is a build.prop file somewhere that lets google play compatible with all apps.
---------- Post added at 06:49 PM ---------- Previous post was at 06:29 PM ----------
I have tried all of the moded roms from the Russian and Chinese sites where all these roms come from if the dpi is set to anything over than 240 google play most apps are not compatible check your build.prop file /system there will be something like this ro.sf.lcd_density=190 delete it then try google play again if you want a different dpi you need a moded google play apk
Click to expand...
Click to collapse
I changed the lcd density, the model and product name in the build.prop file and now its letting me download all the apps. Thanks for your help.
Those are for jbl1
Can u made it for jbl2 ?
Sent from my GT-N7000 using xda premium
xpresotw said:
Those are for jbl1
Can u made it for jbl2 ?
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
This is really important to note. Newer phones have JBL2, and the JBL1 stuff at worst soft-bricks them and at best takes away auto-focus from the camera (still working on this, but seems permanent for now).
waiting
Actually the rom was created by alexey arsenev, will work on jbl2 but need to flash with jbl2 boot image.. But autofocus will not function..
Sent from my GT-N7000 using xda app-developers app
Can you upload it to someother host
i am unable to download anything
stock firmware 19 may
new firmware with better wireless signal
http://115.com/file/e7jyi2dv
oh no.....
thanks...
i did everything in your post i still have the blurry image and to worsen the problem after reboot my phone language is in russian
google now
I've watched the "noob" video for posting - but not really sure if this is the right place to post. Please don't shout at me
I've watched a few videos about getting "google now" working on ICS - but I have little Android experiece and do not want to break the phone. Has anybody done it successfully on this ? can u point me at a failsafe utube video (or something else) to get this done without my loss of £120GBP ? Thx...
niman1 said:
I've watched the "noob" video for posting - but not really sure if this is the right place to post. Please don't shout at me
I've watched a few videos about getting "google now" working on ICS - but I have little Android experiece and do not want to break the phone. Has anybody done it successfully on this ? can u point me at a failsafe utube video (or something else) to get this done without my loss of £120GBP ? Thx...
Click to expand...
Click to collapse
Yes -- it works! I've done it.
I'm sorry that you're not going to find one step-by-step guide for this phone, but all the info is here.
This is a very hard phone to "break" in a permanent sense, but I'd read as much as you could stand before you began to avoid headaches that others have had before you. Between the two threads here, there are 150 or so pages of info. Especially important things to note: Make sure you have the right phone (not quite as easy it sounds) and make sure you note all the current details of your software before you get under the hood.
In order to use Google Now, you'll first need to root your phone and install a custom recovery (if those don't make sense, use the Google to search for an overview).
For our phone, I'd start with the first page of this thread: http://forum.xda-developers.com/showthread.php?t=1695210
So, the question becomes: Do you have root and a custom recovery?
FWIW, Google Now is interesting but has yet to seem revolutionary to me. Seems like something that will be amazing three or four generations from now.
Hi sir.. thanks for your sharing.. i use this rom from a mont h ago... its running stable.. can you porting paranoid android rom for our phone Star N8000..??
Sent from my Star N8000..
dangk said:
Hi sir.. thanks for your sharing.. i use this rom from a mont h ago... its running stable.. can you porting paranoid android rom for our phone Star N8000..??
Sent from my Star N8000..
Click to expand...
Click to collapse
Me? I'm sorry ... I've never tried porting anything before.
I am currently attempting to port Cyanogenmod as well as Clockworkmod to a device known as the Samsung DoubleTime SGH-I857. It is a very unique end of life handset that I think needs a little hacking attention. So far I have found most of the partitions names and sizes on the device, and I have pulled the boot.img and recovery.img out of a firmware file for it that I found online. I am confident in my skills but I am often running into trouble when it comes to building with Cyanogenmod source. I am currently using the Froyo branch as I believe it might be easier to build with the same version that is currently on the phone. I eventually plan to some how build gingerbread for it but i am trying to build what I can as of right now.
I am making this thread to report progress and hopefully get advice from those who are more experienced than me. Any help or advice is deeply appreciated.
Update*
I finally got my build enviornment figured out, I chose Gingerbread because Froyo didn't like me for some reason...
I used the mkvendor.sh method as recommended on the Cyanogenmod Wikipage for porting. I looked through all of the files and everthing seems to be correct except the recovery.fstab which is saying that the system, cache, data, etc. partitions are in all sorts of diffrent file systems; and are mounted in places called the same name as them. The sdcard partition seems to be correct and I'm assuming that I need to manually put in the data. You can look at the files below and tell me if I'm on the right track. I cannot locate any recovery boot or misc partitions using shell commands. There were however there were loop and bml partitions, but they did not appear in the mount or df command.
Update*
I got sick of getting errors regarding my device not existing and random stuff about an HTC ACE. So I plugged the recovery.img from the firmware package into builder.clockworkmod.com and gave it a go. It built sucessfully but I am afraid of the recovery.fstab not being correct.
Upon inspection of sibiling phones most followed a similar pattern or stl## partitions for cache, data and system. Though they all have boot defined as boot and recovery as recovery; both of which with a BML file system. I also noticed the sibilings said their cache, data and systems were ext4 with a 2nd file system of rfs. This is just confusing to me...
I am unsure if I should flash it. I'm confident that the recovery.fstab's recovery and boot partitions are correct but what will happen if I get one of the partitions wrong.
The CWM recovery builder output is here: http://jenkins.cyanogenmod.com/job/recovery/56329/
A sibiling phone example would be: https://github.com/CyanogenMod/android_device_samsung_fascinate/blob/gingerbread/recovery.fstab
Anything other files I am happy to give out.
How I feel about my progress:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Due to my lack of experience, and fear of hardbricking my new DoubleTime, I will be postponing my developement of the Gingerbread port to the Doubletime. My priority now will be learning as much as possible about the device.
To Do List (In Order)
1. Find correct Odin version for flashing.
2. Create Froyo ROM that will maximize freespace.
3. Create working recovery.
4. Build Gingerbread kernel.
5. Port over Gingerbread.
I've recently been looking comparitivly at custom ROMs and so far I think the best option might be stock AOSP. I have also been looking into ways to flash onto the phone but ODIN 1.85 doesn't seem to work. It can't be my antivirus as far as I know because I've added firewall exceptions to Odin.
To Do List (in order)
1. Find way to flash things to Doubletime
2. Make Froyo based AOSP
3. Build Gingerbread kernel.
4. Port Gingerbread
(Porting CWM should probably be in there somewhere)
Progress?
legojr said:
i've recently been looking comparitivly at custom roms and so far i think the best option might be stock aosp. I have also been looking into ways to flash onto the phone but odin 1.85 doesn't seem to work. It can't be my antivirus as far as i know because i've added firewall exceptions to odin.
To do list (in order)
1. Find way to flash things to doubletime
2. Make froyo based aosp
3. Build gingerbread kernel.
4. Port gingerbread
(porting cwm should probably be in there somewhere)
Click to expand...
Click to collapse
did you give up on this?
Teknodad1974 said:
did you give up on this?
Click to expand...
Click to collapse
No I haven't but my schedule has not allowed for a lot of time to be dedicated to this. I also am very new to this and I'm taking a lot of baby steps.
The number one problem right now is there doesn't seem to be any way of flashing CWM to the phone as all of the Odin versions/cables/computers I've tried have failed.
Well no better way to learn than hands on and on your own... Good luck! I have one of these worthless phones laying around to give to my youngest girl 6. It's just sucks it's stick on Froyo 2.2
Sent from my SGH-I777 using XDA Premium 4 mobile app
I believe I may have a correct recovery.fstab now I'll run this through Clockworkmod Builder now and hopefully get Odin 1.87 to flash it. If at anytime anyone thinks I'm doing something wrong PLEASE TELL ME. I'd rather not have another hardbricked Doubletime.
Honest to goodness I need some help here I'm trying really hard but I can't seem to get anything right... Odin doesn't seem to work, CWM Builder doesn't even identify the name of the phone, and all of the code available for the Doubletime from Samsung makes almost no sense to me. I do enjoy doing this but I've made almost no progress at all.
As of right now the primary effort needs to be on finding a way to flash CWM onto the Doubletime. The issue being if CWM builder is giving out KitKat level recoveries I doubt the Doubletime could handle it. The only way I can see a reliable CWM img getting built is if we use Cyanogenmod 6, which will require proprietary blobs, and those will be a pain to get since extract-files.sh doesn't seem to be available for the Doubletime as far as I know.
I've started manually finding the blobs by finding files that are similar to those found in the device-vendor-blob.mk of some other Samsung Froyo devices. The link to it is here
If I'm going in the right direction someone please tell me...:crying:
Well it finally feels nice to know what your doing! While going file by file through the phones system directory might do it, I can't deny that I may have absolutely no idea what I'm doing. So with that lovely feeling in my heart I will be finding each of the parts inside of the DoubleTime and will looking at other phones that have those same parts and copy the blobs specific for them over to the github page I made. Anything that's on the DoubleTime but not in the blobs that I copied I'll put in a miscellaneous section in the vendor-blobs.mk file. So far here is what I know we'll need part wise, and what I know part wise.
List o' part we might need (totally could be wrong):
Bluetooth: ???
Wi-Fi: ???
Camera: ???
Sensors: ???
Audio: ???
Graphics: Qualcomm Aderno 205
GSM: ???
GPS: ???
Media: ???
DRM: ???
DSP: ???
USB: ???
The chipset is a Qualcomm MSM7230, looking at apps that gather information about the device I've come to the conclusion that the phone is running on an extremely generic Android build and is not even really optimized for the devices hardware. The phone seems to think that it has an ARMv6 processor while in fact it has a v7.
That adds to my other phone binary preference. Add anything you thing might be helpful! I'm a total noob at this and I need all the help I can get. :|
Legojr said:
Well it finally feels nice to know what your doing! While going file by file through the phones system directory might do it, I can't deny that I may have absolutely no idea what I'm doing. So with that lovely feeling in my heart I will be finding each of the parts inside of the DoubleTime and will looking at other phones that have those same parts and copy the blobs specific for them over to the github page I made. Anything that's on the DoubleTime but not in the blobs that I copied I'll put in a miscellaneous section in the vendor-blobs.mk file. So far here is what I know we'll need part wise, and what I know part wise.
List o' part we might need (totally could be wrong):
Bluetooth: ???
Wi-Fi: ???
Camera: ???
Sensors: ???
Audio: ???
Graphics: Qualcomm Aderno 205
GSM: ???
GPS: ???
Media: ???
DRM: ???
DSP: ???
USB: ???
The chipset is a Qualcomm MSM7230, looking at apps that gather information about the device I've come to the conclusion that the phone is running on an extremely generic Android build and is not even really optimized for the devices hardware. The phone seems to think that it has an ARMv6 processor while in fact it has a v7.
That adds to my other phone binary preference. Add anything you thing might be helpful! I'm a total noob at this and I need all the help I can get. :|
Click to expand...
Click to collapse
I have this phone and would like a little of hacking on it. Have you gotten anything?
migui0401 said:
I have this phone and would like a little of hacking on it. Have you gotten anything?
Click to expand...
Click to collapse
So far all I got is a plan. Although I do have a recovery.img of CWM 6 from the Clockworkmod builder but the issue is it might not even work. Also as of right now I haven't found a way to flash anything to the DoubleTime. Although I have a theory that Odin on Windows XP might work. If you know anyways of flashing that are universal or something I'm all ears.
Legojr said:
So far all I got is a plan. Although I do have a recovery.img of CWM 6 from the Clockworkmod builder but the issue is it might not even work. Also as of right now I haven't found a way to flash anything to the DoubleTime. Although I have a theory that Odin on Windows XP might work. If you know anyways of flashing that are universal or something I'm all ears.
Click to expand...
Click to collapse
Can you create a flashable zip file for flashing via stock recovery, i mean a recovery which just opens flashing it everytime you need it, there some like this.
migui0401 said:
Can you create a flashable zip file for flashing via stock recovery, i mean a recovery which just opens flashing it everytime you need it, there some like this.
Click to expand...
Click to collapse
I've heard about that but I'm not sure if a stock recovery can flash a recovery on itself.
Besides a recovery.img that we know will work is needed for that and well... we don't really have one.
Being a noob I'm not sure how much is testable before flashing but I believe that those binary files are going to be needed. Do we just need the vendor-blobs.mk file to copy everything in system/lib, system/bin and system/etc directories?
Legojr said:
I've heard about that but I'm not sure if a stock recovery can flash a recovery on itself.
Besides a recovery.img that we know will work is needed for that and well... we don't really have one.
Being a noob I'm not sure how much is testable before flashing but I believe that those binary files are going to be needed. Do we just need the vendor-blobs.mk file to copy everything in system/lib, system/bin and system/etc directories?
Click to expand...
Click to collapse
Search for guide for creating the flashable zip, this is the better way to get a fast recovery working in any device, about the vendor-blobs.mk, i have not tried to create a recovery, so i can't help.
migui0401 said:
Search for guide for creating the flashable zip, this is the better way to get a fast recovery working in any device, about the vendor-blobs.mk, i have not tried to create a recovery, so i can't help.
Click to expand...
Click to collapse
How much experience at Android hacking do you have?
Legojr said:
How much experience at Android hacking do you have?
Click to expand...
Click to collapse
I'm not a great here just like the contributors or reconigzed, but I can do something, do you need help?
migui0401 said:
I'm not a great here just like the contributors or reconigzed, but I can do something, do you need help?
Click to expand...
Click to collapse
Well I'm no expert but we're eventually going to need to find a way to build Gingerbread for the DoubleTime. If you know the basics of a Cyanogenmod build enviornment that would be cool! If you could maybe look for any source code for the DoubleTime that would also be the best! Those are the only things I can think of. I don't really know much...
Legojr said:
Well I'm no expert but we're eventually going to need to find a way to build Gingerbread for the DoubleTime. If you know the basics of a Cyanogenmod build enviornment that would be cool! If you could maybe look for any source code for the DoubleTime that would also be the best! Those are the only things I can think of. I don't really know much...
Click to expand...
Click to collapse
I have the stock firmware extracted, the boot.img and recovery.img.
ITT - Discussion of the Infocus M512 root methods and MIUI ROM.
M512 Running MIUI v5: (Screenshot by me)
View attachment 2977929
Where I bought mine: http://www.pandawill.com/foxconn-in...0-50-inch-gorilla-glass-nfc-white-p91662.html
Youtube video [first impression]: https://www.youtube.com/watch?v=01XhuJwJzcE
Link to Stock Rom root: http://www.needrom.com/download/infocus-m512
And a guide I wrote on how to Root it: http://forum.xda-developers.com/showthread.php?t=2893455
Link to MIUI: http://4pda.ru/forum/index.php?showtopic=597293 (google translate it and go to the Firmware tab in the OP)
Everything is working on MIUI with no crashes or bugs.
To enable Root once MIUI is flashed go to the Security app (not security in settings) -> Permission -> Root Permission
To enable 4G/LTE type *#*#4636#*#* in dialer/phone then go to Phone Information -> Set Preferred network type -> Change from WCDMA to LTE/GSM/CDMA auto (PRL) *Note* You may have to do this after every reboot
*EDIT*
flippy.nl said:
all right, condensed post for a one stop shop to upgrade the M512 to the latest firmware (2260) AND root with gapps and the files are based on a actual fast server (mine)
first get this: original 2260 rom
then this: root
and finally: gapps
to get this on the phone:
install the rom first like usual: personal favourite is putting zip on sd card and use the "adb reboot recovery" command and install the zip from recovery.
rebbot and do basic setup (for wifi) as needed.
to get root: connect usb! press volume + and - AND power and HOLD, after 10 sec the phone will turn off/reboot twice, the second time the blue led will turn off, release the power button but keep holding both volume keys. you will get black screen and simple info like imei number.
now use the root.bat to actually root the phone. it will take about 20 seconds. check the screen for any errors, any error will basically fail the root.
install gapps the same way as root.
congrats, you now have a M512 that has a actual working gps, proper data connections and gapps. if you want to check the glonass sat's: watch for sat numbers above 64, those are glonass.
Click to expand...
Click to collapse
Bump
I´m interested in that device too... Anyone here has it?
wow a month old reply- better now then never.
great device- no root \ recovery\ custom rom support though.
but as a new to android this device is excellent.
quick, great build quality, support from foxconn,
camera is a crappy but better then nothing.
thats it.
bought it at $140 price.
voltrex93 said:
wow a month old reply- better now then never.
great device- no root \ recovery\ custom rom support though.
but as a new to android this device is excellent.
quick, great build quality, support from foxconn,
camera is a crappy but better then nothing.
thats it.
bought it at $140 price.
Click to expand...
Click to collapse
I bought it and rooted mine. Used this method: http://forum.xda-developers.com/gen...discussion-t2893455/post55787107#post55787107 Great phone
Thanks,
I just falshed the 15CN_1_03A , is the 1080_0_15CN much better rom?
or it doesnt really matter?
the 15CN_1_03A is still a 4.4.2 kitkat.
also how did you managed with the low internal memory ? i have only 500mb free and i had to install link2sd to free some space.
still pretty sad picture.. and i cant find any way around it.
voltrex93 said:
Thanks,
I just falshed the 15CN_1_03A , is the 1080_0_15CN much better rom?
or it doesnt really matter?
the 15CN_1_03A is still a 4.4.2 kitkat.
also how did you managed with the low internal memory ? i have only 500mb free and i had to install link2sd to free some space.
still pretty sad picture.. and i cant find any way around it.
Click to expand...
Click to collapse
I had no GPS signal until I flashed 1080_0_15CN, and if you flash the root ROM without it, you'll have no GPS signal.
The internal memory is my biggest gripe, I don't know what to do. I think I'll have to use link2sd too, I can't install apps now. It comes up insufficient space ??
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my LG-D802
try http://forum.xda-developers.com/showthread.php?t=2142844
this should give you some room . if you haven't already.
voltrex93 said:
try http://forum.xda-developers.com/showthread.php?t=2142844
this should give you some room . if you haven't already.
Click to expand...
Click to collapse
I'll have to check it out!
BTW did you end up rooting it?
Sent from my LG-D802
I did . now i can get it running as i like.
also delete all the chinese crap - foxconn apps- this should release you more 100-200mb.
i think there is some issue with the system because 4gb is enough for android .
some thing is wrong.
---------------------------------------------
okay i did some research and yes- 4gb should be enough for android-
i'll have to search more for the problem and solution - will get back to you when i'll get some results.
---------------------------------------------
Okay, the phone is still new to find out how to fix it.
i am following a russian forum which will release a custom rom soon ( i believe ) .
also i did found that after you do a link2sd, the memory filled up with cache files., use auto cache cleaner .
this should hold the phone for some time..
voltrex93 said:
I did . now i can get it running as i like.
also delete all the chinese crap - foxconn apps- this should release you more 100-200mb.
i think there is some issue with the system because 4gb is enough for android .
some thing is wrong.
---------------------------------------------
okay i did some research and yes- 4gb should be enough for android-
i'll have to search more for the problem and solution - will get back to you when i'll get some results.
---------------------------------------------
Okay, the phone is still new to find out how to fix it.
i am following a russian forum which will release a custom rom soon ( i believe ) .
also i did found that after you do a link2sd, the memory filled up with cache files., use auto cache cleaner .
this should hold the phone for some time..
Click to expand...
Click to collapse
Ooo can you please link me to this russian forum? Do u speak russian or are you using google translate?
How do you delete the chinese bloatware btw? All i can do is disable them
EDIT:
Link2Sd helped me uninstall the chinese apps but i cant get this SD link thing to work
GalaxyWhy said:
Ooo can you please link me to this russian forum? Do u speak russian or are you using google translate?
How do you delete the chinese bloatware btw? All i can do is disable them
EDIT:
Link2Sd helped me uninstall the chinese apps but i cant get this SD link thing to work
Click to expand...
Click to collapse
4pda.ru/forum/index.php?showtopic=597293&st=160
I do know a little russian, cant write though..
the rom creator said that there is a lot of work to do and he is on vacation. so expect it next week .
-------------------------------------------
Use ext4 when formatting the sd card, although make one FAT32 partition larger then the ext4.
as well Kitkat 4.4.2 use a lot of internal storage . i wonder if there is a way to reverse to android 4.2.2
but i"ll wait for the new rom first.
voltrex93 said:
4pda.ru/forum/index.php?showtopic=597293&st=160
I do know a little russian, cant write though..
the rom creator said that there is a lot of work to do and he is on vacation. so expect it next week .
-------------------------------------------
Use ext4 when formatting the sd card, although make one FAT32 partition larger then the ext4.
as well Kitkat 4.4.2 use a lot of internal storage . i wonder if there is a way to reverse to android 4.2.2
but i"ll wait for the new rom first.
Click to expand...
Click to collapse
Yeah I'd be very happy with a stock android Rom or even Cyanogen Mod or something.
Its weird though, its like my phone is missing 1gb or storage? Because that only adds up to 3gb? ?
Sent from my LG-D802
GalaxyWhy said:
Yeah I'd be very happy with a stock android Rom or even Cyanogen Mod or something.
Its weird though, its like my phone is missing 1gb or storage? Because that only adds up to 3gb? ?
Sent from my LG-D802
Click to expand...
Click to collapse
the storage is just enough to install all what i need. but barely .
Also did you managed to use Link2SD?
i will try to find a way.
Odin from samsung do extract infocus rom - i should start learning how to create roms i guess.
voltrex93 said:
the storage is just enough to install all what i need. but barely .
Also did you managed to use Link2SD?
i will try to find a way.
Odin from samsung do extract infocus rom - i should start learning how to create roms i guess.
Click to expand...
Click to collapse
Well from what I can tell, porting a ROM from a device with the same Screen size, resolution and processor is the best way to go. And i believe the only device that fits that is the 2014 Moto G
GalaxyWhy said:
Well from what I can tell, porting a ROM from a device with the same Screen size, resolution and processor is the best way to go. And i believe the only device that fits that is the 2014 Moto G
Click to expand...
Click to collapse
Are you suggesting we should try and port that rom to infocus?
---
so much information need to be learned - i have now few free days and i'll try to do it-
if you wish you may join.
i know very little programming but i never messed with android\linux that much .
voltrex93 said:
Are you suggesting we should try and port that rom to infocus?
Click to expand...
Click to collapse
Haha I was thinking about it but I dont know anything about porting a rom :/
I cant even get this Link2Sd app to work...
It just installs apps onto the internal storage and in Link2Sd it says the app is linked to the Sd but its not on the Sd and when I go to move it to Sd I get an error :/
GalaxyWhy said:
Haha I was thinking about it but I dont know anything about porting a rom :/
I cant even get this Link2Sd app to work...
It just installs apps onto the internal storage and in Link2Sd it says the app is linked to the Sd but its not on the Sd and when I go to move it to Sd I get an error :/
Click to expand...
Click to collapse
I know nothing as well - and thats why we shall learn.
also you need to LINK it and not MOVE it .
if you followed the guide you should highlight all and then link it to sd card..
voltrex93 said:
I know nothing as well - and thats why we shall learn.
also you need to LINK it and not MOVE it .
if you followed the guide you should highlight all and then link it to sd card..
Click to expand...
Click to collapse
Haha yeah well I do find this stuff interesting
I thought I followed it correctly... I'm tired. So do I filter to 'On internal' then select all, then link to SD?
Sent from my LG-D802
Also wish I could somehow replace the menu key with a recents key ?
Sent from my LG-D802
AOSP 5.0.2 Barebones for D2303
Hi all.
This is my first run of compiling a barebones AOSP 5.0.2 for our D2303's. I got sick of all the failed ports and wanted to make my own from scratch. Here you have my first launch. You can not get as barebones as this. This ROM was made using the guides on Sony Developer website and should be the same result if anybody else follows the same steps.
I have made ZERO modifications to this ROM. I have changed no code, made no patches or even themed it with a custom name. This ROM is as-is if you built it following the same guides on Sony's site. I just saved you the time.
**This ROM works!**
Data / Calls / SMS / NFC / Bluetooth / GPS/GloNAS / Wifi all work!
Camera does not. It might, but I broke mine and doesn't even work after stock restore!
No lag!
Clean, basic, no-frills, xPosed ready!
Unlock your bootloader!
Be running either a modem from a 4.4.2 ROM or a 4.3 ROM!
This ROM is provided as-is. The sources are freely availble following Sony's guides. You use it purely at you own risk!
Let's clear some confusion with this device, which I am shocked top developers have missed!
* You **have* to be running either 4.3 or 4.4.2 MODEM! If you are running a 4.4.4 ROM, use Flashtool to drop back to 4.4.2 or 4.3 first
* You will not be able to boot ANY 5.x ROM with a 4.4.4 modem, it **HAS** to be 4.4.2 or 4.3 MODEM!
There are guides on how to revert back on this forum and I will not detail that here. But in essence, it is only the modem you need to revert back.
This ROM I would say is usable.
* Camera doesn't work on mine, but I broke it to the point it wont work in stock ROM
* Calls / SMS / Data / Wifi / GPS / NFC / Bluetooth all appear to work as they should
* Sensors appear to all be working as they should (at least compass and light)
* No lag or FCs
This is a totally unmodified ROM using the AOSP & Sony sources provided in Sony guides. I did not develop or make any of the code or scripts. I simply compiled it, flashed it and now using it. All credit to the software that made this ROM goes to all those involved in making, patching and taking the time to make this work.
I do not want any donations. If you wish to donate, donate to FXP/CM12/Omni/PAC/TWRP and the persons that created what I have simply bundled here.
Download via magnet/bittorrent only for now. For trackers, please use OBT trackers. Issue with previous download! I somehow crossed an .img from another project as the boot.img for this. I have recitified this issue and the correct boot.img has been added. Apologies for this & thankyou to all whom spotted it.
Magnet Link
magnet:?xt=urn:btih:44d710f71b92adb9e64475994b5ab905d665af7d&dn=AOSP-5.0.2-D2303.tgz&tr=udp%3A%2F%2Fopen.demonii.com%3A1337
Mega Link
https://mega.co.nz/#!HZUUCCJS!AgjmKr4Nx4NMWPKxVXIGfp72m9JyMMlsF0pvzuGBrg8
Sorry for the bad link effort, since I am new to contributions I'm stuck until I make the relevant posts.
I have no idea if this will work on any of the variants of this device. You are welcome to try, but don't blame me if you break it. This ROM comes as is, is provided under the same licenses as AOSP and Sony Development.
Tricks & Tips:
* Download the .zip for Omni ROM 4.4.4 for our D2303's. Extract the boot.img and keep it safe. This boot.img holds a reliable TWRP which we can use to ''fastboot boot'' instead of flash and even make a reliable backup of a stock ROM. When you put device into fastboot/bootloader (hold power up when plug in data ready cable), execute ''fastboot boot boot.img'' which will boot that kernel w/o modifiying anything. Now keep hitting volume down when you see Sony logo. TWRP should load!
* Use this for all your backing up, flashing zips, ROMs etc. Do NOT flash it. Just fastboot boot it instead. This can even be used AFTER we install Lollipop for the same reasons.
* Flashing this ROM requires you to use the above TWRP to wipe all partitions, System, Data, Cache etc. It's best to start afresh (I actually wiped everything except since I wanted a totally clean slate, wiping external storage isn't necessary but wiping internal is recommended.)
* Extract the tarball with the .img files
* Put the device into fastboot mode again!
* execute the following commands:
* fastboot flash boot boot.img
* fastboot flash system system.img
* fastboot flash userdata userdata.img
Make sure all processes complete successfully!
Unplug cable, wait a second or two and power up your device! (I prefer this to fastboot reboot as the data cable can hang the device in a weird, red led stays on mode that has bootlooped me a few times).
Give it a while to boot. Whalla, Lollipop!
If you want gapps, using the fastboot boot method above with our Omni 4.4.4 boot.img and TWRP.. Download CM's gapps for Lollipop and flash/install it. This does not lag the device. However, you will get a black screen for a while after first boot of installing any system/ZIP flashable (it wont show updating apps, just blank screen). BE PATIENT! The same applies if you do anything that triggers that "Updating App X of X.." Android is updating effort.
xPosed requires you to follow the instructions for flashing the ZIP then installing APK. Use the same method above for installing the ZIP.
To get root, just download the latest SuperSU-2.x.zip and flash the same way as above.
**Issues**
* With a 4.3 Modem, the Bluetooth is slow coming to life. Take about 5 mins when turned on from off. 4.4.2 modem doesn't seem to have this issue
* Location services will forget a change to Accurate on a 4.3 Modem. On 4.4.2 Modem doesn't seem to do this.
* My loudspeaker during calls is tempremental, sometimes it works sometimes it doesn't.
* Some OTG devices work, some dont. I had one or two pendrives that did, some that didn't & a 3G modem (with PPP widget's help) that did & another that didn't!
* Screencasting initially didn't work. Enabling Developer Mode and disable HDCP checks seemed to allow some functionality for me.
* Data icon always said 3G for me, even when on HSPA(+) - I use OSM which showed varying network types. GPRS/EDGE shows as 2G. I do not know for 4G as my carrier isn't 4G enabled yet.
* No hardware accelleration (using VLC & MX Player as guides) for video playback, however it can playback a 1080 MKV over wifi no problem.
* Same applies to screen-recording software. I can't seem to get native Lollipop one to work at all, but SCR Free works.
* 3D Performance is a little smoother than in stock ROM (IMPO playing Ingress).
* GravityBox for Lollipop works. However!! On some instances it can cause a softboot on a boot up (when it goes for PIN entry). For me it comes back after they next cycle. Not pinned it down to what in GB doing it though.
* Compass, proximity & light sensors all work. There is some screen flicker once so often when using dynamic brightness.
* No way to force use of 5Ghz or 2.4Ghz wifi (or leave it to select auto) as there is in stock ROM.
* Battery life when using the device as I do is as the same as stock, the device is however faster in general. I can sit it for 29 hours idling, providing not too many calls. The powersaving modes built-in can extend on this but I haven't properly tested.
I only mention these as some people may care to know. If the camera worked, I would actually be totally happy with this ROM minus it's few pitfalls.
MD5's for the paranoid:
2c053445ab096e813afc2a02079aba85 boot.img
af636c1558e8d6651f211dbd2042443f system.img
adbb0b8d0b5eee98186a71a00d8352a4 userdata.img
Good job, please, compile an AOSP 4.4.4
Sent from my D2303 using XDA Free mobile app
What if I told you I did the same as you and it is EXACTLY the same build you can find on FXP's blog (but files are not straight uploaded, so build can be a little bit outdated). Developers around here are working on sources, and changes are on Xperia Developers Github.
As you can see there are things jerpelea (FXP) has pushed.
https://github.com/sonyxperiadev/device-sony-eagle
Only untouched sources are for Nexus, all other devices need to be patched, and sometimes rewritten from scratch (for example camera wrapper).
If I install this rom, and when I back to stock rom, i won't be able to use camera?
Is that right?
Um ok but why there is no seeding?;/ and why dont u give an alternative link?? haw we supposed to try this rom mate?
who can confirm if camera works or not ?
Update
I will work on a 4.4.4 AOSP eventually. Thanks for the tip, I'd also be curious on this.
I do not doubt that developers that are working on Omni/PAC/CM/FXP have submitted code, that's probably why the barebones is working sweet. I did try FXP but ran into different issues on different versions (all already documented). I built this on a whim as I just got fed up.
With the camera, that is exactly how I killed mine, and I also lost the original backup I made with Flashtool/Companion as well as from TWRP. So I have no hope. If you keep/make a backup upon successful bootloader unlock (companion/flashtool), you should be OK if you do a stock revert that is documented on this forum.
For the download link, sorry about this. I used transmission and it went into meltdown last night from another seed. I believe mega is a method people use here, is there any other suggestions. I will do this when I get back home and check back here.
** I am uploading this to Mega now, I will add the download link to the OP. **
Thank you for uploading this rom Dutch.
I ll test this rom, correct it where i can and send you pm as soon as possible with some fixes plus solution about your camera
cross your fingers to not break mine lol
Best regards
Vampirian
Thanks
If you do make some patches, can you please put them as flashable ZIPs? I really don't want to go and start tampering with a somewhat stable base. I bless whoever made that boot.img for the Omni 4.4.4 - I would like to try and get that working here, but again tampering.. Just means needing a PC or tablet to make mods to your phone each time.
I may have a bash at a custom kernel with a recovery for this, but I'm not rushing into that idea just yet.
** Update **
I got curious about the FOTA partition I saw using Flashtool and see there are already ports of custom recoveries (with custom boot kernels with elf extract support). I am overly curious about this now as I would love to have this TWRP from Omni's boot.img for my internal recovery. I have already made a custom kernel for my device and it seems to not effect anything (not changed a thing mind). I may now start to tinker!!
Has anybody tested this rom?
---------- Post added at 03:37 PM ---------- Previous post was at 02:53 PM ----------
I have the problem with boot.img
It says, failed: this is not a boot image
Bug list same as the omni one
Can You explain that boot.img is over 400MB Large!!!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Which download did you use? That is so not right!! boot. img should only be about 6/7 mb. are the md5s matching on system and userdata? i will look into this asap
Sent from my Xperia M2 (AOSP) using XDA Free mobile app
The mega download is shot. It has become corrupted and I will remove the link from the OP. DO NOT USE IT!
The magnet link is still fine and extracts properly.. Just be patient as there are only 3 peers at present.
I am still using this ROM and there are some issues.
I failed to get Wifi tethering to actually route. It would run, give dhcp and even resolve DNS, but it is as-if the the nat forwarding rule has been missed and everything blackholes.
Camera is a total no go for me, I fooked mine in other ways though.
For how I use my phone (calls/sms/Ingress/HO/G+/Whatsapp/Maps/Wifi location mapping (OSM/Mozilla stumbler/Wigle) / Skymaps) it does just fine. Battery life isnt impressive vs. stock overall (doing same as above). xPosed allows tweaking, but this is where instability occurs.
GB works quite well, but avoid things that dont have direct L support (xPrivacy/Lightningwall etc.).
What I want to do is submit my phone into submission and try to get my camera working in a stock again, then give this another bash. It is a usable ROM if you just want a clean fast phone with no thrills (or camera).
Sent from my Xperia M2 (AOSP) using XDA Free mobile app
Magnet link not working
The magnet link you posted doesn't seem to work for me. I get "unable to parse magnet URI!" error
There is a space in the magnet part of the URI when you C&P. The forum did this. I should be able to post proper links soon.
Sent from my Xperia M2 (AOSP) using XDA Free mobile app
Nice for giving so much info on AOSP experiences and "prerequisites" (like 4.4.2).
I'm using a AOSP 5.1 build I made myself, and have to say the only issue with the latest build/kernel is battery drain (and camera, but "they" are working on it).
I Hope nobody will call you a troll because you share your builds and experiences with everybody
I got a massive lag when using browser or while using a few apps at once, also installing apps and turning on bluetooth take alot more time.
The things I do like is that it is pretty stable....
Thanks to all that have and are testing.
The tether issue was my tablets fault and does actually work. As does BT tethering.
All of the sensors work (i went out of my way to try each one (magnet sensors are always fun)).
The slow Bluetooth I found only happens when using a 4.3 modem. I dont get it now using a 4.4.2 modem.
There is no call record ability in this ROM. CM11/12 have enabled this feature, I believe its a small. xml patch, can anyone confirm please?
I do experience slowness with lots of open apps, i also notice if you have a lot in frequents its a pain to clear all (fixed with gravitybox mind). They also seem to come back even after a reboot. I do find myself regularly clearing the frequents which does sort it.
And thanks for the tips. I find trolls arent entirely too common here. Ive been reading from XDA for years and my sole idea was to demonstrate that its is doable and quite easy. I am still using this ROM everyday and Im quite happy with it. I do still prefer Kitkat though
I do want to play with 5.1.x (and nicer the camera works) - but i went 5.0.2 simply because of xposed support. Nothing else
There is a battery drain which I noticed "out-of-the-box" so to speak. This happens when there are issues with "qdoverlay" which i noticed sometimes occurs on bootup, then will savage your cpu. I spotted this in logcat and didnt find a direct fix (other than sleep the screen when the phone starts lagging, wait a second or two then wake it back up. Location type also counts, oddly high precision seems to give me more life. However, there is an "Over-Counted" cropping up in battery stats, which I cant pin is for what, as its usually a high figure at the bottom.
Can anyone confirm a working camera on this ROM? Opencamera or Googles should work if one doesnt show up.
Thanks again everyone
Sent from my Xperia M2 (AOSP) using XDA Free mobile app
Dutch Burdock said:
Thanks to all that have and are testing.
The tether issue was my tablets fault and does actually work. As does BT tethering.
All of the sensors work (i went out of my way to try each one (magnet sensors are always fun)).
The slow Bluetooth I found only happens when using a 4.3 modem. I dont get it now using a 4.4.2 modem.
There is no call record ability in this ROM. CM11/12 have enabled this feature, I believe its a small. xml patch, can anyone confirm please?
I do experience slowness with lots of open apps, i also notice if you have a lot in frequents its a pain to clear all (fixed with gravitybox mind). They also seem to come back even after a reboot. I do find myself regularly clearing the frequents which does sort it.
And thanks for the tips. I find trolls arent entirely too common here. Ive been reading from XDA for years and my sole idea was to demonstrate that its is doable and quite easy. I am still using this ROM everyday and Im quite happy with it. I do still prefer Kitkat though
I do want to play with 5.1.x (and nicer the camera works) - but i went 5.0.2 simply because of xposed support. Nothing else
There is a battery drain which I noticed "out-of-the-box" so to speak. This happens when there are issues with "qdoverlay" which i noticed sometimes occurs on bootup, then will savage your cpu. I spotted this in logcat and didnt find a direct fix (other than sleep the screen when the phone starts lagging, wait a second or two then wake it back up. Location type also counts, oddly high precision seems to give me more life. However, there is an "Over-Counted" cropping up in battery stats, which I cant pin is for what, as its usually a high figure at the bottom.
Can anyone confirm a working camera on this ROM? Opencamera or Googles should work if one doesnt show up.
Thanks again everyone
Sent from my Xperia M2 (AOSP) using XDA Free mobile app
Click to expand...
Click to collapse
Camera is not working
Dang. Thank you.
Sent from my Xperia M2 (AOSP) using XDA Free mobile app
Unfortunately the hoster where my build server is located raised the fees and i had no way to download a backup of my data... As i can't afford it now i had to delete everything. With a heavy heart I have to discontinue this great ROM for a great phone..
- first of all, thanks to @tdm for his tremendous effort to have us all enjoy LineageOS in the first place, without his contribution this thread would never exist. Also thanks for tdm's Lineage 14.1 where I took this post's layout from -
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Gentlemen,
The time has come to share what's due to be shared.
Supported devices
* US model running 7.1.1 b14 firmware
* EU model running 7.1.1 b12 firmware
Pre-requisites
Make sure to have at least this TWRP version installed
Patience as first start takes a while
First time install Instructions
Use these instructions when coming from any other ROM (stock, AOKP, LineageOS 15.1, etc.)
Download ROM.
Download GAPPS if desired.
Boot into recovery.
Backup your current data.
Format/Wipe 'Dalvik/ART Cache', 'System', 'Data' and 'Cache'
Flash ROM.
Flash GAPPS if desired.
Reboot.
Upgrade instructions
Use these instructions when upgrading from a previous Lineage 16.0 build.
Download ROM.
Boot into recovery.
Backup your current data.
Flash ROM.
Reboot.
Flashing instructions
There are two main ways to flash files onto your phone: local and sideload. Most people are only familiar with local, but sideload is much quicker and easier if you are at a PC.
Sideload
Download the ZIP file(s) to your PC. In TWRP, select advanced and then sideload. Swipe the slider to begin, then on your PC run "adb sideload <filename>".
Local
Download and/or copy the ZIP file(s) to your phone. Note whether they are on internal storage (the default) or the sdcard. In TWRP, select install, find your file, and select it.
Status
This is currently stable quality
Known issues
Very minor graphical glitches
sometimes videos don't play, you have to remove the relevant all from your recent app list and restart (e.g. WhatsApp)
AKM DAC is not supported
Selinux permissive
To Do list
Implement Camera2 API Thanks for customizing libraries and not sharing any code or insight ZTE
Get DSP to kick in for high quality audio again
Download
Google Drive
* works well with open gapps
Sources
Device tree
Kernel
Vendor
Note: please refrain from requesting other Android distributions from me, like AOKP, AOSP, etc - this is most likely not going to happen from my end. As I provided all my sources you can fork the stuff yourself and try to build
Special thanks
@R3bornD4rth for having provided me an axon 7 mini for my testing/debugging, which is heavily in use and doing great so far
@tdm for his original work on this
@armandop_ for his ZMAX Pro Repo and help getting LiveDisplay to work (flawlessly, thanks mate)
intervigilium aka Ethan Chen for his work on HTC One A9 (hiae) (which shares the same chipset as our phones)
Thanks for this rom, there's a way to make work the camera API 2 (in the future)?
jose_777.mx said:
Thanks for this rom, there's a way to make work the camera API 2 (in the future)?
Click to expand...
Click to collapse
Good question, no clue if I will be making it to work somehow I can try to get some pointers if there are just some drivers to be altered or whatever is needed to have this done
I installed magisc 19.1, and dolby for better sound.Now it is my dayly driver,
Thanks Man!
bius88 said:
I installed magisc 19.1, and dolby for better sound.Now it is my dayly driver,
Thanks Man!
Click to expand...
Click to collapse
Cool!
Would be better if GPS and Cam would work though I am working on GPS right now, will soon test my latest build, so fingers crossed
Working well with open gapps 9 micro.
Play store works
Pixel launcher fc.
Camera works. The app doesn't. Download any other camera and you're good.
Looking great so far
Thanks
Holyoblation said:
Working well with open gapps 9 micro.
Play store works
Pixel launcher fc.
Camera works. The app doesn't. Download any other camera and you're good.
Looking great so far
Thanks
Click to expand...
Click to collapse
What? The camera really works? Then I shall replace the camera app with another one maybe ?
Works great with opengapps pico too i am using this for a day and there is not a big issue i will share if any unexpected issue happens. Thx for your effort
EDIT: I think there is still a problem with camera. i tried it with 2 applications and one game.
I have problem with instagram videos i cant play them.
Cant open flashlight from quick settings.
koktey14 said:
Works great with opengapps pico too i am using this for a day and there is not a big issue i will share if any unexpected issue happens. Thx for your effort
EDIT: I think there is still a problem with camera. i tried it with 2 applications and one game.
I have problem with instagram videos i cant play them.
Cant open flashlight from quick settings.
Click to expand...
Click to collapse
I see 2 issues here to be fixed. first with the video playing will be added to my known bugs post, the flashlight thing is related to the camera not working (pretty sure at least)
Small update: unfortunately I can't find a reason why GPS is not working on LOS16, but worked in LOS15.1, even just taking the files from 15.1 and placing them in 16 didn't help. The error messages in the log are not disclosing enough information what exactly the issue could be, just getting loads of invalid handle errors. Comparing with other msm8952 chipsets I don't really see any differences, so I am clueless now
TheSSJ said:
Small update: unfortunately I can't find a reason why GPS is not working on LOS16, but worked in LOS15.1, even just taking the files from 15.1 and placing them in 16 didn't help. The error messages in the log are not disclosing enough information what exactly the issue could be, just getting loads of invalid handle errors. Comparing with other msm8952 chipsets I don't really see any differences, so I am clueless now
Click to expand...
Click to collapse
Can there be a chain problem with sim card, graphics or camera maybe
koktey14 said:
Can there be a chain problem with sim card, graphics or camera maybe
Click to expand...
Click to collapse
Well, this really looks like it - I reverted back to the state where I took over from tdm and applied just the modifications to make nfc, wifi, bt, radio to work. Now GPS works, but wifi went back to sometimes fail to start where you have to reboot to make it actually work again.. it seems something I added along the lines fixed the issue with wifi and another one broke GPS
I am trying to fix wifi now somehow to make it behave stable again, then we can enjoy even a fixed GPS phone
Next stop is camera (after I repaired wifi)
TheSSJ said:
Well, this really looks like it - I reverted back to the state where I took over from tdm and applied just the modifications to make nfc, wifi, bt, radio to work. Now GPS works, but wifi went back to sometimes fail to start where you have to reboot to make it actually work again.. it seems something I added along the lines fixed the issue with wifi and another one broke GPS
I am trying to fix wifi now somehow to make it behave stable again, then we can enjoy even a fixed GPS phone
Next stop is camera (after I repaired wifi)
Click to expand...
Click to collapse
Apparently I fixed wifi I rebooted 15 times to be sure and it always turned on, GPS still functioning as well!
I will update the OP and proceed with cam (which is so broken that not even 3rd party apps work at the moment)
EDIT: Notification lights fixed as well
@TheSSJ -Great Work man!
Will try it out as soon as I get a chance
edit - is the TWRP version the same as Oreo or a newer one ?
edit 2 - Are you building an Aokp version ?
Hi, thanks for the hard work. Does the firmware support fast charging?
BAPK said:
Hi, thanks for the hard work. Does the firmware support fast charging?
Click to expand...
Click to collapse
Yes, as this is setup on kernel side the stock settings have been just kept
k500zm;79544339 [user=2388665 said:
@TheSSJ[/user] -Great Work man!
Will try it out as soon as I get a chance
edit - is the TWRP version the same as Oreo or a newer one ?
edit 2 - Are you building an Aokp version ?
Click to expand...
Click to collapse
Twrp is the same with oreo i installed it.
I was thinking about aokp too but didnt want to put pressure on you. you are already busy. @TheSSJ what do you think about this?
Once I fixed all issues with LOS16, compiling aokp should not be too hard, but I can't promise it
Now i installed the new build but i have a problem. First i made an update but i wasnt able to open get through lock screen after that i made a clean install but now it is too laggy always freezing. Its too difficult to use this build.
koktey14 said:
Now i installed the new build but i have a problem. First i made an update but i wasnt able to open get through lock screen after that i made a clean install but now it is too laggy always freezing. Its too difficult to use this build.
Click to expand...
Click to collapse
Strange,i just clean installed and it is working really fast
Can you provide dmesg and logcat please, then I can check