MoDaCo Custom r6 discussion archive

[Guest Dayzee]

need bit of help... updated everything - it went perfectly... i hit the recovery addon icon by accident now it wont boot! I know it is something silly... any help much appriciated

And another - that app is dangerous!! See my post above, Alfe, and best of luck..

[Guest macray76]

Just bought the ad-free - thanks Paul for the hard work.

I've installed (via linux) r6 with performance pack over a fresh install of the latest stock firmware and when it boots up there is a Sorry! message saying Process system is not responding.

I've tried it twice now and it has occurred both times.

Help please!

[Guest macray76]

Just bought the ad-free - thanks Paul for the hard work.

I've installed (via linux) r6 with performance pack over a fresh install of the latest stock firmware and when it boots up there is a Sorry! message saying Process system is not responding.

I've tried it twice now and it has occurred both times.

Help please!

Just installed the r6 pre-back (small notification) over the top and it now boots into home fine.

Anyone else having this issue?

[Guest fracmo2000]

Anybody else not getting their R6 vega's screen to rotate? I have tried Launcher Pro, Web Browser and other apps...all the same :(

[Guest Clark80]

Installed on via MacBook Pro - All is well. Thanks Paul

[Guest gadget_tech]

This happened to me - The solution is an absolute pain in the arse..... http://android.modaco.com/index.php?s=&amp...t&p=1534759

Seriously Paul, the Clockworkmod install and associated Recovery boot app isn't going well for LOTS of people. Really hope you will still provide the updates for this via the adb method. Or if not, is there a way to run the Clockworkmod update.zips via adb and not recovery? I really really don't want to touch Clockworkmod again, nearly had a heart attack last time..... If r7 is only available via Clockworkmod, then I might be stuck there and will sell the Vega, becauseI don't feel clockworkmod isn't safe for me and I'm worried to use it. I'm more inclined to mess with drivers for ADB than I am to put a not fully working recovery on my vega, because that has potential to brick it... In fact once you get the drivers running, the adb method is VERY successful and safe.

Just my two penneth....

Wobblydoggy - read my post above - the exact same thing happened to me after accidentally clicking paul's recovery app. :(

I second this.

Had two close calls with the Clockworkmod now which wasn’t fun. Installed Clockwork and first few reboots were fine and then nothing but a completely blank screen.

[Guest thedicemaster]

Anybody else not getting their R6 vega's screen to rotate? I have tried Launcher Pro, Web Browser and other apps...all the same :(

checked the switch between the back and power buttons?

[Guest fracmo2000]

checked the switch between the back and power buttons?

yeah, tried that...nothing. was working with stock rom...but with r6 nope!

also, when i updated to pauls r6, it left apps which were already installed on my vega...is this normal (i checked about device and it is indeed pauls r6)

anybody else getting a rotation problem?

[Guest fracmo2000]

Also to Paul:

I was having some problems getting your rom to install, turns out i had to do this part which isnt included in post 1 : installation:

06. Boot to recovery mode by following the next procedure exactly:

* Press and hold the 'back' button on top of the device.

* After 1 second push and hold the 'power' button too. Don't release the back button yet!

* After 1 more second release the 'power' button, while holding the back button.

* After yet another second, release the 'back' button too.

* If you've done this correctly, the PC will play a 'device connected' sound.

07. On the PC go to 'Device manager', right click the "APX" device without drivers and choose to update the device driver

08. Browse the PC for the unzipped drivers and ignore all warnings about driver verification (Install anyway)

09. Done correctly it will show the "NVIDIA USB Boot-recovery driver for mobile devices"

I already had the most upto date rom (1.0.6 i think)...so unplugged my vega which was then stuck in recovery mode. To fix this, just unplugged usb and plugged it back in. I then noticed APX in device manager...this wasnt there before (but everything else was). Im sure this was the missing step which fixed it for me...not sure if you know what I mean but it could help new members!

Thanks for the great work Paul, my sisters bf's vega is now looking like a proper tablet!

[Guest wicca128]

checked the switch between the back and power buttons?

Oh my god i feel like a twonk..... haha i had the same problem... all fixed now thanks

[Guest arad85]

I second this.

Had two close calls with the Clockworkmod now which wasn’t fun. Installed Clockwork and first few reboots were fine and then nothing but a completely blank screen.

Paul,

I third this. You can't move to clockwork for R7 until it is a stable platform to build from. I have no problem with a full ROM as long as I'm sure it'll boot 100% reliably.

[Guest fracmo2000]

Thanks paul all works well.... but my screen will no longer rotate

