Clockwork Recovery 3.0.0.8 - eLocity A7

---

Ok guys, here's the conversation I just had with koush:

[23:14] <Elementix> hey man, you there?
[23:14] <Elementix> i don't use twitter
[23:19] <koush> yea i dont know how to get a hold of you
[23:19] <koush> long story short i made a zip file that you can flash
[23:19] <koush> that starts up clockwork recovery
[23:19] <koush> but i have no idea how to initiate recovery mode via rom manager
[23:19] <Elementix> hmm..
[23:19] <koush> so there is a recovery
[23:19] <koush> but its annoynig to get into
[23:20] <Elementix> so it works, but not?
[23:20] <koush> you start the stock recovery, then you apply update.zip
[23:20] <koush> and it starts clockwork
[23:20] <koush> it works, in a fashion
[23:20] <Elementix> but you have to do it each time?
[23:20] <koush> yeah
[23:20] <Elementix> interesting..
[23:20] <koush> i dont wanna risk flashing a recovery
[23:20] <koush> without knowing how to actually fastboot it
[23:20] <Elementix> i hear ya..
[23:20] <koush> in case something goes wrong
[23:21] <Elementix> ok, well let me do a little research I suppose..
[23:21] <koush> ask around in the community and yeah
[23:21] <koush> if you know of another boot mode
[23:21] <koush> like fastboot
[23:21] <koush> let me know...
[23:22] <koush> or if you know how to flash a recovery.img from within android
[23:22] <koush> either of those
[23:22] <koush> and let me know if you want this thing back
[23:22] <Elementix> kk
[23:22] <Elementix> not yet
[23:22] <koush> btw the zip
[23:22] <koush> is available for testing
[23:22] <koush> its already on my site
[23:22] <koush> http://www.koushikdutta.com/2010/02/...ery-image.html
[23:23] <koush> there's probably some kinks
[23:23] <koush> but recovery starts up
[23:23] <koush> and you can do ****
[23:23] <Elementix> ok cool
[23:23] <Elementix> thanks

so....that's whatsup with it so far. If anyone knows ANYTHING about the information he's asking for please get it to him or post it here while he still has my eLocity.

Again, the link for what he has right now is: http://www.koushikdutta.com/2010/02/...ery-image.html

IDK what knowledge (in case of eLocity A7) have Koush, but i'm trying to allocate all info about hard-flashing process here.

------------------------------------------------------------------------

1. Recovery

eLocity A7 has Android System Recovery <1e>. According info from official update: recovery.img will flash to partition named "SOS"
To get into recovery you should:
- turn Tablet off
- quickly turn on and release power-button (notice green light)
- press power again and hold till text "Booting recovery kernel image"
- if you hold longer your Tablet will turn off)

2. ADB (Android Debug Bridge)

2.1 Cable
Ensure you have USB Cable A-A like in attached image
http://forum.xda-developers.com/atta...1&d=1298973504

2.2 Drivers
Ensure you have Android SDK Tools. If you have SDK Tools already you could start from section "Modifying drivers"

2.2.1 Installing SDK Tools
- Download it from http://developer.android.com/sdk/index.html
- Unpack it to <sdk_folder> (avoid long-names and desktop-folders; good folder: c:\asdk)
- Run "sdk manager.exe"
- From "Android repository" download "Android SDK Platform-tools"
- From "Third-party Add-ons / Google Inc. add-ons" download "Google USB Driver package"
- Exit from SDK Manager

2.2.2 Modifying drivers
- Go to <sdk_folder>/google-usb_driver
- Find android_winusb.inf and edit it
- Add following to both sections [Google.NTx86] and [Google.NTamd64]

;NVIDIA Tegra
%SingleAdbInterface% = USB_Install, USB\VID_0955&PID_7000
%CompositeAdbInterface% = USB_Install, USB\VID_0955&PID_7100&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_0955&PID_7100

- Save and exit
- Run Windows command-promt and type

echo 0x955 >> "%USERPROFILE%\.android\adb_usb.ini"

2.3 Switch modes
eLocity A7 has USB-Host "out-of-box", but it can be converted to simple USB

- Ensure you have Root Explorer
- Run it and go to /data/data
- Create folder name com.compal.usb_otg
- Go into and make file usb.txt
- In usb.txt write 0
- Connect tablet to PC with USB Cable A-A
- Reboot (tablet can switch modes only while rebooting)

Note:
0 - USB Slave mode
1 - USB Host mode

2.4 Checking ADB
- If you done steps above correctly Windows would search adb-drivers. Point them at <sdk_folder>/google-usb_driver
- Check connection by running adb from <sdk_folder>/platform-tools

