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] Need help now matter what i flash

Hi guys,
my problem is that whatever i flash it ends up with reboots.
I have flashed a gingerbread bootloader and then deoxed rom JVQ and finally semaphore Kernel to get CWM(with odin).
Then I have tried Darkys rom but anytime i reboot it reboots again-twice or it reboots when im in the app drawer.
Juwes rom-sometime it reboots itself. SYMPLY rom-after closing voodo control app it hangs and reboot and the same thing happens with control freak or it just reboots when your sliding through the menu.
I dont get it what iam doing wrong why i have this ****ing reboots.
I hope someone can help
selami023

Some ROMs have bugs that cause reboots. Sometimes it might be cause by modem or kernel incompatibilities.
The safest option would probably be to find a ROM you like the look of (with detailed installation instructions) and do a completely clean install of it (factory reset/format SD->Odin flash stock Firmware -> Follow ROM instructions). Or just stick with the stock firmware. Avoid using TitaniumBackup to restore apps to be really safe.

thx dude for your answer now i have miui galnet and everything works fine except that it restarts when i press shut down(but only while charging).
But i really dont get it why there are so much bugs. I have also a htc desire hd and i can overclock it to 1,6 ghz and its still stable almost with all custom roms that are available for the desire hd.
selami023

Camera stops working often after cwm 6.0.4.8 on aosp roms

I'm not sure if I'm the only one experiencing this but every time I try to flash a custom kernel on CM11 and PA4 with cwm 6...4.8 camera app freezes like usual but then freezes again after 5 secs which is not usual.
Not only does this happen on custom kernals but stock CM11 and PA as well e.g. when I was in the science museum using PA taking pics everything was working well, then phone froze so I did a reboot in fact 5 reboots and camera displayed same symptoms as explained above. Also on CM11 stock kernal I did a regular reboot to apply full theme and bam camera stopped working all AF a sudden.
To fix I had to reflash ROM. I even did a full wipe( including format system) and still had same symptoms.
Pimped kernal just breaks camera straight from reboot no matter how many times I reboot it doesn't fix the problem. Only fix seems to reflash ROM (no need to wipe). Restoring stock/original ROM kernel fixes it but WiFi does not work.
Any way to get custom kernels to work without breaking camera?

..just an advice, do not use CWM, is recommended to flash with TWRP because is more efficient. I had many problems with CWM.

eclyptos said:
..just an advice, do not use CWM, is recommended to flash with TWRP because is more efficient. I had many problems with CWM.
Click to expand...
Click to collapse
Thanks for the reply. I have no option but to use cwm cause all my back ups where done on cwm.
As for the problem I found the solution in this thread:
http://forum.xda-developers.com/showthread.php?t=2505973
yup owns Z1 and stuff.

[Q] exhibit 2 4g hangs on incoming call

Dear all,
i have an old samsung galaxy exhibit 2 4g and decided to install a custom rom. i used below mentioned link for the ROMs.
http://forum.xda-developers.com/wiki/Samsung_Galaxy_Exhibit_4G
i have tried majority of the ROMs after v4 but all of them are giving me same problem
Phone hangs on incoming call and only vibrates no sound. and i have to ultimately pull the battery out.
the issue is not observed on stock ROM.
It is also not observed on REMICS 3.0.1 but only if i disable backup and restore option. disabled this option on other custom rom as well but did not fix the issue on other ROMs.
I would appreciate any help.

wonderwall_85 said:
Dear all,
i have an old samsung galaxy exhibit 2 4g and decided to install a custom rom. i used below mentioned link for the ROMs.
http://forum.xda-developers.com/wiki/Samsung_Galaxy_Exhibit_4G
i have tried majority of the ROMs after v4 but all of them are giving me same problem
Phone hangs on incoming call and only vibrates no sound. and i have to ultimately pull the battery out.
the issue is not observed on stock ROM.
It is also not observed on REMICS 3.0.1 but only if i disable backup and restore option. disabled this option on other custom rom as well but did not fix the issue on other ROMs.
I would appreciate any help.
Click to expand...
Click to collapse
sorry late on this. which cwm or twrp version are you using? jfbs twrp 2.7.1.0 or cwm 6.0.4.8 is the latest which is need on kk roms also cars1198 has cwm6.0.4.9. picking one of these 3 is user preference. for kk roms lastest slimbean 7/7build and dcm 6/20 by jfbs is stable and for cm11 cars1198 6/19 build is pretty stable. any of these 3 should work just fine without any issues with latest recoveries. if you dont know how its just like flashing a rom except when you reboot you want to reboot boot back into recovery then do a fresh install. also on a complete fresh install what ever is on on your internal sdcard that you want to keep move it to external sd or pc. then format /system /data /cache /android secure and /sdcard0. then install rom only, reboot and wait for it to fully boot up. then reboot back into recovery and install gapps. then wipe dalvik-cache and reboot. after you sign into gplay give the phone time to sync your contacts and so forth which will bog down the phone for 1-30mins or longer depending how much needs to be sync. after that you should be ready to go with no or very minor issues. in which you would ask in the appropriate rom op.

