Related
Now, I thought, "hey, I'm not a novice with flashing ROM images, nor am I a *nix or system notice..." So, I decided to cook a ROM using the Online ROM kitchen: http://evo.feeder.pk/
I had run unrevoked3 + unrevoked forever, so I had clockwork recovery.
So, I copied the zipped ROM generated off the online ROM kitchen to the sdcard and then via clockwork installed /sdcard/update.zip (the ROM).
So, everything installed okay, then upon reboot, it seems to go into a reboot loop.
Lucky for me I performed a nandroid backup before installing the newly built ROM, and I'm in them middle of performing a nandroid restore; which I hope will resolve the problem.
1) Will the nandroid restore actually restore my entire phone back to how it was previously?
2) How do I actually install another ROM properly?
These are pretty n00b questions, but any help is appreciated.
Thanks,
Matt
branded said:
Now, I thought, "hey, I'm not a novice with flashing ROM images, nor am I a *nix or system notice..." So, I decided to cook a ROM using the Online ROM kitchen: http://evo.feeder.pk/
I had run unrevoked3 + unrevoked forever, so I had clockwork recovery.
So, I copied the zipped ROM generated off the online ROM kitchen to the sdcard and then via clockwork installed /sdcard/update.zip (the ROM).
So, everything installed okay, then upon reboot, it seems to go into a reboot loop.
Lucky for me I performed a nandroid backup before installing the newly built ROM, and I'm in them middle of performing a nandroid restore; which I hope will resolve the problem.
1) Will the nandroid restore actually restore my entire phone back to how it was previously?
2) How do I actually install another ROM properly?
These are pretty n00b questions, but any help is appreciated.
Thanks,
Matt
Click to expand...
Click to collapse
1) Its supposed to...
2) From what it sounds like, you installed everything okay, just with a bad ROM image. Installing any of the other ROMs already posted should relieve you of your bootloops (as should the nandroid). Unless you try overclocking, which some folks experience bootloops when overclocked over 1.15.
nol3n said:
1) Its supposed to...
2) From what it sounds like, you installed everything okay, just with a bad ROM image. Installing any of the other ROMs already posted should relieve you of your bootloops (as should the nandroid). Unless you try overclocking, which some folks experience bootloops when overclocked over 1.15.
Click to expand...
Click to collapse
Thank you sir. nandroid obviously did restore everything back to normal (wasn't sure to what extent nandroid backed up the device, but it looks like every single thing was backed up).
As for a ROM, I really just want the stock froyo ROM, but rooted... Do you have any suggestions? I can't go OTA since I have clockwork recovery.
Thanks,
Matt
branded said:
Thank you sir. nandroid obviously did restore everything back to normal (wasn't sure to what extent nandroid backed up the device, but it looks like every single thing was backed up).
As for a ROM, I really just want the stock froyo ROM, but rooted... Do you have any suggestions? I can't go OTA since I have clockwork recovery.
Thanks,
Matt
Click to expand...
Click to collapse
I have flashed most of the ROMs here, but I have mostly been using CM6 (Cyanogenmod 6) since it came out. I did try Baked Snack, which is a very nice ROM with a beautiful theme, but it is Sense based and if by any chance you wanted to use a Wiimote for emulators, you cant. It is based off the HTC bluetooth stack, CM6 is not. Its kinda nice to get nightly (experimental) updates to flash if you want to also.
Its all a matter of personal preference, but my BEST results have been with CM6 - benchmark, features, and otherwise.
*E* You also may want to consider posting something like this in the Q&A forum next time...
Uhhhh Ohhhh wrong section
nol3n said:
I have flashed most of the ROMs here, but I have mostly been using CM6 (Cyanogenmod 6) since it came out. I did try Baked Snack, which is a very nice ROM with a beautiful theme, but it is Sense based and if by any chance you wanted to use a Wiimote for emulators, you cant. It is based off the HTC bluetooth stack, CM6 is not. Its kinda nice to get nightly (experimental) updates to flash if you want to also.
Its all a matter of personal preference, but my BEST results have been with CM6 - benchmark, features, and otherwise.
Click to expand...
Click to collapse
Very cool. I'll take a look but I really want Sense, which I'm not sure if CM6 has. Thanks.
Sporkman said:
Uhhhh Ohhhh wrong section
Click to expand...
Click to collapse
Just flag the post and request a mod move it. There's really little reason to post a reply. It seemed like the best place given the descriptions of all the EVO sub-forums.
branded said:
Thank you sir. nandroid obviously did restore everything back to normal (wasn't sure to what extent nandroid backed up the device, but it looks like every single thing was backed up).
As for a ROM, I really just want the stock froyo ROM, but rooted... Do you have any suggestions? I can't go OTA since I have clockwork recovery.
Thanks,
Matt
Click to expand...
Click to collapse
Just get netarchys rooted stock rom and you should be ok... just make sure you get the rooted version
Next time do a wipe of your davik cache before installing any rom
playya said:
Just get netarchys rooted stock rom and you should be ok... just make sure you get the rooted version
Click to expand...
Click to collapse
Thanks playya...
http://forum.xda-developers.com/showthread.php?t=740520
http://forum.xda-developers.com/showthread.php?t=719763
evolol said:
Next time do a wipe of your davik cache before installing any rom
Click to expand...
Click to collapse
http://forum.androidcentral.com/htc...-clockwork-clears-dalvik-cache-just-fine.html
http://forum.xda-developers.com/showpost.php?p=4535156&postcount=4
http://androidforums.com/all-things-root-eris/76110-what-dalvik-cache.html#post710236
And thank you both for ignoring that racist bag of donkey twats that responded earlier.
branded said:
Thanks playya... do you have a link?
http://forum.xda-developers.com/showpost.php?p=4535156&postcount=4
http://androidforums.com/all-things-root-eris/76110-what-dalvik-cache.html#post710236
And thank you both for ignoring that racist bag of donkey twats that responded earlier.
Click to expand...
Click to collapse
no problem quote from last response at that forum
Quote:
Originally Posted by Tamasabian View Post
Ok. So I should just clear it when I do a data wipe to flash a new rom? Will it be a problem if I just do a data wipe and flash a new rom without doing the dalvik cache?
i have had issues when i dont clear the dalvik cache, but never had issues when i do. just cear it, nothing bad will happen and only good can come of it
Sporkman said:
Uhhhh Ohhhh wrong section
Click to expand...
Click to collapse
agreed, theres a section for Q&A
evolol said:
no problem quote from last response at that forum
Quote:
Originally Posted by Tamasabian View Post
Ok. So I should just clear it when I do a data wipe to flash a new rom? Will it be a problem if I just do a data wipe and flash a new rom without doing the dalvik cache?
i have had issues when i dont clear the dalvik cache, but never had issues when i do. just cear it, nothing bad will happen and only good can come of it
Click to expand...
Click to collapse
Cool thank you I will do that and attempt to reflash this ROM that I cooked.
Rocklee99 said:
agreed, theres a section for Q&A
Click to expand...
Click to collapse
Flag the thread and request a mod move it. Glad that you all really want to up your post count so badly, shows real dedication to the forums cleanliness.
Your welcome...now show your dedication to this forum by following instructions & quit cluttering the development section with basic Questions
Not to delf: seems like I fall under a ClockworkRecovery user who's dalvik cache doesn't actually clear. (http://forum.xda-developers.com/showthread.php?t=719763) Kick ass!
I have the same problem as you!!!! I posted it in the wrong forum though so I'll briefly psot my problem and maybe someone can help me. I was trying to update my radio to the latest radio and it worked. I then realized I didn't have a 4g signal and the mod I was using supports 4g. So I tried updating to the latest wimax and then my phone started rebooting. After it boots android it reboots after a bout a minute or 2.
I FIXED it with a nandroid restore which had my 2.1-1 back up which I made during the idiot proof guide. So thinking that I can always use that backup as a restore I tried re-installing the radios because I don't see how they could not work on my phone and thought maybe I had a corrupt file, but voila my phone started rebooting again, but this time nandroid restore tells me to fix it via adb restore, BUT my usb isn't working either. So I'm stuck and have no idea on how to get this thing to load my restore. Any help would be appreciated.
I didn't read you're reply. But after installing RA, I think I'll be alright...
Here's the deal from start to finish...
download and install the android SDK
install all the necessary drivers
restart in recovery mode ( adb restart recovery or hold volume down when powering on the device)
use adb shell to access the shell while the device is in recovery
1) install RA recovery using adb method (http://forum.xda-developers.com/showthread.php?t=705026) This may or may not be okay with or without running unrevoked first... not sure if flash_image was placed on the device by unrevoked.
2) reboot into recovery
3) flush dalvik cache via RA recovery.
4) flush cache via RA recovery.
5) use adb push to copy a downloaded ROM zip to /sdcard/update.zip (using RA recovery to mount the /sdcard/ partition)
- I've downloaded http://forum.xda-developers.com/showthread.php?p=7512117
6) Install update.zip from sdcard in RA recovery
- After booting into the new ROM one time, I allowed it to start and configured... then performed 3,4,5 against flashing a new kernel: http://forum.xda-developers.com/showthread.php?t=719763
And that should be that. I'm currently downloading the ROM, so I don't know how it'll be.
I rooted my EVO through UnRevoked and Tried to Load Up the Revolution Rom.
But All it does is replay the start up animation. What Do I do? I know I am a noob but I really need to get this phone back to working.
Thanks,
Justin
Pull your battery out. Hold down power button and volume down at the same time. Select recovery option. When it boots into recovery make sure you wipe cache, wipe David cache. Flash Rom and see if that works.
Sent from my PC36100 using XDA App
Boot into recovery /power on while holding volume down/
Wipe dalvik and data both twice. Maybe also try /system format under advanced I think. Sorry I use RA recovery
If that don't work boot back into recovery and wipe dalvik and restore the nandroid backup that you should have made.
Good luck and this should be in q&a
mym3isfaster said:
I rooted my EVO through UnRevoked and Tried to Load Up the Revolution Rom.
But All it does is replay the start up animation. What Do I do? I know I am a noob but I really need to get this phone back to working.
Thanks,
Justin
Click to expand...
Click to collapse
Take a deep breath, the good news is, you can recover from this. Do what these other guys have suggested and let us know if you get back to a working phone.
Did you also run unrevoked forever?
Thread moved to Q&A.
I first want to say thanks for replying to my post. I also want to say sorry for posting in the wrong section of the forum. But I tried what you guys suggested and it didn't work. I can't seem to get past the Revolution load animation, it just keeps playing over and over. Does this mean I just Bricked my phone?
maybe you got a bad zip. try a fresh ROM, flash it and see what happens. make sure you wipe EVERYTHING twice just for kicks before you do this. www.geekfor.me
mym3isfaster said:
I first want to say thanks for replying to my post. I also want to say sorry for posting in the wrong section of the forum. But I tried what you guys suggested and it didn't work. I can't seem to get past the Revolution load animation, it just keeps playing over and over. Does this mean I just Bricked my phone?
Click to expand...
Click to collapse
OK, here we go. I recommend you do this "because I know it work", deep breath, here we go.
Prerequisites: First I am assuming you have both Root and Nand-Off, if you need help checking let me know.
Some Questions:
1. do you have the Android SDK install on your PC?
2. What OS are you running on your laptop/desktop?
3. What recovery are you using?
4. Do you have a nandroid backup, one from before you flashed the ROM?
Answer this and I will help further.
Im going to say bad zip...redownload and try again
Sent from my PC36100 using XDA App
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
Ok I wrote this for the OP of my ROM because the issues some people were PMing me about were just plain out dumb, This phone has been out quite a long time and still almost every thread I goto, you got people flashing in way's I didn't even know were possible and posting weird issues that were not being reproduced by the community. so I'm just gonna post this guide for all the developers sake and in hopes the people that actually need this information, receive it before posting and clogging up development threads
If you're having issues on rom's that no one else is reporting, or the DEV has not reproduced on his phone, read the following.
1) Full wipe
2) Do not restore System data or data from CWM
3) Do not dirty flash from other ROM's
4) When was the last time you did a odin to stock? this is important in my opinion and I'm not saying you need to do one but I just want to explain that custom zip's that I make and other dev's make in the shape of "roms" only affect
a few partitions on your device, other's do not get touched and can get messy/corrupt over the months (This explains why the GPS icon disappears in some peoples cases during rom switch) and this is why I get posts in this thread about people wondering why their baseband hasn't been updated after flashing my rom when my post states "MF1"
With this being said my personal rule of thumb is to odin to stock latest and then boot into stock recovery and factory reset, wipe cache/dalvik (BACKUP YOUR SD CARD TO YOUR COMPUTER), this gives your phone fresh partitions everywhere, a fresh system to root and the latest bootloader (which you need for any AOSP 4.2 rom). This is also a good time to unlock your phone if you have not already, then reroot and install custom recovery, update the recovery if need be and flash again on a brand new system. here are my steps
1) backup all user apps and data with titanium backup, DO NOT BACKUP SYSTEM APP'S
2) backup internal storage onto PC
3) Odin to stock latest
4) wait for phone to boot then reboot into stock recovery and full wipe and clear all cache
5) reboot and root the phone and custom recovery
6) flash away and put what you need on your internal storage back onto your phone via usb, see my 2nd set of instructions below
this fixes more issues then you will realize. some of the way people flash rom's on XDA and complain to me with problems is rather funny considering I have the install instructions in the OP, not to mention many of you rooted your phone when you first got it in the ICS 4.0.4 day's and haven't done an odin to stock jellybean to update all your partitions including your bootloader, now I will go over my every day flashing step's.
1)backup all USER APPS/DATA with titanium backup, DO NOT BACKUP SYSTEM APP'S (skip this if you did a odin flash to stock)
2)reboot recovery
3)nandroid (skip this if you did a odin flash to stock)
4)factory reset, wipe system, wipe both cache/dalvik
5)install rom
6)boot system
7)*(OPTIONAL) reboot to install a kernel now if needed, always wipe cache/dalvik and fix permissions after installing a kernel
8)setup phone and download titanium backup from the market
9)restore all user apps and data (you will have to put the titanium backup folder that is backed up on your computer back onto your internal storage via usb first)
Every 6 months, backup internal storage to PC and I odin to stock, much like formatting a computer
6 months is actually a long time considering how much I flash, but this device can take a beating let me tell you =P
I DO THIS WITH EVERY ROM I INSTALL, AOSP or TW
Great info, that is actually my same process when I have an issue with anything
Good read. A lot of common sense for seasoned flashers, will be great for people who are unsure.
Sent from my SGH-T999 using xda app-developers app
KorGuy123 said:
Good read. A lot of common sense for seasoned flashers, will be great for people who are unsure.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
thanks man, hoping this gets a sticky.
Danvdh said:
thanks man, hoping this gets a sticky.
Click to expand...
Click to collapse
I'll add it to my sticky
Galaxy S3 / AoCP / V4A / Turbocharged
s3 unrooting issues
I have been having some big problems with unrooting my telus SGH I747 Galaxy s3. I have flashed the stock rom using odin, did a factory reset and wiped cache and everytime i reboot it loads up the same roms i had on there at first. I have had a lot of issues with roms as well such as slow messaging times, echoing voice calls using AOKP and when i use an AOSP rom i cant connect to my phone carriers data connection at all. I read this form and decided its probably a good idea to re root as you said due to updates or whatever else but now im runing into this issue. I have ask on other forms and no one seemed to have heard of this issue. If anyone has any ideas or knows a fix i would really appreciate the help.
Custom ROM data issue
dannyteo14 said:
I have been having some big problems with unrooting my telus SGH I747 Galaxy s3. I have flashed the stock rom using odin, did a factory reset and wiped cache and everytime i reboot it loads up the same roms i had on there at first. I have had a lot of issues with roms as well such as slow messaging times, echoing voice calls using AOKP and when i use an AOSP rom i cant connect to my phone carriers data connection at all. I read this form and decided its probably a good idea to re root as you said due to updates or whatever else but now im runing into this issue. I have ask on other forms and no one seemed to have heard of this issue. If anyone has any ideas or knows a fix i would really appreciate the help.
Click to expand...
Click to collapse
So scrap the unrooting issue i have that figured out now, i just reinstalled the rom and again it doesnt have data, it is the deadly venom rom, anyone else that i know who is using this rom has absolutely no problem. I have tried a few fixes i have found via youtube, google, etc.... but none were successful. If anyone knows a fix or has any ideas please let me know.
I have an I747M S3 from a friend and trying to get it back to stable stock. It had lost it's IMEI and some NVdata corruption but I was able to resolve that searching the forums, But it has issues with apps crashing and rebooting quiet frequently. It can sometimes go feeling pretty stable ofr awhile then just kind of blows up. I have cleared away the flash counter and restored factory stock images from Odin and Keis, still having the issues. Is there a partion or something that could be getting missed? Or possible further problems related to the NVdata issues?
if you have any ideas I would appreciate it.
I used twrp to back up system, data, and boot, should I still use titanium back up to back up anything else, or is that enough to be relatively safe?
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