Database Develop

[GUIDE/FAQ][XT1052] How To Downgrade From 5.1 to 4.4.4 and below [TESTED]

Hello,
This is a short (hopefully) guide on how to downgrade your Moto X 2013 from Android 5.1 to 4.4.4 (and lower).
The procedure is fairly simple and takes about 10-15 minutes, once you get the files you need.It does however needs some technical understanding of how to use fastboot, command prompt and eventually unlocking your bootloader.Fairly strong reading skills recommended.
WIth that said, make sure you read thorough and even few times before you take any actions.
This method has now been proven to be working by multiple people, on many different versions of Moto X 2013, including GPE
Disclaimer
Although this procedure has been tested by me and some friends numerous times, it still has some risk involved.You MUST be aware of the potential risks of modifying your phone software and performing actions that may lead to complete defunct of your device.
As you may expect I will not take any responsibility or be accountable for any damage or loss you may incur by following this guide.
Performing a system downgrade WILL void your warranty and it is NOT supported by Motorola/Lenovo or their service network.
I also recommend you read This post by KidJoe about the potential risks that downgrade might involve.
This guide has came up being needed as many people were afraid to downgrade after reading the post of KidJoe and I don't blame them, it is possible something to go wrong and you end up with non-working device.
HOWEVER, this has been tested on more than 10 separate Moto X 2013 and more than 12 times on my own device, which makes me to believe that it's generally safe.
Prerequisites
You need your bootloader unlocked.Motorola and their bootloader does NOT support downgrading and it will spit errors in fastboot.
WHEN YOU UNLOCK YOUR BOOTLOADER ALL YOUR PERSONAL DATA ON YOUR DEVICE WILL BE LOST.MAKE SURE YOU BACKUP YOUR FILES AND THEN PROCEED.
You can find how to unlock your bootloader HERE or just use the search here in the forums, plenty of info on that matter.
If you cannot or don't want to unlock your bootloader, then you CANNOT downgrade.
Files Needed
For this tutorial we`ll do downgrade from 5.1 to 4.4.4.This is the safest downgrade and it will be successful if you follow all the steps w/o any skipping.
The Android image used is for XT1052, but if you got different model, you can find the image for your own model and use that instead.
1.First you need a signed image of Android 4.4.4 for Moto X 2013.You can find one Filefactory or RetailEU here <=> RetailGB here <=> RetailDE here
If you want to download the image faster, use the Yandex-hosted images, FileFactory is slow.
2.Motorola Device Drivers: You can find them Here
3.Motorola Fastboot and generic adb/fastboot tools package: You can find it attached to this post or click Here
Flashing your device
0.Charge your device's battery to at least 35%.
1.Extract the archive with the signed images somewhere (in this case I`ll use C:\temp , but you can use any drive or directory if you so desire).
2.Extract the android-tools archive in the same directory.You should have boot.img, recovery.img, system.img and mfastboot in same directory.
3.Reboot your device in bootloader (Power your device off -> Hold Volume Down and Press Power button -> then release).
!!THIS WILL DELETE YOUR USER FILES EVEN IF YOU HAVE YOUR BOOTLOADER ALREADY UNLOCKED!!!
4.Open a command prompt and navigate to C:\temp and execute the following commands:
Code:
mfastboot erase cache
mfastboot erase userdata
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
mfastboot erase userdata
mfastboot reboot
DO NOT skip erasing the userdata, doing so , you'll most likely end up with soft brick.Just don't do it.
Result
Congratz, now you have successfully downgraded your device to Android 4.4.4
The device will take some time the first boot to create dalvik cache and some other stuff, but it should not take more than 5 minutes.
When your device boots, it will ask you at some point to downgrade the motorola services bla bla, agree to that, your device will reboot and it will tell you that the downgrade was successful.I did this more than 10 times, seems to be totally safe.
Any feedback will be appreciated, you may ask questions, but don't expect me to answer to every single one.
If I missed something, I'll add up/fix as soon as I can.

