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.

[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

Recovery BootStrap (TWRP) - Motorola Defy\Bravo

Recovery BootStrap (TWRP) - Motorola Defy\Bravo
Version: 4.0
Install Recovery BootStrap (TWRP) for Motorola Defy\Bravo via a USB cable. For computers running the Windows\Linux (port version) operating system.
Download: (Windows: MEGA / Google Drive) | (Linux: port by nastys post>>)
Install Recovery BootStrap (TWRP) you can right out stock firmware (without custom recovery) with superuser.
Recovery BootStrap (TWRP) - for the recovery say thank Quarx, after installation, you can install the rom CyanogenMod from Quarx for December 2014 (but do not forget about resize.zip).
Can be installed on Defy (MB525), Defy Plus (MB526), Bravo (MB520).
Requirements for smartphone:
Enable USB debugging
Superuser (ROOT)
Free space on the memory card of 100 megabytes
Instructions:
1. Download the archive
2. Unpack it somewhere else with a short path, for example D:\andro
3. Connect your phone via USB cable ("debugging on USB" should be included)
4. Run the install_bootstrap.cmd
5. When you see the label "Let's Start? =)", press any key
6. If the superuser ask permission for full access "ADB Shell", allow.
7. After installing the smart phone will automatically restart
!IMPORTANT! after restarting the Stock firmware will not start!, but you will have BootStrap (TWRP) so you can safely install custom firmware\rom
Change log:
V3:
Changed how the script
Fixed installation errors recovery on Android 4.x and later
V4:
The script changed drastically
After installation removes trash from the memory card (so far only on Android 4.x and later)
Made for normal (mortals) users , before you start the installation script checks (by model) which smartphone connected to the computer, if your smartphone is not supported script report it and stop installation, if supported will give something "Device: MB525".
Serviceability checked on the Chinese 231 (Defy) firmware with superuser (what say thank borndead), and on the Asian 231 (Defy)
Questions\FAQ:
Error "[ERROR] Verify device!", what to do?
Error "[ERROR] Verify device!", it is may mean the following:
1. You have not enabled USB debugging
2. Your smartphone does not support this Recovery. (only for MB525, MB526, MB520)
3. You need to confirm the action ADB on your smartphone
4. Or you have some other connection problems
Stock transition to CyanogenMod 11 of Quarx
Stock transition to CyanogenMod 11 (firmware and find all necessary files can be here) of Quarx in short (generally as described on the website Quarx, only simpler and under Windows)
1. Install Recovery BootStrap (TWRP) via USB
2. Enter Recovery install resize.zip
3. Restart your smartphone
4. Install CyanogenMod 11 and GApps

Good work, comrade! I flashed CM11 on the Moto Defy - everything works!

We did observed some cases, where a "new life (resized)" Defy is not booting anymore. Only solution was to reflash SBF and start from scratch.
Does this mean, it is possible to recover TWRP from PC? That would be a step a head!

This is amazing! Everytime I needed to reflash the stock ROM I needed to install cm10, then cm11, then new bootsrap etc...
Unfortunately I don't use Windows...
 @Octanium91 Would you mind if I port your script to GNU/Linux?

starbright_ said:
We did observed some cases, where a "new life (resized)" Defy is not booting anymore. Only solution was to reflash SBF and start from scratch.
Does this mean, it is possible to recover TWRP from PC? That would be a step a head!
Click to expand...
Click to collapse
I tried to do something like that, is not yet happened. Perhaps in the future even try
nastys said:
This is amazing! Everytime I needed to reflash the stock ROM I needed to install cm10, then cm11, then new bootsrap etc...
Unfortunately I don't use Windows...
@Octanium91 Would you mind if I port your script to GNU/Linux?
Click to expand...
Click to collapse
Maybe. If Iunderstand with GNU/Linux scripts

The new version, V4
The new version, V4
Changes:
The script changed drastically
After installation removes trash from the memory card (so far only on Android 4.x and higher)
More debugging: Now the script itself is not closed, and tells the user exactly what happened.
Sorry debris removal only works on Android 4.x and later.

Linux port done!
@Octanium91 I ported it to C++ (for Linux only at the moment). Please add it to the first post . Here is the link: MediaFire | MEGA
On Ubuntu just mount the ISO as image (not archive) then click 'Run' (or you can also extract the ISO and run the executable directly). It works on x86 (32 bit) and x86_64 (64 bit) CPUs. The source code is also included in the ISO. Tested on Ubuntu 14.10 and 16.04 (64 bit).
I tested it with both stock 2.3.6 rooted and CM11. It seems that the stock ROM won't boot after flashing the new bootstrap, but the recovery works fine
Also your version has a very bad bug: it flashes Defy bootstrap even on Bravo!!! It should flash Motorola Bravo specific bootstrap instead. My version only works for Motorola Defy and Defy+ at the moment, but you can edit the source code. EDIT: they are the same file with different names. I updated my version to support MB520.

After run the command script, when i boot in TWRP SDcard shows 0mb.
Already tried flashing the SBF recommended by quarx and after that the root SBF, but the result is always the same.
With CM recovery i can see the SDcard properly, but after the resize, or bootstrap, i always get 0mb at SDcard.
Any help?
Thanks!

evilinheaven said:
After run the command script, when i boot in TWRP SDcard shows 0mb.
Already tried flashing the SBF recommended by quarx and after that the root SBF, but the result is always the same.
With CM recovery i can see the SDcard properly, but after the resize, or bootstrap, i always get 0mb at SDcard.
Any help?
Thanks!
Click to expand...
Click to collapse
Format your SD card (to FAT32) or use another one.

Octanium91 said:
The new version, V4
Changes:
The script changed drastically
After installation removes trash from the memory card (so far only on Android 4.x and higher)
More debugging: Now the script itself is not closed, and tells the user exactly what happened.
Sorry debris removal only works on Android 4.x and later.
Click to expand...
Click to collapse
nastys said:
@Octanium91 I ported it to C++ (for Linux only at the moment). Please add it to the first post . Here is the link: https://www.mediafire.com/folder/candnhxj8aovj/Defy_Bootstrap_Installer_for_Linux
On Ubuntu just mount the ISO as image (not archive) then click 'Run'. It works on x86 (32 bit) and x86_64 (64 bit) CPUs. The source code is also included. Tested on 14.10 x86_64.
I tested it with both stock 2.3.6 rooted and CM11. It seems that the stock ROM won't boot after flashing the new bootstrap, but the recovery works fine
Also your version has a very bad bug: it flashes Defy bootstrap even on Bravo!!! It should flash Motorola Bravo specific bootstrap instead. My version only works for Motorola Defy and Defy+ at the moment, but you can edit the source code.
Click to expand...
Click to collapse
Greetings guys, I'm a user from the Atrix 2 section and a part of the current device supporters there. It's a pleasure to finally post here, 'the domain of Quarx' haha.
I was wondering if this recovery is able to flash and boot android Lollipop 5.0 roms yet? If so, then is there some way to port it from source to my or other similar Moto devices in the OMAP bracket with locked bootloaders?
I'm an Android novice, but I'm experienced in building custom recoveries and roms, as well as beginner git commands, so no need to hold anything back, lol. I appreciate the work you're all doing here, please continue to make the difference. Thanks for reading this and take care!

answer
Aceofzeroz said:
Greetings guys, I'm a user from the Atrix 2 section and a part of the current device supporters there. It's a pleasure to finally post here, 'the domain of Quarx' haha.
I was wondering if this recovery is able to flash and boot android Lollipop 5.0 roms yet? If so, then is there some way to port it from source to my or other similar Moto devices in the OMAP bracket with locked bootloaders?
I'm an Android novice, but I'm experienced in building custom recoveries and roms, as well as beginner git commands, so no need to hold anything back, lol. I appreciate the work you're all doing here, please continue to make the difference. Thanks for reading this and take care!
Click to expand...
Click to collapse
Hi!
flash and boot android Lollipop 5.0 roms - just can not say, but it is theoretically possible (need to check).
If so, then is there some way to port it from source to my or other similar Moto device - No, this is not possible (specifically, in this case). BUT this method you can set recovery to another smartphone (it is theoretically, need to try)
Here recovery that are in the public domain, I think that they can install Lollipop 5.0 roms - TWRP2 \ Safestrap
Moto devices in the OMAP bracket with locked bootloaders? - Most likely will not work, but no one stops to try

Octanium91 said:
Hi!
flash and boot android Lollipop 5.0 roms - just can not say, but it is theoretically possible (need to check).
If so, then is there some way to port it from source to my or other similar Moto device - No, this is not possible (specifically, in this case). BUT this method you can set recovery to another smartphone (it is theoretically, need to try)
Here recovery that are in the public domain, I think that they can install Lollipop 5.0 roms - TWRP2 \ Safestrap
Moto devices in the OMAP bracket with locked bootloaders? - Most likely will not work, but no one stops to try
Click to expand...
Click to collapse
Many thanks for the prompt and well ordered reply! I'll look into your suggestions and I'm aware that there aren't many available recovery software for our locked bootloader phones.
We were actually trying to get Safestrap working on our device since last month, but it's failing to work correctly in booting our kexec roms. So I thought I'd ask here since the Defy works by using the 2nd boot like us, but it's still under investigation. Thanks again for your assistance, we're not out of the game yet and we'll get things rolling eventually. Take care!:thumbup:
Sent from the Ace's MB865 using Tapatalk

Error. More than one device and emulator
what am i doing wrong?

LoeWn said:
Error. More than one device and emulator
what am i doing wrong?
Click to expand...
Click to collapse
Perhaps you have not enabled USB debugging
Requirements for smartphone:
Enable USB debugging
Superuser (ROOT)
Free space on the memory card of 100 megabytes

I did enable usb debugging

LoeWn said:
I did enable usb debugging
Click to expand...
Click to collapse
You can send us a screenshot?

I had a successful installation of a december build and twrp 2,6x installed, everything ran just fine. But when the CM tells me there is a update and i download it does not install from recovery, get errormsg. Also apps like rom manager pro tells my phone is not compatible with any updates, and that i should install CWM recovery. So is it possible to install a real CWM on a defy mb526?

Hi, I flashed Recovery BootStrap v4 on the Defy MB525, but its not working. After flash and reboot, phone starts booting, but it ends up with the following screen.
Doesn't matter if I choose Recovery or continue. I can press the menu button (to choose recovery) and nothing happen, till the 3rd press. Than display goes black and thats all .
Any idea where could be the problem or what I'm doing wrong?
Edit: maybe its related to the bootloader version, which is 09.10

Haldy said:
Hi, I flashed Recovery BootStrap v4 on the Defy MB525, but its not working. After flash and reboot, phone starts booting, but it ends up with the following screen.
Doesn't matter if I choose Recovery or continue. I can press the menu button (to choose recovery) and nothing happen, till the 3rd press. Than display goes black and thats all .
Any idea where could be the problem or what I'm doing wrong?
Edit: maybe its related to the bootloader version, which is 09.10
Click to expand...
Click to collapse
Based on first screenshots, Recovery installed. Now you need to install system.
Than display goes black and thats all - maybe have to wait

marcooleo said:
I had a successful installation of a december build and twrp 2,6x installed, everything ran just fine. But when the CM tells me there is a update and i download it does not install from recovery, get errormsg. Also apps like rom manager pro tells my phone is not compatible with any updates, and that i should install CWM recovery. So is it possible to install a real CWM on a defy mb526?
Click to expand...
Click to collapse
In principle it is possible, but it does not make sense.

[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