Database Develop

Accidentally formatted /sdcard, now phone won't boot.

I accidentally formatted /sdcard instead of /system because I derped while trying to flash Youngunn's AOKP. Now I'm stuck because my phone won't boot any ROM. I re-flashed CWM (because that was erased with /sdcard) and it won't boot with AOKP or CM10.1. My phone is in the process of restoring Echo's PA, which I made a backup of. Anytime it attempted to mount /data it gives an error. All help is appreciated!

Hey bud.
So formatting /sdcard will not delete your recovery. I'm not sure what is going wrong with your phone but a clean install of cwm with fastboot and then installing aokp again will make it all better.
Sent from my MB886 using Tapatalk 4 Beta

Youngunn2008 said:
Hey bud.
So formatting /sdcard will not delete your recovery. I'm not sure what is going wrong with your phone but a clean install of cwm with fastboot and then installing aokp again will make it all better.
Sent from my MB886 using Tapatalk 4 Beta
Click to expand...
Click to collapse
It wouldn't boot into recovery (even selecting it from the bootloader or whatever screen), it would just stick at the Motorola bootlogo. Also tried your AOKP and restoring the PA backup, it kept giving me an error (just "Error mounting /data!") whenever it tried to mount/access /data and would stick at the ROM's bootlogo.
And just a note, when I select "Wipe dalvik cache" it just comes back to the same screen, doesn't wipe it or send me to the "no, no, no, no, yes, no" screen.
AOKP has been attempting to boot for 15 minutes now.
I'm assuming the /data mount is the issue here. Not sure what happened or how to fix it or even how to troubleshoot. All I did was accidentally wipe /sdcard, flash AOKP, stuck on bootlogo so I rebooted to recovery, which didn't work, so I fastbooted CWM back on, and the /data mount issue began.

penser said:
It wouldn't boot into recovery (even selecting it from the bootloader or whatever screen), it would just stick at the Motorola bootlogo. Also tried your AOKP and restoring the PA backup, it kept giving me an error (just "Error mounting /data!") whenever it tried to mount/access /data and would stick at the ROM's bootlogo.
And just a note, when I select "Wipe dalvik cache" it just comes back to the same screen, doesn't wipe it or send me to the "no, no, no, no, yes, no" screen.
AOKP has been attempting to boot for 15 minutes now.
I'm assuming the /data mount is the issue here. Not sure what happened or how to fix it or even how to troubleshoot. All I did was accidentally wipe /sdcard, flash AOKP, stuck on bootlogo so I rebooted to recovery, which didn't work, so I fastbooted CWM back on, and the /data mount issue began.
Click to expand...
Click to collapse
I'd say try the Myth tools and flash a stock image, I've erased my SDcard tons of times, I just did it last night, I wiped int and ext without issue through CWM,
I say use myth because it seems to work for everyone, it doesn't for me, I have to use RSD So I'd say pick your poison, both get you back to stock

Dude oh my god I had this same issue on a different device, I forgot what the fix was. If I come up with something I'll let you know.
Sent from my MB886 using xda app-developers app

I think he has to get the motorola factory programming cable to fix it, since it acts like a os for you to load a new os to your phone. Sorry I don't know a link on where to buy.

penser said:
I accidentally formatted /sdcard instead of /system because I derped while trying to flash Youngunn's AOKP. Now I'm stuck because my phone won't boot any ROM. I re-flashed CWM (because that was erased with /sdcard) and it won't boot with AOKP or CM10.1. My phone is in the process of restoring Echo's PA, which I made a backup of. Anytime it attempted to mount /data it gives an error. All help is appreciated!
Click to expand...
Click to collapse
i got this issue on my device a few days back. and i did format everything and manually flashed stock rom components via fastboot. please use this updated fastboot binary
1)download the required firmware from here i used last one (retail mexican) and recovery
2)extract the zip and place the recovery image and fastboot binaries in the extracted directory and open terminal in this directory.
3)type the following commands in order
fastboot flash modem NON-HLOS.bin
fastboot flash boot boot.img
fastboot flash devtree device_tree.bin
fastboot flash system system.img
fastboot -w
fastboot erase cache
fastboot reboot-bootloader
fastboot flash recovery cwmrecovery6028-xt925_20130219-epinter.img
fastboot reboot
Click to expand...
Click to collapse
if everything is done right, your device is now ok.

