Develop Bugs

Screen issue after .90 update

Hello,
i have the same issue as described in the thread below and shown in this video ==> https://vid.me/NGc5
== > http://www.asus.com/zentalk/forum.php?mod=viewthread&tid=41205&extra=page=1&page=1
i have been suffering from same issue since the .90 update, i tried flashing the 1.1GB file using adb which didn't solve the issue along with the yesterday update
anyone having the same problem?
i want to flash the older .63 version, but using adb it says that it can't flash older version than the current version , anyone can help with that ?

@Asus_USA
any info please

I downgraded the rom to a version from July, yet the same issue persist
Seems like a member mentioned somewhere else that the. 90 update might have broken some hardware using code that is not reversible
Waiting for any feedback from Asus
Sent from my GT-N7000 using Tapatalk

That's actually a screen or onboard video issue.... I see this on laptops all the time

Frankenberrie said:
That's actually a screen or onboard video issue.... I see this on laptops all the time
Click to expand...
Click to collapse
the weird thing that it only happened after the .90 update and several users are reporting it

And some software works fine, like whatsapp where the screen is normal while inside it
Sent from my GT-N7000 using Tapatalk

more users are reporting the same issue on the zentalk forum, good luck all avoiding this

no one else here on the forum suffering from the same issue ? any ideas for troubleshooting or solving ?

@ASUS_Khang
can you please confirm that this is a software issue that will be solved through an update and not a hardware failure ?

AhmadOkda said:
no one else here on the forum suffering from the same issue ? any ideas for troubleshooting or solving ?
Click to expand...
Click to collapse
I am also having this SAME issue ! I have unlocked my bootloader, root access, and flashed the 2.40.97 update again, I tried downgrading, it won't let me install and lower update over an higher one. and I can't get twrp recrovery to stay after the flash, it always goes back to the stock recovery. Also I know whats causing the problem. it's the Auss / powered by intel animated screen , First you have the Asus splash screen, Then the Animated Asus / Intel animation Then the boot animation screen. after unocking my bootloader, and changing the boot animation. I can tell you for sure, the Asus / Intel animation that is causing the issue !. I don't know where this animation is stored on the phone, if anyone knows. maybe we can restore of get rid of it. Anyway my phone is pretty much useless right now, can't use the keypad on the call screen, and can't even see the bottom half of the phone, IT's NOT a hardware problem. like some people have said. it's that dam Asus / Intel animation at starup.

I tried downgrading (using fastboot and abd) to every available firmware and nothing solved this problem
IMHO I think that the 90 upgrade triggered a bug while flashing boot partition
Sent from my GT-N7000 using Tapatalk

UPDATE.. I was able to install cm-12.1-20151011-UNOFFICIAL-Z00A.zip 2015-10-11 01:29 Using Windroid UIniversal Android toolkit. and it worked. and TWRP also the recovery.
Unlocked bootloader, rooted phone, installwd TWRP. Flashed boot, droidboot, with WW. 2.12.40.09 Z00A Then installed cm-12.1-20151011-UNOFFICIAL-Z00A.zip 2015-10-11 01:29 . The screen problem IS still there ! \ Anyone else have any ideas ? ~ Travis

My phone (ZE551ML) developed the same issue. When flashing back to stock didn't work, I sent it in for an warranty RMA. A part was replaced and the phone sent immediately back. Not a word to me about the unlocked bootloader. Just make sure if you send it in, that you state you did flash attempt flashing to stock, and make sure the phone is as close to stock as you can get. Factory reset the phone and go.

I tried last week 3 times I got an RMA & then an advanced RMA and i'm getting the run around from them. they even had the hold of 344.00 on my checkings account to the advanced RMA and then THEY canceled the RMA and everytime I talked to them 3 different customer support people then said " sorry we're updating our systems call back tomorrow. " I got told that 3 times and I've called 4 times. the phone is pretty much useless at the moment.

If they send the phone back to you, the part that was replaced on mine is "90AZ00A1-M02610". Dunno if you can get that part yourself and have it repaired by a third party, but other than that I wouldn't know what to do in your situation.

