Database Users

Flash 5.0.1 N7 2013 Tool [Auto Flash 5.0.1 LRX22C][From Bootloop/Bootloader/Normal]

(WINDOWS ONLY)
WARNING: WIFI VERSION ONLY( Mobile version will be added soon)
This wipes your device! (normally)
This Tool flashes Android 5.0.1 Lollipop to your Nexus 7 2013 Automatically in about 2 mins.
You dont need to know anything about flashing.
You can use that Tool if your Device is in Bootloop/ Bootloader Mode and Normal State.
(Tested it from Bootloop/ Bootloader and from Normal State with Bootloader locked and some times with Bootloader unlocked)
I will update it with new Lollipop Builds for example 5.0.2 or so.
Would be nice if you try this out and give me Feedback!
Download(androidfilehost):
https://www.androidfilehost.com/?w=files&flid=22428
Changelog:
12092014 Release

Julian_os said:
(WINDOWS ONLY)
WARNING: WIFI VERSION ONLY
This Tool flashes Android 5.0.1 Lollipop to your Nexus 7 2013 Automatically in about 2 mins.
You dont need to know anything about flashing.
You can use that Tool if your Device is in Bootloop/ Bootloader Mode and Normal State.
(Tested it from Bootloop/ Bootloader and from Normal State with Bootloader locked and some times with Bootloader unlocked)
I will update it with new Lollipop Builds for example 5.0.2 or so.
Would be nice if you try this out and give me Feedback!
Download(androidfilehost):
https://www.androidfilehost.com/?w=files&flid=22428
Changelog:
12092014 Release
Click to expand...
Click to collapse
Absolutely fantastic tool! Thank you very much.
I received the notification regarding the availability of the Android 5.0.1 OTA today and upon trying to install it, I was unable to due to an error in TWRP. Maybe it was due to my custom recovery, unlocked bootloader or root access.
I downloaded your file a few hours ago, and it really was smooth upon reading the instructions. Simply press any button and watch the magic of complex flashing occur. This tool did what would've required me several hours to research and perform.
Many thanks, just booted up my N7 and setting up the new Android 5.0.1. interface.
Again, many thanks and continue the excellent work!
---------- Post added at 12:37 AM ---------- Previous post was at 12:24 AM ----------
Update: Setup has concluded and I am now using my device. When i go to storage, it shows that I only have 11.29gb of total space even though this is the 32gb Nexus 7 (2013) model. How is this possible and how may I fix this?

Does this wipe the Nexus 7 or just update to 5.0.1? I got the notification about the update, downloaded it and rebooted. It then gave me an error and rebooted back to 5.0. Will this tool help me update to 5.0.1 without wiping?

WiKDMoNKY said:
Does this wipe the Nexus 7 or just update to 5.0.1? I got the notification about the update, downloaded it and rebooted. It then gave me an error and rebooted back to 5.0. Will this tool help me update to 5.0.1 without wiping?
Click to expand...
Click to collapse
It could, if you choose to not relock the bootloader. Locking/unlocking the bootloader is what causes the data wipes as Android wants to ensure that your previous data is unrecoverable to prevent theft e.t.c. (base on what I have read online thus far).
The program provides the alternative for preserving your data as is, so you shouldn't be worried about data wipe providing you select the option that does not include data wipe. As I was upgrading from Android 4.4.4, I decided to do a full system wipe.
---------- Post added at 01:18 AM ---------- Previous post was at 01:03 AM ----------
Big Bread said:
Absolutely fantastic tool! Thank you very much.
I received the notification regarding the availability of the Android 5.0.1 OTA today and upon trying to install it, I was unable to due to an error in TWRP. Maybe it was due to my custom recovery, unlocked bootloader or root access.
I downloaded your file a few hours ago, and it really was smooth upon reading the instructions. Simply press any button and watch the magic of complex flashing occur. This tool did what would've required me several hours to research and perform.
Many thanks, just booted up my N7 and setting up the new Android 5.0.1. interface.
Again, many thanks and continue the excellent work!
---------- Post added at 12:37 AM ---------- Previous post was at 12:24 AM ----------
Update: Setup has concluded and I am now using my device. When i go to storage, it shows that I only have 11.29gb of total space even though this is the 32gb Nexus 7 (2013) model. How is this possible and how may I fix this?
Click to expand...
Click to collapse
New update, it looks like i remedied my own problem by factory resetting. Still running the flashed Android 5.0.1 but now have 26.41 GB total space as it initially should've been.
Many thanks, will keep this thread updated with anything i discover.

WiKDMoNKY said:
Does this wipe the Nexus 7 or just update to 5.0.1? I got the notification about the update, downloaded it and rebooted. It then gave me an error and rebooted back to 5.0. Will this tool help me update to 5.0.1 without wiping?
Click to expand...
Click to collapse
No it will wipe your device

Big Bread said:
It could, if you choose to not relock the bootloader. Locking/unlocking the bootloader is what causes the data wipes as Android wants to ensure that your previous data is unrecoverable to prevent theft e.t.c. (base on what I have read online thus far).
The program provides the alternative for preserving your data as is, so you shouldn't be worried about data wipe providing you select the option that does not include data wipe. As I was upgrading from Android 4.4.4, I decided to do a full system wipe.
---------- Post added at 01:18 AM ---------- Previous post was at 01:03 AM ----------
New update, it looks like i remedied my own problem by factory resetting. Still running the flashed Android 5.0.1 but now have 26.41 GB total space as it initially should've been.
Many thanks, will keep this thread updated with anything i discover.
Click to expand...
Click to collapse
No, the wiping is caused by flashing a clean /data partition (userdata)