Silentwidow said:
I'd say try the Myth tools and flash a stock image, I've erased my SDcard tons of times, I just did it last night, I wiped int and ext without issue through CWM,
I say use myth because it seems to work for everyone, it doesn't for me, I have to use RSD So I'd say pick your poison, both get you back to stock
Click to expand...
Click to collapse
Flashed stock with Myth about 3 times, didn't work.
Aingaran said:
i got this issue on my device a few days back. and i did format everything and manually flashed stock rom components via fastboot. please use this updated fastboot binary
1)download the required firmware from here i used last one (retail mexican) and recovery
2)extract the zip and place the recovery image and fastboot binaries in the extracted directory and open terminal in this directory.
3)type the following commands in order
if everything is done right, your device is now ok.
Click to expand...
Click to collapse
I'll try that. Thanks!
EDIT: It worked!

penser said:
Flashed stock with Myth about 3 times, didn't work.
I'll try that. Thanks!
Click to expand...
Click to collapse
@Aingaran method is my recommendation as well. I'll just add to flash all the fast boot partitions... Might as well since you're already there

penser said:
Flashed stock with Myth about 3 times, didn't work.
I'll try that. Thanks!
EDIT: It worked!
Click to expand...
Click to collapse
nice to hear it worked :highfive:

Aingaran said:
nice to hear it worked :highfive:
Click to expand...
Click to collapse
I thanked ya cause he didn't

skeevydude said:
@Aingaran method is my recommendation as well. I'll just add to flash all the fast boot partitions... Might as well since you're already there
Click to expand...
Click to collapse
I always flash all partitions. Its just good practice
Sent from my MB886 using Tapatalk 4 Beta

TWRP 3.2.3-1 for Pixel Devices

TLDR: It's here and it may eat your data, and you will lose SuperSU root if currently installed. READ the install instructions carefully!
Pixel XL
Pixel
DO NOT RESTORE DATA FROM alpha builds of TWRP using RC1. You will probably lose all data including internal storage. If you need to restore a data backup from an alpha build, reinstall the alpha and restore using the alpha and make a new backup using RC1.
Note: Do not use if you have multiple users (including a guest user)
File Based Encryption (FBE) can be a bit tricky. If a restore doesn't work correctly, it can trigger an automatic wipe of your data. Sometimes TWRP will fail to prompt you to enter your password or otherwise fail to set up decrypt properly. If this happens, reboot TWRP. It seems to be some kind of timing issue and I haven't had time to track it down yet.
Pixel devices have 2 "slots" for ROMs / firmware. TWRP will detect whichever slot is currently active and use that slot for backup AND restore. There are buttons on the reboot page and under backup -> options to change slots. Changing the active slot will cause TWRP to switch which slot that TWRP is backing up or restoring. You can make a backup of slot A, switch to B, then restore the backup which will restore the backup of A to slot B. Changing the slot in TWRP also tells the bootloader to boot that slot.
The zip install method installs TWRP to both slots.
Installation:
If you already have TWRP installed: Download the latest zip and install the zip using TWRP.
If you do not already have TWRP installed: Download both the img and the zip. Copy the zip to your device. You will need to have fastboot binaries and the correct drivers installed. Power off your device completely. Hold volume down and turn on the device. Your device should now be in the bootloader. Connect the device to your PC. Open a command window and run the following command from the proper location:
fastboot boot path/to/twrp.img
This will temporarily boot TWRP on your device. If you are using a lockscreen pin/pattern/password and do not get prompted to enter your passord, reboot to the bootloader and try again. Go to install and browse to the zip and install the zip. If you are currently rooted with SuperSU, you will need to reflash the stock boot image before installing TWRP. After installing the stock boot image, follow the instructions for installing TWRP. Once TWRP is installed, grab the very latest SuperSU released on 2015-11-15 or later and install SuperSU.
If you accidently flash TWRP to your device using fastboot instead of temporarily booting the image, you will need to download the latest factory image for your device and reflash the boot image.
NOTE about 3.2.1-0: This version will decrypt Android 8.1, however the new image is built in Android 8.1 and may not be compatible with SuperSU and/or Magisk until they update their stuff. I have not tested. Good luck.
3.2.1-1 has working decrypt with the February security patch!
3.2.1-2 fixes some zip install errors
3.2.3-1 supports decrypting Android 9.0 Pie even with a pin / pattern / password set