ArmchairWizard said:
If they send the phone back to you, the part that was replaced on mine is "90AZ00A1-M02610". Dunno if you can get that part yourself and have it repaired by a third party, but other than that I wouldn't know what to do in your situation.
Click to expand...
Click to collapse
...This is the Hardware model# of the whole device, not just a part inside , buy a new phone and you have this yourself !
At least for those in Canada, here a short review for my "advanced replacement" experience:
I used the Chat on their website to get a RMA#, then got a confirmation email with a sort of howto. They mentioned to use Fedex or UPS to send the defective device in and noted not to long to wait to do this otherwise the hold on my creditcard... you know! So i sent the package 3 days later with UPS, cost me a bit over CA$60 with insurance and tracking.
Just the other day i got email from Purolator (a Canada only parcel service) to print a return sticker. No one from ASUS mentioned this to me - $60 wasted
The replacement phone came also with Purolator, ASUS emailed me a tracking# but NOT wich carrier they used. Cost me a few hours and a couple phone calls to find out and re-route the package to my workplace.
ASUS did not use a original case, just a folded carton as they stated the replacement would be a new device. In case i decide to sell the phone i don't have original carton
Start to install all my usual App's etc. found that the phone does not receive any GPS signals, so it seems i changed a not usable screen into a not working GPS
For me, this was my last ASUS for a very long time!

Finally got my Advanced RMA going. can't wait to get a working phone, as soon as I do. Going root & unlock bootloader and install CM 12.1 I'm DONE with ASUS's bloatware ! ~ T

I am having the same problem. I have gotten my screen to work, but it still glitches. Is the only solution to send it in?

jeisenhart34 said:
I am having the same problem. I have gotten my screen to work, but it still glitches. Is the only solution to send it in?
Click to expand...
Click to collapse
I think so, I tried to fix it, flash with 2.20.40.97 Four times now, the problem is still there, rooted, unlocked bootloader, and installed CM 12.1 thinking it would get rid of the problem, it didn't. I think the problem is in the boot partition now. I also flashed the splash screen, and the boot animation. the problem is still there, EVEN after returning this phone back to stock to RMA it. the problem is still there.

Rattraps123 said:
I think so, I tried to fix it, flash with 2.20.40.97 Four times now, the problem is still there, rooted, unlocked bootloader, and installed CM 12.1 thinking it would get rid of the problem, it didn't. I think the problem is in the boot partition now. I also flashed the splash screen, and the boot animation. the problem is still there, EVEN after returning this phone back to stock to RMA it. the problem is still there.
Click to expand...
Click to collapse
I contacted Asus and I have to send my phone in. If you haven't dropped your phone, Asus will overnight you a new one for $25. I dropped my phone so they will repair it free of charge if the damage from the drop isn't what caused the issue. Otherwise I'm going to have to pay.

Oneplus 3 Problem after unbrick

Hello, Good Day to all! I wont take too much of your time but please help me!
My Oneplus 3 suddenly bricked itself, I dont know how or why but it just powered off and then when I tried to boot it up it was hard bricked. Now I've managed to fix it by following the Mega Unbrick guide for Oneplus 3 and it boots up, but the problem is it crashes during boot, and it randomly crashes after a few minutes which then leads to the boot logo crash, I have to "let it rest" so to speak for a few minutes so that it would bypass the boot crashes. Once it got past the crashes some apps are not responding like Twitter, Messenger and so on. Stock apps are fine it's the newly downloaded ones that are not responding, I tried numerous factory resets using the stock recovery and TWRP but no luck.
I am on Nougat 7.1.1 on the latest OxygenOS version, Unlocked bootloader with systemless root. I haven't tried flashing a custom rom the only thing I tried to flash was the Stock Rom. I also noticed that the WiFi and the Data/Signal was particularly weaker since the messages would not load, I need to actually check the app for it to sync. When I got Messenger somehow working, the messages would not even load up.
Any ideas what the problem is? Any help is deeply appreciated, Thanks in Advance!

Hi.. Good Day
This may be a motherboard issue why don't u give ur phone to service center to get it checked up once

