Database Develop

[SOLVED] Crap! Phone stuck on HTC logo, accidentally did a full delete from recovery.

I ****ed up. I accidentally deleted everything from the bootloader menu. I was just about to flash a ROM onto the phone and forgot about it not having an SD card so all the internal data was wiped.
The phone is now always on and stuck on the green HTC logo with quietly brilliant written underneath.
Just before this the bootloader was unlocked and the phone was S-OFF. When I plug the phone into my PC it does not get recognized. Is there anything I can do via fastboot or adb to get something back onto the phone? I can't access recovery because it's stuck on the logo. Sometimes when I hold the power button the screen will go black but moments later it will go back to the HTC logo. I assume I'm in some sort of bootloop but I have no idea.
Is there anything I can do? This is an absolute nightmare.
I've tried fastboot reboot-bootloader but that says < Waiting for device >.
I appreciate any help you can give. Thanks in advance.
Edit: I just got into recovery. Don't want to lose my chance, what should be my next step?

Sideload a Rom and install it! You use TWRP?
Sent from my M8

RED_ said:
Edit: I just got into recovery. Don't want to lose my chance, what should be my next step?
Click to expand...
Click to collapse
Yes, you should install now with sideload. In TWRP under "Advanced" in CWM based recoveries under install zip/from sideload
But if there is no connection between ADB and your device it won't work.
Wait for a minute when it is connected and maybe the driver will get re-installed so sideload might work then.
tetakpatalked from P5110

Toxicology said:
Sideload a Rom and install it! You use TWRP?
Sent from my M8
Click to expand...
Click to collapse
tetakpatak said:
Yes, you should install now with sideload. In TWRP under "Advanced" in CWM based recoveries under install zip/from sideload
But if there is no connection between ADB and your device it won't work.
Wait for a minute when it is connected and maybe the driver will get re-installed so sideload might work then.
tetakpatalked from P5110
Click to expand...
Click to collapse
Yes I'm using TWRP.
I did a sideload of a Paranoid Android ROM. After it completed I tried a reboot but the device still warns me that there is no OS installed so I haven't done it yet. Although it said the install completed I'm worried it may not have as a result of this message.

Ok rebooting did in fact boot into the ROM. All is well.
I love you all.

It's stories like this that keep giving us beginners the courage to continue trying new things. This forum has to be one of the friendliest I've found.
Sent from my HTC One using Tapatalk

Nexus 6 - Can't boot TWRP recovery

I was trying to fix an issue with my phone the other day, and saw that re-locking the bootloader might fix it. Nobody mentioned anything about it completely wiping the phone, including the internal SD card. I set most of the stuff back up again but realized that it was suffering from the bug on the old radio version that causes it to lose LTE randomly.
I went and rebooted into TWRP to try and flash it, and TWRP showed a completely empty sdcard partition and said it could not mount '/data'. I enabled "require pattern to boot," thinking it may not have known to decrypt the partition without that, and now I can't get into TWRP at all. I tried disabling the "require pattern to boot" option again but no luck. It shows the "Google" logo for about 5 seconds, then the blue "TEAMWIN" logo for about 3 seconds, then reboots to the "Google" logo and proceeds to boot normally. I should note that I have CM12.1 installed, and the latest TWRP. I've tried reflashing TWRP and that didn't help; I also did "fastboot format cache" and then "fastboot flash cache cache.img" using the stock factory cache.img. I got the radio flashed using fastboot, but I'd really like to have a working recovery.

briman0094 said:
I was trying to fix an issue with my phone the other day, and saw that re-locking the bootloader might fix it. Nobody mentioned anything about it completely wiping the phone, including the internal SD card. I set most of the stuff back up again but realized that it was suffering from the bug on the old radio version that causes it to lose LTE randomly.
I went and rebooted into TWRP to try and flash it, and TWRP showed a completely empty sdcard partition and said it could not mount '/data'. I enabled "require pattern to boot," thinking it may not have known to decrypt the partition without that, and now I can't get into TWRP at all. I tried disabling the "require pattern to boot" option again but no luck. It shows the "Google" logo for about 5 seconds, then the blue "TEAMWIN" logo for about 3 seconds, then reboots to the "Google" logo and proceeds to boot normally. I should note that I have CM12.1 installed, and the latest TWRP. I've tried reflashing TWRP and that didn't help; I also did "fastboot format cache" and then "fastboot flash cache cache.img" using the stock factory cache.img. I got the radio flashed using fastboot, but I'd really like to have a working recovery.
Click to expand...
Click to collapse
no working recovery with a locked bootloader, sorry. if the bootloader is locked, you cant flash anything. its locked. to flash things, you need an unlocked bootloader. its like locking a door, but expecting it to open magically when you walk up to it.

