Rolling back from 5.0.1 to 4.4W2 - Sony Smartwatch 3

Hi,
Is it possible to go back from 5.0.1 to 4.4W(or 4.4W2)?
For my testing purpose, now I need to have my sw3 with KNX01V.
Any advise is welcome!
Thanks

You could probably use fastboot if you download the factory image

mertzi said:
You could probably use fastboot if you download the factory image
Click to expand...
Click to collapse
Yes, but wouldn't the watch update as soon as it was setup through the phone? I've been thinking about trying to roll back as 5.0 software has made my watch slower to wake up, misses alarms, and disconnects more often.

I'm also interested in this for "Sleep As Android" support. Surely there is some way to simply disable the OTA, like maybe renaming some critical file?

mertzi said:
You could probably use fastboot if you download the factory image
Click to expand...
Click to collapse
Do you know where I could find that image? I've searched around and have only found KGW38C and LWX48P, but haven't been able t o find KNX01V anywhere.

bradpitcher said:
Do you know where I could find that image? I've searched around and have only found KGW38C and LWX48P, but haven't been able t o find KNX01V anywhere.
Click to expand...
Click to collapse
I thought Google would publish these images like they do for nexus devices, seems they wont go down that road with android wear, unfortunately.

Related

How to Force the OTA?

I feel like a moron because mine hasn't updated automatically from 4.4.4. Any way to force the Lollipop update? I already checked and have the 24 wait period in effect. Thanks!
Happened to me as well. Go into settings, time and date, uncheck the automatic date/time function and move the date 1 day ahead. I would reboot the phone just in case, and check it again.
efishta said:
Happened to me as well. Go into settings, time and date, uncheck the automatic date/time function and move the date 1 day ahead. I would reboot the phone just in case, and check it again.
Click to expand...
Click to collapse
Weird - just did all that and it still says software is up to date. Any other suggestions?
Called AT&T to see if they could push Lollipop to my device. No dice. Tried the "move ahead one calendar day" trick, but it didn't work. Now it shows that I can't check again for 702 hours. Ha! Any other suggestions? Maybe it just hadn't rolled out to everyone yet. I'm in Chicago, if that matters.
If you don't have an issue wiping your data then you can use the stock Odin file in the general sub to flash it back to stock and update again.
I had my wife's phone updated with a push from AT&T. She had the same issue. They have to file a ti let and tech department did it but took a few days.
Hoshneer said:
I had my wife's phone updated with a push from AT&T. She had the same issue. They have to file a ti let and tech department did it but took a few days.
Click to expand...
Click to collapse
Thanks for the help! Did you do it over support chat on their site or the phone?
nunyabiziz said:
If you don't have an issue wiping your data then you can use the stock Odin file in the general sub to flash it back to stock and update again.
Click to expand...
Click to collapse
Thanks! Yeah, I might just do this.
Also if you factory restore your phone it will go back to the default 24hr wait.
I haven't really messed around with root stuff in a while, but I know even without root we used to be able to download the update, put it in the root or the SD card and rename it update.zip . Does this not work anymore? I really thought there would be a way to force the update somehow..
evilsock said:
I haven't really messed around with root stuff in a while, but I know even without root we used to be able to download the update, put it in the root or the SD card and rename it update.zip . Does this not work anymore? I really thought there would be a way to force the update somehow..
Click to expand...
Click to collapse
That would work if someone has captured the zip file or the download URL, which no one has done. Virtually every 5.0.1 related thread has someone asking for this, with the same response. No one has it, and if they did, it would be available in a stickied post.
Oh the woes of waiting for updates lol.
I remember with my OG moto droid waiting for 2.1 lol.
And how 2.2 blew my mind. Now look at it.
i had to flash oem kitkat to my att note 4, which right after the flash immediately got lollipop.
if you do got to the Samsung kiosk have them re-flash kitkat. then the download for lollipop will update after setup.
Force update to marshmallow?
Hi, absolute idiot when it comes to stuff like this.
So, i was searching through my apps list when i noticed AT&T software update.
I dont need any AT&T applications as i am in Australia and do not have AT&T.
i have tried to force an update by following the clearing data and force stopping the Google services frame work.
tried it multiple times, nothing.
Then i thought i could disable the app of the AT&T software update, and then i fell deeper into the rabbit hole of how OSPolice got in trouble and how there is 2 versions of package disabler pro.
So here i am, stuck with 5.1.1 and i have no idea what to do.
No, i am not going to root it. This is an AT&T phone, with a bootlocker on it. If anyone, *ANYONE*, can help me solve this small issue that would be much appreciated.

