Database Develop

[ROM & Kernel] Aurora 1.0.0 Beta - Tutorial now included

Please note that this ROM is intended for the S5830i only! Flash at your own risk!
If you like Aurora just press the thanks button!
{
"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"
}
Contents
Quote 1: Introduction
Quote 2: Features and Credits
Quote 3: Download Link and Installation Instructions
Quote 4: Known Issues
Quote 5: Screenshots
Quote 6: Other Information
2nd Post: Android Shell Environment Information and Tutorial​
1. Introduction
I've been working on this for a couple of months now and this is a very stable ROM that I hope you will agree, has some great features (see below). It doesn't try to act like any particular later version of Android, I've just gone for what looks best in each individual case. I am experiencing almost no force closes whatsoever and no forced reboots at all. Hopefully others will confirm the same. I have declared this first version a beta as I haven't tested it on every firmware and one person can only test for and eliminate so many bugs. It should run fine on all firmwares. I would be grateful if you could report any bugs or issues in this thread.
Click to expand...
Click to collapse
2. Features and Credits
Core System Features
Prerooted with su binary and Supersu root access management tool
BusyBox v1.20.2-linusyang - Fully working - the latest and best version.
ROM deodexed by me
Rafael.Baugis kernel E3 rev. 201212101860
Android (Bash) Shell Environment (original thread) with many great features including:Bash shell v4.1.11(2)
Custom login screen
Multi-session command history
Tab auto-completion
Colour coded ls output
Nano text editor - fully working!
Dropbear secure shell (ssh) server
adbwifi script - surprisingly it allows you to connect to adb over wifi
reboot script - reboot, reboot recovery, soft/hot reboot, power off device
remount script - easily remount /system as re-writable / read-only​AdAway hosts file - blocks advertisements - install Adaway to remove/update
ROM based on XXLI1 - Was thinking of upgrading it to latest firmware but there has been issues with that particular firmware
Apps Features
Bloatware deleted
Chrome as default browser
Total Commander as default file manager
ICS Gallery as default gallery
No-Frills CPU Control
DroidWall firewall
Latest Play Store
Slightly modded Terminal Emulator included with Bash as default shell (Hacker's Keyboard recommended)
Zipaligned all apps for optimized performance
Still 62.3MB free on /system
Theming Features
Xperia S Launcher
SkyRaider boot animation
15 Toggles and 6 Lockscreens Mod
Lidroid Preferences
Almost all icons of all apps changed for custom hand-picked ones
1% Battery Mod
Light blue right-hand status bar icons - personally redesigned some of the icons
Light blue status bar clock
Themed status bar drop-down
Jellybean menu sound
Aurora-coloured overscroll
Aurora landscape wallpaper
Other minor theming stuff
Credits
Rafael Baugis for his excellent kernel
SenseiSimple for Android Shell Environment
Alucard1989pl for 15 Toggles and 6 Lockscreens
bijoy91 for camera settings small fonts fix
UOT kitchen for some of the theming
dsixda's Android Kitchen to deodex the ROM
Anybody else that I've accidently missed out!
Click to expand...
Click to collapse
3. Download Link and Installation Instructions
Download Link (Click Here)
1. Download Aurora's zip file.
2. Put Aurora's zip file in "/sdcard".
3. Reboot into recovery.
4. If you have stock recovery, select "apply update from sdcard" and use this zip file (put it in /sdcard) to open CWM recovery.
5. Once in CWM recovery, select "wipe data / reset" > "Yes"
6. Now select "install zip from sd" > "choose zip from sd card" > "aurora<version>.zip" > Yes
7. Wait for installation to finish, press the back button and select "reboot system now"
The phone will now reboot into Aurora. The first boot will take around two minutes, during which the screen will go blank for around one minute, so no need to panic! Subsequent boots will be much quicker.
Note: When you install this ROM, you will get e3 (stock) recovery. If you need the permanent version of CWM (because and only if you have an ext4 filesystem), then simply flash Rafael's CWM boot.img after flashing Aurora's zip file.
Click to expand...
Click to collapse
4. Known Issues
An icon of an app that is stored on the SD card that has been placed on the home screen / desktop occasionally dissapears after rebooting. This is a bug in the Xperia S launcher and there is not an awful lot I can do about this personally. There are a couple of workarounds however.
Workaround 1: The obvious, move the app to the phone's internal memory
Workaround 2: Place apps stored on the SD card in a folder on the home screen / desktop and they will not dissapear after reboots.
Click to expand...
Click to collapse
5. Screenshots
Click to expand...
Click to collapse
6. Other Information
You may use and/or redistribute my work but please give me credit. If redistributing this ROM, please link to this thread.
By the way this is my first ROM, thought I'd sneakily leave that until last
Click to expand...
Click to collapse

Android Shell Environment Information and Tutorial
Android Shell Environment Information and Tutorial
You may want to read through the original thread first.
Android Shell Environment Aurora Specific Information
​
The main difference between the original version of Android Shell Environment and the one included in Aurora is that all files are stored on the /system partition except for a couple of configuration files.
Take a look in /system/sbin for the useful utilities mentioned in the original thread
Scripts are in /system/bin (along with a lot of other Android system files).
Most of the configuration files are in /system/etc although a couple are in /data/local
In Aurora, unlike the original version, there is no option to make Bash the default shell. Firstly, this causes a bootloop on the S5830i and secondly it is pretty pointless anyway because Bash doesn't load its configuration files when set as the default shell which removes much of its functionality.
The binaries htop, scp, ssh and vim have been removed because they do not work. For all of these, there are working alternatives. For htop, use top instead, for scp use rsync, for vim use nano, for ssh use adbwifi. The text editor Joe does not work properly but has been included. Either use Nano instead or if you can get it working then please tell me how you did it!
Click to expand...
Click to collapse
Android Shell Environment Tutorial​
How To Use Bash​To start Bash:
ADB: From your PC command line, type 'adb shell' <enter>, then type 'bash' <enter>. Do not type 'adb shell bash' all in one go, this will cause problems.
Terminal Emulator: Bash loads automatically.​
Command History - Press the <UpArrow> and <DownArrow> keys to scroll through your command history. Use Hacker's Keyboard to do this in Terminal Emulator.
Auto Completion - Start typing the name of a file, folder or command, then press <Tab> to have Bash automatically complete the rest of the text. If nothing happens when you press <Tab>, then there may be multiple options, double press <Tab> to see the multiple options.
For auto-completion in Terminal Emulator, I have set a default preference so that when the phone's back key is pressed it send's out the keyboard <Tab> key. Note that this means that you cannot close Terminal Emulator using the back key, you have to enter the 'exit' command. You can change this preference in the app's settings.
To leave Bash: - Enter the command 'exit'
Click to expand...
Click to collapse
How To Use Nano Text Editor​
Nano is a user friendly command line editor. To start nano and create a new file simply type 'nano'. To start nano and open a specific file for editing type, e.g. 'nano /system/build.prop'.
If you are editing on the system partition then make sure you enter the command 'remount rw' before starting nano to mount /system as re-writable.
When you are finished editing, to exit nano enter the key combination <Ctrl>+<X>. If you have modified the file, nano will ask you if you wish to save it and request that you enter a file name.
That's basically all there is to it when it comes to the basics of this program.
Click to expand...
Click to collapse
How To Use the Reboot Command​I have rewritten the original reboot script to include a couple more parameters. Reboot now accepts the following options:
reboot - normal reboot
reboot recovery - obvious
reboot hot - hot/soft/quick reboot, restarts the Android runtime
reboot off - powers off the device, alternatively you can use the command 'halt' to acheive this
Click to expand...
Click to collapse
How To Use The Sudo Command​sudo is a well known Linux feature that runs a single command as root, useful if you generally want to work as a normal user for safety/security.
An example of this would be 'sudo adbwifi on'
Click to expand...
Click to collapse
How To Enable/Disable ADB Over WiFi​Do NOT do this from ADB shell, do this from Terminal Emulator.
Enter the command 'adbwifi on'
Follow the prompts on-screen, it tells you the rest.
To disable use 'adbwifi off'
Click to expand...
Click to collapse
How To Demote Yourself To Normal User In ADB Shell​Note: Do not do this from Bash because it doesn't work, either run it before you start bash or type 'exit', run the command, then start Bash again.
By default, ADB shell logs you in as root because Rafael's kernel has an ADB 'root mod'. This is generally very handy but sometimes, working as root is not ideal because it's very easy to brick your phone. Thankfully it is actually possible to be demoted to normal user status with the following command:
'su shell'
If you wish to return to root user, enter the command 'exit'
Click to expand...
Click to collapse
How To Use DropBear Secure Shell Server​
Dropbear allows you to login to your phone's shell (i.e. like adb shell / terminal emulator) from another device such as a PC or phone using, for example, WiFi.
To start Dropbear with the password 'pickledjelly' enter the command:
/system/sbin/dropbear -A -N root -U 0 -G 0 -C pickledjelly -r /system/etc/dropbear_rsa_host_key -b /system/etc/.dbbanner
To login from another Android device you can use e.g. Connect Bot,
use ssh protocol and in the text box enter [email protected]
Replace x and y with your phone's IP address from your WiFi router (you can get this with the command 'ifconfig')
To login from a PC running Linux enter the command:
ssh 192.168.x.y
To stop the Dropbear server issue the command 'killall Dropbear'
Click to expand...
Click to collapse

gud work man......i think this rom can have great future.....

make it final.

great job dude..:good:. now trying to combined with cronmod script by styrke...(only this way to solve our internal memory issue)
well done... all working with cronmod...

Glad some like it, cheers :good:

your rom sounds great! but is there really no way to get it based on xxlk3 (ins) ?

HeathenMan said:
your rom sounds great! but is there really no way to get it based on xxlk3 (ins) ?
Click to expand...
Click to collapse
Hi HeatherMan, I have held back on upgrading the ROM to XXLK3 so far because there were issues with IMEI numbers going awol when combining XXLK3 ROMs with custom kernels. I'll look at this again at some point though.
Aurora does work perfectly fine on XXLK3 firmware though, I currently have XXLK3 UK myself.

hi. why u don't use hell_lock kernel? thats might be better.i guess so.

SemBoyHehe said:
hi. why u don't use hell_lock kernel? thats might be better.i guess so.
Click to expand...
Click to collapse
hell_lock? wtf it is pre alpha and not stable with less features, what kind of better is THAT ?!?

HeathenMan said:
hell_lock? wtf it is pre alpha and not stable with less features, what kind of better is THAT ?!?
Click to expand...
Click to collapse
hey bro. u se ' I GUESS SO' u see that many people have trouble on that ketnel like dont have imei, earphone prob n etc. that why i guesd so

I chose Rafael's kernel because it has the most features and is currently quite stable. Hells Fusion does not presently have full IP tables needed for firewalls and has no governors or schedulers other than the standard ones.
When testing the XXLK3 IMEI issue I found that it occurred in Hells Fusion kernel as well as Rafael's. I also encountered the headphone problem at one point and found that it was because I'd flashed the boot.img but did not have the kernel modules installed.

[ROM]Ubuntu Touch on RK29 tablets

A new port of Ubuntu Touch just has arrived for RK2918 based tablets.
The first version of the RK29 port is released on CrewRkTablets (crewrktablets.arctablet.com) now.
Custom kernels are currently available for following devices:
* Odys LooxPlus
* Odys Loox
* Odys Next
* Odys Xpress
I would like to encourage you to install it on your RK29 tablet and let me know your experiences and opinion about the system.
* Pros / Cons compared to Android
* UI Usability
* Performance
* etc.
Be aware, it's on your own risk.
Update availabe (V0.1.2):
Changes:
* Corrected initial boot behaviour after RkDevelopTool (automatic boot into CWM)
The installation guide (Installation_Guide_RK29.pdf) is contained the package (CrewRkTablets_RK29_UbuntuTouchPreview_V0.1.0).
Please read ist carefully before starting the installation.
Please request for new custom kernels ONLY if you are willing to provide me with a hardware sample of the intended target device.
(Doing kernels remotely without a sample device available is just too ineffective ) Thx
Thx for your inputs

fr3ts0n said:
Custom kernels are currently available for following devices:
* Odys LooxPlus
* Odys Loox
* Odys Next
* Odys Xpress
Click to expand...
Click to collapse
I have added to our download section the following additional testkernels;
crewrktablets_kernel_308_arnova-an8cg3_201306112347_ubuntu_touch_V1.7z
crewrktablets_kernel_308_bq-kepler2_201306112347_ubuntu_touch_V1.7z
crewrktablets_kernel_308_bq-pascal2_201306112347_ubuntu_touch_V1.7z
crewrktablets_kernel_308_hyundai-h900_201306112347_ubuntu_touch_V1.7z
crewrktablets_kernel_308_M820c3G_201306112347_ubuntu_touch_V1.7z
crewrktablets_kernel_308_odys-neox7_201306112347_ubuntu_touch_V1.7z
crewrktablets_kernel_308_odys-neox8_201306112347_ubuntu_touch_V1.7z
Please give feedback!
Be aware, it's on your own risk.

not working
fr3ts0n said:
A new port of Ubuntu Touch just has arrived for RK2918 based tablets.
The first version of the RK29 port is released on CrewRkTablets (crewrktablets.arctablet.com) now.
Custom kernels are currently available for following devices:
* Odys LooxPlus
* Odys Loox
* Odys Next
* Odys Xpress
I would like to encourage you to install it on your RK29 tablet and let me know your experiences and opinion about the system.
* Pros / Cons compared to Android
* UI Usability
* Performance
* etc.
Be aware, it's on your own risk.
Thx for your inputs
Click to expand...
Click to collapse
does not work for Prestigio pmp5097cpro tried all the kernels, maybe we should describe in detail the installation process?

does not work on my Vivax TPC-7120
Maybe is some my mistake during instalation becouse almost every custom rom i tried on this device didnt work. Only rom i can normaly install is from some Titan tablet (4.0.3)
When i finishinstalation with RKDevelopTool, tablet freeze on boot (on blue "Odys LOOX Plus" spalsh screen).

Not working on odys loox/approx cheesecake v1

Wait a minute.
What did you flash?
1. you need special kernel for ubuntu touch, a normal Android kernel, eg stock rom kernel, does not work.
2. you need a working kernel from the above list for your tablet, and if it is not a Odys Loox Plus, you have to change this, as mentionend in the manual.
3. if your tablet meets not the points 1 and two, we could look if we can compile a custom one, but sources would be needed.

JochenKauz said:
Wait a minute.
What did you flash?
1. you need special kernel for ubuntu touch, a normal Android kernel, eg stock rom kernel, does not work.
2. you need a working kernel from the above list for your tablet, and if it is not a Odys Loox Plus, you have to change this, as mentionend in the manual.
3. if your tablet meets not the points 1 and two, we could look if we can compile a custom one, but sources would be needed.
Click to expand...
Click to collapse
Use kernel of Odys Loox and not working. Not boot ubuntu.

magio081 said:
does not work on my Vivax TPC-7120
Maybe is some my mistake during instalation becouse almost every custom rom i tried on this device didnt work. Only rom i can normaly install is from some Titan tablet (4.0.3)
When i finishinstalation with RKDevelopTool, tablet freeze on boot (on blue "Odys LOOX Plus" spalsh screen).
Click to expand...
Click to collapse
HI magio081,
Thanks for your post. It really helps if a reply contains details as yours does.
This sounds very likely as your device tries to boot into the system rather than into the CWM-recovery right after the RKDevelopTool programming.
Please try to boot it into CWM manually by pressing M-Button at startup without power supply being connected.
If the device comes up in CWM you can continue the installation as described in the installation guide.
For all the others: Please post some details: what steps have been done, what did you see up to this point and what do you see currently. (A blank screen with background light on may identify a different cause than just a black screen). I'm glad to help you through the installation, but I will need to read some details on your situation. Thx

Alexitler said:
does not work for Prestigio pmp5097cpro tried all the kernels, maybe we should describe in detail the installation process?
Click to expand...
Click to collapse
Testing through all kernels is a rather dangerous sequence.
Do you know what listed device your tabelt is compatible with?
Did you go through all the installation steps listed in the installation guide? (the pdf document which is part of the package)
Please could you describe in detail, what your device did/does show on the screen at each step of the installation?

JochenKauz said:
Wait a minute.
What did you flash?
1. you need special kernel for ubuntu touch, a normal Android kernel, eg stock rom kernel, does not work.
2. you need a working kernel from the above list for your tablet, and if it is not a Odys Loox Plus, you have to change this, as mentionend in the manual.
3. if your tablet meets not the points 1 and two, we could look if we can compile a custom one, but sources would be needed.
Click to expand...
Click to collapse
OK. I think im missing here something huge. Lets start from very start:
About tablet
model number: TR720F
Kernel: [email protected] #735
Firmware: 720F_RT5621_GT811&818_RTL8188_AT28_GC0307_MT9D112_CAT6611_TP01_OTG
Build no.: RK2918_ANDROID4.0.3-SDK_V2.10_20120205
Stock rom was 2.3 i upgraded on 4.0.3 with some RKBatchTool what i found for some simular Titan tablet. On that rom tool i have only one file to select - update.img. And all work perfect (ex. camera).
how i tryed to install ubuntu touch
1. copy raring-preinstalled-phablet-armhf.zip & CrewRKTablets_AOSP_4.2.2_Format_NAND_Fix.zip to sd
2. copy kernel.img (kernel_308_odys_loox_plus_ubuntu_201306091043_UbuntuTouch_V1) to rockdev/kernel.img
2a. check all 7 programming parts
3. turn off tablet, hold M button and connect to cable (status: found RKAndroid loader rock usb)
4. eraseIDB (status: erasing IDB OK)
5. Run (status: size 471059, written & checked, download file ok, elapsed (144110MS))
6. Tablet start blue odys screen and freeze on that.

mega-samu said:
Use kernel of Odys Loox and not working. Not boot ubuntu.
Click to expand...
Click to collapse
Knowing that the cheesecake is compatible with the Loox, you are correct to use the Loox kernel.
Please could you also post what parts of the installation you have finished, and waht your device dis/does show on the screen.
@all who have similar problems:
Please try to post as many details as possible on your proiblem: What steps have been performed? what did you see on the display? etc.
Please also try to access the device via USB and try to do a 'adb logcat' and 'adb shell dmesg' from shell or windows command line.
If you can post any of these outputs, this helps for problem analysis.

not working
fr3ts0n said:
Testing through all kernels is a rather dangerous sequence.
Do you know what listed device your tabelt is compatible with?
Did you go through all the installation steps listed in the installation guide? (the pdf document which is part of the package)
Please could you describe in detail, what your device did/does show on the screen at each step of the installation?
Click to expand...
Click to collapse
installed according to instructions. RKAndroidTool writes that the installation is successful, then a black screen. Tried all the cores, the result - black screen.

fr3ts0n said:
Knowing that the cheesecake is compatible with the Loox, you are correct to use the Loox kernel.
Please could you also post what parts of the installation you have finished, and waht your device dis/does show on the screen.
@all who have similar problems:
Please try to post as many details as possible on your proiblem: What steps have been performed? what did you see on the display? etc.
Please also try to access the device via USB and try to do a 'adb logcat' and 'adb shell dmesg' from shell or windows command line.
If you can post any of these outputs, this helps for problem analysis.
Click to expand...
Click to collapse
Kernel Loox
{
"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"
}

mega-samu said:
Kernel Loox
Hi mega-samu,
Thanks for the description. This error shows that the programmed data could not be verified sucessfully.
If this problem is reproducable, this could be caused by too fast flash access of the programming.
The version of install tool used is the RkDevelopTool_V1.35 which was introduced with the RK3066. It works a lot faster, than the RkAndroid from other Rk29 packages, that is why I use it. It works fine on my LooxPlus, but may be too fast for some other devices.
Please could you try to use a copy of the old RkAndroid (from another install package i.E. Oma_JB) for the programming:
Just copy the complete directory RkAndroid into the unzipped package directory (in parallel to the RkDevelopTool) and start the older tool.
PS: There is also a changed package available which has a fix for the automatic boot into CWM after the Rkxxx programming.
Click to expand...
Click to collapse

Alexitler said:
installed according to instructions. RKAndroidTool writes that the installation is successful, then a black screen. Tried all the cores, the result - black screen.
Click to expand...
Click to collapse
If you haven't seen a boot logo at reboot after RkDevelopTool (before the screen got black), then neither of the kernels you installed does support your device.
btw: installing incompatibe kernels may harm your device, since i.e. display drivers may seriously overclock your display hardware. Please be careful about this.
Do you know what other tablets your device is compatible to?
Did you use a custom kernel in android before? If yes, which one?

fr3ts0n said:
Hi mega-samu,
Thanks for the description. This error shows that the programmed data could not be verified sucessfully.
If this problem is reproducable, this could be caused by too fast flash access of the programming.
The version of install tool used is the RkDevelopTool_V1.35 which was introduced with the RK3066. It works a lot faster, than the RkAndroid from other Rk29 packages, that is why I use it. It works fine on my LooxPlus, but may be too fast for some other devices.
Please could you try to use a copy of the old RkAndroid (from another install package i.E. Oma_JB) for the programming:
Just copy the complete directory RkAndroid into the unzipped package directory (in parallel to the RkDevelopTool) and start the older tool.
PS: There is also a changed package available which has a fix for the automatic boot into CWM after the Rkxxx programming.
Click to expand...
Click to collapse
I believe that it is the kernel, that this poorly compiled
`
Sorry for English Bad.

mega-samu said:
I believe that it is the kernel, that this poorly compiled
Click to expand...
Click to collapse
I don't think so, cause a defekt kernel.img would only prevent that your system boot.
Here you see an error in the flash sequence. This can have multiple reasons, the only reason that relates to the kernel.img wolud be that the kernel.img is too large for the kernel partition to fit. Normally the partition is made for kernel.img with max 8MB in size.
To get more information, you could look into the log dir of the RKAndroidTool. There you can find the detailed logs of RKAndroidTool.

JochenKauz said:
I don't think so, cause a defekt kernel.img would only prevent that your system boot.
Here you see an error in the flash sequence. This can have multiple reasons, the only reason that relates to the kernel.img wolud be that the kernel.img is too large for the kernel partition to fit. Normally the partition is made for kernel.img with max 8MB in size.
To get more information, you could look into the log dir of the RKAndroidTool. There you can find the detailed logs of RKAndroidTool.
Click to expand...
Click to collapse
Kernel Odys Loox 8,05 MB
Kernel de Odys Loox Plus 7,86 MB

mega-samu said:
Kernel Odys Loox 8,05 MB
Kernel de Odys Loox Plus 7,86 MB
Click to expand...
Click to collapse
I could verify your problem here, the loox kernel got too big with all ubuntu features enabled.
I made a new kernel for the loox with some other minor features disabled which now fits into the partition.
Please download the kernel Loox V1.1 and re-try the installation.
With this kernel I could verify the complete installation and again have a rocking ubuntu on it
Let me know when it rocks with you ...

magio081 said:
OK. I think im missing here something huge. Lets start from very start:
About tablet
model number: TR720F
Kernel: [email protected] #735
Firmware: 720F_RT5621_GT811&818_RTL8188_AT28_GC0307_MT9D112_CAT6611_TP01_OTG
Build no.: RK2918_ANDROID4.0.3-SDK_V2.10_20120205
Stock rom was 2.3 i upgraded on 4.0.3 with some RKBatchTool what i found for some simular Titan tablet. On that rom tool i have only one file to select - update.img. And all work perfect (ex. camera).
how i tryed to install ubuntu touch
1. copy raring-preinstalled-phablet-armhf.zip & CrewRKTablets_AOSP_4.2.2_Format_NAND_Fix.zip to sd
2. copy kernel.img (kernel_308_odys_loox_plus_ubuntu_201306091043_UbuntuTouch_V1) to rockdev/kernel.img
2a. check all 7 programming parts
3. turn off tablet, hold M button and connect to cable (status: found RKAndroid loader rock usb)
4. eraseIDB (status: erasing IDB OK)
5. Run (status: size 471059, written & checked, download file ok, elapsed (144110MS))
6. Tablet start blue odys screen and freeze on that.
Click to expand...
Click to collapse
I had CWM integrated in some previews rom, but when i install back my 4.0.3 rom CWM was deleted. I was searching to install CWM, but i didnt find way (tryed update.img - bricked my devace), i installd CWM manager from sd .apk, but with thet tool i cant boot intro recovery mod.
Is there any good tutorial for installing CWM Recovery, or Rom with integrated CWM?
When i try on my devace to boot intro recovery (power button + M button) i got this photo

[PORT] Ubuntu Touch for LG L90 Dual

Update 30 October 2016: I'm sorry for very long delay. Being a university student make my free time lower considerably. Anyway, new device tarball is released in stable and rc-proposed channel. This version mostly contains minor fixes, but more importantly, this includes fixes for some famous vulnerability, including the Quadrooter and dirty CoW vulnerabilities. Go to "System Settings" to get your update, or follow instructions below if you haven't update your phone since 9 January 2016.
I still ship experimental fixes in rc-proposed that may freeze your phone when the screen is off. If this matters to you, you may consider using stable channel for now, but that has pretty bad power consumption (but that still means about one day of light usage). Also, there is known bug about mobile network not usable on some network that affects all channels.
Oh, and for those stay on absolute bleeding edge on devel-proposed channel, I currently don't have enough time to test that. So, no release to devel-proposed just yet. Sorry!
Disclaimer
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
By the way, this disclaimer is actually copied from somewhere else just to protect me from being in the court, and I won't actually laugh at you if your device bricks. If your device really bricks, I will help you as much as possible.
Introduction
This is a port of Ubuntu touch to LG L90 Dual and all L90 models. (See below for tested devices.) Basic functionalities work, but there're still some rough edges all around. It's stable enough to use daily, and I personally use it on my phone every day. If you're tired of Android, you may want to give Ubuntu touch a try.
Tested device
This doesn't mean other devices aren't supported. If your device is labeled as "L90" (or can run Cyanogenmod for LG L90), you can give this a try.
LG L90 Dual (D410) (My device )
LG L90 D405n (single card) (Thanks, keturidu!)
LG Optimus L90 D415 (T-Mobile variant) (Thanks, JamesB3)
Click to expand...
Click to collapse
What's working/not working
Note that this is tested using rc-proposed channel.
Screen: Works
Touch: Works
Audio: Works
Screen rotation: Works
Vibration: Works
Camera: Stil picture works for both camera. But video recording doesn't work for the front camera.
Mobile Phone: Works for both SIM, but please see "Bugs and workarounds" below for info about 3G slot and data connection.
Wifi: Works
Video playback: Works
GPS: Works.*
Bluetooth: Works, but on/off doesn't.
*Do note that Wi-Fi-assisted location isn't available as it's licensed for the official devices only.
Click to expand...
Click to collapse
Screenshot
{
"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"
}
Click to expand...
Click to collapse
Information about device tarball and channel selection (obsolete)
Now, you don't have to worry about correct device tarball anymore. You just type in correct channels in the command, and the flashing software will get the correct files for you. You can find out more about Ubuntu touch channels at https://developer.ubuntu.com/en/start/ubuntu-for-devices/image-channels/. If you're in doubt, I recommend you to use stable channel.
Click to expand...
Click to collapse
How to install/upgrade
Installing for the first time (updated):
The easiest way to install it is using ubuntu-device-flash. All of your personal data will be deleted. Make sure you backup everything important before install.
You have to root your device and unlock device's bootloader. This forum has a good tutorial on that.
For rooting, I recommend http://forum.xda-developers.com/lg-l90/general/guide-root-l90-varients-updates-t2928364. If that doesn't work, try http://forum.xda-developers.com/showthread.php?t=2732311. This guide is guaranteed to work.
For unlocking bootloader, I recommend http://forum.xda-developers.com/lg-l90/general/guide-guide-to-unlocking-bootloader-l90-t2852917
Also, you'll need an Ubuntu (virtual) machine.
If your device has been running Lolipop, you may have to flash Kitkat-based bootstack for your device (http://forum.xda-developers.com/lg-l90/development/bootstack-kk-l-l90-t3118632). Make sure you know exact phone model (Dxxx__).
Follow the instruction for preparing your desktop in this link.
Select channel (see information about selection above). Don't download device tarball. The flashing software will get it for you.
Enable ADB for your device. I won't teach you here, but, again, this forum has a good tutorial about that.
Plug your device into your computer. Then, put the device in fastboot mode by running the following command:
Code:
adb shell su -c 'dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/boot bs=16 count=1'
adb reboot
The first command will wipe the first 16 bytes of the boot partition. So, when the device reboot, it'll boot into fastboot mode as the boot partition is broken. Don't worry, it'll be flashed by Ubuntu Touch anyway.
When the device is in fastboot mode, run the following command:
Code:
sudo ubuntu-device-flash --server http://system-image.ubports.com/ touch --channel ubuntu-touch/{selected channel} --device w7 --bootstrap --wipe
There maybe some trouble flashing recovery. If that happen, re-plug the USB chord and try again. You'll see a lot of text and then purple recovery screen. At this point, the computer will push the files into your device. Don't unplug your USB chord until the device reboot again with big Ubuntu logo spinning. Wait until the device reboot into Ubuntu Touch, and, viola, Ubuntu Touch is installed!
Upgrading your device or switch channel (updated):
If you've updated your device with new instruction at least once (since 9 January 2016) and just want to update the device tarball, just go to "System settings" on your device to get your update. But if you've never updated with the new instruction, read on.
Enable developer mode on the device by going to System Settings > About this phone > Developer mode. If you don't have a passcode for your device, set it now by pressing Lock security. Then, enable developer mode by pressing at the check.
Plug your device into the computer, unlock your device (this is important) and run:
Code:
ubuntu-device-flash --server http://system-image.ubports.com/ touch --channel ubports-touch/15.04/stable
Don't unplug your USB chord until the device reboot again with big Ubuntu logo spinning.
Flash different (Android-based) recovery:
Ubuntu recovery can't be used to flash Android-recovery-format ZIP file. If you want to go back to Android using backed up file or ZIP file, you'll need custom Android-based recoveries, such as TWRP or CWM. You'll need raw disk image (IMG file) for this. Run the following command in terminal:
Code:
adb reboot recovery
# wait for recovery to appear
adb push {recovery image name}.img /cache
adb shell dd if=/cache/{recovery image name}.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
adb reboot recovery
Click to expand...
Click to collapse
Download & Source code
You don't need to download device tarball manually anymore as flashing software will deals that for you. But if you want, you can download device-specific tarball using --download-only flag with ubuntu-device-flash. Be warned that you can't flash that image directly because updater in recovery image won't trust the signature.
Customization on the Android side can be found in the local manifest in this Github repository:
https://github.com/peat-psuwit/ubuntu-phone_manifest_w7
All kind of pull request is welcome on all of my repository.
Most customization on Ubuntu side can be found at
https://launchpad.net/~peat-new/+archive/ubuntu/lg-d410-custom/+packages
For those interested, this is programs that make phone call on this device works: https://github.com/peat-psuwit/pulseaudio-droid-card-parameters-setter
Click to expand...
Click to collapse
Legal notice
This distribution of software contains software from Android Open Source Project and CyanogenMod Project. It's under Apache license. Additionally, this distribution also contains software that is normally distributed with Android system, being under various licenses. The detail of license of those files is at /system/etc/NOTICE.html.gz after the system is installed.
This distribution of software contains part of PulseAudio. (Particularly, the modified version of droid module.) It's licensed under GPL version 2 or any later version of GPL. (it's actually distributed under LGPL 2.1+, but it's used with GPL-only libraries, making the effective license GPL. Please look at /usr/share/doc/pulseaudio-module-droid/copyright for detail). Get the patch at https://github.com/peat-psuwit/pulseaudio-droid-card-parameters-setter
This distribution of software contains timekeep, a small utility to keep track of time & date. This is Copyright (c) 2015, Sony Mobile Communications Inc, and licensed under 3-clauses BSD license. The full license can be seen at https://github.com/peat-psuwit/timekeep/blob/master/license.txt
Old legal notice:
This distribution of software contains modified version of oFono, Open Source Telephony. It's licensed under GPL version 2. You may have your source-code at https://launchpad.net/~peat-new/+archive/ubuntu/lg-d410-custom/+packages
This distribution of software contains part of GStreamer, open source multimedia framework. (Particularly, the modified version of androidmedia plugin.) It's licensed under LGPL version 2 or any later version of LGPL. You may have your source-code at https://launchpad.net/~peat-new/+archive/ubuntu/lg-d410-custom/+packages
Click to expand...
Click to collapse
Changelogs
Latest update: 30 October 2016
Fix problem where pressing buttons below the screen in certain way will cause screen not to go sleep.
Fix Quadrooter, dirty CoW, and other vulnerabilities.
Change some aspect of build system.
Make system use our GPS configuration instead of system's default.
Older update
16 June 2016
Fix thumbnail generation for some video resolution.
Revert NetworkManager workaround added in the last release as NM 1.2 is now in both rc-proposed and stable channel.
Change method to wait for Bluetooth config at startup.
Change grid unit size to 13px.
(rc-proposed only) Run init.zetaw.post-boot.sh when the phone finished booting. This'll make battery consumption a lot lower but will cause the phone to lock up sometimes. That's why I release this fix to rc-proposed channel only. If you can't bare with something like this, switch to stable channel.
28 April 2016
Add a workaround for NetworkManager, to fix Wi-Fi connectivity after mobile data is disconnected. The actual fix is preparing to land in rc-proposed soon, but until then, let's use this workaround.
8 April 2016
Update Pulseaudio-module-droid to incorporate audio recording fix.
4 April 2016 (rc-proposed only update)
Update Pulseaudio-module-droid
Update configuration to run ADB in secure mode.
Update recovery image.
11 March 2016
Fix race condition in Bluetooth initialization code.
Update recovery image
4 March 2016
Enable Bluetooth in kernel and android parts.
Update recovery image
6 February 2016
Update pulseaudio-module-droid distributed in device tarball.
9 January 2016
Enforce GPG verification for UBPorts system-image server.
Reduce possibility to reboot at startup due to Wi-Fi subsystem.
3 January 2016
Fixes in kernel and framework for camera due to changes in Ubuntu side.
Make Wi-Fi (pseudo-)on/off works. This fix Wi-Fi not work at startup.
Change the way to distribute Pulseaudio module.
Fix for touchscreen not working in new revision of Ubuntu.
20 November 2015
Split device tarball into 2 versions.
Disable some service in Android container that crashes all the time.
26 August 2015
Working video recording.
4 July 2015:
Include timekeep, a small utility to keep track of time & date.
Remove oFono and gstreamer1.0-plugins-bad, as patches are accepted upstream.
8 Jun 2015
Working GPS.
Update oFono.
1 Jun 2015
Working mobile phone for both SIM slots.
Update gstreamer1.0-hybris, oFono and droid module of PulseAudio, for supporting new Ubuntu version (wily).
6 May 2015
Finally working video playback. Although this is not so good as I cannot make hardware rendering works yet.
Include a modified version of gstreamer1.0-hybris package.
Update oFono and droid module of PulseAudio.
17 April 2015
Update Pulseaudio.
7 April 2015
Fix Wi-Fi
Temporary disable ubuntu-location-service. As GPS doesn't work yet, leaving that enable will make battery drain fast as it'll always try to load GPS library.
4 April 2015
Fix mobile phone in the hackery way.
17 March 2015:
Partially fix camera. It can take a still picture, but cannot record video.
Fix the problem about GPG signature properly. The hack is no longer needed.
Click to expand...
Click to collapse
Bugs and workarounds
Note that this list is based on rc-proposed channel and stable-based device tarball.
At boot, the device may freezes and restarts itself. This is due to the Wi-Fi system and I'm investigating this issue. This is due to fatal subsystem failure in the kernel. I've reduced possibility for Wi-FI subsystem (this is the most common failure), but this may still happen but at the lower rate.
If Wi-Fi list doesn't update during the day, turn Wi-Fi off and on.
Turning Wi-Fi on and off currently doesn't work. (Note that while you can turn Wi-Fi on-off in system settings, the Wi-Fi chip will be not turned off.)
If you're using rc-proposed channel, you may experience lockup when you're trying to wake the phone up from sleep. Currently, there's no fix yet, but if you can't live with it, use stable channel instead.
If you're using some mobile provider, your phone will not be able to detect SIM card. The fix is being developed. (If you're curious, it's about comunication between RILD and oFono and how your SIM card is programed.)
Fixed or disappeared problem:
Camera will stop working after you bring camera app from suspended state. Workaround: bring app back to suspend state and bring back again. This can be done by swiping from left edge. This seems not be the case now.
Sometime, the device may seems freeze because an app is crash. This seems to be the problem in graphic subsystem. The system may becomes responsive again after seconds, but if it takes too long, just restart the phone. This seems not be the case now.
Sometime (at boot or sometime after), Wi-Fi stops working. This can be noticed by having Wi-Fi network list not updated. Fixed by pseudo-on/off fix.
Second One or both SIM slots may stop working at some boot. Simple rebooting should fix it. You may have to reboot multiple times. Seems to be disappear.
3G slot selection doesn't work when there's only 1 SIM card. Workaround: use another SIM slot. (Fix released)
Data connection will work with only 1 of the slots (the one you most recently used before flashing Ubuntu touch. Don't worry, if you can't remember you van try them both). Workaround: put the SIM card with a data plan in another SIM slot. If you happened to have only 1 SIM and the slot that data works is different from the slot with 3G capability, I recommend you to temporary borrow another SIM card from your friend so that you can change 3G slot. change 2G slot in system settings. Fix accepted and released.
Click to expand...
Click to collapse
Credits goes to
Quarx2k for the initial Cyanogenmod port.
Cyanogenmod for many components I used to simplify my build.
Every contributor of LG L90's device tree on Cyanogenmod.
Ubuntu for the porting guide.
awe, ogra, abeato, rsavelti, popey, anpok, and much more people on irc.freenode.net #ubuntu-touch
Sony for timekeep.
mariogrips for UBPorts.
Click to expand...
Click to collapse

Im not testing yet as you dont have phone call working.. But when you do i'm going to take a peek..
Enviado do meu LG-D405n através de Tapatalk

I will try it when I have the time. I have been waiting to try Ubuntu Touch
Question: Does this method of install wipe custom recovery?

ardentis said:
Question: Does this method of install wipe custom recovery?
Click to expand...
Click to collapse
This method will install Ubuntu's recovery before using that recovery to install Ubuntu Touch. So, yes, your custom recovery will be wiped.

I would love to test this out on my D415. Once you get mobile phone and wifi(because t-mobile's mobile data sucks here. I only get 2G xD ), Once those two things get solved i'll be happy to test. Also I think if you moved this thread over to the android development section you'll get more interest shown. I know Ubuntu isn't android but it's still technically development.

JamesB3 said:
I would love to test this out on my D415. Once you get mobile phone and wifi(because t-mobile's mobile data sucks here. I only get 2G xD ), Once those two things get solved i'll be happy to test. Also I think if you moved this thread over to the android development section you'll get more interest shown. I know Ubuntu isn't android but it's still technically development.
Click to expand...
Click to collapse
I'm working on mobile phone now and I promise that Wi-Fi will be the next. Anyway, I cannot guarantee that it'll work on your phone, because I have only LG L90 Dual (D410). It may boot or it may not. I have no clue at all.
BTW, I don't know how to move the thread. Please tell me how.

peat_psuwit said:
I'm working on mobile phone now and I promise that Wi-Fi will be the next. Anyway, I cannot guarantee that it'll work on your phone, because I have only LG L90 Dual (D410). It may boot or it may not. I have no clue at all.
BTW, I don't know how to move the thread. Please tell me how.
Click to expand...
Click to collapse
That's great! I understand I just want to ask if I will have any way to get my device back to android if it doesn't boot?
And you could probably PM the moderators of the forum and get them to move it.

I'm a fan of ubuntu. Never heard much of the mobile version though. How much app is available on this platform or are Android apps also compartible?

ichiato said:
I'm a fan of ubuntu. Never heard much of the mobile version though. How much app is available on this platform or are Android apps also compartible?
Click to expand...
Click to collapse
There are a little over a thousand apps right now and its just an upcoming platform so it doesnt have good support yet. Android apps are not compatible and will not be officially compatible though someone will eventually change that.

ardentis said:
There are a little over a thousand apps right now and its just an upcoming platform so it doesnt have good support yet. Android apps are not compatible and will not be officially compatible though someone will eventually change that.
Click to expand...
Click to collapse
Thanks. Is there any way I can browse through the list of apps and see? I also read somewhere that the apps for desktop version are compatible with that of the mobile version. How through is this?

ichiato said:
Thanks. Is there any way I can browse through the list of apps and see? I also read somewhere that the apps for desktop version are compatible with that of the mobile version. How through is this?
Click to expand...
Click to collapse
https://uappexplorer.com/ is an unofficial app store. I know nothing about compatibility other than what Canonical has said. I have no experience using Touch. It would be awesome if Touch could be flashed by zip because I dont feel like f-ing up my only phone..

Has anyone tested this rom yet? I am curious how well it performs and of any bugs. I want to install it but I dont want to screw anything up

Is there anyway to recover from this if it doesnt work? Or anyway to go back to android?
Is the developer still working on the project at all?

JamesB3 said:
Is there anyway to recover from this if it doesnt work? Or anyway to go back to android?
Click to expand...
Click to collapse
You can take a backup with CWM/TWRP before install. If the rom doesn't work, you can boot into recovery, flash CWM/TWRP back, and restore your android.
If in doubt, you can always install stock rom via KDZ file. Search this device's forum for instruction.
JamesB3 said:
Is the developer still working on the project at all?
Click to expand...
Click to collapse
I'm still working on it if the time permit. The latest update have working Wi-Fi now. Please, don't ask the question like this again, because porting an operating system is not an easy task.

peat_psuwit said:
You can take a backup with CWM/TWRP before install. If the rom doesn't work, you can boot into recovery, flash CWM/TWRP back, and restore your android.
If in doubt, you can always install stock rom via KDZ file. Search this device's forum for instruction.
I'm still working on it if the time permit. The latest update have working Wi-Fi now. Please, don't ask the question like this again, because porting an operating system is not an easy task.
Click to expand...
Click to collapse
Oh ok thats cool. I'll test on D415 when i have time.
I know. I apologize.

peat_psuwit said:
You can take a backup with CWM/TWRP before install. If the rom doesn't work, you can boot into recovery, flash CWM/TWRP back, and restore your android.
If in doubt, you can always install stock rom via KDZ file. Search this device's forum for instruction.
I'm still working on it if the time permit. The latest update have working Wi-Fi now. Please, don't ask the question like this again, because porting an operating system is not an easy task.
Click to expand...
Click to collapse
Do i use Ubuntu's terminal to install?

Instructions for installing Ubuntu can be found here: https://developer.ubuntu.com/en/start/ubuntu-for-devices/installing-ubuntu-for-devices/.
Instructions for reverting back to android can be found here: https://developer.ubuntu.com/en/start/ubuntu-for-devices/reinstalling-android/.
I don't know if the installation instructions will vary at all since we have our own image instead of pulling from their repository....but I imagine it would be similar.
Hope that helps!

JamesB3 said:
Do i use Ubuntu's terminal to install?
Click to expand...
Click to collapse
Yes, you'll use terminal in Ubuntu to type those command. I'm not sure if ubuntu-device-flash is available on another Linux distro.
BellaMay95 said:
Instructions for installing Ubuntu can be found here: https://developer.ubuntu.com/en/start/ubuntu-for-devices/installing-ubuntu-for-devices/.
Instructions for reverting back to android can be found here: https://developer.ubuntu.com/en/start/ubuntu-for-devices/reinstalling-android/.
Click to expand...
Click to collapse
Most of installing instruction will apply here, just don't forget to specify device as generic and provide our device tarball. The parts that doesn't apply is about unlocking bootloader, because we actually can't do it that way. Instead, use instruction in this device's forum.
The reverting instructions can't be used here, as LG doesn't ship our device's ROM in that format. Instead, search this device's forum for instruction.

I tried to install but after install recovery it says that i´ve no space on the device

afpereira said:
I tried to install but after install recovery it says that i´ve no space on the device
Click to expand...
Click to collapse
I guess you probably need to check free space on your computer. The phone probably have enough space to install this.
But if it still doesn't work, please copy full message printed on the terminal. The error should say if it happen on the phone or on the computer.

Ubuntu Touch is back ! (supported by Ubports)

Ubuntu Touch By Ubports
{
"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"
}
Website : https://ubports.com/
As might have know, the mobile operating system developed by Cannonical for the Nexus 4 was called Ubuntu Touch. The project was canceled early 2017.
More information : https://en.wikipedia.org/wiki/Ubuntu_Touch
The legacy subject for Ubuntu touch on Nexus 4 was host by nikwen, https://forum.xda-developers.com/nexus-4/general/rom-ubuntu-touch-14-10-utopic-unico-t2324683
Thanks to the community the entire mobile operating system has been forked by Ubports guys... with a great success, they established a fairly strong monthly finance through donation https://www.patreon.com/ubports and are building a foundation : https://ubports.com/page/foundation
I've the pleasure today, September 21st 2017, to create this subject to announced that Ubuntu Touch for Nexus 4 in a fairly stable version .
So far all the blocking bug found were fixed yesterday , you can track in real time the bug here : https://github.com/ubports/ubports-touch/issues?utf8=✓&q=label:"Device: Mako"
How to test it :
By the official way of course : https://wiki.ubports.com/wiki/How-to-install-UBports-on-your-device
This will wipe all the data on your phone ! Be careful !
Version to install today : Stable
Installer to use : https://github.com/ubports/ubports-installer
By Multirom, strongly disapproved as it is not supported by Ubports project.
***************** It's easy to install, however upgrade from ubuntu touch broke the book 1 over 10 updates.... ************************
It might be useful for you to give a glance to the OS, but for daily driver uses the official installation tool.
Bug from multirom installation will not taken into account if they are not present on the official installation. (Except some boot impossible after an update on the multirom version which required to wipe the ubuntu install, it works fine).
If you want to give a try : https://forum.xda-developers.com/showpost.php?p=72455220&postcount=2140

slash.tux said:
(...)The project was canceled early 2107.(...)
I've the pleasure today, September 21st 2107, to create this subject to announced that Ubuntu Touch for Nexus 4 in a fairly stable version .
(...)
Click to expand...
Click to collapse
Is this the correct year? :cyclops:

And I insist several time , thanks for the correction

I really love this os but i dont see any future for it unless android apps will work

Hello,
I understand your thoughts however we can see on Sailfish OS, it doesn't really help to get better share market.
Right now the focus is to move on Ubuntu 16.04 LTS, to get long term support for security update, last version of Mir and unity 8 and stuff running like andbox :laugh: . For this the developers are creating Halium project to allow any linux project, Plasma Os, Utouch, Sailfish (hopefully) etc... on the same driver layer => If a device will be port on plasma Os it will work on the others.
For more info : https://halium.org/
The OTA-2 has been released and the nexus 4 got it's first stable version https://ubports.com/blog/ubports-blog-1/post/ubuntu-touch-ota-2-release-78
Currently the trend of adoption Ubports : https://stats.ubports.com/

Soooo is there a way to flash this from TWRP? I have tried flashing from both an Ubuntu machine and a Windows machine over. And over. And over. For the past 3 days, and I'm getting really annoyed. On Ubuntu, it always gets stuck after pushing just a few things, and just sits there. Left it overnight. On Windows, it detects ADB and the device just fine, but no matter how many times I reboot to bootloader, even with the correct nexus 4 drivers installed, nothing. Just sits there. I can install Android or Sailfish no problem.
---------- Post added at 10:21 AM ---------- Previous post was at 10:15 AM ----------
Did a fresh run right now, still not working
[email protected]:~$ ubuntu-device-flash --clean-cache touch
2017/09/28 10:18:21 Cleaning prevously downloaded content
[email protected]:~$ sudo ubuntu-device-flash --server=http://system-image.ubports.co m touch --device=mako --channel=15.04/devel --bootstrap
2017/09/28 10:19:17 Device is |mako|
2017/09/28 10:19:17 Flashing version 148 from 15.04/devel channel and server htt p://system-image.ubports.com to device mako
60.64 MB / 60.64 MB [============================================================] 100.00 % 4.69 MB/s
322.74 MB / 322.74 MB [==========================================================] 100.00 % 7.24 MB/s
2017/09/28 10:20:18 Start pushing /home/ian/.cache/ubuntuimages/pool/ubports-4eff6ae1f43900a2919b57c61b3ad5137721f7a9803d85078a82b7829e0c7e55.tar.xz to device
2017/09/28 10:20:18 Start pushing /home/ian/.cache/ubuntuimages/ubports-touch/15.04/devel/mako/version-148.tar.xz to device
2017/09/28 10:20:18 Start pushing /home/ian/.cache/ubuntuimages/pool/keyring-4c4e7ef380ebcfa2c31084efa199138e93bfed8fc58aa3eb06bdf75a78af9b57.tar.xz to device
2017/09/28 10:20:18 Start pushing /home/ian/.cache/ubuntuimages/gpg/image-signing.tar.xz to device
2017/09/28 10:20:18 Start pushing /home/ian/.cache/ubuntuimages/gpg/image-master.tar.xz to device
2017/09/28 10:20:18 Start pushing /home/ian/.cache/ubuntuimages/pool/device-d08eb9751a871a277abe893c4406bf26c4f239be686cfcd7c7b4f221599a826e.tar.xz to device
2017/09/28 10:20:18 Done pushing /home/ian/.cache/ubuntuimages/ubports-touch/15.04/devel/mako/version-148.tar.xz to device
2017/09/28 10:20:18 Done pushing /home/ian/.cache/ubuntuimages/gpg/image-signing.tar.xz to device
2017/09/28 10:20:18 Done pushing /home/ian/.cache/ubuntuimages/pool/keyring-4c4e7ef380ebcfa2c31084efa199138e93bfed8fc58aa3eb06bdf75a78af9b57.tar.xz to device
2017/09/28 10:20:18 Done pushing /home/ian/.cache/ubuntuimages/gpg/image-master.tar.xz to device
2017/09/28 10:20:19 error pushing:
Click to expand...
Click to collapse
I also have tried that magic flash tool many times. Just tried it again, and it's, yep, just sitting there.
Flashing devel channel
< waiting for device >
^C
[email protected]:~/build/magic-device-tool$ sudo ubuntu-device-flash --clean-cache touch
2017/09/28 10:24:14 Cleaning prevously downloaded content
[email protected]:~/build/magic-device-tool$ sudo ubuntu-device-flash --server=http://system-image.ubports.com touch --device=mako --channel=15.04/devel --bootstrap
2017/09/28 10:24:22 Device is |mako|
2017/09/28 10:24:22 Flashing version 148 from 15.04/devel channel and server http://system-image.ubports.com to device mako
60.64 MB / 60.64 MB [============================================================] 100.00 % 4.05 MB/s
322.74 MB / 322.74 MB [==========================================================] 100.00 % 6.98 MB/s
Click to expand...
Click to collapse
It never gets any further than this on the magic tool.

Does your fastboot is unlocked ?
When you flash is the phone in fastboot mode ?
Did you try with another cable ?
Did you try a manual push to Android or Sailfish ?

Nothing works for me.
1.) The Windows-Tool wont find the Nexus 4, but it is in fastboot-mode and unlocked
2.) My both Ubuntu Setups, 16.04. and 17.04 wont install the ubuntu-device-tools and the magic tool have the same problem, it wont find a device, even when its in fastboot-mode (it have the same problem, it wont install the ubuntu-device-tools)

My guess,
1) Widnows doesn't have the correct Nexus 4 driver.
2) I'm not sure to understand.
You cannot install, ubuntu-device-tools on your computer, correct ?
source : https://devices.ubports.com/#/mako
dancle86 said:
Nothing works for me.
1.) The Windows-Tool wont find the Nexus 4, but it is in fastboot-mode and unlocked
2.) My both Ubuntu Setups, 16.04. and 17.04 wont install the ubuntu-device-tools and the magic tool have the same problem, it wont find a device, even when its in fastboot-mode (it have the same problem, it wont install the ubuntu-device-tools)
Click to expand...
Click to collapse

Thanks for the log,
Per chance do you have enough available space on your nexus 4 ?
Did you try with the ubports installer : https://github.com/ubports/ubports-installer
There is the info on how to install it when you scroll down.
idumych said:
Soooo is there a way to flash this from TWRP? I have tried flashing from both an Ubuntu machine and a Windows machine over. And over. And over. For the past 3 days, and I'm getting really annoyed. On Ubuntu, it always gets stuck after pushing just a few things, and just sits there. Left it overnight. On Windows, it detects ADB and the device just fine, but no matter how many times I reboot to bootloader, even with the correct nexus 4 drivers installed, nothing. Just sits there. I can install Android or Sailfish no problem.
---------- Post added at 10:21 AM ---------- Previous post was at 10:15 AM ----------
Did a fresh run right now, still not working
I also have tried that magic flash tool many times. Just tried it again, and it's, yep, just sitting there.
It never gets any further than this on the magic tool.
Click to expand...
Click to collapse

slash.tux said:
Per chance do you have enough available space on your nexus 4 ?
Click to expand...
Click to collapse
Hi,
Do you happen to know on which partition these update files are pushed (on phone side)? And how to evaluate space required?
Regards

The files are pushed to /data
I would say minimum 1 gb left would be sufficient.
Cieniek said:
Hi,
Do you happen to know on which partition these update files are pushed (on phone side)? And how to evaluate space required?
Regards
Click to expand...
Click to collapse

Sailfish OS is linux distro. Ubuntu touch is not real linux! It lacks many apps, it's much slower then Sailfish OS, and can't run android apps like Sailfish OS does. Aliendalvik is available for ported devices too. I have it on my nexus 4 & 5. Everything works on Nexus 4 like on android. Nexus 5 with base CM12.1 has minor issues. camera does not work and sound does not work in some android apps.
Sailfish OS > Ubuntu touch.

Thanks for the feedback. Ubuntu Touch doesn't intent to compete with other mobile operating system, just to gather bunch of people around the same interest.
Sailfish OS and UbuntuTouch has two different approachs of the mobile operating system. For sure Sailfish OS is more polished than Ubuntu Touch, however it is not fully opensource. Moreover it doens't provide the capability of convergence and a GPS navigation system like Unav, http://unav.me/.
Regarding Android app, there is no really rush to go there. The main objective right now is to bring the device with the right kernel to Ubuntu 16.04 LTS to access to more feature and security updates.
The team already released a beta version of 16.04 Lts for 2-3 phones (fairphone, N5 and HTC10)
This operating system upgrade will bring the possibility to use Anbox on Ubuntu Touch : https://anbox.io/
If you want to follow the new app store and see the progress I invite you to look at the OpenStore app included in the Ubports Ubuntu Touch image.

slash.tux said:
My guess,
1) Widnows doesn't have the correct Nexus 4 driver.
2) I'm not sure to understand.
You cannot install, ubuntu-device-tools on your computer, correct ?
source : https://devices.ubports.com/#/mako
Click to expand...
Click to collapse
the installer can't find "ubuntu-device-flash" and "phablet-tools" on actual ubuntu-versions and same for the magic-installer-tool. there is no way to install this on my nexus 4.

dancle said:
the installer can't find "ubuntu-device-flash" and "phablet-tools" on actual ubuntu-versions and same for the magic-installer-tool. there is no way to install this on my nexus 4.
Click to expand...
Click to collapse
It's normal that you cannot install ubuntu-touch on your nexus 4, if you don't have the tool to flash.
1. Please install the required tool on your ubuntu desktop/laptop
Code:
sudo apt-get install ubuntu-device-flash phablet-tools
2. Reboot your Nexus 4 into fastboot mode and Connect your device with an USB cable to your computer.
3. Flash your device using this command: (NOTE! This will wipe your phone!)
Code:
sudo ubuntu-device-flash --server=http://system-image.ubports.com touch --device=mako \
--channel=15.04/devel --bootstrap
As mentioned on this page : https://ubports.com/page/get-ubuntu-touch

slash.tux said:
It's normal that you cannot install ubuntu-touch on your nexus 4, if you don't have the tool to flash.
1. Please install the required tool on your ubuntu desktop/laptop
2. Reboot your Nexus 4 into fastboot mode and Connect your device with an USB cable to your computer.
3. Flash your device using this command: (NOTE! This will wipe your phone!)
As mentioned on this page : https://ubports.com/page/get-ubuntu-touch
Click to expand...
Click to collapse
Cant we install it from Windows 10 desktop/laptop.

atahanali_57 said:
Cant we install it from Windows 10 desktop/laptop.
Click to expand...
Click to collapse
Yes you can install from windows, the .exe installer is the following : https://github.com/ubports/ubports-installer/releases/download/0.1.7-beta/ubports-installer.0.1.7-beta.exe
You might have to install the windows/android/adb drivers required for your device.
dancle said:
the installer can't find "ubuntu-device-flash" and "phablet-tools" on actual ubuntu-versions and same for the magic-installer-tool. there is no way to install this on my nexus 4.
Click to expand...
Click to collapse
You can also try the appimage, which embeds everything for linux.
the link : https://github.com/ubports/ubports-installer/releases/download/0.1.7-beta/ubports-installer-0.1.7-beta-x86_64.AppImage
then Make the AppImage executable https://discourse.appimage.org/t/how-to-make-an-appimage-executable/80
Then run the file by double-clicking
In both case i enclosed some screenshots

Thank you. Very cool thread.
Currently on my Nexus 4 with Stock ROM is installed Ubuntu Xenial.
I used Linux Deploy 2.0.2-223.
Thanks to that I have both android and linux.
In android, I open GUI through VNC viewer, and in Windows via TightVNC 1.5.2.
Do you see the possibility of using Ubuntu Touch and Android via dualboot / multiboot or anything else?

Thanks for the information i didn't know about this tool.
Yes you can run with multirom android and ubuntu touch for testing in parallel. I modified the multirom .apk for that : https://forum.xda-developers.com/showpost.php?p=72455220&postcount=2140
I mentioned testing as multirom is not supported by the community and sometime (happend twice in 2 months) the ubuntu touch upgrade breaks ubuntu touch boot due to some incompatibility.

[ROM][LINUX][LAVENDER] Droidian Bookworm

{
"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"
}
​Droidian is a GNU/Linux distribution based on top of Mobian, a Debian-based distribution for mobile devices. The goal of Droidian is to be able to run Mobian on Android phones. This is accomplished by using well-known technologies such as libhybris and Halium.​Requirements​
Android 9 firmware for your device:
Redmi Note 7 lavender: LINK
Files​
Download the latest fastbootable image: droidian-UNOFFICIAL-phosh-phone-xiaomi_lavender-api28-arm64-nightly_XXXXXXXX.zip
Installation:​
Extract the archive
run the flash_all script
Boot to fastboot and let the script flash everything.
UBports Installer
Alternatively the UBports installer can also be used to install Droidian.
Notes​Default password​The default password is 1234.
List of working things can be found at https://github.com/droidian-lavender/device-page
APN​Mobile data needs an APN to be set up from Settings -> Mobile Network -> Access Point Names.
Broken mobile data after calls​Data connection might break after receiving and making calls. Switch it off and on from Settings -> Mobile Network to fix it. Be careful to not turn off the mobile modem or a device restart might be required.
Out of storage​By default when flashing Droidian it allocates 8GB of storage to the system. This might not be enough and luckily you can allocate more storage with ADB by running (while in recovery): adb shell e2fsck -fy /data/rootfs.img and adb shell resize2fs -f /data/rootfs.img xG where x is the amount of GB to allocate (eg: 50G for 50 GB).
SSH access​connect your phone to your computer and type ssh [email protected], the password is 1234 (on Windows, you may need PuTTY)
Applications​You can find a list of mobile-friendly Linux applications at LinuxPhoneApps
What Works
Manual brightness, Notification LED, Torchlight, Vibration, Carrier info, Data connection, Calls, Pin unlock, SMS, Audio routing, Voice calls, Volume control, Battery percentage, Online charging, RTC time, SDcard, Shutdown, Reboot, Bluetooth, Flight mode, Hotspot, WIFI, Auto brightness, Proximity, Rotation, Touch screen, Earphones, Loud speaker, Microphone, Waydroid
What partially works
Camera works fine in Waydroid but in system itself its slow and requires some technical work.
What doesn't work
GPS, Fingerprint, Offline charging, Dual SIM, Encryption
Waydroid​Waydroid is an Android container which lets Android apps run on Linux phones with GPU acceleration with full speed.
Waydroid works fine on Lavender.
Final Notes​
I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed.
Support​
Device specific telegram group: @Barrys_crib.
Droidian telegram group: @DroidianLinux.
Thanks to the Droidian team, erfanoabdi, Danct12 and Sergio for all helping out to make this happen.
All the sources are available at
https://github.com/droidian-lavender/
Attached images are from different devices but the interface looks and acts the same.

pretty cool, I guess it's nice to have an option if I ever want to turn this old device into a server or maybe run pihole. Nice work!

ghst7 said:
pretty cool, I guess it's nice to have an option if I ever want to turn this old device into a server or maybe run pihole. Nice work!
Click to expand...
Click to collapse
It can actually be used as a daily driver. I have been using Droidian on another device as a daily driver for a long time now.
Because we can run both Linux apps and Android apps it is a good option as a portable computer.

How should I update？

I followed the steps below, but the logo was black after I started
1. adb slideload .\Desktop\droidian-OFFICIAL-phosh-phone-rootfs-api28-arm64-nightly_20230109_4.zip
2. adb sideload .\Desktop\adaptation-droidian-lavender.zip
3. reboot

gas0324 said:
How should I update？
Click to expand...
Click to collapse
sudo apt update and sudo apt upgrade when you're in the OS

gas0324 said:
I followed the steps below, but the logo was black after I started
1. adb slideload .\Desktop\droidian-OFFICIAL-phosh-phone-rootfs-api28-arm64-nightly_20230109_4.zip
2. adb sideload .\Desktop\adaptation-droidian-lavender.zip
3. reboot
Click to expand...
Click to collapse
what is the issue you're having? did it flash everything correctly?
when you flash the adaptation package and reboot it boot up but not to the UI. it will apply the adaptation to the rootfs then reboot itself once and you should be in the OS
if in the first boot you force shutdown or reboot it the installation will fail
you can wipe data and start again
after install then reboot and don't touch your device

FakeShell said:
what is the issue you're having? did it flash everything correctly?
when you flash the adaptation package and reboot it boot up but not to the UI. it will apply the adaptation to the rootfs then reboot itself once and you should be in the OS
if in the first boot you force shutdown or reboot it the installation will fail
you can wipe data and start again
after install then reboot and don't touch your device
Click to expand...
Click to collapse
After Debian's logo appears again, the mobile phone screen is very colored and has no content

gas0324 said:
After Debian's logo appears again, the mobile phone screen is very colored and has no content
Click to expand...
Click to collapse
join the device specific group to debug this

FakeShell said:
join the device specific group to debug this
Click to expand...
Click to collapse
I don't understand

gas0324 said:
I don't understand
Click to expand...
Click to collapse
join me in telegram to debug this issue
Barry's crib
Barry's crib. when we mess with things, stuff go here. don't spam and keep it english thats it
t.me

FakeShell said:
join me in telegram to debug this issue
Barry's crib
Barry's crib. when we mess with things, stuff go here. don't spam and keep it english thats it
t.me
Click to expand...
Click to collapse
OK, I'm downloading telegram

FakeShell said:
join me in telegram to debug this issue
Barry's crib
Barry's crib. when we mess with things, stuff go here. don't spam and keep it english thats it
t.me
Click to expand...
Click to collapse
Sorry, I can't receive the SMS verification code from Telegram now. I'm solving this problem, and I will contact you later

User forgot to downgrade to miui android 9
It's in the requirements guys you need to downgrade to android 9 first!

It works well at present

droidian-OFFICIAL-phosh-phone-rootfs-api28-arm64-nightly_XXXXXXXX.zip
Click to expand...
Click to collapse
There is not a matching file on the nightly released 30 minutes ago, and cant seem to find previous releases. Which one do i download?

rodrimax10 said:
There is not a matching file on the nightly released 30 minutes ago, and cant seem to find previous releases. Which one do i download?
Click to expand...
Click to collapse
if you can't find it there download this
https://github.com/droidian-images/rootfs-api28gsi-all/releases/download/nightly/droidian-rootfs-api28gsi-arm64_20230126.zip
Release nightly · droidian-images/rootfs-api28gsi-all
Deprecated, use https://github.com/droidian-images/droidian/releases - Release nightly · droidian-images/rootfs-api28gsi-all
github.com
droidian-rootfs-api28gsi-arm64_xxxxxxxx.zip

This is the closest system I have used to real Linux, but I still hope it can support Docker. Why can't I run Docker?

FakeShell said:
UBports Installer
Alternatively the UBports installer can also be used to install Droidian.
Click to expand...
Click to collapse
What's the procedure to do that? Thought UBports installer can only install Ubuntu Touch

Sithhy™ said:
What's the procedure to do that? Thought UBports installer can only install Ubuntu Touch
Click to expand...
Click to collapse
Same way you install UT druring os selection select droidian