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] [UNOFFICIAL] CWM 6.0.3.0 TOUCH BASED RECOVERY fully working NO REBOOT BUG

Welcome happy campers
Here is a fully working pretty much fully tested port of Clockwork Mod Recovery 6.0.3.0
Big thanks to UTKANOS at #cyanogenmod irc channel for his help in building this for me to test till everything was working
FEATURES
All features in 6.0.3.0 based CWM recoveries are implemented
Touch screen working
Restore/Backup functions
All wipe functions
All Mount functions
Install from sd and Internal storage
Generally all features you expect from working ClockWorkMod recovery
without further ado here is the link to the recovery image: http://d-h.st/nMv
md5 Checksum : 8f7dda170425218f47717a9c9c931bea
source code at utkanos' github: https://github.com/utkanos/android_device_htc_golfu
Thanks goes out to mmmcfc for his initial work on the recovery we worked on to bring you this version, his original thread at :
http://forum.xda-developers.com/showthread.php?t=1785010
to install recovery is same as always for people who already know
for those of you who are new to this and do not know but are at the point of installing a custom recovery through a rom install guide please simply turn off your Desire C device, drop out the battery just in case fastboot is on in your rom settings, replace your battery then hold the volume down key and hold power button till you boot to bootloader.
Ensure phone is on fastboot setting (will have fastboot written in red if you are) plug in the usb cable and it should say fastboot usb now then enter this command from terminal window that is in the directory where you have this image downloaded to
Code:
fastboot flash recovery recovery-clockwork-6.0.3.0-golfu.img
with any joy you should now be able to reap the benefits of touch screen enabled up to date CWM recovery
enjoy
p.s. if you have issues installing this or do not know what our doing either do not install OR search the forums for root guide and recovery install guides and if you cannot find something relevant feel free to pm me
dont forget to come to our irc channel at irc.freenode.net ##HTCDesireCcm9 (dont forget to put two hash signs not one) we are friendly in the channel and are hoping it will begin to grow alongside development for the device
thanks
soon to come wifi fix for CM9, hopefully soon CM10 build and with all the fixes no doubt many custom roms from many users throughout our device section

Reserved this for maybe other information etc...

russell664 said:
Reserved this for maybe other information etc...
Click to expand...
Click to collapse
this is why we get along so well lol, albeit you do take forever to respond to irc chat but hey no one is perfect....

Great job :good:. Reboot is definetly fixed. Btw are you sure that device tree is updated with all the changes? I tried to build TWRP with that exact tree and still seem to have reboots.
Sent from my Nexus 4 using xda premium

nikhil16242 said:
Great job :good:. Reboot is definetly fixed. Btw are you sure that device tree is updated with all the changes? I tried to build TWRP with that exact tree and still seem to have reboots.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Not totally sure dude about your question as this was actually built by utkanos with no device with me and russell testing the builds as they were made till we had it working with no reboots and with fully accessing adb rights when in recovery. i had massive issues when using th TWRP recovery that was posted so it may be TWRP specific that your issues lie. the source code is all available at utkanos github linked in the OP so you can surely tell from that if device tree is correct. if not maybe try to rebuild the trees. i myself have little experience in these matter XD

mehmehmen said:
Not totally sure dude about your question as this was actually built by utkanos with no device with me and russell testing the builds as they were made till we had it working with no reboots and with fully accessing adb rights when in recovery. i had massive issues when using th TWRP recovery that was posted so it may be TWRP specific that your issues lie. the source code is all available at utkanos github linked in the OP so you can surely tell from that if device tree is correct. if not maybe try to rebuild the trees. i myself have little experience in these matter XD
Click to expand...
Click to collapse
Ahh ok Np . Anyway.. good to have a recovery that doesn't reboot itself :thumbup:
Sent from my Nexus 4 using xda premium

A damn of a recovery, great work and thank your for this. Keep up the good work. Thank you again.

Thank u for this ,and thank u for keeping this phone alive , gl on ur cm work guys
Sent from my HTC Desire C using xda app-developers app

no worries guys, amazing to have 200+ views and what 4 users post in the thread lol all thanks is aimed to utkanos for his work making it happen, and mmmcfc for his original version build we worked on. i just tested and provided needed files to utkanos. all thanks is more than appreciated as we spent a whole day pretty much fixing the bloody thing

By the way, we should contact the guys from CWM to get official support like nikihil did.

