Database Users

Nexus 10 stuck in boot loop.. please help!!!

So, I was using Zedomax's how to root N10 tutorial (http://www.youtube.com/watch?feature=player_embedded&v=wVlI-gWppCA#at=261)... I had everything working fine up until about 4:15 in the video when his restarts mine just gets stuck in boot loop and displays the nexus bootloader for an unlimited amount of time. My device does however show that it is unlocked because when I go back through the process it says it is already unlocked as you can see in the pictures. the first is the cmd I used and the second is what the N10 shows after "fastboot oem unlock"... I am completely lost and have tried over and over to find the problem... I have tried to unroot and restore but I cant even find a working file that isnt malicious... ANY AND ALL HELP OR SUGGESTIONS WOULD BE APPRECIATED...

Andrololol said:
So, I was using Zedomax's how to root N10 tutorial (http://www.youtube.com/watch?feature=player_embedded&v=wVlI-gWppCA#at=261)... I had everything working fine up until about 4:15 in the video when his restarts mine just gets stuck in boot loop and displays the nexus bootloader for an unlimited amount of time. My device does however show that it is unlocked because when I go back through the process it says it is already unlocked as you can see in the pictures. the first is the cmd I used and the second is what the N10 shows after "fastboot oem unlock"... I am completely lost and have tried over and over to find the problem... I have tried to unroot and restore but I cant even find a working file that isnt malicious... ANY AND ALL HELP OR SUGGESTIONS WOULD BE APPRECIATED...
Click to expand...
Click to collapse
I can help you get back to stock, that should fix everything. You will erase everything and have to start whatever you were working on again. So back it up before hand if you can.
So first you need to be sure you have TODAYS latest updates to the fastboot.exe program, do this by installing the SDK from Google, then launching the update manager and doing all updates. See this post:
http://forum.xda-developers.com/showpost.php?p=38961605&postcount=5
Then you need to do what styckx says. Be sure to click 'Thanks' under his posts. The only thing that you may find is hard to understand is, if you download that from Google and it end up as .tar you have to rename it to .tgz to have it extract correclty. See this post:
http://forum.xda-developers.com/showpost.php?p=38091931&postcount=210
EDIT - If you did oem unlock and were stuck at the X bootlogo then there is an easier fix than what I describe. You state you are stuck at bootloader. Just FYI
Good luck!

bigmatty said:
I can help you get back to stock, that should fix everything. You will erase everything and have to start whatever you were working on again. So back it up before hand if you can.
So first you need to be sure you have TODAYS latest updates to the fastboot.exe program, do this by installing the SDK from Google, then launching the update manager and doing all updates. See this post:
http://forum.xda-developers.com/showpost.php?p=38961605&postcount=5
Then you need to do what styckx says. Be sure to click 'Thanks' under his posts. The only thing that you may find is hard to understand is, if you download that from Google and it end up as .tar you have to rename it to .tgz to have it extract correclty. See this post:
http://forum.xda-developers.com/showpost.php?p=38091931&postcount=210
EDIT - If you did oem unlock and were stuck at the X bootlogo then there is an easier fix than what I describe. You state you are stuck at bootloader. Just FYI
Good luck!
Click to expand...
Click to collapse
yes, it is stuck at nexus symbol "X" loading screen.. you say there is an easier fix for that?

Andrololol said:
yes, it is stuck at nexus symbol "X" loading screen.. you say there is an easier fix for that?
Click to expand...
Click to collapse
yes. that is common w/ these after oem unlock. on that fastboot screen you posted, the one you get to by holding the certain key sequence at boot - use the volume keys to select Recovery, then use the start button to boot to that mode. This confuses people because at that point it looks broken - all you see is a triangle with an error X in it (or something like that.) BUT from that screen you access another menu, do this by briefly pressing power volume up and volume down in little spurts. it sounds wierd, but you do that for up to 20 seconds and you'll finally get it. its just hard to enter so you have to do it like that otherwise you go crazy trying. once you've accessed that menu you will know because its all text. using the navigation choose 'factory wipe' and wipe it. after that your N10 will boot like normal. be aware - navigation on that text only menu is tricky.

