[Q]What the usefull and fully working method for backup the rom - Galaxy S II Q&A, Help & Troubleshooting

Hello guys,
My question is what the usefull solution for backup and restore the rom? CWM backup / restore seems not really working well. Xda and custom rom's dev always remind to make a backup, but when u face a problem after flashing rom, you cannot access CWM if you got bootloop, then how to restore? And if you dont like the custom rom that you just flashed for some reason, you might want to restore back to your 'fav' rom.. but unfortunately it's not work as you thought. Sometimes restore failed. Im looking the solution for this..
-restore / backup anywhere without using pc.
-not reflash the rom, this will need to customize it again.. Hassle.
-any android app or android system ability to handle this. If CWM can handle this, then tell me how to restore when u got bootloop and cannot access the recovery mod.
-if there's any other app or method, please suggest them to me.
Any help or idea will be appreciated. Thanks.
Sent from my GT-I9100 using xda premium

When ever Ive made a backup Ive always booted to recovery,"backup and restore" and then "backup".That gives me a full Nandroid backup.As far as the bootloop goes Ive never had a problem to boot to recovery with the 3 button combo.If the 3 button combo works,and its never failed for me then select "backup and restore","restore".Ive also read that reflashing your kernel can solve the problem.I know a simple factory reset can,but not always.

nandroid backup is the best

You can always restore the rom when you can access the recovery mod. If you are a flasholic, you cant escape from bootloop and no recovery mod. My odin binary counter now up to 539.. Nandroid backup sometimes got problem.. Let say i made a backup a checkrom, the i flashed miui, suddenly miui got problem, and i get into recoverymod to restore back my checkrom.. When u done restoring, you will be in checkrom but this time its got many problems. Flashing compatible kernel will not solve the problem. The only solution fot me is to reflash it again.
Im not looking for this way, reflash the rom is hassle, sometimes u got bootloop and cant access recovery, then u need to get back home to use computer with odin to flash only kernel.
What else backup method other than nandroid backup.
Sent from my GT-I9100 using xda premium

cooza said:
When ever Ive made a backup Ive always booted to recovery,"backup and restore" and then "backup".That gives me a full Nandroid backup.As far as the bootloop goes Ive never had a problem to boot to recovery with the 3 button combo.If the 3 button combo works,and its never failed for me then select "backup and restore","restore".Ive also read that reflashing your kernel can solve the problem.I know a simple factory reset can,but not always.
Click to expand...
Click to collapse
How if 3button combo no longer work as it always? When theres no recovery mod for you, what will you do then?
Sent from my GT-I9100 using xda premium

neobirdrio said:
How if 3button combo no longer work as it always? When theres no recovery mod for you, what will you do then?
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Normally when I flash a ROM over top of another and I know,from other threads,that they are not compatable in terms of insalation and basic use(FCs)then I always do a full wipe (format system/data/cache,battery stats and fact. reset) prior to instalation.With Titanium it only takes a few minutes to reinstall my apps and during instalation there is no conflicting data between the old and new ROM which would cause a major failer to occur.Thats why if something happens the 3 button combo always works cos nothing major has happened.A factory reset and Im done,althought very rare and the nandroid backup is still in the SD if needed.The problem is when there is to many ROMs cluttering the devices system.Ive read that flashing over top of CM7,Lightning and Miui can sometimes be problamatic.

cooza said:
Normally when I flash a ROM over top of another and I know,from other threads,that they are not compatable in terms of insalation and basic use(FCs)then I always do a full wipe (format system/data/cache,battery stats and fact. reset) prior to instalation.With Titanium it only takes a few minutes to reinstall my apps and during instalation there is no conflicting data between the old and new ROM which would cause a major failer to occur.Thats why if something happens the 3 button combo always works cos nothing major has happened.A factory reset and Im done,althought very rare and the nandroid backup is still in the SD if needed.The problem is when there is to many ROMs cluttering the devices system.Ive read that flashing over top of CM7,Lightning and Miui can sometimes be problamatic.
Click to expand...
Click to collapse
Ahaaa! Your description attract me, i think you're right, base on the way you explained about full wipe does make sense to me. The real interpretation of 'full wipe' is including formatting the system?
Maybe I'm doing it wrong here, flashing another rom on top of another. What usually i did is 'full wipe'... This is my step :
1 - clear data/factory reset
2 - clear cache
3 - advance > clear dalvik cache
4 - flash new rom
This is what i did, i didn't format anything as you mentioned above. Is your full wipe method lead to 'fresh install'? Well buddy, could you please note down your full wipe method step by step including format the system? Which step should i do 1st and what step next? Could you?
Thanks, highly appreciated.
Sent from my GT-I9100 using xda premium