adb devices

If it returned serial number you have success

3. APX mode

3.1 Getting Nvidia Tools
- Go to http://developer.nvidia.com/tegra/devkit-250tango and download "Android 2.2 (Froyo) for Tegra 250 & Tango ONLY" (one or both Windows/ Linux)
Speedlinks (NVidia updated tools 7 feb 2011, so links would change in future)
Windows: http://developer.download.nvidia.com...o_20110207.msi
Linux: http://developer.download.nvidia.com...0110207.run.gz
- [WIN] Install it in <nvidia_tools_folder> (default it is there C:\Program Files\NVIDIA Corporation\tegra_froyo_20110207)

3.2 Running into APX
- Connect to PC (remember: in USB Slave mode and with Cable A-A)
- Run following command in terminal emulator

echo 1 >/proc/naz10_diag/force_recovery

- Tablet should reboot into APX
- If you've connected properly Windows should search another drivers
- Point them to <nvidia_tools_folder>/usbpcdriver

3.3 Getting partitions
- Go to <nvidia_tools_folder>
- Run nvflash-command to get into bootloader. I used stock bootloader from elocity official update. I didn't use bootloader from <nvidia_tools_folder>.

nvflash --bl bootloader.bin --go

- Tablet should write something at screen (recovery mode bla-bla)
- Run nvflash-command to get list of partitions

nvflash -r --getpartitiontable partitiontable.txt

- I have last official update and in partitiontable.txt "SOS"-partition has number 6
- Run nvflash-command to get specified X partition

nvflash -r --read X part-X.img

I successfully got partition number 6 and it is about 8 MB
I got partition "APP" (with number 9) and it is about 500 Mb - i think our system image can be extended
nvflash has command "--download N filename". It downloads partition filename to N. But i'm afraid to experiments, cause don't have warranty
------------------------------------------------------------------------

Things to investigate

- Running into APX-mode with hardware-buttons. I don't know how it can be. Viewsonic GTablet owners have to press VolumeDown and Power to get into. But our Tablet doesn't have VolumeDown. I tried Volume already but it seems that this button starts working after system was loaded.
Without this method we have only two methods to restore:
1) If tablet is booting properly -> nvflash
2) If tablet won't boot -> recovery

- Custom recovery. It would be great if Koush will realize it. Last step left)
------------------------------------------------------------------------
Thanks to
- greenar
- Dexter_nlb
- nicofs (he added info about nvflash to toshiba ac100 wiki)

wow 5[Strogino], really good write up.

Do you know anything about fastbooting the tablet though?? Thanks for all that info btw.

Sent from my Droid using XDA App

Originally Posted by Elementix

Do you know anything about fastbooting the tablet though?? Thanks for all that info btw.

Sent from my Droid using XDA App

What did you mean? I think Koush knows about it according my post
I will check fastboot in APX mode soon...

No, here's what koush had to say about it:

[23:20] <koush> i dont wanna risk flashing a recovery
[23:20] <koush> without knowing how to actually fastboot it

OMG... clockwork on this thing would be beast...

Thanks Elementix for getting the ball rolling on this one!

thanks for the writeup.
Can someone please try this recovery?
http://mirror1.kanged.net/recoveries...3.0.0.8-a7.img

I need to run to work, and don't want to mess with flashing/breaking this thing at the moment

Should be able to restore a broken recovery jsut fine through nvflash from what I'm reading.

Koush

I installed it from Rom manager, however, it still boots into stock recovery. Tried booting into recovery from Rom manager and from key combo with no luck. Looks like it rewrites stock recovery.

Damn, it was very scary................
Uploading images

Successfully flashed via nvflash

But notice...
Home and Menu buttons are same. They switch between background and menu
Search, Back and Volume do not work

Original buttons have following functions:
Search - Up
Back - Down
Home - Switch between menu and background
Menu - Enter

And got 3 errors:
Can't mount /cache/recovery/command
Can't mount /cache/recovery/log
Can't open /cache/recovery/log

Update 1
Took bootloader from nvidia_tools (not flashed; just executed nvflash --bl bootloader.bin --go)
Device won't boot into APX mode. Did not affect to other things. Rebooted into system, run commands to get into APX mode with eLocity bootloader. Success.

Update 2
Took recovery.img from nvidia_tools. Tried to flash in partition 6 (SOS).
Device won't boot into recovery. Did not affect to other things
Rebooted into system. Run commands to get into APX mode with eLocity bootloader. Success.

Update 3
Took recovery.img from eLocity official update. Successfully flashed and went into it.
Everything seems work.