It no longer works for me either, sounds bad...but at leasst its not just me :(

No such problems for me, loving the 3D mapping.

Follow Pauls advice and uninstall from the Vega and reinstall from the APK.

Did you reinstall too? Mine works, but its jerky

[Guest Dayzee]

All updated, my screen rotating fine, but I'm using LauncherPro. I did my update over adb, including running install-windows.bat - Not sure if that would make any difference. In my case I did it because I always want to do adb-windows devices to check I'm good to go before I start so since I'm in a command window, seems easier than closing it and double clicking the .bat file.

Dayz

[Guest alfe]

Must say so far I'm not liking r6. Seems quite sluggish, something not right... hopefully just teething problems!

[Guest tylordurton]

Ok ... so nothing is working for me since the bad r6 was released and gave me a black screen!

I am unable to revert to the .065 vega build as I receive an error saying the "USB device not found"

I am unable to reflash to the new r6 as I only get as far as the following command

"Remounting system partition

remount succeeded

1296 KB/s (4544329 bytes in 3.422s)

pkg: /data/local/tmp/libflashplayer_froyo_gles2_20101206_v10.1.120.1_sig

ned.apk"

then nothing happens

Trying to run the following code from Paul's post

"adb remount && adb shell ln -s /sbin/busybox /system/bin/busybox && adb shell chmod 0755 /system/bin/* && adb shell chmod 4755 /system/xbin/su && adb reboot"

returns the follwoing error in windowc cmd

"'adb' is not recognized as an internal or external command, operable program or batch file."

Please guys - what steps do I need to take to get me Vega back up and running!!!!

[Guest griff_dai]

Paul,

I third this. You can't move to clockwork for R7 until it is a stable platform to build from. I have no problem with a full ROM as long as I'm sure it'll boot 100% reliably.

after sorting out my install problems, have to say that r6 has the Vega zipping along nicely...... However I fear being left behind as I do not know if I feel confident enough to do the r7 install if it means fooking around with clockwork, especially as so may are having problems.......

so I also add my concern....

r6 is so far, very good indeed :(

[Guest remlap]

We have really no idea when r7 will appear, Paul could have it down to a very easy reliable process before he releases it :(

[Guest arad85]

We have really no idea when r7 will appear, Paul could have it down to a very easy reliable process before he releases it :(

In which case I have no problems ;)

What worries me is that the problem hasn't been acknowledged (even though Paul has asked and been pointed at the problem) nor is it clear it is being worked on/has been reproduced/has been fixed. Moving to something as a main development method that seems to have been shown to have problems really is a little too bleeding edge (BTW I manage the development of complex embedded software as my day job and I would be treating the clockwork mod as my highest priority bug right now ;))

[Guest fracmo2000]

Two questions:

1) When you flash a rom (like r6) should all your previous apps etc still be there?

2) Is the rotation issue not wide spread and just reflash?

Or is r7 round the corner?

[Guest woodski]

Two questions:

1) When you flash a rom (like r6) should all your previous apps etc still be there?

2) Is the rotation issue not wide spread and just reflash?

Or is r7 round the corner?

[Guest woodski]

hi can any one help put mod on yesterday rebooted ok but has came up with sorry processs syterm is not responding cant force close i can power off but it reboots to same fault how can i put it into recovery mode or have i just made a brick

[Guest nickjinks]

Alfie - have you looked into this? - might not be your problem but it helped me back in the day:

Right I've managed to fix my problem. I think a generic usb mass storage driver must have installed itself on my system which clearly wasn't right. Not sure if this is the same that other people are experiencing.

Symptom : WinXP SP3 : when vega is connected, even with usb debugging enabled, it is only recognised by XP as a mass storage controller i.e. no Android phone section in device manager.

Fix :

1. Unzip the drivers that are included in Paul's mod pack e.g. in r3 pack there is a zip file called r1-tegrausbdrivers-modaco.zip in the usbdrivers directory. Unzip that file and remember the path to it.

2. Connect the Vega to your machine and enable USB debugging mode on the Vega.

3. On the XP machine go to device manager and uninstall (select, right click, select "Uninstall") the following devices :

- Disk Drives : Nvidia Tegra 2 USB Device

- Universal Serial Bus Controllers : USB Mass Storage Device

4. Then go right to the top of device manager and select the icon that represents your XP machine, this will have the computer name of your machine. Right click on it and select "Scan for hardware changes".

5. This will now redetect the Vega and allow you to install new drivers. When it prompts you to do this ensure you do not let it automatically detect them, instead make sure you point to the directory you have unzipped pauls drivers as in step 1 above.

6. Once the driver is installed you will now have the following in device manager :

- Android Phone : Android Composite ADB Device

- Disk Drives : Nvidia Tegra 2 USB Device

- Universal Serial Bus Controllers : USB Composite Device

- Universal Serial Bus Controllers : USB Mass Storage Device

You can then install Paul's mod.

Cheers

Rob

can someone help please just downloaded version 1.06.5 from the advent site and got that working on my advent venga however now just downloaded the kitchen r5 after paying a tenner on the advice of others however when following the directions me being a complete virgin at this kinda thing

If you are using Windows, your USB 'Android Developer Bridge' driver MUST be the one included in this download (use 'Have Disk' functionality in device manager to change if required)

when i look for this usb drive on my device manager i only find

Nvidia android composite device and that appears to be upto date with the version im trying to update to top it off when i install the driver as directed

# Download the zip file of your choice from the links below (or the online kitchen) and extract on your Windows PC, Linux PC or Mac

# Connect your device to your PC

# At a command prompt / terminal, ensure you are in the directory you extracted the files, and run 'install-windows.bat', './install-linux.sh' or './install-mac.sh' as appropriate

# Wait for your device to reboot! smile.gif

whe i run install-windows.bat it just stay black and nothing comes up however the last time i did it it came up saying it was running but stays like that forever and the tablet doesnt seem to respond could anyone please help as at the moment its like a doorstop and no use to me lol

Many thanks

Afie

[Guest gdwhitehouse]

OK, dumb questions time...

1. I have the full r5 working sweet as you like, does the upgrade to r6 leave all my apps etc intact?

2. Do I need to 'bake' everything again in the kitchen (as I did the first time) and just redo the process?

3. What would I actually 'need' the recovery boot app for - I have seen it causing a few complications for people, should I just not add it?

Thanks in advance guys

G

[Guest woodski]

how can i restore still saying prosser systermis not responding

[Guest woodski]

how can i restore still saying prosser systermis not responding

Help has any body got any ideas