[Q] V1.11 Firmware - Vega General

Hi all
I have just got my Vega and I have been attempting to master the nvflash technique but with no success.
Everytime I attempt it the screen lights, the android appears and then the unit goes off and there is no indication of any connection between my PC and the Vega.
Anyway I was checking my firmware version and it appears to be V1.11
2.6.32.9_P10_V1.11_20110627_DIX
Has anyone get any experience of this firmware as I cannot seem to find it mentioned anywhere and I am wondering if Dixons have locked the nvflash?
Thanks for you help ahead of time
Oh I think I should mention I have managed to install Clockworkmod V3.0.24 but not yet rooted the device and I was wanting to install modeed stock v2
Thanks again

Oops this doesn't look good, I know this thing is supposed to unbrickable and I do have a nandroid copy of the firmware on the SD card
But I have just shut the unit down to reboot it and it will not come on now.
All that happens is the screen lights up and nothing else.
I have tried shutting it back down and booting again, I have tried the nvflash sequence again but nothing, just a backlit screen and nothing else.
Also whilst the power is plugged in the unit will not even attempt to come on when trying nvflash, I should have mentioned that before as that has always been the case.
All I have done today is install the getjar app, facebook, angry birds and moved the Clean & Stable Add-On For All Stock Firmware V4 mod to the software update folder but not actually flashed it.
I have even taken the SD card out and tried booting up but still the same result.
Any ideas anyone please?

OK that seems nuts but the thing has finally gone into recovery mode just as I had all but given up, I have now updated it with modded stock v2 and vegacomb and just waiting to see if it is now sorted.
It came on and went through all the vegacomb animations but now it appears to be a blank backlit screen again

put original stock firmware back on it, you may fine only v 1.10 on the internet, so give that a try.

Thanks for the reply mate
I have managed to do exactly what you suggested and nvflashed the original Vega1.10 and have since updated with modded stock V2 and then updated to Vegacomb and all seems great except for the odd crash but they are fairly far and between

Related

[Q] eLocity just quit...won't boot up

