Database Users

cant flash new rom

Hi
I have a acer iconia a500 and i was trying to flash a rom using the acer recovery installer, i have dont this about 10 times but this time when i booted into the recovery kernal then wiped the chache and the dalvick cache and the battery stats then installed minimalist 3.1 it installed then i rebooted and it did not have the launcher and all my apps where still there. How can i fix this i have tried other roms same thing i need help fixing this

Not only wipe cache user data.i format partitions as well. Reboot back into car.and wipe cache again after flashing rom before booting into it first time.there is a thread about this

+1 to erica
You need to do a *full* wipe before flashing a new ROM.

if i do a full wipe will i loose all my data ie music etc also where is the thread about it?

If running it fro Acer recovery installer, just check the 'wipe data' checkbox. It won't erase your /data/media files. This is all I do when flashing a new rom. Have never had any issues.
Sent from my A500 using Tapatalk

Stock ICS 4.0.3 to Team EOS 4.0.3?

Hey all still a newb here so posting the question here. Now Ive got myself to 3.2.2 rooted it and then got stock rooted 4.0.3 ics on it. Everything run sweet after ready threads I think the Team EOS build seems better.
So my question is how would I go to the build from what I have now. Ive read the thread but it lacking a bit of info and somewhat confusing. Im thinking I do a complete wipe from recovery (which is clockwork) then flash build zip from sd. then flash gapp.zip (google apps) from sd...
Is this correct? I just want to make sure.
Thanks everyone!

MYYZTIK said:
Hey all still a newb here so posting the question here. Now Ive got myself to 3.2.2 rooted it and then got stock rooted 4.0.3 ics on it. Everything run sweet after ready threads I think the Team EOS build seems better.
So my question is how would I go to the build from what I have now. Ive read the thread but it lacking a bit of info and somewhat confusing. Im thinking I do a complete wipe from recovery (which is clockwork) then flash build zip from sd. then flash gapp.zip (google apps) from sd...
Is this correct? I just want to make sure.
Thanks everyone!
Click to expand...
Click to collapse
This is correct.
Wipe Data (Factory Reset), wipe cache, wipe dalvik-cache and battery stats.
flash the build zip and gapp.zip from SD and you're all set.

thanks!
hoopsdavis said:
This is correct.
Wipe Data (Factory Reset), wipe cache, wipe dalvik-cache and battery stats.
flash the build zip and gapp.zip from SD and you're all set.
Click to expand...
Click to collapse
Battery stats eh? cool didnt know that one! Thanks man! Going to rock this now.

MYYZTIK said:
Hey all still a newb here so posting the question here. Now Ive got myself to 3.2.2 rooted it and then got stock rooted 4.0.3 ics on it. Everything run sweet after ready threads I think the Team EOS build seems better.
So my question is how would I go to the build from what I have now. Ive read the thread but it lacking a bit of info and somewhat confusing. Im thinking I do a complete wipe from recovery (which is clockwork) then flash build zip from sd. then flash gapp.zip (google apps) from sd...
Is this correct? I just want to make sure.
Thanks everyone!
Click to expand...
Click to collapse
If you have CWM recovery installed you can just flash the most current Eos nightly build --if you're wifi-only then it's wingray build #44, and then right after, flash the Eos GApps v 10.3. You will have to wipe your cache partitions and go to advanced and wipe dalvik cache. You might get away without a data wipe, but if things get unstable (due to new version of GApps) you'll have to wipe.
Make sure to make a nandroid backup first.

nice.
okantomi said:
If you have CWM recovery installed you can just flash the most current Eos nightly build --if you're wifi-only then it's wingray build #44, and then right after, flash the Eos GApps v 10.3. You will have to wipe your cache partitions and go to advanced and wipe dalvik cache. You might get away without a data wipe, but if things get unstable (due to new version of GApps) you'll have to wipe.
Make sure to make a nandroid backup first.
Click to expand...
Click to collapse
Thanks everyone for the help rocking EOS!

