I am having trouble getting the 4.04 update to work, I get to the android, then it lays down with a red exclamation point out of his stomach.
I was running Kang B36 w Franco Milestone
I used option 9 on the toolkit my build toro 4.02
I restored facotry image for my phone via option 8
I reflashed stock recovery via option 10
finally I locked my bootloader via option 11
restarted my phone downloaded the update and now it stays stuck on the Android with the red exclamation out of his stomach halfway thru the update.
anyone know the reason why my phone will not update?
did I screw the Basseband? IMEI? or serial? the same thing happend on my Droid Razr when I modified the Build.prop but I never touched the build.prop on my GNEX.
gfropr said:
I am having trouble getting the 4.04 update to work, I get to the android, then it lays down with a red exclamation point out of his stomach.
I was running Kang B36 w Franco Milestone
I used option 9 on the toolkit my build toro 4.02
I restored facotry image for my phone via option 8
I reflashed stock recovery via option 10
finally I locked my bootloader via option 11
restarted my phone downloaded the update and now it stays stuck on the Android with the red exclamation out of his stomach halfway thru the update.
anyone know the reason why my phone will not update?
did I screw the Basseband? IMEI? or serial? the same thing happend on my Droid Razr when I modified the Build.prop but I never touched the build.prop on my GNEX.
Click to expand...
Click to collapse
1) Don't use a toolkit. You don't know what it is doing exactly, so you don't know where it went wrong.
2) I suspect that there is still something that is not stock. I would follow the instructions here, which takes you through the whole process set-by-step (make sure you do the optional steps in part D). That way you can be certain that nothing messed up. Once you do that, then you can have a look here for how to use the OTA update file to update.
3) Don't re-lock your bootloader.
Thank you very much I was unaware of the issues with tool kits, I assumed they worked good since they are stickied.
Sent from my DROID RAZR using xda premium
When I boot into recovery from fastboot my android has a red triangle with a exclamation point, do you think my stock recovery is corrupted?
I am having the same exact probem. I am running the stock 4.0.2 that the phone came with. I used a toolkit that was posted in the Development forums to unlock and root the phone. Other than that, its totally stock.
When I do the OTA update, It gets to the dead android with a triangle coming from his stomach,
I have to pull the battery to get the phone booted, and its still on 4.0.2.
Anyone have any suggestions?
gfropr said:
When I boot into recovery from fastboot my android has a red triangle with a exclamation point, do you think my stock recovery is corrupted?
Click to expand...
Click to collapse
What you see IS the stock recovery screen. (To see the menu, you need to press power and volume up together.) However, if you are seeing that screen when you try to install the update, it is because something on your device is not stock, or, it is not the correct version of stock for the update.
The easiest way to flash the update (assuming you are all stock) is to follow one of the methods in the second link I posted.
Related
Ok, so i have been patiently waiting for the JB update on my Play store purchased USA GSM GN that I have been using on Tmobile.
I finally get the update while I am at work, cant download since I don't have wifi there. The wait until 5pm was agonizing!
I finally get home, download the update, it asks to restart and install, i click ok.
It reboots into recovery, but I see the andorid guy with the triangle and a red exclamation mark! It stays there for a couple of minutes and then just boots normally into android os without applying the update.
I rebooted manually into recovery to see if I could reproduce the issue and sure enough i get the red exclamation mark.
I held down Volume Up and Power button and it boots into stock recovery (3e) where i cannot find anything to apply and I just wiped cache and data and rebooted.
Of course, now I check for system update and it says system is up to date.
What just happened? I was rooted, but with stock recovery, locked bootloader.
Anybody else have this issue. How do I fix it so that the next time it finds the update i don't have this happen again??
Thanks in advance,
I could just pull my hair out in frustration....
Dude q&a section this is development wrong section
Sent from my Galaxy Nexus using Tapatalk 2
Why is this in development?
Read forum rules
Questions go in Q&A
Thread moved
FNM
You must be 100% stock for the OTA to apply. Correct radio, UI, build.prop, etc.
hmm i was just thinking this could be the reason.
A little while back i had modified the build.prop for removing boot animation (using GN Toolkit).
In fact i have been trying to restore the backup of the build.prop file back, but haven't been able to.
Any ideas on how to restore everything back to stock (i even tried that option of downloading google stock image IMM76D from the toolkit) and flashed it, but I still get the exclamation point when I boot into recovery...
kgdg said:
hmm i was just thinking this could be the reason.
A little while back i had modified the build.prop for removing boot animation (using GN Toolkit).
In fact i have been trying to restore the backup of the build.prop file back, but haven't been able to.
Any ideas on how to restore everything back to stock (i even tried that option of downloading google stock image IMM76D from the toolkit) and flashed it, but I still get the exclamation point when I boot into recovery...
Click to expand...
Click to collapse
That android with the exclamation point is the stock recovery, press volume up and power button at the same time a few times and the recovery menu should pop up
Sent from my Galaxy Nexus using xda premium
Look at the "flash" link in my sig to return to stock, and the "update" link to update to 4.1.1 from 4.0.4.
Sent from my Galaxy Nexus using Tapatalk 2
efrant,
I will follow the instructions on the flash link to go completely stock, I assume that will fix the red exclamation issue.
All i want is to put the device in a state that will be able to download the official JB (and future) updates and install them.
I thought I was already in that position when I got the OTA earlier today and downloaded it, but when i tried to install it, it booted into recovery and gave me that red mark, so I was assuming that the issue is with the (stock) recovery image.
Would that be a correct assumption?
negrobombon,
I understand that and that works and have tried that. But I am trying to understand if this exclamation mark showing up in recovery is the cause for the OTA to not install?
Or is it unrelated? It sounds like it is unrelated as people are saying the exclamation mark just means that it is stock recovery.
That seems to be proven since I followed the link erfant posted to go completely back to stock and after all that, I still have that exclamation mark in the recovery.
It really doesn't matter if I can confirm that is NOT the cause for my OTA to not install.
Now I am completely stock and looks like I will have to wait again for the OTA to show up (I just want to OTA, not apply the update manually as I want to test if this time around, the OTA installs correctly)...
efrant said:
Look at the "flash" link in my sig to return to stock, and the "update" link to update to 4.1.1 from 4.0.4.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
efrant,
I would just like to say, what a fantastic job you did on the steps in that guide.
It's definitely my preferred way of doing it instead of a toolkit blackbox method where you don't know what it is doing and it's great for when it works, but if it doesn't...you have no idea how to troubleshoot and don't know which step it failed on or what the error is.
Now, have to go back to #*#*checkin*#*# to see if that will speed up my OTA (not really sure if that helps at all). It seems like that does the same thing as Settings->About->System Update->Check Now...
I have a sprint phone and am trying to update my phone to 4.2.2. A few months ago when I first got the phone I had attempted to root it. Long story short, it totally didn't work (i accidentally installed verizon root), had to use odin to reinstall my radios and whatnot. In the end, I decided to just not root my phone.
However, I think i am screwing my phone up to the point that it won't update. Whenever I try to let it update, it goes into (what i imagine) is the recovery mode where it shows a picture of the android bot with a red alert sign as if there is an error. Furthermore, I went in to fastboot and tried to go to recovery but can't (it shows that same android with it's front open and an error sign on it).
I am not even sure where to start here. Any advice? I tried to reinstall my recovery using the nexus toolkit but that didn't work.:crying:
do this: http://forum.xda-developers.com/showthread.php?t=1626895
I looked into updating my 2013 Nexus 7 to Android L yesterday and hit a couple snags. I was using a guide over on nexus7root, mainly for the files and command lines.
I used Nexus Root Toolkit to get the proper drivers installed and to unlock the bootloader. Then I got on with installed L. Command Prompt got stuck at 'Erasing user data' for about an hour. Not a lot I could do but turn it off and try again. It doesn't want to get past that point. I give up for the evening and just try to turn the tablet back on. It gets stuck with 'Google' written on the screen and an unlocked padlock at the bottom. Won't go any further. I go back to NRT and select 'Flash stock and unroot' with 'Soft bricked/bootloop' selected. It whizzes through a little too quickly and my Nexus is still displaying the recovery screen. NRT says it might not have worked and to select 'Force flash mode' and try again. I do that but still no luck.
The tablet will now only display 2 screens: Google with unlocked padlock, or recovery.
Any ideas on what to try next?
Thanks in advance
CasuallyDressed said:
I looked into updating my 2013 Nexus 7 to Android L yesterday and hit a couple snags. I was using a guide over on nexus7root, mainly for the files and command lines.
I used Nexus Root Toolkit to get the proper drivers installed and to unlock the bootloader. Then I got on with installed L. Command Prompt got stuck at 'Erasing user data' for about an hour. Not a lot I could do but turn it off and try again. It doesn't want to get past that point. I give up for the evening and just try to turn the tablet back on. It gets stuck with 'Google' written on the screen and an unlocked padlock at the bottom. Won't go any further. I go back to NRT and select 'Flash stock and unroot' with 'Soft bricked/bootloop' selected. It whizzes through a little too quickly and my Nexus is still displaying the recovery screen. NRT says it might not have worked and to select 'Force flash mode' and try again. I do that but still no luck.
The tablet will now only display 2 screens: Google with unlocked padlock, or recovery.
Any ideas on what to try next?
Thanks in advance
Click to expand...
Click to collapse
You have 2 choices.
1) Start from square 1 and try to install L again using the instructions you have or other instructions that can be found right here on XDA (i wouldnt because you arent installing the actual OTA but rather the developer version which has bugs and such and you will end up having to do number 2 when L comes out anyways.)
2) unbrick your device by reflashing it to stock. there are plenty of ways to do this, look for unbricking on the forums here and you should be ok.
Just a tip for the next time you decide to flash anything if you ever do, make a backup of your entire stock system before doing so, you can do this in the recovery that you install before flashing the new rom. It makes unbricking quite a bit easier.
metalblaster said:
You have 2 choices.
1) Start from square 1 and try to install L again using the instructions you have or other instructions that can be found right here on XDA (i wouldnt because you arent installing the actual OTA but rather the developer version which has bugs and such and you will end up having to do number 2 when L comes out anyways.)
2) unbrick your device by reflashing it to stock. there are plenty of ways to do this, look for unbricking on the forums here and you should be ok.
Just a tip for the next time you decide to flash anything if you ever do, make a backup of your entire stock system before doing so, you can do this in the recovery that you install before flashing the new rom. It makes unbricking quite a bit easier.
Click to expand...
Click to collapse
1) I can't update using the instructions as it hangs at 'Erasing user data'.
2) I've tried to unbrick and flash back to stock using NRT but it just goes back to FlashBoot and never finishes.
Dunno if I'm allowed to, but...
BUMP!!
metalblaster said:
Just a tip for the next time you decide to flash anything if you ever do, make a backup of your entire stock system before doing so, you can do this in the recovery that you install before flashing the new rom. It makes unbricking quite a bit easier.
Click to expand...
Click to collapse
You're absolutely right! Always, always make a backup/nandroid before flashing a different rom. But if you don't and like to live dangerously you should at least have the sdk installed and know how to use adb/fastboot! One thing though about restoring a backup, it does not restore the bootloader. Android L uses bootloader version 4.04 and KitKat uses 4.02. The first L preview used the same bootloader as KK but the new preview does not. I have no idea what kind of bugs or worse would result from restoring a KK nandroid onto the 4.04 bootloader. Maybe nothing but I purposely didn't try to find out if it would cause any problems. Couple nights ago I checked out the preview for maybe an hour then went back to 4.4.4. I flashed the 4.4.4 factory image using a modified flash_all batch file then restored on top of that. I guess I could have instead fastboot flashed the bootloader then went straight into recovery to install my backup. Just something to think about, bootloader versions.
CasuallyDressed said:
1) I can't update using the instructions as it hangs at 'Erasing user data'.
2) I've tried to unbrick and flash back to stock using NRT but it just goes back to FlashBoot and never finishes.
Click to expand...
Click to collapse
You said previously "The tablet will now only display 2 screens: Google with unlocked padlock, or recovery." Unlocked padlock means your bootloader is unlocked and your device now can have images flashed to it. Recovery or bootloader screen? You need to be able to get into the bootloader screen. Press and hold the volume down button, while still holding down the volume button press the power button for a few seconds release the power button and it should go into the bootloader screen. There are a couple toolkits that might help, Wug"s and One-Click Restore come to mind. I've never used them so I wouldn't be any help as far as they go. I can try to help if you want to use the sdk. Do you have the android sdk installed?
i had the same problem , i tried one click restore and it works fine
Wow don'T!!!!
CasuallyDressed said:
I looked into updating my 2013 Nexus 7 to Android L yesterday and hit a couple snags. I was using a guide over on nexus7root, mainly for the files and command lines.
I used Nexus Root Toolkit to get the proper drivers installed and to unlock the bootloader. Then I got on with installed L. Command Prompt got stuck at 'Erasing user data' for about an hour. Not a lot I could do but turn it off and try again. It doesn't want to get past that point. I give up for the evening and just try to turn the tablet back on. It gets stuck with 'Google' written on the screen and an unlocked padlock at the bottom. Won't go any further. I go back to NRT and select 'Flash stock and unroot' with 'Soft bricked/bootloop' selected. It whizzes through a little too quickly and my Nexus is still displaying the recovery screen. NRT says it might not have worked and to select 'Force flash mode' and try again. I do that but still no luck.
The tablet will now only display 2 screens: Google with unlocked padlock, or recovery.
Any ideas on what to try next?
Thanks in advance
Click to expand...
Click to collapse
Don't delete your user data before backing it up!
See WugFreshs Threads on XDA!
So I used ATGAdmin's guide here: http://forum.xda-developers.com/showthread.php?t=2381582
Used "Dead_Nexus7.bat" and it fixed me right up. Plus, I love the "Look you dumb motherf**kers" attitude he has in his video.
I appear to be all sorted anyway! Thanks to those who suggested 'One Click Restore', it set me on the right path.
My unrooted, stock Nexus 7 was on 4.4. I received an OTA notification about 5.0.1 so accepted the upgrade. After the reboot and seeing the Android with the open stomach, it fails with Error against the Android. All I can do is long power off/volume up to power off and then power on again. It then reverts back to 4.4.
After about an hour I received another 5.0.1 update, went the same process and received the same error.
Does anybody know what that could be? I guess I could factory reset the device there is nothing on the tablet that hasn't been saved in my Google account anyway.
Thanks
Wanted to say I experienced the same thing earlier today, except I didn't get an immediate second chance at the OTA. I have the wifi-only version of the N7 2013, and it is also not rooted.
Browsed around the net and various places to see if others had this issue, but no luck. Not really sure what the problem is unless the download got messed up somehow?
Same issue here. Download the update. It shows verified. Reboots, starts to flash and then the android error
Reboot and it is still 5.0
Happy to report that when I got another crack at the ota the update went fine. Still confused as to what could've caused the problem though.
Well it killed my N7 it seems. Got the error message then shut itself down. Now it won't boot up no matter what I do. Any ideas?
My update just stays in the notification area. After the failure I just power the tablet off with long press of the power button and volume up.
I am stock, rooted and unlocked. I used the WUGS toolkit to flash the stock recovery assuming that this is all that was necessary for the OTA to be recognized and accepted. After flashing back to stock recovery, I rebooted the device and told the OTA to update. It starts going through the process and dies with "Error!" and reboots back into 5.0. I tried using the WUGS toolkit to ADB sideload, but I have not been able to get it to work. At some point, it actually got into the Stock Recovery, but ADB wasn't able to contact the device (that only happened once). Every other time, it goes through the script and shows the Android on it's back with the exclamation mark, and below it says "no command."
The device works, but it's frustrating. I wish there was just a way to fastboot the OTA, or just do it via TWRP.
I'm anxious to hear how others work through this, as it appears that I'm not the only one.
kendoori said:
I am stock, rooted and unlocked. I used the WUGS toolkit to flash the stock recovery assuming that this is all that was necessary for the OTA to be recognized and accepted. After flashing back to stock recovery, I rebooted the device and told the OTA to update. It starts going through the process and dies with "Error!" and reboots back into 5.0. I tried using the WUGS toolkit to ADB sideload, but I have not been able to get it to work. At some point, it actually got into the Stock Recovery, but ADB wasn't able to contact the device (that only happened once). Every other time, it goes through the script and shows the Android on it's back with the exclamation mark, and below it says "no command."
The device works, but it's frustrating. I wish there was just a way to fastboot the OTA, or just do it via TWRP.
I'm anxious to hear how others work through this, as it appears that I'm not the only one.
Click to expand...
Click to collapse
Tried sideloading the factory image?
Sent from my Nexus 5 using XDA Free mobile app
Since my N7 is a secondary device (my main device is a N5 which received the Lollipop upgrade fine), I might just leave it on KitKat rather than muck around with sideloading Lollipop. KitKat works fine for me at the moment. But it's really annoying that a stock N7 cannot get an OTA upgrade and goes into an Android error state.
I was on 5.0 rooted with TWRP and got the same error trying to take the OTA. So I downloaded the rooted rom found here http://forum.xda-developers.com/nex.../rom-factory-stock-rooted-rom-lrx22c-t2960745 , used Wugfresh's NRT 1.9.9 to update the bootloader, and then dirty flashed the 5.0.1 rom with TWRP. Painless and fast with no loss of data or anything.
Same problem! I managed to workaround the issue by using fastboot replacing system.img boot.img recovery.img with stock ones!
chrismast said:
Tried sideloading the factory image?
Click to expand...
Click to collapse
Are you suggesting that I blow away what's installed and just update by doing a fresh install? would prefer to not do that.
I did download razor-lrx21p-factory-ba55c6ab.tgz (the 5.0 factory image) and extract the recovery.img for it, and fastboot flashed it, and the no matter what I end up in the Recovery bootloop with the android on it's back and exlamation point and "No command."
kendoori said:
Are you suggesting that I blow away what's installed and just update by doing a fresh install? would prefer to not do that.
I did download razor-lrx21p-factory-ba55c6ab.tgz (the 5.0 factory image) and extract the recovery.img for it, and fastboot flashed it, and the no matter what I end up in the Recovery bootloop with the android on it's back and exlamation point and "No command."
Click to expand...
Click to collapse
If I am not wrong, there is a way of flashing the factory image without wipe by modifying one of the scripts, never did it though myself.
Sent from my Nexus 5 using XDA Free mobile app
Turns out I was using the wrong key sequence for Recovery to get past that screen. Holding down Vol Up + Power for 3 seconds, then just pressing Power gets you to the right place. Am still having issues with OTA, as the system believes something was altered (install-recovery.sh). Others are saying that the way to do this is as described here: http://forum.xda-developers.com/showpost.php?p=57271130&postcount=423
kendoori said:
Turns out I was using the wrong key sequence for Recovery to get past that screen. Holding down Vol Up + Power for 3 seconds, then just pressing Power gets you to the right place. Am still having issues with OTA, as the system believes something was altered (install-recovery.sh). Others are saying that the way to do this is as described here: http://forum.xda-developers.com/showpost.php?p=57271130&postcount=423
Click to expand...
Click to collapse
jep, that's what I was saying earlier: factory image. For the 5.0.1 update you only need system.img and boot.img, at least that way it worked for me and my N7 2013 is running fine so far.
I dont get 5.0 on my nexus 7 2013, wifi, 32 Gb(flo, ktu84p)
I had stock rooted Rom, u Used tweaks like softkeiz etc. then I unrooted, locked boot loader and flashed stock recovery. Android lollypop rollout was about 2 months ago, but I don't get 5.0 ota. Now I'm running 4.4.4 stock rom , locked boot loader and I unrooted it with super user unroot option. Can somebody help me why I don't get my ota?? Thanks ^^
I know that's wrong thread, I didn't find thread for my question .
I just got my update!!!!!
German8835 said:
I had stock rooted Rom, u Used tweaks like softkeiz etc. then I unrooted, locked boot loader and flashed stock recovery. Android lollypop rollout was about 2 months ago, but I don't get 5.0 ota. Now I'm running 4.4.4 stock rom , locked boot loader and I unrooted it with super user unroot option. Can somebody help me why I don't get my ota?? Thanks ^^
I know that's wrong thread, I didn't find thread for my question .
Click to expand...
Click to collapse
Oh man! It's crasy, I was waiting so long, and exactly on this day when I write to thread I get my update!
EDIT: Never mind. I tried to do it via sideload, and it complained that the /System was too full. I rebooted, compared it to another Nexus 7, and the size was the same and free space was the same (and the other one updated fine). for the heck of it, I tried sideloading again, this time I formatted the cache first (no reason, just a thought) and that time it sideloaded correctly. So I'm up to date now... Weird.
I have the same issue. did a factory image install to 5.0. Now I get the update notification for 5.0.1 (as expected).
When I try to install it, it reboots, then I get "error" - have tried 3 times now. A reboot gets me back in the tablet, but am still at 5.0. This is my kid's tablet, so I have no need to root it or install a new rom, just want the dumb update to work correctly...
Jason
JasonJoel said:
EDIT: Never mind. I tried to do it via sideload, and it complained that the /System was too full. I rebooted, compared it to another Nexus 7, and the size was the same and free space was the same (and the other one updated fine). for the heck of it, I tried sideloading again, this time I formatted the cache first (no reason, just a thought) and that time it sideloaded correctly. So I'm up to date now... Weird.
I have the same issue. did a factory image install to 5.0. Now I get the update notification for 5.0.1 (as expected).
When I try to install it, it reboots, then I get "error" - have tried 3 times now. A reboot gets me back in the tablet, but am still at 5.0. This is my kid's tablet, so I have no need to root it or install a new rom, just want the dumb update to work correctly...
Jason
Click to expand...
Click to collapse
That is indeed strange...If you are pure stock it should work I guess? You could still try to sideload the 5.0.1 as well (did the same as I did not want to wait for OTA). You can do it without full wipe, just wipe cache in the process. (You need only to flash system and boot.img, wipe cache, reboot). Nevertheless let me know if you get the "error" solved, would be interested to know.
newkydawg said:
I was on 5.0 rooted with TWRP and got the same error trying to take the OTA. So I downloaded the rooted rom found here http://forum.xda-developers.com/nex.../rom-factory-stock-rooted-rom-lrx22c-t2960745 , used Wugfresh's NRT 1.9.9 to update the bootloader, and then dirty flashed the 5.0.1 rom with TWRP. Painless and fast with no loss of data or anything.
Click to expand...
Click to collapse
I was skeptical but this worked when I was having a similar problem to the OP Thanks. I have no idea how 5.0.1 is different though.
Hello XDA Members,
Whelp... I've tried everything. I followed this how to on returning to stock, I've tried THIS method of returning to stock, I've tried them all and I am fairly certain everything was done correctly. I have reflashed the stock bootloader, and flashed the stock ROM image from google themselves and I have relocked the bootloader and am still having this problem.
I can flash stock images supplied from Google with no issue, but the big issue here seems to be when I try to install any OTA update, specifically (in this instance) the Marshmellow update.
I always hit "Reboot and Install". It always shuts off and gives me the little android robot with his antennas wiggling, and it shows a progress bar while saying "Installing system update..." and about 1/4 into doing so, everything stops, the Android robot is now laying down with his little chest open, and a big red exclamation icon is popping out, and under him it just says "Error!"
And that's it. The tablet will just stall there for about a minute and then reboot itself. The OTA will re-download itself and I'm back to square one.
I have no idea why it's doing this, or if I did something wrong in the unrooting process, or how to make this stop.
Please help T_T
EmperorOfNyte said:
Hello XDA Members,
Whelp... I've tried everything. I followed this how to on returning to stock, I've tried THIS method of returning to stock, I've tried them all and I am fairly certain everything was done correctly. I have reflashed the stock bootloader, and flashed the stock ROM image from google themselves and I have relocked the bootloader and am still having this problem.
I can flash stock images supplied from Google with no issue, but the big issue here seems to be when I try to install any OTA update, specifically (in this instance) the Marshmellow update.
I always hit "Reboot and Install". It always shuts off and gives me the little android robot with his antennas wiggling, and it shows a progress bar while saying "Installing system update..." and about 1/4 into doing so, everything stops, the Android robot is now laying down with his little chest open, and a big red exclamation icon is popping out, and under him it just says "Error!"
And that's it. The tablet will just stall there for about a minute and then reboot itself. The OTA will re-download itself and I'm back to square one.
I have no idea why it's doing this, or if I did something wrong in the unrooting process, or how to make this stop.
Please help T_T
Click to expand...
Click to collapse
I have the same problem
I actually was about to start a new thread near exact to yours.
EmperorOfNyte said:
Hello XDA Members,
Whelp... I've tried everything. I followed this how to on returning to stock, I've tried THIS method of returning to stock, I've tried them all and I am fairly certain everything was done correctly. I have reflashed the stock bootloader, and flashed the stock ROM image from google themselves and I have relocked the bootloader and am still having this problem.
Click to expand...
Click to collapse
You say you can flash stock images OK - so why not just flash the latest Marshmallow stock image? Why mess around with trying to install updates? Why did you re-lock the bootloader? Follow directions here, then flash the newest image under "razor" for Nexus 7 [2013] (Wi-Fi)"
https://developers.google.com/android/nexus/images?hl=en
airberger said:
You say you can flash stock images OK - so why not just flash the latest Marshmallow stock image? Why mess around with trying to install updates? Why did you re-lock the bootloader? Follow directions here, then flash the newest image under "razor" for Nexus 7 [2013] (Wi-Fi)"
https://developers.google.com/android/nexus/images?hl=en
Click to expand...
Click to collapse
I don't want to flash it manually, and I want it to be able to install OTAs normally because I'm trying to sell it to a friend and don't want them to constantly to be seeing a "Update Available" notification that wont go away.
Nothing? No ideas? ......Anyone?
airberger said:
You say you can flash stock images OK - so why not just flash the latest Marshmallow stock image? Why mess around with trying to install updates? Why did you re-lock the bootloader? Follow directions here, then flash the newest image under "razor" for Nexus 7 [2013] (Wi-Fi)"
https://developers.google.com/android/nexus/images?hl=en
Click to expand...
Click to collapse
I tried this using ADB sideload, got "signature error"??