Develop Bugs

Nandroid failure help!!!!!

when i try to restore my nandroid it says error flashing boot image please help

That happened to me once. I think the actual file was corrupt because I was able to restore from a different nandroid. Do you have any others saved that you can try?

I don't remember that exact error message (I actually think it might have been different), but a very similar (or identical) error can occur of on backup/restore you have a low battery, low disk space or have renamed the directories.

What recovery are you using?
Do you have other backupsyou can try?

Are you trying to restore a clockwork backup with ra, or an ra backup with clockwork?
Sent from my blah blah blah blah

Once you get through this (best option, use one of the other Nandroid backups if you have them), download and install Titanium Backup, I trust it more than Nandroid's backup. Heck use both before you install ROMS and make any major changes. Just a thought...

rcbarr said:
Once you get through this (best option, use one of the other Nandroid backups if you have them), download and install Titanium Backup, I trust it more than Nandroid's backup. Heck use both before you install ROMS and make any major changes. Just a thought...
Click to expand...
Click to collapse
Wait, what?
It's not like you have a choice to do one or the other, nand and titanium do totally different things. You should always do a nand backup before flashing anything, regardless if you use tb...unless I misunderstood what you're saying...
Sent from my blah blah blah blah

I am having this same problem. i switched from the regular sense rom to CM 6 rs2. i can load cm6 backups all day long but my sense rom gives me an error when i try to load it saying "clockwork mod error while flashing boot image!". Both nandroid backups were made with clockworkmod. I had to downgrade my version of hboot to install cm6. I am wondering if i need to upgrade it again to load my original sense rom or am i wrong in thinking this?

DaKlown said:
I am having this same problem. i switched from the regular sense rom to CM 6 rs2. i can load cm6 backups all day long but my sense rom gives me an error when i try to load it saying "clockwork mod error while flashing boot image!". Both nandroid backups were made with clockworkmod. I had to downgrade my version of hboot to install cm6. I am wondering if i need to upgrade it again to load my original sense rom or am i wrong in thinking this?
Click to expand...
Click to collapse
OP didn't give as much detail as you - good example of how details help.
You can only restore backups you made with the same version of hrboot. You can't restore a .79 backup while running .76 (which I'm pretty sure is what you downgraded to in order to load cm6).

Now I need to find flashable zips of both hboots so I can switch between cm6 and sense. I so miss my 4g lol. Thanks for your help!

I upgraded hboot to .79 and still got the same error. Funny thing is that my cm6 loaded fine and my hboot is still reading .79 anyone have any clue as to why sense wont load and why cm6 loaded on a different hboot?

did you ever get this figured out? i am in the exact same boat.
i rooted with unrevoked 3.21, this went well
i backed up oem sense in recovery via nandroid, this worked, i wiped and restored from this backup just to test, again the restore worked just fine.
later i tried to flash cm6 but all arrows pointing towards not having the right hboot. i dont remmeber what i had but i needed to got to eng boot .76.2000, which i finaly got figured out and was able to flash to cm6.
at this point cm6 loads and runs juts fine, i decided to boot to recovery and do a backup via nandroid, infact i did two of these back ups. i wiped my phone and did a restore just to test these back ups.
heres my problem: just for the fun of it i thought i would try to use the first nadroid back up to restore (that had stock sense installed at the time) and it wont flash. it says something about:
"Checking MD5 sums…
Erasing boot before restore…
Restoring boot image…
Error while flashing boot image!"
i thought i found a fix: i need to "Switch .76 with .79", this still did not allow me to restore from my oem sense backup, i get the exact same error.
i found another potential fix pertaining to going back to .93.
i feel like i dont know enough about what i am doing and im abit scared to try this as i dont see much info on this method.
basicaly i'd lile to be able to go back and forth between stock and custom for a while and also i'd like to be able to use nandroid backups to quickly do this.
am i approaching my problem correctly pertaining to the hboot thing? and can i just drop the .76,.79, 93. images in and out of the pc36image.zip file that i will place on root on my sd card with out anything else in this zip and expect it to just work?