New/Stock Oneplus Two, unable to boot into recovery

Hey all, completely new to this forum and my Oneplus Two that I've had for a little over two weeks.
I recently got a OTA update for Oxygen 2.2.0 but I can't seem to install it. Everytime I download it and click the "install" option, the phone reboots (probably to go to recovery) but after a very brief splash screen and a vibration, it vibrates again and displays the standard boot splash screen, boots into the OS and offers me to download the update again.
I've done a little troubleshooting in the past two-three days and from what I understand, the phone doesn't seem to be able to boot into recovery or fastboot. I've enabled the advanced options in the "reboot" menu and when selecting "recovery" the phone reboots and does the same behavior described above. I tried powering off the phone and booting with the volume up button pressed (while pressing power) and the phone boots and displays a "Fastboot Mode" splash screen but it seems to hang there forever until I actually shut it off again and power it back on. Also, I've tried booting it into recovery from ADB, connected to my PC and I get the same behavior: brief splash screen with a vibrate and then the phone seems to reboot again normally.
I haven't tampered with the phone yet, it is brand new out of the box, not rooted and nothing other than simply installing a few games, Nova Launcher, changing the wallpaper and using it as you would normally use your phone.
Anyone has an idea how I could actually get the Recovery functioning on this phone?
Best regards and thanks in advance for any help!

redbay1 said:
Hey all, completely new to this forum and my Oneplus Two that I've had for a little over two weeks.
I recently got a OTA update for Oxygen 2.2.0 but I can't seem to install it. Everytime I download it and click the "install" option, the phone reboots (probably to go to recovery) but after a very brief splash screen and a vibration, it vibrates again and displays the standard boot splash screen, boots into the OS and offers me to download the update again.
I've done a little troubleshooting in the past two-three days and from what I understand, the phone doesn't seem to be able to boot into recovery or fastboot. I've enabled the advanced options in the "reboot" menu and when selecting "recovery" the phone reboots and does the same behavior described above. I tried powering off the phone and booting with the volume up button pressed (while pressing power) and the phone boots and displays a "Fastboot Mode" splash screen but it seems to hang there forever until I actually shut it off again and power it back on. Also, I've tried booting it into recovery from ADB, connected to my PC and I get the same behavior: brief splash screen with a vibrate and then the phone seems to reboot again normally.
I haven't tampered with the phone yet, it is brand new out of the box, not rooted and nothing other than simply installing a few games, Nova Launcher, changing the wallpaper and using it as you would normally use your phone.
Anyone has an idea how I could actually get the Recovery functioning on this phone?
Best regards and thanks in advance for any help!
Click to expand...
Click to collapse
That is the norm for fastboot, it doesn't go past that screen.
It may not make a difference, did you try to boot to recovery via Power+Volume Down buttons?

Greetings Khaos64,
Yes, I've tried booting with Vol-Down+Power but the phone does not start.
With volume-up+power, I get the Fastboot splash screen but the phone does not respond to any input.
I tried selecting "bootloader" from the reboot menu but I get the same thing: Reboots and after a second, the phone reboots again normaly and into OxygenOS.
Is there a way to verify if the bootloader or recovery is corrupt and maybe reflash the stock recovery onto the phone?
Thanks for your input!

You may just want to go straight to oneplus support since everything is stock and only 2 weeks they should be able to get you updated or replace it.
If you'd like to be more hands on... maybe something below can help.
So your phone isn't recognized/no commands acceptred from your computer when booted to fastboot?
Such as unlocking your bootloader and booting into twrp... "fastboot boot yourfilename.img" or maybe flashing it.
Make sure OEM unlocking is selected in Developer options.
If you can't do that then this may not work but is worth a shot.
http://forum.xda-developers.com/showpost.php?p=62973446&postcount=2
These may also be something to look into:
http://forum.xda-developers.com/oneplus-2/general/guide-unbrick-recover-oneplus-2-to-t3269543
http://forum.xda-developers.com/oneplus-2/general/oneplus-solution-hard-bricked-device-t3183449

