Database Develop

[Q] Installing Custom ROMS, why stock?

Simple question. If answered in another thread, please give me a pointer. I searched, but couldnt find an answer. Here is the question.
Why do we have to revert to Stock 2.1 before flashing a custom ROM? Why can't we flash a 2.2 custom ROM over another 2.2 Custom ROM? And finally, is there a CWM flashable version of stock 2.1 with root and cwm pre-installed?
Thanks.

before a lagfix was adopted as "standard" by the dev community this was necessary to reset the phone file system to n unmodified state. Now that all the devs are using the same type of awesome lagfix, reflashing to stock isn't really necessary anymore, IMHO. I never do it anymore. I just do a wipe user data from my recovery menu and everything seems to work fine.

The answer is not simple.
You do not have to flash stock. It used to be more needed. Devs still say so, but I believe that is largely to problem shoot issues from the get go. Threads are cluttered with comments like omg my phone is possessed. Well what were you running prior, and what was your setup? If stock well we know what was what. If ulk kernel with ext 2 loop, then yes there could be issues
Flashing stock at this point is just as risky, if not more risky then flashing directly over. If something feels wrong and you can't fix it, flash stock\master clear start over

So in essence, we can flash fine over an existing ROM and if there are issues, better go to stock and flash from there. Am I right? Can you list the steps you take to flash a new ROM without going to stock? Will there be issues if lets say I flash a 2.2 ROM over a 2.2.1 ROM?

I.do this but it may be redundant
Backup apps
Dl rom
Boot recovery
delete cache
delete davlik cache
Flash rom
delete davlik cache
Boot

I never did flash back to stock. I failed. Odin would not connect.
But for you guys out there - there is a way to bring recovery menu, that's what saved me.
Remove SIM and SD card.
Power+VolumeUp = reboot from any locked state
Power+VolumeDown=reboot into recovery
Power+both Volumes=download mode, never worked for connecting Odin, I could go there from Recovery
So my sequence:
remove old backups
create new backups
download ROM
boot into recovery
flash rom
clear cache partition and dalvik cache (probably the same)
run fix permissions
reboot

I think for most new ROMs that take advantage of the updated 2.2.1 filesystems you don't need voodoo or any lagfix. Can't even remember the last time I used ext4 when using speedmod kernel and JS3/JS5 Rom. Makes it easier to flash new roms when you don't have to worry about corruption.
But flash back to stock clears out any unnecessary gunk that could cause 90% of Force Closes and random vibrates on boot

I always thought of it as installing a new operating system or a different version of. It. Cming from the same roots of the ROM or OS, you can just install a different, major update over it (Different ROM) and be on your way.
However if sonething is built differently from the start (Windows and OSX), you cant just install right over the other because there are problems.
I always start back at the beginning because it onky takes a few minutes extra and it makes the phone a whole lot faster; you clean out alk the gunk and unused folders and whatnot.

you definitely want to do a master clear if you do not start from stock, since there are some caches on your sdcard may ruin your new system.

mengbo said:
you definitely want to do a master clear if you do not start from stock, since there are some caches on your sdcard may ruin your new system.
Click to expand...
Click to collapse
Does anyone know how to do a Master Clear with Odin3? Or is there some other way we can do it without Odin3?
Thanks.

Enhanced said:
Does anyone know how to do a Master Clear with Odin3? Or is there some other way we can do it without Odin3?
Thanks.
Click to expand...
Click to collapse
I use the oneclick odin to do master clear. The master clear works on i896 too.

[Q] Stuck in Boot animation after installing seeARMS ROM

Hi, I have installed seeARMS ROM and followed his instuction. I have kept the JL2 modem and speedmod kernell (I was already on speedmod). I have tried 2 methods to install. The seeARMS.UGJL2.v0.4.zip with the seearms file and the CWM.
Both install went OK and I even had a congratulations screen. The problem is when the phone reboot it stays on the boot animation and get stuck there. I have tried 2 different boot animation and the same happen.
I have no problem to restore my data since I had backup but I would like to have the seearms ROM. Any idea?
Also a side question, can we get the new CK1 modem with seearms?
Richard

Have you been wiping your phone before flashing the rom? I have been having issues like you describe only when i flashed a rom w/o wiping.
(In CWM Recovery: wipe data/factory reset, wipe cache and advanced -> wipe dalvik cache)