TheRedHunter said:
By the way, we should contact the guys from CWM to get official support like nikihil did.
Click to expand...
Click to collapse
you need to shoot a mail to koush to get rom manager or cwm support.

Finally a non-rebooting recovery!! Thanks! :good:

your welcome, cant believe there wasnt one for so long, i only got the device around a month ago and found the xda development section lacking in a few areas im not used to seeing and so worked with a cm dev on getting the recovery up to date and stable
any thanks you guys want to click my way are welcomed and would be nice, amazing that over in my general section post to this thread there is a total of maybe 3 thanks per nearly 2,500 visitors to the link
now thats appreciation for ya

Just one question, am i blind, or this one has no clean battery stats?
Is it really needed, and is there a workaround (which file to delete)?

mehmehmen said:
your welcome, cant believe there wasnt one for so long, i only got the device around a month ago and found the xda development section lacking in a few areas im not used to seeing and so worked with a cm dev on getting the recovery up to date and stable
any thanks you guys want to click my way are welcomed and would be nice, amazing that over in my general section post to this thread there is a total of maybe 3 thanks per nearly 2,500 visitors to the link
now thats appreciation for ya
Click to expand...
Click to collapse
You are a great man, and your work is very appreciated. You have my thanks and I'll try to add as many thanks to you as I can.

I've shot you a few thanks as it's a damn fine cause, even if I strongly dislike cwm. I am afraid I am a Twerp through and through.
Ps I will try and get some extra thanks to you Redhunter as you are such a generous guy with your thanks and you always are upbeat and positive. It's good to see, thank you.
All the best rich
Sent from my Nexus 7 using xda premium

Dead link?
The download link to dev hub seems to be dead/broken ... is it just me?!?

AirCombat said:
The download link to dev hub seems to be dead/broken ... is it just me?!?
Click to expand...
Click to collapse
It works for me

calinorg said:
Just one question, am i blind, or this one has no clean battery stats?
Is it really needed, and is there a workaround (which file to delete)?
Click to expand...
Click to collapse
my ? too.i just updated to current version,and browsing around i noticed it is not there??

Can u make this in colours of mujenu touch recovery and create a guide for building recoveries
Sent from my HTC Desire C using xda app-developers app

