Database Develop

[DEV]Ubuntu-touch for all Xperia2011 devices

Hello,
Developers, I really need help to get the ubuntu-touch port working again!
After the first release of Ubuntu-Touh I tried to port it again to our devices, but I don't get them booting. I only get a black screen. I have updated all sources on github and made the appropriate changes. You can find all relevant sources and information on my new website http://danwin.github.io/ubuntu-touch.html where I have uploaded the non-bootng builds for developers.
I still have the old builds available for those, who want a booting ubuntu-touch, but without any functionality: http://danwin.github.io/ubuntu-touch.html

it is so laggy on mini Dude :/

screenshot please

rod555 said:
screenshot please
Click to expand...
Click to collapse
there is already a video available, but I have made some Photos of my Neo V, sorry for bad quality: http://ubuntuone.com/6keWFpFBG0kEsVF7mBF54D

Can you add the screenshots in the op as pic

slimmer2 said:
Can you add the screenshots in the op as pic
Click to expand...
Click to collapse
I don't think this is really necessary, as I have a video from kakalko4 embedded there, which has a lot better quality than my screenshots. You can download the zip provided above and unzip the pictures inside, if you really want to see them.

can you make a more understandable guide how to install it because i try to follow your guide and my phone boots to kernel logo and for couple of second phone turns off

MarioJerkovic said:
can you make a more understandable guide how to install it because i try to follow your guide and my phone boots to kernel logo and for couple of second phone turns off
Click to expand...
Click to collapse
ok, updated.
You have to created an ext4 partition with CWM of another kernel or Linux and flashed then my kernel to use the ext4 partition on your SD-Card as /data, because ubuntu is to big for the internal storage. Have you really done that step?

DanWin1210 said:
ok, updated.
You have to created an ext4 partition with CWM of another kernel or Linux and flashed then my kernel to use the ext4 partition on your SD-Card as /data, because ubuntu is to big for the internal storage. Have you really done that step?
Click to expand...
Click to collapse
Yep done it and working ubuntu is working it lags a lot :/ but i dont care i am happy that we got Ubuntu on our old devices

I take it this a the same one as we already have? (crappy demo with no gsm)

replicant101 said:
I take it this a the same one as we already have? (crappy demo with no gsm)
Click to expand...
Click to collapse
For now yes, but hopefully officiallysonyrebel can make the kernel patches in one or two days available, so I can rebuild all images to make the daily builds of ubuntu booting, which have a lot of improvements.

Kernel patches related to what? I can help out. And I remember officiallysontrebel saying that he doesnt know much about kernels on the ray thread that was removed.

emwno said:
Kernel patches related to what? I can help out. And I remember officiallysontrebel saying that he doesnt know much about kernels on the ray thread that was removed.
Click to expand...
Click to collapse
The daily images of ubuntu aren't booting and officiallysonyrebel said that this is related to some kernel patches that have to be made, you can PM him and ask if you can help him with patching, so we can make the daily images also booting, which have a lot improvements in stability and usability.

DanWin1210 said:
The daily images of ubuntu aren't booting and officiallysonyrebel said that this is related to some kernel patches that have to be made, you can PM him and ask if you can help him with patching, so we can make the daily images also booting, which have a lot improvements in stability and usability.
Click to expand...
Click to collapse
thats strange.... It cant be kernel related, if you had added the new configs to the source code. It could be with the lastest CM10.1 changes for the 2011 devices. Take a look at http://github.com/cm42semc , here you will find the latest commits. I say this because if there was a problem with the Ubuntu Images, i.e something new needed to be added to get the build to boot, then it wouldn't boot on my n7100 either (as i made the same changes as prescribed on the guide). Either way its just a hunch. Give it a go.

With kernel patches, can performance be addressed?

emwno said:
thats strange.... It cant be kernel related, if you had added the new configs to the source code. It could be with the lastest CM10.1 changes for the 2011 devices. Take a look at http://github.com/cm42semc , here you will find the latest commits. I say this because if there was a problem with the Ubuntu Images, i.e something new needed to be added to get the build to boot, then it wouldn't boot on my n7100 either (as i made the same changes as prescribed on the guide). Either way its just a hunch. Give it a go.
Click to expand...
Click to collapse
I'm already using these sources and the daily images only get a black screen. A lot of other people report the same issue for their devices (not Xperia), too. You can have a lock at my changes on https://github.com/DanWin and maybe you find the mistake I made, if I made any.

replicant101 said:
With kernel patches, can performance be addressed?
Click to expand...
Click to collapse
Maybe, but the daily builds of ubuntu have a lot better performance and stability than the mwc-demo image, which is currently the only booting version.

