Database Info

[DEV] unofficial ClockworkMod Recovery 5 for Ingenic JZ4770/JZ4760 tablets

this is a work-in-progress development project for porting ClockworkMod Recovery 5 to Ingenic JZ4770/JZ4760 tablets.
this is not perfect at all. and I'm very busy. progress will be very very slow. I may not be able to answer your question/request. if you have some idea for improvement, please do it freely.
there is no support from any makers/vendors. you must agree all risks by installing non-supported files, it may brick your tablet, and you may lose official support/warranty.
* YOU MUST READ CAREFULLY POST#1, #2, AND #3!
* DO NOT USE IF YOUR TABLET IS NOT LISTED BELOW. IT WILL BRICK YOUR TABLET!
* project page
http://androtab.info/mips/ingenic/clockworkmod/
* supported tablets
ainol NOVO7 Basic and Paladin
Velocity Micro Cruz T100 series (Android 2.2 updated model and Android 2.0 PT701i model)
Velocity Micro Cruz T301
ronzi A3
* changelog
refer git log
* resources
http://developer.mips.com/android/
https://github.com/naobsd/cm_bootable_recovery/compare/ics...ics-mips-naobsd
https://github.com/naobsd/mips_build/compare/mips-ics-mr1...mips-ics-clockworkmod
https://github.com/naobsd/mips_external-busybox/compare/ics...ics-mips

* How to install ClockworkMod Recovery 5 (for ainol NOVO7 Basic/Paladin, Cruz T100 series, Cruz T301)
1. download recovery-signed.zip for your tablet (DO NOT USE FILES FOR OTHER TABLETS!)
2. (if you are using stock recovery)rename it to update.zip, then put it on root of SD card
3. install update.zip from recovery
on stock recovery, update.zip will be installed automatically. on ClockworkMod Recovery, you need to select menu item manually.
* How to install ClockworkMod Recovery 5 (for ronzi A3)
1. download recovery.zip for your tablet (DO NOT USE FILES FOR OTHER TABLETS!), then extract recovery.cpio.img from it
2. make backup of stock recovery
Code:
adb remount
adb shell mv /system/recovery.cpio.img /system/recovery.cpio.img.bak
3. copy recovery.cpio.img into your tablet, then flash it
Code:
adb shell inand_flash_image recovery recovery.cpio.img
* How to boot recovery
push & hold VOL+ while power on
* How to boot recovery (alternative)
Code:
adb reboot recovery
*How to control ClockworkMod Recovery 5
VOL-/HOME: down, VOL+: up, POWER/MENU: select, BACK: back