TripFX said:
sorry late on this. which cwm or twrp version are you using? jfbs twrp 2.7.1.0 or cwm 6.0.4.8 is the latest which is need on kk roms also cars1198 has cwm6.0.4.9. picking one of these 3 is user preference. for kk roms lastest slimbean 7/7build and dcm 6/20 by jfbs is stable and for cm11 cars1198 6/19 build is pretty stable. any of these 3 should work just fine without any issues with latest recoveries. if you dont know how its just like flashing a rom except when you reboot you want to reboot boot back into recovery then do a fresh install. also on a complete fresh install what ever is on on your internal sdcard that you want to keep move it to external sd or pc. then format /system /data /cache /android secure and /sdcard0. then install rom only, reboot and wait for it to fully boot up. then reboot back into recovery and install gapps. then wipe dalvik-cache and reboot. after you sign into gplay give the phone time to sync your contacts and so forth which will bog down the phone for 1-30mins or longer depending how much needs to be sync. after that you should be ready to go with no or very minor issues. in which you would ask in the appropriate rom op.
Click to expand...
Click to collapse
hey there,
thanks for the reply.
I am using cwm v6.0.1.2.
What i get from your reply is that
flash the latest recovery, reboot in to recovery again
flash your suggested ROM, fresh install
boot in to the OS
boot again in to recovery and install gapps
boot the phone and give it a couple of hours to sych data and update if any and then see if its working or not.
i will give it a try and will let you know. btw i was not facing any issues on any other roms except the mentioned issue and all the roms were running pretty fast.

wonderwall_85 said:
hey there,
thanks for the reply.
I am using cwm v6.0.1.2.
What i get from your reply is that
flash the latest recovery, reboot in to recovery again
flash your suggested ROM, fresh install
boot in to the OS
boot again in to recovery and install gapps
boot the phone and give it a couple of hours to sych data and update if any and then see if its working or not.
i will give it a try and will let you know. btw i was not facing any issues on any other roms except the mentioned issue and all the roms were running pretty fast.
Click to expand...
Click to collapse
everyones had different issues using older recoveries. cwm 6.0.4.4-5 works for anything jb or below. the higher ones are for kk roms which is the most recent and both cars and jfbs kk roms are better then aoip or any of the other roms. Since ion hybrid thanks to adc team and more stable kk roms are out now. imo any of cars is cm roms are good for the everyday people while jfbs slim and dcm are geared more to those who want more features and customization (advance users). i always test both devs roms but personally i like jfbs roms better as far as what i do but any of the 3 are stable for everyday use now. but ya let me know if that helped out.

TripFX said:
everyones had different issues using older recoveries. cwm 6.0.4.4-5 works for anything jb or below. the higher ones are for kk roms which is the most recent and both cars and jfbs kk roms are better then aoip or any of the other roms. Since ion hybrid thanks to adc team and more stable kk roms are out now. imo any of cars is cm roms are good for the everyday people while jfbs slim and dcm are geared more to those who want more features and customization (advance users). i always test both devs roms but personally i like jfbs roms better as far as what i do but any of the 3 are stable for everyday use now. but ya let me know if that helped out.
Click to expand...
Click to collapse
tried cynanogen1, worked smoothly but did not fix the issue
slimkat 4.4.4, faced FC every second. it was almost impossible to even boot the phone.
first i thought there is some hardware issue but the phone is working fine on 2 roms so i guess thats out of the question. let me know if you could suggest something else.

wonderwall_85 said:
tried cynanogen1, worked smoothly but did not fix the issue
slimkat 4.4.4, faced FC every second. it was almost impossible to even boot the phone.
first i thought there is some hardware issue but the phone is working fine on 2 roms so i guess thats out of the question. let me know if you could suggest something else.
Click to expand...
Click to collapse
which cwm or twrp version did you use. I too was facing the fc's on my phone for a while but after using twrp 3.7.1.0 or cwm 6.0.4.8 i dont have that issue anymore. my personal exact order including mods i use.
1. flash twrp 3.7.1.0 < if you already have this or cwm 6.0.4.8 already
2. Format /system then /cache, then /data/ then /internal sd < so everything except /boot and /external sd
3. flash rom < if doing cm11 you can flash oc kernel right after
4. flash supersu < optional its the same as stock superuser but little more options like allow su on boot (on xda)
5. wipe davlik cache and reboot system
6. reboot boot back into recovery
7. flash gapps < if slim get it from slimroms, if dcm or cm11 the gapps from cars1189 mass cm build 1-5-14.
8. flash malive booster < (on xda)
9. wipe dalvik cache and reboot system
10. once full loaded back in install seeder 2.0 (on xda) have a check mark on all 3 with light profile then enable.
11. then finish signing in google account and updating apps. 30mins later its smooth as butter.

