Develop Bugs

[Q] Using ROM manager

Okay, I have rooted my phone and have tried to read as much as I can to get comfortable flashing a new ROM...
I have ROM Manager Pro installed and I really want to try to flash a new ROM.
Can any one give me a step by step on how to flash a new ROM??
and then how to revert back to the old ROM if I dont like the new one??
I have created a NAND Backup, I have backed up all my apps and my pictures and everything... I am just scared if I flash a new ROM and do not like it - I will not know how to flash the stock ROM back on to the phone...
I know I am probably a pain in the ass here on the forums...but any help any one is willing to give me would be greatly appriciated!!

JayStation3 said:
Okay, I have rooted my phone and have tried to read as much as I can to get comfortable flashing a new ROM...
I have ROM Manager Pro installed and I really want to try to flash a new ROM.
Can any one give me a step by step on how to flash a new ROM??
and then how to revert back to the old ROM if I dont like the new one??
I have created a NAND Backup, I have backed up all my apps and my pictures and everything... I am just scared if I flash a new ROM and do not like it - I will not know how to flash the stock ROM back on to the phone...
I know I am probably a pain in the ass here on the forums...but any help any one is willing to give me would be greatly appriciated!!
Click to expand...
Click to collapse
Check the link in my sig, that whole thread is useful, but I put together a detailed walk-through in flashing your first rom once the phone is already rooted. Report back if you still have any questions after you check out that thread.
Sent from my blah blah blah blah

WOW - that was awesome!! Thanks for all the info... Now I think I am ready to flash my first ROM... how ever - now I am wondering about kernels and all that - do you by chance have a walk through for doing that as well??

JayStation3 said:
WOW - that was awesome!! Thanks for all the info... Now I think I am ready to flash my first ROM... how ever - now I am wondering about kernels and all that - do you by chance have a walk through for doing that as well??
Click to expand...
Click to collapse
no prob, glad you liked it To flash a kernel, you would use the same steps you used to flash the rom, except instead of wiping all three, you'll just be wiping cache and dalvic cache (and not the Wipe data/factory Reset option). Make sure you've booted up into your new rom before you flash your new kernel and you should be ok.

Cool, sounds simple enough

[Q] [q] need information regarding flashing another rom

i have HTC wildfire. using CyanogenMOD 7 for past 2 months. want to install Splash ROM now. i have some queries & want to be sure before doing anything.
1. do i need to remove CyanogenMOD completely before i install other ROM ?
2. if i unROOT my phone again will i be able to re-ROOT it ?
3. if i just flash another ROM from ClockworkMOD Recovery, will it be installed properly ?
please guide me.

Depends the rom you want to install, some roms require you wipe first, so check the rom installation requirement for any specific one you want to install.

!
gsmxpert said:
Depends the rom you want to install, some roms require you wipe first, so check the rom installation requirement for any specific one you want to install.
Click to expand...
Click to collapse
um, well this was my 1st question that if i need to wipe it completely .!
could not find the answers elsewhere .......
guide me step by step please if possible .
Thanks.

prds359 said:
um, well this was my 1st question that if i need to wipe it completely .!
could not find the answers elsewhere .......
guide me step by step please if possible .
Thanks.
Click to expand...
Click to collapse
Could not find or just can't be bothered to look? there are plenty of guides on xda and hundreds if not thousands if you search google for a guide on how to flash a Rom!!
Basically if your flashing a gb Rom over a sense Rom a full wipe is needed.
However if the 2 roms are from the same base i.e cm7 and a cm7 rip-off chances are you might get away without wiping anything, do a backup first if it doesn't work without wiping anything, just wipe cache and dalvik cache but leave data alone. If that still doesn't work try again with a full wipe.
As for the guide its pretty simple, backup wipe then install from zip.

Scratch0805 said:
Could not find or just can't be bothered to look? there are plenty of guides on xda and hundreds if not thousands if you search google for a guide on how to flash a Rom!!
Basically if your flashing a gb Rom over a sense Rom a full wipe is needed.
However if the 2 roms are from the same base i.e cm7 and a cm7 rip-off chances are you might get away without wiping anything, do a backup first if it doesn't work without wiping anything, just wipe cache and dalvik cache but leave data alone. If that still doesn't work try again with a full wipe.
Click to expand...
Click to collapse
ofcourse i do know how to flash a ROM !!
that's how i installed CM7 !!
thanks for answering my 1st query
i would give it a try now.

