Related
Hi Guys,
Not sure if much can be done, so before I flashed a rom for 5.1.1, I decided to flash the required, firmware 2.9.710.x, but before flashing that, I re-locked my bootloader, as I have s-on. Before that, I was trying to get the OTA to work but it didn't as I had mounted system as r/w. So I had stock recovery, s-on and relocked bootloader. After I flashed the firmware, I could not unlock the bootloader as there is some new developer setting that I am required to enable. BUT the I am still on old 5.0 ROM that will not boot anymore and is stuck on the splash screen - I've tried wipe cache and factory reset. I have an RUU for 1.32 which I cannot use because now I have 2.9.710.x firmware. I've also tried to sideload the OTA but that will not work because system was mounted r/w
Is there anything I can do to get it to work? I feel like I've tried all avenues, but if there is something you guys think I can do to make it work again, I'd be over the moon!
anshuashmeet said:
Hi Guys,
Not sure if much can be done, so before I flashed a rom for 5.1.1, I decided to flash the required, firmware 2.9.710.x, but before flashing that, I re-locked my bootloader, as I have s-on. Before that, I was trying to get the OTA to work but it didn't as I had mounted system as r/w. So I had stock recovery, s-on and relocked bootloader. After I flashed the firmware, I could not unlock the bootloader as there is some new developer setting that I am required to enable. BUT the I am still on old 5.0 ROM that will not boot anymore and is stuck on the splash screen - I've tried wipe cache and factory reset. I have an RUU for 1.32 which I cannot use because now I have 2.9.710.x firmware. I've also tried to sideload the OTA but that will not work because system was mounted r/w
Is there anything I can do to get it to work? I feel like I've tried all avenues, but if there is something you guys think I can do to make it work again, I'd be over the moon!
Click to expand...
Click to collapse
Never relock if your phone is not 100 % stock. Otherwise it won't boot. Besides there are already numerous post written by people that made the same mistake as you did. Even if your phone could boot you wouldn't be able to enable the OEM Unlock option since it's not implemented in the 1.XX roms and by flashing the firmware you do not update your rom.
I guess the only possibility to recover your phone is using this RUU service.
Just because I'm curious: Why didn't you use one of the backups that are provided here?
Flippy498 said:
Never relock if your phone is not 100 % stock. Otherwise it won't boot. Besides there are already numerous post written by people that made the same mistake as you did. Even if your phone could boot you wouldn't be able to enable the OEM Unlock option since it's not implemented in the 1.XX roms and by flashing the firmware you do not update your rom.
I guess the only possibility to recover your phone is using this RUU service.
Just because I'm curious: Why didn't you use one of the backups that are provided here?
Click to expand...
Click to collapse
Thanks for your reply!
I've submitted an enquiry form to them. Didn't know that service existed. Hopefully they have the RUU file that I need.
I did download the stock backup file from that link but I thought before I give it a go, I'll try and get an OTA and get an official update. That failed so I decided to flash the firmware before going to the latest rom. Forgetting I just locked my bootloader with stock recovery, completely unaware of this 5.1 developer option issue. My fault for not doing research, but I didn't know such issue could exist as for the last few years, I haven't had an issue like this. Normally issues occur if I flash a newer ROM without firmware so was trying to avoid that.
Krassermensch's Firmware Update Tool
My situation:
I'm too young to buy the Sunshine App to set my device S-Off but I want to update my device's firmware every time a firmware update's available. Since I compile ROMs and cannot do that via OTA updates the only acceptable way for me is to install signed firmwares in a locked bootloader. After doing that manually I thought I should write a tool that installs the right firmware for your device automatically. As I'm already running the latest firmware on my device after doing the procedure manually I cannot test if the flash part works correctly. Anyway, I achieved to read out the CID as well as the current firmware version and my tool reports that I'm running the latest firmware version I integrated for my device what's correct. So this part works well.
How the tool works:
The tool asks you if you've already installed the HTC USB drivers on your computer. If you haven't you can install it easily using my tool. After that the tool explains you how to set up your phone to be detected by the computer. Then it checks which device you have and checks which firmware's currently installed on it. Right after that the tool installs all the firmwares newer than the one that's currently installed on your phone one after another until the latest firmware my tool is shiped with runs on your device. The procedure doesn't wipe your data since signed firmware-updates are installed.
Requirements:
- An HTC 10
- A computer running windows
- An internet connection
- An unlocked bootloader
- An installed TWRP
Who is this tool for?
All the people who can't or don't want to set their device S-Off while running a non-stock ROM.
Why should I use this tool?
- It updates your firmware to the latest one available for your device automatically
- It doesn't wipe your storage
- You don't need to be S-Off
Download
https://www.androidfilehost.com/?fid=745425885120704223
When the file is downloaded just extract it on your Windows computer and run the batch file. Everything else will be explained.
Important to know
Your boot and recovery partitions will be replaced by the stock ones so after successfully updating your firmware you need to reflash TWRP as well as your Boot partition.
This process is performed automatically now. No need to do that manually.
Tools using ADB just like mine may interfere with other tools that also use ADB. Make sure all these tools are disabled.
Now I need your feedback to be able to optimize the tool! I'll add new firmwares from time to time. I'm looking forward to your reviews
GitLab
https://gitlab.com/Feulner/Firmware-Update-Tool-HTC10
If you like my work consider a donation to support me in financing computer-components which are meant to replace the defect ones in my broken PC.
If you donate you'll donate to my father who will gimme the money. Thank you really much!
This works with unsigned firmware?
Good job, though irrelevant to me
xunholyx said:
This works with unsigned firmware?
Good job, though irrelevant to me
I would guess that you would have to have matching CID and MID of course.
Click to expand...
Click to collapse
No no, not unsigned firmware. I'll explain it more detailed tomorrow or so. The tool just checks your device's CID as well as your device's current firmware version and updates it to the most current firmware version I integrated in my tool. If your firmware is very old the tool also updates again and again until you have the lässt firmware automatically.But it uses signed firmware packages. The biggest advantage is that it should work fully automatic. Try it out and let me know what you think. I go to bed now...
krassermensch said:
No no, not unsigned firmware. I'll explain it more detailed tomorrow or so. The tool just checks your device's CID as well as your device's current firmware version and updates it to the most current firmware version I integrated in my tool. If your firmware is very old the tool also updates again and again until you have the lässt firmware automatically.But it uses signed firmware packages. The biggest advantage is that it should work fully automatic. Try it out and let me know what you think. I go to bed now...
Click to expand...
Click to collapse
I'm s-off since the day after I got my phone, so.......
It sounds like a great idea. I'm sure lot of people will appreciate this. If it does work like you say, WAY better than going back to stock.
xunholyx said:
I'm s-off since the day after I got my phone, so.......
It sounds like a great idea. I'm sure lot of people will appreciate this. If it does work like you say, WAY better than going back to stock.
Click to expand...
Click to collapse
Since when do you have to go back to stock to "fastboot flash zip some_firmware.zip" (as this tool does)?
--beaups
Hm sounds good, but i wont use it until we have some more information what it actually does.
As far as i know, theres no way to just update your firmware with signed zips without partly wiping your device. I had to reflash Viper10 (or restore a nandroid backup) the last time i updated my firmware, cause boot and recovery partitions got replaced. Not completely sure if this affects stock devices, it may work there, but not for devices which are modified with a custom ROM. For this you need a NoWipe firmware from sneakyghosts thread, but these cant be flashed while s-on.
So please explain in more details what your tool does, of course when youve got your sleep .
It most likely flashes firmware zips from OTA updates since those do not wipe the device. He already said it does that, he said if you're on a very old firmware it will keep updating your firmware progressively until you're on the latest version. So if you've never updated before, and there have been three updates since then, the tool will flash the firmware zip of each OTA one after the other.
Updated the main post, hopefully everything's clear now. I need your reviews now. I'm also thinking about an automatic bootloader lock with backup solution so you don't need to lock your bootloader manually and also don't lose your data partition.
Why it doesn't work with unlocked bootloader?
CroCop18 said:
Why it doesn't work with unlocked bootloader?
Click to expand...
Click to collapse
I didn't try but normally your HTC 10 would block the installation if the bootloader is unlocked. Could you try it out and report. It's a bit hard to try it out by myself currently... It will most probably report that your new firmware's flashed but it actually will not be flashed after that if your bootloader's unlocked. If it's flashed anyway it'd be perfect since I'd not have to make a backup solution in that case. But I guess that the 10 isn't different to the M9 for example when it comes to firmware flashing. I read that you can have an unlocked bootloader if your device is S-Off but those are things I haven't been able to try out so far...
krassermensch said:
I didn't try but normally your HTC 10 would block the installation if the bootloader is unlocked. Could you try it out and report. It's a bit hard to try it out by myself currently... It will most probably report that your new firmware's flashed but it actually will not be flashed after that if your bootloader's unlocked. If it's flashed anyway it'd be perfect since I'd not have to make a backup solution in that case. But I guess that the 10 isn't different to the M9 for example when it comes to firmware flashing. I read that you can have an unlocked bootloader if your device is S-Off but those are things I haven't been able to try out so far...
Click to expand...
Click to collapse
Really? You don't know how to unlock your bootloader? You don't need S-Off for it.
This answers the question I had wondered about. How does this install OTAs with a custom recovery? It doesn't, correct?
You need to be stock for this. The first thing you do after unlocking the bootloader (which pretty much anyone here has done) is to flash a custom recovery.
This tool will only work for users who are still completely on stock.
IO would test myself, but I'm already S-Off/unlocked bootloader/custom recovery/modified firmware/custom ROM|, and I don't want to take the time to go back to stock and incrementally update the steps to see what won't work. I think as soon as you flash custom recovery, you can't use this method.
If you want to unlock your bootloader, HTC provides the method and instructions at htcdev.com
xunholyx said:
Really? You don't know how to unlock your bootloader? You don't need S-Off for it.
This answers the question I had wondered about. How does this install OTAs with a custom recovery? It doesn't, correct?
You need to be stock for this. The first thing you do after unlocking the bootloader (which pretty much anyone here has done) is to flash a custom recovery.
This tool will only work for users who are still completely on stock.
IO would test myself, but I'm already S-Off/unlocked bootloader/custom recovery/modified firmware/custom ROM|, and I don't want to take the time to go back to stock and incrementally update the steps to see what won't work. I think as soon as you flash custom recovery, you can't use this method.
If you want to unlock your bootloader, HTC provides the method and instructions at htcdev.com
Click to expand...
Click to collapse
Sure I know how to unlock a boitloader. If you watch my profile you can see I'm a ROM maintainer. I have to use custom recoveries to do that. People interpret my posts wrongly sometimes. I dunno why. Anyway, I use TWRP but after flashing a recovery or any other image file I lock my bootloader again for safety reasons. You just need to have a locked bootloader to use my tool currently... And no, u don't need to be stock. This tool just requires a locked or relocked bootloader. U can use whatever ROM u like. U just need to have a locked bootloader and my tool installs the latest firmware I integrated for your HTC 10 model. I know what I do. You should just read my posts a bit more carefully to prevent yourself from contending wrong things...
krassermensch said:
Sure I know how to unlock a boitloader. If you watch my profile you can see I'm a ROM maintainer. I have to use custom recoveries to do that. People interpret my posts wrongly sometimes. I dunno why. Anyway, I use TWRP but after flashing a recovery or any other image file I lock my bootloader again for safety reasons. You just need to have a locked bootloader to use my tool currently...
Click to expand...
Click to collapse
" I read that you can have an unlocked bootloader if your device is S-Off" quote from you
I did read it wrong. I was thinking that you meant you needed soff to unlock bootloader.\
And yes, now that I understand what you meant, with S-Off you shouldn't need to re-lock your bootloader.
xunholyx said:
" I read that you can have an unlocked bootloader if your device is S-Off" quote from you
I did read it wrong. I was thinking that you meant you needed soff to unlock bootloader.\
And yes, now that I understand what you meant, with S-Off you shouldn't need to re-lock your bootloader.
Click to expand...
Click to collapse
Yeah, dude, I think I wouldn't be able to write a batch tool with fastboot and adb if I didn't know the whole stuff. My broken Nexus 4 has teached me a lot over the last 3½ years
Just to confirm... and thanks for the tool
I have a HTC 10 and nothing has been done to it since I bought it (Stock everything) will this tool keep it that way but give me the latest OTA?
Milamber said:
Just to confirm... and thanks for the tool
I have a HTC 10 and nothing has been done to it since I bought it (Stock everything) will this tool keep it that way but give me the latest OTA?
Click to expand...
Click to collapse
You do not need this tool if you are Stock everything, unless you unlocked your bootloader.
Milamber said:
Just to confirm... and thanks for the tool
I have a HTC 10 and nothing has been done to it since I bought it (Stock everything) will this tool keep it that way but give me the latest OTA?
Click to expand...
Click to collapse
No, I could write a tool for manual OTA flashing, too, but I don't want to do that since OTAs are for stock devices which are notified about OTA updates automatically. If you want to flash OTAs quicker: there's a thread here on xda where OTA zips are shared with an explaination how to flash it manually... This tool can be used by stock device's owners but it wouldn't be necessary...
krassermensch said:
I didn't try but normally your HTC 10 would block the installation if the bootloader is unlocked. Could you try it out and report. It's a bit hard to try it out by myself currently... It will most probably report that your new firmware's flashed but it actually will not be flashed after that if your bootloader's unlocked. If it's flashed anyway it'd be perfect since I'd not have to make a backup solution in that case. But I guess that the 10 isn't different to the M9 for example when it comes to firmware flashing. I read that you can have an unlocked bootloader if your device is S-Off but those are things I haven't been able to try out so far...
Click to expand...
Click to collapse
Thanks for your explanations, now i understand your tool a bit more.
But if it only works with a locked/relocked bootloader i cant use it. Really no offense and i dont want to sound rude (!), but isnt it already a design problem? You said the tool is designed for people with non-stock ROMS, but that does imply that you have an unlocked bootloader to flash and keep your ROM and recovery up to date. To use your tool you have to relock the bootloader after flashing the ROM. But to update the ROM to a newer version you have to unlock the bootloader again via HTCDev (and loosing your data while doing this)? Sounds a bit weird to me...or did i miss something?
So which adb commands are you using? Didnt have the time to check your script yet (sorry!). Because im S-On with my bootloader unlocked an i COULD flash a signed firmware.zip i extracted from an official OTA via ADB. This wiped my boot and recovery partitions, but not data. Just had to restore the two partitions to get everything working again.
-Vulture- said:
Thanks for your explanations, now i understand your tool a bit more.
But if it only works with a locked/relocked bootloader i cant use it. Really no offense and i dont want to sound rude (!), but isnt it already a design problem? You said the tool is designed for people with non-stock ROMS, but that does imply that you have an unlocked bootloader to flash and keep your ROM and recovery up to date. To use your tool you have to relock the bootloader after flashing the ROM. But to update the ROM to a newer version you have to unlock the bootloader again via HTCDev (and loosing your data while doing this)? Sounds a bit weird to me...or did i miss something?
So which adb commands are you using? Didnt have the time to check your script yet (sorry!). Because im S-On with my bootloader unlocked an i COULD flash a signed firmware.zip i extracted from an official OTA via ADB. This wiped my boot and recovery partitions, but not data. Just had to restore the two partitions to get everything working again.
Click to expand...
Click to collapse
So you could flash the firmware-update.zip from the OTA without relocking your bootloader?
And it was really updated after that?
krassermensch said:
So you could flash the firmware-update.zip from the OTA without relocking your bootloader?
And it was really updated after that?
Click to expand...
Click to collapse
Thats what i did, bootloader was unlocked and flash successfully. I extracted the firmware.zip from an official OTA (TMOB-101) for my device and flashed it via ADB from my PC. Since the firmware.zip is signed, it can be flashed. Doesnt work with modified zips however, like the ones from sneakyghosts thread. He removed unnecessary stuff like the flash command for boot and recovery which my broke my phone initially. Thats why you need TWRP to restore them later.
As you already said with your tool, its also important here to get the right file to flash and not to skip a firmware update in between. You have to go from very old -> old -> current without skipping old.
I used the step-by-step instructions from here:
http://forum.xda-developers.com/htc-10/how-to/2016-05-27-fastboot-flashing-firmware-t3387520
Hello,
I own the 32gb h791 nexus 5x and the phone is bootlooping after android 7.0 update.
so basicly the phone showing google logo and then reboot back..
My bootloader is unlocked, so I tried to flash marshmellow without any success.
I can not access the recovery.
I saw a thread about flashing tot but i read in the thread that It is re lock the bootloader.
I dont have efs backup..
Any help?
Thanks,
Nimrod
Someone got me to try the Nexus Root Toolkit by Wugfresh. There was an option to Restore/upgrade/Downgrade from a soft-bricked/bootloop state. Seems to have a bunch of DIY utilities for us dummies, such as backups and rooting. I was also soft-bricked for over 10 hours, so not all hope is lost.
But that's a hardware bootlop no software
How many files had been flashed when you've tried to flash it? If any, have you done any modifications like root etc ?
If no, just lock bootloader and send RMA
If you can send to Google, you don't have to lock bootloader.
If your warranty expired, try to talk to Google may they will give you a replacement anyway, if not Google, you can try to LG because of 15mo warranty from production date
TypNguy said:
Someone got me to try the Nexus Root Toolkit by Wugfresh. There was an option to Restore/upgrade/Downgrade from a soft-bricked/bootloop state. Seems to have a bunch of DIY utilities for us dummies, such as backups and rooting. I was also soft-bricked for over 10 hours, so not all hope is lost.
Click to expand...
Click to collapse
So did the root toolkit work? Your post sounds like it worked. Could you explain what worked for you? I have a similar situation where I have the boot loop but wasn't associated with any OTA upgrades. It happened about a week after I saw the 7.1 update available for download. I have Minimal ADB loaded and have tried to flash to the latest stock image but no luck. Below is my original post from about a week ago. Any help will be appreciated.
"Nexus 5X Bootloop
I have a Nexus 5X in a bootloop that I can stop at the bootloader but will not boot. About a year ago I unlocked the bootloader to get root and used stock Google OS images as opposed to custom ROMS. It has worked fine until a couple days ago it started with the error message, "Your device is unlocked and can't be checked for corruption, lock bootloader and try again." The error message is Orange and offered a link for review further help. g.co/ABH (I don't have the phone in hand so the messages might not be exact) We have not tried to get OTA updates and haven't downloaded anything within days before it started flaking out. In an effort to fix it, I have downloaded the latest stock image 7.1.1 for the nexus 5x bullhead along with the latest version of Minimal ADB and fastboot 1.4. I have flashed the radio and bootloader with /flash-all.bat after editing the Flash -w line and individually flashed /system, /boot, /recovery, /cache, /vendor but excluded the /userdata in an effort to make it work without losing data. This hasn't worked thus far and showed no difference. I know if I lock the bootloader to check for corruption then I will lose my data and then have to unlock it again to get tether capabilities back but will ultimately resort to that if necessary. Anybody else have this issue that might be able to offer suggestions for fixing while keeping the bootloader unlocked? I'm a bit of a noob but learn quickly. Thanks in advance."
snakeman1978 said:
So did the root toolkit work? Your post sounds like it worked. Could you explain what worked for you? I have a similar situation where I have the boot loop but wasn't associated with any OTA upgrades. It happened about a week after I saw the 7.1 update available for download. I have Minimal ADB loaded and have tried to flash to the latest stock image but no luck. Below is my original post from about a week ago. Any help will be appreciated.
"Nexus 5X Bootloop
I have a Nexus 5X in a bootloop that I can stop at the bootloader but will not boot. About a year ago I unlocked the bootloader to get root and used stock Google OS images as opposed to custom ROMS. It has worked fine until a couple days ago it started with the error message, "Your device is unlocked and can't be checked for corruption, lock bootloader and try again." The error message is Orange and offered a link for review further help. g.co/ABH (I don't have the phone in hand so the messages might not be exact) We have not tried to get OTA updates and haven't downloaded anything within days before it started flaking out. In an effort to fix it, I have downloaded the latest stock image 7.1.1 for the nexus 5x bullhead along with the latest version of Minimal ADB and fastboot 1.4. I have flashed the radio and bootloader with /flash-all.bat after editing the Flash -w line and individually flashed /system, /boot, /recovery, /cache, /vendor but excluded the /userdata in an effort to make it work without losing data. This hasn't worked thus far and showed no difference. I know if I lock the bootloader to check for corruption then I will lose my data and then have to unlock it again to get tether capabilities back but will ultimately resort to that if necessary. Anybody else have this issue that might be able to offer suggestions for fixing while keeping the bootloader unlocked? I'm a bit of a noob but learn quickly. Thanks in advance."
Click to expand...
Click to collapse
His problem is a hardware issue not software. Might get lucky and volte it back to life but I highly doubtful . LG notorious for certain models that infinite bootloop issue g4 was the worse.
Yes, the root toolkit worked for me. I still don't know how to flash correctly, so if you have the right driver's associated with your phone/laptop it should be a breeze. The best part is that there's a log, so you know what the toolkit is doing. For example, it may unroot your phone before it flashes the new stock image for you.
---------- Post added at 02:40 AM ---------- Previous post was at 02:36 AM ----------
Just found wugfresh's answer to your question I think.
Link
Address: http://www.wugfresh.com/faqs/how-to-update-ota-not-working/
snakeman1978 said:
So did the root toolkit work? Your post sounds like it worked. Could you explain what worked for you? I have a similar situation where I have the boot loop but wasn't associated with any OTA upgrades. It happened about a week after I saw the 7.1 update available for download. I have Minimal ADB loaded and have tried to flash to the latest stock image but no luck. Below is my original post from about a week ago. Any help will be appreciated.
"Nexus 5X Bootloop
I have a Nexus 5X in a bootloop that I can stop at the bootloader but will not boot. About a year ago I unlocked the bootloader to get root and used stock Google OS images as opposed to custom ROMS. It has worked fine until a couple days ago it started with the error message, "Your device is unlocked and can't be checked for corruption, lock bootloader and try again." The error message is Orange and offered a link for review further help. g.co/ABH (I don't have the phone in hand so the messages might not be exact) We have not tried to get OTA updates and haven't downloaded anything within days before it started flaking out. In an effort to fix it, I have downloaded the latest stock image 7.1.1 for the nexus 5x bullhead along with the latest version of Minimal ADB and fastboot 1.4. I have flashed the radio and bootloader with /flash-all.bat after editing the Flash -w line and individually flashed /system, /boot, /recovery, /cache, /vendor but excluded the /userdata in an effort to make it work without losing data. This hasn't worked thus far and showed no difference. I know if I lock the bootloader to check for corruption then I will lose my data and then have to unlock it again to get tether capabilities back but will ultimately resort to that if necessary. Anybody else have this issue that might be able to offer suggestions for fixing while keeping the bootloader unlocked? I'm a bit of a noob but learn quickly. Thanks in advance."
Click to expand...
Click to collapse
So it looks like the major feature added is the Google Play assistant, which I don't even use on my phone.
But also, I believe the latest version of YouTube will be the stock app, which I just don't like.
I am rooted, which I realize will go away after the upgrade. But also, I don't have anything installed that requires root really. I wanted to take advantage of some xposed features, but apparently there is no version of the framework that supports nvidia shield tv 5.2?
So is it worth upgrading right now? Has anyone tried it? Anything notable worth upgrading for?
I'm in the same situation (rooted) as you. I tried to update, but I end up in TWRP and I don't know what to do from there. If I boot system it just start up as normal and ask me again to update.
Any ideas? Anyone?
What to do, what to do?
Kickasscowboy said:
I'm in the same situation (rooted) as you. I tried to update, but I end up in TWRP and I don't know what to do from there. If I boot system it just start up as normal and ask me again to update.
Any ideas? Anyone?
What to do, what to do?
Click to expand...
Click to collapse
Most likely have to wait for the developers image .
jionny said:
Most likely have to wait for the developers image .
Click to expand...
Click to collapse
And flash through FlashFire
orificium said:
So it looks like the major feature added is the Google Play assistant, which I don't even use on my phone.
But also, I believe the latest version of YouTube will be the stock app, which I just don't like.
Click to expand...
Click to collapse
I have a stock shield (not rooted), but had backed off the YouTube app to be the old one (the one that works with secondary accounts).
I let it upgrade and it did not force a YouTube update. After it finished, I'm still running YT 1.3.11. So you should be okay there.
Of course other than Google Assistant, I haven't found much new. What I really want is for Google Assistant to work with Google Play Music, but it doesn't do that (yet?).
I'm in the same boat as you guys. Currently rooted and debating the upgrade. I would think that we could update via flash fire if someone knows where the ota is stored once it downloads.
Sent from my Pixel XL using Tapatalk
I hear you guys. I will wait for OTA update to be downloadable or I might even consider returning to stock. I really don't have any use for root now.
FYI, Doesn't work with flashfire.
https://m.imgur.com/a/4ZKy6
n1gh7mar3 said:
FYI, Doesn't work with flashfire.
https://m.imgur.com/a/4ZKy6
Click to expand...
Click to collapse
That's not a developer image right? wouldn't think it would work unless it is the developer image or your bootloader is locked
I got mine to update even though its rooted.
After it finished downloading, it rebooted into twrp and installed the update automatically with no issues.
I did however get some issues after it finished updating.
The recovery/twrp is gone and cant boot into that anymore.
Root is of course gone.
And now im also just getting a black wallpaper in the launcher instead of the default nvidia one.
WisdomWolf said:
I'm in the same boat as you guys. Currently rooted and debating the upgrade. I would think that we could update via flash fire if someone knows where the ota is stored once it downloads.
Click to expand...
Click to collapse
data/data/com.nvidia.ota/app_download
jionny said:
That's not a developer image right? wouldn't think it would work unless it is the developer image or your bootloader is locked
Click to expand...
Click to collapse
I would assume the OTA is a developer image. Since it couldn't get flash fire to work, I reflashed the stock recovery image and applied the OTA, but it kept freezing and after about 10 minutes it would just boot into the original os.
n1gh7mar3 said:
I would assume the OTA is a developer image. Since it couldn't get flash fire to work, I reflashed the stock recovery image and applied the OTA, but it kept freezing and after about 10 minutes it would just boot into the original os.
Click to expand...
Click to collapse
Sorry I meant the developer rooted image that Nvidia usually releases shortly after a upgrade that you can flash over a unlocked bootloader and root and keep root
jionny said:
Sorry I meant the developer rooted image that Nvidia usually releases shortly after a upgrade that you can flash over a unlocked bootloader and root and keep root
Click to expand...
Click to collapse
I totally understand what you mean, I was already on 5.2.0 developer image, so I assume if presented with an OTA it's of the same type.
n1gh7mar3 said:
I totally understand what you mean, I was already on 5.2.0 developer image, so I assume if presented with an OTA it's of the same type.
Click to expand...
Click to collapse
No you have to get that from Nvidias site however last time I checked it was not up yet
n1gh7mar3 said:
I would assume the OTA is a developer image. Since it couldn't get flash fire to work, I reflashed the stock recovery image and applied the OTA, but it kept freezing and after about 10 minutes it would just boot into the original os.
Click to expand...
Click to collapse
you have to flash all the files inside, not only recovery. (nv-recovery-image-shield-atv-5.2.0.zip)
now it worked
Screen flickers
My shield got the latest upgrade (non root) and now my screen flickers from time to time. Any known solution to this issue ?
Tifulb said:
My shield got the latest upgrade (non root) and now my screen flickers from time to time. Any known solution to this issue ?
Click to expand...
Click to collapse
I've seen a few fixes for screen issues, either making sure in advanced display resolution settings things are correct, or disabling/renabling the CEC in settings.
You may want to check out the nvidia geforce forums thread, I'd probably start out middle to last several pages (assuming you read this soon, in a few days you'll just have to take a guess as there will be way more pages) https://forums.geforce.com/default/.../shield-experience-upgrade-6-0-for-shield-tv/
I think there's a post about chroma clipping which may be what yours is doing, but it could be some of the HDR stuff or something with the HDMI or CEC issues for all I know.
Hi,
i have a 2015 Shield (root) with 5.2 image.
I would back to stock image and unroot my shield.
I have download the "nv-recovery-image-shield-atv-5.2.0".
my approach.
*** Prerequisites:
1. Ensure that the bootloader is unlocked (see above step)
*** Flashing instructions:
1. Execute these commands on the host PC:
fastboot flash staging blob
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot reboot
Is this the right way?
Thanks!
OTA zip shield 2015 6.0
if someone need:
Original ota zip for Shield TV 2015 (non pro) 5.2 -> 6.0
https://mega.nz/#!BChlSbaR!em9CV5PoRzalWnMWf7iqAj4oVeDQqLhrz_Q1GGXy0Ug
Hello All,
It been a while since I've been lurking on the forums. Last time I was here was just after when I got the pixel xl and needed to root and unlock it, and was looking for how to update.
Back then when the update past 7.1.1 released they were having issues keeping root and unlocked status after the update.
I'm looking to update my phone now to the newest, stable release, that will let me keep root and unlocked bootloader on a Verizon Google pixel xl.
Here is where I'm currently at:
Verizon Google pixel xl.
Rooted
Unlocked bootloader
7.1.1 (NOF27B) stock image
Flash fire installed
Twrp installed
As of late I've had the common battery issue with this version get worse as the phone ages and now after landing in Indianapolis a few hours ago I'm having radio issues that I'm hoping a fresh install or update will fix.
I'm just looking for some direction on what steps I need to do to update and not lose root or unlocked bootloader.
I need to get full functionality of my phone back asap, so I appreciate all of your help with this.
Thank you
Hobocoe said:
Hello All,
It been a while since I've been lurking on the forums. Last time I was here was just after when I got the pixel xl and needed to root and unlock it, and was looking for how to update.
Back then when the update past 7.1.1 released they were having issues keeping root and unlocked status after the update.
I'm looking to update my phone now to the newest, stable release, that will let me keep root and unlocked bootloader on a Verizon Google pixel xl.
Here is where I'm currently at:
Verizon Google pixel xl.
Rooted
Unlocked bootloader
7.1.1 (NOF27B) stock image
Flash fire installed
Twrp installed
As of late I've had the common battery issue with this version get worse as the phone ages and now after landing in Indianapolis a few hours ago I'm having radio issues that I'm hoping a fresh install or update will fix.
I'm just looking for some direction on what steps I need to do to update and not lose root or unlocked bootloader.
I need to get full functionality of my phone back asap, so I appreciate all of your help with this.
Thank you
Click to expand...
Click to collapse
This excellent guide by HomeBoy76 should give you all the info that you need....
https://forum.xda-developers.com/pixel-xl/how-to/guide-pixel-xl-android-8-1oreo-unlock-t3715279
Hobocoe said:
Hello All,
It been a while since I've been lurking on the forums. Last time I was here was just after when I got the pixel xl and needed to root and unlock it, and was looking for how to update.
Back then when the update past 7.1.1 released they were having issues keeping root and unlocked status after the update.
I'm looking to update my phone now to the newest, stable release, that will let me keep root and unlocked bootloader on a Verizon Google pixel xl.
Here is where I'm currently at:
Verizon Google pixel xl.
Rooted
Unlocked bootloader
7.1.1 (NOF27B) stock image
Flash fire installed
Twrp installed
As of late I've had the common battery issue with this version get worse as the phone ages and now after landing in Indianapolis a few hours ago I'm having radio issues that I'm hoping a fresh install or update will fix.
I'm just looking for some direction on what steps I need to do to update and not lose root or unlocked bootloader.
I need to get full functionality of my phone back asap, so I appreciate all of your help with this.
Thank you
Click to expand...
Click to collapse
I do not think there is anyway to upgrade the 7.1.1 firmware to 8.10 firmware and not lose root. I would suggest you use my guide and Do #4 wipe data and then do #7 root.
Why wipe data? There have been a lot of changes to the firmware since 7.1.1 (NOF27B) stock image.
Note: Copy/Backup the information on your internal storage you want to keep to your computer i.e., pictures SMS, files etc. Why? Because using flash-all with the -w will wipe your internal storage.
It's actually pretty simple, just download the latest factory image of either Oreo,. Flash the flash all script included with fast boot. Afterward boot into the system without setting up a pin or password or anything, set it up, then reboot into boot loader and boot the latest TWRP, then within TWRP flash TWRP zip file and Magisk root. Reboot system.
Homeboy76 said:
I do not think there is anyway to upgrade the 7.1.1 firmware to 8.10 firmware and not lose root. I would suggest you use my guide and Do #4 wipe data and then do #7 root.
Why wipe data? There have been a lot of changes to the firmware since 7.1.1 (NOF27B) stock image.
Note: Copy/Backup the information on your internal storage you want to keep to your computer i.e., pictures SMS, files etc. Why? Because using flash-all with the -w will wipe your internal storage.
Click to expand...
Click to collapse
Thank you everyone for the responses. Homeboy 76, I just had a quick question regarding your guide. The steps for the bootloader. Are you just showing all 3 options (unlock, lock, stock) for thurougness? Or do I have to return the bootloader to stock and lock it before I can install the update and root again?
Also I should test a factory reset before I try updating to see if my radio problem is worse than I expected. If I just go into the system and do a factory reset, besides losing root will it be fine doing that? Or does that get it into a weird root/stock limbo and brick it? Or prevent me from installing the update?
Thank you for your help with this. I just don't want to brick my phone while trying to fix it.
Hobocoe said:
Thank you everyone for the responses. Homeboy 76, I just had a quick question regarding your guide. The steps for the bootloader. Are you just showing all 3 options (unlock, lock, stock) for thurougness? Or do I have to return the bootloader to stock and lock it before I can install the update and root again?
Also I should test a factory reset before I try updating to see if my radio problem is worse than I expected. If I just go into the system and do a factory reset, besides losing root will it be fine doing that? Or does that get it into a weird root/stock limbo and brick it? Or prevent me from installing the update?
Thank you for your help with this. I just don't want to brick my phone while trying to fix it.
Click to expand...
Click to collapse
"...for thurougness?
Yes
Or do I have to return the bootloader to stock and lock it before I can install the update and root again?
No, Do not lock the boot loader.
Also I should test a factory reset before I try updating to see if my radio problem is worse than I expected. If I just go into the system and do a factory reset, besides losing root will it be fine doing that?
Yes
If it locks the bootloader, go here to unlock it:
[How-to] Unlock bootloader on Verizon Pixel/XL by burduli
Or does that get it into a weird root/stock limbo and brick it? Or prevent me from installing the update?
No, No.
Homeboy76 said:
"...for thurougness?
Yes
Or do I have to return the bootloader to stock and lock it before I can install the update and root again?
No, Do not lock the boot loader.
Also I should test a factory reset before I try updating to see if my radio problem is worse than I expected. If I just go into the system and do a factory reset, besides losing root will it be fine doing that?
Yes
If it locks the bootloader, go here to unlock it:
[How-to] Unlock bootloader on Verizon Pixel/XL by burduli
Or does that get it into a weird root/stock limbo and brick it? Or prevent me from installing the update?
No, No.
Click to expand...
Click to collapse
Thank you homeboy for the assistance. It's much appreciated. Luckily my phone issues were related to the location I was in. Indianapolis doesn't like my phone number for some reason.. But ill still be updating either way.
Thanks again.
Hobocoe said:
Thank you homeboy for the assistance. It's much appreciated. Luckily my phone issues were related to the location I was in. Indianapolis doesn't like my phone number for some reason.. But ill still be updating either way.
Thanks again.
Click to expand...
Click to collapse
You're welcome