No. I did not wipe. I am not interested in the new ROM if it mean wiping. I made a test by downloading a boot animation app. I trying 2 different boot animation and had the same result. The boot animation play with no sound but I have a vibration during boot and then nothing. Eventually it go back to the animation, vibrate and this repeat until I restore the backup.
I am wondering if tehre is something special about the Bell Canada boot animation?
Can I use the seearms without any boot animation folder?

I don't think it's a problem about the boot ani in particular.
I am not very familiar with the rom, since i have another device. In the seearms rom thread the dev mentioned two versions of the rom, one that requires wiping and one that does not.
So i guess it could be working out to flash the latter w/o wiping. But in my expirience those things rarely work out that way.
There might be incompabilities with the config data left behind by the rom installed before, or other possible issues.
Only way to be sure that those things aren't blocking anything is to wipe the phone and do a clean flash.
Personally i always do it that way. And if i like the rom, and choose to use it, it is always possible to get back all the apps and settings back with titanium backup and/or syncing them back.
But as always before wiping, if you choose to do so, please be sure to have a full nandroid backup, in case you want to go back, or something goes wrong.

I will try the wipe version

What rom were u on before seearms
Sent from my GT-I9000 using XDA Premium App

I was still on stock (froyo 2.2). Actually still on it today

You were right. The wipe version worked fine. I have now to decide to keep it or not...lol

ROM is awasome was worth well the trouble.

Glad it worked out for you - have fun with the rom
Sent from my Desire Z

[Q] Is wiping required for a ROM update?

When applying an update to a ROM, is a data wipe always required, or can I simply flash boot.img and the .zip over top of the existing installation?
More specific to my situation, I'm using Albinoman's CM11 ROM; if anyone has flashed the December 10 update without wiping data, did it fix the black browser issue or would I need to do a wipe? I'd post this on the ROM's thread, but I don't have ten posts yet.
EDIT: Wiped only Dalvik and flashed the update, works smoothly and the black browser bug is fixed.

Stirlitz_the_Medved said:
When applying an update to a ROM, is a data wipe always required, or can I simply flash boot.img and the .zip over top of the existing installation?
More specific to my situation, I'm using Albinoman's CM11 ROM; if anyone has flashed the December 10 update without wiping data, did it fix the black browser issue or would I need to do a wipe? I'd post this on the ROM's thread, but I don't have ten posts yet.
Click to expand...
Click to collapse
I have found clean wipes the best but use the recovery option to reload certain data etc or back up apps and reinstall clean.
Basically, i back up contacts, calendars, sms etc anyway these days. Makes for an easy transfer of data when needed.
Sent via HTC Velocity 4G + [HolicsROM v1.3] [Sweep2WAKE]

Stirlitz_the_Medved said:
When applying an update to a ROM, is a data wipe always required, or can I simply flash boot.img and the .zip over top of the existing installation?
More specific to my situation, I'm using Albinoman's CM11 ROM; if anyone has flashed the December 10 update without wiping data, did it fix the black browser issue or would I need to do a wipe? I'd post this on the ROM's thread, but I don't have ten posts yet.
Click to expand...
Click to collapse
If you are updating the same ROM... Usually you don't need to wipe... Anything more than dalvik cache and cache
However... EVERYONE will ask you and then suggest a full wipe if you have any issues...
Sent from my Vivid 4G using Tapatalk

Trouble flashing some roms

So I am able to flash dynamickat, hyperdrive, & jovy's deodex stock perfectly fine and they boot up normal and everything. However, when I try darthstalker or skyfall I get bootloops on both. They flash fine but I never make it past the boot animation. It'll be on for a few minutes and then reboot itself. I tried wiping data afterwards but nothing happens. I've downloaded the roms on different pcs, my phone, the md5 was correct, I flashed from my internal sd & external, I formatted everything (even my internal sd to see if that would help for some odd reason), I flashed a different kernel & I also odin'd back to stock and I still have no luck. I am on a t-mobile note 4 & twrp 2.8.1.1. I have no clue what to do anymore & this is becoming pretty frustrating