How to install SuperSU SR5 on TWRP RC1: In TWRP tap on Advanced -> File Manager and scroll to and select the fstab.marlin or fstab.sailfish file and then delete it.

Amazing work sir! I think this is what we've all been waiting for! I mean I know I've been checking here frequently, hoping for this

Wow and so it begins, great work thanks!

Thanks
Sent from my Pixel using XDA-Developers mobile app

has anyone got the zip installed? when i boot into twrp.img everything is encrypted? im 100% stock as well

Dees_Troy said:
Note: I am going to be very busy the next couple of weeks. I probably won't be able to answer your questions or fix things immediately.
Click to expand...
Click to collapse
the pixel installer.zip is corrupt. :crying:

Really looking forward to having this and SuperSU working together. After that, I just need things to flash. Been going crazy not being able to appeasey crack flashing addiction.

GeekMcLeod said:
Really looking forward to having this and SuperSU working together. After that, I just need things to flash. Been going crazy not being able to appeasey crack flashing addiction.
Click to expand...
Click to collapse
Do you happen to have a copy of the .zip? All the ones I download are corrupt...

zaksimmermon said:
Do you happen to have a copy of the .zip? All the ones I download are corrupt...
Click to expand...
Click to collapse
No I haven't downloaded anything yet. Not going to until I can have supersu alongside twrp.

Why does installation of this remove SuperSU?
Aren't they supposed to be used side-by-side?
And it also warns not to install if expecting important calls.
Does it prevent the phone apps from operating or what?
I understand everything else.

Snowby123 said:
Why does installation of this remove SuperSU?
Aren't they supposed to be used side-by-side?
And it also warns not to install if expecting important calls.
Does it prevent the phone apps from operating or what?
I understand everything else.
Click to expand...
Click to collapse
"In other words, Chainfire's systemless root method modifies the same binary that TWRP needs to modify in order to get data decryption working. Therefore, when you flash TWRP you are overwriting the changes made to the init binary by Chainfire's systemless root method. While this is a minor setback, thanks to the dual partition nature of the Pixel (and future devices shipping with Nougat), TWRP has some nifty new capabilities."
I'm pretty sure he's just saying dont chance something going wrong like it bootlooping or wiping data if you need your phone for something important like a phone call. Tough to answer said phonecall in a boot loop.

zaksimmermon said:
has anyone got the zip installed? when i boot into twrp.img everything is encrypted? im 100% stock as well
Click to expand...
Click to collapse
I get exactly the same. Even after several attempts at booting the img, i don't get prompted to enter the PIN / passphrase as stated in instructions hence why the data is encrypted i presume.

rtthane said:
I get exactly the same. Even after several attempts at booting the img, i don't get prompted to enter the PIN / passphrase as stated in instructions hence why the data is encrypted i presume.
Click to expand...
Click to collapse
I finally got passed that issue. I had to flash factory images and erase everything to the point of being at setup screen. I didn't set anything up, no network or wifi, skipped Google sign in, no password and also no Google functions activated. This led to an unencrypted setup, so after turning on dev settings and Android debugging I booted up the image. Now my issue is the zip to install twrp for sailfish is corrupt and if you try to unzip it there are no files in it....I downloaded the marline zip and there are files when unzipped....

Maybe I'm an asshole but I cNt for the life of me flash this I download the .IMG I even changed name to TWRP.img but it won't flash boot at all just an error hmmmmm maybe I'm just dumb?

