ROM manager do not backup - T-Mobile Samsung Galaxy S II SGH-T989

I was able to do backp using the ROM manager. Yesterday, I am not able to do back up. when it starts the backup of the data, it is not able to do so.
I decided to flash the backup I did with ROM manager last March 2. It restored it with no problem, I thought the issue might be because I installed an app that ROM manager doesn't play well with. But when I did a backup, it still showed the same problem.
How do I fix this?

Did you uninstall rom manager and reinstall it?
Sent from my SGH-T989 using XDA

tomasitoc said:
I was able to do backp using the ROM manager. Yesterday, I am not able to do back up. when it starts the backup of the data, it is not able to do so.
I decided to flash the backup I did with ROM manager last March 2. It restored it with no problem, I thought the issue might be because I installed an app that ROM manager doesn't play well with. But when I did a backup, it still showed the same problem.
How do I fix this?
Click to expand...
Click to collapse
I have this issue too, not everyone can do a backup through ROM manager for whatever reason. You'll just have to boot to recovery and do the backup manually.

A greedy dev with skewed priorities (money over functionality) is the problem.....
As others have mentioned, just reboot into recovery and perform the backup and you should have no issues. And stay away from the TOUCH version of the recovery.

G1ForFun said:
A greedy dev with skewed priorities (money over functionality) is the problem.....
As others have mentioned, just reboot into recovery and perform the backup and you should have no issues. And stay away from the TOUCH version of the recovery.
Click to expand...
Click to collapse
I wouldnt say koush is greedy, but your advice about booting into recovery for all related tasks is spot on.
Sent from my SGH-T989 using XDA App

born2gethard said:
Did you uninstall rom manager and reinstall it?
Sent from my SGH-T989 using XDA
Click to expand...
Click to collapse
I uninstalled and installed again the rom manager, still the same issue.
what I liked with rom manager is that I am able to name the backup.
I can back up thru recovery no problem.
Question:
How can I properly name/rename the backup in recovery?

G1ForFun said:
A greedy dev with skewed priorities (money over functionality) is the problem.....
As others have mentioned, just reboot into recovery and perform the backup and you should have no issues. And stay away from the TOUCH version of the recovery.
Click to expand...
Click to collapse
Hello g1forfun,
why do you say Stay away from touch recovery?

I've always had to do it manually in recovery. Selecting backup from ROM manager will cause my phone to reboot into recovery, but nothing further happens automatically lol. I feel more comfortable doing it myself anyway.

tomasitoc said:
Hello g1forfun,
why do you say Stay away from touch recovery?
Click to expand...
Click to collapse
Just because I have seen a lot of issues being reported with the touch recovery. Basically, it just does acts wonky at times.
Sent from my SGH-T989 using XDA

G1ForFun said:
Just because I have seen a lot of issues being reported with the touch recovery. Basically, it just does acts wonky at times.
Sent from my SGH-T989 using XDA
Click to expand...
Click to collapse
now i understand why you said stay away from touch recovery. I tried it, it is not good at all.

strange I tried to backup with rom manager, it worked!
I didn't do anything, it just fixed itself

Related

[Q] Broken system after restoring backup after trying MIUI

