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.

Flash stock software update through TWRP?

First of all this phone belongs to my dad. This means I haven't used it and I'm not familiar with many things about it.
The phone is running a stock ROM. It is not rooted, but it does have TWRP.
A software update prompt popped up trying to install "v20p-apr-03-2018" (why is an update for the G4 called v20 lol).
Telling it NOT to download it and NOT check for updates ever doesn't work. The update prompt comes back in 2 days tops. So **** you LG.
Since it's not rooted the easiest option seems to be to flash the update, however it just launches TWRP and does nothing. I found no way to actually download the update and keep it on the device so that I can manually tell TWRP to flash it.
So: Is there a way to download said update and flash it through TWRP? Or should I root it and delete the stupid update tool? I really don't want to flash a stock recovery.

ast00 said:
First of all this phone belongs to my dad. This means I haven't used it and I'm not familiar with many things about it.
The phone is running a stock ROM. It is not rooted, but it does have TWRP.
A software update prompt popped up trying to install "v20p-apr-03-2018" (why is an update for the G4 called v20 lol).
Telling it NOT to download it and NOT check for updates ever doesn't work. The update prompt comes back in 2 days tops. So **** you LG.
Since it's not rooted the easiest option seems to be to flash the update, however it just launches TWRP and does nothing. I found no way to actually download the update and keep it on the device so that I can manually tell TWRP to flash it.
So: Is there a way to download said update and flash it through TWRP? Or should I root it and delete the stupid update tool? I really don't want to flash a stock recovery.
Click to expand...
Click to collapse
Freeze or uninstall Software Update (LG proprietary, i.e., closed source, app) - may require root. That should stop the annoying requests. If you are able to upgrade you will lose TWRP and will have to re-flash TWRP again. You may want to consider that you do not have the latest Google security patches by not doing the update, putting your Dad's phone more at risk.

sdembiske said:
Freeze or uninstall Software Update (LG proprietary, i.e., closed source, app) - may require root. That should stop the annoying requests. If you are able to upgrade you will lose TWRP and will have to re-flash TWRP again. You may want to consider that you do not have the latest Google security patches by not doing the update, putting your Dad's phone more at risk.
Click to expand...
Click to collapse
It's not like LG updates security patches that often so it's not that big of a deal if I can't update it.
It's also fine if I lose TWRP during the process, I just want to avoid flashing stock recovery just for the sake of updating it.
And I still can't download the update and keep it. I don't know where it puts the update after downloading it. I couldn't find it in TWRP.

ast00 said:
It's not like LG updates security patches that often so it's not that big of a deal if I can't update it.
It's also fine if I lose TWRP during the process, I just want to avoid flashing stock recovery just for the sake of updating it.
And I still can't download the update and keep it. I don't know where it puts the update after downloading it. I couldn't find it in TWRP.
Click to expand...
Click to collapse
It helps if you include your phone model when looking for specific firmware updates.
If you're Dad's phone is an H815, there are some v20p downloads available here: https://lg-firmwares.com/lg-h815-firmwares/firmwares/
In order to flash in TWRP without losing TWRP, you would have to remove the stock recovery and create a flashable zip ...
Easiest is to simply freeze or remove the lg Software Update app as I indicated - the annoying update notification should then disappear ...
Note: XDA courtesy is to hit the Thanks button (bottom right of post), when members are trying to help and solve your issues. As a Senior Member you know this.

This update does not contain any security fixes it's just for the new European data protection law..
First thing you should try is:
Upgrade TWRP.
Do a full TWRP backup!
Test android update again.
Second thing:
Have you tried the LG bridge windows software to update?
If so and it fails there too you can find the update when you try to Flash it within the LG folder of your Windows PC afterwards use this KDZ file and lgup to flash it.
There is a chance that when using the internal updater that you can find the update file when in TWRP in /cache in a folder fota but it will likely be in a LG specific format so may don't help you much.
Third thing :
Disable the LG updater within TWRP (search for a howto)
Sent from my LG-H815 using XDA Labs

Question 11.2.5.5LE15AA Update Error

Is anyone else getting this or does anyone know of a solution to this? It basically tries to download and fails immediately on WiFi and cellular. I wish I could get the update from OP but of course it's still not listed.

awarman said:
Is anyone else getting this or does anyone know of a solution to this? It basically tries to download and fails immediately on WiFi and cellular. I wish I could get the update from OP but of course it's still not listed.
Click to expand...
Click to collapse
are you rooted?

Yes but I have removed root and tried, same thing. Cleared dalvik cache, same thing.

Try using the oneplus updater apk. https://play.google.com/store/apps/details?id=com.arjanvlek.oxygenupdater