ne0ns4l4m4nder said:
Maybe I'm an asshole but I cNt for the life of me flash this I download the .IMG I even changed name to TWRP.img but it won't flash boot at all just an error hmmmmm maybe I'm just dumb?
Click to expand...
Click to collapse
Are you trying to fastboot flash or fastboot boot?
Sent from my Pixel using Tapatalk

Guys, check out super su and root in xl thread. New Super su posted by chain fire to work with twrp.

fracman said:
Guys, check out super su and root in xl thread. New Super su posted by chain fire to work with twrp.
Click to expand...
Click to collapse
Posted on standard pixel SU thread as well. Now if only I could make sense on the steps I need to take. This dual partition issue is throwing me off

ej_424 said:
Posted on standard pixel SU thread as well. Now if only I could make sense on the steps I need to take. This dual partition issue is throwing me off
Click to expand...
Click to collapse
My phone won't be here till tomorrow but as I understand it you need to use these steps (someone correct me if I'm wrong)
Reboot bootloader
Fastboot boot (twrp).img
Reboot recovery
In recovery, flash the twrp flashable .zip file
Reboot recovery
Flash the SuperSU sr4.zip
Reboot
Profit????

BakedTator said:
My phone won't be here till tomorrow but as I understand it you need to use these steps (someone correct me if I'm wrong)
Reboot bootloader
Fastboot boot (twrp).img
Reboot recovery
In recovery, flash the twrp flashable .zip file
Reboot recovery
Flash the SuperSU sr4.zip
Reboot
Profit????
Click to expand...
Click to collapse
OK thanks, wondering if root will work with November update or of I need to roll back first. Prior to SU update today Nov update didn't work with the auto cf root

I need help. My 3T has no OS and won't mount data partition in twrp.

I guess I wasn't paying close enough attention and I tried installing the 7.0 update from this thread.
I can now only get to TWRP recovery and fastboot. When I'm in TWRP my internal storage says 0MB and it won't let me mount the data partition. Flashing anything fails.

Fastboot format userdata

flammenwurfer said:
I guess I wasn't paying close enough attention and I tried installing the 7.0 update from this thread.
I can now only get to TWRP recovery and fastboot. When I'm in TWRP my internal storage says 0MB and it won't let me mount the data partition. Flashing anything fails.
Click to expand...
Click to collapse
Flash the stock recovery through fastboot. You can use the toolkit found here on xda forums.

Also you can format data in TWRP and then it should work, but you lose everything in internal storage, pics, music, all your own stuff.

Thanks guys. I got the stock recovery installed and it wiped everything, which was fine. I already backed up important stuff. It seems the update went through because I have Nougat now. But I'm having trouble installing any other roms. It wants to decrypt but it doesn't work. I read on the TWRP post that you can set a boot password and it would update the crypto key type or something and it should work after that. Well I did that, but twrp still won't accept my password and let me flash anything.

flammenwurfer said:
Thanks guys. I got the stock recovery installed and it wiped everything, which was fine. I already backed up important stuff. It seems the update went through because I have Nougat now. But I'm having trouble installing any other roms. It wants to decrypt but it doesn't work. I read on the TWRP post that you can set a boot password and it would update the crypto key type or something and it should work after that. Well I did that, but twrp still won't accept my password and let me flash anything.
Click to expand...
Click to collapse
I had the same problem. I used the 3T toolkit to force decrypt (Option 14). This worked for me.

