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.

if i have GB bootloaders can i flash any GB ROM??

Lets say im already on serendipity 7, naturally i have the GB bootloaders. Can I flash any GB ROM over serendipity, or do some GB firmwares not play well with others when flashing one over another?
Or is it pretty straight forward, if I'm already on Gingerbread, im good to go as far as flashing any other gingerbread ROM over the one im on?

yes it should be pretty straight forward...unless you are switching to continuum(which has talon kernel and cwm 3) you need to odin talon first and then flash continuum from the orange cwm. if you were going to any other gb rom, say mosaic for example, just wiping data/factory reset, wiping cache, and wiping dalvik cache then flashing the rom will be fine.
oh if youve done any converting to EXT4 (chainfire app, or voodoo lagfix) convert back to rfs first.

In the threads for each rom it should say which bootloaders its running and from which model, if it matches what you have it'll work. Just be careful with CM7 and MIUI because they use custom ones.

What did I do wrong?

I downloaded that AIO Captivate Toolbox. I got to 2.1 stock, I rooted the phone. I installed clockwork mod. Then i downloaded MIUI 1.8.19. I booted into clockwork, did a backup, then cleared data, then flashed the MIUI zip.
My phone got stuck on the Att World Phone logo. Thankfully I'm back to stock again, but I'm curious as to what I did wrong to get to where I was.
thanks

I cant see what you did wrong maybe corrupt rom download? You did wipe system, data, and cache yes?
Also what I do step by step below.
Odin Oneclick jf6 (with bootloaders)
Flash cwm without rooting by placing update.zip on internal memory
Wipe data/factory reset
Format system
Flash miui (then language pack if miuiandroid.com version)
Reboot
Enjoy!
Edit: if you plan on using gb bootloaders they have only worked for me in the past if I flash them on stock jf6 before flashing miui. Might just be my cappy though.
Sent from my i897 running MIUI 1.8.19 with TalonMTD kernel.

It seems like you followed the instructions. Only advice i can give you is try again, maybe wipe davild cache. I'm not a fan on AOSP for captivate since they dont always work well, and can give complications to fix. But that's just my experience Ive had much better experience with AOSP's and other brands like HTC.
edit---what xijar said about a bad download could be the issue.

Q: What did I do wrong?
A: Non-descriptive thread title.

cliffgardner said:
Q: What did I do wrong?
A: Non-descriptive thread title.
Click to expand...
Click to collapse
Lol
Sent from my i897 running MIUI 1.8.19 with TalonMTD kernel.

[Q] Switching to Sense Rom to update PRL, etc

I'm trying to flash a sense ROM to update my PRL. I'm currently using:
Jaybob's TeamHeroC Rom, the .35 kernal
Firerats 1.5.8 Partition mod
The issue I'm running into is once I install a sense ROM (have tried NFX and Liquidsense so far) I get a never ending white HTC screen, have to pull the battery and back up using Nandroid.
The order I've been trying to do things:
Wipe, Clear cache and Dalvik
Flash Remove 1.5.8
Wipe, Clear Cache and Dalvik
Reboot Recovery
Flash Sense ROM
White screen/won't boot
From there I have to battery pull, wipe, re-flash Firerats and do a nandroid restore to get back where I was. I'm pretty sure I'm leaving out a step, so I was wondering if anyone could give me a clue on what I'm leaving out.

Is it safe to assume u didn't save a backup of ur original ROM right after u rooted ur hero?
If u did then go there to do the prl update.
If not then, try "fresh ROM" first, then try liquid sense or nfx...
But you may to factory reset twice, then under CMR recovery go to mounts and storage and format all but SD card stuff. Most recommend to do it twice .... just to make sure.
Now flash the ROM by itself since u don't need to sign in for anything so no need to flash gapps if ROM doesn't already have it.
Are you using any tweaks perhaps, firerat's? If so I've read that there are issues with that if your system is partitioned too small.
Good luck
Good luck!
Sent from my HERO200 using Tapatalk

When going from an AOSP ROM to Sense and vice versa you format boot, cache, system, data and dalvik cache.

vidaljs said:
Are you using any tweaks perhaps, firerat's? If so I've read that there are issues with that if your system is partitioned too small.
Click to expand...
Click to collapse
Yes, using the Supercharged V6, 3G Supercharger, KAK and Firerats.
I flash the fr-remove before flashing the new ROM. Taking care to format everything had the same results, as did flashing my old backup just after I rooted. I haven't tried flashing another ASOP rom or CM7, but so far it seems I can only restore my most recent backup.

oldredhat said:
Yes, using the Supercharged V6, 3G Supercharger, KAK and Firerats.
I flash the fr-remove before flashing the new ROM. Taking care to format everything had the same results, as did flashing my old backup just after I rooted. I haven't tried flashing another ASOP rom or CM7, but so far it seems I can only restore my most recent backup.
Click to expand...
Click to collapse
Firerats is the issue. Your /system partition is currently too small. I've never had good luck with FR-remove. Re-flash your recovery image prior to flashing Sense. I triple format my /boot, /system, /data, /cache, and Dalvik cache using Clockwork receovery as well. Thank goodness I don't have to do that very often!

[Q] Flashing ICS Roms when you are already on ICS

Hello guys!
I was wondering how should I go about flashing another ICS Rom. I am already on AOKP build 23. If I want to flash another rom do I just wipe data, cache and dalvik cache and install from SD card?
Also, to change a kernel do I just install from SD card?
Many thanks!!

its no difficult man

Just reading. No so difficult like he said.

erm, so is what i said correct?

Factory reset (which is the same as wipe) -> install from SD. Done.

Yes, you got it right. Also follow instruction for the specific rom you want to use.
If there are problems flash to stock with odin + repartition.

Restore and flash
I tried to flash slim rom from sharing rc 4.2.but failed to pass the kernel screen. Don't know what went wrong