Hi,
I was fascinated by MIUI english version and I decided to try it out. Backuped my current setup (Virtuous 2.0.0 with custom kernel) twice then downloaded and installed MIUI us from ROM Manager Premium and it went fine. Decided to stay on my old setup for a while and restored it back.
Then noticed first this error message: "UID's on the system are inconsistent, you need to wipe your data partition or your device will be unstable." and button "I'm feeling lucky". Nothing works properly. Now I'm flashing MIUI again and try to get to use to it...
Tried many times to wipe and restore all over again. My backups should be fine. How to get my earlier system back or do I? What the error message means? Tried to google around and search from the forums but did not find much help...
If you can help, I would appreciate very much. Thanks.
Have you done a complete wipe?
Sent from my HTC Vision using XDA App
Are you referring to a nandroid? Nandroid would be the backup you made with either with rom manager or through recovery
If you made a backup through the above mentioned methods you should download superwipeG2 and flash through recovery. The "I'm feeling lucky" thing is nothing I've ever seen in recovery or rom manage so what are you talking about?
Sent from my HTC Vision using XDA Premium App
coachmoore said:
Have you done a complete wipe?
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Yeah.
Spastic909 said:
Are you referring to a nandroid? Nandroid would be the backup you made with either with rom manager or through recovery
Click to expand...
Click to collapse
Yeah, backup from clockworkmod recovery which I suppose is called "nandroid" backup?
Spastic909 said:
If you made a backup through the above mentioned methods you should download superwipeG2 and flash through recovery.
Click to expand...
Click to collapse
So now that I have nandroid backup I could do this "superwipe" (never heard of that before) and then flash the backup (=restore)? Am I misunderstanding something here..?
Spastic909 said:
The "I'm feeling lucky" thing is nothing I've ever seen in recovery or rom manage so what are you talking about?
Click to expand...
Click to collapse
I admit I was a bit unclear. This message and button showed up when I rebooted to system after restoring backup, when some of the stuff seemed to be there, but some not (theme was broken, some apps were not installed etc), not a fully restored backup I guess...?
I don't really want to go gack to Virtuous now that I'm fallen in love with MIUI, but I'm curious to know what caused this?

What's wrong with my phone

Ok I'm really irritated right about now. I am unable to flash any custom ROMS on my phone. Actually let me rephrase, I can flash them but many things do not work. I have tried Wicked, FreeGS3 and CapROM. They all have the same issues. Let me explain.
Once the ROM is booted I get odd string of numbers and TXT in the status bar, (goes away, think nothing of it)
Root not avail/accessible by root apps.
Home button does not work
Play store missing
standard Google login prompt at first boot is missing, it never asks me to login
Using CWM 5.8.4.5 Touch Recovery
TMO GS3 Rooted with Odin no trip method
I don't get it. I am i just stuck using stock ROM? If anyone can help I would love you forever.
are you clearing /cache and dalvik-cache before you reboot to the custom rom?
mrmako777 said:
are you clearing /cache and dalvik-cache before you reboot to the custom rom?
Click to expand...
Click to collapse
If you mean clearing those after the install (in recovery completes) then no. Basically after the install I just reboot. Obviously clear and reset everything before I install though.
hd2Raz said:
Ok I'm really irritated right about now. I am unable to flash any custom ROMS on my phone. Actually let me rephrase, I can flash them but many things do not work. I have tried Wicked, FreeGS3 and CapROM. They all have the same issues. Let me explain.
Once the ROM is booted I get odd string of numbers and TXT in the status bar, (goes away, think nothing of it)
Root not avail/accessible by root apps.
Home button does not work
Play store missing
standard Google login prompt at first boot is missing, it never asks me to login
Using CWM 5.8.4.5 Touch Recovery
TMO GS3 Rooted with Odin no trip method
I don't get it. I am i just stuck using stock ROM? If anyone can help I would love you forever.
Click to expand...
Click to collapse
Touch recovery might be your problem
Sent from my SGH-T999 using Tapatalk 2
horr1blek1tten said:
Touch recovery might be your problem
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
Really? A recovery can cause these kinds of issues. Haven't heard of that before. Any other thoughts? What recovery are you using?
Try TWRP 2.2.1.1
hd2Raz said:
Really? A recovery can cause these kinds of issues. Haven't heard of that before. Any other thoughts? What recovery are you using?
Click to expand...
Click to collapse
Yeah I've heard touch recovery has its problems so I don't use it. Try using the recovery rom manager gives you.
Sent from my SGH-T999 using Tapatalk 2
horr1blek1tten said:
Yeah I've heard touch recovery has its problems so I don't use it. Try using the recovery rom manager gives you.
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
I use TWRP and have no problems.
Do a Factory reset, wipe cache, wipe dalvik cache, fix permissions.
If that doesn't work, flash stock and reroot and try again.
I use touch recovery 5.8.4.7 and flashed it with adb. I've flashed almost everything. Cyanogenmod and every other ROM. NEVER had a problem with an instalation. Or even lost IMEI. I think people specifically aren't reading over OP's and figuring out what's safest for their devices and end up with these kind of results. Just my input.
Sent from my SGH-T999 using xda premium
Use mskips tool for our phones. It does everything you can image and then some. I have been using his tools since the HD2 and no issues to date.
The odd string of numbers that flashes upon boot in the status bar sounds like it's just identifying your external sd card. Totally normal.
OK so nothing worked. TWRP did the same thing. Tried diff ROM, same thing. I flashed back to 100% stock, unrooted ROM. Wiped the phone in the standard Android recovery. Then I rooted again, installed TWRP and flashed my ROM of choice and voila. Everything works. Problem solved. Thanks all for the inputs.