Q2. If you unroot it you can reroot it again afterwards but I don't see any point unrooting.
Q.3 is basically the same answer as Q.1.

Tmobile Galaxy S III ROM Help.

First of all, I don't know that much about ROMS but I know that they will make you save battery and let you customize it better. I just don't know how to install the correct and best ROM for my device. I would like some help with this and need someone to explain everything about ROMs please. Thank you in advance.

garciaomar0203 said:
First of all, I don't know that much about ROMS but I know that they will make you save battery and let you customize it better. I just don't know how to install the correct and best ROM for my device. I would like some help with this and need someone to explain everything about ROMs please. Thank you in advance.
Click to expand...
Click to collapse
First, there is no correct or best rom for a device. You find a rom that has the features that you want. The "best" rom will be different for most everybody. Just flash a rom, try it out. When you get bored, nandroid the current rom, then flash another rom. Repeat until you're satisfied. Some people are just too chicken **** to mess around on android phones, but barring complete idiocy (like flashing an ill-matching rom) or an EFS corrruption, you won't screw anything up.
As for the "explain everything about roms," go onto the home page of the XDA forums. Go into each "general" forum of each phone subforum and I GUARANTEE you will find a newbie [GUIDE] to android/roms/flashing/anystupidnewbquestion.

erikikaz said:
First, there is no correct or best rom for a device. You find a rom that has the features that you want. The "best" rom will be different for most everybody. Just flash a rom, try it out. When you get bored, nandroid the current rom, then flash another rom. Repeat until you're satisfied. Some people are just too chicken **** to mess around on android phones, but barring complete idiocy (like flashing an ill-matching rom) or an EFS corrruption, you won't screw anything up.
As for the "explain everything about roms," go onto the home page of the XDA forums. Go into each "general" forum of each phone subforum and I GUARANTEE you will find a newbie [GUIDE] to android/roms/flashing/anystupidnewbquestion.
Click to expand...
Click to collapse
One more question. What is the adama kernel? I want to install the sonic team rom but don't know if to still the adama kernel. It is optional

I'd recommend against it. Until you know what "normal" behavior is for modded roms, you don't want to convolute the whole thing by modifying the kernel as well.

Basically what you do is make a backup in clockwork mod recovery and then put the rom on the root of your sd card then you reboot back into recovery then do the wipe data/factory reset then you wipe cache then go in to the advanced tab and wipe dalvic cache then go to install zip from sd card and install the rom and then once again wipe cache and dalvic then fix permissions and reboot then your good

Please help. Think I have bricked it!

So, I was relocking my HOX in order to get the OTA JB update from carrier (H3G) in order to use the new Viper ROM.
All went well and managed this. Got re rotted and installed CWM ans Super SU.
However, I read that before installing the JB Viper ROM it was important to do a full wipe. Using CWM i did this. Specifically I did the wipe data/factory reset, wipe cache partition, wipe dalvik cache and format system.
Now my phone is stuck on the white HTC screen. Please help.
Thanks

You formatted system, which basically wiped the rom. Reflash and don't format system.
Sent from something that's BETTER THAN YOURS

You should probably read what bricking your phone means.
Sent from my HTC One X

And don't forget to flash the boot.img file !

Thanks for the quick response and apologies for the basic and wrongly termed questions. Just panicking a little.
How do i get the ROM and boot.img on to the fone? Because it sticks at the white screen the pc doesn't seem to detect it.
Last time i used a stock RUU and followed that process. Will i be able to flash the new Viper ROM instead?
thanks

The boot.img is supposed to be flashed from the PC. To get the Rom into the phone you need to go back to clockworkmod, go into mounts and storage and press the mount usb thing
Edit - to flash the boot.img find a thread about fastboot. Don't worry you'll get there

To get the ROM on the phone boot into cwm and GOTO mounts & storage
Then mount USB storage
It should now be detected as a drive on your PC and you can copy the ROM back over
Sent from my HTC One X using xda app-developers app

