flashing questions - Vega General

Hi,
what is the difference between nightly cyanogen, corvus and stock rom?
I keep reading that i should update stock rom and install corvus. What is the difference between stock and corvus? It's not sufficient to just install corvus?
My POV Mobii was delivered with 1.07 and i only installed corvus.
Also is it possible to update stock rom by using adb wireless?

kizzarizz said:
Hi,
what is the difference between nightly cyanogen, corvus and stock rom?
I keep reading that i should update stock rom and install corvus. What is the difference between stock and corvus? It's not sufficient to just install corvus?
My POV Mobii was delivered with 1.07 and i only installed corvus.
Also is it possible to update stock rom by using adb wireless?
Click to expand...
Click to collapse
Cyanogen is a Android 2.3 ROM based on CM source
Corvus is a AOSP Android 2.2 ROM build from Google sources
Stock ROM is a OEM Android 2.2 ROM
Differences:
CM is still experimental, not everything is working yet (most things are though), overclocking, not sure if WiFi and background tasks run when screen off
Corvus has a very unique theme, very fast, overclocking, Wifi and background tasks running when screen off. Does not support my Huawei 3G modem (others not tested by me)
Stock ROM is slower, supports internal 3G modems (usually), no overclocking (until you change the kernel), Wifi and background tasks stop when screen goes off.
You can go from any ROM to any other ROM without flashing a stock ROM, but for the pov Mobii, there might be a restriction. As far as I know (not tested) the pov Mobii stock ROM switches the USB to host mode by default, so flashing by ADB debug interface is not possible.
Yes, you can update from stock ROM to other ROMs by wireless adb, as long as the ROM you want to install offers the option to flash through adb debug.

very clear!
One more question though.
When i installed Corvus5 on my stock 1.07 i ended up with three launchers.
When upgrading through CWM i selected both options to clear caches.
Is it normal to end up with three launchers?

kizzarizz said:
very clear!
One more question though.
When i installed Corvus5 on my stock 1.07 i ended up with three launchers.
When upgrading through CWM i selected both options to clear caches.
Is it normal to end up with three launchers?
Click to expand...
Click to collapse
3 launchers sounds strange to me. I checked corvus files and I see only the standard Android launcher in it. You can try to uninstall the launchers you dont want.
In CWM there is a third wipe option, hidden under the menu advanced. Wipe Dalvik-cache. Did you try this too?

my stock rom has two laucnhers and after installing corvus5 it added a 3th one.
I used CWM to install the rom and definitely cleared the dalvik cache.
I upgraded the rom from the sd card though, does that make a difference?
Is it possible to maybe format the device?
EDIT:
My stock rom has 2 different app stores and after installing corvus i have 3 app stores. It's definetely not formatting the device but just overwrites files.

kizzarizz said:
my stock rom has two laucnhers and after installing corvus5 it added a 3th one.
I used CWM to install the rom and definitely cleared the dalvik cache.
I upgraded the rom from the sd card though, does that make a difference?
Is it possible to maybe format the device?
EDIT:
My stock rom has 2 different app stores and after installing corvus i have 3 app stores. It's definetely not formatting the device but just overwrites files.
Click to expand...
Click to collapse
You must no clear the dalvik cache... you must do a full wipe (factory reset). And then reinstall the rom.
Corvus.

Oh just noticed in the settings there is a factory reset, i did a different reset...
Thanks!

My tablet was stuck booting after i tried a usb switcher app.
I bought a usb cable and installed the newest stock rom.
But i can't find the factory reset anymore, what is the best way to do this?
EDIT:
Nevermind, really tired, its the wipe option in CWM...

Related

Modaco ROM alternatives?

