Develop Bugs

[Q] HTC One x Bricked

Hello guys,
Yesterday I bricked my One x, I followed this section down here.
---------------------------------------------------------------------------------------------------------------------
Let's begin.
Download my toolkit from here.
http://forum.xda-developers.com/show...php?p=24972527
Extract the FOLDER to your C: drive or to your desktop.
MAKE SURE YOUR DIRECTORY DOES NOT HAVE A PERIOD OR SPACE.
Open One X.exe
So now you have my program open. Great.
On your phone, go to Settings -> Developer Options and Enable USB Debugging.
From my toolkit, Click 1. Install HTC Drivers.
After the drivers install, restart your computer.
After your computer loads up, open my toolkit and connect your phone to the computer. Your phone should now be recognized.
Now, click 2. Register at HTCDev. Register with a VALID email address and LEAVE the web browser open.
Now, under the commands section of my toolkit, press Boot into Bootloader.
You should have a nice, white, shiny screen that says FASTBOOT USB.
Click 3. Get Token ID. Look at the pop up and it will tell you how to get the Token ID.
Highlight where it says < < < < Identifier Token Start > > > > all the way to < < < < < Identifier Token End > > > > > and right click and it will automatically copy it.
Now, click Submit Token ID. Your web browser should now open a new tab. Scroll down and in the empty box, paste your Token ID. Press submit. HTCDev now emailed you your unlock token.
Your phone should still be in the bootloader. Now, go to the email address you registered to HTCDev and DOWNLOAD your unlock_code.bin. Press 5. Unlock Bootloader. Locate your unlock_code.bin and it will flash it to your phone.
READ the warning. THIS WILL WIPE ALL YOUR DATA FROM THE PHONE.
When you agree to it, press the volume up button and press the power button to accept it. Your phone will now restart.
When your phone loads up, go through the set up wizard. Then, on your phone, go to Settings -> Developer Options and Enable USB Debugging.------------------------------------------------------------------------------------------------------------------------------------
So far so good!
After that I try the permroot \/ only it wouldn’t work.
----------------------------------------------------------------------------------------------------------------------------------
Under the Extras section, press Perm Root. It will push SuperSU.zip to your phone.
Under commands, press Boot into Bootloader once again.
Now, it is time to flash a recovery.
TWRP (Team Win Recovery Project) is a custom recovery that will allow you to flash custom ROMs, Mods, etc.
CWM (ClockWorkMod) is a custom recovery that will allow you to flash custom ROMs, Mods, etc.
I recommend TWRP and we will use it for this tutorial,
Select TWRP and press Flash Recovery.
After it flashes, remove the USB cable and have HBOOT selected in bootloader. Press the power button and it will reload to another screen. Press the Volume Down button until you get to Recovery. Press the power button to select it.
Go to Backup and back up your boot and system partition. Always have a back up before you flash or do anything.
After that, go to Install and locate SuperSU.zip. Click it and slide the screen on the bottom to flash it. After it flashes, reboot the phone.
In your app drawer (your menu with all the apps), open SuperSU. If it says the binary needs to be updated, then update it. If it doesn't, then you are fully rooted!-------------------------------------------------------------------------------------------------------------------------------
So I Googled to antoher solution and found a UNROOT tool, stupid is I was, I tried id.
Now my phone only startup in the bootloader so this is maybe a good thing?
Is there anyone how has an idea to solve this problem? I hope someone can help me out .
Phone info:
***UNLOCKED***
Endeavoru PVT SHIP S-ON RL
HBOOT-1.39.000
Radio-5.1204.162A.29

Well if you can access the bootloader, then go into fastboot and run
fastboot earse cache
then flash the recovery (CWM Touch) again, make sure it's the latest version for your phone, so
fastboot flash recovery recovery.img
now reboot into recovery and do a factory reset/wipe data and dalvik and reboot...
if it boots up you are good to go, if not than try to restore your nandroid from recovery.
Now find and download the latest SuperSU.zip and move it is your sdcard.
Now once more go into your recovery and click on install zip and find supersu.zip, install and reboot

You can't brick hox that easy, relax and try to reflash recovery, boot.img and reset cache. If problem not solved you need to wipe data or even reflash rom one more time
Sent from my HTC One using Tapatalk 4

genocide_ru said:
You can't brick hox that easy, relax and try to reflash recovery, boot.img and reset cache. If problem not solved you need to wipe data or even reflash rom one more time
Sent from my HTC One using Tapatalk 4
Click to expand...
Click to collapse
The only good thing in being S-ON...
You can't f**k anything up.
Everything is easily fixable.

