Database Info

Stuck in boot loop every time I flash a rom

I've flashed a few roms now (masters stock rooted voodoo versions of nexus s firmware) and every time I do the boot logo just keeps on going until I do a battery pull and reboot, and then it's ok.
It's not a problem, I just wondered why this happens??

did you wipe dalvik, factory settings, cache?
did you change the kernel?

zephiK said:
did you wipe dalvik, factory settings, cache?
did you change the kernel?
Click to expand...
Click to collapse
No. These roms don't wipe anything and I don't want to lose my stuff. I don't think you are meant to wipe with them either.

buachaille said:
No. These roms don't wipe anything and I don't want to lose my stuff. I don't think you are meant to wipe with them either.
Click to expand...
Click to collapse
I was asking if YOU did wipe them because if you're going from one ROM to the other ROM you are supposed to wipe.
You lose your settings and apps. Back them up using Titanium Backup (Or any other related app).
Or.. better yet, just perform a nandroid backup. After that, wipe those 3 and reboot. See if the problem is resolved, if it is then you already know. If not then nandroid restore.

If you're going from one ROM to a completely different ROM made by someone else, you have to wipe data/factory settings!
If you're flashing an updated version of the current rom you're using, wipe cache/dalvik-cache.
If you're flashing different roms every other day, go buy Titanium Backup to backup your apps/settings.
And uh what ROM are u flashing where "you're not meant to wipe"
-Nexus S

nxt said:
If you're going from one ROM to a completely different ROM made by someone else, you have to wipe data/factory settings!
If you're flashing an updated version of the current rom you're using, wipe cache/dalvik-cache.
If you're flashing different roms every other day, go buy Titanium Backup to backup your apps/settings.
And uh what ROM are u flashing where "you're not meant to wipe"
-Nexus S
Click to expand...
Click to collapse
I am new to this so I'm still getting my head around it.
From stock I went to the rooted voodoo version of this - http://forum.xda-developers.com/showthread.php?t=971690.
From there I went to the stock rooted version of this - http://forum.xda-developers.com/showthread.php?t=979851
In both cases it says:
Rom Information:
Does it wipe: No
Does it flash the radio: Yes
So since they don't wipe, I assumed I shouldn't wipe anything, but it looks like I was wrong. From your post it looks like I should have wiped the cache and dalvik cache. I know how to do this in CW but I've never done it and my roms are working fine.
So next time master releases an update I gather I should wipe cache and dalvik cache yeah?
Also, when I do this will it remove any of my settings or apps?
Hope you can answer these questions, and thanks for advice so far.
<<edit>>
Just did a bit of googling and it looks like you don't lose settings when you wipe dalvik cache and cache, so what does actually get removed.

There is a thread stickied in development called ref roms themes and kernels. It gives step by step directions on how to flash all three including what should be wiped. Check it out
Sent from my MattedBlues CM7 Nexus S from the XDA Premium app.

It says:
Does it wipe: No
Does it flash the radio: Yes
Click to expand...
Click to collapse
because its saying that the ROM doesn't wipe. Some ROMs are built in a way so that it automatically wipes your phone to ensure best performance. The creator is just saying that it doesn't do that BUT you need to wipe. The keyword does and need are two different things. The basic concept between going from 1 ROM to another (unless its the same ROM series) requires a wipe in all three: dalvik, cache, factory. If you're going from the same ROM to a newer version and encounter bugs, its best if you wipe.
I'm a more advanced user when it comes to Android since the first Android phone. I know what I'm talking about. When you go from stock ROM to another, its going to have bugs if you don't wipe.
If you're using Axura 1.1.1.0 and its fine, and he releases a new version. You can flash without wiping (but you can wipe cache & dalvik to be safe; none of your settings will be wiped). Wiping factory settings is the only one that will wipe your settings / apps.
If you're going to be a flasher, its best if you purchase Titanium Backup Pro (or MyBackup.. but I highly recommend Titanium Backup). Use this program and it will save all of your apps + settings to them. Just don't use it to save SYSTEM apps/files because it will cause FCs.
Dalvik Cache / Cache.. its nothing you need to know in particular. It's just removing cache that your phone set up to increase speeds. It just wipes them and gets the Android system to re-establish them. So no caches from the previous ROM will carry over onto the new one.

EDIT: n/m..............