Julian_os said:
No it will wipe your device
Click to expand...
Click to collapse
Julian_os said:
No, the wiping is caused by flashing a clean /data partition (userdata)
Click to expand...
Click to collapse
I am sorry, your statements conflict each other. Is there an option in your program that does not wipe my tablet or is the only choice to wipe it?

WiKDMoNKY said:
I am sorry, your statements conflict each other. Is there an option in your program that does not wipe my tablet or is the only choice to wipe it?
Click to expand...
Click to collapse
It will always wipe if your bootloader isn't already unlocked. If it is, you can prevent it when you rename the .bat to a .txt, scroll down to the flashing userdata and erase "echo Flashing Userdata..." and the "fastboot flash userdata.img". Then save it and rename it back to a .bat . now there shouldnt be a wipe but the tool will then always not flash data and you need to (if you want to) wipe from stock recovery.

Waiting for 0 seconds, press a key to continue ...
Flashing bootloader...
sending 'bootloader' (3911 KB)...
OKAY [ 0.130s]
writing 'bootloader'...
OKAY [ 1.234s]
finished. total time: 1.367s
Rebooting bootloader...
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.008s
Flashing Recovery...
error: out of memory
Flashing Boot...
error: out of memory
doesnt go past this point.... out of memory?

mejdam said:
Waiting for 0 seconds, press a key to continue ...
Flashing bootloader...
sending 'bootloader' (3911 KB)...
OKAY [ 0.130s]
writing 'bootloader'...
OKAY [ 1.234s]
finished. total time: 1.367s
Rebooting bootloader...
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.008s
Flashing Recovery...
error: out of memory
Flashing Boot...
error: out of memory
doesnt go past this point.... out of memory?
Click to expand...
Click to collapse
Thats because of your pcs (low) performance.

I have unlocked bootloader, so I did close the command line when app asked if I want to relock it, and it unfortunatelly wiped all my data.
Nice tool though, thanks for it!

I did something wrong it wiped out my Nexus 7 2013. :crying:

Lol, fortunately for me, i backed up all my movies to my pc because i anticipated that it would wipe the device. Then, i simply just transferred my movies to the device and good as new.
You have android 5.0.1 now and that's something to be grateful for.

Thank You
I signed up to thank you for this. My N7 was unlocked and rooted and I kept getting an error when trying to install the OTA update. I then tried to manually update through adb sideload and that was giving me trouble as well. This was the only option that has worked for me. I ran it through the bootloader/fastboot mode. I backed up everything from my 4.4.4 and restored it. I am now enjoying 5.0.1. I am grateful for your work. Thanks again.

is this flo or deb?
Will this work on LTE ?
Oh sorry, must read property before posting. I see its WiFi now.

Gurocz said:
I have unlocked bootloader, so I did close the command line when app asked if I want to relock it, and it unfortunatelly wiped all my data.
Nice tool though, thanks for it!
Click to expand...
Click to collapse
1. Relocking Bootloader doesnt wipe anything but if you then want to unlock it again(or unlock it in general), it gets wiped.
2. In my earlier post i explain how to prevent from wiping when bootloader is unlocked before starting the program

chibiwings said:
I did something wrong it wiped out my Nexus 7 2013. :crying:
Click to expand...
Click to collapse
The tool tells you that at beginning!(before you press any key first time). Or do you mean that really everything got wiped ?(system etc.)

Question
Julian_os said:
(WINDOWS ONLY)
WARNING: WIFI VERSION ONLY( Mobile version will be added soon)
This wipes your device! (normally)
This Tool flashes Android 5.0.1 Lollipop to your Nexus 7 2013 Automatically in about 2 mins.
You dont need to know anything about flashing.
You can use that Tool if your Device is in Bootloop/ Bootloader Mode and Normal State.
(Tested it from Bootloop/ Bootloader and from Normal State with Bootloader locked and some times with Bootloader unlocked)
I will update it with new Lollipop Builds for example 5.0.2 or so.
Would be nice if you try this out and give me Feedback!
Download(androidfilehost):
https://www.androidfilehost.com/?w=files&flid=22428
Changelog:
12092014 Release
Click to expand...
Click to collapse
Hi, this is a really good tool. I hope I can use this.
Can this be used while on Recovery Mode (sideload)? I'm not an expert, but according to the resource I've read so far tells me that it won't since sideload only works in OTA.
I have posted a thread about my problem. If you have time, can you kindly help me?
Here's a link to my thread:
http://forum.xda-developers.com/nexus-7-2013/nexus-7-2013-qa/n72013-saved-t2970725
Any enlightenment will be appreciated!

lrdmz said:
Hi, this is a really good tool. I hope I can use this.
Can this be used while on Recovery Mode (sideload)? I'm not an expert, but according to the resource I've read so far tells me that it won't since sideload only works in OTA.
I have posted a thread about my problem. If you have time, can you kindly help me?
Here's a link to my thread:
http://forum.xda-developers.com/nexus-7-2013/nexus-7-2013-qa/n72013-saved-t2970725
Any enlightenment will be appreciated!
Click to expand...
Click to collapse
You get into fastboot mode right? (Bootloader). Then you can use the tool. Extract it and run universaladbdriversetup.msi and then double click on from bootloader.bat.