Thanks. I did as you guys suggested and was able to install the Viper ROM (used the tweaked stock kernel as recommended in the download).
So have a ROM now but I have no service with my carrier and when I try to connect to wifi it says 'error'. Have I missed or done something wrong?
Cheers

columbo67 said:
Thanks. I did as you guys suggested and was able to install the Viper ROM (used the tweaked stock kernel as recommended in the download).
So have a ROM now but I have no service with my carrier and when I try to connect to wifi it says 'error'. Have I missed or done something wrong?
Cheers
Click to expand...
Click to collapse
While installing the rom, did you choose at the kernel question to keep the stock kernel and modules
Sent from my GT-P5110 using xda app-developers app

Mr Hofs said:
While installing the rom, did you choose at the kernel question to keep the stock kernel and modules
Sent from my GT-P5110 using xda app-developers app
Click to expand...
Click to collapse
Got it resolved. I had used the tweaked kernel and assumed that this was not standard, so when asked about which kernel i was using i said it wasn't the viper one.
So i went back to basics and used the kernel that came with the ROM zip and just flashed both. Working fine now. The only question is whether I could have used the tweaked kernel and answered yes to using the viper version?
Thanks for your help. Felt like I have learned a fair bit in the last 12 hours though!

Well if you flashed a different custom kernel you can answer that with the question so it won't load the stock modules but backs up the custom modules from the custom kernel. This way it won't mess up functionality.
When you use a boot.img without it proper modules it can mess up those things you experienced. Hope i make my self clear

Mr Hofs said:
Well if you flashed a different custom kernel you can answer that with the question so it won't load the stock modules but backs up the custom modules from the custom kernel. This way it won't mess up functionality.
When you use a boot.img without it proper modules it can mess up those things you experienced. Hope i make my self clear
Click to expand...
Click to collapse
Ye, perfectly. cheers

Looking at this thread, makes me realize that there are still a lot of polite helpful guys out there :thumbup:
Sent from my Bladed One X. Blade v5.0.0 is here. Based on RUU and with OTA.

[Q] Need some advice for a noobie

Hi first time posting so please take it easy on the noob. So i just rooted my nexus 7 2013. The main reason was because i wanted to be able to extend battery life and the main thing is that i bought a micro usb host otg cable with power and want to be able to charge as well as power my external hard drive. now i read that elementalx kernel allows you to do that. Would i flash the elementalx kernel first or do i flash a rom before a kernel. I'm pretty confused on where to go to download and which one i flash first.

Welcome to an experience with a great tablet! You want to flash a kernel after a ROM. As the intro to ElementalX says,
Installing a new ROM
If you install a new ROM, it will probably replace this with the stock kernel and will definitely overwrite /etc/init.d/99elementalx and /etc/elementalx.conf so you will lose your settings and certain features. So always reinstall the kernel after installing a ROM.

Pandae said:
Welcome to an experience with a great tablet! You want to flash a kernel after a ROM. As the intro to ElementalX says,
Installing a new ROM
If you install a new ROM, it will probably replace this with the stock kernel and will definitely overwrite /etc/init.d/99elementalx and /etc/elementalx.conf so you will lose your settings and certain features. So always reinstall the kernel after installing a ROM.
Click to expand...
Click to collapse
can you install any rom with any kernel. are their roms that will be more compatible with certain kernels. lastly is flashing a rom and kernel the same process of wiping out all the cache then installing while in recovery mode?

