Stuck in USB-host with stock 1.06.5 and no SU

[Guest mutasim]

Yay! USB host now works on my Vega ;)! playing some files from my external usb now :) wonder if i could get a 3G dongle to work?...

USB Host on Vega

EDIT:

If anyone wants to try for themselves, download this file and extract it somewhere, put your Vega into recovery mode and run Update.bat and let nvflash flash the new update including the new kernel and boot.img to your Vega. AT YOUR OWN RISK. This is the stock 1.06.5 update but with usb host enabled in the kernel.

Just to let you know before flashing or kernels, barely got this boot.img to extract... I just wanted to play some files from my USB and couldn't wait til tomorrow for Paul to do it better than me... but it works :D

EDIT 2:

Okay, can't install Paul's R5 pack now because its no longer USB slave... hmm..

I got to this stage and Host works, then I installed Gscript, but I can't run either script.. I get the following error message:

stderr: su: uid 10123 not allowed to su

I cannot connect it to my PC and use adb because its stuck in Host, I tried the adbWireless app, but that needs su, tried unticking "Needs su" on the script, then I get this message:

stderr: /data/local/flash_image: not found

Any ideas?

[Guest r8zer]

I got to this stage and Host works, then I installed Gscript, but I can't run either script.. I get the following error message:

stderr: su: uid 10123 not allowed to su

I cannot connect it to my PC and use adb because its stuck in Host, I tried the adbWireless app, but that needs su, tried unticking "Needs su" on the script, then I get this message:

stderr: /data/local/flash_image: not found

Any ideas?

if you have flash from pauls clockwork u can still get into recovery as slave.

[Guest mutasim]

if you have flash from pauls clockwork u can still get into recovery as slave.

I'm running stock 1.06.5 and I checked /data/local/ and it's empty

[Guest JingleManSweep]

I'm running stock 1.06.5 and I checked /data/local/ and it's empty

Can't you reflash official firmware in official recovery mode, before android even loads and configures as host. Start over.

[Guest mutasim]

Can't you reflash official firmware in official recovery mode, before android even loads and configures as host. Start over.

Nice one.. seems to be flashing the official firmware :)

[Guest JingleManSweep]

Nice one.. seems to be flashing the official firmware :)

Yeh, the underlying NVidia recovery layer (pre-Android) will prove quite handy for unbricking "bricked" devices.

Edited December 17, 2010 by JingleManSweep

[Guest T4ylor]

Can't you reflash official firmware in official recovery mode, before android even loads and configures as host. Start over.

Can I just clarify something that’s been confusing me and at the moment preventing me a enabling the USB host.

If I was to enable the USB as host and at some point everything when drastically wrong could I still re flash to stock from the device being switched off and doing the whole button sequence thing because in theory the USB is slave until powered up which then transfers it to host?

I know people talk about the whole Clockwork recovery but to be honest I cannot get my head round it at all hence the caution.

Thanks

[Guest JingleManSweep]

As far as I understand it:

The Vega has two bottom level systems, the main one (Android) and a recovery state which, I think, is part of the nvidia tegra chipset/baseboard.

This alternative "recovery" system actually exposes a different hardware ID than the main system. This causes Device Manager in Windows to refresh and a different device appear in your device list.

I think this recovery mode offers direct access to the filesystem on the device. For example, it can partition, format, read and write to all parts of the internal storage. As such, I think normal Android hacking disasters can be recovered from by repartitioning, reimaging and installing the software.

Not sure though.

[Guest warriorscot]

As far as I understand it:

The Vega has two bottom level systems, the main one (Android) and a recovery state which, I think, is part of the nvidia tegra chipset/baseboard.

This alternative "recovery" system actually exposes a different hardware ID than the main system. This causes Device Manager in Windows to refresh and a different device appear in your device list.

I think this recovery mode offers direct access to the filesystem on the device. For example, it can partition, format, read and write to all parts of the internal storage. As such, I think normal Android hacking disasters can be recovered from by repartitioning, reimaging and installing the software.

Not sure though.

Thats also how I understand it to work. Best comparison I can think of is on a PC where you press delete or tab to access the motherboards built in menus and features like BIOS and POST etc. the OS itself hasn't booted yet so its not a factor and you can make changes. In order to actually brick a vega in the true sense of the term you would have to alter the files loaded for recovery preventing you to access it even with the correct sequence of button presses. You can't really brick the vega with a custom rom because its the android OS they are making changes to not the boot files for the vega so if you mess up a ROM all you need to do to fix it is reflash back to stock from recovery.