[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

[MOD] MultiROM (sharing kernel)

I found the bug with not isolating kernel in additional roms after posting multirom here. Unfortunately I havent solved it yet. I decided to not delele this project because the rest of this works. This is useful who want to have similar rom in on tab. For example to test apps. Sorry for inconvience.
this is beta release. for p900 only.
I'll write full instruction later. For full description see http://forum.xda-developers.com/showthread.php?t=2011403
I'm not sure that everything is stable, so I dont publish source code. I dont want to distribute buggy sources. thanks for understanding.
for stock firmware only. for now. use stock frimware as primary. you can flash cm as additional.
Installation:
1. https://yadi.sk/d/RVXpEgc6c4GKo - this is modded recovery. flash via odin
2. https://yadi.sk/d/CHl8wTYYc4GMZ - patched kernel. (patched my 1.3 pro kernel)
https://yadi.sk/d/D2riVhEgc4GPP - multirom main program
flash through modded recovery patched kernel and multirom.
uninstallation:
https://yadi.sk/d/jc4uxZeCc4GRb - flash this uninstaller through recovery, then flash original twrp
known issues:
- 1920x1200 resolution in twrp
- in List Roms installed roms dont shown
- in multirom boot menu touchscreen downt work. use buttons (vol-,vol+,power)
multirom apk from play store doesnt support this release.

reserved

more reserved

bonuzzz said:
this is beta release. for p900 only.
I'll wrote full instruction later. For full description see http://forum.xda-developers.com/showthread.php?t=2011403
I'm not sure that everything is stable, so I dont publish source code. I dont want to distribute buggy sources. thanks for understanding.
Click to expand...
Click to collapse
I saw earlier that you had plans for this, but I didn't expect it to happen this quickly.
Anyway, great initiative.

WOW
@bonuzzz,
nice to see you here. Actually I bought this high end class tablet because of its specifations and over standarts. Still is the most powerful tablet in market.. But somehow it always lacked development and support of developers. Recently maybe the price is dropped so it started make owners smile little bit.
I was almost giong to change it, but still there is no powerful alternate..
I would like to be a tester of multiboot. because I would love to see ubuntu desktop in this tablet.
Thank you!

m_carleone82 said:
@bonuzzz,
nice to see you here. Actually I bought this high end class tablet because of its specifations and over standarts. Still is the most powerful tablet in market.. But somehow it always lacked development and support of developers. Recently maybe the price is dropped so it started make owners smile little bit.
I was almost giong to change it, but still there is no powerful alternate..
I would like to be a tester of multiboot. because I would love to see ubuntu desktop in this tablet.
Thank you!
Click to expand...
Click to collapse
it's not so difficult to run ubuntu desktop here, but it wiil be very big problem with drivers. I thought about ubuntu, but now I'm not going to have a deal with it. I advice you to look linux deploy

Great job
bonuzzz said:
it's not so difficult to run ubuntu desktop here, but it wiil be very big problem with drivers.
Click to expand...
Click to collapse
Here are some drivers for the GPU. I will look into it.
http://malideveloper.arm.com/develop-for-mali/features/mali-t6xx-gpu-user-space-drivers/

ESmazter said:
Great job
Here are some drivers for the GPU. I will look into it.
http://malideveloper.arm.com/develop-for-mali/features/mali-t6xx-gpu-user-space-drivers/
Click to expand...
Click to collapse
If you could get it working it would be great.

arcadia2uk said:
If you could get it working it would be great.
Click to expand...
Click to collapse
I'm currently having a lot of work with multirom, so I think I'll not have time to deal with ubuntu

bonuzzz said:
I'm currently having a lot of work with multirom, so I think I'll not have time to deal with ubuntu
Click to expand...
Click to collapse
My appreciation was actually meant for ESmazter saying: I will look into it

oops, i haven't noticed esmazter's phrase

I found the bug with not isolating kernel in additional roms after posting multirom here. Unfortunately I havent solved it yet. I decided to not delele this project because the rest of this works. This is useful who want to have similar rom in on tab. For example to test apps.

bonuzzz said:
I found the bug with not isolating kernel in additional roms after posting multirom here. Unfortunately I havent solved it yet. I decided to not delele this project because the rest of this works. This is useful who want to have similar rom in on tab. For example to test apps.
Click to expand...
Click to collapse
I was still hoping to get the minor issues resolved, notably the issue with Rom's installer are not shown in the installed ROM's section.

Any possibility of porting this to Galaxy Note 10.1 (2014)? The hardware is almost exactly identical. Really like your work, keep it up!

hhairplane said:
Any possibility of porting this to Galaxy Note 10.1 (2014)? The hardware is almost exactly identical. Really like your work, keep it up!
Click to expand...
Click to collapse
I dont have any plans to port to other devices. It doesnt fully working and I dont have any progress with it...

Do you mean the first (pre multirom install ) flashed rom kernal is the only kernal that boots regardless of the chosen rom, is multirom a separate bootloder that is chainloaded by the original bootloader? Does multirom have a config file describing the various kernals with different filenames if so can it be manually edited? Does multirom mount emulated system partition images or are their actual multiple prexisting system partions in the mbr that multirom can choose from ? What would quilify as similar roms, stock and omni are they similar enouph ?

brock28 said:
Do you mean the first (pre multirom install ) flashed rom kernal is the only kernal that boots regardless of the chosen rom, is multirom a separate bootloder that is chainloaded by the original bootloader? Does multirom have a config file describing the various kernals with different filenames if so can it be manually edited? Does multirom mount emulated system partition images or are their actual multiple prexisting system partions in the mbr that multirom can choose from ? What would quilify as similar roms, stock and omni are they similar enouph ?
Click to expand...
Click to collapse
I dont recommend to use this multirom because it has the bug with sharing kernel. So you need to use similar roms as primary and as additional. I dont have an idea how to solve it at this moment.

[CLOSED][Discontinued][UPDATED][ROM][UNOFFICIAL][MIUI][4.4.4] MIUI 7 for espresso3g devices

Discontinued.
Awaiting for thread deletion.

Thanks...Nice work after your miui 5 ROM

Help please..
Need someone who can risk his device by testing this ROM......

Happy holi.....
Happy holi my friends...
May this holi bring lots of Colors in your life!! and in mine too.

Kunal Gautam said:
Need someone who can risk his device by testing this ROM......
Click to expand...
Click to collapse
I tried to install but it gives error 7 i think update.script should be rechecked.

Deep_dhimaan said:
I tried to install but it gives error 7 i think update.script should be rechecked.
Click to expand...
Click to collapse
Thank you very much, i've understood whats the problem( as a pm by ashkineeeeee).
New update coming soon. Stay tuned.

Hey bros...
so there were some problem with permissions, it seems that it is fixed now..
Flash the ROM and review here....
----------------------edit 1---------------------
dont flash the rom now!!!
Some files are missing in boot.img
how stupid i am!!
------------------------edit 2-----------------------
Flash it now!

Last build not installed,error 7.

mels01 said:
Last build not installed,error 7.
Click to expand...
Click to collapse
Logs,screenshots?
Try installing from internal storage... Or update your recovery to the latest one by android andi...
Thanks!

Hey, I would like to help out, can I have the link to the ROM?

theportal2 said:
Hey, I would like to help out, can I have the link to the ROM?
Click to expand...
Click to collapse
I agree this message is a bit long but it is worth reading.
- Thanks, but sorry. Even if I give you the links and even if spend your precious time you would only be able to fix the error 7.
- Actually I've already fixed that(or know what's the issue atleast). There are files that are missing from the directories that are listed in the updater script. They cannot be deleted as the original base ROM I compiled was from UA(unlegacy android) that are based on the newer sources.
- Some files that are required for MIUI are also missing.
- Boot.img is incomplete. Which will result in bootloop even if I upload the error 7 fixed ROM.
- I am giving my board exams that are one of the biggest exams in India. And I cannot afford to score less in these.
- All I need is a older base ROM ,CyanogenMod 11 made around may of 2016. And also it must support init.d because the port ROM requires that.
- I've taken permissions from the maker of the port ROM. He has allowed me to proceed.
- All I need is permission from Android-Andi, as only he has older CM ROMs.
- I cannot compile because older sources are not available or maybe I am not known to them
Hope you understand. Thank you.
P.S. - Android-Andi if you read this please reply. You are the only one who can help me(by providing me permissions to use your ROM as a base).
With best regards,
Kunal Gautam