j0hnnyyyy said:
can you install any rom with any kernel. are their roms that will be more compatible with certain kernels. lastly is flashing a rom and kernel the same process of wiping out all the cache then installing while in recovery mode?
Click to expand...
Click to collapse
For the most part there will be two types of ROMs
#AOSP based ROMs
#Cyanogen based ROMs
Each kernel and ROM developer will state in the OP (original post; first post of the thread) which source they built their ROM off of.
As a general rule, flash AOSP based kernels for AOSP based ROMs and Cyanogen based kernels for Cyanogen based ROMs.
Flashing a ROM usually requires a factory reset in recovery (apps will be gone, but your personal data/media will be intact) if coming from another ROM. For example you are on ROM A and want to try ROM B, you must factory reset and wipe caches and flash ROM B.
Once you are on ROM B and if the developer updates ROM B, you can sometimes flash ROM B without the factory reset and only perform the wiping of the caches (this is called a dirty flash).
** IMPORTANT ** Each ROM might have their own special instructions for installation, so always read the first 2 or 3 posts of the thread to get all the important info you need.
If you need help:
1. Check the OP
2. Use the search function in the thread
3. Google it
4. After you have done that and still can't find an answer, post in the respective thread about your problem and provide as much detail as possible.
The reason for this is because threads sometimes get spammed with the same questions over and over again, which clog up the thread unnecessarily. Your question might have been asked before, so searching to see if the question has been asked can also lead you to the answer!
Another thing I've learned is to use the thanks button for those developers whose ROM or kernel you use and like, and people who have helped you. Sometimes donating money to developers to show support isn't a viable option for some, but using the thanks button to show appreciation can go a long way as well!
Hope this helps!
- Another noob

Protomartyr said:
For the most part there will be two types of ROMs
#AOSP based ROMs
#Cyanogen based ROMs
Each kernel and ROM developer will state in the OP (original post; first post of the thread) which source they built their ROM off of.
As a general rule, flash AOSP based kernels for AOSP based ROMs and Cyanogen based kernels for Cyanogen based ROMs.
Flashing a ROM usually requires a factory reset in recovery (apps will be gone, but your personal data/media will be intact) if coming from another ROM. For example you are on ROM A and want to try ROM B, you must factory reset and wipe caches and flash ROM B.
Once you are on ROM B and if the developer updates ROM B, you can sometimes flash ROM B without the factory reset and only perform the wiping of the caches (this is called a dirty flash).
** IMPORTANT ** Each ROM might have their own special instructions for installation, so always read the first 2 or 3 posts of the thread to get all the important info you need.
If you need help:
1. Check the OP
2. Use the search function in the thread
3. Google it
4. After you have done that and still can't find an answer, post in the respective thread about your problem and provide as much detail as possible.
The reason for this is because threads sometimes get spammed with the same questions over and over again, which clog up the thread unnecessarily. Your question might have been asked before, so searching to see if the question has been asked can also lead you to the answer!
Another thing I've learned is to use the thanks button for those developers whose ROM or kernel you use and like, and people who have helped you. Sometimes donating money to developers to show support isn't a viable option for some, but using the thanks button to show appreciation can go a long way as well!
Hope this helps!
- Another noob
Click to expand...
Click to collapse
thanks this helped out a lot and completely understand about not trying to repost questions that have been answered. Just one question if i flash a rom and do a backup. then flash a completely different rom and do a backup for that as well I'm guessing ill have back up for both roms. my question is i use twrp and have the app online nandroid backup, would it be better to go into recovery and backup or is it safe to use the app? Also after flashing a rom is it the same process to flash the kernel?

Yes, it is the same process. Some flashable zip packages are included with the AROMA installer, which is a simple interface to give you options as you flash. Be sure to wipe Cache and Dalvik Cache after flashing roms and kernels.
Don't bother asking for the best Rom and Kernel combo. Try them out for yourself, if you truly want to learn more about what you are doing. Please don't become another user looking for a quick fix. (You called yourself a noobie, so I assume that you intend to learn more.)
Read, read, read! Follow the advice of the users who replied to you! It could save your life! Or, at least, save you a brick.
Most importantly, DON'T PANIC when your device doesn't get past the boot animation. Most likely, you asked something that doesn't work well with the Rom/kernel/MOD combo. Reboot into recovery, wipe, and try again.
Extra tips: clean flash whenever you can. You tend to lose track of stuff that you have flashed when you dirty flash a few times, and not every mod gets removed completely. Backup often as well.
Feel free to come back if you need more help.
_______________________________________
Phone: HTC EVO 4G LTE
Sense 5, S-Off
Tablet: ASUS Nexus 7.2
Rooted, Custom Rom & Kernel
_______________________________________