simms22 said:
no working recovery with a locked bootloader, sorry. if the bootloader is locked, you cant flash anything. its locked. to flash things, you need an unlocked bootloader. its like locking a door, but expecting it to open magically when you walk up to it.
Click to expand...
Click to collapse
I forgot to mention that I re-unlocked the bootloader. I can also boot the OS so I'd be able to enable OEM unlock again if needed.

briman0094 said:
I forgot to mention that I re-unlocked the bootloader. I can also boot the OS so I'd be able to enable OEM unlock again if needed.
Click to expand...
Click to collapse
important thing to forget to mention

So what happened when you reflashed the lasted version of twrp for your device after verifying the downloads md5?

simms22 said:
important thing to forget to mention
Click to expand...
Click to collapse
I guess I assumed that when I said "continues to boot normally" people would assume I could re-enable "OEM Unlock" if needed
scryan said:
So what happened when you reflashed the lasted version of twrp for your device after verifying the downloads md5?
Click to expand...
Click to collapse
All the console output indicates success, and it boots to the initial "TEAMWIN" logo for a few seconds and reboots.

No Recovery Similiar issue
briman0094 said:
I was trying to fix an issue with my phone the other day, and saw that re-locking the bootloader might fix it. Nobody mentioned anything about it completely wiping the phone, including the internal SD card. I set most of the stuff back up again but realized that it was suffering from the bug on the old radio version that causes it to lose LTE randomly.
I went and rebooted into TWRP to try and flash it, and TWRP showed a completely empty sdcard partition and said it could not mount '/data'. I enabled "require pattern to boot," thinking it may not have known to decrypt the partition without that, and now I can't get into TWRP at all. I tried disabling the "require pattern to boot" option again but no luck. It shows the "Google" logo for about 5 seconds, then the blue "TEAMWIN" logo for about 3 seconds, then reboots to the "Google" logo and proceeds to boot normally. I should note that I have CM12.1 installed, and the latest TWRP. I've tried reflashing TWRP and that didn't help; I also did "fastboot format cache" and then "fastboot flash cache cache.img" using the stock factory cache.img. I got the radio flashed using fastboot, but I'd really like to have a working recovery.
Click to expand...
Click to collapse
Briman, I seem to have a similar issue on my and wife's Google Nexus 6s. I unlocked and rooted using Wug Tool Kit I used in years past with seamless success. To confirm root CM 12.1 I can get into bootloader, Teamwin. From there I am to flash the Superuser, Busybox and TWRP zips under SD\iReady to Flash\Rootfiles..... Only I am not given an option on the menu? I am struggling with using the command prompt and proper paths from SDK Tools so that is not an option at this moment. I see a File Manager that shows this path but am hesitant to use it as I have READ this could cause damage ( brick) to the system. Watching your thread for answers or possibilities. I know the senior members as Simm22 dislike tool kits and so do I. I am simply trying to grow and learn.

ray6279 said:
Briman, I seem to have a similar issue on my and wife's Google Nexus 6s. I unlocked and rooted using Wug Tool Kit I used in years past with seamless success. To confirm root CM 12.1 I can get into bootloader, Teamwin. From there I am to flash the Superuser, Busybox and TWRP zips under SD\iReady to Flash\Rootfiles..... Only I am not given an option on the menu? I am struggling with using the command prompt and proper paths from SDK Tools so that is not an option at this moment. I see a File Manager that shows this path but am hesitant to use it as I have READ this could cause damage ( brick) to the system. Watching your thread for answers or possibilities. I know the senior members as Simm22 dislike tool kits and so do I. I am simply trying to grow and learn.
Click to expand...
Click to collapse
na, toolkits work fine. sure, they occasionally do mess up, but its not very ofver. i generally like ut when noobies do the rooting the correct way the first time, that way they can learn some basic things about how everything works. then, they can yse toolkits all they
btw, teamwin isnt your bootloader, its your recovery. team win = twrp. now all you need to do is download the latest supersu and flash it via your recovery, and the you can install a busybox app from tbe play store, and use it to unstall .