lol i just wish you didnt have to wipe everything....

lucky
alex94kumar said:
lol i just wish you didnt have to wipe everything....
Click to expand...
Click to collapse
I was lucky and hadn't put too much on it. So the wipe wasn't a big deal, if I'm right don't have to wipe every time to update build so was worth it. As a lot say my Xoom a lot snappier now. Would recommend doing it!

Wiping is usually the best way to go. There are workarounds, but the effort it takes to do so kinda outweighs the result.

so my question is....
im new over here, and fairly new to xoom and modding and what not.... anyway would i let the xoom update to 4.0.3 then flash to the nightly?
this is where im lost cause im on 3.2 right now, im unlocked, rooted and have cwm 3.2.0.0 ( US ver wifi only )
i want to finally get a custom rom on here but not sure what to go with?

TheLostXoom said:
im new over here, and fairly new to xoom and modding and what not.... anyway would i let the xoom update to 4.0.3 then flash to the nightly?
this is where im lost cause im on 3.2 right now, im unlocked, rooted and have cwm 3.2.0.0 ( US ver wifi only )
i want to finally get a custom rom on here but not sure what to go with?
Click to expand...
Click to collapse
I went from a rooted tiamat 3.2 rom to a nightly and it worked fine. I would do a wipe within clockwork recovery before flashin the new rom. Also remember to use titanium backup to backup your stuff first...
Sent from my ADR6350 using xda premium

bacon612 said:
I went from a rooted tiamat 3.2 rom to a nightly and it worked fine. I would do a wipe within clockwork recovery before flashin the new rom. Also remember to use titanium backup to backup your stuff first...
Sent from my ADR6350 using xda premium
Click to expand...
Click to collapse
the other thing is im trying to find a walkthough ish or something goin from 3.2 to the nightly.. i cant find to to much on this.. or maybe i havent searched enough anyway .... and i dont have anything installed right now on it other then the rom manager ....
so would i just go about flashin it the same as i did when i did the full restore? still a little confused

TheLostXoom said:
the other thing is im trying to find a walkthough ish or something goin from 3.2 to the nightly.. i cant find to to much on this.. or maybe i havent searched enough anyway .... and i dont have anything installed right now on it other then the rom manager ....
so would i just go about flashin it the same as i did when i did the full restore? still a little confused
Click to expand...
Click to collapse
Are you still rooted and do you have CWM recovery installed? If yes, it's easy to flash Eos ICS. You go to the correct thread for your device, download the latest Eos ICS rom, the latest Eos GApps v 10.3, put them on your micro sdcard (or internal storage, depending on what CWM recovery you have), boot into recovery, do a nandroid backup, do a data wipe/factory reset, wipe cache and dalvik cache, then flash the rom and the GApps zips one after the other all in the same recovery session, without a reboot inbetween. Then, reboot into Eos ICS goodness! Get all set-up and you're good to go. It will help if you do a full backup of all user apps and data in Titanium Backup and then, after your wipe, do a batch restore of "missing apps and data."

okantomi said:
Are you still rooted and do you have CWM recovery installed? If yes, it's easy to flash Eos ICS. You go to the correct thread for your device, download the latest Eos ICS rom, the latest Eos GApps v 10.3, put them on your micro sdcard (or internal storage, depending on what CWM recovery you have), boot into recovery, do a nandroid backup, do a data wipe/factory reset, wipe cache and dalvik cache, then flash the rom and the GApps zips one after the other all in the same recovery session, without a reboot inbetween. Then, reboot into Eos ICS goodness! Get all set-up and you're good to go. It will help if you do a full backup of all user apps and data in Titanium Backup and then, after your wipe, do a batch restore of "missing apps and data."
Click to expand...
Click to collapse
When first flashing a nightly a nandroid backup is recommended but it's not that necessary when going from your first nightly to another nightly. At least I don't do that because I'd rather hasten the whole data wipe/flash process and it works for me.

CM7 vs CM9 kernel

