[GUIDE] Nexus 4 - Factory Image Restore

[2defmouze]

The reason is 4.2.2 OTA caused my Nexus4 to not be able to connect to Simple Mobile at all. It's as if a SIM card wasn't in there. If i move SIM to iPhone 4, then it can connect.

Might just need to check the APN settings (Google it).. But I can link to the 4.2.1 image when I get home in a bit if you can't fix it.

Sent from my Nexus 4 using Tapatalk 2

 

[2defmouze]

Here is the 4.2.1 factory image, if needed: https://dl.dropbox.com/u/47300967/occam-jop40d-factory-ca7602f0.tgz

 

[mrdwong]

I followed the steps and I get stuck at boot up with the "X". I boot into TWRP and it asks me for a password. I had my phone encrypted before and I used that password, but it's not working. Is there a generic password that I can try. I think that is what is messing with the startup of the phone.

I think I solved my own problem. If the password screen shows up, cancel and then clear both caches and do a factory reset. After that, my phone booted up fine.

 

[2006yamahaR6]

yeah... i'm stuck at the X splashscreen - any ideas?

I followed the directions exactly, I tried waiting 8 minutes, and rebooting manually, I tried unplugging then rebooting, I tried booting into bootloader (which worked) then I used fastboot on my mac to erase the cache, and rebooted once again.... and nothing.

I would try using the toolkit, but I dont have windows

 

[ahealey]

yeah... i'm stuck qat the X splashscreen - any ideas?

I followed the directions exactly, I tried waiting 8 minutes, and rebooting manually, I tried unplugging then rebooting, I tried booting into bootloader (which worked) then I used fastboot on my mac to erase the cache, and rebooted once again.... and nothing.

I would try using the toolkit, but I dont have windows

Let me preface this with: I'm no expert and don't know exactly what I'm doing.

However, I was in your same situation. My phone previously was encrypted and had a passcode. I did the factory reset and couldn't get past the X. Tried clear cache afterwards, did the recovery volume up + power, etc.

Finally, I tried oem lock and then oem unlock. Got the screen to delete everything. Restarted the phone and it's worked ever since.

Ben

 

[macshome]

I was stuck at the X as well after restoring the 4.2.2 factory image. Nothing worked until I did the oem lock, oem unlock like you did.

Works fine now!

 

[DeadpoolJunior]

I'm truly stuck guys. Followed these instructions from CM10.1 and got stuck on the X after wiping everything, same as everybody. Tried using a toolkit but the two I used wont work despite my drivers being installed perfectly. They say turn USB debugging on, but how can I do this without being able to even get to the home screen. Im a little pissed here.

EDIT: Tried the lock, unlock thing you guys did. Worked like a charm. Thank God. I recommend anyone who has troubles getting stuck at the X simply lock, then unlock their bootloader from the command prompt. All is well now.

 

[2defmouze]

Adding that to the troubleshooting tab now guys.. thanks for the heads up, and glad you got everything working!

 

[Lawrence Dorn]

the lock/ unlock trick worked for me also....

 

[slowcom]

Question - how long is too long for it to be on the 'writing 'system'...' step?

Actually it's having a problem erasing userdata.

erasing 'userdata'... FAILED (command write failed (No such file or directory))

Any ideas?

 

[2defmouze]

Skip it if possible..

Sent from my Nexus 4 using Tapatalk 2

 

[slowcom]

Skip it if possible..

Sent from my Nexus 4 using Tapatalk 2

I ended up doing that... I am able to get past the Google splash screen now it's sitting on the green, yellow, blue and red x. I've wiped caches and all that stuff... Any other ideas?


EDIT: I got it fixed. Used the Nexus4ToolKit -> Download, Extract + Flash Google Facotry Stock Rom and just followed the directions. Thanks for this tutorial!

 

[2defmouze]

I ended up doing that... I am able to get past the Google splash screen now it's sitting on the green, yellow, blue and red x. I've wiped caches and all that stuff... Any other ideas?

See the last few posts.. Lock/unlock again..

Sent from my Nexus 4 using Tapatalk 2

 

[Robert Cross]

I am Totally lost these directions from what I see are not step by step. Or I am just ed.
Step 3 nope.
I have the driver installed I think. Google nexus 4 boot loader interface is the name.
The Note section you have completely lost me do I need to add
fastboot-windows ? ? ? before the rest of the code you have in the "green section"
My Devices don't even show up.
What I have is a phone that wont go past the google screen (I really think I wiped out the entire device)

 

[2defmouze]

I am Totally lost these directions from what I see are not step by step. Or I am just ed.
Step 3 nope.
I have the driver installed I think. Google nexus 4 boot loader interface is the name.
The Note section you have completely lost me do I need to add
fastboot-windows ? ? ? before the rest of the code you have in the "green section"
My Devices don't even show up.
What I have is a phone that wont go past the google screen (I really think I wiped out the entire device)

Take your time and start from the beginning. Read carefully. If dozens of noobies can follow the directions you can too

Let me know any specific issues, and browse the thread to see solutions others may have found to similar ones... It's not that long, and the process is pretty simple.

Sent from my Nexus 4 using Tapatalk 2

 

[Tronstar]

This saved my butt last night. I thought my phone was toast! The night before my phone randomly rebooted and then froze at the nexus X boot screen. Couldn't even turn the screen off, had to let it drain in that frozen sate (I wish we had a removable battery!). Since it was almost dead when trying to flash, I was having lots of issues. So I charged it up and it went flawless. I also had to do the lock/unlock after.

Morale of the story, make sure your phone is properly charged before fastboot/adb as the computer usb port doesn't provide much power.

 

[pjc123]

