Develop Bugs

Recently updated to A5FMB19

I purchased the tablet online in China about two months ago, so I got a tablet running CN system. (A5CN51C as I got it.)
So I followed a manual and immediately flashed a A5FM51C system.img to my tablet.
When the OTA A5FM91E came, I checked up this forum, only found high risk of updating.
While today, while I consulted a Chinese forum, there is a method to safely update the tablet to a newer version of system without converting back to CN systems ( meanwhile the boot is still lost after updating ! )
Basically, for all who initially has a CN system installed and successfully converted to TW version, there is a way to update your system while keeping all google frameworks.
Method is listed below.
1. Enable developper mode and USB debugging, and connect to PC using adb.
2. Flash the corresponding boot.img and recovery.img to the tablet. (By saying corresponding, it's the boot.img and recovery.img must match the version you're using. For eg, I'm updating from a A5FM51C version, so I should at least have a boot.img and recovery.img of A5FM51C.)
Below you can find the boot.img and recovery.img of A5FM51C.
HTML:
http://pan.baidu.com/s/1gdwKN7P
Password 2jwi
or https://www.dropbox.com/sh/drmfv30k54jgb35/AABc9uPxpOSUNHsV1lSD-k_1a?dl=0
command on adb shell should be like :
Code:
su
dd if=/sdcard/recovery.img of=/dev/block/pci/pci0000:00/0000:00:01.0/by-name/recovery
dd if=/sdcard/boot.img of=/dev/block/pci/pci0000:00/0000:00:01.0/by-name/boot
3. After rebooting once and rebooting into recovery mode, check if the recovery is converted to the targeted version.
As I am updating to a system with Google applications, I should check if the version is marked FM.
4. In the recovery mode, side load the updating zip files, after a patient waiting, the system should be successfully updated.
ATTENTION ! [/SIZE]the zip file should be a full updating file, NOT A PATCH zip. So the file you are side loading is at least 300+ M.
If you are updating from A5FM51C, you can directly download from the links below two files.
HTML:
A5FM91E 848.38M
http://ota-service.oss.fc811.com/upload/Nokia/moorefield/Nokia_N1/N1-tw2015/A5FM91E_update.zip
A5FMB19 816.04M
http://ota-service.oss.fc811.com/upload/Nokia/moorefield/Nokia_N1/N1-tw2015/A5FMB19_update.zip
5. The first time booting the updated system could be time consuming, so take a cup of coffee and be patient.
All credits should be given to the Baidu Tieba user "遇上咨询", and if you happened to be capable to read Chinese, you can visit http://tieba.baidu.com/p/4174802149 for further consult.
PS.
I updated from A5FM51C firstly to A5FM91E, after once rebooting normally into the system, I then updated again to A5FMB19, just being careful not to cause any damage.
And after updating there could be several applications crash unconditionally, since I've been using the system for less than 24 hours, I am not sure if this situation can be optimised after a period of time.
So the update only brought the Android version to 5.1.1, and Nokia added a "Close all app" button in the overview. Consider again if you are willing to spend one hour to update the tablet into a very similar system !
Wish you luck.

Update
As soon as I finished updating the "System Webview" app to newest version at Play, all those apps started running again

Neegola said:
Update
As soon as I finished updating the "System Webview" app to newest version at Play, all those apps started running again
Click to expand...
Click to collapse
i'm update to A5CNB19 today. How can move Chinese to Taiwan?

thanks for your post, is there any chance to make it rooted in A5FMB19 ??
thanks

p233 said:
i'm update to A5CNB19 today. How can move Chinese to Taiwan?
Click to expand...
Click to collapse
Originally, I converted my tablet at A5CN51C, with root. Following this manual.
http://forum.xda-developers.com/nokia-n1/general/n1-taiwan-release-t3083115/post62313790
So using this method to convert, you should guarantee a valid root state executing DD command on adb shell.
So I personally think that at least you should wait for a root method, then there would be a chance for converting system.

I directly updated from A5FM51C to A5FMB19 (not went through A5FM91E . confirmed it's okie with this method

Thanks a lot. I confirm that we can directly update from A5FM51C to A5FMB19. I just have a question, if an update release can i do the update by the ota ? Sorry for my bad english.

Xiware said:
Thanks a lot. I confirm that we can directly update from A5FM51C to A5FMB19. I just have a question, if an update release can i do the update by the ota ? Sorry for my bad english.
Click to expand...
Click to collapse
After converting the recovery and boot partitions to FM version, there should not be a problem in updating directly by OTA.
Before, when I execute OTA, it will pop up a message read "Could not download the update, please check the storage". And after, I could successfully start the download. It was because the limited network speed, I've chosen to side load the update package.
But it's merely my guess. Since the tablet has at least 20 partitions, and I don't know if there's any other which could influence this process. Maybe we could invite a real expert to join in this discussion.

Are you update with OTA?

gazziandrea said:
Are you update with OTA?
Click to expand...
Click to collapse
No.
But technically I did use the ota package to update. Given it was a whole system compressed file.

Neegola said:
No.
But technically I did use the ota package to update. Given it was a whole system compressed file.
Click to expand...
Click to collapse
I did rootare the devise to other people ( chinese guys) and i dnot have many experience in modding, only with TWRP in Xiaomi Redmi Note 2, so I can update via OTA diretly ?

gazziandrea said:
I did rootare the devise to other people ( chinese guys) and i dnot have many experience in modding, only with TWRP in Xiaomi Redmi Note 2, so I can update via OTA diretly ?
Click to expand...
Click to collapse
Hi, I'm afraid I don't understand what you are asking.
Do you speak any other languages like Chinese or French, or your native language so I can do a google translate ?

Thanks for these updated information.

Hi, guys, thank you for help with moving from CN to TW. I've done this from rooted A5CN51C to A5FMB19.
But, now I've got system reboot every 15 min. Uptime no more than 30-35 min. It's very unstable during watching video (e.g. youtube app). Do you have the same? Model: n1s.
Hard reset doesn't solve this problem.

Reinstall Android wear 2.0?

I had updated by using the spam update trick, but I had forgotten to reset my watch before that. Here are a few problems that accured because of that:
- unable to link Google account during setup. Was able to link afterwards after a bit of difficulty.
- Bluetooth keeps disconnecting from phone. Problem only started a few days ago.
- overall buggy performance. Even though it is rumered that a second core was enabled.
- suprisingly better battery life! That's not a problem isint it? :silly:
To solve these problems I tried resetting but to no avail. So the only thing to do is try reinstalling the stock firmware. I still have warrenty so I don't want to unlock the bootloader right now. I know that you can restore a stock system image on phones without unlocking the bootloader. I would prefer an 2.0 system image.
Is there a method available?

164 views and no comments.

Soneliem said:
I had updated by using the spam update trick, but I had forgotten to reset my watch before that. Here are a few problems that accured because of that:
- unable to link Google account during setup. Was able to link afterwards after a bit of difficulty.
- Bluetooth keeps disconnecting from phone. Problem only started a few days ago.
- overall buggy performance. Even though it is rumered that a second core was enabled.
- suprisingly better battery life! That's not a problem isint it? :silly:
To solve these problems I tried resetting but to no avail. So the only thing to do is try reinstalling the stock firmware. I still have warrenty so I don't want to unlock the bootloader right now. I know that you can restore a stock system image on phones without unlocking the bootloader. I would prefer an 2.0 system image.
Is there a method available?
Click to expand...
Click to collapse
To restore the stock 2.0 image without unlocking your bootloader, you would need the officially signed 2.0 firmware package from Google/Huawei. These packages are easy to get for phones because carriers will often have a "repair tool" that downloads the full package and flashes it. Once downloaded, the package is easy to capture and upload for everyone else to have. I'm aware of no such tool for the HW, and I don't think that Google posts the full firmware packages anywhere other than the 1.5 package that they posted on the AW 2.0 dev preview site.
So without unlocking your bootloader, the answer to your question is no. If you want to unlock it, you can flash the 1.5 image and then OTA back to 2.0.

TheSt33v said:
To restore the stock 2.0 image without unlocking your bootloader, you would need the officially signed 2.0 firmware package from Google/Huawei. These packages are easy to get for phones because carriers will often have a "repair tool" that downloads the full package and flashes it. Once downloaded, the package is easy to capture and upload for everyone else to have. I'm aware of no such tool for the HW, and I don't think that Google posts the full firmware packages anywhere other than the 1.5 package that they posted on the AW 2.0 dev preview site.
So without unlocking your bootloader, the answer to your question is no. If you want to unlock it, you can flash the 1.5 image and then OTA back to 2.0.
Click to expand...
Click to collapse
Thanks, that was my fear. I will restore to 1.5 and then upgrade. Thanks for your in-depth explanation.

SHIELD Experience 6.0 upgrade just released - Worth upgrading?

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

Android 11 OTA takes forever on sideload

Hello,
I'm trying to install Android R DP2 update with sideload, but i'm stuck at Verifying update package, been stuck for like 1 hour and nothing happens, in cmd there's no Serve and percentage text... What might be the problem?
I'm on stock rom, latest update, no root, locked bl

I've same problem. Do you found a solution already?

rgj8 said:
I've same problem. Do you found a solution already?
Click to expand...
Click to collapse
Nope, just gave up until OTA i guess... have no idea why tho and there is no threads around about same problem

It worked for me maybe try redown loading the OTA.
The biometrics for most of my apps do not work on DP2. They were working on DP1. Since I made the mistake of using my Verizon version instead of my unlocked one I'm stuck either waiting for DP3 or the beta version as the only option to downgrade back to 10.

wolfu11 said:
It worked for me maybe try redown loading the OTA.
The biometrics for most of my apps do not work on DP2. They were working on DP1. Since I made the mistake of using my Verizon version instead of my unlocked one I'm stuck either waiting for DP3 or the beta version as the only option to downgrade back to 10.
Click to expand...
Click to collapse
I'm on Verizon as well... and well re-downloading OTA did not work for me, i have tried that one too...

USB C to USB 2.0 will work. USB C to C will not, ADB doesn't have the proper protocols to work with it.

Make sure your adb and fastboot are up to date.

Question Android 13 beta 3.3 won't install ...

Having issues installing beta 3.3 on my 6 pro.. did a factory reset then tried installing it. First time it took forever to install and phone rebooted and had missing operating system so I had to factory reset.. second time I got a failed to install message.. rebooted the phone and it said no operating system please visit this link from another device.. rebooted then phone worked normal.. what is going on here ? Phone is purchased from att, so idk if it's considered global version but whatever either way . Is there something stopping it from being installed? Was trying to do all this OTA.. thanks kinda new to it

I'm not sure if it being an att version has anything to do with it or not.. maybe the version google releases is only working on unlocked global models?? Someone shine some light on this..

You can use https://flash.android.com/ to flash with a computer.

So why would the flash tool work but not the ota method ?? Really curious cause when the official comes out hopefully I can flash that ota without any issues.. right now I opted out of the beta cause I really want the ota method to work and it doesn't ..

Can someone tell me why the ota wouldn't install ? Installed it the way I installed any other update on the phone through check for updates.. Id rather get ota working vs hassling with a computer to install it. That can mess things up if done wrong .

Is it failing to ota install the beta cause of a locked bootloader ? It does fine with install ota security patches on Android 12. Trying to install 13 ota on the phone itself fails.. I don't see why that would be though ?

@Redbeardkevv Welcome to XDA. Instead of posting multiple times in a row, please use the Edit button to edit your post and just add to it, in the future.
Official Google Android Flash Tool (OEM Unlocking needs to be toggled on - you may not have to manually unlock the bootloader - the "site" will do that on its own)
^ That Google site has saved many users on XDA. It has revived or corrected a mistake on their devices (mine too, once) when even flashing the full factory image didn't fix the problem. I have no idea what exactly it does that manually flashing doesn't. I normally use the full factory image zip, and that alone sometimes fixes issues that users have when they have issues flashing via the OTA method.

Oem unlocking toggled on isn't an option on this phone , purchased at att . I'll just wait till they release the official ota. But what would of been holding it up and making the installs corrupt??

Redbeardkevv said:
Oem unlocking toggled on isn't an option on this phone , purchased at att . I'll just wait till they release the official ota. But what would of been holding it up and making the installs corrupt??
Click to expand...
Click to collapse
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developer.android.com
Important excerpt:
Android Flash Tool guides you step-by-step through the process of flashing your device—there's no need to have tools installed—but you will need to unlock your device and enable USB Debugging in Developer options.
Click to expand...
Click to collapse
If I remember correctly from other AT&T variant Pixel 6 Pro users in this section, once you pay off the phone and/or own the phone for long enough, AT&T should carrier unlock the phone, and that will likely make it so that you can OEM Unlocking and unlock the bootloader. (this also applies to T-Mobile, but does not apply to Verizon)

Well it's a far ways from being paid off I'll just add that .. what are my flashing options ? Also why would a security patch install just fine, then I enroll into beta ,try to install it, and bam it won't install and is corrupt install. Just doesn't seem right to me.. should I just wait until official release early August and then the OTA install from phone will work ?

Why would a security patch install without any issue , but I go to install this beta 13 and it fails and is corrupt . Same method as installing a security patch , only difference is beta won't install . Will it install correctly OTA when they release the final version in August ???

Redbeardkevv said:
Why would a security patch install without any issue , but I go to install this beta 13 and it fails and is corrupt . Same method as installing a security patch , only difference is beta won't install . Will it install correctly OTA when they release the final version in August ???
Click to expand...
Click to collapse
Firstly, unlocked bootloader is required to flash custom or beta firmware. While you can sideload OTA packages on a locked bootloader, I would highly recommend against doing so as you may end up with no way to recover your device.
When installing a beta, it is generally best to wipe and perform a clean flash. OTA is not recommended because beta software by nature is not yet suitable for public release, and may not appropriately handle everything correctly coming from older firmware.
As has been mentioned before, I recommend you use the Android Flash Tool to flash the beta. To ensure you have a fresh start, tick the Wipe device and Force flash all partitions boxes. Do not re-lock the bootloader.

So in short, wait for the official ota to roll out in August and install from phone then?? Cause I won't be able to unlock bootloader , phones not paid off... Would this explain why it's failing to install an beta from within the phone itself cause the bootloader's locked? So I have to wait for official ota rollout like I said earlier ??

Redbeardkevv said:
So in short, wait for the official ota to roll out in August and install from phone then?? Cause I won't be able to unlock bootloader , phones not paid off... Would this explain why it's failing to install an beta from within the phone itself cause the bootloader's locked? So I have to wait for official ota rollout like I said earlier ??
Click to expand...
Click to collapse
Most likely. I doubt the beta will pass signature verification until it is updated to public release.

So not passing signature verification would be the reason it won't install ( ota ) most likely ? I'm just confused why a patch will install ota but the beta cannot .. must have something to do with bootloader being locked and it not being an official verified release or something

Just curious

Redbeardkevv said:
Just curious
Click to expand...
Click to collapse
Yes, you need the bootloader unlocked. So you cannot use those builds - only officially released OS builds.

NippleSauce said:
Yes, you need the bootloader unlocked. So you cannot use those builds - only officially released OS builds.
Click to expand...
Click to collapse
Well that explains it not installing and saying corrupted install ... Lol

Redbeardkevv said:
Well that explains it not installing and saying corrupted install ... Lol
Click to expand...
Click to collapse
It's a beta, so there will be issues for sure (but your last comment said you are getting an error [device is corrupt] that was common a few months ago so read on). You don't need to have an unlocked bootloader to enroll in the beta. Tons of users on Verizon and AT&T with a locked BL have installed the beta. Most are fine, some have had issues.
I wouldn't install a Beta on a locked BL. Why risk it? If something goes wrong, you'll need to get a warranty replacement. Seems like such a hassle.
For your issue, since you said you're getting a device corrupt message. This message is caused by q few different things (there's a thread on here about it). To fix it, users needed to do a factory reset in recovery mode. If you really wanted to try installing the beta (and you understand the risks), you'd probably need to: go to recovery mode and perform a wipe/factory reset.
From there, you could install the latest stable ota (via recovery mode) then see if the beta will update for you (via beta enrollment like you are trying to do), or directly flash the beta ota (link below). I'm just not sure if you can flash a beta ota image, over a stable build. I haven't tried it but according to xda, you can be on Android 12, and flash the Beta 13 ota (instructions found here).
There's two ways to flash an Android image: ota builds via recovery mode (doesn't require BL unlock) and factory image via fastboot which can be done manually or using Google's web flash tool (flash.android.com) - both if these require BL unlock.
You can find all the latest image downloads here. Google strongly recommends to flash the beta with an unlocked bootloader using their flash web tool. It's a beta so I would stay away until you can unlock your bootloader. Don't risk it. But I still think it might be a good idea for you to eventually perform a factory reset from recovery mode, since you are seeing the device is corrupt error message.

Had same problem, tried installing it twice and gave up