I did try to contact Oneplus for support but I am not the one who purchased the phone. Long story short, it was a gift from my girlfriend that she bought off of someone. The phone was new in box and was a warranty replacement. I would have to contact the seller and go trough him for support unfortunately.
Thanks for the different suggestions!, I will fiddle around with it this afternoon while the kids are having their mid-day nap and I'll get back with the results
Thanks again for the help, it's greatly appreciated!

Hello,
I eventually started fiddling around with fasboot and tried unlocking the bootloader. This sent the phone into a bootloop where it would try to boot into recovery and reboot right away.
I found an article on how to restore the phone to Oxygen 2.1.1. It would wipe user data but I did it anyway and it actually did restore the phone and now I have a worling recovery.
Here is a link to the guide I used:
http://forum.xda-developers.com/oneplus-2/general/guide-unbrick-recover-oneplus-2-to-t3269543
Thanks again for the help in solving my issue

Congratulations hope you enjoy the phone
Sent from my ONE A2005 using Tapatalk

redbay1 said:
Hello,
I eventually started fiddling around with fasboot and tried unlocking the bootloader. This sent the phone into a bootloop where it would try to boot into recovery and reboot right away.
I found an article on how to restore the phone to Oxygen 2.1.1. It would wipe user data but I did it anyway and it actually did restore the phone and now I have a worling recovery.
Here is a link to the guide I used:
http://forum.xda-developers.com/oneplus-2/general/guide-unbrick-recover-oneplus-2-to-t3269543
Thanks again for the help in solving my issue
Click to expand...
Click to collapse
Glad one was able to help you do it. :good:

redbay1 said:
Hello,
I eventually started fiddling around with fasboot and tried unlocking the bootloader. This sent the phone into a bootloop where it would try to boot into recovery and reboot right away.
I found an article on how to restore the phone to Oxygen 2.1.1. It would wipe user data but I did it anyway and it actually did restore the phone and now I have a worling recovery.
Here is a link to the guide I used:
http://forum.xda-developers.com/oneplus-2/general/guide-unbrick-recover-oneplus-2-to-t3269543
Thanks again for the help in solving my issue
Click to expand...
Click to collapse
HI there,
I am having the exact same issue with my oneplus 2. Unfortunately i know almost nothing regarding these android thingy. I know it has been almost 2 years, would you mind guide me through the steps? I would appreciate it so much.
Thanks.

Nexus 6P BootLoop with Locked BootLoader

Hi all,
I'm sure I am still one of many that cannot use XCnathan32's solution to fix their phones. I think the biggest problem is that it is difficult to discern between hardware vs. software being the culprit. If hardware, nothing I do can help. I've wanted to use the solution but when the computer cannot even find the device/recognize it, I cannot even start the solution. Let me explain what my phone is like/ the state the boot loader is in:
Google logo is the only thing to show.
Even when trying to boot from bootloader -> recovery mode, it only goes to the google logo and boot loops from there.
Unfortunately I did not unlock developer options / USB debugging so my bootloader is LOCKED, my computer does not recognize the 6P at all unless in boot loader. It gives a strange description of the device, but does not treat it as a device in the device manager. Even if it does show I cannot update it's driver. It essentially seems like only the bootloader is a device rather than the phone.
I have tried leaving the device to boot in hopes of it miraculously starting and allowing me to go to developer options, this has failed as well.
Would anyone know/ be willing to explain how to proceed from here? I'm sure the options are limited when the device does not even show up on the computer.
Note: I don't know much about TWRP, ADB, SDK etc, its all 2 days new to me.
Thanks for any help!