i was able to achieve my objective and then some. now i can restore to a cm6 or a oem rom in a matter of maybe 5 or ten minutes.
maybe it wasn't directly the way i wanted to do it but i think it was similar enough that it worked without me understanding what i was doing therefore keeping me out of the mix which is why it probably worked.
what ui did was i found a ruu.exe for 3.29, i downloaded it and ran it
once it was done i ran unrevoked to get root again and the boot loader installed, i think the .97 boot loader was key here, but i dont know.
then i booted to recovery and did a nandbackup
then i did a nand recovery to my older backups of cm6-success
then i did a nand recovery of a older oem 3.29 sense rom- success
im sure that i rambled on here and i never really knew what i was doing but i was able to do what i set out to do and then some. if only we could dual boot roms.....

potna said:
i was able to achieve my objective and then some. now i can restore to a cm6 or a oem rom in a matter of maybe 5 or ten minutes.
maybe it wasn't directly the way i wanted to do it but i think it was similar enough that it worked without me understanding what i was doing therefore keeping me out of the mix which is why it probably worked.
what ui did was i found a ruu.exe for 3.29, i downloaded it and ran it
once it was done i ran unrevoked to get root again and the boot loader installed, i think the .97 boot loader was key here, but i dont know.
then i booted to recovery and did a nandbackup
then i did a nand recovery to my older backups of cm6-success
then i did a nand recovery of a older oem 3.29 sense rom- success
im sure that i rambled on here and i never really knew what i was doing but i was able to do what i set out to do and then some. if only we could dual boot roms.....
Click to expand...
Click to collapse
You are doing exactly what I am trying to do, and ran into the same trouble.
Seems like having to run unrevoked again is unnecessary. There must be a way to switch the boot loader without it ? Did you ever find a quicker way?
I feel pretty comfortable messing with this stuff, even though I am new to the EVO. That said, I really do not want to brick it doing something stupid. Messing with these boot loaders does scare me a bit.

potna said:
did you ever get this figured out? i am in the exact same boat.
i rooted with unrevoked 3.21, this went well
i backed up oem sense in recovery via nandroid, this worked, i wiped and restored from this backup just to test, again the restore worked just fine.
later i tried to flash cm6 but all arrows pointing towards not having the right hboot. i dont remmeber what i had but i needed to got to eng boot .76.2000, which i finaly got figured out and was able to flash to cm6.
at this point cm6 loads and runs juts fine, i decided to boot to recovery and do a backup via nandroid, infact i did two of these back ups. i wiped my phone and did a restore just to test these back ups.
heres my problem: just for the fun of it i thought i would try to use the first nadroid back up to restore (that had stock sense installed at the time) and it wont flash. it says something about:
"Checking MD5 sums…
Erasing boot before restore…
Restoring boot image…
Error while flashing boot image!"
i thought i found a fix: i need to "Switch .76 with .79", this still did not allow me to restore from my oem sense backup, i get the exact same error.
i found another potential fix pertaining to going back to .93.
i feel like i dont know enough about what i am doing and im abit scared to try this as i dont see much info on this method.
basicaly i'd lile to be able to go back and forth between stock and custom for a while and also i'd like to be able to use nandroid backups to quickly do this.
am i approaching my problem correctly pertaining to the hboot thing? and can i just drop the .76,.79, 93. images in and out of the pc36image.zip file that i will place on root on my sd card with out anything else in this zip and expect it to just work?
Click to expand...
Click to collapse
I'm having the same problem, but I don't have the luxury of either Sense or Cyanogen working--I'm just permanently stuck inside the ClockworkMod Recovery and can't get back to a nandroid restore point I've verified in the past as working.
Is there something I can do to remove the pc36img.zip file? How?!

I have amon_ra and I ran into this issue a while back too. You most likely got this error due to your battery level being too low. Turn your phone off, charge the battery for a while and try again.
http://forum.xda-developers.com/showthread.php?t=705026&highlight=%5Brecovery%5D
Near the top of his post it states your battery must be atleast 30%, in red text.
Sent from my HTC Evo 4g

[Q] HELP!!!!! Bricked Evo maybe??

Hi guys I am a noob and am pretty good with computers. I tried to flash cyanogen to my evo using there wiki page. I used clockwork for recovery then i downloaded the engineering spl. this is where things went to hell. i did the update from zip then it would reboot but get stuck and keep going to the fastboot page (with the android guy on the skateboard). i tried to nandroid but that didn't work. it says checking md5 sums for a long time then it say erasing boot before restore... restoring boot image.. error while flashing boot image!
I just want to go back to stock evo at this point. please help i can do anything with my phone!