Cool.The thing is not all ROMs are compatablie and therefore can cause problems between each other.Your phone holds data from the previous ROM and also your battery collects info and data from each ROM.All this data and info if not cleaned up (and if from various non-compatablie ROMs) will most likely always result in problems.A full wipe,that I will write below is like installing your ROM on a completely clean devive.First of all a nandroid and titanium backup which i explained ealier,I think?
1.Pass the new ROM to internal-SD
2.boot to recovery and wipe cache partition,dalvik cache,battery stats(go back)
3.select "mounts and storage"
4.format cache,system and data (go back)
5.now wipe data/factory reset and your phone is now completely clean
6.now just install your ROM from the internal-SD as normal and I also do another factory reset to avoid possible bootloops and reboot device but if you get one pull the battery or use the 3 button combo to do one.
this full wipe will clean up all system data but will not touch your SD card so your titanium and nandroid backups will not be touched if you should choose to use them.Once I reinstall all my apps again with titanium its a good idea to reboot to recovery and wipe cache partition and dalvik cache then reboot phone.This will help avoid market connetion problems.

cooza said:
Cool.The thing is not all ROMs are compatablie and therefore can cause problems between each other.Your phone holds data from the previous ROM and also your battery collects info and data from each ROM.All this data and info if not cleaned up (and if from various non-compatablie ROMs) will most likely always result in problems.A full wipe,that I will write below is like installing your ROM on a completely clean devive.First of all a nandroid and titanium backup which i explained ealier,I think?
1.Pass the new ROM to internal-SD
2.boot to recovery and wipe cache partition,dalvik cache,battery stats(go back)
3.select "mounts and storage"
4.format cache,system and data (go back)
5.now wipe data/factory reset and your phone is now completely clean
6.now just install your ROM from the internal-SD as normal and I also do another factory reset to avoid possible bootloops and reboot device but if you get one pull the battery or use the 3 button combo to do one.
this full wipe will clean up all system data but will not touch your SD card so your titanium and nandroid backups will not be touched if you should choose to use them.Once I reinstall all my apps again with titanium its a good idea to reboot to recovery and wipe cache partition and dalvik cache then reboot phone.This will help avoid market connetion problems.
Click to expand...
Click to collapse
Omg! I thought you not gonna reply me anymore. Dude, i even copy and paste the whole texts in my note app as my reference on the future. I highly appreciated for your efforts into this. Thanks for those details.
Check your PM.
Sent from my GT-I9100 using xda premium

Wasnt going to leave out in the cold mate,was just a bit busy.Thanks for the PM.Glad I could help

Related

Help!

I completely bricked my phone. i was rolling on fr008 and it was working fine. i nandroid packuped, then tried cyanogenmods 6.1.1... it's now bricked and whenever i do a nandroid backup it stays on the loading screen... help anyone?
Can you get into clockwork mod? If so, do a data wipe/factory reset, then clear cache, then on advanced menu clear dalvik cache. Then reinstall latest FR008ddx
tripstermcgee said:
I completely bricked my phone. i was rolling on fr008 and it was working fine. i nandroid packuped, then tried cyanogenmods 6.1.1... it's now bricked and whenever i do a nandroid backup it stays on the loading screen... help anyone?
Click to expand...
Click to collapse
So I am assuming you are able to get into recovery? If so please try to get into the advanced menu and do a "wipe dalvik cache". Next, backup 1 menu and wipe your cache partition and user data, then try and boot your phone. When switching from the FR series to CM or vice versa you need to wipe dalvik and regular cache plus user data. Also when you try and flash roms make sure your phone is not plugged in, clockwork recovery does not work the same when your phone is plugged in. If you flashed CM while your phone was plugged in then you need to attempt to flash again with your phone unplugged.
Thanks guys, that really helped, ill try it know
Thanks for the help guys, but do you know how to get my nandroid backup to work? because its factory reset, and everytime i try to do a nandroid backup i have to repeat this process... help again?
tripstermcgee said:
Thanks for the help guys, but do you know how to get my nandroid backup to work? because its factory reset, and everytime i try to do a nandroid backup i have to repeat this process... help again?
Click to expand...
Click to collapse
Forget the nandroid backup its corrupt
Sent from my Liberty using XDA App
What do you mean it's factory reset? If you restored your phone back to stock I don't believe you can use nandroid. You should be in clockwork recovery to use nandroid. The factory reset/data wipe from recovery does not bother nandroid in any way that I am aware of. Are you trying to restore a nandroid backup?
Sent from my HTC Liberty using XDA App
Eh, oh well, thanks for the help guys, ill start moving everything back....
Dont use clockwork recovery when plugged into your computer, thats the only conclusion i can come up with for why your nanodroid backup is corrupt...
Signatures are fancy.
Yeah... make sure you're unplugged while you're doing this and be sure to wipe the cache as mentioned above. You can then put a rom on your SD and flash again, then go back and flash your favorite rom or go back to factory.
cant stress it enough, read the install instructions and ALWAYS wipe before flashing(or is that flushing? j/k)
anyway, you should be able to Nandroid Restore. and the previous posters were right, the only way to enter recovery properly is with the phone unplugged, then power on holding the volume down key, select recovery and Bingo!!
let us know how you made out
Thanks guys, got everything up and running again, and thanks for the instructions
Sent from my HTC Liberty using XDA App