kinfam said:
I had the same problem. I used the 3T toolkit to force decrypt (Option 14). This worked for me.
Click to expand...
Click to collapse
I just did this and it worked in TWRP: I was able to create a backup (which is not possbible in password-bugged state) and then I noticed I still was not able to mount the USB partition and thought I had to boot in to OOS once, so I did it, set up the bare minimum and then checked back at TWRP and voilà: Locked again.
The OOS said "encrypted" as well after I booted it.
I was (am) running 7.0, TWRP, non rooted (because I freaking can't)
Anynone can help here?

Nobody121 said:
I just did this and it worked in TWRP: I was able to create a backup (which is not possbible in password-bugged state) and then I noticed I still was not able to mount the USB partition and thought I had to boot in to OOS once, so I did it, set up the bare minimum and then checked back at TWRP and voilà: Locked again.
The OOS said "encrypted" as well after I booted it.
I was (am) running 7.0, TWRP, non rooted (because I freaking can't)
Anynone can help here?
Click to expand...
Click to collapse
Did you flash SuperSU before booting into OOS? Not sure what to tell you I did the Force Decrypt then went into TWRP and immediately flashed SuperSU.

kinfam said:
Did you flash SuperSU before booting into OOS? Not sure what to tell you I did the Force Decrypt then went into TWRP and immediately flashed SuperSU.
Click to expand...
Click to collapse
I wanted to do so but was not able to because I was not able to mount the relevant partition, nvm though I think I`ll wait a day or two to see if TW releases a new build. Thanks anyways:good:

Nobody121 said:
I wanted to do so but was not able to because I was not able to mount the relevant partition, nvm though I think I`ll wait a day or two to see if TW releases a new build. Thanks anyways:good:
Click to expand...
Click to collapse
,Using the toolkit take the option 14....To push decryption..,
DONT boot to your ROM...With the toolkit push the SuperSU and then flash it...
Now you can boot to your ROM....
If you boot without SuperSU will reenforse encryption.....

cultofluna said:
,Using the toolkit take the option 14....To push decryption..,
DONT boot to your ROM...With the toolkit push the SuperSU and then flash it...
Now you can boot to your ROM....
If you boot without SuperSU will reenforse encryption.....
Click to expand...
Click to collapse
Push with adb sideload? Because I was not able to get that going for me. ADB is installed on my PC. Also is there a way to backup my apps and data without root? I just set everything up. Thanks for the help

Nobody121 said:
Push with adb sideload? Because I was not able to get that going for me. ADB is installed on my PC. Also is there a way to backup my apps and data without root? I just set everything up. Thanks for the help
Click to expand...
Click to collapse
Options 1 and 2 on the toolkit is backup and restore apps and data..

cultofluna said:
Options 1 and 2 on the toolkit is backup and restore apps and data..
Click to expand...
Click to collapse
Nice haha, Ill try it later. Thank you really much

So there is currently no way to root and use TWRP without completely disabling encryption?

I'm having the same issues as the OP here. Whenever I go to use the toolkit it says "the system cannot find the path specified." Any ideas? I've tried within Android and in TWRP..
Sent from my ONEPLUS A3000 using Tapatalk

[Question] Unsuccessful Encryption

Hello, I've softbricked a fair amount of phones and tablets in my time but I must admit never had this show up. After flashing Twrp and a dm-verity thingy, I received this shiny new error on my new 1+3t. While I'm assuming it's a straightforward fix such as:
Booting into Twrp and flashing stock 4.x Oxygen os and the stock recovery to bring phone back to where I started.
My question is, can't I just go straight about flashing a rom? I.e freedom rom, or is it advisable to just try start again?
And is me flashing stock os then recovery got to work?
Everything is still stock there is no root. All I have done is:
Code:
fastboot > oemunlock > reboot > fastboot flash Twrp > Twrp boot > Twrp > swiped to Modify > flashed dm-verity.
I did receive a password request first time round but after I rebooted phone it wasn't there again.
Thank you for helping in advance.

Archtects said:
Hello, I've softbricked a fair amount of phones and tablets in my time but I must admit never had this show up. After flashing Twrp and a dm-verity thingy, I received this shiny new error on my new 1+3t. While I'm assuming it's a straightforward fix such as:
Booting into Twrp and flashing stock 4.x Oxygen os and the stock recovery to bring phone back to where I started.
My question is, can't I just go straight about flashing a rom? I.e freedom rom, or is it advisable to just try start again?
And is me flashing stock os then recovery got to work?
Everything is still stock there is no root. All I have done is:
Code:
fastboot > oemunlock > reboot > fastboot flash Twrp > Twrp boot > Twrp > swiped to Modify > flashed dm-verity.
I did receive a password request first time round but after I rebooted phone it wasn't there again.
Thank you for helping in advance.
Click to expand...
Click to collapse
You had to flash supersu or Magisk after the process to disable force encryption also make sure your are on the nougat supported twrp 3.0.4-1 or later
You can flash any rom if you have an unlocked bootloader and a working twrp
Sent from my Funk Tuned 3T

Funk Wizard said:
You had to flash supersu or Magisk after the process to disable force encryption also make sure your are on the nougat supported twrp 3.0.4-1 or later
You can flash any rom if you have an unlocked bootloader and a working twrp
Click to expand...
Click to collapse
thanks I think that's where I went wrong. I should have flashed Magisk. The guide says so but I only intended to flash a rom. Eh. I'll see if I can flash Magisk. All is not lost. I'll update once I get home. I'm annoyed with my self lol.
-101 xda points

Archtects said:
thanks I think that's where I went wrong. I should have flashed Magisk. The guide says so but I only intended to flash a rom. Eh. I'll see if I can flash Magisk. All is not lost. I'll update once I get home. I'm annoyed with my self lol.
-101 xda points
Click to expand...
Click to collapse
No prob buddy, let me know if you get stuck anywhere :fingers-crossed:
Sent from my OnePlus 3T using XDA Labs

Funk Wizard said:
No prob buddy, let me know if you get stuck anywhere :fingers-crossed:
Click to expand...
Click to collapse
I will do, hopefully it be fine. I'll try different thing if stuff doesn't work and I'll post back what I did incase anyone else has similar problem .

Twrp doesn't see any internal storage what so ever. So Ive flashed stock recovery from fastboot and going to attempt to sideload the stock OS. fingers-crossed

Funk Wizard said:
No prob buddy, let me know if you get stuck anywhere :fingers-crossed:
Click to expand...
Click to collapse
Thanks for your help im back to a working phone!
For anyone who get stuck!
1) download op3t stock recovery and the oxygen OS from oneplus website
2) boot into fastboot.
3) with your pc get up Adb and:
Code:
fastboot flash recovery stock.img
Fastboot boot stock.img
[\CODE]
4) Once you boot into recovery navigate to install from adb.
5) in cmd again on pc type
[CODE] adb sideload filename.zip
[\CODE]
6) then reboot :). You can leave it here if you want.