briman0094 said:
I was trying to fix an issue with my phone the other day, and saw that re-locking the bootloader might fix it.
Click to expand...
Click to collapse
Saw that bit of advice where? I can't think of a single thing re-locking the bootloader would fix.

nhizzat said:
Saw that bit of advice where? I can't think of a single thing re-locking the bootloader would fix.
Click to expand...
Click to collapse
A screenshot of an e-mail from a Google employee regarding Android Pay and SafetyNet.

50% JOY No Fastboot?
simms22 said:
na, toolkits work fine. sure, they occasionally do mess up, but its not very ofver. i generally like ut when noobies do the rooting the correct way the first time, that way they can learn some basic things about how everything works. then, they can yse toolkits all they
btw, teamwin isnt your bootloader, its your recovery. team win = twrp. now all you need to do is download the latest supersu and flash it via your recovery, and the you can install a busybox app from tbe play store, and use it to unstall .
Click to expand...
Click to collapse
I followed your directions while working on my Nexus6 phone. Was able to access bootloader then install iReady files. Worked perfectly and phone loaded SUPERUSER, BUSYBOX & PERM RECOVERY. Not so much on wife's Nexus 6. I get thru UNLOCK & ROOT w/custom recovery on the Wug Fresh Tool Kit. At RECOVERY menu pulls up SD - Up one level. No option is allowed to continue on and load the three mentioned packages. I then able to reboot to system. Does it appear I am bootloading but not fastbooting? Will try and insert images.

ray6279 said:
I followed your directions while working on my Nexus6 phone. Was able to access bootloader then install iReady files. Worked perfectly and phone loaded SUPERUSER, BUSYBOX & PERM RECOVERY. Not so much on wife's Nexus 6. I get thru UNLOCK & ROOT w/custom recovery on the Wug Fresh Tool Kit. At RECOVERY menu pulls up SD - Up one level. No option is allowed to continue on and load the three mentioned packages. I then able to reboot to system. Does it appear I am bootloading but not fastbooting? Will try and insert images.
Click to expand...
Click to collapse
one question.. what is perm recovery?? the only recovery that works on the n6 is twrp recovery.
and when you are in her recovery, is it showing you the right location where the files should be? if nit, you csn change the lication.

Simm & Others. Thank you for your good words and suggestions. It would be easier for me to list what I did not attempt rather than what I did try. . I tried nearly most functions in the Wug Fresh ( by Harold) v2.0.5 after failing to find the correct command prompt to use ADB. What happened is an odditity. Mind you, I've been on these two Nexus 6 phones for 4-6hours a day for about ten days! Day later, Happened to be waiting for wife in parking lot and picked up phone and pressed SuperUser. Viola! It went into TWRP and gave me an RECOVERY option. On impluse, I flashed TWRP and Superuser zips. It took and processed. however, the best part of this is the hands on learning experience of booting, flashing, wiping, language, terms, SDK, Android and more. Once I figure out my path problem on my windows based PC to loading ABD commands I am continuing my self study of Android and App development. How do I get the packages out of the SDK Tool Kit to folders in PC? Thanks all.

ray6279 said:
Simm & Others. Thank you for your good words and suggestions. It would be easier for me to list what I did not attempt rather than what I did try. . I tried nearly most functions in the Wug Fresh ( by Harold) v2.0.5 after failing to find the correct command prompt to use ADB. What happened is an odditity. Mind you, I've been on these two Nexus 6 phones for 4-6hours a day for about ten days! Day later, Happened to be waiting for wife in parking lot and picked up phone and pressed SuperUser. Viola! It went into TWRP and gave me an RECOVERY option. On impluse, I flashed TWRP and Superuser zips. It took and processed. however, the best part of this is the hands on learning experience of booting, flashing, wiping, language, terms, SDK, Android and more. Once I figure out my path problem on my windows based PC to loading ABD commands I am continuing my self study of Android and App development. How do I get the packages out of the SDK Tool Kit to folders in PC? Thanks all.
Click to expand...
Click to collapse
your welcome, but you are still off in one bit of fact. you use fastboot, not adb, to flash a recovery(and system.img)
edit.. you can use apps like flashify to flash recovery, if you have root already.

So BOOTLOADER is the USB connection between the device and PC. FASTBOOT is the process via we make changes in the device via the PC. ADB is the device language via which we communicate. So do I still need to flash a system recovery image? Flashify App? I already went thru install>iready to flash> superuser (version)>busybox>flash>reboot>system. I'm going cross eyed from reading. The wiping part worries me as I fear formatting or deleting essential data.

