Related
My phone asks me if I want to install, I hit yes, it powers off and goes to the screen with the droid and the status bar. Status bar fills up then it changes to the droid with the ! in the triangle and just stays there. If I pull the battery it asks me if I want to install again when the phone boots up.
Rooted 2.2 w/ unrevoked forever.
my update went to that page with the !....had 2 arrows kinda making a circle around it. Just wait it out...mine sat there a few but did its thing...
Mine doesn't have the arrows. It has been sitting there for 15+ minutes on two different occasions now.
i get "assert failed" then boots to previous rom
hmmm... Does it have any red on that page? I have seen that page with red on it...battery pull usually fixes it. Mine was same page but no red at all just the arrows. Maybe you should be on a stock 2.2 ROM?
There are several different ways to get it now here is one you can try:
http://forum.xda-developers.com/showpost.php?p=8279411&postcount=23
AnHero said:
My phone asks me if I want to install, I hit yes, it powers off and goes to the screen with the droid and the status bar. Status bar fills up then it changes to the droid with the ! in the triangle and just stays there. If I pull the battery it asks me if I want to install again when the phone boots up.
Rooted 2.2 w/ unrevoked forever.
Click to expand...
Click to collapse
Same configuration here with the same results.
It's just the little green guy and the !. No red. Battery pulled 3 times now, won't work. I'm on stock 2.2.. only rooted. I rooted it and haven't changed anything. Not even a custom kernel.
Hmm, something must be up with the OTA update. Just download the package from one of the other threads, save it to SD card and update from zip from recovery.I did that and it worked in less than 10 minutes
There are several different ways to get it now here is one you can try:
http://forum.xda-developers.com/showpost.php?p=8279411&postcount=23
Also I have the actually files that I got when I did the OTA if you want them. I am actually unrooted on one of my phones...for comparison stuff. So the files I recieved on the unrooted OTA are here:
These are the 2 files I recieved when I updated:
1: http://www.mediafire.com/?i2ypi9121snmpyo
2: http://www.mediafire.com/?cljyvv281l1b000
I have not tested to see if they break root but this is the official updates...2 seperate files/apk's.
Same problem here with unrevoked so I did it manually and it worked like a charm.
I can't post links but if you go to androidcentral it has the instruction there on the front page.
http://www.androidcentral.com/....
AnHero said:
My phone asks me if I want to install, I hit yes, it powers off and goes to the screen with the droid and the status bar. Status bar fills up then it changes to the droid with the ! in the triangle and just stays there. If I pull the battery it asks me if I want to install again when the phone boots up.
Rooted 2.2 w/ unrevoked forever.
Click to expand...
Click to collapse
had that exact same problem. i think the OTA doesn't bode well with being rooted, at least thats what it seems. i was unrevoked and tried it (then got your problem with the !). so i tried unrooting it and the update worked like a charm
BTW....You will need run unrevoked again if you applied the update manually!
yep i went all stock unrooted and it took it right away. it probably didnt like the fact i was on metropcs too lol
why are you guys doing ota? there is already a rooted version of this update in development that you can flash from recovery.
i just want pri,radio,etc and rom to be stock without any mods besides what i do.
poetictragdyx said:
had that exact same problem. i think the OTA doesn't bode well with being rooted, at least thats what it seems. i was unrevoked and tried it (then got your problem with the !). so i tried unrooting it and the update worked like a charm
Click to expand...
Click to collapse
I'm getting error 7.
Can you provide the link for unrooting?
Help with OTA
Hello everyone.Im sure your getting bombarded with a lot of questions.I have the OTA Downloaded on my computer.I changed the name to update.zip
Im not sure if im putting the file on the sdcard of if there is a specific file i cant find to put it in.
When i go through the process of shutting phone off and using the volume button i get are you sure you want to install and i click yes.
This is what i get.
Clockwork recovery v2.5.0.1
---Install from sdcard...
Finding update package....
Opening update package...
E: Cant open/sdcard/update.zip
(No such file or directory)
Installation aborted.
Thanks in advance...
So is the manual update working for everyone that rooted using unrevoked 3.2? I just want to make sure before I go through the process.
AnHero said:
My phone asks me if I want to install, I hit yes, it powers off and goes to the screen with the droid and the status bar. Status bar fills up then it changes to the droid with the ! in the triangle and just stays there. If I pull the battery it asks me if I want to install again when the phone boots up.
Rooted 2.2 w/ unrevoked forever.
Click to expand...
Click to collapse
Guide for this
http://forum.xda-developers.com/showthread.php?p=8285266#post8285266
So after doing some edits and removing the AT&T bloatware the phone stopped wanting to allow me to add apps. Even though I had 20MB free. My phone now reboots when I put the SD card in.
So I decided to do a factory reset which worked fine but now I'm stuck on the first screen of the android set up. now the screen is just black with the taskbar at the top and the words "setup" right below it but no android icon in the center, and the emergency button is absent on the bottom.
I googled and found out that if you touch the 4 corners in a clockwise pattern this is suppose to bypass the setup and just go straight to your home screen. well this is a no-go.
The phone receives call fine and the screen is responsive when I slide the taskbar down. also when I plug it into my comp the motosuite boots up and works fine as well.
So any suggestions on how to get past this or how I can just reflash the phone?
It sounds like you don't have a launcher...
How to fix... i'm not so sure...
Maybe a forum search?
Sent from my MB508 using Tapatalk
Can someone hook me up with the launcher for the flipside. I was going to use sideloader wonder machine to reload it. since I do remember deleting it like an idiot.
I've googled he crap out of it with no success. so can someone please hook me up?
thebluetoothkid said:
Can someone hook me up with the launcher for the flipside. I was going to use sideloader wonder machine to reload it. since I do remember deleting it like an idiot.
I've googled he crap out of it with no success. so can someone please hook me up?
Click to expand...
Click to collapse
Cant you just go to android market on your computer and send a launcher to your phone that way? It automatically installs for you and if you are able to open the notification bar you should then be able to launch it to make it your default. Hope this helps.
pre4speed said:
Cant you just go to android market on your computer and send a launcher to your phone that way? It automatically installs for you and if you are able to open the notification bar you should then be able to launch it to make it your default. Hope this helps.
Click to expand...
Click to collapse
The issue is i'm stuck on the very first screen of the phone. you know when you first power one up for the first time and set up gmail and everything else. well mins is stuck on the first screen so i can't get to market to download it.
If it is stuck on the setup it doesn't sound like a launcher problem. I can get the launcher off my phone if you want it but I know after I did a NON SBF update (using android recovery) mine got stuck on the MotoBlur setup and would freeze at 95% or so no matter if it was signing into my old account or creating a new one. I had to do an SBF flash for it to work. Not sure what the problem was but using update.zip looked like it was fine but it screws something up in it.
devi59 said:
If it is stuck on the setup it doesn't sound like a launcher problem. I can get the launcher off my phone if you want it but I know after I did a NON SBF update (using android recovery) mine got stuck on the MotoBlur setup and would freeze at 95% or so no matter if it was signing into my old account or creating a new one. I had to do an SBF flash for it to work. Not sure what the problem was but using update.zip looked like it was fine but it screws something up in it.
Click to expand...
Click to collapse
I'd gladly flash it again, but the snare is I don't have debugging mode on and with that black screen I can't get to it. I even hunted for Hotkeys to get into settings. So any possibility to get the phone into debugging mode without going through settings?
thebluetoothkid said:
I'd gladly flash it again, but the snare is I don't have debugging mode on and with that black screen I can't get to it. I even hunted for Hotkeys to get into settings. So any possibility to get the phone into debugging mode without going through settings?
Click to expand...
Click to collapse
You can follow this guide located here http://forum.xda-developers.com/showthread.php?p=17042497
Flipside Bootloader Mode - Restore with SBF File
To put the Flipside into bootloader mode:
Open the keyboard
Press and hold the up arrow key (to the left of the OK key)
Hold the power button down
Release both buttons after about 4 seconds
You should see a display that says:
Bootloader
91.2B (If you already went to Froyo then this number is going to be like 91.7 I think)
Battery Ok
OK to Program
Connect to USB
Data Cable
This mode is for flashing an sbf file (ROM) to your phone using RSDLite.
RSD Lite version 4.9 works with the Flipside
I have received info from a reliable source that downgrading the Flipside from the not-yet-released Froyo upgrade using the available SBF files will brick your AT&T phone.
I do not have personal knowledge of this, but I trust my source.
Click to expand...
Click to collapse
Then just download the SBF listed on that post. Let me know if you are confused. I've done this about 3 times now on my phone. I keep screwing around with it and reflashing it.
devi59 said:
You can follow this guide located here http://forum.xda-developers.com/showthread.php?p=17042497
Then just download the SBF listed on that post. Let me know if you are confused. I've done this about 3 times now on my phone. I keep screwing around with it and reflashing it.
Click to expand...
Click to collapse
Thanks, I'll try that again, I've actually already tried that but RS lite doesn't seem to read my phone. but I had that issue before and I know I have to use and older version instead of 4.9. Hopefully it'll work
Thats odd. I know I just bought our phones but they came with 2.1 and it worked just fine with it. I've upped to froyo now but I never had problems. Only had problems doing the update and doing a factory reset. After doing them I needed to do the SBF. Only thing that fixed mine.
Ok I have it fixed now. I tried a few different version of RS lite. and it just wouldn't read the phone even though the phone would read the comp.
Solution: run friggin RS Lite in Compatibility mode with XP SP3. worked fine.
So the phone is up and running again, but for some reason now everytime I put my 16GB sd card in it, the phone will reboot. I'm going to format the card as FAT and see if that solves it.
Cool. Glad you got it working. Now we just need some cyanogenmod love for our phones
I am far way ahead of your problem
i had the same issue
i downloaded the SAGE_U3_10.23.20_SIGNATT_USASAGE02B25ND0ATTNA02E.0R_PDS001_SAGEATT_P033_HWp4_1FF.sbf and flashed using RSD lite 5.3.1 multi flashing desktop
however i am struck at boot loader and my mb 508 doesnt even boot into the same state after flashing
its strucked at boot loader, i also have the Blur_Version.2.159.17.MB508.ATT.en.US.zip but i can not flash it either
i tried to download the Download BL_917B_4G_sageemu_Consumer_replacer.zip for free on Filesonic.com but filesonic is no more supported to access downloading any kind of boot loader or other files
my question is, how can i restore my phone
current display:
boot loader:
91.7 B
ERR: A5, 70, 70, 00, IF
MEM_ MAP Blank
Service Req'd
Battery Ok
Ok to progress
Connect USb
Data cable
please help here
tnt4ever said:
I am far way ahead of your problem
i had the same issue
i downloaded the SAGE_U3_10.23.20_SIGNATT_USASAGE02B25ND0ATTNA02E.0R_PDS001_SAGEATT_P033_HWp4_1FF.sbf and flashed using RSD lite 5.3.1 multi flashing desktop
however i am struck at boot loader and my mb 508 doesnt even boot into the same state after flashing
its strucked at boot loader, i also have the Blur_Version.2.159.17.MB508.ATT.en.US.zip but i can not flash it either
i tried to download the Download BL_917B_4G_sageemu_Consumer_replacer.zip for free on Filesonic.com but filesonic is no more supported to access downloading any kind of boot loader or other files
my question is, how can i restore my phone
current display:
boot loader:
91.7 B
ERR: A5, 70, 70, 00, IF
MEM_ MAP Blank
Service Req'd
Battery Ok
Ok to progress
Connect USb
Data cable
please help here
Click to expand...
Click to collapse
I replied to your pm. Ill send both files if you want. Just send me your email in pm and ill do it.
I kept getting a pop up message on my phone saying a new software update is available for my device. It appears to be an Android update MB860 v4.5.141. So I downloaded the update with no problems but the update won't install.
When I clicked Install the phone shut down as it's supposed too. But the update fails and I keep getting a black screen with Android & an exclamation point inside a Triangle. I have to pull the battery and restart but once the phone boots up it shuts down again to attempt to Install the update and again I get the black screen with the Android and exclamation point. The phone is unusable at this point. Any ideas?
My Atrix is NOT rooted.
I just tried the manual update and it won't work because the phone can't start up long enough, it shuts down before I can do anything. How can perform a factory reset if the phone shuts off before I can get into the menu to select factory reset? Will a factory reset even fix this problem?
Hi,
check this:
http://forum.xda-developers.com/showpost.php?p=22636544&postcount=5
Good luck
Thank you for the help. The problem is I'm new to Android so I don't really understand what that post is telling me and I'm a new member here so the forum won't let me post a question there. I don't understand how to boot into CWM or how to format the /cache partition once I get there. Any help would be greatly appreciated.
NY Yankee Pride said:
Thank you for the help. The problem is I'm new to Android so I don't really understand what that post is telling me and I'm a new member here so the forum won't let me post a question there. I don't understand how to boot into CWM or how to format the /cache partition once I get there. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Have you flashed a custom recovery? If you have, boot into it by holding volume down after turning the device on. Then hit volume down until you have selected recovery. Then hit volume up to boot into recovery. From there, wipe the cache partition and reboot.
If you haven't flashed custom recovery... I dunno what to tell you. It's strange that the OTA update isn't working on a non-rooted, non-unlocked phone.
I don't even know what flashed recovery is. Is that what the post above is about where it explains to boot into CWM and format the /cache partition? Sorry for the newb questions but I'm really lost here and kind desperate because now I'm without a phone.
NY Yankee Pride said:
I don't even know what flashed recovery is. Is that what the post above is about where it explains to boot into CWM and format the /cache partition? Sorry for the newb questions but I'm really lost here and kind desperate because now I'm without a phone.
Click to expand...
Click to collapse
Make sure phone is off.
Press and hold the volume down button, then press the power button.
When text appears on the screen, release the down volume button. Then press the down volume button again and watch the text change... keep going until text reads "Android Recovery". Press up volume button. IF YOU go to far (too many down presses) keep pressing down and it will cycle back...don't press the up volume expecting to go back.
You are now in recovery...if you have a screen with a big triangle and an exclamation point, press both volume buttons at the same time. A menu will appear. Use volume buttons to move to the option you want and the power button to select it. Most likely, you'll want "factory reset". do that.
If you end up with any other screen (not the triangle) then you have a custom recovery and you knew everything I just told you...
Yeah it looks like a factory reset is my only option at this point, I was hoping to avoid that. Thanks for all the help and tips.
I got it working!! I spent about an hour searching google with different search phrases and I found a post where someone had a similar problem about a year ago with a different phone. This is what I did:
-I pulled the battery then booted up the phone by pressing the power button & the volume down button at the same time until "Fastboot" showed at the top of the screen.
-Then I scrolled through & selected "Android Recovery"
-I then selected "Wipe Cache Partition"
-Then I selected "Yes-Wipe Cache"
The phone then restarted and I got a message that the update failed but the phone stayed up and running and has been working fine since. I've since restarted it several times.
So the update did not install but I'm not going to attempt the update again at this point because I'm sure I'll just have the same problem.
I know I said the phone was not rooted but I failed to mention that I did buy the phone used so I don't know what the previous owner did to it. But I did a Factory Reset on the phone when I bought it so wouldn't that remove any previous rooting on the phone if there was any?
NY Yankee Pride said:
I got it working!! I spent about an hour searching google with different search phrases and I found a post where someone had a similar problem about a year ago with a different phone. This is what I did:
-I pulled the battery then booted up the phone by pressing the power button & the volume down button at the same time until "Fastboot" showed at the top of the screen.
-Then I scrolled through & selected "Android Recovery"
-I then selected "Wipe Cache Partition"
-Then I selected "Yes-Wipe Cache"
The phone then restarted and I got a message that the update failed but the phone stayed up and running and has been working fine since. I've since restarted it several times.
So the update did not install but I'm not going to attempt the update again at this point because I'm sure I'll just have the same problem.
I know I said the phone was not rooted but I failed to mention that I did buy the phone used so I don't know what the previous owner did to it. But I did a Factory Reset on the phone when I bought it so wouldn't that remove any previous rooting on the phone if there was any?
Click to expand...
Click to collapse
No. Factory reset does not clear out rooting, unlocking, or any modifications to the bootloader or recovery.
for root: There's a root checker app in marketplace to test root access. If you do have root access you need to unroot before applying the update.
for unlocked: the only way I know to tell is when you power on the phone the word "unlocked" will appear at the top of the screen.
bootloader and recovery: if you have a locked bootloader than you should have stock bootloader and recovery = ok to apply OTA update. If you're unlocked, do NOT apply the OTA update. A few people have succeeded somehow, many do not.
Thanks Gnac. I just noticed when I turn the phone on it does say "unlocked" at the top left of the screen, I never noticed that before. I know for sure the previous owner was using it on AT&T so I don't know why he would have unlocked it. I think I'll just skip the update to avoid any further problems.
I know it's been a couple of months since my last post but I never got the update to work even with the manual update from Motorola's site. I followed the exact directions more than once but I just can't get it to work. At this point I don't really care about the update but the nagging pop up every hour on my phone reminding me to update is getting annoying. Is there an easy way to stop the nagging update pop up that give the option to download now or download later? I always choose later but it nags me probably 20 times a day.
NY Yankee Pride said:
I know it's been a couple of months since my last post but I never got the update to work even with the manual update from Motorola's site. I followed the exact directions more than once but I just can't get it to work. At this point I don't really care about the update but the nagging pop up every hour on my phone reminding me to update is getting annoying. Is there an easy way to stop the nagging update pop up that give the option to download now or download later? I always choose later but it nags me probably 20 times a day.
Click to expand...
Click to collapse
titanium backup's freeze function (you need to buy the paid version) can fix this. Just freeze Updater to stop the pop up.
Thanks for the suggestion but that won't really work for me since I have no experience in rooting and I'm way too worried about bricking it to even try that.
You say you bought your phone used, and haven't rooted or modified it. Are you on AT&T? If so, and were it my phone, I'd be taking it to an AT&T store and having them check it out.
We are great at looking for alternate routes to fix our own stuff and using "official routes" as a last resort (as it requires putting it all back to stock first), but to me, this is a clear case of their own update screwing up for some arbitrary reason -- totally not your fault.
I don't think that will work because the bootloader is unlocked so I have to assume the previous owner rooted the phone. When I start up the phone it says "unlocked" in the top left corner during start up.
Wait for the update but I know that come in 2013 when android world will be jelly bean
Inviato dal mio MB860 usando Tapatalk
Ok I'm sorry to be a pest but I can't take this darn nagging pop up 20+ times a day. Obviously I don't have a clue about rooting but a guy a work with said he could probably unroot this phone for me so I can install the update. My question is if I take the SIM card out & sign into blur will he be able to do whatever needs to be done without a SIM card in the phone? That way I can put my SIM card in an older phone I have so I won't be without a phone if it takes him a few days.
NY Yankee Pride said:
Ok I'm sorry to be a pest but I can't take this darn nagging pop up 20+ times a day. Obviously I don't have a clue about rooting but a guy a work with said he could probably unroot this phone for me so I can install the update. My question is if I take the SIM card out & sign into blur will he be able to do whatever needs to be done without a SIM card in the phone? That way I can put my SIM card in an older phone I have so I won't be without a phone if it takes him a few days.
Click to expand...
Click to collapse
Actually you could probably do this yourself.. search for "Petes Motorola root" then download and follow instructions in how to "unroot"..
Sent from my MB860 using XDA
Thank you for that suggestion. Since I don't have any experience in rooting I'm a little nervous but it seems pretty straight forward. How do I verify steps 1 & 2?
1. Make sure the Motorola drivers are still installed.
2. Make sure USB Debugging is still selected.
3. Connect your Bionic to your computer.
4. Run the Pete's Motorola Root Tools.exe.
5. Select UnRoot My Phone at the bottom.
6. Your phone will reboot 3-4 times as the program goes through all 4 steps in the process.
Hi,
I've just received the 4.3 JB update notification and I need to know if it's ok to install it bcz my N7's bootloader is unlocked and in recovery mode I get the 'No Command' error. Please tell me if I should put the factory image first (I know, it's a guide but I don't have the link) and then update to 4.3. Also, I read here, on Nexus 7 forums that the 4.3 got some problems/errors after installing. Should I wait for 4.3.x JB or 5.0 KLP ?
Sent from my Nexus 7
bv31top said:
Hi,
I've just received the 4.3 JB update notification and I need to know if it's ok to install it bcz my N7's bootloader is unlocked and in recovery mode I get the 'No Command' error. Please tell me if I should put the factory image first (I know, it's a guide but I don't have the link) and then update to 4.3. Also, I read here, on Nexus 7 forums that the 4.3 got some problems/errors after installing. Should I wait for 4.3.x JB or 5.0 KLP ?
Sent from my Nexus 7
Click to expand...
Click to collapse
First, the "no command" does not prevent the access to the stock recovery. To go to the menu recovery press power and tap volume up.
Your update will still be installed.
Second, it is the safe way to keep the stock recovery - not re-installing the whole factory image - to get a smooth installation of JB 4.3.
Third, some issues are popping up. Some apps do not work, like MX Player, because the devs are still updating their apps for JB 4.3. It's matter of being patient, if such concept still exists in today world.
In addition if your Nexus 7 gets root you will lose it. No panic. You need to update SuperSu. Chainfire offered a temporary fix with the update version 1.43.This version is replaced as of today by version 1.51.
gunner1937 said:
First, the "no command" does not prevent the access to the stock recovery. To go to the menu recovery press power and tap volume up.
Your update will still be installed.
Second, it is the safe way to keep the stock recovery - not re-installing the whole factory image - to get a smooth installation of JB 4.3.
Third, some issues are popping up. Some apps do not work, like MX Player, because the devs are still updating their apps for JB 4.3. It's matter of being patient, if such concept still exists in today world.
In addition if your Nexus 7 gets root you will lose it. No panic. You need to update SuperSu. Chainfire offered a temporary fix with the update version 1.43.This version is replaced as of today by version 1.51.
Click to expand...
Click to collapse
Ok. I understood only the 3rd part.
I don't need root. I tried to acces the recovery mode after the fastboot menu and the result was no command error. I tried volume up + power (within the no command screen) and nothing. And you are wrong there bcz it's press, not tap.
I forgot to mention, I will use the stock 4.2.2 factory image to make it like 'out of the box'. I want to make it like a brand new unit, fresh pulled out of the box.
Sent from my Nexus 7 using xda app-developers app
bv31top said:
Ok. I understood only the 3rd part.
I don't need root. I tried to acces the recovery mode after the fastboot menu and the result was no command error. I tried volume up + power (within the no command screen) and nothing. And you are wrong there bcz it's press, not tap.
I forgot to mention, I will use the stock 4.2.2 factory image to make it like 'out of the box'. I want to make it like a brand new unit, fresh pulled out of the box.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Obviously I misunderstood your case and I do apologise for my mistake.
I wrongfully assumed that your tablet was unlocked and root.Therefore my mention of SuperSu was irrelevant in your case. And you do not have apps which need root to be used.
Since you are still stock including recovery I do not see why the update to JB 4.3 will not installed. In this case there is no need to access the recovery mode.
Depending of the definition of "tap", mine is a brief and quick press, I access the recovery menu by pressing power and then quickly and briefly pressing ( a tap) up volume to get in the recovery menu.
Hope you will get JB 4.3 without an issue
So, is it safe to flash the factory image and then update to 4.3? What is the chance of succes when using the following sticky? (in %)http://forum.xda-developers.com/showthread.php?t=1907796
bv31top said:
So, is it safe to flash the factory image and then update to 4.3? What is the chance of succes when using the following sticky? (in %)http://forum.xda-developers.com/showthread.php?t=1907796
Click to expand...
Click to collapse
That sticky is correct. Make sure that you flash boot BEFORE anything else though, and download the actual Android platform tools (i.e. don't cheat and look for just fastboot or adb). There seems to have been a recent update to fastboot that makes older versions play very badly with 4.3
Rirere said:
That sticky is correct. Make sure that you flash boot BEFORE anything else though, and download the actual Android platform tools (i.e. don't cheat and look for just fastboot or adb). There seems to have been a recent update to fastboot that makes older versions play very badly with 4.3
Click to expand...
Click to collapse
Umm... To flash 'boot'? About the cheating, if I follow the thread correctly it's ok, isn't it? I mean, if I download the latest SDK I'm safe, right?
Up
Please respond... I really need some help on this thing.
Yeah. I finally managed to acces the recovery mode using the power + volume up buttons in the "No Command" screen. I also succesfully locked the bootloader and the white padlock is gone. Right now, I touched on the install update notification and then on the 4.3 system update page I tapped on the "Reboot and Install button". It did the 10 sec countdown for restarting and now it says "Rebooting - 157.5 MB" but nothing happens.
"no command" boot loop
I too was able to enter the bootloader (unlocked) from the "No Command" bootloop by continuously holding down the power and volume down buttons (after about 5 rapidfire reboot attempts). From there I opened Nexus Root Toolkit (v1.7.8) and was able to flash 4.4.0 KRT16S using the button "Flash Stock + Unroot" (current status soft-bricked/Bootloop). Hope this helps with unbricking your device.
Well, what a surprise.
After sideloading the OTA (as usual, no errors or anything strange) and waiting for the "Updating android app 1/1xx", the screen goes black. I can't do absolutely anything but to press the power on button to turn on/off the screen (which is black illuminated), and if I hold the button I clearly see the "Power Off?" message in the white box as usual over the black background, and the animation of "Android is turning off" if I turn it off..
Sometimes a SystemUI error appears and after pressing OK it reappears again and again, sometimes showing the live wallpaper behind it. It ends up with an infinite loop of SystemUI crashes.. It may be a prob loading the launcher? it's not even showing status/navigation bars..
This sideloading the OTA on an stock N7. Really google??
When cleaning cache on recovery, it does the updating apps again, then shows for few secs that some app failed and goes black again.
This N7 is stock with the bootloader locked, any way to fix this without needing to unlock (and so wipe)?
Thanks in advance.
EDIT: I'm definitely in a SystemUI crash loop. Even rebooting to safe mode doesn't work at all.
MD5?
I've just downloaded the OTA myself, and thought I'll check out xda just to be sure there is nothing to worry about, and then I see This!
First thing ofcourse would be to make sure the OTA file was not incomplete/damaged. Would you mind confirming the MD5 you've got? Mine is "d394ba9a61f8f6a206b8c427844b5427", file size 106,509,760 bytes.
Silver-Hawk said:
I've just downloaded the OTA myself, and thought I'll check out xda just to be sure there is nothing to worry about, and then I see This!
First thing ofcourse would be to make sure the OTA file was not incomplete/damaged. Would you mind confirming the MD5 you've got? Mine is "d394ba9a61f8f6a206b8c427844b5427", file size 106,509,760 bytes.
Click to expand...
Click to collapse
Hello,
Using "HashMyFiles",
MD5 is d394ba9a61f8f6a206b8c427844b5427,
SHA1 is 9f163586073265c54d86679efd63513a4477cfd8.
Size: 106,509,760 bytes
So yeah, good download file.
And there is no problem with the cable or "Minimal ADB and Fastboot" version since I used it to flash the partitions directly in my other N7 (rooted and such) and also tested applying the N5 5.1 OTA on my N5 and both results were good.
There is no bad stuff here, the REAL file ota 5.0.2 to 5.1 "semi-bricked" my not rooted n7 in 5.0.2..
Google really has QA? I still don't believe an ota did this to a pure n7 stock rom that used otas since the real first 4.1 build to these days.
S**t happens!??
Well, don't know what happened in your case, but all I can tell here (for someone else in a similar situation maybe) is that it worked perfectly fine for me. I updated using adb sideload on a totally stock device as well. Never rooted, no custom recovery, only difference being mine was already bootloader unlocked (don't know if that's why it didn't work for you, though I doubt it). Unlocking the bootloader was the first thing I did out of the box actually, for situations exactly like u're describing.
As for you, I hope it's still being recognized on USB connection so you can pull most of your data atleast. All the best
adb logcat gives me:
[ 03-12 20:52:48.421 29480:29480 E/AndroidRuntime ]
FATAL EXCEPTION: main
Process: com.android.systemui, PID: 29480
java.lang.NullPointerException: Attempt to invoke virtual method 'boolean com.android.systemui.statusbar.phone.PhoneStatusBar.isKeyguardSecure()' on a null object reference
at com.android.systemui.statusbar.phone.KeyguardBottomAreaView.isCameraDisabledByDpm(KeyguardBottomAreaView.java:260)
at com.android.systemui.statusbar.phone.KeyguardBottomAreaView.updateCameraVisibility(KeyguardBottomAreaView.java:237)
at com.android.systemui.statusbar.phone.KeyguardBottomAreaView.onFinishInflate(KeyguardBottomAreaView.java:168)
at android.view.LayoutInflater.rInflate(LayoutInflater.java:814)
at android.view.LayoutInflater.parseInclude(LayoutInflater.java:916)
at android.view.LayoutInflater.rInflate(LayoutInflater.java:802)
at android.view.LayoutInflater.parseInclude(LayoutInflater.java:916)
at android.view.LayoutInflater.rInflate(LayoutInflater.java:802)
at android.view.LayoutInflater.rInflate(LayoutInflater.java:809)
at android.view.LayoutInflater.inflate(LayoutInflater.java:504)
at android.view.LayoutInflater.inflate(LayoutInflater.java:414)
at android.view.LayoutInflater.inflate(LayoutInflater.java:365)
at android.view.View.inflate(View.java:18532)
at com.android.systemui.statusbar.phone.PhoneStatusBar.makeStatusBarView(PhoneStatusBar.java:638)
at com.android.systemui.statusbar.phone.PhoneStatusBar.addStatusBarWindow(PhoneStatusBar.java:3047)
at com.android.systemui.statusbar.phone.PhoneStatusBar.createAndAddWindows(PhoneStatusBar.java:3043)
at com.android.systemui.statusbar.BaseStatusBar.start(BaseStatusBar.java:561)
at com.android.systemui.statusbar.phone.PhoneStatusBar.start(PhoneStatusBar.java:588)
at com.android.systemui.statusbar.SystemBars.createStatusBarFromConfig(SystemBars.java:106)
at com.android.systemui.statusbar.SystemBars.onNoService(SystemBars.java:58)
at com.android.systemui.statusbar.ServiceMonitor.startService(ServiceMonitor.java:228)
at com.android.systemui.statusbar.ServiceMonitor.access$000(ServiceMonitor.java:49)
at com.android.systemui.statusbar.ServiceMonitor$1.handleMessage(ServiceMonitor.java:73)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:135)
at android.app.ActivityThread.main(ActivityThread.java:5254)
at java.lang.reflect.Method.invoke(Native Method)
at java.lang.reflect.Method.invoke(Method.java:372)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:903)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:698)
[ 03-12 20:52:48.425 468: 484 W/ActivityManager ]
Process com.android.systemui has crashed too many times: killing!
Silver-Hawk said:
Well, don't know what happened in your case, but all I can tell here (for someone else in a similar situation maybe) is that it worked perfectly fine for me. I updated using adb sideload on a totally stock device as well. Never rooted, no custom recovery, only difference being mine was already bootloader unlocked (don't know if that's why it didn't work for you, though I doubt it). Unlocking the bootloader was the first thing I did out of the box actually, for situations exactly like u're describing.
As for you, I hope it's still being recognized on USB connection so you can pull most of your data atleast. All the best
Click to expand...
Click to collapse
Yeah I saved all the stuff via adb, but it SUCKS to have to format because an OFFICIAL OTA did this. Thanks mate!
And I now recognize the error of not having the bootloader unlocked. I NEVER suspected to get in such a situation only sideloading otas on a device never unlocked. Google really fails at delivering an stable platform.
Have same problem after sideload update. No root, no unlock and same problem in the logs. I have updated wife's nexus 5 and it works well, but mine stuck on start-up.
Any ideas how to fix it w\o full wipe ?
---------- Post added at 11:20 AM ---------- Previous post was at 10:24 AM ----------
Btw @RusherDude, have you used something like 'Lockscreen Policy' app to disable camera or lock screen ?
Kaspian said:
Have same problem after sideload update. No root, no unlock and same problem in the logs. I have updated wife's nexus 5 and it works well, but mine stuck on start-up.
Any ideas how to fix it w\o full wipe ?
---------- Post added at 11:20 AM ---------- Previous post was at 10:24 AM ----------
Btw @RusherDude, have you used something like 'Lockscreen Policy' app to disable camera or lock screen ?
Click to expand...
Click to collapse
Same prob? So we may not be alone on this.. Google really messed up this OTA.
No, I didn't do anything of that to this N7, it was pure stock lock screen and nova launcher.
@Kaspian
EDIT:
Yes now I remember I had one from the 4.2 times, Lockscreen Policy
https://play.google.com/store/apps/details?id=com.wordpress.chislonchow.deviceadminkeyguard&hl=es
Now I should be able to uninstall it via adb but I get this:
adb uninstall com.wordpress.chislonchow.deviceadminkeyguard
Failure [DELETE_FAILED_DEVICE_POLICY_MANAGER]
Checking the doc:
static int DELETE_FAILED_DEVICE_POLICY_MANAGER
Uninstall return code
uninstall fail if the system failed to delete the package because it is the active DevicePolicy manager.
Any way I can delete this app or deactivate his DeviceAdmin status with ADB and no root? :S I can't find any way.. this is frustrating.
I'm not sure uninstall will help now. I think you need to revert the changes made by "Lockscreen Policy".
I didn't find the solution quick enough and just wiped my nexus 5
Kaspian said:
I'm not sure uninstall will help now. I think you need to revert the changes made by "Lockscreen Policy".
I didn't find the solution quick enough and just wiped my nexus 5
Click to expand...
Click to collapse
It seems that I just need to disable it from the Device Admin rights window (the same reason why you need to disable its device admin rights before uninstalling it normally), but the prob is seems that there is not a way to do that without UI interaction. I can lauch the system activity or even the device admin activity from ADB, but I don't see them in the tablet so I can't interactuate.
It is really, really frustrating. This is the last non-rooted Android device I own, for sure. What a traition....
Yep, this time I unlocked bootloader also...
Kaspian said:
Yep, this time I unlocked bootloader also...
Click to expand...
Click to collapse
Same, just wiped it, unlocked the bootloader and rooted it.. never had this intention but it's terrible that on Android you're forced to wipe because an OTA made an app ruin the tablet (and thank god I had ADB debugging enabled before, otherwise I even wouldn't had be able to save the data via ADB before wiping), it's incredible, Google epic sucks compared to Apple on this.
RusherDude said:
And I now recognize the error of not having the bootloader unlocked. I NEVER suspected to get in such a situation only sideloading otas on a device never unlocked. Google really fails at delivering an stable platform.
Click to expand...
Click to collapse
if you go to the android factory image website
https://developers.google.com/android/nexus/images
in the flashing instructions they give you they specifically tell show and tell you to unlock the boot loader before applying an update. after the update they also instruct you on how to lock the bootloader again. do not start to bash google because you do not follow their instructions.
phrozenstare said:
if you go to the android factory image website
https://developers.google.com/android/nexus/images
in the flashing instructions they give you they specifically tell show and tell you to unlock the boot loader before applying an update. after the update they also instruct you on how to lock the bootloader again. do not start to bash google because you do not follow their instructions.
Click to expand...
Click to collapse
I was NOT flashing a factory image, I was SIDELOADING an OTA.Nothing to do with that.
In fact, my problem would be reproduced if anyone being pure stock on 5.1 downloaded that app and gave it device admin.