DanWin1210 said:
I'm already using these sources and the daily images only get a black screen. A lot of other people report the same issue for their devices (not Xperia), too. You can have a lock at my changes on https://github.com/DanWin and maybe you find the mistake I made, if I made any.
Click to expand...
Click to collapse
Yes, others did have a blackscreen, even the n7100 users did. But some, including myself got it to boot.
This is what I did:
1. Wipe system / data / dalvik
2. install device part
3. install ubuntu image
NOTE: You made a new partition on the sdcard where ubuntu was to be installed. I recommend you to WIpe your sdcard, create a new partition and try again. Also try with try flashing with a different recovery / kernel then flashing the ubuntu kenrel in the end. Sometimes recoveries mess up.

Thx for the job but i had some problemes with the ARc S when i flash the Ubuntu systeme it's abortes whith the statu 0 what i have to do ?

d4k-pho3nix said:
Thx for the job but i had some problemes with the ARc S when i flash the Ubuntu systeme it's abortes whith the statu 0 what i have to do ?
Click to expand...
Click to collapse
Normally status 0 means success, can you go in CWM to advanced -> show log and enter the output of this here, maybe I can help you.

[RECOVERY] TWRP Recovery 2.6.3.0 | MoltenMotherBoard

FEEL FREE TO DONATE US FOR ALL WE'RE DOING FOR YOU!
For general discussions, bug reports and FAQ, write HERE!​
Credits:
MoltenMotherBoard team!
Downloads:
TWRP Recovery | Code.Google
Full sources:
MoltenMotherBoard sources: MoltenMotherBoard | Github
CyanogenMod sources: CyanogenMod | Github
Kernel: lge-kernel-p880 | Github
Changelog:
20131126
Fixed partition table
Code updates from TWRP, Google
20131120
First release
Issues:
Do you want to report an issue? Do it here!
In order to do it, create a new issue, choosing correct labels corrisponding to: Device/OS which you're using, ROM/project you're on, kind of issue.
Also, please, be sure you're running the ROM/project in the exact way we've provided it to you (do not create issues if you're using different
kernel, mod, plugins and dependencies we didn't tell to use).
General Questions: MoltenMotherBoard Projects | General Questions and Info
Official Mantainer(s): Mackief, ItachiSama, p4c0

Installation guide:
[Method 1° ~ fastboot]
Code:
$ adb reboot oem-unlock
$ fastboot flash recovery /PATH-TO-THE-IMG-FOLDER-ON-YOUR-COMPUTER/twrp.img
$ fastboot reboot
[Method 2° ~ adb] (put the recovery.img in your sdcard)
Code:
$ adb shell
$ su
# cat /sdcard/twrp.img > /dev/block/mmcblk0p1
# sync
# exit
$ exit
---------- Post added at 09:44 PM ---------- Previous post was at 09:43 PM ----------
I know you already have a 2.6.3.0 TWRP recovery, but it's based on 4.4 OMNI Android source code, and it's still in work-in-progress. This means, I'll keep it up-to-date with mainline sources.
Anyway, it would be appreciated if you report bugs here, so that I can check them!

"I know you already have a 2.6.3.0 TWRP recovery, but it's based on 4.4 OMNI Android source code, and it's still in work-in-progress. This means, I'll keep it up-to-date with mainline sources."
what does it mean ? Is 4.4 OMNI Android source code bad ? What did you use ? Whay is it better for us ?

EB20XY said:
"I know you already have a 2.6.3.0 TWRP recovery, but it's based on 4.4 OMNI Android source code, and it's still in work-in-progress. This means, I'll keep it up-to-date with mainline sources."
what does it mean ? Is 4.4 OMNI Android source code bad ? What did you use ? Whay is it better for us ?
Click to expand...
Click to collapse
It means it this versions supports Android4.4-based roms flashing.
It also means that it will be updated by the team.
Obviously, the team is doing a great work, why shouldn't it have done it?

Error or not? I wanted to make a backup copy of a recovery, and it turned out that there is no choice where to save it! Neither the internal memory card or an external card!

negativman said:
Error or not? I wanted to make a backup copy of a recovery, and it turned out that there is no choice where to save it! Neither the internal memory card or an external card!
Click to expand...
Click to collapse
Don't understand. What are you meaning?

mackief said:
Don't understand. What are you meaning?
Click to expand...
Click to collapse
I go into recovery, make a backup copy. Click "Backup", in the center of a blank window, and there is nowhere to select the item to save a backup (internal or external sdcard).

negativman said:
I go into recovery, make a backup copy. Click "Backup", in the center of a blank window, and there is nowhere to select the item to save a backup (internal or external sdcard).
Click to expand...
Click to collapse
OK. I'll check!

Think it's almost important for you to read this post: http://forum.xda-developers.com/showpost.php?p=47827005&postcount=11

mackief said:
It means it this versions supports Android4.4-based roms flashing.
It also means that it will be updated by the team.
Obviously, the team is doing a great work, why shouldn't it have done it?
Click to expand...
Click to collapse
what is exactly is the difference for kitkat ? Are the partitions different ?

EB20XY said:
what is exactly is the difference for kitkat ? Are the partitions different ?
Click to expand...
Click to collapse
Nope. At recovery-level, the biggest differencies are in the binary commands, then in Edify scripts.
Nothing relevant, but if you wanna flash a KitKat rom, you HAVE to use a 'KitKat' recovery!

mackief said:
Think it's almost important for you to read this post: http://forum.xda-developers.com/showpost.php?p=47827005&postcount=11
Click to expand...
Click to collapse
And where can I download it? Discovered the mistake about which I spoke to you?

negativman said:
And where can I download it? Discovered the mistake about which I spoke to you?
Click to expand...
Click to collapse
It should be a still-working-on broken feature by team.
It's a early recovery port, as the team is still making its own modifies on 4.4 code.
BTW, today I should release newer build

negativman said:
And where can I download it? Discovered the mistake about which I spoke to you?
Click to expand...
Click to collapse
Ok, I was wrong. That's an issue caused by the fact that TWRP doesn't support fstab v2 - the partition table - and, as our device tree is using this version of table, TWRP didn't load our partition and couldn't backup anything.

Just released new build of CWM.
Changelog:
Fixed partition table
Code updates from TWRP, Google
Follow us on Google+, Facebook & Twitter!
Cheers.

I have a few questions. They apply both to this and CWM.
Why have another build of both recoveries? I still understand TWRP, but @laufersteppenwolf has a released touch version of CWM. Why would anyone use a non-touch version?
The above doesn't apply if these builds have something special. If there is any, update the OP with the features list.
If #2 applies, you should share your sources.
Restore commit history as soon as you can here and in other device folder repos. Original creators deserve the credit. Also, rename the branch from cm9, it's misleading. If somebody tried to build CM9 with that branch, they surely couldn't.
What flags do you use for building TWRP? I don't see any in BoardConfig.mk.
What kernel sources do you use? Even if you didn't change anything in kernel source, put a link to the source you used in the OP.

Adam77Root said:
I have a few questions. They apply both to this and CWM.
Why have another build of both recoveries? I still understand TWRP, but @laufersteppenwolf has a released touch version of CWM. Why would anyone use a non-touch version?
The above doesn't apply if these builds have something special. If there is any, update the OP with the features list.
If #2 applies, you should share your sources.
Restore commit history as soon as you can here and in other device folder repos. Original creators deserve the credit. Also, rename the branch from cm9, it's misleading. If somebody tried to build CM9 with that branch, they surely couldn't.
What flags do you use for building TWRP? I don't see any in BoardConfig.mk.
What kernel sources do you use? Even if you didn't change anything in kernel source, put a link to the source you used in the OP.
Click to expand...
Click to collapse
Actually, they're based on 4.4 . No new features, nothing new.
Then, my device tree with CM9 has nothing to do with these recoveries; of course I'll add kernel sources and so on.
---------- Post added at 08:57 PM ---------- Previous post was at 08:46 PM ----------
Just updated OP and sources. Thanks for the report.

@Adam77Root is right, posting 2 equal projects is not only useless, but it could also be counted as spamming the forum (please don't get me wrong, it's the mod in me speaking ATM, not the person )
If you want to, I can give you access to my thread so we both can use it. I guess that'd be a win-win situation for everyone then
So, what do you say?

laufersteppenwolf said:
@Adam77Root is right, posting 2 equal projects is not only useless, but it could also be counted as spamming the forum (please don't get me wrong, it's the mod in me speaking ATM, not the person )
If you want to, I can give you access to my thread so we both can use it. I guess that'd be a win-win situation for everyone then
So, what do you say?
Click to expand...
Click to collapse
Nope, don't worry! If you think it's a problem, don't worry. Close my doubled threads! It's not a problem!

mackief said:
Nope, don't worry! If you think it's a problem, don't worry. Close my doubled threads! It's not a problem!
Click to expand...
Click to collapse
You know, that's exactly the problem/difficulty of being a mod in his own section
I personally do not have a problem with it, but if someone wants to, he can see it as spamming, which could get you in trouble some time.
So I usually try to avoid such situations as soon as possible
So all in all it's your call. I have no problem giving you access to my thread, so we both can keep on deving on it, but it would be less work for both of us if we'd share it. (which I actually could use ATM )
So you tell me what you want to do

[moto_msm8960][CWM Advanced Edition] PhilZ Touch 6.xx.* and upwards.

Main thread + features + install instructions + dev support
http://forum.xda-developers.com/showthread.php?t=2201860
Click to expand...
Click to collapse
PhilZ Touch is a CWM Advanced Edition that adds all the features you could ever miss in CWM
It is a well proven recovery for many phones
It also adds a full touch interface a completely configurable GUI
Please give your feedback, what works, and any bug you could encounter
Read the features, and check if you are missing something
Also, do not forget to read about the powerful aroma file manager integration and double tap shortcut
Addendum: Unified builds, in particular this one for moto_msm8960 devices:
Supposed list of unified devices: Previous RAZR HD, Photon Q, Atrix HD, etc. : xt897, xt901, xt905, xt907, xt905, xt925, xt926, mb886 are now:
Now: moto_msm8960
I'm going to put them in a list so I can get around to checking Y on known working ones, and N on known non-working ones:
- xt926 (Y)
- xt925 (Y)
- mb886 (Y)
- xt897 (Y)
- xt901 (?)
- xt905 (?)
- xt907 (Y)​
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Quick notes about unified devices:
Do they all work in this build? I have no idea, but am pretty sure that from feedback that xt926/5, xt907 and xt897 have been reported to work.
The bottom line is that I rely on anyone reading here (or who is directed here from their development pages) to let me know what works, what doesn't so please let me know.
----------------------------
Download links
Latest versions built by me can be found here: (currently 6.xx.* and up).
Note: 6.58.7 final/stable is the latest (see the main development thread if not understood)
Changelogs:
v6.58.7 - new code and fixes
Click to expand...
Click to collapse
6.43.6 (02.06.2014)
- fix recursive path creation bug for /data/media/0
- default to /data/media/0 unless we define BOARD_HAS_NO_MULTIUSER_SUPPORT
- use lstat to check if file exists
6.43.4 - Final, Stable
- fix text print color could persist after md5 check
6.42.9 - Final & Stable
- default again to libtar for backup/restore
6.42.7 - Stable
- default to busybox tar:
- use busybox tar by default as it now supports selinux context backup/restore
- unify libtar and busybox tar options (-p for selinux context)
- remove now deprecated external selinux container code
6.41.6 - Stable & perhaps Final
- update exfat to dorimanx 1.2.9 latest sources
- fix compile error when enabling BOARD_RECOVERY_USE_BBTAR
- repo sync latest sources
- Galaxy Tab Pro 8.4 WiFi SM-T320 (mondrianwifi)
- HTC M7 variants: use new cm kernel with exfat sources
- HTC M8 variants: use new unified recovery
6.41.5 - Stable
- libtouch_gui 1.21: auto detect BRIGHTNESS_SYS_FILE path if it is not set during compile
* search for the file in most common locations
* if found, save it to recovery settings ini file to be called on next recovery starts
* else, disable adjust brightness function to avoid error logs on recovery start
- fix various compiler warnings and errors
- enhance pre-compile setup
- dedupe: merge clean up code from @xiaolu
- merge: fix restorecon_from_file potential crash from @xiaolu (only for BOARD_RECOVERY_USE_BBTAR)
- fix 240x320 images
- merge "cwm: Honor recovery variant "
- merge "cwm: Remove hardcoded paths"
- merge "Keep 'show log' on screen until user dismisses it"
- create /data/media directory after internal storage is wiped
prevents denial to read/write from internal storage under some circumstances
- open source touch_gui library
- update licence files
Click to expand...
Click to collapse
- Unified msm8960: 6.58.7 (4.4.4): Image : http://d-h.st/2xD
- v6.43.6: Unified msm8960: http://d-h.st/HgH
- v6.43.4: Unified msm8960: http://d-h.st/sQQ
- v6.42.9: Unified msm8960: http://d-h.st/SjY
- v6.42.7: Unified msm8960: http://d-h.st/9pD
- v6.41.6: Unified msm8960: http://d-h.st/uq1
- v6.41.5: Unified msm8960: http://d-h.st/QiK
Click to expand...
Click to collapse
Note: tested only on my xt926. Aroma has a few little glitches but is not often maintained.
Older versions built by Phil (or his 'crew'):
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/xt926 // oldest (and substitute your dev name for pre-unified builds)
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/moto_msm8960 // newer, recent.
Click to expand...
Click to collapse
My github(just created/work-in-progress) for tracking changes on this: https://github.com/Hachamacha/philz.git
Click to expand...
Click to collapse
Note: My part in this is very minuscule. I just got (git) his source and stuck it into cm11 as a build base. I changed very little, only added the msm8960 build since I think phil is working on the source rather than many individual builds due to time. If you look at his github from the main page link, the only file I really changed was ./boardconfig/BoardConfig.mk under ./recovery.
Goal: Just to make this available and keep people out of the main thread that aren't developing. If I can help with the specific device I'd do it, but I'm really not an xt926/5 expert. Still, if you've got msm8960 questions (so: device-specific, not general philz touch) ask them here about the device and recovery since odds are better you'll get an answer here than in the main thread. I'll try to update this with latest builds each week.
Disclaimer: The usual stuff you read in all of these threads. If your mind turns into margarine after installation, please send a sample to the CDC labs in Virginia. I searched all over XDA for a thread for philz for the msm8960 but didn't find it. If you do, feel free to destroy this thread, call me names, threaten my relatives (please do this), etc.
Credits: I think all credit should go to Phil, @Orphee and the CM11 guys if you like this type of recovery.

Thanks for doing this bro. Otherwise AHD'd be on 6.0.7x..
EDIT: Great job, I can confirm, 6.22.1 flashes and screen touches work perfect, format, wipe clean new rom, install new rom, restore backup on the Atrix HD/mb886.

Who wouldn't like the best recovery of all? Right? Thanks a lot

Works with keys only on the 907. Thanks.

aviwdoowks said:
Works with keys only on the 907. Thanks.
Click to expand...
Click to collapse
I don't recall the xt907 being unified into the msm8960, at least not in the philz code, but I could be wrong. Could you try a recent (6.19.x) build from over here http://goo.im/devs/philz_touch/CWM_Advanced_Edition/xt907 and let me know if that works? I think the msm8960 so-called unified builds are still a bit confused. It looks to me like only xt926 and 5 are covered.
If the build I linked to works, then it's to do with the 'unified' setup and I might need to grab some vender ID's etc.
By saying "works with keys only": I assume you're saying that the touchscreen stuff is off-kilter or just off period?
Thanks and I'll look it over for that device.
Everyone else: Glad it's working out for you. I'll update as soon as there's another git update.

No touch function at all. The mb886, 'hd & photon Q (screen input works too, albeit mirrored) recoveries have always worked on the M.
Any can be used on the others for key only use.
The Q twrp works 100% on the m but mirrored input. Arrrghhh said he may port his version to the m.

Since we can have unified recoveries now, would it be possible to make TWRP and have it work for all the unified devices?
Sent from my ATRIX HD using Tapatalk

aviwdoowks said:
No touch function at all. The mb886, 'hd & photon Q (screen input works too, albeit mirrored) recoveries have always worked on the M.
Any can be used on the others for key only use.
The Q twrp works 100% on the m but mirrored input. Arrrghhh said he may port his version to the m.
Click to expand...
Click to collapse
Took a look at the cm11 base I'm using as a building platform for philz code and it appears xt907 isn't yet part of the unified group though it ought to be according to CM. I'll leave a note and see if that's in the works. I'll check if xt907 has it's own build over there. By the way, from your reply I wasn't sure if you'd tried the pre-unified version I linked to on goo.im? Also philz stuff is using his own touch library GUI these days, and there might be something about that and the 907. Got some stuff to figure out.
Looks like (Atrix HD, Electrify M, Photon Q, Razr HD, and Razr M) are supposed to be part of it but from the way the code looks, (boardconfig) , not sure I believe it's yet been worked out. Razr M has some 9xx x {?} resolution, right?
Edit: CM11 looks fine as far as unified for xt907, so it must be something in the philz code that's not yet ready for the full array of unified devices.

penser said:
Since we can have unified recoveries now, would it be possible to make TWRP and have it work for all the unified devices?
Sent from my ATRIX HD using Tapatalk
Click to expand...
Click to collapse
I've used TWRP and like it a lot, but haven't looked at the build requirements yet. It seems possible to do unified builds for anything especially if you can do something like build the cm11 default code with it's default recovery, then substitute TWRP recovery for the default CWM in the ./bootable/recovery code. TWRP would have to be setup for that which is something I don't know. CM11 is where the unified structure is coming from in the case of these recoveries.

The 6221 you posted works.

aviwdoowks said:
The 6221 you posted works.
Click to expand...
Click to collapse
Cool! Thanks for letting me know.

hachamacha said:
Cool! Thanks for letting me know.
Click to expand...
Click to collapse
Are you savvy enough to allow/provide a partition backup of /persist?
At least Philz no longer lets noobs format it. Why not back it up? As it gets clobbered often.
---------- Post added at 09:41 AM ---------- Previous post was at 09:22 AM ----------
Could it have been the previous presence/oversight of the fomat command the the cwmr base gave be used on the phones that is the sole cause of all the /persist hubub & it being only on the phone is not an issue?
---------- Post added at 10:17 AM ---------- Previous post was at 09:41 AM ----------
More on persist
http://forum.xda-developers.com/showthread.php?t=2589790

aviwdoowks said:
Are you savy enough to allow/provide a partition backup of /persist?
At least Philz no longer lets noobs format it. Why not back it up? As it gets clobbered often.
---------- Post added at 09:41 AM ---------- Previous post was at 09:22 AM ----------
Could it have been the previous presence/oversight of the fomat command the the cwmr base gave be used on the phones that is the sole cause of all the /persist hubub & it being only on the phone is not an issue?
Click to expand...
Click to collapse
savvy: I don't know the answer to that yet
I just took a look at a) the main thread, noticed this (http://forum.xda-developers.com/showthread.php?p=48940651&highlight=persist#post48940651) and b) the code. What I come up with is that while in recovery, I can go to 'mounts' and mounting "persist" is an option which works for me. It's not on the backup list, mounted or not, but shows up in aroma FM when it's mounted. That link I put there claims there is allowed 5 "extra" partitions for backup/restore, so I might be able to set up /persist as one of them. I'm still new to this recovery code for android so don't expect too much. Looks like if I can get it to work on mine, then it ought to on yours.
As a workaround (if ADB is working to your box in recovery) , you could yank (pull) that /persist stuff yourself, but I think a new version is coming along pretty soon and I'll try to see if I can get it to work. (Time permitting etc etc)
edit: I realized that /persist is in the recovery.fstab file when I build which is why it's a mount choice in that menu. The other stuff (make it a backup choice) appears to be hard-coded in one of the .c files so it could be added, but there's a fair amount of stuff to do to add it. Yeah, it could be modified, but I'd want to ask Phil about it before messing with it. I suspect he had some reason since I noticed you and he talked about this in the main thread. Did he ever get back to you?

Mount is ok. When I posted the now unavailable format was there.

aviwdoowks said:
Mount is ok. When I posted the now unavailable format was there.
Click to expand...
Click to collapse
I'm trying to reopen the discussion in the main thread so we'll see how that goes.
Edit: General build update.
There's a new build, same version but some fixes that I'll put up eventually here. CM11 probably has the newest API and I'm restructuring my environment, so need to sync and clobber repo, include philz as a localrepo. Might take .. all day for the syncing and building to complete. Doing this in a VM today

Fixed: Aroma now works with screen input when booted from the msm version while key only from philz.
Translation: aroma works fully while using this on a 907.

hachamacha said:
savvy: I don't know the answer to that yet
I just took a look at a) the main thread, noticed this (http://forum.xda-developers.com/showthread.php?p=48940651&highlight=persist#post48940651) and b) the code. What I come up with is that while in recovery, I can go to 'mounts' and mounting "persist" is an option which works for me. It's not on the backup list, mounted or not, but shows up in aroma FM when it's mounted. That link I put there claims there is allowed 5 "extra" partitions for backup/restore, so I might be able to set up /persist as one of them. I'm still new to this recovery code for android so don't expect too much. Looks like if I can get it to work on mine, then it ought to on yours.
As a workaround (if ADB is working to your box in recovery) , you could yank (pull) that /persist stuff yourself, but I think a new version is coming along pretty soon and I'll try to see if I can get it to work. (Time permitting etc etc)
edit: I realized that /persist is in the recovery.fstab file when I build which is why it's a mount choice in that menu. The other stuff (make it a backup choice) appears to be hard-coded in one of the .c files so it could be added, but there's a fair amount of stuff to do to add it. Yeah, it could be modified, but I'd want to ask Phil about it before messing with it. I suspect he had some reason since I noticed you and he talked about this in the main thread. Did he ever get back to you?
Click to expand...
Click to collapse
Currently, recovery doesn't allow backup/restore of all what's in fstab
It would be dangerous in my opinion as you sometimes have the bootloader there
try to edit this line:
Code:
/dev/block/platform/msm_sdcc.1/by-name/persist /preload ext4 rw,nosuid,nodev,noatime,nodiratime,barrier=1
setting the mountpoint to preload will add it to my mod as it supports that partition
However, restoring could fail if you do not add the selinux needed permissions
Also, you can follow my guide here to add extra partitions using this flag: EXTRA_PARTITIONS_PATH
Actually, without adding the flag or recompiling, you can just edit recovery.fstab to:
Code:
/dev/block/platform/msm_sdcc.1/by-name/persist /extra_part1 ext4 rw,nosuid,nodev,noatime,nodiratime,barrier=1
by default, it is enabled when you name it extra_part1 to extra_part5
That way, you can easily add support to 5 extra partitions to nandroid menu with just a repack, no recompile needed

Phil3759 said:
Currently, recovery doesn't allow backup/restore of all what's in fstab
It would be dangerous in my opinion as you sometimes have the bootloader there
try to edit this line:
Code:
/dev/block/platform/msm_sdcc.1/by-name/persist /preload ext4 rw,nosuid,nodev,noatime,nodiratime,barrier=1
setting the mountpoint to preload will add it to my mod as it supports that partition
However, restoring could fail if you do not add the selinux needed permissions
Also, you can follow my guide here to add extra partitions using this flag: EXTRA_PARTITIONS_PATH
Actually, without adding the flag or recompiling, you can just edit recovery.fstab to:
Code:
/dev/block/platform/msm_sdcc.1/by-name/persist /extra_part1 ext4 rw,nosuid,nodev,noatime,nodiratime,barrier=1
by default, it is enabled when you name it extra_part1 to extra_part5
That way, you can easily add support to 5 extra partitions to nandroid menu with just a repack, no recompile needed
Click to expand...
Click to collapse
Thanks for the tips. After I test the next version (6.23.x) I'll try these techniques out, see how it goes on mine.

hachamacha said:
Thanks for the tips. After I test the next version (6.23.x) I'll try these techniques out, see how it goes on mine.
Click to expand...
Click to collapse
also, take a look here, at the highlighted line:
https://github.com/CyanogenMod/andr...8960/blob/cm-11.0/device_moto_msm8960.mk#L121
You have also a ro property to forbid mount:
Code:
ro.cwm.forbid_mount
Both these properties affect the format/mount options in "Mounts and Storage" menu

As far as screen input for the 907 goes, are you not almost there if aroma works?
---------- Post added at 08:12 AM ---------- Previous post was at 08:10 AM ----------
It works on 6227.

[Q] [UPDATED] Probelm Bootloop error with dsixda's kitchen cooked ROM

Hello guys:laugh:
I searched every forum thoroughly but didn't found a proper and working solution for Xperia devices
I am trying to make a custom ROM from stock using dsixda kitchen
I used stock 12.1.A.201 as the base ROM
I believe that it's either the updater script error or kernel probelm as I am using stock kernel and my zip is like this
Data
META-INF
system
boot.img
check_data_app
Click to expand...
Click to collapse
This happens when rom is created
De-odexed it rooted it and added X-Reality engine and created the rom
First on installing I got error of status 0 so I changed my update binary file from same de-odexed version from this link http://forum.xda-developers.com/showthread.php?t=2704312 by @dipesh1502 (thanks to him for that awesome rom)
Next I am getting error status 7
ROM Starts flashing then it comes to this part
formatting system bla bla
expected 5 args got 3
Click to expand...
Click to collapse
something like that and then it stops on error status 7
here is the updater-script please have a look. I really want to create this ROM. Please help
Updater-Script Download
here is my build prop build.prop download
Help guys please I'll be highly grateful
My device is C5302 rooted and unlocked bootloader with 12.1.A.205 stock kernel
EDIT : Got past the error status 7 now ROM gets installed
But unfortunately now it ends in a bootloop :/ Got stuck on Sony splash logo and then reboots constantly :/
Had a nandroid backup ready x)
Had to flash the ftf file over and over again. :/
Phone is allright just want to catch this error of bootloop.
I changed kernel with the dipesh1502's ROM but still no luck. Modified Updater script but still no luck. help me I am soo confused and screwed!! :'( :'(
My new Updater-Script

There's a HUGE difference in creating boot animations and creating a ROM.
Don't expect to teach yourself how to make a ROM in just a few days.
It takes, weeks, months, years...
If you're mainly planning to make some exterior changes, which I think you're currently doing, I would focus on making complete themes and not ROMs.
People are not waiting for a ROM which is already available but that looks somewhat different and maybe has some extra or removed apps.
Regarding your problem, I will not be able to help you since I don't have that kind of knowledge.
Anyway, good luck!

Gamm86 said:
There's a HUGE difference in creating boot animations and creating a ROM.
Don't expect to teach yourself how to make a ROM in just a few days.
It takes, weeks, months, years...
If you're mainly planning to make some exterior changes, which I think you're currently doing, I would focus on making complete themes and not ROMs.
People are not waiting for a ROM which is already available but that looks somewhat different and maybe has some extra or removed apps.
Regarding your problem, I will not be able to help you since I don't have that kind of knowledge.
Anyway, good luck!
Click to expand...
Click to collapse
Thanks for the reply.
Yeah I know that it's not easy to create ROM and also it takes a lot of time. I am ready to give it a shot
I am just making some small changes just for my sake I'll be using this ROM personally for my own use I know that there are a thousand times better ROM's than mine
Anyway glad you considered my probelm.

Bootloop can be cause by:
- Wrong permissions
- Corrupt installation
It is nice if you collect either the last_ksmg or logcat when bootlooping. (if possible)
~~Regard
---------- Post added at 08:08 PM ---------- Previous post was at 08:04 PM ----------
But first:
Share me the .zip you have created perhaps I can take a small look
~~ Regards

mrjraider said:
Bootloop can be cause by:
- Wrong permissions
- Corrupt installation
It is nice if you collect either the last_ksmg or logcat when bootlooping. (if possible)
~~Regard
Click to expand...
Click to collapse
Thanks for the reply
Can you please have a look at my new updater-script and tell me what is wrong?
I will surely try to get logcat but before that if you can just analyze this updater-script and pinpoint the mistakes it'll make my work a lot easier.
Thanks in advance :good:

Sent me the entire .zip file instead (but start with updater-script)
~~Regards

mrjraider said:
Sent me the entire .zip file instead (but start with updater-script)
~~Regards
Click to expand...
Click to collapse
Sure thing I'll
I am compressing it to maxium extent using KGB archiver and it'll become around 10~20 mb only
It's still compressing so it'll take some time before it reaches it's max compression.
I'll surely send you asap

Porting CM12

Hi! I'm currently making a somewhat desperate attempt at porting cm12 to the d950. I know some basic things, I once tried to make a custom kernel. I have the device and vendor trees set up, with the cm12 source and the files from the flex source, and I've been making some changes. Can anyone help point me in some direction from here?

dongdong6968 said:
Hi! I'm currently making a somewhat desperate attempt at porting cm12 to the d950. I know some basic things, I once tried to make a custom kernel. I have the device and vendor trees set up, with the cm12 source and the files from the flex source, and I've been making some changes. Can anyone help point me in some direction from here?
Click to expand...
Click to collapse
Okay, so now I need to run extract-files.sh, only problem is it doesn't exist. and from my understanding, I have to already be running cm12 to do this, which obviously is not possible. Can anyone help me get the proprietary blobs?

You're better off looking at the g2 proprietary blobs as when I was trying I had the most success with them on CM11, its a good starting point

So should I take those, then make changes to suit the flex?

Yeah, its a good place to start, but it won't suddenly make it compile, it helped sort a couple of issues once we'd got it compiling in the first place....

Try msg playfulgod and see if he will point you in the right direction

Alright, I've got something that looks pretty good going, but I can't do anything without a working kernel. And as I don't know much about kernels, could Someone possibly try to make one for cm12? Also, I have the blobs from my boyfriend's g2, and I've made a lot of changes, but I might need a little more guidance. Any help is appreciated.

Do you have coding experience though thats the question.
Either Build a dummy kernel or modify the original kernel from cm11 roms that your device has and built it alongside the system images.
CyanogenMod doesnt allow Building of only the system.
Youll need to modify the following:
Kernel Source
Device Trees
Vendor Files
A good way to look at what is required for a cm12 bringup is to check other similar devices with the same architecture and compare the changes and the sources you have on your pc.
Regards
Sent from my Xperia SP using xda Forum

I took programming classes, and there were a few units on android.

So I just forked the blobs from playfulgods repo, and I've made a lot of changes to tbe devices folder, as well as 'POSSIBLY' do something good as for a kernel, but I doubt that will work. How does one build the kernel to test it? Using linux btw. I have all of the dependencies and everything, could someone explain breakfast/brunch/lunch?

HEY SO I THIN K I HAVE SOMETHING THAT MIGHT WORK AFTER HAVING SOME REALLY SMART PEOPLE HELP sorry for caps, but now I have something in the out folder for zee, what do i do with this, and how do i make it flashable? could someone do it for me? and also, kernels?

dongdong6968 said:
HEY SO I THIN K I HAVE SOMETHING THAT MIGHT WORK AFTER HAVING SOME REALLY SMART PEOPLE HELP sorry for caps, but now I have something in the out folder for zee, what do i do with this, and how do i make it flashable? could someone do it for me? and also, kernels?
Click to expand...
Click to collapse
I can write and add the meta-inf folders to make it flashable. But I don't do kernels

mattwheat said:
I can write and add the meta-inf folders to make it flashable. But I don't do kernels
Click to expand...
Click to collapse
I would really appreciate that! What means should I take of sending you the output?

dongdong6968 said:
I would really appreciate that! What means should I take of sending you the output?
Click to expand...
Click to collapse
I see 2 things with the Out Folder having problems.
1) What has the Build System Generate in the out folder?
2) CM12 will generate a pre configured Zip File if it doesn't, the build failed
Sent from my Huashan Device utilizing RR Milestone 1