hallo dare said:
Try using the oneplus updater apk. https://play.google.com/store/apps/details?id=com.arjanvlek.oxygenupdater
Click to expand...
Click to collapse
I have but it doesn't show incremental updates. It just proclaims that I'm up to date.

awarman said:
I have but it doesn't show incremental updates. It just proclaims that I'm up to date.
Click to expand...
Click to collapse
You won't get incremental if rooted, only full updates.

hallo dare said:
You won't get incremental if rooted, only full updates.
Click to expand...
Click to collapse
So in theory, if I unroot then run OnePlus updater I should be able to get the update. Then reboot after. Correct?

Maybe I did something wrong, but I tried unrooting for the last OTA and still received the same error. I had to wait until the full version was on the OnePlus site, I think OnePlus updater grabs the zip from there too. It also took a month longer for the full zip to hit the OnePlus site.

Flash the stock boot.img and then try again. It should update. Just make sure you use the correct boot.img for the version your currently on

I have global unlocked varient and when I first received it I just flashed BA/EU on both slots(local upgrade twice) and I've been able to get all full zip updates(via system updates and/or O2 updater app) staying rooted the whole time. I'm in US on tmo, I'm wondering what could have been so beneficial some ppl want to stay on AA/glo builds.?

Initially I was getting that error. Then I ran the uninstall in Magisk and chose to RESTORE IMAGES. I then just hit retry on the OTA from the phone settings (NOT Oxygen Updater) and the update installed. Initially this did not for 11.2.3.3 as it would still give the error after unrooting by uninstalling Magisk, then it worked for 11.2.4.4 and 11.2.5.5. So YMMV. You can look here for my update process as I was having an issue post-OTA:
No cell service after update to 11.2.4.4AA while keeping root
I'll try to keep this short. Global OP9 Pro on 11.2.2.2AA, bootloader unlocked, rooted w/Magisk. Been trying to find the best way to update. Decided on trying this: 1. Un-rooting by going in to Magisk and doing UNINSTALL->RESTORE IMAGES 2...
forum.xda-developers.com

jammin6996 said:
Flash the stock boot.img and then try again. It should update. Just make sure you use the correct boot.img for the version your currently on
Click to expand...
Click to collapse
This worked, btw. Never had to do this with my OP8P. Hopefully this isn't a regular occurrence.

Shooter7889 said:
I'm in US on tmo, I'm wondering what could have been so beneficial some ppl want to stay on AA/glo builds.?
Click to expand...
Click to collapse
Not knowing that the AA variant would have dog**** updates from the start, and already having restored my old phone's data and not wanting to go through setup and restore again.
Edit: The goal is also to eventually get on crDroid anyway so it's whatever. I'm not resetting until there's an official crDroid build out.

12.5 update on QGGMIXM

So, this may be a dumb question but I can't seem to find the answer anywhere. I have my phone for almost two years now, and it used to get the updates the right way, until the 12.0.7, then it just stopped getting any updates, when I checked it says "no updates avaliable".
Searching yesterday, I manage to update it to 12.0.8 by changing the device region to India, but it just stopped there, I can't update to 12.5 or further.
While searching i've seen that the devices different from QGGMIXM (which mine is), like RGGMIXM already got the updates.
I even tried to install the 12.5 update (for RGGMIXM) manually and it said it could not verify the update.
Is there any way to change QGGMIXM to RGGMIXM or to get the update without changing it? Any help are appreciated

Illyve1 said:
So, this may be a dumb question but I can't seem to find the answer anywhere. I have my phone for almost two years now, and it used to get the updates the right way, until the 12.0.7, then it just stopped getting any updates, when I checked it says "no updates avaliable".
Searching yesterday, I manage to update it to 12.0.8 by changing the device region to India, but it just stopped there, I can't update to 12.5 or further.
While searching i've seen that the devices different from QGGMIXM (which mine is), like RGGMIXM already got the updates.
I even tried to install the 12.5 update (for RGGMIXM) manually and it said it could not verify the update.
Is there any way to change QGGMIXM to RGGMIXM or to get the update without changing it? Any help are appreciated
Click to expand...
Click to collapse
1/ Try to use vpn app and change to other
2/ Try method downgrade with ota on youtube
3/ Unlock bootloader and flash rom you want by twrp or mi flash tool

Kirasu2080 said:
1/ Try to use vpn app and change to other
2/ Try method downgrade with ota on youtube
3/ Unlock bootloader and flash rom you want by twrp or mi flash tool
Click to expand...
Click to collapse
1/ Just tried vpn, didn't work
2/ Neither downgrading or upgrading worked, downgrading says it's unable to downgrade and tried to upgrade says it couldn't verify the update
3/ I haven't tried this yet, but I'm guessing it'll be the only way to update it.

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