Database Develop

Android 4.4 KitKat installation failed on nexus 7 (2012)

Hello,
I had a problem with my nexus 7 today, hope someone will help me.
Today i got a notification that says, new android system has been downloaded.. touch to install..
So i tapped the notification, and if anyone who has nexus 7 and got an updated before.. he will know exactly mo problem.
So i clicked the button "reboot and install".. my device has been rebooted .. and there was that screen like cmd in Windows.. i remember some messages from it "MD5 not found" then the the deviced booted and didn't get Android kitkat update.
Information about my nexus 7 device:
1) It's rooted.
2) I've Android 4.3.
My Questions are:
1) How can i get that notification another time to try install it again?
2) When i go to Recovery.. Install.. I see the ZIP file for Android 4.4, it's name was "kataski" i think, my question if i flashed that ZIP file.. means i've installed kitkat manually, then i'll lose my auto updates?
Waiting for the reply.
Thanks

Mob_Dev said:
Hello,
I had a problem with my nexus 7 today, hope someone will help me.
Today i got a notification that says, new android system has been downloaded.. touch to install..
So i tapped the notification, and if anyone who has nexus 7 and got an updated before.. he will know exactly mo problem.
So i clicked the button "reboot and install".. my device has been rebooted .. and there was that screen like cmd in Windows.. i remember some messages from it "MD5 not found" then the the deviced booted and didn't get Android kitkat update.
Information about my nexus 7 device:
1) It's rooted.
2) I've Android 4.3.
My Questions are:
1) How can i get that notification another time to try install it again?
2) When i go to Recovery.. Install.. I see the ZIP file for Android 4.4, it's name was "kataski" i think, my question if i flashed that ZIP file.. means i've installed kitkat manually, then i'll lose my auto updates?
Waiting for the reply.
Thanks
Click to expand...
Click to collapse
Hi,
As per: http://forum.xda-developers.com/showpost.php?p=47648484&postcount=2342
OTAs will never work on a system which is modified in some way, because they contain only bytes which were changed between two Android versions. If files on the device are changed (custom ROM, different kernel, MultiROM-injected init, sometimes even root), OTA simply can't be applied. Everyone who roots his device should be aware of that.
Wait for the flashable ZIPs,
Click to expand...
Click to collapse
So, instead of OTA (over-the-air), you can simply download the image files directly from Google Android's site: https://developers.google.com/android/nexus/images#nakasi