FAQ
What if I want to downgrade to Android 4.4.2 / 4.3 / 4.2.2 ?
This is possible, the procedure is the same as listed above.You just have to know that if you do such downgrade, you should never update via OTA update, at any cost.This will corrupt the bootloader of your device and you won't be able to restore it.If you downgrade to anything below 4.4.4 and you want at some point to upgrade, you should do it ONLY by official signed image and NOT OTA.
You've been warned.
I can't find the exact same firmware that my device runs, eg. AsiaRetail.Is it possible to use firmware image from a different region/operator?
While it's recommended to use your exact firmware image, it is not necessary. You can use an image from other region, but you should follow some simple rule. Try to stick to the same phone model, eg XT1052 firmware.
I updated via OTA but I've recently rooted and installed a custom rom. Is it necessary to go back to stock 5.1 to downgrade?
No need, as long as your custom rom/kernel didn't mess with the fs of the partitions.
Why is this flashing procedure cut down, omg there are other commands that I've read in other guides and they say that I must flash modem, fsg, delete some magical modem states, why you didn't include these?!?
While it is true that other guides suggest you flash modem, fsg and some other things, these are mainly driven from the Motorola's own procedure xml file, flashing these is not necessary at all, this is used to repair eventual errors in these parts, but usually there is no problem there at all.
Another thing is that these parts are cross-compatible and leaving them as they are is perfectly fine.
How do I go back to 5.1 stock?
1.Do NOT update by OTA, just to be on the safe side.
2. Use the same procedure as described, but with image of 5.1 instead.
How do I disable the OTA notifications?
1. If you're rooted, then just delete or revoke permissions of /system/priv-app/3c_ota.apk
2. If you're not rooted, then don't install the Motorola Update Services from the Play Store. If you already updated them, then just uninstall the update and that's all.
I'm getting "Not enough space" errors, when I try to flash the system.img.I'm using mfastboot, but still the same problem?!?
Use this and it will work:
mfastboot flash system system.img -P

What if I have a custom recovery? Sorry I'm new to this stuff. Which mode do you enter before entering the commands in cmd prompt?

legend.in.boxers said:
What if I have a custom recovery? Sorry I'm new to this stuff. Which mode do you enter before entering the commands in cmd prompt?
Click to expand...
Click to collapse
Having custom recovery doesn't affect anything. This process will flash the stock recovery.
You don't need to enter any mode in the list, just leave the phone in the bootloader menu.

Hello.
I just might use this method to downlograde from 5.1 to 4.4.4...
I have the always mobile radio active bug while being connected to wifi, so my stand by time with wifi is just awful.
Thanks.

SanD-82 said:
Hello.
I just might use this method to downlograde from 5.1 to 4.4.4...
I have the always mobile radio active bug while being connected to wifi, so my stand by time with wifi is just awful.
Thanks.
Click to expand...
Click to collapse
I had the same issue, wifi would never go sleep. RAM management is horrific and the YouTube app was causing some troubles with the sound module, at some point the sound was totally not working.

liveroy said:
I had the same issue, wifi would never go sleep. RAM management is horrific and the YouTube app was causing some troubles with the sound module, at some point the sound was totally not working.
Click to expand...
Click to collapse
I also have a problem with the optimising apps bug every time I reboot. Going to downgrade today. Hopefully everything will go well

liveroy said:
I had the same issue, wifi would never go sleep. RAM management is horrific and the YouTube app was causing some troubles with the sound module, at some point the sound was totally not working.
Click to expand...
Click to collapse
Actually, that's not what's happening to me... Wifi is active only when connected to a network...
Now, what you are saying is that your wifi is always on?
Did you check in the advanced wifi properties the status of the 'always on' setting?... Because if you configured the location settings to use WiFi, then WiFi will be always on, even when you manually turn it off...
So, make sure you do not have that turned on...
Enviado desde mi XT1058

SanD-82 said:
Actually, that's not what's happening to me... Wifi is active only when connected to a network...
Now, what you are saying is that your wifi is always on?
Did you check in the advanced wifi properties the status of the 'always on' setting?... Because if you configured the location settings to use WiFi, then WiFi will be always on, even when you manually turn it off...
So, make sure you do not have that turned on...
Enviado desde mi XT1058
Click to expand...
Click to collapse
That's not the case either, it was set to never keep it on during sleep and scaning always available was not allowed.The wifi just wont go off durring sleep and that's it.Tried all possible settings to no avail.Actually wifi was the 2nd highest battery consumer in the stats after the screen.This problem does not exist in 4.4.4.