aarsyl said:
Yes, it is the same process. Some flashable zip packages are included with the AROMA installer, which is a simple interface to give you options as you flash. Be sure to wipe Cache and Dalvik Cache after flashing roms and kernels.
Don't bother asking for the best Rom and Kernel combo. Try them out for yourself, if you truly want to learn more about what you are doing. Please don't become another user looking for a quick fix. (You called yourself a noobie, so I assume that you intend to learn more.)
Read, read, read! Follow the advice of the users who replied to you! It could save your life! Or, at least, save you a brick.
Most importantly, DON'T PANIC when your device doesn't get past the boot animation. Most likely, you asked something that doesn't work well with the Rom/kernel/MOD combo. Reboot into recovery, wipe, and try again.
Extra tips: clean flash whenever you can. You tend to lose track of stuff that you have flashed when you dirty flash a few times, and not every mod gets removed completely. Backup often as well.
Feel free to come back if you need more help.
_______________________________________
Phone: HTC EVO 4G LTE
Sense 5, S-Off
Tablet: ASUS Nexus 7.2
Rooted, Custom Rom & Kernel
_______________________________________
Click to expand...
Click to collapse
thanks. I flashed cleanrom and wiped all the cache before doing so. then i flash elementalx but i didn't wipe cache. one of my friend told me it doesn't really matter that much for kernels but does for roms. he also suggested i wait before rebooting after installing a rom in recovery mode. can you answer any of the part of waiting a certain period of time to let the rom and kernel set?

j0hnnyyyy said:
thanks. I flashed cleanrom and wiped all the cache before doing so. then i flash elementalx but i didn't wipe cache. one of my friend told me it doesn't really matter that much for kernels but does for roms. he also suggested i wait before rebooting after installing a rom in recovery mode. can you answer any of the part of waiting a certain period of time to let the rom and kernel set?
Click to expand...
Click to collapse
Your friend was correct on both accounts.
Wiping cache is not really necessary when flashing kernels.
It it's also usually a good practice to wait a bit before your first reboot after flashing a ROM. From my understanding, it allows the code to "settle"and make sure everything completes in the initial boot.
I'm not too sure about the reasoning, so if someone knows then feel free to chime in!
Sent from my Nexus 4 using xda app-developers app

Protomartyr said:
Your friend was correct on both accounts.
Wiping cache is not really necessary when flashing kernels.
It it's also usually a good practice to wait a bit before your first reboot after flashing a ROM. From my understanding, it allows the code to "settle"and make sure everything completes in the initial boot.
I'm not too sure about the reasoning, so if someone knows then feel free to chime in!
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
he tried explaining to me over text but confused so go into recovery mode wipe all cache. then click install. find file swipe to install then page comes to reboot. on that reboot page is that when you wait or click reboot then wait?

j0hnnyyyy said:
he tried explaining to me over text but confused so go into recovery mode wipe all cache. then click install. find file swipe to install then page comes to reboot. on that reboot page is that when you wait or click reboot then wait?
Click to expand...
Click to collapse
Once you get to the reboot screen in recovery, go ahead and reboot. It's after you reboot that first time that you should wait some time.
Sent from my Nexus 4 using xda app-developers app

Protomartyr said:
Your friend was correct on both accounts.
Wiping cache is not really necessary when flashing kernels.
It it's also usually a good practice to wait a bit before your first reboot after flashing a ROM. From my understanding, it allows the code to "settle"and make sure everything completes in the initial boot.
I'm not too sure about the reasoning, so if someone knows then feel free to chime in!
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Sorry, I didn't know that about Nexus devices. I always wipe caches for my phone, because I will enter a bootloop if I do not do so. This is my first Nexus device, and I'm learning a lot of new things myself.
_______________________________________
Phone: HTC EVO 4G LTE
Sense 5, S-Off
Tablet: ASUS Nexus 7.2
Rooted, Custom Rom & Kernel
_______________________________________

I have a question about backups. I've been researching and reading lot but there are a lot of different opinions . so I installed cleanrom with elemntalx kernel. Would it be best to make a backup in recovery mode or use online nandroid backup. I read something like online nandroid backup works only on certain Roms. Also I have titanium backup but I read that it isn't good to use titanium backups on different Roms? So if I backup through titanium backup and flash let's say a different ROM like cyanogenmod ROM I can't use the backup I created when I had cleanrom flashed?