You have to take you SD card out unless abd can be used here I don't know. Then copy amon ra recovery to the root of the SD then flash amon then wipe everything and flash cm6 again. If you can't get back into recovery I don't know what to say someone knows ya should probably check others points about it. Or you could just move another Rom onto the card and flash that clockwork and cm6 are bad news together.

exactly the same thing happened to me. HELP!

OK so if you power down the phone (turn it off), then, power up + volume down, can you get to recovery at all Y/N.
Step 2. Do you have a nand backup Y/N. If you do, perform a restore and carry on with life, if not, 3 demerits.
Step 3 will be dependent on 1 and 2 above.

yeah I can get into restore, but the issue is that when I try to restore a backup, it says checking MD5 sums for a bunch of time and then says erasing boot before restore, restoring boot image, then error while flashing boot image

How much battery do you have right now?
You need > 30% for nandroid restore to work.
The good news is, you will be able to recover from this....talk to me..

Ummmmmm..... I dunno maybe 50%. But sweeeeeet! I tried something, I just reflashed the ota update from last week and im getting a boot screen..... im gonna cross my fingers! I performed a backup before, so I am hoping that everything isn't lost since i did a factory data restore.

Sweet, let us know.

Always, Always, backup before flashing, I do a nandroid and titianum backup before flashing.
And before flashing wipe everything (me = twice) "ALL CACHES".

Im Lost: Did you do a nandroid backup first from Clockwork recovery?

ok so that at least go me back to where I was, but i tried factory reset before that so all my stuff is gone. I tried doing a restore from rom manager, and still says error locating boot image. Will this prove to be a problem later on? Like if I want to flash other new roms?

Download everything first, move it to your sdcard !!!!, then...continue...
Masonm159 , what I would do if I was you is (1) do a FULL wipe, everything !!!! (Exception, don't wipe battery stats and/or ext. partition, which you probably don't have anyway, cause you have not set it up...assuming)
Then try this ROM,
http://forum.xda-developers.com/showthread.php?t=793471&page=18
Post Number 1
Rom first, then Kings #9 BFS Kernel (kernel) this is the actual link, but it is also in the thread.
Then the theme: Swype v2.4.44.10912 MetaMorph theme
Then lastly:Stock Fonts
Flash them 1, 2, 3, 4, then reboot
Come up, everythings good, power down, come back up, everything is good, go into recovery, nandroid backup.
Reboot, done, Happy Camper.
If you like the ROM stay with it (best I have seen), if not, flash away from there.

Yeah I did, and a titanium backup too. The issue was that engineering SRL or whatever it was called. So I am back in business. Doesn't lookout backup all your stuff too, cuz I think I have one of those somewhere.
My main question is, will this problem persist if I try another rom? Will there be no boot image?

i did a nand but it "recognize it" i can see my sdcard and I can move items to it through adb, but when i try to install them it says " E: can't open /sdcard.update.zip (bad) intallation aborted."

ok so now i am trying to restore everything with titanium and it says error "there is a problem parsing the package" WTF

Great question, here is my hopothesis: If the ROM includes a kernel and I think most of them do, then yes, here is a script from Kings #9 (2.6.32.15), from the link I gave you already, if we look at a scipt included with this kernel , I found this script, which "creates" a new boot.img.
#!/sbin/sh
echo \#!/sbin/sh > /tmp/createnewboot.sh
echo /tmp/mkbootimg --kernel /tmp/zImage --ramdisk /tmp/boot.img-ramdisk.gz --cmdline \"$(cat /tmp/boot.img-cmdline)\" --base $(cat /tmp/boot.img-base) --output /tmp/newboot.img >> /tmp/createnewboot.sh
chmod 777 /tmp/createnewboot.sh
/tmp/createnewboot.sh
return $?
Now, with all that said, I am just now getting back into both Linux, scripting and diving into cooking. So my recommendation is, research to be sure.
Lastly, pass this message to your phone, welcome back to the living
Cya.

Screw Titanium and the apps, pull em from the market and be done with it. Sh!t I am now a pro at reinstalling, have documented my favorite apps. Have not yet used Titanium to restore, have not needed to so, it could be any number of things. So just pull em back down.

im lost, OK so when you say, "when I try to install them", what "exactly" does this mean, install them how?

Masonm159 said:
ok so now i am trying to restore everything with titanium and it says error "there is a problem parsing the package" WTF
Click to expand...
Click to collapse
Consider this your validation on whether these tools properly restore the apps, thanks for being a trendsetter here, laughing, sorry. Good news is, you are back in business.