Problem Solved
Julian_os said:
You get into fastboot mode right? (Bootloader). Then you can use the tool. Extract it and run universaladbdriversetup.msi and then double click on from bootloader.bat.
Click to expand...
Click to collapse
Hi, thanks for the reply...
Even on bootloader, the PC won't recognize my N7.
However, it is now fixed. Just went to Control Panel>System and Security>System>Advanced System Settings>Environment Variable>Path (and added the local directory where my apk manager/SDK manager is installed).
And it worked like magic! Seems like the PC is not recognizing the bootloader mode since I installed my apk manager /SDK manager elsewhere.
After I finished manual flashing, I did try your tool, and... Booom! Sweet... Your tool is amazing.
Keep up the good work!

[Updata]WW-4.21.40.223(andriod M)

ASUS ZenFone 2=ZE551ML(Z00AD/Z00ADA/Z00ADB/Z00ADC) software Image: V4.21.40.223 for WW SKU only* (andriod M)
Improvement Item:
1)Improve Wi-Fi/Bluetooth stability
2)Update Security patch
3)Improve system stability
4)Support India SOS call (India only)
Full Rom Download Link: http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE551ML/UL-Z00A-WW-4.21.40.223-user.zip

Hi,
How to install it on a rooted ZE551ML ?
When checking for OTA, it is not purposing the update for the moment.
Thanks

fredlamour said:
Hi,
How to install it on a rooted ZE551ML ?
When checking for OTA, it is not purposing the update for the moment.
Thanks
Click to expand...
Click to collapse
It is, but not if your bootloader is unlocked.

Rodepo said:
It is, but not if your bootloader is unlocked.
Click to expand...
Click to collapse
Thanks.
bootloader unlocked so no way.
I am thinking about jumping into a lineage rom.

VoLte support?? in this new update....

I felt like this was happening today! came in and here it is. Updating right now.
Thanks

any update for this update of asus zenfone 2

optimumgiant said:
any update for this update of asus zenfone 2
Click to expand...
Click to collapse
Hello. This forum is for galaxy 8.07. We don't know about zendroid 2 or whatever you ask.
Just joking. This IS for zenfone 2.
I'm currently using the update. Screen flickering has stopped for the time being.

i have a rooted device ZE551ml 2.3gzh 4gb and when i checked for firmware update it starts downloading and now my device is on the update prompt screen i.e. to install , postponed or cancel it.
so my question is :- is it safe to install the updates on a rooted device.
thanks in advance

crownpiyush said:
i have a rooted device ZE551ml 2.3gzh 4gb and when i checked for firmware update it starts downloading and now my device is on the update prompt screen i.e. to install , postponed or cancel it.
so my question is :- is it safe to install the updates on a rooted device.
thanks in advance
Click to expand...
Click to collapse
it seems you are first. Give it a try and find it out for yourself and let us know!

crownpiyush said:
i have a rooted device ZE551ml 2.3gzh 4gb and when i checked for firmware update it starts downloading and now my device is on the update prompt screen i.e. to install , postponed or cancel it.
so my question is :- is it safe to install the updates on a rooted device.
thanks in advance
Click to expand...
Click to collapse
My way is unroot and uninstall Xposed first, than sideload the whole rom with stock recovery.
I had failed to OTA many times because I modified some system files (forgot to restore them), so now I just reflash rom to save the trouble.

Wifi auto-connect problem seems fixed and the phone has more available ram after "power and boost".
It's worth to update imo.
Battery life seems the same

All sensors working with this version in my brazilian zenfone 2 z00a.

Running this for last two days so far , yup Wi-Fi connects quicker , graphics seem sharper round the web and there's the security patch .
To update ..
Coming from .184 rooted and twrp.
Full unroot first.
Then used the modder tool , to "return back to stock " option. Select boot.img then recovery.img, remember it flashes .134 .img's and I was coming from .184 to begin with.
Then boot to stock recovery .
Scroll to update from adb. Then adb cmd >
adb sideload MOFD_SDUPDATE.zip
Remembering to put the new firmware in adb/fastboot folder first and changing the file name to MOFD_SDUPDATE before sideloading.
Will give it a few more days then will try to use the modder tool to get back to lineage os and back up the new firmware.

I was on rooted .184 and twrp. I booted into fastboot, flashed recovery, booted to recovery, and updated from SD card. After the update has been installed and the phone booted, I unlocked the bootloader, flash twrp, root, remove bloatware, profit

audit13 said:
After the update has been installed and the phone booted, I unlocked the bootloader, flash twrp, root, remove bloatware, profit
Click to expand...
Click to collapse
I had unlocked the BL before so i updated and directly tried regaining root and xposed but failed (softbrick at asus loading screen), I confirm that applying the whole ota from sideload sort of relocks the bootloader and you must do it again, now it is booting and rebuilding the dalvik cache.

audit13 said:
I was on rooted .184 and twrp. I booted into fastboot, flashed recovery, booted to recovery, and updated from SD card. After the update has been installed and the phone booted, I unlocked the bootloader, flash twrp, root, remove bloatware, profit
Click to expand...
Click to collapse
In conclusion you did only flashed stock recovery and, from that, you flashed the whole zip in the first post, right?
Inviato dal mio ASUS_Z00AD utilizzando Tapatalk