Hello,
I have old Defy with Bayer module. Which software is better for me? I heard that GB kernel has a bug - full CPU thortle. But when it happens ? Does CM9 have any other bugs ? And is it possible to record videos on this?
Thank you for answers !

Hi,
which Kernel is better is related to the software you are using. But you can't be wrong to use the CM7 Kerner with Quarx newest builds. If you want to use Cyanogenmod 9 I would also recommend you to stay on Froyo-Builds, it causes less problems with the camera.

Im of course considering proper kernel for proper CM7 version.

If you use CM7, I see no reason to change to a GB-Kernel-Version, cause it makes nothing better. In additional the newest nighties are made by Quarx for the Froyo-Kernel. See on ge. tt/8rDd1nC
Edit: No space between the dot and the t

But I've heard that GB kernel is much faster... This problem with max CPU use is problem of soft and will be never fixed on this kernel ?

kernel doubt
hi sorry to bother you
i flashed cm7.1.0-rc1.5-jordan-signed.zip a couple months ago, working fine.
i've been wanting to try out the new cm9 builds.
mi kernel version is [email protected]# 1 i dont know if this "froyo kernel" o "gingerbread kernel"
1_which rom sould i flash... quarx (29 jan) or epsylon3 ( 31 jan)?
2_do i need to flash another kernel previously?
3_what steps do i need to take to flash it?
4_will i be able to downgrade back to froyo 2.2.1 or at least my current cm7 ?
thanks a million
matias

elendil1310 said:
hi sorry to bother you
i flashed cm7.1.0-rc1.5-jordan-signed.zip a couple months ago, working fine.
i've been wanting to try out the new cm9 builds.
mi kernel version is [email protected]# 1 i dont know if this "froyo kernel" o "gingerbread kernel"
1_which rom sould i flash... quarx (29 jan) or epsylon3 ( 31 jan)?
2_do i need to flash another kernel previously?
3_what steps do i need to take to flash it?
4_will i be able to downgrade back to froyo 2.2.1 or at least my current cm7 ?
thanks a million
matias
Click to expand...
Click to collapse
1) both roms use froyo kernel, so you can try anyone.
2) you don't have to flash any kernel, cm7 uses froyo kernel aswell
3) I've just flashed 31Jan, I was using cm7 previously. What i did:
-reboot, when the motorolla logo displays, wait for the blue led to show and then press volume down.
-then you go to recovery, latest recovery. (I highly recomend to do a backup (nandroid) before wiping data)
-wipe data/factory reset, wipe cache.
-install from zip file, and choose either 29jan or 31jan zipfile. (remeber 31jan has gapps included, if you go for 29jan you should install gapps too)
-wipe cache.
-go to advanced, wipe dalvik cache.
-reboot!
First time to boot will take some minutes.
4) If you want to get back to cm7, just recover your backup (nandroid) or follow the same steps in 3) but installing cm7 zipfile.
Hope it helps you, if any more experienced user finds an error in what i've said, please correct me.

