Database Develop

[Recovery]Clockwork Mod 4.0.1.4 (3.2 compatable)

DJ Steve ported CWM 4.0.1.4 with the release of 507.
Requirements:
Stock 5xx based rom [Honeystreak is not supported!]
Ability to enter fastboot mode: Fastboot+ADB.zip
Battery with 60% or greater charge
Basic understanding of the command line
Install Instructions:
Download recovery.img
flash the recovery with "fastboot flash recovery recovery.img"
Finished
Credits:
DJ_Steve for porting it
Koush for creating clockwork mod
I take no credit beyond this basic guide
Notice:
The Streak 7 with HC might now detect the driver properly, if it doesnt you must force install it using the "Android ADB Interface" from the list of available drivers
Will not work on 2.2.x, you must use CWM 3.0 for that.
Do not attempt to wipe data from within CWM, it will likely case a boot loop afterwards.

Thank you!!
Can I just push this recovery to my recovery partition within 3.2?
Im having issues having my PC at work recognize the fastboot device, and installing the drivers.
I am on xp..
TIA!

'error: cannot load 'recovery.img'
I got fastboot going fine, commands like 'fastboot reboot' are working.
However just above when I use your line to flash recovery, any ideas on what it might be!?

Uploaded new version of fastboot+adb.zip hopefully it has the correct IDs so you dont have to force install it.
Are you sure you downloaded the image correctly, and did you name it correctly when using fastboot

Yeah I was making a repeated typo when pointing fastboot to the recovery but its all working now, thanks a lot.
Clockwork mod (cool blue writing) and rooted all within a few days, good work and thanks to all involved.

FWIW I tried this on the T-MO stock 2.2.2 ROM. The install went fine, I copied S7-4.0.1.4.img to recovery.img and ran the fastboot command with no problems.
I power up the Dell Streak 7 while holding power and the up volume key, and get the menu as expected. I Select "Software Upgrade via update.pkg on SD Card", and the message "Booting recovery kernel image" is displayed.
At this point the machine seems to be frozen. I can reset with a paper clip, and reboot the machine into 2.2.2 just fine, but if I cannot resolve why it does not show the clockwordmod menu, then I guess it is back to NVFLASH.
So what am I doing wrong? do I need an SD card in the device with an update.pkg on the card? Or is there something else?

Oh that was a strong possibility.
CWM 4.0 uses the 507 kernel as a base. 507 will not boot without updating the bootloaders.
So that means CWM 4.0 wouldnt be able to boot unless you had 50x installed.

TheManii said:
Oh that was a strong possibility.
CWM 4.0 uses the 507 kernel as a base. 507 will not boot without updating the bootloaders.
So that means CWM 4.0 wouldnt be able to boot unless you had 50x installed.
Click to expand...
Click to collapse
Probably a good idea then to remove that "Assumed to work on 2.2.2" phrase then from your first append.
So I guess it is NVFLASH time ... Or could I somehow flash back only the original recovery.img using fastboot somehow?

Post updated, i needed someone to actually confirm that it didnt work as i dont have access to a s7

dblml320 said:
Probably a good idea then to remove that "Assumed to work on 2.2.2" phrase then from your first append.
So I guess it is NVFLASH time ... Or could I somehow flash back only the original recovery.img using fastboot somehow?
Click to expand...
Click to collapse
I posted over at TabletRoms yesterday that the new recovery did not work with Froyo 2.2.2.
To answer your question, all you have to do is fastboot flash the old CWM recovery, version 3xx something I think it is.

"waiting for device " and nothing happen !!! what should i do? i can not install driver using files in : Fastboot+ADB\Win32\Streak 5+Streak 7+Venue\Win7 !

cdzo72 said:
I posted over at TabletRoms yesterday that the new recovery did not work with Froyo 2.2.2.
To answer your question, all you have to do is fastboot flash the old CWM recovery, version 3xx something I think it is.
Click to expand...
Click to collapse
Like he said if you flashed it on a s7 that's still on 2.2.x just reflash with the CWM 3.0 one and that one will work fine on 2.2.x

Is there another way to root stock 3.2?
I am getting this error in fastboot...
"Flashing StorMgr partition recovery
Read after write verify partition recovery"

Not the stock one, as no other rooting tools work on it.
Ways to get around it include: using a pre-rooted rom or using a custom rom (which are normally pre-rooted)
Something may be wrong with your device/install if that is coming up. Or possibly your download was bad, try re-downloading it.

I tried re-downloading didn't work, I have stock rom, I don't think I can install a custom or pre-rooted rom without installing CWM?

You can with nvflash, as honeystreak is ment to be installed with nvflash then updated with the bundled CWM, which is prerooted
Whichever method you decide is up to you, as I cannot formally recommend that one method is better then the other.

thesmacker11 said:
Is there another way to root stock 3.2?
I am getting this error in fastboot...
"Flashing StorMgr partition recovery
Read after write verify partition recovery"
Click to expand...
Click to collapse
Well just as an update I tried this on a windows xp, windows 7 32bit, windows 7 64bit computer, and redownloaded that file each time and it still does the same thing on my device.