timbernot said:
Running this for last two days so far , yup Wi-Fi connects quicker , graphics seem sharper round the web and there's the security patch .
To update ..
Coming from .184 rooted and twrp.
Full unroot first.
Then used the modder tool , to "return back to stock " option. Select boot.img then recovery.img, remember it flashes .134 .img's and I was coming from .184 to begin with.
Then boot to stock recovery .
Scroll to update from adb. Then adb cmd >
adb sideload MOFD_SDUPDATE.zip
Remembering to put the new firmware in adb/fastboot folder first and changing the file name to MOFD_SDUPDATE before sideloading.
Will give it a few more days then will try to use the modder tool to get back to lineage os and back up the new firmware.
Click to expand...
Click to collapse
Running this update since it came out 5hrs SOT over a 26hr period seems very good :good:
Still on stock no mods apart from using firefox browser with adblock .
Good to know too .... official downgrade version of LP WW-52.20.40.196 firmware is on my ext SD card and i still get notification for this downgrade update OTA after a reboot on this WW-4.21.40.223(andriod M) latest firmware
https://forum.xda-developers.com/zenfone2/help/success-downgrade-mm-to-lp-via-sd-card-t3520642

timbernot said:
Running this update since it came out 5hrs SOT over a 26hr period seems very good :good:
Still on stock no mods apart from using firefox browser with adblock .
Good to know too .... official downgrade version of LP WW-52.20.40.196 firmware is on my ext SD card and i still get notification for this downgrade update OTA after a reboot on this WW-4.21.40.223(andriod M) latest firmware
https://forum.xda-developers.com/zenfone2/help/success-downgrade-mm-to-lp-via-sd-card-t3520642
Click to expand...
Click to collapse
can you please share your adblock app with us.
thanks

crownpiyush said:
can you please share your adblock app with us.
thanks
Click to expand...
Click to collapse
its a add-on downloaded and installed from ` tools ` in firefox browser settings :good:
ps, i had trouble using adblockplus add-on from firefox ,when viewing XDA pages ..they turned out blank , XDA i think prevented the use of such adblock , so now i use the less blocking add-on in firefox called `uBlock`
its good enough

[marmite] Android 7.1.1 TOS118C fastboot/recovery images

For those that didn't receive the update yet, I've requested the links to the Wileyfox nougat support team, so here you can download the incremental, recovery and fastboot images of the latest upgrade TOS118C.
RECOVERY IMAGE (2GB) (works neat in TWRP as well as in Cyanogen Recovery / does not necessarily require open bootloader)
FASTBOOT IMAGE (2GB) (requires open bootloader)
INCREMENTAL UPDATE (OFFICIAL) (DRIVE MIRROR LINK by me) (from TOS089A to TOS118C / from decf3a575d to aa4d5d86bc)
In the post below you can have some information on how to grab OTA links from the WileyFox BSP server. Have fun, and don't forget to debloat your system