I see...
It's actually hard to see how in 2015, Android keeps having these deal breaker issues...
I somehow feel that the best version of my xt1058 was when it was at 4.2.2... After the subsequent updates, bugs started to appear, and on 5.1 i got the first big issue...
Sent from my XT1058

Works!
Successfully downgraded. Thank you so much!

What would i have to be aware of in the future if i do this?
Of course, no OTA install for 5.1...
Before making any 'stock upgrade' or something **** that, i would have to flash the 5.1 full firm right?
Sent from my XT1058

SanD-82 said:
What would i have to be aware of in the future if i do this?
Of course, no OTA install for 5.1...
Before making any 'stock upgrade' or something **** that, i would have to flash the 5.1 full firm right?
Sent from my XT1058
Click to expand...
Click to collapse
Basically if you are on 4.4.4, shouldn't be any problem to update back to 5.1 even via OTA.But since the images for 5.1 are available, I wouldn't suggest OTA update anyway.
For future updates, when Android M is out for example, just update to 5.1 using fastboot, then update through the OTA.
Other than that, there are no other potential problems that might arise, at least nothing that I can think of.

IS Android 4.4.2 or 4.2.2 files avalable for indian moto x (xt1052 asian retail)
liveroy said:
Basically if you are on 4.4.4, shouldn't be any problem to update back to 5.1 even via OTA.But since the images for 5.1 are available, I wouldn't suggest OTA update anyway.
For future updates, when Android M is out for example, just update to 5.1 using fastboot, then update through the OTA.
Other than that, there are no other potential problems that might arise, at least nothing that I can think of.
Click to expand...
Click to collapse
WHere can i find those files??

visheshjotshi said:
WHere can i find those files??
Click to expand...
Click to collapse
Check the first post, the File Factory link, you can find tons of images there, the moto x 2013 is codenamed Ghost, if there is no model listed.
Good Luck.

Cant find files
File factory doesnt have files for asian retail other than android 4.4.4 file can i find it any where else?????
How many people frm india have sucessfully downgraded thier phones??

visheshjotshi said:
File factory doesnt have files for asian retail other than android 4.4.4 file can i find it any where else?????
How many people frm india have sucessfully downgraded thier phones??
Click to expand...
Click to collapse
Try searching 4pda.
Also, you don't need exactly your original firmware to begin with, it's recommended, but not necessary.

Thank you for this information. I dont have the wifi bug. But i have the mobile data bug. (Even turning it off it still continues to sap battery)
Sent from my XT1052 using XDA Free mobile app

I was looking for a post like this becouse my WiFi doesn't work on XT1058 5.1... i thought was a Lollipop related issue so wanted to downgrade to 4.4.4 and see if the problem really was related to android version, but it isn't. I downgraded successfully from 5.1 to 4.4.4 with your tutorial, but the WiFi problem persist. Now i know i'm really screwed up becouse i tried i believe everything possible... airplane mode, factory reset, cache wipe, full wipe, custom rom, custom kernel, android 5.1, android 4.4.4, different AP's and routers, delete supplicant conf... So i don't know what to do. Te specific problem is that WiFi can see available networks, but randomly some of them disappear and others show up, and when i try to connect por ex to my home network, it says "connecting" and then "saved", with all networks happens the same. Does anyone has a clue? BTW, thanks for your post!

Download the archive from this link https://app.box.com/s/idnxxhunecvtxf1mbqve0bpooyogvxng
unzip it on your device and copy the files to /persist.You need root to do that. Set the permissions to rw-r-r--- and rw-rw---- for the .bt_nv.bin
Reboot and see if something changes.

(Exynos) N910U downgrade to KitKat

Guys
I have tried to downgrade from stock MM to stock KitKat via odin for various reasons(battery,smoothness etc).
Every time it fails on bootloader step.
If anyone can provide me with kitkat bootloader and kitkat modem for the N910U it would be very helpful.
~~~N910U TGY HongKong based

If you have searched a little you probably already saw it. Unfortunately Samsung permanently blocked users from turning back to older versions of the OS since 5.1.1 Lollipop. There is no way of doing it unfortunately.

