Database Develop

M7 OTA : OTA_M7_WL_L50_SENSE60_SPCS_MR_Sprint_WWE_6.23.651. 10-6.23.651.7_R_release

Just got the notification for OTA update for m7 .
File name: OTA_M7_WL_L50_SENSE60_SPCS_MR_Sprint_WWE_6.23.651.10-6.23.651.7_R_release_452237.zip
Size: 189.61 mb
{
"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"
}
Sprint Website
Download link
I rooted my phone yesterday and dont want to go back to stock for the update. Can someone please help me with a flashable zip which I can use.
cheers

tangojoker said:
Just got the notification for OTA update for m7 .
I rooted my phone yesterday and dont want to go back to stock for the update. Can someone please help me with a flashable zip which I can use.
cheers
Click to expand...
Click to collapse
From my understanding, you should be able to take the OTA, but you need to make sure everything is as stock as possible first. Follow these steps:
0. BACKUP with a nandroid backup
1. Uninstall any apps that changed the /system partition (like xposed).
2. Unroot from the SuperSU app.
3. Flash the stock recovery (easiest way is to flash the latest full firmware).
4. If you are s-on, you may have to relock the bootloader first (I'm s-off, so I'm not sure).
5. Take the OTA.
6. If you are s-on, unlock the bootloader if you locked in step 4.
7. Flash TWRP.
8. Allow TWRP to root the phone (it will ask you if you want to root when you exit the recovery).
You can get the full firmware from this thread. If you wait though, someone might release a flashable stock rooted ROM, but the phone is old, so that may not happen.

Won't this wipe everything?

jy04 said:
Won't this wipe everything?
Click to expand...
Click to collapse
I don't believe so. The OTA typically leaves the /data partition alone. Of course, as always, everything you do to your phone is at your own risk.

coal686 said:
From my understanding, you should be able to take the OTA, but you need to make sure everything is as stock as possible first. Follow these steps:
0. BACKUP with a nandroid backup
1. Uninstall any apps that changed the /system partition (like xposed).
2. Unroot from the SuperSU app.
3. Flash the stock recovery (easiest way is to flash the latest full firmware).
4. If you are s-on, you may have to relock the bootloader first (I'm s-off, so I'm not sure).
5. Take the OTA.
6. If you are s-on, unlock the bootloader if you locked in step 4.
7. Flash TWRP.
8. Allow TWRP to root the phone (it will ask you if you want to root when you exit the recovery).
You can get the full firmware from this thread. If you wait though, someone might release a flashable stock rooted ROM, but the phone is old, so that may not happen.
Click to expand...
Click to collapse
If anyone does take the OTA and wants to send me a TWRP backup, I'd be more then willing to post a stock rooted flashable Rom.
Just throwing it out there, in case there's anyone interested, willing, and able.
Sent from my HTC6535LVW using Tapatalk

This is the second Stagefright patch/update.
There is an issue with the idea of flashing the latest full firmware, as it is not posted on the forum, the latest RUU post is the firmware before the first Stagefright update, I didn't realize this so I flashed stock recovery as that's how I took the first Stagefright patch, the problem with this is in the OTA update installation it identifies your build before installing so you will receive an error: "Package expects build fingerprint of blah blah/499067.10:user" but it will show as "499067.7:user" and abort installation as that is the fingerprint of the most recent firmware available on the forum, and not the most recent as of the first stagefright update. Someone needs to upload or find updated full firmware or maybe just stock recovery before the installation is possible.

So 6.23.651. 10 is not patched for "stagefright"?

