Okay so I just had this problem and I don't want anyone getting stuck on it and not knowing how to fix it. I decided to write a quick guide for everyone.
Steps
Boot phone into "Boot Android (No BP)" by holding the Volume Down key and the Power button.
Press the Volume Down button until you see "Boot Android (No BP)"
Press the Volume Up button and wait.
Hold the Power button once its on and press Airplane Mode.
Reboot the device.
Skip the Error Message about not being able to activate. (Keep Airplane Mode on)
Open Sprint Zone app.
Activate through Sprint Zone. (When prompted to exit Airplane Mode, say yes.)
Thanks: thaisport_sf & w0lf215
I had to do that exact same thing a few months ago, twice... I'm glad to see someone took the time to document this... Now I know where to look when I do it again...
ZeroManArmy said:
Okay so I just had this problem and I don't want anyone getting stuck on it and not knowing how to fix it. I decided to write a quick guide for everyone.
Steps
Boot phone into "Boot Android (No BP)" by holding the Volume Down key and the Power button.
Press the Volume Down button until you see "Boot Android (No BP)"
Press the Volume Up button and wait.
Hold the Power button once its on and press Airplane Mode.
Reboot the device.
Skip the Error Message about not being able to activate. (Keep Airplane Mode on)
Open Sprint Zone app.
Activate through Sprint Zone. (When prompted to exit Airplane Mode, say yes.)
Thanks: thaisport_sf & w0lf215
Click to expand...
Click to collapse
This wont work for me as I am using an International GSM. Dont have access to sprint. I have to delete / rename SprintOMADM* in /system/app location..
androiderb89 said:
This wont work for me as I am using an International GSM. Dont have access to sprint. I have to delete / rename SprintOMADM* in /system/app location..
Click to expand...
Click to collapse
Do you have a way to fix it so I can add it?
Huge thanks! Conveniently enough, I saw this right as it happened to me. lol
I get stuck on "Contacting Network" during a PRL/Profile update, but I am able to exit by clicking on an app(IMO beta) on the notifications pull down, and pressing home. I am activated, just want to update the data profiles.
Plancy, press ##786# on your phone. Whats your HW version?
Accidental formatting of Internal SD through CWM
I have run into this problem before where the boot logo is erased saying that it will "cold-boot" into Linux. The only problem is that when I SBF to get back to stock, the photon wouldnt update the PRL or the data profile. The only remedy I have found is that I need to restore the PDS partition from a nandroid backup after unlocking again. Doing so rendered the green hands-free activation screen. Hope that helps anyone.
hoslayer13 said:
I have run into this problem before where the boot logo is erased saying that it will "cold-boot" into Linux. The only problem is that when I SBF to get back to stock, the photon wouldnt update the PRL or the data profile. The only remedy I have found is that I need to restore the PDS partition from a nandroid backup after unlocking again. Doing so rendered the green hands-free activation screen. Hope that helps anyone.
Click to expand...
Click to collapse
I don't have a nandroid backup, how can I restore the PDS partition? I get stuck on "Contacting Network" during PRL or Data Profile Update on any ROM All 198_7SBF'd Locked/Unlocked Rooted/Unrooted
This is a fix from the Atrix forum that might be able to help. I haven't tried it but the OP mentioned that method 1 was a universal fix, although not sure if meant as a multi-device fix. Best of luck, worst case scenario is having to shell out 35$ for a replacement
hoslayer13 said:
This is a fix from the Atrix forum that might be able to help. I haven't tried it but the OP mentioned that method 1 was a universal fix, although not sure if meant as a multi-device fix. Best of luck, worst case scenario is having to shell out 35$ for a replacement
Click to expand...
Click to collapse
Thanks , but I dont really want to chance it unless a someone can verify that it's universal.
Plancy said:
Thanks , but I dont really want to chance it unless a someone can verify that it's universal.
Click to expand...
Click to collapse
No problem. Have you checked what your HW version was by chance to see if it was the PDS that borked? Normally it would say P30A, or at least that's what it shows on both Photons that I have.
Edit: The one I messed with said it was unavailable.
hoslayer13 said:
No problem. Have you checked what your HW version was by chance to see if it was the PDS that borked? Normally it would say P30A, or at least that's what it shows on both Photons that I have.
Edit: The one I messed with said it was unavailable.
Click to expand...
Click to collapse
Webtop version is unavailable, can't find "Hardware".
I'm running ROCK2.4
ZeroManArmy said:
Okay so I just had this problem and I don't want anyone getting stuck on it and not knowing how to fix it. I decided to write a quick guide for everyone.
Steps
Boot phone into "Boot Android (No BP)" by holding the Volume Down key and the Power button.
Press the Volume Down button until you see "Boot Android (No BP)"
Press the Volume Up button and wait.
Hold the Power button once its on and press Airplane Mode.
Reboot the device.
Skip the Error Message about not being able to activate. (Keep Airplane Mode on)
Open Sprint Zone app.
Activate through Sprint Zone. (When prompted to exit Airplane Mode, say yes.)
Thanks: thaisport_sf & w0lf215
Click to expand...
Click to collapse
If you're not with Sprint, then you just follow the above AND also delete these files:
SprintOMADMConnMOPlugin.apk
SprintOMADMConnMoPlugin.odex
They're found under System/app and you need Root Explorer to delete the file(s). At the top, you tap on "Mount..." and then you'll be allowed delete these files. To delete, simply long press the files and choose delete. Some might only find one of the above files (if they have a custom ROM).
Someone showed this trick to me, so... I can only take credit for being the messenger
Hmm doesn't look like anyone knows how to help I really want to update.
coolqf said:
If you're not with Sprint, then you just follow the above AND also delete these files:
SprintOMADMConnMOPlugin.apk
SprintOMADMConnMoPlugin.odex
They're found under System/app and you need Root Explorer to delete the file(s). At the top, you tap on "Mount..." and then you'll be allowed delete these files. To delete, simply long press the files and choose delete. Some might only find one of the above files (if they have a custom ROM).
Someone showed this trick to me, so... I can only take credit for being the messenger
Click to expand...
Click to collapse
When do they delete the files? Which step?
Gonna have to ask around on how to fix the PDS partition or restore it.
ZeroManArmy said:
Okay so I just had this problem and I don't want anyone getting stuck on it and not knowing how to fix it. I decided to write a quick guide for everyone.
Steps
Boot phone into "Boot Android (No BP)" by holding the Volume Down key and the Power button.
Press the Volume Down button until you see "Boot Android (No BP)"
Press the Volume Up button and wait.
Hold the Power button once its on and press Airplane Mode.
Reboot the device.
Skip the Error Message about not being able to activate. (Keep Airplane Mode on)
Open Sprint Zone app.
Activate through Sprint Zone. (When prompted to exit Airplane Mode, say yes.)
Thanks: thaisport_sf & w0lf215
Click to expand...
Click to collapse
THANK YOU VER MUCH, you save me from calling Sprint. thank you
The first chance they get. They have to be removed before they reboot the phone, or when they boot normally they will get the activation message. This replaces your activation step for people whom do not have sprint.
Sent from my Photon
ZeroManArmy said:
Okay so I just had this problem and I don't want anyone getting stuck on it and not knowing how to fix it. I decided to write a quick guide for everyone.
Steps
Boot phone into "Boot Android (No BP)" by holding the Volume Down key and the Power button.
Press the Volume Down button until you see "Boot Android (No BP)"
Press the Volume Up button and wait.
Hold the Power button once its on and press Airplane Mode.
Reboot the device.
Skip the Error Message about not being able to activate. (Keep Airplane Mode on)
Open Sprint Zone app.
Activate through Sprint Zone. (When prompted to exit Airplane Mode, say yes.)
Thanks: thaisport_sf & w0lf215
Click to expand...
Click to collapse
THANKS soooooooooooooooooooooooooo many many much bro!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!111 i love you man hahahaa... u saved me from paying $119 thanks
Related
I cant get my phone to go into recivery mode. From searching a few other threads, it seems my option is to rerurn the phone as defective. Please tell me Thats not true!! Is there no other way?? Thanks
download ROM Manager from Market and reboot into recovery that way
I looked that up in the market. The phone has to be rooted first. I cant root it because I cant get into recovery.
If your after a root method...read and follow this thread...
http://forum.xda-developers.com/showthread.php?t=739300&highlight=root
by far the simplest way...
GreggoryD502 said:
I cant get my phone to go into recivery mode. From searching a few other threads, it seems my option is to rerurn the phone as defective. Please tell me Thats not true!! Is there no other way?? Thanks
Click to expand...
Click to collapse
I dunno if you have tried this, but try doing what I do, follow the instructions exactly, and it may work for you, let me know if it does.
1) START with your phone off, no usb cables attached.
2) Press volume down AND volume up at same time, keep them pressed in the entire time, do NOT let go. I prefer to hold my phone in landscape, this gives me better control with my fingers.
3) WHILE holding down volume up and volume down, press and hold power button, DO NOT LET GO OF ANYTHING. You should be holding down volume up, volume down, and power, DON'T LET GO! HOLD ON... and proceed to next steps, dont let go!
4) PHONE will start, you will see the white Vibrant logo. STILL DON'T LET GO, volume down, volume up, and power all pressed.
5) White Vibrant logo disappears, still dont let go!
6) White Vibrant logo re-appears again for the second time. When the white vibrant logo appears the second time, let go of the power button, but keep holding down volume down and volume up.
7) Phone begins to enter recovery mode, you can let go finally.
8) To exit, select "reboot system now" and use your power button to select, you will exit recovery mode.
SamsungVibrant, my phone is hardware locked from the factory. I tried your method several times with no success. I took the phone back to te store and exchanged it. Havent tried it yet, kinda nervous to.....
masterotaku said:
If your after a root method...read and follow this thread...
http://forum.xda-developers.com/showthread.php?t=739300&highlight=root
by far the simplest way...
Click to expand...
Click to collapse
+1, I have a hardware locked vibrant too and the 1-click root worked flawlessly, its the only way guaranteed to work.
PS: you might have to copy the update.zip file manually into the phone cause it failed to copy it automatically for me
You can also root by downloading the Android SDK and using it to boot into recovery. That's how I rooted.
Sent from my SGH-T959 using XDA App
That way makes me kinda nervous. I know this is a stupid question, but how do you know if your pc is a 32 or 64 bit system. You can see why im nervous now...
Go to control panel. Then go into system and maintenance. Then pick system. You should see the system type there.
ADB is easy. If you haven't already, do a search on ADB for dummies in the G1 forum.
XDA Mobile
GreggoryD502 said:
That way makes me kinda nervous. I know this is a stupid question, but how do you know if your pc is a 32 or 64 bit system. You can see why im nervous now...
Click to expand...
Click to collapse
This is one the things that should tell you: you shouldn't be rooting your phone, young padwan.
-bZj
You are probably right. But Im going to try after I do a little more research.
(This issue is RESOLVED, thanks for the help.)
Hello,
I had a few issues with my last Motorola Photon 4G, so I returned it, and got a new one.
Like an idiot, I rooted my phone, installed CWM and did a full restore.
I now have lost 4G Connectivity. How do I get 4G back? I know that this has something to do with the RSA Keys, if I didn't do a backup, how do I restore the RSA Keys?
You didn't unlock the bootloader right? And you did a full restore from CWM? To what? What you had saved on your SD card from your other phone?
xTMFxOffshore said:
You didn't unlock the bootloader right? And you did a full restore from CWM? To what? What you had saved on your SD card from your other phone?
Click to expand...
Click to collapse
Didn't unlock the bootloader, fresh out of the box, went home, rooted the new phone, restored a backup via CWM from my old phone. Dumb thing to do, now my 4G won't work. I forgot all about RSA keys and everything. So basically, I rewrote my RSA keys, and can't restore them since I didn't make a backup. Anyone know what I should do?
Hmmmm.....try to pull your SD card and reformat your phone then do a factory restore and see if that takes you back to stock. Then try your 4G?
I fixed it with a simple factory reset via the following method, (in case anyone ever runs into a similar problem),
"Power off the phone, press and hold volume down button, press power button
Screen will come up with "Fastboot", press Vol down key to cycle through choices until you get "Android Recovery", then press Vol up key
Wait for the "triangle ! / Android" screen then go on to step 4
Press both Vol up and Vol down key simultaneously. A menu will come up
Use the Vol Down key to select "wipe partition" by pressing the power button.
Once that is done continue to step 7.
Tap on Vol down key until "wipe data/factory reset" is highlighted, and tap Power key. Another Confirmation screen will come. Tap on Vol down key until coming to Yes and tap Power key
After userdata is cleared, the "reboot system now" option will be highlighted by Default. Tap Power key
Phone will reboot to initial setup screen."
I have 4G back, now I will root, install CWM, and restore /Data, or go by RSA keys, backup and restore.
So more of less the route I was telling you to go. Glad you got it figured out. And that everything works for you now again. :]
xTMFxOffshore said:
So more of less the route I was telling you to go. Glad you got it figured out. And that everything works for you now again. :]
Click to expand...
Click to collapse
You are the best xTMFxOffshore, I notice that you have helped me a lot lately. When I need help, you have been here with the answers! You are the best!
(Sorry if I ever become too needy, and ask for your help by PM too much, please kindly let me know. I have been running into lots of issues lately, and you, Shabbypenguin, and Lokifish Marz, are, what I call... my "XDA Big Guns," so I call you guys in when I'm in deep oil.)
I am just kinda bumbling my way through. Shabby and Loki are legit Devs. I just read a lot and learn from **** other people post and do. And things I screw up along the way. But no worries. This community SHOULD be about helping each other out.
I'm not sure why, but it'll show the "Samsung Galaxy S2" boot screen then it'll just go black. When I hold "down" and power at the same time, it'll ask me to "download a custom OS" hit "up" or hit "down" to restart. Yes, it's rooted. But it's worked fine for about 3 weeks now since root.
Any help would be appreciated.
amaffey said:
I'm not sure why, but it'll show the "Samsung Galaxy S2" boot screen then it'll just go black. When I hold "down" and power at the same time, it'll ask me to "download a custom OS" hit "up" or hit "down" to restart. Yes, it's rooted. But it's worked fine for about 3 weeks now since root.
Any help would be appreciated.
Click to expand...
Click to collapse
Have you installed a custom kernel?
In the case you are trying to boot into recovery, remove the phone from charger and press all: vol up, vol down and power while bootup to boot into recovery
I've actually reset my device now using the factory reset. And it still does the same thing. Not sure what else to do at this point?
And no, stock everything. Stock rooted.
People have had this problem before. Keep trying random passwords, and sooner or later it'll wipe your data. If that doesn't work, flash Entopy's "Back to Stock" package on XDA.
jcracken said:
People have had this problem before. Keep trying random passwords, and sooner or later it'll wipe your data. If that doesn't work, flash Entopy's "Back to Stock" package on XDA.
Click to expand...
Click to collapse
I'll try this once I get home. Thank you.
amaffey said:
I'm not sure why, but it'll show the "Samsung Galaxy S2" boot screen then it'll just go black. When I hold "down" and power at the same time, it'll ask me to "download a custom OS" hit "up" or hit "down" to restart. Yes, it's rooted. But it's worked fine for about 3 weeks now since root.
Any help would be appreciated.
Click to expand...
Click to collapse
Is your phone an AT&T Galaxy S II I777? You say: "When I hold "down" and power at the same time, it'll ask me to "download a custom OS" hit "up" or hit "down" to restart." On the I777, holding vol- and power at the same time is the same as turning the phone on with the power button. I've never seen anything like you describe.
You havn't said you were getting a security password prompt, so I don't know why the suggestion to keep entering a password. Are you getting a security password prompt when you try to enter recovery?
To troubleshoot the problem, we need to determine if there was any change or "event" that would have triggered the problem.
creepyncrawly said:
Is your phone an AT&T Galaxy S II I777? You say: "When I hold "down" and power at the same time, it'll ask me to "download a custom OS" hit "up" or hit "down" to restart." On the I777, holding vol- and power at the same time is the same as turning the phone on with the power button. I've never seen anything like you describe.
You havn't said you were getting a security password prompt, so I don't know why the suggestion to keep entering a password. Are you getting a security password prompt when you try to enter recovery?
To troubleshoot the problem, we need to determine if there was any change or "event" that would have triggered the problem.
Click to expand...
Click to collapse
Yes, there was a build.prop edit. I reset my phone after the edit and it won't power up past the "Samsung" boot screen. I got passed the password prompt and I was able to successfully factory reset my phone and it still doesn't boot past the "Samsung" boot screen.
amaffey said:
Yes, there was a build.prop edit. I reset my phone after the edit and it won't power up past the "Samsung" boot screen. I got passed the password prompt and I was able to successfully factory reset my phone and it still doesn't boot past the "Samsung" boot screen.
Click to expand...
Click to collapse
It's possible a build.prop edit could cause boot failure. Can you connect to the phone through ADB? If you can do that, you might be able to reactivate the build.prop.bak file that was probably created when you did the edit.
If you can't get into the file system, then probably the best thing is to flash stock. If it was my phone, I would probably flash the stock one-click downloader in the "Return you phone to the Store or for Warranty Replacement" guide, and then re-root with DooMLords zergrush method from the other guide. Links in my signature.
Yeah, I'm downloading the file now to attempt this. Thank you.
Admin please lock this thread.
Thank you everyone to helped. My phone is UP AND RUNNING!
Thanks guys! You just saved me hundreds of dollars..
amaffey said:
I've actually reset my device now using the factory reset. And it still does the same thing. Not sure what else to do at this point?
Click to expand...
Click to collapse
Factory reset wont help you. Go to recovrry and re flash rom you got om that phone. Should take care of it.
Send from my SG2-i777 using XDA Premium App
Got the phone with rebooting problem: it got the rebooting after updated. The device restarted during Android app optimization stage so I just unblock with the AT&T stock file (pda-odin-att-stock.tar) after that the phone can boot up fine the problem still. It works but continuing reboot every 2 minutes. I tried to clear the cache, test redbend fota... but nothing works
Anyone has idea?
abbuyacc said:
Got the phone with rebooting problem: it got the rebooting after updated. The device restarted during Android app optimization stage so I just unblock with the AT&T stock file (pda-odin-att-stock.tar) after that the phone can boot up fine the problem still. It works but continuing reboot every 2 minutes. I tried to clear the cache, test redbend fota... but nothing works
Anyone has idea?
Click to expand...
Click to collapse
your English is a little rough my friend
did you get the phone with reboot issue?
or
it started rebooting after an update?
what kind of update?
what rom are you trying to run?
and I don't understand "unblock with the ATT stock file " ?????
also what is "test redbend fota" ???
you need to be a little clearer with information please
captemo said:
your English is a little rough my friend
did you get the phone with reboot issue?
or
it started rebooting after an update?
what kind of update?
what rom are you trying to run?
and I don't understand "unblock with the ATT stock file " ?????
also what is "test redbend fota" ???
you need to be a little clearer with information please
Click to expand...
Click to collapse
First of all sorry about my English. I wish I can do better.
I got the phone with the rebooting and base on the owner of the phone he said it started rebooting after an update.
Not sure what was of update to but the phone I got always rebooting during Android app optimization stage ( when it updating about 90 files or so) but it got reboot when updating to the file of 57th (So it was not actually working)
I watched and followed the youtube (how to unblock/unbrick galaxy i717) which it used the pda-odin-att-stock.tar file with the ODIN3 V1.85 (I guess that original ROM of AT&T (android version 2.3)
After successful unblock/unbrick the phone the phone actual worked but the problem still. It works but only 2 minutes and the phone reboots.
2/ test redbend fota is one the options you can choose after hard booting the phone using both up - down keys and power key (other options are to clear the cache, or wipe the data..)
That actually happened to me while testing out Bean Stalk(which btw AWESOME ROM). It would do a Random Reboot and continuously do that every 2 minutes or so. The way I fixed it was by doing the following steps:
1) Power off your phone. If unable to power off, remove and reinsert the battery.
2 )Press and hold between both Volume keys and the Power key at the same time until the phone vibrates, then release ONLY the Power key.
3)Continue holding the Volume keys until Samsung appears on the screen. Then release both volume keys.
The recovery menu will display.
4) Press Volume down to move to option 3, Wipe data/factory reset, and then press the Home key to accept.
5) Use Volume Up and Volume Down buttons to navigate in the menu and select Yes- Delete all user data.
6)Navigate to highlight OK and press the Home key to select.
7) Select Reboot system now.
PLEASE UNDERSTAND THAT THIS WILL DELETE EVERYTHING INSIDE YOUR SD CARD AS WELL! SO DO A BACKUP BEFORE ERASING EVERYTHING!
hafridi said:
That actually happened to me while testing out Bean Stalk(which btw AWESOME ROM). It would do a Random Reboot and continuously do that every 2 minutes or so. The way I fixed it was by doing the following steps:
1) Power off your phone. If unable to power off, remove and reinsert the battery.
2 )Press and hold between both Volume keys and the Power key at the same time until the phone vibrates, then release ONLY the Power key.
3)Continue holding the Volume keys until Samsung appears on the screen. Then release both volume keys.
The recovery menu will display.
4) Press Volume down to move to option 3, Wipe data/factory reset, and then press the Home key to accept.
5) Use Volume Up and Volume Down buttons to navigate in the menu and select Yes- Delete all user data.
6)Navigate to highlight OK and press the Home key to select.
7) Select Reboot system now.
PLEASE UNDERSTAND THAT THIS WILL DELETE EVERYTHING INSIDE YOUR SD CARD AS WELL! SO DO A BACKUP BEFORE ERASING EVERYTHING!
Click to expand...
Click to collapse
I have done it already and it didn't works. I tried to clear the cache also and other options too but none of them worked.
abbuyacc said:
I have done it already and it didn't works. I tried to clear the cache also and other options too but none of them worked.
Click to expand...
Click to collapse
Could it be a battery issue? I mean if its not software, it might be hardware. Please check if the battery is fine? If you could elaborate the steps you took or the update process you followed, that would be great.
Don't worry we will definitely figure this out, i know how sad it can be when you are without your phone.
hafridi said:
Could it be a battery issue? I mean if its not software, it might be hardware. Please check if the battery is fine? If you could elaborate the steps you took or the update process you followed, that would be great.
Don't worry we will definitely figure this out, i know how sad it can be when you are without your phone.
Click to expand...
Click to collapse
No. Surely it is not about the battery. Battery is full and hold the charge pretty well. As I mentioned I was re-installed the original ROM of the phone and there was nothing much to say about this procedure. After reinstalled the original rom the phone works but the problems is still same (rebooting after 2 minutes), before the the phone didn't work and just was in the updating stage but I guess the time of the updating file was also about 2 minutes.
I believe this is about the software than the hardware issue. I am thinking that I may want to install the newest ROM to see it will work or not but I am in the middle of some works right now and have no time for it. So I am just wait to see if there is anyone had similar issue and follow their instruction. Thank you you all.
I am sure you either have hardware issue or in most circumstances it is a user issue.
Is there any possibility you have not read everything or something you are not understanding?
Those of us responding do so because our methods are tried and true. Nobody else is having this issue.
I just ask is it possible?
Have you confidently tried all suggestions with no shortcuts? Even the smallest deviation can lead to the biggest problems
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Here is a suggestion:
Please go to stock rom. After Odin restarts the phone...do not touch. Let the phone sit there for a little bit. Then if it restarts u might need to format your internal sd card after formatting system, data, cache and then install rom.
I had to flash it
hafridi said:
That actually happened to me while testing out Bean Stalk(which btw AWESOME ROM). It would do a Random Reboot and continuously do that every 2 minutes or so. The way I fixed it was by doing the following steps:
1) Power off your phone. If unable to power off, remove and reinsert the battery.
2 )Press and hold between both Volume keys and the Power key at the same time until the phone vibrates, then release ONLY the Power key.
3)Continue holding the Volume keys until Samsung appears on the screen. Then release both volume keys.
The recovery menu will display.
4) Press Volume down to move to option 3, Wipe data/factory reset, and then press the Home key to accept.
5) Use Volume Up and Volume Down buttons to navigate in the menu and select Yes- Delete all user data.
6)Navigate to highlight OK and press the Home key to select.
7) Select Reboot system now.
PLEASE UNDERSTAND THAT THIS WILL DELETE EVERYTHING INSIDE YOUR SD CARD AS WELL! SO DO A BACKUP BEFORE ERASING EVERYTHING!
Click to expand...
Click to collapse
factory reset did not help me with this...I ended up having to flash CM 10.1. Its the most stable custom I have used on this phone yet....
Hello All,
I have a completely stock (Not rooted, and bootloader is locked) Nexus 9 (wifi) that will no longer boot after trying to update to the latest security patch (MOB30G).
I received the notification that there was an update available for my Nexus 9 this weekend. It was functioning just fine, so I chose to download an install the update.
I let it do its thing, and some time during the process something went wrong. I came back to see the little android picture with red "!". There were no words or messages with the error picture.
When I rebooted, There was a momentary message that stated that, "Device is corrupt and cannot be trusted..." and "...press the power button to pause boot".
It then goes back to the little android picture with the red exclamation mark and says "No Command".
I am at a total loss at what to do. It was completely stock, never rooted or anything else and I was applying a factory update?
Please help!
-Jason
@Jsunn Try side-loading the OTA update again from recovery.
Instructions can be found here.
If that doesn't work, try side-loading the Android N OTA instead.
I just had to deal with this after the May OTA. My device was locked and ADB was not enabled but I was able to sideload the dev preview of Android N.
I used the info at this link: Search "Reset your Nexus device to factory settings"
Specifically these steps:
Option 2: Reset device in Recovery mode
If you can't open the Settings app because of device issues, you can use Recovery mode to factory data reset ("format") your device.
Tip: If your device becomes unresponsive at any point, you can restart it by holding down the Power button for several seconds.
After following all the Before you start steps above:
If your device is on, turn it off.
Press & hold the Volume down button. While holding Volume down, press & hold the Power button until the phone turns on. You'll see the word "Start" with an arrow around it.
Press the Volume down button until you highlight "Recovery mode."
Press the Power button to start recovery mode. You'll see an image of an Android robot with a red exclamation mark (you may also see "No command").
Press & hold the Power button. While holding Power, press the Volume up button once. Then release the Power button.
Press the Volume down button until you highlight "Wipe data/factory reset." Then press the Power button.
Press the Volume down button until you highlight "Yes" (or "Yes - delete all user data"). Then press the Power button to select it.
After the reset is complete, press the Power button to select "Reboot system now."
When you're done, restore your data.
My biggest issue was not realizing the second menu was available. After getting "No Command" the power and vol up buttons are what get you to where you can use adb to sideload even if you never unlocked your device. This might work with a normal marshmallow OTA (Search for "Factory Images for Nexus Devices") but I used the N preview 2 which can be found by searching for "volantis-npc91k"
This had me fuming for a few days... No way I was sending a nexus device back and paying shipping for bricking after a stock update.
NOTE: Sorry I had to remove the direct links. My profile doesn't have enough posts yet. Really dumb, but I get it. Hope this helps.
Thanks for your help. I will try it this week.
Pretty bummed about this, I didn't have a lot of stuff on there but don't like having to deal with this.
Do you know what could have caused it?
-J
Had same issu with May update and applied the N preview OTA (that's the only thing you can do on a locked bootloader).
Once booted in N preview, I've enrolled the device in the beta program, then retired. Few seconds after, I've received the downgrade OTA, and no more issue.
Before doing anything else, I've unlocked the bootloader so at least it if occurs again with the MOB30G, I will have some more access !
Jsunn said:
Thanks for your help. I will try it this week.
Pretty bummed about this, I didn't have a lot of stuff on there but don't like having to deal with this.
Do you know what could have caused it?
-J
Click to expand...
Click to collapse
Nobody knows what causes this, maybe a corrupted download of the OTA.
It happens to people's devices nearly every month when an OTA is available.
Try sideloading the failed OTA (linked above) again first before taking the Android N route.
Google Now provide full block level OTA images, so they can be sideloaded onto your device no matter what version your on.
https://developers.google.com/android/nexus/ota
Use the latest OTA image from that link, instead of sideloading the patching OTA zips.
I can't seem to sideload the package. My computer doesn't detect that a fastboot device in connected.
I am trying a factory reset now? If that doesn't work, I guess I can try the N preview? Other suggestions?
Thanks,
Jason
@Jsunn Make sure you have the correct drivers on your computer, Nexus Root Toolkit has a driver installation guide.
Check that your in fastboot mode and your device should show up in device manager as
Android Device - Android Bootloader Interface
@corkiejp, Thank you for the tip. That was it and I now am back up and running. I am back on the May 1 Security update. I'd really like to avoid having to do this again in the future. Do you have any suggestions? i.e. should I always sideload the update? Customer ROM etc?
Thanks,
-J
@Jsunn What was the trick? Reinstalling drivers, i Guess.
Remember to Enable OEM unlocking in developer options.
And if you have already factory reset? It might be a good time to Unlock Your bootloader with "fastboot oem unlock".
So if anything goes wrong in the future, you will have the option to flash factory images.
corkiejp said:
@Jsunn What was the trick? Reinstalling drivers, i Guess.
Remember to Enable OEM unlocking in developer options.
And if you have already factory reset? It might be a good time to Unlock Your bootloader with "fastboot oem unlock".
So if anything goes wrong in the future, you will have the option to flash factory images.
Click to expand...
Click to collapse
It was the drivers, I didn't think to check that the first time. I am going to unlock the book loader, I was thinking the exact same thing! I'm just glad to be back up and running.
-J