Furrydaus said:
I see 2 things with the Out Folder having problems.
1) What has the Build System Generate in the out folder?
2) CM12 will generate a pre configured Zip File if it doesn't, the build failed
Sent from my Huashan Device utilizing RR Milestone 1
Click to expand...
Click to collapse
If anyone wants to take a look I zipped the out folder.

So you're going to tell us you zipped the folder but you're not going to tell us where it is? Lol
Sent from my Huashan Device utilizing RR Milestone 1

dongdong6968 said:
So I just forked the blobs from playfulgods repo, and I've made a lot of changes to tbe devices folder, as well as 'POSSIBLY' do something good as for a kernel, but I doubt that will work. How does one build the kernel to test it? Using linux btw. I have all of the dependencies and everything, could someone explain breakfast/brunch/lunch?
Click to expand...
Click to collapse
The device tree repos found in lg-devs github are the correct ones just change kernel source to our stock kernel and edit z.mk and verndor files can be extracted with the ./extract-fikes.sh script . But our kernel needs to be updated a little which i am working on mostly caf header need to be added to include/Linux for media and display. I trued using msm8974 kernel but our kernel has specific blobs we use which is easier to use stock kernel.
---------- Post added at 06:26 PM ---------- Previous post was at 06:16 PM ----------
dongdong6968 said:
HEY SO I THIN K I HAVE SOMETHING THAT MIGHT WORK AFTER HAVING SOME REALLY SMART PEOPLE HELP sorry for caps, but now I have something in the out folder for zee, what do i do with this, and how do i make it flashable? could someone do it for me? and also, kernels?
Click to expand...
Click to collapse
What you mean you got something lol. We just need to update our stock kernel which you can have a better understanding. Of what i mean visit lg-devs for z repos . we should stick to stock kernel doe.

dongdong6968 said:
I would really appreciate that! What means should I take of sending you the output?
Click to expand...
Click to collapse
Upload it to drive then message me with a link

mattwheat said:
Upload it to drive then message me with a link
Click to expand...
Click to collapse
https://www.dropbox.com/s/dx3sjp8bq720bkn/out.zip?dl=0

Furrydaus said:
So you're going to tell us you zipped the folder but you're not going to tell us where it is? Lol
Sent from my Huashan Device utilizing RR Milestone 1
Click to expand...
Click to collapse
Sorry, completely forgot. https://www.dropbox.com/s/dx3sjp8bq720bkn/out.zip?dl=0