ray6279 said:
So BOOTLOADER is the USB connection between the device and PC. FASTBOOT is the process via we make changes in the device via the PC. ADB is the device language via which we communicate. So do I still need to flash a system recovery image? Flashify App? I already went thru install>iready to flash> superuser (version)>busybox>flash>reboot>system. I'm going cross eyed from reading. The wiping part worries me as I fear formatting or deleting essential data.
Click to expand...
Click to collapse
ok, when wiping, dont do the first option wipe, itll wipe your whole phone clean. you need to select the advanced options and pick what you want wiped. fastboot is the way to unlock your bootloader, or flash a recovery. also, you use it to flash a system.img or any part of it.
adb is a general linux that can be used with android, anywhere but in the bootloader(only fastboot in the bootloader).
bootloader isnt the usb connection between the device and the pc, its part of the phone that boots it and decides if the rom is safe to run. thats why we unlock it. so we can flash roms eithout googles key.
fastboot is the tool that you use to do whatever needs to be fone in the bootloader, adb everywhere else.
a recovery you need if you want to flash custom roms, kernels, supersu, or other mods. you can also wipe different partitions with the recovery, or make a "nandroid' backup. thats a bavkup of everything. its like a complete snapshot of everything during the time you made it. if you ever mess up your phone, you can restore it, and you will be at the exact same place when you made the backup.
anything else?

Help with Nexus 6 possible Brick

Alright I am looking for some help here. I was attempting to unroot to update my Nexus 6 to Android M. Not sure how this happened but here it goes. I can boot the phone into recovery TWRP and into boot loader but the OEM is locked....In recovery I have no backups or ROMs o flash and my mac is not connecting with the Nexus 6. It seems like there is no ROM on the phone at all and I cant use Terminal commands I keep getting Failures. I have run the 1 click root and unroots for mac and still nothing. I also have no access to Developer options since I cant load into a ROM...So I cant select allow OEM unlock... Please let me know if there is anything I can do to fix this. Thanks for your help everyone!

Try to uninstall all drivers then re install to see if mac recognizes your phone then sideload a rom to recovery or adb

Had this before. I believe when connecting to your computer, you have to delete every nexus 6 previous connections so it would be as if your phone never connected to your computer before. Then after you do that, it should install drivers and recognize your phone. I'm not sure if I remember correctly but I believe its from your toolbar on your computer where it normally pops up "eject USB " warnings. Sorry if I couldn't help

Delete all drivers relating to Android. Download and install the Android SDK Tools from Google. Update the SDK and install the Google USB driver. Boot into TWRP, connect the N6, then use adb push rom.zip /sdcard.
I think that should work.

or fastboot wipe user data and cache.

nhizzat said:
Delete all drivers relating to Android. Download and install the Android SDK Tools from Google. Update the SDK and install the Google USB driver. Boot into TWRP, connect the N6, then use adb push rom.zip /sdcard.
I think that should work.
Click to expand...
Click to collapse
I have been working on this since last night 7pm... I tried adb push and it just sits there and says starting adb sideload for about 10 min then vibrates with a cancellation. I tried removing Android File Transfer and reinstalling it and I still get the can not find device error. Im thinking this might be a loosing battle.

simms22 said:
or fastboot wipe user data and cache.
Click to expand...
Click to collapse
I did both of these to get past the TWRP boot loop. I can get into TWRP but its empty like everything has been wiped I have no backups or ROMs to flash to. Since the OEM is locked and I cant launch into a ROM to select allow OEM unlock it seems like im going to inevitably lose this battle. Last resort I have a friend coming over with Windows (hoping) WUGfresh can solve the issues....

ibaldwin85 said:
I did both of these to get past the TWRP boot loop. I can get into TWRP but its empty like everything has been wiped I have no backups or ROMs to flash to. Since the OEM is locked and I cant launch into a ROM to select allow OEM unlock it seems like im going to inevitably lose this battle. Last resort I have a friend coming over with Windows (hoping) WUGfresh can solve the issues....
Click to expand...
Click to collapse
did you have any roms on your phone before all this? if you did, did you try to search if they are in a different location in your storage now?

Do you have access a a Windows machine? NRT has an option to reflash a bricked phone. Never bricked mine but that tool has been awesome otherwise.

snatale1 said:
Do you have access a a Windows machine? NRT has an option to reflash a bricked phone. Never bricked mine but that tool has been awesome otherwise.
Click to expand...
Click to collapse
he has no rom and bootloader locked. nrt cant do anything.