System wiped clean by CWM restore! Please help

Last night, I installed TW 4.5/TW Manager. I did a ClockworkMod backup first. I decided to restore it.
However, after restoration, the phone is in a factory state. Save for my lock pattern, which it remembered, the phone is in first-run setup mode, all my home screen layouts are gone, all my apps are not in the aop drawer except those the G2 ships with. Contents of the virtual SD card like photos are still there.
I tried restoring my only other CWM backup (a November backup that previously *restored ok* to undo a MIUI test, for example), but this, too, now boots in to the same state.
What has gone wrong here?
And is there any way of getting back the system that I assume/d is/was in the CWM backup files?
If I can't guarantee I can restore a CWM backup, it makes the world a very scary place to be.
Did you wipe before restoring? Sound to me you did not.
1. Full wipe
2. Restore again.
If that does not work, wipe again and use advanced restore.
Don't use rom manager but do everything manually from the recovery.
Wipe what?
You mean, choose Wipe Data and/or Wipe Cache?
Lennyz1988 said:
Did you wipe before restoring? Sound to me you did not.
1. Full wipe
2. Restore again.
If that does not work, wipe again and use advanced restore.
Don't use rom manager but do everything manually from the recovery.
Click to expand...
Click to collapse
Wiped data, Wiped cache, Restored backup - still doesn't retrieve the actual backup.
Now wiped again. In Advanced Restore, what should I do?
Lennyz1988 said:
Did you wipe before restoring? Sound to me you did not.
1. Full wipe
2. Restore again.
If that does not work, wipe again and use advanced restore.
Don't use rom manager but do everything manually from the recovery.
Click to expand...
Click to collapse
Restore the boot, system, data.
Lennyz1988 said:
Restore the boot, system, data.
Click to expand...
Click to collapse
This doesn't work either.
I had the same trouble early last month; even after a restore it was pretty much factory settings and I had to put everything back myself.
It was very irritating as I'd taken the precaution of making a backup but it still didn't work. I've pretty much recovered everything I needed to since then, though.
What excactly did you do prior to the restoring? Did you flash a new rom? If yes, what was your previous rom? Or is TW4.5 an app of some kind?
Lennyz1988 said:
What excactly did you do prior to the restoring? Did you flash a new rom? If yes, what was your previous rom? Or is TW4.5 an app of some kind?
Click to expand...
Click to collapse
I did this... http://forum.xda-developers.com/showthread.php?t=1365605
That is...
Installed TouchWiz 4.5, a modified TouchWiz launcher (left it alongside TouchWiz, set no default - home button press asked for confirmation of home screen each time)
TW4.5 comes with the TW4Manager app for controlling settings.
I downloaded the Suava theme for use with TW 4.5.
Before any of that, I made a CWM backup. Then I did the above. Now the backup (and even a backup which restored perfectly a month ago) will not restore to anything but factory new state.
And you are not getting an error message of any kind? How long does it take to restore? What is the size of the backup?
Lennyz1988 said:
And you are not getting an error message of any kind?
Click to expand...
Click to collapse
None.
Lennyz1988 said:
How long does it take to restore?
Click to expand...
Click to collapse
Seven minutes
Lennyz1988 said:
What is the size of the backup?
Click to expand...
Click to collapse
972Mb
The last thing I can think of is flashing an old stock rom and then rooting it with CF-Root. Then you have an older version of CWM.
A stock rom like KE2. Then try to restore.
If that does not work find a rom which has the latest CMW. Version 5 I believe. Then try restoring it.
Lennyz1988 said:
The last thing I can think of is flashing an old stock rom and then rooting it with CF-Root. Then you have an older version of CWM.
A stock rom like KE2. Then try to restore.
Click to expand...
Click to collapse
Hmm, are you talking about kernel?
If I'm correctly reading my rough notes from my rooting and tinkering, then my original kernel was KF3, I rooted in mid-October with an insecure equivalent (KF3) (CF-Root method), but quickly upgraded through Kies... I now have kernel XWKI4 (baseband XXKI1, build KI4).
So I moved from 2.3.3 to 2.3.4.
BUT - the backup and restore I did with CWM under the current system as recently as two weeks ago in November worked fine.
Lennyz1988 said:
If that does not work find a rom which has the latest CMW. Version 5 I believe. Then try restoring it.
Click to expand...
Click to collapse
So, you're saying there - you think a newer version of CWM might have eliminated a bug or something?
Might I find any FURTHER problems by changing the ROM and trying to restore?
Thanks for your help.
ClockworkMod - merry effing Christmas.
I really don't know. But I think it's worth the effort determining of your CWM is still functioning properly.
You can also try just flashing the KI4 CF-root kernel, then boot in recovery and then try to restore.
Make sure you have important stuff backuped of course
If you can boot to working phone backup data and copy clockwork mod folder to PC .
Then try posted below . boots to working phone root it with CWM and root copy clockwork folder back then try restore nandroid backup .#
Clean Slate for those that balls up the firmware .
Backup data first if phone is working .
Boot CWM recovery
Mounts and Storage
Format cache data system sd card .
Remove battery
Boot to download mode
Open Odin
Install correct stock firmware .
jje
JJElgan, thanks,
So let me clarify what you're essentially suggesting...
Store my ClockworkMod safely on the PC
Wipe cache, data, system and SD card in Recovery Mode
"Install correct firmware"
Then put the backup file back and try restoring
What do you mean by "correct firmware"?...
I currently have Baseband XXKI1, Kernel XWKI4, Build XWKI4. That is the firmware with which I made the backup. (I guess that's KI4?)
But the firmware I originally rooted with CWM was PDA: KF3, PHONE: KE7, CSC: KD1 (XEU). (I guess that was KF3?)
What's the aim of this here and what's the source of the info?
Thanks very much.
JJEgan said:
If you can boot to working phone backup data and copy clockwork mod folder to PC .
Then try posted below . boots to working phone root it with CWM and root copy clockwork folder back then try restore nandroid backup .#
Clean Slate for those that balls up the firmware .
Backup data first if phone is working .
Boot CWM recovery
Mounts and Storage
Format cache data system sd card .
Remove battery
Boot to download mode
Open Odin
Install correct stock firmware .
jje
Click to expand...
Click to collapse
You dont need to wipe before restoring. Just a quick note
Sent from my GT-I9100 using xda premium
CdTDroiD said:
You dont need to wipe before restoring. Just a quick note
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Ever?
How about after?
And how about in the advice the previous correspondent gave, to reinstall kernel/firmware?

I kinda messed up :P

Hello guys!
Today i installed ClockworkMod Touch recovery and installed SuperNexus 2.0 Build 4 Rom , the whole process took less than 5 minutes. But before i installed SuperNexus i did a "Nandroid?" backup which went fine and took lots of space xD Anyway i proceeded with SuperNexus and it installed fine and played with the rom for a few hours ... i decided to restore the backup so my whatsapp and all that stuff comes back .. i didnt know that it'll restore system too! Ofcourse the phone went on a bootloop so i went to CWM and wiped data/factory reset and the phone booted with Stock 4.1.2 and the phone is kinda slow at the first boot ... now i dont really know what to do :/ The nandroid backup is large and im afraid the SuperNexus rom wont fit and it'll cause errors n all xD Im really stuck at this point , should i repeat installing SuperNexus?
EDIT: I cleared 4.6GB of space , what to do next?
the backup restore shouldn't have caused a bootloop, that's weird.
it restores everything - system and data. so if you want to keep the data when switching ROMs, use Titanium backup or something if the sort. try restoring again. if it fails, try a custom restore of /data
Glebun said:
the backup restore shouldn't have caused a bootloop, that's weird.
it restores everything - system and data. so if you want to keep the data when switching ROMs, use Titanium backup or something if the sort. try restoring again. if it fails, try a custom restore of /data
Click to expand...
Click to collapse
Im not sure if its a bootloop , it keeps restarting boot animation after 1min , i fixed it anyway by wipe data/factory reset option thru recovery and its on stock now booting fine , Shall i flash SuperNexus again normally ? Other than wipe data/factory reset is there anything else to do ?
I mean, if you don't care about your data being lost - then sure
Yeah no probs , contacts on sim and pic's and movies on sd card , Ill just have to redownload my games and all Ill charge my phone then proceed , thanks One more question. Since I installed SuperNexus before does it have system files that I need to delete? Or wipe data/factory reset will cover it?
Sent from my GT-I9300 using xda app-developers app
no, a data wipe will do.
Success Thanks for the help xD I learned a lesson Ill use titanium backup from now on

[Q] Device Reboots when wiping /Data

Hi all,
I'm having a very strange issue with my i9300 today. I left it charging switched off overnight, and when I tried to switch it back on, it hangs on the Samsung bootscreen. I thought it was odd, but solvable. I went into recovery to try and reflash with the backup I have stored on my sdcard, however when it tried to wipe /Data, it rebooted and hung on the bootscreen again.
I initally had CWM 6.0.4.4 recovery installed, however I have tried PhilZ and TWRP to no avail. All three reboot on flashing /Data.
Anyone have any ideas?
For information, I was running 4.4 KitKat Unofficial. If you need any more information (preferably what can be pulled in Recovery/Download), I'll be happy to post it.
I need my phone running back normally ASAP!
Hi just a little confused..When you say all three reboot on flashing data do you mean data from your backup? If so your backup might be corrupt have you tried doing a clean flash with another rom or tried returning to stock?..Also if you don't want to lose data stored on your backup you can try flashing the original rom that you where on when you made the backup then using philz recovery in advanced settings/ restore you can then just restore data from your backup not the whole rom...And try formatting data system and cache but don't forget this will leave you without a rom so have one ready to install on your sd card....Hope all that makes sense
tallman43 said:
Hi just a little confused..When you say all three reboot on flashing data do you mean data from your backup? If so your backup might be corrupt have you tried doing a clean flash with another rom or tried returning to stock?..Also if you don't want to lose data stored on your backup you can try flashing the original rom that you where on when you made the backup then using philz recovery in advanced settings/ restore you can then just restore data from your backup not the whole rom...And try formatting data system and cache but don't forget this will leave you without a rom so have one ready to install on your sd card....Hope all that makes sense
Click to expand...
Click to collapse
Sorry, I should have been clearer. I was trying to Format the /Data partition in recovery in preparation to restore the backup, and every time a Recovery attempts to Format the partition the phone reboots.
I understand now thanks..Mmm..If you can't format data I would probably just flash stock again with Odin get your phone stable, then try to restore your backup...
tallman43 said:
I understand now thanks..Mmm..If you can't format data I would probably just flash stock again with Odin get your phone stable, then try to restore your backup...
Click to expand...
Click to collapse
Bleh. Returning to stock didn't work. It went past the bootscreen to the green android loading bar screen, went part way then rebooted, and stuck on boot again. >.>
Stickied faqs and guides .
But first what does Product Code say in download mode .
Originally Posted by tallman43<br />
I understand now thanks..Mmm..If you can't format data I would probably just flash stock again with Odin get your phone stable, then try to restore your backup...
Click to expand...
Click to collapse
<br />
<br />
Bleh. Returning to stock didn't work. It went past the bootscreen to the green android loading bar screen, went part way then rebooted, and stuck on boot again. >.>
Click to expand...
Click to collapse
You now have to go to recovery and wipe data/factory reset, wipe cache and reboot. It'll most probably work.
Sent from my silky smooth Samsung GALAXY S3
Rayan28 said:
You now have to go to recovery and wipe data/factory reset, wipe cache and reboot. It'll most probably work.
Sent from my silky smooth Samsung GALAXY S3
Click to expand...
Click to collapse
Ah, that would make sense. I'll give that a try now.
Nope. It's still hanging on the Samsung Bootscreen. Sigh.
I think I'm resigned to the fact I'm going to have to replace this. Most likely with a Nexus 5. Oh well. That sets back some of my luxury spending for the month again.
TermyJW said:
I think I'm resigned to the fact I'm going to have to replace this. Most likely with a Nexus 5. Oh well. That sets back some of my luxury spending for the month again.
Click to expand...
Click to collapse
Are you even flashing the correct ROM for your device with the correct model number? If yes, redownload the ROM. It could be a bad download. This time try the latest 4.3 Jelly Bean.

(Q) phone stuck in bootloop after flashing. Download and recovery mode working.

tetakpatak said:
Please quote my post and copy&paste whole text into some help thread for your phone, it is better idea as we are now getting off topic here. I'll try to help you there.
Format /system is done in recovery mode under "mount and storage" then after that you can restore your nandroid if it is done with the same recovery you use now. If you're on PhilZ 6, it usually can restore also CWM 6 backups.
Click to expand...
Click to collapse
What does format system do? And please help me load sentinel rom. That's the one I was gonna do.
Okay now for the question... I was running stock 4.1.2 with siyah kernel 6.0 b5. Then I decided to install philz kernel, but ended up in bootloop. Then I tried flashing dorimanx but still in bootloop. All the while I wiped everything before flashing.
Now im stuck as I can boot into recovery via any kernel but ultimately phone is stuck.
What to do?
And can anyone give me steps to install sentinel rom from this stage?
Sent from my Nexus 4 using xda app-developers app
AndroidReborn said:
What does format system do? And please help me load sentinel rom. That's the one I was gonna do.
Okay now for the question... I was running stock 4.1.2 with siyah kernel 6.0 b5. Then I decided to install philz kernel, but ended up in bootloop. Then I tried flashing dorimanx but still in bootloop. All the while I wiped everything before flashing.
Now im stuck as I can boot into recovery via any kernel but ultimately phone is stuck.
What to do?
And can anyone give me steps to install sentinel rom from this stage?
Click to expand...
Click to collapse
Mate, sorry for waiting, I was out of home. We will get your ROM back as soon as the phone boots again.
Don't worry, it doesn't sound serious so far. We have recovery and download mode (so topic name "nothing works" isn't really correct)
Formatting /system wipes all data from the system partition (so your system will be gone then) and it is important to do before installing new ROMs (essencially important for KitKat). It can't do any harm. As you have tried to install other kernels and didn't work we should check first what did you try to flash so far and it didn't boot? Is that what you wrote all what you have tried?
Now let me know please which recovery do you have now and is it the same version like when you have created your nandroid backup? If the recovery is the same, I would indeed try to restore nandroid backup right after wiping /system. Before you wipe the system just let me know: can you use ADB? If yes, check do you have ADB connection in the recovery mode?
tetakpatak said:
Mate, sorry for waiting, I was out of home. We will get your ROM back as soon as the phone boots again.
Don't worry, it doesn't sound serious so far. We have recovery and download mode (so topic name "nothing works" isn't really correct)
Formatting /system wipes all data from the system partition (so your system will be gone then) and it is important to do before installing new ROMs (essencially important for KitKat). It can't do any harm. As you have tried to install other kernels and didn't work we should check first what did you try to flash so far and it didn't boot? Is that what you wrote all what you have tried?
Now let me know please which recovery do you have now and is it the same version like when you have created your nandroid backup? If the recovery is the same, I would indeed try to restore nandroid backup right after wiping /system. Before you wipe the system just let me know: can you use ADB? If yes, check do you have ADB connection in the recovery mode?
Click to expand...
Click to collapse
Will it wipe the internal memory? Or the rom in the phone?
I have cwm based recovery v. 6.0.1.2. Yes I used it to make the backup.
Checking for adb.. How do I do it? .
Sent from my Nexus 4 using xda app-developers app
AndroidReborn said:
Will it wipe the internal memory? Or the rom in the phone?
I have cwm based recovery v. 6.0.1.2. Yes I used it to make the backup.
Checking for adb.. How do I do it?
Click to expand...
Click to collapse
Hi! Internal memory usually shouldn't get wiped by formatting /system, as it is "storage", not part of the system. I would give a try, wipe all: data/factory reset, cache, dalvik cache (advanced) and format /system (mounts and storage). Then back to the main menu --> backup & restore --> restore from (internal or external memory where your nandroid is saved) and choose your backup. It should reboot normally then.
tetakpatak said:
Hi! Internal memory usually shouldn't get wiped by formatting /system, as it is "storage", not part of the system. I would give a try, wipe all: data/factory reset, cache, dalvik cache (advanced) and format /system (mounts and storage). Then back to the main menu --> backup & restore --> restore from (internal or external memory where your nandroid is saved) and choose your backup. It should reboot normally then.
Click to expand...
Click to collapse
Thanks for helping, but I ended up downloading the stock rom and flashing it. Everything was normal. Then I installed cm10.2 so everything's great now. Thanks!
Sent from my Nexus 4 using xda app-developers app
Cool, @AndroidReborn! Now you can install your old ROM again and restore nandroid. Keep that stock FW saved on your PC, so if your phone gets ever again soft-bricked, no problem to revive it again.
I am wondering how nobody here responsed your help prompt, we have in i9000 help threads always handfull people of experience and skills who are ready to help in need. And there are double amount of the SGS2 units sold around the world.... strange.
tetakpatak said:
Cool, @AndroidReborn! Now you can install your old ROM again and restore nandroid. Keep that stock FW saved on your PC, so if your phone gets ever again soft-bricked, no problem to revive it again.
I am wondering how nobody here responsed your help prompt, we have in i9000 help threads always handfull people of experience and skills who are ready to help in need. And there are double amount of the SGS2 units sold around the world.... strange.
Click to expand...
Click to collapse
No idea. The people seem pretty 'busy'. Thanks for helping. Just one teeny tiny last question.. How do I install cm11 or any kitkat rom over this? Cwm is 6.0.4.5 so it's compatible...
Sent from my Nexus 4 using xda app-developers app
If you want to flash kitkat, the first thing you need to do is flash a kitkat compatible CWM (v6.0.4.7). If you try to flash KK with an 'older' CWM, you'll get 'installation aborted....error status 7' or something similar........
I'm currently running @infected_s KK build, and in the OP, you will find download links for the correct CWM, ROM and GApps files.......
Sent from my Infected KitKat bar.....
keithross39 said:
If you want to flash kitkat, the first thing you need to do is flash a kitkat compatible CWM (v6.0.4.7). If you try to flash KK with an 'older' CWM, you'll get 'installation aborted....error status 7' or something similar........
I'm currently running @infected_s KK build, and in the OP, you will find download links for the correct CWM, ROM and GApps files.......
Sent from my Infected KitKat bar.....
Click to expand...
Click to collapse
6.0.4.5 is compatible? I think so ......
Sent from my Nexus 4 using xda app-developers app
I've always read....not.....
In any case, probably best not to risk it......
6.0.4.7 is DEFINITELY KK compatible.... and it'd take a couple of seconds to flash.........
Sent from my Infected KitKat bar.....
AndroidReborn said:
No idea. The people seem pretty 'busy'. Thanks for helping. Just one teeny tiny last question.. How do I install cm11 or any kitkat rom over this? Cwm is 6.0.4.5 so it's compatible...
Click to expand...
Click to collapse
Yes, mate, CWM 6.0.4.5 is capable of flashing KitKat.
It is usually always the same:
download your ROM zip and compatible Gapps
check in the phone (or PC) if the zips are corrupted through download (if they open after clicking them, they are fine)
move the zips to the folder you will flash it from (if you use PC to flash zips with ADB sideload, put them in the sdk/platform-tools folder)
make nandroid backup of your presently used ROM
wipe data/factory reset
wipe cache
wipe dalvik cache (advanced)
format /system (under mount and storage)
flash ROM.zip
flash Gapps
reboot
It is in general always good to read in the development thread of the ROM you attend to flash in the opening post which Gapps are recommended, or if there is some unusual order of flashing (sometimes, developers recommend reboot system after flashing ROM, and after that going to recovery and flash Gapps zip.
Some KitKat ROMs struggle with root access by using Superuser, so SuperSU should be flashed. If SuperSU app from Play Store gives errors by updating binary, you should uninstall SuperSU app then, find in the Chainfire's thread the compatible UPDATE-SuperSu.zip (version for your phone), flash its zip in the recovery, install SuperSU app, update binary (either "normal" or "through CWM/TWRP")

Categories

Resources