zephiK said:
It says:
because its saying that the ROM doesn't wipe. Some ROMs are built in a way so that it automatically wipes your phone to ensure best performance. The creator is just saying that it doesn't do that BUT you need to wipe. The keyword does and need are two different things. The basic concept between going from 1 ROM to another (unless its the same ROM series) requires a wipe in all three: dalvik, cache, factory. If you're going from the same ROM to a newer version and encounter bugs, its best if you wipe.
I'm a more advanced user when it comes to Android since the first Android phone. I know what I'm talking about. When you go from stock ROM to another, its going to have bugs if you don't wipe.
If you're using Axura 1.1.1.0 and its fine, and he releases a new version. You can flash without wiping (but you can wipe cache & dalvik to be safe; none of your settings will be wiped). Wiping factory settings is the only one that will wipe your settings / apps.
If you're going to be a flasher, its best if you purchase Titanium Backup Pro (or MyBackup.. but I highly recommend Titanium Backup). Use this program and it will save all of your apps + settings to them. Just don't use it to save SYSTEM apps/files because it will cause FCs.
Dalvik Cache / Cache.. its nothing you need to know in particular. It's just removing cache that your phone set up to increase speeds. It just wipes them and gets the Android system to re-establish them. So no caches from the previous ROM will carry over onto the new one.
Click to expand...
Click to collapse
That is a very helpful post and clears a lot up. Many thanks. Looks like I had better do it again and do it right this time.
I've got titanium backup. Bought it after I rooted, but never restored with it yet. Also, thanks for the info about no saving system files with it, as I currently do have it setup to backup all user apps and system data, so I will have to change that. I gather I should just change it to all user apps??

buachaille said:
That is a very helpful post and clears a lot up. Many thanks. Looks like I had better do it again and do it right this time.
I've got titanium backup. Bought it after I rooted, but never restored with it yet. Also, thanks for the info about no saving system files with it, as I currently do have it setup to backup all user apps and system data, so I will have to change that. I gather I should just change it to all user apps??
Click to expand...
Click to collapse
Backup all user apps is the one you want to do. You can backup bookmarks using Google sync or a app known as BookmarkSB
If you have system apps backed up, delete all backups using batch and reapply user app backup

zephiK said:
Backup all user apps is the one you want to do. You can backup bookmarks using Google sync or a app known as BookmarkSB
If you have system apps backed up, delete all backups using batch and reapply user app backup
Click to expand...
Click to collapse
Thanks for your help. I reflashed the rom and I did it properly this time. Had a bit of a problem with TB restore as I'm a noob but Joel from TB answered an email I sent him very quickly and I got it sorted (thanks joel).
How long does it take to flash a rom once you get good at it? Took me a while tonight because of mistakes.
Sent from my Nexus S using XDA App

buachaille said:
Thanks for your help. I reflashed the rom and I did it properly this time. Had a bit of a problem with TB restore as I'm a noob but Joel from TB answered an email I sent him very quickly and I got it sorted (thanks joel).
How long does it take to flash a rom once you get good at it? Took me a while tonight because of mistakes.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
I can usually get from booting into recovery to having a usable device with most everything set up in about...10 minutes? Assuming I already downloaded the ROM lol sometimes those mirrors are slooooooow.

[Q] Titanium backup question

