Related
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!!!
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".
I have a TMobile/MetroPCS GS4 model SGH-M919N that got stuck in a boot loop last week. I was finally able to find working firmware last night and used Odin to flash. Once it got to PASS my phone automatically rebooted with the blue recovery boot text in the top left, but then it just went back into a boot loop. I tried all other firmwares and none of them got to 100% so now I don't know what else I can do.
I have the same issue on a GT-i9505. I was using my phone this evening when it randomly rebooted and just keep rebooting until I removed my battery. After that, it was dead . Flashing stock firmwares like shooting a minigun and nothing works. Smells like a hard brick?
alesu69 said:
I have the same issue on a GT-i9505. I was using my phone this evening when it randomly rebooted and just keep rebooting until I removed my battery. After that, it was dead . Flashing stock firmwares like shooting a minigun and nothing works. Smells like a hard brick?
Click to expand...
Click to collapse
Have you tried replacing the battery? I figured I would try that but I havent gotten around to it yet
Not yet, i have no spare battery. Looks like when i plug the charger my phone just vibrates, like it's rebooting, and it's not showing anything. I found a similar issue here: http://forum.xda-developers.com/showthread.php?t=2532447
Looks like one guy did solve his problem.
*need to mention that by dead I mean it shows the "Samsung Galaxy S4 GT-I9505" logo and also shows "RECOVERY BOOTING", even though I didn't enter in recovery mode. Looks like now it doesn't shows anymore "RECOVERY BOOTING", but still, it doesn't boot. I was able to flash firmwares via odin and kies, but still no luck.
LE: It start booting by.. magic, i got to samsung boot logo, but that's all, crashed again.
After flash with Odin, immediately boot into recovery, perform a factory wipe, and reboot.
The problem is it doesn't boot into recovery.
LE: I managed to flash twrp via odin and boot into recovery, but i have an error:
"Unable to mount /data"
Any ideas?
LE2: Everything is useless, i managed to flash the rom, manage to boot into the rom, but then it will still reboot (which it did). Next step will be maybe to disassemble and clean all contacts.
alesu69 said:
The problem is it doesn't boot into recovery.
LE: I managed to flash twrp via odin and boot into recovery, but i have an error:
"Unable to mount /data"
Any ideas?
LE2: Everything is useless, i managed to flash the rom, manage to boot into the rom, but then it will still reboot (which it did). Next step will be maybe to disassemble and clean all contacts.
Click to expand...
Click to collapse
How did you manage to get into recovery?
harary said:
How did you manage to get into recovery?
Click to expand...
Click to collapse
Yes, but if I leave my phone in recovery (stock or custom), it just either freezes, either reboots, even though i don't do anything, just let it idle.
I can't manage to boot into the ROM 'cause eventually it will reboot. I couldn't finish the setup wizard.
OK so I don't know if this helps, but I managed to at least get past the "blue recovery boot" part. When the phone vibrated I let go of the power while still holding home + vol up, and I managed to get to the android guy with a blue progress bar below him. My phone shut off as the progress bar got 80-90% but now I know it's not impossible to start recovery.
Well, nothing works. After flashing pit file, an 4.4.2 odin prerooted image from here, cf auto root and then twrp, it will still randomly reboot. I manage to get past the boot logo into setup wizard, but phone just freezes after a couple of minutes, can't finish the setup wizard. Also, if i idle in twrp it will reboot sooner or later, tested already.I left my phone idling in twrp just to recharge my battery.
At least i have no more "unable to mount /data" errors.
I finally got it to work, all I had to do is keep flashing twrp and stock firmware back and forth. But it is just one problem after another with this thing, the problem now is every 5 minutes it will freeze and restart, also it tells me there is no sim even though it worked the first time i put it back in.
Operation Ivy said:
I finally got it to work, all I had to do is keep flashing twrp and stock firmware back and forth. But it is just one problem after another with this thing, the problem now is every 5 minutes it will freeze and restart, also it tells me there is no sim even though it worked the first time i put it back in.
Click to expand...
Click to collapse
What do you mean with back and forth?
harary said:
What do you mean with back and forth?
Click to expand...
Click to collapse
It means he flahsed and reflashed many times until he got lucky and it worked. That's what happened to me also. But i have the same issue, phone reboots or freezez after a couple of minutes, even though everything else is installed properly.
Dude, we have the same issue. Btw, is this happening to you too? Like, now and then when the phone freezes, that the screen is turning to a bright yellowish green?
I know a friend who repairs phone hardwares for a living, i gave it to him, i'll let you know how this went.
alesu69 said:
It means he flahsed and reflashed many times until he got lucky and it worked. That's what happened to me also. But i have the same issue, phone reboots or freezez after a couple of minutes, even though everything else is installed properly.
Dude, we have the same issue. Btw, is this happening to you too? Like, now and then when the phone freezes, that the screen is turning to a bright yellowish green?
I know a friend which repairs phone hardwares for a living, i gave it to him, i'll let you know how this went.
Click to expand...
Click to collapse
I got several times into Recovery Mode now, flashed several ROMs. I had no issues with freezing, especially not in TWRP Recovery Mode. But sometimes if i am trying to go into Recovery Mode or i just want to start ROMs, the screen turns into yellow behind the Samsung logo. If i dont take out the battery this wents into a complete white, but nothing happens.
Yes please tell if you got some news..
guys its not hard bricked its a problem wiht your power button
my friend had the same issue and then i killed the battery by letting it keeep bootlooping
then plugged it in and let it charge to around 10% and booted it
just try to press the power button slowly
Joashrox said:
guys its not hard bricked its a problem wiht your power button
my friend had the same issue and then i killed the battery by letting it keeep bootlooping
then plugged it in and let it charge to around 10% and booted it
just try to press the power button slowly
Click to expand...
Click to collapse
But it is sure that the power button is working because i get this blue "recovery booting". Or am i wrong?
So.... bad news, the guy whom i gave the phone to said that it's a short on the motherboard and there's nothing he can't do other than changing the motherboard. If you guys found another solution and that guy is mistaking, let me know.
alesu69 said:
So.... bad news, the guy whom i gave the phone to said that it's a short on the motherboard and there's nothing he can't do other than changing the motherboard. If you guys found another solution and that guy is mistaking, let me know.
Click to expand...
Click to collapse
Replace power button to new one. I have the same problems with s3 and this works. Try it.
Sent from my GT-I9300 using XDA-Developers mobile app
My phone is dead, it's not even charging anymore. The guy whom I give it to said it's a short on the motherboard. You guys managed to solve something with your phones? Or still a dead end?
alesu69 said:
My phone is dead, it's not even charging anymore. The guy whom I give it to said it's a short on the motherboard. You guys managed to solve something with your phones? Or still a dead end?
Click to expand...
Click to collapse
If You can't charge phone... Yup, motherboard is died. If You plug the charger and see something this have to be button but if You plug charger and don't see anything this is motherboard.
A couple of days ago my Nexus 6P suddenly rebooted while in normal use. Now it is stuck in a bootloop ("Please lock the bootloader"-screen -> White "Google" logo -> brief black screen -> repeat).
The device is unlocked, and I am able to enter fastboot mode. Flashing partitions is possible, but I am NOT able to enter recovery. When selecting "Recovery mode" from the menu, the device just goes into the same bootloop. I tried to flash and boot different recovery images (Stock, CM, TWRP) without success. The bootloader and fastboot appear to working normally otherwise.
Does anyone have any idea what is going on?
Thanks
This just happened to me yesterday.. I've tried flashing different recoveries too but no dice.. I reflashed factory image and still the same bootloop..
This happened to me too like a month ago. I was just checking facebook and stuff, when suddenly it rebooted. Didnt think about it at first as I know it reboots some times, but it just got to the "please lock your bootloader" - message and then the white google-logo. Was able to access bootloader but not recovery. So i flashed stock to see if it helped, but it didnt. Got in contact with the store that sold me the phone, and they said it had to be repaired. Obviously I never told them that it was unlocked, never mentioned I saw the "please lock" - message, only the white google logo. So as I had already flashed stock I just locked the bootloader and returned it to the store and a week later I got it back. They had replaced the circuit board so yeah, nothing you can fix by flashing.
So get an RMA on it, or you will have a very pretty and expensive brick
Hope this helps you
Jaggenite said:
This happened to me too like a month ago. I was just checking facebook and stuff, when suddenly it rebooted. Didnt think about it at first as I know it reboots some times, but it just got to the "please lock your bootloader" - message and then the white google-logo. Was able to access bootloader but not recovery. So i flashed stock to see if it helped, but it didnt. Got in contact with the store that sold me the phone, and they said it had to be repaired. Obviously I never told them that it was unlocked, never mentioned I saw the "please lock" - message, only the white google logo. So as I had already flashed stock I just locked the bootloader and returned it to the store and a week later I got it back. They had replaced the circuit board so yeah, nothing you can fix by flashing.
So get an RMA on it, or you will have a very pretty and expensive brick
Hope this helps you
Click to expand...
Click to collapse
Oh my.. I was hoping against hope nobody would say this..
Thanks mate!
So I think my Nexus 6P is hard bricked, but I just want to be sure before I issue an RMA.
I was on a plane flying over the Pyrenees and opened the camera to take a picture. The phone froze and started rebooting, which I found strange really strange as it never happened before. Since then, it wasn't able to boot again. The phone is completely stock, running 7.0, apart from the unlocked bootloader that I had unlocked the day I bought it (March/April this year). The phone shows the unlocked bootloader warning, goes to the white Google logo with the padlock below, and then goes back to the unlocked bootloader.
From here I can Power + Vol down and get to bootloader, which I thought would leave me to recover the phone somehow. I know my way around nexus devices so the first thing I tried was scrolling in the bootloader menu and boot into stock recovery. No luck, unlocked bootloader warning, white Google logo and loop. Tried "Factory" in the menu and the same thing happens.
So then I've gained access to a computer and tried downloading a twrp recovery and boot into it. Ran fastboot boot twrp.img, the phone tries to boot again, and the same thing happens. Boot loop. After that, I've downloaded the latest stock Google images and I've run a different set of things, all with no luck. Booting directly from fastboot into stock recovery doesn't work. Flashing stock recovery and trying to enter stock recovery via bootloader menu doesn't work. I've erased and flashed bootloader, radio, and all other partitions (system, boot, recovery, vendor and cache), without any luck. The fastboot commands return "OKAY" but it seems like it's doing nothing.
I am out of ideas, I always thought I would be able to recover a Nexus phone as long as I could reach bootloader mode, but I guess I'm wrong. Should I RMA, or is there anything else I should try?
Thank you.
You say you "Ran fastboot boot twrp.img." Try to do fastboot flash recovery twrp.img from fastboot and see if you can get twrp working. Then try to flash a ROM
vladniko said:
You say you "Ran fastboot boot twrp.img." Try to do fastboot flash recovery twrp.img from fastboot and see if you can get twrp working. Then try to flash a ROM
Click to expand...
Click to collapse
Done both, actually. Tried to boot directly from a fastboot command and then tried flashing the actual recovery image to the phone. No luck in both. Never able to get into twrp.
I had the same thing happening to me. I was also using stock 7.0 with an unlocked bootloader. My screen froze during webbrowsing and had to restart the phone. Once booting up, it never came past the Google logo. Getting into recovery didn't work either, just started looping again. Tried to flash twrp, got in there after many tries. Tried flashing all kind of android versions but nothing helped. After that I decided to just use my warrenty and send the phone to the store. They replaced the motherboard and are now sending it back.
hubhib said:
I had the same thing happening to me. I was also using stock 7.0 with an unlocked bootloader. My screen froze during webbrowsing and had to restart the phone. Once booting up, it never came past the Google logo. Getting into recovery didn't work either, just started looping again. Tried to flash twrp, got in there after many tries. Tried flashing all kind of android versions but nothing helped. After that I decided to just use my warrenty and send the phone to the store. They replaced the motherboard and are now sending it back.
Click to expand...
Click to collapse
Yep, I gave up already. Tried all different sort of thing, and was never able to get into any kind of recovery, let alone Android itself.
Called Google support yesterday evening, a replacement is on its way already.
eddie_gordo said:
Yep, I gave up already. Tried all different sort of thing, and was never able to get into any kind of recovery, let alone Android itself.
Called Google support yesterday evening, a replacement is on its way already.
Click to expand...
Click to collapse
Needed the RMA anyways. If you had an unlocked bootloader and formatted each partition and then flashed each partition with the corresponding image file from the latest factory image, it was shot. It happens from time to time. Happened to mine as well. 2 or 3 days after I finally got it (pre ordered on launch) I rebooted the phone at some point 2 or 3 days later and it just never turned back on. 100% bone stock. Not even an unlocked bootloader. Nothing would happen when I plugged it into a PC, left it on AC power for hours and hours and still nothing. Holding power 10-15 seconds, nada. RMA'd and luckily this one's been perfect ever since. Good luck with the new device!