Jump to content

Did I kill it already?


Recommended Posts

Guest Dyonas
Posted (edited)

OK after some problems getting the USB driver to show up and having to use USBDeview to install it I finally got up to the batch file. Unfortunately after running it I'm now stuck sitting at the Android logo with nothing happening. I looked at the batch file log and my heart sank when I saw this at the end...

push: files/system/bin/keystore -> /system/bin/keystore

push: files/system/bin/iptables -> /system/bin/iptables

push: files/system/bin/installd -> /system/bin/installd

failed to copy 'files/system/bin/installd' to '/system/bin/installd': No space left on device

Creating Symlinks...

Setting permissions...

Windows flashing fix phase 2...

		1 file(s) moved.

cp: write error: No space left on device

Flashing boot image...

- exec '/system/bin/sh' failed: Exec format error (8) -
No space left? I hadn't installed anything aside from the backlight killer app hosted here. As it stands I'm about to cry, please tell me I haven't just killed my device within a few hours of getting it. I've turned it off and on again, still stuck at the Android logo and adb logcat just shows this...
- exec '/system/bin/sh' failed: Exec format error (8) -

Edited by Dyonas
Guest gavinlew
Posted

Download the Advent firmware from www.myadventvega.co.uk, flash that and try again? , You should still be able to enter the bootloader mode with a key combination when you power the unit on.

It is nearly (if not) impossible to brick the unit.

Guest Dyonas
Posted (edited)
Download the Advent firmware from www.myadventvega.co.uk, flash that and try again? , You should still be able to enter the bootloader mode with a key combination when you power the unit on.

It is nearly (if not) impossible to brick the unit.

I realised this just after I posted but thanks for the information. Phew! I'm used to messing around with flashing images and messing with ADB, recovery (clockwork or otherwise) but with a new device panic took over before anything else. Thanks though, the fast reply is always good to see! With regards to the error, is that a new thing with the Vega? I'm going to try again but if it fails this time I'll wait and see what replies I get to the error message.

Edit to note that it failed at the same point again. I'm surprised to see it when the file has been up for so long.

Edited by Dyonas
Guest gavinlew
Posted

What OS are you flashing from?

Have you verified the file is OK (MD5 sum)?

I flashed my Vega from Ubuntu (as I dont trust Windows :huh:

Guest Dyonas
Posted
What OS are you flashing from?

Have you verified the file is OK (MD5 sum)?

I flashed my Vega from Ubuntu (as I dont trust Windows :huh:

Windows Server 2008 R2 (yes it's a legit version :) )

MD5 matches, I just checked it again there to be sure.

Guest Dyonas
Posted

OK this is a bit confusing and also potentially a bad sign. I tried to manually push files, enough to get me Market access at least, and just doing that from a stock 1.09 image I kept running into the same error about running out of space. I really hope I'm wrong on this but to confirm that I need to know if there's a way to find out how much room is being used by the ROM and / or show space left. I don't mean space to install apps, I have a few hundreds MBs still on the internal storage, I mean space that the ROM has to fit into. I don't want to find out that my Vega has less than earlier models but if I do then I'm going to be pretty upset.

Out of all the MoDaCo R8 files these are the only files I pushed, all apks in an attempt to get the Market working.

GoogleServicesFramework.apk

GooglePartnerSetup.apk

GoogleFeedback.apk

GoogleContactsSyncAdapter.apk

GoogleCalendarSyncAdapter.apk

GoogleBackupTransport.apk

Drm.Provider.apk

CheckinProvider.apk

CertInstaller.apk

PackageInstaller.apk

DrmProvider.apk

Street.apk

Maps.apk

Talk.apk

NetworkLocation.apk

MarketUpdater.apk

Vending.apk

I had to remove a few things as I went so this may not be a full list but it's close enough. There wasn't even room for Link2SD.apk when I was done. No wonder I ran into the problem I first posted about, for some reason my device is missing a big chunk of storage.

Guest Dyonas
Posted

OK last reply to my own thread but it might help others if they run into the same issues. I used Vega Tools from here to quickly and easily install Paul's Clockworkmod Recovery image then flashed the MoDaCo r8 zip file from there, no problems and fully up and running now. I was a bit unsure of flashing a different recovery in case it breaks the ability to restore it to factory with the official PC World flashing software but on the Vega Tools menu it seems to hint, to me, that basically running the exe with the firmware on wipes everything, including the recovery image, and restores it to factory default.

Anyway, I'm done for now until someone hopefully manages to port Honeycomb for the Vega. The tools around this forum alone are really good considering how small the Vega community must be compared to phones and the iPad. I'm so glad I stuck with it and kept trying even if I had a few scares while getting there!

Guest simonta
Posted

One thing that confues Vega noobs is that it has 2 recoveries. There is the one we all know and love like Clockwork or the Vega software tool and there's the one you get into via back, power, back etc. The first is self contained and can only be reached (currently) via reboot into recovery. The other, which thank the stars makes the Vega unbrickable, is a firmware (or maybe even hardware) NVidia APX device which provides connectivity via the NVidia Harmony Recovery driver for NVFlash.

The lingo round these parts tends to refer to the latter as recovery and the former as Clockwork or simply CWM.

Clear as mud eh?

Hope it helps...

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.