every time I try to create a backup through recovery, its never successful. either it would get stuck at backing up system (or at backing up data) or it would give me an error message asking if I want to report it through ROM manager. I realized that it would get stuck at system (and/or at data) because the partitions weren't mounted. I've tried to remount them through recovery and through various file managing apps, but nothing seemed to work. I've been getting the "failed to mount /system (or /data)” message. what the hell is up with my phone?!
I'm using clockworks 6.0.4.3
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
xenelym said:
every time I try to create a backup through recovery, its never successful. either it would get stuck at backing up system (or at backing up data) or it would give me an error message asking if I want to report it through ROM manager. I realized that it would get stuck at system (and/or at data) because the partitions weren't mounted. I've tried to remount them through recovery and through various file managing apps, but nothing seemed to work. I've been getting the "failed to mount /system (or /data)” message. what the hell is up with my phone?!
I'm using clockworks 6.0.4.3
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
where did you get 6.0.4.3
rom manager?, are you doing from recovery or rom manager, if doing it from rom manager dont use rom manager for anything related to recovery.
are cards full?
I believe so. I've tried backing up through both recovery and rom manager but nada. the last time I was able to successfully complete a backup was about a month ago when I unsuccessfully flashed slimkat and flashed slimbean right after. but ever since then it hasn't allowed me to. im also wondering why im unable to mount /system and /data partitions. I was thinking I should revert back to stock and start all over again....but would that even fix anything?
Sent from my SAMSUNG-SGH-I727
There are only 2 recoveries I'm aware of capable of flashing any 4.4 ROM.
As for backup and restore depends on what Roms you're trying to backup.
Sent from my SGH-I727 using Tapatalk
so the fact that my phone isn't mounting /system and /data has nothing to do with why I can't create a backup? restoring a backup isn't an issue, being able to make a backup for future restoration is. lol. and i checked my SD cards, they aren't full, so that's not the error I'm receiving. idk. I'm stumped.
Sent from my SAMSUNG-SGH-I727
.....still stuck on stupid.
I'm still stumped. I don't know how to go about this issue. Can anyone help a girl out and point me in the right direction?
xenelym said:
I'm still stumped. I don't know how to go about this issue. Can anyone help a girl out and point me in the right direction?
Click to expand...
Click to collapse
can u copy anything to ur cards, if not do the last part of q.25b in READ THIS B4 POSTING | THE MOST Common Questions Answered HERE, if yes do it anyways
Related
My recovery wont restore any backups I make. This may be an easy fix and I'm sure I'm asking a stupid question but I can't seem to get it to restore a back up. I get an error when it trys to. I'm on CWM-based Voodoo Lagfix Recovery v5.0.2.7.
what error do you get?
Sent from my SGH-T959V using xda premium
Let me guess... Cant mount system in the restore feature. I use titanium back and just use flashable roms if i need to restore... Dont know any other way around it. Maybe someone else does.
Sent from my SGH-T959V using XDA
5.0.2.7 shouldn't have the issue with being unable to mount /system.
What error or message do you get when you try to restore?
I'm getting the mount/system error. I thought flashing the new cwm recovery and kernel would have gotten rid of that problem. It never did. I still get the same error.
And your trying to restore back ups made with CWM 5. Not CWM 3 right.
if the backup was made with cwm 3.x it won't restore with cwm 5.x and vice versa.
Also, GB roms had issues restoring backups made with cwm 3.x - you had to flash a clean rom, and then do an advanced restore, and restore data only.
Helllo everyone, I have problem in restoring nandroid backups generated by CWM 5.0.2.0
When I restore backup, I get boot loops and cleaning up dalvik cache and cache wont help. First i thought it maybe a random error but it has happened even after lot of tries. I dont have a faulty sd card.
The backup i was trying to restore was of oxygen 2.3.2 with a theme installed + some apps
Can anyone suggest a a solution?
If you are getting bootloops then sorry to say the backup is not a healthy one, you need to reflash ROM. I also had problems with themes installed, now I made a backup keeping everything stock with apps.
Oxygen has inbuilt app2sd script. This causes problems many times. I would recommend restoring the system first, boot it up den restore both data and sdext.
sarus_b said:
Helllo everyone, I have problem in restoring nandroid backups generated by CWM 5.0.2.0
When I restore backup, I get boot loops and cleaning up dalvik cache and cache wont help. First i thought it maybe a random error but it has happened even after lot of tries. I dont have a faulty sd card.
The backup i was trying to restore was of oxygen 2.3.2 with a theme installed + some apps
Can anyone suggest a a solution?
Click to expand...
Click to collapse
Switch to twrp or amonra(if I'm not mistaken amonra can restore cwm backups).
Sent from my LG-P500 using xda premium
if Im not mistaken, we can flash a recovery within a recovery right?
sarus_b said:
if Im not mistaken, we can flash a recovery within a recovery right?
Click to expand...
Click to collapse
Yes, just download xxx.zip and flash, no problems, also they are very stable if you are wondering...
Sent from my LG-P500 using xda premium
You could have an error, like bad block, in your internal memory. To rule that out, install some other ROM fresh & see if you get errors.
-- Sent from my TouchPad using Communities
If the backup isn't restoring, then you should try restoring the backup, then reflashing the rom. I would recommend switching to amon ra recovery or twrp since they don't have that problem and imho they're better.
It seems the theme I installed had some problems since they replace system files such as framework-res.apk , settings.apk etc.
I flashed clean oxygen, installed lot of apps, created and restored the backup and it seems to work flawlessly now.
post-mortem said:
You could have an error, like bad block, in your internal memory. To rule that out, install some other ROM fresh & see if you get errors.
-- Sent from my TouchPad using Communities
Click to expand...
Click to collapse
Thats not the case, if it was i would have phone's PCB replaced by now.
bluespoon4 said:
If the backup isn't restoring, then you should try restoring the backup, then reflashing the rom. I would recommend switching to amon ra recovery or twrp since they don't have that problem and imho they're better.
Click to expand...
Click to collapse
This solution may also work i think.
I've had my Photon Q for 4 days. I unlocked the bootloader, flashed CWM, and rooted using instructions in this forum and everything was working great. I had not flashed any other mods.
I bricked it today by accidentally formatting the internal SD card instead of the external one. It would only reboot into recovery (CWM) and I couldn't mount the internal SDcard from CWM. After reading several threads here I managed to get into Fastboot Mode and flash TWRP, Then, I downloaded the back-up system and boot files posted here:
http://forum.xda-developers.com/showpost.php?p=34555560&postcount=11
and placed them in the TWRP back-up folder on my external SD card as instructed.
When I try to restore from this backup I get an md5 match failure. I also tried moving the backup to the internal SDcard using the file manager in TWRP and got the same result.
Also, TWRP (2.3.3.0) isn't playing nice on my device. All the functions seem to work, but It displays the menus twice in side by side columns, though the touch controls are where they are supposed to be.
Any suggestions?
Don't use the latest TWRP. I need to get with Dees_Troy to sort out what happened with the latest version.
Edit - I think 2.3.1.0 is the latest version that works.
Wow, sounds really familiar. I did the same exact thing. Took me forever to figure out how to fix it. Have you gotten twrp back on?
Sent from my XT897 using xda app-developers app
still bricked
befrosty8612 said:
Wow, sounds really familiar. I did the same exact thing. Took me forever to figure out how to fix it. Have you gotten twrp back on?
Sent from my XT897 using xda app-developers app
Click to expand...
Click to collapse
TWRP is sorted, still having trouble getting the restore to take. I'll post again if I get it figured out
I have what seems like a very basic question on backing up using TWRP, and yet I havent been able to find this anywhere in the help threads.
When I am creating a backup it asks for what I want to backup: System, Data, Boot, Recovery, Cache, .android_secure.
Which of these do I want to make sure are checked? The first backup I did I left the default (which was only System and Data) and now I am unable to restore to that backup (I just get a blank, dark screen). Looking through the forums it seems I may need to flash boot.img in order to restore?
So does that mean in the future I should make sure to also check the Book option when I create backups? Any others?
Thanks.
system, data, boot
leave the other 3 unchecked
vincom said:
system, data, boot
leave the other 3 unchecked
Click to expand...
Click to collapse
Thanks again for all of your help over the last few days!
Would the failure to check Boot on my first backup be the reason I am getting that blank screen when I try to restore? And is this fixable by flashing "boot.img" if I can find it somewhere?
Would the failure to check Boot on my first backup be the reason I am getting that blank screen when I try to restore? > yes
And is this fixable by flashing "boot.img" if I can find it somewhere? > yes from another backup from siimar rom through the backup utility from twrp, but just flashing a rom would be easier
vincom said:
And is this fixable by flashing "boot.img" if I can find it somewhere? > yes from another backup from siimar rom through the backup utility from twrp, but just flashing a rom would be easier
Click to expand...
Click to collapse
You could probably just flash the same ROM you made the backup from and then just restore the data from that backup through TWRP. Then you'd be back to the same setup you tried to backup originally, right?
Sent from my SAMSUNG-SGH-I897 using xda app-developers app
If you want your backup to work after you do it - don't touch the default selection.
And this is also the reason you don't see any threads about it. All those who don't understand what each partition does just don't touch anything, and all those that understand don't write about it.
Read more to see why the first suggestion you got (system, data, boot) might fail you.
Backing up recovery in recovery is useless, though.
Jack_R1 said:
If you want your backup to work after you do it - don't touch the default selection.
And this is also the reason you don't see any threads about it. All those who don't understand what each partition does just don't touch anything, and all those that understand don't write about it.
Read more to see why the first suggestion you got (system, data, boot) might fail you.
Backing up recovery in recovery is useless, though.
Click to expand...
Click to collapse
My initial backup was made just with the default - first two boxes ticked. Unfortunately I now cannot get that backup to recover and boot, which is why I am asking. What else might be the cause or how would you suggest I try to solve?
Also, apologies but I dont understand what you mean when you say "Backing up recovery in recovery is useless, though." Do you mean this isnt the best way to make a backup/nandroid to recover to?
Alright, here's a short explanation to get you started:
/boot - your kernel partition. Without it the ROM won't boot.
/system - your ROM.
/data - user data, all the apps and app settings that user has.
/.android_secure - all the apps that are on SD (or USB storage).
/cache - temporary place for storing downloads, exchanging data with recovery and such.
/recovery - where your recovery resides.
From this you should be able to understand why it's useless to backup recovery partition - you won't be able to restore it if you don't have custom recovery in place, and if you have custom recovery in place - you don't need to restore this partition, it's already populated.
This should also tell you why you need .android_secure. Some apps are still installed by default to SD card, and these will be lost if you don't back it up.
Jack_R1 said:
Alright, here's a short explanation to get you started:
/boot - your kernel partition. Without it the ROM won't boot.
/system - your ROM.
/data - user data, all the apps and app settings that user has.
/.android_secure - all the apps that are on SD (or USB storage).
/cache - temporary place for storing downloads, exchanging data with recovery and such.
/recovery - where your recovery resides.
From this you should be able to understand why it's useless to backup recovery partition - you won't be able to restore it if you don't have custom recovery in place, and if you have custom recovery in place - you don't need to restore this partition, it's already populated.
This should also tell you why you need .android_secure. Some apps are still installed by default to SD card, and these will be lost if you don't back it up.
Click to expand...
Click to collapse
Thanks. I think I misunderstood your initial post. When you said "system, data, boot" advice might fail me, I thought you meant NOT to backup boot. But I think you meant to ALSO backup .android_secure, not to avoid backing up boot.
When doing a recover, is it generally advised to do full cache, davlik wipe and factory reset, like when flashing a new ROM?
lirong said:
When doing a recover, is it generally advised to do full cache, davlik wipe and factory reset, like when flashing a new ROM?
Click to expand...
Click to collapse
I never do any of the wipes and never have had a problem when restoring a nandroid.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
jd1639 said:
I never do any of the wipes and never have had a problem when restoring a nandroid.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
and you're totally wrong...the only "cleaning" the restore function is doing is erasing boot before restoring (to at least protect from statements like yours) , imagine you restore a windows image over another windows installation ...
mahanddeem said:
and you're totally wrong...the only "cleaning" the restore function is doing is erasing boot before restoring (to at least protect from statements like yours) , imagine you restore a windows image over another windows installation ...
Click to expand...
Click to collapse
Only erasing boot? So the only thing that remotely connects to what you're saying would be boot.IMG which is the kernel in which case you would be incorrect. Please if you plan on correcting someone at least be concise so people understand the point you are trying to convey.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
mtdew said:
Only erasing boot? So the only thing that remotely connects to what you're saying would be boot.IMG which is the kernel in which case you would be incorrect. Please if you plan on correcting someone at least be concise so people understand the point you are trying to convey.
Click to expand...
Click to collapse
LOL. Can't we all just get along.
Since I'm not one to speak for others I'll only guess that what he was trying to get at is restoring only erases the boot.img. It then restores boot.img, system, data, android.secure, and cache. So in theory it doesn't actually erase any of the remaining partitions. It just writes over them. Whether or not this leaves any residual parts of any of the partitions has been a source of debate for quite some time. If it does format the partitions before restore there is no indication textually that I have seen.
Carry on.
EDIT: I might as well point this out before some one else does. The restores I stated above where done from CWM not TWRP. I forget what the thread was originally about. For that I apologize. The logic behind the post stands for either recovery though.
mahanddeem said:
and you're totally wrong...the only "cleaning" the restore function is doing is erasing boot before restoring (to at least protect from statements like yours) , imagine you restore a windows image over another windows installation ...
Click to expand...
Click to collapse
Maybe. But a couple of points. First, I've never had any issues. Second, have you watched what happens when you restore?
Wiping system.....
Formatting system....
Restoring system....
Wiping data....
Formatting data....
Restoring data....
Restoring boot...
This is on twrp 2.3.3.0 and 2.4.0.0. So technically it does the wipes for you.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
So TWRP restore system, data, cache before boot ? Big fail...
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
mahanddeem said:
So TWRP restore system, data, cache before boot ? Big fail...
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Is this even English because I can't understand the point of this sentence. Was it meant to be an insult? It honestly makes no sense.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
mtdew said:
Is this even English because I can't understand the point of this sentence. Was it meant to be an insult? It honestly makes no sense.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
It's Japanese
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
mahanddeem said:
It's Japanese
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
So basically you have no idea what you're saying. I guess I'll go back to my being concise point
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
mahanddeem said:
So TWRP restore system, data, cache before boot ? Big fail...
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
You're obviously a CWM guy. I'm a TWRP guy. Both are good recoveries and used by many. So use what you're comfortable with and you know works.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Hey all,
Recently, I had an issue with the SD card in my skyrocket. Phone will get stuck at custom boot screen for a while. After finally booting, I noticed I had to reinstall some apps...not all.
Anyways,
Right after this happened, I noticed that I could no longer perform a clockwork mod backup as I have done with no issues. It gets stuck randomly during the system files backup state. What can I do to fix this?
I have tried many things, including fix per, flash new cwm version and format new card and copy over all files previously other. Nothing seems to work.
Any help is appreciated...
Thanks
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
I would flash back to stock reload the whole initial bootloader and stock recovery then go and redo the actual superuser then put on the custom recovery try TWRP or you can try cwm again nothing against skaters CWM twrp is just easier for me
Ahh, was not familiar with twrp and have always used cwm. However, after your reply and downloading and flashing it, I must say I love the GUI and ease of use.
Anyways,
I flashed it and did perform a backup. While I did get two errors, it did actually complete and I believe it did save data to this SD card. Should I worry about the errors though?
What's the difference between this from recovery tool and cwm? Still can't get cwm to backup after that SD card issue.
Thank you much for quick reply
--mike
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
pookieguy said:
Ahh, was not familiar with twrp and have always used cwm. However, after your reply and downloading and flashing it, I must say I love the GUI and ease of use.
Anyways,
I flashed it and did perform a backup. While I did get two errors, it did actually complete and I believe it did save data to this SD card. Should I worry about the errors though?
What's the difference between this from recovery tool and cwm? Still can't get cwm to backup after that SD card issue.
Thank you much for quick reply
--mike
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
if your not having issue with twrp then i wouldnt worry there has been alot people that said thta sk8ters recovery was giving issues never personally had any trouble when i used maybe just bad recovery.. sometimes thing act wonkie for no reason
Thanks...
Should I worry about the two errors even if it did complete?
Also, how do you restore?
I tested by booting to twrp and hit the restore button. I browsed to directory on SD card where backup is but not sure what file to chose?
Thanks again...
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
pookieguy said:
Thanks...
Should I worry about the two errors even if it did complete?
Also, how do you restore?
I tested by booting to twrp and hit the restore button. I browsed to directory on SD card where backup is but not sure what file to chose?
Thanks again...
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
I don't use twrp but shouldn't the backup be named after the time/date it was created. If that's true then you should know which backup to choose by looking at the time/date.
I'm thinking the folders for the failed backups are also there..