Take a trip to home Depot. Put your heat gun above the finger print unlock after getting power to 5%. Profit.

mattrb said:
Take a trip to home Depot. Put your heat gun above the finger print unlock after getting power to 5%. Profit.
Click to expand...
Click to collapse
I got it! Used a blowdryer though. Unfortunately it went back to boot looping even after I did a factory reset. I'm going to apply the fix now that OEM has been unlocked and USB debugging!

Archavius said:
I got it! Used a blowdryer though. Unfortunately it went back to boot looping even after I did a factory reset. I'm going to apply the fix now that OEM has been unlocked and USB debugging!
Click to expand...
Click to collapse
Congrats on getting it to work! Let me know if you need any help with flashing the modified images.

XCnathan32 said:
Congrats on getting it to work! Let me know if you need any help with flashing the modified images.
Click to expand...
Click to collapse
I'm currently writing a guide to get to the OEM unlock stage on your thread . Thanks so much for all of your work, my phone is currently booting. Its got the google logo with a unlocked pad lock on the bottom and then it switches to a section with android warnings saying "Device software cant be checked for corruption, please lock the bootloader".

Its actually bootlooping again... I've flashed all the images possible on your downloads part of the thread Not sure if there's another option to take to get rid of the bootlooping.

Archavius said:
Its actually bootlooping again... I've flashed all the images possible on your downloads part of the thread Not sure if there's another option to take to get rid of the bootlooping.
Click to expand...
Click to collapse
Have you been here? ?

Exodusche said:
Have you been here?
Click to expand...
Click to collapse
That's the exact guide I used. I also used his first guide before that one was published by XDA. It almost seems too simple though. I feel like I'm missing something. I flashed the 48B_A4 firmware, then the twrp3_1_1_4Cores.img and reboot. It still boot looped. I then proceeded to flash the other possible imgs to see if they would work. I cant flash the EX kernel since I can't boot into recovery since it just boot loops again.