Searched and didn't find this specific question or anything close - so I'll post
I've been flashing roms a lot now that I've got the hang of it, but I think I was creating a problem for myself with titanium backup, which I think I've maybe now solved, but I'm not absolutely sure.
On the last couple of nighlies of CM that I've flashed I've been getting unfixable FC of the phone app (rom manager fix permissions didn't fix it and neither did wiping dalvik cache).
So I flashed ns-collab and I like it, but today I got the same FC problems and had to restore my nandroid to get the phone working (I was at work).
NS-collab is meant to be stable so I was starting to think that it's not the roms that are at fault but something I'm doing, and I had a feeling it was what I do with TB. So here is exactly what I do when I flash a new rom.
____________________________
I have TB set to "backup all user apps". That's it - no system data.
Before flashing the rom (even if it's just an update) I clear data, cache, and dalvik cache.
When I've got the new rom flashed I do not allow google backup to restore my stuff as I want it done with TB.
In TB restore I run "Restore all apps with data". When I do this I select the app+data checkbox in TB before clicking "Run the batch operation".
___________________________
So, I had a look at the apps that get restored when I run TB "Restore all apps with data", and I noticed there is quite a lot of android stuff in there like the dialler and lots of other services that are part of the android os and don't need restored with TB really.
I've just flashed the updated version of ns-collab and I removed all these android services from the TB restore before I ran it so I'll see if any problems crop up now.
But my question is, was I causing the phone to be unstable by allowing these android services to be restored by TB. Remember I did not select to restore system data, but I am wondering if system data was restored anyway because there were android apps in the list and I had the app+data option selected.
Hope the above isn't confusing and any advice will be appreciated.

Lot of information but I say you found your problem yourself.

I have not had issues in the past restoring: bookmarks, contacts/calls storage, SMS/MMS/APN Dialer storage, SMS/MMS PREFS etc.
I do think you are giving yourself a little extra work than needed. It is not necessary to do a data wipe before updating a ROM, wiping cache and dalvik cache should be sufficient and a lot of people don't even do that. Of course a good clean wipe every now and then is good and gives you that warm fuzzy feeling inside like after you change the oil in your car
In general, I do not recommend a full batch restore like restore all apps and data. I find when restoring with TB it is a good time to clean up and only restore the apps your really want back on your phone. I also do a batch restore, de-select all and just go down the list and pick out the stuff I HAVE to have.

irishrally said:
I have not had issues in the past restoring: bookmarks, contacts/calls storage, SMS/MMS/APN Dialer storage, SMS/MMS PREFS etc.
I do think you are giving yourself a little extra work than needed. It is not necessary to do a data wipe before updating a ROM, wiping cache and dalvik cache should be sufficient and a lot of people don't even do that. Of course a good clean wipe every now and then is good and gives you that warm fuzzy feeling inside like after you change the oil in your car
In general, I do not recommend a full batch restore like restore all apps and data. I find when restoring with TB it is a good time to clean up and only restore the apps your really want back on your phone. I also do a batch restore, de-select all and just go down the list and pick out the stuff I HAVE to have.
Click to expand...
Click to collapse
I think you are right about me giving myself work. Because I'm still a noob I'm still over cautious I think.
Maybe I'll try doing it your way. Sounds sensible.
Anybody know definitively whether me restoring everything via all apps and data would have contributed to the FCs I have been getting?

buachaille said:
I think you are right about me giving myself work. Because I'm still a noob I'm still over cautious I think.
Maybe I'll try doing it your way. Sounds sensible.
Anybody know definitively whether me restoring everything via all apps and data would have contributed to the FCs I have been getting?
Click to expand...
Click to collapse
Did you try fixing permissions? I only use the batch for Backup all user apps.
Backing up bookmarks.. I use BookmarkSB and SMS (i know theres a app for that) but i use GVoice so i dont need it

I've never had a problem restoring user apps with data. Instead of restoring all, choose restore missing user apps with data or something like that.
Although, I've had problems restoring SMS and certain data for system apps on the NS. Can't figure out why it doesn't work but whatever.
Sent from my Nexus S using XDA App

I would suggest you install app2sd & move your application to the sd-card. Each time you flash a new rom just wipe the /cache, dalvik-cache and battery stats. This is all you would ever require.

Thanks for all the replies. Quite a few suggestions there which I will try out.
Didn't have any FC problems at all at work today, so I'm hoping my more cautious restore last night might have done the trick.

buachaille said:
Thanks for all the replies. Quite a few suggestions there which I will try out.
Didn't have any FC problems at all at work today, so I'm hoping my more cautious restore last night might have done the trick.
Click to expand...
Click to collapse
Yeah FCs happen when you backup system apps / bookmarks etc. It could interfere

Help a confused guy out about rom flashing?

So I really want to flash a new ROM on my AT&T One X but am a bit confused on how to do it so as its as qucik and painless as possible. I have titanium backup and I have backed up all my apps & system data using it. I also am on a mac so I have the one click CID tool that came out for mac. What is the best order of steps to follow so I can restore my phone on the new rom to the same settings and apps and what not that it is in now?
I should mention I am on 1.73
If some kind soul could help me that would be great as I have searched and read all the info on here and my head is spinning

Try this thread I don't know of a more detailed tutorial
http://forum.xda-developers.com/showthread.php?t=1678308
Sent from My Nocturnalized Beast

Ok I have that and read i actually had that the other day but more importantly the question is how do I do this so I dont lose any of my data?
Also I am not trying to install 1.85 I am trying to flash King Cobra ROM.
Hope that clears things up

***Shameless self promotion *** My Index thread can help answer a lot of your questions.
http://forum.xda-developers.com/showthread.php?t=1671237
In particular, there is a tutorial on how to keep your data through the bootloader unlock process. But don't know how this would work on Mac.
http://forum.xda-developers.com/showthread.php?t=1671746
But its actually not recommended to keep user data when moving to new ROMs. Doing so can cause random and severe bugs, which will force you to wipe data and reflash anyway. Moving between one version of a particular ROM (for instance, one version of King Cobra to a newer one) is usually ok to keep data, unless the dev says otherwise. But going to a new ROM, I always wipe data, cache and Dalvik.
You can backup your app data using Titanium. But I would suggest doing the rest of the setup (settings, etc.) fresh after you flash the ROM. I would also backup the Titanium folder (and anything else on the internal SD that you don't want to lose) on your Mac before flashing anything, as there have been random cases of corrupted data from CWM, and possibly TWRP also.
Again, I can't help with Mac in particular. But in general you need to:
1) Backup any data you want to keep on your Mac
2) SuperCID
3) Unlock bootloader
4) Install recovery
5) Download ROM onto internal SD (or copy it there from your Mac)
6) Backup current ROM
7) Wipe data, cache and Dalvik
8) Flash the ROM
Research the guides in Development to learn the details of each step, and come back on here if you have specific questions.