There are many a users who claim they are able to revert back from LP to KK and plenty youtubers show it.
I dont claim they are genuine but atleast one out of them would/may be genuine, so whats wrong in giving a try.
Anyways you have the files?

decron04 said:
If you have searched a little you probably already saw it. Unfortunately Samsung permanently blocked users from turning back to older versions of the OS since 5.1.1 Lollipop. There is no way of doing it unfortunately.
Click to expand...
Click to collapse
I did roll back to Kitkat in the end of July on my Note 4, when was the rollback blocked? Everything worked perfectly for me just a couple of months back

galaxyYtester said:
I did roll back to Kitkat in the end of July on my Note 4, when was the rollback blocked? Everything worked perfectly for me just a couple of months back
Click to expand...
Click to collapse
Can you share the method?
As when i try to do so it fails on the bootloader step.
I have also tried flashing the kitkat bootloader alone...still same error.

its_me_Sandy said:
Can you share the method?
As when i try to do so it fails on the bootloader step.
I have also tried flashing the kitkat bootloader alone...still same error.
Click to expand...
Click to collapse
I have the N910F, so it may be different for me (my device also shipped with Kitkat when I bought it), I got the Kitkat ROM from this thread, about 1,5 gigs:
http://forum.xda-developers.com/note-4/general/note-4-n910f-original-firmwares-t3189968
Even though at the time I had a MM or LP bootloader, the zip file only has one md5 file, and installing it worked perfectly with no errors (it probably installed a KK bootloader because, well, it booted after the installation and worked without any problems)
I don't think I can help you because you have an exynos and I have a snapdragon, but I still find the claims of Samsung making installing kitkat impossible VERY improbable, because I did it on the 26th of July this year with no errors
Edit: I digged up this guide I used, not sure if it helps but these are the steps I took and it worked for me: http://www.androidexplained.com/galaxy-note-4-how-to-downgrade-to-android-4-4-4-kitkat/

galaxyYtester said:
I have the N910F, so it may be different for me (my device also shipped with Kitkat when I bought it), I got the Kitkat ROM from this thread, about 1,5 gigs:
http://forum.xda-developers.com/note-4/general/note-4-n910f-original-firmwares-t3189968
Even though at the time I had a MM or LP bootloader, the zip file only has one md5 file, and installing it worked perfectly with no errors (it probably installed a KK bootloader because, well, it booted after the installation and worked without any problems)
I don't think I can help you because you have an exynos and I have a snapdragon, but I still find the claims of Samsung making installing kitkat impossible VERY improbable, because I did it on the 26th of July this year with no errors
Edit: I digged up this guide I used, not sure if it helps but these are the steps I took and it worked for me: http://www.androidexplained.com/galaxy-note-4-how-to-downgrade-to-android-4-4-4-kitkat/
Click to expand...
Click to collapse
Thanks for the detailed one.
i believe the issue is with snapdragon vs exynos processor, as i have followed the same procedure but iam unable to pass the sboot.bin step in odin, it fails there.
not sure on unlocking bootloader as i am rooted, tried few custom roms and kernels too, so i believe it may be unlocked.

did you try a full wipe whit TWRP, data, cache, dalvik, internal, wipe all, then install KK whit ODIN?

MatiasETirimaco said:
did you try a full wipe whit TWRP, data, cache, dalvik, internal, wipe all, then install KK whit ODIN?
Click to expand...
Click to collapse
Except for internal storage, all.

Actually you can't downgrade from stock mm to kk on n910u, your phone bl was locked when you flash 6.0 bl, but you can downgrade to 5.1 LL.
sorry for my bad English.

You are asking for the U model though. Mine is the C model. Sorry for that. However they shouldn't be that different because both have exynos soc. For the C model, you cannot turn back with odin.

decron04 said:
You are asking for the U model though. Mine is the C model. Sorry for that. However they shouldn't be that different because both have exynos soc. For the C model, you cannot turn back with odin.
Click to expand...
Click to collapse
OMG!
Really? I cannot back to KK from MM ? I have the 910c. It's already came with LP...
If I try I can kill my phone or I just will get a error message ?
Thank you!