Couple of problems after flashing roms

Alright, so I was running MIUI on my phone, and I decided to check out some other roms. I flashed the All Stars rom, wasn't too fond of it, then I flashed CM10. After flashing CM10, the default android keyboard kept crashing (it would continually pop up saying it has stopped every few seconds or so.) Also, my when I unlock my phone, there is no lock screen. Thirdly, my home button, well, doesn't do anything when I push it.
I'm really not sure what to do at this point, I flashed AOKP and the problems still persist. Any ideas on what I could do? Thanks.
What recovery are you using?
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Wolfygang said:
What recovery are you using?
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
cwm 5.0.2.7
Here's an update, I unrooted my phone, flashed back to stock and everything worked fine, rooted again, still fine. Now whenever I flash a rom, the problem comes up again. The default stock browser isn't working either. Any help on what is going on would be greatly appreciated!
if you're using cwm 5.0.2.7, then you need to use darkside scripts.
merrygocow said:
if you're using cwm 5.0.2.7, then you need to use darkside scripts.
Click to expand...
Click to collapse
I am using them.
teeson24 said:
I am using them.
Click to expand...
Click to collapse
If CWM 5.0.2.7 is still not working for you, update to CWM 6.0.x.x or even better try flashing and using the latst TWRP recovery system.
Make sure you do the proper data/cache wipes before flashing the ROM again. Also, flashing the proper Gapps file for the specific ROM may help you fix the issue you are having with the home button and possibly the application issues you are having.
FineTalent said:
If CWM 5.0.2.7 is still not working for you, update to CWM 6.0.x.x or even better try flashing and using the latst TWRP recovery system.
Make sure you do the proper data/cache wipes before flashing the ROM again. Also, flashing the proper Gapps file for the specific ROM may help you fix the issue you are having with the home button and possibly the application issues you are having.
Click to expand...
Click to collapse
Actually, it's 6.0.2.7, I either mistyped or misread it, my bad. Going to try TWRP tomorrow, thanks for the help and will post updates.

Phone won't boot into recovery?