* Superuser, su, and busybox
it can be installed from ClockworkMod Recovery 5
- Superuser, su, and busybox for JZ4770 ICS
- Superuser, su, and busybox for JZ4760 Froyo
* random notes
- stock recovery
if you installed update.zip from stock recovery, stock recovery image should be renamed as /system/recovery.cpio.img.bak. (unless you didn't remove /system/recovery.cpio.img)
it can be flashed by "inand_flash_image" command. (use "flash_image" command for T100 series except PT701i model)
- mbr, xboot, boot, and recovery areas
backup/restore doesn't work for mbr, xboot, boot, and recovery areas
- time for reboot/poweroff (NOVO7 Basic)
I don't know why but reboot/poweroff take long time (as same as stock rom). you should wait 1 minute. if nothing is happened in 10 minutes, use reset hole

for now I'm preparing to push my changes to github. I'm very busy so it needs some time.
if you made some.zip file to do something for MIPS Android (e.g. superuser.apk with su binary for MIPS), please tell me. I'll add link to post#1.
if you have some idea for next work, please tell me too. (but, as I wrote, I may not be able to answer your request. sorry)

Thanks for your starting thread and project.
I bought a Advanced model but they send us a Basic Novo7.
All we know the incompatibilites using a cpu MIPS, that doesnt allow to run a lot of Android software that for default its compiled for ARM processors.
Im getting a bundle pack of apps running under our device.

Kashamalaga said:
Thanks for your starting thread and project.
I bought a Advanced model but they send us a Basic Novo7.
All we know the incompatibilites using a cpu MIPS, that doesnt allow to run a lot of Android software that for default its compiled for ARM processors.
Im getting a bundle pack of apps running under our device.
Click to expand...
Click to collapse
thank you. I understand your condition.
but here is dev thread for clockworkmod for novo7 basic. if you want to talk about apps which support mips android and/or any general things about novo7b, I recommend you to make new thread for it.

fun_ said:
thank you. I understand your condition.
but here is dev thread for clockworkmod for novo7 basic. if you want to talk about apps which support mips android and/or any general things about novo7b, I recommend you to make new thread for it.
Click to expand...
Click to collapse
I will do as you said

This is great news. If you are wanting to test any work with users on Velocity Cruz t301's which also run an ingenic processor (JZ4760) .
UPDATE: Tried running CWM for the hell of it on the t301 . Stuck at boot screen was able to get back to original recovery however. I'm guessing it might be due to the entry point into the kernel . Since the t301 is ancient Froyo. Would love to take a look at the source

Also here SHOULD be a working SU for MIPs. It work's on the cruz tablets

vanduhl said:
This is great news. If you are wanting to test any work with users on Velocity Cruz t301's which also run an ingenic processor (JZ4760) .
UPDATE: Tried running CWM for the hell of it on the t301 . Stuck at boot screen was able to get back to original recovery however. I'm guessing it might be due to the entry point into the kernel . Since the t301 is ancient Froyo. Would love to take a look at the source
Click to expand...
Click to collapse
I couldn't read what you did exactly. if you flashed my image w/o modification, it must not work. as I wrote, DO NOT USE file for other tablet.
please explain what you did, and please explain detail about your tablet before any random work.

fun_ said:
I couldn't read what you did exactly. if you flashed my image w/o modification, it must not work. as I wrote, DO NOT USE file for other tablet.
please explain what you did, and please explain detail about your tablet before any random work.
Click to expand...
Click to collapse
Attempted using the above stated method(understanding you said DO NOT US file on other tablet) I was curious to see as what kind of error would or may of come up. I'm interested in modifying this for the Velocity Cruz T301 tablet(running a JZ4760 processor) as that community of tablet users has been left under the dust. Now with the novo coming out it will further pile under the dust. I have not yet made any modifications to it, although I would very much like to.

vanduhl said:
Attempted using the above stated method(understanding you said DO NOT US file on other tablet) I was curious to see as what kind of error would or may of come up.
Click to expand...
Click to collapse
kernel must not work because it's for NOVO7B. in general, kernel can't be shared among different products.
key assign, and partition layout may be different too. but currently I have no idea how to fix them because I don't have any detail about your tablet...

http://en.ingenic.cn/product.aspx
it seems JZ4760 is NOT MIPS32R2. then I need to recompile userland binaries.
anyway, technical detail is required to support other tablets.

http://bbs.imp3.net/thread-10520163-1-2.html
it seems source code for xboot, android 2.2 and (part of?)kernel source for NOVO7B is released. I don't try to compile them yet so I may be wrong.
I'll check them later.

Is it possible that someday this recovery will be also ported for ainol novo7 Advanced ?

endrju100 said:
Is it possible that someday this recovery will be also ported for ainol novo7 Advanced ?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1378594
you should use search engine before post a question.

vanduhl said:
This is great news. If you are wanting to test any work with users on Velocity Cruz t301's which also run an ingenic processor (JZ4760) .
UPDATE: Tried running CWM for the hell of it on the t301 . Stuck at boot screen was able to get back to original recovery however. I'm guessing it might be due to the entry point into the kernel . Since the t301 is ancient Froyo. Would love to take a look at the source
Click to expand...
Click to collapse
How did you get back to your stock recovery image on the T301? I think I borked mines on a T105 accidentally with ROM Manager. I accidentally pressed the screen too many times while 'exploring' and the delayed input caused ROM Manager to start flashing a recovery. Now I can't boot into recovery. I just see black nothing.
EDIT:
Disregard - My stock recovery boots. I was performing the boot into recovery procedure incorrectly. Also, because the recovery.cpio.img was in /system I assume it was flashed on each power cycle.
Apologize: I have read the complete topic and now understand that at present it is only for Novo.

Please dont use this thread to talk for another devices that arent be Novo7 Basic.
Asi cant start a new thread yet, here is my thread at spanish forum comunity with a full starter packs of mips app + games and a guide to be root.
htcmania. co m/showthread.php?t=303749

I´ve got successfully get a compiled MIPS version of Titanium backup that works like a charm for our device Novo7 Device! Checkout at the link upside.
Regards. (I will open a new thread when i´ve got 50 messages...)

fun_ said:
it seems source code for xboot, android 2.2 and (part of?)kernel source for NOVO7B is released. I don't try to compile them yet so I may be wrong.
I'll check them later.
Click to expand...
Click to collapse
what other info would you like?

[HELP!] Velocity Cruz T301 Full Brick Recovery

Hi XDA,
so basically i bought a Velocity Cruz T301 recently and followed the known procedures for rooting, flashing ClockworkMod Recovery and custom rom (SJHill Rom v0.3).
before the full brick my device was at ClockworkMod 5 and rooted with SJHill Rom v0.3.
i installed CWM by flashing the zip in stock recovery, then succesfully rooted the device, finally wiped and flashed my custom rom
after major dissapointment in this tablets performance i decided i wanted to get rid of it.
So i downloaded the stock rom, wipe and flashed it onto the tablet...
the tablet turned off when it was finished (i think it was attempting to reboot) and never turned back on again...EVER! :good:
i cant even get to recovery
i tried flashing with adb and fastboot but the device is never even presents itselft to the computer.
i found out that you can boot the device into USB boot mode where you hold the "VOL -" (Volume Down) button and press the reset button and while connected to the computer (windows only) a "JZ4760 USB Boot Device" appears.
i did some googling and also found out that the T301 is based on similar tech to a bunch of tablets and they can all be modified by some software released by Ingenic called USBBootTool.exe
the tool is written in chinese and i cant decypher it all, though i found out how to use it based on its usage for other Ingenic based tablets
1.) you will need to disable driver signature verification (press F8 on boot of windows and toggle the setting, i hate rebooting too but it has to be done)
2.) boot your tablet into USB Boot Mode (hold down Vol - and press Reset button)
3.) install the driver for your device (included in the files below)
4.) with the tablet disconnected you would open the USBBootTool.exe
5.) select your tablet in the options and fill each box with the files needed to flash (files included below)
6.) reconnect the tablet while still in USB Boot Mode and the software will flash your device on detection
everything goes fine for me except when i get to the flashing part in the end.
when USBBootTool detects my tablet, it attempts to flash and gives me a stream of errors and never flashes my device.
i dont know what to do at this point. i have provided direct links to all the software im using and also links to where i got them.
any help would be appreciated, thank you to the XDA community in advance
>------------------- DOWNLOADS ------------------------<
USBBootTool.exe / Tablet Drivers (4725 / 4725B / 4740 / 4750 / 4755 / 4760 / 4770)
http://dl.dropbox.com/u/79196608/burn_tools_3.0.16.rar
obtained from - http://forum.xda-developers.com/showthread.php?t=1720621
Velocity Cruz T301 Update.zip (contains the system.img / data.img / mbr-xboot.bin files)
http://www.cruztablet.com/T301update.zip
obtained from - http://www.cruztablet.com/Article_861.php
SJHill Rom v0.3
http://www.androidfilehost.com/?fid=9390362690511176486
obtained from - http://www.slatedroid.com/topic/27583-rom-t301-sjhill-rom-17-feb-2012-download-link-updated/
ClockworkMod 5
http://files.androtab.info/ingenic/cwm/20120514/T301-recovery-signed.zip
obtained from - http://androtab.info/mips/ingenic/clockworkmod/

I have the same situation. I have gone through every menu in the USB Boot tool and to no avail am I able to recover my T100.

gmick is redoing the software because the coding is set up wrong. Once he gets that figured out there should be a fool proof unbricking method that we can follow. He is posting information over on Slate Droid if you want to take a look.

feyerbrand said:
gmick is redoing the software because the coding is set up wrong. Once he gets that figured out there should be a fool proof unbricking method that we can follow. He is posting information over on Slate Droid if you want to take a look.
Click to expand...
Click to collapse
ok post the link to the thread, and ill add it to the first post as a solution if its found to be a working one

