1. Hi, I have a locked ST18a that was on Forsaken GB v3.0 as of recent. While I was on the rom, curiosity got the better of me I applied part of the root keeping process as found in the m/h dpi root tutorial, the local prop hack. It was my intention to upgrade to ICS, but I was wondering what would happen if I tried to do it straight from a custom GB rom (bad idea, I know) and continued from there. The script created a /data/local.prop to enable android emulator hack. I then went into recovery and made a nandroid backup (I know I should have done it before applying anything new) and it carried on without a hitch. However, when I powered off and back on, I was stuck on the boot logo. No matter what I did, I couldn't get it to work, so I went to flashtool and flashed stock GB, then rooted and installed recovery again. I then went into recovery and restored my nandroid, but I had the same issue again. I reflashed stock, but this time I went all the way to rooted ICS and installed appextractor, to restore my appdata and sms data from the weird nandroid. I could install apps, but could not restore their data or my messages. So, with all this background info, can adding a local.prop mess up a nandroid that badly? Was appextractor not working as a result of that nandroid with local.prop, or is it appextractor's problem? Also, I had backed up my messages through sms backup as well. A local.prop shouldn't have any effect on a xml. type backup, right? My sms backups would not restore either.
Edit: Was able to extract asp data through titanium backup, but there's an error with the xml and I still can't restore my messages.
2. Also, while this is a completely different issue, I noticed that although they are the same recovery and should both be in /system, the CWM from xParts and RecoverX tools (the same 5.0.27 by nobodyAtall) seem to be different. If I format /system (a requirement for roms I use with locked bootloader) on the xParts version of the recovery, nothing happens. I am able to continue my flashing process. However, when I try that with the RecoverX version of CWM, the recovery crashes and I am stuck on a blank screen no matter what I do. What is going on here?
3. Also, one more question: I have the ST18a, the North American version of the Xperia Ray. All roms are developed as ST18i roms. I've been googling some info, and there doesn't seem to be any negative effects after installing an ST18i firmware or rom on my ST18a, but I did notice weaker signal (bigger dBm, eg -85 instead of -77), and faster battery drain in standby and normal usage than if I had a stock ST18a rom. What difference do the different frequencies make?
Could you please answer my three questions? And sorry for the long paragraphs.
Related
Apologies if this is the wrong forum.
The update notice came through on my phone yesterday afternoon. From reading on here I knew that a number of people were having problems with it. Like a meth addicted crackwhore I couldn't say no.
Before saying yes, I did make a backup.
Here's what I had on my phone beforehand:
Modified swype overlay
Modified battery icon
OCLF 2.1+
GPS fix update
I'd renamed the startup video so it wouldn't show
I'd replaced the startup sound with my own
I think that's all.
I did a nandroid backup before applying the update and even made a copy of the backup just in case.
I undid the lagfix but - perhaps stupidly - left all the other updates in place.
After applying the update my phone was stuck at the vibrant screen right after boot. No amount of waiting - 30 minutes the first time - did any good.
I've been through several rounds of flashing using the second round of steps in this thread but the best that happens is when the phone boots I see the stock home and the media,calendar,(+a few others I can't recall) FC continuously and the home shows a bunch of missing widget boxes.
If I do a nandroid restore I strangely end up with the hung vibrant screen again. It's like it's automatically applying the update or something other odd like that.
I can repartition and flash stock or the updated rom and things are working fine but I'd really rather not lose my data.
It occurred to me this morning that I might have done the backup before removing the lag fix. I'm guessing the backup won't recreate the ext2 partition and that's why things are FC'ing like mad?
I'm going to - probably pointlessly - try to re-flash, install the lag fix and do a restore to see if anything different happens.
If anyone else has a suggestion while I wait for my phone to charge enough to do the lag fix .... little tiny voice... <help?>
Well, re-installing oclf 2.1 didnt change the behavior. I've still got a brick after restoring my nandroid backup.
I've gone back to a clean ji6 install and I'm trying a titanium restore. I'll be a week out of date if this works but won't lose anything critical. If this works. I hope, I hope, I hope.
That happen to me too, had to odin back to stock then flash bionix 1.7. lost all my data
How about flashing JI6, applying OCLF, booting into clockwork recovery and selecting Nandroid-> Advanced-> (Your restore file)-> Data-> Yes.
This will reflash all your data on top of the new rom. The reason for reapplying the OCLF is because you backed up BEFORE undoing OCLF, so all your data is still in a .EXT2 file, so we have to have it expecting that before restoring.
Only thing left to do at this point is redo any themes you had installed, and your phone should be back to normal + the update.
I must have backed up after removing OCLF because I ended up flashing stock and restoring just the data. Unfortunately while the data was there, none of my apps were so the fact that the data was there was moot since I couldn't get at a lot of it.
I followed up by flashing just system and now I've got my full functionality back just without ji6.
I'll probably try again after rolling back a few more changes -such as removing the rom manager update.zip - and making another backup or three.
I wonder if the people who've rooted - like me - are having problems because of updated versions of busybox that clockworkmod installs.
Also, the titanium restore worked on stock. I haven't tried it on ji6. yet.
After all the forced learning by doing where flashing roms is concerned I decided to skip the tmo update since they can't be bothered to provide a full list of fixes. I've installed the latest bionix and couldn't be happier.
phillipxenxciel said:
That happen to me too, had to odin back to stock then flash bionix 1.7. lost all my data
Click to expand...
Click to collapse
I've found that a Titanium backup is enough to use when flashing a new rom. Do a full backup. Flash the new rom. Restore apps+data. Selectively restore the green system items (so you get all your sms msgs and contacts). Enjoy. Worked for me on Sunday as I flashed various versions of bionix to try.
Hello, I need some help with restoring via CWM on the Galaxy S3.
On the S2 I pretty much always used CM9 and jumped back and forth between versions and backing up/ restoring was never an issue.
Now however I am using the stock ROM and its rooted of course.
I made a back up of my stock rom 'cause I wanted to try and install some stuff.
I tried installing the jelly bean transition effects but the install failed, the device felt kinda sluggish (maybe my imagination) afterwards so I decided to restore my phone. The restoring went good but the last ting that happens is that CWM says that restoring /Data failed.
I reboot my phone and I come to the first start up screen where I get to choose language and so on. Everything but photos has been deleted. I try to install CM9, and I do that without any issues. Then I trie to backup my stock backup but I get the same error message and I get back to stock setup page.
My backup is a staggering 6GB, and I read somewhere that CWM can only restore 2GB?
I've deleted that backup and done another one but that is also 6GB.
Does anyone know how to restore from that first restore or how to make future restores work?
undegaard said:
Hello, I need some help with restoring via CWM on the Galaxy S3.
On the S2 I pretty much always used CM9 and jumped back and forth between versions and backing up/ restoring was never an issue.
Now however I am using the stock ROM and its rooted of course.
I made a back up of my stock rom 'cause I wanted to try and install some stuff.
I tried installing the jelly bean transition effects but the install failed, the device felt kinda sluggish (maybe my imagination) afterwards so I decided to restore my phone. The restoring went good but the last ting that happens is that CWM says that restoring /Data failed.
I reboot my phone and I come to the first start up screen where I get to choose language and so on. Everything but photos has been deleted. I try to install CM9, and I do that without any issues. Then I trie to backup my stock backup but I get the same error message and I get back to stock setup page.
My backup is a staggering 6GB, and I read somewhere that CWM can only restore 2GB?
I've deleted that backup and done another one but that is also 6GB.
Does anyone know how to restore from that first restore or how to make future restores work?
Click to expand...
Click to collapse
I had this problem with my sisters Xperia X8,couldn't restore anything that i backed up.It goes for a while and stops.But she had bootloader locked.I was shore that i unlocked her bootloader but i didn't,so i unlocked bootloader,and tried to backup and restore and it worked fine.
I'm not 100% and i don't know is that the way CWM works,but i think in order to restore your data,that you backed up,you have to unlock your bootloader.But it's the best to wait someone who knows this for 100% sure.
If you haven't unlocked bootloader try that,or you don't won't to lose your warranty!?
Good luck!
I don't think that CWM has size limitation but i can be wrong.
Have you made sure that your CWM is up-to-date? if in doubt flash the latest CF-root.
was there ever a resolution to this problem? I did the same thing, rooted the galaxy s 3 and unlock the bootloader. Get a backup of my stock set up using clockwork recovery mod. Now when I try to restore, it does not restore the data. All of my apps look like they are there, but none of them are really installed. I think I can just reinstall all of the apps by hand, I would like to know how to get over this.
Searched, but found nothing specifically related to this. I was on CM10 and flashed back to stock until they get the bugs worked out. Flashed back to stock via Odin with Samsung toolkit v. 2.1. I had backups for TB so I decided to restore missing apps with data and system data, however whenever I did, the device would get stuck at the samsung logo. I suppose this is due to conflicting system files, so the device doesnt know what to boot from, but how can i avoid this in the future? I thought TB was the ultimate answer when switching roms to transfer data, this is the first time I've had trouble with boot issues with TB.
emoandy said:
Searched, but found nothing specifically related to this. I was on CM10 and flashed back to stock until they get the bugs worked out. Flashed back to stock via Odin with Samsung toolkit v. 2.1. I had backups for TB so I decided to restore missing apps with data and system data, however whenever I did, the device would get stuck at the samsung logo. I suppose this is due to conflicting system files, so the device doesnt know what to boot from, but how can i avoid this in the future? I thought TB was the ultimate answer when switching roms to transfer data, this is the first time I've had trouble with boot issues with TB.
Click to expand...
Click to collapse
You're getting boot loops from restoring system data, thats a big no, no. Missing apps and data, I usually dont have any problems with that. The only "ultimate" is do a nandroid backup in CWM
True, but nandroid replaces system so it wouldn't be best when switching roms, correct?
Ok, first of I was wondering what odin and the jb bootloaders do?
Im running baked blackbean 6 jb4.12 with the new devil kernel...followed instructions to a t, odined to stock eho3 pit, gb bootloaders, worked for a bit perfectly n got stuck in a bootloop from hell, although I think my bit animation may have caused it. So back to Odin, stock, ect, but didn't do the gb bootloaders, n all works fine, seems a bit slower and the splash screen from the kernel no longer shows up, and room control will no longer boot into recovery
Can I odin the bootloaders after the rom is already installed or do I need to start from scratch? If I do start from scratch will a nandroid still work with the new bootloaders installed?
Onto titanium backup, I have all user only apps backed up and created an update.zip file with them..No system data at all...if I have the update zip can I delete all the backups n just use that? Save memory on the sd I'm assuming you just flash it as an update in recovery as opposed to a reg zip? Then all my apps should be back?...
I'm really out of date with the fassy last thing I had was skunkworks aokp m6...and I never flashed any bootloaders, just started from stock, and this update zip thing is new to me...just trying to get it all stable for my son...I've also noticed when I go to the homescreen it takes a while to show anything n I have it kept in memory, don't think bootloaders would affect that though correct?
One last thing...if I keep the stock kernel I get an md5 error when I try to do a backup...but once I switch it to devil it's fine...anyone else have this? That was with and without bootloaders...but all in all the gb bootloaders are the main thing I want to find out about being I've never used them before....
Thanks!
Sent from my blackened liquid galaxy
I've actually always flashed the GB bootloaders separately with Odin after the ROM/Kernel was installed (twice in total) and never had a problem.
I tried the update.zip with TiBu once and it didn't work... never tried it again. I'm just sticking to the regular method.
Bootloaders have no effect after you boot so no, that wouldn't cause your home screen issue.
Not sure about the md5 thing as I don't do nandroids.
Hope this helped
The update.zip that you create is just titanium backup, not your apps. When you flash it, it allows you to run tibu and install your apps without signing into google. You'll still need the folder with all your app backups.
Is this possible? The full details are I had my phone stolen, and got a new one with android 4.0.4 on it. I have on my computer a copy of my latest backup of my old cognition gingerbread rom. Can I just use CWM to recover to my old rom, or do i need to first downgrade to a gingerbread rom, and then recover?
Thankyou very much for assistance
Edit: Also, I don't actually want to use the old rom, I just need the contacts it saved, afterwards I'll wipe everything and install a clean ICS mod. In case there's any way of doing this without having to revert
You'll probably need to restore the backup with a version of CWM close to the one the backup was made with, you can often have problems restoring if you're using a CWM version a lot (say 12 mths or more) newer than the one you made the backup with.
So I'd probably go GB/with a rooted GB kernel first, restore the backup & go from there. I mean, it could work first try with an ICS kernel that's running a recent CWM build, but there's a fair chance it won't.
Edit - And be really careful with stock 4.0.4, don't do a wipe while you're running that.
Wow. I just... wow.
Ok, so I did the stupid thing and just tried to restore my old backup without doing proper downgrading first and it ended up soft bricking my machine, couldn't get recovery mode up, but I got into download mode. So I downloaded my country's stock gingerbread rom from samsung's site and flashed it with odin just to see what happens, and somehow my old rom was working again, and I have all my contacts and data. saved everything up to google, upgraded to ICS, import.
Everything went better than expected.
Thanks for the help
Told you Important thing is you managed to fix it yourself without asking silly questions in Q&A. Not many people seem to be able to do that these days.
Well done. I'm glad you got it sorted
Edit -You're welcome