topet2k12001 said:
Hi,
As per: http://forum.xda-developers.com/showpost.php?p=47648484&postcount=2342
So, instead of OTA (over-the-air), you can simply download the image files directly from Google Android's site: https://developers.google.com/android/nexus/images#nakasi
Click to expand...
Click to collapse
Aha, i see. So maybe because i've rooted my nexus 7, and i've also got a different kernel for MultiRom( I've installed ubunto touch on my device). ... Those the reasons that leads the installation to be failed?
Anyway, my system auto downloaded the update, it name was "nakasi".
I tried to go to Recover mode, and tried to flash the nakasi ZIP file and flash it,,, but the operation was failed!
What should i do?
How i get auto update installation for kitkat on my nexus 7?
Another question, if i downloaded the Factory image from the link you gave me: https://developers.google.com/android/nexus/images#nakasi and flash it in Recovery Mode... Let say it will success? then i''ll lose auto system update on my nexus in future - because it will be installed manually.
=========
Please Copy the questions in your reply, and post the reply below each one.
Thanks

You modified your rom, therefore, you cannot ota. Use the full images or restore the rom to normal (kernel and whatever else you did).

topet2k12001 said:
Hi,
As per: http://forum.xda-developers.com/showpost.php?p=47648484&postcount=2342
So, instead of OTA (over-the-air), you can simply download the image files directly from Google Android's site: https://developers.google.com/android/nexus/images#nakasi
Click to expand...
Click to collapse
That quote isn't exactly correct. My N7 (tilapia) is rooted, unlocked & twrp recovery. The OTA worked fine. I had to reroot (which us normal), but its clear evidence that's contrary to "OTA's will never work on a system that has been modified in some way". In fact, wug's toolkit thread has multiple comments where people go it the OTA after rooting, unlocking & installing a different recovery. That said, mods MAY result in OTA's failing.
Sent from my Nexus 7 using XDA Premium 4 mobile app

khaytsus said:
You modified your rom, therefore, you cannot ota. Use the full images or restore the rom to normal (kernel and whatever else you did).
Click to expand...
Click to collapse
Can you guide me how to install kitkat on my nexus 2012 - rooted and modified ROM.
What do I need?

Another 4.4 Upgrade failure
I am having problems with the OTA upgrade too. However I am running a unmodified/rooted version of 4.3. I have also tried sideloading the factory zip and doing OTA and sideload from a factory reset.
I get the dead android and red triangle error and if I go to the restore menu then this is the error report I get each time
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
/system/apps/hangouts.apk produces some type of verfication error.
I can then reboot and I am back to 4.3
Any thoughts on solutions are gratefully recieved

Mob_Dev said:
Can you guide me how to install kitkat on my nexus 2012 - rooted and modified ROM.
What do I need?
Click to expand...
Click to collapse
You can use this ZIP( http://forum.xda-developers.com/showthread.php?t=2528090) file flash using recovery. You can use cyanogenmod window installer to give nexus new life and then revert to kitkat. Using that zip. This zip can update via ota. Just help
Sent from my Nexus 7 using XDA Premium 4 mobile app
PS: cyanogenmod window installer auto root your rom

dbgeek said:
That quote isn't exactly correct. My N7 (tilapia) is rooted, unlocked & twrp recovery. The OTA worked fine. I had to reroot (which us normal), but its clear evidence that's contrary to "OTA's will never work on a system that has been modified in some way". In fact, wug's toolkit thread has multiple comments where people go it the OTA after rooting, unlocking & installing a different recovery. That said, mods MAY result in OTA's failing.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
We are probably agreeing to refer to the same thing; maybe it was just a little miscommunication.
If we take only the first sentence of the quoted post "as-is", then it may contextually be construed as an over-generalization (to which, I agree that it is not exactly correct). However if we read the entirety of the quoted post, it was explained further that if a user has a "different kernel and multiROM-injected init), then OTA cannot be applied.
...to which, this thread's OP eventually mentioned that he has "a different kernel for MultiROM" installed.
But as far as being able to receive the OTA, yes I did receive it (rooted and running MultiROM); I just couldn't apply the OTA update. To solve, I performaed a "fresh install", i.e. download and install factory image method.

yusopa said:
You can use this ZIP( http://forum.xda-developers.com/showthread.php?t=2528090) file flash using recovery. You can use cyanogenmod window installer to give nexus new life and then revert to kitkat. Using that zip. This zip can update via ota. Just help
Sent from my Nexus 7 using XDA Premium 4 mobile app
PS: cyanogenmod window installer auto root your rom
Click to expand...
Click to collapse
I am following this guide to install Android kitkat on my nexus 2012 (Wifi only): http://www.droidviews.com/install-kitkat-factory-image-on-nexus/
But if you can see the last step satisfy that i need to flash the 4.4 Factory Image, type, using the following command:
fastboot -w update image-nakasi-krt16s.zip
Click to expand...
Click to collapse
The problem is that, the nakasi file i downloaded from here: https://developers.google.com/android/nexus/images
is not a ZIP file!. It's (.tar) file. And i can't process that command!!
Let me know what is the problem.
Thanks in advance

topet2k12001 said:
We are probably agreeing to refer to the same thing; maybe it was just a little miscommunication.
If we take only the first sentence of the quoted post "as-is", then it may contextually be construed as an over-generalization (to which, I agree that it is not exactly correct). However if we read the entirety of the quoted post, it was explained further that if a user has a "different kernel and multiROM-injected init), then OTA cannot be applied.
...to which, this thread's OP eventually mentioned that he has "a different kernel for MultiROM" installed.
But as far as being able to receive the OTA, yes I did receive it (rooted and running MultiROM); I just couldn't apply the OTA update. To solve, I performaed a "fresh install", i.e. download and install factory image method.
Click to expand...
Click to collapse
My bad. I read the "different kernel..." as an example of mods that might be made, that could cause failure, not a specific listing of mods that would cause a failure (implying that if the mod's not on the list then it wouldn't be a problem).

So i have the same problem, but aditionally my Windows 8 is unable to recognize my Nexus 7 while in recovery mode and i can't mount the sdcard to install a new rom. Only recognizes it as "grouper". Any advice?

I think Wug Fresh for nexus toolkit can help you guy to bring back your nexus to life. I use from the start.
Sent from my Nexus 7 using XDA Premium 4 mobile app

Stock Nexus 6 (Verizon) will not update!

Hi guys,
As I wrote in the title, my Verizon Nexus 6 will not update. When I get a notification for the software update, I see that it downloads and is ready to restart the phone so it will install the update...
but when I do, it will display the android icon with the word "error" above it. No error number or details about why it did not work.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Things I tried already are:
formatting the phone (both through the settings menu as well as the stock bootloader)
deleting data and cache in Google Services Framework (via settings/apps/all apps)
I have more than enough space in my storage; more than 2/3rds of my storage is free space, so I really am having trouble wrapping my head around why this software update is failing to install. And since all the threads and help things I find are for rooted phones, I am having trouble finding something that would offer an answer. I was hoping to keep this phone stock as long as possible, which is an oddity for me because I usually want to root my phone immediately. I guess I just really like this phone as stock. And other than this update that fails to load, the phone has no other issues, other than a few emojis that fail to show, but I feel like that's from the software not being able to update for the 6 months that I've been trying to update it.
Any help with this would be greatly appreciated! Thank you!!

Is your device unlocked? Have you tried to sideload the update?
If your device is unlocked you can use NRT to update without loosing any data.

PickelledEggs said:
Hi guys,
As I wrote in the title, my Verizon Nexus 6 will not update. When I get a notification for the software update, I see that it downloads and is ready to restart the phone so it will install the update...
but when I do, it will display the android icon with the word "error" above it. No error number or details about why it did not work.
Things I tried already are:
formatting the phone (both through the settings menu as well as the stock bootloader)
deleting data and cache in Google Services Framework (via settings/apps/all apps)
I have more than enough space in my storage; more than 2/3rds of my storage is free space, so I really am having trouble wrapping my head around why this software update is failing to install. And since all the threads and help things I find are for rooted phones, I am having trouble finding something that would offer an answer. I was hoping to keep this phone stock as long as possible, which is an oddity for me because I usually want to root my phone immediately. I guess I just really like this phone as stock. And other than this update that fails to load, the phone has no other issues, other than a few emojis that fail to show, but I feel like that's from the software not being able to update for the 6 months that I've been trying to update it.
Any help with this would be greatly appreciated! Thank you!!
Click to expand...
Click to collapse
You might try clearing the cache partition in recovery and reboot. Maybe the next OTA will be install without issues.

lol!
if you made any kind of changes, chances are that any ota will not work. but that's alright, all you have to do is flash the factory image. it would've been updated already if you did that instead of writing out your post. you can grab it here https://developers.google.com/android/nexus/images

simms22 said:
lol!
if you made any kind of changes, chances are that any ota will not work. but that's alright, all you have to do is flash the factory image. it would've been updated already if you did that instead of writing out your post. you can grab it here https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
I don't think you read my post at all... I didn't make any changes. My phone is fully stock. No root at all. No unlock. No modifications whatsoever The ota Software update just will not work.
gee2012 said:
You might try clearing the cache partition in recovery and reboot. Maybe the next OTA will be install without issues.
Click to expand...
Click to collapse
I tried going in to recovery mode, but when I do, it gives me the same android error icon, but instead of "error" it says "no command"

Timza said:
Is your device unlocked? Have you tried to sideload the update?
If your device is unlocked you can use NRT to update without loosing any data.
Click to expand...
Click to collapse
Nope. Not unlocked. No modification whatsoever

PickelledEggs said:
Nope. Not unlocked. No modification whatsoever
Click to expand...
Click to collapse
If you nothing else works, I would try to sideload the update by downloading the image from Google's Factory Images for Nexus Devices page.

PickelledEggs said:
Nope. Not unlocked. No modification whatsoever
Click to expand...
Click to collapse
Best is to enable OEM UNLOCKING and usb debugging in developer options, reboot into fastboot and unlock the bootloader and after the reboot flash the latest MMB29S firmware as @simms22 allready stated. Flash the img`s seperately in fastboot, all i would flash personaly is the system and boot img.

Timza said:
If you nothing else works, I would try to sideload the update by downloading the image from Google's Factory Images for Nexus Devices page.
Click to expand...
Click to collapse
gee2012 said:
Best is to enable OEM UNLOCKING and usb debugging in developer options, reboot into recovery and unlock the bootloader and after the reboot flash the latest MMB29S firmware as @simms22 allready stated. Flash the img`s seperately in fastboot, all i would flash personaly is the system and boot img.
Click to expand...
Click to collapse
Oh ok, I must have misinterpereted what SImmz was saying, then. I got in to recovery mode and wiped cache finally, so I will see if that works, otherwise I'll try your guys' other suggestions

PickelledEggs said:
Oh ok, I must have misinterpereted what SImmz was saying, then. I got in to recovery mode and wiped cache finally, so I will see if that works, otherwise I'll try your guys' other suggestions
Click to expand...
Click to collapse
I had this issue with my Nexus 7 (stock) - wiped the cache partition in recovery, and waited for OTA to appear again - and it worked.

BTW, you don't need root to make certain changes(I don't know what changes, but I know many don't get ota because of). or google just made it to sensitive.

Timza said:
If you nothing else works, I would try to sideload the update by downloading the image from Google's Factory Images for Nexus Devices page.
Click to expand...
Click to collapse
You can only sideload OTA`s in stock recovery afaik, not complete images.

gee2012 said:
You can only sideload OTA`s in stock recovery afaik, not complete images.
Click to expand...
Click to collapse
Ah, my mistake. I (wrongly) assumed OTAs were included on that download page.

is using nexus root tool kit let you flash with su 2.5.2 or it using the lastest 2.66? or that makes no difference when flashing stock image?

MikePancake6 said:
is using nexus root tool kit let you flash with su 2.5.2 or it using the lastest 2.66? or that makes no difference when flashing stock image?
Click to expand...
Click to collapse
The latest version of NRT (v2.1.4) uses SuperSU 2.6.6.

Timza said:
The latest version of NRT (v2.1.4) uses SuperSU 2.6.6.
Click to expand...
Click to collapse
is there any way to use 2.5.2, or flashing a custom rom will system root or will it be systemless root anyhow?

MikePancake6 said:
is there any way to use 2.5.2, or flashing a custom rom will system root or will it be systemless root anyhow?
Click to expand...
Click to collapse
After you flash with TWRP (a step with NRT). When you opt to reboot system, you will get a message asking if you would like to install SuperSU. If you swipe to install you will have a "system root". If you opt to not install, you will have a systemless root.
Personally, I have a "system root", and it seems to be working fine, whereas before, I was having an issue with the systemless root.

Timza said:
After you flash with TWRP (a step with NRT). When you opt to reboot system, you will get a message asking if you would like to install SuperSU. If you swipe to install you will have a "system root". If you opt to not install, you will have a systemless root.
Personally, I have a "system root", and it seems to be working fine, whereas before, I was having an issue with the systemless root.
Click to expand...
Click to collapse
ok, thank you for all the help. i already unlocked the bootloader using the tool kit.
tonight i will root it and try a custom rom. maybe chrome or pure nexus project, those seem to be stock with extra options and rro customize.

Thanks guys. I just got around to sideloading the update last night and it's working like a dream.
I'll probably root it soon now. I've been feeling the itch recently... Lol
This (so far) is probably my favorite stock phone though. I might keep it stock for a bit longer
Sent from my Nexus 6 using Tapatalk

I have just bought the fire 7, update and register if I wish to root right now?

Hi, first of all, thanks for accepting to me in the community I am a new user, now.
I have just bought a fire 7, and now I want to root so soon so possible...
Come with the version 5.1.3, my question (very important question right now) is if I have to update and register the device or not, I have not set up the device with wifi cause I think it would automatically upgrade to a higher version....
and the reason to not doing, is reading this http://forum.xda-developers.com/amazon-fire/development/amazon-fire-5th-gen-supertool-root-t3272695 have to downgroad the 5.1.3 to 5.1..2 and after this useing SuperTool.
Help with my first steps for not brick the device,
Thanks friends

If you upgrade your fire tp 5.3.2.0 you can then downgrade it to 5.3.1.0 which can be rooted.
Reuben
---------- Post added at 05:06 PM ---------- Previous post was at 05:05 PM ----------
Use "adb sideload" to downgrade

thanks, but how can I know what a version it will be to upgrading....

Reuben Talbott said:
If you upgrade your fire tp 5.3.2.0 you can then downgrade it to 5.3.1.0 which can be rooted...Use "adb sideload" to downgrade
Click to expand...
Click to collapse
deivitbcn said:
thanks, but how can I know what a version it will be to upgrading....
Click to expand...
Click to collapse
Agree on 5.1.3->5.3.2 via OTA followed by 5.3.1 rollback (sideload); then root using the 'SuperTool', not Kingroot directly. 5.3.2 is the latest build at present (reference date of post); first OTA typically updates to most recent build.
Other thoughts:
- no benefit to 5.1.3->5.1.2 rollback; leaves you with a slightly older kernel
- be sure to keep WiFi off after rollbacks (except while rooting)
- no need to register device w/Amazon if custom rom is ultimate goal

Davey126 said:
Agree on 5.1.3->5.3.2 via OTA followed by 5.3.1 rollback (sideload); then root using the 'SuperTool', not Kingroot directly. 5.3.2 is the latest build at present (reference date of post); first OTA typically updates to most recent build.
Other thoughts:
- no benefit to 5.1.3->5.1.2 rollback; leaves you with a slightly older kernel
- be sure to keep WiFi off after rollbacks (except while rooting)
- no need to register device w/Amazon if custom rom is ultimate goal
Click to expand...
Click to collapse
Thanks guys, so I am going to upgrade 5.3.2 the last version
But I am looking for Use "adb sideload" to downgrade ,
where could find the link?
and the SuperTool link?
Thanks very much

to side load you will need the "update-kindle-global-37.5.5.2_user_552153420.bin" file then you power off the fire, then hold down both volume down and the power button in till you see a screen that looks says this "Amazon system recovery <3>"
Scroll down with the volume buttons to "apply update from ADB" use the power button to select it and sideload the file from earlier.
---------- Post added at 09:33 PM ---------- Previous post was at 09:33 PM ----------
to side load you will need the "update-kindle-global-37.5.5.2_user_552153420.bin" file then you power off the fire, then hold down both volume down and the power button in till you see a screen that looks says this "Amazon system recovery <3>"
Scroll down with the volume buttons to "apply update from ADB" use the power button to select it and sideload the file from earlier.

Finally I am so happy so root... thanks to all you.

Hello, my device is now brick cause I desintalled any system app from the Titanium backup.
Tried to use SuperTool to come back Nova Launcher or Native Os, but not working.
The good new is I can access to Recovery Amazon from the device, and I did think to useing somo options, what I can do?
Thanksss

deivitbcn said:
Hello, my device is now brick cause I desintalled any system app from the Titanium backup.
Tried to use SuperTool to come back Nova Launcher or Native Os, but not working.
The good new is I can access to Recovery Amazon from the device, and I did think to useing somo options, what I can do?
Thanksss
Click to expand...
Click to collapse
Reload (sideload) FireOS 5.3.1 via stock recovery menu. Refer to forum index, specifically forth post, for recovery details.
http://forum.xda-developers.com/amazon-fire/general/index-amazon-fire-2015-t3210485

this one firmware is? https://www.androidfilehost.com/?fid=24269982087009066
I did root from 3.2.1.0, my device never uploaded the 3.2.2 so not did need downgroading, so the firware would help to me?
it is my first device I root (and brick too lol )
thanks

I think I find the firmware you said
fire-OS-5.3.1-update-kindle-global-37.5.5.2_user_552153420.bin
here it is http://rootjunkysdl.com/files/?dir=Amazon Fire 5th gen/Firmware
is it ok?

deivitbcn said:
I think I find the firmware you said
fire-OS-5.3.1-update-kindle-global-37.5.5.2_user_552153420.bin
here it is http://rootjunkysdl.com/files/?dir=Amazon Fire 5th gen/Firmware
is it ok?
Click to expand...
Click to collapse
Yes, correct file. Forum index (previously referenced) contained a direct link; you didn't have to go hunting.

Thanks again, I have to find out how flashing it to my device ... I saw supertool have a recovery tool, but for the early firmwares ... my english is not so good, I am newbie, and I do not want to make a false step that could break the device so I apreciate a lot you helping me..

Hello,
Searching and reading other threads, I thinks this is the way to unbrick my device, only I want to make sure http://forum.xda-developers.com/amazon-fire/general/unbrick-restore-stock-2015-amazon-fire-t3250639
I think not having to install drivers again (supertool did when I rooted, it is ok?) and the only thing to do is change the extension firmware from bin to zip and place it to sd, finally run the Amazon Recovery following the steps i did read.
Although not sure if I have to install the Twrp thing at somewhere.
Thankssss

deivitbcn said:
Hello,
Searching and reading other threads, I thinks this is the way to unbrick my device, only I want to make sure http://forum.xda-developers.com/amazon-fire/general/unbrick-restore-stock-2015-amazon-fire-t3250639
I think not having to install drivers again (supertool did when I rooted, it is ok?) and the only thing to do is change the extension firmware from bin to zip and place it to sd, finally run the Amazon Recovery following the steps i did read.
Although not sure if I have to install the Twrp thing at somewhere.
Thankssss
Click to expand...
Click to collapse
No, that won't work. Nor can you "install" TWRP. If you can not access the stock recovery menu the device is not recoverable.

I can access to menu recovery, if is this one below, yes I can
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I downloaded the firmware 3.2.1 how you said, but I dont know the next step to come....

deivitbcn said:
I downloaded the firmware 3.2.1 how you said, but I dont know the next step to come....
Click to expand...
Click to collapse
See below, 1st and 2nd posts. Includes video. Make sure you have the proper firmware; 3.2.1 is not relevant to this device. Should be 5.1.2, 5.3.1, etc. Must be identical or higher that version of FireOS previously on device. Attempting to go lower usually yields a brick.
http://forum.xda-developers.com/amazon-fire/general/unbrick-amazon-fire-7in-2015-5th-gen-t3285294

Thank I just saw the video.
Although I'm a little afraid to have to take so many steps lol
If I installed drivers to computer, I did it when I ran supertool to do root, I can avoid this step now, can't I?

deivitbcn said:
Thank I just saw the video.
Although I'm a little afraid to have to take so many steps lol
If I installed drivers to computer, I did it when I ran supertool to do root, I can avoid this step now, can't I?
Click to expand...
Click to collapse
No - different drivers are used (or just try; of device won't connect you'll need to install/update drivers).

[GUIDE] How to install early Android Pie build on Nokia 5

UPDATE: ND1-612E released. If you have already installed ND1-612D or 558K, you can download it from https://androidfilehost.com/?w=files&flid=287909 and install it manually by dialing *#*#874#*#*.
I strongly recommend you to unlock the bootloader before proceed - I won't tell how to unlock the bootloader in this guide.
Take a look to this video first if you want to know the experience of Android Pie: https://youtu.be/ay6CeonzoD8
Click to expand...
Click to collapse
In this guide, I'll provide two different methods to get Android Pie on your Nokia 5.
Both methods will erase your userdata.
I only tested it on TA-1024, but it should also work on TA-1053.
Here's an important hint: Nokia 5 (ND1) and Nokia 6 (D1C or PLE) can flash each other's stock firmware, including TA-1000 Chinese firmware.
So the TWRP ported for Nokia 6 can be also used on Nokia 5.
If you want to experience fully customized Android Pie (CN) on your Nokia 5, read this guide:
https://forum.xda-developers.com/nokia-6/how-to/guide-how-to-install-android-pie-build-t3879899/
To confirm your current firmware revision, please dial *#*#227#*#*.
If you're running ND1-558*-0-00WW-B01, you can use both methods.
If you're running ND1-560*-0-00WW-B01 or ND1-563*-0-00WW-B01, you can only use method 1.
Click to expand...
Click to collapse
Method 1: Use OST LA to flash my homebrew firmware
You should be familiar with this method.
1. Download "ND1-612C-0-00WW-B01.7z" from following site:
Or, you can also download ND1-558K-0-00WW-B01.7z instead then perform method 2.
Click to expand...
Click to collapse
https://androidfilehost.com/?w=files&flid=287885
https://fih-firmware.hikaricalyx.com/index_en.html
2. If you have Android 8.x running with LOCKED bootloader, please downgrade bootloader back before processing. If you have unlocked bootloader, you needn't to downgrade the bootloader.
3. Open OST LA or NOST and load the mlf file, in download options, only choose "Normal Download" and "Erase userdata".
If your phone boots suddenly when flashing splash, close OST LA and force power off your phone then flash again.
You can download NOST from https://github.com/StollD/NOST
4. All done, enjoy Android Pie.
Method 2: OTA Update from ND1-558J or ND1-558K
1. Download packages from here:
https://androidfilehost.com/?w=files&flid=287909
https://tpedutw-my.sharepoint.com/:...1BsF1FoPk--uIBfiMbYurDs7NCwOHd05fanA?e=MToYsb
2. Place both packages to root directory of internal storage.
5. Dial *#*#874#*#* to update.
6. After update installed, it will tell you "Encryption failed", click "Factory Reset".
If your phone encountered boot loop, you can enter recovery to perform factory reset manually.
Here's how:
1. Press and hold both volume keys and power key.
2. When you see "shutdown device:" on the left up corner of the screen, release these keys.
3. Connect your phone to a charger.
4. When you see a charging animation, press and hold volume up key and power key.
5. When you feel the phone vibrates, release the power key but only hold the volume up key.
6. When you see Android Robot lying and "No command", press the volume up key with power key holding to get the recovery menu.
7. I needn't to mention what to do next.
Click to expand...
Click to collapse
7. Enjoy Android Pie.
FAQ:
Q1: Can I root it?
A1: Yes, but you must have unlocked bootloader, and Magisk 18 seems unusable.
Q2: How to downgrade bootloader in case I want to roll back without unlocked bootloader?
A2: Rename existing Android 7.x or 8.x OTA package for your model to ND1-9999-0-00WW-B09-update.zip. Then you should know what to do next.
Q3: When will you unlock Nokia X7 / Nokia 8.1?
A3: I don't know!
Q4: When will you get Nokia 9 Penta Camera Phone?
A4: I don't know, don't ask.

How to use method 2 if unlocked bootloader and updated to December security patch
---------- Post added at 04:14 PM ---------- Previous post was at 04:13 PM ----------
And which file download for india android pie

I can watch your video!

Jitender Baloda said:
How to use method 2 if unlocked bootloader and updated to December security patch
---------- Post added at 04:14 PM ---------- Previous post was at 04:13 PM ----------
And which file download for india android pie
Click to expand...
Click to collapse
You still need to check if you're running ND1-558J. If yes, download both packages and follow the guide.
You'll need to update twice.

How to check which version is running on my phone

Here's an important hint: Nokia 5 (ND1) and Nokia 6 (D1C or PLE) can flash each other's stock firmware, including TA-1000 Chinese firmware.
So the TWRP ported for Nokia 6 can be also used on Nokia 5.
Click to expand...
Click to collapse
Anything else, guy? except stock firmware, please!

Installed on TA-1053
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Good evening, to use method 2, is it also necessary to have the bootloader unlocked?

Hiiii Sir I am not able to boot into twrp recovery give me solution
Bootloader is unlocked

Jitender Baloda said:
Hiiii Sir I am not able to boot into twrp recovery give me solution
Bootloader is unlocked
Click to expand...
Click to collapse
Flash TWRP-3.2.3-0-PLE.img to recovery partition, then power off the phone:
Code:
.\fastboot oem HALT
Pull the USB cable, connect your phone to a charger. When you see the charging animation, press and hold volume up and power key.

two things in a single post
noe zapata said:
Good evening, to use method 2, is it also necessary to have the bootloader unlocked?
Click to expand...
Click to collapse
(my device is TA-1027, and my version was ND1-558J-0-00WW-B01 before the process)
it is not necessary to unlock the bootloader of the device, in my case (I do not know if it was just good luck) but do not need to restore the phone to the factory state (keep my complete info, even some banking applications that are more delicate than usual with the updates)
-----
Installed on a TA-1027, method 2
No problems encountered after 3 hours of testing.

Does the temporary bootloader unlock method suffice for said unlocked bootloader requirements?
I can't get NOST working as it says i have to be in critical bootloader state(?)
When doing OTA update method, it says file not found

+1

One question
Would I be able to further update my phone by OTA updates or not

the link is broken
the link to download the file from nd1-558j can not be access

Looks like a great tutorial. Too bad that official version is just around the corner. On the other hand.. Are there any plans to make NOST linux-friendly? Not talking about wine.

Benderisas said:
Looks like a great tutorial. Too bad that official version is just around the corner. On the other hand.. Are there any plans to make NOST linux-friendly? Not talking about wine.
Click to expand...
Click to collapse
Yeah official update will roll out January 2019

Question, is adoptable storage feature still present in this pie build?

Respected which file is to download to upgrade Nokia 5 T-1053 to android pie

wick00750 said:
Respected which file is to download to upgrade Nokia 5 T-1053 to android pie
Click to expand...
Click to collapse
Check using *#*#227#*#* then you'll se which version you're using the files doesn't matter but the method does

Question Fleeting chance to update to MIUI13 - what happened?

Hi all,
I've been hanging out for the MIUI13 (Global) OTA update for ages, hoping it would fix a bunch of issues. before I go the nuclear option* and install a custom ROM. I've joined the beta program and been hitting check for updates obsessively.
Finally late last night it said MIUI 13 was available! Based on Android 12. Woohoo! I hit the download and waited.
When it finished, it asked to reboot, but unsure as to how long the install would be, I quickly went and checked my mail. Of course, when I returned to the update screen, the reboot prompt was gone and there were no updates to MIUI 13 anymore - back to 'no updates available'.
I rebooted many times and have checked dozens of times, but the update to 13 has vanished. If I manually download the latest package, it's still 12.5.9.0 Stable.
I'm guessing I've tripped a flag or something and it thinks I have a failed update. Any thoughts on how to proceed?
Cheers!
* nuclear in that I would have to get a few specialist apps reregistered etc. and it would be a major PITA.

serapax said:
Hi all,
I've been hanging out for the MIUI13 (Global) OTA update for ages, hoping it would fix a bunch of issues. before I go the nuclear option* and install a custom ROM. I've joined the beta program and been hitting check for updates obsessively.
Finally late last night it said MIUI 13 was available! Based on Android 12. Woohoo! I hit the download and waited.
When it finished, it asked to reboot, but unsure as to how long the install would be, I quickly went and checked my mail. Of course, when I returned to the update screen, the reboot prompt was gone and there were no updates to MIUI 13 anymore - back to 'no updates available'.
I rebooted many times and have checked dozens of times, but the update to 13 has vanished. If I manually download the latest package, it's still 12.5.9.0 Stable.
I'm guessing I've tripped a flag or something and it thinks I have a failed update. Any thoughts on how to proceed?
Cheers!
* nuclear in that I would have to get a few specialist apps reregistered etc. and it would be a major PITA.
Click to expand...
Click to collapse
Why you didn't search for this file:
miui_SWEETGlobal_V13.0.4.0.SKFMIXM_4e557a2f1f_12.0.zip
and clean flash it via orange fox?
Or search for the same fastboot file and flash it via miflash?

Laptapper said:
Why you didn't search for this file:
miui_SWEETGlobal_V13.0.4.0.SKFMIXM_4e557a2f1f_12.0.zip
and clean flash it via orange fox?
Or search for the same fastboot file and flash it via miflash?
Click to expand...
Click to collapse
That will be my next step - normally I would just flash a ROM of my choosing.
Mainly I didn't want to lose all my data and settings. For example, the scanning app I use for my Invisalign requires the dentist to generate a new registration code if I reinstall or get a new phone.

serapax said:
That will be my next step - normally I would just flash a ROM of my choosing.
Mainly I didn't want to lose all my data and settings. For example, the scanning app I use for my Invisalign requires the dentist to generate a new registration code if I reinstall or get a new phone.
Click to expand...
Click to collapse
Backup all customs APK with alpha backup pro and later restore them with all settings....

Laptapper said:
Backup all customs APK with alpha backup pro and later restore them with all settings....
Click to expand...
Click to collapse
Perfect - thanks!

I went back to Miui from Pixel Extended due to camera features. Today i got my update on Miui13...holy hell...
I havent seen a worse system in years. Laggy, slow..simply trash. Sorry to brag about this, but this is unnacceptable. and i look into some alternatives soon.(another rom).

serapax said:
Hi all,
I've been hanging out for the MIUI13 (Global) OTA update for ages, hoping it would fix a bunch of issues. before I go the nuclear option* and install a custom ROM. I've joined the beta program and been hitting check for updates obsessively.
Finally late last night it said MIUI 13 was available! Based on Android 12. Woohoo! I hit the download and waited.
When it finished, it asked to reboot, but unsure as to how long the install would be, I quickly went and checked my mail. Of course, when I returned to the update screen, the reboot prompt was gone and there were no updates to MIUI 13 anymore - back to 'no updates available'.
I rebooted many times and have checked dozens of times, but the update to 13 has vanished. If I manually download the latest package, it's still 12.5.9.0 Stable.
I'm guessing I've tripped a flag or something and it thinks I have a failed update. Any thoughts on how to proceed?
Cheers!
Click to expand...
Click to collapse
serapax said:
* nuclear in that I would have to get a few specialist apps reregistered etc. and it would be a major PITA.
Click to expand...
Click to collapse
The MIUI OTA update first downloads the update file to your phone. That file should still be on your phone somewhere. See if you can find it and note where it is. Then ...
​Launch ‘Settings’ app on your device, select ‘About phone’, click ‘System update’, then press ‘three dots’ icon at the top-right corner, and select ‘choose update package’ to enter. Choose the ROM file you’ve put in ‘downloaded_rom’ in Step 2.
Fold Image
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

serapax said:
Hi all,
I've been hanging out for the MIUI13 (Global) OTA update for ages, hoping it would fix a bunch of issues. before I go the nuclear option* and install a custom ROM. I've joined the beta program and been hitting check for updates obsessively.
Finally late last night it said MIUI 13 was available! Based on Android 12. Woohoo! I hit the download and waited.
When it finished, it asked to reboot, but unsure as to how long the install would be, I quickly went and checked my mail. Of course, when I returned to the update screen, the reboot prompt was gone and there were no updates to MIUI 13 anymore - back to 'no updates available'.
I rebooted many times and have checked dozens of times, but the update to 13 has vanished. If I manually download the latest package, it's still 12.5.9.0 Stable.
I'm guessing I've tripped a flag or something and it thinks I have a failed update. Any thoughts on how to proceed?
Cheers!
* nuclear in that I would have to get a few specialist apps reregistered etc. and it would be a major PITA.
Click to expand...
Click to collapse
something like that happened to me sometime back with MIUI 12. came back the update prompt few days later.