In the last weeks I blogged a couple of times about how we want to get Ubuntu out to more and more users in a much much easier way. It would be great if we could have gotten all images built in the data centre, but unfortunately do redistributability issues (some firmwares, blobs and proprietary kernel modules) not allow us to redistribute them easily. Another issue were some short-comings in our infrastructure, which have to some degree been fixed already.
Anyway... we wanted to make it easier and take sort of a short-cut, so the unstoppable Sergio Schvezov sat down and restructured phablet-tools to let us much more easily support community ports of Ubuntu Touch.
What does this mean?
{
"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"
}
Up until now, phablet-flash just supported these four devices: Galaxy Nexus, Nexus 4, Nexus 7 and Nexus 10. That was it.
After some discussions with port maintainers around the globe, we are quite happy to announce that we are now adding the following community ports to the mix: HTC Desire Z, Samsung Galaxy S2, Huawei Ascend P1. Now the family of phablet-flash‘able devices would look like this:
Once Sergio’s branch has landed, you will be able to just run
Code:
phablet-flash community --device u9200
to flash your device. (The above would be what you’d need to type in for a Huawei Ascend P1.) Until then you can just
Code:
bzr branch lp:~sergiusens/phablet-tools/flash_change
and run it from there.
More and more devices are on the way, and the process for telling phablet-flash about your port is actually quite easy.
You can help!
If you have any of the devices lists on our Touch Devices list, and you made a backup of things and you generally know your way around in terms of flashing, etc. Do the following:
Check if your port is registered already. If yes, great. If not, please talk to the port maintainers listed on the page linked from our devices list and follow the instructions for registering the port.
Code:
bzr branch lp:~sergiusens/phablet-tools/flash_change; cd flash_change; ./phablet-flash community --device <vendor>
(ie, i9100)
Give feedback on the ubuntu-phone mailing list.
Thanks a bunch in advance!
Quick update: now it's just
bzr branch lp: phablet-tools; cd phablet-tools
./phablet-flash community --device <vendor>
Click to expand...
Click to collapse
(Remove the space between "lp:" and "phablet-tools" - auto-smiley got me here.
If you run saucy and have phablet-tools installed, you can now just run:
Code:
phablet-flash community --device <vendor>
Great work, everyone.
Any word on when/how we'll be able to use CM10.2 to build the Android parts? I don't have much of an option for the new N7.
Sent from my Nexus 4 using Tapatalk 2
Related
IN THE WORKS
{
"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"
}
STATUS:
============================================================================
[3:11 AM | 6/1/2011] - Kubuntu Mobile booted till cursor then got into shell asking for login
============================================================================
[2:54 AM | 6/1/2011] - finished building custom rootfs, copying to sdcard, hope it starts
============================================================================
Hi Nyl, clearly you are very talented and you are making a tremendous contribuition to the XDA/TG01 community.
Now dont take this the wrong way but would it not be a good idea to pool your findings with the guys having problems getting Android to run on the TG01 as you seem to have overcome the stumbling blocks they have reached?
I know Linux is not the same as Android but in terms of getting radio, 3g working your work may go a long way to helping those guys out??
this build gonna be available for download as official kubuntu release, if i get it working and the other ubuntu version will be canceled as fact that kubuntu mobile is more finger friendly...
hi ^^
if i understand, you dont know username and pass
i found this for ubuntu hd2
user: 'htc-linux'
password: 'ubuntu'
Hope this can help
Nice project!
I forgot to state that this ain't related to HD2 Ubuntu this is a new project from scratch specially made for tg01
the problem is that i don't have any hardware keyboard to create new user and login
nyl said:
I forgot to state that this ain't related to HD2 Ubuntu this is a new project from scratch specially made for tg01
the problem is that i don't have any hardware keyboard to create new user and login
Click to expand...
Click to collapse
I know nothing of android, so sorry if this is useless, but..
I believe that the Kernel from the android project has USB support, so maybe you could connect a USB keyboard to the host cable and connect to the TG01.
I'm only thinking this because I've seen a photo of a device i can't remember running Ubuntu with a USB keyboard
I realise this may be useless if the host drivers are not there but don't know enough to go and find out.
well my problem is that i can't run qemu ARM on my linux/windows OS
h ttp://fedoraproject.org/wiki/Architectures/ARM/HowToQemu
Cant wait till it is ready! I love your ToshDroid ROM
nyl> Are you still continuing with this project?
I subscribe to this!
Great project. I hope you will manage to fix that wifi driver
Too bad that people who ported Android to htc hd2 don't want to share with us the secret of converting the wm wifi driver to a android/linux wifi driver...
Hi!
In case anyone want to try to run the new Ubuntu Touch on our Ideos S7 device, Canonical provided a porting guide, which explains the steps needed to port Ubuntu on a new hardware:
--> wiki.ubuntu.com/Touch/Porting
( a grande bosta que é o XDA não me deixa colocar links externos... )
Remenber it is a developer preview!
{
"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"
}
Theoretically should be possible to have everything on the S7 working, as Ubuntu re-uses the same Android binary blobs already available on the S7.
To rapidly support a wide range of devices, our architecture reuses some of the drivers and hardware enablement available for Android.
As a consequence, at the current images you'll find some of the Android services running at the device, and the Ubuntu filesystem living separately, inside a container.
For quick reference, these are the current components used from Android:
- Linux Kernel (stock Android kernel provided by the vendor, with a few changes to support some extra features needed by Ubuntu)
- OpenGL ES2.0 HAL and drivers
- Audio/Media HAL and services, to re-use the hardware video decoders
- RILD for modem support
Click to expand...
Click to collapse
:good:
Some have already done some work:
http://forum.xda-developers.com/showthread.php?t=2168473
http://forum.xda-developers.com/showthread.php?t=2160773
( links internos deixa! )
hi
please discussion step by step how work to porting Ubuntu touch on huawei ideos s7 105 .
i am biginer and require to discussion details.
my device android 2.2.2
JotaMG said:
Some have already done some work:
http://forum.xda-developers.com/showthread.php?t=2168473
http://forum.xda-developers.com/showthread.php?t=2160773
( links internos deixa! )
Click to expand...
Click to collapse
Hi JotaMG, this will require much work, specialy the kernel part, better bet a group of people and do it together.
My best bet is used some part of the work for htc passion same type cpu ( it helps ) same type of board.
If you get more people interested you can count with me.
hal_2000
hal_2000 said:
Hi JotaMG, this will require much work, specialy the kernel part, better bet a group of people and do it together.
My best bet is used some part of the work for htc passion same type cpu ( it helps ) same type of board.
If you get more people interested you can count with me.
hal_2000
Click to expand...
Click to collapse
please help us!
you can:angel:
...that I cannot explain and have no idea how to fix.
A while ago I've been getting pretty inexplicable build errors mentioned here and here. It took me a couple of days to realize that these issues were happening because of the multi-window cherry pick.
1. I would do a fresh sync, compare several of my local files in frameworks/base/core/java to those at Omni github repo, and everything would match,
2. then cherry pick multi-windows, and
3. revisit the same files in f/b/c/java, and they would be different from the Omni repo.
It felt as if the HEAD rolled back a couple of steps after the cherry pick.
Things are even worse today; this is a screenshot of my frameworks/base/packages after a fresh sync and before the cherry pick:
{
"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"
}
This is the cherry pick a moment later:
And this is another screenshot of frameworks/base/packages immediately after the cherry pick, with several folders missing (DocumentsUI, Keyguard, services etc):
Let me add that the small cherry picks, let's say in a device tree, are perfectly OK.
Would someone be kind enough to shed some light on this and offer a way to rectify the situation, please?
I have managed to persuade it to work with a little bit of git branching.
What I did was
1. rm -rf frameworks and resync
2. go to frameworks/base and cherry pick
3. git checkout -b widow™
4. repeat step #1
5. again drop into frameworks/base
6. git checkout -b main
7. git merge widow
And it worked.
I still don't know why it happens, though.
That's because:
1) You're using checkout instead of cherry-pick
2) You're not using "repo start"
Mostly 1)
Entropy512 said:
That's because:
1) You're using checkout instead of cherry-pick
2) You're not using "repo start"
Mostly 1)
Click to expand...
Click to collapse
Let me repost image #2 from the first post:
I started using branches as a workaround because simple cherry pick didn't work.
chasmodo said:
Let me repost image #2 from the first post:
I started using branches as a workaround because simple cherry pick didn't work.
Click to expand...
Click to collapse
Why are you reposting an image that confirms that you are using checkout instead of cherry pick?
?
It appears that you've clicked on "checkout" instead of "cherry-pick" in the gerrit patch summary.
Hi all!
I'm happy to say that, thanks to iovyroot, and with a lot of help from zxz0O0, we managed to create a new root tool for the Xperia M2, EagleRootTool, meaning we don't actually need to use Kingroot anymore to root LBL devices under latest Lollipop firmware :victory:
However, since this root binary is compatible with (probably) any kernel built before December 2015, I thought of making the tool compatible with some other devices, like your Z tablet, since it's actually very similar to my device.
Unfortunately, since this tool's based on some kernel-specific addresses, to make it compatible with other devices like the Z tablet, I need them from every single variant.
I'm going to take for reference all models and firmware build numbers from XperiFirm.
WHAT YOU NEED:
- An already rooted device in 10.7.A.0.228 (10.7.A.0.222 might be compatible too) (it doesn't matter if it was rooted by Kingroot, or via UBL methods).
- A little of Android general knowledge: Usage of ADB (mainly).
- Patience.
DEVICES:
- SGP311
- SGP312
- SGP321 ✘
- SGP351
HOW TO DO IT?:
Just open an ADB prompt and run a shell in it. Then, run the following commands, replacing the *location with storage/sdcard1 if you want to use your SD Card, or with data/media/0 if you want to use the internal memory.
Code:
su
cat /proc/version > /[COLOR="Purple"]*[/COLOR][COLOR="red"]location[/COLOR]/version.txt
echo 1 > /proc/sys/kernel/kptr_restrict
cat /proc/kallsyms > /[COLOR="Purple"]*[/COLOR][COLOR="red"]location[/COLOR]/kallsyms.txt
(remember to hit enter after each line of the above :silly
Now upload those two files (version.txt & kallsyms.txt) wherever you want, or attach them in your comment, saying which model they're from, and I'll add the required offsets to support your device manually!
________________________
DISCLAIMER: This is NOT a placeholder NOR Spam thread. I just want to help this device users to get them supported in a common Lollipop Xperia rooting toolkit, since this device won't get Marshmallow, and has a compatible kernel. If you, moderator or user, decide to close/report this thread, I may understand it, but think it twice before doing it.
Files in archive attached SGP311/321.
Rootk1t said:
SGP321 (.228) Files in archieve attached.
Click to expand...
Click to collapse
I'm sorry! This particular Xperia Z Tablet seems not to be supported.
Even though the kernel is valid, and technically vulnerable, it doesn't have present the ptmx_fops address in the kallsyms, so it won't be possible to make it compatible.
{
"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"
}
Thanks anyway for providing it!
@linuxct
I added files from SGP311. Check them, but 99% result will be the same as for SGP321.
Rootk1t said:
@linuxct
I added files from SGP311. Check them, but 99% result will be the same as for SGP321.
Click to expand...
Click to collapse
Yep, it's the very same as the other model. I must ask Dosomder what to do in this case.
Hi guys extremely excited to release this, as I was working hard on it. Now its time for you to make worth of it
I (KP) takes no responsibility for any fault or damage caused by using the MTK Tools. No warranties of any kind are given. Use at your Own Risk
Click to expand...
Click to collapse
{
"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"
}
WHAT IS THIS BASICALLY
This na guys,,,, this is a software guys.... LOL! Read Features You will get all the things, if then too not.... Then this is not right place for you ... (KIDDDING)
WHAT CAN YOU MAKE OUT FROM THIS
With This Tool you can easily able to hack into your phone with not an only ease process but also a simple gui interface tool for your phone. Give a try. If you like you can freely donate my work, so that i could make this site a an independent domain
FEATURES :laugh:
Check from here :fingers-crossed: lol..
TIPS TO USE IT :laugh:
1. Make sure while using any option move your cursor onto it, to display its information.
2. If toolkit suddenly doesn't respond, make sure you first End its process from task manager then contact me from the toolkit - that why this happen (log)
3. Do not jump onto the options quickly, wait till the first process gets over.
4. That's it, ENJOY
Please install the ToolKit to the root folder on your PC if possible.
For example C:\MTK-Tools or D:\MTK-Tools
If you install it to a folder with brackets or special characters in the filename such as C:\Program Files (x86)\ then it may cause certain processes in the ToolKit to fail.
If you already have the Toolkit installed and want to update it, just open MTK Tools.exe and then Select Help tab to check for updates. If updates are available it will be automatically downloaded.
There have been reports of the Toolkit not working properly if the User Account name is very long or contains special characters so be aware if you have problems.
SCREENSHOTS ::
All Views And Downloads HERE
HIT THANKS ,, AND DONATE ,, WOULD BE APPRECIATED HERE :angel:
Great Work done bro, it would be of much help and time limiting to/for the noons..
Well-done bro.
iykeDROID™ said:
Great Work done bro, it would be of much help and time limiting to/for the noons..
Well-done bro.
Click to expand...
Click to collapse
Thanks bro...