I was using Ultimate ROM XXLSZ_JB_4.1.2_v5.2 without any problems apart from poor battery performance.
However, I attempted to install Rocket ROM-V1-XXLSZ and have now got myself into trouble.
I followed the instructions to flash the latest XXLSZ-OXA cwm kernel and then flashed the Rocket ROM. It worked ok but I would like to return to the Ultimate ROM and kernel I had before.
I have a pevious full Nandroid backup of the phone (made with ROM Manager Premium) of the Ultimate ROM and the PhilZ kernel it came with but cannot restore it. I get the error "MD5 Mismatch" and the restore aborts.
Even if I reflash the original Ultimate ROM with all the usual wipes, the XXLSZ-OXA cwm kernel is still there and I still can't restore from the Nandroid backup. I tried re-flashing PhilZ 3.1 kernel separately and then the Ultimate ROM file but this didn't work either. The kernel is still the same.
Can anyone tell me how to either
1. completely wipe the phone so I can install Ultimate ROM AND the built-in PhilZ 3.1 kernel.
OR
2. get the phone to the point where I can restore from my Nandroid backup which I assume will restore the earlier version of the ROM at the same time.
I hope I've explained the situation clearly enough.
Thanks in advance.
Trevor
Install a cm kernel then wipe your phone then install a fresh ultimate rom and later on advance restore the data
Sent from my GT-N7000 using Tapatalk 2
Go to cwm/backup and restore/misc nandroid setting/ untick md5 check. And try to restore again
Sent from my GT-N7000 using xda premium
You don't want to restore your nandroid. It is a bad backup.
In philz recovery go to mounts and storage. Format system data preload cache. Them go to advanced from main page and wipe dalvik
Flash ROM. Guaranteed to work.
Sent from my Samsung Galaxy SV using Tapatalk 3
Thanks. I know I can flash the ROM again but I was hoping to learn why the Nandroid backup no longer works.
Since posting, I gave up trying to restore the Nandroid backup, did all the usual wipes, re-flashed the Ultimate ROM and re-installed all my apps from scratch so my phone is more or less back to normal (Incidentally, I notice that no matter how many times I do this, all my music and photos are still there even though they're stored on the internal sd card. Dunno why).
Most of the ROMs I've tried have the kernel built in so all I needed to do was do the usual wipes and then flash. If I didn't like the ROM, I just wiped again and restored the Nandroid backup using CWM (Vol Up + Menu + Power) and the phone was back to its previous state.
The only thing I did different this time, as per the Rocket ROM instructions, was flash a kernel first. I may have done something wrong with that step or messed it up somehow. Even when I flashed an earlier version of the PhilZ kernel, the restore still didn't work. I've still a lot to learn about ROMs and Kernels, I guess.
As I said, I have successfully restored from Nandroid backups many times before this without any problem after experimenting with different custom ROMs. Can I ask you why Nandroid is a bad backup? Is it a problem with ROM Manager?
(One problem I've always had with ROM Manager is that if I choose to write the backup to the external sd card, it falls over with error messages. If I choose the option to backup to the internal card, it works but writes the BACKUP TO THE EXT CARD ANYWAY! I cannot get a reply from the dev about this).
Is there a better, more reliable backup method you'd recommend that does the same thing as the Nandroid?
I notice that different ROM managers use different CWM Recovery versions ie ROM Manager Reboot Recovery = 6.0.1.2, ROM Toolbox Rebooter = CWM 6.0.2.8 (same as Vol Up + Menu + Power). Could that be part of the problem?
Sorry for the long winded post.
Trevor
asf58967 said:
You don't want to restore your nandroid. It is a bad backup.
In philz recovery go to mounts and storage. Format system data preload cache. Them go to advanced from main page and wipe dalvik
Flash ROM. Guaranteed to work.
Sent from my Samsung Galaxy SV using Tapatalk 3
Click to expand...
Click to collapse
Related
I've made a nandroid backup of my rooted stock Rom with cyanogen recovery and flashed Modacos FR15 wich worked retty good for me. But after some testing i wanted to change back to my stock Rom. After doing backup of the Modaco I wiped and restored the stock rom backup which refused to boot. I restored the modaco Rom which worked perfect. Any ideas what the reason could be? BTW md5 check before restore was all fine and no errors on restore.
Sent from my LG-P990 using XDA App
Did you wipe everything? Also Dalvik cache? It worked for me tho, what kind of version are you using for CWM?
CWM is 3.0.2.8 (latest version which i installed via ROM Manager) - as I said - other backups of CM Nightly and Modaco FR15 worked without probs. But I made 2 Backups of my rooted Stock ROM v10c which refuse to boot after restore :/
Wiped all except Dalvik - I thought Dalvik gets wiped when doing Wipe Data / Factory Reset ... but I will try again with wiping Dalvik too.
I tried again to restore this time with dalvik wipe - but no change - boot hangs at the LG logo with the grey/blue loading-bar, the bar is moving some seconds and then stops and nothing happens. :/
try to press power+vol down to reset the phone to factory default. see if it can help...
I've had similar problem.
phone wont boot.
Only way I found out, you can see here:
http://android.modaco.com/content/l...rom-release-v10b-dated-1300166062-15-03-2011/
but you will loose everything what is on your phone
The reason it won't work, is because MCR converts the file system to ext4 (which CM7 can cope with). To revert to stock, you need ext3 - either
1. Use this to convert back to ext3 and immediately restore the backup (don't reboot or it will go fubar) http://android.modaco.com/content/l...3-for-converting-your-device-er-back-to-ext3/
2. Use nvflash to restore the stock 10b, then flash Clockwork, and then restore your backup.
The choice is yours .
Hi
i have just flashed ICS_Stunner_1.4.26.1 onto my Note.
Its amazing, I love it.
I have changed the dpi to 189 and changed it to forced landscape with 10 x 10 icon layout.
It was working fine the whole day and now when I turned on my phone the icons are cut in half. Not sure how to fix this?
Secondly I flashed from GB 2.3.6 with abyss kernal... they say you must charge battery to full then discharge empty and then charge to fill and delete some battery config. Is this true?
What would your path of action be when flashing a new rom? Also how do I restore all my contacts? I made a complete backup using titanium backup (system, apps & data) when I was on my root stock rom...
I got a few questions there and hopefully I can be pointed in the right directions...
One final question, if I wanted to try out KingDroid rom. How would I do it coming from this ICS Stunner Rom?
randomwalsh said:
Hi
i have just flashed ICS_Stunner_1.4.26.1 onto my Note.
Its amazing, I love it.
I have changed the dpi to 189 and changed it to forced landscape with 10 x 10 icon layout.
It was working fine the whole day and now when I turned on my phone the icons are cut in half. Not sure how to fix this?
Secondly I flashed from GB 2.3.6 with abyss kernal... they say you must charge battery to full then discharge empty and then charge to fill and delete some battery config. Is this true?
What would your path of action be when flashing a new rom? Also how do I restore all my contacts? I made a complete backup using titanium backup (system, apps & data) when I was on my root stock rom...
I got a few questions there and hopefully I can be pointed in the right directions...
One final question, if I wanted to try out KingDroid rom. How would I do it coming from this ICS Stunner Rom?
Click to expand...
Click to collapse
I follow the procedure suggested by xda thread when I change from ICS rom to another ICS or GB rom:
1. download AbyssNote 4.2 kernel and place it on your internal/external SD Card
Also download the ICS Rom you want to install and put it on your SD card.
2. reboot to CWMR and do a backup of your current system
3. after your backup is done, stay in Recovery
4. go to install a zip from SD card --> select AbyssNote 4.2 zip and flash it
5. go back to CWMR's root menu --> advanced --> reboot recovery
6. you'll find yourself in AbyssNote's Touch Recovery
7. factory reset --> wipe cache --> wipe dalvik
9. flash the ICS Rom of your choice
10. reboot and let the Rom settle for a couple of minutes
I have no problem with this procedure so far.
If you want to be absolutely safe, you will use PC Odin back to stock Gingerbread, root it, then flash a safe rom/kernel combo. Abysskernel will work, but it's not 100% safe.
Your contacts should be restored if you had them synced with Google (Settings --> Accounts).
When you restore with TI Backup (if you do) don't restore anything system wise. Just apps and data with them only. If you have bugs, you will have to re-flash and NOT restore apps.
ok concerning my contacts... i didnt sync them with google... i know silly me. it was on the phone.
So doesn't titanium backup copy them anywhere.
I have made backup of my rom with cwm... would that contain my contacts if i restored that backup?
was its either use cwm which isnt 100% safe or use pc odin and stock gb...
Could i just restore the backup of my gb rom and then flash from there to a ics?
Use PC Odin back to gb stock prerooted, the stunner use a bad kernel i think and wipe can cause emmc to break?, so i suggest using PC odin back to stock prerooted gb , then follow some guides ( i used abysskernel ) then Asylum as its same and good rom!
randomwalsh said:
ok concerning my contacts... i didnt sync them with google... i know silly me. it was on the phone.
So doesn't titanium backup copy them anywhere.
I have made backup of my rom with cwm... would that contain my contacts if i restored that backup?
was its either use cwm which isnt 100% safe or use pc odin and stock gb...
Could i just restore the backup of my gb rom and then flash from there to a ics?
Click to expand...
Click to collapse
If you restore "Phone" and Contacts app + data with TI backup, it MIGHT restore them but no guarantees.
You can restore the backup of your GB rom IF you are NOT using CWM on a stock ICS rom. Use Abyss Kernel to restore nandroid backup. Flash Abyss. Reboot recovery. Restore nandroid.
Go to stock ICS OR franco, speedmod, or CM9 kernels or a CM9 build.
ok I flash abyss kernel via cwm... then advance reboot recovery... restored my backup via cwm... merged my phone contacts with google...
Then i got curious about Kingdroid v2.0 with s3 add ons. So I downloaded that and flashed it via cwm... the play store wasnt downloading apps but i could browse internet, so reflashed abyss kernal via cwm and re flashed ics stunner...
I am back on stunner now. I prefer to look of this rom. So i guess as long as your flash abyss kernel you should be fine with flashing different roms and retaining root?
Just need to find out about the battery issue... when flashing a new rom what do you do concerning the battery to ensure correct % and charge...
edit: currently on Kernel : 3.0.15-I9220ZCLP6-CL343671
should i flash to one of the kernels you mentioned above?
also still having problem with cut off icons with apex set at 10x10 in landscape mode...
ok i think i has figured out the solutions...
At current apex doesn't support icon resizing so i changed my layout to 6 x 6 for now.
also was having problem making calls, it kept fc. I found out somewhere that if you use 160dpi you can use a fix or change to 200dpi and you don't need a fix and it works and still looks awesome.
I am very happy with this rom thus far... otg works which is a plus. I think i will use it for a week or so and then try the next one...
flashing roms is like eating pringles... once to flash you can't stop
Dont take me wrong dude but all these fixes including the call fc are in the stunner page,if u read everything before flashing u will not have problems and if u do, u would know how to solve yourself...and be careful restoring nandroids from cwm,flash abyss,then restore.
Sent from my GT-N7000 using xda premium
Also for the playstore,u could only clean the caches in my apps or change the dpi that would work
Sent from my GT-N7000 using xda premium
hahaha why would i take it the wrong way?
but seriously there are like 500 pages... and sometimes your searches are using the right key words. But yip I will try my best not to ask questions that have already been answered... even tho those answers are hidden in the mine that is xda...
With time you learn to navigate such a mine without feeling lost and confused but i am still a wee padawan
Yes always flash abyss first ALWAYS
Hi there,
I have a rooted N7000 running original Android v 2.3.6
I want to flash (test) it with a custom ROM.
I made a full backup of my current system (via CWM backup)
Now, when I flash a (new Android 4) custom ROM, will it then be possible to restore the old v2.3.6 image that I made, using CWM?
Other question: Do I need to take care of what type Kernal version I have
I have 2.6.35.7-N7000XXKKA-CL726566
Baseband-version is N7000XXkk5
Thanks for your reply.
Rene
jbin said:
Hi there,
I have a rooted N7000 running original Android v 2.3.6
I want to flash (test) it with a custom ROM.
I made a full backup of my current system (via CWM backup)
Now, when I flash a (new Android 4) custom ROM, will it then be possible to restore the old v2.3.6 image that I made, using CWM?
Other question: Do I need to take care of what type Kernal version I have
I have 2.6.35.7-N7000XXKKA-CL726566
Baseband-version is N7000XXkk5
Thanks for your reply.
Rene
Click to expand...
Click to collapse
nothing to worry about, that is what backup is intended to do.
the only thing you have to watch that you're on safe kernel like philZ when wiping data in stock ics or jb (read sticky threads)
example: if you are on philz kernel and runing ics or jb, when you restore your backup of gb, you restore your gb kernel, system, data etc, just like backing home
djoni_gitara said:
nothing to worry about, that is what backup is intended to do.
the only thing you have to watch that you're on safe kernel like philZ when wiping data in stock ics or jb (read sticky threads)
example: if you are on philz kernel and runing ics or jb, when you restore your backup of gb, you restore your gb kernel, system, data etc, just like backing home
Click to expand...
Click to collapse
OK, Thanks for the reply. So if I understand correctly:
1. I make a backup of my current ROM (Image via CWM) and put it in a safe place.
2. I can flash any custom ROM, and test/play with them.
3. Afterwards I can put back my old ROM again via CWM restore.
4. Reboot, and I'm back in the old state.
Is this right?
Can I flash ROMs by using CWM also (using zip files) or do I need to flash, using Odin?
I actually do not understand your remark about philZ, can you explain a bit more about what that means.
Thanks for your help so far
Rene
jbin said:
OK, Thanks for the reply. So if I understand correctly:
1. I make a backup of my current ROM (Image via CWM) and put it in a safe place.
2. I can flash any custom ROM, and test/play with them.
3. Afterwards I can put back my old ROM again via CWM restore.
4. Reboot, and I'm back in the old state.
Is this right?
Can I flash ROMs by using CWM also (using zip files) or do I need to flash, using Odin?
I actually do not understand your remark about philZ, can you explain a bit more about what that means.
Thanks for your help so far
Rene
Click to expand...
Click to collapse
Since you are going to try custom rom, you need not to worry about emmc brickbug, since they will be using a safe kernel..but double check before flashing...so, if you are on Stock ICS kernel, you should NOT wipe/factory reset..if you do, you will brick your phone..you can just go through couple of sticky threads to know abt emmc brickbug, if you are not aware of that..whatever the steps you have mentioned above are correct..but when you flash a custom rom, follow the instructions mentioned in the Custom rom OP...
Shyam said:
Since you are going to try custom rom, you need not to worry about emmc brickbug, since they will be using a safe kernel..but double check before flashing...so, if you are on Stock ICS kernel, you should NOT wipe/factory reset..if you do, you will brick your phone..you can just go through couple of sticky threads to know abt emmc brickbug, if you are not aware of that..whatever the steps you have mentioned above are correct..but when you flash a custom rom, follow the instructions mentioned in the Custom rom OP...
Click to expand...
Click to collapse
+1
jbin said:
OK, Thanks for the reply. So if I understand correctly:
1. I make a backup of my current ROM (Image via CWM) and put it in a safe place.
2. I can flash any custom ROM, and test/play with them.
3. Afterwards I can put back my old ROM again via CWM restore.
4. Reboot, and I'm back in the old state.
Is this right?
Can I flash ROMs by using CWM also (using zip files) or do I need to flash, using Odin?
I actually do not understand your remark about philZ, can you explain a bit more about what that means.
Thanks for your help so far
Rene
Click to expand...
Click to collapse
1. Yes, copy your /clockworkmod to your pc (just for double safety) dont cut it or move it, you need it on your internal sd card always, if you wanted to restore it again... and dont rename it (you will end up with message md5 missmatch!)
2. of course
3. Every new custom kernel like Philz kernel ( for ICS TW and JB TW) http://forum.xda-developers.com/showthread.php?t=1901191
or hydracore (not working on TW JB, but works on all other) http://forum.xda-developers.com/showthread.php?t=1749863
have built in CWM 6.x.x.x , You can recognize them by the gray background in CWM recovery. (there is no need to install independet CWM or something else, like you do on your stock GB kernel)
They are built in almost every custom rom, and these kernel are safe for wipe.
3.1 . So if you flashed new custom TW ics or jb, and after playing with them, you want back to your nandroid backup, just go boot in recovery (now you see a grey background CWM6) do all the wipes (in my experience the best way is: (advanced > wipe dalvik cache, go back > wipe cache, then wipe/data factory reset, then go into mounts and storage > format cache,system,data and preload , dont format emmc and sd card. go back into backup/restore > restore from (internal sd card or some other place depends on where you place your backup)
4. of course, when youo see a message backup complete, reboot it
Hello then!
The situation is as follows:
- Done a nandroid backup using a certain kernel and CWM
- Installed various ROMs
- Trying to restore my original ROM, using the same kernel and CWM version that created it
- The system boots, showing the startup animation (in this case the cellphone carrier animation, after the Samsung logo) and gets stuck, vibrating every once in a while like in forced-closes.
My guess is that some system process crashes or fails to start, dragging the rest of the system with it. I just don't know why it would happen after a nandroid recovery with the same kernel and CWM version, factory wipe, formatting etc.
- Tried a factory reset + cache wipe + dalvik cache wipe
- Tried formatting the various partitions and re-partitioning using a 512 PIT file
- Tried flashing similar (slightly earlier or later) ROMs through Odin, then restoring
I do have a Titanium backup in place, but not an Odin-flashable version of this ROM, so this isn't the end of the world, but it will force me to switch a ROM at an odd timing if I don't solve this.
Any ideas?
tempnick said:
Hello then!
The situation is as follows:
- Done a nandroid backup using a certain kernel and CWM
- Installed various ROMs
- Trying to restore my original ROM, using the same kernel and CWM version that created it
- The system boots, showing the startup animation (in this case the cellphone carrier animation, after the Samsung logo) and gets stuck, vibrating every once in a while like in forced-closes.
My guess is that some system process crashes or fails to start, dragging the rest of the system with it. I just don't know why it would happen after a nandroid recovery with the same kernel and CWM version, factory wipe, formatting etc.
- Tried a factory reset + cache wipe + dalvik cache wipe
- Tried formatting the various partitions and re-partitioning using a 512 PIT file
- Tried flashing similar (slightly earlier or later) ROMs through Odin, then restoring
I do have a Titanium backup in place, but not an Odin-flashable version of this ROM, so this isn't the end of the world, but it will force me to switch a ROM at an odd timing if I don't solve this.
Any ideas?
Click to expand...
Click to collapse
Yes , you must flash the same version of android how the nandroid is.
When Nandroid is made while using ICS 4.0.4 then flash a 4.0.4 based rom then you can restore it.
SOLVED
kevinrus123 said:
Yes , you must flash the same version of android how the nandroid is.
When Nandroid is made while using ICS 4.0.4 then flash a 4.0.4 based rom then you can restore it.
Click to expand...
Click to collapse
That much I already know.
What finally solved it is this procedure: It seems that the carrier ROM that I had (in a *.tar file) wasn't enough for resetting the device, and flashing one of the ROMs listed in this thread did the job. I then flashed the carrier ROM and the CF-Root kernel, which I had before, and successfully restored everything from my nandroid backup.
tempnick said:
That much I already know.
What finally solved it is this procedure: It seems that the carrier ROM that I had (in a *.tar file) wasn't enough for resetting the device, and flashing one of the ROMs listed in this thread did the job. I then flashed the carrier ROM and the CF-Root kernel, which I had before, and successfully restored everything from my nandroid backup.
Click to expand...
Click to collapse
Nice to hear that it's fixed now
Hi there,
I recently rooted and flashed a custom ROM onto my Samsung Galaxy S3 Mini. I'm very new to this thing and find everything quite overwhelming, but I want to learn.
I flashed this ROM - http://forum.xda-developers.com/showthread.php?t=2119219 (the v6 No Wipe version because I was petrified about losing my data if I factory reset), but the phone is now extremely laggy and buggy, so I want to go back to the stock ROM (so I can do a nandroid backup) and then try a different custom ROM like Dmod.
So, my question is, do I have to factory reset my phone to go back to stock? Or can I just flash this file (http://hotfile.com/dl/189271016/833...T-I8190N-BTU-I8190NXXALL6-1356151513.zip.html) using the CWN recovery menu without wiping? I'm asking because my phone keeps giving me an error everytime I try to backup using the CWM Recovery menu.
Thanks and if you need me to explain something in further detail, let me know.
YamiWheeler said:
Hi there,
I recently rooted and flashed a custom ROM onto my Samsung Galaxy S3 Mini. I'm very new to this thing and find everything quite overwhelming, but I want to learn.
I flashed this ROM - http://forum.xda-developers.com/showthread.php?t=2119219 (the v6 No Wipe version because I was petrified about losing my data if I factory reset), but the phone is now extremely laggy and buggy, so I want to go back to the stock ROM (so I can do a nandroid backup) and then try a different custom ROM like Dmod.
So, my question is, do I have to factory reset my phone to go back to stock? Or can I just flash this file (http://hotfile.com/dl/189271016/833...T-I8190N-BTU-I8190NXXALL6-1356151513.zip.html) using the CWN recovery menu without wiping? I'm asking because my phone keeps giving me an error everytime I try to backup using the CWM Recovery menu.
Thanks and if you need me to explain something in further detail, let me know.
Click to expand...
Click to collapse
That firmware is a zipped odin-file. Can't be flashed in CWM.
Make a cwm nandroid backup of your "/data" to your external sd (that's your installed apps)
You can also backup your apps and appdata using titanium backup or similar, for later restore.
Just remember to never backup/restore systemapps.
Backup internal sd to computer just to be sure, if you in any situation have to make a factory reset. Make sure any kind of backup is on your external sd before you make factory reset, or it will be lost forever
YamiWheeler said:
Hi there,
I recently rooted and flashed a custom ROM onto my Samsung Galaxy S3 Mini. I'm very new to this thing and find everything quite overwhelming, but I want to learn.
I flashed this ROM - http://forum.xda-developers.com/showthread.php?t=2119219 (the v6 No Wipe version because I was petrified about losing my data if I factory reset), but the phone is now extremely laggy and buggy, so I want to go back to the stock ROM (so I can do a nandroid backup) and then try a different custom ROM like Dmod.
So, my question is, do I have to factory reset my phone to go back to stock? Or can I just flash this file (http://hotfile.com/dl/189271016/833...T-I8190N-BTU-I8190NXXALL6-1356151513.zip.html) using the CWN recovery menu without wiping? I'm asking because my phone keeps giving me an error everytime I try to backup using the CWM Recovery menu.
Thanks and if you need me to explain something in further detail, let me know.
Click to expand...
Click to collapse
Backup your data in CWM, flash my ROM and restore your data with CWM.
Benzonat0r said:
Backup your data in CWM, flash my ROM and restore your data with CWM.
Click to expand...
Click to collapse
CWM has NO choice to backup/restore only parts of the device. Only a full backup is possible.
This is only in TWRP. Pity! I only use CWM because TWRP makes corrupted backups (three times) for me.
Or is it possible to pick out only DATA from the backup? And what is happen with the dalvik cache, which
consists of the byte-code for all installed apps, optimized for the ROM which created it?
"advanced restore and restore only /data". Is this the way in CWM that you mean @benz?
JackoMJ
Yes that's exactly what I meant, "advanced restore and restore only /data"
You don't have to worry about cache and dalvik because it's automatically created on the initial start.
thx for the information Benz (usefull in the future perhaps),
but i´ve decided to use Titanium Backup.
JackoMJ