Hi guys, so I was using wicked ROM, whenever I tried to boot into recovery, it just rebooted back to system. Odin'ed back to stock, flashed twrp through goo manager app, but still no use. Any help greatly appreciated
Sent from my Nexus 7 using xda premium
eggydrums said:
Hi guys, so I was using wicked ROM, whenever I tried to boot into recovery, it just rebooted back to system. Odin'ed back to stock, flashed twrp through goo manager app, but still no use. Any help greatly appreciated
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
What methods have you tried?
adb reboot recovery is the easiest way to get to recovery
Maybe try flashing CWM, seeing if that works, and then flashing TWRP (I've never flashed TWRP through Goo Manager so I don't know how that works)?
If you don't have adb set up, get quick boot from market and try recovery through that.
If that doesn't work, I honestly don't know. I'm assuming you've done the power off then volume up+home+power at the same time trick already.
EtherealRemnant said:
What methods have you tried?
adb reboot recovery is the easiest way to get to recovery
Maybe try flashing CWM, seeing if that works, and then flashing TWRP (I've never flashed TWRP through Goo Manager so I don't know how that works)?
If you don't have adb set up, get quick boot from market and try recovery through that.
If that doesn't work, I honestly don't know. I'm assuming you've done the power off then volume up+home+power at the same time trick already.
Click to expand...
Click to collapse
With the goo app, I can boot directly into recovery, but my issue is that I get to the Recovery's splash screen, it hangs there for a second and immediately reboots back to system. I'm thinking to get the stock recovery back and try again I'm really not sure what the Hecks going on
Sent from my Nexus 7 using xda premium
Mhm OK, got cwm working, guess I'll just use that one for the time being
Sent from my Nexus 7 using xda premium
eggydrums said:
Mhm OK, got cwm working, guess I'll just use that one for the time being
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
I would highly recommend putting TWRP back on there. The CWM was more for testing... people have reported issues using CWM with certain ROMs. Glad you were able to get CWM on though.
Nothing wrong with CWM.
Aerowinder said:
Nothing wrong with CWM.
Click to expand...
Click to collapse
There are a number of ROMs that do not support CWM so that statement is false. FreeGS3 loses update functionality, for example.
Also, there have been complaints in the case of CWM touch of it being too easy to wipe your entire device.
Not to mention there is no Goo Manager functionality without TWRP as well.
Lots of benefits of TWRP versus CWM. I used CWM for years then had to switch to a modified TWRP for my MAXX and was more than happy when I found out the SGS3 used TWRP as well (although I wish we had the ROM slots like the MAXX though - that was actually cool)
The statement is not false. I think FreeGS3 hasn't been updated for 4.5 months? Maybe not the best example. And I still think you should use as few automated tools as possible where flashing is concerned (Goo/ROM Manager).
It can be easy to wipe the wrong partition in CWM, if you are careless or illiterate. In the 6 months that I've used it (nearly every day), I have never once wiped the wrong partition, or my entire device. Never had a backup that wouldn't restore.
I like some of what TWRP offers. But I still experience showstopping bugs with it on my device. At this time, the devs are unable to track down the cause of the problems.
Aerowinder said:
The statement is not false. I think FreeGS3 hasn't been updated for 4.5 months? Maybe not the best example. And I still think you should use as few automated tools as possible where flashing is concerned (Goo/ROM Manager).
It can be easy to wipe the wrong partition in CWM, if you are careless or illiterate. In the 6 months that I've used it (nearly every day), I have never once wiped the wrong partition, or my entire device. Never had a backup that wouldn't restore.
I like some of what TWRP offers. But I still experience showstopping bugs with it on my device. At this time, the devs are unable to track down the cause of the problems.
Click to expand...
Click to collapse
Don't get me wrong, I've used CWM on many devices for years and even have a premium license for ROM Manager but I've seen a number of ROMs explicitly say not to use CWM, FreeGS3 was just the first that came to mind. I don't flash often because quite frankly, I have no problems with Wicked v8 and see no reason to switch to anything else.
And I am neither careless nor illiterate but I have accidentally borked things using CWM before in the past (it was a modified CWM Touch recovery) and I was not happy.
I think most of the complaints about CWM these days though come from CWM Touch, not regular CWM. Sorry TWRP has issues for you.
OK, so I'm getting a new issue, I changed to AOKP and I had problems with the ROM saying I needed to wipe data, I did, the issue persisted for few reboots, now apps won't install, and for some reason the /data folder still displays apps from my previous ROM ugh I don't know what's happening
Oh and for some reason the app exchange service kept force closing
Sent from my Nexus 7 using xda premium
eggydrums said:
OK, so I'm getting a new issue, I changed to AOKP and I had problems with the ROM saying I needed to wipe data, I did, the issue persisted for few reboots, now apps won't install, and for some reason the /data folder still displays apps from my previous ROM ugh I don't know what's happening
Oh and for some reason the app exchange service kept force closing
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Which recovery? Try erasing data, cache, and system three times each and reinstalling the ROM... If that doesn't work you might consider doing a back up of everything internally stored on your phone and then wiping the internal storage entirely and starting over.
EtherealRemnant said:
Which recovery? Try erasing data, cache, and system three times each and reinstalling the ROM... If that doesn't work you might consider doing a back up of everything internally stored on your phone and then wiping the internal storage entirely and starting over.
Click to expand...
Click to collapse
I tried. I think for some reason, the recovery isn't wiping data, even though it says so. I'm using twrp
Managed to install apps through the play website, still no go with the play store app though
Sent from my Nexus 7 using xda premium
eggydrums said:
I tried. I think for some reason, the recovery isn't wiping data, even though it says so. I'm using twrp
Managed to install apps through the play website, still no go with the play store app though
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Hmmm... Have you tried doing it through CWM? Its starting to sound like your partitions are messed up.
EtherealRemnant said:
Hmmm... Have you tried doing it through CWM? Its starting to sound like your partitions are messed up.
Click to expand...
Click to collapse
I think that's a possibility I just tried through clockwork, and it's all good now but exchange service fcs here and there
Sent from my Nexus 7 using xda premium
eggydrums said:
I think that's a possibility I just tried through clockwork, and it's all good now but exchange service fcs here and there
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Did you fix permissions?
EtherealRemnant said:
Did you fix permissions?
Click to expand...
Click to collapse
I tried while I was in twrp, it failed, something about a an error "failed to chmod data/data/ email.apk" (not exactly like that)
Sent from my Nexus 7 using xda premium