I have been running my a7 with dexter's mod 1.4 for about 1 1/2 weeks...everything has gone well. This afternoon I turned on the device and it failed to complete boot. The word Android would come up and then nothing. I tried to reboot, reset, but device would do neither...nor would it turn off completely. I kept trying to take it into recovery mode and then after several tries was able to wipe, do update again, and get everything back as before. What would cause this and should I look for this to happen again? deepmagic
My a7 was running well for about a week since it quit...but today when I booted up device, it failed to recognize sd card...same card used for updating to mod 1.4...same card I've been using to listen to my music, etc...but now won't recognize...I've tried two different micro sdhc cards..formatted, reformatted, but device continues to display mount sd card...all else works fine! Does anyone have any new ideas? I can't even reinstall mod since a7 can't read my cards. Thanks for any input that would be helpful. I understand these issues are ongoing for many out there...what to do?
deepmagic said:
I have been running my a7 with dexter's mod 1.4 for about 1 1/2 weeks...everything has gone well. This afternoon I turned on the device and it failed to complete boot. The word Android would come up and then nothing. I tried to reboot, reset, but device would do neither...nor would it turn off completely. I kept trying to take it into recovery mode and then after several tries was able to wipe, do update again, and get everything back as before. What would cause this and should I look for this to happen again? deepmagic
Click to expand...
Click to collapse
Mine has hung on a black screen on me. Seemed that it didn't fully come out of sleep mode.
I was able to recover by holding the power button for 15 seconds to hard power down. No data loss.
deepmagic said:
I have been running my a7 with dexter's mod 1.4 for about 1 1/2 weeks...everything has gone well. This afternoon I turned on the device and it failed to complete boot. The word Android would come up and then nothing. I tried to reboot, reset, but device would do neither...nor would it turn off completely. I kept trying to take it into recovery mode and then after several tries was able to wipe, do update again, and get everything back as before. What would cause this and should I look for this to happen again? deepmagic
Click to expand...
Click to collapse
Exact same thing happened to me this morning. Tried to reset - not happening. Hard powered down. Don't have time to try anything else right now. I'm new to the forums and new to android. Wish me luck! I've been loving my A7, and much appreciation to Dexter and all the other knowledgeable hackers/modders/posters.
hey the same thing happened 2 me twice. Once the first day after i got it, since i had only had it for 1 day i wiped it reinstalled dexter's mod 1.41 and it worked. First app i installed was backup root. Now, a week later the exact same thing is happening. This time i dont want to wipe it because of all of the apps i have installed, games ive played etc. Any ideas? Could we just try reinstalling dexter's md without wiping? Or wiping reinstalling and recover from a backup?
Also have you installed busybox? I had just installed it both times before it failed to turn on. Maybe its just coincidence but you never know..
-D
Thanks to anyone who can help! and also thanks Dexter for all your hard work as well as everyone else that has contributed to the elocity, im lovin it! (when it works )
success!!!!
I got it to work! I don't have a permanent fix but if it happens again just boot into recovery and reinstall the dexter's mod update 1.41 and it works again! No wiping required. This isn't a permanent fix but it will work until we find one
-Dylan
Hasn't happened to me (yet) but I didn't upgrade to the newest ROM. I'm still using 1.3and it has been very stable. Only issue I've had was when I tried to use Killswitch to go to sleep mode when the cover is shut (great idea) but it didn't work and froze all except the live wallpaper. Weird.
Good luck, guys.
in the event it does happen to you, you might want to check out my apx thread for reflashing the factory firmware if you can't get your tablet unstuck. theres alternatives if you don't want to get stuck again.
The method you outline seems so complex...way above my abilities, but makes me wish I had followed though on some early programming training opportunities. That was the road not travelled.
okantomi; while i wouldn't encourage others to follow thru with procedures they fear would cause more harm, i would mention that if you google up my nick you'll find i've been able to do much w/ android software and devices while not knowing anything about programming. if i can do it, anyone can. i just wanted some themes for my phone.
i'm just an android hobbyist by night (and when i get a chance during the day), and a computer tech by day. no programming expertise, but i can reasonably reverse engineer and port software and components using simple file managers like ztreewin(trialware).
don't be mistaken that the folks out there providing you solutions necessarily know anything about programming or software development. just how to chef up files at different levels. i understand this doesn't go for everybody.
Thanks for the encouragement. I'm impressed with what you've been able to do. It is also nice to read upbeat comments about the A7. There is something sort of special about a device that you really almost have to build yourself... putting so much into it... biting your fingernails to nubs with each ROM flashing. You don't get as attached to any device that is 100 percent complete right out of the box, though of course there would be a lot less aggravation.

[Q] Problem: Unresponsive screen after update

My wonderful wife gave me an Acer a500 for Christmas. Awesome gift. I had rooted it immediately with no problems, since all of my phones and families phone are rooted, it just seemed to be the natural thing to do.
As someone that "plays" with their android a lot I did all of the backups. Well, the time came to have my tablet "approved" for use at my company and also have the appropriate "encryption" software and keys added. Just as a precaution I decided to restore the original backup and unroot the tab.
All was going well until I received the update message. I went ahead and downloaded the update and ran it. During the install process it froze. I thought it was just busy so I left it for a good 20 minutes and finally realized it was frozen. I rebooted and it went through a couple of reboots and finally settled on the lock screen. But now I find the touch screen unresponsive.
I plugged in a mouse and keyboard in hopes that I could get back into it and start over, but, although, the mouse shows up, it is jumpy sluggish and will not grab the lock to slide open and eventually freezes.
I have tried all of the "update.zip" files I could find and they all fail at one point or another.
ADB allows me to explore in shell but since I unrooted, I cannot get su privileges.
Acer is of course, useless and the vendor it was purchased from is worthless.
I have been through every thread I could find and tried every trick I could come up with. Now I'm just stuck.
Any help is appreciated
I've had this a couple of times already. Usually just turning the screen off and on a couple of times does the job (the issue seems to be with the driver, also on various custom roms). Just try it after each off-on cycle, most of the time it takes no more than two or three tries, though there are exceptions.
Thanks, but it has been rebooted many many times since it's demise.
Decided to skip sleep tonight and keep plugging away.
I found an update.zip recovery file for an a501. Figured I can't do much worse so I went ahead and ran it.
It froze at about 95% but.........
Good News:
The tablet is responsive and touch panel works again.
Bad News:
It boots straight into system settings and although you can open the settings menu, nothing actually launches.
Decided to try all of the old update.zips and still everything fails.
No more ADB response.
When you originally unrooted your device did you revert back to the stock recovery or did you leave cwm on your device?? If you left cwm on your device that may be the problem with the update.zips and OTAs.
You are sooo right. I've never gone back to a stock rom before and I completely forgot about reverting to the stock recovery.
As a matter of fact, I was on Civato's Flexstriker 3.2.1 rom with the new CWM before I reverted back to the stock rom.
Well, at least we've determined my stupid mistake, but now the question lies: "How do I get back to any working rom?"
Here's an update. I did find an update.zip file that also begins to load but does not finish. It stops at 95% still.
I will attach the photos in case someone notices something otherwise I am at a loss. In addition to all of the above, I tried everything I could to get into APX mode but nothing. I am willing to try almost anything at this point, so all suggestions are appreciated.
Something I noticed was the recovery for the a501 was android with gears spinning in the body. The recovery I have now is a package with an arrow. The recoveries are different. The current update file is Acer_A500_1.145.05_COM_GEN1
So this brings me to a question: Can I put Thor's 1.6 CWM back on the a500 and at least work from there? I do have my original backups and thought I might be able to get somewhere that way.