Thanks guys,
I'm a bit further at the moment, now looking for the right backup.

Same Problem, please HELP !!!
Good day Friends of the Forum
I have a problem and do not know how to fix it , I have navigate a lot in the network and I could not get my phone to work . I have HTC One X from AT&T. By playing around with the phone, accidentaly I delete the O.S. so right now my phone is locked . I can't load Origanal or Custom ROMS . The only thing I can do is enter the bootloader and install recovery ( TWRP ) I installed several versions of TWRP to install a custom rom or I locked the bootloader to install the original RUU and everything has been WITHOUT SUCCESS .
Right now I have S -ON , my HBOOT is 2.14 and I can install TWRP Recovery 2.6.0.0 or 2.6.3.0 .
I have read in many places that I have to make an S -OFF to install a Custom ROM , but all I get Tips that I need an OS runing to finish the installation (or modified to do the S -OFF) . What can I do if my S.O. is actuall blocked (brick). Only screen I got when I turned on or reboot my is the white screen " HTC quietly brillant" .
My friends , I request help from the wise in this range. Since I ran out of ideas. I attached pictures with my phone information
regards

eL_pIt said:
Good day Friends of the Forum
I have a problem and do not know how to fix it , I have navigate a lot in the network and I could not get my phone to work . I have HTC One X from AT&T. By playing around with the phone, accidentaly I delete the O.S. so right now my phone is locked . I can't load Origanal or Custom ROMS . The only thing I can do is enter the bootloader and install recovery ( TWRP ) I installed several versions of TWRP to install a custom rom or I locked the bootloader to install the original RUU and everything has been WITHOUT SUCCESS .
Right now I have S -ON , my HBOOT is 2.14 and I can install TWRP Recovery 2.6.0.0 or 2.6.3.0 .
I have read in many places that I have to make an S -OFF to install a Custom ROM , but all I get Tips that I need an OS runing to finish the installation (or modified to do the S -OFF) . What can I do if my S.O. is actually. Only screen I got when I turned on or reboot my is the white screen " HTC quietly brillant" .
My friends , I request help from the wise in this range. Since I ran out of ideas. I attached pictures with my phone information
regards
Click to expand...
Click to collapse
Unfortunately, you are in the wrong forum my friend.
This is the forum for the quad core version htc one x (endeavoru)
and yours sais evita in the bootloader.
Do not flash ANYTHING of these forums as they might brick your phone!!!

Stefan0vic said:
Unfortunately, you are in the wrong forum my friend.
This is the forum for the quad core version htc one x (endeavoru)
and yours sais evita in the bootloader.
Do not flash ANYTHING of these forums as they might brick your phone!!!
Click to expand...
Click to collapse
Thanks.
Have a nice day

:thumbup:
Sent from my HTC One X using xda app-developers app

Possibly bricked One X - need assistance!

