Database Info

[Q&A] Ubuntu on the Transformer (eMMC install)

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.

[UPDATE: 2011.11.16] [RECOVERY] [ROOT] G2x Gingerbread 2.3.3 Stock using Linux

Follow the chronological order of the listed items...
1. Several things to KNOW and DO BEFORE starting:
- this is for Linux (that is your computer OS is Linux based) users ONLY!
- Mac (though UNIX based) and Windows users GO somewhere else!
- this REPLACES your stock recovery w/ clockwork recovery; this is NOT the same as installing rom manager from the market, which won't work on your "unrooted" phone anyway, go ahead try it
- this does NOT root your phone by itself, you need to follow all the directions
- be sure your battery is FULLY CHARGED, even though you'll be removing it for part of the directions
- COPY a rom of your choice to your external sd (ONLY if using ctso's procedure or using the updated clockwork recovery zip file labeled "external," otherwise copy the rom to the internal sd); I recommend CyanogenMod 7.1.0.1 Stable
- follow the procedure listed in #2
2. Procedure for replacing your stock recovery w/ clockwork recovery:
- SEE UPDATE BELOW as this flashes clockwork recovery v3.0.2.4
***********************************************************************************************************************************
The following procedure was provided by xda member ctso...many thanks to him!
***********************************************************************************************************************************
http://forum.xda-developers.com/showthread.php?t=1044326&highlight=recovery
***********************************************************************************************************************************
Again, thanks to ctso for the UNIX terminal bash script! Be sure to THANK him yourself!
***********************************************************************************************************************************
UPDATE:
- download one of the attached clockwork recovery zip files (they include nvflash) below INSTEAD of ctso's "nvflash-recovery.tgz" to have the newer clockwork v4.0.1.5
- use the "external" file to have clockwork read files from your external sd card
- OR use the "internal" file to have clockwork read files from your internal sd card
- THANKS to krylon360 for the updated clockwork
3. Several things to DO AFTER your DONE with the procedure by ctso above:
- reboot device into clockwork recovery by holding the POWER button and VOL DOWN button, let go when you see the word "ANDROID" in the mid-left, upper portion of the screen (occurs after the LG logo appears)
****I can't stress the next 4 items in bold red enough BEFORE proceeding to load your new rom****
***If you don't do this, you're a fool***
- be sure to "wipe data/factory reset"
- be sure to "wipe cache partition"
- be sure to go to "mounts and storage" then "format /system" then "format /data" then "format /cache"
- be sure to go to "advanced" and "Wipe Dalvik Cache"
- NOW, you may INSTALL the rom you copied to your sd card in #1
- be patient! You may not get feedback that the rom is loading! Let it sit for ~10min.
- once finished the clockwork recovery menu will reappear
- be sure to go to "advanced" and "Fix Permissions"
- be sure your battery is FULLY CHARGED, go to "advanced" then "Wipe Battery Stats"
- your done; you now have "rooted" and "rom'ed" your device!
_____________________________________________________________________________________________
- I'm NOT responsible if you "BRICK" your phone
- If you don't understand what Linux is, you probably shouldn't be elevating the user privileges by "rooting" a phone that runs the linux kernel
- Do as I say, not as I do
- If I'm coming across as an asshole, it's because I probably am; I'll try to be nicer next time
- Developers put in a lot of their time and talent into projects for us for free, be sure to THANK them and DONATE to them
_____________________________________________________________________________________________
- LG P999, Rooted, CyanogenMod v7.1.0.1 Stable
- HP dv7t w/ Debian Linux

interesting
but usability does it actually bring to the phone

navendugoyal said:
but usability does it actually bring to the phone
Click to expand...
Click to collapse
Endless ....

navendugoyal said:
but usability does it actually bring to the phone
Click to expand...
Click to collapse
If you have to ask, then you probably shouldn't be "rooting" your mobile.

navendugoyal said:
but usability does it actually bring to the phone
Click to expand...
Click to collapse
You obviously have never checked the G2x Development Forum... lol

I used to have a G2x that was preloaded with Froyo 2.2, but since then have swapped phones for a newer G2x that was preloaded with Gingerbread 2.3.3. Both phones were brand new when purchased. Using the Froyo model, I was easily able to root and flash customer recovery i.e., super one click and NVFlash, however with the preloaded Gingerbread model, neither option works. I understand that I am supposed to just NVFlash clockworkmod recovery and then flash a custom 2.3.3 rooted ROM, but during the battery pull and plugging in the device while holding VOL UP + VOL DOWN, I no longer get the SW lettering on the screen. I have the exact same APX drivers and NVFlash that worked perfectly on my Froyo based G2x. Did LG change something to not allow official preloaded 2.3.3 devices to recognize APX drivers? Is anyone else experiencing this issue from a brand new 2.3.3 based G2x?
---------- Post added at 02:43 AM ---------- Previous post was at 02:38 AM ----------
I only ask this because I went as far as installing Ubuntu OS to obtain the linux NVflash method to see if the drivers work under a different operating system. I then got stuck on ctso's description of "you should see device listed under "lspci." I typed in "lspci" into ubuntu's version of command prompt and did not see any android device connected. What am I supposed to be looking for exactly?

leonblade45 said:
I used to have a G2x that was preloaded with Froyo 2.2, but since then have swapped phones for a newer G2x that was preloaded with Gingerbread 2.3.3. Both phones were brand new when purchased. Using the Froyo model, I was easily able to root and flash customer recovery i.e., super one click and NVFlash, however with the preloaded Gingerbread model, neither option works. I understand that I am supposed to just NVFlash clockworkmod recovery and then flash a custom 2.3.3 rooted ROM, but during the battery pull and plugging in the device while holding VOL UP + VOL DOWN, I no longer get the SW lettering on the screen. I have the exact same APX drivers and NVFlash that worked perfectly on my Froyo based G2x. Did LG change something to not allow official preloaded 2.3.3 devices to recognize APX drivers? Is anyone else experiencing this issue from a brand new 2.3.3 based G2x?
---------- Post added at 02:43 AM ---------- Previous post was at 02:38 AM ----------
I only ask this because I went as far as installing Ubuntu OS to obtain the linux NVflash method to see if the drivers work under a different operating system. I then got stuck on ctso's description of "you should see device listed under "lspci." I typed in "lspci" into ubuntu's version of command prompt and did not see any android device connected. What am I supposed to be looking for exactly?
Click to expand...
Click to collapse
At that point it is not an Android device. It is an Nvidia APX device. If you have a Windows computer handy (friend or at work) just use the One-Click Recovery Flasher method.

Listen to me very carefully...
leonblade45 said:
I used to have a G2x that was preloaded with Froyo 2.2, but since then have swapped phones for a newer G2x that was preloaded with Gingerbread 2.3.3. Both phones were brand new when purchased. Using the Froyo model, I was easily able to root and flash customer recovery i.e., super one click and NVFlash, however with the preloaded Gingerbread model, neither option works. I understand that I am supposed to just NVFlash clockworkmod recovery and then flash a custom 2.3.3 rooted ROM, but during the battery pull and plugging in the device while holding VOL UP + VOL DOWN, I no longer get the SW lettering on the screen. I have the exact same APX drivers and NVFlash that worked perfectly on my Froyo based G2x. Did LG change something to not allow official preloaded 2.3.3 devices to recognize APX drivers? Is anyone else experiencing this issue from a brand new 2.3.3 based G2x?
---------- Post added at 02:43 AM ---------- Previous post was at 02:38 AM ----------
I only ask this because I went as far as installing Ubuntu OS to obtain the linux NVflash method to see if the drivers work under a different operating system. I then got stuck on ctso's description of "you should see device listed under "lspci." I typed in "lspci" into ubuntu's version of command prompt and did not see any android device connected. What am I supposed to be looking for exactly?
Click to expand...
Click to collapse
************************************************************************************************************
************************************************************************************************************
thank you, for a detailed question. i appreciate that. i am glad you understand the basic concept of replacing the stock recovery, this helps immensely.
************************************************************************************************************
read carefully and thoroughly!
************************************************************************************************************
************************************************************************************************************
First, some questions and a bit of information...
1. did you install ubuntu linux as a virtual machine (guest) (i.e. using vm ware or virtual box) while using another os as a host (main) os?
2. ...or did you erase your previous os and replace it with ubuntu linux?
3. ...or are you dual booting ubuntu linux w/ windows or some other os (i only ask this to AVOID confusion in any further communicae)?
4. for the rest of this discussion we will assume you are EITHER dual booting w/ a linux os OR you erased your previous os and replaced it w/ some flavor of linux; if we HAD assumed that you were "virtualizing" a linux guest os inside of a host system like windows, then the unix bash script that ctso wrote MAY NOT work b/c virtual systems (regardless if vm ware or oracle's vrtual box) sometimes fowl up, for lack of better explanation at this point, and may not be able to identify usb connected devices properly
Second, some information...
1. a linux os (i.e. linux mint, ubuntu, debian, cent os, fedora, arch, open suse, slackware etc., etc.) does NOT need drivers to communicate to your linux kernel mobile as windows does. the linux os communicates, so to speak, to the linux that is running in your mobile handset
2. windows needs apx drivers to translate, if you will, windows/dos speak into linux/unix speak; again, the apx drivers mean NOTHING to linux b/c it does NOT need them and further more CAN NOT use them as they are for windows based computers only
3. windows' super oneclick/nv flash will NOT work w/ ANY g2x that has stock gb on it, even though it did work w/ a g2x that has stock froyo; this may change in the future (if this has changed tell me; though the info is personally useless to me b/c i have ran linux since 1999)
Third, more information...
1. the unix command 'lspci', literally means "list all pci devices" in unix speak, which, to reinforce again, is NOT understood by windows (for the most part; though dos was formulated off the unix structure)
2. the 'lspci' command is used just so you can verify that your g2x is connected to your linux computer, nothing more; and it is NOT necessary for any of ctso's procedure, he's just being complete
3. if you typed 'lspci' into the linux/unix terminal (what windows users like to call a command prompt), you would NOT see 'g2x' or anything of that nature listed; you would see a listing such as '00:05.0 PCI bridge: blah blah' (just an example!) that would indicate your mobile device is connected
4. so, do NOT worry about 'lspci'
Fourth and finally, more information and hopefully, a solution...
1. now, let's move on to more lessons in linux
2. let's pretend you downloaded ctso's script "flash-recovery.sh," how do you use it?
3. remove your mobile's battery
4. hold down VOL UP + VOL DOWN
5. simutaneously, connect your g2x to your computer (remember it better be running linux for this to work!)
6. release VOL UP + VOL DOWN
7. nothing will happen on your mobile (no "updating" or anything) and nothing will happen on your computer running linux (no windows popping up, no devices found, nothing!)
8. at this point, you could type 'lspci' into the linux/unix terminal (what windows users like to call a command prompt), but you won't b/c you don't know what you're looking at anyway
9. now, open the linux/unix terminal (what windows users like to call a command prompt)
10. navigate, yes, navigate through the folders using the terminal to where you downloaded ctso's script "flash-recovery.sh"
11. let's pretend you have the script and the ACCOMPANYING FILES that you got from ctso in a folder named 'linux' on your desktop
12. when you opened the terminal, you saw something that looked like this...
"[email protected] ~ $" w/o the quotes
13. navigate to the desktop by typing...cd Desktop
[email protected] ~ $ "cd Desktop" w/o the quotes, the "D" in desktop is capitalized and no spaces after the $
14. navigate to the folder named 'linux' that has all the goodies, not just the bash script, that ctso gave us (you are NOT going to directly use these other files, but the bash script DEPENDS on them!)
[email protected] ~/Desktop $ "cd linux" w/o the quotes
15. now, your in the folder named 'linux'
[email protected] ~/Desktop/linux $
16. now what? you will type the following...sudo bash flash-recovery.sh
[email protected] ~/Desktop/linux $"sudo bash flash-recovery.sh" w/o the quotes
17. you will be prompted for your user password, type it and press enter!
18. your mobile's screen will magically light up and say, "updating" or "SW" or whatever
19. when the terminal says the recovery image was transferred successfully, disconnect the mobile from the computer's usb, regardless of the mobile still displaying "SW"/"updating"!
20. you're done
21. i'm exhausted
_____________________________________________________________________________
- I'm NOT responsible if you "BRICK" your phone
- If you don't understand what Linux is, you probably shouldn't be elevating the user privileges by "rooting" a phone that runs the linux kernel
- Developers put in a lot of their time and talent into projects for us for free, be sure to THANK them and DONATE to them
__________________________________________________ __________________________
- LG P999, Rooted, Gb 2.3.3 Tweaked v1.2.2 by Xboarder
- HP dv7t w/ Debian Linux

If windows didn't exist, it would be a better world...
leonblade45 said:
I used to have a G2x that was preloaded with Froyo 2.2, but since then have swapped phones for a newer G2x that was preloaded with Gingerbread 2.3.3. Both phones were brand new when purchased. Using the Froyo model, I was easily able to root and flash customer recovery i.e., super one click and NVFlash, however with the preloaded Gingerbread model, neither option works. I understand that I am supposed to just NVFlash clockworkmod recovery and then flash a custom 2.3.3 rooted ROM, but during the battery pull and plugging in the device while holding VOL UP + VOL DOWN, I no longer get the SW lettering on the screen. I have the exact same APX drivers and NVFlash that worked perfectly on my Froyo based G2x. Did LG change something to not allow official preloaded 2.3.3 devices to recognize APX drivers? Is anyone else experiencing this issue from a brand new 2.3.3 based G2x?
---------- Post added at 02:43 AM ---------- Previous post was at 02:38 AM ----------
I only ask this because I went as far as installing Ubuntu OS to obtain the linux NVflash method to see if the drivers work under a different operating system. I then got stuck on ctso's description of "you should see device listed under "lspci." I typed in "lspci" into ubuntu's version of command prompt and did not see any android device connected. What am I supposed to be looking for exactly?
Click to expand...
Click to collapse
****************************************************************************************************************
jboxer said:
At that point it is not an Android device. It is an Nvidia APX device. If you have a Windows computer handy (friend or at work) just use the One-Click Recovery Flasher method.
Click to expand...
Click to collapse
****************************************************************************************************************
jboxer, I appreciate you trying to help leonblade45 , but...
****************************************************************************************************************
You are confusing the issue.
- apx drivers are NOT needed in a linux based os (i.e. ubuntu linux) and WILL NOT work in linux
- leonblade is trying to use linux, but is getting confused w/ windows knowledge he may have regarding drivers and why they are needed for windows
- windows' oneclick (as far as i know; if i'm wrong, correct me) is NOT currently able to flash the recovery onto any g2x running STOCK GB
- PLEASE SEE MY POST BELOW leonblade's QUESTION
- thank you

linux_user9 said:
If you have to ask, then you probably shouldn't be "rooting" your mobile.
Click to expand...
Click to collapse
Or he could be new and getting a feel for rooting.
Why do you people need to say rude things like this?

Oh well...
blestsol said:
Or he could be new and getting a feel for rooting.
Why do you people need to say rude things like this?
Click to expand...
Click to collapse
****************************************************************************************************************
Mr. bletsol:
- remember "rooting" or granting super user access to the linux kernel is NOT BENIGN
- Aesthetics of the mobile is NOT a good enough reason to "root", functionality/usability is understandable
- I'll say it until I'm blue in the face (which seems to be, what it takes when trying to educate windows and mac users): If you don't understand what Linux is, you probably shouldn't be elevating the user privileges by "rooting" a phone that runs the linux kernel

I see. Thanks linux_user9, your explanation is much more clear than the instructions provided by ctso. This has been a great help. I actually did end up partitioning my drive and fulling installing Ubuntu along side the Windows 7 OS. The only reason I got rid of my originally rooted G2x was because I could not escape the plagued GPS-lock problems from installing a CM7-based rom. I bought the preloaded 2.3.3 G2x in hopes of rooting it and installing an OTA 2.3.3 based rom right from the get go.

Glad to hear it!
leonblade45 said:
I see. Thanks linux_user9, your explanation is much more clear than the instructions provided by ctso. This has been a great help. I actually did end up partitioning my drive and fulling installing Ubuntu along side the Windows 7 OS. The only reason I got rid of my originally rooted G2x was because I could not escape the plagued GPS-lock problems from installing a CM7-based rom. I bought the preloaded 2.3.3 G2x in hopes of rooting it and installing an OTA 2.3.3 based rom right from the get go.
Click to expand...
Click to collapse
I'm glad to hear that the instructions were of use, please forgive me if I came across stern or condescending. I am also glad to hear you are exploring the world of linux and that you're one-step closer to completely replacing windows!
linux_user9

leonblade45 said:
I see. Thanks linux_user9, your explanation is much more clear than the instructions provided by ctso. This has been a great help. I actually did end up partitioning my drive and fulling installing Ubuntu along side the Windows 7 OS. The only reason I got rid of my originally rooted G2x was because I could not escape the plagued GPS-lock problems from installing a CM7-based rom. I bought the preloaded 2.3.3 G2x in hopes of rooting it and installing an OTA 2.3.3 based rom right from the get go.
Click to expand...
Click to collapse
Yeah, I did that dual-booting a year ago as well. And then, after 2-3 weeks, I switched. I've been Windoze-free for a year now.
(lol... sounds like out of rehab)

G2X Root with linux
WINNING!!!
Ubuntu lucid. Worked perfectly.

softbrick
So I have an lg g2x running gingerbread 2.3.3 and I went through this procedure. Everything seemed to work as described except that the phone now will not boot. I get to the LG screen but then the buttons just blink and shuts down.
I must have missed a step somewhere, though I am not sure where that might have happened. In any case, I would like to get this working or, at the very least, get the phone back and working.
Any advice is appreciated.

Soft-Brick
cyberlync said:
So I have an lg g2x running gingerbread 2.3.3 and I went through this procedure. Everything seemed to work as described except that the phone now will not boot. I get to the LG screen but then the buttons just blink and shuts down.
I must have missed a step somewhere, though I am not sure where that might have happened. In any case, I would like to get this working or, at the very least, get the phone back and working.
Any advice is appreciated.
Click to expand...
Click to collapse
2011.12.05
cyberlync:
I am sorry to hear that you're having issues with the procedure. Let me first say that I didn't receive your message until yesterday, as I choose to receive only weekly updates via email on posts that I create.
If your issue is resolved, let me know. What you're describing in your post is what is called a "boot loop," if I'm understanding you correctly.
PLEASE READ ALL OF THE INSTRUCTIONS (I know that I can be long-winded)
First, several questions for you:
1. What Linux distro are you using (i.e. Debian, Linux Mint, LMDE, Ubuntu, CentOS, etc.)? Also, what version of Linux distro are you using (i.e. Debian 6.0, Linux Mint 11, etc.) Hopefully, you're not running Linux as a VM in a Mac or Windows host.
2. What Android distro or "rom" did you decide to use (i.e. CyanogenMod, Bionix, EDT, WeaponG2x, Tsugi, etc.)? You may need to download a "fresh" copy of the "rom" in case it is damaged, corrupt or incomplete. Again, I highly recommend Cyanogenmod 7.1.0.1 Stable (Don't forget to install "gapps" if you want Google Apps in CM7)
3. With your mobile off, are you able to boot into Clockwork Recovery by HOLDING DOWN THE VOL DOWN KEY and the POWER BUTTON simutaneously, THEN RELEASING them after the initial splash screen has displayed (the splash screen image will depend on which Android distro you're using; i.e. the LG logo.)?
4. Which Clockwork Recovery are you using, that is, what is the version number (if you don't know, tell me the color that the text is appearing; i.e. orange, red, blue, etc.)? Did you use ctso's recovery flash image or one of the updated attached one's that I provided, courtesy of krylon?
Second, there's GOOD NEWS if you can boot into Clockwork Recovery, the "fix" will be much quicker. Boot into Clockwork Recovery, then do the following:
1. Check to ensure that you have a copy of the "rom," that you downloaded onto your computer, on your mobile by going to (the power button is the enter key, vol keys allow scrolling up/down) --> install zip from sdcard > choose zip from sdcard; if you do NOT have this on the sdcard, all is NOT lost in the short-term provided you used the EXTERNAL recovery flash image from krylon that I provided or the ONLY recovery flash image from ctso. If you have used the INTERNAL recovery flash image (and depending on which "rom" you have chosen, as some have re-ordered the P999's mount points), make your life easier and REPEAT THE INSTRUCTIONS IN THE OP USING THE EXTERNAL IMAGE, otherwise you may need to download the Android Debugging Bridge (ADB) from the Google developer's website and I'll have to administer some Linux/UNIX command-line instructions. IF THIS IS THE CASE, I DON'T MIND HELPING YOU, BUT IT MAY BE EASIER TO CHAT IN ICQ OR ANOTHER ONLINE MESSAGING SERVICE.
2. PROCEED TO THE FOLLOWING IF YOU USED AN EXTERNAL RECOVERY IMAGE AND HAVE A "ROM" ON YOUR MOBILE'S SDCARD:
a) If you do NOT have a "rom" on your EXTERNAL SDCARD, connect your mobile via USB to your computer, boot into Clockwork Recovery, then go to: mounts and storage > mount USB storage, press enter (power button). Then copy the "rom" to your device's EXTERNAL sdcard (NOT THE 5.8GB SDCARD [IF APPEARING; IT MAY NOT DEPENDING ON WHICH "ROM" YOU'VE CHOSEN AS SOME RE-ORDER THE P999'S MOUNT POINTS], THAT IS YOUR INTERNAL SD); next > unmount USB storage. Safely Remove drive (right-click) via the Linux file manager.
b) NOW DO THE FOLLOWING FROM MY OP:
- be sure to "wipe data/factory reset"
- be sure to "wipe cache partition"
- be sure to go to "mounts and storage" then "format /system" then "format /data" then "format /cache"
- be sure to go to "advanced" and "Wipe Dalvik Cache"
- NOW, you may INSTALL the rom you copied to your sd card
- be patient! You may not get feedback that the rom is loading! Let it sit for ~10min.
- once finished the clockwork recovery menu will reappear
- be sure to go to "advanced" and "Fix Permissions"
- be sure your battery is FULLY CHARGED, go to "advanced" then "Wipe Battery Stats"
3. This should've fixed it.
More questions/problems? We'll work through it.
linux_user9

[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

[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