[Q] A500 hanging, SOD, crashing ..

My A500 hasn't been acting quite right. Since I upgraded a while back to a FLEXREAPER rom from Taboonay (HC) I've had numerous SOD issues, but even more so worse and worse crashing and hanging.
Things I've done:
Full wipe/install of latest FLEXREAPER, Lightspeed, Taboonay (3.1). My A500 would hang even during initial setup (google account, etc). Eventually I'd get through the setup and it would still crash (screen freezes) or SOD. Oddly enough, I can't seem to format my internal sdcard .. but I have wiped everything else several times, and absolutely before installing any of the ROMs.
It would also, many times, not even boot. The white power light would come on, the vibrator would spin, but nothing would happen on the screen. It would boot about one in five times.
I then tried going back to a reinstall of old HC Taboonay 2.2 .. it worked for quite some time before, but now it's hanging and crashing just as it did with the ICS ROMs.
Up to this point I didn't touch the bootloader, which meant I was on the old HC bootloader. But in doing a lot of reading it seemed that many SOD issues were fixed with the new ICS bootloader (unlocked and patched).. so I used nvflash to flash a the ICS bootloader.
Well, this solved my only-would-boot-one-in-five problem and it boots everytime. But it still crashes. I even had it crash in CWM 1.7 just like everywhere else ... frozen screen. I've never seen that before in any of my Android devices.
I really don't know what's happened at this point. I'd be happy just to go back to a version of HC that works. I'm downloading timmyDean's V4 3.2 package (the depositfiles link is the only one that works .. and it'll be done in ELEVEN hours.) to attempt a shot at going back to full stock. But considering that's 11 hours or more away, without knowing it'll work .. I thought I'd ask.
Is there any way to downgrade from the ICS unlocked/patched bootloader?
Is there another bare-metal restore for HC out there besides the hellishly slow timmyDean V4 on depositfiles? Another location to download it from?
Is there anything else I can do?
Thanks ...
Found EUUs_SBK_Acer_A501_0.017.01_PA_ATT on some russian site.
I was able to reinstall everything back to 3.01 from the EUU loader. However my A500 still has serious problems.
- During loading the EUU, getting it in AXP mode worked every time, but bouncing it to Download mode worked rarely.
- Most of the time when attempting to power on it will turn on the power light and vibrate, but nothing shows on the screen.
- Sometimes if it makes it past the above, it will display "ACER" but go no further.
- Once actually loaded into an OS (doesn't seem to matter which one) it will lock up after a short while with the screen frozen. Only a hard power off (hold power for 5 sec) will shut it off.
- It will simply die if soft powered off .. not right away, but after some time.
So, is my A500's hardware broken? I can't seem to get any part of it stable.
Many reinstalls later, all options expired. Returned to Acer for warranty repair.

major issue with my vega booting and I can't get into recovery to fix it.

Hi guys
Im having a nightmare with my vega, I have been running vegacomb for a while without issue and decided I fancied upgrading to an ICS ROM instead, but have hit major problems. I went into rom manager to do a nandroid before I flashed anything, when I opened the app it told me to confirm the device type. it came up saying viewsonic 10 so I confirmed it. Then it decided to re-flash the recovery from within the app, I let it do that too. Then I told it to do a backup of the current ROM, so it reboots and then I get nothing. It does the same thing that normally happens when you go into NVflash (screen backlight comes on, nothing else). I have plugged it into the PC and its not in this mode, its also not letting me get into nvflash using the 2 second hold method. Im really stummped now, I have been messing round with android for a while so im pretty familiar with flashing etc, but without being able to get into recovery im lost. Do you have any suggestions?

Galaxy S4 GT-i9505 Install ROM loading issues. Help please

G'day all,
Hoping someone can help. (firstly I've searched on here over and over and some things have really helped, but can't find this issues on here)
Samsung Galaxy S4 GT-i9505 (originally with Vodafone rom)
Back story, I managed to put google rom via WINTEAM at some point in time (I don't recall how I did this now) this file - crdroid-6.0.0-20151208-jfltexx.zip (I still have this but not a md5 file)
Anyway, I wiped it under settings and basically stuffed it right up. Loops on WINTEAM (this part I had found in search and downloaded Odin3 v3.13) and Samsung Rom and a couple of others.
I9505XXUHOJ3_I9505VAUHOJ1_I9505XXUHOJ3_HOME.tar.md5
I9505XXUHQK1_I9505MAXHQK1_I9505XXUHQK1_HOME.tar.md5
I9505XXUHOL3_I9505TELHOL2_I9505XXUHOL3_HOME.tar.md5
CF-Auto-Root-jflte-jfltexx-gti9505.tar.md5
The last one actually fixed up the google install but was hoping to place the original Samsung ROM back on and now it doesn't help at all when I run again.
The top 3 are Vodafone, Telstra and Max a forum had suggested (from a page on here somewhere). All of these say pass in Odin3 when installing onto phone. But once it gets to the Samsung with what looks like dots shooting out from the word it never gets past this at all.
When I power up the S4 phone, to get to download screen. I have volume up to download or volume down to restart phone. Some places I've read say to select wipe, I don' t have this option at all.
I saw an option to install s8 rom to s4 which I would like to do, but the how to do that requires working software first and install TWRN or something like that.
I'm not sure if this will run fast or ok on this phone, but it isn't a MD5 file either.
I would like Samsung ROM back on as it (for me cleaner than google or maybe just what I've been used to). I'd like to give to my youngest child as their first phone.
I also had tried to place zip files and also unzipped files on the SD card on the phone, nothing worked for me as it looks like it is expected ODIN3 to work.
At this stage of the day, I would just like to have it functioning again with anything that works.
Any advice on what to do now would be greatly appreciated, also I'm truly sorry if this problem has been documented, I really did try to do my research first before putting this up here. I've been on this for weeks now
So quick update. through more research, I have managed to install TWRP and now have access to additional utilities through WINTEAM. I've now tried to install ROM through the Micro SD card.
I think it comes up with a mount error, but has rebooted and still stuck so can confirm just yet.
I've managed to go through the entire process of installing the PurifieD+ROM+v3.5.zip through the micro SD card in the phone. Asked me about all the options etc during the install. There didn't appear to be any errors at all. Asked to reboot. etc....
I even had sound on the bootup, Now I have the Samsung word on the main screen with a blue backlight just flashing. Been like that for nearly 10 minutes. Not looking good.
Have I got bad memory or am I doing something wrong?
I managed to do a wipe after I did an install and it booted up find. I had no WiFi but than installed the vodafone install that should be the original and all works now.
The amount of time I had been working on this, I really didn't think I was going to get it going. I honestly thought I had some hardware error going on.
In the end it runs now, I can setup and had to my child
so I've managed to now use several different ROMs but now I can't root the phone (it should be able to, has been before)
When I run Motochopper I get this error
error: only position independent executables (PIE) are supported.
Seems to happen no matter what rom I've installed. I can't seem to find an older rom running android version 5.01 now
Any help on how to root this. Would be great
Now says it has been rooted, but I do not get the teamwin boot menu option at all. more like just a text style menu for wiping and loading other roms.

Categories

Resources