Related
I created a backup using CWM 3.1.0.1 (from rooted EC05). I then flashed one of the new roms, and today wanted to go back, so i booted into 3.1.0.1 and did the restore (from cw). Now the phone boots up to the Samsung screen and sits there. What am I doing wrong? Sorry if this has already been asked, I did a search but couldn't find this particular issue. Thanks for any and all help.
both backups were made using 3.1.0.1? and were both made in 3finger recovery? and when you restored you were in 3 finger recovery, not reboot recovery?
chris41g said:
both backups were made using 3.1.0.1? and were both made in 3finger recovery? and when you restored you were in 3 finger recovery, not reboot recovery?
Click to expand...
Click to collapse
I only did 1 backup, not sure what you mean by 3 finger recovery? I booted in CWM (purple) and did the back-up. I then put on the "Bamboozle" rom (and yes, I wiped everything 3x like qb shows in the vid) then installed the rom. I ran it for the past week (loved the rom, but it was eating my battery really bad) so wanted to try a different rom. I thought the easiest way to start was to restore the backup I made, so I booted back into cwm and selected Backup/Restore, Restore, Yes and it ran and said it restored fine. I reboot, but all I get to now is the Samsung screen, no further.
libracolo said:
I only did 1 backup, not sure what you mean by 3 finger recovery? I booted in CWM (purple) and did the back-up. I then put on the "Bamboozle" rom (and yes, I wiped everything 3x like qb shows in the vid) then installed the rom. I ran it for the past week (loved the rom, but it was eating my battery really bad) so wanted to try a different rom. I thought the easiest way to start was to restore the backup I made, so I booted back into cwm and selected Backup/Restore, Restore, Yes and it ran and said it restored fine. I reboot, but all I get to now is the Samsung screen, no further.
Click to expand...
Click to collapse
Let me just say, I think I f'ked my phone up. So I gave up trying to restore, just odin'd back to stock (ec 05). Which I then re-rooted and re-installed CWM 3.1.0.1 (I have titanium backups as well). However, now the phone runs really, really slow and when I try to restore apps from titanium it just sits there (in batch mode). Sorry, for being a noob; hey, if nothing else, maybe I'm making someone smile at my dumb a$$. But now, if I can be even more stupid, is there a way to just "reset" the phone, by that I mean put it back to a "true stock" form so I can start over? And then, can I just delete these backups, and roms from the sd card (just hookup to laptop and delete from the sd-card)? I think maybe it'd be easier to just start from scratch again...thanks for the help, I try to keep up with the forums, but so many posts....
What he means by 3 finger is the ONLY way to get into recovery for proper operation. With power off press and hold camera, volume down, and power. Holding all 3 until you see the recovery menu. If you use any other method such as ROM Manager or Quick Boot you will more than likely screw up your phone. Neither application is recommended for recovery operations.
Sent from my SPH-D700 using XDA App
I believe clockwork does not backup the kernel. You may need to install a kernel.
Just a thought...
libracolo said:
I created a backup using CWM 3.1.0.1 (from rooted EC05). I then flashed one of the new roms, and today wanted to go back, so i booted into 3.1.0.1 and did the restore (from cw). Now the phone boots up to the Samsung screen and sits there. What am I doing wrong? Sorry if this has already been asked, I did a search but couldn't find this particular issue. Thanks for any and all help.
Click to expand...
Click to collapse
If you backed up on ec05 and installed a gingerbread rom you need to odin back to ec05 and then do the restore. It won't work if you are on different os versions. At least it never has for me.
Sent from my SPH-D700 using XDA Premium App
crawrj said:
If you backed up on ec05 and installed a gingerbread rom you need to odin back to ec05 and then do the restore. It won't work if you are on different os versions. At least it never has for me.
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
Thanks, that must have been it. I was on Bamboozle, which is based on Gingerbread.
libracolo said:
Thanks, that must have been it. I was on Bamboozle, which is based on Gingerbread.
Click to expand...
Click to collapse
Wait, did you wipe data/system,cache, and Dalvik Cache then restore your nandroid? I have a SRF 1.2, an Urban Regeneration, and a CM7 nandroid. As long as I wipe everything then restore I have no problems. I have bounced between all three today with no issues
Sent from my SPH-D700 using XDA Premium App
JohnCorleone said:
Wait, did you wipe data/system,cache, and Dalvik Cache then restore your nandroid? I have a SRF 1.2, an Urban Regeneration, and a CM7 nandroid. As long as I wipe everything then restore I have no problems. I have bounced between all three today with no issues
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
Yeah, the issue was I was running bamboozle (GB leaked rom), so once I odin'd back to EC05, I was able to run the restore without problem. I am now running SRF 1.2 (awesome rom btw) and I was able to restore when trying to install that rom (and the genocide kernel). Thanks for all the helpful answers.
crawrj said:
If you backed up on ec05 and installed a gingerbread rom you need to odin back to ec05 and then do the restore. It won't work if you are on different os versions. At least it never has for me.
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
I would have thought the same thing. However, I simply restored my SFR 1.2 nandroid right over the gingerbread rom. With a few glitches smoothed out I am running fine again with no Odin involved.
Sent from a secret underground bunker
mjben said:
I would have thought the same thing. However, I simply restored my SFR 1.2 nandroid right over the gingerbread rom. With a few glitches smoothed out I am running fine again with no Odin involved.
Sent from a secret underground bunker
Click to expand...
Click to collapse
Yeah, I have gotten the dreaded Google Services Framework FC's a couple of times but for the most part I can wipe everything and restore a Froyo setup even when on a Gingerbread ROM. The purp recovery is good like that.
Sent from my SPH-D700 using XDA Premium App
JohnCorleone said:
Yeah, I have gotten the dreaded Google Services Framework FC's a couple of times but for the most part I can wipe everything and restore a Froyo setup even when on a Gingerbread ROM. The purp recovery is good like that.
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
Thanks for the info. I will have to remember that and try it out in the future.
crawrj said:
Thanks for the info. I will have to remember that and try it out in the future.
Click to expand...
Click to collapse
Hey, no problem crawrj. It definately comes in handy with all of the testing I do for sure.
Sent from my SPH-D700 using XDA Premium App
When restoring across different OS versions it is handy to do a Restore>Advanced Restore Data from the Nand backup. There may be the occasional FC if the data format has changed but that usually can be fixed by clearing data of the offending app, especially for Google sevice framework.
kennyglass123 said:
When restoring across different OS versions it is handy to do a Restore>Advanced Restore Data from the Nand backup. There may be the occasional FC if the data format has changed but that usually can be fixed by clearing data of the offending app, especially for Google sevice framework.
Click to expand...
Click to collapse
Kenny - I did try that as well. I tried everything, I did the "Restore" option like 4 separate times, I wiped data, cache, dalvik cache 3 x, even did the Advanced option and went down the list. None of that helped. Now it may be that I just didn't wait long enough, but I figured 4-6 minutes of the "Samsung" screen meant it had stopped responding (I see that all that time in MS apps). I finally odin'd back to stock ec05, re-rooted (and updated back to cwm 3.1.0.1), then I ran the restore (not advanced), and it worked like a charm. Thanks for all the suggestions on this.
libracolo said:
Kenny - I did try that as well. I tried everything, I did the "Restore" option like 4 separate times, I wiped data, cache, dalvik cache 3 x, even did the Advanced option and went down the list. None of that helped. Now it may be that I just didn't wait long enough, but I figured 4-6 minutes of the "Samsung" screen meant it had stopped responding (I see that all that time in MS apps). I finally odin'd back to stock ec05, re-rooted (and updated back to cwm 3.1.0.1), then I ran the restore (not advanced), and it worked like a charm. Thanks for all the suggestions on this.
Click to expand...
Click to collapse
Sometimes our phones can be so finicky. Glad you got it working. Usually when Dalvik is rebuilding it takes awhile at the S screen, so you are correct that 4-6 minutes at Samsung is a cry for help from your phone.
crawrj said:
If you backed up on ec05 and installed a gingerbread rom you need to odin back to ec05 and then do the restore. It won't work if you are on different os versions. At least it never has for me.
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
Not true. I always go from froyo to gingerbread with backups. What he Did wrong was not wipe when he tried to restore his back up that's why he got stuck on the Sammy screen. Also if he tried to restore a rfs froyo rom it could've gotten stuck there also since bammbozle was ext4.
Sent from my SPH-D700 using XDA Premium App
Esteway.619 said:
Not true. I always go from froyo to gingerbread with backups. What he Did wrong was not wipe when he tried to restore his back up that's why he got stuck on the Sammy screen. Also if he tried to restore a rfs froyo rom it could've gotten stuck there also since bammbozle was ext4.
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
You can restore from EXT4 to RFS with advanced restore data nand. He said he tried all of this and still got stuck. But I think you are correct and the first restore attempt borked everything. From there a reflash then advanced restore data should have worked.
kennyglass123 said:
You can restore from EXT4 to RFS with advanced restore data nand. He said he tried all of this and still got stuck. But I think you are correct and the first restore attempt borked everything. From there a reflash then advanced restore data should have worked.
Click to expand...
Click to collapse
So if I understand what you guys said, I should have wiped first (before the initial restore), which I didn't do. When the first restore didn't work, then I did the wipe x3, but it sounds like by that point it was already too late. So should you always wipe before restoring? I only ask, because once I got everything back to a good place I flashed the sfr 1.2. The first attempt caused the phone to boot up with that annoying "Android" screen, so I just booted into CWM and restored. That time I just restored (no wipes, no advanced) and it restored fine. I then re-flashed and all was good. So it seems like you don't always have to wipe x3 before restoring? Thanks btw, all good info for future ref.
Useing CWM wiping everything clean to install a rom. At this point back up useing CWM. Now if I just restored that backup before every rom would that be like wiping everything for it?
rom install
If you don't perform the wipe before installing a different rom, all you are doing is installing over top of, and you can run into problems that way. The exception would be that some of the developers start the installation by formatting.
Omnicide said:
Useing CWM wiping everything clean to install a rom. At this point back up useing CWM. Now if I just restored that backup before every rom would that be like wiping everything for it?
Click to expand...
Click to collapse
I get what your saying and its an interesting question..
RESTATED: WIPE EVERYTHING AND BACKUP THE WIPAGE....lol
So that if) t were restored, it would restore a blank...tricky to explain
Ok so imo, i dont think it works...i have zero base for my opinion. But even if it does work why? Wiping is faster than restoring anyway. Flashing TDJ's superwipe is even better and still faster than restoring.
Interesting question nonetheless
Sent from my SGH-T989 using XDA
Omnicide said:
Useing CWM wiping everything clean to install a rom. At this point back up useing CWM. Now if I just restored that backup before every rom would that be like wiping everything for it?
Click to expand...
Click to collapse
You want to backup before you wipe because if you backup afterwards you would be backing up either a blank ROM or by a small chance a wiped version of your current one.
Sent from my Galaxy Nexus using xda premium
Master&Slave™ said:
You want to backup before you wipe because if you backup afterwards you would be backing up either a blank ROM or by a small chance a wiped version of your current one.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Thanks yeah i learned why backup are so inportent so i have tons of backups all labeled.
Sent from my SGH-T989 using xda premium
Hi everyone. I used TWRP to make a backup of my CM10 nightly so I could flash a TW rom and be able to boot between the two by using the recoveries. Backed up CM10 no problem. Wiped/installed the TW rom (FreeGS3) successfully and it booted just fine. Used it for a little, then I restored my CM10 backup and it just shows the CM10 boot animation and nothing else is happening. I noticed that it made 2 data archives while backing up, but thought nothing of it. Upon further review, I discovered that I can boot with just the 1 data file restored but once I restore the 2nd data file, I get the endless boot animation. Is there anything I can do to solve this? I really need the data I have on here for school and it annoys me that it's sitting in a file that I can't restore!
I posted a question about this same type of issue yesterday here:
http://forum.xda-developers.com/showthread.php?p=31573026
...and nobody has seemed to give a crap. But I too have been having trouble restoring my CM10 nandroids. I dunno what the deal is. It's weird.
Also I posted the question in the CM10 nightly thread, and all I got was, "TWRP works fine for me. TWRP restores fine for me. Blah, blah, blah...
Although did read in other places, rootzwiki and around google that TWRP has been known to not restore CM10 nands well for some reason. Something having to do with it not restoring the kernel data well. And the only way around it is to reflash whatever kernel you were using. Kind of a drag. But I'm with you, my TW rooms have been restoring just fine, but the CM10s have been a mess.
Considering switching back to CWM.
Sent from my SPH-L710 using xda app-developers app
drewmonge said:
I posted a question about this same type of issue yesterday here:
http://forum.xda-developers.com/showthread.php?p=31573026
...and nobody has seemed to give a crap. But I too have been having trouble restoring my CM10 nandroids. I dunno what the deal is. It's weird.
Also I posted the question in the CM10 nightly thread, and all I got was, "TWRP works fine for me. TWRP restores fine for me. Blah, blah, blah...
Although did read in other places, rootzwiki and around google that TWRP has been known to not restore CM10 nands well for some reason. Something having to do with it not restoring the kernel data well. And the only way around it is to reflash whatever kernel you were using. Kind of a drag. But I'm with you, my TW rooms have been restoring just fine, but the CM10s have been a mess.
Considering switching back to CWM.
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
So am I basically screwed? I have my notes and stuff for school saved on there and I kinda need them, and about 40,000 text messages. :/ Did yours make 2 data archives?
iTzFeRReTTi said:
So am I basically screwed? I have my notes and stuff for school saved on there and I kinda need them, and about 40,000 text messages. :/ Did yours make 2 data archives?
Click to expand...
Click to collapse
Actually I only get one data archive. But someone somewhere did mention something about using the "extract from nandroid" option in Titanium Backup. I haven't tried it yet, but supposedly it works. I think there's other "extract from nandroid" app on the market if I'm not mistaken.
As of right now, I'm about to email the Team Win development team to ask them about the issue. Maybe they can tell me what's going on. Cuz it's only recently this started happening with the restoring of CM10 nandroids, at least for me.
Sent from my SPH-L710 using xda app-developers app
drewmonge said:
Actually I only get one data archive. But someone somewhere did mention something about using the "extract from nandroid" option in Titanium Backup. I haven't tried it yet, but supposedly it works. I think there's other "extract from nandroid" app on the market if I'm not mistaken.
As of right now, I'm about to email the Team Win development team to ask them about the issue. Maybe they can tell me what's going on. Cuz it's only recently this started happening with the restoring of CM10 nandroids, at least for me.
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
Yeah I've used TWRP to make CM10 backups and this is the first time that this has happened to me and of course it happens when I need it most! I flashed a TW rom so I could flash the corporate PRL (24006). I went to restore my backup and bam, no boot.
iTzFeRReTTi said:
Yeah I've used TWRP to make CM10 backups and this is the first time that this has happened to me and of course it happens when I need it most! I flashed a TW rom so I could flash the corporate PRL (24006). I went to restore my backup and bam, no boot.
Click to expand...
Click to collapse
Same thing happened with me. Did the whole Prl thing, and now they're not restoring well. Happened to me with trying to restore the last three CM10s I've ttied to restore. I dunno if the Prl change would have anything to do with it. Although I did get one to settle down after wiping cache and delvik twice, and fix permissions.
But gonna try it again tonight.
Also, I emailed team win and linked them back to here. Hopefully we'll hear back soon.
Sent from my SPH-L710 using xda app-developers app
drewmonge said:
Same thing happened with me. Did the whole Prl thing, and now they're not restoring well. Happened to me with trying to restore the last three CM10s I've ttied to restore. I dunno if the Prl change would have anything to do with it. Although I did get one to settle down after wiping cache and delvik twice, and fix permissions.
But gonna try it again tonight.
Also, I emailed team win and linked them back to here. Hopefully we'll hear back soon.
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
I tried changing the PRL back to what it was before the backup and it still doesn't boot unfortunately. :/ Luckily I backed up the TWRP backup to my computer so I don't have to worry about losing it. Does your boot animation just keep playing over and over again after it reboots?
iTzFeRReTTi said:
I tried changing the PRL back to what it was before the backup and it still doesn't boot unfortunately. :/ Luckily I backed up the TWRP backup to my computer so I don't have to worry about losing it. Does your boot animation just keep playing over and over again after it reboots?
Click to expand...
Click to collapse
Yeah it does. For the 3rd one I tried restoring, it at least booted into the rom, but once I started using it, it would force close after a couple minutes. And it would do that over and over. Until I wiped cache and delvik.
Was going to try doing a nandroid with the same prl and restoring. Cuz I've only experienced this problem when I've tried to restore a nandroid with the old prl.
Sent from my SPH-L710 using xda app-developers app
---------- Post added at 08:48 PM ---------- Previous post was at 08:34 PM ----------
Also, here's a link to Nandroid Browser. This should help you to get your stuff for school.
https://play.google.com/store/apps/details?id=de.goddchen.android.nandroidbrowser
Sent from my SPH-L710 using xda app-developers app
drewmonge said:
Yeah it does. For the 3rd one I tried restoring, it at least booted into the rom, but once I started using it, it would force close after a couple minutes. And it would do that over and over. Until I wiped cache and delvik.
Was going to try doing a nandroid with the same prl and restoring. Cuz I've only experienced this problem when I've tried to restore a nandroid with the old prl.
Sent from my SPH-L710 using xda app-developers app
---------- Post added at 08:48 PM ---------- Previous post was at 08:34 PM ----------
Also, here's a link to Nandroid Browser. This should help you to get your stuff for school.
https://play.google.com/store/apps/details?id=de.goddchen.android.nandroidbrowser
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
For the third what you tried restoring? And the nandroid browser doesn't see anything in my CM10 TWRP backup folder.
iTzFeRReTTi said:
For the third what you tried restoring? And the nandroid browser doesn't see anything in my CM10 TWRP backup folder.
Click to expand...
Click to collapse
For the 3rd nandroid, once it booted up, I immediately booted into recovery and wiped cache and delvik, and rebooted. I did that like three times before it settled down a bit. But ultimately it didn't fix it 100%. I still got FCs. Just not as frequent.
But I finally restored a couple "new" nandroids with the same prl, and I had no problems. I really think it had something to do with the two prls clashing.
Sent from my SPH-L710 using xda app-developers app
drewmonge said:
For the 3rd nandroid, once it booted up, I immediately booted into recovery and wiped cache and delvik, and rebooted. I did that like three times before it settled down a bit. But ultimately it didn't fix it 100%. I still got FCs. Just not as frequent.
But I finally restored a couple "new" nandroids with the same prl, and I had no problems. I really think it had something to do with the two prls clashing.
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
But I have gone back into my TW rom and updated the PRL back to what my CM10 backup has it and still won't boot. I have narrowed it down to just being the data archives not restoring properly because it will boot if I don't restore data at all, just that I have nothing on there for data. Is there a way I can restore without data, then restore the data while booted into CM10?
iTzFeRReTTi said:
But I have gone back into my TW rom and updated the PRL back to what my CM10 backup has it and still won't boot. I have narrowed it down to just being the data archives not restoring properly because it will boot if I don't restore data at all, just that I have nothing on there for data. Is there a way I can restore without data, then restore the data while booted into CM10?
Click to expand...
Click to collapse
To be honest, I'm stumped about your situation. Because I'm not sure why your old back up is not restoring for you, even tho you change prl back. Cuz my remedy was basically to delete all my old cm10 back ups and start fresh with some new nandroids. And they all seem to be restoring well now that haven't changed the prl. But I know you want to try and salvage your old data. At this point, I'd try and email Team Win and tell them about your situation. They may be able to give you some more tips.
PS . I'm still waiting for a response from the email I sent a couple says ago.
Sent from my SPH-L710 using xda app-developers app
drewmonge said:
To be honest, I'm stumped about your situation. Because I'm not sure why your old back up is not restoring for you, even tho you change prl back. Cuz my remedy was basically to delete all my old cm10 back ups and start fresh with some new nandroids. And they all seem to be restoring well now that haven't changed the prl. But I know you want to try and salvage your old data. At this point, I'd try and email Team Win and tell them about your situation. They may be able to give you some more tips.
PS . I'm still waiting for a response from the email I sent a couple says ago.
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
Basically it restores fine as long as I don't restore the data files, which are kinda important. :banghead:
Sent from my SPH-L710 using xda app-developers app
By the way, I just threw my CM10 backup on my SD card to see if it would work and it's currently restoring so I'll let you know if it works. I'm just trying anything at this point!
EDIT: It's restoring archive 2 right now! That never happened before. This should be good. So anxious!
OMG IT WORKED! I'M SO HAPPY! drewmonge, put the backup on your SD card and restore and it will work!
It's the kernal. I had the same problem but just from switching between TW and ASOP roms. Flash a new kernal made for whatever type (asop or tw) you're trying to install and it'll work. Mine happened on a s4 though, but I bet same base problem.
Something weird happens when I try a different ROM or updating the current ROM I'm on.
Everything changes to "unknown" imei, network, etc.
I restore a backup and everything is perfectly fine.
I have tried going back to stock and re-rooting the device, once I flash a ROM everything goes to "unknown".
What I've tried:
Returning to stock and re-rooting
Switched recoveries (tried both cwm and Twrp)
Made sure downloads weren't bad (both ROM and gapps)
Made sure recoveries were up to date
Full wipes when trying a different ROM
T-Mobile gs3 T-999 (yes, I'm sure)
Rooted
Twrp recovery
Running Ayysir's PA 3.99 RC1
Sent from my SGH-T999 using XDA Premium 4 mobile app
Da Kine said:
Something weird happens when I try a different ROM or updating the current ROM I'm on.
Everything changes to "unknown" imei, network, etc.
I restore a backup and everything is perfectly fine.
I have tried going back to stock and re-rooting the device, once I flash a ROM everything goes to "unknown".
What I've tried:
Returning to stock and re-rooting
Switched recoveries (tried both cwm and Twrp)
Made sure downloads weren't bad (both ROM and gapps)
Made sure recoveries were up to date
Full wipes when trying a different ROM
T-Mobile gs3 T-999 (yes, I'm sure)
Rooted
Twrp recovery
Running Ayysir's PA 3.99 RC1
Sent from my SGH-T999 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Almost certain it's a known issue with 4.3 and our device.
Aerowinder said:
Almost certain it's a known issue with 4.3 and our device.
Click to expand...
Click to collapse
So I guess its flash a ROM, cross your fingers and hope everything doesn't say "unknown"? That sucks lol.
Sent from my SGH-T999 using XDA Premium 4 mobile app
Aerowinder said:
Almost certain it's a known issue with 4.3 and our device.
Click to expand...
Click to collapse
I second this.
Some reported that after rebooting several times, everything returned to normal. It is very weird, but in this case the IMEI is not lost, it's just the O/S isn't reading it for whatever reason.
If rebooting doesn't eventually help, you could try using nvrestore. But just about everyone has said an Odin flash back to stock solved it.
Sent from my SCH-I535 using Tapatalk 4
DocHoliday77 said:
I second this.
Some reported that after rebooting several times, everything returned to normal. It is very weird, but in this case the IMEI is not lost, it's just the O/S isn't reading it for whatever reason.
If rebooting doesn't eventually help, you could try using nvrestore. But just about everyone has said an Odin flash back to stock solved it.
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
I'll have to try rebooting a few times the next time it happens.
Yes going back to stock does resolve the issue. I was going to Odin back to stock (once again), instead I tried restoring from a back and everything was back to normal.
I was just wondering if this common, I will definitely try rebooting a few times the next time. Thanks Doc.
Sent from my SGH-T999 using XDA Premium 4 mobile app
DocHoliday77 said:
I second this.
Some reported that after rebooting several times, everything returned to normal. It is very weird, but in this case the IMEI is not lost, it's just the O/S isn't reading it for whatever reason.
If rebooting doesn't eventually help, you could try using nvrestore. But just about everyone has said an Odin flash back to stock solved it.
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
I decided to flash the ROM again and still had the same issue, went through the setup wizard and rebooted the device and everything went back to normal. Thank you DocHoliday77.
Sent from my SGH-T999 using XDA Premium 4 mobile app
Anytime! Haven't seen him much lately but mt3g had this issue and it seemed that once he ran the reboot nvbackup command, it would fix itself after the first boot, whereas for others he said it was taking several attempts.
I think it was aerowinder that was also in that discussion with us so I credit the two of them for educating me on it. The two of them are usually who I learn the cm/aosp stuff from!
Sent from my SCH-I535 using Tapatalk 4
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!