Hey, everyone!
So within the past week or two my stock standard HTC One X started playing up, which I'm pretty sure was a result of a recent system update (to 4.2.2, from memory). My 'twilight' app (similar to f.lux but for phones) started randomly turning on and off for no reason, the screen became very rapidly unresponsive unless a great deal of force was applied or the phone was repeatedly locked and unlocked, it began to heat up (even more so than normal), etc, etc. Yesterday the unthinkable happened: it got stuck in a bootloop.
So here's how I wound up where I am right now.
I came to terms with the fact that I was going to lose all of my data (at least Google has automatically backed up my images and videos every few days), and anyone important enough to me that I need their phone number I also have on facebook/google plus or see frequently enough in person that when the issue is resolved I can add their numbers again. So I performed a factory reset hoping that would fix the problem. It didn't. Today, at the behest of a friend of mine, I decided to flash a custom ROM on my phone in an effort to salvage what was increasingly likely looking to be a $600 paperweight. I've never done this before, so I followed the instructions in the following video exactly as shown, and downloaded the latest stable version of Cyanogen mod for the One X. The video can be found by googling, "HTC One X - How To Root (in-depth)". It's the first result.
Everything went... well, not smoothly. But I got there in the end. Eventually the phone rebooted, and the blue (or cyan, I suppose) Cyanogen mod logo came up with the circular loading symbol tracing around it. It stayed this way for some 30 minutes or so. I decided to reboot the phone. Same issue again. I performed a factory reset, cleared the cache, cleared the Dalvik cache, and rebooted again. Still wouldn't pass the booting process. I cleared everything a second time and even reinstalled the update.zip (which for some reason appeared as update.zip.zip in ClockworkMod Recovery v5.8.2.7... I'm wondering if that caused some issue). Still no progress. Eventually, out of frustration, I began playing around with random settings within Clockwork Mod Recovery and tried backtracking a few steps computer-side in terms of the installation process, and somewhere along the way I've really F'd things up.
And here's the current situation.
Now, whenever the phone restarts the white HTC splash comes up, followed very quickly by a black screen which flickers momentarily, and then immediately jumps to ClockworkMod Recovery (v5.8.2.7).
Whereas earlier today both fastboot and adb recognised my device, now only fastboot will. I can't get anything to appear in the adb device list anymore. I'd prefer it if people didn't immediately scream, "DRIVER ISSUE!" considering adb worked for half of the day so it seems relatively unlikely to me that that's the problem.
My computer itself won't recognise that my phone is plugged in (probably because there's no OS anymore by the seems of things). I've tried two USB cables to no avail (the first worked earlier on this afternoon, so that shouldn't be an issue).
Within the 'choose zip from sdcard' section of ClockworkMod Recovery I can choose from (other than all of the files that were already in there):
CWN-SuperSU-v0.87.zip
update.zip.zip (the double file extension really bugs me)
'mount USB storage' within ClockworkMod Recovery gives me an erroy reading, E: Unable to open ums lunfile (No such file or di...) (runs off the screen, although presumably it just says no such file or directory exists).
I can't think of anything else that's relevant or would help troubleshoot this issue. If you need anymore info please just let me know and I'll do my best to supply it (you may have to lead me through the data acquisition process, however). I'm really hoping the phone isn't completely bricked because I don't exactly have the money right now to buy a new phone - I'm a uni student who only works part time and I just bought a car a few weeks ago. Bye bye, savings.
Regards,
Scott.

man, stupid question, did you flash the boot.img in the bootloader before or after flashing the rom?
if yes,
what cyanogen did you install?
cyanogen 10.2 should work with your recovery but cyanogen 11 needs a particular one
edit:did you make a backup (in the recovery) before flashing?

Want a working phone for now, follow this :
Download this recovery and flash it :
https://www.dropbox.com/s/qp21ubo10xetcvn/Philz recovery 5.15.9.img
Download a sense 5 rom like arhd or blade from the forum here. Copy the boot.img from the rom and flash that too. Then enter the recovery and mount the sdcard as a usb mass storage device and wait as long as it needs to pop up on the pc.
Copy the rom to the sdcard and then perform a full wipe
Factory reset
Wipe cache partition
Advanced - wipe dalvik cache
Mounts and storage - format cache, data and system
Then install the rom.zip and reboot.

Husky34 said:
man, stupid question, did you flash the boot.img in the bootloader before or after flashing the rom?
if yes,
what cyanogen did you install?
cyanogen 10.2 should work with your recovery but cyanogen 11 needs a particular one
edit:did you make a backup (in the recovery) before flashing?
Click to expand...
Click to collapse
I flashed SOME .img file, but not one called 'boot.img'. Can't remember when, unfortunately. If you find the youtube video I mentioned I followed that exactly.
No recovery unfortunately. I saw no point given that the phone was almost unusable in any form prior to me getting Cyanogen installed (it was constantly and randomly rebooting). Probably a mistake in retrospect.
Version 10.2, by the way.
Mr Hofs said:
Want a working phone for now, follow this :
Download this recovery and flash it :
Download a sense 5 rom like arhd or blade from the forum here. Copy the boot.img from the rom and flash that too. Then enter the recovery and mount the sdcard as a usb mass storage device and wait as long as it needs to pop up on the pc.
Copy the rom to the sdcard and then perform a full wipe
Factory reset
Wipe cache partition
Advanced - wipe dalvik cache
Mounts and storage - format cache, data and system
Then install the rom.zip and reboot.
Click to expand...
Click to collapse
Can you walk me through it step-by-step. Again, I'm a total noob to this and I DON'T want to stuff this up again. Is the fact that adb (or my PC in general) isn't recognising my phone going to make this difficult? I mean how am I meant to copy anything to the SD card if I can't access it through windows explorer or via adb push?!

