This is a port of Ubuntu for Phones for the Xperia S.
THIS IS VERY EXPERIMENTAL STUFF. NOTHING REALLY WORKS AS OF NOW. THIS IS MEANT FOR DEVS ONLY.
It's based on my own sources and kernel. Those can be found at:
https://github.com/OpenSEMC
Also the sources for Ubuntu are at:
http://phablet.ubuntu.com/gitweb
PLEASE DO A NANDROID BACKUP BEFORE INSTALLING THIS ROM.
THIS NEEDS AN UNLOCKED BOOTLOADER.
Installation instructions:
* Wipe data
* Install the device specific part of Ubutnu
* Install the generic Ubuntu part
* Reboot
* Enter the following commands:
Code:
adb root
Code:
adb shell
Code:
ubuntu_chroot shell
Code:
ubuntu-session
--- Enjoy the testing! ---
Screenshots:
Coming up
Download links:
Device specific: http://goo.im/devs/RaymanFX/downloads/Ubuntu-Touch/ubuntu_quantal-nozomi-0.0.0.zip
Generic: http://cdimage.ubuntu.com/ubuntu-to...current/raring-preinstalled-phablet-armhf.zip
Working:
Ubuntu Touch Quantal System
Touchscreen
Team Win Recovery Project (TWRP) - (Backup & Restore fixed)
WiFi
Untested:
Audio
Bluetooth
Video
HWA
GPS
Mobile Data
Not working:
RIL - Ubuntu related
Some apps - Ubuntu related
Lots more probably
Information:
DO NOT POST BUGREPORTS! THIS IS NOT IN A PUBLIC TESTING STAGE!
The Ubuntu Touch system is currently in developer-preview state, just to give you an idea of how incomplete this is.
My build sources may be broken; either get along with it or wait for me to fix it.
I am the only one working on this. If anybody is capable of helping, PM me.
Some general notes
1) Do not flash any other kernel with this; there are no compatible ones as of now.
2) This will NOT wipe your internal storage; all your media files and things on /sdcard are secure!
3) There are random lockups bringing you to the lockscreen; you have to unlock again.
4) In case you missed it: I am the official Ubuntu Touch developer responsible for the Xperia S. Intel: https://wiki.ubuntu.com/Touch/Devices/nozomi
Developers only
Bring down the source code for the Nozomi with the following command:
Code:
repo init -u git://github.com/OpenSEMC/android.git -b cm-10.1-ubuntu
Code:
repo sync
Building the source:
Code:
. build/envsetup.sh
Code:
brunch nozomi
Hanging on the Edge of my seat
Sony Xperia S Devs are remarkably one of the best devs here in XDA.. Keep it up guys..
Sv: [DEV][WiP] Ubuntu Touch - Nozomi
There surely comes a lot of new stuff keep it up
Sent from my Xperia S using xda app-developers app
Awesome...gonna try it this weekend...
Sent from my Xperia S using xda app-developers app
This is an absolute marvel of a feat... Great job RaymanFX. You sir, deserve a bow....
Sent from my Xperia S using xda app-developers app
nice work!
though i am unclear about the
RaymanFX said:
1) Do not flash any other kernel with this. EVER.
Click to expand...
Click to collapse
part
waht do u mean exactly?
DooMLoRD said:
nice work!
though i am unclear about the
part
waht do u mean exactly?
Click to expand...
Click to collapse
Possibly that the device won't boot?
Man you're the best, you have done so much for the XS .:fingers-crossed:
DooMLoRD said:
nice work!
though i am unclear about the
part
waht do u mean exactly?
Click to expand...
Click to collapse
Ubuntu Touch needs a few specific kernel patches, which Android kernels don't have.
If flashing another kernel, which was not explicitly designed for Ubuntu, ghost bugs will appear; bugs that aren't related to the releases; but to custom kernels. Basically; not to confuse other people, I could remove the 'ever'. If there should be some other Ubuntu kernel designed for the Xperia S (which I highly doubt, though), it could be flashed; just like on android releases.
By the way, I do not know which capabilities you have (never worked with you), but if you have some time in the future, how about joining me? From the work you did (and you signature, lol) I can guess you quite have some experience with Android/Linux, that's why I ask.
RaymanFX said:
Ubuntu Touch needs a few specific kernel patches, which Android kernels don't have.
If flashing another kernel, which was not explicitly designed for Ubuntu, ghost bugs will appear; bugs that aren't related to the releases; but to custom kernels. Basically; not to confuse other people, I could remove the 'ever'. If there should be some other Ubuntu kernel designed for the Xperia S (which I highly doubt, though), it could be flashed; just like on android releases.
By the way, I do not know which capabilities you have (never worked with you), but if you have some time in the future, how about joining me? From the work you did (and you signature, lol) I can guess you quite have some experience with Android/Linux, that's why I ask.
Click to expand...
Click to collapse
i thought u ment we cant flash any kernel after flashing this kernel
well about my capabilities... tricky question... have a decent idea about linux, android... mostly involved in rooting, custom recovery creation, kernel development... average knowledge about roms... and i guess thats about it...
about working with you... i am always there to help anyone serious enough in developing for any device (specially Xperia)... for now i am **** busy with submissions and studies... but hopefully soon i should be free.. then can dedicate more time to development...
I test it soon. Thx
Sent from LT26i 4.2.2
Good job Rayman. And good luck!
Thank you.
awesome work! ive got it running now and wifi works, i love it thanks....
Testing it now too :
Small report :
WiFi : OK
Video :NOK (Youtube and local)
Mobile Data : NOK
Camera : NOK
HWA : Untested
GPS : Untested
Audio : Untested
Bluetooth : Untested:
laugh: :good:
Nice work to boot it
Great!Do you know that you are really doing an amazing work!Thanks!
Sent from my Xperia S using xda app-developers app
penta42 said:
Testing it now too :
Small report :
WiFi : OK
Video :NOK (Youtube and local)
Mobile Data : NOK
Camera : NOK
HWA : Untested
GPS : Untested
Audio : Untested
Bluetooth : Untested:
laugh: :good:
Nice work to boot it
Click to expand...
Click to collapse
Did you have any problems to install?
When I type "adb shell", I have this error:
- exec '/system/bin/sh' failed: No such file or directory (2)
We're going crazy awaiting some screnshots
Great Work Dude.
It's nice to see Dev like you care for us.
I will wait for the stable version.
BTW, is it true that Ubuntu will not let us Dual Boot Ubuntu Touch Officially?
I like Ubuntu but I can never leave Android.
So, is it possible to Dual Boot Ubuntu?
Related
UPDATE statement.
As original author for this thread, videos and first demos, I'm not currently working on the Gingerbread port these days (heavily busy working on Voodoo sound improvements).
It doesn't mean I lost interest in it, only that I miss time at the moment.
CyanogenMod team work on a serious port of Gingerbread for Galaxy S, witch won't be just a technical demo like the original spirit of this one.
Of course, such goal requires a lot of work, dedication, and also some calm.
There is a lot of natural interest about Gingerbread on Galaxy S, and it's perfectly understandable too.
Giving an ETA until the porting work is done or some major advance is made would be dishonest.
It means that not asking for ETA will be appreciated. However, you're welcome discussing other aspects.
If you want more technical insights and a few updates by most actives developers for this port, i would recommend to follow:
http://twitter.com/CMSGSTeam
http://twitter.com/codeworkx
http://twitter.com/dumdidum
[list needs to be completed, thanks for input]
Thank you!
Original post:
Galaxy S with Nexus S kernel - Booting Nexus S Android Gingerbread
Videos are here:
http://www.youtube.com/supercurioxda
Early demo Releases - V6
Requirements
You must be root on your phone
Your /data must be converted in Ext4 by Voodoo lagfix or another Ext4 lagfix.
Verizon Fascinates are not yet supported - Epic4G will require a lot more development.
You must have proceed to complete backups before
Some busybox installation is also useful for tar.
Another Important note
Be sure you have access to the download mode using the 3 buttons combination.
If you don't, it will be extremely difficult (even if in theory not impossible) to to flash another kernel back.
Steps:
1/ Download this system dump on your sdcard:
system dump archive
2/ Run these commands
Code:
adb shell
su
cd /data
mkdir gingerbread
cd gingerbread
busybox tar zxvf /sdcard/system-dump-as-root.tar.gz
busybox cp -a /efs efs
sync
reboot download
3/ unzip the attached nsonsgs.tar.zip to nsonsgs.tar
4/ flash the kernel with Odin or Heimdall - no pit - no re-partition
Watch Gingerbread boot on your phone !
How do I get back?
Everything is still in place on your phone - no harm done.
All you need to do is to flash your preferred custom (that support Ext4 obviously) Kernel back on your phone
What's about this port:
- It uses the Nexus S kernel compiled from sources
- It runs the exact /system image release, we dumped on IRC from an actual Nexus S device.
Am i French ?
Now you don't have any doubt anymore
Which filesystem ?
This early preview runs on Ext4. no RFS at all, the kernel don't support RFS.
Does everything work ?
Nope, but there are progresses.
Don't work: GPS / Voice / camera
Work: everything else: like sound, GL acceleration etc
Will it work ?
I think most of it will work after countless hours spent on it.
Is it flashable with Odin ?
Won't be so easy, but it's one of the goals
Do you work alone ?
Credits go the IRC channel #NSdev on freenode, and now a team formed regrouping most Captivate/Vibrant/Fascinate/I9000 developers and CyanogenMod team, with Kernel and ROM developers and also newcomers.
When will this/that work ?
The only honest answer is: there is no answer.
Please don't ask for ETA, don't pressure developers, they need peace of mind
Is this Open Source ?
Everything is fully published under an open source license
Latest initramfs: https://github.com/project-voodoo/nsonsgs-initramfs
Kernels: https://github.com/galaxys-kernel
Who are the actual contributors to the code?
For the kernel, you can follow works here : who / when.
https://github.com/galaxys-kernel/linux_samsung_galaxys_port/commits/galaxys-port
As it is a team work, sometimes it's not the guy who had the idea who commits the code, but still
Articles:
http://www.engadget.com/2010/12/18/samsung-galaxy-s-receives-gingerbread-port-right-from-the-nexus/
http://briefmobile.com/samsung-galaxy-s-android-2-3-gingerbread
And a lot of other ones now!
Versions:
V6
- Easy root. You only need to install Superuser app from Market.
Downloads :
Kernel you can flash with Odin / heimdall / kernel flashing apps
ClockWorkMod unsigned update.zip
V5
- Wifi semi-working (tend to crash the phone on Wifi sleep timeout)
- Calls working but no DATA for me (coolya had data, which means: erratic) - voice not tested.
- kind of laggy, but there is a lot of headroom.
- GPS working only by Wifi/Triangulation networking - No satellites.
Fantastic job by coolya who did most of the advancement, for Wifi, baseband and also OneDRAM partitions configuration. Really really awesome work.
We were so lucky the snow forced him to stay at home instead of going to work
This time you can really start to play with the phone, install apps, surf on the Internet all this with Gingerbread! kind of cool
V4
Buttons fixed thanks to the contributions of xcaliburhands, pawitp, fenfir
No need to create some directories manually anymore.
Kernel available as ClockWorkMod recovery update.zip - be sure you have access to 3 buttons !
V3
SDcard now works
- As internal storage
- As USB storage
V2
improved pre-init script and mounts:
no more insufficient space
improved dual-boot solution
faster boot
faster disk I/O
V1
initial
Edit: we started working now as a team, joining XDA forces with CyanogenMod.
Gingerbread CM is AOSP, which means the port will be the real Google experience, using clean source modified just as we need to.
Holy moly..... I can't wait! Thanks Curio (and any other devs)!
I wonder how fast this ROM will be! 2.2.1 is smooth as butter as it is!
That was quick! I saw the title before saw who posted I thought it was just going to to someone asking for eta's... Nice work!
LOL are u serious? Doc was trying to run it the other day but couldn get pass the boot screen haha
Let's wait patiently for the port, and let the dev do his work.
Sent from my GT-I9000 using Tapatalk
Will this port be only for a specific sgs? For instance the Captivate perhaps.....
Sent from my GT-I9000 using XDA App
We're waiting...
heymanator said:
Will this port be only for a specific sgs? For instance the Captivate perhaps.....
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Patience, it will come to all in time
Sent from my GT-I9000 using XDA App
heymanator said:
Will this port be only for a specific sgs? For instance the Captivate perhaps.....
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
What works on one GSM Galaxy S works on every GSM Galaxy S with only minor tweaks.
Time to dust off my i9000 and get it out of the drawer.
why was it in the drawer?
boodies said:
why was it in the drawer?
Click to expand...
Click to collapse
Cause I was fed up GPS not working among other things... been using my Desire for about 6 weeks. Boy, definitely missed this screen, and Swype... but not the lag.
I want the package more than the video!
I think I just wet myself!
in other words this means that we can brag about having non banana shaped nexus s´es with sd-card slot... sweet...
Red John said:
Cause I was fed up GPS not working among other things... been using my Desire for about 6 weeks. Boy, definitely missed this screen, and Swype... but not the lag.
Click to expand...
Click to collapse
If your GPS doesn't work and you have lag then it is your fault for being too lazy to fix it
Sent from my GT-I9000 using XDA App
TettZor said:
in other words this means that we can brag about having non banana shaped nexus s´es with sd-card slot... sweet...
Click to expand...
Click to collapse
That made my day lol
Sent from my GT-I9000 using XDA App
TettZor said:
in other words this means that we can brag about having non banana shaped nexus s´es with sd-card slot... sweet...
Click to expand...
Click to collapse
HAHAHA I'm hoping Samsung hire some of these devs! And I guess there's not much use of a "Nexus S" now that the Galaxy S is able to run what the Nexus S runs.
Waiting waiting.....
Sent from my bad-ass i9000
Looks like it will be out later.
supercurio François Simond
But I guess that in about than 1 day I will publish a method, and you will be able to boot #Android #Gingerbread on your #GalaxyS
1 hour ago Favorite Retweet Reply
»
François Simond
supercurio François Simond
Ok the video will come later, no ETA
1 hour ago Favorite Retweet Reply
ICS for Galaxy Tab 7
**PLEASE READ THE ENTIRE POST BEFORE FLASHING!**
Before you flash, Do an NANDroid backup, and then you can use an app called "App Extractor" to restore your important apps (Or you can use TB).
Changelog is in the second post
Supported Versions for GSM networks:
• P1000
• P1000N
• P1000L
• P1000R
Supported Versions for CDMA networks:
The CDMA kernel isn’t perfect at the moment, but it does work, so your tab won’t be bricked if you flash the right kernel, you'll just have more issues!
• Verizon
• Sprint
Not Supported:
P1010 (Wi-Fi only tab).
Current version:
Alpha 3
Developers:
Angel_666
koxudaxi
cdesai
cheatman
humberos
Working features:
• Reverse tethering- http://forum.xda-developers.com/show....php?t=1371345
• External SD
• Sound
• Multitouch
• Orientation sensor does work, but with a delay (you need to enable it in settings)
• Wifi
• Root
• 3G
Not Working:
• Camera doesn’t work yet, and won’t anytime in near future, due to great changes in ICS. We’d have to either write of wrapper or find some other workaround
(although it does work in panorama mode)
• Bluetooth
•
Notes:
• Touch buttons can be enabled if you want, (ro.product.characteristics=tablet in build.prop).
• Once you have a file manager installed, you can install app the normal way
• Honeycomb tablet apps works.
• Apparently you can boot this on CDMA sprint tabs as well (very long boot time at first) and P1000R!.
• If you can't get Wi-Fi to work, check here how to: http://forum.xda-developers.com/show...postcount=1175.
If you've got any questions, post them here(thanks joethc): http://webchat.freenode.net/?channels=##galaxytab7-ics.
FAQ:
Q: Keyboard not showing up:
A: Change dpi to 160 in build.prop and click on small keyboard icon and slide physical keyboard off
Q: I've got no root?
A: Flash the root at bottom of post (thanks cheatman), or
http://forum.xda-developers.com/show...&postcount=262,
Then add the sh.zip (at bottom of page) file via adb to the /system/bin folder of this device.
Thanks to sinamosavi for root!
Q: Issues with apps and/or settings:
A: WIPE DATA, THEN SEE, IT WORKS PERFECT!
Install Guide(Make sure you are on ext4 file format and gingerbread bootloaders!):
• Plug Tab into computer.
• Mount USB storage.
• Copy ICS ROM to SD Card.
• Reboot into recovery.
• Perform a ROM backup.
• Optional, but recommended: Wipe data (if you don't wipe, wait for some time on home screen for the old data to work fine with the new rom).
• Wipe the dalvik-cache.
• Flash ICS ROM.
• Reboot.
• Flash the kernel depending on your tab, (thanks to humberto for this!)
• Flash the root patch and then then the Wi-Fi patch.
• Reboot.
Enjoy!
Downloads:
Alpha Series:
• Alpha 1:
http://depositfiles.com/files/qf2yahrb0?
http://www.megaupload.com/?d=Q9EY9U38
• Alpha 2:
ftp://xda:[email protected]
• Alpha 3:
http://depositfiles.com/files/xhhvucq67
ftp://xda:[email protected]
Kernels:
http://forum.xda-developers.com/show...&postcount=544
Other Stuff:
Google apps: http://minus.com/mbgPLHnlmN#2
Kernels:
P1000
http://www.multiupload.com/I0GAWLNFKF
sha1sum: 256d530f84b61a00897c2dc0a6db45ab3dd083d0
==================================================
P1000L
http://www.multiupload.com/5T54ROP1L7
sha1sum: b1b9e545f092e9017eea8b6c3a68aa060b2a4d77
==================================================
P1000N
http://www.multiupload.com/XNP7QZJJVO
sha1sum: 7aba6a545c153cc5cf2b8c9e8b9587bdb4a30891
==================================================
CDMA
http://www.multiupload.com/8C0RV66449
sha1sum: 483a64214a054629f57ab75d2861e8ea9c8a5fe7
==================================================
Sources (CM9 Kernel)
https://github.com/sgt7
Changelog: https://github.com/sgt7/p1000-kernel-cm9/commits/master
Look at the attachments for additional files
Added the build.prop if any1 wanted to modify!
Enjoy the rom!
Please rate this ROM 5 stars and hit the thanks button if you like it!
Special thanks to:
koxudaxi
Angel_666
cheatman
dizgustipated
cdesai
woocashewski
joethc
humberos
mssmison
speedsilwady
{Diemex}
d2dyno
Changelog
CHANGELOG
Alpha 1:
Touchscreen works
Everything else doesn't work.
Alpha 2:
Works:
3G works for some
Sounds and effects
GSM
Camera
Alpha 3:
Works
Mobile data work (works fully now!)
External/internal storage automount
Orientation sensor works (sometimes )
Phone
Wifi (see patch)
Root(see patch)
Alpha 4:
In progress!
What doesn't work:
GPS
Bluetooth
HW Accelaration (not just smooth gui!)
multitasking button
everything else...
ani55 said:
If anyone wants to help, please PM me for files and stuff
Sent from my GT-P1000 using XDA App
Click to expand...
Click to collapse
https://github.com/dizgustipated
For devs : http://forum.xda-developers.com/showthread.php?t=1313337
We need to edit the boot.img and init.rc first. I can't do this today so will do tomorrow if I can.
Sent from my GT-P1000 using XDA App
Even though nexus one has fully working build, I chose to port from nexus a as it has same processer and other similar hardware
Sent from my GT-P1000 using XDA App
To help devs, download nexus s rom then download cm7 by technomancer and unzip it. Extract the boot.img with splitbootimg.pl script. Compare the init.rc to ICS init.rc. Specifically the most important part here is the PATH, LD_LIBRARY_PATH statement and BOOTCLASSPATH lines. Build your kernel with the updated init.rc and flash with heimdell.
From mssmison porting guide.
I am in no way responsible for anything that happens to your Tab
Sent from my GT-P1000 using XDA App
Help! Guys, any developers:
When i try to split technomancer's cm7 boot.img in terminal, it says:
Android magic not found. Giving up.
Yet when I do this with nexus s ics it splits it, so until unless I can't change the init.rc we can't even build a kernel. Please help, anyone!
If someone can split the cm7 boot.img for me it would help a lot!
Thanks!
Best for you is to try to download Techno Heimdal version and extract initramfs from zimage, check here .
Good luck.
ani55 said:
Help! Guys, any developers:
When i try to split technomancer's cm7 boot.img in terminal, it says:
Android magic not found. Giving up.
Yet when I do this with nexus s ics it splits it, so until unless I can't change the init.rc we can't even build a kernel. Please help, anyone!
If someone can split the cm7 boot.img for me it would help a lot!
Thanks!
Click to expand...
Click to collapse
yea the cm7 boot.img wont split, me n diz already working since days, just synced cm7 source and now gonna make a new kernel with the edit, zImage doesnt work, needs boot.img
af974 said:
Best for you is to try to download Techno Heimdal version and extract initramfs from zimage, check here .
Good luck.
Click to expand...
Click to collapse
But then I can't compare that with the ICS rom
Sent from my GT-P1000 using XDA App
I am looking for someone with good porting knowledge who can check my build prop.
Looking at it right now
EDIT: Ok,it should be fine
dariolob said:
Looking at it right now
EDIT: Ok,it should be fine
Click to expand...
Click to collapse
Cool, but in the mssmison guide, he says something about the propiertray files. What do I do with these?
Thanks dario
hi, ani55
it's good project to make sure a possibility of Galaxy Tab
Have you build a kernel and ROM ?
you should edit init.rc in initramfs which have other block device names.
if i help you , i will happy
dariolob said:
Looking at it right now
EDIT: Ok,it should be fine
Click to expand...
Click to collapse
How does it know the resolution of my screen and the cm7 one. Because in your hc build prop( which is a lot more organised) It has resolution and everything?
koxudaxi said:
hi, ani55
it's good project to make sure a possibility of Galaxy Tab
Have you build a kernel and ROM ?
you should edit init.rc in initramfs which have other block device names.
if i help you , i will happy
Click to expand...
Click to collapse
Thank you very much, hopefully we will then release a test version.
Quick note, make sure that the new kernel/initrdfs uses the proper new class statements in the *.rc files, there's been a change to that.
Secondary, getting the system to boot isn't terrible once you have the right class statements and new services loading in the init.rc. There will be challenges however with networking due in part I beleive to the sdk build most are sourced from.
I spent some time playing with it the other day, and waiting for the source is the best idea. You'll probably get it booting, but would want to have the source to make some of the changes requried to really get it working more than 80%.
I totally appluad you guys for starting on this though Good to see.
mssmison said:
Quick note, make sure that the new kernel/initrdfs uses the proper new class statements in the *.rc files, there's been a change to that.
Secondary, getting the system to boot isn't terrible once you have the right class statements and new services loading in the init.rc. There will be challenges however with networking due in part I beleive to the sdk build most are sourced from.
I spent some time playing with it the other day, and waiting for the source is the best idea. You'll probably get it booting, but would want to have the source to make some of the changes requried to really get it working more than 80%.
I totally appluad you guys for starting on this though Good to see.
Click to expand...
Click to collapse
Get mssmison, good to see you back! I am following your porting guide, but is the build.prop the only thing that you need to edit when you port from device to device.
Btw I am porting from nexus s.
Sent from my GT-P1000 using XDA App
has anyone tried the kernel from the HC build? Just a stab in the dark but that could at least provide a starting point
Im also starting to take a look at this but im more of higher level software guy
I need someone to build a kernel please
Sent from my GT-P1000 using XDA App
Advanced Stock ICS Kernel for Xperia SHere is a kernel based on the Stock ICS kernel with some features which come from DoomLord's GB kernel.
Features
autorooting
CWM recovery (with reboot recovery support)
init.d support (thanks DoomLord)
TUN/TAP driver
Download links
Build 17 (Fastboot)
Build 17 (CWM)
Build 16 (Fastboot)
Build 16 (CWM)
Prerequisites
An unlocked bootloader: Tuto here.
A stock ICS ROM (6.1.A.0.452 to 6.1.A.2.55). Don't expect this kernel to work with CM9/10.
How to flash
For elf files :
Read DoomLord's guide
You just have to replace kernel.elf by the name of the downloaded kernel in the flash command (eg : ics4.elf)
For zip files:
Flash the zip file from the recovery
Changelogs
Build 17 (08/12/12) :
Merge 6.1.A.2.55 kernel sources
Autodetect rom version in default.prop based on build.prop
Updated recovery, adbd and busybox (JB version)
Build 16 (01/11/12) :
Random reboot issue probably fixed (patch from CM10 kernel, thanks Kali)
Rom version increased to 6.1.A.2.50
Updated recovery, adbd and busybox (JB version)
SD card mounted by default in recovery
Vibration at boot removed, only led and backlight now
Build 15 (05/09/12) : Increase ROM version in default.prop from 6.1.A.0.452 to 6.1.A.2.45
Build 14 :
New MMC driver (from codeaurora) : it fixes issue while formatting partitions in CWM
Wifi module built from source (in the ramdisk)
Updated recovery
Disable again hardware clock
Build 13 :
Backup / Restore fixed with dedupe
Backlight enabled in CWM
Better "reboot recovery" handling in adbd / busybox and recovery
Build 12 :
Updated recovery
Hardware clock correctly saved (from CM9 kernel)
Build 11 : Go back to GCC 4.4 (fix artifacts with camera preview)
Build 10 :
Kernel built with GCC 4.6
Several autoroot fixes (Superuser app pushed just once and correctly removed in /data)
Working reboot recovery command (with adb too)
Updated su (3.1.1) and Superuser (3.1.3)
A bunch of new command included in the new busybox (ifconfig, wget, vi, and many more !)
Build 9 :
Kernel built from sources
TUN/TAP driver included (for VPN)
Build 8 : Fix mass storage in CWM
Build 7 : Fix MTP
Build 6 : Key mapping in CWM fixed
Build 5 :
New recovery built from latest CM9 sources
Fixed generation of md5sum with nandroid
Increased font size in CWM
Boot partition backup and restore
New adbd built from CM9 sources (fixed an issue with hardcoded sh path in /system)
Build 4 :
Correct su binary
Don't wait 3 sec if /cache/recovery/boot exists
Build 3 :
Leds and vibrator at startup fixed
Sources
Ramdisk sources
Kernel sources
Credits
DoomLord : many thanks to him for its kernel and all his scripts.
championswimmer and sminki for their help
FreeXperia team for their work on CM
makes it perfectly start does not make any errors
greetings and thanks
yes it boots!
(maybe you can help with my Question here )
Hey, I also have tested several times to include recovery, but withut succes, didn't get any further then a booting kernel without recovery or vibration and LED on to enter recovery but no entering recovery and kernel that doesn't boot.
Please pm me if you want to work together, I saw your kernel is from ICX team? I know nick very well so I'd would be a pleasure to work with you too
sminki said:
yes it boots!
(maybe you can help with my Question here )
Click to expand...
Click to collapse
for this question and any other other question similar to this
head here
http://forum.xda-developers.com/showthread.php?t=1659584
it has menu driven process to extract and repack kernel.elf (ramdisk also can be extracted and packed )
Welcome Champ, good to see you mate.
I will leave the thread here as knowing you, you will have a kernel ready for us in a few hours.:fingers-crossed:
thanks for the test guys... so now i'm diving into including recovery....
good to know i could pull off kernel.elf editing in my first attempt lol
@colossus if not in hours, then definitely within 1 or 2 days
EDIT :
can someone send me the kernel.elf from FXP122 cm9 ??
will save me the time to download the whole ROM
This is sweet, good job!!
john9 said:
This is sweet, good job!!
Click to expand...
Click to collapse
Only a few files to edit now
We'll keep you updated
Sent from my LT26i using XDA
championswimmer said:
btw if anyone wishes to do this before me,
this diffstats should help you
https://github.com/championswimmer/xps-ramdisk/commit/a61969aefca00ce3a6e4e112e97403fb6f0c79e9
it shows how doomlord added recovery to gb kernel..
Click to expand...
Click to collapse
cool.. well that's a hell of a lot easier than the manual route I was taking. This was my goal, but for personal rather than pseudo "xda glory" as I'm working with DooM's stuff I didn't feel right posting it without his permission, but he's probably too busy to care
go for it championswimmer :victory:
Excuse my noob-ish question, but... what's the difference between a 'stock' kernel with recovery and a completely custom kernel like DoomLord's? Is it to do with core frequencies/governors?
fNOOB said:
Excuse my noob-ish question, but... what's the difference between a 'stock' kernel with recovery and a completely custom kernel like DoomLord's? Is it to do with core frequencies/governors?
Click to expand...
Click to collapse
Frequencies and governors are one possible customicing for kernels, for the most users the most important thing. also Kernel modifing can allows you init.d support, undervoltscripts and also allows (or denies) MSC support... and, for shure, clean out some tings, make things more efficiently and and and... a dev is nearly totaly free to create a very customiced kernel with or without special Driver support or so
noob.fl said:
Frequencies and governors are one possible customicing for kernels, for the most users the most important thing. also Kernel modifing can allows you init.d support, undervoltscripts and also allows (or denies) MSC support... and, for shure, clean out some tings, make things more efficiently and and and... a dev is nearly totaly free to create a very customiced kernel with or without special Driver support or so
Click to expand...
Click to collapse
Cheers mate
sminki said:
cool.. well that's a hell of a lot easier than the manual route I was taking. This was my goal, but for personal rather than pseudo "xda glory" as I'm working with DooM's stuff I didn't feel right posting it without his permission, but he's probably too busy to care
go for it championswimmer :victory:
Click to expand...
Click to collapse
using someone's work just because 'he's too busy to care' is not the aim which we at xda strive for ...
i've already talked with Doomlord regarding using his recovery... and as long as I clearly mention it's his work and provide links back to his thread, he has no issues with anyone else using it...
(and i'll surely do that ^^ when i release a kernel containing his recovery, if i ever do that)
championswimmer said:
using someone's work just because 'he's too busy to care' is not the aim which we at xda strive for ...
i've already talked with Doomlord regarding using his recovery... and as long as I clearly mention it's his work and provide links back to his thread, he has no issues with anyone else using it...
(and i'll surely do that ^^ when i release a kernel containing his recovery, if i ever do that)
Click to expand...
Click to collapse
cool, i was only making a bad joke, we all know DooM cares
sminki said:
cool, i was only making a bad joke, we all know DooM cares
Click to expand...
Click to collapse
lol.. ok
and i'll bring you some unicorns soon
championswimmer said:
lol.. ok
and i'll bring you some unicorns soon
Click to expand...
Click to collapse
I can't wait! :victory:
so this kernel has the ro.secure property in default.prop set to 0??
Tnaks mate for your job!
tested right now the test version and the sony logo fades and reboots
can you plug it into a pc and run a logcat from command prompt and give me the output of any comes??
Main thread + features + install instructions + dev support
http://forum.xda-developers.com/showthread.php?t=2201860
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
Download links
Last version can be found here:
Sony Xperia Z1 (honami)
http://goo.im/devs/philz_touch/CWM_Advanced_Edition
Click to expand...
Click to collapse
Big credits to @DooMLoRD for his help to rebase on stock kernel
XDA:DevDB Information
[honami][CWM Advanced Edition] PhilZ Touch, a Tool/Utility for the Sony Xperia Z1
Contributors
Phil3759, DooMLoRD, [NUT]
Version Information
Status: Testing
Created 2014-03-29
Last Updated 2014-03-29
hello and thank you.
I have found the file. img I can not find my method for installing or flashed to the files on my Z1.
sorry i use google translation I'm French
Français
bonjour et merci . j'ai bien trouvé le fichier .img mes je ne trouve pas la méthode pour l installer ni pour flashé le fichiers sur mon Z1
Bien cordialement
Xque_31
Envoyé de mon C6903 en utilisant Tapatalk
Phil3759 said:
Main thread + features + install instructions + dev support
http://forum.xda-developers.com/showthread.php?t=2201860
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
Download links
Last version can be found here:
Click to expand...
Click to collapse
hi @Phil3759,
firstly welcome to the Z1 forums!
the kernel image you posted will not boot on any device as it misses the crucial device tree files... here are detailed instructions on how to build bootable kernels for many Xperia device since 2011:
http://forum.xda-developers.com/showthread.php?t=2447310
I have fixed this by integrating the ramdisk with stock FW 290 (android 4.3) so that people can test out this recovery..
download link for fixed image is:
http://d-h.st/Iz2
BTW me and my colleague @Napstar have worked on similar "Advanced recovery" before (it was released some time in late 2011/early 2012):
our sources have also been released quite some time back:
http://forum.xda-developers.com/showthread.php?t=1485829
but i discontinued work on it as i got busy with personal work
I would recommend getting in touch with @Napstar, may be we can collaborate for some bigger things
also another thing... since I have worked on multi-recoveries in my kernels, i had 4 recoveries in my X10 kernel way back in septmber 2011!!, and since you are actively developing this advanced recovery, do i have your permission to integrate this recovery in my DooMKernel? (I have made my DooMKernel for close to 21 devices from various vendors Sony, HTC, Samsung, Huawei, Kindle, etc; currently I actively support only 4 devices though: Xperia Z1, Z, SP & T)
note to users:
if you want to test out this recovery then you need to HOTBOOT this kernel:
Code:
fastboot boot kernel.img
regards,
DooMLoRD
DooMLoRD said:
hi @Phil3759,
firstly welcome to the Z1 forums!
the kernel image you posted will not boot on any device as it misses the crucial device tree files... here are detailed instructions on how to build bootable kernels for many Xperia device since 2011:
http://forum.xda-developers.com/showthread.php?t=2447310
I have fixed this by integrating the ramdisk with stock FW 290 (android 4.3) so that people can test out this recovery..
download link for fixed image is:
http://d-h.st/Iz2
BTW me and my colleague @Napstar have worked on similar "Advanced recovery" before (it was released some time in late 2011/early 2012):
our sources have also been released quite some time back:
http://forum.xda-developers.com/showthread.php?t=1485829
but i discontinued work on it as i got busy with personal work
I would recommend getting in touch with @Napstar, may be we can collaborate for some bigger things
also another thing... since I have worked on multi-recoveries in my kernels, i had 4 recoveries in my X10 kernel way back in septmber 2011!!, and since you are actively developing this advanced recovery, do i have your permission to integrate this recovery in my DooMKernel?
note to users:
if you want to test out this recovery then you need to HOTBOOT this kernel:
Code:
fastboot boot kernel.img
regards,
DooMLoRD
Click to expand...
Click to collapse
Many thanks for your support
Yes, I looked at your amazing work. TWRP-ifying CWM is just amazing
However, the codes we use diverge too much, but yes, why not, collaboration can be always welcome. It just take a big effort to start so that each one familiarizes with other's code
Obviously you can use and repack any of my files to your wish
I also should added a note that this is a sample for devs to use it at their wish, like I do for Xperia Z. I knew well that it won't boot any stock ROM. Thought it would boot cm-11.0 roms though...
Anything I have to do when compiling to make it at least boot cm-11.0?
If you agree, I will add your recovery.img to goo.im instead of actual one + add full credits in OP
Phil3759 said:
Many thanks for your support
Yes, I looked at your amazing work. TWRP-ifying CWM is just amazing
However, the codes we use diverge too much, but yes, why not, collaboration can be always welcome. It just take a big effort to start so that each one familiarizes with other's code
Obviously you can use and repack any of my files to your wish
I also should added a note that this is a sample for devs to use it at their wish, like I do for Xperia Z. I knew well that it won't boot any stock ROM. Thought it would boot cm-11.0 roms though...
Anything I have to do when compiling to make it at least boot cm-11.0?
If you agree, I will add your recovery.img to goo.im instead of actual one + add full credits in OP
Click to expand...
Click to collapse
well @Napstar is currently working on something new please get in touch with him, he is busy with his PhD work but I am sure he can find out some time
it wont even boot on any Z1 irrespective of ROM... actually the kernel formats for Sony devices vary A LOT! they are not using standard boot.img format... and anyways especially for the msm8974 board (and beyond) the new device tree format will be used... its a bit tricky to explain but Krab has a good tutorial here:
http://forum.xda-developers.com/showthread.php?t=2469421
sure go ahead... u can link the recovery.img where ever u want i just repacked ur ramdisk with the correct zImage & dt.img
Phil3759 said:
Many thanks for your support
Yes, I looked at your amazing work. TWRP-ifying CWM is just amazing
However, the codes we use diverge too much, but yes, why not, collaboration can be always welcome. It just take a big effort to start so that each one familiarizes with other's code
Obviously you can use and repack any of my files to your wish
I also should added a note that this is a sample for devs to use it at their wish, like I do for Xperia Z. I knew well that it won't boot any stock ROM. Thought it would boot cm-11.0 roms though...
Anything I have to do when compiling to make it at least boot cm-11.0?
If you agree, I will add your recovery.img to goo.im instead of actual one + add full credits in OP
Click to expand...
Click to collapse
here is a bonus for you...
build tools for honami...
http://d-h.st/Vk3
just extract the archive, replace the ramdisk.cpio.gz with new compressed ramdisk and run makeit.sh
that should build a bootable boot.img for Z1 (honami)
DooMLoRD said:
here is a bonus for you...
build tools for honami...
http://d-h.st/Vk3
just extract the archive, replace the ramdisk.cpio.gz with new compressed ramdisk and run makeit.sh
that should build a bootable boot.img for Z1 (honami)
Click to expand...
Click to collapse
That's a lot
I will take a look at it or maybe just provide recovery.zip installer so that interested devs can repack, or even the ramdisk
Huge thanks
I will get in touch with Napster :good:
DooMLoRD said:
here is a bonus for you...
build tools for honami...
http://d-h.st/Vk3
just extract the archive, replace the ramdisk.cpio.gz with new compressed ramdisk and run makeit.sh
that should build a bootable boot.img for Z1 (honami)
Click to expand...
Click to collapse
I took a look at your script
I was aware of the dt.img and already use it for Note 3 and Note 10.1 2014 from Samsung and on many of the new LG devices
Actually, cm-11.0 build tree is fixed to use a custom bootimg make file:
https://github.com/CyanogenMod/android_device_sony_rhine-common/blob/cm-11.0/custombootimg.mk#L56
The dt.img is kernel specific and is built along the zImage as you surely know. When compiling cm-11.0 boot.img, the zImage and matching dt.img are compiled and repacked using custombootimg.mk
Unpacking your fixed recovery.img I see the only changes are the dt.img and zImage to be able to use with stock ROMs. That's great and most people would prefer it that way
However, I am still unsure why you say that my original release won't boot a cm-11.0 ROM? Is it mandatory to have the kernel built along the ROM ? I do not think else your repack with zImage would work only on one specific ROM
Hope you can enlighten me on that
Phil3759 said:
I took a look at your script
I was aware of the dt.img and already use it for Note 3 and Note 10.1 2014 from Samsung and on many of the new LG devices
Actually, cm-11.0 build tree is fixed to use a custom bootimg make file:
https://github.com/CyanogenMod/android_device_sony_rhine-common/blob/cm-11.0/custombootimg.mk#L56
The dt.img is kernel specific and is built along the zImage as you surely know. When compiling cm-11.0 boot.img, the zImage and matching dt.img are compiled and repacked using custombootimg.mk
Unpacking your fixed recovery.img I see the only changes are the dt.img and zImage to be able to use with stock ROMs. That's great and most people would prefer it that way
However, I am still unsure why you say that my original release won't boot a cm-11.0 ROM? Is it mandatory to have the kernel built along the ROM ? I do not think else your repack with zImage would work only on one specific ROM
Hope you can enlighten me on that
Click to expand...
Click to collapse
the original boot.img didnt have a dt.img
DooMLoRD said:
the original boot.img didnt have a dt.img
Click to expand...
Click to collapse
really wired as I used the device tree with custom bootimg make file I linked above
I will look at it and thank you for your repack. I added to main goo.im repo
Afternoon chaps,
Just wanted to give this a whirl as i've used your recoveries before, so out of the two which are on the download section, which one should work on 4.2.2, with a locked bootloader?
Cheers m8 an glad you've made it onto the Z1
@Phil3759
For some reason on locked bootloader devices, while the texfat module has been loaded, I'm unable to get philz touch to mount any exFAT sdcard unless I change the extra.fstab line for it from 'auto' to 'texfat' ... any way to get this working normal again?
[NUT] said:
@Phil3759
For some reason on locked bootloader devices, while the texfat module has been loaded, I'm unable to get philz touch to mount any exFAT sdcard unless I change the extra.fstab line for it from 'auto' to 'texfat' ... any way to get this working normal again?
Click to expand...
Click to collapse
The honami version is compiled without minivold support for exfat modules. It will only work with fuse
https://github.com/PhilZ-cwm6/philz_touch_cwm6/blob/cm-11.0/boardconfig/BoardConfig.mk#L520
You can try to use the yuga minivold binary instead. If it is ok and you want to add support it officially with updates, I will do like yuga and enable the exfat flag
hey I have the Xperia T & SP can you create a touch version for them too?
i can be your guinea pig for testing
SP: https://github.com/CyanogenMod/android_device_sony_huashan
T: https://github.com/CyanogenMod/android_device_sony_mint
DooMLoRD said:
hey I have the Xperia T & SP can you create a touch version for them too?
i can be your guinea pig for testing
SP: https://github.com/CyanogenMod/android_device_sony_huashan
T: https://github.com/CyanogenMod/android_device_sony_mint
Click to expand...
Click to collapse
Compiled and opened dedicated threads
Feel free to put your magic if needed :angel:
@Phil3759: The backlight is really very dim on locked bootloader devices... setting that to the max setting doesn't change it all that much either.
Anything I can do to test if it's philz touch causing this?
[NUT] said:
@Phil3759: The backlight is really very dim on locked bootloader devices... setting that to the max setting doesn't change it all that much either.
Anything I can do to test if it's philz touch causing this?
Click to expand...
Click to collapse
I use this path:
Code:
/sys/class/leds/wled:backlight/brightness
Since the repack was done using a stock kernel, not sure if it still matches!
Phil3759 said:
I use this path:
Code:
/sys/class/leds/wled:backlight/brightness
Since the repack was done using a stock kernel, not sure if it still matches!
Click to expand...
Click to collapse
It does still match. It's like the value to it got cut in half...
[NUT] said:
It does still match. It's like the value to it got cut in half...
Click to expand...
Click to collapse
try to set brightness in recovery gui, then:
Code:
adb shell
cat "/sys/class/leds/wled:backlight/brightness"
Post the value here, maybe you're getting some crap because I did not properly escape those ":"
No idea why Sony have such genius ideas in naming their paths
Phil3759 said:
try to set brightness in recovery gui, then:
Code:
adb shell
cat "/sys/class/leds/wled:backlight/brightness"
Post the value here, maybe you're getting some crap because I did not properly escape those ":"
No idea why Sony have such genius ideas in naming their paths
Click to expand...
Click to collapse
Busy with making a system dump on my Z1 now, will do that soon though.
---------- Post added at 12:55 AM ---------- Previous post was at 12:36 AM ----------
Phil3759 said:
try to set brightness in recovery gui, then:
Code:
adb shell
cat "/sys/class/leds/wled:backlight/brightness"
Post the value here, maybe you're getting some crap because I did not properly escape those ":"
No idea why Sony have such genius ideas in naming their paths
Click to expand...
Click to collapse
[NUT] said:
Busy with making a system dump on my Z1 now, will do that soon though.
Click to expand...
Click to collapse
Done that:
Code:
~ # cat "/sys/class/leds/wled:backlight/brightness"
10
~ # cat "/sys/class/leds/wled:backlight/brightness"
255
First one is from the screen/power save mode, the second is when fully lit... but still the screen is only half as bright or maybe even less then half compared to using the XZ philz ...
[updated 20150104]
version v2.2
migration to twrp2.8.3.0
quickfix for lzma initrd roms
fix baseband not recognized on some tw roms
added f2fs feature to multiboot kernel for future versions..
moved qemu tools to sdcard to free space
[updated 20150101]
version v2.13
lollipop support
Hi all,
This dev thread is to continue the multiboot thread that I starded few months ago in general section.
To read history of the project you can take a look here http://forum.xda-developers.com/showthread.php?t=2577211
With Multiboot, you can launch any ROM from your internal card or your external sdcard. It is a TWRP recovery ROM modified to add this feature.
This feature is possible thank's to kexec-hardboot method created by mkasic (http://forum.xda-developers.com/showthread.php?t=1266827).
I adapted this method to be able to apply it quite easily on any android device.
This method includes few pieces of software ( sources will be published) :
kexec-hardboot : kernel patch from mkasic
hardboot-reserve : new kernel patch
kload-hardboot : new userspace program
Next part of the method is an on the fly modification of initrd ramdisk before injecting new kernel/initrd. Early versions of multiboot (before v1.2) were simply modify [on fs] section of init.rc to replace original block devices ( mmcblk0p14, mmcblk0p15 etc ) by loop devices pointing to img files.
Since Multiboot v1.2, a new method is used to replace original filesystems : a script replace original init binary, his goal is to prepare all the filesytems before launching original init.
All this method is done by shell scripts that you can check in /sbin and /multiboot directories when booted into recovery.
Creating img files (raw) is very efficient on internal sdcard as this card is formatted ext4 and img files can be thin provisiionnig ( sparse files ).
Unfortunaltely, external sdcard are offently fat32 or exfat formated. Those filesystems do not support thin provisionning ( note also that multiboot supprot only vfat for the moment ).
Creating img files on vfat filesystems is very long process and consume lot of space.
Version Multiboot V2.1 add support for ubuntu touch 14.04 support ( only img files )
Version .Multiboot V20 introduced a new feature : qcow2 support for external sdcard.
With qcow2 image files, we can create small images which grows only when needed.
You can check some video demonstrating features of multiboot on youtube channel : http://www.youtube.com/channel/UCefO8F4YX6qMQsqpBHTqTqQ
Main advantages of using qcow2 :
thin provisionning
snapshots
compression
liveboot ( livefull if small rom, "livedvd-like" if bigger roms )
Some problem (and solutions) of qcow2 :
need target kernel with nbd support - nbd is very easy to activate when compiling kernels but not already activated on kernels. Decimalman kernels already are compiled with it. http://forum.xda-developers.com/showthread.php?t=2226889
Slow speed on standard : speed on qcow2 especially when first installation is not good. To reduce this, livesnap booting mode gives very good speed.
suspend/resume : on tw43 kernels, deepsleep can hang the system. To correct it, their are 2 methods : adding a wakelock or apply a small patch to nbd.c sources.
Some details about qcow2 booting mode :
- standard : qcow2 images are acceded read/write directly on sdcard ( not recommended especially in firsts boot )
- livesnap : qcow2 images are acceded read, writes are done in zram snapshots. commit are done at reboot time : this is the recommended mod. If you install apps, you'd better to reboot first to commit qcow2. Note that if modifications are big, reboot can be long ( few minutes ), be patient. Note also that in this mode, I added a wakelock to fix suspend/reboot of tw roms.
- liveboot : same that livesnap but without commit - Same than a LiveCD in linux world. reboot speed is regular
- fulllive : only for small roms ( say ~500M ). All qcow2 are copied to zram at boot and mounted from memory. No internal/external card needed. very good speed.
- livesnap2 : same than livesnap but without wakelock. Best for speed and battery. Working except tw43. Download my modified dkp kernel to use this option on tw43 roms.
Important recommendations :
- when choosing qcow2, always choose the right nbd kernel as the last zip to install ( and don't reboot after Aroma installer )
take dkp kernels for tw43 and kk4.4.2 : http://forum.xda-developers.com/showthread.php?t=2226889
or kernels I compiled
- please follow videos on youtube
Here are last video I did to demonstrate qcow2 features. Some parts of video are boring ( during compression or commit ) but I wanted to let it go live to give an idea of processing times.
Downloads : http://www.androidfilehost.com/?w=files&flid=12801
References / Credits :
mkasic : kexec-hardboot creator - http://forum.xda-developers.com/showthread.php?t=1266827
Tassadar : MultiROM creator - best project - http://forum.xda-developers.com/showthread.php?t=2011403 - bbootimg used
TWRP Team : http://www.teamw.in/project/twrp2
reserved
First
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Love your work Philippe. This has been amazing to use for testing out multiple roms and still maintaining my daily driver. I'm a crack flasher so its nice having the options to constantly change.
Sent from my SCH-I535 using Tapatalk
Totally forgot about this, I'll have NBD included in my next kernel so this can work
this is awesome ! i been looking for muilt-boot since i got an S3 !
it's working great!
Awesome!
Now does it matter what bootloader you're on for this?
i want to try this... but the bandwidth Nazi's at work wont let me download and watch YouTube videos. would the main ROM need to be on the internal memory? or would it matter? just wondering.
Do these videos have audio? kinda hard to follow... or it just my laptop?
Restore
Hello,
Since I install the V2.0 I can't restore my new backup. I can restore the backup make before V2.0 installation but the one made with V2.0 multiboot.
Restore Failed
I try with different TWRP 2.6.3.1 and 2.7.0
Do you have and idea how to fix that.
Thanks
PwnCakes193 said:
Totally forgot about this, I'll have NBD included in my next kernel so this can work
Click to expand...
Click to collapse
I will add a link to your kernel in first message when it becomes compatible with qcow2 support.
vbetts said:
Now does it matter what bootloader you're on for this?
Click to expand...
Click to collapse
There is no prerequisite about bootloaders versions. Just be sure that your bootloader is unlocked ( I mean that you can install custom recovery images - for example, verizon 4.3 ota update locked the bootloader )
stanguay said:
Hello,
Since I install the V2.0 I can't restore my new backup. I can restore the backup make before V2.0 installation but the one made with V2.0 multiboot.
Restore Failed
I try with different TWRP 2.6.3.1 and 2.7.0
Do you have and idea how to fix that.
Thanks
Click to expand...
Click to collapse
As multiboot feature does not have relation with this part of twrp, not sure if it is linked with multiboot.
Do you have same behavour with original twr2.7.0 ?
Philippe,
ubuntu touch trusty in progress
Hi all,
Just to give a small news.
I started try to port latest ubuntu touch release (trusty) and to integrate it to multiboot.
Now, at least, I can boot on it, get the GUI, touchscreen, wifi, rotation, battery level and on/off button working.
( everything else not working : no sound, no phone, no gps etc... )
But at least, it is "usable" to play with it... Also, I integrated it to multiboot.
Don't know if you want to try that at this stage ( not sure than I can go further and get other things to work....)
Just tell me, I will package this week-end a multiboot v2.01 and ubuntu_touch_trusty_d2att.zip.
Here is a small video : http://youtu.be/y1G9hZI3deg
Philippe,
Philippe,
Phil_Suz said:
Hi all,
Just to give a small news.
I started try to port latest ubuntu touch release (trusty) and to integrate it to multiboot.
Now, at least, I can boot on it, get the GUI, touchscreen, wifi, rotation, battery level and on/off button working.
( everything else not working : no sound, no phone, no gps etc... )
But at least, it is "usable" to play with it... Also, I integrated it to multiboot.
Don't know if you want to try that at this stage ( not sure than I can go further and get other things to work....)
Just tell me, I will package this week-end a multiboot v2.01 and ubuntu_touch_trusty_d2att.zip.
Here is a small video : http://youtu.be/y1G9hZI3deg
Philippe,
Philippe,
Click to expand...
Click to collapse
I remember the last time someone built Ubuntu Touch to the d2att S3, but we ran into the same issues as you previously mentioned. Will there ever be a way to get the data to work?
codemonkey98 said:
Will there ever be a way to get the data to work?
Click to expand...
Click to collapse
Hi codemonkey98, the answer is possibly yes.
In fact, I succeeded to make cellular data work under my ubuntu touch port ( Bell carrier) .
Just have to confirm this first experimental results - I can surf internet with cell data ( without wifi ).
However, phone line is still not working.
[edit] Also sent and received SMS, so this is working also.
Philippe,
Phil_Suz said:
Hi codemonkey98, the answer is possibly yes.
In fact, I succeeded to make cellular data work under my ubuntu touch port ( Bell carrier) .
Just have to confirm this first experimental results - I can surf internet with cell data ( without wifi ).
However, phone line is still not working.
[edit] Also sent and received SMS, so this is working also.
Philippe,
Click to expand...
Click to collapse
I'd be very interested in testing the very alpha versions of this, as long as they're d2att or d2lte. best of luck man, i'm looking out for great stuff from you.
https://www.youtube.com/watch?v=j6GdvUfNppE In this video I see that you booted in the ROM w/o flashing gapps along w/ flashing the ROM ... is that necessary for this to work?
If you need a tester for anything, I'm always available.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
shekinahsmoke said:
https://www.youtube.com/watch?v=j6GdvUfNppE In this video I see that you booted in the ROM w/o flashing gapps along w/ flashing the ROM ... is that necessary for this to work?
Click to expand...
Click to collapse
Hi shekinahsmoke, no it is not necessary at all. It's better to install all zip in one shot, but I did this demo to show that you can come back to multiboot, select an already created rom and apply another zip ( gapps in this example ) even after first installation.
codemonkey98 said:
I'd be very interested in testing the very alpha versions of this, as long as they're d2att or d2lte. best of luck man, i'm looking out for great stuff from you.
Click to expand...
Click to collapse
rani9990 said:
If you need a tester for anything, I'm always available.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
Hi codemonkey98 and rani9990, thank's for your future help on testing. I am now able to call and be called . I fixed partially audio too. Calling ring and microphone during call are now ok, only incoming audio is problematic ( because exit from speaker and not earphone ).
Fall-back temporarly solution is to plug headset, in this case everything is fine during phone calls.
Now, I will start to prepare version 2.1 of multiboot to support this ubuntu touch and I will probalby open a dev thread dedicated to this ubuntu touch 14.04 when I finish first package ( this we or start of next week ).
Philippe,
Phil_Suz said:
Hi codemonkey98 and rani9990, thank's for your future help on testing. I am now able to call and be called . I fixed partially audio too. Calling ring and microphone during call are now ok, only incoming audio is problematic ( because exit from speaker and not earphone ).
Fall-back temporarly solution is to plug headset, in this case everything is fine during phone calls.
Now, I will start to prepare version 2.1 of multiboot to support this ubuntu touch and I will probalby open a dev thread dedicated to this ubuntu touch 14.04 when I finish first package ( this we or start of next week ).
Philippe,
Click to expand...
Click to collapse
I'm glad to hear. I appreciate you shedding some light towards us with Ubuntu Touch and your support for multiboot. :good:
Hi All,
Multiboot v2.1 is now ready on same download link ( http://www.androidfilehost.com/?w=files&flid=12801 )
This version add support for unbutu touch 14.04.
Philippe,
Phil_Suz said:
Hi all,
Just to give a small news.
I started try to port latest ubuntu touch release (trusty) and to integrate it to multiboot.
Now, at least, I can boot on it, get the GUI, touchscreen, wifi, rotation, battery level and on/off button working.
( everything else not working : no sound, no phone, no gps etc... )
But at least, it is "usable" to play with it... Also, I integrated it to multiboot.
Don't know if you want to try that at this stage ( not sure than I can go further and get other things to work....)
Just tell me, I will package this week-end a multiboot v2.01 and ubuntu_touch_trusty_d2att.zip.
Here is a small video : http://youtu.be/y1G9hZI3deg
Philippe,
Philippe,
Click to expand...
Click to collapse
I would love to try your touch port I have been using your recoveries for a few weeks now and just flash the touch wip Rom that is on the site but to have a simi-working port to play with would be awesome.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app