Joshlul said:
This is the second Stagefright patch/update.
There is an issue with the idea of flashing the latest full firmware, as it is not posted on the forum, the latest RUU post is the firmware before the first Stagefright update, I didn't realize this so I flashed stock recovery as that's how I took the first Stagefright patch, the problem with this is in the OTA update installation it identifies your build before installing so you will receive an error: "Package expects build fingerprint of blah blah/499067.10:user" but it will show as "499067.7:user" and abort installation as that is the fingerprint of the most recent firmware available on the forum, and not the most recent as of the first stagefright update. Someone needs to upload or find updated full firmware or maybe just stock recovery before the installation is possible.
Click to expand...
Click to collapse
Just updating the firmware to the previous version won't be enough to allow the update to work.
Most OTA updates, unless they are a full Rom update or RUU, contain patch files.
Those patch files will check the MD5 of every single system file before patching each one.
So even if your firmware is current or your build.prop is edited, to pretend like you have the last version, it will still fail when checking the system files it intends on patching.
There is no way to trick an OTA to work.
You have to have the proper system files, for them to patch at all or properly.
So don't waste your time on that...you need the previous stock Rom for the latest OTA to ever apply properly, or at all.
Good luck!!
Sent from my HTC6535LVW using Tapatalk

links broken can anyone post the OTA update zip like ,i'm rooted with twrp recovery with s-on

santod040 said:
If anyone does take the OTA and wants to send me a TWRP backup, I'd be more then willing to post a stock rooted flashable Rom.
Just throwing it out there, in case there's anyone interested, willing, and able.
Sent from my HTC6535LVW using Tapatalk
Click to expand...
Click to collapse
I created a TWRP backup using the following procedure:
1. Relocked my bootloader
2. Took the RUU (RUU_M7_WL_L50_SENSE60_SPCS_MR_Sprint_WWE_6.23.651.10.exe)
3. Unlocked my bootloader
4. Booted into fastboot
5. I tried to run: fastboot boot twrp-2.8.7.0-m7wls.img but that didn't work
6. fastboot flash recovery twrp-2.8.7.0-m7wls.img
7. I booted to recovery.
8. I selected read only
9. Created a backup leaving out the cache.
I'm not sure where to send it or where to post it (1.73GB)

chrishonson said:
I created a TWRP backup using the following procedure:
1. Relocked my bootloader
2. Took the RUU (RUU_M7_WL_L50_SENSE60_SPCS_MR_Sprint_WWE_6.23.651.10.exe)
3. Unlocked my bootloader
4. Booted into fastboot
5. I tried to run: fastboot boot twrp-2.8.7.0-m7wls.img but that didn't work
6. fastboot flash recovery twrp-2.8.7.0-m7wls.img
7. I booted to recovery.
8. I selected read only
9. Created a backup leaving out the cache.
I'm not sure where to send it or where to post it (1.73GB)
Click to expand...
Click to collapse
Could upload to Dropbox, Google Drive, Mega, whatever host you prefer.
Then send me a link via PM, or post it here and mention me.
If using Dropbox, a public link could cause too much traffic on your account, if posted publicly.
Feel free to shoot me a PM if you need further guidance on it.
Thanks for your effort, it should benefit a few folks.
Sent from my HTC6535LVW using Tapatalk

I can't post links yet so pm me if anyone wants the link.
The funny thing about this rom is that TWRP didn't root it like i expected it would. It installed SuperSU but "There is no SU binary installed, and SuperSU cannnot install it..."
Maybe I'm missing something.

santod040 said:
Could upload to Dropbox, Google Drive, Mega, whatever host you prefer.
Then send me a link via PM, or post it here and mention me.
If using Dropbox, a public link could cause too much traffic on your account, if posted publicly.
Feel free to shoot me a PM if you need further guidance on it.
Thanks for your effort, it should benefit a few folks.
Sent from my HTC6535LVW using Tapatalk
Click to expand...
Click to collapse
having a similar issue. relocked and RUU'd using last release. For some reason my OTA fails. I found some other guidance that said to extract the stock recovery from the OTA and flash it then run the OTA again, but for some reason I can't extract recovery from firmware. If anyone can post it, I'd like give that method a try. Thanks!

yeah so twrp-2.8.7 wasn't able to flash super su binary in a way that would stick. twrp-2.8.6 worked fine. I think may have seen this issue elsewhere.

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).

EMUI 9 root updates