So I'm back on stock. With Magisk installed. Only dm-verity still come up which I'm not keen on. But I guess I can live with it. But I'm stuck with a bunch of system apps I can't get rid of? I've tried titanium backup, and link2sd my go to but nothing any ideas? Anyone now how to get rid?

Archtects said:
So I'm back on stock. With Magisk installed. Only dm-verity still come up which I'm not keen on. But I guess I can live with it. But I'm stuck with a bunch of system apps I can't get rid of? I've tried titanium backup, and link2sd my go to but nothing any ideas? Anyone now how to get rid?
Click to expand...
Click to collapse
I can recommend OOS Aroma Debloater Credits: @siankatabg :good:

Funk Wizard said:
I can recommend OOS Aroma Debloater Credits: @siankatabg :good:
Click to expand...
Click to collapse
Cheers I found the zip you. Mentioned after I posted the question, worked sort of lol. Some still won't go but it's got rid of a fair chunk an dive just frozen any I don't want.

Stuck in Oneplus logo. Can't access recovery. Fastboot working.

Hi everyone.
I was trying to flash Nitrogen OS. First I flashed the latest firmware, then the actual rom and then GAPPS. After that my mobile got stuck in Oneplus logo without being able to go into recovery mode.
I tried using fastboot to flash the files in this thread(https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306) which worked once, but even after that I can't surpass the logo screen.
I've been trying to look for information but I can't find anything.
To clarify:
- I already tried erasing userdata and cache from fastboot
-I already tried flashing recovery images from twrp, stock and bluspark
Thanks in advance guys.