All set guys now running King Cobra!
Thanks for the help!

Backups before Flashing

Hello fellow ROM-flashers!
What do you do too keep your setup when flashing, what do you backup? settings, data, accounts and so on.
Is there any good way to backup and keep your settings, and so on... or do you have to redo all that after you flashed a new ROM?
Perhaps its recommended to do it all over again and again? ... I use Pandoriam 5.7 and are happy with it :good:
But then again 6.0 around the corner I sure I want to have the latest update. Dont we all?
I find myself redo my phone settings more then I actual use my phone

Wouldn't it be awesome if there was a way to update it as you do with a stock ROM.. so you didnt had to wipe all when you go from 5.7 to 6.0 for example.
I guessing there are a lot of reasons why this isn't really a valid option... but would be great

Wrekk said:
Wouldn't it be awesome if there was a way to update it as you do with a stock ROM.. so you didnt had to wipe all when you go from 5.7 to 6.0 for example.
I guessing there are a lot of reasons why this isn't really a valid option... but would be great
Click to expand...
Click to collapse
..TitaniumBackup....
https://play.google.com/store/search?q=titanium+backup
in free version no batch backup / restore...
backup system+app data
wipe system / data / cache / davlik cache in cwm - flash new rom... installl TB ... restore all.... finish

This should be in the Q and A forum
But yeah, buying titanium backup is the best purchase you'll ever make if you often flash ROMs with full wipes. The batch backup/restore process is brilliant, I have it also saving my backups to dropbox so if anything happens to my phone, I have a copy there too (4G is awesome for this).
I've also found the best launcher is Nova, using Titanium Backup to backup and restore Nova, I don't even have to setup my homescreen again (4 sized widgets, 4 folders, completely customised - you can see it in the homescreen thread in the Q and A forum), even the widgets are there after a full wipe which wasn't possible with other homescreen launchers. The only thing I setup fresh each time is my work exchange account.
By the way, you mostly DON'T have to wipe between ROM versions. I always do because that's how I like to do things (and due to the above I have the process sorted), but most poeple don't..

When updating ROM's - I do a Nandroid + SMS/Call log backup + Titanium backup of all user apps +data.
I the upgrade the ROM over exissting without any data/cache wipe. If I run into FC's after updating the ROM, I either restore my Nandroid or do a clean install of the new ROM and restore apps + settings from my Titanium backup.

I use online nandroid to backup full data. Works a treat and you can use your phone while backing up!

[GUIDE]: To transfer all app data + settings + all user configuration from old os to

