I haven't updated my Shield for at least a year as a while back there seemed to be some issues with the latest firmware that people were complaining about, is there any reason I shouldn't now update to the latest?
I did the update and bricked my shield had to take out ssd and re-flash with saved image
Just by taking the update you bricked your shield? I have the 2017 with an SSD....curious how that happened?
Im now flashing it using pc.....Im burning the image to the ssd using my pc using sata
Cool. Glad you're getting it working. But I was asking if it bricked just by taking the update. Don't want to update if that is what may happen
Related
Rooted
Stock Rom
Backed Up Stock w/ Rom Manager V5.5.1.5
If you need more info, please tell me how to get it to you. I'm a noob @ mobile mod stuff...
Today January 17, 2013 my Phone said I had an OTA update, it will not tell me what the update is.
Is this the 4.0 update?
Will this remove my root?
Is it true this update will remove flash player?
how long have you had your phone? 2.3.x is old, the t989 got has been on 4.0.x for some time now (4.04 is the current factory rom), you probably have a few updates to do!
SGH-T989 FW2.3.6 OTA update
I believe We got our phones June 2012. They came with Uvlke1 I think then updated to UVLDE around November 2012...
I wouldnt mind 4.x.x, You can use Xbox360 SmartGlass.
Does Adobe Flash Player matter anymore?
Do I need to unroot to update ota or just click start?
Will updating remove my root SU?
How hard is it to ReRoot when i've finished updating?
cliqrootnoob said:
I believe We got our phones June 2012. They came with Uvlke1 I think then updated to UVLDE around November 2012...
I wouldnt mind 4.x.x, You can use Xbox360 SmartGlass.
Does Adobe Flash Player matter anymore?
Do I need to unroot to update ota or just click start?
Will updating remove my root SU?
How hard is it to ReRoot when i've finished updating?
Click to expand...
Click to collapse
Yes
No, as long as u didn't debloat
Not the supersu app, but u will lose root, have to reflash in cwm
Its not
I clicked it.... smh, it was some 5 second update. have no clue what it did...
So now I did my wifes phones with kies (unrooted) all went well, update it to 4.0.4 ....
What is debloat?
Debloat if I'm not wrong. Its when they take all the T-Mobile things out that you don't actually need in the phone.
Sent from Land Of Ooo.
My wife is in the sane boat as you. She's pure stock. Has had it since the free phone sale last year in T-Mobile. She is still on your firmware. GB 2.3.6 with the T989UVLDG baseband. She's had 3 OTAs since shes had it but remains on GB. Don't understand why. Her last OTA was the 17th as well. No idea what it was for since it took the longest of the 3 and left her on GB.
Sent from my SGH-T989 using Tapatalk 2
As the title states, has anyone's 2013 n7 bricked after the 5.0.2 update when flashing a factory image instead of the OTA? Mine bricked after taking the 5.0.1 OTA, but i now have it back from Asus after repair and am wanting to flash the factory image to 5.0.2. However, if anyone has experienced bricking as a result of this (or 5.0.1 or 5.0) being flashed and not just the OTA, which we know is bricking devices, then I will stick with 4.4.4 for now.
Thanks
You can not brick a Nexus 7 unless you somehow screw up the bootloader and can no longer enter the bootloader.
khaytsus said:
You can not brick a Nexus 7 unless you somehow screw up the bootloader and can no longer enter the bootloader.
Click to expand...
Click to collapse
Well then some form of that must be happening due to or in very strange coincidence with the 5.0, 5.0.1, and 5.0.2 updates - just ask those of us whose tablets turned off only to turn on and be stuck at the google logo with so far zero solution for fixing it other than a hardware replacement. My tablet was at ASUS's repair factory for almost a month and had the motherboard replaced. This was after a "successful" OTA update to 5.0.1 that worked for a few days and then died. This has happened more than just infrequently to many members on here recently.
So what I would like to know is is anyone experienced the same "successful update" and then a few days later a dead tablet via factory image flashingof 5.0+. We already know that taking the OTA to 5.0+ might be a problem, and before I flash up to 5.0.2 I'd like to hear if anyone did a manual factory image flash and still had the die a few days later issue, despite not going via OTA.
Norcalz71 said:
Well then some form of that must be happening due to or in very strange coincidence with the 5.0, 5.0.1, and 5.0.2 updates - just ask those of us whose tablets turned off only to turn on and be stuck at the google logo with so far zero solution for fixing it other than a hardware replacement. My tablet was at ASUS's repair factory for almost a month and had the motherboard replaced. This was after a "successful" OTA update to 5.0.1 that worked for a few days and then died. This has happened more than just infrequently to many members on here recently.
So what I would like to know is is anyone experienced the same "successful update" and then a few days later a dead tablet via factory image flashingof 5.0+. We already know that taking the OTA to 5.0+ might be a problem, and before I flash up to 5.0.2 I'd like to hear if anyone did a manual factory image flash and still had the die a few days later issue, despite not going via OTA.
Click to expand...
Click to collapse
I don't understand the obstinance regarding official LP flashing. OTA has been pulled from the shelf, lots have killed their devices with it, so it's obvious something seriously wrong is going on. I've been flashing CM and other custom roms derived from LP without problems. Why insist on incantations? This is not the first time Asus screws up with its firmwares! LP ain't nothing special that's worth it.
graphdarnell said:
I don't understand the obstinance regarding official LP flashing. OTA has been pulled from the shelf, lots have killed their devices with it, so it's obvious something seriously wrong is going on. I've been flashing CM and other custom roms derived from LP without problems. Why insist on incantations? This is not the first time Asus screws up with its firmwares! LP ain't nothing special that's worth it.
Click to expand...
Click to collapse
So you are saying LP Roms/factory images should be just fine, provided they don't go OTA? I'm sure most are, my concern is if anyone has experienced a failure hours/days after flashing to LP
Norcalz71 said:
So you are saying LP Roms/factory images should be just fine, provided they don't go OTA? I'm sure most are, my concern is if anyone has experienced a failure hours/days after flashing to LP
Click to expand...
Click to collapse
Given previous experiences with Asus JB on another model, I'd avoid anything "official" like the plague, and wait till major bugs are swatted. Clearly, I'm not saying "LP Roms/factory images should be just fine." But I've been flashing custom roms based off LP, and nothing out of the ordinary has happened. They work fine. What I don't get is people would insist on flashing the crappy OTAs Asus has been putting out in the face of so much bricking.
Asus doesn't put out updates for the N7; Google does.
Telyx said:
Asus doesn't put out updates for the N7; Google does.
Click to expand...
Click to collapse
I don't see the difference. Just because Google funded and marketed the device doesn't make it less Asus. An Asus is an Asus is an Asus, whether you buy it at Staples or in China. I seriously doubt the firmwares are 100% (or 10% for that matter) Google unless one can prove to the world otherwise.
I haven't bricked mine, and I manually updated using the 5.0.1 (and then 5.0.2) image on Google's site. However, I also have an unlocked boot loader (It was unlocked about an hour after we got it home, and hasn't been locked since) and modified /system partition. I have always manually updated the software images from fastboot.
You're saying Asus makes aosp? No. Google makes the software for nexus devices.
Asus assembled the hardware. Google makes the software (aside from proprietary drivers, of which Asus made only audio and "sensors").
Asus has very little to do with the n7 aside from the fact that they put it together.
jshamlet said:
I haven't bricked mine, and I manually updated using the 5.0.1 (and then 5.0.2) image on Google's site. However, I also have an unlocked boot loader (It was unlocked about an hour after we got it home, and hasn't been locked since) and modified /system partition. I have always manually updated the software images from fastboot.
Click to expand...
Click to collapse
Mine will remain unlocked from now on. I took it from 4.4.2 back to 4.4.4 (since after repair it was back to original and wiped) via fastboot, and will probably wait awhile longer to update it via fastboot to 5.0.2. No more OTA for me though.
My beloved N7 2013 fell victim to the eMMC-nuking 5.0 (unsure about exact version) OTA update last year. I put off replacing the motherboard, as I had already bought a new tablet. Lately, though, my N7 itch returned. I was able to successfully replace the motherboard, but the replacement I purchased was also Kingston...much to my chagrin.
Anyways, I updated the new motherboard to 4.4.4 via OTA, and forewent the next OTA (5.0 OTA update). Things are smooth, and my tablet has been resurrected.
My question, then, is two-fold. First, is the 6.0.1 stock update worth the hassle of running a clean install? And second, will I run into the same problem that killed my N7 the first time (update nukes eMMC)?
I tried to find a thread where this has been discussed, but I must not fully understand searching for things on this site. Thanks for your help!
Amazing how you'd consider throwing good money after bad. If you insist on everything stock, you assume the risk, random though it might be with MM. There are plenty of custom roms that mirror stock almost totally, why the insistence? What's so sacred about it?
hekat0n said:
My beloved N7 2013 fell victim to the eMMC-nuking 5.x OTA. I was able to successfully replace the motherboard. I updated to 4.4.4 via OTA, and forewent the next OTA (5.0 OTA update). Is the 6.0.1 stock update worth running a clean install? Will I run into the same problem that killed my N7 before? I tried to find a thread where this has been discussed, but I must not fully understand searching for things on this site. Thanks for your help!
Click to expand...
Click to collapse
There was a known write loop error in one of the 5.x OTA updates that baked boards, but the Kingston boards are generally known to be unreliable among the three common boards for razor. Long story short, you have nothing to lose by updating to the latest OTA, 6.x adds nice features, runs well, and has the latest security updates and compatibility with the latest popular apps. Bricks on 6.x OTAs seem random, and are most likely related to instances of hardware failure on individual devices that developed over long periods of device use, than from a single software update causing or contributing to a hardware failure.
The users here have been contributing to a thread regarding this issue, it can be found here.
It's worth mentioning that instances of eMMc failure on devices running custom ROMs are far fewer in number than instances of bricks on stock devices.
Hi, hoping I could get some help.
I just got a huawei watch and cannot get it to update. It is on version 1.3xxxx. When I try to update it, it says it's already the latest version. Hopefully I'm just overlooking something very obvious as right now I feel stuck in the mud. Thanks for your help in advance!
Same issue here! Own the watch from 4 days now.
Same for me
An idea ?
Ok, i updated my watch with success. I believe that the OTA don't work because my watch is a refurbished one and the OTA system think that my watch is already up to date.
Here's how to update, it's easy:
You have to do an adb sideload of the OTA files:
Tutorial here:
http://phandroid.com/2016/03/02/huawei-watch-marshmallow/
You have to flash this file first if you are stuck in LCB43B:
http://android.googleapis.com/packa...866b47.signed-sturgeon-MEC23L-from-LCB43B.zip
After the reboot, continue with:
https://android.googleapis.com/pack.../6bae896422cb963c01b479eea9838f1b1b0d705e.zip
After that update the OTA worked normally.
Hope this help.
Thanks for starting this thread! I think all the people stuck on older firmware are Canadians with refurbs from newegg (incl me)? However, I am not sure how being refurb has anything to do with it.
My watch did update once from the version it came with, but kept on saying its up-to-date after that. I guess flashing stock image is the only way to go.
jainanshal said:
Thanks for starting this thread! I think all the people stuck on older firmware are Canadians with refurbs from newegg (incl me)? However, I am not sure how being refurb has anything to do with it.
My watch did update once from the version it came with, but kept on saying its up-to-date after that. I guess flashing stock image is the only way to go.
Click to expand...
Click to collapse
The issue with flashing the stock image is that you have to unlock the bootloader, and after that it seems that you loose the warranty.
Better flashing OTA if you want to stay stock. I bought my refurb from newegg.ca too.
ndompierre said:
Ok, i updated my watch with success. I believe that the OTA don't work because my watch is a refurbished one and the OTA system think that my watch is already up to date.
Here's how to update, it's easy:
You have to do an adb sideload of the OTA files:
Tutorial here:
http://phandroid.com/2016/03/02/huawei-watch-marshmallow/
You have to flash this file first if you are stuck in LCB43B:
http://android.googleapis.com/packa...866b47.signed-sturgeon-MEC23L-from-LCB43B.zip
After the reboot, continue with:
https://android.googleapis.com/pack.../6bae896422cb963c01b479eea9838f1b1b0d705e.zip
After that update the OTA worked normally.
Hope this help.
Click to expand...
Click to collapse
Same problem.
Then I took your advice and it worked out great, and without changing the bootloader, thank you so much ndompierre :good::victory:
I got my newegg refurb yesterday and could not force the OTA despite resetting and checking multiple times. This afternoon it updated to marshmallow.
Each time time it reboots, I check for updates. I am currently receiving my fourth update of the day.
I guess each security patch has to be downloaded separately. I'm up to August so far..
Ok long and short; reverted to MM base, wiped clean, accepted the OTA for 7.0. Did not get an error message in stock recovery while it updated. It finished went to reboot and nothing. When I plug it in , led flashes. unplug it and led turns off. Plug in and out of computer. And the PC recognizes something is plugged in but can't find any hardware changes in device manager. Not sure what I ca try next????
Attempted
fast boot - no device
Adb - no device
Computer - makes sound when plugged or unplugged but not in window explorer
Rsd lite- no device.
I feel like the battery died while writing battery charging files or something???
Willing to try anything
Thanks guys. Matt
RETUS xt1635-02 / sec. patch either August or November 2016 mm 6.0.1
It's a hard brick. Sad, there is nothing you can do to fix it. Except You will need to send it back to the manufacturer or change the logic board.
The reason of the brick is accepting 7.0 ota after downgrading to MM.
Yousvel said:
It's a hard brick. Sad, there is nothing you can do to fix it. Except You will need to send it back to the manufacturer or change the logic board.
The reason of the brick is accepting 7.0 ota after downgrading to MM.
Click to expand...
Click to collapse
Yup, can confirm. Sorry OP.
Sent from my XT1635-02 using Tapatalk
Another one. Sucks bro...
The issue did indeed come from downgrading and then accepting the OTA. When you downgrade firmware on a moto phone you can NOT flash the downgraded bootloader. It can cause problems like this.
That's what I figured,wasn't worried since I was on November security patch. why is it that I was able to do so a couple months ago? Was on MM ota'd then custom rom and when I had problems I flashed MM and ota'd back to 7.0? I
tpx00 said:
That's what I figured,wasn't worried since I was on November security patch. why is it that I was able to do so a couple months ago? Was on MM ota'd then custom rom and when I had problems I flashed MM and ota'd back to 7.0? I
Click to expand...
Click to collapse
It was possible with any patch before the April one. Since April, no dice.
FanDroid09 said:
Another one. Sucks bro...
The issue did indeed come from downgrading and then accepting the OTA. When you downgrade firmware on a moto phone you can NOT flash the downgraded bootloader. It can cause problems like this.
Click to expand...
Click to collapse
If i downgrade without flashing bootloader and gpt, will I be able to receive and install OTA?