Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This guide is for:
SuperPad / Flytouch2 / WWE10 Tablets
Make sure you've got the right device.
- Infotmic 10.2" Flytouch2 SuperPAD
- It has 256MB RAM
- It has 2GB Internal Storage
- Android OS 2.1
- Have 2 MicroSD Card Slots
- 1024x600 Screen Resolution
- Infotmic X210 Processor
This ROM is NOT for you if your device is SuperPad 2 / Flytouch 3
- Infotmic 10.2" Flytouch2 SuperPAD
- It has 512MB RAM
- It has 4GB Internal Storage
- Android OS 2.2
- Have 1 MicroSD Card Slots
- 1024x600 Screen Resolution
- Infotmic X220 Processor
-------------------------------------------
Warning: Follow these steps. All of them. If you do, it will work. If you misread or miss a step or skip a step because you are hurrying through the process, it WILL brick your tablet. Flashing is a relatively simple process but it requires patience. If you don't have the time to read all of the directions and follow them, YOU DO NOT HAVE TIME TO FLASH, and stick with your old firmware.
I AM NOT RESPONSIBLE FOR ANY DAMAGE THAT THIS ROM HAS CAUSED. FLASH AT YOUR OWN RISK! SINCE THERE ARE SO MANY CLONES OF THIS TABLET, DON'T EXPECT IT WILL WORK PERFECTLY.
-------------------------------------------
Note: I'm not so good in English and grammar, so bear with me. The images is not so clear co'z im using webcam for fast capture and focusing.
If I made mistakes, corrections are welcome.
:: Super Improvement ::
- Much Faster response, you will notice playing Angry Birds is smoother.
- New Default Application updates
- New Icons
- New 3D Gallery
- Supports Flash on browser.
- GPS is now working, GPS app required to test the satellite lock.
- Youtube on browser working fine if you have fast connection.
:: Known Issues ::
- "Some" RJ45 (Ethernet) Port sometimes not working
- "Some" WiFi unstable
- "Some" 3G Device not working
- Market is still free, no paid apps.
- Save path not on MicroSD but inside your Tablet (fixed)
- When it sleeps, it sleep to power off.
- Youtube App is not working, you need to download another compatible version.
:: Thanks to the Donors ::
- Austin Pc Fixed .Com
- frank rugolo
- pastorb1
:: Credits ::
- stragulus
- dgcruzing
- isergio
- _barsuk_
- Aries on an Android (android tablet forum)
- rgocal (android tablet forum)
- and others who I forgot to mention
This guide is for Windows XP, I'm windows7 user before but I downgrade because I want to use my other old softwares for flashing. If you get the idea you can do this also on windows7.
------------------------------
NOTE:
- For windows7 user Run As Administrator the IUW application.
- 64bit Operating System may not work with IUW application.
------------------------------
NOTE: If your tablet showing version 6.1.5 (559[or higher]) or 0.6.1.2(587) Then you can skip some part of the guide. Scroll down directly to the "Alternative Solution" using MicroSD burning. You still need to download the Android 2.2 Froyo Main Firmware.
------------------------------
:: Preparing the Male to Male USB Cable :: (if you have one skip this)
Ok let's start, what you need is a male to male USB cable, if you don't have one you can make your own male to male cable.
Tools
- 2 USB Cable
- Scissor or Cutter
- Electrical Tape or anything to cover the exposed wire
- Solder Lead (Optional)
- Soldering Iron (Optional)
1. Cut each USB to the nearest tip of the female, to make your USB cable longer.
2. Cut each end of the USB to expose the wires and copper wires.
3. Now you can connect each end of the USB, and twist each wires, you can solder it if you like.
4. Now you can tape each wires, and tape all the wires.
This is the finish product.
:: Preparation for Files and Flashing Procedures ::
*Note: Please PM me if there are missing links.
Download IUW 1.1 Flashing Tool
Download Firmware V2852
Download Uboot - V 0.6.1.2(587) working camera
Download Main Android 2.2 Froyo ROM with Flash 10.1
Download New Ramdisk image to change the path of save files to SDCard1
Download Extra Tools Apps
Updated ROM: 25.11.2011
Download Firmware Froyo 2.2 v2.5 #4325
------------------------------------------------------------
:: Clean up the tablet files ::
- Wipe cache partition
- Wipe data/factory reset
- then reboot.
Remove all microSD so that it will not start burning if you have firmware on your microSD.
Visit this link how to clean the data for your tablet.
------------------------------------------------------------
:: Let's Start ::
1. Make a Folder on your desktop for fast track of your files, I named it Froyo 2.2 and save all your downloaded files here.
2. Download IUW Flashing tool, and save it inside the folder of your desktop.
3. After download, unpack it inside the folder.
NOTE: Your tablet should be full charged, and connect the charger while flashing, just to make sure it will not drain much power on your tablet. Don't forget also to remove all your MicroSD cards from the tablet.
4. Since your done making your USB Cable, your tablet should be off and plug the other end USB to the PC and plug the other end on your tablet USB Port between the headphone jack and SDCard Slot 1.
5. Open the IUW application, select Link USB on the left side. And on the Link information the DV (driver) is greyed, because it's not detecting the tablet with driver.
6. Power up the tablet with this combination Power + Menu button for few seconds until you see the message on your tablet "Communicating with PC..."
7. A New Hardware notification will pop up on your PC Screen.
(you have 2 minutes to setup this or the tablet will boot normally)
Select Advance, Next.
Browse the driver from your desktop inside the folder "otg_driver"
Then it will install the driver.
The flasher will turn to green.
:: FLASHING V2852 ::
This rom will only run on tablets which display a version number in the bottom-right "Infotmic" screen when first turned on.. If yours doesn't display a number there, you will need to flash firmware v2852 first.
8. 'Choose a wrapped image' press the "..." button Select the IUS file "WWE10B_Android_393477-v9full.ius"
9. Click 'burn' to flash the tablet.
This picture is flashing the tablet.
10. After burning finishes, plug out the USB cable and press Reset, then restart the device.
:: Flashing UBOOT ::
11. Open UIW application, and connect your tablet USB to PC.
12. Select "Link USB" on "USB Mode:" select "Expert Mode" Uncheck all except "UO".
13. Browse the "u-boot-nand.bin" the one with working camera.
14. After flashing this is the result.
15. Your screen with start to flicker, it will start to initialize.
16. I will take time to load up, until you are in display calibration.
:: Flashing IMAGES ::
17. Power off your tablet, and prepare again the UIW to flash the main android 2.2 firmware.
18. Click Link USB, and select Expert burn.
NOTE: Use the other Ramdisk.img fix you download, not from the flash10.1-android2.2 folder.
19. Power up the tablet with this combination Power + Menu button for few seconds until you see the message on your tablet "Communicating with PC...", if the Dv is green your ready and click the burn button.
20. I will take time to load up, until you are in display calibration and your Done!
:: Alternative Solution ::
If you cant burn the main android image using USB method. You can try the MicroSD card method, but this is only applicable if your tablet will display the version under the InfoTMIC start up logo.
Lets make a bootable MicroSD, to convert the file size to 700~705MB, you need a MicroSD at least 1GB.
Download WinHex with MicroSD Clone Image.
1. Open your WinHex
2. Click Tools->Disk Tools->Clone Disk->
3. On Source Raw Image: click the file button.
locate the "aben.start sector" file, click open.
4. On Destination Medium: click the drive button.
locate the Physical Media of your card reader/MicroSD, ok.
5. Fill in the Start Sector with 0 (zero).
6. Click OK, and WinHex pop up will appear, click OK and it will start cloning the image file to your MicroSD.
7. A notepad will pop up that you are done cloning the image, close and press OK on the pop up message.
8. Close WinHex, and safely remove the card reader/MicroSD.
9. Plug the card reader/MicroSD again, and do a quick format.
10. If you successfully formated the MicroSD to 700~705MB then create an "android" folder, and copy all the main image files on the folder. And your Done! :: If you fail there are some other reason, some card reader is not working properly, try to find another card reader, if your phone has MicroSD Slot and able to communicate and serve as card reader, you can use this also.
- ramdisk (use the other ramdisk you download)
- system
- uImage
- userdata
some optional or skipped file.
- u-boot-nand (android v2.2)
- zSYS (Flytouch Official Image 3245)
This is what's inside the MicroSD on android folder.
12. After copying the files plug the MicroSD at the top most/Slot 1 between the 2 USB port.
13. And Power On your Tablet, and it will start Flashing just like here on the video. http://www.youtube.com/watch?v=47kf4-Vbba8#t=3
You can also use this MicroSD to downgrade back to 3245 firmware.
Thank you.
Don't forget to click the Thank You button
joshgabel said:
SmaRkieS whats your Paypal email address? i owe you $ worked like a charm!
Click to expand...
Click to collapse
Confirmed that the 3G USB modem Huawei E1752 is working perfectly. Just create an APN and reboot while the Huawei E1752 is in the USB port.. After startup it makes a connection and works fast!
manually created an APN in settings/connections/mobile providers and configured for your local provider. Also enabled data connection, otherwise I won't start searching. After that reboot and it started working. No specials actions required.
:: Google Sync ::
If you want to sync the calendar (basic) and contacts go to:
Contacts-> Menu-> Accounts-> Add Account-> Corporate-> enter data for a google account -> choose the default setting -> set the sync options-> Enter the name
:: z4root USB Debug solution ::
1. Download Launcher Pro.
2. Install Launcher Pro.
3. Tap the Home Button at the upper left, it will let you choose different type of launchers.
4. Select Launcher Pro.
5. Tap Menu Button = or at press the menu button at the top of your tablet.
6. Tap the + add
7. Tap Shortcuts
8. Scroll Down, and Tap the Activities.
9. Wait it will load, scroll down to Settings.
10. Scroll down and look for Development.
11. Press OK without changing the name.
12. On Desktop/Home Tap Development.
13. Check the USB Debugging.
14. Restart if necessary.
15. And your done ready to root.
:: Enabling Live Wallpapers ::
1. After rooting your device, your good to go.
2. Install Busybox Installer.
3. Open Busybox Installer, OK, SuperUser request Allow.
4. If BusyBox is not found, tap Install.
5. Press Back Button on your tablet.
6. Install Terminal Emulator.
7. Open Terminal Emulator.
8. Type this commands.
Code:
su
mount -o remount,rw,codepage=utf8,vfat,xattr,check=no /dev/stl5 /system
cat /sdcard/LiveWallpapersPicker.apk > /system/app/LiveWallpapersPicker.apk
cat /sdcard/libRS.so > /system/lib/libRS.so
cat /sdcard/librs_jni.so > /system/lib/librs_jni.so
sample pic of my terminal emulator, I made a mistake in line 5 but it's ok just retype it.
9. Reboot your tablet.
10. Install your live wallpaper apps.
11. On your home screen, tap the menu button. (near the volume next to back)
11. Tap Wallpaper
12. Tap Live wallpapers
13. Select your live wallpapers, and your done.
sample screen shot.
:: GPS Configuration and Setup ::
Download GPS Test Tool
1. Install that app in your tablet.
2. Go to Settings
3. Go to Location & Security
4. Check Use wireless networks
5. Check GPS Satellites
6. Plug your GPS Antenna.
7. Take your antenna outdoor, if the wire is still long try to place the antenna higher.
8. Connect to your WiFi.
9. Run the GPS Status application.
10. Wait for 5~20 mins for satellite discovering and locking.
11. Wait for 5 satellite lock on and you are done.
12. Run your Google Maps, and your locked to your location.
This is the picture number of satellites and number of locked satellites.
The GPS is very accurate.
:: Dismantle/Dissemble of Superpad/Flytouch2 ::
http://www.androidtablets.net/forum/gome-flytouch-ii/14255-inside-my-superpad.html
===========================================================
This is my screen now.
with new virtual keyboard.
I also try swapper2, they say it can improve the performance. This is my Terminal Emulator.
Other Useful Guides here.
http://forum.xda-developers.com/showthread.php?t=1067746
http://forum.xda-developers.com/showthread.php?t=1048776
http://forum.xda-developers.com/showthread.php?t=831178
-------------------------------------
Good work
25-12-2012 -updated links
Download IUW 1.1 Flashing Tool iuw1.1-english.rar - 291.98 KB
Download Firmware Froyo 2.2 v2.5 #4325 - 4325.zip - 212.16 MB
Download Uboot - V 0.6.1.2(587) working camera u-boot-nand.zip v0.6.1.2(587).zip - 130.13 KB
Download New Ramdisk image to change the path of save files to SDCard1 Ramdisk_SmaRkieS.zip - 166.06 KB
Barsik recovery for superpad flytouch - recovery_rd.zip - 1.32 MB
Thank you, cause this people are lazy enough to open the pdf/docx file instructions hehehehe.
I made some mistakes on my post, please post some corrections and suggestions are welcome also.
Thank u for your instructions. Its the first time I manually try to flash my pad so I had to flash to 2852 rom first and it does but when i restart and check my version build it is still on build 1561 (flashing with usb cable).
Tried couple of times can u help me out?
kolk11 said:
Thank u for your instructions. Its the first time I manually try to flash my pad so I had to flash to 2852 rom first and it does but when i restart and check my version build it is still on build 1561 (flashing with usb cable).
Tried couple of times can u help me out?
Click to expand...
Click to collapse
Can you see the version under the InfoTMIC start up logo?
If you can see it then you are ready to update using MicroSD method.
@smarkies
no there is no version number
first time I connected to pc it said found new hardware but no driver. There I selected the otg driver in the package.
Burntool does connect and goes up from 0 to 100 procent (very quick about 7 secs.) when i burn but when i check im still on my previous build.
After that I tried to update to other firmware using update.zip on winhexed sd card. This did work so now I am on 1623 build.
after that I tried again using burntool but still didnt work out.
In the folder containing the 2852 rom there are also two folders
0.6.1.2_1.4.587_OV2655 and
0.6.1.5_1.4.587_GT2005
both contain uboot and uboot nand files is there something I have to do with them before I can flash?
Any advice?
Other thing I noticed: in recovery menu there is a line saying:
e:can't open / cache / recovery / command
It didnt stop me from update with update zip but could it be the reason burntool isnt working for me?
kolk11 said:
@smarkies
no there is no version number
first time I connected to pc it said found new hardware but no driver. There I selected the otg driver in the package.
Burntool does connect and goes up from 0 to 100 procent (very quick about 7 secs.) when i burn but when i check im still on my previous build.
After that I tried to update to other firmware using update.zip on winhexed sd card. This did work so now I am on 1623 build.
after that I tried again using burntool but still didnt work out.
In the folder containing the 2852 rom there are also two folders
0.6.1.2_1.4.587_OV2655 and
0.6.1.5_1.4.587_GT2005
both contain uboot and uboot nand files is there something I have to do with them before I can flash?
Any advice?
Other thing I noticed: in recovery menu there is a line saying:
e:can't open / cache / recovery / command
It didnt stop me from update with update zip but could it be the reason burntool isnt working for me?
Click to expand...
Click to collapse
dont touch any file inside the folder of 0.6.1.2_1.4.587_OV2655 and 0.6.1.5_1.4.587_GT2005.
Try to burn the UO first, u-boot-nand.bin the one with working camera, if not try this another u-boot-nand.
Then burn the Main Image Android Rom.
Thanks for the quick repy to be sure I wont Brick my Pad
for the uo file I use Uboot - V 0.6.1.2(587) or uboot - 0.6.1.5 (587)
and for the ROM files I only use files from the 20110416-v1001 folder?
If so I will burn right away
kolk11 said:
Thanks for the quick repy to be sure I wont Brick my Pad
for the uo file I use Uboot - V 0.6.1.2(587) or uboot - 0.6.1.5 (587)
and for the ROM files I only use files from the 20110416-v1001 folder?
If so I will burn right away
Click to expand...
Click to collapse
I abused my pad flashing many times, and still it is alive, It will brick if your USB cable is poorly made, or overpowered that will fry the motherboard of your tablet, just like what happen to other people.
the safest way to flash is microSD, but it is tricky with this froyo update that's why I risk on flashing using USB.
V 0.6.1.2(587) this one has working camera. But you can try both uboot to display the version under the InfoTMIC logo. But I use V 0.6.1.2(587) coz I want the camera to work fine.
Yes the files inside the 20110416-v1001 folder except for the u-boot-nand inside.
If the USB flashing doesnt work you can try the alternative, using the microSD.
Thank u very very much worked like a chime.
camera and wifi are working I used uo V 0.6.1.2(587)
will play with it tonight to see what else it can do now
Greetz
kolk11 said:
Thank u very very much worked like a chime.
camera and wifi are working I used uo V 0.6.1.2(587)
will play with it tonight to see what else it can do now
Greetz
Click to expand...
Click to collapse
Glad you made it! Check out the speed and the Gallery is now 3D
So you did the UO burn first then Main Image?
Confirm this and I will revise my post.
Co'z I burn my tablet the other way. Main Image then UO.
Yep U0 first than main Rom
Only thing is market has only free apps
but doesnt matter can get apps all over the internet
kolk11 said:
Yep U0 first than main Rom
Only thing is market has only free apps
but doesnt matter can get apps all over the internet
Click to expand...
Click to collapse
Thank you for the confirmation.
Confirm this again.
First: WWE10B_Android_393477-v9full.ius burn
Second: UO burn
Third: Main Image burn
Check my post, applanet can help you with that hehehehe.
This is my screen now.
with new virtual keyboard.
I also try swapper2, they say it can improve the performance. This is my Terminal Emulator.
IUW does not work with 64 bit
Please add in the OP that some on other forum sites have confirmed that IUW does NOT work with any 64 bit operating system.
I will link to reference if I come across it again...
For Development USB debugging options for Z4Root, you may also want to link to my post HERE.
quick tip for windows 7 users, picture 6 will not happen, at least it didn't for me, you need to navigate to devices and printers, find the unknown device, and manually install the otg driver
Works as advertised.
I bricked my tab first, but got it up and running again with your step by step guide. Many thanks!
I followed your instruction for SD card and it worked perfectly. I now have the 3925 version on my Superpad and it seems to be working well. Definite improvement on Angry Birds(which I play way too much) and Home Run Battle 3D. WiFI works fine, don't know about GPS or camera as I don't really use them, but I will check just for curiosity sake Seems to be faster and I have had no random lockups that I had with the v5 I had on previously. I will report back as I use it. Thanks for all the great work!
Jiggity Janx said:
Please add in the OP that some on other forum sites have confirmed that IUW does NOT work with any 64 bit operating system.
I will link to reference if I come across it again...
For Development USB debugging options for Z4Root, you may also want to link to my post HERE.
Click to expand...
Click to collapse
Yes, that's why I made it with Windows XP, and we are aware that 64bit OS is so choosy in terms of software compatibility.
About the USB Debugging, I already made a guide after the Flashing/Burning guide.
caravanman said:
quick tip for windows 7 users, picture 6 will not happen, at least it didn't for me, you need to navigate to devices and printers, find the unknown device, and manually install the otg driver
Click to expand...
Click to collapse
Yes, It is self understanding, there is a note above I use windows XP, but the idea is still there.
If you like to contribute for a guide in windows 7 is welcomed.
nullandvoid said:
I bricked my tab first, but got it up and running again with your step by step guide. Many thanks!
Click to expand...
Click to collapse
You are welcome, enjoy your new faster tablet.
woodeman said:
I followed your instruction for SD card and it worked perfectly. I now have the 3925 version on my Superpad and it seems to be working well. Definite improvement on Angry Birds(which I play way too much) and Home Run Battle 3D. WiFI works fine, don't know about GPS or camera as I don't really use them, but I will check just for curiosity sake Seems to be faster and I have had no random lockups that I had with the v5 I had on previously. I will report back as I use it. Thanks for all the great work!
Click to expand...
Click to collapse
Thank you so much, but I would like to suggest to remove the long quote of my post, just to make the thread clean.
SmaRkieS said:
Thank you for the confirmation.
Confirm this again.
First: WWE10B_Android_393477-v9full.ius burn
Second: UO burn
Third: Main Image burn
Check my post, applanet can help you with that hehehehe.
FOr your confirmation I directly made the UO burn and than burned the main image burn never touched WWE10B_Android_393477-v9full.ius
Where can I find your post on applanet to get market running?
Thanks in advance
Click to expand...
Click to collapse
kolk11 said:
SmaRkieS said:
Thank you for the confirmation.
Confirm this again.
First: WWE10B_Android_393477-v9full.ius burn
Second: UO burn
Third: Main Image burn
Check my post, applanet can help you with that hehehehe.
FOr your confirmation I directly made the UO burn and than burned the main image burn never touched WWE10B_Android_393477-v9full.ius
Where can I find your post on applanet to get market running?
Thanks in advance
Click to expand...
Click to collapse
pmed you.
Click to expand...
Click to collapse
This thread is for help and support related to ubuntu on the eeepad transformer, all questions not related to development should be asked here, please be friendly and do not flame each other or I will request the thread be closed.
Download links are in the third post.
There is a wiki entry here that has a bit more detailed explanation. Please note though that as it is a wiki information
quoted in there may or may not be entirely accurite.
you will need to download an nvflashable rom, like prime.
Please read the README before attempting this. The readme is below as well as in the kit, YOU WILL LOSE DATA.
Download links are in the second post.
OLiFE for the ASUS transformer
------------------------------------------------------------------
(c) 2011 Steven Barker <[email protected]>
This package should have only been linked to from xda-developers
or rootzwiki if you got the links to this package from anywhere
but those sites please send an email to the above email
address with the subject: "unauthorised posts"
DISCLAIMER
------------------------------------------------------------------
Steven Barker (lilstevie) nor anybody will take any responsibility
for any damage, data loss, fire, death of a loved one, or loss of
data resulting from using this mod for your device. Using this mod
may void your warranty.
NVFLASH
------------------------------------------------------------------
nvflash is the intellectual property of nvidia, and remains the
property of nvidia. Any questions or queries regarding the usage
and licence of nvflash should be directed to nvidia.
abootimg
------------------------------------------------------------------
abootimg is by Gilles Grandou <[email protected]> and is
unmodified. The source is available from online at
http://gitorious.org/ac100/abootimg
usage
------------------------------------------------------------------
Usage has changed since the release of the last kit, please read
these instructions carefully, as the install method is a little
more complex, (but easier once you use it).
If you downloaded OLiFE.tar.gz you will need to inject the android
rom and ubuntu image. You can use any nvflashable rom with this.
I recommend that you use prime as that is the configuration that
I have tested myself, and the ROM that I support for use with this
device. You can download the ubuntu image from
http://lilstevie.geek.nz/ports/ubuntu.img.gz.
If you downloaded OLiFE-Prime-Edition.tar.gz you will not need to
download the ubuntu image or an nvflash rom as they are seeded into
the image.
Install instructions:
1) Download the specific flavour of OLiFE that you want to use, and
extract it with "tar xvf <filename>".
2) If needed inject android rom and ubuntu image.
3) From the directory that OLiFE was extracted in run the main script
with the command ./OLiFE.sh.
4) Read the text that comes up and answer the question it asks.
5) Follow the menu to the option you want (below is a breakdown of
what each menu item is) and follow the instructions prompted. (also below
is instructions on how to get into the modes requested).
Menu items:
1) Backup Menu:
1) Full Backup (stock)
- Full backup (stock) takes a full backup of a stock
android system. This gives you an option to also back
up your user data(this will take a while).
2) Full Backup (ubuntu)
- Full backup (ubuntu) takes a full backup of a system
that dualboots android and ubuntu, this backs up your
system, and the ubuntu image. This gives you an option
to also back up your user data(this will take a while).
3) User data only
- This backs up the user data partition on your device.
(This option takes a while)
4) Android ROM
- This option backs up the android system only. This
option generates all the files (minus bootloader, and BCT)
required to flash a rom via nvflash.
5) Ubuntu Install
- This option backs up the ubuntu install on your device.
2) Flash Device:
1) Dualboot:
- This option will install ubuntu to your device in a
dualbooting configuration with android. During the
installation process it asks you which OS you would like
to boot by default.
2) uboot (linux only):
- This option will install ubuntu with u-boot and the
ChromeOS kernel that supports acceleration. This option
is currently unavailable, but should be available soon.
3) asus boot (linux only):
- This option will install ubuntu with the asus bootloader
with this configuration you will use all the eMMC for ubuntu
and there will be no android system installed on your device.
4) stock:
- This option will partition the device in a stock way and
install the android system that is in ./images. Use this
option if you no longer want ubuntu on your device.
3) Update Device:
1) Android Kernel:
- This option will update the android kernel on your device
with the boot.img from ./images/. This allows you to install
your own kernel on the device for android rather than the one
that comes with your chosen rom.
2) Ubuntu/Linux Kernel:
- This will update the ubuntu kernel on your device to the version
included in this flashkit. This option is for updating just the
kernel with nvflash rather than using the blob method. This method
is also good for if you flash a bad ubuntu kernel to the device.
3) Android ROM:
- This option will update the android rom on the device with the
one from ./images/. This is good for if the ROM you use is updated
or you would like to change ROMs and there is an nvflash image for it.
This option does not destroy your data.
4) Ubuntu Rootfs:
- This will update your ubuntu image on the device. This is destructive
to data stored in the ubuntu image.
5) Advanced (Unsupported):
- Any option in this menu is not supported and should be considered
unstable. There may be bugs in these options and they are not maintained
at this point in time.
1) Flash ChromeOS Kernel (Primary Boot):
- This option will flash the ChromeOS kernel to the primary boot
partition. This option may not currently work in it's current
configuration.
2) Flash ChromeOS Kernel (Secondary Boot):
- This option will flash the ChromeOS kernel to the secondary boot
partition. This option may not currently work in it's current
configuration.
3) Update Uboot Partition:
- This option will update the u-boot boot partition that u-boot
reads the kernel and boot script from. This option does work if
you have installed u-boot by compiling it from source and installed
it yourself.
4) Flash ClockworkRecoveryMod:
- This option allows you to temperarily flash CWR to the device so
you can update the installed rom. It backs up the current kernel in
the recovery kernel position and then flashes CWR. When you have finished
using CWR you then push any key and put the device back in APX mode and
it will restore the kernel that was in that position. (This only works if
android is your primary boot option at this time).
4) Inject Firmware:
1) Bluetooth firmware (default install):
- This option will inject the Bluetooth firmware from the
android ROM located at ./images/ in to the ubuntu of your
currently running system.
2) Bluetooth firmware (CrOS Kernel):
- This option will inject the Bluetooth firmware from the
android ROM located at ./images/ in to the ubuntu of your
currently running system and flashes the proper u-boot kernel
if you no longer need adb support.
5) Onscreen Keyboard:
- This runs OnBoard so that you can run through oem-config properly
you only need to use this option if you do not have a keyboard dock
and on the first boot.
1) Standard Kernel:
- This will invoke oem-config on the standard kernel installed
on the device.
2) ChromeOS Kernel:
- This will invoke oem-config on the u-boot kernel that is
installed on the device and flashes the proper u-boot kernel
if you no longer need adb support.
Device Modes:
APX Mode:
-This mode is used by nvflash to write files to the eMMC device.
To boot in this mode you press Power and Vol-Up.
Recovery Mode:
- This mode is where CWR or Asus recovery normally lives, but is
replaced by the secondary OS in the dualboot configuration.
To boot in this mode you press Power and Vol-Down, then Vol-Up when prompted.
Normal Boot:
-This mode is where android normally lives.
To boot in this mode you press the Power button until the screen turns on.
Changelog
------------------------------------------------------------------
1.2a - Release name: Odyssey
* New name for kit: OLiFE
* New menu system
* Updated README
* Better handling of platform detection
* Bluetooth support in ubuntu.img
* Preliminary support for ChromeOS kernel
* Preliminary support for uboot
* Fixed touchpad
* Fixed network manager
* Updated to ubuntu oneiric
* More options for flashing and updating
* OTB Wireless support (No more injecting)
* Smaller ubuntu.img for faster upload to device
* Auto resizing of rootfs on first boot
* Larger partition size (6GB) for ubuntu
* Refactored to more easily between devices
* Maybe something else I have missed
1.1 - Release name: Daedalus
* Firmware injector for BT and wifi firmwares
1.0 and silent updates - Release name: Prometheus
* Support for x86_64 linux distributions
* Updated README for release on xda-developers
* Fixes to install scripts
* Initial Release
Downloads:
RootFS md5sum(1a9fa8a698e4a96245a3c08511841eb4)
OLiFE md5sum(c30263fd8271a23bb211fd9fdd69fa45)
OLiFE Prime Edition md5sum(767779ccfa200e5e00b2f1e33a3d73a9)
Sources:
http://gitweb.lilstevie.geek.nz
To clone the repos "git clone git://lilstevie.geek.nz/$(name of repo).git"
lilstevie said:
This is running natively and from the eMMC so no µSD card required,
The video is a class2 µSD card and speeds are not an example of speeds from this kit.
Click to expand...
Click to collapse
Thanks for your hard work, but I'm a bit confused by those 2 statements, contradicting each other :/
Also, if I understood properly, there is no CWM after selecting dual boot
Finally, is this a final release, or for testing purpose only ?
If final, a step by step guide would be very welcome
Edit : Just saw there is the tag [DEV] so forget about my last question (guide)
Wow, amazing work here. Haven't been able to do much to my Transformer as of late (due to uni starting up again, and been seeing how the TF goes as a substitute for my usual netbook), but absolutely can't wait to try this out when I got some time.
And yeah, I'm a tad confused here as well. I'm assuming that you mean the video was of Ubuntu running of your microSD drive using Jhinta's scripts but now this allows us to run it off the internal drive... am I right?
And how is the speed difference so far, running off internal vs class 2 microSD?
EDIT: Also, I'm assuming the same things that didn't work on Jhinta's aren't working on this (network-manager gui, touchpad etc)? Or have you changed things up a bit? And the tegra ppa you talk about; that contain the proprietary 3D drivers you were talking about having a lack of in the video?
Nice to see the post in XDA Good work !
bud77 said:
Thanks for your hard work, but I'm a bit confused by those 2 statements, contradicting each other :/
Also, if I understood properly, there is no CWM after selecting dual boot
Click to expand...
Click to collapse
The video was taken before I was stable enough to even think about using internal memory, where as this kit is not using the µSD
and yeah you lose recovery after selecting dual boot, not much we can do about that for the time being.
poltak11 said:
Wow, amazing work here. Haven't been able to do much to my Transformer as of late (due to uni starting up again, and been seeing how the TF goes as a substitute for my usual netbook), but absolutely can't wait to try this out when I got some time.
And yeah, I'm a tad confused here as well. I'm assuming that you mean the video was of Ubuntu running of your microSD drive using Jhinta's scripts but now this allows us to run it off the internal drive... am I right?
And how is the speed difference so far, running off internal vs class 2 microSD?
EDIT: Also, I'm assuming the same things that didn't work on Jhinta's aren't working on this (network-manager gui, touchpad etc)? Or have you changed things up a bit? And the tegra ppa you talk about; that contain the proprietary 3D drivers you were talking about having a lack of in the video?
Click to expand...
Click to collapse
I started back at uni this week myself, and have been using my transformer as a netbook replacement with ubuntu. The video is using my stuff but before I had it running on the internal memory.
speed diference is massive between the class2 and internal. It was so great of a difference that I forget that it is arm now that it is on internal
the PPA will have things such as kernel updates, bluetooth enabler and all that. as for what is working in the release, things are pretty similar to Jhintas release, touchpad does not work correctly network manager gui doesn't work, I have something to enable bluetooth, that works nicely, but it isn't in the fs or up on the ppa yet. 3D drivers are a work in progress, still no EGL and the likes with the L4T releases, so it is really just acceleration for normal use, I have been working on them but as of yet no dice.
So using the PPA, in theory we won't have to flash the device again (at least for the ubuntu part), it will be able to auto-update itself ?
ErGo_404 said:
So using the PPA, in theory we won't have to flash the device again (at least for the ubuntu part), it will be able to auto-update itself ?
Click to expand...
Click to collapse
yes, that is the plan anyway
lilstevie said:
the PPA will have things such as kernel updates, bluetooth enabler and all that. as for what is working in the release, things are pretty similar to Jhintas release, touchpad does not work correctly network manager gui doesn't work, I have something to enable bluetooth, that works nicely, but it isn't in the fs or up on the ppa yet. 3D drivers are a work in progress, still no EGL and the likes with the L4T releases, so it is really just acceleration for normal use, I have been working on them but as of yet no dice.
Click to expand...
Click to collapse
Ah lovely idea with the PPA. When new 3.2 based Prime gets released, I'll try to get a few hours to myself to get this all working together.
Just a few quick questions first:
How do your scripts change the eMMC layout? Does eMMC work the same as a standard HDD/SSD partitioned with a GPT? As in, have you made separate partitions for Android and Ubuntu, or is it somehow shared?
And also related, how much room will it take up on the eMMC (as I've only got a 16GB TF)?
And finally, since you've been using yours at uni running Ubuntu, have you got any idea of the battery life running Ubuntu? I'm assuming it'd be pretty similar to stock, but yeah the battery indicator wasn't working last time I was playing around with Ubuntu from the microSD. Also, does the second keyboard battery work?
poltak11 said:
Ah lovely idea with the PPA. When new 3.2 based Prime gets released, I'll try to get a few hours to myself to get this all working together.
Just a few quick questions first:
How do your scripts change the eMMC layout? Does eMMC work the same as a standard HDD/SSD partitioned with a GPT? As in, have you made separate partitions for Android and Ubuntu, or is it somehow shared?
And also related, how much room will it take up on the eMMC (as I've only got a 16GB TF)?
And finally, since you've been using yours at uni running Ubuntu, have you got any idea of the battery life running Ubuntu? I'm assuming it'd be pretty similar to stock, but yeah the battery indicator wasn't working last time I was playing around with Ubuntu from the microSD. Also, does the second keyboard battery work?
Click to expand...
Click to collapse
The second battery does work, unless you get one of those dodged ones that just randomly stops charging which happened to me, with the dock connected and the battery in it refusing to charge my battery lasted 6 hours.
the layout is different to standard, UDA(User DAta partition) is 4.2GB smaller than what it was, so you have 9.99gb for android and 4.2 for ubuntu, the kernel and recovery kernels are moved up to the end of the flash as well so that they are accessible through /dev
Just finished installing it. Yea, from internal memory it's working much faster. ~20 second boot time!(I didn't have timer with me, so I counted in the head) That's like my laptop with SSD + 10 second bios booting. With a dock it feels like a true netbook. I think I'll even dare to test c/c++ IDE on this thing. Good job!
Used online timer. It's 21 seconds.
Hmm how do I start wifi? eth0 is not even showing in the list of devices.
aligatro2010 said:
Just finished installing it. Yea, from internal memory it's working much faster. ~20 second boot time!(I didn't have timer with me, so I counted in the head) That's like my laptop with SSD + 10 second bios booting. With a dock it feels like a true netbook. I think I'll even dare to test c/c++ IDE on this thing.
Used online timer. It's 21 seconds.
Hmm how do I start wifi? eth0 is not even showing in the list of devices.
Click to expand...
Click to collapse
Sorry forgot to mention in the first post, firmwares are not included in this release due to potential licensing issues, you can push the wifi firmware via adb to /lib/firmware and also the nvram, they are located in /system/vendor/fw_bcm4329.bin and /system/etc/nvram.txt on your android system, the module will autoload on boot once you have the firmware in place, and the interface will be named wlan0
lilstevie said:
Sorry forgot to mention in the first post, firmwares are not included in this release due to potential licensing issues, you can push the wifi firmware via adb to /lib/firmware and also the nvram, they are located in /system/vendor/fw_bcm4329.bin and /system/etc/nvram.txt on your android system, the module will autoload on boot once you have the firmware in place, and the interface will be named wlan0
Click to expand...
Click to collapse
nvram.txt to /etc right? I copied them straight from android partition, but it still doesn't load. Could it be because of the bcm4329_sta.bin or nvram should be placed in /lib/firmware ?
It works now.
So basically we will be able to dual boot Windows 7 and Android?
liorry said:
So basically we will be able to dual boot Windows 7 and Android?
Click to expand...
Click to collapse
No, Windows 7 doesn't have arm version. Windows 8 maybe in future, long future ....
aligatro2010 said:
nvram.txt to /etc right? I copied them straight from android partition, but it still doesn't load. Could it be because of the bcm4329_sta.bin or nvram should be placed in /lib/firmware ?
It works now.
Click to expand...
Click to collapse
the wifi firmware should be called fw_bcm4329.bin and nvram.txt should be in /lib/firmware, I probably should have been a little clearer, but I posted that just before going to bed, and was a little tired
lilstevie said:
the wifi firmware should be called fw_bcm4329.bin and nvram.txt should be in /lib/firmware, I probably should have been a little clearer, but I posted that just before going to bed, and was a little tired
Click to expand...
Click to collapse
"bcm4329_sta.bin" was already there before I even copied 2 modules and it was also loaded as module when I did modprobe. (not 100% sure about the second)That's why I thought it was conflicting with android's modules.
Wow, great work! Can't wait to try it.
Sent from my Transformer TF101 using XDA Premium App
I've probably missed something obvious.. But I get this.
file not found: linux.img
failed executing command 2147483647 NvError 0x4
command failure: create failed
rm: cannot remove `linux.img': No such file or directory
Click to expand...
Click to collapse
After like 5 minutes of NvFlash installing stuff.
Does anyone have this tablet? I can't find this tablet on the website.
I want to know if this tablet can be upgraded to v3.0 or higher when ics comes on CyanogenMod?
Technical Specifications
Weight: 426 gr
Dimensions: 202 x 140 x 11 mm
CPU Samsung Cortex A8 1.0 GHZ
OS: Android 2.2
WiFi 802.11 b/g/n
Bluetooth
Capacitive Multi Touch Screen
7" TFT-LCD Display
SDRAM 512 MB
4 GB Internal Memory
Micro SD/SDHC slot (Up to 32 GB)
G-Sensor
Mini-HDMI port out
Mini-USB port
Microphone
Adobe Flash Compatible
Camera: 2 MP
2 Stereo Speakers
I've the exact same question about the Cyanogen Mod.
Also, I would like to know if it's possible to perform a COMPLETE back up (root or nand backup) without this mod. (without nandroid backup)
The device is also released as the BQ DaVinci. That company released a firmware update to Gingerbread a couple of days ago.
However, I'm a bit reluctant to install it, because it'll change the splash screen and who knows what else.
The update procedure seems to be different from other devices: you have to put a folder called SDFUSE on the root of the SD-card and reboot. The folder contains these files:
SDFUSE
--> ramdisk-uboot.img
--> sdfuse.txt
--> system.img
--> u-boot.bin
--> zImage
Does anyone have any idea on how to reverse-assemble these files (i.e. extract or replace boot splash screen,...)
Mahalaleel said:
I've the exact same question about the Cyanogen Mod.
Also, I would like to know if it's possible to perform a COMPLETE back up (root or nand backup) without this mod. (without nandroid backup)
The device is also released as the BQ DaVinci. That company released a firmware update to Gingerbread a couple of days ago.
However, I'm a bit reluctant to install it, because it'll change the splash screen and who knows what else.
The update procedure seems to be different from other devices: you have to put a folder called SDFUSE on the root of the SD-card and reboot. The folder contains these files:
SDFUSE
--> ramdisk-uboot.img
--> sdfuse.txt
--> system.img
--> u-boot.bin
--> zImage
Does anyone have any idea on how to reverse-assemble these files (i.e. extract or replace boot splash screen,...)
Click to expand...
Click to collapse
There is not much help here..
I think we can forget an answer to our question
From experience I can say 2.3.4 DaVinci upgrade works fine on BeBook Live, even Angry Birds Space is now playable!
Indeed so, I discovered that as well.
But... still no possibility to upgrade to a custom ROM apparently?
AGSO Somx 7 GS20 has same format for their ROMs. In my understanding:
zImage - linux kernel compressed
u-boot-config - ???
ramdisk-uboot.img - ram disk image for loading
system.img - image of /system disk
To convert other ROMs into this format you have to get kernel and ramdisk images from boot.img, then make system partition image (create virtual disk with same size, make filesystem on it, move all /system files to the disk).
After some researching:
zImage - linux kernel gzip-compressed (just kernel, with empty initramfs inside) with built-in unpacker code at start
u-boot-config.bin - u-boot loader and/or its config (perhaps, stage 2 loader as S5PC110 has two-stage loader)
ramdisk-uboot.img - initramfs image (initramfs archive by cpio, then gz [output name "ramdisk"], then mkimage from u-boot distribution)
system.img - image of /system disk (ext4, not compressed)
BQ put ICS (Android 4.0) online for the BQ DaVinci, works fine also (booting takes a bit). Definitely a good idea if you still are using the device, Skype and so on works smooth!
Developers thread for users general.
I will post here some external links and additional information.
GitHub tf700 Repository - place for config files and step-by-step manual to create you own kernel and rootfs
GOO.IM file place
Tablet PPA for Raring
Changed packages is placed in /root/deb directory.
Known problems: (nexus7 wiki, mattfischer blog post, nexus7 bugs)
Unity has some problems with performance and ram eating - this is place for optimizations.
In-device microSD really bad works.
WiFi disabling is fail bcmdhd kernel module.
vt1-only, if you try to switch to vt* (`chvt 2`) - your device is freezes and reboot.
To use unity you need nux-tools, libnux-3.8-0 and libnux-3.8-common with version 3.8.0-0ubuntu1nexus7.1 (this packages are hold)
Sometimes I can see really bad artifacts with fonts and background on the device screen (mostly if using chromium browser). Only reboot fixes it.
Progress list:
Test Linux boot {DONE}
SDCard rootfs {DONE}
Graphical boot{DONE}
Keyboard special keys remapping (Esc, F1-12, Ins, Print, Break, Del, Home->Alt, Search->Meta4) {DONE in 0.8.0}
WiFi {DONE}
OpenGL ES {DONE}
Audio {DONE} In pavucontrol as output device selected Analog Stereo Output, in alsamixer (tegra-codec) unmute IntSpk
Video up to 1080p {DONE} (ac100 info) - Soft audio requires gstreamer0.10-plugins-*
nvgstplayer --sas="audioconvert ! pulsesink" -i <videofile> - Fullscreen mode
nvgstplayer --svs="nvxvimagesink" --sas="audioconvert ! pulsesink" -i <videofile> - Window mode
Touchscreen {DONE in 0.7.0} - used mtev one-touch driver 0.1.13 with api and 2button patches - right click by push one finger and click by second finger (thanx, cb22)
Touchpad {DONE in 0.6.1}
2 fingers scrolling {DONE}
3rd mouse button by 2 finger tap {DONE 0.6.1} - created new version of package multitouch "-swaptaps"
Updated tegra3 drivers and codecs to 16.2 {DONE in 0.6.1}
Ubuntu/Android dualboot {DONE in 0.7.0}
Initrd bootloader trying to boot sda1(dock sd cardreader or usb device), mmcblk1p1(internal microsd cardreader), sdb1 (dock sd cardreader or usb device), mmcblk0p9(inernal device), /data/media/tf700-rootfs-linux.img(in-device installed virtual disk) (0.7.0)
If it can't load linux - fallback to Android (0.7.0)
Boot android if voldown (or special, like Up key) key pressed in menu (0.7.0)
Fixed nvavp problem in android (0.7.0)
Fixed problems with Android sleeping by unbinding vtconsole before Android boot (0.7.0)
Initrd installer to mmcblk0p8 user partition and mount as loop with binding mmcblk0p8 {DONE in 0.7.0}
Fonts and cursor size {DONE in 0.8.0}
ZIP installer by Aroma {partially}
Install of boot image {DONE in 0.7.1}
Install script for SDcard-way and Virtual Disk-way {DONE in 0.8.0}
Possibility of using mmcblk0p8 /data as /home {DONE in 0.8.0}
Dynamical making of boot.blob {DONE in 0.8.1}
Select rootfs to boot {DONE in 0.8.1}
CM10.1 initrd (link) {DONE in 0.8.1}
Android boot from sdcard or virtual drive {DONE in 0.8.1}
UbuntuTouch initrd {DONE in 0.8.2}
Change boot system names {DONE in 0.8.2}
Add option to boot android by default {DONE in 0.8.2}
Check md5 of rootfs archive
Encryption for linux partition
FSCK check & fix rootfs before mounting {DONE in 0.8.2}
GPIO keys {partially in 0.8.0}
Switch rootfs to 13.4 (link) {partially}
Bluetooth
Try this: /system/bin/brcm_patchram_plus --bd_addr `cat /etc/bluetooth/bt_addr` --enable_hci --enable_lpm --no2bytes --tosleep 50000 --baudrate 4000000 --use_baudrate_for_download --patchram /lib/firmware/bcm4334.hcd --i2s=1,0,0,0 /dev/ttySAC0&
Totem and nvgst modules
Go to Wayland+Weston+libhybris to use egl android drivers
Disable speaker if headphones connected
Additional:
Ubuntu Cube Desktop {DONE in 0.6.2}
Chromium browser with egl and ffmpeg support {partially} - Youtube has problems with performance
Games & software {partially}
Duke3D {DONE}
Minecraft {partially}:
+ MCP
+ LWJGL 2.8.x (`ant jars_es && ant compile_native_es`)
+ Hands
Games and Emu (in Russian)
Xonotic
C-Dogs SDL
pcsx-rearmed (pi) (Return Fire and other good ps1 games)
Open Clonk
OpenLieroX
Blender + LuxRender
Need help:
Suspend to RAM - Not working with X (trace), without X (stop lightdm) - suspended, but not wake.
Wakelock to emmc
Wake up: echo "on" > /sys/power/state or powerbutton (maybe with kernel patching)
Totem - now is not working
gstreamer-properties and set Audio->Output=Custom, Audio->Output->Pipeline="nv_omx_audiosink" and Video->Output=Custom, Video->Output->Pipeline="nvxvimagesink"
HDMI copy of screen (any ideas?)
Xorg configuration shows blue lines on HDMI screen
Not working properly with 1920x1080: `xrandr --output LVDS-1 --auto --output HDMI-1 --mode 1920x1080` - I get "xrandr: Configure crtc 1 failed"
Tested on different display with fullhd support - seems like tegra3 drivers problem
Works ok with 1280x800:
xrandr --newmode `gtf 1280 800 60 | tail -n2 | head -n1 | sed 's/ Modeline //'`
xrandr --addmode HDMI-1 1280x800_60.00
xrandr --output LVDS-1 --auto --output HDMI-1 --auto
HDMI audio (any ideas?)
Adobe Flash player (any ideas?)
Skype (any ideas?)
List of optimizations:
ZRam {DONE}
UKSM (Ultra Kernel Samepage Merging) {DONE} (info in Russian)
CPU optimizations {partially}
Clemsyn OC 1.3 - 1.8ghz 650GPU Kernel {DONE in 0.6.2} - seems like not properly working on AndroidRoot hacked bootloader
Boot optimizations {partially}
Initrd scripts {DONE in 0.6.2}
Kernel modules upgrade from initrd {DONE in 0.7.1}
IO optimizations {partially}
Some optimizations of filesystem mounting {partially in 0.6.2}
Install to device main emmc memory {DONE in 0.7.0}
Power optimizations:
Screen off on lid
RAM Sleep
Powersave, Auto and Performance modes
Plans for the future:
Prepare common installer for any tegra3 device.
Test builds:
Nope
If you can help in development - please, write here.
This is very nice! Its certainly a good start.
There are definitely changes between your implementation and Jay's build. It would seem that after reviewing your source code that the major difference is your overall system config and choice of location of rootfs.
The kernels aren't too too different.
you are using noop vs cfq which is understandable since you are using the stock kernel vs CM10
you incorporated less debugging vs debugging (agree with your preference)
you incorporated framebuffer vs no fb
you incorporated zram vs no zram (smart move to help chromium)
your enhancements are much better IMHO.
You are not utilizing the linux for Tegra drivers. I think we could benefit by utilizing the latest version at least for sound. After reviewing the documentation and reviewing the drivers themselves I think we should integrate. That is unless you are trying to have two separate kernels instead of a monolithic kernel that can boot android and linux kind of like "Ubuntu for Android"
Since I have a working nvflash'd tf700 I am working on a dualboot kexec.
I still prefer the monolithic kernel approach for Android and Linux concept though, and make selection during boot as to which environment to go to. Essentially, it is possible to boot the kernel and run a specific environment and end that environment and switch to another environment.
As others have suggested I think we should integrate both into 1 tree and also try to get the tf300 on board because other than their kernel, specific tf700 configs/rules the rest of the rootfs and other portions should be identical.
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
quicknik said:
You are not utilizing the linux for Tegra drivers. I think we could benefit by utilizing the latest version at least for sound. After reviewing the documentation and reviewing the drivers themselves I think we should integrate. That is unless you are trying to have two separate kernels instead of a monolithic kernel that can boot android and linux kind of like "Ubuntu for Android"
Click to expand...
Click to collapse
You mean - HW sound? I have integrated drivers, because I use modified nexus7 rootfs. Maybe, I wrong...
Also, integration of kernels is too difficult task for me now...
quicknik said:
Since I have a working nvflash'd tf700 I am working on a dualboot kexec.
I still prefer the monolithic kernel approach for Android and Linux concept though, and make selection during boot as to which environment to go to. Essentially, it is possible to boot the kernel and run a specific environment and end that environment and switch to another environment.
Click to expand...
Click to collapse
I also have nvflash by wheele, but for users preparing device for this - is too difficult. Now I already prepared dualboot with same kernel through initrd menu. In 0.6.0 I will release it. I have some problems with integrated cameras, but wifi is now works in android.
I think we have some problems with non-JB androids with this dualboot... But it is simple.
quicknik said:
As others have suggested I think we should integrate both into 1 tree and also try to get the tf300 on board because other than their kernel, specific tf700 configs/rules the rest of the rootfs and other portions should be identical.
Click to expand...
Click to collapse
Applying to tf300 - is good idea. It's a part of integration all tegra3 devices in same Ubuntu installation for pads.
Sorry, guys. I found my mistake with no-dualboot initrd. Now i replaced it to true dualboot (0.6.1).
rabits said:
Developers thread for users general.
Test builds:
boot.img dualboot initrd Pre-release 0.6.1
for me dualboot nice works, but I need to change verbosity of kernel output and boot menu more user frendly. If you can try it and write your suggestions - that will be cool.
assembly of mini initrd and android JB 4.1.1 (I have CleanROM 2.4 installed on my tf700t).
wifi on android is supported (added p4p bcmdhd option), but nvavp can't load fw.
boot menu (included linux, android, initrd shell) is showing after kernel loading.
Click to expand...
Click to collapse
I am more than willing to try, but how can I dualboot that first build ? If you provide a few step by step instructions, I am sure a lot of people will try which will help the development by giving several feedbacks.
I am currently on Clean Rom Inheritance (= CROMI) 2.7.2 which is the latest update in the Clean Rom series. Since you are using 2.4, I guess the steps woul be exactly the same as for you. I am however using Clemsyn kernel. Is the stock kernel required to be able to dual boot ?
One the OP, Ubuntu seems tobe pretty stable since a lot of features ar working. Is that really the case ? Is compiz already something I could consider using at this point of the developpment or is it still a little bit early ?
I am really interested in this project and I thank you a million time for starting actively a development allowing us to dualboot Ubuntu. Keep up you awesome work !!!
singoutout said:
I am more than willing to try, but how can I dualboot that first build ? If you provide a few step by step instructions, I am sure a lot of people will try which will help the development by giving several feedbacks.
I am currently on Clean Rom Inheritance (= CROMI) 2.7.2 which is the latest update in the Clean Rom series. Since you are using 2.4, I guess the steps woul be exactly the same as for you. I am however using Clemsyn kernel. Is the stock kernel required to be able to dual boot ?
One the OP, Ubuntu seems tobe pretty stable since a lot of features ar working. Is that really the case ? Is compiz already something I could consider using at this point of the developpment or is it still a little bit early ?
I am really interested in this project and I thank you a million time for starting actively a development allowing us to dualboot Ubuntu. Keep up you awesome work !!!
Click to expand...
Click to collapse
Thanks for your support)) I think, you could use users general thread for test boot steps. The steps are the same, but with the current rootfs (0.5.0) linux in dualboot may not start. Android with CleanRom should work. Soon I will release a rootfs 0.6, which can be used with dualboot section.
rabits said:
Thanks for your support)) I think, you could use users general thread for test boot steps. The steps are the same, but with the current rootfs (0.5.0) linux in dualboot may not start. Android with CleanRom should work. Soon I will release a rootfs 0.6, which can be used with dualboot section.
Click to expand...
Click to collapse
can do for TF300 ?
tailormoon said:
can do for TF300 ?
Click to expand...
Click to collapse
I don't know - but you can try.
Hi
How is it going with the developpment? Is the dualboot working nice with Ubuntu now?
Do you think a cube desktop will ever be usable on a dualbooted Ubuntu on our device?
Thanks for the good work
Hello, I have managed to get this booting on my tf300t tablet. It is working alright and I would like to learn a bit about this area of development so I can tweak it to get it working as well as contribute to the project as a whole. So far it has bugs with wifi, bluetooth, and sound. Also, when I select shutdown from the ubuntu menu, it corrupts the image and it will boot to lightdm and then freeze. I tried compiling a kernel for it based on a tweaked tf700t 10.4.4.20 kernel that was patched by untermensch to work for the tf300t but it did not solve any issues, it pretty much performed the same. I wanted infrom everyone of the issues on the tf300t as well as ask for some guidance as to documentation for what steps I can take to fix these issues. Thanks.
keeganmccallum said:
I wanted infrom everyone of the issues on the tf300t as well as ask for some guidance as to documentation for what steps I can take to fix these issues. Thanks.
Click to expand...
Click to collapse
It seems that this is the rootfs problem. Maybe you find some info in tf300 forum or ubuntu forums, but you need try to read log files and, maybe, do hard gdb trace.
Trying it when i get home
Thanks
Sent from my GT-N7000 using xda premium
BTW happy to have CROMI involved with this
rabits said:
[*]boot.blob v0.6.2 - Anyone can try to flash it? I can't flash it by fastboot on AndroidRoot bootloader - maybe it should work on JB bootloader?
Click to expand...
Click to collapse
Your dummy signblob header is one byte too long - there is a 0a byte before "MSM-RADIO-UPDATE" that should not be there.
_that said:
Your dummy signblob header is one byte too long - there is a 0a byte before "MSM-RADIO-UPDATE" that should not be there.
Click to expand...
Click to collapse
Thanx, I missed this byte)) Damn sed. We should always use echo and cat))
Blob is updated.
rabits said:
Blob is updated.
Click to expand...
Click to collapse
Successfully flashed via fastboot and it booted my Android (still the old CleanROM 2.3) fine. The initrd menu and framebuffer console is awesome. Can't try your rootfs right now because my PC cardreader is making trouble (I hate SD cards and readers, they are unreliable sh**, or they hate me).
Only everything is very tiny (160 dpi instead of 240), and adding ro.sf.lcd_density=240 to /system/build.prop did not help. I'll have to add it to the initrd and see if it helps. Strange, because I thought newer CleanROMs also set the dpi via /system/build.prop, but who knows. Eventually I should install CRI 3.0 anyway.
Hm, while I was writing this, the TF700 spontanously rebooted... looks like problems turning off the screen. /proc/last_kmsg contained two WARNINGs with stack trace, both containing do_blank_screen (drivers/tty/vt/vt.c:3728 and vt.c:650)
I just read that this is Clemsyn's kernel - where did you find the sources for the current version and what did you modify? There are so many different binaries in that thread and so few source drops that I totally lost track.
Hi
I've just seen the cube desktop is know supported on 0.6.2. How is it performing ? Is the latest version smoother than 0.5 ?
Thanks for the great work!!! I hope our tabs will soon have a stable and smooth Ubuntu dualbootable with CROMI
_that said:
Only everything is very tiny (160 dpi instead of 240), and adding ro.sf.lcd_density=240 to /system/build.prop did not help. I'll have to add it to the initrd and see if it helps. Strange, because I thought newer CleanROMs also set the dpi via /system/build.prop, but who knows. Eventually I should install CRI 3.0 anyway.
Hm, while I was writing this, the TF700 spontanously rebooted... looks like problems turning off the screen. /proc/last_kmsg contained two WARNINGs with stack trace, both containing do_blank_screen (drivers/tty/vt/vt.c:3728 and vt.c:650)
Click to expand...
Click to collapse
Yeah, seems like too old CR version...
_that said:
I just read that this is Clemsyn's kernel - where did you find the sources for the current version and what did you modify? There are so many different binaries in that thread and so few source drops that I totally lost track.
Click to expand...
Click to collapse
You can find info about kernel here and here. I'm used this source from second link to build 0.6.2 kernel.
singoutout said:
Hi
I've just seen the cube desktop is know supported on 0.6.2. How is it performing ? Is the latest version smoother than 0.5 ?
Click to expand...
Click to collapse
I just installed extra plugins))) Currently Nexus7 is more smoothed then tf700 with unity... Cube is rotating ok, but with IO lags - sd speed so slow.
Currently I working on more basic things, like install linux in main flash drive. If you have any ideas - please, post it here.
Hi everyone,
I've been working on getting ArchLinuxArm running on the TF300 over at http://forum.xda-developers.com/showthread.php?t=1918849
Just something that might help with your touchscreen - you should be able to get basic functionality if you use the xf86-input-mtev driver (see https://aur.archlinux.org/packages/xf86-input-mtev-meego/ )
While less than ideal, it's better than nothing. We have the same issue with X segfaulting when the evdev driver is used. I actually looked into that, and it has to do with the way events are reported by the kernel driver, if I remember correctly.
The intention behind this thread is to share some experience of a little project where I try to migrate the Sony Xperia Shinano devices (based on Qualcomm MSM8974 chipset with a Broadcom BCM4339 wifi/bluetooth chip) from the old bcmdhd wifi driver to a close-to-mainline brcmfmac driver. I want to share the progress and status here, and maybe get some hints. It is work in progress, and for sure it still contains some mistakes - I haven't done something like this before and am still learning.
Why?
The Shinano devices are still maintained by the LineageOS, and some devices are currently on the official LineageOS 17.1 stream.
The kernel however is terribly outdated, based on msm-3.4
There are some wifi issues with all LineageOS-based ROMs since years, like weak 5GHz connections and non-working wifi in some countries. There are some hacks around that, but they work (afaik) by practically disabling the kernel-level regulatory system by e.g. setting a static country code like "DE".
I am curious if we can improve that by updating the kernel drivers and network/wifi components, and maybe also the firmware (to the latest release available from Broadcom, 6.37.34.43 ?) . I got the ideas from Sonyxperiadev/Loire (+ related platform config), the Linux Backport Project and other MSM8974 based devices.
Working so far:
Did a few tests only so far, STA with WPA2 and p2p (hotspot) seem to work
Wifi connection is stable on 2,4GHz on 00 world regulatory domain (tested on a Z3 and a Z3c)
5GHz manually setting a country code (could only test DE)
Switching countries / setting new regulatory domains is now working, too
Download speed looks OK to me, in my case at least better than before Download >60MBit, Upload >30 Mbit on some initial tests.
Not working yet:
WifiHAL (qcom-caf) does not work correctly. This may create multiple issues, tbd.
Connection bandwidth seems to be not reported correctly
I don't know if wowlan works (interrupts working?)
Stability: After 1-2 days without reboot wifi sometimes crashes but immediately reconnects. Reason not yet understood.
Patches & Picks
Kernel:
backported and configured brcmfmac, cfg800211 wireless configuration API and wireless network stack from linux-stable v5.8 by adopting the compatibility patches from the linux backporting project.
updated Shinano device tree, updated Z3, Z3c and Z2 (Z2 test needed!) defconfigs (unset bcmdhd and enabled brcmfmac) and removed board-sony_shinano-wifi.o in the arch-msm makefile
Note: the backported drivers and compatibility-patches are located in a separate backports/ subdirectory
Sorry, this is work in progress and contains some hacks, to be cleaned up later
--> https://github.com/LineageOS/androi...1...Tom1000:lineage-17.1-driver-backport-v5.8
Vendor blobs / device z3(c): removed proprietary firmware and replaced that by publicly available firmware for bcm4339 on linux-firmware.git
z3c --> https://github.com/LineageOS/androi.../lineage-17.1...Tom1000:lineage-17.1-brcmfmac
z3 --> https://github.com/LineageOS/androi.../lineage-17.1...Tom1000:lineage-17.1-brcmfmac
Shinano-common: Use qcwcn instead of bcmdhd WLAN device, serve wpa_supplicant_overlay.conf
--> https://github.com/LineageOS/androi.../lineage-17.1...Tom1000:lineage-17.1-brcmfmac
msm8974-common: raise wpa_supplicant version (unknown if we need that) and update sysfs node for MAC address
--> https://github.com/LineageOS/androi.../lineage-17.1...Tom1000:lineage-17.1-brcmfmac
As a follow up, the driver seems to work quite stable already. I still have issues with nl80211 private commands, as a mainline brcmfmac does not seem to accept command strings passed via a libnl control socket like this:
qcwcn/wpa_supplicant_8_lib/driver_cmd_nl80211.c
@vknecht : I've seen your backporting work for the Xperia X. How does this work for Loire with SODP? Does e.g. a "set country code request" work for you, and if so, can you give me a hint?
I need some feedback from people with a Z3/Z3c/Z3Dual to see if the new builds work in affected countries, where 5GHz wifi is not working on current custom ROMs like e.g. LineageOS 17.1. I would appreciate if you test one of the builds below and send me a full log.
WARNING: The following builds are for debugging purpose only. Do not use them as a daily driver, as they have SELinux disabled and create excessive log entries. This ROM is not stable, some features are not yet implemented.
Xperia Z3 (D6603):
lineage-17.1-20201227-UNOFFICIAL-z3.zip
drive.google.com
Xperia Z3c (D5803):
lineage-17.1-20201227-UNOFFICIAL-z3c.zip
drive.google.com
Xperia Z3Dual (D6633) Update 10Jan2021:
lineage-17.1-20210110-UNOFFICIAL-z3dual.zip
drive.google.com
Z3Dual build has SELinux enabled already
If possible, please follow these steps:
Install ROM with TWRP for Android 10 or Lineage Recovery for 17.1
If possible, factory reset the device. Be sure to get rid of all former Magisk modules which try to set country codes etc. (if applicable).
Make sure a a local SIM card is inserted.
Boot the device. Enable mobile data and enable wifi. Connect to a 5GHz capable access point or router.
Optional: Increase log buffer size. This may be required as the kernel is set to verbose logging, creating large logfiles. You can do this via settings/developer options or via adb:
adb logcat -G 8M
Get close to the access point or router, so that the device would prefer 5GHz over 2.4GHz.
Reboot the device and let wifi connect. Check if device uses a 5Ghz connection. (Ignore bandwith / speed for now.)
Create a logfile, e.g. with this command via adb:
adb shell logcat -d -b all > mylog.log
The logfile may contain private information, so I recommend not to post them public. Together with the ligfile I would like to know
a) Wifi 5GHz working?
b) The country in which you have tested this.
nice work bro.
i live in iran and in this build my Z3 Dual detects wifi networks while the sim card is also connected.
but in 10 Jan 2021 update my phone can't detect my router's wifi unfortunately while the previous build could do it without problems.
hotspot turns on on both 2.4GHz and 5GHz.
in this new build cellular network and data are working.
Thanks @TheShadowOfAGhost20 !
Can you please run a root shell (E.g. by connecting via ADB, run adb root, then adb shell) and then
$> iw wlan0 scan → scan for networks
and then look if your access point is found?
Furthermore, can you please check which WiFi channel this particular router ist set to, and if possible the bandwidth?
Mr.Tom_Tom said:
Thanks @TheShadowOfAGhost20 !
Can you connect via ADB, run adb shell and then
$> iw wlan0 scan → scan for networks
and then look if your access point is found?
Furthermore, can you please check which WiFi channel this particular router ist set to, and if possible the bandwidth?
Click to expand...
Click to collapse
i did that but got this error: "/system/bin/sh: iw: inaccessible or not found"
but i found the cause: my wifi channel was set to 12. i changed it and then got detected!
TheShadowOfAGhost20 said:
i did that but got this error: "/system/bin/sh: iw: inaccessible or not found"
Click to expand...
Click to collapse
Sorry I forgot to write that you have to do this as root, I edited the post accordingly.
TheShadowOfAGhost20 said:
i found the cause: my wifi channel was set to 12. i changed it and then got detected!
Click to expand...
Click to collapse
Tha sounds reasonable. However, Channel 12 should be usable in IR.
Mr.Tom_Tom said:
Sorry I forgot to write that you have to do this as root, I edited the post accordingly.
Tha sounds reasonable. However, Channel 12 should be usable in IR.
Click to expand...
Click to collapse
channel 13 has detection problem too. the others are OK
.sorry erroneous post
New buildsFeedbacks have been positive so far, so here are some updated builds.
Lineage Sources* as of 20 March 2021
Kernel sources* based on Linux 3.4.113 with backported wifi from 5.8.18 plus cherry-pick of the following changes:
bluetooth: fixed #ifdef'ed PM callbacks ("BTLowPower" wakelock) 50f16d16b32871c5ce97b029e68692008c848bb2
SELinux enforcing
Build as userdebug, normal loglevels
* For links to sources see 1st post. Z3Dual does not have official Lineage17.1 sources yet, bringup is in progress.
Xperia Z3 (D6603):
HiDrive
hidrive.ionos.com
md5: d7aaf1fea120df3e2aad10b3a2d32226
Xperia Z3c (D5803):
HiDrive
hidrive.ionos.com
md5: 456ff87441c3a63e8dc8c7a8d03bdf39
Xperia Z3Dual (D6633):
HiDrive
hidrive.ionos.com
md5: 1848681c82d608f3212f1ace621327cb
As always, feedback is welcome.
Has anyone found a bug/installed this latest build yet? lineage-17.1-20210320-UNOFFICIAL-z3dual
Finding this super stable.. The only thing that does not work for me is the advanced boot recovery that goes back into system, But that's a known issue.
Mr.Tom_Tom said:
New buildsFeedbacks have been positive so far, so here are some updated builds.
Lineage Sources* as of 20 March 2021
Kernel sources* based on Linux 3.4.113 with backported wifi from 5.8.18 plus cherry-pick of the following changes:
bluetooth: fixed #ifdef'ed PM callbacks ("BTLowPower" wakelock) 50f16d16b32871c5ce97b029e68692008c848bb2
SELinux enforcing
Build as userdebug, normal loglevels
* For links to sources see 1st post. Z3Dual does not have official Lineage17.1 sources yet, bringup is in progress.
Xperia Z3 (D6603):
HiDrive
hidrive.ionos.com
md5: d7aaf1fea120df3e2aad10b3a2d32226
Xperia Z3c (D5803):
HiDrive
hidrive.ionos.com
md5: 456ff87441c3a63e8dc8c7a8d03bdf39
Xperia Z3Dual (D6633):
HiDrive
hidrive.ionos.com
md5: 1848681c82d608f3212f1ace621327cb
As always, feedback is welcome.
Click to expand...
Click to collapse
hi mr.tom. it's perfect as always, found no bug except wifi signal power, it's weak compared to stock roms but there was no difference in speeds. maybe it's because of wifi icon that shows little weaker signal.
and about overheating: i didn't test this build for long but while working with it i have noticed that my device is cooler than previous builds, maybe it's because of this new kernel.
i have recorded 4k for about 7 minutes then my phone rebooted i think that was because of too much heat, then i've reinstalled stock rom, however, stock rom's camera won't let me record much and the app shuts down because of heat, so i can't find out if stock rom can record 4k at least without rebooting.
i need to test this build for more time i hope the heating is now gone
and one question: can you port cyberian camera mod for these roms? or is that possible?
netwave said:
Has anyone found a bug/installed this latest build yet? lineage-17.1-20210320-UNOFFICIAL-z3dual
Finding this super stable.. The only thing that does not work for me is the advanced boot recovery that goes back into system, But that's a known issue.
Click to expand...
Click to collapse
lineage os recoveries have these problems yet, there's no fix for that, only the developer can fix it. currently the twrp works if you flash it to FOTAKernel partition but i think the twrp is useless because it doesn't install these builds.
Surely better to do: fastboot boot recovery-20201012-TESTING-z3dual.img rather than a "flash" recovery. What would be the point in flashing a recovery if its not working.
Hey
Thanks @Mr.Tom_Tom for new build and @TheShadowOfAGhost20 for testing dev builds!
today i installed the new release
but i have some problems with recovery and boot
after installing Lineage i cannot boot to recovery again
i tried adb, android advanced boot options and "fastboot boot image.img"
none of them taken me to recovery mode
so i needed to install Magisk , OpenGApps , and rom itself with adb sideload and reboot to system because i can't boot to recovery again
i'm now installing my apps for daily usage testing - i need about one or two week to test and use and see if anything is wrong or not
for now WiFi problem is gone , i have full wifi access and both sims antenna
again , thanks to everyone puts effort on this project (and sorry for bad English)
i will update this post if i found anything
navidmafi said:
today i installed the new release
but i have some problems with recovery and boot
after installing Lineage i cannot boot to recovery again
i tried adb, android advanced boot options and "fastboot boot image.img"
none of them taken me to recovery mode
Click to expand...
Click to collapse
If your going to settings\system\developer options\advanced restart\power\restart recovery , Forget it! this method doesn't work for now, & will only boot you back into Lineage. It's an issue that hopefully get's fixed in the future.
But here's a better way of entering recovery without having to flash it...
Check all your drivers are installed correctly & make sure you have the correct recovery to hand.
Here's what I Command:
adb devices
adb reboot bootloader
fastboot devices
fastboot boot recovery-20201012-TESTING-z3dual.img
Good luck!
Hey again
Thanks to @netwave i can now boot to recovery without problems by going to fastboot from adb , and booting image directly by "fastboot boot"
while using devices after installing new release , i have a problem with WiFi connectivity
when i lock the screen by power button , the wifi disconnects
for example i use whatsapp a lot and when screen is locked wifi is not connected
i checked power settings - and even set the battery profile to "Quick" (and battery saver is off) but it did not help
is this a bug or a feature?
navidmafi said:
Hey again
Thanks to @netwave i can now boot to recovery without problems by going to fastboot from adb , and booting image directly by "fastboot boot"
while using devices after installing new release , i have a problem with WiFi connectivity
when i lock the screen by power button , the wifi disconnects
for example i use whatsapp a lot and when screen is locked wifi is not connected
i checked power settings - and even set the battery profile to "Quick" (and battery saver is off) but it did not help
is this a bug or a feature?
Click to expand...
Click to collapse
Have you tried without Magisk installed? Don't use v22.0 what ever you do as it disables WiFi
Ow
I'm using Magisk and it is version 22.0
and even root not works
should i reflash ?
Edit : Ok i'm flashing again now
navidmafi said:
Ow
I'm using Magisk and it is version 22.0
and even root not works
should i reflash ?
Click to expand...
Click to collapse
Install the Magisk uninstall.zip from recovery
when your back in Lineage your still have a disabled WiFi as Magisk does not uninstall correctly.
So Install the original boot extracted from the Lineage.zip to get things working again.
- adb devices
- adb reboot bootloader
- fastboot devices
- fastboot flash boot boot.img
- fastboot reboot
Then your be sorted.