So, oem lock and oem unlock didn't work for me. I am stuck at the Google screen and can't even turn the device off. Hopefully it doesn't catch fire while I am asleep tonight.

This is my first time unlocking a bootloader and rooting a smartphone, but that part seemed to go OK. Here are the specifics:

1) Started with 4.2.1 because I didn't want to add any new version complications. Followed the directions on this forum ([GUIDE] Nexus 4 Unlock & Root) to unlock the bootloader and root. Very easy to follow and everything worked perfectly.
2) Loaded the OTA Rootkeeper app to save the unlocked root.
3) Upgraded to 4.2.2.
4) Restored root with OTA Rootkeeper.
5) Loaded all my apps back up, but this time loaded some that required root.
6) Titanium Backup required some special setting permissions. When I tried to go to the Security section of the Settings Folder it crashed the Settings screen (I see others on the web are having the same problem).
7) I saw a set of directions to fix the Security setting issue which stated to re-install the factory image as follows:

fastboot flash system system.img
reboot

So I did the following (I guess this is what they mean by the above statement) and it ran OK. Used the image for Nexus 4 from Googles site.:

fastboot flash system occam-jdq39-factory-345dc199
There was no ?reboot? command so I can only suspect they meant turn the device off/on

So what now? Am I going to have to follow the instructions here ([GUIDE] Nexus 4 ? Factory Image Restore) to install the factory image again and lose all my changes and start all over again?

More importantly, how do I avoid this next time? Did 4.2.2 cause this problem? Did one of my apps cause this problem?

 

[2defmouze]

So, oem lock and oem unlock didn't work for me. I am stuck at the Google screen and can't even turn the device off. Hopefully it doesn't catch fire while I am asleep tonight.

This is my first time unlocking a bootloader and rooting a smartphone, but that part seemed to go OK. Here are the specifics:

1) Started with 4.2.1 because I didn't want to add any new version complications. Followed the directions on this forum ([GUIDE] Nexus 4 Unlock & Root) to unlock the bootloader and root. Very easy to follow and everything worked perfectly.
2) Loaded the OTA Rootkeeper app to save the unlocked root.
3) Upgraded to 4.2.2.
4) Restored root with OTA Rootkeeper.
5) Loaded all my apps back up, but this time loaded some that required root.
6) Titanium Backup required some special setting permissions. When I tried to go to the Security section of the Settings Folder it crashed the Settings screen (I see others on the web are having the same problem).
7) I saw a set of directions to fix the Security setting issue which stated to re-install the factory image as follows:

fastboot flash system system.img
reboot

So I did the following (I guess this is what they mean by the above statement) and it ran OK. Used the image for Nexus 4 from Googles site.:

fastboot flash system occam-jdq39-factory-345dc199
There was no ?reboot? command so I can only suspect they meant turn the device off/on

So what now? Am I going to have to follow the instructions here ([GUIDE] Nexus 4 ? Factory Image Restore) to install the factory image again and lose all my changes and start all over again?

More importantly, how do I avoid this next time? Did 4.2.2 cause this problem? Did one of my apps cause this problem?

You lose me at #6.. None of that makes sense or should be necessary... Also when you are stuck on the boot logo just hold power until the device turns off.

Sent from my Nexus 4 using Tapatalk 2

 

[pjc123]

Also when you are stuck on the boot logo just hold power until the device turns off.

Does not work, and others are having the same problem. The phone turns off and then immediately turns back on again. It is impossible to turn the phone off.

You lose me at #6.. None of that makes sense or should be necessary.

I can only tell you what occurred; let me give you more details. During the Titanium Backup install, a message came up stating that for the program to operate properly, that I had to checkmark two settings in the settings menu of my phone. These are the two settings it told me I had to enable (Not sure I have the exact titles or path because I didn't write it down):
1) Settings > Application > Development >USB debugging
2) Settings > Application > Security > Unknown Sources

I could not get into the Security settings, as has happened to many others. See here:
[FIXED]Upgraded to 4.2.2 through the OTA and now I get a settings FC... - xda-developers

As a side note I can still get into the fastboot mode (Android picture screen), but I have to time it just right, before the phone turns itself back on automatically after attempting to power it down with the power button. I have a feeling that OTA Rootkeeper may have caused the corruption with the Security menu having to abort when trying to access it, though I am just speculating.

 

[2defmouze]

Also when you are stuck on the boot logo just hold power until the device turns off.

Does not work, and others are having the same problem. The phone turns off and then immediately turns back on again. It is impossible to turn the phone off.

You lose me at #6.. None of that makes sense or should be necessary.

I can only tell you what occurred; let me give you more details. During the Titanium Backup install, a message came up stating that for the program to operate properly, that I had to checkmark two settings in the settings menu of my phone. These are the two settings it told me I had to enable (Not sure I have the exact titles or path because I didn't write it down):
1) Settings > Application > Development >USB debugging
2) Settings > Application > Security > Unknown Sources

I could not get into the Security settings, as has happened to many others. See here:
[FIXED]Upgraded to 4.2.2 through the OTA and now I get a settings FC... - xda-developers

As a side note I can still get into the fastboot mode (Android picture screen), but I have to time it just right, before the phone turns itself back on automatically after attempting to power it down with the power button. I have a feeling that OTA Rootkeeper may have caused the corruption with the Security menu having to abort when trying to access it, though I am just speculating.

You mention 2 problems you are having that "many others" are having.. But these are not people following my guide. I'm not going to go digging through another forum to diagnose the issues people are having with their guide.. Have to worry about my own, lol. Nobody else who has used this guide has mentioned the issues you are having, and a lot of people have used it

Sent from my Nexus 4 using Tapatalk 2