re: try this
xoxo_xdagirl91 said:
So I am able to flash dynamickat, hyperdrive, & jovy's deodex stock perfectly fine and they boot up normal and everything. However, when I try darthstalker or skyfall I get bootloops on both. They flash fine but I never make it past the boot animation. It'll be on for a few minutes and then reboot itself. I tried wiping data afterwards but nothing happens. I've downloaded the roms on different pcs, my phone, the md5 was correct, I flashed from my internal sd & external, I formatted everything (even my internal sd to see if that would help for some odd reason), I flashed a different kernel & I also odin'd back to stock and I still have no luck. I am on a t-mobile note 4 & twrp 2.8.1.1. I have no clue what to do anymore & this is becoming pretty frustrating
Click to expand...
Click to collapse
I have read your posts in the development thread about the issue you are having.
Give this a try
#1: Do a full wipe including Wipe System, Data, Cache, Dalvik and
last but not least to a factory reset in twrp recovery.
#2: Flash Jovy23's, stock rooted deodexed rom again.
#3: Copy Darthstalker zip file rom to your computer's desktop.
#4: Open Darthstalker zip file rom and remove/delete "boot.img"
from the zip file using winrar or winzip (or other archiver).
#5: Once "boot.img" is no longer in the Darthstalker zip file rom
copy it back to your phone's internal sdcard.
#6: Flash the Darthstalker zip file rom but do NOT wipe anything this time.
If this works for you then that means that for whatever reason your
phone has issues with the original kernel file (boot.img) which was in
the darthstalker zip file before you removed/deleted it,.
Doing it using the above step by step you will be using the kernel (boot.img)
from jov23's stock rooted rom.
If it works for you can open jovy23's stock rooted zip file rom and copy
the boot.img from it to your desktop then close the zip file.
Then open darthstalker zip file rom and copy jovy23's stock boot.img
from your desktop into darthstalker zip file rom.
The darthstalker zip file rom which has no boot.img in it since you have
already deleted and removed it.
Then copy the modified darthstalker zip file rom into your internal sdcard
over-writing the one already there.
Then if you like you can do a full wipe again and flash the modified
darthstalker zip file rom which has jovy23's kernel (boot.img) in it
and it should work fine.
Good luck!

xoxo_xdagirl91 said:
So I am able to flash dynamickat, hyperdrive, & jovy's deodex stock perfectly fine and they boot up normal and everything. However, when I try darthstalker or skyfall I get bootloops on both. They flash fine but I never make it past the boot animation. It'll be on for a few minutes and then reboot itself. I tried wiping data afterwards but nothing happens. I've downloaded the roms on different pcs, my phone, the md5 was correct, I flashed from my internal sd & external, I formatted everything (even my internal sd to see if that would help for some odd reason), I flashed a different kernel & I also odin'd back to stock and I still have no luck. I am on a t-mobile note 4 & twrp 2.8.1.1. I have no clue what to do anymore & this is becoming pretty frustrating
Click to expand...
Click to collapse
When I built the N4 rom, I was having serious qmg boot animation issues, I disabled them, and the rom booted normal, we may have a issue with the new roms and the animations. Just a thought.

re:
AxAtAx said:
When I built the N4 rom, I was having serious qmg boot animation issues, I disabled them, and the rom booted normal, we may have a issue with the new roms and the animations. Just a thought.
Click to expand...
Click to collapse
If that's the case then perhaps it might be a good idea for her to
remove all the qmg files in the system/media folder just to see
if it resolves her bootloop issues before trying anything else.
(I have not had any bootloop issues)
But then why don't all the users of the rom have the bootloop issue?

Misterjunky said:
If that's the case then perhaps it might be a good idea for her to
remove all the qmg files in the system/media folder just to see
if it resolves her bootloop issues before trying anything else.
(I have not had any bootloop issues)
But then why don't all the users of the rom have the bootloop issue?
Click to expand...
Click to collapse
Thanks for trying to help! I did what you said and flashed the stock rom but got an error when flashing darthstalker afterwards when I removed the boot.img but I still went ahead and added the boot.img from the stock rom to to the darthstalker zip and that didn't work. Still bootloops. And that's what I don't understand how it works fine on everyone else's phone and not mine I mean it's not all roms but it's still very weird and I want to know why it's happening. On another note when I do flash the stockrom, hyperdrive, & dynamickat right before it boots I get android system upgrading.. optimizing app 200 out of 200 or so, does that happen with anyone else? is that suppose to happen? does that happen on darthstalker or skyfall?