sorry, try to restore them from titanium. Its ok I have app brain too, so i am just going down the check list of markit apps. I will just have to re do my homescreens. I am just worried about this boot image thing.
So lets talk about that if you have a few minutes, and my phone an I thank you by the way for the support and time. Now is there a unique boot image on every rom i flash? Or does my phone just have one that is used for every rom? ..... fun

Nandroid Error

Last night after i did my nightly backup, i noticed that i couldn't exit the menu. After i did a backup, no buttons will work. I had to do a battery pull. I did three different backups, having to do a battery pull each time. Menu works fine, until i do the backup. It even says backup complete. The 3rd time i deleted the nandroid folder before running the backup, yet the problem is still there. I'm using the org HBOOT 0.76 eng, AMON_RA 1.8.0, CM 6.1.1, Zendroid kernel. Only thing i can think of is re-flashing the recovery and formatting the card. Anyone had this happen before???

Formatting the card did nothing. Re-flashed recovery did nothing. Any ideas???

You do a backup every night? Dang! I only one every couple weeks...
-Z

zzelinka said:
You do a backup every night? Dang! I only one every couple weeks...
-Z
Click to expand...
Click to collapse
Yea i do, i keep only the last 4 though. Just thought i would update this in-case it happens to someone else. To fix this, i had to repartition my sdcard in recovery, then reinstall my ROM. I guess what happen was when i installed the ROM on the new sdcard, without partitioning the new sdcard, it installed it wrong. This was causing the error.

This is one of the cases where your program failed working and is frozen like out of battery kinda fishy thingy there, I wish I could explain but It's bad mojo jojo.
I don't even use backups on my SDCARD, i put them on my computer, then switch roms/kernels with my pc on to my phone EVO. :/
THat sucks, sorry bro.

i dont have that problem with my nandroid backups but i keep gettin restore via adb on them...i keep about 3roms backed up on my card and this keeps happening...anyone have any ideas how to fix?

I'd try asking over the in Amon_RA recovery thread or you can @Amon_RA on Twitter. I've honestly never heard of or seen this issue.

Sounds like something is over-writing your recovery. "The moving over writer having writ moves on."
So start with all new "stuff" (os, recovery,downloads)

The recoveries are not very good about telling you what the Nandroid error was. You should run it via adb just as described:
adb shell
nandroid-mobile.sh -b (or I think -r for restore?)
Then you get a much better idea of what's going on. Happened to me once because my battery was too low to do a backup; recovery didn't tell me why, but running it from the shell did.

bwcorvus said:
To fix this, i had to repartition my sdcard in recovery, then reinstall my ROM. I guess what happen was when i installed the ROM on the new sdcard, without partitioning the new sdcard, it installed it wrong. This was causing the error.
Click to expand...
Click to collapse
Already fixed but thank you all

what was the issue? so others can find out as well.

[Q] rom manager issue

i havent been able to restore any backups for a while now, not an issue since im not as bad with the crackflashing addiction lol
well went to try a restore, didnt work-error while flashing boot img
tried advanced restore and got the same messge.
how do i check to see why it isnt working properly?
ive never been able to get an answer for this issue before so a little help would be awesome
reason i tried a backup, i did a flashover on cm7, and lost some(quite a few) of my pictures...so i tried the backup and got that crap again
so ya...not sure whats up

OMG_VTEC said:
i havent been able to restore any backups for a while now, not an issue since im not as bad with the crackflashing addiction lol
well went to try a restore, didnt work-error while flashing boot img
tried advanced restore and got the same messge.
how do i check to see why it isnt working properly?
ive never been able to get an answer for this issue before so a little help would be awesome
reason i tried a backup, i did a flashover on cm7, and lost some(quite a few) of my pictures...so i tried the backup and got that crap again
so ya...not sure whats up
Click to expand...
Click to collapse
shouldn't your pictures have been on your sd card?
anyways, you didnt really give any helpful information as to what your problem is, but maybe you could try this http://forum.xda-developers.com/showthread.php?t=714114

yes they were on my sd card, thats what doesnt make a lot of sense about it
and its not say md5 mismatch, i told you everything my phone said...all it says is "error flashing boot img"
if i had helpful info pertaining to this issue id be a lot closer to solving it...

