Oneplus 3T Bootloader - OnePlus 3T Questions & Answers

I have a oneplus 3t. recently got the pie upgrade, and since then, the phone started behaving strangely. calls getting mute on their own, loudspeaker coming on during calls on its own, lag in a lot of apps, and so many more such issues.
there were absolutely no issues in oreo, so I looked up online and decided to go back to oreo. after reading a lot about it, i unlocked my bootloader, and tried to flash the oneplus oreo installation package, but what happened was, my phone got wiped clean, and pie was installed again, with my bootloader open.
thankfully, I had a backup of everything, so i was able to get back the things. But then, now whenever I'm restarting or switching on my phone, there's a message saying, your bootloader is open, and your phone cannot be trusted. Also, google and some more apps have almost frozen. Play store is not opening, i'm not able to add new google accounts, uber doesn't work, gmail has stopped, banking apps don't work, and so forth.
I want to go back to normal, when things weren't so jumbled. Perhaps Pie would be okay, or if I could go back to Oreo, that would be fantastic.
I am a complete novice when it comes to things like rooting, bootloader, TWRP, etc. Been reading about these but haven't really understood what they are. So please respond in layman's language. Thanks!

Apps misbehaving might be caused by the problems you experienced, or possibly by restoring the backup (if the backup read from Oreo, if you restored data for system apps, etc). Whenever I experience issues as described I do a full wipe and start clean...
Banking apps are likely not working because of the unlocked bootloader (they see it as your device not being secure). Solution would be to lock it again, or install Magisk to hide the bootloader state. Resources on that:
https://topjohnwu.github.io/Magisk/
https://www.didgeridoohan.com/magisk
The message at boot, about the bootloader being unlocked, is perfectly normal and can be ignored.
Personally I've abandoned OxygenOS, since I don't really like how it has evolved. There are many good custom ROMs available to choose from instead:
https://forum.xda-developers.com/oneplus-3t/how-to/info-list-oreo-roms-kernels-available-3-t3688139

Related

[Q] Android Process FCs and General Device Instability After Flashing MMB29V