Links

Kunal Gautam said:
I agree this message is a bit long but it is worth reading.
- Thanks, but sorry. Even if I give you the links and even if spend your precious time you would only be able to fix the error 7.
- Actually I've already fixed that(or know what's the issue atleast). There are files that are missing from the directories that are listed in the updater script. They cannot be deleted as the original base ROM I compiled was from UA(unlegacy android) that are based on the newer sources.
- Some files that are required for MIUI are also missing.
- Boot.img is incomplete. Which will result in bootloop even if I upload the error 7 fixed ROM.
- I am giving my board exams that are one of the biggest exams in India. And I cannot afford to score less in these.
- All I need is a older base ROM ,CyanogenMod 11 made around may of 2016. And also it must support init.d because the port ROM requires that.
- I've taken permissions from the maker of the port ROM. He has allowed me to proceed.
- All I need is permission from Android-Andi, as only he has older CM ROMs.
- I cannot compile because older sources are not available or maybe I am not known to them
Hope you understand. Thank you.
P.S. - Android-Andi if you read this please reply. You are the only one who can help me(by providing me permissions to use your ROM as a base).
With best regards,
Kunal Gautam
Click to expand...
Click to collapse
Have you seen this CM 11? https://forum.xda-developers.com/galaxy-tab-2/7-inch-development/rom-cm-11-0-galaxy-tab-2-t3737392
Just made last month by @Deltadroid

Links are removed because *the ROM is not complete yet*.
Thanks, but I need to confirm a few things before I could use a ROM(includes init.d support and a bunch of other things). Also, it is very important that deltadroid provide me permission to use his ROM.
Thank you!
Regards,
KG
-----_edit_--------
I just saw deltadroid's thread, the title clearly says that the ROM is for p3110. I want to make a unified one. I need a ROM made with unified device tree.
If I do port, it will only work on p3110 and maybe on every 7" device. I don't want do this.
Sorry, but yeah thanks!
Just wait till 3 april 2018. Most probably I will upload.
Edit 2
Or I must say it an update. 75 percent of the work is done. Somehow I managed to get a base ROM(only I know how). Only build.prop editing and Updater script editing work left(these are the most difficult BTW).
Update coming soon. Stay tuned.

I've updated the links. I've uploaded the new ROM. I've done with porting(i guess). I've used a lot of time.
Flash and review!

