So today i flashed a custom rom and my s3 got soft bricked, the worst thing is i forgot to make a nandroid backup, i would appreciate it if someone gave me a nandroid backup (stock) for my s3
@FreedomUser: that's no good way to repair. Rebuild your system, beginning with original-firmware (from sammobile.com). If everything works fine, root, backup efs, flash custom recovery & ROM…
Try pushing over a custom ROM to your SD card and try flashing it.
sent from my nexus
Related
ok guys, here we are again.. you're wanting to backup your phone for if you want to try a test rom, or just to have a backup in case something goes wrong. this tut will show you how! I will also explain how to restore your phone to a backup you've previously made. it is also possible to backup/restore using rom manager but this is the harder way.. not too hard once you figure it out, but thats all opinion
Pre Requirements:
1.) be rooted
2.) have clockwork recovery installed
3.) not a necessity, but it DEFINITELY helps to have the engineering build installed at least once
BACKUP STEPS:
1.) boot into clockwork recovery mode
2.) scroll down to nandroid and select
3.) click backup
4.) it will now automatically backup your ENTIRE PHONE.. this includes your contacts, messages, emails, everything you have on the phone prior to booting into recovery. you will see a yellow bar at the bottom that shows progress
5.) REBOOT!
6.) there is no step 6... you're done
RESTORE STEPS:
1.)boot into clockwork recovery mode
2.) scroll down to nandroid and select
3.) scroll down to restore and select
4.) scroll to your desired restore nandroid and select
5.) scroll to yes and select
6.) it will now auto restore your backup and everything in it. when done it will tell you DONE!
7.) reboot and you're done!
well there ya go guys, one (two?) more tut(s) done and have fun be safe and remember to wipe if you're ever scared you have a boot loop
I actually do have a specific question about these nandroid backups. If I backup, then flash a "updated" ROM (update to an existing one already installed), and THEN do a restore, does the restore take me back to the previous version of the ROM? I've never used the nandroid backups as I usually never have a need to.
the restore takes your phone back to exactly how it was when you performed the backup
Gotcha, so if you backup, wipe, and then update a ROM, you cannot expect to be able to use your nandroid backup to restore anything you had previously, unless you wanted to go back to the ROMs previous version... gotcha.
where are these backups stored?
I think it's /sdcard/clockworkmod/backup/[BackupDate]/
is it safe to remove them from the sdcard & store for safekeeping until needed & replace in same location?
yep, sure is!
Is it necessary to perform a wipe before restoring, if you currently have a different ROM than what is being restored? Or does nandroid wipe for you?
romis138 said:
Is it necessary to perform a wipe before restoring, if you currently have a different ROM than what is being restored? Or does nandroid wipe for you?
Click to expand...
Click to collapse
no, nandroid doesnt wipe for you. i suggest always wiping if you're changing roms
hi im kinda new to this, but I rooted my slide using the tuts from droiddog.com and here. Got mostly everything working but when I try to backup my current rom clockwork crashes and it doesn't take me to recovery and just reboots the phone. Ive tried clearing the download cashe and downloading an older recovery but nothing seems to work. I basically cant boot into recovery to make backups or flash any roms. any suggestions on what else I could try.
I gave this explination of a nandroid to a friend of mine today. It will act like a time machine and put your device back exactly as it was when you did the backup. Now if you need an explination like that, you realy should not be messing with your phone that way.
freeze
hi
i have a problem. when i try to restore my backup. everything looks fine. but when restoring finish and reboot my phone screen is freezing on htc logo. what can i do?
sorry for my bad english!
Just wait it takes a while to boot sometimes, treat it like you would treat a new ROM being flashed.
i need to wipe data/factory reset or?
ok
i wipe data.. restore backup from nandroid.. reboot phone and i waiting almost 30 min and screen still show only htc logo..
I have copied the nandroid backups on my SD card
but in recovery mode, it is not showing any nandroid backup file ?
warewolf4586 said:
I have copied the nandroid backups on my SD card
but in recovery mode, it is not showing any nandroid backup file ?
Click to expand...
Click to collapse
is it in the sd\clockworkmod\backup folder??
Hello,
I have a question about Nandroid backups using CWM...I read on some forum that...the backup and the installed version of CWM recovery should match to make it work..I.e If I took the backup using CWM version 5.0.0.0 I have to use the same CWM recovery version to restore the ROM and I can not restore nandroid backup using the later version lets say 5.0.1.5 of CWM...is it true?
Thanks..
I kinda doubt that. Itd be much more likely that a nandroid created by 5.0 couldnt be used by an earlier version. I doubt that is true either, just more likely than the other way around.
Nothing wrong with waiting for better confirmation than mine, but if it were an issue I think wed have heard a lot more about it by now.
Sent from my SGH-T999 using xda app-developers app
Not sure if this is the right place. So after trying to install a theme. My tab is stuck at boot. i tried to factory restore and cache wipe. Neither worked. Need help. thanks.
edit:looks like i posted in the wrong place so. Gonna make another thread in the right area.
i made the samething but i made backup before installing the theme , so i restored it back
Did you make any backup before? Just restore it..
-If you made a Nandroid backup (wich you always should do before flashing "anything") just restore it, and your fixed.
-If you didnt made a backup, just reflash your original or custom rom in CWM, after clearing "System cashe/Dalvic Cashe and Wipe date/factory reset".
-After you reflashed your custom/original rom, MAKE A NANDROID BACKUP! and at the first boot save it to your desktop just to be safe.
Hi guys little intro
Samsung galaxy S3 I9300 International
Running
TWRP recovery
Slimbean android 4.3
Basically what happened is the battery died on the phone so i swapped it out for a charged one and the device just bootloops on the slimbean logo. I then went into recovery to restore from a backup and after the restore it said "This device does not appear to be rooted would you like to install supersu." <-- alarm bells?? so i click yes, and now it doesnt even boot up the slimbean logo it just sits at the samsung one.
I have tried
Re rooting using cfroot
Reinstalling recovery
Reinstalling the rom
Restoring to a backup.
Nothing is working? is it possible for phones to throw wobblys and unroot themselves? which would explain why i cant load a custom rom?
Whats worse i cannot for the life of me figure out why just pulling the battery would result in a bootloop?
#
help pleaseeee
An instant shut down will usually result in data corruption, first try clear cache and dalvik, next a mega wipe script.
If that also fails then probably best to flash a stock rom using odin on your pc. You might need your efs backup if that partition was damaged.
Managed to resolve the issue by first re rooting with cfroot then installing twrp then reflashing the ROM, unfortunately my micro SD card got corrupted over 30gb of music and data gone, not impressed, also lost my nandroid backups and my titanium backups
Sent from my GT-I9300 using Tapatalk 4
guys im trying to fix my friends phone whici is samsung galaxy s2, heres what he did, he was on cynogen mod and then directly went to another rom without changing the bootloader and then he change it again to kitkat rom hoping it would fix things now what i did was first fix the bootloader cause im trying to restore its backup which is the original os 4.1.2 i was able to enter cwm which is 6.0.2.7 now i was able to restore the backup but still on bootloop. any tips?
rarela1234 said:
guys im trying to fix my friends phone whici is samsung galaxy s2, heres what he did, he was on cynogen mod and then directly went to another rom without changing the bootloader and then he change it again to kitkat rom hoping it would fix things now what i did was first fix the bootloader cause im trying to restore its backup which is the original os 4.1.2 i was able to enter cwm which is 6.0.2.7 now i was able to restore the backup but still on bootloop. any tips?
Click to expand...
Click to collapse
Wipe data
Sent from my GT-I9100 using xda premium
Flash stock sammy rom with odin.
If wiping data doesnt work, try flashing kernel. If that doesn't work, flash stock 4.1.2 via odin
Sent from my SGH-I317 using XDA Premium 4 mobile app
i just installed the stock firmware which is 4.1.2 and then tried wipe but theres a message in the system recovery says failed to mount /efs? any clue? thanks in advance.
flash latest philz kernel from here http://forum.xda-developers.com/showthread.php?t=1877270 ,boot to recovery,then restore your efs backup from there(you should have one in your external sd)
Sent from my blazing fast Note 2, running MIUI 5x and pleasantly surprised by it.
just installed philz kernel and went to recovery im searching for restoring the efs but cant find it though. still on bootloop.
i think this phone has other problem already tried 3 different stock firmware for this phone and then go to recovery wipe still on bootloop. tried installing kernel from philz its desame but only thing i noticed is every time i installed a new rom and go to recovery is says failed to mount efs. can it be one of the reason why its on boot loop? and also my friend didnt back up his efs thats why i think this is happening.
do you have a nandroid backup of any previous rom?
yup he has nandroid backup which has on the stock rom but i doubt cause when i installed the stocked rom then installed philz cwm which was 6.0.2.7 i was able to restore the back up but its still on bootloop so i dont know if the cwm is the ones not compatible or the rom.
after you restore your backup do a factory reset in cwm.
now i tried what you said and its showing md5 mismatch when i try to restore.
could be a corrupted backup.did you tried factory reset on your current rom?
argghh im on the blink on giving up on this phone already tried different methods.............
assuming you're now on stock 4.1.2,i suggest you to flash dorimanx 8.43 kernel,,if it doesnt boot,reboot to recovery,do a factory reset.If that doesnt help,try to restore nandroid from this cwm.Of course before restoring do a factory reset and format system and preload partitions.
ayt will try this now!!!
still no luck not working T_T..
you mean you can't restore your backup?And dont forget to wipe cache and dalvik cache when doing factory reset.As for efs,did you looked for it in internal sd too,in clockwork folder?It can be either in tar.gz,img.gz or zip formats.It's stuck at boot probably because of corrupted efs partition.If I remember well,you can restore efs partition from nandroid backup in philz touch cwm.
Have you done a stock samsung rom install usin odin? That should get you back to sqaure 1. If your backup is currupt it will never work.
Sent from my SGH-I317 using XDA Premium 4 mobile app
I am currently trying to repair a soft bricked(stuck in boot loop) Samsung Galaxy S2. I am trying to save the info (contacts,sms,pictures..etc).
Would using Odin to flash CWM Recovery and doing a nandroid backup and then restoring the phone to factory settings.
Would it somehow save everything in the internal memory and fix the phone?
Please, If you can Update me with some info, I would greatly appreciate it.
Thanks
Might be possible, if you backup, reinstall a rom based the same update you're on and then do an advanced restore of just /data, Really depends on what made it soft brick in the first place though. You're pictures won't be touched either way, but contacts, messages, etc are a different story. Hopefully you had your phone synced to Google to backup the contacts at least...
Try This.
on CWM , you can do a backup.. then flash your previous rom before you get softbricked.
reboot.
cwm again,
Backup and restore >> andvance restore >> restore data
this usually works with me..