fedexmagno said:
1) both roms use froyo kernel, so you can try anyone.
2) you don't have to flash any kernel, cm7 uses froyo kernel aswell
3) I've just flashed 31Jan, I was using cm7 previously. What i did:
-reboot, when the motorolla logo displays, wait for the blue led to show and then press volume down.
-then you go to recovery, latest recovery. (I highly recomend to do a backup (nandroid) before wiping data)
-wipe data/factory reset, wipe cache.
-install from zip file, and choose either 29jan or 31jan zipfile. (remeber 31jan has gapps included, if you go for 29jan you should install gapps too)
-wipe cache.
-go to advanced, wipe dalvik cache.
-reboot!
First time to boot will take some minutes.
4) If you want to get back to cm7, just recover your backup (nandroid) or follow the same steps in 3) but installing cm7 zipfile.
Hope it helps you, if any more experienced user finds an error in what i've said, please correct me.
Click to expand...
Click to collapse
Correction in 4th point ---
for restoring ur Nandroid Backup
1. Do a factory Reset/Data wipe
2. Install CM7.zip
3. Go to restore and Restore the Nandroid that u want to restore.
4. Wipe Dalvik Cache ( Don't wipe cache partition)
5. Reboot

kanna91 said:
Correction in 4th point ---
for restoring ur Nandroid Backup
1. Do a factory Reset/Data wipe
2. Install CM7.zip
3. Go to restore and Restore the Nandroid that u want to restore.
4. Wipe Dalvik Cache ( Don't wipe cache partition)
5. Reboot
Click to expand...
Click to collapse
Thanks for the correction, but I've just came back to CM7 by restoring my old nandroid, without wipe and worked well.

camera doesn't work.and some small bugs

If you use CM7
If you use CM7, I see no reason to change to a GB-Kernel-Version, cause it makes nothing better. In additional the newest nighties are made by Quarx for the Froyo-Kernel. See on ge. tt/8rDd1nC

[Q] Motorola Defy on CM7 stucked on boot screen! Urgent!

Hi guys!
I have just rooted my Motorola Defy and installed CM7 (7.0.2) into it using the instructions provided by CM wiki. I decided to use ClockworkMod and bootmenu, since I'm on Mac OS X.
Well, everything went fine until I tried to open the Market app, which was not working. Searching the web, I found that the solution could be wiping user data and caché through the recovery mode. As I could not figure out how to start the bootmenu (which I learned later), I did it through the stock recovery mode (using power + volume down)... and since that I can't boot my phone anymore!
I have already tried wiping everything again and installing CM7, but I'm still facing this problem.
Please, anyone have any ideas? I'm almost desperate.

gfreh said:
Hi guys!
I have just rooted my Motorola Defy and installed CM7 (7.0.2) into it using the instructions provided by CM wiki. I decided to use ClockworkMod and bootmenu, since I'm on Mac OS X.
Well, everything went fine until I tried to open the Market app, which was not working. Searching the web, I found that the solution could be wiping user data and caché through the recovery mode. As I could not figure out how to start the bootmenu (which I learned later), I did it through the stock recovery mode (using power + volume down)... and since that I can't boot my phone anymore!
I have already tried wiping everything again and installing CM7, but I'm still facing this problem.
Please, anyone have any ideas? I'm almost desperate.
Click to expand...
Click to collapse
So after doing a factory reset from stock recovery, you say you're trying to install CM7...
Are you installing this from CWM recovery?
Did you wipe Dalvik cache?
Are you using an MB525 Defy or an MB526 Defy+, and is the CM7 zip you're flashing a Defy or a Defy+ build?
>
You've probably not wiped Dalvik it seems.
In CWM recovery, go to Advanced and under that select Wipe Dalvik Cache.
Do yhis and a normal cache wipe every time you flash a ROM update. If you flash a totally new rom like CM10, wipe data also.

krushnam said:
So after doing a factory reset from stock recovery, you say you're trying to install CM7...
Are you installing this from CWM recovery?
Did you wipe Dalvik cache?
Are you using an MB525 Defy or an MB526 Defy+, and is the CM7 zip you're flashing a Defy or a Defy+ build?
>
You've probably not wiped Dalvik it seems.
In CWM recovery, go to Advanced and under that select Wipe Dalvik Cache.
Do yhis and a normal cache wipe every time you flash a ROM update. If you flash a totally new rom like CM10, wipe data also.
Click to expand...
Click to collapse
Hi! Thanks for the reply, and sorry for my English.
Actually, I have already installed CM7 and it worked fine, except for the Market app. Trying to solve this, I have done a factory reset from stock recovery and, since that, CM7 is locked to the boot screen.
And yes, I have installed CM7 through CWM recovery, and I'm using a MB525 Defy.
Well, I have just tried wiping Dalvik Cache, but it seem as if nothing happens when I select this.

Ya wiping Dalvik is very fast, but it will make a lot of difference. Every time you update your ROM, wipe both cache and dalvik.
>
If this didn't solve your problem, try wiping market data and uninstalling market updates. They will reinstall on their own.
>
If even that doesn't work, reflash the GAPPS zip.
BTW, shouldn't you be on CM7.2? That's the latest CM7 as far as I know.
CM7.2:
WhiteRabbit 1.8: http://forum.xda-developers.com/showthread.php?t=1510063
Maniac's builds: https://github.com/maniac103/android_device_motorola_jordan-common/downloads
Quarx's builds: http://quarx2k.ru/cm7-nightly-defy/

krushnam said:
Ya wiping Dalvik is very fast, but it will make a lot of difference. Every time you update your ROM, wipe both cache and dalvik.
>
If this didn't solve your problem, try wiping market data and uninstalling market updates. They will reinstall on their own.
>
If even that doesn't work, reflash the GAPPS zip.
BTW, shouldn't you be on CM7.2? That's the latest CM7 as far as I know.
CM7.2:
WhiteRabbit 1.8: http://forum.xda-developers.com/showthread.php?t=1510063
Maniac's builds: https://github.com/maniac103/android_device_motorola_jordan-common/downloads
Quarx's builds: http://quarx2k.ru/cm7-nightly-defy/
Click to expand...
Click to collapse
How can I wipe market data? It is not an option from CWM...

gfreh said:
How can I wipe market data? It is not an option from CWM...
Click to expand...
Click to collapse
You can only wipe data from an app trough the Apps Manager inside CM7 (that means you have to boot up your phone).
Try flashing the newest CM7.2 and the newest GAPPS for CM7.2.
If the problem persists, return your phone to the old .sbf and start all over again.

thiagoelg said:
You can only wipe data from an app trough the Apps Manager inside CM7 (that means you have to boot up your phone).
Try flashing the newest CM7.2 and the newest GAPPS for CM7.2.
If the problem persists, return your phone to the old .sbf and start all over again.
Click to expand...
Click to collapse
Well, I really can't boot my phone. I just can access bootloader and both recovery modes from stock and CWM (bootmenu).
Do you know how can I flash a .sbf on OS X? I know a lot of programs for Windows, and I also have found a script (sbf_flash.sh) that should work on Mac, but it seems that a lot of people are having problems in OS X (including myself).

gfreh said:
Well, I really can't boot my phone. I just can access bootloader and both recovery modes from stock and CWM (bootmenu).
Do you know how can I flash a .sbf on OS X? I know a lot of programs for Windows, and I also have found a script (sbf_flash.sh) that should work on Mac, but it seems that a lot of people are having problems in OS X (including myself).
Click to expand...
Click to collapse
OK. Go to CWM recovery. Wipe data. Wipe cache. Wipe dalvik.
Now install WhiteRabbit 1.8 or Maniac's CM7.2.
Flash the GAPPS packages linked in the respective threads.
Now AGAIN wipe cache and dalvik.
You should boot normally.
>
As long as you can access CWM, there's no need to reflash the SBF.

krushnam said:
OK. Go to CWM recovery. Wipe data. Wipe cache. Wipe dalvik.
Now install WhiteRabbit 1.8 or Maniac's CM7.2.
Flash the GAPPS packages linked in the respective threads.
Now AGAIN wipe cache and dalvik.
You should boot normally.
>
As long as you can access CWM, there's no need to reflash the SBF.
Click to expand...
Click to collapse
Hi,
I have just reflashed a retailer version using RSD on a friend's computer and it is now back to life... now I'm figuring out what is the best path to follow.
Thanks for the help!

Factory resetting from stock recovery messes up custom Rom!! If You are on custom rom, you have to use CWM for doing wipe etc...
Sent from my Defy green lense using xda-developers app

sa3e1 said:
Factory resetting from stock recovery messes up custom Rom!! If You are on custom rom, you have to use CWM for doing wipe etc...
Sent from my Defy green lense using xda-developers app
Click to expand...
Click to collapse
Yeah... I know that. I just wanted to rollback everything and have the phone back. I'm now studying which is the best ROM for me to install again, but meanwhile, I have my phone working.

Fix camera sw issue (green noise)

If You have Rear camera that doesn't show picture and there is weird green noises and Tile pics from Front camera, here is how to fix it.
1) If You are on unlocked BL flash latest version (V8), with Pub recovery version 0.2 ( important part )
You need your SBK for flashing VIA APX flash tool, GUIDE (thanks to civato and blackthund3r) : http://forum.xda-developers.com/showthread.php?t=1622425
If You are on bl v4 or up you can flash it via CWM. Thread (thanks to Skrilax_CZ) : http://forum.xda-developers.com/showthread.php?t=1619913
PUB recovery Ver 0.2, here (Thanks to Ezterry) : http://forum.xda-developers.com/showthread.php?t=1654476
2) Reboot in recovery mode.
3) Factory data reset.
4) Wipe cache partition.
Go to advanced
5) Wipe dalvik cache.
6) Wipe battery stats.
Return to menu and go to mounts and storage
7) Format cache and data
8) Format System and flexrom 2-3 time
Return to menu
9) install zip from sdcard, choose one of Civato's ICS Roms and then flash it.
Civato's Rom, Here : http://forum.xda-developers.com/showthread.php?t=1969887
Great Rom, no problem at all, Thanks to Civato and Ezterry For Their great work.
Now reboot Your Tab.
It delete all trash files from previous Roms and Your camera goes back to normal mode.
Hope It help

