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
Related
In response to some requests, I have added some pre-made boot.img files. They need to be flashed with nvflash, but at least you don't have to mess around with linux and coverting the files.
The files attached below have this logo that replaces the "G-Tablet" boot logo:
{
"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"
}
TNT Lite 3.0 Tegra.zip
TNT Lite 3.1 Tegra.zip
VEGAn beta 3 Tegra.zip
VEGAn beta 5.1 Tegra.zip
(attached to bottom of post)
-----------------------------------------------------------------------------
ADVANCED USERS ONLY - NVFLASH REQUIRED
I would like to reiterate the importance of when I say this is not for the faint of heart. You should be familiar with nvflash, know how to pull the partition table, know how to do a full restore, etc. You are directly and blindly flashing a partition. A small percentage of devices have a different partition table, which this guide would not work for. -Rothnic.
Thanks Rothnic! I couldn't say it better myself, so I didn't!
Thank you to JSZESZE for the image I used. It can be found here.
If you need help getting NVFLASH to work, you can find it here.
This will show you how to change the second boot screen or the "G-Tablet" screen with an image of your choice. I have attached the tools you need to do it, to565 needs to be compiled. Do not ask me how, I had to search google since I never compiled anything before, but I have included the to565.c so you don't need to go looking for it.
1. Extract the boot.img out of the rom zip you are using (update.zip) to your desktop
2. Place the boot.img, unpack-bootimg.pl, to565, and the boot folder on your desktop
3. Open a terminal
4. type in terminal
Code:
perl unpack-bootimg.pl boot.img
5. You should then have boot.img-ramdisk, boot.img-kernel.gz and boot.img-ramdisk.cpio.gz on your desktop
6. Delete boot.img-ramdisk.cpio.gz
7. Open the boot.img-ramdisk directory
8. Remove and save initlogo.rle
9. Open the photo you want to use in GIMP
10. Resize to 1024 x 600
11. Click save as...
12. Name the file splash.raw
13. Select file type "raw image data" and save to your desktop
14. RGB Save Type should be Standard (R,G,B)
15. Indexed Palette type should be R,G,B (normal)
16. In terminal:
Code:
./to565 -rle < splash.raw > initlogo.rle
17. You should now have ititlogo.rle on your desktop
18. copy that file to boot.img-ramdisk directory
19. Move boot.img-ramdisk folder and boot.img-kernel.gz to the boot folder
20. In terminal:
Code:
cd boot
perl repack-bootimg.pl boot.img-kernel.gz boot.img-ramdisk boot.img
21. Should have a boot.img file in the boot directory now.
22. In terminal:
Code:
./nvflash --bl bootloader.bin --download 10 boot.img
If you read through all of this and are lost, but really want that G-Tablet screen gone, I may help you out if you ask nicely.
Roebeet, Rothnic and Gojimmy... I would love to create something with your guys' roms.
Worked a treat. Thanks again!
How about just uploading the rom with it done?
movieman123 said:
How about just uploading the rom with it done?
Click to expand...
Click to collapse
It really depends on which rom you have because the boot.img file is different in every rom.
I would invite the rom builders to incorporate these changes into their roms and I have offered via this thread to help include different initlogo.rle for the rom builders.
Hi! How to make it all in Windows? Nothing with Linux near...
KirMit said:
Hi! How to make it all in Windows? Nothing with Linux near...
Click to expand...
Click to collapse
Can't... unless you can cross-compile to565. If you manage to do that, I am not sure how you would run the perl scripts in windows because they are written to use the linux binaries.
or... you could run a VMware virtual machine with a linux dist on it. That really how I did it. I have Ubuntu running on a VM machine on Windows 7. But then again, you run into the problems of possibly never running linux before.
or... tell me which rom you are on and post the picture you want here and I can do it for you. You'll still need to do NVFLASH to get it installed on your tab.
Ok... You're right! I have 2 ways to decide this. Just find any linux based computer right now or ask you to compile boot.img from this firmware http://forum.xda-developers.com/showthread.php?t=859884 I've just flashed
I need just a g-tablet logo has been removed or replaced by simple standart nvidia or android logo.
rayden25 said:
Can't... unless you can cross-compile to565. If you manage to do that, I am not sure how you would run the perl scripts in windows because they are written to use the linux binaries.
or... you could run a VMware virtual machine with a linux dist on it. That really how I did it. I have Ubuntu running on a VM machine on Windows 7. But then again, you run into the problems of possibly never running linux before.
or... tell me which rom you are on and post the picture you want here and I can do it for you. You'll still need to do NVFLASH to get it installed on your tab.
Click to expand...
Click to collapse
KirMit said:
Ok... You're right! I have 2 ways to decide this. Just find any linux based computer right now or ask you to compile boot.img from this firmware http://forum.xda-developers.com/showthread.php?t=859884 I've just flashed
I need just a g-tablet logo has been removed or replaced by simple standart nvidia or android logo.
Click to expand...
Click to collapse
I can send you my one for VEGAn beta 3 with the black tegra+android logo when I get home in about 8 hours. You still need nvflash setup to flash it.
WickedStyx said:
I can send you my one for VEGAn beta 3 with the black tegra+android logo when I get home in about 8 hours. You still need nvflash setup to flash it.
Click to expand...
Click to collapse
It will be great! Thank you a lot! Nvflash works fine on my win laptop right now.
This image in Vegan B3 boot.img
delete the .zip off the end of the file name and flash to partition 10 with nvflash.
works great rayden thanks man
thanks for the tutorial worked great finally got rid of that logo!
Sent from my VEGAn-TAB-v1.0.0b3 using Tapatalk
aver2one said:
thanks for the tutorial worked great finally got rid of that logo!
Click to expand...
Click to collapse
That G-Tablet logo is the most unappealing logo I have ever seen... It's horrible! LOL!
Great FAQ thanks for all your good work!
rayden25 said:
... tell me which rom you are on and post the picture you want here and I can do it for you. You'll still need to do NVFLASH to get it installed on your tab.
Click to expand...
Click to collapse
I would like the attached BMP for VEGAn-TAB b5.1 please
Thanks
Agreed -- I'd like to show off the fact that this tablet has a Tegra2 inside!
...but wouldn't it be easier to implement in the bootanimation file?
nice guide gonna try this when i get home
TeutonicWolf said:
Agreed -- I'd like to show off the fact that this tablet has a Tegra2 inside!
...but wouldn't it be easier to implement in the bootanimation file?
Click to expand...
Click to collapse
Yes, it would be easier. but my point is to get rid of the gtablet boot logo. advertising viewsonic gtablet is enough on the back for me. and i would also like to keep the vegan tablet bootanimation to show what ROM i'm running
Can you do the same image posted above for the TNT Lite 2.1.2 rom? Mucho appreciated if you can! I just hate the white backgrounded logo... Thanks!
cnathanw said:
Can you do the same image posted above for the TNT Lite 2.1.2 rom? Mucho appreciated if you can! I just hate the white backgrounded logo... Thanks!
Click to expand...
Click to collapse
I will do it for you, but please verify your rom version. TNT Lite 2.12 never existed and 2.1 is very old. Do you mean 3.12?
{
"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"
}
NEW GUIDE SEE HERE: http://forum.xda-developers.com/showthread.php?t=1653566
Hi everyone! The following guide I put together is a simple, easy to follow guide, for all G9 users. If you own an ARCHOS G8, this guide will not work for you. This guide will help you easily root your tablet. If you have found anything helpful, please click "thanks" on my post, and visit the original threads of our amazing developers and leave thanks there too! Before you go on, please BACKUP ALL IMPORTANT FILES YOU DO NOT WANT TO LOSE TO A SAFE LOCATION.
If you have rooted other android devices before..rooting your Archos G9 may be a little difference. Instead of rooting stock firmware, we first temp root, then enable SDE (special developer edition) menu. Once SDE menu is enabled, it adds an option in recovery to install developer firmware. This is when we install a modified firmware that has busybox and super user included. We do this because the exploit in the temp root causes some issues that doesn't make sense to keep in the long term. Hence the name "temp" root. This guide is very safe to follow. Chances are most problems you run into are very easy to recovery. Please view the FAQ at the bottom of this post if you have questions or run into problems. Because we don't have to flash recoveries or mess with the bootloader like some Android devices require, and because all methods are universal to G9s, this rooting process is very safe and easy to follow.
Please if you have any issues following this guide, reply with the stock firmware you have (be it honeycomb, ICS, firmware 4.0.6 etc) and the G9 model (flash or HDD 250gb). Board version and processor (OMAP 4430 and 4460 should not be a problem with anything, so probably don't include this when you ask your problem.)
STEP 1: Pre-root/Temp-root
1. Install the ADB drivers, using Quinny's thread here (WINDOWS ONLY)
2. Make sure you have the Android SDK installed and have access to adb
3. Open up a command window (Windows key + R, type cmd and hit enter)
4. Type, with your tablet plugged in:
Code:
adb devices
Your device should appear. If not, repeat steps 1-4 until it does. You may need to restart your computer
5. Download root_hack and extract. Note: Don't open these links in a browser, not tapatalk or the xda app
Download them to your desktop (or wherever your ADB installation is if you cannot access ADB from your desktop)
6. Double click rootdevice.cmd to open, press any key after reading the prompt.
(Note: Device will reboot a couple times)
7. Restart your tablet (important do not skip this step)
THANKS TO PAUL FROM MoDaCo for this root
THANKS TO QUINNY and LETAMA for the original guide
STEP 2: Enable SDE
1. Make sure you have done the temp root method. Please turn off your tablet. Your tablet should now be off.
2. Download this zip and extract to your desktop
3. Turn on your tablet. Once your tablet is on, plug it into your computer via usb cable.
4. double click enable_sde.bat
5. Once that is finished, type the following: (press enter after each line)
Code:
adb shell
rm /data/local.prop
6. (If the above code doesn't work or doesn't do anything, it is okay, move on with the rest of the guide). SDE should now be enabled, make sure buy turning off your device, then once it's off:
7. Hold power + volume down until the archos logo appears and a recovery menu appears
8. Use Volume Up + Down and power to select Recovery Menu > Developer Edition menu
9. If you can get to Developer Edition menu, you have correctly enabled SDE.
STEP 3: (optional, but recommended from honeycomb). Format your device, and then install/re-install ICS. No worries: You will not lose SDE menu doing this.
It is recommended to do a full device format when upgrading to ICS. If your device is acting up or feels "laggy" after updating to ICS, this usually helps. Before you begin, please note: You will lose all apps, media files, pictures, etc. Please backup any important files. Consider Titanium Backup (root users only to backup any apps with personal data you want to keep (game scores, etc).
AGAIN: YOU WILL LOSE *ANYTHING* NOT BACKED UP!
Note: You WILL need a PC connected to the internet, and the USB cable that came with your device. Before you being, please download Archos 80/101 G9 OS v 4.0.6 (190668Kb, for 80/101 G9 devices only) to your PC, copy to your desktop or wherever you will remember, then do the following:
Step 1: Power off your device
Step 2: Boot into recovery by holding the volume rocker down and pressing the power button simultaneously
Step 3: Once in recovery, select "Format System", then "Reformat Device..." (use the volume up/down to change selection, power button to select)
Step 4: Once formatted, return to recovery using the same method above, this time select "Update Firmware"
Step 5: Plug your device into your computer using the USB cable that came with your device
Step 6: A new drive should appear in "My Computer", copy firmware_archos_it4.aos to this device
Step 7: Ensure the transfer is completed, then press the power button on your device, keep it plugged in while it is updating
Step 8: Your device should boot, and be updated to the latest firmware 4.0.6
STEP 4: Install rooted firmware. YES! This will work after installing the official ICS OTA update or official AOS.
Before you begin, you will need SDE enabled. Please follow steps 1 & 2 in my first post. If you have SDE enabled, you can continue. Any downloaded applications and personal media should remain untouched. You have some options for which ROM you want. Please download files to your PC hard drive.
For stock ROM w/ root (busybox and superuser), download and extract the following:
4_0_6_update.zip
kernel_update.zip
For custom ROM [email protected]_V02, download and extract the following:
https://hotfile.com/dl/154778665/e6b99ad/ics_blue_update.zip.html
http://www.2shared.com/file/triOUMDR/ics_blue_kernel.html
BE SURE to extract, Archos recovery does not recognize zip files
Step 1: Power your device on
Step 2: Once your device is on, and your home screen is visible, plug your device into your PC
Step 3: Open a command prompt on your PC and type
Code:
adb devices
Step 4: Ensure your device shows up so you know it's connected properly and adb is active
Step 5: Type
Code:
cd desktop
This is to change the directory to where you download the two files
Step 6: If you have flash NAND model (8gb or 16gb): Type
Code:
adb push archos.ext4.update /data/media
If you have HDD model (250gb): Type
Code:
adb push archos.ext4.update /mnt/storage
Give it some time to transfer, it is a large file and will take several minutes, you will be presented with transfer info once the transfer is complete
Step 7: Power off your device
Step 8: Boot into recovery by holding the volume rocker down and pressing the power button simultaneously
Step 9: You should now be in Recovery mode with the following options "No" "Reboot" "Update Firmware" "Repair System" "Format System" "Developer Edition Menu". Select "Developer Edition Menu"
Step 10: Select "Remove Android Kernel" (if the option is present, if not, skip)
Step 11: Select Flash Kernel and Initramfs
Step 12: Copy zImage and initramfs.cpio.lzo to the drive that appears
Step 13: Reboot your device. Your device should now be rooted.
Frequently Asked Questions! (FAQ)
Will this guide work for my Archos 80 G9? For my 101 G9? I have Archos 101 G9 OMAP 4430. I have 250GB hdd model! I have turbo edition!
Yes this guide will work for ALL Archos G9 users. This includes 80 G9s and 101 G9s. This includes all 8gb G9s and 16gb G9s and 250GB G9s and 1.0 GHz G9s and 1.2 GHz G9s and 1.5 GHz G9s and OMAP 4430 G9s and OMAP 4460 G9s and board version V5 etc etc. ALL G9s!
Can I just drag the .zip file to the RAMDISK that appears when I flash zImage and initramfs?
No! Archos recovery cannot read ZIP files. You must first EXTRACT, then copy the contents of the extracted folder. NOT the folder itself. This means you will have two files on the RAMDISK, and no additional folders. If you don't know what a RAMDISK is, try Google or Wikipedia. If you get stuck in a boot loop because you forgot to extract archos.update.ext4 or drive.zip, you must follow the instructions below.
Help! I am stuck in a bootloop! Archos splash screen appears and keeps rebooting. I messed up when I was rooting, and now android will not boot! I accidentally formatted my device, and now I cannot boot into android.
This is a simple mistake and in 99% of cases it is easy to fix. Follow these steps:
Step 1: Download official Archos G9 firmware for ALL G9 tablets (aos file) HERE
Step 2: Boot into recovery turning your device off and then holding volume down + power at the same time
Step 3: Choose "Update Firmware"
Step 4: Connect USB cable to computer and tablet
Step 5: A removable device should appear (RAMDISK), copy the file you just download straight to that drive
Step 6: Press the power button once the file is done copying. DO NOT UNPLUG your device until it has finished updating and has booted back into android.
If you did not format your tablet or delete any personal media, your files should be uneffected.
Will I lose SDE menu if I update my tablet with official AOS or OTA update
As of the latest update (4.0.6) no official update from Archos has removed SDE menu. You should be fine, and your SDE menu should remain untouched.
Useful tips
Overclock
How to overclock your device. For SDE only.
First please download and extract https://hotfile.com/dl/152251241/ef27ecd/fast_ics_oc.zip.html
Then follow the instructions in my second post to push to your device then copy zImage and initramfs.
After you have successfully booted download SetCPU or No-Frills CPU Control and overclock to your desire. Thanks to surdu for making this happen! Visit his original thread HERE to view all warnings.
Howto take a screenshot
ICS has a built-in screenshot feature. No need to download any app!
Step 1: On the screen you wish to capture, press and hold the power button and volume down button simultaneously for a few seconds until the screen flashes and you hear a shutter. Be sure to press them at the same time
Step 2: You can find the saved screenshots in storage > Pictures > Screenshots
Step 3: Alternately, you can simply find them in the folder labeled "Screenshots" in the gallery.
Touchscreen issues
If you have touch related issues/errors, try the following:
Step 1: Turn your device off
Step 2: Carefully wipe down the screen with a dry or lightly damp rag. If you use a lightly damp rag, be sure to dry it with a dry one quickly.
Step 3: Power on your device
Step 4: Go to Settings > Repair & formatting > Touch screen calibration > *Put your device down on a flat, hard surface like a table, tap Calibrate the Touch Screen ONCE, then DO NOT TOUCH.
Step 5: Once finished, you can return to your launcher or wherever you wish
Multiple Users
More than one person uses your Archos?
Either designate home screens using a contact widget, or use a note widget in launchers like GO Launcher. There are also apps that support multiple profiles for root users like SwitchMe Root Profile Manager, however I can not guarantee this will work.
Multi-boot!
See this: http://forum.xda-developers.com/showthread.php?t=1578438
Removeable System apps
System apps you can safely disable (new ICS feature) or delete via Titanium Backup or other root app: (only remove the ones you don't use)
Archos Connect
Archos Remote Control
Media Center
Media Server
Movie Studio
Online Registration
Photo Frame
Talk Back
User Manual
If you have any tips I should add, or if any part of this guide is inaccurate or outdated, please let me know!
BIG THANKS:
Android Development Team for giving us awesome Honeycomb and Ice Cream Sandwich OS!
Archos for their hardware and awesome customer support!
serdu_petru for full root and all his hard work putting together these rooted firmwares so quickly!
letama for his original work on this device and work with kernels for overclock!
gen_scheisskopf for his work on allowing root access for HDD models!
Quinny899 for putting together his easy root guide for noobs like me!
Any other wonderful people involved in the development and advancement of this wonderful device!
GUIDE TBC
Didn't you mean "reformat device"? because by reformatting Android, you don't lose data in /mnt/storage...
Hi!
Thank you very much for your good and complete tutorial !
Have a nice week !
blogmaw said:
Didn't you mean "reformat device"? because by reformatting Android, you don't lose data in /mnt/storage...
Click to expand...
Click to collapse
yes that's what I meant. Thanks, got those two mixed up simple mistake
surdu_petru said:
Hi!
Thank you very much for your good and complete tutorial !
Have a nice week !
Click to expand...
Click to collapse
thanks man! have a great week too
Hi !
Thank you....but into BIG THANK !.....do not forget to mention the @gen_scheisskopf for your useful help ....without him work ...now HDD models wouldn't work !
surdu_petru said:
Hi !
Thank you....but into BIG THANK !.....do not forget to mention the @gen_scheisskopf for your useful help ....without him work ...now HDD models wouldn't work !
Click to expand...
Click to collapse
I have added him thank you for reminding me!
Concerning multiple users, I would suggest you Switch Me, it allows users to have their own sessions on the tablet.
As for the uncompatible apps, it's mostly games that haven't been certified as compatible but they actually run flawlessly! (9mm, Asphalt 6 HD...). I tried to modify build.prop and init.Archos.80S (in my case) but it didn't work on ICS (see topic http://forum.xda-developers.com/showthread.php?t=1528899)
Sent from my Archos 80G9 using XDA Premium HD app
blogmaw said:
Concerning multiple users, I would suggest you Switch Me, it allows users to have their own sessions on the tablet.
As for the uncompatible apps, it's mostly games that haven't been certified as compatible but they actually run flawlessly! (9mm, Asphalt 6 HD...). I tried to modify build.prop and init.Archos.80S (in my case) but it didn't work on ICS (see topic http://forum.xda-developers.com/showthread.php?t=1528899)
Sent from my Archos 80G9 using XDA Premium HD app
Click to expand...
Click to collapse
Is this what you're talking about?
first,thanks for your work with the tutorial
i have a few questions:
it is possible to root with ICS already installed?
by enabling SDE and installing the rooted fimware is the only steps necessary?
if not, is possible to downgrade to honeycomb to gain root?
i have a little of experience with rooting android devices(huawei u8230,still alive and kicking an a nexus s of a friend) and i remember that in some cases with a diferent version of android i had to gain root again.
thanks in advance and sory for the questions
sleepingman said:
first,thanks for your work with the tutorial
i have a few questions:
it is possible to root with ICS already installed?
by enabling SDE and installing the rooted fimware is the only steps necessary?
if not, is possible to downgrade to honeycomb to gain root?
i have a little of experience with rooting android devices(huawei u8230,still alive and kicking an a nexus s of a friend) and i remember that in some cases with a diferent version of android i had to gain root again.
thanks in advance and sory for the questions
Click to expand...
Click to collapse
hi! this firmware is "pre-rooted", meaning you just have enable sde and install the firmware seen in the big STEP 2
Do that, and your device will be rooted. I don't think you can downgrade, however ICS is far superior, surdu already released the rooted firmware
hope that answers your question
thanks for your advice.
the only reason to downgrade is to enable root but if the only needed step is to enable SDE and install this rom, much easier
today or tomorrow im going to do that and after i will post the results
cumps
sleepingman said:
thanks for your advice.
the only reason to downgrade is to enable root but if the only needed step is to enable SDE and install this rom, much easier
today or tomorrow im going to do that and after i will post the results
cumps
Click to expand...
Click to collapse
good luck!
alternate location for phase 1 phase 2 files
Hi Shano56,
Thanks for the thread. It is just what I am looking for. I have upgraded to ICS and want to root it.
One question though, is there an alternate location to down load files "1" and "2" when attempting to temp root?
It seems everytime I go to download Step1 and Step2 in temp rooting I get an error message "all free slots on server are taken try again later" ......
colinevers said:
Hi Shano56,
Thanks for the thread. It is just what I am looking for. I have upgraded to ICS and want to root it.
One question though, is there an alternate location to down load files "1" and "2" when attempting to temp root?
It seems everytime I go to download Step1 and Step2 in temp rooting I get an error message "all free slots on server are taken try again later" ......
Click to expand...
Click to collapse
Hi!
You can download now => https://hotfile.com/dl/149500142/93e089a/Pre_RootEnable_SDE.zip.html
( pre-root with 1 & 2 and enable_sde ). Good Luck !
Hi,
The first post says work in progress. Is this work in progress or is it working without any problems?
Thanks in advance.
Dan
Hi again,
So I couldn't resist. Followed the instructions and all went fine. Looks like I have root access (E.g. can install apps which require root access).
One problem and one question.
Problem: Please ignore if people do not want to talk about this app but adfree doesn't work. says it can't see partition.
Question: Will I always have root access or do I need to go into boot options screen every time that I turn on the device and choose developer edition?
Thanks,
Dan
e9508686 said:
Hi again,
So I couldn't resist. Followed the instructions and all went fine. Looks like I have root access (E.g. can install apps which require root access).
One problem and one question.
Problem: Please ignore if people do not want to talk about this app but adfree doesn't work. says it can't see partition.
Question: Will I always have root access or do I need to go into boot options screen every time that I turn on the device and choose developer edition?
Thanks,
Dan
Click to expand...
Click to collapse
You will have always root accesse if you Remove Android Kernel into SDE recovery ....! Good luck !
e9508686 said:
Hi,
The first post says work in progress. Is this work in progress or is it working without any problems?
Thanks in advance.
Dan
Click to expand...
Click to collapse
hi! i just put WIP up there cause I'm still adding stuff to the guide.. however everything posted is okay to use. it is safe
NEED HELP PLEASE!
1)Okay I tried prerooting using surdu_petru file from previous post
(everything looked fine except touch screen response that a six second delay after prerooting)
2) then ran surdu_petru sde_enable.bat file.
(everyting looked okay, but still had six second screen response delay)
I tried rebooting into recovery holding power and volume down simultaneously, wanted to try sde boot. UNfortunately now I am screwed.
I can only boot in recovery console and there is no OS to boot from.
How do I get back to the semblence of a working system (forget ROOTING) from the recovery console ?
PLEASE HELP
---------- Post added at 06:23 AM ---------- Previous post was at 05:59 AM ----------
okay panic mode has resided......
followed STEP 1 at the first entry of this thread and am back to square one!
Will attempt to root ICS again after a good night sleep!
Can't tell you how much I appreciate this forum.....
Hello guys as a developer when we make a rom, we have alot of requests from people which is fine and good. However, it comes to a point where we have so many requests for things, which we do not have time for in our free time. You have to remember we develop in our free time, and it is not a full time job, it is something we enjoy to do. Developers do expect requests, but not constantly, i will try to add features when people request it, but as explained above some of us, physically do not have the time, but some members annoy you by sending the same messages over and over again so the aim of this thread is:
If the Developers cannot do it, for whatever reason you should try it your self, and not just annoy them about it!
Now before we start there are things I want you to consider, before starting:
Code:
#include
*
* Your warranty is now void.
*By you using my Mods, Roms etc...
* I am not responsible for bricked devices, or 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.
Do not Start a thread with upcoming, or WIP because it is a waste of space, only post it when it is ready.
If you don't plan on continuing development, do not post it!
Do not steal other peoples work, ask them first, if they say no, build your own from a RUU or from source.
You can ask for help from other Developers, but do not annoy them over the issue they will help in their own time
Now the main things are out of the way, just one more thing if you are using lets say my ReVoluTioN RoM as a base if you just place a theme over it, and say it is your work it ISN'T! If you are just going to do that make a new theme thread instead, that way you will be credited, however, if you are adding extra code and your OWN custom HTC apps, or whatever that is maybe then yes it is worth making a new rom thread,ONLY IF IT IS YOUR WORK at implementing such code or new features.
ALSO if you are using a Existing rom as a base, give the developer credit for that and a link to their profile, to make sure you appreciate their work!
Now Onto the Tutorial:
In this guide, or new RoM builders it is a good idea to use an android rom kitchen called dsixda's Android Kitchen it is Compatible with Windows, Linux and Mac OS X.
Just a note about this kitchen:
The kitchen will not automatically turn you into a developer. A developer is someone who writes code or builds something from the ground up and understands exactly what goes on behind the scenes. The kitchen hides all that and puts a user-friendly interface above it. However, this may be the push that gets you into development in the future.
A little bit of prior UNIX command-line knowledge would be useful to get started with the kitchen, but the help guides should be enough for a newbie. Knowledge of command lines is always important if you ever want to get involved in Android or development.
However, just as a reference this is what the user interface looks like:
Main Menu:
1. Set up working folder from ROM
2. Add root permissions
3. Add BusyBox
4. Disable boot screen sounds
5. Add wireless tethering
6. Zipalign all *.apk files to optimize RAM usage
7. Change wipe status of ROM
8. Change name of ROM
9. Check update-script for errors
10. Show working folder information
Advanced Options
11 - Deodex files in your ROM
12 - Add task killer tweak for speed (stock ROM only)
13 - Add /data/app functionality
14 - Add Nano text editor + sysro/sysrw
15 - Add Bash (command shell)
16 - Add Apps2SD
17 - Add /etc/init.d scripts support (busybox run-parts)
18 - Add custom boot animation functionality
19 - Porting tools (experimental)
20 - Tools for boot image (unpack/re-pack/etc.)
21 - Unpack data.img
22 - Sign APK or ZIP file(s)
23 - Convert update-script or updater-script
24 - Miscellaneous optins / Plugin scripts
99. Build ROM from working folder
00. About/Update kitchen
0. Exit
Click to expand...
Click to collapse
In order to make the kitchen work you will need to be running one of the following operating systems:
Windows, this can be from Windows XP all the Way up to Windows 8
Linux/Unix, based system I use ubuntu 11.04 but 12.10 is good too
Mac/OSX, however it is recommended 10.4 or above.
First of all you need to download the kitchen from here: LINK
Once you have downloaded it follow the operating system guide of your choice below:
Windows, XP, 7 and 8:
There are currently three choices for windows users these include:
Cygwin, this is a UNIX command line environment for windows
Virtual Machine, this is a good choice but you need a powerful system, with a fast CPU and lots of RAM!
Use the Ubuntu WUBI installer, this basically creates a installation of ubuntu inside windows, and can be easily uninstalled.
WINDOWS OPTION 1: CYGWIN:
I currently use this option for my Rom compiling, but this is due to the fact I have a 2nd Gen Core i3, and 8GB of RAM if your CPU is not very fast I recommend the third option!
Lets get started then...
Fist of all download the Java JRE for windows, it is recommended you use this link.
Secondly, download the cygwin binaries from here.
Below you will find the additional steps required to get it working properly on your windows based system
Russell664's guide to getting cywin working for HTC Desire C
First of all run the downloaded Cygwin" setup.exe" you downloaded in the last step, but be sure to select the default installation paths, which are:
Install from the internet, to download required packages
install to C:\cygwin, to make it easy to access
Once that is done you will be greeted with the "select packages" screen, from there go to the search box and look for the following packages:
gcc, this is found under the "devel" section to select it click the + icon on the section it is found in. After this find this single package "IT HAS TO HAVE THE EXACT NAME OF gcc NOTHING ELSE! once you have found it click it and press "Skip" after to select more packages.
Once the above is done you will need to search for these packages:
perl, this is found under the section of "Interpreters"
cpio, this is found under the section of "Utils"
util-linux, this is found under the section of "Utils"
ncurses, this is found under the section of "Utils"
zip, this is found under the section of "Archive"
unzip, this is found uder the section of "Archive"
wget, this is found under the section of "Web"
Once this is done click next to begin downloading the required packages, this may take some time to do this.
When everything is downloaded, and installation had completed, there will be a new cygwin desktop icon, once this is clicked a linux terminal will be displayed.
Once this terminal is displayed, we need to next configure "java" do do this follow these simple steps:
First of all type "java" (do it without the quotes) if the terminal says "command not found" go on the the next step. However if it dooes not say that skip these following steps for setting up java
To fix the no command found follow these steps:
First, make a backup of your .bash_profile file in case you make a mistake later in this procedure.
Enter the following in the terminal:
cp .bash_profile .bash_profile.backup
Next, find out where your java.exe file is and run the appropriate command to add it to your Cygwin path.
For example, my java.exe is found under C:\Program Files\Java\jre7\bin, so I had to type:
echo "PATH=/cygdrive/c/Program\ Files/Java/jre7/bin:\${PATH}" >> .bash_profile
Modify the command above so that it matches the actual path to your installed Java.
Remember to add a "\" character before any spaces in your path, as shown above.
Type the following so that the file gets loaded (you only need to do this once):
source .bash_profile
There should not be any errors displayed if successful.
(Otherwise, if you made an error in the .bash_profile file, restore your backup by typing: cp .bash_profile.backup .bash_profile, and then try the procedure again)
If done correctly, then when you type 'java' it should display some help information.
Once this is finished you are now setup to use the kitchen on your Windows based computer!
Click to expand...
Click to collapse
WINDOWS OPTION 2: VIRTUAL MACHINE:
Before considering this option for building Roms in this environment reads the Pros and cons first.
Advantages of using virtual box:
The size of the installation doesn't have to be predetermined. It can be a dynamically resized virtual hard drive.
You do not need to reboot in order to switch between Ubuntu and Windows.
The virtual machine will use your Windows internet connection, so you don't have to worry about Ubuntu not detecting your wireless card, if you have one.
The virtual machine will set up its own video configuration, so you don't have to worry about installing proprietary graphics drivers to get a reasonable screen resolution.
You always have Windows to fall back on in case there are any problems. All you have to do is press the right Control key instead of rebooting your entire computer.
For troubleshooting purposes, you can easily take screenshots of any part of Ubuntu (including the boot menu or the login screen).
It's low commitment. If you later decide you don't like Ubuntu, all you have to do is delete the virtual hard drive and uninstall VirtualBox.
Disadvantages of using virtual box:
In order to get any kind of decent performance, you need at least 512 MB of RAM, because you are running an entire operating system (Ubuntu) inside another entire operating system (Windows). The more memory, the better. I would recommend at least 1 GB of RAM.
Even though the low commitment factor can seem like an advantage at first, if you later decide you want to switch to Ubuntu and ditch Windows completely, you cannot simply delete your Windows partition. You would have to find some way to migrate out your settings from the virtual machine and then install Ubuntu over Windows outside the virtual machine.
Every time you want to use Ubuntu, you have to wait for two boot times (the time it takes to boot Windows, and then the time it takes to boot Ubuntu within Windows).
If you still wish to use the virtual box route follow these steps to get it installed:
Installation of virtual box
The first thing you have to do is obtain VirtualBox. First of all visit the VirtualBox website's download page and install it the same way you would any normal Windows program.
Once Virtualbox is installed, launch it from the windows start menu, after this click New to create a new virtual machine. Once the wizard comes up press the next button as seen below:
{
"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"
}
You can call the machine whatever you want. If you're installing Ubuntu, it makes sense to call it Ubuntu, I guess. You should also specify that the operating system is Linux.
VirtualBox will try to guess how much of your memory (RAM) to use for the virtual machine. If you have 1 GB or less of RAM, I would advise you stick with the recommendation. If, however, you have over 1 GB, about a quarter your RAM or less should be fine. For example, if you have 2 GB of RAM, 512 MB is fine to allocate. If you have 4 GB of RAM, 1 GB is fine to allocate. If you have no idea what RAM is or how much of it you have, just press next.
If this is your first time using VirtualBox (which it probably is if you need a tutorial on how to use it), then you do want to Create new hard disk and then click Next.
Click next at this section, don't change anything!
A dynamically expanding virtual hard drive is the best option, because it'll take up only what you actually use. I have come upon weird situations, though, when installing new software in a virtualized Ubuntu, in which the virtual hard drive just fills up instead of expanding. So I would actually recommend picking a Fixed-size storage.
Ubuntu's default installation is less than 3 GB. If you plan on adding software or downloading large files in your virtualized Ubuntu, you should tack on some buffer.
Click Create and wait for the virtual hard drive to be created. This is actually just a very large file that lives inside of your Windows installation.
Then this will show up:
The next thing to do to make the (currently blank) virtual hard drive useful is to add the downloaded Ubuntu disk image (.iso) boot on your virtual machine. Click on Settings and Storage. Then, under CD/DVD Device, next to Empty, you'll see a little folder icon. Click that.
Select the Ubuntu .iso you downloaded earlier.
Once the image is selected, click ok.
You may get a bunch of random warnings/instructions about how to operate the guest operating system within VirtualBox. Read those, and then you may also want to mark not to see those again.
Wait for Ubuntu to boot up.
Once it's started up, just follow the regular installation procedure as if you were installing Ubuntu on a real hard drive (instead of a virtual one).
Afterwards, in order to use your virtualized installation (instead of continually booting the live CD), double-check that the CD/DVD Device entry is Empty again.
Now you have ubuntu installed on virtualbox! Now on the the next part, making the kitchen work.
WINDOWS OPTION 3: WUBI INSTALLER:
Before you start this download the ubuntu iso image from the website, and burn it to a cd!
You may want Linux but think Virtual Box is too much effort to install, or it runs too slow for you, then you can try the 'Wubi' installer from Windows. This method will install Ubuntu Linux inside a file in your Windows operating system and will boot from it.
Use this method only as a last resort, as it will modify your PC's boot loader and may also require some hunting for video drivers if you're not lucky. The benefit to this method is that it runs the kitchen super fast. The downside is that setting it up may require some technical expertise and Linux experience! If it's not working out for you, just go back to Windows and run the Wubi installer again to uninstall.
You can find lots more info about Wubi in YouTube and Google search. In the meantime, here is a summary of the required instructions:
First, download and install the Wubi installer. A good size to allocate for Ubuntu would be 20 GB (this is for all your roms and updates)
When it finishes installing, the PC will reboot.
Select Ubuntu from the boot selection menu.
Notes:
NOTE: If the screen remains blank afterwards and never shows the login screen, then you have a video driver issue. You will need to reboot, and then at the Ubuntu boot options, press 'e' to edit the command line. To force the generic video drivers you will need to add something like this: nomodeset (Just Google it)
When you arrive at the desktop, configure your Wi-Fi connection by clicking on the seashell-shaped icon at the top right section of the screen.
Follow the instructions in the next section of this FAQ ("Ubuntu Linux") for installing Java. That should be all you need to do. I really hope this helped you out.
NOTE: If you had to do the video workaround earlier on, then you'll need to edit /etc/default/grub and change the appropriate lines so that it always boots up in this mode and so you won't need to edit it every time in the boot menu. i.e. Open up an xterm and then type sudo vi /etc/default/grub, modify the file, then type sudo update-grub. Again, Google is your friend.
Ubuntu 11.04 to 12.10:
UBUNTU NATIVE INSTALL:
Before you follow any of these step mentioned in this ubuntu section, you NEED to have it installed either on a physical drive (Partition) or inside a virtual machine. If you do not meet the requirements you need to first install ubuntu, which will be mentioned above this post.
Okay these next steps of setting up the running requirements for the kitchen on linux are very easy compared to the windows setup, the required steps are:
First open up the terminal windows, the buttons to quickly do this are:
Code:
CTRL + ALT + T
If you are using the 64-bit version of ubuntu, type the following into your terminal:
Code:
sudo apt-get install ia32-libs
Now if you go onto the ubuntu market place, a shortcut is found on the sidebar.
Once you are in to market, in the search bar type "Java"
There will be many choices which come up, but you need to install the package name of:
Code:
OpenJDK Java Runtime
This option is usually displayed at the top of the search result.
Once the Java has installed, type "java -version" If installed correctly it will bring back some information into the terminal.
Code:
java -version
If you are using Ubuntu in a virtual machine, you NEED to follow these extra steps to complete installation.
This thread will be updated as soon as possible, i need to get other stuff done so hang tight.
Configuring DSiXDA's kitchen
Just to note the HTC Desire C is not compatible with kitchen, there is a work around that works perfectly so follow the steps further down the thread, these are the officially supported devices for a reference:
Remember this is a reference, and is extracted from DSiXDAs thread itself.
Code:
Acer Liquid
Dell Streak 7
HTC Amaze 4G
HTC Aria / Liberty
HTC Desire
HTC Desire HD / Inspire 4G
HTC Desire S
HTC Desire Z / Vision / T-Mobile G2
HTC Dream / G1
HTC Droid DNA
HTC Droid Eris
HTC Evo 3D
HTC Evo 4G
HTC Evo 4G LTE
HTC Evo View 4G (untested)
HTC Evo Shift 4G
HTC Flyer (untested)
HTC HD2
- Use NAND ROM method (Please follow this thread for details)
HTC Hero / G2 Touch
HTC Incredible
HTC Incredible 2
HTC Incredible S
HTC Legend
HTC Magic / myTouch 3G
HTC myTouch 3G Slide
HTC myTouch 4G / Glacier
HTC Nexus One
HTC One S
HTC One X
HTC One X+ (AT&T and International versions)
HTC One XL
HTC One V (including CDMA version)
HTC Rezound
HTC Sensation
HTC Tattoo / Click
HTC Thunderbolt
HTC Wildfire / Buzz
HTC Wildfire S
Huawei Ideos X6
- Please follow this thread for details
Huawei U8100/U8110/U8120/U8150/U8160/U8180/U8650
Huawei U8220 / T-Mobile Pulse
LG Ally
LG GT540 Optimus
LG Nexus 4 (mako)
LG Optimus 2X (P990)
LG Optimus Black
- Please follow this thread for details
LG Optimus G2X (P999)
LG P500
- Please follow this thread for details
LG Shine Plus
LG Vortex
Micromax A60
Motorola Atrix (unconfirmed)
Motorola CLIQ / CLIQ XT
Motorola Droid
Motorola Droid Bionic
- Please follow this thread for details
Motorola Milestone (unconfirmed)
- You may need to remove the boot.img before building
Samsung Galaxy Ace 2 - GT-I8160(L/P)
Samsung Galaxy Mini
Samsung Galaxy Nexus (untested, 'maguro' and 'toro' versions only)
Samsung Galaxy Note
- GT-N7000 - please follow this thread for details
- SGH-I717 - Please follow this thread for details
Samsung Galaxy Note 2
- Supported for:
-- Sprint variants - SPH-L900 - Please follow this guide
-- T-Mobile variants - SGH-T889(V) - Please follow this guide
-- Verizon variants - SCH-I605
(unconfirmed - see this equivalent guide)
-- International variants - GT-N7100/N7105(T)/N7108
(unconfirmed - see this equivalent guide)
-- AT&T/Rogers/Bell/Telus variants - SGH-I317(M)
(unconfirmed - see this equivalent guide)
-- US Cellular variants - SCH-R950
(unconfirmed - see this equivalent guide)
Samsung Galaxy R GT-I9103
Samsung Galaxy S (GT-I9000 and most variants)
- Please follow this thread for details
Samsung Galaxy S Plus (GT-I9001)
- Please follow this thread for details
Samsung Galaxy S2
- Supported for:
-- GT-I9100 and Exynos CPU variants - Please follow this thread for details
-- Qualcomm/LTE variants
(AT&T Skyrocket, Rogers, Telus, T-Mobile, Bell HD LTE SGH-I757M,
Telstra GT-I9210T)
- Please follow this thread for details
Samsung Galaxy S3
- Supported for:
-- T-Mobile/Mobilicity/Wind variants: SGH-T999(V) - Click here for a guide
-- AT&T/Rogers/Bell/Telus variants: SGH-I747(M) - Click here for a guide
-- Verizon variants: SCH-I535, SCH-R530U - Click here for a guide
-- Sprint variants: SPH-L710, SCH-L710 - Click here for a guide
-- International variants: GT-I9300(T) - Click here for a guide
-- International LTE variants: GT-I9305(T) - Click here for a guide
-- Korean variants: SHV-E210K/L/S and SHW-M440S (unconfirmed)
Samsung Galaxy W (GT-I8150)
- Please follow this thread for details
Samsung Nexus S / Nexus S 4G
Sony Ericsson Xperia 2010 devices (X10 / X10 Mini / X10 Mini Pro)
- Can only build ROM without boot.img (please follow this thread for details)
Sony Xperia 2011-12 devices, specifically:
- TX, P, U, Sola
- Active, Arc, Arc S, Mini, Mini Pro, Neo, Neo V, Neo L,
Play, Ray (follow steps below):
- Can only build ROM without boot.img
- If using stock FTF for kitchen:
1) Unzip FTF file, extract the system.sin
2) Dump system image from system.sin w/ Flashtool
(Advanced-> SIN Editor)
3) Rename dumped file to system.img
- OR If using Nandroid backups: Rename system.yaffs2.img to system.img
- Use this system.img in kitchen's original_update folder
- WARNING - If using a ROM made from system.sin (not Nandroid), it
is recommended to flash from the temporary (fastboot) Clockwork
Recovery, rather than the regular Clockwork Recovery, otherwise
device may not boot (possibly because custom recovery files in
system folder are not added to ROM? e.g. recovery.tar).
ZTE Blade / Orange San Francisco
Now for the compatibility fix details
There are one of two ways you can do this, these being:
Do the file editing manually, I will explain it step by step for you.
Or be lazy and use my provided file at the bottom if this post.
If you choose to learn a little bit more from this tutorial, you may want to go the manual route. That is all well and good, however, follow these instructions precisely, or you could cause a lot of problems with your phone. If you don't feel safe doing it manually, use my file below to make sure that does not happen.
Here we go...
Option 1:
By this step your kitchen should be downloaded, and confirmed that it does in fact start up, if it does your set to go and follow these remaining steps.
In your kitchen directory, you will find a tools folder you want to Click that and then the Edify_defs folder after that, the file structure should look like this:
Code:
C:\cygwin\home\yourusername\Kitchen\tools\edify_defs
This is on a Windows based system.
Code:
\home\yourusername\Kitchen\tools\edify_defs
This would be on a linux based system, it will be very similar.
Once you are in this folder save a file called "Golfu". (You can do this by saving the file as a blank text document, but save it as *file insted of .txt)
Get a recovery.img (Yes the one used for flashing your recovery, or a stock one) And save it in the "Original_update" folder, the file structure should look like so:
Code:
C:\cygwin\home\yourusername\Kitchen\Original_update
This is on a Windows based system.
Code:
\home\yourusername\Kitchen\Orginal_update
This would be on a linux based system, it will be very similar.
Once you have done that follow these menus through the kitchen:
Code:
Advanced --> Tools for boot image --> Extract from boot.img/recovery.img in any folder.
Once this is done, once again go to the Orginal_update folder and you will find the extracted recovery.img, open it's ramdisk folder and Follow this file structure:
Code:
/system/etc/recovery.fstab or /etc/recovery.fstab
After you have found this file open it with a text editor. (Due to this being code, you will want it in a neat fashion, this is why I recommend NOTEPAD++ for windows user, linux user you are fine with the standard one included)
When looking at the code you are looking for these lines:
Code:
sys_mnt=\/dev\/block\/[B]mmcblk0p25[/B]
cache_mnt=???
data_mnt=???
sdcard_mnt=???
However you are only really looking for the system block number, you can add data etc later on manually though updater scripts it is much easier. Remember you are looking for this line highlighted in bold, you can just copy that number down, it is the same for every HTC Desire C.
The last step is too add these lines you have found, to the "golfu" file you created, basically you want it to look exactly ike the code below, copy and paste it if you wish:
Code:
change_mnt=yes
param1=ext4
param2=EMMC
param1_sdcard=vfat
param2_sdcard=MTD
sys_mnt=\/dev\/block\/mmcblk0p25
cache_mnt=???
data_mnt=???
sdcard_mnt=???
Now the configuration is now done of the kitchen, now you can move onto how to build your Rom from a RUU, or from an exsting rom such as Revolution, or nameless.
Option 2:
As said in option 1 you need to make sure you Rom kitchen starts up and shows the menu, this means it is working. If it does not do that you have done something wrong.
Basically you need to download this attached file, unzip it and place it in the following directories. (Make sure you read to notes at the end of the directory code, so you know what operating system it is aimed at)
Move the file here:
Code:
C:\cygwin\home\yourusername\Kitchen\tools\edify_defs\thefileyoudownloaded
This is on a Windows based system.
Code:
\home\yourusername\Kitchen\tools\edify_defs\thefileyoudownloaded
This would be on a linux based system, it will be very similar.
That is basically it, now you need to read below, on how to actually build your roms.
Reserved for FAQ
Great Russell! I'm glad to see a guide of this nature within our forum, it will certainly help to promote further development on our device. There are a lot of guides available concerning this topic, however none that have anything specific to the Desire C, I look forward to seeing the completed guide!
First post updated, nearly finished, the windows section is finished, the ubuntu section needs a little bit of work. However this guide is ready to use for people who plan on using windows.
Good luck guys.
russell664 said:
First post updated, nearly finished, the windows section is finished, the ubuntu section needs a little bit of work. However this guide is ready to use for people who plan on using windows.
Good luck guys.
Click to expand...
Click to collapse
Thankyou russell I plan on following this ...once I get the time . I'm out of thanks again this morning which is weird as I havn't used any today . I will spam you later :good:
Thanks Rich
The thread should be complete tomorrow, with the ubuntu section.
Sent from my HTC Desire C using xda premium
I can't get Ubuntu installed, the installation freezes at about 75%. Tried using Wubi and real installation on a partition.
I suggest you to use Ubuntu on dual boot. Boot Ubuntu from stick.
I know but that is just a demo
Sent from my HTC Desire C using xda app-developers app
You can install it from the demo, let it load to the desktop. There is a icon saying install ubuntu on the desktop, click it and install ubuntu. You can do this from a USB stick or cd
Good luck.
Sent from my HTC Desire C using xda premium
That's what I did, installation doesn't complete but freezes after about 75 per cent
Sent from my HTC Desire C using xda app-developers app
Could you take a picture of the screen?
Are you installing on a VM, and if so how much RAM have you allocated to you VM, and how much does your system have?
Sent from my HTC Desire C using xda premium
Strange, okay if you are using a VM my recommendation is to use 2Gb of ram, if you have 4GB in your computer. However installing linux is still your best option. Now if ubuntu does not work for you, you can try linux mint. This already has java installed, and can run the kitchen out of the box, all you need to do is make it comparable with our phone.
The main thing what I think could be happening is lack of ram or possible corrupt image of ubuntu, try the linux mint approach and update us with your results mate.
Best of luck.
Sent from my HTC Desire C using xda premium
Not using a vm my computer wouldn't be able to run smoothly it's pretty crap
I'll re download the iso and try again, if that doesn't work ill try Linux mint
Sent from my HTC Desire C using xda app-developers app
update: still didn't work, downloading linux mint right now...
does anybody know a way to install that awesome looking unity interface on mint?
Use the version of ubuntu from this link http://forum.xda-developers.com/showthread.php?t=2152398
It already has most of the packages required for building a rom preinstalled
Unity awesome? never KDE is much better im my opinion.
Yes you can install it with the command:
Sudo apt-get update
Sudo apt-get ubuntu-desktop
That will install unity for you.
nikhil16242 said:
Use the version of ubuntu from this link http://forum.xda-developers.com/showthread.php?t=2152398
It already has most of the packages required for building a rom preinstalled
Click to expand...
Click to collapse
Staahp!!! xD
So many choices... my linux mint download only just completed and you posted that xD
will look at it later
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.
Code:
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!! Everything you do, !!
!! you do at your own peril and risk. !!
!! !!
!! I do not bear any responsibility !!
!! for your faulty devices. !!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!! !!
!! THIS ROM IS ONLY FOR THE EXYNOS VERSION !!
!! !!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
First I would like to thank NoKit, monich, elros34 and all the Sailfish OS porter guys who helped me to make this port.
Thank you very much guys!
News 05/03/2023: OTA to SFOS 4.5.0.18
26/10/2022: OTA to SFOS 4.4.0.72
14/07/2022: OTA to SFOS 4.4.0.68
08/06/2022: OTA to SFOS 4.4.0.64
30/05/2022: OTA to SFOS 4.3 & 4.4
22/02/2022: OTA to SFOS 4.2
16/10/2021: Waydroid on Galaxy Note4 (SFOS 4.1)
03/09/2021: OTA to SFOS 4.1
23/03/2021: OTA to SFOS 4.0
Requirements:
Before you start to download anything, please read all this through carefully.
The first requirement is your device must be rooted and you should be able to install a custom recovery (preferably TWRP) onto it.
Installation instructions:
1. Download all files, LOS14.1 zip, Sailfish OS zip and twrp2.8.7.img to the external SD card on the phone
2. Reboot into TWRP (Hold buttons: Power on + Home + Volume up)
At this point you should install TWRP 2.8.7 as the installation work the best with this recovery.
Once you flashed TWRP 2.8.7, please reboot into recovery and continue the process.
3. Do a factory reset
4. Still in recovery, flash the LOS14.1 image
5. Still in recovery, flash Sailfish Os image
8. Reboot
9. Enjoy the latest (3.3.0.16) Sailfish OS on your Note 4 (treltexx).
You will need patience as the first boot will take for a while. Then you can go through the initial Sailfish OS set up.
This Sailfish OS Android HAL based on LOS 14.1.
Downloads:
twrp2.8.7.img for Note 4 (treltexx)
LOS14.1 for Note 4 (treltexx)
Sailfish OS 4.5.0.18 for Note 4 (treltexx) - 05/03/2023
Sailfish OS 4.4.0.72 for Note 4 (treltexx) - 26/10/2022
Sailfish OS 4.4.0.68 for Note 4 (treltexx) - 13/07/2022
Sailfish OS 4.1.0.24 for Note 4 (treltexx) - 09/09/2021
Sailfish OS 3.3.0.16 for Note 4 (treltexx) - 09/10/2020
Boot logo updater for Note4 (treltexx)
kernel for lxc support (this kernel is only for sfos 3.3, the newer OTA updates all have this support!)
fix for 'Private number' calls
Problems/Solutions:
Problem: LXC container doesn't start on any of these two builds.
Solution: In TWRP install the kernel for lxc support. (This will be included into a later build.)
Problem: Incoming calls are not displaying the number only the 'Private call' text.
Solution: Install the fix for 'Private number' calls rpm. (This will be included into a later build.)
Some useful patches:
Patchmanager 3.0
More folder icons
Operator name at bottom (Stopped working on 3.3.0.16)
Silica mail (transparent background) - Well documented here
Apps from Openrepos
Apart from the Jolla store there are plenty of other, community made apps in Openrepos. There is a user-friendly app to install/remove apps from this source called Storeman. It can be downloaded and install from this location: Storeman
Debug/login/troubleshooting:
In Ubuntu, connect USB cable. telnet 192.168.2.15 2323 or SSH [email protected].
Notes:
On Sailfish OS, as it is a Linux system, you cannot install/run any android apps.
How to make a backup/restore with TWRP:
You can boot into TWRP with the usual button combination (Hold buttons: Power on + Home + Volume up) and can make backup/restore.
Battery life
In my experience this build gives a very good battery life (I've tested with a new battery and it drops beteen 5% - 10% overnight with wifi on)
Changelog:
10.10.2020
=========
Custom (Sailfish OS) boot logo
09.10.2020
=========
Sound fix is included, it works out of the box
GPS fixed!
S-Pen works as a mouse! To make the cursor visible (thanks for elros34!) you need to install:
Patchmanager 3 from openrepos
mousetracker
amend '/var/lib/environment/compositor/droid-hal-device.conf' file, add the -plugin evdevmouse:abs:/dev/input/event3 to the end of LIPSTICK_OPTIONS. (That line should look like this:
Code:
LIPSTICK_OPTIONS=-plugin evdevtouch -plugin evdevkeyboard:keymap=/usr/share/qt5/keymaps/droid.qmap -plugin evdevmouse:abs:/dev/input/event3
as final step apply the moustracker patch in Settings/Patchmanager, then restart the services (pulley menu in Patchmanager) or reboot, then pull out the S-Pen and use it as a stylus/mouse.
(Note: As patchmanager doesn't yet work when the default user is defaultuser, the instruction above works only on sfos 3.3.0.16 or the OTA updated 4.0.1.48. On fresh sfos 4.0.1.48 install you need to install mousetracker and manually apply the patch from it.)
28.09.2020
=========
Work:
Screen
Touch
IMEI number is detected
Sensors (Rotation, Acceleration, Gyroscope, Magnetometer, Light & Proximity)
GPS (The permanent solution will be included in a future build. Now, the workaround is (do it only once): as root delete the folder /data/system/gps and then reboot. GPS should start working)
Notification LEDs (white, green, blue, red)
Wifi
MTP
Bluetooth
Calls incoming/outgoing
Messages incoming/outgoing
Mobile data
External SD card detected and mounted to /run/media/nemo/_sdcard_name_ (where _sdcard_name_ is the name of the sd card when it was formatted like 4B93-785B)
Home button and the Back soft button
Vibra
Pixel ratio and icons set to 2.00
Audio is routed to headphone if that presents
Camera front/rear
Video recording (only on the rear camera)
Jolla store (please skip the account creating/adding in the initial setup)
findutils is installed by default (updatedb and locate commands work out of the box)
Torch
can boot into TWRP recovery with the usual button combination (hold buttons: Power on + Home + Volume up)
Low Power Mode (AKA "sneak peek" or "ambient display") works (install instruction is in this post)
Sound - Please download the 'Sound fix script for Note4 (treltexx)' and save it into /home/nemo/Download, then give it executable permission and run as root or do the following:
Download the 'Sound fix script for Note4 (treltexx)' and save it into /home/nemo/Download
goto Settings/Developer tools, enter a Password and save it
start the Fingerterm app and within, issue the following commands
devel-su (press enter, then enter the password you set)
chmod +x /home/nemo/Download/soundfix-treltexx.sh
/home/nemo/Download/./soundfix-treltexx.sh
Do not work:
USB mode selection from Settings (workaround: as root run 'systemctl restart usb-moded' command)
Video recording on the front camera
Video playback in Gallery app (You can use Kodi for playing videos)
Internal SD card is not mounted to /android
S-Pen WIP
Extra 1: Change boot logo, Download warning image, Charring image and Download image for Sailfish OS like.
Simply download the Note4-Boot-Logo-Updater_by_edp17.zip from the download section and flash it with TWRP.
Important!: Once the zip is flashed, boot into recovery again, then you can boot into Sailfish OS.
To revert these images back to original:
Download the original param.bin and flash it with heimdal:
Code:
heimdall flash --PARAM param.bin
Inspired by this post
Extra 2: Desktop Linux distro install/run on the Note 4!
1. First flash the kernel from the Downloads section (in a later build this kernel will be included)
2. Install all the following packages:
lxc
lxc-templates
nemo-qml-plugin-dbus-qt5
sailfish-polkit-agent
python3-base
python3-gobject
dbus-python3
lxc-templates-desktop
qxdisplay
harbour-containers
mouse cursor support for SFOS and LXC
3. Once the packages are installed, fire up the LXC and install a distro into it (e.g. Debian SID)
On the Note 4 the harbour-containers GUI doesn't work properly. Fortunately the desktop distro installation can be done from a command line. Here are the steps:
sudo lxc-create -t sfos-download -n mycontainer
follow the instruction and set the distribution (e.g. debian) then the version (e.g. sid) then the architecture (armhf)
example command: sudo lxc-create -t sfos-download -n mycontainer -- --arch armhf --dist debian --release sid
sudo lxc-start -n mycontainer
sudo lxc-attach -n mycontainer
then within the container:
/mnt/guest/setup_desktop.sh
/mnt/guest/setups/debian.sh
4. Once the Desktop distro is installed you can start:
I recommend to use one of these scripts as they save a little time. (Note: You need sudo installed and configured for these scripts!)
Start LXC and desktop in landscape mode with mouse support: debian-mouse-landscape.sh
Start LXC and desktop in portrait mode with mouse support: debian-mouse-portrait.sh
Start LXC and desktop without mouse support: debian.sh
5. Enjoy.
6. More info about the Full linux distros on Sailfish OS.
Pictures:
{
"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"
}
Custom boot logo and other pictures:
Looks really good, have you posted the source on github or anywhere? I made a port of UT for the snapdragon note 4 and would like to make one for the exynos variant
tigerpro357 said:
Looks really good, have you posted the source on github or anywhere? I made a port of UT for the snapdragon note 4 and would like to make one for the exynos variant
Click to expand...
Click to collapse
Yes, all sources are available on github: here
Please let me know when the UT is available for this device! I'd like to try it.
calls not work
Oh, it's you again dude That is AWESOME
lee.wp14 said:
Oh, it's you again dude That is AWESOME
Click to expand...
Click to collapse
I am still chasing my n7000. Once I got that I will complete that port too. Will let you know.
usaman65 said:
calls not work
Click to expand...
Click to collapse
What variant of Note 4 is that? This port is for the European Exynos version (SM-N910C).
edp17 said:
What variant of Note 4 is that? This port is for the European Exynos version (SM-N910C).
Click to expand...
Click to collapse
test on n910c .sound also not work
usaman65 said:
test on n910c .sound also not work
Click to expand...
Click to collapse
Yeah, I installed the build again and tested these. I can confirm these do not work. Hmm, all those worked fine on all previous builds, so I am not sure why the stopped working. It seems permission issue to me. I double check and will come back with a solution. Thanks for reporting!
edp17 said:
Yeah, I installed the build again and tested these. I can confirm these do not work. Hmm, all those worked fine on all previous builds, so I am not sure why the stopped working. It seems permission issue to me. I double check and will come back with a solution. Thanks for reporting!
Click to expand...
Click to collapse
any patch possible for android apps ?
usaman65 said:
test on n910c .sound also not work
Click to expand...
Click to collapse
I have figured out a solution to the sound issue. It was me forgot to include this into this build. I will add it into a later one. Until then, please follow the instruction from the main post. (I added a script into the Download section and a comment how to apply it.)
For me, this fix solved the issues with calls and torch too.
edp17 said:
I have figured out a solution to the sound issue. It was me forgot to include this into this build. I will add it into a later one. Until then, please follow the instruction from the main post. (I added a script into the Download section and a comment how to apply it.)
For me, this fix solved the issues with calls and torch too.
Click to expand...
Click to collapse
thanks its fix now .tuch missing some time while tipping
who to install lxc for desktop linux .nothing find on google
usaman65 said:
who to install lxc for desktop linux .nothing find on google
Click to expand...
Click to collapse
How do you mean? There is instruction in the first post and there is a link to the main post of lxc (option 5).
edp17 said:
How do you mean? There is insttuction in the first post and there is a link to the main post of lxc (option 5).
Click to expand...
Click to collapse
there is a link but cannot find all required files .and how to fire lxc ...? cannot find harbour-containers .there is a link but cannot instaled it
usaman65 said:
any patch possible for android apps ?
Click to expand...
Click to collapse
No, none of the community ports have support for android apps. However you can install a desktop linux and can run desktop apps. (Although very few is touch control friendly.) Instruction for how to install a desktop distro on this device is available in the main post.
usaman65 said:
there is a link but cannot find all required files .and how to fire lxc ...? cannot find harbour-containers .there is a link but cannot instaled it
Click to expand...
Click to collapse
The link to the harbour-container is in the 'Extra: Desktop Linux distro install/run on the Note 4!' section (main post).
Although, here is how to install it, follow these steps:
download the 'harbour-containers-0.4-1.armv7hl.rpm' from this link.
open a terminal (Fingerterm)
type: devel-su (then press enter, then type your password and press enter again)
go to the library where you downloaded the rpm file
type: pkcon install-local harbour-containers-0.4-1.armv7hl.rpm (then press enter)
!Note: Before installing the harbour-container, you need to install ALL the other packages that are listed in the 'Extra: Desktop Linux distro install/run on the Note 4!' section (main post).
There is a full topic about all of this (also provided in the main post) here.
Does it work on note 4 n910v verizon?
Hola117 said:
Does it work on note 4 n910v verizon?
Click to expand...
Click to collapse
I think the N910V is not an Exynos but a Snapdragon device. This means, no, this port won't work on that. Sorry.
edp17 said:
I think the N910V is not an Exynos but a Snapdragon device. This means, no, this port won't work on that. Sorry.
Click to expand...
Click to collapse
you are correct, the 910V is a snapdragon device, its actually what I used to do my Ubuntu Touch port, BTW, I am still going to do a exynos note 4 UT port, just been busy