Hello all. Generally I've been able to troubleshoot all my Android issues on my own. Most of the time someone has had the same problem (amirite?!). However, I'm stumped and could use a little help from the community.
I've been going along on Marshmallow with FK as my kernel. Generally, waiting a bit to take an update til SuperSU was confirmed all working correctly and that there wasn't any surprises. I had been putting off the MMB29V update for a bit just because everything was running fine and I had no real reason to upgrade. Well, one day I started getting a few FCs and things seemed a bit off performance wise so I decided that I'd go and move on to the next release.
Now, since I've had my N6 I really haven't had the need to run a custom ROM which is completely unlike my old habits on the S3. I decided that it's been a while since I've checked out AOSP so I flashed MMB29V using the batch file with no issues and then DU and their recommended GApps. Here's the first hint of an issue. When I loaded up the OS for the first time I got acore and phone FC's constantly. I instantly thought that I didn't wipe something or that I had a bad zip. I re-downloaded everything and checked MD5s. Everything looked good and after the flash I was able to get through the setup wizard without any issues. As I was sitting there checking out the tweaks and options available I started getting FCs again. It seemed related to Google apps. I did the whole process a second time and still had the same issues. Basically it seemed like at some random point in time the FCs would come and then shortly after the device would be highly unstable. I'd get random reboots, etc. Looking at the stack traces the errors seemed like odd NPEs and native errors.
I decided that AOSP wasn't going to cut it right now if I was going to have a relatively unstable phone and went to flash completely back to stock. Much to my surprise I still got the same errors! Apps like Feedly would never even be able to open. They would just FC on launch. The device hot reboots. The phone process seems to crash during most calls. I triple checked my MD5 on the download from Google. Made sure I wasn't doing something super stupid. I even tried doing the factory flash, booting to the welcome screen, then powering down, going to stock recovery, and factory resetting before continuing. All the same errors.
I've flashed back to complete stock a few times before without any issues. I've been able to flash system.img without any issues. Now it seems like the phone is completely unstable no matter what I do. I get the "Your device is corrupt. It can't be trusted and may not work properly." (red) message when doing a cold boot.
So... What gives? Am I completely blanking on a step here? Is it possible that I have a hardware issue that is corrupting stuff (I've suffered a bad DIMM before in a desktop and it was mind numbingly frustrating)?
I've burned through two backup cards of Google 2-Step backup codes! I'd really like to figure this one out!
mikejr83 said:
.
So... What gives? Am I completely blanking on a step here? Is it possible that I have a hardware issue that is corrupting stuff (I've suffered a bad DIMM before in a desktop and it was mind numbingly frustrating)?!
Click to expand...
Click to collapse
You could read the OP of the following thread and flash a debloated and prerooted ROM.
http://forum.xda-developers.com/showthread.php?t=3059493
I guess I'll try that. I'm still scratching my head why a flash from the factory image is still suffering from FC's and general instability. It also concerns me that I get the corrupted message at boot. It would be one thing if I flashed factory, then put a recovery, kernel, and rooted, but I haven't done that.
Hopefully I'll get a chance to try that this evening. Thanks for the link to that image. It's pretty much what I run when I take an update.
N, n, ne, necromancy!
I brought this thread back to life because I've never been able to solve the instability issues since my last post back in March.
Having some free time lately I decided to nuke my device and start again. I first grabbed the latest stock image and flashed stock. Then I downloaded the latest TWRP and Dirty Unicorns and decided that I'd give it a whirl again. I had FC issues right after the first go at it. I decided to try another GAPPs and do it again. I was able to get through setup. It took a few hours but the FCs started again.
I decided that I would try factory resetting the device and then starting a setup. I remembered that on my previous devices that I sometimes would have to do an immediate factory reset after flashing.
Well that did crap. FCs are random. The device is stuck booting now after a hot reboot.
How can I debug this? What do I need to grab from a logcat? Is there a way to run something like memtest to see if there is a bad section of RAM and something against storage to see if there is a bad sector?
This is frustrating as hell!

New OP3T not restoring from Nexus 5X

Got my new 3T two days ago. It's a beautiful phone. I am replacing my currently not-bootlooping Nexus 5X.
I have spent nearly 10 hours trying to get this phone restored from my existing phone. NOTHING IS WORKING - AT ALL!
Originally I unlocked bootloader and rooted using TWRP and SuperSU (using the toolkit from XDA). All seemed to work.
First bootup asked about activating location services in a popup window - said something about 'in a previous version of android this was disabled' So I activated it.
I attempted to do the initial setup - only the basic information was transferred (and I think that came via providing my Google Account info).
Tap & Go would connect and then finish in a matter of seconds and It says nothing to restore.
I input wifi info.
I input my google account information.
I attempted to use Tap & Go from Nexus 5. It only transferred my email address and a few settings. No apps, nothing else.
I have since restored via TWRP recovery, restored using factory recovery image, etc. I've wiped data a multitude of times. I am now locked and not rooted and I should be with OnePlus stock recovery and OS.
I rebooted and it always has a message that says that 'in a previous version of Android location services were disabled' and do I want to activate them.
It asks me for my Language, whether I wanted to restore from a device, etc. The Tap & Gp transfers nothing. I have manually used the Nexus 5x "prepare a new device' and when the restore starts it stops almost immediately with nothing transferred.
I have activated Developer Options and also did and "adb backup -apk -shared -all -f name.ab" from Nexus 5X and a "restore name.ab" on the OP3T. It did move some of my pictures. None of my apps, none of my app data, etc.
When I got my Nexus 5x it was able to restore from a google backup from a broken Moto X via Google Drive Backup. It brought over apps, settings, screen setup, etc. All I had to do was put pictures and music back on. I can see the Nexus 5X backup in Google Drive, but the OP3T doesn't see it or want to use it... or even ask to restore from it.
This shouldn't be this difficult. Does it have something to do with Oxygen vs Vanilla?
I basically decided that I wouldn't unlock and root since Google won't let you use android pay (and probably other things in the future) if it's "not secure".
I'm willing to try just about anything! I appreciate any help!
I don't have any real help for you, sorry... But I just wanted to let you know it's perfectly possible to restore from a previous device.
I did it 2 days ago when I switched from my Nexus 6.
First thing I did was to unlock the bootloader, install TWRP and root (Magisk). I then update to OOS 4.1.1 and did a factory reset in TWRP (to start the initial setup again). After that, all I had to do was to choose "Restore from the cloud" and choose my Nexus 6 in the list during the initial setup.
I figured out part of it. my 5X was on Android 7.1, the OP3T was on 7.0, so when I forced OP3T to 7.1 everything started restoring.
Only problem is that I unlocked bootloader in the process. I have since relocked and restored factory recovery and 7.1.1 but now I get the stupid DM_Verity warning and I can't get it reset no matter what I do.

UI Lag

Hello Guys, I would like to confront a problem I encountered during my time with this phone.
I bought it a week ago and I unlocked the bootloader right away and then rooted it via magisk.
The phone UI felt quite laggy since the first time I used it. I come from a Oneplus 3.
All the reviews state that the experience with this phone is snappy, but it is much slower than my (now dead) OP3, so I need to check in to know if it's a placebo effect or if it's true.
Scrolling through nova launcher drawer is slower, pulling up the notification shade often lags a lot, scrolling through reddit stutters.
I'm on the V9.6.10.0.ODIMIFE version.
I tried reinstalling everythin from scratch, by further unlocking the system with "fastboot flashing unlock_critical" and then using Mi Flash Tool to install the rom found in this OTA dump thread.
I tried doing an antutu benchmark that returned a value of 113000, instead of the expected 130000 or so.
I checked some parameters via kernel adiutor and it all seemed in order (frequencies, schedulers and such).
The phone is original (as confirmed by xiaomi's site).
Please tell me this is software related since this is a new device and that it will be solved.
Edit: better english, added some detail.
Flash again everything to stock, don't root...and don't do an restore backup that google will offer you when you first boot your newly fresh phone.
Install and setup everything again manually, and then test your phone for a day.
I think that you messed up something with root, I did the same, and only fresh new install with manual setup and install of apps step by step fixed the problem.
minnuss said:
Flash again everything to stock, don't root...and don't do an restore backup that google will offer you when you first boot your newly fresh phone.
Install and setup everything again manually, and then test your phone for a day.
I think that you messed up something with root, I did the same, and only fresh new install with manual setup and install of apps step by step fixed the problem.
Click to expand...
Click to collapse
Than you for your answer.
I should have probably mentioned that I chose the option " configure the phone as new", as I always do.
This leaves out the root part. Is it really that taxing? It never occurred to my with my previous phones.
I can try it and do without root for a day, but not much longer.
heavp said:
Than you for your answer.
I should have probably mentioned that I chose the option " configure the phone as new", as I always do.
This leaves out the root part. Is it really that taxing? It never occurred to my with my previous phones.
I can try it and do without root for a day, but not much longer.
Click to expand...
Click to collapse
It's fluid here with root so I doubt that changes anything
minnuss said:
I think that you messed up something with root
Click to expand...
Click to collapse
Just to clarify myself here, I did not meant that root can do something to phone it self, but the user when he is overplaying with the phone, like I did, and some app triggered something and made my phone buggy.
And, I don't use other launchers, I always use the default one that came with the phone itself, because I would always feel that "laggines" with custom launchers.
On Huawei for example, I would try google launcher, but it would lag, so I would get used to default one...
And yeah, here is also super fluid experiance so far with Mi A2.
minnuss said:
Just to clarify myself here, I did not meant that root can do something to phone it self, but the user when he is overplaying with the phone, like I did, and some app triggered something and made my phone buggy.
And, I don't use other launchers, I always use the default one that came with the phone itself, because I would always feel that "laggines" with custom launchers.
On Huawei for example, I would try google launcher, but it would lag, so I would get used to default one...
And yeah, here is also super fluid experiance so far with Mi A2.
Click to expand...
Click to collapse
I just tried flashing again with mi flash tool, I'm not rooted and I'm using the default launcher.
Pulling down the notification shade is still a pain.
I guess that I'll just wait for a working twrp and for custom ROMs.
heavp said:
I just tried flashing again with mi flash tool, I'm not rooted and I'm using the default launcher.
Pulling down the notification shade is still a pain.
I guess that I'll just wait for a working twrp and for custom ROMs.
Click to expand...
Click to collapse
It just follows my finger as fast as I can move them. Something is fishy on your device
Go to TWRP and erase dalvik, and try another source of stock ROM download, maybe something is wrong with that.
And flash all via fastboot like this
https://forum.xda-developers.com/showpost.php?p=77302899&postcount=4
The stock rom, extract images...
http://en.miui.com/download-353.html

OTA update endless fail loop PPWS29.69-39-6-4 on Magisk (un)rooted X4

I have two (identical) X4 1900-1 Android One phones , both were rooted with Magisk patched boot image on PPWS29.69-39-6-2. I was able to restore boot image with Magisk Manager on one and the January 1 PPWS29.69-39-6-4 OTA update completed successfully, I reinstalled Magisk per tutorial, root is present and Safetynet passed. The other one became stuck in a kind of updating loop for this OTA prior to restoring the image with Magisk, the update failed on "Step 3 of 6", then starts all over again, ad infinitum, causing battery drain and slowdown. It started this before I restored the boot image with Magisk but fail is continuing since doing so and after a reboot. Automatic updates were turned off in Developer Options, but it still tried to install the update before notifying me that it was available. One difference after restoring boot image with Magisk is that the phone is no longer showing the update progress page--when you tap System Updates the CHecking for Updates flashes briefly and then a toast says Software Update Unsuccessful. That message comes up every few seconds.
My past experience with failed OTA updates on other devices has been the update process stops with one failed update, never tries again and I had to flash manually. Wondering about the best way to address this issue is. One of these phones is my "backup" device, so I have some wiggle room on what to do. Should I (a) flash stock back on the problem phone and let it go through the several security updates, or could I possibly restore a TWRP backup from the updated phone on the problem one? I did a similar restore years ago from one Moto XT926 to another and it worked, but I believe the restored phone might have acquired the serial # of the donor.
I took logcats before and after unrooting, but had trouble uploading one of them. I'll try again.
I spoke a little too soon on the one that "successfully" updated. It is unable to complete phone calls with the same SIM that works in the one that keeps giving the failed update message. Calls just end as soon as send is pressed, or hang trying to connect. In Settings it shows the correct phone number etc., network settings are same as the working phone and this one worked with this SIM a few weeks ago. Some problems connecting to computer visa wifi as well. Beginning to wonder if this is a bad update? Could really use some help here as I don't have a fully functional phone now.
Turns out the "successfully" updated phone is pretty borked. Lots of strange behavior and black screen freezes. The modem/radio seem to have major problems. With no sim card in the phone, the LTE icon shows and indicates signal, but no connectivity. Freezes and blank screens when I hop around in Settings. Wifi connect is wonky. And no phone connectivity with SIM. Looking like I'm gonna have to go back to stock with PPWS29.69-39-6-2, the latest full FW I have.
Has anyone out there had problems with this OTA?
Where can I find the log file from the OTA update, to try and see what went bad?
On the "failed" phone, I was able to find the url for the OTA update (Blur_Version.29.461.4-29.481.10.payton_fi.google_fi.en.US.zip -- PPWS29.69-39-6-4) on the logcat and download it. I've uploaded it to Drive and here is the link is below if anyone needs it. There are lot of error and suspicious messages in one of the logcats from the failed one but interpreting them meaningfully is above my paygrade. I've attached another log to this post. Can someone tell me how to stop the endless updater loop until I can fix the other phone? I am unsure what app/service to disable. I read somewhere there is a way to delay updates on Pie, but it doesn't appear to be a toggle anywhere in Settings.
This is the Android One/Google Fi variant XT1900-1. Flash at own risk!
https://drive.google.com/open?id=151TRLKfmlROCT6f--U4PWRPqmkFyD0T9
The option to force updates is in Developer Options about 10 lines down.
Apparently it defaults to ON.
I have not tested that this would prevent updates since I leave it on, since I want updates.
Force Updates
KrisM22 said:
The option to force updates is in Developer Options about 10 lines down.
Apparently it defaults to ON.
I have not tested that this would prevent updates since I leave it on, since I want updates.
Click to expand...
Click to collapse
Thanks , however that option was turned OFF in Developer Options. Update still forced itself on both phones.
Oh well! It's all google's fault!
Back to stock working so far
KrisM22 said:
Oh well! It's all google's fault!
Click to expand...
Click to collapse
Appears so. Keep reading.
I flashed stock PPWS29.69-39-6-2 and so far things seem to be working--phone, data, wifi.
I'll give a full update on functionality and de-borking when the thing's finished its updates and app installs.
I did notice that in device setup, in the Google Terms the last item "Install updates and apps", states "This device may automatically download and install updates and apps from Google and your device manufacturer...." and there is no on/off toggle!!!! You are forced to accept this "setting", the only option is "Accept"!
Thanks again Google.
I suppose this means that the Developer Options setting is moot.
I would be interested to know if this "(it's not a bug it's a) Feature" is present in Oreo builds?
Remember that google doesn't write android so we can modify it - in fact, google goes WAY out of its way to prevent that - that is why there are so many releases of things like Majisk - google keeps blocking them.
Only a tiny tiny fraction of Moto X4 users attempt any modification of their phones.
You might succeed because you have not yet flashed a custom ROM and thus changed the bootloader and file system from the stock OTA'ed Pie setup. Those that have cannot return. Apparently ever.
KrisM22, would you say that the X4 is a less suitable device than others for rooting? And BTW appreciate your noob warnings, only wish they had appeared sooner. I had already rooted these earlier.
As a matter of practice, I never flash custom ROM or recovery on devices until after they've reached end of OEM support. Actually with the ability to boot TWRP via fastboot I don't see any advantage to installing it but numerous disadvantages. I have unlocked and rooted all my (unlockable) devices, but I may rethink that in light of these recent Android changes. For my next phone I would probably choose a more mod-friendly OEM, if such exists. One+ maybe?
a) you're welcome
b) don't mod this X4 in any way if you are OTA upgraded to Pie.
You might have been able to modify it if it was still on 7 or 8 but I have no idea what the devs are using for
1) bootloader
2)file structiure.
I think, if you have to root, go back to something like a G3, where the bootloader didn't change and the file structure didn't change. Even the Z play had probs around the Oreo bootloader change, but we still could use rsdlite to get back from most disasters.
iow, think pre/pre Treble in any form. It may be, in a couple more years, when Treble has stabilized, that we can get away with modifying things, but on a current phone I would avoid it, UNLESS others have already successfully/repeatedly done it.
I also feel that most of the reason for flashing a custom ROM are gone. People get there, spend a lot of time playing with updates and releases, and eventually go back to stock. There are always a few exceptions, but... As to the various reasons for "needing" root, I feel there are always alternatives. I use Block This! to keep ads out of Brave, BBC app, and APNews app. While there are occasions like can't-edit-build prop, I find I can live without it. It is an adjustment of attitude/expectation. Yes, I have had tons of fun and wasted tons of hours playing with my past phones, it happens I haven't missed it with this one, especially since the sec updates are so recent - I don't worry until it's a year or 2 past.
Once the X4 is on Pie stock, do not modify it in any way.
As to other phones, yes, if you really have to modify it, search the wealth of info that is XDA until you have found a phone that folks have been able to repeatedly get back to stock - be on the lookout for a trail of endless posts about bricked phones and blank flash stuff - a sure sign to avoid it. - This forum is littered with them!
If you have modified a phone: BEFORE taking an OTA, flash phone with latest stock, then let it take the OTA. I had to modify that - I have no idea if you can flash this thing once it is on Pie.
I also feel that most of the reason for flashing a custom ROM are gone.
Click to expand...
Click to collapse
I agree, especially for current devices that are still supported. I'll leave these stock at least until that ends. I actually though it had already reached EOS, so I was caught with my pants down. That said, these phones ran just as well stock/rooted as all of their predecessors I have owned, and as well as when unrooted--until the update fail happened. I may root one if I decide to keep using it beyond EOS. And it's true that most custom ROMs are rarely as smooth and reliable as factory.
Yes, I have had tons of fun and wasted tons of hours playing with my past phones
Click to expand...
Click to collapse
True Dat! But, a hobby is a hobby, and not everything hobbyists do in any field turns out stellar. One reason I always try to have have a decent running backup phone if I mess with a daily driver.
With an EOS device, the risk of a bad outcome is to a large degree mitgated by the greatly diminished value of the device. I have a Moto X 2015 Clark that I've been playing with Randomblame's LOS16 builds on, and it is very usable. Too bad that phone never had good battery life, I liked everything else about it. Might as well keep it rather than sell it for the maybe 50 bucks it might bring. Hell, I only cut my last XT926 loose early last year!
Everything's looking good. After flashing back to stock PPWS29.69-39-6-2, Phone updated OTA to PPWS29.69-39-6-4 and everything appears to be working well. So far no bad residue from past rooting etc.
redwoodie said:
Everything's looking good. After flashing back to stock PPWS29.69-39-6-2, Phone updated OTA to PPWS29.69-39-6-4 and everything appears to be working well. So far no bad residue from past rooting etc.
Click to expand...
Click to collapse
EXCELLENT!!! Great to hear!
Yes, always have a backup!!!
EOS: I was surprised by this update and am now guessing that we might even get one in Mar or Apr. We'll just have to see if that includes 10. But to me a phone is not really "EOS" until maybe a year or 2 after it stops getting updates. I haven't heard of anyone getting hacked. On any phone.
Great!!!
If you are willing, could you do a couple things:
Go to first post edit, go advanced and mark thread as SOLVED.
add a post about how you did it:
1) disclaimer: "Do at your own risk. I am not responsible for anything." or some such!
2. a sentence or 2 about how you did the flash.
3. attach a copy of the bat file you used for the flash.
I think only works if you haven't changed bootloader or file system - NO custom ROM.
Thanks!
Post issue solved etc.
I will happily do that once I've gotten the second X4 straightened out, at that point I'll feel confident it is really "solved".. Probably next week at soonest, I have a minor medical procedure today. I didn't use a .bat file, I fastboot flashed each .img, erase and sparsechunk the old school way. There was a flashall.bat I found on XDA but it was for Oreo builds, had a couple lines in it I was unsure about, and wasn't comfortable modifying it.
Many thanks! Hope all goes well with that today!
If you could provide a log, or list of commands used, that would help!
Update on flashing 2nd X4 back to stock...Flashed PPWS29.69-39-6-2 twice same results: I have wifi/LTE connectivity issues, the wifi constantly connects and disconnects and phone/LTE tries and fails.
There are a couple of threads that discuss similar probles with the X4 and offer various solutions. I may try those, or going back to original Moto Pie ROM or an intermediate build. I also was able to grab the latest Jan. 1 update ROM and that's another option.
The odd thing about this flash is that everything about the phone state was 100% identical to the other X4 that I successfully restored via exact same methods. It would appear that "your mileage may vary" applies. I'll update again when I have new info.
redwoodie said:
Update on flashing 2nd X4 back to stock...Flashed PPWS29.69-39-6-2 twice same results: I have wifi/LTE connectivity issues, the wifi constantly connects and disconnects and phone/LTE tries and fails.
There are a couple of threads that discuss similar probles with the X4 and offer various solutions. I may try those, or going back to original Moto Pie ROM or an intermediate build. I also was able to grab the latest Jan. 1 update ROM and that's another option.
The odd thing about this flash is that everything about the phone state was 100% identical to the other X4 that I successfully restored via exact same methods. It would appear that "your mileage may vary" applies. I'll update again when I have new info.
Click to expand...
Click to collapse
Thanks. modem problems? Dunno... Keep us posted! Thanks!
Are your two One fi, or regular - I bet the motherboards on the two are different, thus the different result.
Both One/Fi. Same baseband versionon both.
Just re-flashed NON-HLOS.bin ad fsg.mbn, same results.
I'm a little baffled by the script commands that follow these flashes to "erase modemst1/t2". One user on this thread claimed omitting (commenting out) those erase commands cured the problem https://forum.xda-developers.com/moto-x4/how-to/android-one-xt1900-1-wifi-sim-stock-t3941837.
I tried the modem flash mentioned above with out the erase commands. No change.
Another suggests:
My XT1900-7 had lost its IMEIs and Wifi connections, even after factory reset.
The solution:
Get XT1900-1_PAYTON_FI_9.0_PPWS29.69-39-2-4_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip from lolinet
if you are booting from slot _b, then go to fastboot and flash modem from this FI ROM:
Code:
fastboot flash modem_b NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot reboot
Click to expand...
Click to collapse
Thinking about flashing back to original stock Pie 29.69-26, or the latest 29.69-39-6-4.

Need to go back to system recovery and re-lock bootloader, Help? Anyone?

Hi all,
I've rooted my device a few months ago. Unlocked bootloader, flashed TWRP and installed magisk. After that I have removed root because I couldn't use any payment or banking applications. Now my device heats up everytime i play games like pubg or CODM and getting lag. Also there is sound issue while calling. People can hear my background noise but cannot hear what i'm saying. I don't know if it's related to the rooting but I want to revert back to the factory settings. Can anyone help me do that? Downloading the firmware file from ASUS website and flashing the update will reset my recovery? I could not find anything from the net.
Yes you can roll it fully back to factory. Doing a RAW flash and re-locking BL is probably the easiest way, and then upgrading to the ROM you need via the official way.
Banking/payment apps can be handled with root however even if tricky, so you could probably have kept your root, but that's a different topic...

Categories

Resources