You can't kill your phone. It just won't allow you to install the KK bootloader. Same goes for all exynos phones. Once you leave KK, there is no turning back. That's why I made sure to get a snapdragon. Sorry to be the bearer of bad news.

* G925VVRS4DQD1 * Full Odin Nougat 7.0 Firmware *

Hello!
Here is the full G925VVRS4DQD1 Odin manual update to 7.0 Nougat for everyone to enjoy. You can flash from any current version you have now it doesn't matter whether you are on 5.1.1 or 6.0.1.
https://www.androidfilehost.com/?fid=529152257862722630
If for whatever reason you want to downgrade or don't like 7.0, you can safely downgrade to any of the below versions without any issues. After you flash a lower android version using Odin, phone might get stuck on Verizon logo. If that happens, all you need to do is boot into recovery and do a factory wipe/reset and phone will boot right up after that.
G925VVRS4CQA3 (6.0.1) - https://www.androidfilehost.com/?fid=529152257862700500
G925VVRS4CPL3 (6.0.1) - https://www.androidfilehost.com/?fid=673368273298921946
G925VVRU4CPK2 (6.0.1) - https://www.androidfilehost.com/?fid=385035244224407601
G925VVRU4CPD2 (6.0.1) - https://www.androidfilehost.com/?fid=24566454284190657
G925VVRU4BOK7 (5.1.1) - https://www.androidfilehost.com/?fid=24269982087018504
G925VVRU4BOG9 (5.1.1) - https://www.androidfilehost.com/?fid=24052804347845467

Thanks a lot! I downloaded one from sammobile but there was one only one file, modified date 4/07...
I notice the files within the zip from your link mention REV02 and are dated 4/26.
G925V_G925VVRS4DQD1_VZW_USA_v7.0_IMEIAUTHORITY.COM.zip
2.54 GB (2,732,088,886 bytes)
MD5: 145a137d2c639b30ef5addac9094f331
I have attached the results from HashMyFiles for the 4 within the archive (Filename, MD5, SHA1, CRC32, SHA-256, SHA-512, SHA-384, Modified Time, File Size).

@toutanje Out of curiosity, how did you determine which builds you can safely downgrade to from 7.0? Is it something you personally tested or did someone recently go through the hard work and post their results somewhere? BTW, you can now add G925VVRS4CQA3 (6.0.1) - https://www.androidfilehost.com/?fid=529152257862700500 as two people have confirmed downgrade success here: https://forum.xda-developers.com/verizon-galaxy-s6-edge/help/downgrading-nougat-t3601096 . One used firmware from sammobile and the other directly from the link above. This is the very last build available for Marshmallow.

Hi there. I installed the new update on my s6 edge 7.0 via verizon software updating tool.am noticing the sound quality of mt s6 edge has been changed.before the sound quality was thick and now its not that thick anymore.i want to bring back the thick quality sound on my s6 edge.there is setting called sound quality and effects but i cant manage to get back that sound quality i had with 6.0. Is there anyone who able to notice this change in the sound?

blkt said:
@toutanje Out of curiosity, how did you determine which builds you can safely downgrade to from 7.0? Is it something you personally tested or did someone recently go through the hard work and post their results somewhere? BTW, you can now add G925VVRS4CQA3 (6.0.1) - https://www.androidfilehost.com/?fid=529152257862700500 as two people have confirmed downgrade success here: https://forum.xda-developers.com/verizon-galaxy-s6-edge/help/downgrading-nougat-t3601096 . One used firmware from sammobile and the other directly from the link above. This is the very last build available for Marshmallow.
Click to expand...
Click to collapse
With a very a simple observation, no testing or anything needed
G925VVRS4DQD1 <-- you see the 4 towards the end of firmware build? That is the revision bit number. This means you can flash ANY firmware for that model with a 4 or higher. Take this 5.1.1 firmware for example ---> G925VVRU3BOG5. Even though this firmware is also 5.1.1 like the ones from above, this particular one will NOT work because it is on an older firmware revision bit (3).
The same is true and goes for ALL Samsung phone/tablet models and firmwares.

toutanje said:
With a very a simple observation, no testing or anything needed
G925VVRS4DQD1 <-- you see the 4 towards the end of firmware build? That is the revision bit number. This means you can flash ANY firmware for that model with a 4 or higher. Take this 5.1.1 firmware for example ---> G925VVRU3BOG5. Even though this firmware is also 5.1.1 like the ones from above, this particular one will NOT work because it is on an older firmware revision bit (3).
The same is true and goes for ALL Samsung phone/tablet models and firmwares.
Click to expand...
Click to collapse
That is very good to know. Yeah I noticed it about the firmware naming convention but I had no idea what the value means (or the character before revision bit, U has become S). My phone out of the box was on G925VVRU3BOG5, so I guess I could go all the way back to G925VVRU4BOG7 if "needed" lol.
One of my fears about Nougat is about all the work they did to automate and place updates into the background. This could allow disabling of downgrades, or anything else at the discretion of Samsung and/or the carrier. I think this has already been done in Marshmallow, just on a smaller scale for security fixes. Anyway, it seems to me like an attack vector waiting to happen: less control over my phone combined with an easy way to break things. Imagine all the troubleshooting fun we will have.

So I upgraded to nougat. I'm having battery issues and just want to go back to marshmallow. but I'm having problems. The nougat rom installs just fine with odin. But when I try with any of the 6.0.1 roms it was failing. Then I noticed that re-partition was chcekd. So I unchecked it and now it goes through the process just fine. But now the complains with dm-verity verification failed. I can install nougat on it no problem. It's just the downgrade that's not working... any clues?

toutanje said:
With a very a simple observation, no testing or anything needed
G925VVRS4DQD1 <-- you see the 4 towards the end of firmware build? That is the revision bit number. This means you can flash ANY firmware for that model with a 4 or higher. Take this 5.1.1 firmware for example ---> G925VVRU3BOG5. Even though this firmware is also 5.1.1 like the ones from above, this particular one will NOT work because it is on an older firmware revision bit (3).
The same is true and goes for ALL Samsung phone/tablet models and firmwares.
Click to expand...
Click to collapse
I actually managed to get the N925V to downgrade all the way back to the firmware version G925VVRU3BOG5.. May have cost some money for some very specific files but my phone's back on G925VVRU3BOG5 and it's really only a test phone for someone I do work for! I have it rooted with SuperSU and not kingroot and I created a script to keep the phone set to "permissive" so it's able to do full reboots and not just hot reboots using xposed... Unfortunately it seemed like no one cared about it when I posted it in the other thread so it's probably not worth it to a lot of people but I think it is with the amount of fine tuning I did to get it to where it is today!!

MrMike2182 said:
I actually managed to get the N925V to downgrade all the way back to the firmware version G925VVRU3BOG5.. May have cost some money for some very specific files but my phone's back on G925VVRU3BOG5 and it's really only a test phone for someone I do work for! I have it rooted with SuperSU and not kingroot and I created a script to keep the phone set to "permissive" so it's able to do full reboots and not just hot reboots using xposed... Unfortunately it seemed like no one cared about it when I posted it in the other thread so it's probably not worth it to a lot of people but I think it is with the amount of fine tuning I did to get it to where it is today!!
Click to expand...
Click to collapse
Mike! Can you explain how you did it? I'm stuck on nougat. Every time I try to downgrade, I get the dm verity error. I've tried all the 6.0.1 version and the 5.0.1. No luck . I'm back on nougat. Can you please let us know your process... Thanks!
Did you have to select anything special in the options? I just left it at default which is Auto reboot & F. Reset Time.

strandedhuman said:
Mike! Can you explain how you did it? I'm stuck on nougat. Every time I try to downgrade, I get the dm verity error. I've tried all the 6.0.1 version and the 5.0.1. No luck . I'm back on nougat. Can you please let us know your process... Thanks!
Did you have to select anything special in the options? I just left it at default which is Auto reboot & F. Reset Time.
Click to expand...
Click to collapse
I mean I could but I had to shell out some money for this firmware and I don't even know if you can flash it with odin because I don't use odin I bought a box to do my flashing since I work on so many phone's and odin just doesn't cut it.

No Worries. Finally figured it out. Good luck to you
MrMike2182 said:
I mean I could but I had to shell out some money for this firmware and I don't even know if you can flash it with odin because I don't use odin I bought a box to do my flashing since I work on so many phone's and odin just doesn't cut it.
Click to expand...
Click to collapse