mattrb said:
Take a trip to home Depot. Put your heat gun above the finger print unlock after getting power to 5%. Profit.[/QUOTE
Excuse my pessimism, but for real? I'm having the same issue, what exactly does this do?
Click to expand...
Click to collapse

JohnnyKilo said:
mattrb said:
Take a trip to home Depot. Put your heat gun above the finger print unlock after getting power to 5%. Profit.[/QUOTE
Excuse my pessimism, but for real? I'm having the same issue, what exactly does this do?
Click to expand...
Click to collapse
This will throttle the big cluster of processors making it so the phone can stop boot looping by using only the small clusters.
Click to expand...
Click to collapse

Archavius said:
JohnnyKilo said:
This will throttle the big cluster of processors making it so the phone can stop boot looping by using only the small clusters.
Click to expand...
Click to collapse
Format all partition except for internal storage.
1. Flash N2G48B_vendor.img into vendor partition
2. Flash N2G48B_4Cores.img into boot partition
3. Flash purenexus_angler-7.1.2-20170725-OFFICIAL.zip
4. Flash BeansGapps-Full-7.1.x-20170610.zip
5. Flash EX4_1_1_4Cores.zip (Elemental Kernel), step up the core speed one notch on first screen, leave the rest on default.
Reboot.
Waited about 10min on the animation screen (4 dot jumping), eventually phone completed booting
Click to expand...
Click to collapse

sorry to hijack your thread, can i know the steps that you took to enable oem unlock ?
Because i am in your similar situation, all i can see is the google logo & bootloader is locked (i cannot go to the settings menu because the phone doesnt bootup, i am stuck in the google logo).
If i run the fastboot flashing unlocl it fails (since bootloader is locked)

ShadowSounds said:
sorry to hijack your thread, can i know the steps that you took to enable oem unlock ?
Because i am in your similar situation, all i can see is the google logo & bootloader is locked (i cannot go to the settings menu because the phone doesnt bootup, i am stuck in the google logo).
If i run the fastboot flashing unlocl it fails (since bootloader is locked)
Click to expand...
Click to collapse
You need to use a heat gun or hair dryer above the fingerprint sensor. Keep phone at low battery but not empty. 5%

.....

mattrb said:
You need to use a heat gun or hair dryer above the fingerprint sensor. Keep phone at low battery but not empty. 5%
Click to expand...
Click to collapse
lol it worked. Thanks

ShadowSounds said:
lol it worked. Thanks
Click to expand...
Click to collapse
How did you know your battery was at 5%? At the fastboot screen I see that the battery says OK, but not a specific number. Does that battery field change when it gets below "OK"?

Archavius said:
I'm currently writing a guide to get to the OEM unlock stage on your thread . Thanks so much for all of your work, my phone is currently booting. Its got the google logo with a unlocked pad lock on the bottom and then it switches to a section with android warnings saying "Device software cant be checked for corruption, please lock the bootloader".
Click to expand...
Click to collapse
This is my phone. Can you help me?

Hi there - I ended up having to use a blow dryer to throttle the phone using High heat. I wouldn't recommend it, it wasnt safe and my phone after fixing stopped working in an hour. If your phone isn't working despite following the fix above get a new phone, the pixel 3a seems like a nice new option, good luck!

Stuck in recovery mode
Archavius said:
JohnnyKilo said:
This will throttle the big cluster of processors making it so the phone can stop boot looping by using only the small clusters.
Click to expand...
Click to collapse
OK, I don't have a bootloop problem per se, but I changed my battery and now it only goes to the Reboot bootloader screen. The arrow keys don't work to change the menu. Sometimes I can get it to Recovery mode, but neither the power key or arrow keys will work. Once I got it to the Start, but the power key did nothing. ADB devices returns nothing, so even though I installed the Google USB drivers in Android Studio I can't get the computer and the Nexus to talk to each other. I'm ready to try heating the device, but that goes against everything I've ever known about electronic devices. Are you sure? .
Click to expand...
Click to collapse

Don't heat up your phone, this thread is uselss for you.

Have to press start button to boot after upgrade, why?

Good afternoon
After upgrading to LOS 15 when the phone boots up it displays "if power key is not pressed, your device will power off in 30 seconds"
If I don't, it really powers off.
That's annoying. If my phone randomly reboots during the night, it won't ring to wake me up!
Is it possible to remove this annoyance?
Thanks

i had this problem too; mine is A2017 model.
Oki said:
Removing the message at boot is easy. If you already have TWRP Exclusive v3.2.1-7 and the aforementioned bootloader, then you just have to boot TWRP Advanced menu > More > Del inscription. Easy, Isn't it? It works in my A2017U so It should work for you too.
Click to expand...
Click to collapse
just flash recovery 3.2.1-8-TREBLE for android 8.x-9.x (new bootstacks) and do as @Oki said
just pay attention: Warning! "Del Inscription" - only for A2017 and A2017G !!!
https://forum.xda-developers.com/axon-7/development/twrp-3-1-0-2-t3591075
i recommend this guide for LOS15.1 by @Oki:
https://forum.xda-developers.com/showpost.php?p=77731728&postcount=1238

Glad this got some attention, but remember to post this in the right section next time.

Thank you very much, I've installed this recovery, and it' great.
For the ones that will read this thread:
If you use a locking scheme, don't forget to reset the scheme with advanced/more/unlock/reset lockscreen, otherwise you'll be denied the access.

Did I just brick my phone?...

Alright, so I had just installed TWRP and Magisk, made backups of my ROM and EFS, everything is going well. I go to install LuisROM.
I go into TWRP, click install, and click on the LuisROM package. Says it doesn't find a digest file, but installation is continuing, so I figure it's no big deal. Reboot, and I get the Unlocked Bootloader warning that I've just recently began to familiarize myself with, but at the bottom of the screen, say the bottom half inch or so, is crazy static. Completely jumbled nonsense. It's not animated or anything, just randomly colored static pixels. Odd.
Next screen? Black. Nothing. Plugged into the computer and the she makes the familiar beeps that a device has been plugged in. For a time I find myself stuck in a boot loop trying to get back into recovery via power + vol down, but nothing. Seems to instant reboot back into the warning then black screen.
Now: I can't even seem to turn the phone off! If I plug into the laptop, I hear the familiar sounds, but can't do anything about it that I know of. If I hold the power button for 30-60 seconds: nothing.
I saw a few posts on here saying something about a complete power drain and recharge, so that's my next best guess, but I'm hoping someone else has a better idea.

lynxon said:
Alright, so I had just installed TWRP and Magisk, made backups of my ROM and EFS, everything is going well. I go to install LuisROM.
I go into TWRP, click install, and click on the LuisROM package. Says it doesn't find a digest file, but installation is continuing, so I figure it's no big deal. Reboot, and I get the Unlocked Bootloader warning that I've just recently began to familiarize myself with, but at the bottom of the screen, say the bottom half inch or so, is crazy static. Completely jumbled nonsense. It's not animated or anything, just randomly colored static pixels. Odd.
Next screen? Black. Nothing. Plugged into the computer and the she makes the familiar beeps that a device has been plugged in. For a time I find myself stuck in a boot loop trying to get back into recovery via power + vol down, but nothing. Seems to instant reboot back into the warning then black screen.
Now: I can't even seem to turn the phone off! If I plug into the laptop, I hear the familiar sounds, but can't do anything about it that I know of. If I hold the power button for 30-60 seconds: nothing.
I saw a few posts on here saying something about a complete power drain and recharge, so that's my next best guess, but I'm hoping someone else has a better idea.
Click to expand...
Click to collapse
Can you reboot to EDL Mode? Plug in your phone. And hold the power and Volume Up button till it turns off. As soon as the Screen Goes black, let go of Power and Hold both the Volume Buttons. You will hear the Windows Connection Sound from your PC but phone screen will be back. After that, follow the instructions from the MSM Download Tool thread. It's in the Guides Section or you can Google 'MSM Download Tool OP6T"

DarthVader said:
Can you reboot to EDL Mode? Plug in your phone. And hold the power and Volume Up button till it turns off. As soon as the Screen Goes black, let go of Power and Hold both the Volume Buttons. You will hear the Windows Connection Sound from your PC but phone screen will be back. After that, follow the instructions from the MSM Download Tool thread. It's in the Guides Section or you can Google 'MSM Download Tool OP6T"
Click to expand...
Click to collapse
The phone is currently stuck in a state where the screen is black, but is stuck powered on. I cannot seem to power down manually.
That being said, after going to the thread you've directed me to, it does appear in the device manager under the name indicated by the thread! I will report back once I've tried all I can with this lead, thank you very much.

lynxon said:
The phone is currently stuck in a state where the screen is black, but is stuck powered on. I cannot seem to power down manually.
That being said, after going to the thread you've directed me to, it does appear in the device manager under the name indicated by the thread! I will report back once I've tried all I can with this lead, thank you very much.
Click to expand...
Click to collapse
Good Luck.

Alright, so right now I'm getting "Sahara Communication Failed, please try again after power off phone."
So, I guess I'm back to waiting for the phone to run out of battery on its own. I'll try the MSM Download Tool again once that time comes :good:

lynxon said:
Alright, so right now I'm getting "Sahara Communication Failed, please try again after power off phone."
So, I guess I'm back to waiting for the phone to run out of battery on its own. I'll try the MSM Download Tool again once that time comes :good:
Click to expand...
Click to collapse
I think you're forgetting the 3-button-magic of your device. Press power + vol-up + vol-down simultaneously for 10 seconds to make it power down.
Wrapped with delicious Fajita [emoji896]

Timmmmaaahh said:
I think you're forgetting the 3-button-magic of your device. Press power + vol-up + vol-down simultaneously for 10 seconds to make it power down.
Click to expand...
Click to collapse
I did actually try that as well, to no avail.
DarthVader said:
Can you reboot to EDL Mode? Plug in your phone. And hold the power and Volume Up button till it turns off. As soon as the Screen Goes black, let go of Power and Hold both the Volume Buttons. You will hear the Windows Connection Sound from your PC but phone screen will be back. After that, follow the instructions from the MSM Download Tool thread. It's in the Guides Section or you can Google 'MSM Download Tool OP6T"
Click to expand...
Click to collapse
Good news is that this time the MSM Download Tool could recognize the phone, however I received "Images do not match with the phone." I had to download 9.0.12. as it seems that 9.0.13. actually got removed from that server as I was in the middle of downloading it. I found another source for 9.0.13. and am downloading that now. Hopefully that's the correct version...

lynxon said:
I did actually try that as well, to no avail.
Good news is that this time the MSM Download Tool could recognize the phone, however I received "Images do not match with the phone." I had to download 9.0.12. as it seems that 9.0.13. actually got removed from that server as I was in the middle of downloading it. I found another source for 9.0.13. and am downloading that now. Hopefully that's the correct version...
Click to expand...
Click to collapse
Is your phone a T-Mobile Converted

DarthVader said:
Good Luck.
Click to expand...
Click to collapse
And the phone is alive again! Hallelujah! I had to use the T-Mobile version of the MSM Download Tool, which is funny because I had bought the phone used and there was no T-Mobile screen at boot before, but there is now, but she is alive!!!
Thank you again for your help. You're doing great work since returning to the light side, Vader

lynxon said:
And the phone is alive again! Hallelujah! I had to use the T-Mobile version of the MSM Download Tool, which is funny because I had bought the phone used and there was no T-Mobile screen at boot before, but there is now, but she is alive!!!
Thank you again for your help. You're doing great work since returning to the light side, Vader
Click to expand...
Click to collapse
Glad to know you're back up. You bought it off eBay I assume? That would explain the no TMo Splash Screen earlier. Now if you'd like to revert to International again, there is a Guide you can use to convert your TMo into International and then update to latest 10.3 or Flash a Custom ROM as you please. It's in the Guides Section.
May the Force be with You.

DarthVader said:
Glad to know you're back up. You bought it off eBay I assume? That would explain the no TMo Splash Screen earlier. Now if you'd like to revert to International again, there is a Guide you can use to convert your TMo into International and then update to latest 10.3 or Flash a Custom ROM as you please. It's in the Guides Section.
May the Force be with You.
Click to expand...
Click to collapse
Yes! Back up and then immediately down... So, I followed the procedure to remove the T-Mobile info and that worked well, back to stock OxygenOS 9.0.13. Followed the directions here for unlocking the bootloader, running TWRP and Magisk. All good.
Last time I flashed with RR and crashed. This time I flashed with LineageOS 17 and... Exact same crash. Static on the bottom of the screen, bootloop and all. So, now I'm stuck waiting again for the battery to die down before I can reflash to T-Mobile, then to international, then unlock the bootloader.
Any idea what I can do differently this time so I can have a custom ROM?
Not eBay, but I was using OfferUp and found a local shop selling it so I was able to sidestep the middleman.

lynxon said:
Yes! Back up and then immediately down... So, I followed the procedure to remove the T-Mobile info and that worked well, back to stock OxygenOS 9.0.13. Followed the directions here for unlocking the bootloader, running TWRP and Magisk. All good.
Last time I flashed with RR and crashed. This time I flashed with LineageOS 17 and... Exact same crash. Static on the bottom of the screen, bootloop and all. So, now I'm stuck waiting again for the battery to die down before I can reflash to T-Mobile, then to international, then unlock the bootloader.
Any idea what I can do differently this time so I can have a custom ROM?
Not eBay, but I was using OfferUp and found a local shop selling it so I was able to sidestep the middleman.
Click to expand...
Click to collapse
Could you perhaps provide an image of Said Crash? And a couple more things. Which ROM were you trying to Flash. What was your OOS version before trying to Flash the ROM. And what TWRP did you use? Because this sounds like a Crash Dump which is common if you use the wrong Vendor Firmware.

DarthVader said:
Could you perhaps provide an image of Said Crash? And a couple more things. Which ROM were you trying to Flash. What was your OOS version before trying to Flash the ROM. And what TWRP did you use? Because this sounds like a Crash Dump which is common if you use the wrong Vendor Firmware.
Click to expand...
Click to collapse
Well, hopefully I won't crash again as I have to wait a day for the battery to train to fix the crash haha. It happened so far with RR and LineageOS. OxygenOS 9.0.13. And...
Woah. Just now seeing that my TWRP Zip file is 3.2.3-2 and Img file is 3.3.1-1. Perhaps that is the culprit?
EDIT: Nope! Just tried with TWRP 33.1-1, LineageOS 16 official build as of 1/11/2020. Included is a photo of the boot warning page, and apparently I can fastboot right now as well, but there's no particular information on either page that I can imagine is useful.
Boot warning
Fast boot
This time I also tried wiping the Dalvik. I also notice that on the bootloader unlocking directions it says to not update with partial OTAs (under 1GB) as this can cause a soft-brick. All of the ROMs I've been trying to flash are about 500mb. Is this the problem?

lynxon said:
Well, hopefully I won't crash again as I have to wait a day for the battery to train to fix the crash haha. It happened so far with RR and LineageOS. OxygenOS 9.0.13. And...
Woah. Just now seeing that my TWRP Zip file is 3.2.3-2 and Img file is 3.3.1-1. Perhaps that is the culprit?
Click to expand...
Click to collapse
It is. Always use the latest version of TWRP, OOS, Magisk, etc UNLESS said otherwise.

DarthVader said:
It is. Always use the latest version of TWRP, OOS, Magisk, etc UNLESS said otherwise.
Click to expand...
Click to collapse
I seem to have edited my last post without noticing your reply. Updated both copies of TWRP, img and zip, to the latest and still crashed. Though if you look at my last post there is one other potential, though I'm not sure what to do about it, I also uploaded pics.

This magic right here!!
After following the directions in this video, I have achieved a custom rom. RR is loading right now. It would seem the major difference is that I wasn't decrypting my data, which is included in this video.
Thanks again for sticking with me and being so patient. ?

lynxon said:
This magic right here!!
After following the directions in this video, I have achieved a custom rom. RR is loading right now. It would seem the major difference is that I wasn't decrypting my data, which is included in this video.
Thanks again for sticking with me and being so patient. ?
Click to expand...
Click to collapse
Hmm. Glad to know that you're up and running. If you don't mind, could you tell me what you did different when flashing this time? And how were you flashing before that lead to the bricks.

DarthVader said:
Hmm. Glad to know that you're up and running. If you don't mind, could you tell me what you did different when flashing this time? And how were you flashing before that lead to the bricks.
Click to expand...
Click to collapse
Basically it comes down to the directions here, which I used as a base, and the directions in this video.
The unlocking bootloader directions didn't have anything about installing a custom ROM, so I figured that once I had everything else set up: unlocked bootloader, TWRP, root, then all I had to do was go to "install" in TWRP and flash the new ROM, which had led to the crash with static at the bottom of my screen.
But then, when using the video tutorial, this guy did things in a particular way. The very first thing was decrypting the data, which I didn't know was necessary, but probably made the difference. This was done under "wipe" and then "format data" in TWRP. He also instructed on flashing the newest version of OxygenOS and TWRP twice, apparently this installed it under both A/B partitions. After installing the custom ROM he also wiped the "data" and "cache." Lots of steps in the video, I felt as if they didn't need to be done exactly the way he directed, but in this case I trusted his method and I'm glad I did.