FORUMS

Index Project For XDA Device Subforums

Another ambitious project from the collaborative efforts of Recognized Contributors and Forum … more

The Atlas of XDA

A few weeks ago, we asked you “How Does Your Location Affect Your Life As A Power User?”. In the days that … more

New Snapdragons: Some Context & Contrast

It hasn’t been a good year for Qualcomm so far. Every device featuring the Snapdragon 810 … more

Google To Launch Next Gen Android One On July 14

The first gen of Android One devices to be launched in India in September 2014 were … more

[Q] Can't open Security settings after restoring Nandroid for replacement

37 posts
Thanks Meter: 4
 
By Platypus222, Member on 29th May 2014, 05:08 AM
Post Reply Subscribe to Thread Email Thread
OK, so I have a Moto X Developer Edition (rooted, stock 4.4.2) that I recently requested a replacement for from Motorola. I took a full Nandroid backup on the old phone and restored it on the new one. After ironing out the initial kinks on the original phone (disabling Xposed and removing PIN) and trying again, the new phone looked to be at 100% until I tried setting my PIN up again. Whenever I try to go to the Security settings, I get an "Unfortunately, Settings has stopped" message. One suggestion I found was to re-flash system.img, which I did to no avail. This page gives a way to fix the issue by fixing permissions of a file, but it seems to be specific to the Nexus 4 as the Moto X does not have the file specified (or at least I can't find it).

The only other potential means to fixing this that I can find is to wipe the data partition, but that means I can't use my Nandroid backup, which means more work I'd like to prevent if possible. Of course, I still have both phone for a limited time, so if there's something I can do on the original phone that will make my backup usable, that would also work.

Thanks!
 
 
29th May 2014, 08:47 AM |#2  
SymbioticGenius's Avatar
Senior Member
Thanks Meter: 128
 
More
If they are both rooted etc backup everything with Titanium backup then restore to the new phone everything except settings related apps.

Not saying that's the fix but it's definitely what I would try next. If it doesn't work the first time. Factory reset the phone, wipe caches, confirm settings works then restore again. If that doesn't work let me know, we'll troubleshoot some more.
29th May 2014, 07:34 PM |#3  
Ctrl-Freak's Avatar
Senior Member
Thanks Meter: 119
 
More
That error is likely related to a mismatch between /system and the modem/radio version.

I am guessing you restored the 4.4.2 nandroid to the phone while it was running 4.2.2. This will not flash the modem, but you can manually flash the corresponding modem for your build of android using fastboot.
29th May 2014, 08:57 PM |#4  
OP Member
Thanks Meter: 4
 
More
Quote:
Originally Posted by Ctrl-Freak

That error is likely related to a mismatch between /system and the modem/radio version.

I am guessing you restored the 4.4.2 nandroid to the phone while it was running 4.2.2. This will not flash the modem, but you can manually flash the corresponding modem for your build of android using fastboot.

Yeah, that's exactly what I did. Where can I get the modem/radio image file? I have the zip from the latest version but I don't see it in there.
29th May 2014, 11:26 PM |#5  
Ctrl-Freak's Avatar
Senior Member
Thanks Meter: 119
 
More
Quote:
Originally Posted by Platypus222

Yeah, that's exactly what I did. Where can I get the modem/radio image file? I have the zip from the latest version but I don't see it in there.

The modem is called NON-HLOS.bin. Also, I believe that "fsb.mbn" is related to the modem, and I update mine whenever I update the modem.


Here are the commands for motorola's fastboot (do not use a generic fastboot exe):
Quote:

fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2

The Following 2 Users Say Thank You to Ctrl-Freak For This Useful Post: [ View ]
30th May 2014, 03:18 AM |#6  
OP Member
Thanks Meter: 4
 
More
Quote:
Originally Posted by Ctrl-Freak

The modem is called NON-HLOS.bin. Also, I believe that "fsb.mbn" is related to the modem, and I update mine whenever I update the modem.


Here are the commands for motorola's fastboot (do not use a generic fastboot exe):

Thank you! So far as I can tell that worked perfectly!
The Following User Says Thank You to Platypus222 For This Useful Post: [ View ]
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes