Nexus 4.3 update failed, "no command" - Nexus 4 Q&A, Help & Troubleshooting

So i got the new 4.3 update notification on my phone today. Eager to get it i started the installation (battery level was about 90%). After a while the installation went into a constant reboot, always went untill halfway of the progress bar and then phone went off and started again to same screen. I knew it was ****ed up so i went into recovery mode but then it starts to do the update again and i got the "ERROR" message. So i went into recovery again and now i get the "NO COMMAND". I was running 4.2.2 with everything stock, device was not even rooted...
Any ideas?

ybuedts said:
So i got the new 4.3 update notification on my phone today. Eager to get it i started the installation (battery level was about 90%). After a while the installation went into a constant reboot, always went untill halfway of the progress bar and then phone went off and started again to same screen. I knew it was ****ed up so i went into recovery mode but then it starts to do the update again and i got the "ERROR" message. So i went into recovery again and now i get the "NO COMMAND". I was running 4.2.2 with everything stock, device was not even rooted...
Any ideas?
Click to expand...
Click to collapse
Unlock your bootloader, and flash the stock 4.3 image manually. Download it from here
https://dl.google.com/dl/android/aosp/occam-jwr66v-factory-08d2b697.tgz
After that, you can relock your bootloader if you want.

abaaaabbbb63 said:
Unlock your bootloader, and flash the stock 4.3 image manually. Download it from here
After that, you can relock your bootloader if you want.
Click to expand...
Click to collapse
I've got very basic knowledge of android so i don't really know what to do... I imagine if i flash the stock manually i will lose all my data? Because in that case i might aswell go to the store and ask a new one since i still have my warranty...

ybuedts said:
I've got very basic knowledge of android so i don't really know what to do... I imagine if i flash the stock manually i will lose all my data? Because in that case i might aswell go to the store and ask a new one since i still have my warranty...
Click to expand...
Click to collapse
Ok, if you have a store nearby, go to them. They will fix it properly. With basic knowledge, it's pretty dangerous.

Similar Prob
Hey guys,
I have a similar problem. Tried the upgrade to 4.3 and it stucked.... well now i constantly see the Google-X-symbol and thats all. Tried to unlock the bootloader via developer tools (for later flashing to Stock ROM) but there's no connection. Tried to replug it, etc.
When I start the bootlaoder (via Vol-Down and On-Button) I can choose the options (but recovery is not possible) But hm, the bootloader doesn't seem to be broken.
Can anyone help me? I'm not really a developer (although I work for a software-company) but I already unlocked and rooted devices and I have experiences in changing deep settings.
Help would be great!!! I don't want to sent it to google - I am lost without my S-Phone....
Thanks!

I have a similar issue, I found the update notification on my phone, went ahead with the update and it took ages! The battery was nearly full and the battery fully discharged while it was updating. I was at a friends house so no charger. When I got home I fully charged the phone and switched the phone on and got the nexus cross animation and thats all. I tried to enter recovery mode but got the no command icon.
Any help would be appreciated, I do have experience of rooting and flashing custom roms on my HTC Desire but have not touched the nexus since I got it. So everything on the phone is stock
Heres interesting, My wife tagged me into a facebook post telling peeps my phone was out of order, as she did it, the facebook app on my phone notified me of the tag!! Still got the nexus boot animation showing on the screen!

waynehardy said:
I have a similar issue, I found the update notification on my phone, went ahead with the update and it took ages! The battery was nearly full and the battery fully discharged while it was updating. I was at a friends house so no charger. When I got home I fully charged the phone and switched the phone on and got the nexus cross animation and thats all. I tried to enter recovery mode but got the no command icon.
Any help would be appreciated, I do have experience of rooting and flashing custom roms on my HTC Desire but have not touched the nexus since I got it. So everything on the phone is stock
Heres interesting, My wife tagged me into a facebook post telling peeps my phone was out of order, as she did it, the facebook app on my phone notified me of the tag!! Still got the nexus boot animation showing on the screen!
Click to expand...
Click to collapse
Ha, that's exactly the same issue.... Thank God I'm not the only one (sorry )

I got the "no command" error after my update this morning. My battery was pretty low, but the phone was docked. I just left the phone alone while I came here to investigate, and it eventually rebooted itself. Then it stuck on the loading X for around 5 minutes, but now it is optimizing my apps. Looks like it is going to work after all.

Mine has been on for a while but its not seeming to play. what mkes no sense is that it is switched on in the background but the nexus animation is the only thing it shows

I'm having the exact issue. I got my update notification this morning and it failed, going into an endless loop. I called google and they didn't know what was happening, so they're sending me a new phone. I don't want to wait for the new one, so I'm trying to fix this one still. I can start the bootloader, but I can't get into recovery. Is there a way to correct this through ADB?

justin1701 said:
I'm having the exact issue. I got my update notification this morning and it failed, going into an endless loop. I called google and they didn't know what was happening, so they're sending me a new phone. I don't want to wait for the new one, so I'm trying to fix this one still. I can start the bootloader, but I can't get into recovery. Is there a way to correct this through ADB?
Click to expand...
Click to collapse
When you get to the screen with "NoCommand" on it.
1. Press and hold power button
2. Then once you pressing the power button, press the Vol - Up
Thats it
OrangeNik

Here is the fix for everyone
Ok, I just got off a chat with an Asus rep.
Step 1: Hold the power and volume up/down to get the android with the "start" option
Step 2: Use the volume down to select "recovery mode" It will now power off and power back up with the dead android and "no command" below it
Step 3: While holding the power button TAP, but DO NOT hold the volume up button. You will get an option to wipe all data. Do that.
Blammo the world's problems are solved

LG Nexus 4 E960
Work perfectly for me
Nexus Root Toolkit v2.1.4
I can't post a link because I don't have 10 posts!!!

Related

[Q] Phone unresponsive randomly

Hi guys, something strange happened, got my nexus 3 weeks ago and i right away unlocked bootloader, flashed custom recovery and rooted it, installed a few apps and everything was fine, day before yesterday while sending an email my phone got stuck and rebooted, took awhile and when it did i noticed the cell network being empty, i would press anything on the screen and it would do the same. So i downloaded the stock images and flashed everything according to section D of the topic http://forum.xda-developers.com/show....php?t=2010312 and boot took awhile finally it started and i got the welcome screen, clicked on English USA and again the cell network is empty and phone frooze in the first screen only, it rebooted and it boots up with a black screen and i get the message "process system isn't responding, OK or wait" and press ok or wait whichever and phone reboot or even if i try to press any of the options, its stuck. But bootloader works since i can do fastboot devices or fastboot reboot-bootloader, i can also boot into recovery which is CMW. This is getting frustrating and im confused, can anyone help me out here? Thanks
RMA time. Relock the bootloader and ship her off. If reloading the stock images doesn't fix it, it's likely hardware.
estallings15 said:
RMA time. Relock the bootloader and ship her off. If reloading the stock images doesn't fix it, it's likely hardware.
Click to expand...
Click to collapse
Isn't there anything else i can try before shipping it back or give up?
EDIT:
I pushed CM zip file via adb and it got pushed successfully and i even flashed it via CMW recovery and it even said complete and when i reboot the device its stuck on the Google screen and nothing else happens..
masantula said:
Isn't there anything else i can try before shipping it back or give up?
Click to expand...
Click to collapse
Gong back to all stock software with fresh flashes is the most extreme attempt at a fix, software wise. What else would you do?
Hmmm, true...this sucks, no other option...thanks

[Q] ? OTA 4.2 to 4.3 Error. Please help

I just received my nexus 7 today 32gb checked for firmware update it asked to reboot and install clicked ok then i received an error during update install with a picture of a green aandroid character . My nexus will not reboot its stuck at the bootloader screen with the x. Is this common and how do i fix it ?
Rmontoya83 said:
I just received my nexus 7 today 32gb checked for firmware update it asked to reboot and install clicked ok then i received an error during update install with a picture of a green aandroid character . My nexus will not reboot its stuck at the bootloader screen with the x. Is this common and how do i fix it ?
Click to expand...
Click to collapse
If you just received it today, is it really a Nexus 7 2012 edition device? If not, you should be in the Nexus 7 2013 forum instead of this forum.
Having said that though, a completely stock device which fails an OTA update is somewhat unusual.
Make sure the tablet is 100% charged and do a factory reset on it. Don't spend a bunch of time on re-configuring it; do the minimum needed to get it connected to the internet and attempt the OTA again once it is fully charged.
If you get the same trouble again, return the tablet immediately.
If you see that little graphic (android lying down) on the screen, you need to push some buttons to get the hidden menu items to pop up on the screen. The 2013 N7 might be different than the 2012 N7, but the button sequence for seeing that is pressing the power button simultaneously with Vol-Up and releasing them. One of the menu items there is "reboot" (or power off - I can't remember), and another is "factory reset".
As I mentioned, don't do any of this stuff unless the tablet is well charged.
The (hidden) button pressing combinations for the 2012 N7 are here. I have no idea if they are similar for the 2013 N7.
good luck. sorry about your Dec 25th hiccup.
I tried no luck i used wugs to try and restore it but i think it deleted my system img files and stuf if there a way i can put them back with a locked bootloader. I can get to the bootloader menus and stuff but top left corner says bootfailed.
Rmontoya83 said:
I tried no luck i used wugs to try and restore it but i think it deleted my system img files and stuf if there a way i can put them back with a locked bootloader. I can get to the bootloader menus and stuff but top left corner says bootfailed.
Click to expand...
Click to collapse
Just unlock the bootloader and flash a factory image.
How when i cant get the phone to boot up,

lg mobile support tool stuck at 49%

i tried going back to stock firmware using the method in general section but i always seem to get an error at 49%. can someone explain how to get passed this.
i using the t-mobile d801.
also my recovery seemed to have gotten erased because i cant boot into twrp anymore.
LG G2 Stuck @ 49%
El Killer said:
i tried going back to stock firmware using the method in general section but i always seem to get an error at 49%. can someone explain how to get passed this.
i using the t-mobile d801.
also my recovery seemed to have gotten erased because i cant boot into twrp anymore.
Click to expand...
Click to collapse
HEY! I'm on the d801 as well and I've been where you're at a number of times, unfortunately. But I've always gotten out. Here's the conclusion I've reached. Trying to flash directly back to stock without wiping all the partitions first is what makes the RDTool get stuck. It's like the phone runs out of memory and can't host a full Gig+ of data since your last ROM is in the way. Sorry if I'm wrong but I'm only assuming you didn't wipe everything except the Internal storage. The good thing every time this has happened to me is that your recovery partition should be intact. Mine always is, and we're on the same variant. Another thing, booting back into recovery is not impossible. It's all in the timing it takes from the first time you see the LG logo while holding volume - and the power button, but don't let go. What worked for me was to let the phone cycle between off and boot power states twice until the phone is completely off again. You may even notice the LED indicator flash red. Release your keys if the phone stays off and immediately hold the combo down again until the phone tries to boot again just don't let go of the buttons. Once it powers down again, leave the phone alone for a few minutes. Come back and this time get ready to boot into recovery. The combo button press will initiate boot but don't let go until the next time you see the LG logo flash, then quickly release and depress the vol down power up combo and hold. May take a minute longer than usual but the reset menu should pop up thereafter. Tap power 2 more times and you should back into recovery. It's worked every time for me. Let me know if you're good and whether this helped!
Good Luck,
tinydynamite00
try with x86
El Killer said:
i tried going back to stock firmware using the method in general section but i always seem to get an error at 49%. can someone explain how to get passed this.
i using the t-mobile d801.
also my recovery seemed to have gotten erased because i cant boot into twrp anymore.
Click to expand...
Click to collapse
i had exact same issue that progress stucked on 49%. if you are using 64bit OS, try to flash it with 32bit(x86) OS
good luck
tinydynamite00 said:
HEY! I'm on the d801 as well and I've been where you're at a number of times, unfortunately. But I've always gotten out. Here's the conclusion I've reached. Trying to flash directly back to stock without wiping all the partitions first is what makes the RDTool get stuck. It's like the phone runs out of memory and can't host a full Gig+ of data since your last ROM is in the way. Sorry if I'm wrong but I'm only assuming you didn't wipe everything except the Internal storage. The good thing every time this has happened to me is that your recovery partition should be intact. Mine always is, and we're on the same variant. Another thing, booting back into recovery is not impossible. It's all in the timing it takes from the first time you see the LG logo while holding volume - and the power button, but don't let go. What worked for me was to let the phone cycle between off and boot power states twice until the phone is completely off again. You may even notice the LED indicator flash red. Release your keys if the phone stays off and immediately hold the combo down again until the phone tries to boot again just don't let go of the buttons. Once it powers down again, leave the phone alone for a few minutes. Come back and this time get ready to boot into recovery. The combo button press will initiate boot but don't let go until the next time you see the LG logo flash, then quickly release and depress the vol down power up combo and hold. May take a minute longer than usual but the reset menu should pop up thereafter. Tap power 2 more times and you should back into recovery. It's worked every time for me. Let me know if you're good and whether this helped!
Good Luck,
tinydynamite00
Click to expand...
Click to collapse
still no luck
El Killer said:
still no luck
Click to expand...
Click to collapse
OK. So tell me, what ROM were you on, which recovery version and name are you using, why were you flashing back to stock, i.e. were you having problems, what kind. Explain as much as you can in detail. Need to retrace your exact steps to best get you fixed up!
tinydynamite00
tinydynamite00 said:
OK. So tell me, what ROM were you on, which recovery version and name are you using, why were you flashing back to stock, i.e. were you having problems, what kind. Explain as much as you can in detail. Need to retrace your exact steps to best get you fixed up!
tinydynamite00
Click to expand...
Click to collapse
i was using pa4.0 and wanted to go back to stock because i preffered the lg ui. i had twrp 2.6.3.5 i restored my back up of stock but when i rebooted i got into fastboot mode.
twrp wasnt working after i had restored my back up go straight to fastboot was stuck in fastboot until i found a thread explaining how to get out of fastboot and restore download mode.
managed to get download mode working and tried to flash stock with mobile support tool and got the 49 percent error,
my phone never really displayed any progress just says download mode with a white box and blue dots
El Killer said:
i was using pa4.0 and wanted to go back to stock because i preffered the lg ui. i had twrp 2.6.3.5 i restored my back up of stock but when i rebooted i got into fastboot mode.
twrp wasnt working after i had restored my back up go straight to fastboot was stuck in fastboot until i found a thread explaining how to get out of fastboot and restore download mode.
managed to get download mode working and tried to flash stock with mobile support tool and got the 49 percent error,
my phone never really displayed any progress just says download mode with a white box and blue dots
Click to expand...
Click to collapse
K, now if you're only seeing the blue dots when you attach by USB your phone to PC, then you're not fully in DL mode to process the kdz. You should see a white wheel in the center of the screen when you connect and a viewing mirror near the base of your phone with ROOTED in red directly below that. And you're sure your PC is detecting your phone? You've the drivers installed? Because when RDT tells you to run the tool, you'll see some binary code in the viewing window I spoke of, the white wheel will turn and below it will be shown the COM port to which you're connected and a solid thin red bar will begin to fill a space in the viewer showing you the progress.
Also, be sure when attempting the first steps I gave you to boot into recovery that you are not USB connected. It won't work.
And, try to remember if your phone was well enough charged, should have been at least 80% full. It happened to me once that I couldn't boot recovery and my phone would go to fastboot like yours until I left it alone to charge and then I repeated the stepsvi laid out to get back into recovery. This part is paramount!
Please READ CAREFULLY
I used to be in your same situation. I thought I had bricked my phone for good. I finally figured it out. Here is my solution from my Thread.
Esteef said:
Okay, after 12+ hours of trying every method possible on XDA I finally resolved my issue. I will update the first post just incase any others care or fall into the same dilemma I was in.
The LG Mobile Support tool would not download the firmware and it would NOT ask me for my IMEI to download it either.
So my solution....
***
Installed LG Mobile Support Tool then Installed the LG Drivers. (FROM HERE http://forum.xda-developers.com/showthread.php?t=2471370
BEFORE I connected the phone to the computer. I opened the LG Mobile support tool clicked (Options on the top right).
When the dropped down opened, I clicked the (Upgrade Recovery) option. THEN, is when the prompt opened to ask me what my IMEI is.
Before I entered my IMEI, I connected my phone to the computer in download mode, then proceeded to enter my IMEI and hit OK.
This is when the LG Mobile Support tool SUCCESSFULLY downloaded the latest official LG firmware and installed it.
*** BE AWARE, with the phone connected to the PC, the prompt NEVER appeared to enter my IMEI.
*** But with the phone disconnected, the prompt came up every time. This might be the trick for some people.
*** with the IMEI prompt opened, I then connected the phone , entered the IMEI, then hit OK. BOOM HERPES....
Well I'll polish this up more later. I hope this works for every LG G2 Variant and not just the T-Mobile one (D801)
-Esteef
Click to expand...
Click to collapse
THIS WILL WIPE YOUR PHONE COMPLETELY...
tinydynamite00 said:
K, now if you're only seeing the blue dots when you attach by USB your phone to PC, then you're not fully in DL mode to process the kdz. You should see a white wheel in the center of the screen when you connect and a viewing mirror near the base of your phone with ROOTED in red directly below that. And you're sure your PC is detecting your phone? You've the drivers installed? Because when RDT tells you to run the tool, you'll see some binary code in the viewing window I spoke of, the white wheel will turn and below it will be shown the COM port to which you're connected and a solid thin red bar will begin to fill a space in the viewer showing you the progress.
Also, be sure when attempting the first steps I gave you to boot into recovery that you are not USB connected. It won't work.
And, try to remember if your phone was well enough charged, should have been at least 80% full. It happened to me once that I couldn't boot recovery and my phone would go to fastboot like yours until I left it alone to charge and then I repeated the stepsvi laid out to get back into recovery. This part is paramount!
Click to expand...
Click to collapse
yeah my computer does recognize my phone. but i cant run adb or fastboot anymore. all drivers are installed also.
i never got the while wheel or any progress indicator. so i guees im not really in download mode.
i let my phone charge for a few hours and try your method again and let you know what happens
El Killer said:
yeah my computer does recognize my phone. but i cant run adb or fastboot anymore. all drivers are installed also.
i never got the while wheel or any progress indicator. so i guees im not really in download mode.
i let my phone charge for a few hours and try your method again and let you know what happens
Click to expand...
Click to collapse
Sounds good. A full charge can make all the difference. I learnt the hard way! One or more of us will be along should you need further help.
I do hope you get this sorted! I've come back from the brink too many times to not believe you won't.
tinydynamite00
Do as esteef recommended..
Sent from my LG-D802 using XDA Premium 4 mobile app
Falaco147 said:
Do as esteef recommended..
Sent from my LG-D802 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
im trying but i get a battery to low error. i guess i need to charge it longer
i owe you all a million thanks for helping me unbrick my phone. i really thought i was left with a paper weight and then i tried esteefs method again i really owe you guys thank you for the support
El Killer said:
i owe you all a million thanks for helping me unbrick my phone. i really thought i was left with a paper weight and then i tried esteefs method again i really owe you guys thank you for the support
Click to expand...
Click to collapse
You are welcome... The first time I did it too my battery was at 28% and I panicked since I got the low battery error.
I could of sworn that my phone officially became a paper weight. My heart dropped.
I'm glad you are up and running with the rest of us!
-Esteef
1732359994
hey !
I have the same problem, but... I can't acces to the recovery :/ i tried to install CWM (with Freegee) over Team win recovery and... boot loop :
The rom 4.2.2 flex was gone, no boot animation
-When i pres volum down + power, i have the reset menu, but after that, there is a black screen and it's written at the top left "started usb_start Fastboot Mode ()"
Please, i need your help, i'm so afraid !!
Thx !
Esteef said:
I used to be in your same situation. I thought I had bricked my phone for good. I finally figured it out. Here is my solution from my Thread.
THIS WILL WIPE YOUR PHONE COMPLETELY...
Click to expand...
Click to collapse
I know this thread is a bit old, but it saved my butt. Your method worked perfectly. Thank you for this post.
My LG F460 was bricked (error 570), only download mode was working. Esteef method works fine even my pictures and programs was saved. Thanks!

**SOLVED** [Q] My Droid Razr M won't get past the droid eye on boot up

I apologize already if this has already been posted before, I couldn't see one that had my issues so I'm making this thread.
OK, so here is my problem and everything that I can think of that I've done to my phone.
Today I tried to restart my phone as it was getting a bit sluggish. When I did it started booting fine then the animation sound stopped while the droid eye was being put together. Now my phone will not pass the droid eye during the boot phase. I press the power and both volume buttons and after a few seconds it starts itself back up again. I do the power button and down volume buttons and it still does the same thing. I've even performed the factory reset twice and it still won't help.... And no matter what I do it keeps booting itself back up on its own.
What I've done to my phone:
I am rooted but never got the boot loader unlocked since i waited too long and the last update wouldn't allow the boot loader unlock methods anymore. I have used titanium backup app to delete some system apps for example the Verizon football one, slacker radio, and any of those useless apps that I never use. I haven't deleted anything lately and have restarted my phone many times since. I have been delaying the recent update hitting no or not now, whatever it says. I thought that I said no today on the system update as well. Even then my phone was working before I restarted it.
PLEASE I hope that there is something that I can do to fix my phone because I'm forced to use my LG Vortex again and my upgrade isn't for another year..... I don't want to buy a new one since this phone has been great and I'm almost certain that if there was a way to reinstal or flash the droid razr m OS that that would fix my issues.
Thanks in advance for your input and please know that I'm a novice with this kind of thing so you will have to explain the process to me. If i have instructions I can definitely follow them.
THANKS!
You Factory Reset a couple of times, so that tells me you know how to get into recovery. See if you can get back into recovery and try clearing cache/dalvik too. I think you can still do that from stock recovery.
If that doesn't work and your battery is good, you can fastboot to recover it. If your battery was low when you started this, charge it prior to fastbooting. Just hold down the power button until the phone shuts off and plug into a WALL charger until it's charged. If the battery is good, you can grab the firmware from here http://sbf.droid-developers.org/phone.php?device=8 (use the second one from the bottom, .3, if you flash the last one you will not be able to gain root) and flash in RSD. Another choice is to use House of Moto to recover: http://www.droidrzr.com/index.php/topic/28162-house-of-moto-20/ .
OK, so I deleted the cashe and still a no go. For the second step of getting the .3 to regain root. would it be possible to get an even earlier version so I can unlock the boot loader? Also when you say flash in RSD, what is that? I know of the AP flash from the first menu, is that something inside of Recovery menu options?
Thanks for your help!
**UPDATE**
THANKS! I was able to eventually figure it out and used the last option that you said and my phone works! Now working on getting root back. Thanks again!! But I really would like to know if I could do the same thing but with an earlier version to unlock the bootloader.
Droid Razr starting up issue
Hi guys, I am facing a weird issue with my Droid Razr and hoping pros to help me sort this out and get my phone running.
I am using Droid Razr but since last one week it is not starting up. Let me elaborate, currently it is switched off and not getting up. While starting it pass through M logo but can't go ahead for startup animation (droid eye animation). Even after leaving on that animation for entire day, it is not going ahead of that.
However, if I connect it to a wall charger (while it is off) it shows battery getting charged. It is taking a usual timing of 90 minutes for full charge.
I have important pictures and data into phone memory is there any way to recover it.
I would appreciate if you can guide me to get my phone up and running as usual.
RikRong said:
You Factory Reset a couple of times, so that tells me you know how to get into recovery. See if you can get back into recovery and try clearing cache/dalvik too. I think you can still do that from stock recovery.
If that doesn't work and your battery is good, you can fastboot to recover it. If your battery was low when you started this, charge it prior to fastbooting. Just hold down the power button until the phone shuts off and plug into a WALL charger until it's charged. If the battery is good, you can grab the firmware from here (use the second one from the bottom, .3, if you flash the last one you will not be able to gain root) and flash in RSD. Another choice is to use House of Moto to recover: .
Click to expand...
Click to collapse

5.0 bricked my phone

Saturday evening I got a notification saying 5.0 lollipop was available for my s5 so I eagerly downloaded the update. During the update my phone froze and crashed (had this happen twice earlier in the day) and it rebooted to the update screen. Once the update finished installing the phone rebooted like normal and sat at the verizon screen for about 2 minutes before crashing again. This caused the phone to enter a boot loop that ended up making an open padlock symbol appear on the start screen. After this appeared it took me to a screen that said "System software not authorized by Verizon has been found on your phone". After getting this error I tried using Odin and Kies to reinstall 4.4 on my device. The install was successful but after the phone booted it was freeze and crash again leading to another boot loop and a "recovery booting" message in the top left screen. It now either boots back to the System software screen or loops until it hits the recovery menu. Is there any way to fix this or did Verizon brick my phone?
koerng said:
Saturday evening I got a notification saying 5.0 lollipop was available for my s5 so I eagerly downloaded the update. During the update my phone froze and crashed (had this happen twice earlier in the day) and it rebooted to the update screen. Once the update finished installing the phone rebooted like normal and sat at the verizon screen for about 2 minutes before crashing again. This caused the phone to enter a boot loop that ended up making an open padlock symbol appear on the start screen. After this appeared it took me to a screen that said "System software not authorized by Verizon has been found on your phone". After getting this error I tried using Odin and Kies to reinstall 4.4 on my device. The install was successful but after the phone booted it was freeze and crash again leading to another boot loop and a "recovery booting" message in the top left screen. It now either boots back to the System software screen or loops until it hits the recovery menu. Is there any way to fix this or did Verizon brick my phone?
Click to expand...
Click to collapse
Try doing a wipe and then factory reset from recovery mode.
Rapunzl said:
Try doing a wipe and then factory reset from recovery mode.
Click to expand...
Click to collapse
Still boots with the custom rom padlock and freezes on the verizon screen
Try pulling the battery. I've read where that's helped some people get it to boot.
newmanx4 said:
Try pulling the battery. I've read where that's helped some people get it to boot.
Click to expand...
Click to collapse
I've got to pull it when it freezes, I think the problem is that its reading it as a rooted rom even though its not
Same problem
koerng said:
Saturday evening I got a notification saying 5.0 lollipop was available for my s5 so I eagerly downloaded the update. During the update my phone froze and crashed (had this happen twice earlier in the day) and it rebooted to the update screen. Once the update finished installing the phone rebooted like normal and sat at the verizon screen for about 2 minutes before crashing again. This caused the phone to enter a boot loop that ended up making an open padlock symbol appear on the start screen. After this appeared it took me to a screen that said "System software not authorized by Verizon has been found on your phone". After getting this error I tried using Odin and Kies to reinstall 4.4 on my device. The install was successful but after the phone booted it was freeze and crash again leading to another boot loop and a "recovery booting" message in the top left screen. It now either boots back to the System software screen or loops until it hits the recovery menu. Is there any way to fix this or did Verizon brick my phone?
Click to expand...
Click to collapse
I am having the EXACT same issue. I need to something up and going. Any help here would be appreciated.
BryceRuss said:
I am having the EXACT same issue. I need to something up and going. Any help here would be appreciated.
Click to expand...
Click to collapse
Have you tried talking to verizon yet? I'm gonna take my phone down to the store tomorrow and see if theres anything they can do.
koerng said:
Have you tried talking to verizon yet? I'm gonna take my phone down to the store tomorrow and see if theres anything they can do.
Click to expand...
Click to collapse
Ok, so I am safe now. I was able to flash a stock NK2 Kernal.
Pull the battery on the phone. Hold down Vol. Down, Home, and Power and go to download mode. Plug in the phone, and open Odin. Flash the kernal.
Reboot and you should be ok. This just worked for me.
BryceRuss said:
Ok, so I am safe now. I was able to flash a stock NK2 Kernal.
Pull the battery on the phone. Hold down Vol. Down, Home, and Power and go to download mode. Plug in the phone, and open Odin. Flash the kernal.
Reboot and you should be ok. This just worked for me.
Click to expand...
Click to collapse
I tried flashing the kernel, it booted and I got an error that said "processing system isn't responding" and it crashed back to the verizozn software screen.
koerng said:
I tried flashing the kernel, it booted and I got an error that said "processing system isn't responding" and it crashed back to the verizozn software screen.
Click to expand...
Click to collapse
If Kies doesn't work, try Verizon Update Tool. It also has a repair tab and may help you get back to stock.
Rapunzl said:
If Kies doesn't work, try Verizon Update Tool. It also has a repair tab and may help you get back to stock.
Click to expand...
Click to collapse
The verizon tool won't even recognize my phone
koerng said:
The verizon tool won't even recognize my phone
Click to expand...
Click to collapse
Instead of flashing only the kernel, flash a stock, unrooted retail version of KK 4.4.4.
BryceRuss said:
Ok, so I am safe now. I was able to flash a stock NK2 Kernal.
Pull the battery on the phone. Hold down Vol. Down, Home, and Power and go to download mode. Plug in the phone, and open Odin. Flash the kernal.
Reboot and you should be ok. This just worked for me.
Click to expand...
Click to collapse
This worked for me as well, thanks! For anyone that wants to know, I used "NK2_Stock_Restore.tar.md5" specifically. You can get it from this thread labeled as "NK2 Stock Restore".

Categories

Resources