Thanks man.
I'll try this as soon as i arrive home.
Do you know why such problem happens?
Since i rooted a500, this problem started.

Didn't work
It didn't work.
I really don't know what to do to fix this problem, otherwise, send it back to Acer.

this one worked for me, i get this problem last week and i think this happens because bad installation of SW.
Are you flashed unlocked bl V8?
try this. use thor recovery 1.7.3 and perform a real format
boot in recovery and format cache and dalvik cache and battery status.
then go to recovery menu, enter Backup and Restore and click on Toggle backup and restore of internal storage data/media
then go to Mounts and Storage and format /data-/system-/flexrom-/cache
keep in mind this will format data and you will loose all you have in the in the internal memory. (backup first)
install civato's rom (rev 6.2 available) and reboot.
see if camera work normal, flash pub recovery (stable)
if camera doesn't work you need to goes back to acer's original rom with acer's recovery and if it doesn't work again it is a HW problem.
this thread can help you for factory reset : http://forum.xda-developers.com/showthread.php?t=1516012

Payman_92 said:
this one worked for me, i get this problem last week and i think this happens because bad installation of SW.
Are you flashed unlocked bl V8?
try this. use thor recovery 1.7.3 and perform a real format
boot in recovery and format cache and dalvik cache and battery status.
then go to recovery menu, enter Backup and Restore and click on Toggle backup and restore of internal storage data/media
then go to Mounts and Storage and format /data-/system-/flexrom-/cache
keep in mind this will format data and you will loose all you have in the in the internal memory. (backup first)
install civato's rom (rev 6.2 available) and reboot.
see if camera work normal, flash pub recovery (stable)
if camera doesn't work you need to goes back to acer's original rom with acer's recovery and if it doesn't work again it is a HW problem.
this thread can help you for factory reset : http://forum.xda-developers.com/showthread.php?t=1516012
Click to expand...
Click to collapse
I tried 4 times.
All the wipes and all the formats.
I have the unlocked bootloader v8
I did install Civato's rom, but still the same problem.
I'll try again later, and report here. If it didn't work, then i know it's a hardware problem.
Thanks man.

LucasPDude said:
I tried 4 times.
All the wipes and all the formats.
I have the unlocked bootloader v8
I did install Civato's rom, but still the same problem.
I'll try again later, and report here. If it didn't work, then i know it's a hardware problem.
Thanks man.
Click to expand...
Click to collapse
Did you drop yourr tablet or did the tablet has a hard bump on something? You may have a loose connection between the camera and the main board.