simms22 said:
he has no rom and bootloader locked. nrt cant do anything.
Click to expand...
Click to collapse
But if he has TWRP......he can transfer a ROM from the PC and flash it......

paclaco said:
But if he has TWRP......he can transfer a ROM from the PC and flash it......
Click to expand...
Click to collapse
absolutely! and he knows he can do that, but he had no access to a computer(he wrote that his friend is gonna come over with one though).

snatale1 said:
Do you have access a a Windows machine? NRT has an option to reflash a bricked phone. Never bricked mine but that tool has been awesome otherwise.
Click to expand...
Click to collapse
All due respect to the developer, but all WUg's NRT does is automate the downloading and the commands you use to flash manually. It doesn't do anything "special"

simms22 said:
absolutely! and he knows he can do that, but he had no access to a computer(he wrote that his friend is gonna come over with one though).
Click to expand...
Click to collapse
True, but have a Mac, and it is rare that being in recovery and connected to the Mac, do not recognize ....
then wait a Windows computer then ....

FIX! we got it!
Thanks for all the responses guys! We spend another 4 hours on this Sunday and finally got it! We ended up using this forum step by step. http://forum.xda-developers.com/nexus-6/help/info-nexus-6-nexus-9-enable-oem-unlock-t3113539
While my friend was installing all of the ADB drivers on his PC I attempted the steps on my mac. It made it through the first to lines of code but when rebooting into Boot loader it came back with a fail notice to unlock the OEM.
When he got all drivers installed we used the same lines of code (modifying C: for the location he had the ADB drivers) and it accepted all codes. Seeing that screen change into the OEM unlock select yes screen was a GREAT moment lol. After that we used NRT to flash Marshmallow...
All in all it was fun trying to figure this out! Not so much fun thinking I had to drop another $300 to get a new phone! Again thanks everyone for the help!

BladeRunner said:
All due respect to the developer, but all WUg's NRT does is automate the downloading and the commands you use to flash manually. It doesn't do anything "special"
Click to expand...
Click to collapse
Agreed, but its convenient as all hell.
Sent from my Nexus 6 using Tapatalk

Phone bricked after an OTA update

Sorry, I didn't know where to post this, but okay; I've installed an Oxygen OS update two days ago and I've had my phone rooted, my phone has been bricked since. Whenever I enter the bootloader my device isn't detected anymore by my laptop therefore I can't re-flash TWRP and now I'm completely stuck and don't know what to do, any help please?

u_ser_n_a_m_e said:
Sorry, I didn't know where to post this, but okay; I've installed an Oxygen OS update two days ago and I've had my phone rooted, ever since my phone has been bricked, whenever I enter the bootloader my device isn't detected anymore by my laptop therefore I can't re-flash TWRP and now I'm completely stuck and don't know what to do, any help please?
Click to expand...
Click to collapse
You're best bet would be to download the full OOS OTA and then ADB Sideload the OTA.
You should find all the files you need on*
http://downloads.oneplus.net/
First, you download the full OOS ROM and the stock recovery for Nougat.
Then you flash the stock recovery (fastboot flash recovery <file name>).
Then you boot into recovery and select "install from USB" to get into sideload mode.
And finally you sideload the latest OOS (ADB Sideload <filename>).
It will take some time, but your phone should work after it.
FYI, keep in mind that you'll have to manually flash updates when using a custom recovery
Hope this does the trick for ya!
Good luck and happy flashing!
Sent from my SM-G955U using XDA-Developers Legacy app

u_ser_n_a_m_e said:
Sorry, I didn't know where to post this, but okay; I've installed an Oxygen OS update two days ago and I've had my phone rooted, my phone has been bricked since. Whenever I enter the bootloader my device isn't detected anymore by my laptop therefore I can't re-flash TWRP and now I'm completely stuck and don't know what to do, any help please?
Click to expand...
Click to collapse
Assuming you have ADB on your laptop, does the command "adb devices" list your device?
I think your problem may have been caused by attempting an OTA update while using a custom recovery. I have learned this is not recommended.
Try and connect with ADB and if you can follow the instructions to sideload given by the other member
You may also like to check this thread
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306