[Q] Such bad luck with recoveries

Ok, I've tried several different roms and I always back up. I've used Oudhs, Clocworkmod and TWRP. No matter which one I back up with I never have any luck on restore. They all seem to restore ok but I get stuck in boot loops everytime. Factory reset doesn't help. Wiping caches don't help. This is just beginning to really drive me nuts. I don't really mind having to reinstall everything but jeez I just wish I knew what the deal was. I never had trouble on my Motorola Defy or my Galaxy S2 but I sure can't seem to get anywhere on the S4
It happens sometimes to me. When I get stuck after restoring nandroid, I get back into recovery and reflash the kernel and it boots the device. I am using philz recovery and its been working great.
Sent from my SM-N900T using Tapatalk
Have you tried PhilzTouch yet?
Alex9090 said:
It happens sometimes to me. When I get stuck after restoring nandroid, I get back into recovery and reflash the kernel and it boots the device. I am using philz recovery and its been working great.
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
lalec said:
Have you tried PhilzTouch yet?
Click to expand...
Click to collapse
Never used philz and never thought of just reflashing the kernel. I may try that though. Now to find the kernel. I should mention that I end up using Odin to reflash stock. Then I root and then custom recovery. That boots fine and for the most part all I'm ever doing is trying to restore a 4.4 rom I backed up.
Flashing a kernel worked. lol my phone doesn't think it's the stock kernel but it booted at least.
I do find this interesting. I would think when you restore a nandroid backup that it would restore the kernel that was with the rom you are restoring. I guess this isn't the case?
Using the latest clockwork has always worked for me.
Sent from my SGH-M919 using XDA Premium 4 mobile app
I use ROM manager premium, as well.
Sent from my SGH-M919 using XDA Premium 4 mobile app
Android_Monsters said:
I use ROM manager premium, as well.
Sent from my SGH-M919 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I've had Rom Manager Premium since my Defy days. I'm a firm believer in it. I was just surprised I would have to reflash a kernel after restoring a rom.
Corwinder said:
Ok, I've tried several different roms and I always back up. I've used Oudhs, Clocworkmod and TWRP. No matter which one I back up with I never have any luck on restore. They all seem to restore ok but I get stuck in boot loops everytime. Factory reset doesn't help. Wiping caches don't help. This is just beginning to really drive me nuts. I don't really mind having to reinstall everything but jeez I just wish I knew what the deal was. I never had trouble on my Motorola Defy or my Galaxy S2 but I sure can't seem to get anywhere on the S4
Click to expand...
Click to collapse
I use OUDHs Touch recovery v1.0.3.3 in conjunction with Rom Manager and I have NEVER had that problem. Also, when I use Rom Manager to "Back Up Current Rom" I can NAME the backup file, and it goes into the recovery and uses the filename I have already typed in and it's a seamless operation. Even using restore via Rom Manager works seamlessly and it has NEVER balked on me.
The only time I had a problem was once using My Backup Pro and trying to do an on-line system backup. MMS, SMS, Call Log has always been absolutely perfect! No out of sequence messages, and all the pictures are restored correctly too!
Aloha and Good Luck!
BTW, I am on a Stock 4.2.2 with the latest M919UVUFNB4 (modem.bin) Flashed for the radio and it's reception qualities are better than it's ever been before!

Categories

Resources