JustSayTech said:
ok post the link to the thread, and ill add it to the first post as a solution if its found to be a working one
Click to expand...
Click to collapse
*Cross Post from SlateDroid* (but I can't post the link because XDA won't allow it)
I found out why the USB boot isn't working. Well, more appropriately I know where it fails but not exactly "why".
The USB Boot tool works like this:
1) Send x00 command (Get CPU Info)
2) Device responds with "JZ4760V1"
3) Host sends two binaries, stage1 and stage2. Stage 1 sets up memory stuff, and Stage 2 sets up USB flashing functions.
4) Host checks that the binaries executed by issuing another x00 command (Which serves as an "Are you still there?" function)
5) If the response is good, the host will flash the images, if the response is bad, it will abort.
Our devices are failing at step 4. The linux usb boot tools (xburst-tools) fail in an identical fashion.
I know that the first stage binary transfers and executes fine because if it didn't the device would be limited to 16k. The second stage is 120K and is transferred successfully. Once the second stage "execute" command is sent, the device crashes.
The second stage is also unique to the CPU type. I've used all of the binaries for JZ4760 I could find on the net and when that failed I cross compiled my own binary from source and it still crashed.
At this point I highly doubt I'll ever be able to fix it, and this completely explains why no one could get any usb recovery tool to work while others using similar devices could. I guess our board is modified just enough for ingenic's stock binaries to fail. Without knowing what's changed (getting Velocity Micro's source) we're SOL.
I can open it up again and solder on the serial header but I'm betting it's going to give me some generic "couldn't execute" message that isn't going to help me. I'll probably do this anyway though because I've come this far so what's the loss.

wow, i learned alot from that post, seems like writing a usbboottool-like application that can send the commands but also log and possibly bypass security checks etc but that def would take sometime. thank you for your insight, seems youve come the closest to cracking the case, actually you found the fault, hopefully your methods can eventually bring about a fix

JZ 4770
gmick said:
*Cross Post from SlateDroid* (but I can't post the link because XDA won't allow it)
I found out why the USB boot isn't working. Well, more appropriately I know where it fails but not exactly "why".
The USB Boot tool works like this:
1) Send x00 command (Get CPU Info)
2) Device responds with "JZ4760V1"
3) Host sends two binaries, stage1 and stage2. Stage 1 sets up memory stuff, and Stage 2 sets up USB flashing functions.
4) Host checks that the binaries executed by issuing another x00 command (Which serves as an "Are you still there?" function)
5) If the response is good, the host will flash the images, if the response is bad, it will abort.
Our devices are failing at step 4. The linux usb boot tools (xburst-tools) fail in an identical fashion.
I know that the first stage binary transfers and executes fine because if it didn't the device would be limited to 16k. The second stage is 120K and is transferred successfully. Once the second stage "execute" command is sent, the device crashes.
The second stage is also unique to the CPU type. I've used all of the binaries for JZ4760 I could find on the net and when that failed I cross compiled my own binary from source and it still crashed.
At this point I highly doubt I'll ever be able to fix it, and this completely explains why no one could get any usb recovery tool to work while others using similar devices could. I guess our board is modified just enough for ingenic's stock binaries to fail. Without knowing what's changed (getting Velocity Micro's source) we're SOL.
I can open it up again and solder on the serial header but I'm betting it's going to give me some generic "couldn't execute" message that isn't going to help me. I'll probably do this anyway though because I've come this far so what's the loss.
Click to expand...
Click to collapse
for my JZ4770 Earlier USB tool was flashing .img without any problem but for now it is saying "load cfg failed". "API downlaod failed' like dialogues and doesnt flash anything. Any idea? Thanks in advance!!

First restart your computer (actually restart it) then redownload the USB boot tool and save it in a completely new directory and use a different USB port
Sent from my Pokeball

Yes, I did
JustSayTech said:
First restart your computer (actually restart it) then redownload the USB boot tool and save it in a completely new directory and use a different USB port
Sent from my Pokeball
Click to expand...
Click to collapse
Yes, I tried with this suggestion. Rather I reinstalled xp and the tried again. But the dialogues are same. The history is like this. Was having ICS on JZ 4770. Formatted with usb tool and put JB updates. It was not sensing touch so reflashed another JB updates. Now the tab boots, it reaches to boot logo for around 12 seconds and restarts in stock recovery. While it is in booting stage it get detected by windows and adb also. In stock recovery mode it get detected by windows and in turn by adb also. If I tried to install updates through SD card it shows it had installed and reboots after completion. But again the same way it goes to boot logo and then back to stock JB recovery. It also boots in ingenic boot device mode and gets detected by USB burn tools. But when try to flash any of the ROM it gives the same dialogues "check cfg failed" "api download failed" "boot. fw failed" and cant flash anything.
Is there any tool which can be flashed or a script which can be used from SD card for completely formatting flash memory so that USB burn tool can flash required ROM?

can you flash the stock rom in recovery?

Managed using USB BOOT TOOL for ingenic JZ 4770 board in English
JustSayTech said:
can you flash the stock rom in recovery?
Click to expand...
Click to collapse
thanks man but I managed to boot the device. I used following USB BOOT TOOL for ingenic 4770 boards. The goodness with this tool, this is completely in English. You will know what you are doing. Even after opening the main window of the tool you can right click and then get another options(yes again in English). My problem with this device was bad blocks at 1024. In the options there is chance to force erase whole the nand partitions which I used and erased all the partitions thereby made all the partions available for flashing and readable by the tool. Then from File option selected stock rom files and flashed them. While flashing selected JZ4770 iNanad.ini file in manual configuration. This tool has really helped me to come out of the issue and will be useful for guys using JZ 4770 board.
http://www.4shared.com/rar/m1BUV5r2/USBBurnTool_20120401_for_relea.html