RiskTaker10 said:
Hello, Good Day to all! I wont take too much of your time but please help me!
My Oneplus 3 suddenly bricked itself, I dont know how or why but it just powered off and then when I tried to boot it up it was hard bricked. Now I've managed to fix it by following the Mega Unbrick guide for Oneplus 3 and it boots up, but the problem is it crashes during boot, and it randomly crashes after a few minutes which then leads to the boot logo crash, I have to "let it rest" so to speak for a few minutes so that it would bypass the boot crashes. Once it got past the crashes some apps are not responding like Twitter, Messenger and so on. Stock apps are fine it's the newly downloaded ones that are not responding, I tried numerous factory resets using the stock recovery and TWRP but no luck.
I am on Nougat 7.1.1 on the latest OxygenOS version, Unlocked bootloader with systemless root. I haven't tried flashing a custom rom the only thing I tried to flash was the Stock Rom. I also noticed that the WiFi and the Data/Signal was particularly weaker since the messages would not load, I need to actually check the app for it to sync. When I got Messenger somehow working, the messages would not even load up.
Any ideas what the problem is? Any help is deeply appreciated, Thanks in Advance!
Click to expand...
Click to collapse
This sounds like an hardware issue, have you tried method 2 of the unbrick tool, perhaps you could try to re-download it, have you unzipped it? If it boots let it boot and then upgrade to a new OOS version and then you can do whatever you want. If it doesn't work after you followed my suggestions you might wanna contact Oneplus, don't worry even though your bootloader is unlocked you still have full warranty..

Puddi_Puddin said:
This sounds like an hardware issue, have you tried method 2 of the unbrick tool, perhaps you could try to re-download it, have you unzipped it? If it boots let it boot and then upgrade to a new OOS version and then you can do whatever you want. If it doesn't work after you followed my suggestions you might wanna contact Oneplus, don't worry even though your bootloader is unlocked you still have full warranty..
Click to expand...
Click to collapse
I did the method 2 of the unbrick tool, I've done it like twice or thrice now. I have the latest version of OOS, I am afraid to flash a custom rom because after it flashes in TWRP it immediately crashes, it does not even give me a chance to clear the dalvik or reboot. It crashes no reboot or anything.
But thank you I didn't expect anyone would reply well I regained my faith in humanity in forums
Sidenote: What custom rom would you suggest? or is the stock rom better?

RiskTaker10 said:
I did the method 2 of the unbrick tool, I've done it like twice or thrice now. I have the latest version of OOS, I am afraid to flash a custom rom because after it flashes in TWRP it immediately crashes, it does not even give me a chance to clear the dalvik or reboot. It crashes no reboot or anything.
But thank you I didn't expect anyone would reply well I regained my faith in humanity in forums
Sidenote: What custom rom would you suggest? or is the stock rom better?
Click to expand...
Click to collapse
I would suggest VertexOS. It's simple and really fast, EAS and Voxpopuli takes peformance per watt to the next level, if you like feature you might try Zenixx RR.

hrishikeshgramani said:
Hi.. Good Day
This may be a motherboard issue why don't u give ur phone to service center to get it checked up once
Click to expand...
Click to collapse
Unfortunately that is out of the question, there is no Service Center for Oneplus where I live so I cant get it checked ASAP

Puddi_Puddin said:
I would suggest VertexOS. It's simple and really fast, EAS and Voxpopuli takes peformance per watt to the next level, if you like feature you might try Zenixx RR.
Click to expand...
Click to collapse
Thanks for the suggestion! Should I YOLO and flash a custom rom even though my phone is like this?

RiskTaker10 said:
Thanks for the suggestion! Should I YOLO and flash a custom rom even though my phone is like this?
Click to expand...
Click to collapse
You can always try..

Puddi_Puddin said:
You can always try..
Click to expand...
Click to collapse
Okay thanks good citizen of XDA I'll try to flash a custom rom and I'll try to report back here ASAP

getting "your device is corrupt and cannot be trusted pixel"

