I tried a new rom out this morning (miui 1.12.30 {2.3.7} {1-1-2012}), liked the interface of the rom, but the phone started to heat up immediately. I need to do some more research of why this happened. So I decided to go back to Unammed via a nandroid backup. When restoring i get this error
.android_secure.img not found. Skipping restore of /sdcard/.android_secure.
Click to expand...
Click to collapse
Any help would be appreciated.
gadget069 said:
I tried a new rom out this morning (miui 1.12.30 {2.3.7} {1-1-2012}), liked the interface of the rom, but the phone started to heat up immediately. I need to do some more research of why this happened. So I decided to go back to Unammed via a nandroid backup. When restoring i get this error
Any help would be appreciated.
Click to expand...
Click to collapse
Are you sure you wiped data and cache. Also dalvic. I always flash miui twice also. That happened to me once before and I re flagged and all is well. The reason it is overheating is cause it stays at Max frequency ( CPU). Anyways check out the Miui thread in development if you want to try it again.
As far as your restore error, I don't know.
One time at football camp, I put my shoulder pads in my arse.
I may try miui again in the future, just want to get back where i was before. Thanks.
gadget069 said:
I tried a new rom out this morning (miui 1.12.30 {2.3.7} {1-1-2012}), liked the interface of the rom, but the phone started to heat up immediately. I need to do some more research of why this happened. So I decided to go back to Unammed via a nandroid backup. When restoring i get this error
Any help would be appreciated.
Click to expand...
Click to collapse
I assume you have UnNamed back and all is working normally?
That message most likely means the restore was looking for something that was not present in the backup because it was not there to back up in the first place.
creepyncrawly said:
I assume you have UnNamed back and all is working normally?
That message most likely means the restore was looking for something that was not present in the backup because it was not there to back up in the first place.
Click to expand...
Click to collapse
Yes, everything seems to be running fine, I'm wondering if miui installed something that a nandroid wont write over. I also noticed in cwm i can use the power button to select the option i choose, actually i can use both the home and power button now. So something has changed in cwm i believe.
gadget069 said:
Yes, everything seems to be running fine, I'm wondering if miui installed something that a nandroid wont write over. I also noticed in cwm i can use the power button to select the option i choose, actually i can use both the home and power button now. So something has changed in cwm i believe.
Click to expand...
Click to collapse
sdcard/.android_secure is the hidden folder where apps2sd puts apps. It might be specific to cyanogen mod and miui, but not sure.
It happened when you first made your nandroid backup via cwm. The other day when I did a backup I watched it and saw the error skipping sdcard cause of no . android_secure . It has to do with cwm not being able to do a restore backup to our external sd. If you go in your external sdcard dir you will see the android secure file. So if next time you want your apps just move the file over for the backup and restore
Sent from my SAMSUNG-SGH-I777
Related
This is my first time flashing a new ROM. I decided to go with the stock Froyo ROM. And that went pretty smoothly.
I did the Titantium Backup to restore some of the apps I wanted back. However some settings didn't seem to come over, even though I selected to backup app and system settings. Examples included my phone contacts and my WinAmp playlists (songs are still there).
Anyway, that isn't so much the reason for this topic though. I did a Nandroid backup before and decided to do a restore of that backup. I initiated it from the Rom Manager and got into the Clockwork Recovery and saw it restoring. All appeared fine.
But when the phone rebooted, it is now stuck at the "Vibrant" screen. Has been stuck there for 15-20 minutes now.
I've been looking around. Is the problem because I went from 2.2 back to a 2.1 backup?
Hahaha I had that problem a few days ago, just flash back to stock with odin. Best to try a different rom....
Sent from my SGH-T959 using XDA App
Starting to think the phone might be bricked. Can't get into recovery mode or download mode. Always immediately comes back to the Vibrant screen. Pulled the battery. Didn't help.
Did you try holding down the volume buttons while putting the battery back in? Had a bit of a brick yesterday and that put it straight into download mode without even showing the vibrant logo.
DPCerberusBlaze said:
Did you try holding down the volume buttons while putting the battery back in? Had a bit of a brick yesterday and that put it straight into download mode without even showing the vibrant logo.
Click to expand...
Click to collapse
Thank you! That did the trick. I put the stock Froyo back on via Odin now and am back up again. Whew, Christmas is saved! Thanks.
Try Eugene Ginger Clone is pretty face...I'm currently running Team Whiskey Nero Beta 3...noticed a couple bugs nothing major
Sent from my SGH-T959 using XDA App
Ravynmagi said:
This is my first time flashing a new ROM. I decided to go with the stock Froyo ROM. And that went pretty smoothly.
I did the Titantium Backup to restore some of the apps I wanted back. However some settings didn't seem to come over, even though I selected to backup app and system settings. Examples included my phone contacts and my WinAmp playlists (songs are still there).
Anyway, that isn't so much the reason for this topic though. I did a Nandroid backup before and decided to do a restore of that backup. I initiated it from the Rom Manager and got into the Clockwork Recovery and saw it restoring. All appeared fine.
But when the phone rebooted, it is now stuck at the "Vibrant" screen. Has been stuck there for 15-20 minutes now.
I've been looking around. Is the problem because I went from 2.2 back to a 2.1 backup?
Click to expand...
Click to collapse
You were trying to load a 2.1 nandroid restore onto a 2.2 kernal. Nandroid does not restore the kernal so you would have to install one separate from the nandoid if you want to try it again.
in order to restore your nandroid backup you would have to first flash a 2.1 ROM, preferably the one you are restoring from, whenever I am changing versions, 2.2 to 2.1, I always Odin back to JFD and build up from there.
Kernel flashing questions
I have flashed numerous roms but have never flashed just the kernel. Do you flash it just like you would any zip file? Can I use CWM to flash using the flash rom from sd card method? If I decide to not use the kernel I just flashed can I just flash the rom over it(assuming it has its own kernel)? Sorry for all of the questions I have researched it and still do not have a clear enough understanding to try to flash a kernel at this point in time. Any and all help is absolutely appreciated.
tenbeau said:
I have flashed numerous roms but have never flashed just the kernel. Do you flash it just like you would any zip file? Can I use CWM to flash using the flash rom from sd card method? If I decide to not use the kernel I just flashed can I just flash the rom over it(assuming it has its own kernel)? Sorry for all of the questions I have researched it and still do not have a clear enough understanding to try to flash a kernel at this point in time. Any and all help is absolutely appreciated.
Click to expand...
Click to collapse
Thanks button right next to the quote >.<
I'm used to the quote being on the left.
Anyway, you can flash just the kernel. Check the Development section. There are some out there (Eugene has a bunch as do others). Depending on how they packaged the kernel, you would either flash with CWM or through Odin. The different ROMs typically come with the kernel, so you could just flash a 2.1 ROM and then nandroid back to what you had, or flash just the kernel, then nandroid.
Decided I better ask for help before digging a deeper hole...
I had rooted my Vibrant around September 2010 and tried some ROM at the time, don't remember which one. I didn't keep it for very long...I accepted one or two stock OTA updates thereafter, ending up with 2.1-update1/KA6.
Fast forward to yesterday, when I decided to try to go to Gingerbread so as to be able to install an app I wanted. I chose CM7.2. I presumed I wasn't rooted anymore after the OTA's, so used CWM to run the update.zip that I still had on the SD card from 2010. I did a Titanium backup. I started following the abbreviated directions, then went to the full directions here:http://wiki.cyanogenmod.com/wiki/Samsung_Vibrant:_Full_Update_Guide
So I actually made two nandroid backups as a result of switching between the two sets of directions and getting distracted after I made the first one.
All went well, except after CM7.2 was booted and everything restored from Titanium, I had the following issues:
1. Messaging was broken
2. Most contacts were missing
3. GPS wouldn't lock
I poked around for fixes and tried some, but it was not looking promising. I decided I didn't really need that new app after all, and today tried to revert to stock. I supposed it would be a simple matter of a nandroid restore followed by a Titanium restore. Unfortunately the nandroid restore failed.
Research revealed this is a known issue with "different hboots".
I then compounded the issue by accidentally pressing the power button while in Recovery. The phone rebooted but stuck on the "Vibrant" splash screen, because of the corrupted restore attempt. No amount of 3-button resets got me back to Recovery. The phone is now connected to my laptop in Download mode.
I think what I now need to do is odin, per http://forum.xda-developers.com/showthread.php?p=13132341#post13132341
I will then be able to do a nandroid restore and Titanium restore and be back where I started? Any additional hints, warnings, etc?
Thanks in advance.
Be careful about what you backup with Titanium on stock and then restore on CM. Did you backup your Messaging app or any system data? If you restored system apps or data from a TI backup onto CM from stock, that could cause issues.
And about the contacts, where did you store them before? On Google, SIM, or in memory?
I may have clicked, in Titanium, "restore app and data" rather than just "data" for the messaging app. Thinking that may have been the case, I thought that reinstalling the ROM or Google apps zip files might fix it. It didn't. (this was before I soft-bricked)
Since I needed a working phone this afternoon, I went ahead and did the Odin thing. That went well. I am back to JFD and my contacts are back.
If I do a nandroid restore now, followed by a Titanium restore, it should get me back to where I was before starting the move to CM7.2, right? Except I would still have a JFD radio? (because nandroid does not touch that, as I recall)
In that case, finding a KA6 to install with odin would be best? And would there be any point to the nandroid restore if I did that?
GPS took a very long time to lock after going back to JFD, too. I think perhaps I need to try the antenna fix.
Maybe I will give CM7.2 another go...
m3rb said:
I may have clicked, in Titanium, "restore app and data" rather than just "data" for the messaging app. Thinking that may have been the case, I thought that reinstalling the ROM or Google apps zip files might fix it. It didn't. (this was before I soft-bricked)
Since I needed a working phone this afternoon, I went ahead and did the Odin thing. That went well. I am back to JFD and my contacts are back.
If I do a nandroid restore now, followed by a Titanium restore, it should get me back to where I was before starting the move to CM7.2, right? Except I would still have a JFD radio? (because nandroid does not touch that, as I recall)
In that case, finding a KA6 to install with odin would be best? And would there be any point to the nandroid restore if I did that?
GPS took a very long time to lock after going back to JFD, too. I think perhaps I need to try the antenna fix.
Maybe I will give CM7.2 another go...
Click to expand...
Click to collapse
If you do a nandroid restore you don't need to do a TI restore as nandroid will restore all your apps and data. (Even down to which wallpaper you're using and Wifi networks)
If the KA6 modem works best for you then go for it.
Where you rooted before you flashed the CWM update.zip? I didn't see that you were...
Sent from my SGH-T959 using xda app-developers app
whatiznt said:
Where you rooted before you flashed the CWM update.zip? I didn't see that you were...
Sent from my SGH-T959 using xda app-developers app
Click to expand...
Click to collapse
You don't need to be rooted, you just need a way to install. For example when you install from stock, you don't need to root it, only flash the custom kernel that has CWM, and then flash, since root is a state of the ROM.
Sent from my SGH-T959 using xda premium
Huh. Always thought you needed root to flash CWM.
Sent from my SGH-T959 using xda app-developers app
whatiznt said:
Huh. Always thought you needed root to flash CWM.
Sent from my SGH-T959 using xda app-developers app
Click to expand...
Click to collapse
Well, in our case we can use download mode + heimdall to flash a kernel that has the CWM recovery included.
Sent from my SGH-T959 using xda premium
Good evening XDA -people.
I do not really want to bother anyone, but I'm sure I do.
SO. I'm quite stressed about this as it happens all the time.
I got the PredatorUnity Rom (1.1 I guess, but it already happened before)
And if I try to do a nandroid backup it says it does work, sometimes it does NOT work though. so, I restart after that backup (or just a normal reboot, any kind of reboot causes this, even if I just go into recovery and don't change anything) the rom starts and boots alright for a few seconds and then does a hot restart.
So once this made me SO angry, I changed rom. then it actually went alright until I restored my apps via Titanium. then the same thing happened. Don't worry, I'm not that dumb anymore to backup my system apps. Anyway I located the apps that caused my bootloops. Chrome, Busybox etc. I THOUGHT SO. It looks like theres more.
The problem now is, everything worked well for a few days. EVEN 1 REBOOT WORKED! so now, I went into recovery to do a nand backup via rom manager and then just this..
so sorry. wi'll give thanks to any useful comment
oh yea. just for you to know if you need it;
S-Off
HBOOT-1.49.1107
Radio: 0-11.23.3504.09_M2
GSM
yes.
Don't hate. I've looked around and haven't found any case like this..
Comments Withdrawn
zcink said:
It almost sounds like you've got a bad recovery. I would reflash it.
which recovery are you using? The latest 4ext seems to work best. Lots of roms here support it.
If you get everything working again, I would redo all your backups also.
Click to expand...
Click to collapse
Thanks man
I am using the latest 4ext touch.. and I flashed it only about a week ago! I've had these problems before- and after the recovery change. should I reflash it anyway?
Comments Withdrawn
zcink said:
It wouldn't hurt anything to reflash it but if you've had these problems before and after then its probably not your problem.
Have you tried other roms? And still get these problems?
One guy had a thread where he was getting bootloops and turned out to be a physical problem where his battery was loose:
http://forum.xda-developers.com/showthread.php?t=1705261
Click to expand...
Click to collapse
Okay I won't take it as an option then. At least not for now..
I did, but as I said it broke after I restored my apps via titanium..
Yeah, I've seen that thread and I can be sure it isn't this as it doesn't reboot randomly. only afer a reboot. Like, you wanna break your phone? reboot it! haha
I really love Sense 4 and the predators' rom is really awesome, but I'd even try a AOSP rom. Onbly problem is, I don't think I could restore sms (I saved them via the stock sense sms)
Oh and if this could be a problem; today I downloaded BootManager lite and saved my boot.img? didn't do anything but might have been a problem for the backup?? Ah I dunno...
Comments Withdrawn
zcink said:
Guess I'm out of ideas also.
Wondering about Titanium backup pro though. It updated when I went on the market the other day. I bought the pro version awhile back. Now after the update when I go in and try to remove something from a rom, it tells me it can't.
I used to make user app and then delete or uninstall. Won't do it anymore with Titanium Backup. However, Rom Toolbox pro will.
Click to expand...
Click to collapse
aw man.. Thansk anyway
I don't know exactly what you mean, because all I ever did was backup and restore
I do have Pro, but just because of Lucky Patcher haha
So Rom Toolbox Pro is better? (got that too, not using it tho)
Alright. it seems like all I can do right now is; flash the latest radio, do a super wipe, (now comes the worst) restore an old nand. sense backup, restore my sms, download another sms backup program, use it, do a super wipe, etc etc etc. and install the aosp rom (sense 3.6 feels ugly after sense 4..) or whatever else I find and restore the sms that way and then live like never before.
OR I try to install the latest predator, which has a new base.
I'll do the last thing haha
Use twrp everyone says 4ext is great but get twrp
Hit the thanks button if i helped
Hello, I have a major problem with something that should have been a minor project. I used System Recovery to do a backup of the phone. The only thing I can think of there that I might have done differently is save the backup to the external SD card, instead of internal. After the backup completed, I went to reboot the phone and it's stuck on the Motorola splash screen. I tried to pull the battery and go into that general Android Recovery in order to wipe data and try again, but I just get the Android with an exclamation point over his head. I've tried booting it without the SD card too. I was using CM7
Can anyone help please!
EDIT: A couple hours later, since it was my work phone, I had to do something. I reverted the SBF, re-rooted and tried to restore from the backup I made and the same thing happened. I'm going to try to revert to my previous backup. I have a full backup from Titanium Backup if it comes down to it. The phone was working fine, I just can't figure out why it blew up on me after I ran the backup. Grr..
iceolate said:
Hello, I have a major problem with something that should have been a minor project. I used System Recovery to do a backup of the phone. The only thing I can think of there that I might have done differently is save the backup to the external SD card, instead of internal. After the backup completed, I went to reboot the phone and it's stuck on the Motorola splash screen. I tried to pull the battery and go into that general Android Recovery in order to wipe data and try again, but I just get the Android with an exclamation point over his head. I've tried booting it without the SD card too. I was using CM7
Can anyone help please!
EDIT: A couple hours later, since it was my work phone, I had to do something. I reverted the SBF, re-rooted and tried to restore from the backup I made and the same thing happened. I'm going to try to revert to my previous backup. I have a full backup from Titanium Backup if it comes down to it. The phone was working fine, I just can't figure out why it blew up on me after I ran the backup. Grr..
Click to expand...
Click to collapse
sounds like a bad backup. i always use external sd for nandroids and it has never had issues.i would just re-flash. as for stock recovery with andy with an exclamation , push both volume keys. should work regardless of what state the phone is in. i have had it completely unusable and it still worked.
Lorenzo VonMatterhorn said:
sounds like a bad backup. i always use external sd for nandroids and it has never had issues.i would just re-flash. as for stock recovery with andy with an exclamation , push both volume keys. should work regardless of what state the phone is in. i have had it completely unusable and it still worked.
Click to expand...
Click to collapse
OK - You mean to flash cleanly with CM7 and then restore from Titanium backup instead of my previous nandroid backup?
I'm slightly confused about that System Recovery tool, because first I had ROM Manager and it says that CWM is installed, but it doesn't work. Do I have to manually install that System Recovery APK each time I do stuff like this, or does it stay installed? And if so, from a powered off state, how do you enter it? Or do you have to boot up to Android and enter recovery mode from the app? Thanks.
iceolate said:
OK - You mean to flash cleanly with CM7 and then restore from Titanium backup instead of my previous nandroid backup?
I'm slightly confused about that System Recovery tool, because first I had ROM Manager and it says that CWM is installed, but it doesn't work. Do I have to manually install that System Recovery APK each time I do stuff like this, or does it stay installed? And if so, from a powered off state, how do you enter it? Or do you have to boot up to Android and enter recovery mode from the app? Thanks.
Click to expand...
Click to collapse
yes i would try that. second, dont use rom manager. dont delete it either. but it doesnt work on our phone. the bootstrap recovery that you install would only need to be reinstalled if you delete cache in recovery. otherwise it should always work. hope this helps. im not completely sure exactly what you are asking.
try just restoring system part of backup, see if phone will boot, then restore user data
or reinstall cm7 and restore just user data
Sent from my XT862 using xda premium
sd_shadow said:
try just restoring system part of backup, see if phone will boot, then restore user data
or reinstall cm7 and restore just user data
Sent from my XT862 using xda premium
Click to expand...
Click to collapse
I should be fine now, thanks for the advice. I don't know why that backup blew up the phone, but it was sure an inconvenience haha! I just reflashed CM completely, and now I'm gonna roll out my Titanium backup. I don't have a lot of stuff, just the essential stuff for work, so it shouldn't take too long.
this question was originally posted as my phone stuck in bootloop by itself
I've been using Slim Bean very neatly for the past 3 months until today
I charged my phone and I saw only battery icon (you know like when you charge it from no battery)
I unplugged and there is a red ! on top left corner in the GT-i9300t boot screen.
I was able to get to TWRP recovery, fortunately.
ok now I get it to boot what I did I restored to my NEATROM that I have backed up long time ago and before that I failed to restore to Slim Bean also.
I was happy it worked but
I'm now so confused as my newly RESTORED Neat rom looks like a new flash, with Samsung welcome screen and gmail login and all.
I have been restoring ROMS for some time now I know this ain't right, it should look like the state when I BACKED IT UP.
Is something wrong with my phone????
You must have backed up and restored a stock type rom .
Phone cannot change to stock by itself .
jje
I'm pretty sure it's not stock because I have been restoring it before and all the apps are there
now there's nothing
pinmemo said:
I'm pretty sure it's not stock because I have been restoring it before and all the apps are there
now there's nothing
Click to expand...
Click to collapse
Sounds like it failed to restore data
slaphead20 said:
Sounds like it failed to restore data
Click to expand...
Click to collapse
perhaps
This is getting even weirder, I cannot install Slim Bean or any AOSP ROM, only able to restore Samsung ROM with the same result...
grr
pinmemo said:
perhaps
This is getting even weirder, I cannot install Slim Bean or any AOSP ROM, only able to restore Samsung ROM with the same result...
grr
Click to expand...
Click to collapse
Time for a completely clean install,full wipe, Odin flash of stock firmware I reckon and start from scratch, easiest solution imho
slaphead20 said:
Time for a completely clean install,full wipe, Odin flash of stock firmware I reckon and start from scratch, easiest solution imho
Click to expand...
Click to collapse
your 'start from scratch' solution work thanks a lot! although different method
first I tried internal wipe, nothing changes
then here comes FORMAT DATA bam that fixed it :good:
unfortunately I didn't fulfill my curiosity as to what just happened
and I thought NANDROID back up is the best way to prevent any disaster ROM wise
it may not be made to withstand partition problem which is what I think happened.
The problem, to my recent realization actually happened after I recorded a very long video (20mins)...
Backup could have corrupt if in internal sd.
Sent from my GT-I9300 using Tapatalk 4 Beta
rootSU said:
Backup could have corrupt if in internal sd.
Sent from my GT-I9300 using Tapatalk 4 Beta
Click to expand...
Click to collapse
but it's in my external card. Copied over from my computer even.
Moving / copying files can also be a catalyst for corruption.
I've had the same issue with a backup from computer before.
My reference to internal sd was if your partitions are messed up, its likely your backup was corrupt.
It could even be the backup just didn't take properly. If you have md5 checking turned on then that is more likely.
Anyway, it can happen from time to time
Sent from my GT-I9300 using Tapatalk 4 Beta
ok next time I'll make sure MD5 was checked.