I was able to use this to flash my Samsung Galaxy S6 Edge from 5.1.1 to 7.0.
Not that I want to upgrade again, but is there a 7.1.2 available? Is there a routine schedule for that sort of thing or was the 7.0 Nougat think kind of a special case?
Thanks!
--
Furry cows moo and decompress.

WyrdWyrd said:
I was able to use this to flash my Samsung Galaxy S6 Edge from 5.1.1 to 7.0.
Not that I want to upgrade again, but is there a 7.1.2 available? Is there a routine schedule for that sort of thing or was the 7.0 Nougat think kind of a special case?
Click to expand...
Click to collapse
I haven't been keeping up, but now curious. Verizon shows DQH1 as current (a 7.0 build), while sammobile and androidfilehost show four builds available (all 7.0).

Ok, so I updated my G925V with nougat, now I'm just wondering if anyone has come out with a way to root this build? That's what I'm waiting for. Plz fill me in when that happens. Thanks.

MrMike2182 said:
I mean I could but I had to shell out some money for this firmware and I don't even know if you can flash it with odin because I don't use odin I bought a box to do my flashing since I work on so many phone's and odin just doesn't cut it.
Click to expand...
Click to collapse
I've been wanting to get one too. Which box plus tool do you use?

Delgoth said:
I've been wanting to get one too. Which box plus tool do you use?
Click to expand...
Click to collapse
I use the Z3x box and Octoplus box I have 2 of them for different phone makers but I have so many different wire connectors that I lost count because what works on Samsung doesn't work on LG, HTC etc etc.. You can find them pretty cheap but I'd avoid buying from eBay because of to many scams selling broken or bad boxes that can't be activated.
Team Z3x .com

MrMike2182 said:
I use the Z3x box and Octoplus box I have 2 of them for different phone makers but I have so many different wire connectors that I lost count because what works on Samsung doesn't work on LG, HTC etc etc.. You can find them pretty cheap but I'd avoid buying from eBay because of to many scams selling broken or bad boxes that can't be activated.
Team Z3x .com
Click to expand...
Click to collapse
was this the only way to downgrade? im on 6.0.1 and im not able to downgrade to 5.1.1 for root lol

raven213 said:
was this the only way to downgrade? im on 6.0.1 and im not able to downgrade to 5.1.1 for root lol
Click to expand...
Click to collapse
You unfortunately cannot downgrade the bootloader once you updated to 6.0.1 you lost the ability to go back and there's so far, no way possible to do it.

Downgrade 4.1.3 to 4.1.1 (and beyond)

Hi all,
I am having issues with my Bluetooth and GSM. I am considering trying to downgrade from OOS 4.1.3 to 4.1.1. I am completely stock, not rooted and don't even have TWRP.
Would appreciate some clarification to the following questions:
1) Can I downgrade by just flashing the official full 4.1.1 zip found in OP website?
2) Should I only flash the modem zip? And if so, can I use 4.1.1 modem while having 4.1.3 installed?
3) Since 4.1.1 already has nougat 7.1.1, is 1) also safe for further downgrades, for example, directly to 4.0.4?
Thanks.
Best regards,
Oldiamond

If your bootloader is locked, you can't downgrade (unless you exploit the security vulnerability from a few weeks back).
If your bootloader is unlocked, use TWRP or fastboot to clean flash whatever version of OOS you want.

You should consider flashing the latest open beta release, I think it's already fixed over there plus there are some Extra goodies and its stable as ****

Anova's Origin said:
If your bootloader is locked, you can't downgrade (unless you exploit the security vulnerability from a few weeks back).
If your bootloader is unlocked, use TWRP or fastboot to clean flash whatever version of OOS you want.
Click to expand...
Click to collapse
Pharrax said:
You should consider flashing the latest open beta release, I think it's already fixed over there plus there are some Extra goodies and its stable as ****
Click to expand...
Click to collapse
Thanks to both. I am this close to send it back to RMA, as I did not install anything other than 4.1.3, and didn't even unroot it. I don't know... perhaps by sending it back without ever installing TWRP or unlocking anything would provide more feedback to the manufacturer, other than saying "damn guy, started fiddling with the phone and ROMs, and here's the result".
Regarding the beta, I initially considered avoiding it because i read in the forums about issues such as sometimes alarms not ringing. I figure that my boss wouldn't like that
Going back from BETA to regular version also requires TWRP?
Best regards,
Old