'Idiots' guide to root, backup, and ROM update ?...

Hi everyone,
Obviously this forum is a great resource for these head units, a lot of people putting in a lot of hard work (as is often the case on XDA).
I believe for some (myself included occasionally!) that the quantity of information and terms/language used can be a little overwhelming.
Add to that the fact that the forum is somewhat fragmented, it can be a bit hard to know where to start (although it is good that this is being addressed at the moment by splitting it up into sections.)
I was wondering if anybody had created or would be willing to look at creating, an 'idiots' style guide for the very basics.
I.e. assume that somebody with no knowledge in this field has purchased one of these units and simply wants to:
Get root access
Backup the current unit completely in case of problems updating etc
Locate the correct firmware/ROM for their unit.
Install the new firmware/ROM
Any further info can be found through research in the forums, all depending on what mods/apps etc the individual wants.
Thanks all!
phil001 said:
Hi everyone,
Obviously this forum is a great resource for these head units, a lot of people putting in a lot of hard work (as is often the case on XDA).
I believe for some (myself included occasionally!) that the quantity of information and terms/language used can be a little overwhelming.
Add to that the fact that the forum is somewhat fragmented, it can be a bit hard to know where to start (although it is good that this is being addressed at the moment by splitting it up into sections.)
I was wondering if anybody had created or would be willing to look at creating, an 'idiots' style guide for the very basics.
I.e. assume that somebody with no knowledge in this field has purchased one of these units and simply wants to:
Get root access
Backup the current unit completely in case of problems updating etc
Locate the correct firmware/ROM for their unit.
Install the new firmware/ROM
Any further info can be found through research in the forums, all depending on what mods/apps etc the individual wants.
Thanks all!
Click to expand...
Click to collapse
I agree, I think this would be a good idea :good:
I would be willing to put something together from what Ive read on here but I'm still unsure of the best way to take a backup? Is the only way not through TWRP which then means you can't update your MCU again?
You do not need a backup of your ROM as most factory ROMs are available for flashing.
did you read the Wiki-Artikel and the Knowledge-Thread?
dark alex said:
You do not need a backup of your ROM as most factory ROMs are available for flashing.
did you read the Wiki-Artikel and the Knowledge-Thread?
Click to expand...
Click to collapse
Hi
Yes i did read them, and i'm sure i could use that to get through what i want to do.
Although the knowledge thread does state "IT IS ADVISABLE TO BACKUP YOUR SYSTEM BEFORE PLAYING WITH IT" so i assumed i did need to make some sort of backup
It also advises using "nandroid root" form play store, there are various apps with similar names to this, but not exactly this name.
Just little things like this put seeds of doubt in my OCD mind
Wasn't meaning to criticize in anyway, was just giving my opinion (which may well not be the same as everyone elses!)
Cheers
dark alex said:
You do not need a backup of your ROM as most factory ROMs are available for flashing.
did you read the Wiki-Artikel and the Knowledge-Thread?
Click to expand...
Click to collapse
Yes I've read it but I wanted to be absolutely sure I have a backup of my exact ROM. I also noticed on the server, the ROMs are not specific, for example I have a KLD2 but there are only KLD ROMs, is that an issue?
dark alex said:
You do not need a backup of your ROM as most factory ROMs are available for flashing.
did you read the Wiki-Artikel and the Knowledge-Thread?
Click to expand...
Click to collapse
I agree. You are a developer: could explain to me why in these units, that theoretically they are Android, I can't do a full backup and in my Smartphone if I can do it.
For example with TWRP or CWM and retrieve it without problems.
I think that the former companion wants to say is:
I have my unit (Smartphone or auto) and when I have all my programs to my taste I do a backup. But one day I want to try some update that I have seen in the Forum. I do and I get wrong; as I have my backup, nothing happens. I restore it and that's all.
This I have done it many times with my Smartphone, from GingerBread to Lollipop.
Many Thanks
phil001 said:
I was wondering if anybody had created or would be willing to look at creating, an 'idiots' style guide for the very basics.
I.e. assume that somebody with no knowledge in this field has purchased one of these units and simply wants to:
Get root access
Backup the current unit completely in case of problems updating etc
Locate the correct firmware/ROM for their unit.
Install the new firmware/ROM
Any further info can be found through research in the forums, all depending on what mods/apps etc the individual wants.
Thanks all!
Click to expand...
Click to collapse
Go to Factory setting enter *#hct#root#
Go to Factory setting enter adbon
Firmware update instructions Here
Joying Firmware Here
Malaysk ROM Here
The original Recovery is not that advanced as TWRP and others are.
The problem is that it is using special proprietary code to flash the MCU and if you replace it you are not able to flash MCU anymore until you install the original recovery again.
dark alex said:
The original Recovery is not that advanced as TWRP and others are.
The problem is that it is using special proprietary code to flash the MCU and if you replace it you are not able to flash MCU anymore until you install the original recovery again.
Click to expand...
Click to collapse
Thanks mate. So the safest way to do a backup would be to take a backup of the original recovery then install TWRP and take a backup of the ROM with that? I know there are stock ROMs on the server but I would just like to be 100% sure.
I did this in my room "Go to Factory setting enter *#hct#root#"
After that I have root access and I can backup or freeze my apps with titanium backup. The problem is when I try to remove a system app, the app is not removed. I need to do more steeps?
thanks a lot
lynksss said:
The problem is when I try to remove a system app, the app is not removed. I need to do more steeps?
Click to expand...
Click to collapse
What app?
tmiller101 said:
What app?
Click to expand...
Click to collapse
Anything, I tried with gmail, gallery and others
Sent from my Nexus 5 using Tapatalk
lynksss said:
Anything, I tried with gmail, gallery and others
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Did you install superSU?
Go to apps and stop the one you are trying to remove. Change the extension to back or old. That should do it.
Turn developers mode on if you haven't. Password adbon in factory settings.
tmiller101 said:
Go to Factory setting enter *#hct#root#
Go to Factory setting enter adbon
Firmware update instructions Here
Joying Firmware Here
Malaysk ROM Here
Click to expand...
Click to collapse
Is Joying firmware valid for no Joying units?
jrm209 said:
Is Joying firmware valid for no Joying units?
Click to expand...
Click to collapse
Yes and no. Joyous is a manufacturer. There are several resellers who go under different names. I believe pumpkin is one. Do a search for huifei and in the mega thread they list several of the resellers.
Hi all, I'm in the same boat that I am reading like fury but there are thousands of pages, so I really appreciate this thread, and the contributions and the Wiki's.
I've got a MX v2.72 and found the following worked perfectly to get me past the first hurdle.
rickthecabbie said:
If you are new to Android, the first thing I would suggest is looking at replacing the Launcher. This will give you a lot more freedom
to add widgets for things like Shuttle and other apps you may want to try. I would also leave the ROM stock for as long as you can stand to do so. Take notes as you work with the stock ROM of the changes you would like to make, and search through the threads here to find if
you can make them without flashing to a custom ROM.
Rooting this unit is quite simple by using the temporary root method. Enter *#hct#root# as the password when opening System Settings.
DO NOT REBOOT. First go to the Play Store and Install the SUPERSU app by CHAINFIRE Once you have done that, let the system reboot,
and then go back to System Settings and enter the password adboff This will turn off the temporary factory SuperUser app, but you will still be able to use the CHAINFIRE SUPERSU app you installed to control root access of your apps.
I will say that if you want to jump in off the deep end, Malaysk has put together some awesome stuff.
I started with a DSA Rooted Stock Rom and installed APEX Launcher, mostly because it let me get started with a built in root,
and it also gave me 2 or 3 GBs to install other apps where the Stock ROM from the Factory only had a 1 GB partition.
Have Fun, and
Good Luck,
Rick
Click to expand...
Click to collapse
I've now got to think about how to do the changes I want which include wanting to change default EQ and fader settings, button mapping, auto dimming, (some of that should be doable through the Xposed Mod) and finding a nicer launcher....
tmiller101 said:
Go to Factory setting enter *#hct#root#
Go to Factory setting enter adbon
Firmware update instructions Here
Joying Firmware Here
Malaysk ROM Here
Click to expand...
Click to collapse
thanks,
i have entered *#hct#root#
but i just get an incorrect password message, should there be a confirmation of root message?
thanks
and for the sake of completeness here is the info
MCU Version
MTCB-HZC-V2.69
Android Version
4.4.4_22072015
Kernel version
3.0.36+
[email protected] #401
Build number
Rk3188-eng4.4.4 22072015.18:52:09
CPU
Arm7 1.6GHz (x4)
Memory
1024 MB
I still dont really understand how i can do a nandorid (or similar) backup, as i do not have root (see last post) and the backup apps require it.
The knowledge thread states the only way to root 4.4.4 is to install a pre rooted rom, meaning i could not backup factory rom.
I cannot see my rom available on here anywhere, and the manufacturer aren't providing it to me so far....
confused.com!
phil001 said:
thanks,
i have entered *#hct#root#
but i just get an incorrect password message, should there be a confirmation of root message?
thanks
Click to expand...
Click to collapse
I do not remember what the the confirmation said, but a toast bubble popped up on the screen. maybe it said "root enabled" something along those lines. But after it is rooted in the settings there will be a new menu called Superuser.
If *#hct#root# is not working try adbon then *#hct#root#.
But my system is a KitKat 4.4.4 so I know it will work on 4.4.4. However, I have a Joying unit. From what I read Joyous makes a good number of these units but not all. I have no idea if your particular unit is compatible. Read the [url="http://forum.xda-developers.com/showthread.php?t=2660662'] mega thread[/url] I think the various makers are addressed in there somewhere.
.
tmiller101 said:
I do not remember what the the confirmation said, but a toast bubble popped up on the screen. maybe it said "root enabled" something along those lines. But after it is rooted in the settings there will be a new menu called Superuser.
If *#hct#root# is not working try adbon then *#hct#root#.
But my system is a KitKat 4.4.4 so I know it will work on 4.4.4. However, I have a Joying unit. From what I read Joyous makes a good number of these units but not all. I have no idea if your particular unit is compatible. Read the [url="http://forum.xda-developers.com/showthread.php?t=2660662'] mega thread[/url] I think the various makers are addressed in there somewhere.
.
Click to expand...
Click to collapse
This code definitely does not work on my head unit unfortunately, just tried it several times, it states 'password incorrect'. And checked with a root checker app and supersu, definitely not got root

Nougat 7.1.1 is rolling out!

Hey everyone, been a little while, but 7.1.1 N is rolling out to you guys.
Awesome! Is this the same 108 build that went out to beta testers?
Does it include the battery optimization that was mentioned some time ago?
***
New update appears to be uncertified and Android Pay doesn't work.... any way to fix this?
ipowyourface said:
New update appears to be uncertified and Android Pay doesn't work.... any way to fix this?
Click to expand...
Click to collapse
Is your bootloader unlocked?
Nextbit_Khang said:
Is your bootloader unlocked?
Click to expand...
Click to collapse
No, I relocked it after I flashed the image and turned off the oem unlocking option after. I was previously rooted though, but the script on the image should have taken care of that right?
ipowyourface said:
No, I relocked it after I flashed the image and turned off the oem unlocking option after. I was previously rooted though, but the script on the image should have taken care of that right?
Click to expand...
Click to collapse
Yeah that's kinda weird. It should work. I'll ask around.
Nextbit_Khang said:
Yeah that's kinda weird. It should work. I'll ask around.
Click to expand...
Click to collapse
Yeah, there was another person on the Razer forums who had the same problem as well.
Just got my Nextbit today updated few times before work on 7.0 present and update pending hopefully 7.1.1 , How's the update ? any issues fixed not had it long enough to find any
Sent from my Robin using Tapatalk
Nextbit_Khang said:
Yeah that's kinda weird. It should work. I'll ask around.
Click to expand...
Click to collapse
I figured it out, I had just came from Omni Rom. For some reason, I had to flash the 6.0 image then flash the 7.1.1 image and now everything passes, and AP works.
ipowyourface said:
I figured it out, I had just came from Omni Rom. For some reason, I had to flash the 6.0 image then flash the 7.1.1 image and now everything passes, and AP works.
Click to expand...
Click to collapse
You had to re-lock your bootloader also, correct?
Is anybody having issues with sending text messages (your standard text message) with WiFi on? Not over WiFi, but just with WiFi on. I tried the default messaging app and the Google one. They both work the same. For me to get a text message out, I have to turn off WiFi.
I flashed stock N88 and still have TWRP recovery installed I got a system update that updated now stock on nextbit logo on boot , is this coz I still have TWRP recovery or just bad update would factory reset in TWRP fix ? Thanks
Sent from my MotoG3 using Tapatalk
DoobyDroid said:
I flashed stock N88 and still have TWRP recovery installed I got a system update that updated now stock on nextbit logo on boot , is this coz I still have TWRP recovery or just bad update would factory reset in TWRP fix ? Thanks
Click to expand...
Click to collapse
Why don't you flash the latest factory image?
You can't flash an OTA update via custom recovery.
Loving this new update!
However, if you want to save resources and please your customers at the same time when doing the next update -
skip the nextbit bits.
Just make the next updates (if you plan on making any more of course) stock, for all intents and purposes, except perhaps for the backup/cloud feature.
revert back to 7.0 ?
since i updated to 7.1.1, my pebble 2 would constantly disconnect.
how to revert back to plan 7.0 ?
thanks!
Any word on android 8
Franzferdinan51 said:
Any word on android 8
Click to expand...
Click to collapse
Lmao very doubtful
hey there guys i'm having this weird trouble updating to 7.1.1, i'm currently on 7.0 (Robin_Nougat_88) and i have downloaded the 7.1.1 update (560 mb) and when i hit the "reboot and install" button it say restarting in 10 ... 9... 8 blah blah then rebooting now and never get to reboot... i can't install this update is there some solution? do i have to install the N108 image like new following the razer thread? thanks in advice guys have a good day!

Shield Oreo

It's possible that it comes today/tomorrow at some point!!
Source: https://twitter.com/nvidiashield/status/913265527480475648
Yes, major speculating here, but usually Nvidia is very very quick with updates. SO let's all hope and pray. This COULD also be the Nvidia Spot announcement/availability.
Tomorrow 29th or today 28th. Their message is very cryptic. Google Assistant was just released for Nvidia Shield TV! Not Oreo unless they have their own announcement since Assistant one was by Google
Apparently some people are updating to Oreo already. But it looks like US only. :crying:
edit...not Oreo
kalinskym said:
Tomorrow 29th or today 28th. Their message is very cryptic. Google Assistant was just released for Nvidia Shield TV! Not Oreo unless they have their own announcement since Assistant one was by Google
Click to expand...
Click to collapse
Yes, correct. It was assistant that was released! http://www.androidpolice.com/2017/09/28/assistant-finally-come-shield-tv-looks-great/
JoeFCaputo113 said:
Yes, correct. It was assistant that was released! http://www.androidpolice.com/2017/09/28/assistant-finally-come-shield-tv-looks-great/
Click to expand...
Click to collapse
Unfurtunately only in U. S.... Hopefully there will be a way to get it, elsewhere
Kantraz said:
Unfurtunately only in U. S.... Hopefully there will be a way to get it, elsewhere
Click to expand...
Click to collapse
Wonder if changing the language to English US will force it to work like with phones. I'll have a play about tonight.
Also...from what I understand this is Nvidia Experience 6 and not Oreo. The new launcher is not yet here for the shield.
dunjamon said:
Wonder if changing the language to English US will force it to work like with phones. I'll have a play about tonight.
Also...from what I understand this is Nvidia Experience 6 and not Oreo. The new launcher is not yet here for the shield.
Click to expand...
Click to collapse
Hopefully it is enough, gonna try as soon as I get home from work!
Kantraz said:
Hopefully it is enough, gonna try as soon as I get home from work!
Click to expand...
Click to collapse
Snap! I've already told the missus to plug in the controller to get it charged up and ready. Ha!
dunjamon said:
Snap! I've already told the missus to plug in the controller to get it charged up and ready. Ha!
Click to expand...
Click to collapse
I can confirm that Google Assistant, can be enabled by changing the language
Just got the update. But it failed to install. It downloads the update and restarts the shield, but never finishes the install. Stops at about 20% on the Android System Update Screen then restarts back to the home screen asking if I want to install the Experience 6.0 update. Is it because I'm rooted? I don't have TWRP installed but I do have superuser installed....Tried 3 times.
dk1keith said:
Just got the update. But it failed to install. It downloads the update and restarts the shield, but never finishes the install. Stops at about 20% on the Android System Update Screen then restarts back to the home screen asking if I want to install the Experience 6.0 update. Is it because I'm rooted? I don't have TWRP installed but I do have superuser installed....Tried 3 times.
Click to expand...
Click to collapse
I always remove root then do the update. No TWRP either but it would always fail on me.
dk1keith said:
Just got the update. But it failed to install. It downloads the update and restarts the shield, but never finishes the install. Stops at about 20% on the Android System Update Screen then restarts back to the home screen asking if I want to install the Experience 6.0 update. Is it because I'm rooted? I don't have TWRP installed but I do have superuser installed....Tried 3 times.
Click to expand...
Click to collapse
Got #root#?!
If so, well there's your problem. You can NOT update in the conventional way once your rooted. In short you'll have to first download, and use fastboot, to flash the last 5.0.x Recovery For (Chiefly Recovery, System, and Vendor), and then most likely as not do a full system reset. Which if your unfortunate to be doing this on a Pro. Will mean about roughly 2.5h's+ of downtime. Before you'll then need to worry about the latest Update.
Unfortunately I keep telling myself to never root the damned thing again. 'Cause this IS a huge PitA! but, somehow I never learn.
JagXK8 said:
I always remove root then do the update. No TWRP either but it would always fail on me.
Click to expand...
Click to collapse
Alas One does NOT just remove root on the Shield. And, sadly 'cause of it. The only way I know of to be rid of it is flashing a new (Clean Recovery OS), and then factory resetting it fresh for the "New OS" to actually get written. Otherwise root seem to longer like a bad smell on the Shield.
And, now an aside...
Where is all this scuttlebutt about Oreo (Cookie), coming from?
Having done the above... (Sigh again!) I just finished wrapping up that part of the Install. When it occurred to me to check the Version... Which is still Android 7 (e.g. Nougat), so unless someones getting something I'm not. Then, this is not the Chocolate Wafer Cookie your looking for....
Which begs a different question. Why are they calling this "Experience 6..x", and not 5.x.x?
Ichijoe said:
Got #root#?!
If so, well there's your problem. You can NOT update in the conventional way once your rooted. In short you'll have to first download, and use fastboot, to flash the last 5.0.x Recovery For (Chiefly Recovery, System, and Vendor), and then most likely as not do a full system reset. Which if your unfortunate to be doing this on a Pro. Will mean about roughly 2.5h's+ of downtime. Before you'll then need to worry about the latest Update.
Unfortunately I keep telling myself to never root the damned thing again. 'Cause this IS a huge PitA! but, somehow I never learn.
Alas One does NOT just remove root on the Shield. And, sadly 'cause of it. The only way I know of to be rid of it is flashing a new (Clean Recovery OS), and then factory resetting it fresh for the "New OS" to actually get written. Otherwise root seem to longer like a bad smell on the Shield.
And, now an aside...
Where is all this scuttlebutt about Oreo (Cookie), coming from?
Having done the above... (Sigh again!) I just finished wrapping up that part of the Install. When it occurred to me to check the Version... Which is still Android 7 (e.g. Nougat), so unless someones getting something I'm not. Then, this is not the Chocolate Wafer Cookie your looking for....
Which begs a different question. Why are they calling this "Experience 6..x", and not 5.x.x?
Click to expand...
Click to collapse
I don't know about any Oreo update, but I updated to the new release without doing any data reset. Simply boot to fastboot and flash the downloaded system.img, boot.img, and recovery.img. No need to clear data. Then in the system you can install the OTA as normal and re-root using TWRP and Magisk/SuperSu.
eelsid said:
I don't know about any Oreo update, but I updated to the new release without doing any data reset. Simply boot to fastboot and flash the downloaded system.img, boot.img, and recovery.img. No need to clear data. Then in the system you can install the OTA as normal and re-root using TWRP and Magisk/SuperSu.
Click to expand...
Click to collapse
Can you elaborate on this? Maybe post a small guide? I am bootloader unlocked, and currently rooted, but recovery is stock. Where do I get the files you are talking about? Download, boot, and recovery img files? Thanks in advance!
bradleyw801 said:
Can you elaborate on this? Maybe post a small guide? I am bootloader unlocked, and currently rooted, but recovery is stock. Where do I get the files you are talking about? Download, boot, and recovery img files? Thanks in advance!
Click to expand...
Click to collapse
I found this guide here: https://forums.geforce.com/default/topic/667705/-guide-how-to-update-a-rooted-nvidia-shield/
I actually found this helpful guide for updating if you are on a pro and unlocked. http://nvidiashieldzone.com/2017/10/shield-tv-pro-500gb-experience-6-0-upgrade-solution/

Warning for Canadians waiting for Pie

I just got the ota notification this morning, updating it and bricked the damn thing.
Phone wasn't rooted, rebranded or anything, straight OTA messed it up. It boots straight to erecovery, and nothing can be done with it. Hisuite don't work either
Fastboot & rescue mode says
Android reboot issue
Bootloader 1
no
N/A
Reboot_enter_fastboot_common_function
I'm new to Huawei, so how df can I fix it?
In eRecovery, can you enable wifi, connect to wifi, download whole package?
That SHOULD be possible actually!
EML-L29 via Tapatalk
Kaherdin said:
In eRecovery, can you enable wifi, connect to wifi, download whole package?
That SHOULD be possible actually!
EML-L29 via Tapatalk
Click to expand...
Click to collapse
Does not work, says failed to gather package info
https://forum.xda-developers.com/huawei-p20-pro/how-to/upgrade-to-android-pie-throught-t3884054
oslo83 said:
https://forum.xda-developers.com/huawei-p20-pro/how-to/upgrade-to-android-pie-throught-t3884054
Click to expand...
Click to collapse
Not luck with that either, failed to gather package info
So use your huawei warranty.
oslo83 said:
So use your huawei warranty.
Click to expand...
Click to collapse
thats what I ended up doing, still trying though
The update just became available to me tonight on public mobile. Im going to try to take it tonight maybe. I know when i downloaded it from firmware finder before it actually became approved, it wasnt the size it said it should have been when it finished downloading. Im wondering if it is corrupt. It's C792 for Kirin 970. I also dont see it on androidhost.
Ok so i took the update through software update app built into the phone and everything went fine. Seems like the phone may even be a tad snappier. Still no expandable notifications though.

Categories

Resources