j0hnnyyyy said:
I have a question about backups. I've been researching and reading lot but there are a lot of different opinions . so I installed cleanrom with elemntalx kernel. Would it be best to make a backup in recovery mode or use online nandroid backup. I read something like online nandroid backup works only on certain Roms. Also I have titanium backup but I read that it isn't good to use titanium backups on different Roms? So if I backup through titanium backup and flash let's say a different ROM like cyanogenmod ROM I can't use the backup I created when I had cleanrom flashed?
Click to expand...
Click to collapse
Nandroid and Titanium backups are used for different purposes.
Titanium backups deal with apps and app settings. They are useful when after flashing a ROM Update. For example, you are using ROM A revision 1 and the developer has posted a new update ROM A revision 2. Since it's usually recommended to clean flash updates of a ROM (read the OP of the ROM thread for further info), this would result in you having to reinstall all your apps and reapply settings and such (which takes time). However with titanium backup, all you have to do is make sure you backup apps/settings when on revision 1. Then after you flash revision 2, you can restore your titanium backup and now you have all your apps and settings.
** IMPORTANT ** Titanium backups should not be used when moving to a DIFFERENT ROM. This may cause problems/incompatibilities.
Nandroid Backups are basically system images. So basically it just takes a snapshot of the current state of your phone, and when you restore it it will be the same as if nothing has changed. This is especially helpful in two situations:
1) when trying different ROMs (i.e. you flash another ROM but don't like it, you can easily switch back via the nandroid backup)
2) when messing with system files and reverting to a previous state (i.e. you are trying to mod your navigation bar or some other customization and decide you don't like it or accidentally messed up. You can use the nandroid backup to revert those changes)
It's also usually helpful to take backups at the appropriate time and name them accordingly. For example, this is the process I take when flashing a custom mod.
1) Nandroid backup before you apply custom mod A. I name the backup "Before applying custom mod A"
2) Apply custom mod A
3) If all goes well and mod A works, I also make a nandroid backup after this and name it "Applied custom mod A"
OR
If custom mod A messes up my phone, I just restore the backup named "Before applying custom mod A"
The reason why I also make a nandroid backup after successfully applying mod A (and decide to keep the mod) is so that I can have an up to date restore point. If you make modifications to the phone and decide to keep them, make an updated nandroid so you don't have to reapply the modifications again.
Sorry for the long wall of text, but hope this helps!

Protomartyr said:
Nandroid and Titanium backups are used for different purposes.
Titanium backups deal with apps and app settings. They are useful when after flashing a ROM Update. For example, you are using ROM A revision 1 and the developer has posted a new update ROM A revision 2. Since it's usually recommended to clean flash updates of a ROM (read the OP of the ROM thread for further info), this would result in you having to reinstall all your apps and reapply settings and such (which takes time). However with titanium backup, all you have to do is make sure you backup apps/settings when on revision 1. Then after you flash revision 2, you can restore your titanium backup and now you have all your apps and settings.
** IMPORTANT ** Titanium backups should not be used when moving to a DIFFERENT ROM. This may cause problems/incompatibilities.
Nandroid Backups are basically system images. So basically it just takes a snapshot of the current state of your phone, and when you restore it it will be the same as if nothing has changed. This is especially helpful in two situations:
1) when trying different ROMs (i.e. you flash another ROM but don't like it, you can easily switch back via the nandroid backup)
2) when messing with system files and reverting to a previous state (i.e. you are trying to mod your navigation bar or some other customization and decide you don't like it or accidentally messed up. You can use the nandroid backup to revert those changes)
It's also usually helpful to take backups at the appropriate time and name them accordingly. For example, this is the process I take when flashing a custom mod.
1) Nandroid backup before you apply custom mod A. I name the backup "Before applying custom mod A"
2) Apply custom mod A
3) If all goes well and mod A works, I also make a nandroid backup after this and name it "Applied custom mod A"
OR
If custom mod A messes up my phone, I just restore the backup named "Before applying custom mod A"
The reason why I also make a nandroid backup after successfully applying mod A (and decide to keep the mod) is so that I can have an up to date restore point. If you make modifications to the phone and decide to keep them, make an updated nandroid so you don't have to reapply the modifications again.
Sorry for the long wall of text, but hope this helps!
Click to expand...
Click to collapse
thanks very helpful so using the online nandroid backup app is the same thing as making a backup in twrp recovery mode