oldiamond said:
Thanks to both. I am this close to send it back to RMA, as I did not install anything other than 4.1.3, and didn't even unroot it. I don't know... perhaps by sending it back without ever installing TWRP or unlocking anything would provide more feedback to the manufacturer, other than saying "damn guy, started fiddling with the phone and ROMs, and here's the result".
Regarding the beta, I initially considered avoiding it because i read in the forums about issues such as sometimes alarms not ringing. I figure that my boss wouldn't like that
Going back from BETA to regular version also requires TWRP?
Best regards,
Old
Click to expand...
Click to collapse
Alarm issues were fixed, also it never happened to me I and I've been on beta a long time i think on the official page there are the steps to switch between stable and beta. I don't think it requires twrp but don't take my word for it.

Update OP3 from 3.1.2 to OOS 5.0.1 (process and files required)

Hi guys, I have a OP3 which is running on 3.1.2 Marshmallow.
I always get a notification for system update to 4.5.1. I've tried downloading and installing the update but after the first boot my OP crashes/gets bricked. There is only a Linux penguin logo that appears no matter what button you press.
From there I always have to follow the mega unbrick guide and get my phone back to working with stock recovery and 3.1.2.
I've tried side loading the downloaded file as well.
Then I've tried installing .zip file of 5.0.1 via TWRP, still no luck. it still bricks my phone.
Am comfortable rooting my phone, my bootloader is unlocked. I don't care too much about keeping root after updating my phone to the latest version, I would be grateful to anyone who can point me towards the proper full ROM files of 5.0.1 along with any firmware files that may be required.
And the exact process of when to flash the firmware and with/without which version of TWRP. I am ready to completely wipe and clear data.
in simple words I just want to update from 3.1.2 to 5.0.1. The simple downloading and updateing from the OTA update doesn't work.

AbhiM7 said:
Hi guys, I have a OP3 which is running on 3.1.2 Marshmallow.
I always get a notification for system update to 4.5.1. I've tried downloading and installing the update but after the first boot my OP crashes/gets bricked. There is only a Linux penguin logo that appears no matter what button you press.
From there I always have to follow the mega unbrick guide and get my phone back to working with stock recovery and 3.1.2.
I've tried side loading the downloaded file as well.
Then I've tried installing .zip file of 5.0.1 via TWRP, still no luck. it still bricks my phone.
Am comfortable rooting my phone, my bootloader is unlocked. I don't care too much about keeping root after updating my phone to the latest version, I would be grateful to anyone who can point me towards the proper full ROM files of 5.0.1 along with any firmware files that may be required.
And the exact process of when to flash the firmware and with/without which version of TWRP. I am ready to completely wipe and clear data.
in simple words I just want to update from 3.1.2 to 5.0.1. The simple downloading and updateing from the OTA update doesn't work.
Click to expand...
Click to collapse
Try this: https://downloads.oneplus.com/oneplus-3/oneplus_3_oxygenos_5.0.1/

hellcat50 said:
Try this: https://downloads.oneplus.com/oneplus-3/oneplus_3_oxygenos_5.0.1/
Click to expand...
Click to collapse
Hi, I've already downloaded this very stable file and tried flashing using TWRP

AbhiM7 said:
Hi, I've already downloaded this very stable file and tried flashing using TWRP
Click to expand...
Click to collapse
I read something about wrong batteries causing this problem. Do you use the original battery?

hellcat50 said:
I read something about wrong batteries causing this problem. Do you use the original battery?
Click to expand...
Click to collapse
I though of running a diagnosis check by dialing *#808# and looked up Charger option, it shows the battery as "itech_3000mah"
is that original?
I had given the phone to repair for water damage to a professional service chain (Not OnePlus, some company here called Yaantra). I've heard from talking to an official repair person of OnePlus that fake batteries are not possible for OnePlus.
The battery works absolutely alright, charges up nicely and I get decent SOT. Can't complain at all.