I'm just wondering what's so good about the Modaco ROMS... From what I was reading it's the best thing to ever happen to Hero but I've flashed it and it actually seems slower/laggier than my stock ROM... should this be?
My stock ROM was 2.73.XX but I can't remember the exact build number. I'm using Modaco 3.0... are there any other ROMS out there I should consider trying? I'm looking for the fastest and most responsive ROM out there. I do A LOT of multitasking so I'd like to have a ROM that can keep up.
If you did a complete data wipe/factory reset, while having the Modaco Rom, the Hero should be a lot more responsive and faster.
I like Modaco rather than stock rom because it removes some useless apps and allows for more customization. Btw, another alterative to the stock and Modaco is the [email protected] and the Clean ION Roms.
There are several different Roms, the differences is the types of apps removed/installed and the Android firmware.
i like modacos roms, because they work reliable and good. with pauls roms i am sure that he has tested them well, and i can use them as basis for my own modifications, or just can push them to my friends' heros without having them complain that something doesn't work. also in case you need support you can ask paul, he is really a nice guy.
there are some other roms, but imho mcr3.0 is by far the most evolved rom, esp. for everyday use. check the development section here for other roms, including the brandnew android 2.1 roms
Well here's the thing. I didn't wipe/factory reset before I Flashed the ROM. After flashing it went into a reboot loop, it would keep rebooting and when it got to the last boot animation, reboot again... I then did a wipe using the recovery boots wipe option and then it booted fine... Maybe I should do another wipe and flash again? It sucks though because now I've customized it back to the way I like it... I hate having to do that all over again. I guess I need to do the A2SD thing so I don't have to redownload my apps again... that was annoying when I had to do it after flashing Modaco's.... I couldn't even remember all that I had installed lol.
Anyone think reflashing might make it better?
I've been using MCR since about 2.2 so I can't speak for 3.0, but when I first flashed with 2.2 I didn't factory reset or format my SD card and it was a complete fail... apps force closing constantly, unable to recieve SMS, and other assorted weirdness.
So I factory resetted, reflashed and from that point MCR has run very smoothly and each update has gone OK (except for one where i had to format and repartition my SD card for A2SD, but didn't lose any settings).
So my advice would be that if you go to the effort of starting with a clean slate you'll get a much better user experience, which is what all us existing MCR users have...
streetdaddy is spot on. Do a clean wipe and then a rom flash.
I'm using MoDaCo 2.9. For my Hero, 3.0 ate up a lot of my phone's internal memory and kept saying I was running out of memory. The differences are minuscule and the speed improvement is about the same.
I started using Pauls ROM as soon as I got my Hero (which was a few days after release) because the stock ROM was toilet, and I've not looked back. The ROM itself is excellent and the support is first-class.
Make sure to wipe before installing. Once you've got it up and running you shouldn't have to wipe it when you upgrade next time.

Very Few ROMs or kernels work on my DHD

Basically, I have s-off and the official clockwork mod recovery installed. However, the same problems occurred with paul's version of custom recovery.
When flashing, I always go through the process of erasing all the partitions via mounts and storage, then i erase davlik cache and battery stats.
Then I install the ROM by the zip install.
And with kernels, I just install (not aware of any other steps that are needed)
But this is where I come unstuck. I am currently on RaiderX303's Cyanogen port. But I can't get any other roms to work. The same with kernels. Basically, flashing always completes with no errors, but then it crashes/stops at the second spash. So on core droid, it crashes on the android with a green circle going round it.
Anyone got any idea why this might be happening? Couldnt find any reference to it from anyone else.
Anyone got any idea?
tried getting clockworkmod from rom manager? the earlier version has a bootloop issue
I have the same problem with the Core Droid Rom, I believe its the kernal it has,some devices don't like it. The phone don't like the overclock, Infact not many do work on my device.
Sent from my Desire HD
rorydaredkign said:
Basically, I have s-off and the official clockwork mod recovery installed. However, the same problems occurred with paul's version of custom recovery.
When flashing, I always go through the process of erasing all the partitions via mounts and storage, then i erase davlik cache and battery stats.
Then I install the ROM by the zip install.
And with kernels, I just install (not aware of any other steps that are needed)
But this is where I come unstuck. I am currently on RaiderX303's Cyanogen port. But I can't get any other roms to work. The same with kernels. Basically, flashing always completes with no errors, but then it crashes/stops at the second spash. So on core droid, it crashes on the android with a green circle going round it.
Anyone got any idea why this might be happening? Couldnt find any reference to it from anyone else.
Click to expand...
Click to collapse
When you say erasing the partitions , do you mean wiping?, I personally would try installing ROM Manager from the market and letting that install the rom from SD, select wipe and backup before flashing and see if that helps at all, Can you flash the CM RC-1?
I can flash that and also the leeDroid and hd Rom. Just don't like the core Droid and buzz kernals
Sent from my Desire HD
yep I am installing by wiping, but on the last install I used rom manager and still the same problem. Just like vimto, I think it may be the Buzz kernel, so I will try a different kernel and see.
rorydaredkign said:
yep I am installing by wiping, but on the last install I used rom manager and still the same problem. Just like vimto, I think it may be the Buzz kernel, so I will try a different kernel and see.
Click to expand...
Click to collapse
There are some strange issues, camera not working for some of us on raiderx303's ROM, which seem to point to possible hardware variation I wonder if this is a symptom of the same issue?, CoreHD uses buzz kernel as default doesn't it?
But didnt you say you had issues with the MCR? that is based on stock rom so am surprised at that
Yep, I was thinking the same. Maybe EU/US difference. I think the Kaiser has about 4 versions didnt it?

help

folks, my a500 is overheating .. is getting too hot near the Dock Connector ...
is without overclocking, began in the ROM v10 ... already installed a four roms and the error still continues,
currently with honeyvillian, I leave with the original stock which is 3.0.1
I try the same way as was done to use mod 3.2, and does not work
... only shows the current version
well ..
current version: 1.0.1 Honey Villian ...
New Verson: N / A
I want to install the original version to send assistance to repair the high temperature
Verdeee said:
folks, my a500 is overheating .. is getting too hot near the Dock Connector ...
is without overclocking, began in the ROM v10 ... already installed a four roms and the error still continues,
currently with honeyvillian, I leave with the original stock which is 3.0.1
I try the same way as was done to use mod 3.2, and does not work
... only shows the current version
well ..
current version: 1.0.1 Honey Villian ...
New Verson: N / A
I want to install the original version to send assistance to repair the high temperature
Click to expand...
Click to collapse
You're not flashing your Rom correctly. I told you this in Thor's forum (at least the exact post was there also, so I suspect it's you, if it's not you, then accept my apologies ).
The reason it keeps telling you that a certain Rom/kernel is installed, is because it seems like you're just flashing one over the top of another without cleaning anything out. This is why your cpu overheats. You've got a corrupted OS.
Also, a Kernel image is not a Rom. And there are 2 types of kernels. 1 for a stock rom, and 1 for a cooked rom. You shouldn't mix the 2 or you may get problems depending on the rom. Another reason why your cpu overheats.
Do this. Put your SD in your PC's card reader, and format it to Fat32. Reason, is that I have absolutely no idea what you have on your sd. Update.zips, Kernels, Roms, etc.
Copy your VillainRom or Revolver Rom or Taboonay Rom (or whatever rom you want to use) to your SD, then put it back in your 500.
When you flash a new rom, you boot to CWM.
Wipe User Data
Wipe Cache Partition
Goto Advanced and Wipe Delvik
I like to do each a couple of times, just to be sure.
Then go back to the previous menu, and select "Install zip from sd"
Choose your rom and install it.
All three of the above roms come with a cooked kernel so you shouldn't have to mess with kernels.
Also, if you wish to install a different cooked kernel, you only need to wipe Delvik before installing.
Also, Install the rom first and let it run for awhile before installing a kernel. Never do both at the same time.
And the final rule, if you used a backup program like Titanium Backup or any of the others, Never Ever backup and restore system files to a different rom.
But, if you want to put it back to stock, the I suppose you can use the acer recovery tool to flash a stock acer rom and flash the stock recovery image. For more info, see this thread;
http://forum.xda-developers.com/showthread.php?t=1155664

Problems after flashing EliteMod Kernel ICS 120704

Hi all,
first of all sorry for posting here and not in the EliteMod Thread. But i have to post 10 times and then ........
After flashing the new kernel i´m missing a lot of apps?!?!?!
No matter how i flash (wipe data/dalvik or wipe nothing) the apps are missing. I use dataswap (64mb) if necessary.
The apps i miss are Titianium Backup, Terminal, Gentle Alarm and so on.
I dont know why this is happens. Until now every new kernel or Elitemod Rom was fine.
I normally flash via 4ext recovery, but same via RomManager.
Any tipps or help??
BTW: I really love the work from Nikr. His EliteMod Rom and tweaks are really the best i´ve seen so long.
thx for help and keep flashing :fingers-crossed:
If you did a full wipe and installed a fresh new Rom then course you're going to be missing apps until you re-install them. Or at the very least install the titanium backup app then running a restore for the apps.
Though with a kernel-only flash (i.e.: that new one the other day) you shouldn't be wiping data/etc to flash it.
Maybe a little more details on your problem?
Hi,
thx for the quick respond.
I downloaded kernel zip and put it on the sdcard. After that boot into recovery and choose install zip from sdcard.
Thats was the normal way for kernels. But if i do this now i miss a lot of apps.
I tried to wipe only dalvik and flash, same result. I tried to wipe dalvik/data and flash, same result.
Only changes till the last rom flash i did, was to pull down the LCD destiny from 240 to 210 via Rom Toolbox.
It wouldn´t be such a big deal, but the apps i miss i also couldn´t find in the market. If i search for Titanium Backup nothing appears. Same for Gentle Alarm and so on.
I flash Roms for over 1 year now, but something like that never happend
the change in dpi will affect some apps as "not avalaible" as the are only able to work with certain densities. maybe change this and see what happens
Sent from my HTC Vision using xda premium
Today was a new Kernel Version released and everything is fine now.
Looks like there was a kernel problem with apps on stored on the sd card.
thx for help anyway

[Question][Help] Unlocking I9000 Phone and installing cyanogenmod

Hello,
First of all, let me state that I've read much of the FAQ and it is greatly written. However, some of the links are old and not working and I did not understand what I need to do at my stage. Therefore I would really appreciate it if you would kindly direct me to the proper steps and maybe explain some things if I'm stuck along the way. I'm not afraid of learning.
So, I have the following phone which I received from a family member who tried to install something on it but probably did not know what he was doing.
Samsung Galaxy S
MODEL: GT-I9000
SSN:I9000GSMH
- The phone CAN enter the Download state (volume down + home + start) and it shows a yellow Android Icon with a shovel and the word "download" (I think).
- The phone CAN enter the recovery mode (where you can install from zip).
At start, the phone is stuck at loading screen of Samsung and Cyanogen mod.
Unfortunately
-I DO NOT KNOW if the phone is rooted.
-I DO NOT KNOW what is the android/kernal/firmware versions.
So what do I need to know and do in order to:
1. Get the phone back to working order.
2. Root it if so needed.
3. Install the appropriate cyanogen ROM or any other recommended ROM.
a. I want to use the phone for the app XCSOAR. Which is a great flight computer for soaring pilots. Therefore, I don't care much about effects. I do want the phone to be light on battery as possible
(Sometimes for this app to work up to 3-4 hours) and the screen to be bright (so I can see it under the sun).
As mentioned above, I'm willing to learn and would really appreciate your help.
Ramiv
Boot into recovery, do a wipe data/factory reset, wipe cache, Download this ROM , place it on SD card or internal storage and flash it in recovery.. (that's latest and best working KitKat ROM with latest security patches), also download Open Gapps ( ARM, 4.4, nano) and flash it right after flashing the ROM. Wipe cache again, and then reboot system, wait for it to boot, that's it.
.
After further reading I managed to recover the phone to the original local ROM (created by the distributer). I was much helped by a post in this forum regarding a "dbdata" error (cannot mount E).
Now I'll try to flash your new ROM onto my phone.
Thank you very much for your reply. I'll update.
Ramiv
MobileTechArena said:
Boot into recovery, do a wipe data/factory reset, wipe cache, Download this ROM , place it on SD card or internal storage and flash it in recovery.. (that's latest and best working KitKat ROM with latest security patches), also download Open Gapps ( ARM, 4.4, nano) and flash it right after flashing the ROM. Wipe cache again, and then reboot system, wait for it to boot, that's it
.
Click to expand...
Click to collapse
I did just what you recommended and it works fine, so thanks!!
However, when it runs XCSOAR (glider pilot free flight computer) the phone gets very hot unlike in the original distributor's ROM.
Do you have suggestion for a different ROM or settings? Or should I revert back to stock samsung GB ROM?
Thanks again,
Rami
ramiv said:
I did just what you recommended and it works fine, so thanks!!
However, when it runs XCSOAR (glider pilot free flight computer) the phone gets very hot unlike in the original distributor's ROM.
Do you have suggestion for a different ROM or settings? Or should I revert back to stock samsung GB ROM?
Thanks again,
Rami
Click to expand...
Click to collapse
You can try reverting back to stock GB. This is an old phone so its not very good for heavier apps. Google or HERE maps won't even work for me on any ROM i tried, it's too slow.
MobileTechArena said:
You can try reverting back to stock GB. This is an old phone so its not very good for heavier apps. Google or HERE maps won't even work for me on any ROM i tried, it's too slow.
Click to expand...
Click to collapse
Actually it works. It is a nice and probebly not heavy app since it has a version for older PDA computers.
Anyway, I will try and install a stock ROM from this thread.
Thanks again,
Rami

Categories

Resources