So after a few months of using my google pixel 2 xl, while I was using it I randomly got a black screen with the message:
"Your device is corrupt. It can't be trusted and may not work properly.
Visit this link on another device: g.co./ABH
PRESS POWER BUTTON TO CONTINUE".
Now it happens every time I turn on my phone. :/
I Have tried doing a factory reset and it still appears.
My phone is not rooted, I have the official OS that I got it with it (updated it through the phone's updater).
The phone was purchased directly from the us google online store.
I've tried to contact their support but they didn't have a solution.
Please help me!!

almogsad said:
So after a few months of using my google pixel 2 xl, while I was using it I randomly got a black screen with the message:
"Your device is corrupt. It can't be trusted and may not work properly.
Visit this link on another device: g.co./ABH
PRESS POWER BUTTON TO CONTINUE".
Now it happens every time I turn on my phone. :/
I Have tried doing a factory reset and it still appears.
My phone is not rooted, I have the official OS that I got it with it (updated it through the phone's updater).
The phone was purchased directly from the us google online store.
I've tried to contact their support but they didn't have a solution.
Please help me!!
Click to expand...
Click to collapse
Sounds like one of those non harmful, annoying messages at boot up. Is your bootloader still locked I assume? If so, have you tried side loading the March OTA. I think sometimes during the OTA updater process that some files don't always make it to the system, which is why you get those messages. Is your phone still functioning properly??

Badger50 said:
Sounds like one of those non harmful, annoying messages at boot up. Is your bootloader still locked I assume? If so, have you tried side loading the March OTA. I think sometimes during the OTA updater process that some files don't always make it to the system, which is why you get those messages. Is your phone still functioning properly??
Click to expand...
Click to collapse
First of all thanks for the response!
yes my bootloader is still locked.
Badger50 said:
have you tried side loading the March OTA
Click to expand...
Click to collapse
How do I do that? ^^
and it seems like the phone still functions properly, but I guess only time will tell

almogsad said:
First of all thanks for the response!
yes my bootloader is still locked.
How do I do that? ^^
and it seems like the phone still functions properly, but I guess only time will tell
Click to expand...
Click to collapse
Just follow these instructions if you want to side load an OTA. It's really not that hard ??
https://developers.google.com/android/ota

Badger50 said:
Just follow these instructions if you want to side load an OTA. It's really not that hard
Click to expand...
Click to collapse
Thanks! I'll try that...
Do you think it might fix the problem?
Edit:
it says in the guide:
"find the appropriate driver for your device from the OEM drivers"
but I don't know which one is mine ^^

almogsad said:
Thanks! I'll try that...
Do you think it might fix the problem?
Edit:
it says in the guide:
"find the appropriate driver for your device from the OEM drivers"
but I don't know which one is mine ^^
Click to expand...
Click to collapse
Once you choose the proper OS version for your pc, and install SDK, when you plug your phone in, it should automatically update your device drivers :good:
And yes, there's a good chance it'll fix your problem. Never any guarantees with this tech stuff though

Badger50 said:
Once you choose the proper OS version for your pc, and install SDK, when you plug your phone in, it should automatically update your device drivers :good:
And yes, there's a good chance it'll fix your problem. Never any guarantees with this tech stuff though
Click to expand...
Click to collapse
Hey! It seems like it worked!!!! Thanks!!
I only wish I hadn't listened to the google support team , and hadn't done a factory reset to phone before lol they don't seem to understand too much about their phones, the guy told me he thinks it's just an add
Thanks again man!

almogsad said:
Hey! It seems like it worked!!!! Thanks!!
I only wish I hadn't listened to the google support team , and hadn't done a factory reset to phone before lol they don't seem to understand too much about their phones, the guy told me he thinks it's just an add
Thanks again man!
Click to expand...
Click to collapse
Oh sweet! Glad to hear it my friend, well done. Now you can help others out with the same issue if it comes up :good: Yeah, the Google folks are kinda funny sometimes. The factory reset is their standard MO! And right, an add on the boot up screen....yeah that's funny! I'd be willing to bet most of them use iPhones!!??????

Badger50 said:
Oh sweet! Glad to hear it my friend, well done. Now you can help others out with the same issue if it comes up :good: Yeah, the Google folks are kinda funny sometimes. The factory reset is their standard MO! And right, an add on the boot up screen....yeah that's funny! I'd be willing to bet most of them use iPhones!!
Click to expand...
Click to collapse
How ironic! lol ???

Badger50 said:
Sounds like one of those non harmful, annoying messages at boot up. Is your bootloader still locked I assume? If so, have you tried side loading the March OTA. I think sometimes during the OTA updater process that some files don't always make it to the system, which is why you get those messages. Is your phone still functioning properly??
Click to expand...
Click to collapse
Thanks!! I also had this issue and following your suggestion to sideload the latest OTA, it appears to have fixed the problem.

I've been getting the same corrupt error on reboots on my xl 2(also not rooted), but I have not been able to get the latest OTA to sideload. It nearly completes but aborts last second and gives a Status 1 error. I'm not sure what I'm doing wrong here. Any help will be appreciated.
Got a similar run-around with Google support. When the factory reset was unsuccessful, they've recommended replacing the phone since it's under warranty, however they think replacing my virtually brand new phone with a refurbished phone is appropriate.

Apsel said:
I've been getting the same corrupt error on reboots on my xl 2(also not rooted), but I have not been able to get the latest OTA to sideload. It nearly completes but aborts last second and gives a Status 1 error. I'm not sure what I'm doing wrong here. Any help will be appreciated.
Got a similar run-around with Google support. When the factory reset was unsuccessful, they've recommended replacing the phone since it's under warranty, however they think replacing my virtually brand new phone with a refurbished phone is appropriate.
Click to expand...
Click to collapse
Are adb/fastboot tools the very newest?

Apsel said:
I've been getting the same corrupt error on reboots on my xl 2(also not rooted), but I have not been able to get the latest OTA to sideload. It nearly completes but aborts last second and gives a Status 1 error. I'm not sure what I'm doing wrong here. Any help will be appreciated.
Got a similar run-around with Google support. When the factory reset was unsuccessful, they've recommended replacing the phone since it's under warranty, however they think replacing my virtually brand new phone with a refurbished phone is appropriate.
Click to expand...
Click to collapse
Unlock then re-lock your bootloader(/s) maybe?

Great job guys, this solution with sideload latest OTA worked for me too with no need to unlock bootloader! :good::good::good:

I can confirm this working again. Pixel 2 XL with 9.0 and November security update.

Thanks!
I just had the corrupt message pop up (bootloader locked), and the sideload ota update seems to have worked!

michaelbsheldon said:
Are adb/fastboot tools the very newest?
Click to expand...
Click to collapse
I'm experiencing the same problem as Apsel, yes the adb/fastboot are the latest.
Error applying update: 15 (ErrorCode : kNewRootfsVerificationError)
E:Error in /sideload/package.zip (status 1)

Badger50 said:
Just follow these instructions if you want to side load an OTA. It's really not that hard ??
https://developers.google.com/android/ota
Click to expand...
Click to collapse
I know this is an old post but I'm having the same issue. Also cannot connect to pc due to, I'm assuming daughterboard issue this and previous pixel models have. I have been rooting phones since the S3 and am no virgin to the sdk. I tried to take it to ubreakifix which was a 4 hour round trip for me. I was told I would have to sign a waiver since the screen is glued to the phone and that was the only way to get to the internals. When I arrived I watched 4 bozos poke at the charging port for 20 min and then contradicting what I was told the night before over the phone that they were not comfortable doing the repair and then they tried to sell me a new device. I just got off chat with google and they want to charge me 270 dollars to fix even though I went to an authorized service center when it was in warranty. Will fastboot work over wifi?

Toolmighty said:
Will fastboot work over wifi?
Click to expand...
Click to collapse
'fraid not. Both the bootloader and recovery have stripped down hardware support, limited essentially to the display and storage. Neither has WiFi support that I know of, thus you have to use a USB cable.

I figured it out after I figured out how to fix the daughterboard issue w/o replacing the daughterboard. Verizon are some sneaky *^&$^s. Thx for the reply tho. I'm sure ur quite busy.

Oneplus 5t Not Working even after unbrick

After the latest update of Oxygen os my 5t had start crashing so I Installed TWRP recovery and Installed Linage OS but in that rom also there was same problem so i Installed another rom OMNI and there was the same problem Today the phone crashed as always and it Didn't boot up It got stuck in Boot animation and that i tried to flash another rom but no rom will get flashed from twrp also so I used ADB Sideload to flash rom it got flashed but it also got stuck in bootanimation It wasn't a Bootloop It just got Hang on Bootanimation and than I use hardbrick method (MSMdownloadTool V4.0.8) It flashed The Stock OS which Booted Fine for 10sec And the same problem happens again I have Flashed two Stock OS (1 - dumpling_43_O.06_171206.ops) and (2 - dumpling_43_O.36_180613.ops) Now there is no boot-animation Its Stuck on One-plus Logo (POWERED BY ANDROID) Plz Help sorry for my English

Sounds like a faulty flash storage. RMA it.

freyrnygaard said:
Sounds like a faulty flash storage. RMA it.
Click to expand...
Click to collapse
what is RMA I Really Need your Help PLZZZ

Why did you use nougat and oreo unbricking tools if you were on pie? No wonder your phone doesn't boot.
The latest unbricking tools for 9.0.3 can be found here: https://www.androidfilehost.com/?fid=11410963190603910105
RMA means Return Merchandise Authorization (send back to the seller). Since you've already used the phone, you can't just send it back anyway. If unbricking doesn't work, you'll have to contact oneplus support to find out what your options are.

bud7dha said:
Why did you use nougat and oreo unbricking tools if you were on pie? No wonder your phone doesn't boot.
The latest unbricking tools for 9.0.3 can be found here: https://www.androidfilehost.com/?fid=11410963190603910105
RMA means Return Merchandise Authorization (send back to the seller). Since you've already used the phone, you can't just send it back anyway. If unbricking doesn't work, you'll have to contact oneplus support to find out what your options are.
Click to expand...
Click to collapse
Offtopic but you can use Nougat and Oreo unbrick tools even if you're on Pie (I did it myself because I was curious to see if it will erase /vendor partition or not). I however agree that this is not a normal situation and that his storage might be faulty.

Can you at least flash stock recovery?

freyrnygaard said:
Sounds like a faulty flash storage. RMA it.
Click to expand...
Click to collapse
Hmm. I was thinking about rooting mine today. But you got me thinking again lol.
I googled "faulty flash storage Android" and not much came up tho. Can you get into a little bit more detail what is that and is it very common with onePlus devices ?
*Sorry if I asked sth dumb. Im new to Android ?

nevethlexfiend said:
Hmm. I was thinking about rooting mine today. But you got me thinking again lol.
I googled "faulty flash storage Android" and not much came up tho. Can you get into a little bit more detail what is that and is it very common with onePlus devices ?
*Sorry if I asked sth dumb. Im new to Android
Click to expand...
Click to collapse
I meant as in a a damaged internal storage drive. You know, a storage drive can fail but it certainly won't happen from rooting your phone. So go ahead and enjoy.

Question "Rooted" now what?

Oneplus finally came through with my bootloader unlocking token.Not to mention all the hoops T-Mobile had me jump through.With that being said im in possession of my very first fully rooted phone that just happens to be a 9 Pro.Any suggestions on which modules I can command Majisk to install first?How bout any general pointers thus being this is my first experience free and in full control of my 9pro.?

Here's some ideas:
What Magisk modules are you using?
Hey all moving up from my OP 7 pro to the OP 9 pro. What are all the magisk modules everyone is using on the OP 9 pro.? 1.Anything to force full screen mode on all apps? The settings for full screen apps dont include all the apps im using as...
forum.xda-developers.com

Shanemichealrowland said:
Oneplus finally came through with my bootloader unlocking token.Not to mention all the hoops T-Mobile had me jump through.With that being said im in possession of my very first fully rooted phone that just happens to be a 9 Pro.Any suggestions on which modules I can command Majisk to install first?How bout any general pointers thus being this is my first experience free and in full control of my 9pro.?
Click to expand...
Click to collapse
To be honest, I would hold off until we have a working TWRP build, especially if this is your first experience of root, etc

djsubterrain said:
To be honest, I would hold off until we have a working TWRP build, especially if this is your first experience of root, etc
Click to expand...
Click to collapse
I was thinking the same thing .I just thought maybe there are some safer mods I should do in the meantime.

@Shanemichealrowland
I've been rooting Android for many years now. I always read read and read some more before I begin to install anything and I always wait until there is a working custom recovery and make a FULL backup of every partition and transfer it to a USB drive and or my computer first thing. Make sure to backup your efs as well so that if you lose your IMEI at some point it too can them be reflashed using fastboot. These are things I've always done and will continue to always do. Many users get excited and rush out to install things and don't read enough about their device and end up with an expensive piece of plastic and glass. If you always wait and read everything and make sure you fully understand how your device works before you install things then you will always have a great experience and never have to go through the bad feeling of ruining your expensive device. I read everything in a forum about my device first. You can't go wrong doing things that way. I hope this helps. OnePlus makes great devices! I'm using my OnePlus 6t now to type this and I still love it!! Welcome to XDA my friend.
Edit added: I see you're from Houston. Me too.

flash713 said:
@Shanemichealrowland
I've been rooting Android for many years now. I always read read and read some more before I begin to install anything and I always wait until there is a working custom recovery and make a FULL backup of every partition and transfer it to a USB drive and or my computer first thing. Make sure to backup your efs as well so that if you lose your IMEI at some point it too can them be reflashed using fastboot. These are things I've always done and will continue to always do. Many users get excited and rush out to install things and don't read enough about their device and end up with an expensive piece of plastic and glass. If you always wait and read everything and make sure you fully understand how your device works before you install things then you will always have a great experience and never have to go through the bad feeling of ruining your expensive device. I read everything in a forum about my device first. You can't go wrong doing things that way. I hope this helps. OnePlus makes great devices! I'm using my OnePlus 6t now to type this and I still love it!! Welcome to XDA my friend.
Edit added: I see you're from Houston. Me too.
Click to expand...
Click to collapse
Wow,your so right. Ive already caught and stopped myself from installing a couple things I wasnt sure about.I think im gonna slow down a bit and keep learning.Thanks for bringing me back to whats should be going on.

Shanemichealrowland said:
I was thinking the same thing .I just thought maybe there are some safer mods I should do in the meantime.
Click to expand...
Click to collapse
There are Magisk modules but if you get into trouble you need to be able to access recovery, OnePlus's default recovery isn't quite as all encompassing as TWRP

djsubterrain said:
There are Magisk modules but if you get into trouble you need to be able to access recovery, OnePlus's default recovery isn't quite as all encompassing as TWRP
Click to expand...
Click to collapse
Afaik you can delete problematic magisk modules in safemode. Plus I havent used TWRP pretty much for anything with OnePlus 8 pro and after. That just helps me understand better how things work. Plus because I use Linux msm is useless to me but thats another topic
Edit: Dont get me wrong, not trying to convince people to mod/flash anything. Just pointing out that TWRP is not necessity.

pyry666 said:
Plus because I use Linux msm is useless to me but thats another topic
Click to expand...
Click to collapse
Could you clarify this? What procedure do you follow in the event of a brick? I use Linux exclusively and would prefer to be able to recover from a brick using Linux instead of relying on MSM, but I'm not clear on all the steps MSM does or where/how I would find the specifics needed to do the same thing myself.

terlynn4 said:
Could you clarify this? What procedure do you follow in the event of a brick? I use Linux exclusively and would prefer to be able to recover from a brick using Linux instead of relying on MSM, but I'm not clear on all the steps MSM does or where/how I would find the specifics needed to do the same thing myself.
Click to expand...
Click to collapse
Ive only done that once myself and that was with 6T. But basicly you need to flash every partition etc via terminal

pyry666 said:
Ive only done that once myself and that was with 6T. But basicly you need to flash every partition etc via terminal
Click to expand...
Click to collapse
Ok, I've flashed all partitions before, but I thought there was more to MSM's steps than that. E.g. fixing the partitions themselves, or some sort of voodoo required to recover from any sort of soft brick.

terlynn4 said:
Ok, I've flashed all partitions before, but I thought there was more to MSM's steps than that. E.g. fixing the partitions themselves, or some sort of voodoo required to recover from any sort of soft brick.
Click to expand...
Click to collapse
AfaIk there is not that much. It locks bootloader though and IF something goes wrong that could cause issues. One of the reasons ive never used it.
Edit: Ill correct myself. MSM uses EDL mode. And if device is borked that badly then only it works. And imo should be used only then
Edit2: One could try using virtual machine to use MSM with Linux but I have zero knowledge how that would play out

pyry666 said:
AfaIk there is not that much. It locks bootloader though and IF something goes wrong that could cause issues. One of the reasons ive never used it.
Edit: Ill correct myself. MSM uses EDL mode. And if device is borked that badly then only it works. And imo should be used only then
Edit2: One could try using virtual machine to use MSM with Linux but I have zero knowledge how that would play out
Click to expand...
Click to collapse
Right, I've been in situations with my last phone where EDL was my only option and I had to use MSM. I have dual boot on a laptop for those occasional Windows-only things like MSM. In the past I've found the USB passthrough to be unreliable for this purpose using a VM in virtualbox, though I haven't tried in a few years so it may have improved.