Pavononer23 said:
Hi everyone.
I was trying to flash Nitrogen OS. First I flashed the latest firmware, then the actual rom and then GAPPS. After that my mobile got stuck in Oneplus logo without being able to go into recovery mode.
I tried using fastboot to flash the files in this thread(https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306) which worked once, but even after that I can't surpass the logo screen.
I've been trying to look for information but I can't find anything.
Thanks in advance guys.
Click to expand...
Click to collapse
Which TWRP are you using? Which firmware are you flashing? You can't access recovery at all? I've run into plenty of bricks like this and I'm usually able to get back to recovery by forcing the device off (vol up + power hold) and rebooting back to recovery. and if that doesn't work I can at least get to the bootloader and re-flash a recovery file.

rykanator said:
Which TWRP are you using? Which firmware are you flashing? You can't access recovery at all? I've run into plenty of bricks like this and I'm usually able to get back to recovery by forcing the device off (vol up + power hold) and rebooting back to recovery. and if that doesn't work I can at least get to the bootloader and re-flash a recovery file.
Click to expand...
Click to collapse
I was using last bluspark recovery. I was flashing OB21 when everything happened.
There is no way I can access to recovery. I tried reflashing the stock recovery from that unbricking thread with all the other things through fastboot and I can't boot into recovery at all. It is the first time I face this error so I am lost.

Pavononer23 said:
I was using last bluspark recovery. I was flashing OB21 when everything happened.
There is no way I can access to recovery. I tried reflashing the stock recovery from that unbricking thread with all the other things through fastboot and I can't boot into recovery at all. It is the first time I face this error so I am lost.
Click to expand...
Click to collapse
can you boot into the bootloader/fastboot?

rykanator said:
can you boot into the bootloader/fastboot?
Click to expand...
Click to collapse
Yes I can

Pavononer23 said:
Yes I can
Click to expand...
Click to collapse
okay, well what I would do is boot into the bootloader, and then reflash the blu_spark recovery via adb so you can boot into it. then wipe everything and restart. but this time I would try the OB 20 firmware and not the 21. when I was on NOS I used that one and it worked just fine. I'm not sure if it made a difference, but I flashed the firmware both right before and right after flashing NOS

rykanator said:
okay, well what I would do is boot into the bootloader, and then reflash the blu_spark recovery via adb so you can boot into it. then wipe everything and restart. but this time I would try the OB 20 firmware and not the 21. when I was on NOS I used that one and it worked just fine. I'm not sure if it made a difference, but I flashed the firmware both right before and right after flashing NOS
Click to expand...
Click to collapse
It doesnt recognize my device through adb and I don't know why. If that worked I would have tried to sideload some firmware, but when I do adb devices it doesn't appear

Pavononer23 said:
It doesnt recognize my device through adb and I don't know why. If that worked I would have tried to sideload some firmware, but when I do adb devices it doesn't appear
Click to expand...
Click to collapse
idk if it'll recognize as an adb device if it's in the bootloader. maybe try fastboot devices? sorry, I'm just spitballin here

rykanator said:
idk if it'll recognize as an adb device if it's in the bootloader. maybe try fastboot devices? sorry, I'm just spitballin here
Click to expand...
Click to collapse
Somehow fastboot devices does send me that my device is there but adb devices no, I will try looking into that to see if that works. Thanks for the help anyway

Pavononer23 said:
Somehow fastboot devices does send me that my device is there but adb devices no, I will try looking into that to see if that works. Thanks for the help anyway
Click to expand...
Click to collapse
yeah! try fastboot flash recovery "recovery file name".img
make sure that recovery img file is in the platform-tools file (or wherever your adb files are) and see if that works!

rykanator said:
yeah! try fastboot flash recovery "recovery file name".img
make sure that recovery img file is in the platform-tools file (or wherever your adb files are) and see if that works!
Click to expand...
Click to collapse
It is not working, I think I lost my Oneplus 3t...

Pavononer23 said:
It is not working, I think I lost my Oneplus 3t...
Click to expand...
Click to collapse
I mean idk if you wanna do this, but you could always try to "format userdata", then flash the stock recovery, and then sideload OOS. but you would lose all of your data in your internal storage, and it's still not a guarantee. there are some posts about doing a full wipe and starting from scratch. I'd look into those. Best of luck reviving your OP3T