Kunal Gautam said:
I've updated the links. I've uploaded the new ROM. I've done with porting(i guess). I've used a lot of time.
Flash and review!
Click to expand...
Click to collapse
No wonder the ROM doesn't work.... Security patch is in a wrong format.
"ro.build.version.security_patch=2080-17-March"
It should be, "ro.build.version.security_patch=2018-03-01"
or,
"ro.build.version.security_patch=2018-03-05"
And this, hardly doubt this will work, but idk.
"ro.build.date.utc=999999999999"
Mistakes....................
EDIT**** Build id should be the app id: example lets say the id is 678, on build.prop, it would say 678.
you have, "ro.build.id=KUNAL"

secretwolf98 said:
No wonder the ROM doesn't work.... Security patch is in a wrong format.
"ro.build.version.security_patch=2080-17-March"
It should be, "ro.build.version.security_patch=2018-03-01"
or,
"ro.build.version.security_patch=2018-03-05"
And this, hardly doubt this will work, but idk.
"ro.build.date.utc=999999999999"
Mistakes....................
EDIT**** Build id should be the app id: example lets say the id is 678, on build.prop, it would say 678.
you have, "ro.build.id=KUNAL"
Click to expand...
Click to collapse
You, sir, definitely have a lot to offer. I am afraid that this is not the actual problem. By now, I surely understand the importance of logs. Would be very helpful if someone could arrange me them.
And about your post it seemed really rude, raw, insulting and manipulating to me. But however, helpful. It makes it really hard to continue developing for a 6 years old Tab, with hardware that has nothing to offer in 2018. At least, I am trying.
Since, this was an Alpha build(because I moved sources) these problems are sure to arise. I did the same(build.prop things) with my kinda successful ROM MIUI 5(see it in the 7" forums).
I guess you haven't tasted port ROMs yet. They are hard to build. Alike your compiling ones, you have source, type some commands, turn your computer on for about 5 hours, when done upload it.
I am sure you must have did trail and error (in chemistry and math) porting ROMs is just the same. I am sure, that as a developer, you must know what logs actually mean.
But whatever, thank you for you review(insult I guess).

Kunal Gautam said:
You, sir, definitely have a lot to offer. I am afraid that this is not the actual problem. By now, I surely understand the importance of logs. Would be very helpful if someone could arrange me them.
And about your post it seemed really rude, raw, insulting and manipulating to me. But however, helpful. It makes it really hard to continue developing for a 6 years old Tab, with hardware that has nothing to offer in 2018. At least, I am trying.
Since, this was an Alpha build(because I moved sources) these problems are sure to arise. I did the same(build.prop things) with my kinda successful ROM MIUI 5(see it in the 7" forums).
I guess you haven't tasted port ROMs yet. They are hard to build. Alike your compiling ones, you have source, type some commands, turn your computer on for about 5 hours, when done upload it.
I am sure you must have did trail and error (in chemistry and math) porting ROMs is just the same. I am sure, that as a developer, you must know what logs actually mean.
But whatever, thank you for you review(insult I guess).
Click to expand...
Click to collapse
FYI, I port ROMs. It was pointers what to fix, if you wanted to get this ROM better, than it is already.

Kunal Gautam said:
(...)
P.S. - Android-Andi if you read this please reply. You are the only one who can help me(by providing me permissions to use your ROM as a base).
With best regards,
Kunal Gautam
Click to expand...
Click to collapse
Sorry, I won't give permissions after different people used my ROMs as base in the past without permissions. Hope there is a learning affect....
Since i love OpenSource: Sources are available on every official GitHub (slim, Omni, Lineage, UA) and up to date (note: I wouldn't have to do this, I could keep all device trees private but I am updating them for everyone - always). You'll have to compile your own base ROM to use for such port ROMs (I am not a fan of).

Android-Andi said:
Sorry, I won't give permissions after different people used my ROMs as base in the past without permissions. Hope there is a learning affect....
Since i love OpenSource: Sources are available on every official GitHub (slim, Omni, Lineage, UA) and up to date (note: I wouldn't have to do this, I could keep all device trees private but I am updating them for everyone - always). You'll have to compile your own base ROM to use for such port ROMs (I am not a fan of).
Click to expand...
Click to collapse
Thank you. For at least replying. You works will always be appreciated. Now, I am gonna close this thread. Thanks again!