How to grab the official OTA from BSP's server
In the OP, I left a link to the official incremental update right from the OTA server (which I'll talk about a bit later). If you directly click it, it will return an Error 404, but that is not true since the file actually exists... But requires a special HTTP header to be visible.
Since I wanted to grab the OTA link now that, for once, I finally got an OTA in this phone after always upgrading through fastboot images, I used wireshark to determine the server where it fetches it and the full file route. It turns out the header sends a special UA string as you can see in the picture attached: rsotaua 1.0, which is, most probably, a randomly generated string.
Now here's the thing: if you want to switch the UA you'll need an extension to do so. I've used this one. As soon as it's installed, go to the Options of the extension and add it like here:
Code:
WILEYFOX rsotaua 1.0 Chrome Replace WF
Once the string is inserted, switch to it and hit the URL. The OTA should be downloadable now.
... Or you can just wait til someone mirrors it, like I already did
Lastly, as a side note, I'd also like to comment the following, regarding BSP:
Wileyfox's devices software is now in charge of this company, called BSP.ninja and that clearly defines themselves as a company to "launch an Android device without knowing where to start". It's said to be formed by former Cyanogen employees, or, at least Ricardo Cerqueira @aremcee (which btw, is also in charge of the Open Source code available in BitBucket for the Wileyfox devices), since he's the owner of the domain. In any case, what I want to say is that the code is being done quite possibly by the very same people that did the job at the now dead Cyanogen, so it shouldn't be a reason to worry. Also, it'd be awesome if the team released a working device tree so that the community could bring custom ROMs just like you (the team) used to do.

linuxct said:
RECOVERY IMAGE (2GB) (works neat in TWRP as well as in Cyanogen Recovery / does not necessarily require open bootloader)
FASTBOOT IMAGE (2GB) (requires open bootloader)
Click to expand...
Click to collapse
So these two can be flashed on my rooted phone with unlocked bootloader and I don't have to wipe anything?

boa05 said:
So these two can be flashed on my rooted phone with unlocked bootloader and I don't have to wipe anything?
Click to expand...
Click to collapse
Correct. I'm preparing a new version of my debloater tool, and I'll briefly explain in it's thread how to move from TOS089A to TOS118C without losing anything in rooted and/or debloated devices. Stay tuned!

Well....I must say, that every "update" from Wileyfox shows me that it's the worst phone to update I've ever owned.
I can't proceed any update (OTA of course not, recovery via TWRP) on my rooted + some skin parts changed via substratum Swift 2 without wiping everything.

zerospaced said:
Well....I must say, that every "update" from Wileyfox shows me that it's the worst phone to update I've ever owned.
I can't proceed any update (OTA of course not, recovery via TWRP) on my rooted + some skin parts changed via substratum Swift 2 without wiping everything.
Click to expand...
Click to collapse
I also skin my phone through substratum (the default orange theme is disgusting), I use magisk and plenty of other tools both systemless or even require modifying the system partition (like Wileyfox debloater), and, using the instructions I wrote in this post here I've found no single problem upgrading my device from a debloated, rooted and themed TOS089A to TOS118C to then debloat, root and theme it again. It's true you will need to install your substratum themes again, but the rest should work perfect.

I've tried the recovery update on my Swift 2X but can't get it to boot. I have TWRP installed (3.1.0-0) and it's rooted via SuperSU. Do I have to unroot first?
Edit for more info: I did the OTA upgrade from the stock CyanogenOS ROM to 7.1.1 TOS089A. Then I installed TWRP and flashed SuperSU. The OTA to TOS118C predictably doesn't work. Flashing the recovery image via TWRP seems to go fine but I'm stuck at the white "Wileyfox powered by Android" screen. Tried wiping Cache/Dalvik but no dice.
Edit 2: flashing Magisk afterwards seems to make it work.

I try to install the ZIP via TWRP and after the process ends the phone reboots but it remains stuck at the "WileyFox" white screen.
EDIT: I tried the fastboot one and it worked. Sometimes is hard to understand our devices

I'm guessing it's some kind of dm-verity issue? Flashing in TWRP worked for me when I flashed Magisk 12.0 afterwards, which seems to take care of dm-verity. Linuxct suggested installing Magisk in his debloat thread and I thought "what's the harm". Now I'm a happy camper.

Yes indeed, it appears a dm-verity issue message. Actually, I managed to install 7.1 from fastboot, but then this flash restores the original recovery. If I try to install again TWRP it stuck again on the WileyFox white screen. I'll try installing Magisk.
Edit: flashed Magisk, all works. Awesome.

Will this Firmware work on my Swift 2 Plus?

Cappucinto said:
Will this Firmware work on my Swift 2 Plus?
Click to expand...
Click to collapse
Yes it will. Anything for the swift 2 will work on the plus because the only difference between them is ram and storage size.

Afifus said:
Yes it will. Anything for the swift 2 will work on the plus because the only difference between them is ram and storage size.
Click to expand...
Click to collapse
Thank You so much

Installed it via fastboot and now iam stuck in a bootloop :S
EDIT: Did a factory reset in recovery! Works now.

Swift 2 Plus on 13.1.5 Cyanogen. Which method is best to install Android 7.1.1 TOS118C manually. The phone is stock, not rooted. Thanks

gaborkov9 said:
Yes indeed, it appears a dm-verity issue message. Actually, I managed to install 7.1 from fastboot, but then this flash restores the original recovery. If I try to install again TWRP it stuck again on the WileyFox white screen. I'll try installing Magisk.
Edit: flashed Magisk, all works. Awesome.
Click to expand...
Click to collapse
If you use the
Code:
adb reboot "dm-verity enforcing"
can you remove the dm-verity menu on boot or do you need it left as after bootloader unlocked?

TOS373J?
Anyone have the images for the latest update?

TOS373J OTA
other link

Pooh042 said:
TOS373J OTA
other link
Click to expand...
Click to collapse
doesnt work gives me instal error 7 when i try to instal it

DarthBraindrain said:
doesnt work gives me instal error 7 when i try to instal it
Click to expand...
Click to collapse
what is your current firmware version?

Final Official Oreo 8.1.0 Release - OPP28.85-16 OTA

I've just captured the Official OPP28.85-16 OTA for retail cedric and I'm posting it here. I'm on retbr channel but this will work on any retail device. If you're on another updated channel, I don't know what would happen if you installed this.
Notice that to install this YOU MUST be on NPPS25.137-93-2-5 to install these, since OTA's are not full firmwares like fastboot files, but instead they're patchings tailored to be applied upon a specific firmare - NPPS25.137-93-2-5 in this case.
Another particular detail is that the OTA file (gotten directly from my credric) lists the Blur Version as Blur_Version.25.361.10.cedric.retail.en.US, but curiously, the fastboot version for the same firmware ( which you can download here) lists it as Blur_Version.28.41.15.cedric.retail.en.US
Someone also reported in another thread that they just sideloaded this upon the Second Soak test. I wouldn't doubt it since this is what should happen to regular soak testers, but if you do it, DO IT AT YOUR OWN RISK
I also won't post instructions on how to install this since they're already available here
Download
Gdrive: https://drive.google.com/file/d/149hrGFpuWUgAvJr02McYNwJVaqSvllYO/view?usp=sharing
That's it.

changelog?

Has anyone already tried it?

Since this is a (Delta) OTA Update that expects NPPS25.137-93-2-5 (Blur_Version.25.361.10) it should be correctly named "block_delta-ota-Blur_Version.25.361.10-28.41.15.cedric.retail.en.US" in my view.
Someone also reported in another thread that they just sideloaded this upon the Second Soak test.
Click to expand...
Click to collapse
I'm on the 2nd soak test update OPP28.85-13.
Just tried to flash the update from SD card and ADB sideload.
Update failed due to wrong version.
E3002: Package expects build thumbprint of 8.1.0/OPP28.85-16/0400:user/release-keys or 7.0/NPPS25.137-93-2-5/10:user/release-keys; this device has 8.1.0/OPP28.85-13/789a:user/release-keys.

JoeDoe0 said:
Since this is a (Delta) OTA Update that expects NPPS25.137-93-2-5 (Blur_Version.25.361.10) it should be correctly named "block_delta-ota-Blur_Version.25.361.10-28.41.15.cedric.retail.en.US" in my view.
I'm on the 2nd soak test update OPP28.85-13.
Just tried to flash the update from SD card and ADB sideload.
Update failed due to wrong version.
E3002: Package expects build thumbprint of 8.1.0/OPP28.85-16/0400:user/release-keys or 7.0/NPPS25.137-93-2-5/10:user/release-keys; this device has 8.1.0/OPP28.85-13/789a:user/release-keys.
Click to expand...
Click to collapse
seems like it can be updated. from. soak test then, but I never heard nor did I find anything about OPP25. 85-16 build. maybe there was a third soak test and we don't know about it

Works perfect
Hi,
i used the above Image in Germany and i am now on Oreo 8.1
Everything works perfect. First i had a little bit trouble due to an old Version of ADB Tools, but after Update ADB to current Version the Update to Oreo took something around 30min.
Build 28.85-16
Oreo 8.1
Software Channel reteu
Patch Level 01.08.2018

bori321 said:
Hi,
i used the above Image in Germany and i am now on Oreo 8.1
Everything works perfect. First i had a little bit trouble due to an old Version of ADB Tools, but after Update ADB to current Version the Update to Oreo took something around 30min.
Build 28.85-16
Oreo 8.1
Software Channel reteu
Patch Level 01.08.2018
Click to expand...
Click to collapse
On which version you were before update?

Firmware
Hi,
before update to Oreo i flashed NPPS25.137-93-2-5 Firmware and after that the Image from this thread.
Worked perfect.
Alex
I tried to post a Screenshot but it was not possible because i am a new member...

Update failed due to wrong version.
E3002: Package expects build thumbprint of 8.1.0/OPP28.85-16/0400:user/release-keys or 7.0/NPPS25.137-93-2-5/10:user/release-keys; this device has 8.1.0/OPP28.85-13/789a:user/release-keys.
Click to expand...
Click to collapse
freeZbies said:
seems like it can be updated. from. soak test then, but I never heard nor did I find anything about OPP25. 85-16 build. maybe there was a third soak test and we don't know about it
Click to expand...
Click to collapse
Update fails from OPP28.85-13 since it expects either OPP28.85-16 which is the latest Oreo build (that I want to update to) or the latest Nougat NPPS25.137-93-2-5.
There is no OPP25. 85-16 build! I think you misread the error message.
BTW I updated from OPP28.85-13 to -16 using the full fastboot version and it worked out perfectly.

JoeDoe0 said:
Update fails from OPP28.85-13 since it expects either OPP28.85-16 which is the latest Oreo build (that I want to update to) or the latest Nougat NPPS25.137-93-2-5.
There is no OPP25. 85-16 build! I think you misread the error message.
BTW I updated from OPP28.85-13 to -16 using the full fastboot version and it worked out perfectly.
Click to expand...
Click to collapse
yeah, I actually misread it, now I see it.
Anyways, flashing it from fastboot doesn't prove anything. but seems like Cedric can be upgraded from the soak test to final version using this ota. Idk because I used fastboot myself too, since I had already modified my system partition.

AsusZenFone3Deluxe said:
changelog?
Click to expand...
Click to collapse
seriously?
stop joking, Motorola doesn't release changelogs.
but I'll try:
updated from nougat to oreo?
duhhh

how is speaker quality in this build ?
because there is some issues in previous oreo builds

Speaker
Hi,
i would say that for my ears the speaker sounds better than it was with Nougat.
After a few days of testing everything works really good and i have not found anything not working or any problems.
Alex

bori321 said:
Hi,
before update to Oreo i flashed NPPS25.137-93-2-5 Firmware and after that the Image from this thread.
Worked perfect.
Alex
I tried to post a Screenshot but it was not possible because i am a new member...
Click to expand...
Click to collapse
how do you get back to NPPS25.137-93-2-5

I followed the steps from this Thread: https://forum.xda-developers.com/g5/development/stock-upgrade-to-official-stock-oreo-8-t3823598
- Unlocked bootloader (don't know of this is necessary)
- back to NPPS25.137-93-2-5 via the commands from the thread i linked (without the lines:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
)
- via ADB sideload with the Oreo download from this thread to Oreo.
Alex

ahmedAZ said:
how is speaker quality in this build ?
because there is some issues in previous oreo builds
Click to expand...
Click to collapse
In my experience the quality is better than on previous oreo builds.
ahmedAZ said:
how do you get back to NPPS25.137-93-2-5
Click to expand...
Click to collapse
if you have an unlocked bootloader download NPPS25.137-93-2-5 Flashable Zip here and flash it with twrp
bori321 said:
I followed the steps from this Thread: https://forum.xda-developers.com/g5/development/stock-upgrade-to-official-stock-oreo-8-t3823598
- Unlocked bootloader (don't know of this is necessary)
Alex
Click to expand...
Click to collapse
to flash official Motorola files there's no need to unlock the bootloader.
you've just unnecessarily voided your warranty

@freeZbies
Hey is that twrp stock rom (137-93-2-5) the only thing we need to flash before going for the ota ? Cause I've been told that we needed to be on a completely unmodified system partition in order to receive the ota. In that case just flashing twrp stock wouldn't be sufficient right?
https://forum.xda-developers.com/g5...o-official-stock-oreo-8-t3823598/post77713117

Chekm8Qc said:
@freeZbies
Hey is that twrp stock rom (137-93-2-5) the only thing we need to flash before going for the ota ? Cause I've been told that we needed to be on a completely unmodified system partition in order to receive the ota. In that case just flashing twrp stock wouldn't be sufficient right?
https://forum.xda-developers.com/g5...o-official-stock-oreo-8-t3823598/post77713117
Click to expand...
Click to collapse
I dont know if the twrp version would be valid. To apply an OTA, your system must matchbit by bit, so the most guaranteed way is to flash that firmware via fastboot, but you could try flashing the twrp version, and in case it works, you could post the results here.
just dont forget that if the ota fails youll soft brick ur phonr and will only be able to recover it via fastboot

freeZbies said:
I dont know if the twrp version would be valid. To apply an OTA, your system must match stick bit by bit, so the most guaranteed way is to flash that firmware via fastboot, but. you could try flashing the twrp version, and in case it. woeks you could post the results here.
just dont forget that if the ota fails youll soft brick ur phonr and will only be able to recover it via fastboot
Click to expand...
Click to collapse
Thanks I'll keep that in mind
Being soft bricked,, wouldn't I be able to use twrp still? Like to flash a valid rom or one of my backups?
Anyways I can't really try it that way since the update hasn't come to me yet I'm on software channel Retca.
Edit : right I forgot that I could just use the official ota available here if I would like to test it.

Chekm8Qc said:
Thanks I'll keep that in mind
Being soft bricked,, wouldn't I be able to use twrp still? Like to flash a valid rom or one of my backups?
Anyways I can't really try it that way since the update hasn't come to me yet I'm on software channel Retca.
Edit : right I forgot that I could just use the official ota available here if I would like to test it.
Click to expand...
Click to collapse
being soft bricked doesnt necessarily mean you can recover it through twrp. OTA's are different of twrp flashables in that it modifies things beyond system partition. I've seen reports from people with other motorola devices who applied an OTA while having a modified system partition, and even though they were able to boot to twrp, flashing a custom Rom or restore a backup wouldn't make the phone boot. Their phones weren't hard bricked, but still they had to fastboot to recover their phones. Anyways, why don't you flash the Twrp flashable if, it's already available (considering you have an unlocked bootloader).
I'm case you have a locked bootloader you may fastboot without executing "fastboot erase userdata" in case you want to try. I did it without losing my data (although I was already in Opp 28.85-16)
but after all I really advice you to flash the twrp zip if u can

Downgrade From Android 10 to Android 9 is working now

Android 10 downgrade.
now the tools are available in realme website to unlock the bootloader...
install deep testing apk and unlocking the boot loader with the android 10 ( procuder will be found in realme website)
After the bootloader is unlocked......follow the procedure below..
second reboot to bootloader and flash the twrp recovery
and reboot using fastboot command itself
it will go straight to twrp recovery mode.
just give wipe data function which is default...
then flash the android 9 ozip , after that dont reboot to system
go back and flash the stock recovery from android 9 which is attached with this post and then reboot..
now you are back to android 9.
this method is working for me ..
after sitting many hours with stucked twrp recovery i just flashed the stock recovery and it get in to the device
Please read whats the state of my realme x2 pro so that you can understand what I have done.
I purchased the realme x2 pro 12gb/256 in the uk , it is shipped with the android 9, there was some OTA update and I had done that and the phone was still in Android 9 with some bugs fixed. Again I recheked the software update for Realme ui update but nothing was found.
So I headed to realme uk website and downloaded the Android 10 realme ui ozip , copied to the phone and updated. Now the phone was in android 10 with realme ui.
The software update is good but I don’t like the finger print animation and also I noticed a sight battery drain,but I am not sure if it was same like in android 9 , I mean the batter life. So decided to go back android 9 . so after so many tries and all finally downgraded to android 9 with the bootloader locked and widevine to L1 and google pay working. Now all stock and all finger print this and that working !!!
Downgrade procudure :-
Backup All the things that are required, All will be wiped.
1.First thing is to unlock the bootloader in Android 10 because of I updated to android 10.
Follow this link below , download the deep testing apk and unlock the bootloader.
https://c.realme.com/in/post-details/1253651898825703424
2.Make sure you all had the proper working adb drivers in pc and android bootloader drivers,
After completing the 1st step , Download the twrp from the link below:
I downloaded the one in this name TWRP 3.3.1-13 Unofficial by mauronofrio
https://forum.xda-developers.com/re...covery-unofficial-twrp-realme-x2-pro-t3997879.
How to flash twrp in realme x2 pro follow this guide below:
https://forum.xda-developers.com/realme-x2-pro/how-to/guide-unlocking-bootloader-to-getting-t4010189
follow the procedure above and until flashing recovery and don’t flash vbmeta and all
3. Download the Android 9 firmware with stock recovery , this was the lastest one I dowloaded from xda
(https://forum.xda-developers.com/realme-x2-pro/how-to/rmx1931ex11a-10-available-t4059607)
4.Downloading stock recovery :
https://sourceforge.net/projects/rmx1931ex-stock-files/files/RMX1931EX_11_A06_GLOBAL.zip/download
download this zip file and use only the recovery.img after unzip , this is the only file we need from this folder
Second part:
I Assume the bootloader is unlocked , the device wiped and rebooted to os , copy the ozip in the and stock recovery in internal memory, we might need to use this for later.
now flash the twrp using the guide above and reboot to twrp recovery.
In twrp install the android 9 ozip that we downloaded in the phone memory , after it flashed don’t reboot.just go back and flash the (recovery.img) from twrp itself and choose the path recovery and flash , after that the phone will reboot and it will go to stock recovery. Then give a wipe in the stock recovery and reboot. Now you are back to stock android 9.
Now we are in android 9 with the unlocked bootloader. That’s all.
For those who needs to lock the bootloader read the information below
Check the stock recovery version number ( if it shows rooted near the version number) if it says rooted don’t relock the bootloader. From the phone just run stock ozip again and let it boot in to os, after that again check the stock recovery if rooted string is gone. If it is gone now you are good to lock the bootloader.
Because with unlocked bootloader the google pay is not working so for me locking the bootloder is important for me , also I checked in the device info that widevine is change back to L1.
dont lock bootloader with twrp recovery

where can i get in depth test for global version ?
and did i lose the fingerprint after unlocking bootloader?

Where is the stock recovery that you attached? Can u show step by step with more detail explaination?

rhazes305 said:
Where is the stock recovery that you attached? Can u show step by step with more detail explaination?
Click to expand...
Click to collapse
Hi,
from this link i had downloaded the stock recovery of android 9, it is 54 mb zip file , after you unzip use only recovery.img
i will post properly the procedure..
https://forum.xda-developers.com/realme-x2-pro/how-to/boot-stock-recovery-boot-t4003971
download link :
https://sourceforge.net/projects/rmx1931ex-stock-files/files/RMX1931EX_11_A06_GLOBAL.zip/download

arthajudeenuk said:
Android 10 downgrade.
now the tools are available in realme website to unlock the bootloader...
install deep testing apk and unlocking the boot loader with the android 10 ( procuder will be found in realme website)
After the bootloader is unlocked......follow the procedure below..
second reboot to bootloader and flash the twrp recovery
and reboot using fastboot command itself
it will go straight to twrp recovery mode.
just give wipe data function which is default...
then flash the android 9 ozip , after that dont reboot to system
go back and flash the stock recovery from android 9 which is attached with this post and then reboot..
now you are back to android 9.
this method is working for me ..
after sitting many hours with stucked twrp recovery i just flashed the stock recovery and it get in to the device
Click to expand...
Click to collapse
Thanks, but I would also like a more detail explanation of the steps. Where to download the deep testing apk? And will fingerprint also work after unlocking bootloader?

rhazes305 said:
Where is the stock recovery that you attached? Can u show step by step with more detail explaination?
Click to expand...
Click to collapse
nightzun said:
Thanks, but I would also like a more detail explanation of the steps. Where to download the deep testing apk? And will fingerprint also work after unlocking bootloader?
Click to expand...
Click to collapse
Hi mate,
i typing the procedure in word document now and upload soon, afte unlocking the bootloader in android 10 the fingerprint is working good , it didnt affect the fingerprint because the realme didnt block it in this update.

you are the best! thanx
** sadly i cannot unlock bl coz i got error " This is carrier-customized phone" on deep testing apk.
I would appreciate it if anyone would help me to solve this problem

Is there something wrong with Android 10?
Or why downgrade to 9?

Yerry said:
Is there something wrong with Android 10?
Or why downgrade to 9?
Click to expand...
Click to collapse
- More battery long lasting on A9, perhaps more services are running in A10 rising power consumption or not well updated.
- In early versions of A10 call recording was capped due privacy rights. With the last update C.26 I can record calls but not tag the records accesing to the contacts list.
- Also in the last C.26 update of A10, you can take RAW photos in 'expert mode'.

pr0orz1337 said:
- More battery long lasting on A9, perhaps more services are running in A10 rising power consumption or not well updated.
- In early versions of A10 call recording was capped due privacy rights. With the last update C.26 I can record calls but not tag the records accesing to the contacts list.
- Also in the last C.26 update of A10, you can take RAW photos in 'expert mode'.
Click to expand...
Click to collapse
Thank you for the info.
Just upgraded, first there was an odd connectivity issue, every GPS fix loss, deactivated mobile and WiIfi for 5 seconds
After turning Smart power savings mode off and on, the issue disappeared.
About raw mode: Odd raw mode that does not save in 64 MPix

arthajudeenuk said:
Android 10 downgrade.
Check the stock recovery version number ( if it shows rooted near the version number) if it says rooted don’t relock the bootloader. From the phone just run stock ozip again and let it boot in to os, after that again check the stock recovery if rooted string is gone. If it is gone now you are good to lock the bootloader.
Because with unlocked bootloader the google pay is not working so for me locking the bootloder is important for me , also I checked in the device info that widevine is change back to L1.
dont lock bootloader with twrp recovery
Click to expand...
Click to collapse
It is possible after lock bootloader,unlock one more time?

The links on step 3 are not correct.
Can you update the post?

Yerry said:
The links on step 3 are not correct.
Can you update the post?
Click to expand...
Click to collapse
Updated ...please download from the XDA page link , downoad the firmware with stock recovery.

Thanks bro...i downgraded to color os and now it ia running smoothly..

This method works with RMX1931 (CN version)? Because i see that the recovery used in the op is for RMX1931EX

Thanks for ur help But is there a way to get a stock recovery for Chinese version ?

Are you sure that we don't have to flash vbmeta.img.because somewhere i have read that if i don't flash vbmeta my phone will be dead

will still working on CN Rom based devices?

Even after installing the ozip from phone my recovery says rooted! Anyway to change that or remove the root?