You need fastboot. Rename my linked recovery to just recovery.img and flash it :
Fastboot flash recovery recovery.img
Fastboot erase cache
Flash the boot.img from the rom :
Fastboot flash boot boot.img
Fastboot erase cache
Then enter the recovery and follow earlier given steps

Mr Hofs said:
You need fastboot. Rename my linked recovery to just recovery.img and flash it :
Fastboot flash recovery recovery.img
Fastboot erase cache
Flash the boot.img from the rom :
Fastboot flash boot boot.img
Fastboot erase cache
Then enter the recovery and follow earlier given steps
Click to expand...
Click to collapse
This seems to work at first - instead of jumping into ClockworkMod Recovery, after flashing the image file you gave me, it jumps into a new recovery mode. But after rebooting and going into recovery mode again it's back to ClockworkMod Recovery (I made sure to clear the cache).

You mean the old cwm. The new one is cwm based and looks just like it. If it's flashed it can't be gone without flashing something else as a recovery !

Mr Hofs said:
You mean the old cwm. The new one is cwm based and looks just like it. If it's flashed it can't be gone without flashing something else as a recovery !
Click to expand...
Click to collapse
Oh. Well it looks different the first time I boot into recovery versus the second time (PhilZ Touch 5 with a distinct purple background the first time, but the second time it goes back to a black background with blue text).
Not really sure how to proceed from here. Battery is dropping fast (9%) despite being plugged in, so I'm worried if I don't fix this ASAP it'll be forever FUBAR.

The old one does not support charging. Try flashing philz again and keep it in there and charge it up as Philz does enable charging in recovery.
If you use Fastboot flash recovery command the old one is gone.....can't come back like that !

Mr Hofs said:
The old one does not support charging. Try flashing philz again and keep it in there and charge it up as Philz does enable charging in recovery.
Click to expand...
Click to collapse
Mr Hofs, you sir are a gentlemen and a scholar! I have managed to get back to the initial bootscreen for Cyanogen mod. AND SUCCESS! IT JUST PASSED THAT SCREEN AS I WAS TYPING!
I am indebted to you, you glorious man! Thank you so very much I'll keep you guys posted (for better or worse)!

Hope it will be fine. I will keep an eye out here

Mr Hofs said:
Hope it will be fine. I will keep an eye out here
Click to expand...
Click to collapse
So I tried updating the camera (?) as a suggested update after getting back into my phone, and it's already stuffed up again. It rebooted and said that root access has possibly been lost. What's happening now?

Doesn't appear to be a big issue for now, actually. Reset, not caused any problems since then! Managed to get google apps working, and downloaded a bunch of the apps I need All's well!
Thanks one again!

Alright ! Hope i don't see you here again

Hi all - I have been searching these threads for hours and hope I can bother for some assistance. I too have soft bricked, I went to install Android Revolution HD 33.1 but missed a step. I am currently Tampered, unlocked, and S-On. I have TWRP v2.5.0.0. When I mount the sd card in TWRP, and try to copy files over, I get a message from the PC to format the sd card - I didn't for fear of wiping out everything and hardbricking the phone. I am a noob when it comes to using commands/fastboot to copy files over. I am sorry to ask, but can someone please help me with exactly what to type?
Oh - and do I need to use philz recovery since I have TRWP installed and can access?

darule_2011 said:
Hi all - I have been searching these threads for hours and hope I can bother for some assistance. I too have soft bricked, I went to install Android Revolution HD 33.1 but missed a step. I am currently Tampered, unlocked, and S-On. I have TWRP v2.5.0.0. When I mount the sd card in TWRP, and try to copy files over, I get a message from the PC to format the sd card - I didn't for fear of wiping out everything and hardbricking the phone. I am a noob when it comes to using commands/fastboot to copy files over. I am sorry to ask, but can someone please help me with exactly what to type?
Oh - and do I need to use philz recovery since I have TRWP installed and can access?
Click to expand...
Click to collapse
TAMPERED ? what does your hboot say :
1: ENDEAVORU
2: EVITA

Mr Hofs said:
TAMPERED ? what does your hboot say :
1: ENDEAVORU
2: EVITA
Click to expand...
Click to collapse
EVITA PVT SHIP S-ON RL
HBOOT-1.14.0002
Radio-0-19as.32.09.11_2

As i thought. You are in the very wrong forum. Head over to the HTC ONE XL forum....AT&T .....

Mr Hofs said:
As i thought. You are in the very wrong forum. Head over to the HTC ONE XL forum....AT&T .....
Click to expand...
Click to collapse
uh oh, that doesn't sound good for me...I don't have the XL version, just the one X. Will that matter? Did I flash this baby using files for the XL when I should have used something else?