Yeah, There shouldn't be an MD5 mismatch when your phone generated the MD5 to begin with.
I would suggest reflashing clockwork a few times from within ROM manager. It is the first option on the app which says "Flash ClockworkMod Recovery"
If that doesn't help your problem:
It shouldn't make a difference because ROM Manager is made by the CWM team but I would suggest trying to create a backup from within Clockwork and see if you can then restore the backup or even to just try restoring the backup you already made from within CWM rather than trying to use ROM manager. I've heard a lot about ROM manager having problems, so even though it takes a little more work you might want to take that route from now on.
In case you don't know how, all you need to do to get to clockwork is hold down the power button on your phone and then select reboot into recovery.
Once you're in recovery mode you need to select backup/restore using the optical joystick at the bottom of the phone to make your selections. When you make a backup from within clockwork you are unable to change the name before the backup is created but when you boot your phone up you can use any file manager to navigate to the clockwork/backup folder on your SD card and the bottom one should be the most recent because they are listed by date and then time that they were created.
I know it is a little redundant but it is always worth trying the easiest thing first before trying to overhaul your phone.

i dont use rom manager for anything...
i think im gonna try to complete reflash and re root and see what happens...kinda pissed i lost a lot of my pictures though
really confuses me...

try checking the internal flash memory, for some reason some of my pictures wind up there on accident sometimes. When you connect to your PC it is the third mass storage that shows up usually. I don't know how to access it from within the phone. and I apologize for the confusion but the title of the thread is "ROM manager issue" so that's what i thought you meant.

i tend to mistakenly call cwm rom manager since thats where i got it from

[Q] [q] soft brick -- a little help plz?

So I was got my s3 awhile back and rooted it and ran Clean bean without any problems, well after those annoying system update messages started to get to me I decided I wanted to try and new rom and update my phone a bit as I would be leaving the country and wanted my phone updated. So I decided to flash slimbeam , It went off without a hitch. Only problem was I could not figure out how to get Titanium backup to restore all my contacts and app data. I saved all the backup files on my computer and even after putting them in the Titanium backup directory it would not let me do it. Anyway.....I decided to try and use the titanium backup program that lets you extract the data from a nandroid backup and flash it in recovery. I forgot to put it on my internal card when doing so and when I did my wipe I deleted it (epic facepalm) so I have to reflash cleanbean go back into my phone and make the .zip file to flash...
So I got tired and went to bed before flashing anything else, when I wake up. My phone is stuck on the samsung boot image screen. I try starting only to get the same thing. So I boot to CWS recovery and try to restore one of my nandroid backups. I accidentally hit backup to external sd and it started to run a backup, thenn my car charger came unplugged and the phone died....thinking it would just make that specific nandroid corrupt I thought nothing of it. So I reboot to CWS recovery again and actually try to do a restore with my oldest nandroid, But I get the error "Error updating /system" and error updating "/data".....I tried multiple backups that I have, none of them work and all produce that message.. 'm fairly new to this, What Am I doing wrong? I really love this site and all you guys do and I will be forever greatful of any help you guys can give me. I leave the country for Mexico in 2 days and I cant afford to pay the $150 to get my phone warrantied from sprint!
Thanks in advance, and sorry for spelling/grammar mistakes (at work, not suppose to be on here)
-Lucid.

Lucid420 said:
So I was got my s3 awhile back and rooted it and ran Clean bean without any problems, well after those annoying system update messages started to get to me I decided I wanted to try and new rom and update my phone a bit as I would be leaving the country and wanted my phone updated. So I decided to flash slimbeam , It went off without a hitch. Only problem was I could not figure out how to get Titanium backup to restore all my contacts and app data. I saved all the backup files on my computer and even after putting them in the Titanium backup directory it would not let me do it. Anyway.....I decided to try and use the titanium backup program that lets you extract the data from a nandroid backup and flash it in recovery. I forgot to put it on my internal card when doing so and when I did my wipe I deleted it (epic facepalm) so I have to reflash cleanbean go back into my phone and make the .zip file to flash...
So I got tired and went to bed before flashing anything else, when I wake up. My phone is stuck on the samsung boot image screen. I try starting only to get the same thing. So I boot to CWS recovery and try to restore one of my nandroid backups. I accidentally hit backup to external sd and it started to run a backup, thenn my car charger came unplugged and the phone died....thinking it would just make that specific nandroid corrupt I thought nothing of it. So I reboot to CWS recovery again and actually try to do a restore with my oldest nandroid, But I get the error "Error updating /system" and error updating "/data".....I tried multiple backups that I have, none of them work and all produce that message.. 'm fairly new to this, What Am I doing wrong? I really love this site and all you guys do and I will be forever greatful of any help you guys can give me. I leave the country for Mexico in 2 days and I cant afford to pay the $150 to get my phone warrantied from sprint!
Thanks in advance, and sorry for spelling/grammar mistakes (at work, not suppose to be on here)
-Lucid.
Click to expand...
Click to collapse
Ok Lucid, stay calm.
First off, never do any work in Recovery without a fully charged phone. You're just asking for trouble if you're relying on the cable being plugged in.
I've never had good luck with trying to restore data in TiBu from a nandroid backup.
I'm not going to go into how to make your backups work. I'm honestly more concerned with just getting your phone back into working order. This thread has the most current Stock Rom in TAR form. Odin instructions can be found in this post within that thread.
After you're back to 100% stock, unrooted, you can follow the rooting guide to gain root back.