Pavononer23 said:
It is not working, I think I lost my Oneplus 3t...
Click to expand...
Click to collapse
just a tip, try posting the output instead of "it's not working",
so the devs here might be able to analyze the problem..

nicknacknuke said:
just a tip, try posting the output instead of "it's not working",
so the devs here might be able to analyze the problem..
Click to expand...
Click to collapse
I already post a lot of information on the first post:
Mobile not passing the first time Oneplus logo appears.
Only fastboot is working, not adb, not recovery.
I already tried flashing other recoveries and the stock one->Can't pass Oneplus logo anyway
Tried formatting userdata through fastboot and flashing the .img files from my first post->Not working

Then just do the Qualcomm restore and unlock, boot to fastboot and flash the latest TWRP. Then boot into TWRP and format cache partitions, system and data and then adb sideload using this option under TWRP advanced to flash firmware zip, NitrogenOS zip and then 8.1 Gapps and try booting to see if same thing happens again. You are using the NitrogenOS stock kernel and not some other?

pitrus- said:
Then just do the Qualcomm restore and unlock, boot to fastboot and flash the latest TWRP. Then boot into TWRP and format cache partitions, system and data and then adb sideload using this option under TWRP advanced to flash firmware zip, NitrogenOS zip and then 8.1 Gapps and try booting to see if same thing happens again. You are using the NitrogenOS stock kernel and not some other?
Click to expand...
Click to collapse
What do you mean by the Qualcomm restor and unlock? I already tried the flashing of latest TWRP and it did not work.
I was coming from Validus last beta but did a previous factory reset and that stuff.
Thank you for the answer

Pavononer23 said:
What do you mean by the Qualcomm restor and unlock? I already tried the flashing of latest TWRP and it did not work.
I was coming from Validus last beta but did a previous factory reset and that stuff.
Thank you for the answer
Click to expand...
Click to collapse
What he meant is probably unbrick tool - https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Try flashing official firmware with it and then try again by flashing TWRP and flashing Nitrogen.

przemcio510 said:
What he meant is probably unbrick tool - https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Try flashing official firmware with it and then try again by flashing TWRP and flashing Nitrogen.
Click to expand...
Click to collapse
I can't install the drivers:
-First, stupid Windows policy saying that its driver is the best one available.
-Second, choosing from a disk to avoid one saying that the driver is not a x64 one.

Pavononer23 said:
I already post a lot of information on the first post:
Mobile not passing the first time Oneplus logo appears.
Only fastboot is working, not adb, not recovery.
I already tried flashing other recoveries and the stock one->Can't pass Oneplus logo anyway
Tried formatting userdata through fastboot and flashing the .img files from my first post->Not working
Click to expand...
Click to collapse
None of that answer what he actually asked, which is: what was the output (error message, result, etc.) when you tried to flash TWRP?
Did it flash successfully, but still can't boot to TWRP? Or else, what was the exact error message?
In general, when asking for help and giving status, be specific as possible, and give as many details as possible. Saying you "tried xxx" or "it did not work" is not specific enough.
Seems silly, but I've seen a lot of times where it's as simple as the user not using the correct command or entering the right file name.

redpoint73 said:
None of that answer what he actually asked, which is: what was the output (error message, result, etc.) when you tried to flash TWRP?
Did it flash successfully, but still can't boot to TWRP? Or else, what was the exact error message?
In general, when asking for help and giving status, be specific as possible, and give as many details as possible. Saying you "tried xxx" or "it did not work" is not specific enough.
Seems silly, but I've seen a lot of times where it's as simple as the user not using the correct command or entering the right file name.
Click to expand...
Click to collapse
There were no errors when flashing TWRP. When I tried rebooting using fastboot(fastboot boot recovery.img) it got stuck in the message saying booting up... and the only thing that changed was that my phone left the bootloader screen to a screen with the Oneplus logo and a fastboot mode message under it.
The command I used was fastboot flash recovery recovery.img(Name of the actual recovery file)