No you don't read well. You have the HTC one XL (EVITA) and this forum is for the ENDEAVORU HTC one X international version.
We here have the quad core and you there have the dual core phone !

Soft brick help (HTC M9)

Hi guys – hoping you can help me following an issue with my M9 I bought a couple of days ago. Last night I unlocked the bootloader with HTC dev, rooted with TWRP/SuperSU, S-OFF’ed with SunShine, updated firmware to 1.40.401.5 per matanlevanon‘s thread, then flashed MaximusHD.
Up until the last step, everything went well – but I’m now stuck in boot loops. I can currently access both Download Mode and bootloader; but trying to launch recovery gets as far as the TWRP splash screen before my phone reboots again.
I've reflashed TWRP.img using fastboot; but when rebooting into recovery I still have the same result (TWRP splash screen before my phone reboots again)
I've also lost ABD - in Download Mode/bootloader, Windows Device Manager see’s my phone without issue and correct drivers – but ADB server doesn’t recognise my phone.
I’ve tried everything from HTC Sync bundled drivers, PdaNet drivers to generic ADB drivers – but ADB seems to refuse to see my phone regardless of what I try.
Seemingly if I can get a working recovery image / TWRP on and working I can wipe and try to flash again, but current images don't seem to be helping. Any suggestions / help please?

Got it, cache partition was corrupted! fastboot erase cache let me get back into TWRP and reflash my ROM.
Fingers crossed it's smooth sailing from here

Phone soft bricked after applying software updates

Hello.
The other night I applied 3 software updates to Android and ended up with an unusable phone. The updates (I assume) were like this: http://forum.xda-developers.com/tmobile-htc-one-m8/help/3-software-updates-t3268014
After the phone rebooted a couple times, it got stuck at the white HTC logo screen (I ended up falling asleep and the phone was like the after waking up, so stuck for about 6 hours) and wouldn't respond to just holding the power button. I had to hold power + vol up to get it to restart. After restarting it now boots to a black screen. It is possible to get to HBOOT and TWRP but I can't get adb to recognize it anymore so I'm not sure how to go about getting fixes on the phone.
The phone was running a custom recovery (clockwork recovery) and rooted. I then tried to get it back to stock to apply the Android 5.0 RUU and then used TWRP without flashing the recovery to root the phone again. My guess is that something about that process might have messed with something that one of the software updates was updating.
So, I have two questions:
1. Is it possible to recover files (pictures, for exampl) off the internal sd? Like I said, I cannot get adb (or windows) to recognize the phone, though it does show in the windows device manager.
2. If it's not possible to get recover those files, how can I get the phone usable at all?

Can you get it into the boot loader?

Yes, luckily I can get to the bootloader.

hatbocs said:
Yes, luckily I can get to the bootloader.
Click to expand...
Click to collapse
If so once in the bootloader can you use something like:
fastboot boot twrp-2.8.7.0.img
to boot into twrp? (note twrp-2.8.7.0.img is the filename of the twrp image that I saved it as, yours might be different)
If you can boot into twrp then you can install a rom/backup. also you could use, I think, something like "fastboot flash recovery twrp-2.8.7.0.img" as well.
-brad

I'm at work so I can't test this again to make 100% sure but if fastboot works like ADB then my phone doesn't show.
I do currently have TWRP installed however windows does not see the phone.

So if twrp works, you should be able to use that to connect to your pc. If not go and buy an OTG usb drive. Copy a Rom onto it, and then connect it to your phone. One time I messed my phone up and I used this method.

Worth a try. I'm in the middle of moving and that box of stuff isn't in this house. So I'll have to wait to report back. Thanks for the help so far.

Stuck on team win recovery project please help

I have no idea how to root or anything like that, I bought this oneplus 3 and had a update a week later.. so when I did the software update it took me into teamwin recovery mode and now I don't know how to get back into my phone please help....