I just looked up a few threads about rooting EMUI 9.
The one and only who kinda managed to do it is the developer of Magisk John Wu.
If you wanna stay updated about rooting EMUI 9 on Huawei P20pro, you should follow this guy:
EMUI9 root
still NO EMUI 9 kernel sources released

Rooting / Magisk is one thing. I think in addition to that we also need a working twrp or some recovery for Emui 9 to be able to flash stuff with relative ease. On top of that the OEM unlock option is greyed out which is problematical itself. So, this is all gonna be a bit complicated.

Well, there is a modded versions of TWRP Mate Rs Porsche with working decryption and for most people including me, oem-unlock is not greyed out when you have unlocked frp and unlocked bootloader.
I'm on the final of EMUI 9. So the last important thing would be a rooted EMUI 9 to get some important things working.
mrabcx said:
Rooting / Magisk is one thing. I think in addition to that we also need a working twrp or some recovery for Emui 9 to be able to flash stuff with relative ease. On top of that the OEM unlock option is greyed out which is problematical itself. So, this is all gonna be a bit complicated.
Click to expand...
Click to collapse

ArtaxXP said:
and for most people including me, oem-unlock is not greyed out when you have unlocked frp and unlocked bootloader.
Click to expand...
Click to collapse
Unlocked frp = oem unlock enabled in dev options
Unlock bootloader and frp itself doesn't cause "enable oem unlock" being greyed out. It's not getting greyed out just by upgrading to pie either. Upgrade to pie and factory reset does!
Good to know about twrp working on p20 pro

Hello, i changed my system font by using huawei themes.
Now it's not possible anymore, to edit photos and use different fonts for editing.
Does anybody have an idea, what i can do?i want to keep the new system font.
I hope to get a usefull help, i really would be grateful.
Sorry for this comment, i doesn't belong at this page

there is already something new on this topic?

not much but some
Heinzx3 said:
there is already something new on this topic?
Click to expand...
Click to collapse

some good news
good news

Rooted on 9.0
{
"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"
}
Sent from my CLT-L04 using Tapatalk

Dene_Bluesman said:
Rooted on 9.0 View attachment 4673784
Sent from my CLT-L04 using Tapatalk
Click to expand...
Click to collapse
Yeah awesome! Well done!
John Wu just released some info in a post: EMUI9 root

Dene_Bluesman said:
Rooted on 9.0 View attachment 4673784
Sent from my CLT-L04 using Tapatalk
Click to expand...
Click to collapse
Link pls

mr.mgmg said:
Link pls
Click to expand...
Click to collapse
https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337
Sent from my CLT-L04 using Tapatalk

Dene_Bluesman said:
https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337
Sent from my CLT-L04 using Tapatalk
Click to expand...
Click to collapse
There are alot files
https://github.com/topjohnwu/magisk_files/tree/master/canary_builds
Any file i must download and flash

mr.mgmg said:
There are alot files
https://github.com/topjohnwu/magisk_files/tree/master/canary_builds
Any file i must download and flash
Click to expand...
Click to collapse
Would like someone to drop round and flash it for you too? Do some reading, or don't flash.

purple patch said:
Would like someone to drop round and flash it for you too? Do some reading, or don't flash.
Click to expand...
Click to collapse
I think the Q not for you, just keep silent

mr.mgmg said:
I think the Q not for you, just keep silent
Click to expand...
Click to collapse
his point is, even you got the question wrong,
no files from that list will root your emui 9 simply by flashing any of it,
you gonna need a copy of RECOVERY_RAMDIS.img pulled from update.app of latest emui 9.0 firmware,
copy it to device with latest canary magisk & magisk manager installed,
patching the .img using that canary manager, and you will get patched_boot.img stored in download folder in that device,
copy it to your pc and flash it to recovery_ramdisk partition using fastboot,
or if you really are that lazy, simply download the prepatched one here : https://drive.google.com/file/d/1rhl405-ALbYrtGHilrNUR5Fuq4yATvTH/view?usp=drivesdk
and flash it from fastboot to your recovery_ramdisk partition
boot by holding vol up button