re: updating apps
xoxo_xdagirl91 said:
Thanks for trying to help! I did what you said and flashed the stock rom but got an error when flashing darthstalker afterwards when I removed the boot.img but I still went ahead and added the boot.img from the stock rom to to the darthstalker zip and that didn't work. Still bootloops. And that's what I don't understand how it works fine on everyone else's phone and not mine I mean it's not all roms but it's still very weird and I want to know why it's happening. On another note when I do flash the stockrom, hyperdrive, & dynamickat right before it boots I get android system upgrading.. optimizing app 200 out of 200 or so, does that happen with anyone else? is that suppose to happen? does that happen on darthstalker or skyfall?
Click to expand...
Click to collapse
The upgrading apps is NOT supposed to happen or appear at all unless you have NOT done a FULL
and complete wipe before flashing.
It's normal for it to upgrade a lot of apps during boot if you decided or have not done a full and
complete wipe which includes Factory Reset, Wipe System, Data, Cache and Dalvik cache.
In your case you need to do a full and complete clean flash and the only way to do that is by doing
a full and complete wipe.
If you keep seeing the "updating apps" after flashing any rom it means you have not done a full wipe.
When you have finally done a full and complete wipe before flashing you will no longer see the
phone doing the "upgrading apps" counting the number of apps to be upgraded during bootup
at all when the phone is actually wiped clean before flashing any roms.
(I am assuming that you're using twrp recovery to wipe and flash roms).
Good luck!

Misterjunky said:
The upgrading apps is NOT supposed to happen or appear at all unless you have NOT done a FULL
and complete wipe before flashing.
It's normal for it to upgrade a lot of apps if you decided or have not done a full and complete wipe
including Factory Reset, Wipe System, Data, Cache and Dalvik cache.
In your case you need to do a full and complete clean flash and the only way to do that is by doing
a full and complete wipe.
If you keep seeing the "updating apps" after flashing any rom it means you have not done a full wipe.
When you have finally done a full and complete wipe before flashing you will no longer see the
phone doing the "upgrading apps" counting the number of apps to be upgraded during bootup
at all when the phone is actually wiped clean.
Good luck!
Click to expand...
Click to collapse
I am doing a full wipe though?

System wipe

Hey. What are the advantages/disadvantages of wiping system when installing new ROM? For example Xiaomi.eu rom instructions says you should not wipe system or phone can be bricked. But there are many tutorials that say to wipe also system when installing new ROM.
I've had cm 13, cm 14.1 and different versions of Xiaomi.eu but I've never wiped system - just cache, dalvik and data. I wonder if this causes some problems on my mi 5.

Full wipe of your Mi 5 storage does NOT cause problems to your phone of any sort. In fact, it is good to perform a full wipe of your phone when you are upgrading from one android version or another, for example cm13 to cm14.1! Full wiping completely removes all junk on your phone as it literally removes everything. One thing to not however, is that you will need to reflash your recovery and your preferred ROM after performing a full wipe. If you are just thinking of flashing between different builds of the same ROM such as between CM14.1 nightly builds, only a dirty flash is needed (Clearing cache/dalvik). Hope this clear things up for you!

achickennugget said:
Full wipe of your Mi 5 storage does NOT cause problems to your phone of any sort. In fact, it is good to perform a full wipe of your phone when you are upgrading from one android version or another, for example cm13 to cm14.1! Full wiping completely removes all junk on your phone as it literally removes everything. One thing to not however, is that you will need to reflash your recovery and your preferred ROM after performing a full wipe. If you are just thinking of flashing between different builds of the same ROM such as between CM14.1 nightly builds, only a dirty flash is needed (Clearing cache/dalvik). Hope this clear things up for you!
Click to expand...
Click to collapse
I understand. Just thinking the term "full wipe". Somewhere that is data/dalvik/cache wipe, somewhere data/dalvik/cache/system wipe. I always do clean flash when i change between roms and clear cache/dalvik/data. But I'm just unsure about wiping system partitition. At least with xiaomi.eu rom you should NOT wipe system, just data/cache/dalvik.
Some AOSP roms are advicing wiping also system partitition.

The "System" partition is essentially where your OS resides (correct me if I'm wrong!), hence by wiping it, you are essentially removing your OS. Reinstalling the ROM afterwards then ensures that the ROM is in a sense "cleanly" flashed and will not have any unnecessary or corrupt files of sorts. Wiping system partition will NOT cause issues, that I can guarantee you, just that your phone will not have any OS to boot into when you reboot. Which is why I recommend you to have the ROM and recovery zip on your computer to flash it afterwards!

Well it's safe to wipe system partition but I am not sure about xiaomi.eu nougat ROM's the first nougat update bricked many devices, anyways wiping system is safe.