THANKS
topherk said:
Ok Lucid, stay calm.
First off, never do any work in Recovery without a fully charged phone. You're just asking for trouble if you're relying on the cable being plugged in.
I've never had good luck with trying to restore data in TiBu from a nandroid backup.
I'm not going to go into how to make your backups work. I'm honestly more concerned with just getting your phone back into working order. This thread has the most current Stock Rom in TAR form. Odin instructions can be found in this post within that thread.
After you're back to 100% stock, unrooted, you can follow the rooting guide to gain root back.
Click to expand...
Click to collapse
Thanks man! Most appreciated! You just relieved a large amount of stress! I'll pay it forward!

topherk said:
Ok Lucid, stay calm.
First off, never do any work in Recovery without a fully charged phone. You're just asking for trouble if you're relying on the cable being plugged in.
I've never had good luck with trying to restore data in TiBu from a nandroid backup.
I'm not going to go into how to make your backups work. I'm honestly more concerned with just getting your phone back into working order. This thread has the most current Stock Rom in TAR form. Odin instructions can be found in this post within that thread.
After you're back to 100% stock, unrooted, you can follow the rooting guide to gain root back.
Click to expand...
Click to collapse
Do what he said, I can vouch that restoring data through tibu from a nandroid has never worked for me either. If you backed up your contacts with Google you can just export them into a file (either .csv or .xml i forget) and then import that into your contacts
Sent from my SPH-L710

sevenpioverthree said:
Do what he said, I can vouch that restoring data through tibu from a nandroid has never worked for me either. If you backed up your contacts with Google you can just export them into a file (either .csv or .xml i forget) and then import that into your contacts
Sent from my SPH-L710
Click to expand...
Click to collapse
And after looking through the sextape forums thread a bit more, you don't actually have to reroot, just use the following TAR file:
"Restore" Versions - Wipes your user data
SPH-L710_MD4_1130792_Stock_Restore [EXE|TAR.MD5.GZ]
SPH-L710_MD4_1130792_Rooted_Restore [EXE|TAR.MD5.GZ]
Click to expand...
Click to collapse
They also have really good instructions for the Odin work on there.
Hope you get it working!

GOT IT! Thanks for the help man, worked like a charm. Even learned a thing or two .....So can you tell me how I get my stuff back using titanium backup? I got the backup files on my computer and I'm flashing a rom as I type this.

Lucid420 said:
GOT IT! Thanks for the help man, worked like a charm. Even learned a thing or two .....So can you tell me how I get my stuff back using titanium backup? I got the backup files on my computer and I'm flashing a rom as I type this.
Click to expand...
Click to collapse
Here is a link to a post where I talked about Tianium Backup and what not to restore. It should be fairly informative.

In TiBu for SMS and call logs hit menu from the main screen and backup data as XML, select save locally when it's done. Move the xml files to external SD if you're gonna flash a 4.2.2 rom, flash new rom move the xmls back to internal, go to tibu, same menu, restore from xml and select which one you want to restore. It'll open a quasi file explorer, locate the corresponding xml for the option you chose(call log, SMS, wifi, bookmarks) and select it. It will restore the data via XML and you'll have all your call logs, sms, bookmarks and wifi accesspoints back like you never left your previous rom.
°•○●¤◇★S☆A: Son's of Android★◇¤●○•°
I like to break stuff!