I basically am holding out switching my daily driver to the Axon 7 until we have a fully functional CM or other clean ROM with root capability. My Axon 7 is on B20, and I got the update notification. Any reason I should avoid going to B27?
My concern is that we've found an unlock workaround for B20 but I am not clear if it works on B27, and I don't think ZTE has re-opened unlocking after the B27 update. So is updating a big risk that I won't be able to unlock/install CM when it is feature-functional?
I'll be very simple and easy answer.
Yes , Unlock Bootloader with know method base on B20 and you'll still be able to get goodies
DrakenFX said:
I'll be very simple and easy answer.
Yes , Unlock Bootloader with know method base on B20 and you'll still be able to get goodies
Click to expand...
Click to collapse
I am sorry, I am interested too in this topics and I do not understand well.
If I unlock the bootloader on the B20 and root the phone, can I simply update the smartphone at the B27 (and others) with the ZTE OTA updates without brick the phone or lost the unlock bootloader?
Thanks
Edit: I found the asnwer in an other topic, I am sorry.
youngz89 said:
I am sorry, I am interested too in this topics and I do not understand well.
If I unlock the bootloader on the B20 and root the phone, can I simply update the smartphone at the B27 (and others) with the ZTE OTA updates without brick the phone or lost the unlock bootloader?
Thanks
Edit: I found the asnwer in an other topic, I am sorry.
Click to expand...
Click to collapse
No problem, in your case just unlock bootloader and get the update.
No need to root till you are B27.
DrakenFX said:
No problem, in your case just unlock bootloader and get the update.
No need to root till you are B27.
Click to expand...
Click to collapse
Cool, so if I unlock my bootloader on B20, I can do the OTA update to B27 and that won't cause problems? Can I install TWRP on B20 without breaking updates?
Bootloader unlocked = no more OTAs for you.
DrakenFX got us from unlocked B20 to unlocked B27 - I have faith in him
RedWave31 said:
Bootloader unlocked = no more OTAs for you.
Click to expand...
Click to collapse
I've unlocked my bootloader on B20 and was able to upgrade to B27 with no issues.
Stock B20 -> Upgrade to B20_Boot -> Unlocked bootloader -> Downgraded back to B20 -> Upgraded to B27 -> Bootloader still unlocked
xtermmin said:
I've unlocked my bootloader on B20 and was able to upgrade to B27 with no issues.
Stock B20 -> Upgrade to B20_Boot -> Unlocked bootloader -> Downgraded back to B20 -> Upgraded to B27 -> Bootloader still unlocked
Click to expand...
Click to collapse
Oh, of course you can UPDATE. You just can't do it via a "real" OTA : you have to go here, get the files, apply modded updates via sdcard.
RedWave31 said:
Oh, of course you can UPDATE. You just can't do it via a "real" OTA : you have to go here, get the files, apply modded updates via sdcard.
Click to expand...
Click to collapse
What about receiving OTAs on rooted devices that haven't unlocked the bootloader?
I'm on B27 and I've been waiting for some progress before unlocking or rooting due to the plethora of issues reported like broken wifi, or camera, etc, but I'm getting tired of BS that could be dealt with if I had root such as the insufferable YouTube ads. I'm not going to watch an unskippable 30 second ad for a 2 minute video. I looked into it and the process of simply rooting it seems pretty convoluted (requiring drivers, flashing multiple things, etc) and some parts are ambiguous. For example there was no specific instructions, on the guide I was looking at, about how to install TWRP which I want to see stated clearly since again there are reports of people screwing up their phones simply trying to install that.
I'm kind of surprised there isn't an all-encompassing sticky with links to every possible issue and how to resolve them and I'm sitting here wondering if there's every going to be solid support for this device with easy root/unlock/recovery/updates like other flagships have.
Cyrus D. said:
I'm kind of surprised there isn't an all-encompassing sticky with links to every possible issue and how to resolve them and I'm sitting here wondering if there's every going to be solid support for this device with easy root/unlock/recovery/updates like other flagships have.
Click to expand...
Click to collapse
You might be looking for this thread?
About B27 and Cyanogen
- From what I've read, you still have to downgrade to B20 to unlock/root/twrp then update to B27 using modified files.
- Once you got TWRP, you have several options to restore your phone in case of problems (despite full stock firmwares being limited to EU models - officially)
- From the actual state of Cyanogen, to me, you're better off unlocking+rooting and using xposed than installing CM
- Unfortunately, the systemless root isn't compatible with Xposed (and likely will never be) so you don't have a "temporary" solution
- Think about us poor A2016G users in europe
About Root+OTA's
- If you have systemless Root, you can have the OTAs, but it will wipe the root...
About TWRP, if I remember correctly there is one requirement:
- Being unlocked (Guide here)
- Installing it (Guide here)
I am, myself, waiting for a repartition tool, because 14GB being used by system is making my eyes roll so hard I'm getting motion sickness. A stock MM build is 400MB today, and I can't believe there is 13.5GB worth of camera and wallpapers in here (so, wasted space)
- We can dream it's here for the Nougat Dual Boot system, but even then, 14GB !!!
RedWave31 said:
Oh, of course you can UPDATE. You just can't do it via a "real" OTA : you have to go here, get the files, apply modded updates via sdcard.
Click to expand...
Click to collapse
Nope. I used the official ZTE OTA update that I grabbed from ZTE servers myself. I did not use any sort of modified update. Yes, I did sideload it via sdcard, but that was because I didn't want to bother connecting to the network. I used ZTE's official update and applied it through the stock recovery fine.
---------- Post added at 11:29 AM ---------- Previous post was at 11:27 AM ----------
RedWave31 said:
- From what I've read, you still have to downgrade to B20 to unlock/root/twrp then update to B27 using modified files.
Click to expand...
Click to collapse
See above. Did not have to use modified to update from stock B20 (with unlocked bootloader) to stock B27 (still with unlocked bootloader).
I am interested in this post as I am in the same boot. I am kind of waiting for stock firmwares before I start messing around because things have gone wrong it the past that only a fresh install have fixed. I am good with my current build and am just missing xposed and all the ad block features.
xtermmin said:
Nope. I used the official ZTE OTA update that I grabbed from ZTE servers myself. I did not use any sort of modified update. Yes, I did sideload it via sdcard, but that was because I didn't want to bother connecting to the network. I used ZTE's official update and applied it through the stock recovery fine.
---------- Post added at 11:29 AM ---------- Previous post was at 11:27 AM ----------
See above. Did not have to use modified to update from stock B20 (with unlocked bootloader) to stock B27 (still with unlocked bootloader).
Click to expand...
Click to collapse
My bad, I just assumed that unlocked meant modified recovery with TWRP (and in that situation, it seems OTA won't work). "Just" unlocking the bootloader with everything else stock is usually rare.
Related
Had my A2017G for a few months, but still stuck on v1.0.0b06 with no available OTA updates.
Will I manually have to flash it to a android 7 version then will I be able to receive OTA?
Any guidance is much appreciated.
It really depends on where your device is from. That build may very well be the most up-to-date build released. Check the ZTE support site to be sure.
If you want to go to nougat right away, I'd suggest manually installing the German update zip / installing the leaked 7.1.1 B01 zip floating around. Afterwards, you'll receive the OTA prompt for the 7.1.1 B02 build.
Jacques101 said:
Had my A2017G for a few months, but still stuck on v1.0.0b06 with no available OTA updates.
Will I manually have to flash it to a android 7 version then will I be able to receive OTA?
Any guidance is much appreciated.
Click to expand...
Click to collapse
Yes, you need to download nougat image from ztedevices then push it to SD card and update to nougat will be available via system updater.
oleung4 said:
It really depends on where your device is from. That build may very well be the most up-to-date build released. Check the ZTE support site to be sure.
If you want to go to nougat right away, I'd suggest manually installing the German update zip / installing the leaked 7.1.1 B01 zip floating around. Afterwards, you'll receive the OTA prompt for the 7.1.1 B02 build.
Click to expand...
Click to collapse
I'm in the UK, and had no update since getting the handset.
So I won't need a build 10 to do the update to nougat?
Many thanks
Jacques101 said:
I'm in the UK, and had no update since getting the handset.
So I won't need a build 10 to do the update to nougat?
Many thanks
Click to expand...
Click to collapse
I forgot if it's required. But no harm in doing the updates incrementally. The German support page has the B10 update, as well as the 7.0 update. Then the 7.1.1 B01 leak can be found around here. These of course are all for the A2017G variant.
If you intend to unlock your bootloader, I'd suggest doing so before upgrading to nougat.
oleung4 said:
I forgot if it's required. But no harm in doing the updates incrementally. The German support page has the B10 update, as well as the 7.0 update. Then the 7.1.1 B01 leak can be found around here. These of course are all for the A2017G variant.
Click to expand...
Click to collapse
Thanks. I'll give that a try when I'm home. Is this becoming stuck on certain software versions common on the A7?
Also in hoping in the future OTA works normally. Apart from this, the phone is solid all-around.
Many thanks
I have one german version... live in argentina, and otas comes really fast... the same day that someone post some info here...
I manually update to 7.0, then manualy to 7.11 b1, then ota notifies me that b02 is relased, so manual update dont break otas...
I have a full stock phone, locked bl and nothing changed
pelelademadera said:
I manually update to 7.0, then manualy to 7.11 b1, then ota notifies me that b02 is relased, so manual update dont break otas...
I have a full stock phone, locked bl and nothing changed
Click to expand...
Click to collapse
Thanks for the piece of mind, I'll replicate your methodology and hope for the best.
Jacques101 said:
Thanks for the piece of mind, I'll replicate your methodology and hope for the best.
Click to expand...
Click to collapse
There is a full 7.1.1 B02 somewhere that you can also use. Just use the MiFlash flasher thing, it shouldn't go bad if you're using the stock flasher
Jacques101 said:
Thanks for the piece of mind, I'll replicate your methodology and hope for the best.
Click to expand...
Click to collapse
This is the full ota for V1.2.0B01: https://www.androidfilehost.com/?fid=457095661767151720
I'd suggest you manually update to V1.0.0B10 and then to V1.2.0B01.
You can find t he V1.0.0B10 on the ztemobile.de page: http://www.ztemobile.de/support/downloads/?product_id=2100 (Software Update B10)
I'd skip going to Nougat 7.0 first. Just upgrade directly to 7.1.1 with the full ota I posted.
Copy both of the files onto your sd card. They will then appear in the Updater (Settings -> Updates). Just run the upgrade from there.
Be aware! As previously stated by @oleung4 unlock your bootloader before upgrading. I unlocked mine on B06.
sToRm1nG said:
This is the full ota for V1.2.0B01: https://www.androidfilehost.com/?fid=457095661767151720
I'd suggest you manually update to V1.0.0B10 and then to V1.2.0B01.
You can find t he V1.0.0B10 on the ztemobile.de page: http://www.ztemobile.de/support/downloads/?product_id=2100 (Software Update B10)
I'd skip going to Nougat 7.0 first. Just upgrade directly to 7.1.1 with the full ota I posted.
Copy both of the files onto your sd card. They will then appear in the Updater (Settings -> Updates). Just run the upgrade from there.
Be aware! As previously stated by @oleung4 unlock your bootloader before upgrading. I unlocked mine on B06.
Click to expand...
Click to collapse
Thanks for your help, I'll update the thread in the next day or two about my progress.
Is the bootloader difficult to unlock past B06 in that case?
Jacques101 said:
Thanks for your help, I'll update the thread in the next day or two about my progress.
Is the bootloader difficult to unlock past B06 in that case?
Click to expand...
Click to collapse
It gets more complicated starting with (afaik) V1.0.0B11. If you want the easy way I'd suggest you do it before you upgrade past B10, I would even say do it before upgrading from B06.
Bootloader unlock
Jacques101 said:
Thanks for your help, I'll update the thread in the next day or two about my progress.
Is the bootloader difficult to unlock past B06 in that case?
Click to expand...
Click to collapse
I unlocked mine without too much problem from B08 using the windows 1.1.1 toolkit: https://forum.xda-developers.com/axon-7/development/tool-axon7toolkit-t3573108
I did get into a lot of trouble when I relocked it, so just avoid that.
Good luck
I've put the German image file on a USB and connected via an OTG cable, no joy......
I have V.1.0.0B11
If I were you I'll stuck with the latest marshmallow update. Nothing against nougat but MiFavor's version is sucks.
hollandnigel said:
I've put the German image file on a USB and connected via an OTG cable, no joy......
I have V.1.0.0B11
Click to expand...
Click to collapse
First: Check that you didn't put the zip with the buncha numbers. If you open the zip you should find an update.zip and a pdf or something, and you have to use the update.zip inside. NOT directly the one with the numbers!
Second: Your phone probably won't find the file on the OTG, if so just copy the file from the OTG to the root of the internal storage
Ah....
I unzipped it.....
Okay so still no joy, neither of the files would update
"System Update Failed"
Attached screenshots if anyone can help ??
hollandnigel said:
Okay so still no joy, neither of the files would update
"System Update Failed"
Attached screenshots if anyone can help ??
Click to expand...
Click to collapse
You almost brick the phone. Tell me a couple of things:
-What's the model? Turn it around and look below the Dolby Atmos symbol, it should be etched there. Either A2017 or G or U.
-I see that your software is of the A2017G. You probably have an A2017.
-What's the version that you downloaded? If it is for another version you can lose the IMEIs.
I have a similar issue. I have an A2017G. I had LOS on and am trying to go back to stock. I can get MM B10 or B11 to load, but N B01 won't flash within Android and if I force it from within recovery, the phone won't boot. anyone any smart ideas?
Hello,
I have a ZTE Axon 7. I have not received the OTA update to Android 7.1. Just now, I am on 6.0.1 (ZTE A2017GV1.0.0B08). My device has only the stock features (I have no unlocked anything).
So, my question is, which is the ordered and simplest steps to have a phone with a stock ROM (updated to 7.1) and with Bootloader, TWRP, and root?
I would like to maintain the stock ROM in order to use Google Daydream and Maintain an acceptable quality on Camera and Audio. I heard that LOS have some issues on these aspects.
Thanks,
youngz89
https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379
follow this guide until B
then, reflash stock recovery, upgrade your phone with ota.
after that, reenter edl mode, and flash twrp 3.1
look that the first twrp you flash is only to unlock, its signed and dont work. so dont keep it.
I use aosp extended, works really good, no manual camera unless you flash stock, sound works good
youngz89 said:
Hello,
I have a ZTE Axon 7. I have not received the OTA update to Android 7.1. Just now, I am on 6.0.1 (ZTE A2017GV1.0.0B08). My device has only the stock features (I have no unlocked anything).
So, my question is, which is the ordered and simplest steps to have a phone with a stock ROM (updated to 7.1) and with Bootloader, TWRP, and root?
I would like to maintain the stock ROM in order to use Google Daydream and Maintain an acceptable quality on Camera and Audio. I heard that LOS have some issues on these aspects.
Thanks,
youngz89
Click to expand...
Click to collapse
Or you can just use my toolkit which does it all for you https://forum.xda-developers.com/axon-7/development/tool-axon7toolkit-t3573108
Bkroes, using your tool, you suggest to update at nougat and, after the update, unlock the bootloader and root the device?
I have not received the OTA update, so I am thinking to update with FOTA.
youngz89 said:
Bkroes, using your tool, you suggest to update at nougat and, after the update, unlock the bootloader and root the device?
I have not received the OTA update, so I am thinking to update with FOTA.
Click to expand...
Click to collapse
Download the 7.1.1 zip and put it in the sd, then go to updates
Yes, but can I unlock the bootloader and root the device after the update? Or I have to unlock the bootloader before the update?
Where you able to do it?
hi folks!
I am pretty confused now. I am looking to get the V20 H990DS, but i am more confused now after reading here. My questions:
1. Is Bootloader unlock possible?
2. Can i install TWRP?
3. Can i root?
4. There is LOS official i know, but is the problem with 2. screen now fixed / going to be fixed?
Seems so good of a device, but i am insecure about it now after reading here. My old Mi4/Cancro is one of the best supported phones out there, so i dont expect it to be the same with V20, but i need working LOS with Root and working 2. screen (or the outlook on it working in the future) to be confident in buying it.
I hope you forgive me my nood questions,
Greetings
With sadly no replys, let me add what i know now:
1. + 2. + 3. Still no easy way in sight AFAIK. EDIT: To be clear: There IS a way, Dirty Santa, but the instructions are somewhat too complicated to be confident with trying. Have had rooted Phones with custom ROMs since over 5 years and never again a stock device, but i dont dare it. The 300€ i payed are much to much to have spend it on a bricked device. Will try to find more dirty Santa noob friendly explanations and post them here. EDIT2: For those who DO dare it, here the thread: https://forum.xda-developers.com/v20/development/dirtysanta-h990-t3624296
4. Second screen still a problem, nothing new heard for quite a long time.
Anyone with knowledge to add or correct, please help! Stock ROM is not as bad as i thought, but without Root, Android is not fully usable for me.
thank you pro for this thread
very useful for me.
Stele88 said:
With sadly no replys, let me add what i know now:
1. + 2. + 3. Still no easy way in sight AFAIK. EDIT: To be clear: There IS a way, Dirty Santa, but the instructions are somewhat too complicated to be confident with trying. Have had rooted Phones with custom ROMs since over 5 years and never again a stock device, but i dont dare it. The 300€ i payed are much to much to have spend it on a bricked device. Will try to find more dirty Santa noob friendly explanations and post them here. EDIT2: For those who DO dare it, here the thread: https://forum.xda-developers.com/v20/development/dirtysanta-h990-t3624296
4. Second screen still a problem, nothing new heard for quite a long time.
Anyone with knowledge to add or correct, please help! Stock ROM is not as bad as i thought, but without Root, Android is not fully usable for me.
Click to expand...
Click to collapse
i dont get about your complain. you said already using phone with root for 5 years so i guess you've been here on xda for a while. if you really want a phone which support custom rom go with phone which support unlock bootloader like HTC, Oneplus, or even xiaomy. its not that hard finding them on XDA. 300euro for briked devices? well, if you read v20 section carefully you knew most people here bought this devices for the camera, audio, and other things like removable battery, etc. i never found someone who bricked their devices while rooting here, even if they do we already had flasher tools like LG up which already tested fully working by some members. and whats the problem with second screen? its working for whatever it made for. are you expecting to watch movie on those 2.1 inch display? i had lg v20 h990ds rooted with magisk and had no problem so far. bought some apps like grenify and titanium backup for debloated and my phone rocking solid for abouth 2 month. if you cant wait for LOS just bought lenovo zuk2 or oneplus 3t on the same price range.
No problem doing 1+2+3 with DirtySanta exploit/procedure. It's not as complicated or dangerous as it might seem from the instructions. I thought I had soft-bricked my phone twice after rebooting normally with the old kernel instead of straight to TWRP to update the kernel first, but it was easy to re-flash the 10d factory firmware file I had and start over again without any issues both times.
Basic summary of procedure:
1. Flash factory firmware version earlier than 31 December 2016 (only needed if installed firmware version is after 1 January 2017).
2. Do DirtySanta exploit to unlock bootloader and install TWRP and root.
3. Use kdzwriter to update phone's system/modem/cust partitions to latest firmware version without overwriting unlocked bootloader/TWRP, reinstall root (SuperSU or Magisk) from TWRP.
4. Disable automatic OTA updates so that any future firmwares won't automatically install and overwrite bootloader/recovery and remove root and set ARB 1. If that ever happens then TWRP/root will probably be gone forever.
provided you follow the instructions carefully, it's safe to root with DirtySanta.
xoose said:
No problem doing 1+2+3 with DirtySanta exploit/procedure. It's not as complicated or dangerous as it might seem from the instructions. I thought I had soft-bricked my phone twice after rebooting normally with the old kernel instead of straight to TWRP to update the kernel first, but it was easy to re-flash the 10d factory firmware file I had and start over again without any issues both times.
Basic summary of procedure:
1. Flash factory firmware version earlier than 31 December 2016 (only needed if installed firmware version is after 1 January 2017).
2. Do DirtySanta exploit to unlock bootloader and install TWRP and root.
3. Use kdzwriter to update phone's system/modem/cust partitions to latest firmware version without overwriting unlocked bootloader/TWRP, reinstall root (SuperSU or Magisk) from TWRP.
4. Disable automatic OTA updates so that any future firmwares won't automatically install and overwrite bootloader/recovery and remove root and set ARB 1. If that ever happens then TWRP/root will probably be gone forever.
Click to expand...
Click to collapse
Using the steps on #3, would it be safe to say that we can update the device to oreo and still keep root?
nurse_chuck said:
Using the steps on #3, would it be safe to say that we can update the device to oreo and still keep root?
Click to expand...
Click to collapse
No, right now if you update you'll lose root as the engineering aboot isn't compatible with Oreo and you have possibly non working data, invalid sim issues etc
Sent from my LG-H910 using XDA Labs
cnjax said:
No, right now if you update you'll lose root as the engineering aboot isn't compatible with Oreo and you have possibly non working data, invalid sim issues etc
Sent from my LG-H910 using XDA Labs
Click to expand...
Click to collapse
Too bad. Your earlier post actually got me excited. Hehe. Anyway, hopefully someones starts working on rooting the oreo firmware.
The short answer? @Stele88
Yes. To all of it.
The long answer starts with the Dirty Santa root process. Believe me, I was daunted by it as well, but as long as you follow it (or the noob version of the guide you can find by searching around the same section the original guide is in) and take your time, you'll be okay. It's what I did and I'm now where I am today.
I'll address a couple things since I have the same device as you. If you want to get your device working properly on LineageOS/ResurrectionRemix (LOS with more customisation) then it's a long process.
1. Start by following the bootloader unlock process for Dirty Santa. Depending on what firmware your device gets shipped with, you may need to downgrade to (in the case of the H990DS) the v10c firmware. Once done, then you can Dirty Santa the bootloader and get it unlocked.
2. Once that's done and you're rooted with the initial TWRP from the thread installed, you'll want to look into KDZWriter. It's a program by the same emdroidle who did the Dirty Santa process for us that allows you to update your STOCK system software to newer versions and keep root. You can use it for example with the H990DS firmware KDZ files and go from rooted 10c -> rooted 10f -> rooted 10xx -> etc. until you're on the latest available 7.0 KDZ for the H990DS. This will be the longest part of your process, but it ensures that everything is up to date before going to AOSP/Lineage/Resurrection, specifically the modem partition. I recommend using the TWN region of firmwares if you're just going to convert to a custom ROM anyway, but any region will work fine (the only real difference is that, for example, the Australia region of firmwares comes with more bloat than the TWN region).
2b. You can also use KDZWriter from an updated TWRP you can get in the thread by Phoenix591, his latest TWRP versions have KDZWriter built-in so you don't have to run it off the computer, you can do it all with the kdz files in recovery.
3. Yes, you can root using the Dirty Santa method on v10c kdz firmware. I recommend Magisk for root over SuperSU.
4. There's no official LineageOS that is as up to date as the unofficial ones, and there's no official ones with second screen enabled full stop. That being said, the unoffcial LineageOS 15.1 by x86cpu has been my rock solid daily driver for about 2 months now and I've never had any issues that stop me from using it. The same can be said for ResurrectionRemix 6.2 by Blaises. To use either of these, you will need the updated TWRP from Phoenix591.
4. Second-screen enabled builds of LineageOS and ResurrectionRemix do exist, and in this case ResurrectionRemix is (as of this post) more up-to-date than the LineageOS 15.1 second screen version. If you find yourself needing additional features that aren't in the stock kernels for those ROMs (such as KCAL configuration to help with burn in, among other things), then I maintain the second-screen version of the Gamma Kernel by Omar-Avelar. People are successfully using this with second-screen ROMs and have full functionality. You can purchase the app BoredSigns from the play-store to add additional functions to the second-screen.
As I said at the start, it is a long process, but a very worthwhile one. The jump from stock to custom-ROMs is absolutely incredible. Again, in short, yes. You can get everything you want.
Just do your searching around the forums for the processes I outlined above, ask any questions you have, pre-download your kdz firmwares from HERE and any software you need, and just take your time. It's maybe a couple hours to get setup with a rooted stock system that's up-to-date, and maybe another hour or so to go from stock to Lineage/Resurrection.
P.S: If all goes well with the Dirty Santa process, but you get screen distortion after rebooting when flashing the TWRP from Dirty Santa, just pull the battery instead of rebooting.
Good luck, good searching, and remember to not be afraid to ask questions in the relevant threads.
---------- Post added at 04:50 AM ---------- Previous post was at 04:49 AM ----------
nurse_chuck said:
Too bad. Your earlier post actually got me excited. Hehe. Anyway, hopefully someones starts working on rooting the oreo firmware.
Click to expand...
Click to collapse
It's highly doubtful this will happen, but one can hope. Right now the best way to get Oreo is through a custom ROM, purely because of how security is implemented by LG in the stock Oreo ROMs.
iDefalt said:
It's highly doubtful this will happen, but one can hope. Right now the best way to get Oreo is through a custom ROM, purely because of how security is implemented by LG in the stock Oreo ROMs.
Click to expand...
Click to collapse
Actually it is possible runningnak3d has already said awhile ago he has a process to root stock oreo he's just not releasing it yet so LG can't patch it before the Oreo roll out is complete
Sent from my LG-H910 using XDA Labs
I am having xt1686 indian variant .. i unlocked the bootloader and installed the custom roms.. now while going back to stock i mistakenly installed NPNS (US VARIANT, I suppose) ..
I am unable to install the NPN version now .. i guess the bootloader is not matching ..
Right now i am having a bootloader - C0.8(*) in NPNS ...
PLEAAE SUGGEST HOW TO MOVE TO INDIAN VERSION OF NPN... THNKS..
S does not mean US or any other variant specific build... there are literally different builds for different variants. My US Retail version is NPN25.173-83
In previous Moto models, the S meant it had been upgraded from an OTA, but in looking in my current device it has received several OTAs and does not have the S, so either that has been depreciated or our original assumptions in earlier models was incorrect.
Either way, the fact the S is there does not mean US (or any other country), just a slightly different build... I don't have an answer of why you can't go back though.
https://forum.xda-developers.com/g5-plus/help/npns-nps-firmware-t3677576
Fastboot NPN25.137-15 build (may be found as brasil-latam)
Lock bootloader (necessary to receive ota) google it
Reboot device
Update phone via ota received in system
Done.
Use this link to download 137-15 build
http://www.stechguide.com/download-moto-g5-plus-stock-firmware/
abhi.a3s said:
Fastboot NPN25.137-15 build (may be found as brasil-latam)
Lock bootloader (necessary to receive ota) google it
Reboot device
Update phone via ota received in system
Done.
Use this link to download 137-15 build
http://www.stechguide.com/download-moto-g5-plus-stock-firmware/
Click to expand...
Click to collapse
Generally, OTA updates can be received with a locked or unlocked bootloader. Only requirement is to have a stock and unmodified system.
However, I personally would caution against downgrading from NPNS firmware to NPN, as you run a risk of hard bricking if you take OTA updates after you've downgraded. As acejavelin has mentioned, the NPNS firmware should reflect OTA/security updates (but seems that Motorola's naming convention is a bit inconsistent), which means your bootloader is likely updated by the firmware. If you've flashed a NPNS firmware, you'd likely be at least on the may security patch. The Indian firmware you'd need is the January patch (NPN25.137-15, as I don't think the NPN25.137-67 or 67-5 firmwares have been leaked). Thus, downgrading to an earlier firmware might give you problems if you then use OTA updates to update. We've already seen a similar situation in the Moto G5 plus unbrick thread.
Instead of reflashing the Indian stock ROM and risking a hard brick, you may wish to look into using the TWRP flashable images which only touch the system.
echo92 said:
Generally, OTA updates can be received with a locked or unlocked bootloader. Only requirement is to have a stock and unmodified system.
However, I personally would caution against downgrading from NPNS firmware to NPN, as you run a risk of hard bricking if you take OTA updates after you've downgraded. As acejavelin has mentioned, the NPNS firmware should reflect OTA/security updates (but seems that Motorola's naming convention is a bit inconsistent), which means your bootloader is likely updated by the firmware. Thus, downgrading to an earlier firmware might give you problems if you then use OTA updates to update. We've already seen a similar situation in the Moto G5 plus unbrick thread.
Instead of reflashing the Indian stock ROM and risking a hard brick, you may wish to look into using the TWRP flashable images which only touch the system.
Click to expand...
Click to collapse
I had same issue.
I unlocked my bootloader when I was on NPN25-137-67, installed custom roms as well. My bootloader got corrupted.
I tried flashing the twrp stock zip but it didn't work.
I know the risks of downgrading and it can hardbrick the device. But since I already downgraded and my fone is still alive I thought it could help him as well. So it's tested. And it did not mess up anything.
About locked/unlocked bootloader, you might be right that ota updates can be received. But since I locked my bootloader and then did the update process. twice. it worked.
Well ofcourse there are lots of ifs so I would also suggest downgrading firmware as a last resort.
P. S. I have xt1686 Indian variant.
---------- Post added at 07:37 AM ---------- Previous post was at 07:31 AM ----------
Twrp images
https://forum.xda-developers.com/g5-plus/development/rom-twrp-flashable-stock-builds-t3675616
Build 67-5
https://rsdsecure-cloud.motorola.co...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Credit to rickk
Use vpn if unable to download
abhi.a3s said:
I had same issue.
I unlocked my bootloader when I was on NPN25-137-67, installed custom roms as well. My bootloader got corrupted.
I tried flashing the twrp stock zip but it didn't work.
I know the risks of downgrading and it can hardbrick the device. But since I already downgraded and my fone is still alive I thought it could help him as well. So it's tested. And it did not mess up anything.
About locked/unlocked bootloader, you might be right that ota updates can be received. But since I locked my bootloader and then did the update process. twice. it worked.
Well ofcourse there are lots of ifs so I would also suggest downgrading firmware as a last resort.
P. S. I have xt1686 Indian variant.
---------- Post added at 07:37 AM ---------- Previous post was at 07:31 AM ----------
Twrp images
https://forum.xda-developers.com/g5-plus/development/rom-twrp-flashable-stock-builds-t3675616
Click to expand...
Click to collapse
Okay, when you hard bricked and then used the blankflash, then by flashing the NPN25.137-15 update, you may not have run into any issues as that was the update prior to NPN25.137-67. Thus, you may have been okay as the OTA update simply patched the same files as before. You may also have been able to downgrade without issue as the NPN25.137-67 firmware is only up to the March 2017 patch level.
The opening poster has the different problem of having NPNS25.137 firmware, which at the moment is either NPNS25.137-33-5/NPNS25.137-33-11 or NPNS25.137-35-5 (EU or US firmware) with the May 2017/August 2017 security patch. Downgrading from the May 2017 patch or later and then accepting OTA updates appears to cause a hard brick, especially if you cross downgrade from the NPNS firmware to the Indian firmware: https://forum.xda-developers.com/g5-plus/help/moto-g5-plus-hard-bricked-recognized-t3636457
echo92 said:
Okay, when you hard bricked and then used the blankflash, then by flashing the NPN25.137-15 update, you may not have run into any issues as that was the update prior to NPN25.137-67. Thus, you may have been okay as the OTA update simply patched the same files as before. You may also have been able to downgrade without issue as the NPN25.137-67 firmware is only up to the March 2017 patch level.
The opening poster has the different problem of having NPNS25.137 firmware, which at the moment is either NPNS25.137-33-5/NPNS25.137-33-11 or NPNS25.137-35-5 (EU or US firmware) with the May 2017/August 2017 security patch. Downgrading from the May 2017 patch or later and then accepting OTA updates appears to cause a hard brick, especially if you cross downgrade from the NPNS firmware to the Indian firmware: https://forum.xda-developers.com/g5-plus/help/moto-g5-plus-hard-bricked-recognized-t3636457
Click to expand...
Click to collapse
Well ofcourse there is a big potential of hard bricking the device by the method. That's why I said last resort.
So what do you suggest?
TWRP image? And if it doesn't work, he should probably wait up for next NPN build? @toyesh.patra you should consider keeping a custom rom if possible.
Btw
The ota update which I received was August patch. After which I unlocked my bootloader. It was either NPN25.137-67 or NPN25.137-67-5. I'M not sure about version. But it was definitely August patch.
Or maybe I was lucky one time.
Won't do it another time.
anuraag.neo said:
Build 67-5
https://rsdsecure-cloud.motorola.co...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Credit to rickk
Use vpn if unable to download
Click to expand...
Click to collapse
For 1686? Full fastboot firmware leaked?
yea, right now i m using the 67-5 build using twrp..
although i wanted to use the 67-5 with locked bootloader.. nevermind ..
psychopac said:
For 1686? Full fastboot firmware leaked?
Click to expand...
Click to collapse
Yes
So if I wanted to go full stock after flashing any custom ROM, all I need to do is flash the 67-5 firmware and I'll be good to go, right?
PS: I'm already on stock and updated to 67-5
psychopac said:
So if I wanted to go full stock after flashing any custom ROM, all I need to do is flash the 67-5 firmware and I'll be good to go, right?
PS: I'm already on stock and updated to 67-5
Click to expand...
Click to collapse
Yes
I can't download it. How Can I download? please upload googel Thanks bro
birkhoffChang said:
I can't download it. How Can I download? please upload googel Thanks bro
Click to expand...
Click to collapse
use search function before asking
https://forum.xda-developers.com/g5-plus/how-to/stock-firmware-npn25-137-67-5-fastboot-t3694738
Can you please guide me how to manually update my AT&T v20 to be stock not rooted oreo, my h910 is stock never touched, not rooted of version h91010m which can't get updates as it is unlocked and am not in US.
All i want is just to update it manually to the stock oreo software.
Thanks a lot
https://forum.xda-developers.com/v20/how-to/root-h910-v10m-t3664500
Use this to root.
Instead of flashing the 10v att image like the last step suggests, use the 20g Oreo image instead
H910 Oreo 20g: https://androidfilehost.com/?fid=1322778262903991071
Thank @clsA for the Oreo link
Thank you
Thanks a lot for the clarification...
i have read more, i believe this rom will let me stock oreo so am worried i can't update the phone again in case of future updates.
is there a way to update in future? Also is there a way to change the software from h910 to h915 so that i can recieve ota updates normally in future?and is it safe as am afraid to loose signal or brick phone etc...
Thanks a lot in advance.
seikobasha said:
Thanks a lot for the clarification...
i have read more, i believe this rom will let me stock oreo so am worried i can't update the phone again in case of future updates.
is there a way to update in future? Also is there a way to change the software from h910 to h915 so that i can recieve ota updates normally in future?and is it safe as am afraid to loose signal or brick phone etc...
Thanks a lot in advance.
Click to expand...
Click to collapse
After you flashed the 20g Oreo image, it will be stock as if you took the ota update itself. You'll be able to accept ota updates after words. Follow the root thread, amd you'll be fine
hawkeye29 said:
After you flashed the 20g Oreo image, it will be stock as if you took the ota update itself. You'll be able to accept ota updates after words. Follow the root thread, amd you'll be fine
Click to expand...
Click to collapse
The problem is i can't recieve ota updates even i am stock, it is AT&T restriction because my phone is unlocked am using other network (am not in us)
ota updates need to have a working AT&T SIM inserted in phone. It is very stupid policy for AT&T.
So my question now is, is there a way to convert h910 to h915 safely? Because Canadian operators allow ota to unlocked phones...
Or is there a way to manually upgrade in future after i upgrade to stock oreo?
seikobasha said:
The problem is i can't recieve ota updates even i am stock, it is AT&T restriction because my phone is unlocked am using other network (am not in us)
ota updates need to have a working AT&T SIM inserted in phone. It is very stupid policy for AT&T.
So my question now is, is there a way to convert h910 to h915 safely? Because Canadian operators allow ota to unlocked phones...
Or is there a way to manually upgrade in future after i upgrade to stock oreo?
Click to expand...
Click to collapse
why are you worried about updates when you can't take them now ?
Yes you can convert your phone to 915 it's the first step in the rooting process
if you want to stay 915 use the H915 Oreo KDZ > https://forum.xda-developers.com/v20/how-to/h915-oreo-kdz-link-t3826812
If you want a H910 on Oreo use my zip. If another update comes along their will always be another zip (provided we get root and TWRP for Oreo)
In case i will just flash the h915 oreo kdz, should i flash all partitions? Including modem, bootloader, etc...
Is it safe? Because in the guide it say i will loose the signal after flashing h915...
Also Should i still root first or can just flash directly?
Also is it safe to get future ota updates when software is for h915 and treat my phone as if it is h915 from the beginning?
Many thanks in advance.
seikobasha said:
In case i will just flash the h915 oreo kdz, should i flash all partitions? Including modem, bootloader, etc...
Is it safe? Because in the guide it say i will loose the signal after flashing h915...
Also Should i still root first or can just flash directly?
Also is it safe to get future ota updates when software is for h915 and treat my phone as if it is h915 from the beginning?
Many thanks in advance.
Click to expand...
Click to collapse
You flash all partitions for non rooted stock which should work like normal with everything working.
My guide is for those trying to keep root intact so to preserve the dirtysanta eng aboot so there are problems with data at the moment.
hawkeye29 said:
https://forum.xda-developers.com/v20/how-to/root-h910-v10m-t3664500
Use this to root.
Instead of flashing the 10v att image like the last step suggests, use the 20g Oreo image instead
H910 Oreo 20g: https://androidfilehost.com/?fid=1322778262903991071
Thank @clsA for the Oreo link
Click to expand...
Click to collapse
I'm in the same situation as the creator of this thread, I can not update my phone from OTA
Assuming I do this to update. Would Android Oreo be rooted? Could I enter TWRP ?.
Since If I do this procedure and update my phone to Oreo and I don't have root or chance to get into TWRP . I would be stuck until there is some way to root the phone (if it comes into existence)
PS: I bought an AT&T sim card from eBay, but I couldn't activate it. Do you guys have any idea if the sim being activated I could update my phone despite not being in an AT&T network?
alan2323 said:
I'm in the same situation as the creator of this thread, I can not update my phone from OTA
Assuming I do this to update. Would Android Oreo be rooted? Could I enter TWRP ?.
Since If I do this procedure and update my phone to Oreo and I don't have root or chance to get into TWRP . I would be stuck until there is some way to root the phone (if it comes into existence)
PS: I bought an AT&T sim card from eBay, but I couldn't activate it. Do you guys have any idea if the sim being activated I could update my phone despite not being in an AT&T network?
Click to expand...
Click to collapse
You will loose root and be back to stock bootloader so no twrp. It's stock oreo with no way of rooting it for now.
CaseyS said:
You will loose root and be back to stock bootloader so no twrp. It's stock oreo with no way of rooting it for now.
Click to expand...
Click to collapse
Just to clarify this statement a little. If you want to run Oreo now, you can't have root. However, you CAN downgrade back to Nougat and root when we finally have the Oreo + engineering bootloader issues worked out.
The US996 will be getting Oreo eventually, and that firmware is what is going to allow us to have rooted Oreo on models that use the engineering bootloader.
If the US996 wasn't getting Oreo, then I would waste the time trying to get things sorted out -- but that is just a waste of time.
We have waited for Oreo this long, waiting another couple of weeks isn't going to hurt.
As a final statement, I have had a chance to play with Oreo on my H910, and I am NOT impressed. What a ****poor, crap job that LG has done. It may get better with future updates, but I wouldn't bank on it.
-- Brian
runningnak3d said:
Just to clarify this statement a little. If you want to run Oreo now, you can't have root. However, you CAN downgrade back to Nougat and root when we finally have the Oreo + engineering bootloader issues worked out.
The US996 will be getting Oreo eventually, and that firmware is what is going to allow us to have rooted Oreo on models that use the engineering bootloader.
If the US996 wasn't getting Oreo, then I would waste the time trying to get things sorted out -- but that is just a waste of time.
We have waited for Oreo this long, waiting another couple of weeks isn't going to hurt.
As a final statement, I have had a chance to play with Oreo on my H910, and I am NOT impressed. What a ****poor, crap job that LG has done. It may get better with future updates, but I wouldn't bank on it.
-- Brian
Click to expand...
Click to collapse
Just as I suspected, no oreo orgasm lol ?
Sent from my LG-H910 using XDA Labs
runningnak3d said:
Just to clarify this statement a little. If you want to run Oreo now, you can't have root. However, you CAN downgrade back to Nougat and root when we finally have the Oreo + engineering bootloader issues worked out.
The US996 will be getting Oreo eventually, and that firmware is what is going to allow us to have rooted Oreo on models that use the engineering bootloader.
If the US996 wasn't getting Oreo, then I would waste the time trying to get things sorted out -- but that is just a waste of time.
We have waited for Oreo this long, waiting another couple of weeks isn't going to hurt.
As a final statement, I have had a chance to play with Oreo on my H910, and I am NOT impressed. What a ****poor, crap job that LG has done. It may get better with future updates, but I wouldn't bank on it.
-- Brian
Click to expand...
Click to collapse
got alot more weeks to wait for us996.
It could come in mid october.
https://www.reddit.com/r/lgv20/comments/9b9n6a/us996_oreo_date/?st=jlflkarq&sh=a9643b7f
runningnak3d said:
As a final statement, I have had a chance to play with Oreo on my H910, and I am NOT impressed. What a ****poor, crap job that LG has done. It may get better with future updates, but I wouldn't bank on it.
-- Brian
Click to expand...
Click to collapse
I remember reading earlier this year about how LG was going to reform their mobile division, getting better at software updates and halting/slowing down the typical release schedule of phones.
Seems none of that has happened as far as I can tell, especially the software part. What a farce.
finally i updated my H910
i managed to updated my H910 by simply flashing the oreo H915 KDZ file with patched LGUP and it seems very good... signal is ok no errors so far except one after rebooting phone
ARB is still zero.
thanks a lot for all of you
runningnak3d said:
Just to clarify this statement a little. If you want to run Oreo now, you can't have root. However, you CAN downgrade back to Nougat and root when we finally have the Oreo + engineering bootloader issues worked out.
The US996 will be getting Oreo eventually, and that firmware is what is going to allow us to have rooted Oreo on models that use the engineering bootloader.
If the US996 wasn't getting Oreo, then I would waste the time trying to get things sorted out -- but that is just a waste of time.
We have waited for Oreo this long, waiting another couple of weeks isn't going to hurt.
As a final statement, I have had a chance to play with Oreo on my H910, and I am NOT impressed. What a ****poor, crap job that LG has done. It may get better with future updates, but I wouldn't bank on it.
-- Brian
Click to expand...
Click to collapse
Why do you think US996 getting Oreo helps? What if the eng aboot can't initialize the oreo modem properly (maybe intentional change)? I have a thought, maybe we can try if the stock nougat aboot, say H910, can boot the Oreo with data? We could flash everything Oreo stock and just leave the aboot nougat. Since signatures are still LG, it should boot up? And if it still can't have data, maybe eng aboot can never initialize properly, I don't know.
Questions about the H910 --> H915 Conversion
I have read several different postings on how to change the H910 to H915
I read the posting by runningnak3d and I am bit confused.
Sorry for the noob questions
1) If I flash H910 to the H915 v10e kdz, do I have to continue the steps to flash to oreo or can the phone be updated from OTA?
I really don't want the AT&T logos on my phone and I don't need my phone to be rooted or need dirtysanta.
2) Would flashing it with LG UP be enough to get Oreo?
3) I'm confused with the steps after downloading terminal emulator? - Do I need to do these steps if I want to keep the H915 Rom?
Sorry if my questions are dumb.
Thank you in advance.
Much appreciated
-Rmc604
rmc604 said:
I have read several different postings on how to change the H910 to H915
I read the posting by runningnak3d and I am bit confused.
Sorry for the noob questions
1) If I flash H910 to the H915 v10e kdz, do I have to continue the steps to flash to oreo or can the phone be updated from OTA?
I really don't want the AT&T logos on my phone and I don't need my phone to be rooted or need dirtysanta.
2) Would flashing it with LG UP be enough to get Oreo?
3) I'm confused with the steps after downloading terminal emulator? - Do I need to do these steps if I want to keep the H915 Rom?
Sorry if my questions are dumb.
Thank you in advance.
Much appreciated
-Rmc604
Click to expand...
Click to collapse
you can do as i did, just flash H915 KDZ Oreo file directly using patched LGUP and select to Partition DL all partitions.
you will have stock oreo H915 fully functional phone, there is only 1 error message that will appear every reboot of phone but will not make any harm.
there is no any issues or problems i have noticed so far, also the software seems more stock than AT&T version.
rmc604 said:
I have read several different postings on how to change the H910 to H915
I read the posting by runningnak3d and I am bit confused.
Sorry for the noob questions
1) If I flash H910 to the H915 v10e kdz, do I have to continue the steps to flash to oreo or can the phone be updated from OTA?
I really don't want the AT&T logos on my phone and I don't need my phone to be rooted or need dirtysanta.
2) Would flashing it with LG UP be enough to get Oreo?
3) I'm confused with the steps after downloading terminal emulator? - Do I need to do these steps if I want to keep the H915 Rom?
Sorry if my questions are dumb.
Thank you in advance.
Much appreciated
-Rmc604
Click to expand...
Click to collapse
you can simply use lgup to backup your current setup (not userdata)
and use lgup to flash the 915 Oreo kdz
Note: someone said that converting to 915 caused google now to stop working but everything else was ok
if you want to return to 910 stock you'll have to do the root procedure and flash h910 10q or 20g back to stock rom from TWRP
clsA said:
Note: someone said that converting to 915 caused google now to stop working but everything else was ok
Click to expand...
Click to collapse
it is working fine with me am H910 converted to H915 by flashing via LGUP.