Got USBBootTool.exe kind of working.
1. Download the following file from Ingenic.
ftp * ingenic * cn/3sw/01linux/tmp/jz4770-20110610.rar
2. Download Applocale from Microsoft.
www * microsoft * com/en-us/download/details.aspx?id=13209
3. Extract the jz4770-20110610.rar and find the folder. (Using 7zip should keep the UTF encoding in Chinese)
20110610\04burn\20110524_4770_Programmer
4. Copy the folder 20110524_4770_Programmer to location you want to use it in.
5. Install Microsoft Applocale (Just in case, I don't think it is required)
Now Start Applocale and create a shortcut to USBbootTool.exe inside 20110524_4770_Programmer
中文(简体) is simplified Chinese option and should let you view the GUI correctly.
6. Now with the Applocale Shortcut created for USBbootTool.exe you can start the application with correct fonts.
Now this is where is breaks down.
TABLET-8 NAND FINAL BSP(S3 TEST) will allow you to read from it and write to it, but the CFG is off.
\tool_cfg\tablet-8-nand-final.ini is the configuration for it.
DO NOT CONNECT THE DEVICE WITH ANY OPTIONS CHECKED OR LOAD ANY FILES.
See Attached Images.
Next to the Read button is some Boot Option menu. I am not fulling aware of what this does.
What I need is a someone to help me fix/correct the ini/cfg files in
\20110524_4770_Programmer\tool_cfg\.ini
\20110524_4770_Programmer\4760\
to correctly match the files of the NAND.
Also if anyone has a copy (dd to img) or (cat to img) of the block devices.
That would help a ton.
# cat /proc/partitions
# cat /proc/mtd
I would also love another T10x Tablet for cheap.
I want to start building things like new bootloader, kernel, system image,
performance libraries to take full use of the Ingenic JZ4760 (www * ingenic * cn/product.aspx?CID=11)
I also bring Christmas gifts
2 APKS. You can place them in /system/app or /data/app.
Google Play will crash now and again, but it will load and work. (Vending.apk)
Secondly I bring the gift of performance increase, just by a slight bit.
edit the line of the heapsize in /system/build.prop dalvik.vm.heapsize=96m
Remember to make sure the permissions are set back to 666 or 644.
Original Vending.Apk before updates came from here: (Incase you are paranoid)
code * google * com/p/ics-nexus-s-4g/source/browse/trunk/system/app/Vending.apk?spec=svn20&r=18
ics-nexus-s-4g * googlecode * com/svn-history/r18/trunk/system/app/Vending.apk
To prevent spam on the XDA forums, ALL new users prevented from posting outside links in their messages. After approximately 10 posts, you will be able to post outside links. Thank you for
Click to expand...
Click to collapse
Stupid. how do you expect real people to help post Tech Docs? That is bad Moderating and Administrating.
Make sure to replace the Asterisk's with spaces to normal dots.

Requesting Block Images.
Does anyone have a copy of it they can send me for a T10x?

block images......
IceGryphon said:
Does anyone have a copy of it they can send me for a T10x?
Click to expand...
Click to collapse
Which block images do you want?
...also is there a way to rip the stock images off the jz4760 in the t301.
Such as:
Can i usethe ingenic uboot tool?
Anybody find the jtag pins?
Is the 4 pin conn next 2 the batt for serial?
.......i guess ill try to take a look this weekend
Ics would be really nice, but probably slower than stock..... especially with the limited ram
I unpacked the stock rom. I also unpacked an ics rom for a jz4770, and repo sync'd the aosp and mips 3.0.8 android kernel.
I'm still trying to figure out specs for the processor though. I know that its mips32 - el- fp- r1, but i cannot figur out the dsp version ... if it has one?

Error in erasing nand
nanachitang420 said:
thanks man but I managed to boot the device. I used following USB BOOT TOOL for ingenic 4770 boards. The goodness with this tool, this is completely in English. You will know what you are doing. Even after opening the main window of the tool you can right click and then get another options(yes again in English). My problem with this device was bad blocks at 1024. In the options there is chance to force erase whole the nand partitions which I used and erased all the partitions thereby made all the partions available for flashing and readable by the tool. Then from File option selected stock rom files and flashed them. While flashing selected JZ4770 iNanad.ini file in manual configuration. This tool has really helped me to come out of the issue and will be useful for guys using JZ 4770 board.
http://www.4shared.com/rar/m1BUV5r2/USBBurnTool_20120401_for_relea.html
Click to expand...
Click to collapse
I used english ingenic tool to erase bad blocks but m nt able erase bad blocks live suit is giving eror id=0x4848

[Win32/64][Dual Boot][Mount-Loop] Tubuntu - 1 click installer SBK1 & SBK2! *2/1/2013*

[Win32/64][Dual Boot][Mount-Loop] Tubuntu - 1 click installer SBK1 & SBK2! *2/1/2013*
* ADDED Ubuntu Raring(13.04) *
* ADDED ARCH Linux *
Tubuntu - One Click Installer for Windows​
Hi, i recently been seeing myself flashing my tf101 a lot using OLiFE2. yes my main os is linux but i also use windows and came across a lot of people asking about windows verison SBK2 for ubuntu installer. I found modified version of Frankc123 tools http://forum.xda-developers.com/showthread.php?t=1760513 but it's down. so i created a new one from scratch.
thanks
lilstevie for his OLiFE scripts
wheelie app
Frankc123
kenshin1388
and a few more. (i will find there names and edit this post again)
*Name is still Pending. couldn't think of a good name when i was making this tool. suggestions are welcomed!
Disclaimer:
you know the usual stuff. use are your own risk blah blah might brick.. will not help your become rocket scientest... yea that stuff.
Note:
this was made using VS2010. package needed to run will be dot net 4.0. google is your friend
this is very alpha not all the features are implemented yet
Code:
v0.4.7:
fixed sbk1 device flashing.
v0.4.6beta:
reworked the code for loading into sync mode for sbk1 devices
basically wasted my time with version 0.4.4b & 0.4.5b due to this new update =P
v0.4.5beta:
removed --setbct parameter for sbk1 devices
v0.4.4beta:
fixed bct loader for sbk1 devices
v0.4.3beta:
fix bootloader injection for sbk1 devices
v0.4.2beta:
fixed more bugs not initiating wheelie when needed to for sbk2 devices
v0.4.1beta:
fixed syntax error for flashing kernels
v0.4beta:
added sbk1 support(not tested nor confirmed yet)
re coded flashing method
fixed kernel flashing
fixed only ubuntu boot
fixed only ubuntu/android boot
v0.3alpha:
added RootFS install only option to selected partition
added 2.6x x3maniac kernel to the mix
removed uboot kernel image.( i will not be developing on uboot yet)
reduces zip from 80mb to 50mb. quicker download for faster hacking =)
v0.2.2alpha:
fixed ubuntu/android flash.(ubuntu as default was not booting)
fixed timing issue caused with apx mode detection.
v0.2.1alpha:
added APX mode detection.(now this app will let you know if you are really in apx mode, using drivers i provided)
v0.2alpha:
added logo
added ability to for different flashes and restore back to stock
added different recovery CWM and TWRP
added kernel flashing for chromium or jhanti
fix textbox not updating with console
few bug fixes in program
v0.1a:
initial release
Known bugs:
Code:
[strike]when flashing with Ubuntu Only. kernel panic and keeps rebooting. i am working on a fix.[/strike]
program appears to not be doing anything while flashing device. if it's not frozen and window can be dragged
around it's working. wait for device to reboot. usually 15 - 20 mins to upload 1gb
Not my program bug. but should be mentioned. After you flash your device the 1st time. let Prime run until welcome
screen. then you can flash twrp to flash custom rom. Failure to do so and flashing custom rom without letting prime
run will cause boot loop in newly flashed custom rom. i havn't looked into the logcat but i'm pretty sure that the data
partion don't match or something.
if you run into any problems and you feel it might be bricked.( haven't happen to be at all using this tool) you can use http://forum.xda-developers.com/showthread.php?t=1688012 easy flasher to fix.
Instructions:
MOUNT-LOOP now possible! * 2/1/2013 *​
I have now made my new kernel which supports Mount-Loop!! thanks to transformador for the suggestion.
http://goo.im/devs/x3maniac
what does this mean?
this means that you can now just place the ubuntu.img in your internal sdcard and boot the image.
How it works?
i have turned this into a blob file(can be flash with cwm or twrp). which mean you can boot into your recovery flash ubuntu-mountloop.zip. To go back to your android you would need the kernel blob that goes along with the rom your are using. http://www.mediafire.com/?labcx60jowrdx which can be found here. (this is not my link)
Need more information?
http://forum.xda-developers.com/showthread.php?t=1537566
**Useful posts**​information regards to partition size
Thanks again to TomTcom for putting together instruction to get BLUETOOTH working!!!! http://forum.xda-developers.com/showthread.php?t=2128080
**FOR SBK1 devices**​Follow this guide TomTcom has created! don't forget to thank him!
http://forum.xda-developers.com/showthread.php?t=2041030
**FOR SBK2 devices**​
FOLLOW THIS UPDATED GUIDE [GUIDE][Win32/64][Dual Boot] For SBK2 Install of TFUbuntu for x3Maniac Thread by Kingzak34 & don't forget to thank him!!
download the prime image and have it named system.img(if not so already) and place it in the /images folder
download the ubuntu image of your choice and name it ubuntu.img and plce it in the images folder.
go into APX mode. (press volumn up & power at the same time until screen goes black) for windows try to listen for a usb connected sound( for linux type lsusb and look for nvidia(not asus))
Dual Boot A/U:
use flash from dual boot a/u option and wait for device to reboot.
Flash Recovery for Custom rom:
to flash custom rom. goto advanced option and use "flash TWRP recovery" and click "flash". the button will now say "reflash" to reflash the kernel back into the recovery partition.
Drivers:
this option is to install the drivers for APX mode.
(¯`'•.¸//( Using Custom ROM(cm, aosp, etc......))\\¸.•'´¯)​this app will re-partition the file system adding a new ubuntu partition on block 16 (mmcblk0p8). this mean it will erase everything. keep the CustomRom.ZIP in your external sdcard. (flash/dual boot a/u) wait till that finishes then let prime Rom boot fully till you get "welcome" screen. reboot into APX mode and use (advanced/flash twrp recovery).. goto recovery(volume down & power) to boot into twrp and flash your CustomRom.ZIP. when done flashing custom rom. go back into tubuntu app and click "ReFlash" in (advanced/flash TWRP recovery) to flash the recovery back to booting ubuntu.
Screens
{
"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"
}
tubuntu v0.4.7 [1mb] Executable ONLY - download v0.4.2b and replace the tubuntu.exe with this one
download v0.4.7 (jan, 3 2013)
tubuntu v0.4.6beta [1mb] Executable ONLY - download v0.4.2b and replace the tubuntu.exe with this one
download v0.4.6b (dec, 10 2012)
tubuntu v0.4.2beta [78mb] without Prime(system.img) or ubuntu.img
download v0.4.2b (dec, 7 2012)
tubuntu v0.3alpha [57mb] without Prime(system.img) or ubuntu.img
download v0.3a
Prime ROM[stock hc w/ root](system.img)
download
lilstevies Prime
http://forum.xda-developers.com/showthread.php?t=1191141
Tubuntu Image - lightweight ubuntu
Tubuntu In Action! video submitted by hugantic​
Ubuntu Raring Ringtail (13.04) is up on goo.im
This is a ubuntu-core image.(this mean it has nothing)
for a quick and dirty howto check post #652
password: family
added Nano
added WPA_SUPPLICANT
added kernel supplicants(2.6.36-12.10+)
added wifi modules on boot
Image is 200M
this is a nightly development from http://cdimage.ubuntu.com/ubuntu-core/daily/20130201/
i have this up cause when 13.04 does launch i know what i'm dealing with =)
ARCH Linux for ARM (alarm)
Arch Linux - http://goo.im/devs/x3maniac 151M
More Details for How To
this is a build it yourself system.
It Boots
root password: family
Ubuntu(ubuntu.img)
Lubuntu v1.2 (12.10) - http://goo.im/devs/x3maniac 496.01 MB
only added support for 2.6.36 kernel.(if you want to use newer kernels must installed kernel and supplements)
please review all change log from previous version to see what and how much i have done
zram is broken with kernel 2.6.36 (I am working on patching this up to new zram variation)
added multi-touch support
minimize - three finger down swipe
scroll - two finger up or down
maximize - three finger up swipe
move window - 3 finger drag
right click - two finger tap
fixed boot loop when using "reboot to recovery" from android space
fixed typos on applations not starting
updated a few program forked from "raring" 13.04
removed unnecessary boot up bloat
fixed conky from dissappearing when clicking on desktop
sound works (must use alsamixer and enable DACL & DACR)
Hot plugging works!
DO NOT INSTALL NVIDIA DRIVERS!!(2.6.36.4 does not have hw acceleration)
Lubuntu V1.1-rc1 (12.10)- [download] -382mb 1.4G unrar (wip)(i don't have dock yet so some stuff can't be tested. but it's stable @ 1.2ghz)
Don't forget to download and flash the new kernel below
lots of fixes read post #236 remember to thank Serkenar!!
changed swappiness to 10
now will start on performance mode on boot(had to recompile the kernel for that)
added script in rc.local to fix sound on boot up(you will now hear a slight click noise on boot, means sound should be working)
added scripts to brighten and darken screen(can't test yet but should would with function keys on keyboard)
using newest 3.1.10 kernel forked from jhinta(i just overclocked it)
added script to turn off backlight completely when xscreensaver "blanks" screen
added initial firstboot script to re-partition file system broken: run "sudo resize2fs /dev/mmcblk0p8" (in terminal for now until i get it working again)
sound is working
added cpufreq goverenor controller(located in menu/preferences/cpu-goverenor)
added conky (auto starts with session)
changed XF86poweroff button to disable screen(instead of logoff-selection)
added adb support(jhinta kernel break it, do doesn't work. i'm looking for a fix)
removed programs that our tablet can't use(example: xbacklight)
added zram support
added cifs support(to mount window shares install cifs-utils)
fixed nvidia tegra headers(now can be installed via "software sources" and disabled if needed)
added support for ntfs read and write support
chromium fixed
added some what of a patching system. to upgrade my builds without having to reflash.
added default user "user" (password family)
fixed "waiting for network". no more waiting
removed option with onbaord on boot in favor or default user
added gnome-system-manager (much better i think)
removed extra /lib/modules/ not needed
fixed apparmor complaining issues on boot.
added kernel boot to show everything(easier to debug for me, will be removed in future release when i know it's stable)
some more stuff i can't seem to think of( just bug fixes).
kernel issue: usb stuff gotta be plugged in before you turn on device
kernel issue: touch pad not working(look at post #154 & #206 for fix)
Discussion starts from page 13: http://forum.xda-developers.com/showthread.php?t=1995157&page=13
Lubuntu (12.10)- download - 448mb zip 1.5gb unzipped -now its working, but still don't have my dock =(
version 1.0
removed ubiquity
removed oem-config-firstinstall
removed wpa-supplicant on boot in flavor of network manager(much easier)
pre-installed all packages needed to startup and run
added support for kernel 2.6x and 3.1x
hardware accereration fully working
(not working :cryingadded onboard support for login(people without dock)
added resize2fs on boot (first time) to resize ubuntu image to fill partition (6gb)
pre-installed openssh
more stuff like bug fixes.
what's not working yet:
**do not use android os to reboot to recovery - you will be stuck in recovery boot loop!**
if you happen to be stuck in recovery loop type this in terminal
Code:
sudo echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
sound
zram
aircrack
webcam(don't think this will ever work)
chromium-browser (use firefox instead for now)
this is a LXDE destop version of ubuntu http://lubuntu.net/ light weight and works pretty fast with our devices. i have not been able to fully test if this linux image is stable. currently still waiting for my keyboard to arrive. i will be making this lubuntu image better as i go.
(root password is family i changed it due to hurricane Sandy, yes i'm from NYC)
i'm in the works for my own Lubuntu Image and Arch linux. (waiting for my keyboard dock to arrive but i do have both os booted)
I use netinstaller v0.5 (smaller file size) v0.6(more bug fixes and better support for no dock)
http://forum.xda-developers.com/showthread.php?t=1852702
lilstevies ubuntu.img
http://forum.xda-developers.com/showthread.php?t=1191141
shaola Debian image
http://forum.xda-developers.com/showthread.php?t=1476835
Kernels
#470 Controlling your CPU for stability
Stable kernels (use with care for OC version)
[extreme]
2.6.36 - [cpu 1.6 ghz] [gpu 400mhz] - download
benchmarks - blowfish score 30
glxgear - 70 fps
[good]
2.6.36 - [cpu 1.4 ghz] [gpu 300mhz] - download
benchmarks - blowfish score 36
glxgear - 59 fps
[stock]
2.6.36 - [cpu 1.2 ghz] [gpu 300mhz] - download
benchmarks - blowfish score 40
glxgear - 50 fps
kernel supplement - 2.6.36.4-1210.zip
extract and copy the kernel suppliment to /lib/modules/ then use tubuntu tool to flash new kernel
[whats up with 2.6.x]
clocked at 1.2ghz (for now)
hot plugging works
sound works
chrome works (enable CONFIG_SYSVIPC & CONFIG_SHMEM)
STABLE. does not have freezing issues
lid patch
hardware acceleration (not working)
** experimental NOT Stable! **
compiled with gcc 4.7
3.1.10 - xlinux.img
source - http://github.com/novaspirit
*kernel Instructions*
download kernel unzip and place in \tubuntu\images folder
copy the xlinux.img over linux.img(temp fix to load new kernel until i get the program fixed)
flash using "x3maniac 2.6 kernel" (even tho it says 2.6, your acutally uploading the new xlinux.img, which is 3.1.10)
*updated kernel 12/10/2012*
kernel image - 3.1.10-g6e2783c
kernel supplement - kernel_sup.tar.gz
download the kernel supplement file and place it on the root of the drive.
you can also wget the file
Code:
sudo wget http://novaspirit.com/tubuntu/kernel_sup.tar.gz /
unzip using root
Code:
sudo tar zxvf /kernel_sup.tar.gz
this will extract the new firmware and modules to the correct location(/lib/modules, lib/firmware)
now use my tubuntu tool copy the linux3.img to the \images\ folder and rename to xlinux.img
now flash using "x3maniac kernel" option in the advanced section.
** I will be making a tutorial when i get around to it **
*linux version*
as per a few request in this thread about a linux version. i will not be creating a linux version for there is one that works perfect!
OLiFE by lilstevie
someone then has modified the version and made it compatible with SBK2 devices using wheelie. due to OLiFE sbk2 is hard to find on this forum i have uploaded the version to my own server
OLiFE sbk2
I did not create this program so support for it will be limited.
*i don't remember where i found the thread nor who modified it. if someone knows the orginal creator please pm me and i will update to apply credit to the dev. the orginal creator contacted me josteink. thanks for his amazing work on updating oLiFe to support sbk2
Source Codes - http://www.github.com/novaspirit/
Downloads - http://goo.im/devs/x3maniac

I am very interested in this!
However, I do not want to spend time tweaking a whole bunch of stuff and there seems to be conflicting and outdated info on how linux/ubuntu runs on the tf101
Would you summarize what bugs you've noticed with both your tool and using ubuntu on the tf101? I'd really appreciate it as its been hard to get a good picture.

LeoBloom. said:
I am very interested in this!
However, I do not want to spend time tweaking a whole bunch of stuff and there seems to be conflicting and outdated info on how linux/ubuntu runs on the tf101
Would you summarize what bugs you've noticed with both your tool and using ubuntu on the tf101? I'd really appreciate it as its been hard to get a good picture.
Click to expand...
Click to collapse
give me a few more days and i'll come up with a good summary for you(waiting for my dock). but as for a brief one. it works really well on minimal install like lxde or gnome classic. everything does work except webcam. it's pretty stable but i've been flashing my device so much i havn't stayed on one os that long(1 day max). hardware acceleration does work on certain kernel (will be updating my programs to inject new kernels later). my goal for this program in general is to keep my transformer as a fully functional 2nd laptop and being able to swap between / backup my ubuntu as i go along trying to find the perfect build.

Definitely man, take your time. I really appreciate you doing this!
I too wanna convert the transformer into a laptop because I am sick of android honestly, but the transformer is a pretty sweet piece of hardware.
I'll try it out now

LeoBloom. said:
Definitely man, take your time. I really appreciate you doing this!
I too wanna convert the transformer into a laptop because I am sick of android honestly, but the transformer is a pretty sweet piece of hardware.
I'll try it out now
Click to expand...
Click to collapse
i have flashed my own device at least 10x working on this program. so i know it works. thanks for trying it out let me know if you have any bugs or features you want to see

x3maniac said:
i have flashed my own device at least 10x working on this program. so i know it works. thanks for trying it out let me know if you have any bugs or features you want to see
Click to expand...
Click to collapse
I must be a complete noob.
For the life of me I can't figure out where to find a system.img or ubuntu.img
The link to lilstevie's ubuntu.img doesn't seem to be pulling anything up, and I thought that the system.img is somehow extracted from the android update zip file but I can't figure that out either. The link that you posted for the system.img didn't seem to mention it, but I'll look a little deeper.

LeoBloom. said:
I must be a complete noob.
For the life of me I can't figure out where to find a system.img or ubuntu.img
The link to lilstevie's ubuntu.img doesn't seem to be pulling anything up, and I thought that the system.img is somehow extracted from the android update zip file but I can't figure that out either. The link that you posted for the system.img didn't seem to mention it, but I'll look a little deeper.
Click to expand...
Click to collapse
look in post #3 of lilstevies thread. OLiFE with prime. pull the system.img from there. it's going to be a bit before i get mine up on my website. 500mb

Hi!
Hi!
Thanks for the great and awsome work!
I just used ur tool but when i boot to ubuntu i get this screen:
I have no idea what to do....

Hi,
Why prime name? it's for TF101 or TF2 Prime?
Envoyé depuis mon Transformer avec Tapatalk

billouetaudrey said:
Hi,
Why prime name? it's for TF101 or TF2 Prime?
Envoyé depuis mon Transformer avec Tapatalk
Click to expand...
Click to collapse
well "prime" is the ROM stock from asus.

x3maniac said:
well "prime" is the ROM stock from asus.
Click to expand...
Click to collapse
Oh ok, I am on PA Rom, so I need PA.zip or It's work only with stock rom ?

billouetaudrey said:
Oh ok, I am on PA Rom, so I need PA.zip or It's work only with stock rom ?
Click to expand...
Click to collapse
for now you have to flash with stock rom. then install custom rom later using advanced/twrp recovery.
this app will repartition the file system adding a new ubuntu partition on block 16 (mmcblk0p8). this mean it will erase everything. keep the pa.zip in your external sdcard. (flash/dual boot a/u) wait till that finishes then let prime Rom boot fully till you get "welcome" screen. reboot into APX mode and use (advanced/flash twrp recovery).. goto recovery(volume down & power) to boot into twrp and flash your custom rom.
hope this helps

thxxxxxx

x3maniac said:
for now you have to flash with stock rom. then install custom rom later using advanced/twrp recovery.
this app will repartition the file system adding a new ubuntu partition on block 16 (mmcblk0p8). this mean it will erase everything. keep the pa.zip in your external sdcard. (flash/dual boot a/u) wait till that finishes then let prime Rom boot fully till you get "welcome" screen. reboot into APX mode and use (advanced/flash twrp recovery).. goto recovery(volume down & power) to boot into twrp and flash your custom rom.
hope this helps
Click to expand...
Click to collapse
OK Thx I will try tommorow Thx !
Envoyé depuis mon Galaxy Nexus avec Tapatalk

i9apps said:
Hi!
Thanks for the great and awsome work!
I just used ur tool but when i boot to ubuntu i get this screen:
I have no idea what to do....
Click to expand...
Click to collapse
follow the instructions on screen to finish the installtion process. head over to http://forum.xda-developers.com/showthread.php?t=1852702 post #1

Other question... Any possibility to use it on linux ? Because I don't have windows...
Manually maybe by command... Thx
Envoyé depuis mon Galaxy Nexus avec Tapatalk

billouetaudrey said:
Other question... Any possibility to use it on linux ? Because I don't have windows...
Manually maybe by command... Thx
Envoyé depuis mon Galaxy Nexus avec Tapatalk
Click to expand...
Click to collapse
my main os is linux also. but i use windows a lot also. this is what i use when in linux
Modified OLifE http://forum.xda-developers.com/showthread.php?t=1872229

x3maniac said:
my main os is linux also. but i use windows a lot also. this is what i use when in linux
Modified OLifE http://forum.xda-developers.com/showthread.php?t=1872229
Click to expand...
Click to collapse
Okey Thx if I want remove dual boot, what need I do ?
Envoyé depuis mon Galaxy Nexus avec Tapatalk

billouetaudrey said:
Okey Thx if I want remove dual boot, what need I do ?
Envoyé depuis mon Galaxy Nexus avec Tapatalk
Click to expand...
Click to collapse
i have not implemented in my app yet... soon to come(working on it as we speak) but now you can use OLiFE to return to stock android.

x3maniac said:
i have not implemented in my app yet... soon to come(working on it as we speak) but now you can use OLiFE to return to stock android.
Click to expand...
Click to collapse
OK so I wait because I'm not expert and don't all understand... And I'm french and it's not easy...
Envoyé depuis mon Galaxy Nexus avec Tapatalk

[DEV] Multiboot Linux on Infinity tf700 (project closed)

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.

[Kernel] EFIDROID - Ultimate preboot enviroment! - Multiboot / Fastboot / UEFI

updated4/4/2017 (Still does not work on stock 5.0) - Removed due to it still not booting stock 5.0, and ALSO now breaks booting unpatched.
twrp 3.1 is broken
twrp 2.7 is broken
twrp 3.0.1 works
some/most custom roms work
Most official/stock do not.
EFIDROID - Official link
Developer: m11kkaa
DO NOT BUG THE AUTHOR ABOUT BUGS/FEATURES, THIS IS UNOFFICIAL.
Most custom roms appear to boot
Install:​
assumes on stock firmware (Custom roms must report the DEVICEID as hlte, hltetmo, hltespr or hltevzw. Ask your Rom maintainer to correct it or visit post #51)
assumes root and bootloader unlocked
For now "efidroid" on playstore is not configured for our device, so we will do this using our own server:
Download "EFIDROID" from the playstore
Download "TerminalEmulator" from the playstore (or use adb shell)
Download "SimpleHTTPServer" from the playstore
NEW UNTESTED - Removed
OLD Download EFIDROID_SERVER_FILES from View attachment EFIDROID_SERVER_FILES.zip
Open and extract the "device" and "ota" folder to the INTERNAL storage of your phone
Open SimpleHTTPServer (do not change default settings)
Open Terminal Emulator and enter: (make sure you didn't forget any spaces)
su
setprop efidroid.server_url "http://localhost:12345"
Now open efidroid, it should automatically connect. Now press the menu key in the top left corner and press install, then press the big install button.
Now create your slot, and reboot.
Use the vol +/- to navigate up or down, use the power button to select an option
Long press power button on internal rom/recovery to boot without efidroid
Reinstalling/Updating:
Download the new OTAPACKAGE file and extract to INTERNALSD, replace old device/ota folders
Clear EFIDROIDMANAGER cache/data
Run the SETPROP command (don't forget su)
Turn on SimpleHTTPserver
Open efidroid and click uninstall, and then click install (Or click reinstall)
MAKE SURE YOUR BUILD DATE NOW MATCHES THE UPDATED BUILD DATE
Uninstall:
if you hit the uninstall button, the app copies the contents of the UEFIESP back to the real partitions and deletes the partition_*.img files. It does not delete the UEFIESP directory or any of the multiboot directories because they may contain other important files.
flashing boot+recovery outside of EFIDroid's control(e.g. using stock's fastboot/odin flash, or using unpatched boot) is pretty much the same as uninstalling efidroid without deleting the partition_*img files.
All that means that you don't have to worry about any of that if you restores your boot+recovery partitions(either through the app or manually). If you want to free up some space you can delete the UEFIESP directory using a root file manager.
Bugs/Issues:
REPORT ERRORS/BUG ON GITHUB
"can't find tagloader for type -1" - your recovery/rom is not supported (like twrp 3)
Report errors: https://github.com/efidroid/projectmanagement/issues
What you must include:
Exact steps to reproduce the error
Give the exact error shown on screen
If its storage related:
Give the output of "cat /proc/1/mountinfo"
EMERGENCY :
If you find yourself frustrated and just wanting things back the way they were:
Download odin
Download twrp (get the md5/tar version for odin)
Turn off phone (pull battery)
boot to download mode by holding vol down and home and power
Start up odin and press the AP button and browse for the TWRP file. Press start to flash.
Reboot phone into twrp recovery (vol up + home + power), and restore your boot/recovery partitions.
EFIDROID has now been effectively disabled[/HIDE]
Help and info:
If you are familiar with adding touchscreen support please visit us!
Join us on Slack : http://join-efidroid.rhcloud.com/
Once joined: https://efidroid.slack.com/
EFIDROID G+ page : https://plus.google.com/communities/...43671219382368
[/CENTER]

Works on N9005 LTE ?

It looks pretty cool but I've got limited knowledge. My N9005 is on phronesis rom v4.1, IdleKernel v6.6.5 and all partitions converted to F2FS, will it work on this format as well :/

As long as it is a note 3 on msm8974 (sorry exynos) it should work.
File system support should be trivial. I used that same FS myself

Is this an actual GRUB loader for android?
If so am ashuming this means it's possible for UNIX install
i.e. Arch Linux as OS.......

Hmmm.... Windows RT on Note 3... ^^
What about ACPI? We might need this for WinRT

With all due respect, I think you've posted a how to post bit earlier. I'm a flashaholic & the wait for the zip is killing me

I didn't think the day would come.
As a pleb, I will follow this thread with great interest.

djmalik420 said:
With all due respect, I think you've posted a how to post bit earlier. I'm a flashaholic & the wait for the zip is killing me
Click to expand...
Click to collapse
lololol

Wonder if this is ever going to work Great concept though.

Fake ¿ ???
Only what i see its a bootanimation, in the Video from a "older and other"

The OP account is suspended so I guess something fishy is going on.

Guess we will wait and see

oh come on now. I got suspended for being rude to a well respected member of xda. And its not fake... Really? Anyways... I took my ban as a break and just started back with m1cha on getting the uefi part to work with the screen.
A few pointers: You still need devs to port each os, like windows, true linux ect.
This is just a multiboot. So many devices lack that, some had safestrap, or kexec ect, but all those methods had quirks or special rules, or depended on android. This loads before even the kernel.
Also, it will have many tools that a typical recovery has, so you may not even need to reboot into recovery to setup partitions, also aroma was ported, so maybe even installing roms/kernels too.
Also, there will be an efidroid server "store" where you can get tools and apps to run in efidroid. So devs can extend functionality. Also there will be an android installer to make everything easier.
Just think of this as a pimped out safestrap.

SaschaElble said:
oh come on now. I got suspended for being rude to a well respected member of xda. And its not fake... Really? Anyways... I took my ban as a break and just started back with m1cha on getting the uefi part to work with the screen.
A few pointers: You still need devs to port each os, like windows, true linux ect.
This is just a multiboot. So many devices lack that, some had safestrap, or kexec ect, but all those methods had quirks or special rules, or depended on android. This loads before even the kernel.
Also, it will have many tools that a typical recovery has, so you may not even need to reboot into recovery to setup partitions, also aroma was ported, so maybe even installing roms/kernels too.
Also, there will be an efidroid server "store" where you can get tools and apps to run in efidroid. So devs can extend functionality. Also there will be an android installer to make everything easier.
Just think of this as a pimped out safestrap.
Click to expand...
Click to collapse
It doesn't matter what negative comments you get because "Criticism Is The Key To Innovation" it's my personal quotation ...I've been visiting this thread since day one at minimum of three times a day hopping that you would have uploaded the zip...Make it quick buddy & keep up the good work :good:

We need a samsung expert. Getting the display to work in uefi is troublesome. DTSI and gcdb display experience is needed.

SaschaElble said:
We need a samsung expert. Getting the display to work in uefi is troublesome. DTSI and gcdb display experience is needed.
Click to expand...
Click to collapse
as far as my knowledge is concerned, Master @darkera13 is kinda expert you're looking for...I don't personally know him or his skills but people around note 3 forums praise his work very much

Is this Note 3 specific?
This is kinda an off topic question, but, just a few days ago i wanted to try Remix OS out in my PC, but noticed that there is no direct EFI support...just thinking if this thread would be any benefit for PC UEFI users trying to boot Android x86 directly through efi file.
sorry for the question, might be my knowledge limitation on the field...

Using a x64 cpu and grub or refind you can boot RemixOS, they have a uefi image on their site. (Thats what they said) Basically you really don't need efidroid for this, as it would only make it more complicated.

grub is exactly my problem...
thanks a lot for clarifying