It's likely your device itself that's the issue then, I cant be more specific as I dont own a S7

I'm not sure if I should be asking questions here or over in another forum. Figure I'll start here...
I was sorely missing app2sd in honeycomb so went to use and install Link2SD figuring I'd use that. But it doesn't seem to see the second partition I've made on my SDHC card. I can mount the card on Mac OS and Linux and both mount the two partitions on the card so I feel pretty sure I formatted the card correctly. I saw some comment about a change in the way CW mounts things and it causing troubles in the Link2SD thread but I don't understand enough about the magic of Android and how it mounts discs, although I know it had Linux roots, so the comments in that thread weren't clear to me what I can do to get Link2SD working or for that matter even start to gather info to try to figure out what's wrong. Can anyone help me out or point me to a thread that can get me started in figuring out what's going wrong?
Sent from my HTC Flyer P512 using Tapatalk

ok so i installed the drivers for fastboot and i can enter fast boot , but how can i push the file? soory im a newb with the streak.

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

[SOLVED] E: Can't mount /cache/

I'm sorry to do this, but I don't know where to start. Here's what I did to get to where I'm at:
- previously running SlimBean flashed using TWRP
- Downloaded ROM Manager and it recommended installing CWM Recovery
- Followed prompts
- It installed CWM 6.0.4.8
- Booted back into ROM and used ROM Manager to attempt to flash SlimKat 4.4.2 build 6
- CWM wiped dalvik but then got hung up
- Now it keeps saying Can't mount /cache/recovery/command
I'm completely stuck. Can't figure out what to do next. Please help!!!

Have you tryed reflashing the recovery to rule out a faulty install of cwm?
I should say, have you tried reflashing cwm *through Fastboot* to rule out a faulty cwm install?

Use TWRP recovery, preferred is 2.6.3.3 although there are newer versions, enter recovery, wipe - format data, basically for some reason, fastboot erase cache wipes the cache into an un-readable format.
note: this will also erase your internal storage too, so if theres anything important you want on there, make sure you back it up first using the adb pull command.

dougeedug said:
Have you tryed reflashing the recovery to rule out a faulty install of cwm?
I should say, have you tried reflashing cwm *through Fastboot* to rule out a faulty cwm install?
Click to expand...
Click to collapse
I can't get it to recognize my devices in order to use ADB. When connected, I type ADB Devices and I don't see anything listed. Is there a way to check I'm doing this ok?
EDIT: Ok, I got it to recongize my device. I'm going to try flashing TWRP thru ADB....will report back shortly...
Seanie280672 said:
Use TWRP recovery, preferred is 2.6.3.3 although there are newer versions, enter recovery, wipe - format data, basically for some reason, fastboot erase cache wipes the cache into an un-readable format.
note: this will also erase your internal storage too, so if theres anything important you want on there, make sure you back it up first using the adb pull command.
Click to expand...
Click to collapse
I can't quite risk doing this yet. Only as a last, last resort...

cartisdm said:
I can't get it to recognize my devices in order to use ADB. When connected, I type ADB Devices and I don't see anything listed. Is there a way to check I'm doing this ok?
EDIT: Ok, I got it to recongize my device. I'm going to try flashing TWRP thru ADB....will report back shortly...
I can't quite risk doing this yet. Only as a last, last resort...
Click to expand...
Click to collapse
whilst your phone is in recovery and plugged into your computer, open device manager, is there a yellow ! where its says android devices or myHTC ?
IGNORE THIS, You got it working whilst I was typing this.

cartisdm said:
I can't get it to recognize my devices in order to use ADB. When connected, I type ADB Devices and I don't see anything listed.
Click to expand...
Click to collapse
Use the command "fastboot devices" from the bootloader with "fastbootUSB" highlighted. You can't use adb commands in the bootloader because adb is to interact with android, which is not running while in bootloader. Let me know if you get output with the "fastboot devices" command.
EDIT: I should specify, if you are trying to flash recovery from anywhere but the bootloader using fastboot commands (it sounds like you may be trying to flash recovery with adb commands), you are just doing it wrong. so lets get that sorted first.

cartisdm said:
I can't get it to recognize my devices in order to use ADB. When connected, I type ADB Devices and I don't see anything listed. Is there a way to check I'm doing this ok?
EDIT: Ok, I got it to recongize my device. I'm going to try flashing TWRP thru ADB....will report back shortly...
Click to expand...
Click to collapse
you flash a custom recovery with fastboot commands not adb commands.

Got it!!! Thank you everyone for taking the time. I have a flight in a few hours and I was panicking!!!!
I grabbed universal drivers from here: download.clockworkmod.[com]/test/UniversalAdbDriverSetup6.msi (remove the brackets around .com)
Then my computer picked up the device and I was able to install TWRP. Clockworkmod recovery still doesn't work, no matter which version I tried. I'll stick with TWRP for now.
Thanks again!
EDIT: Well eff me, it wiped my internal storage. It must have done it after I flashed because that's where I grabbed the zip in the first place. That sucks...