TWRP METHOD ONLY
HOW TO TRANSFER ALL APP DATA + SETTINGS + ALL USER CONFIGURATION FROM PREVIOUS ANDROID OS TO NEW ANDROID CUSTOM ROM
Greetings, i have Great info for everyone for RESTORING User App + Data as it was before from TWRP. I used pixel experience 10 official rom for 2 days and after flashing it i restored my app data from titanium backup which after that took time to configure everything which is a bummer hectic to configure phone settings as per our likes and install & configure every app. Official Pixel 10 showed me little lags and slower performance compared to MIUI 11. Caution: TWRP DOES NOT BACKUP users Internal Storage data so make sure you backup your internal storage data like Photos, videos anything in internal flash storage backup somewhere else.
Now here's what i did, i rebooted to TWRP > Backup > Backed-up system image(incase anything goes wrong), boot and specially DATA (All user app + its data + settings stored in this). Make sure you backup data in external storage like memory card or OTG flash drive.
Then i installed EvolutionX Pixel 10 latest version released on 5th Dec after complete format, flashed DFE, Flashed Drunk Kernel, Flashed Magisk and wiped cache & dalvik cache. Then rebooted phone and configured the new os startup> rebooted to TWRP > Restore > selected only DATA and restored it > BOOTED SUCCESSFULLY WITH SAME APP DATA AND SETTINGS including same wallpaper and everything was same.
WARNING: After you boot your fresh backed up data & it asks for password after boot & gets stuck then reboot to TWRP and Install ResetScreenLock.zip (find it in XDA or CLICKHERE and boot successfully.
You can ONLY do this on SAME VERSION OF ANDROID OS. Like i had Pixel Experience 10 Official so it's data can only be transferred to any other Pixel Experience 10 custom Rom. I'm not sure about transferring Data from different versions of Android example android 9 Pie TO android 10 Q let me know if it's possible.
I didnt backup from titanium backup because usually restoring backup from titanium freezes & it cannot restore specific User App data to a new rom and it was a headache restoring apps manually after titanium backup didn't restore half of my apps & its data
You are welcome have blessed day. God Bless:laugh:

This is twrp 101. But mind that every problem and every force close you will encounter (and you most probably will) is going to be because of this.
Phone overheating, battery drain, apps crashing etc.
Developers suggest clean flashing for a reason, old ROM data interference with the new ones.
What you did is called dirty flashing and is the same as wiping system, davlik, cache and flashing ROM and gapps.
Your data backup is very useful when you want to try a new rom, clean flash it and then want to go back to your previous one.

sotosgolf said:
This is twrp 101. But mind that every problem and every force close you will encounter (and you most probably will) is going to be because of this.
Phone overheating, battery drain, apps crashing etc.
Developers suggest clean flashing for a reason, old ROM data interference with the new ones.
What you did is called dirty flashing and is the same as wiping system, davlik, cache and flashing ROM and gapps.
Your data backup is very useful when you want to try a new rom, clean flash it and then want to go back to your previous one.
Click to expand...
Click to collapse
Not a single problem till now, No phone heating, no abnormal battery drain, not a single app crashed. Phone is working perfectly smooth and not even a mili second lag. Basically Technically what actually i did is transfer my previous Pixel 10 data to New Pixel 10 data so there are no changes at all in Data.
You can test it if you follow my steps exactly you will successfully transfer Data to any New custom rom, i have tried. Just make sure the data you want to transfer is between same base roms like i transferred from Official Pixel 10 TO EvolutionX Pixel 10, similarly you can transfer to any Custom rom that is based on same base rom which you are using currently.
NOTE: Before you go & do TWRP backup, make sure you do complete system cleanup, app cleanup, corpse cleanup from SD Maid Pro and then do clean backup from TWRP
After you flash new custom rom make sure you boot it and go through its initial startup process then go back to TWRP and restore rom and flash ResetLockScreen.zip
Enjoy

eladamcain said:
Enjoy
Click to expand...
Click to collapse
I'm using custom ROMs since 2014, i have certainly enjoyed the issues i'm describing above.
Dirty flashing causes a lot of unwanted stuff.
Anyway, that's my two cents.

sotosgolf said:
I'm using custom ROMs since 2014, i have certainly enjoyed the issues i'm describing above.
Dirty flashing causes a lot of unwanted stuff.
Anyway, that's my two cents.
Click to expand...
Click to collapse
If you don't know what you are doing, you will face problem. This method works perfectly IF you are on Stock Rom and it is not bloated and you are transferring your data to custom rom who's made from the same base stock os. Example heavily bloated and transferring its settings to a different setting os is going to create instability its common sense. Backing up non bloated stock rom data to custom rom works

You saved my life... I tried a similiar method but it didn't work. But this... this saved my LIFE
(2FA Problems...)