TripFX said:
which cwm or twrp version did you use. I too was facing the fc's on my phone for a while but after using twrp 3.7.1.0 or cwm 6.0.4.8 i dont have that issue anymore. my personal exact order including mods i use.
1. flash twrp 3.7.1.0 < if you already have this or cwm 6.0.4.8 already
2. Format /system then /cache, then /data/ then /internal sd < so everything except /boot and /external sd
3. flash rom < if doing cm11 you can flash oc kernel right after
4. flash supersu < optional its the same as stock superuser but little more options like allow su on boot (on xda)
5. wipe davlik cache and reboot system
6. reboot boot back into recovery
7. flash gapps < if slim get it from slimroms, if dcm or cm11 the gapps from cars1189 mass cm build 1-5-14.
8. flash malive booster < (on xda)
9. wipe dalvik cache and reboot system
10. once full loaded back in install seeder 2.0 (on xda) have a check mark on all 3 with light profile then enable.
11. then finish signing in google account and updating apps. 30mins later its smooth as butter.
Click to expand...
Click to collapse
you are the MAN man. from your instructions i deduced that i was not wiping davlik cache after flashing but before. now every rom is working fine, no issue is observed. thanks
Since you know your stuff could you let me know which rom is the best in terms of performance and battery life?
thanks again

wonderwall_85 said:
you are the MAN man. from your instructions i deduced that i was not wiping davlik cache after flashing but before. now every rom is working fine, no issue is observed. thanks
Since you know your stuff could you let me know which rom is the best in terms of performance and battery life?
thanks again
Click to expand...
Click to collapse
Stock wise Slim has better performance over cm11 with slightly less bettery life. to get the best performance to battery life follow my oc guide i posted. you want to keep the voltage equal to or less then stock voltage while having the highest frequency as possible. the lower voltage from stock the higher battery life over stock will be. if you do plan on overclocking and undervolting your self make sure you read my oc entirely before attemping. the oc guide methodology is the same for anything that can overclock including desktop cpus, gpus, and yes some nics. some routers as long as it can support a 3rd party firmware such as ddwrt or openwrt. other phones that have oc and voltage control support. you may also get some extra performance and battery saving by trying different build.prop tweaks or mods or any of the combination. some may help you and not me and vise versa and some may help everyone. its more about find what works best for you for what you do.

Note 4 boot loops on every COD6 based rom

I have no idea why it's doing this, I've ensured I'm yak g the latest TWRP, checked every MD5 and still it boot loops on every COD6 based rom, even stock. Any idea what might be going wrong?

brokenbentou said:
I have no idea why it's doing this, I've ensured I'm yak g the latest TWRP, checked every MD5 and still it boot loops on every COD6 based rom, even stock. Any idea what might be going wrong?
Click to expand...
Click to collapse
Just to make sure you don't have a bad file, go here and grab the zip that has everything you need in one zip. Use those files and follow the instructions and see if you have a different result.
http://forum.xda-developers.com/showpost.php?p=56226823&postcount=2

brokenbentou said:
I have no idea why it's doing this, I've ensured I'm yak g the latest TWRP, checked every MD5 and still it boot loops on every COD6 based rom, even stock. Any idea what might be going wrong?
Click to expand...
Click to collapse
In my experience, most boot issues can be caused by one of 3 things: kernel issue, not enough system partition space for the rom (could also be corruption that Odin flashing could fix), or bad file. However, with lollipop roms, they do take a solid 10-20 mins to boot so it's possible you're just not letting it sit long enough!
To rule out kernel issues, I'd flash the rom then flash the stock cod6 kernel (before first boot). It should boot up fine. If not, then I'd go to the second on the checklist.
With the note 4 we don't really have to worry about system space so it could be you just need to freshen things up and flash the stock firmware in Odin. Have you done that yet at all? Because you do have to upgrade certain critical things (modem, bootloader, etc) before any lollipop rom will boot on your device.
Third I'd update my recovery and make sure my files are good. Personally I think it may just be a case of not waiting long enough or a kernel thing, but give some of those things a try & see if it doesn't sort your issue.