otonieru said:
his point is, even you got the question wrong,
no files from that list will root your emui 9 simply by flashing any of it,
you gonna need a copy of RECOVERY_RAMDIS.img pulled from update.app of latest emui 9.0 firmware,
copy it to device with latest canary magisk & magisk manager installed,
patching the .img using that canary manager, and you will get patched_boot.img stored in download folder in that device,
copy it to your pc and flash it to recovery_ramdisk partition using fastboot,
or if you really are that lazy, simply download the prepatched one here : https://drive.google.com/file/d/1rhl405-ALbYrtGHilrNUR5Fuq4yATvTH/view?usp=drivesdk
and flash it from fastboot to your recovery_ramdisk partition
boot by holding vol up button
Click to expand...
Click to collapse
Thanks for help

It will seem dumb for some of you but important to me and others (i Hope there are some lol)..... so just to be clear :
1- do we have to follow these steps AFTER installing emui 9 ? coming from emui 8.1 161 with evira kernel and using mods i wanna start 100% fresh because first time i installed emui 9 163 i came back a week later because of battery consuption that was way worse and real bad SOT so it's major to me to proceed the best way - i have to go first to twrp and wipe all, data+system+caches before flashing emui 9 ?
2- any reason not to use the easiest way ? why to prefer the complicated one : pulling the file from update.app and copy and etc....?
3- magisk modules will be usable ?
Thanks to those of you who will bring light or give me confident in re-installing pie.
And of course merry Christmas everyone

deltaman83 said:
It will seem dumb for some of you but important to me and others (i Hope there are some lol)..... so just to be clear :
1- do we have to follow these steps AFTER installing emui 9 ? coming from emui 8.1 161 with evira kernel and using mods i wanna start 100% fresh because first time i installed emui 9 163 i came back a week later because of battery consuption that was way worse and real bad SOT
2- any reason not to use the easiest way ? why to prefer the complicated one : pulling the file from update.app and copy and etc....?
3- magisk modules will be usable ?
Thanks to those of you who will bring light or give me confident in re-installing pie.
And of course merry Christmas everyone
Click to expand...
Click to collapse
1. Steps is for rooting, if you wanna start fresh, you can consider wiping /data after update. So none of your previous mods data no cache will tag along to your EMUI 9
2. Reason is, the difference of firmware versioning betweem region. You told me you updated to .163. My prepatched ramdisk is from C636 .168, although most of the time it can work universally across region and version (just like how custom recovery work in a universal way), there's no telling what huawei actually did between version update. So its always best to use and patch your own file. Since it will give you confidence, its your own doing after all.
3. I use youtubevanced, LKT, systemless host, swap torpedo, busybox and detach magisk modules, all work just fine on EMUI 9. You only need to redownload and reinstall all the modules (if you didnt wipe data, like me), because installation from oreo version wont work straight away on EMUI 9.
for extra information, SafetyNet and MagiskHide all working as well. I can use my banking app just fine.
as for precaution info,
i suggest you to use the flashy tools to install EMUI 9 from PC instead of using HuRU,
i did the HuRU way, and ends up with a messed up software serial number and broken recovery partition, meaning i can't flash TWRP, stock recovery nor a patched recovery ramdisk to acquired root. It will all fall to an error screen, telling me no recovery image available inside the system, and ask me to update system again. Fortunately the phone still boot just fine to system.
scratched my heads for hours until i manage to resolved it by flashing Recovery META and Recovery Vendor image through fastboot. After that i can reflash stock recovery, and the patched one (after i confirm stock one work fine)

Thanks a lot for your answers.
---------- Post added at 06:42 PM ---------- Previous post was at 06:24 PM ----------
otonieru said:
1. Steps is for rooting, if you wanna start fresh, you can consider wiping /data after update. So none of your previous mods data no cache will tag along to your EMUI 9
Click to expand...
Click to collapse
One thing no clear to me is what i do of the magisk canary Zip file...?.... ? As twrp not working on emui 9...

[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.