Related
I bought Zenfone 2 that initially had a WW firmware but a CN recovery. When I tried updating the firmware to UL-Z00A-WW-2.15.40.10-user, it threw an assertion failure because the device image SKU is CN while the OTA image SKU is WW. I wanted to update the firmware because of the persistent permission bug that was claimed to be solved by just updating the firmware. Since there is an assertion failure, I tried installing UL-Z00A-CN-2.14.40.22-user and it installed successfully. Unfortunately, google play store is now gone.. And I wanted to install WW OTA but it continually fails.
How do I fix this? Help.
Xegara said:
I bought Zenfone 2 that initially had a WW firmware but a CN recovery. When I tried updating the firmware to UL-Z00A-WW-2.15.40.10-user, it threw an assertion failure because the device image SKU is CN while the OTA image SKU is WW. I wanted to update the firmware because of the persistent permission bug that was claimed to be solved by just updating the firmware. Since there is an assertion failure, I tried installing UL-Z00A-CN-2.14.40.22-user and it installed successfully. Unfortunately, google play store is now gone.. And I wanted to install WW OTA but it continually fails.
How do I fix this? Help.
Click to expand...
Click to collapse
1) Download recovery image file (https://app.box.com/s/ohk0aki3nfxjqyuygbl629612tfmi6d9)
2) Boot to fastboot mode (Power + Vol Up)
3) Using ADB command prompt flash recovery by using command : fastboot flash recovery recovery.img
4) reboot to fastboot again
5) launch recovery from fastboot
6) Flash the latest WW firmware same way u flashed latest CN firmware
7) wipe cache
8) reboot
Then Flash system.img directly like you flashed recovery.img :
1) Download system image file (http://www.mediafire.com/download/xf...oot_system.zip)
2) Boot to fastboot mode (Power + Vol Up)
3) Using ADB command prompt flash system by using command : fastboot flash system system.img
4) wipe cache
5) reboot
This will make ur phone WW and you can simply update with any ww firmware ota or by downloading zip from Asus site.
I followed your procedure from a previous thread and it worked perfectly! Thank you.
Broken link
Link for the system.img is dead.
The link redirects to...
HTTP WWW mediafire DOT com/error.php? errno=320
smartbuddy said:
1) Download recovery image file
2) Boot to fastboot mode (Power + Vol Up)
3) Using ADB command prompt flash recovery by using command : fastboot flash recovery recovery.img
4) reboot to fastboot again
5) launch recovery from fastboot
6) Flash the latest WW firmware same way u flashed latest CN firmware
7) wipe cache
8) reboot
Then Flash system.img directly like you flashed recovery.img :
1) Download system image file
2) Boot to fastboot mode (Power + Vol Up)
3) Using ADB command prompt flash system by using command : fastboot flash system system.img
4) wipe cache
5) reboot
This will make ur phone WW and you can simply update with any ww firmware ota or by downloading zip from Asus site.
Click to expand...
Click to collapse
Thank you for sharing your knowledge. But the link for the system.img is dead.
The link redirects to...
HTTP WWW mediafire DOT com/error.php? errno=320
Can I ask for another download link?
Xegara said:
Thank you for sharing your knowledge. But the link for the system.img is dead.
The link redirects to...
HTTP WWW mediafire DOT com/error.php? errno=320
Can I ask for another download link?
Click to expand...
Click to collapse
Will upload tommorrow. Sorry for the delay.
Same Problem. Now with CN Version and no google play etc
rootcron said:
I followed your procedure from a previous thread and it worked perfectly! Thank you.
Click to expand...
Click to collapse
Hi.. it seem that you were able to fix it.. to me its the first time trying to root or flash a phone.. what can i do in order to fix this? do you have like a step by step way .
I already download all the files and IMG files.. also i have the firmware downloads from asus support page.. i hope you can help me... thanks
Xegara said:
Thank you for sharing your knowledge. But the link for the system.img is dead.
The link redirects to...
HTTP WWW mediafire DOT com/error.php? errno=320
Can I ask for another download link?
Click to expand...
Click to collapse
Here you go for system.img :
http://www.mediafire.com/download/1nwpoqo8rpi1kur/Z00A_2.13.40.13_preroot_system.zip
smartbuddy said:
Here you go for system.img :
HTTP WWW mediafire DOT com download/1nwpoqo8rpi1kur/Z00A_2.13.40.13_preroot_system.zip
Click to expand...
Click to collapse
Thanks a lot! It worked! You just saved my zenfone 2! By the way, I was wondering why I needed to flash the pre-root system image if I already flashed the firmware? What is their difference aside from the pre-root system image being pre-rooted?
I installed the firmware which is UL-Z00A-WW-2.15.40.10-user. But now, the version was 2.13.40.13, same as the system.img.
So either of the images (firmware or pre-rooted system) is sufficient enough after installing the recovery image?
Xegara said:
Thanks a lot! It worked! You just saved my zenfone 2! By the way, I was wondering why I needed to flash the pre-root system image if I already flashed the firmware? What is their difference aside from the pre-root system image being pre-rooted?
I installed the firmware which is UL-Z00A-WW-2.15.40.10-user. But now, the version was 2.13.40.13, same as the system.img.
So either of the images (firmware or pre-rooted system) is sufficient enough after installing the recovery image?
Click to expand...
Click to collapse
Yes either of them should be ok. Some people are unable to update to latest ww firmware even after installing ww recovery hence need to flash pre root system.img.
Once u have installed ww recovery and ww system you have converted to ww phone and can update to any ww firmware in future.
smartbuddy said:
Yes either of them should be ok. Some people are unable to update to latest ww firmware even after installing ww recovery hence need to flash pre root system.img.
Once u have installed ww recovery and ww system you have converted to ww phone and can update to any ww firmware in future.
Click to expand...
Click to collapse
I see. I was wondering where did you find the recovery.img? The recovery.img cannot be found on asus official website. Is there a tool to extract the recovery.img of an existing android phone?
smartbuddy said:
1) Download recovery image file ...
2) Boot to fastboot mode (Power + Vol Up)
3) Using ADB command prompt flash recovery by using command : fastboot flash recovery recovery.img
4) reboot to fastboot again
5) launch recovery from fastboot
6) Flash the latest WW firmware same way u flashed latest CN firmware
7) wipe cache
8) reboot
Then Flash system.img directly like you flashed recovery.img :
1) Download system image file ...
2) Boot to fastboot mode (Power + Vol Up)
3) Using ADB command prompt flash system by using command : fastboot flash system system.img
4) wipe cache
5) reboot
This will make ur phone WW and you can simply update with any ww firmware ota or by downloading zip from Asus site.
Click to expand...
Click to collapse
I get error, when try to flash system.img
C:\fastboot_adb(1.0.32)_071114_r21>fastboot flash recovery system.img
target reported max download size of 536870912 bytes
sending sparse 'recovery' (524257 KB)...
OKAY [ 18.063s]
writing 'recovery'...
FAILED (remote: flash_cmds error!)
finished. total time: 19.015s
there is any clue ?
sonic2epix said:
I get error, when try to flash system.img
C:\fastboot_adb(1.0.32)_071114_r21>fastboot flash recovery system.img
target reported max download size of 536870912 bytes
sending sparse 'recovery' (524257 KB)...
OKAY [ 18.063s]
writing 'recovery'...
FAILED (remote: flash_cmds error!)
finished. total time: 19.015s
there is any clue ?
Click to expand...
Click to collapse
Your command is wrong, fastboot flash recovery system.img (You are giving command to flash recovery and giving system.img )
Use the command fastboot flash system system.img
If you still get the error, try after restarting the PC.
smartbuddy said:
Your command is wrong, fastboot flash recovery system.img (You are giving command to flash recovery and giving system.img )
Use the command fastboot flash system system.img
If you still get the error, try after restarting the PC.
Click to expand...
Click to collapse
Oops, sorry .. my command is wrong, thanks ..
http://forum.xda-developers.com/zenfone2/help/how-to-upgrade-cn-version-to-ww-t3101556
help with zenfone 2
I ordered a zenfone 2 from Taiwan but its the ww version. My question is....I ordered it because it says that it supports 1700mhz/2100mhz and aws band 4...I am with Mobilicity in Canada...For the life of me I cannot get this stupid phone to recognize my sim card. Ive messed around with the settings, changed sim card slots...tried everything I can think of, and its still not working. Will this method (or any you know of) get it working?
Are 2nd Set of Steps Necessary?
smartbuddy said:
1) Download recovery image file
2) Boot to fastboot mode (Power + Vol Up)
3) Using ADB command prompt flash recovery by using command : fastboot flash recovery recovery.img
4) reboot to fastboot again
5) launch recovery from fastboot
6) Flash the latest WW firmware same way u flashed latest CN firmware
7) wipe cache
8) reboot
Then Flash system.img directly like you flashed recovery.img :
1) Download system image file
2) Boot to fastboot mode (Power + Vol Up)
3) Using ADB command prompt flash system by using command : fastboot flash system system.img
4) wipe cache
5) reboot
This will make ur phone WW and you can simply update with any ww firmware ota or by downloading zip from Asus site.
Click to expand...
Click to collapse
First of all, thanks so much smartbuddy for taking the time to write up these steps and provide the necessary files. I've been working on this issue for 12+ hours and am now finally resolving with your information. I just have a couple of questions.
I completed the first set of steps without issue and ended up right where I wanted to be - with the most recent firmware version and the ability to check for software upgrades OTA (finally had the button now!). I then went through the second set of steps without issue until I booted my phone after clearing the cache - it hung while booting. I waited for like 15-20 min. and then rebooted, but it hung again. No errors or anything, just booting. So when this happened, I went back through the first set of steps and am now again right where I want to be - with the firmware I want and the ability to check for upgrades OTA.
So do I have to attempt to go through the second set of steps again? And if so, do you have any idea why my phone hung while doing so the first time? Also, with my phone in it's current state, if I were to do a factory reset in the future, would it take me all the way back to square one without any of these updates? Sorry if this is a nube question, I'm still learning.
Thanks again for all your help. You da man! :good:
tapierce said:
First of all, thanks so much smartbuddy for taking the time to write up these steps and provide the necessary files. I've been working on this issue for 12+ hours and am now finally resolving with your information. I just have a couple of questions.
I completed the first set of steps without issue and ended up right where I wanted to be - with the most recent firmware version and the ability to check for software upgrades OTA (finally had the button now!). I then went through the second set of steps without issue until I booted my phone after clearing the cache - it hung while booting. I waited for like 15-20 min. and then rebooted, but it hung again. No errors or anything, just booting. So when this happened, I went back through the first set of steps and am now again right where I want to be - with the firmware I want and the ability to check for upgrades OTA.
So do I have to attempt to go through the second set of steps again? And if so, do you have any idea why my phone hung while doing so the first time? Also, with my phone in it's current state, if I were to do a factory reset in the future, would it take me all the way back to square one without any of these updates? Sorry if this is a nube question, I'm still learning.
Thanks again for all your help. You da man! :good:
Click to expand...
Click to collapse
No you can skip that if you wish. I have moved to Oneplus 2 so dont have a zenfone 2 anymore.
My phone is the ASUS Zenfone 3 deluxe (zs550kl) model and its bricked only can enter fastboot or adb still but my os will not boot I tried going to asus website for stock firmware (UL-Z018-WW-11.40.71.37-user.zip) and stock kernel (ZS550KL_Kermel_11_40_71_37.zip). how do I install these to fix my phone unless there is a better way to make it boot. by the way im new to android I always had iphone jailbroken until last year I am android now but give me noob instructions for the how to. maybe I should add this I already have adb/fastboot installed and the commands for adb devices or fastboot devices when in fastboot mode both recognize my device so maybe my commands are wrong or something but I tried every way I could toinstill firmware and not sure what to flash kernel as the zip or the file unzipped please help thanks in advance. Not sure why this happened exactly but my bootloader is unlocked already but was never rooted so if there is another way to install another custom firmware besides stock I would like those instructions also thanks again
first off your phone is soft brick meaning all you have to do is flash the stock android software back onto your phone.
install to sd card -> boot into recovery (stock or twrp whatever you have works)
flash from sd
let it load (this will work if you have the correct files)
it will reboot and will work good as new again.
you shouldnt have to flash the kernal, just the UL-Z0 file.
That would have worked yesterday but im having another issue now basically instead of waiting for a response on here I went ahead and did other stuff now my recovery menu is not showing up so I cant install from sd now the only option I'm getting is fastboot so is there a way to fix the stock recovery option or even install a custom recovery which might be eaiser because my bootloader is already unlocked. I was going to try to flash stock recovery my self but not sure how exactly I know I use fastboot flash recovery (recovery file name in the folder) and I think it's .img but not sure so I think it will be either .zip or .img file type but not sure what it will be called if it's stock or custom and not sure where to find either. Last issue I'm not sure of is the actual files I downloaded from asus.com the firmware for my specific phone model not working when I try to flash it as the .zip file so my question is do you need to do something with it such as edit the script of something inside the zip of it and I also downloaded the kernel for my specific phone model from the Asus site and not sure if I needed it when flashing stock rom back to device or how to even flash it on the device please help if you can and I know some questions might be dumb to you but remember I'm a noob when it comes to Android recently left iPhone and I was a pro there every phone had a jailbreak and all types of stuff so I know I can get this just takes time I'm sure
I have this exact issue with a new Padfone Infinity A86... No access to stock recovery, only fast boot... But in my case I'm even unable to flash the recovery.img from a firmware package...
I'm wondering if you guys can help this person, maybe there is something in that solution for my Padfone
1: download the full firmware package
2: use sdat2img to convert the sparse system image to a regular one
3: use fastboot to flash the stock boot.img & the newly converted system.img
4: hoping you didn't flash the recovery partition, if you did, reflash the stock dump from the file in my Bootloader unlock thread via fastboot
5: reboot to recovery & do a factory reset
Read the documentation at each step, do your research, learn the process.
I got a ZF3 Deluxe from Italy, is TIM branded, and stuck on MM 6.0, no updated released for this brand, so a friend of mine told me there is of course android 7 for ZF3Deluxe, so i wanted to manually upgrade system to 7.0 Nougat, i downloaded the Stock ROM from asus (2.15ghz cpu, i've checked of course) but when i try to flash it from the Stock Recovery i get this error (see the attachment) i also attach the software informations, (looking at the error i receive it may see the archive is corrupted, but i've tried to download it from Asus many and many times)
You have a carrier rom on your phone and the international version fails the upgrade check.
If you could get your bootloader unlocked that would be a way around it but you need to upgrade to a certain rom version to do that and the carrier hasn't supplied that rom...
You're essentially screwed until the carrier either releases the bootloader unlockable rom or upgrades the rom to nougat...
LeGrim said:
I got a ZF3 Deluxe from Italy, is TIM branded, and stuck on MM 6.0, no updated released for this brand, so a friend of mine told me there is of course android 7 for ZF3Deluxe, so i wanted to manually upgrade system to 7.0 Nougat, i downloaded the Stock ROM from asus (2.15ghz cpu, i've checked of course) but when i try to flash it from the Stock Recovery i get this error (see the attachment) i also attach the software informations, (looking at the error i receive it may see the archive is corrupted, but i've tried to download it from Asus many and many times)
Click to expand...
Click to collapse
You should try to flash stock recovery of WW in fastboot.
And then flash 6.0 WW rom by WW recovery.
Even though ,I didn't sure that if it will work(because I don't have Z016S),but you can try it.
samson1357924 said:
You should try to flash stock recovery of WW in fast boot.
And then flash 6.0 WW rom by WW recovery.
Even though ,I didn't sure that if it will work(because I don't have Z016S),but you can try it.
Click to expand...
Click to collapse
Ok thanks, i can give a try, but where i can download the WW stock recovery? There is no recovery.img inside the WW_user.zip ROM
LeGrim said:
Ok thanks, i can give a try, but where i can download the WW stock recovery? There is no recovery.img inside the WW_user.zip ROM
Click to expand...
Click to collapse
Here it comes~
ZenFone 3 Deluxe ZS570KL_WW stock recovery
Ok guys, i think i've found a way to debrand my Zenfon 3 Deluxe, im testint the procedure right now, i will post the whole procedure if i succeed
Install : ADB & Minimal Fastboot.
Install : pyton 3.6 https://www.python.org/downloads/
Download the latest WW-4.12.40.1698 (For 2.15GHz CPU or 2.40GHz CPU) from Asus WebSite.
Download "Dat to img by stupdroid.com" (search it with google).
Extract Dat to img by stupdroid.com in a Folder.
Open the Firmware ZIP and copy system.new.dat, system.transfer.list e file_contexts in the Dat2IMG's folder.
Execute system.new.dat 2 flashable img converter.exe and just press ENTER and wait till the end of procedure, you will receive 2 files : system.raw.img e system.new.img.
Copy system.new.img in your Fastboot's folder.
Put the Phone into Fastboot mode.
Open fastboot and put this command: " fastboot flash system system_new.img "
Wait the end of flash procedure and type : Fastboot Reboot.
Enter recovery wipe data and cache.
Done.
LeGrim said:
Install : ADB & Minimal Fastboot.
Install : pyton 3.6 https://www.python.org/downloads/
Download the latest WW-4.12.40.1698 (For 2.15GHz CPU or 2.40GHz CPU) from Asus WebSite.
Download "Dat to img by stupdroid.com" (search it with google).
Extract Dat to img by stupdroid.com in a Folder.
Open the Firmware ZIP and copy system.new.dat, system.transfer.list e file_contexts in the Dat2IMG's folder.
Execute system.new.dat 2 flashable img converter.exe and just press ENTER and wait till the end of procedure, you will receive 2 files : system.raw.img e system.new.img.
Copy system.new.img in your Fastboot's folder.
Put the Phone into Fastboot mode.
Open fastboot and put this command: " fastboot flash system system_new.img "
Wait the end of flash procedure and type : Fastboot Reboot.
Enter recovery wipe data and cache.
Done.
Click to expand...
Click to collapse
I forgot to say, after this procedure, just flash the stock WW recovery via Fastboot, then download from asus the lastest 7.0 firmware SKU WW, all perfect. tested by me.
Ok I already have system.new.img, I copied it to the root folder of the SD. Device restart in Fastboot mode (power + vol.up key). Exit screen with message Fastboot mode and does nothing.
Install in the computer the pyton 3.6, I suppose that it serves for the process of generating system.new.img.
I do not know how to do the first step "Install: ADB & Minimal Fastboot.".
Thank you and forgive my translator
If i want to unlock the bootloader for root and unbrand this phone what i have to do? I need unbranded nougat with root but the phone is TIM branded
Ryder. said:
If i want to unlock the bootloader for root and unbrand this phone what i have to do? I need unbranded nougat with root but the phone is TIM branded
Click to expand...
Click to collapse
What version is your phone right now??
Now only have official unluck
For 2.15GHz:8996(None-PRO) UnlockTool
For 2.4GHz:8996P(PRO) UnlockTool
If you are WW version right now,try these tools.
samson1357924 said:
What version is your phone right now??
Now only have official unluck
For 2.15GHz:8996(None-PRO) UnlockTool
For 2.4GHz:8996P(PRO) UnlockTool
If you are WW version right now,try these tools.
Click to expand...
Click to collapse
It's not WW. I'ts from italy and it's tim branded
Ryder. said:
If i want to unlock the bootloader for root and unbrand this phone what i have to do? I need unbranded nougat with root but the phone is TIM branded
Click to expand...
Click to collapse
Try this
or try flash ZenFone 3 Deluxe ZS570KL_WW stock recovery of 4.12.40.1698 and flash UL-Z016-WW-4.12.40.1698-user.zip in recovery (by micro sd or adb sideload)not sure if it work(need verification,I wish you to try first).
Please help me, my model is the Z016S
I can convert UL-Z016-WW-4.12.40.1698-user.zip img and flash with fastboot.
Reboot and it works, but I do not know how to get into recovery.
I have also installed the Z016-WW-4.11.40.1085_recovery.img. The TIM DISAPPEARED
Then I copied the UL-Z016-WW-5.14.44.1898-user.zip into the internal memory and it does not install well.
I have proven the same with UL-Z016-WW-5.14.44.1898-user.zip and it does not work me it stays in a non-comands and will not boot.
greetings and thanks
P.S. At least you do not see the TIM anywhere.
barbapapa said:
Please help me, my model is the Z016S
I can convert UL-Z016-WW-4.12.40.1698-user.zip img and flash with fastboot.
Reboot and it works, but I do not know how to get into recovery.
I have also installed the Z016-WW-4.11.40.1085_recovery.img. The TIM DISAPPEARED
Then I copied the UL-Z016-WW-5.14.44.1898-user.zip into the internal memory and it does not install well.
I have proven the same with UL-Z016-WW-5.14.44.1898-user.zip and it does not work me it stays in a non-comands and will not boot.
greetings and thanks
P.S. At least you do not see the TIM anywhere.
Click to expand...
Click to collapse
So,what is your system version right now?4.12.40.1698?
Why not flash the recovery of 4.12.40.1698?
samson1357924 said:
So,what is your system version right now?4.12.40.1698?
Why not flash the recovery of 4.12.40.1698?
Click to expand...
Click to collapse
This is my situation
samson1357924 said:
So,what is your system version right now?4.12.40.1698?
Why not flash the recovery of 4.12.40.1698?
Click to expand...
Click to collapse
I have done this and it installs,
fastboot flash recovery Z016-WW-4.12.40.1698_recovery.img
reboot, boot system, detect update file is installed, reboot and then gives error (3) unknown.
barbapapa said:
I have done this and it installs,
fastboot flash recovery Z016-WW-4.12.40.1698_recovery.img
reboot, boot system, detect update file is installed, reboot and then gives error (3) unknown.
Click to expand...
Click to collapse
Tow solution you can try
1.install the rom of 4.12.40.1698 again(some of tile,such as xbl,devcfg,devcfgbak..... may be still TIM versio.install it in recovery may turn it into WW version)
2.If fail, try flash these files in fastboot.(I will upload these files for you to flash,also you can draw by yourself)
Ok already worked, the solution is to unlock as you put in # 11.
Thank you
barbapapa said:
Ok already worked, the solution is to unlock as you put in # 11.
Thank you
Click to expand...
Click to collapse
Good!
Can you share what step did you do? Which might help another TIM user.
I decided to make this thread so people won't brick their devices/lose their IMEI/explode their phone when trying to update to the recently leaked/released Oreo Motorola ROM.
This is very information dense. Please, read this and the linked threads carefully and do not miss any step unless told so.
WARNING: This will erase all your data, reset all your settings. MAKE BACKUPS.
I also do not hold responsibility for any negative outcomes out of following this tutorial.
Always look for as many sources of information as you can. There is always something that isn't 100% correct in every tutorial.
Also, making it clear. This is for those who are currently on an Oreo CUSTOM ROM such as Lineage, Pixel Experience or other.
Preparation Steps:
Backup all your important files to your PC. You should do that since everything will be reset.
Make sure your phone is well charged. 80% at least. You want to be safe.
Boot into fastboot.
Install Minimal ADB and Fastboot.
In the command prompt of Minimal ADB and Fastboot, type:
Code:
fastboot getvar all
You will see a bunch of lines come up on the screen. Scroll and look for
Code:
(bootloader) ro.build.fingerprint[0]
.
This will tell the last version of the Stock ROM (Nougat) you had installed.
Example: "NPNS25.137-92-4" Yours won't/may not be the same.
Write it down somewhere. You will need this version number.
Open this link https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/ to download the exact version you found. If anything, download a version above the one you found. Never an inferior. Those are Motorola's Official Nougat ROMs.
Keep it somewhere accessible in your PC and extract the zip. Remember where you put it, you will need it later.
You will now proceed to check your persist partition. Aka: The thing everyone overlooks and screws your IMEI.
IMPORTANT: Take a look at https://forum.xda-developers.com/g5-plus/how-to/fix-persist-resolve-imei0-explanation-t3825147 to find out if your persist partition has permission issues and see if it's recoverable. It is 99% likely that if you are on a custom Oreo ROM that the permissions won't be intact.
If that is the case (most likely), download NZedPred's TWRP Persist Restore zip into your phone.
Feel free to skip these last steps if you have a backup of your persist and efs.
Reboot into recovery and using the most recent TWRP make a backup of your persist and efs. (Information about this can be found on the second post of the "Fix Persist" thread. I am not willing to write a thousand instructions on one thread for the sake of not overcomplicating things.) //****ty steps: have/flash most recent TWRP > backup > select persist and efs > profit
These backups should be on a TWRP folder of the internal storage of your Moto G5. Reboot the phone (or mount USB) and copy that folder to your PC. In case anything goes wrong you will have a copy of your persist.
Steps:
Reboot into recovery (TWRP) using your preferred method. (Be it by the buttons, or via ADB (adb reboot recovery)).
Flash the TWRP Persist Restore zip.
Reboot into bootloader
Open (on your PC ofc) the folder with the extracted files of the Stock ROM zip (NOUGAT).
Open the extracted files folder then press Shift+RMB (Right Mouse Click/Button) and select "Open Command Prompt here" (It may work with Powershell??? If anything, write a post here)
For a quick test, type
Code:
fastboot
In case an error pops-up and tells you that it can't recognize such a command. Follow this article https://www.xda-developers.com/adb-fastboot-any-directory-windows-linux/ to add Minimal ADB and Fastboot to your system environment variables
Now, make sure that the path to the left of the typing cursor is the path of the folder where you have your extracted Nougat ROM files.
Please, for your phone's OTA update ability sake. Make sure that you are flashing the exact version you had before. The version you found by running fastboot getvar all.
The commands below will attempt to update the bootloader and gpt. You should NEVER flash an older version of the bootloader.
If you wish, you can skip the GPT/Bootloader commands. I haven't done myself because I flashed the correct version I had before anyway.
Copy and paste these commands and press enter in the CMD.
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
This will flash the Stock Nougat ROM you have downloaded and will reboot your phone. If all goes well you will be back on Nougat, set up your device as normal.
Attention, everything has been reset, erased, wiped.
Oreo OTA Steps:
After setting up everything, check for OTA's. You should be safe to install them. If you are on a recent firmware, you may only need to install security ones. Keep installing and checking until it says there are no more updates available.
This is where people **** up when they downgrade their bootloader by flashing an older Stock ROM than the one they had before.
Before proceeding, double check that there aren't any OTAs available or that Oreo is available at the time of reading this.
If Oreo is officially available, skip all of these steps and be happy.
Otherwise, if at the time of reading, there is a ZIP of the Oreo ROM that matches your region. Download it.
In case of RETLA, RETBR, and RETIN, at the time of writing, this is the correct file:
https://mega.nz/#!DxdSVaJb!5VEht-s6HYCNOZ2hXXVIPdFBqmWCuAvQL1Wzmp7rhZk or https://drive.google.com/open?id=1ZmtSW40oZi1EXD0PsRib3dqIeF9vauAY
In case you are on RETUS, RETAPAC, RETEU, etc. You may need another file that may not be available. The best course of action would be to wait for the Official OTA. :good:
Download it and put in the root of the internal storage of your Moto G5 Plus.
Go to the Settings app. In the Settings app, you'll want to find the OTA App (Motorola Update Services) by showing System apps and enable storage permissions.
Before you proceed: This is apparently indeed the official OTA that they will ship, which seems to be the same as the Soak 4. It's seemingly stable here, so, you should be fine to use that.
Check on your phone for an OTA.
Reboot it.
Check for an update again. There will be a prompt telling you about copying "system" files. Accept it.
After a while, another prompt will ask you about the update. There won't be a changelog, this is normal. Make sure your device is charged and install it.
Wait for the update to complete and you're done.
Tips:
You can also refer to this thread for some more information about fastboot flashing:
https://forum.xda-developers.com/g5-plus/development/stock-firmware-npn25-137-67-5-fastboot-t3694738
Refer to this thread if you need persist information:
https://forum.xda-developers.com/g5-plus/how-to/fix-persist-resolve-imei0-explanation-t3825147
Google and XDA are your friends.
It's good practice to wipe/reset your phone after you're done. Updates usually leave dirt behind. I haven't personally done this myself and everything is OK, but still...
Feel free to correct me on any mistake. It took me about an hour (or more) to write this and I could have potentially overlooked an important detail.
I flashed OPS28.85-13 by TWRP and when I put fastboot getvar all show me: ro.build.fingerprint[0] OPS28.85-13, so what should I do to flash the official OTA without troubles?, I read that probably I should flash nougat flashable by TWRP and then install Official Nougat and then Official Oreo , what do you think? Thanks!
TheGameExtreme said:
I flashed OPS28.85-13 by TWRP and when I put fastboot getvar all show me: ro.build.fingerprint[0] OPS28.85-13, so what should I do to flash the official OTA without troubles?, I read that probably I should flash nougat flashable by TWRP and then install Official Nougat and then Official Oreo, what do you think? Thanks!
Click to expand...
Click to collapse
Maybe I didn't explain the purpose of this thread...
This is meant for those who are currently in a CUSTOM Oreo ROM such as Lineage, Pixel Experience.
I assume you have the correct firmware installed already. No need to revert anything.
Well, that's what it says here.
Code:
(bootloader) ro.build.fingerprint[0]: motorola/potter_nt/potter_nt:8.1.0/OPS28.85-13/b8ea:user/release-keys
I don't think you need to do anything.
However, what's the bootloader version? Should be:
Code:
(bootloader) version-bootloader: moto-msm8953-C0.92
I had hardbricked my phone and am using a tarp flashablr stock ROM. Can I use this method to go back to stock?
BlackScout said:
Maybe I didn't explain the purpose of this thread...
This is meant for those who are currently in a CUSTOM Oreo ROM such as Lineage, Pixel Experience.
I assume you have the correct firmware installed already. No need to revert anything.
Well, that's what it says here.
Code:
(bootloader) ro.build.fingerprint[0]: motorola/potter_nt/potter_nt:8.1.0/OPS28.85-13/b8ea:user/release-keys
I don't think you need to do anything.
However, what's the bootloader version? Should be:
Code:
(bootloader) version-bootloader: moto-msm8953-C0.92
Click to expand...
Click to collapse
It says: version-bootloader: moto-msm8953-C0.8C, I think it's an older version because before to install Oreo by TWRP I had Nougat with the March security patch
TheGameExtreme said:
It says: version-bootloader: moto-msm8953-C0.8C, I think it's an older version because before to install Oreo by TWRP I had Nougat with the March security patch
Click to expand...
Click to collapse
Yeah, your bootloader is still from Nougat. One day, that could become a problem (hard brick) when taking OTA's.
You can easily fix that by going back to Nougat. (Just make sure to flash the exact version (or one above) the one you had before. Remember, never downgrade your bootloader.).
I think you can just fastboot flash NPNS-25.137.92-14 (since the difference between that and the base 92 patch is just security patches...), download the OTA zip that's been posted around and follow the last set of instructions here (The ones labeled Oreo OTA Steps)
Remember, flashing those TWRP zips made by NZedPred is technically not the same thing as fastboot flashing or taking an OTA. These zips don't upgrade your bootloader and the OP of those threads do not recommend you to take any OTAs.
Quoting from the source: https://forum.xda-developers.com/g5-plus/development/twrp-flashable-stock-builds-t3813351
The partition table and bootloader are not included, which makes it safer to up/downgrade.
Do not attempt to apply standard OTAs over these builds. They'll probably fail, worst case they will brick your phone
So if you want to take the Oreo OTA and have an upgraded bootloader (C0.92), don't flash these. Flash the official Stock ROM (Nougat) images using fastboot then take the OTA.
I got all the information from this guide thanx but one doubt is there , i have my own efs nd persist and i have also backed it up so do i need to restore the restore zip or m i good to just fastboot flash nougat rom and update it via OTA to oreo? I m using custom oreo rom right now and i have never lost 4g or imei that means my efs and persist is my original..
I successfully flashed nougat thnx to your guide.i have downloaded the oreo update but where to put it the update is not being detected in system update
I m an Indian user so retin variant and dwnlf the oreo file provided by you.
karan3660 said:
I successfully flashed nougat thnx to your guide.i have downloaded the oreo update but where to put it the update is not being detected in system update
I m an Indian user so retin variant and dwnlf the oreo file provided by you.
Click to expand...
Click to collapse
The zip file needs to be placed in the internal memory and not within any folder in the internal memory (i.e in the root directory of internal memory), after that you need to give storage permission to the updater app and reboot. After reboot, you need to check for updates and the updater app should now be able to pick up the zip file you placed in internal memory as a new system update
psychopac said:
The zip file needs to be placed in the internal memory and not within any folder in the internal memory (i.e in the root directory of internal memory), after that you need to give storage permission to the updater app and reboot. After reboot, you need to check for updates and the updater app should now be able to pick up the zip file you placed in internal memory as a new system update
Click to expand...
Click to collapse
I have to directly place the zip file?? I extracted it into folder maybe thats why updater app didnt detected
Let me try again.
Tried after placing the zipe file directly into the root of internal storage and gave motorola update service storage permission then rebooted
Still not detevtion the zip file.
karan3660 said:
I have to directly place the zip file?? I extracted it into folder maybe thats why updater app didnt detected
Let me try again.
Tried after placing the zipe file directly into the root of internal storage and gave motorola update service storage permission then rebooted
Still not detevtion the zip file.
Click to expand...
Click to collapse
There's no need to extract the file. Simply place the zip in the root directory. You must be on June 137-92-14 update to install it.
psychopac said:
There's no need to extract the file. Simply place the zip in the root directory. You must be on June 137-92-14 update to install it.
Click to expand...
Click to collapse
I was on 93-10 version thats y it didnt detect update.
Flashed 92-14 nd updated to stock oreo
Thanks for the guide
karan3660 said:
I was on 93-10 version thats y it didnt detect update.
Flashed 92-14 nd updated to stock oreo
Thanks for the guide
Click to expand...
Click to collapse
Just for your info: 93-10 is a firmware for reteu/retus/retapac devices, 92-14 is for retin/rebra.
So you won't receive future OTA as you are on the wrong software channel.
Sent from my Moto G5 Plus using XDA Labs
Wolfcity said:
Just for your info: 93-10 is a firmware for reteu/retus/retapac devices, 92-14 is for retin/rebra.
So you won't receive future OTA as you are on the wrong software channel.
Click to expand...
Click to collapse
It's actually quite possible that future otas will still be picked up (although I wouldn't recommend that others try this). Flashing another channel was important before, but given that Moto seem to have unified the builds.
NZedPred said:
It's actually quite possible that future otas will still be picked up (although I wouldn't recommend that others try this). Flashing another channel was important before, but given that Moto seem to have unified the builds.
Click to expand...
Click to collapse
That would be a nice move from Moto/Lenovo.
So I should have said:
So you probably won't receive future OTA as you are on the wrong software channel.
Sent from my Moto G5 Plus using XDA Labs
The stock OTA update for retus can be found here: https://technoplanners.blogspot.com/...S28.85-13.html
I downloaded this to root internal storage and changed storage permissions but System update doesn't find it. I also tried putting it in the sdcard root with same result. I tried to adb sideload it but it failed because Nougat has to be at Build number NPNS25.137-92. Since I had previously installed the OTA June security patches I'm at Build number NPNS25.137-93. So I seem to be between a rock and a hard place.
Any suggestions has to how to get upgraded to oreo OTA?
nvrpayretail said:
The stock OTA update for retus can be found here: https://technoplanners.blogspot.com/...S28.85-13.html
I downloaded this to root internal storage and changed storage permissions but System update doesn't find it. I also tried putting it in the sdcard root with same result. I tried to adb sideload it but it failed because Nougat has to be at Build number NPNS25.137-92. Since I had previously installed the OTA June security patches I'm at Build number NPNS25.137-93. So I seem to be between a rock and a hard place.
Any suggestions has to how to get upgraded to oreo OTA?
Click to expand...
Click to collapse
This Oreo OTA requires the Brazil or Indian firmware to flash onto (possibly Latin America firmware). As you've found out, this OTA is NOT compatible with US devices as they're on a different stock build. You'd have to wait for the EU, APAC or US OTA updates to be leaked or released. You'd also have to be on the NPNS25.137-93-14 update to apply the OTA update when it arrives.
The OTA I linked to is for the retus version - Blur_Version.28.51.16.potter.retail.en.US.zip
nvrpayretail said:
The OTA I linked to is for the retus version - Blur_Version28.potter.retail.en.US.zip
Click to expand...
Click to collapse
Yup, I've checked the link and it's linking to the Brazil Oreo OTA update. Despite the suffix 'en.US', this does not necessarily mean this update is for the US devices.
Furthermore, looking at the OTA updater script, it specifically requires NPNS25.137-92-14 or OPS28.85-13:
Code:
Package expects build thumbprint of 8.1.0/OPS28.85-13/b8ea:user/release-keys or 7.0/NPNS25.137-92-14/16:user/release-keys
Since you have mentioned you have NPNS25.137-93-14 this OTA simply will not flash to your device. You must wait for the compatible OTA to be released.
nvrpayretail said:
The OTA I linked to is for the retus version - Blur_Version.28.51.16.potter.retail.en.US.zip
Click to expand...
Click to collapse
Despite its name, it is not the us ota.
So, as the title says, I can't install that update. I'm currently on LE2127_11_C.16. About 1/5 of the way through downloading the update, it stops, and at the top of the screen it says "Couldn't update" and underneath in red letters, it says "Installation problem". The MSM tool won't communicate with my phone for some reason that I'm still trying to figure out. If it matters, everything is stock with the exception of my bootloader being unlocked. Does anybody know an alternate method to install the update, or convert to the global ROM so I can make use the Oxygen Updater?
EDIT
So, I found a solution that converted my phone to the global rom AND allowed me to get OTA updates again
1) Using the Oxygen Updater app, download the latest (full) global firmware, then copy the zip file to your adb/fastboot folder. Rename the zip file to firmware.zip
2) Download the TWRP recovery, rename the file to twrp.img and copy it to your adb/fastboot folder
3) Place your phone into fastboot mode
4) Using fastboot, boot the TWRP recovery image (fastboot boot twrp.img)
5) Once your phone has booted the TWRP image, select Advanced, then select ADB Sideload
6) Use ADB to sideload the downloaded firmware (adb sideload firmware.zip)
For anyone trying this, you'll need to flash the modem files from your stock firmware back onto your phone to get cell service
TinkerNerd said:
So, as the title says, I can't install that update. I'm currently on LE2127_11_C.16. About 1/5 of the way through downloading the update, it stops, and at the top of the screen it says "Couldn't update" and underneath in red letters, it says "Installation problem". The MSM tool won't communicate with my phone for some reason that I'm still trying to figure out. If it matters, everything is stock with the exception of my bootloader being unlocked. Does anybody know an alternate method to install the update, or convert to the global ROM so I can make use the Oxygen Updater?
Click to expand...
Click to collapse
If you are rooted with magisk, uninstall it.
TheGhost1951 said:
If you are rooted with magisk, uninstall it.
Click to expand...
Click to collapse
Not rooted, just unlocked the bootloader
TinkerNerd said:
Not rooted, just unlocked the bootloader
Click to expand...
Click to collapse
Look for this thread....
LE2127 OnePlus 9 Pro Custom ROM (T-Mobile)
I am seeing a lot of folks who are still (year later) unable to enjoy custom ROM with T-Mobile devices, so I wanted to quickly post this easy method for enjoying your device with FULL DATA. If you are using a T-Mobile branded OnePlus 9 Pro and...
forum.xda-developers.com
TheGhost1951 said:
Look for this thread....
LE2127 OnePlus 9 Pro Custom ROM (T-Mobile)
I am seeing a lot of folks who are still (year later) unable to enjoy custom ROM with T-Mobile devices, so I wanted to quickly post this easy method for enjoying your device with FULL DATA. If you are using a T-Mobile branded OnePlus 9 Pro and...
forum.xda-developers.com
Click to expand...
Click to collapse
I'm on the C.16 firmware, not the C.19 firmware, otherwise that would work
TinkerNerd said:
So, as the title says, I can't install that update. I'm currently on LE2127_11_C.16. About 1/5 of the way through downloading the update, it stops, and at the top of the screen it says "Couldn't update" and underneath in red letters, it says "Installation problem". The MSM tool won't communicate with my phone for some reason that I'm still trying to figure out. If it matters, everything is stock with the exception of my bootloader being unlocked. Does anybody know an alternate method to install the update, or convert to the global ROM so I can make use the Oxygen Updater?
Click to expand...
Click to collapse
If you are on the c16, that means you are using TMO firmware and that means you have something that is not stock in the firmware. If MSM doesn't recognize your phone, the correct drivers are not installed or installed properly. The Qualcomm USB drivers have to be installed with driver signature disabled on PC indicated by a watermark in lower right corner of PC stating "test mode". Test mode must be enabled before installing drivers then reboot PC!
So, I found a solution that converted my phone to the global rom AND allowed me to get OTA updates again
1) Using the Oxygen Updater app, download the latest (full) global firmware, then copy the zip file to your adb/fastboot folder. Rename the zip file to firmware.zip
2) Download the TWRP recovery, rename the file to twrp.img and copy it to your adb/fastboot folder
3) Place your phone into fastboot mode
4) Using fastboot, boot the TWRP recovery image (fastboot boot twrp.img)
5) Once your phone has booted the TWRP image, select Advanced, then select ADB Sideload
6) Use ADB to sideload the downloaded firmware (adb sideload firmware.zip)
For anyone trying this, you'll need to flash the modem files from your stock firmware back onto your phone to get cell service