cartisdm said:
Got it!!! Thank you everyone for taking the time. I have a flight in a few hours and I was panicking!!!!
I grabbed universal drivers from here: download.clockworkmod.[com]/test/UniversalAdbDriverSetup6.msi (remove the brackets around .com)
Then my computer picked up the device and I was able to install TWRP. Clockworkmod recovery still doesn't work, no matter which version I tried. I'll stick with TWRP for now.
Thanks again!
EDIT: Well eff me, it wiped my internal storage. It must have done it after I flashed because that's where I grabbed the zip in the first place. That sucks...
Click to expand...
Click to collapse
did you format data inside twrp recovery, like I said above, that will erase your internal storage too, you will need to push a rom over to your internal storage now using adb and then flash it.

Seanie280672 said:
did you format data inside twrp recovery, like I said above, that will erase your internal storage too, you will need to push a rom over to your internal storage now using adb and then flash it.
Click to expand...
Click to collapse
I didn't do so intentionally, but it's possible I did it without paying attention. I'm back to my system now so I'll just live with the loss. I flashed an existing ROM that I had in my Downloads folder once I was able to get into TWRP. It's just weird that folder is empty now.

[Q] After flashing TWRP, XT1063 only boots to the unlocked warning screen

My apologies if this has already been posted. I've been looking all morning but haven't seen anyone with the same issue.
Unlock bootloader: no problem.
Flash TWRP: I downloaded from http://teamw.in/project/twrp2/275, and I got an error about partition size mismatch, but that's ok, right?
But when I try to enter recovery, all I get is the warning screen that my phone is unlocked. The drivers are certainly installed correctly, and fastboot is working fine. I just can't get into recovery to flash a ROM!

Restoring to 4.4.4 stock worked like a charm.
http://forum.xda-developers.com/mot...dows-tool-moto-g-2014-xt1064-restore-t2957167
I've re-enabled USB debugging. Do I dare try to flash a custom recovery again?

Pandae said:
Do I dare try to flash a custom recovery again?
Click to expand...
Click to collapse
You can use Flashify to make a backup of your current recovery and to flash TWRP.img. should work like a charm.

But Flashify requires root, I see? The reason I'm trying to flash a custom recovery is so I can root in the first place.

Pandae said:
But Flashify requires root, I see? The reason I'm trying to flash a custom recovery is so I can root in the first place.
Click to expand...
Click to collapse
You're right. Latest motorola driver and [TOOL]Minimal ADB and Fastboot will do the trick.

Sorry, I should have clarified that when flashing TWRP, I've already been using fastboot.exe from a command line (and administrator level), with the drivers correctly installed. That's how I was able to unlock in the first place.
I did try it with the version of Fastboot you linked to (what I have works peachy for my Nexus 7), still the same thing. I can't boot into recovery and only get stuck at the Motorola unlocked warning.

Pandae said:
I can't boot into recovery and only get stuck at the Motorola unlocked warning.
Click to expand...
Click to collapse
Oh. Sorry. Can you post the output (terminal & device) of
Code:
fastboot devices
fastboot flash recovery NAME_OF_RECOVERY.img

I'd done "fastboot devices" already to verify, and it returns the serial number, though as I said it's clearly working since I was able to unlock as well as flash recovery. I'm flashing "TWRP2801-titan-motog-2014.img" that I downloaded from the TWRP site, and fastboot gives the standard messages about size and success (and my phone gives the size mismatch error).
It's so strange to me. I've flashed a custom recovery dozens of times on both generations of my Nexus 7s, but I've never seen this.

Pandae said:
It's so strange to me.
Click to expand...
Click to collapse
Yeah......have to meditate about that problem....... is your battery low? Fastboot mode of the device gives me all sorts of problems if it detects low battery

I had been using fastboot at 100% (literally finished a full charge) and 84%, but thanks for the continued attempts at explanation.

Oh, did you check the md5 checksum of your download?

Ah, good thought! I rarely do, but I did just now...and they're the same. It's crazy, isn't it?

Pandae said:
Ah, good thought! I rarely do, but I did just now...and they're the same. It's crazy, isn't it?
Click to expand...
Click to collapse
If you are willing to risk it, try a fresh download and try again. I've flashed TWRP more than 20 times by now and never recieved an error whatsoever. It basically the easiest thing to do.
Incase you are stuck again, don't reflash the entire stock rom. Just flash the recovery.img from the stock rom files.
OR
Try this:
HOW TO ROOT MOTO G 2014 with Temporary Custom Recovery
Cheers

I've flashed a custom recovery many a time and have helped people through it, though on Nexus 7s.
Now shall I compound the mystery? I didn't think yet to use ADB to make my phone reboot to recovery. I had assumed recovery wasn't working. So here we go, after booting into Android:
adb reboot devices: my phone's there.
adb reboot recovery: TWRP's working?! And now root is complete!
It doesn't make sense to me why I can't get into recovery from the bootloader, but I can get into it with the simple ADB command. But I appreciate all the help, thanks!

Pandae said:
It doesn't make sense to me why I can't get into recovery from the bootloader
Click to expand...
Click to collapse
A little workaround:
Install Android Terminal Emulator
Add "Term shortcut" widget.
In "Arguments" enter
Code:
su -c reboot recovery

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)