dave457 said:
Assuming you have ADB on your laptop, does the command "adb devices" list your device?
I think your problem may have been caused by attempting an OTA update while using a custom recovery. I have learned this is not recommended.
Try and connect with ADB and if you can follow the instructions to sideload given by the other member
You may also like to check this thread
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Click to expand...
Click to collapse
It only lists my device when I'm in the booting process. Everywhere else, it does not

Use the usual Qualcomm recovery solution, it will work as long as you hold the buttons correctly and don't power it on, else you will not end up in Qualcomm preboot mode.
It's just like MTK recovery on Mediatek phones if you've owned one of many MTK-devices. ?

u_ser_n_a_m_e said:
Sorry, I didn't know where to post this, but okay; I've installed an Oxygen OS update two days ago and I've had my phone rooted, my phone has been bricked since. Whenever I enter the bootloader my device isn't detected anymore by my laptop therefore I can't re-flash TWRP and now I'm completely stuck and don't know what to do, any help please?
Click to expand...
Click to collapse
Yeah follow the unbrick thread
I just updated my own thread that has ULTRA-BRICK in the title a second ago for how I solved my issue haha
edit: if needed, can PM me too. I won't hold your hand, but since I just came out of the worst brick I've ever managed to do to myself, I might be able to help if you encounter the same things

Also brick is a misleading word, as you can't really brick this phone unless you tamper with other partitions than the visible ones, which nobody does as they don't see them. ? (unless your tampering with firmwares or trying to unlock frequency bands)

Alright guys, I solved it. I just had to flash TWRP really quickly in the bootloader and install a substratum legacy rescue zip or something through TWRP, thanks for the help.

Oneplus3T stuck while trying to unroot using SuperSu

Hi,
I use a oneplus 3T
I had previously rooted my phone successfully using SuperSu and TWERP and I used it for 6 months. Now I tried to unroot it and did a full unroot using SuperSu. But my phone is stuck now. when I restart it oneplus logo comes. If I go to recovery mode, it just restart again and if I go to fastboot, nothing happens. When I connect my device to pc, it doesnt show up there. So I am not able to do fastboot because when I tried typing it, an error came.
Please someone help me out with this and guide me with a solution.
Thanks
EDIT:
Hey Guys after 5 hours of research and experimentation, I found the solution. If anyone in future have a similar problem, please PM me.

Abhimanyubadola said:
Hi,
I use a oneplus 3T
I had previously rooted my phone successfully using SuperSu and TWERP and I used it for 6 months. Now I tried to unroot it and did a full unroot using SuperSu. But my phone is stuck now. when I restart it oneplus logo comes. If I go to recovery mode, it just restart again and if I go to fastboot, nothing happens. When I connect my device to pc, it doesnt show up there. So I am not able to do fastboot because when I tried typing it, an error came.
Please someone help me out with this and guide me with a solution.
Thanks
Click to expand...
Click to collapse
Just download and flash your rom, assuming it's the stock OOS.
It will be unrooted afterwards.
Unleashed by ONEPLUS 3T rooted

RASTAVIPER said:
Just download and flash your rom, assuming it's the stock OOS.
It will be unrooted afterwards.
Unleashed by ONEPLUS 3T rooted
Click to expand...
Click to collapse
Hi, thanks for the reply.
I found out, I can fastboot because when I typed fastboot devices, it showed me the serial number.
Now I can't switch on my phone, because it gets stuck on the oneplus logo screen. I tried going in recovery but it still restarts. but i'm not able to access any screens other than fastboot.
I tried flashing TWRP. On pc it said successful. but no changes on my phone. I think I have accidentally deleted my OS and TWRP. but I cant figure out how to install these again.
How do I flash a ROM, if I can't access the storage of my phone.
I don't know what to do now.

Abhimanyubadola said:
Hi, thanks for the reply.
I found out, I can fastboot because when I typed fastboot devices, it showed me the serial number.
Now I can't switch on my phone, because it gets stuck on the oneplus logo screen. I tried going in recovery but it still restarts. but i'm not able to access any screens other than fastboot.
I tried flashing TWRP. On pc it said successful. but no changes on my phone. I think I have accidentally deleted my OS and TWRP. but I cant figure out how to install these again.
How do I flash a ROM, if I can't access the storage of my phone.
I don't know what to do now.
Click to expand...
Click to collapse
Try flashing another version of twrp using fastboot...open recovery....if it stuck on boot logo then wait for few minutes....it will work
Use power button and volume down button to boot into recovery!
Sent from my OnePlus3T using XDA Labs

Solved
Hey admin I got the solution. Please close this thread