Did you buy the phone second hand or did you try to flash TWRP yourself? It shouldn't have TWRP installed by default.
Regardless, you can use TWRP to flash the latest update.
Given that you have TWRP, I'm assuming that you have an unlocked bootloader. Did you notice a warning pop up everytime you reboot your phone before? It should say something along the lines of "your device has been unlocked and can't be trusted". If not, you'll have to unlock it (it wipes your phone in the process).
If the bootloader is unlocked, you can simply download and flash the latest zip for OOS 4.0.3 in TWRP. This will update you phone and replace TWRP with the stock recovery (so you don't run into this problem again in the future when installing an OTA). If you don't intend to modify your phone in any way, then this is all you need to do, your phone should be functional.
There are plenty of threads with detailed guides on how to do all of this.

I'm also stuck on TWRP after stupidly downloading the latest OTA and I don't know what to do!
Phone won't boot normal, just goes off.
Situation:
- Bootloader, Fastboot and TWRP wil load.
- Device seen by windows
- Zip install in TWRP gets stuck at 'patching zip unconditiontally'
- Another zip flashes, but gets stuck at the end, no reboot option (manually but that's not the way)
Can someone please point me in the right direction? I don't care if I lose data, just want my phone back!
not helping:
Saying i'm a dipsh-t I know, I know, I will do better in the future, for now, help a brother out please

sndr1384 said:
I'm also stuck on TWRP after stupidly downloading the latest OTA and I don't know what to do!
Phone won't boot normal, just goes off.
Situation:
- Bootloader, Fastboot and TWRP wil load.
- Device seen by windows
- Zip install in TWRP gets stuck at 'patching zip unconditiontally'
- Another zip flashes, but gets stuck at the end, no reboot option (manually but that's not the way)
Can someone please point me in the right direction? I don't care if I lose data, just want my phone back!
not helping:
Saying i'm a dipsh-t I know, I know, I will do better in the future, for now, help a brother out please
Click to expand...
Click to collapse
Simple, check the OnePlus D/L sites for this one http://oxygenos.oneplus.net.s3.amazonaws.com/recovery_op3.img and flash it by TWRP or fastboot to RECOVERY. Boot once with the official Recovery and all ist fine again.

This is issue of using a faulty twrp so for that when ur phone us booting up go to fastboot and flash twrp 3.0.4-1 and everything will work

emuandco said:
Simple, check the OnePlus D/L sites for this one http://oxygenos.oneplus.net.s3.amazonaws.com/recovery_op3.img and flash it by TWRP or fastboot to RECOVERY. Boot once with the official Recovery and all ist fine again.
Click to expand...
Click to collapse
Similar Problem here:
just wanted to flash latest OOS 4.0.3, so I flashed back stock recovery with flashify and rebooted into recovery mode to flash the already downloaded OOS 4.0.3. zip. That's when it began to go poop! After rebooting it just went dark with no Chance to power it on again! No dice with power button, Volume up/down + power button, nothing! Not even the LED's are blinking when plugged in. So this one seems to be basically dead!
I got it once booting again after randomly pushing the buttons (after x minutes!?), but everytime I reboot the phone it just shuts off without beeing able to power it on again. At the Moment it's dead!
Any ideas what might happened? If I get it on again, should I immediately reset it to factory Settings?
I am kinda lost here! Any help/ideas would be much appreciated!

Flashify? Never used it and never trusted apps which flash stuff on a running system. Use fastboot and reflash the recovery partition. Link to recovery is in my former post.
fastboot flash recovery PATHTOIMGFILE

Thank you for your advice! Still a lot to learn! Got it up again, will try as you suggested!

It appeared that my stock recovery file was corrupted , but all is fine again! Thank you very much!

Mannycolon85 said:
I have no idea how to root or anything like that, I bought this oneplus 3 and had a update a week later.. so when I did the software update it took me into teamwin recovery mode and now I don't know how to get back into my phone please help....
Click to expand...
Click to collapse
I may have been the person you traded with to get the OnePlus 3, but I took the phone back and after 5 hours I got it up and running.
The phone would boot to TWRP, but even after wiping the entire system and dragging a ROM zip to the internal storage, reinstalling did nothing. It just kept booting back to recovery.
The solution entailed the following.
Download stock recovery IMG. Flashed through TWRP. Rebooted recovery and now was back to stock recovery.
Download the official OxygenOS ROM zip from the OnePlus website and changed the name to update.zip
Next I downloaded Android studio for access to ADB. I had never used ADB before, but I knew this was needed to push a file to the phone.
Needless to say, ADB kept freezing my computer when I would type in the commands to side load.
I deleted Android studio and installed a minimal ADB/Fastboot I found online. I opened my command prompt, typed the command for sideloading, and immediately got my installation starting. It took about 10 minutes to fully install. When it was finished, I rebooted and had a fully functioning OnePlus 3
Sent from my ONEPLUS A3000 using Tapatalk