Database Develop

[Q] Flashing a ROM with Unlocked Bootloader but S-ON. Possible ?

Hi
I have a HTC one m7 which went in Boot loop just like that. It was working perfectly some time back., just rebooted and won.t me back now. I had the latest stock OS 4.4 with sense 6 developer edition on it with no tamperig.
I tried many time wipe cache and factory reset. Nothing helped. Finally someone here suggested i do a unlock bootloader -> custom recovery -> custom rom -> s-off -> Load my Stock RUU.
Problem with above is i have done the unlock boot loader and install twrp recovery. But to do a s-off i need my device to read adb commands. As its in boot loop i cannot. Can i flash a custom binary which can run on S-on just to run those commands of firewater to make s-off.
I am stuck here. Please help to revive my device and reach me back to stock 4.4 sense 6 .
Also i came to know as i was on latest version if i flash a older RUU with S-On it can brick my device. True ?
And something else i noticed , i read some 4-5 thread in last two days complaining of HTC going in boot loop just like that.
HTC to blame ? Is this some issue with htc ???
Thanks

anirudhgargi said:
Hi
I have a HTC one m7 which went in Boot loop just like that. It was working perfectly some time back., just rebooted and won.t me back now. I had the latest stock OS 4.4 with sense 6 developer edition on it with no tamperig.
I tried many time wipe cache and factory reset. Nothing helped. Finally someone here suggested i do a unlock bootloader -> custom recovery -> custom rom -> s-off -> Load my Stock RUU.
Problem with above is i have done the unlock boot loader and install twrp recovery. But to do a s-off i need my device to read adb commands. As its in boot loop i cannot. Can i flash a custom binary which can run on S-on just to run those commands of firewater to make s-off.
I am stuck here. Please help to revive my device and reach me back to stock 4.4 sense 6 .
Also i came to know as i was on latest version if i flash a older RUU with S-On it can brick my device. True ?
And something else i noticed , i read some 4-5 thread in last two days complaining of HTC going in boot loop just like that.
HTC to blame ? Is this some issue with htc ???
Thanks
Click to expand...
Click to collapse
as mentioned in the previous post you made, you need to install a custom ROM first in order to boot back into your phone. You have unlocked the bootloader and installed TWRP recovery. Now you need to sideload the ROM by adb sideload commands in order to boot the phone up again
Do not run an earlier RUU.zip as you will brick your phone. Firewater needs a working ROM, there are no ways to bypass this

Flash ARHD 81 or Insert Coin or Team Venom Rom
Step 1. Unlock Bootloader and Install TWRP 2.7.x.x recovery. Don't install Twrp v2.8.x.x, wont work with any roms.
Step 2. Boot to Recovery.
Step 3. Mount the system using twrp. I am assuming that you don't have custom rom on your phone storage.
Note that TWRP v2.7.x.x wont mount the phone storage. v2.7 and above always had issues. My recommendation is to install TWRP v2.8 for temporary purposes. Now mount the phone storage copy any rom you downloaded to the system.
Step 4. Assuming that you install TWRP v2.8 to copy rom files to phone storage. Boot to bootloader again and Install TWRP using fastboot. Command: "Fastboot flash recovery openrecovery-twrp-2.7.1.1-m7.img"
Step 5. Reboot to recovery. WIPE DATA, CACHE, DALVIK CACHE, SYSTEM > Install Rom.
Note do not wipe "internal storage." Otherwise you have to go back and start again with installing twrp v2.8, then copy rom...
Step 6: follow the steps.
IMO ARHD 81 is a stable rom, provides better battery life. If you like Sense then stick with this Rom, if you want Stock Android aka AOSP then try aospa legacy, CM, SlimKAT, AOSB and many more.
Moreover, i haven't found RUU for Sense 6 KK4.4.3, if you do please provide me a link as well.

As of yet there are no links for 4.4.3 RUU's. Haven't been released anywhere. He just needs a working ROM to get s off again. Nice step by step guide tho

Not able to copy my custom rom in phone.
stovie_steve said:
As of yet there are no links for 4.4.3 RUU's. Haven't been released anywhere. He just needs a working ROM to get s off again. Nice step by step guide tho
Click to expand...
Click to collapse
Hi , i got stuck with a minor issue. I am with 2.8 TWRP was trying to mount the phone . i am using a mac os with the Android Revolution Rom downloaded in place. .
m7 gets mount i could see the phone in android fie transfer ( MTP utility for mac) . I selected the System and data and cache back in the twrp mount page. I can write and create some folders etc.
Issue is when i start to copy the Custom ROM file to the phone ( any folder) it says 'filexxx.zip not copy'. However i copied a small file (1mb). It was copied ok.
Any idea what is the issue with the file size restrictions?
I tried the adb sideload that also fails with saying device not found. Wanna avoid sideload, as sideload will execute also the zip after copying . I Want to change the recovery file as the recovery file need to changed to a twrp 2.7xx before installation starts. I hear that V2.8 is not compatible with lot of roms.

anirudhgargi said:
Hi , i got stuck with a minor issue. I am with 2.8 TWRP was trying to mount the phone . i am using a mac os with the Android Revolution Rom downloaded in place. .
m7 gets mount i could see the phone in android fie transfer ( MTP utility for mac) . I selected the System and data and cache back in the twrp mount page. I can write and create some folders etc.
Issue is when i start to copy the Custom ROM file to the phone ( any folder) it says 'filexxx.zip not copy'. However i copied a small file (1mb). It was copied ok.
Any idea what is the issue with the file size restrictions?
I tried the adb sideload that also fails with saying device not found. Wanna avoid sideload, as sideload will execute also the zip after copying . I Want to change the recovery file as the recovery file need to changed to a twrp 2.7xx before installation starts. I hear that V2.8 is not compatible with lot of roms.
Click to expand...
Click to collapse
You are better using the 2.7.xx version of TWRP. Sounds like you could also be using out of date adb drivers. You can download the most up to date ones by downloading the latest Google sdk
Try fixing the above and sideloading again

No luck ! Fastboot mode also not getting detected now.
stovie_steve said:
You are better using the 2.7.xx version of TWRP. Sounds like you could also be using out of date adb drivers. You can download the most up to date ones by downloading the latest Google sdk
Try fixing the above and sideloading again
Click to expand...
Click to collapse
Hello i tried updating the drivers from the sdk itself. No luck . The device won't just get detect as adb device. Tried cache clear. factory reset , reboot pc and phone. And Loaded other twrp recovery images ( 2.8 and 2.7).
Today tried with a window machine also. I thought some issue with Mac + adb drivers. But with window also No luck.
Also one more issue, my phone fastboot has stopped detecting om pc and mac. Tried everything almost.
It was like just working some time back, i loaded twrp 2.7.x and booted to recovery for adb sideload.
Adb Sideload failed as mentioned above on this window machine also ... so i was like this adb is not working at all.
But then i thought of loading 2.8 twrp and see if mount (mtp) works, i can send the ROM to device this way. But for that when i booted to fastboot. Fastboot just stopped detecting in PC (window and mac)
I wonder can the Fastboot mode ( within Hboot bootloader) can go corrupt ?
I am sure drivers are there, usb cable is fine, usb port in HTC one is fine. It just show "fastboot ac" not "fastboot usb" . No activity in the device manager when i plug surprisingly !! (can't see Android phone there " . Afterall it was working ok when i loaded the recovery image of 2.7.1.
Also , can the recovery mess up with the fastboot mode ? i am still s-on and in boot loop.
-Thanks,

anirudhgargi said:
Hello i tried updating the drivers from the sdk itself. No luck . The device won't just get detect as adb device. Tried cache clear. factory reset , reboot pc and phone. And Loaded other twrp recovery images ( 2.8 and 2.7).
Today tried with a window machine also. I thought some issue with Mac + adb drivers. But with window also No luck.
Also one more issue, my phone fastboot has stopped detecting om pc and mac. Tried everything almost.
It was like just working some time back, i loaded twrp 2.7.x and booted to recovery for adb sideload.
Adb Sideload failed as mentioned above on this window machine also ... so i was like this adb is not working at all.
But then i thought of loading 2.8 twrp and see if mount (mtp) works, i can send the ROM to device this way. But for that when i booted to fastboot. Fastboot just stopped detecting in PC (window and mac)
I wonder can the Fastboot mode ( within Hboot bootloader) can go corrupt ?
I am sure drivers are there, usb cable is fine, usb port in HTC one is fine. It just show "fastboot ac" not "fastboot usb" . No activity in the device manager when i plug surprisingly !! (can't see Android phone there " . Afterall it was working ok when i loaded the recovery image of 2.7.1.
Also , can the recovery mess up with the fastboot mode ? i am still s-on and in boot loop.
-Thanks,
Click to expand...
Click to collapse
Sounds also like a driver issue
Try instling HTC sync to get the up to date HTC drivers and retry. Use different usb ports (2.0 preferably) and different cables. If it's saying fastboot ac then the phone is not being detected correctly, so it's a driver issue
You can also try manually installing the driver by searching for I think the Google naked driver

[Q] "Bricked" Optimus 4X

Hi.
I was trying to flash LiquidSmooth ROM, installed TWRP recovery, formatted /data and /cache to F2FS and installed the rom, an custom kernel by mourta and PA Gapps.
The phone stucked in LiquidSmooth bootlogo. I tried to boot in recovery unsuccessfully (my Vol - key is kinda broken), the command adb reboot recovery didn't work.
After many tries, I could flash the LG Stock rom, the Kdz program didn't finish the process and the phone rebooted, don't know why.
Tried many other times to flash.
To sum up, I could flash the original firmware, the phone is booting up normally and aparently is working properly, the problem is: I still can't go to recovery to restore my old rom. (The adb reboot recovery comand just reboot the phone). So, I can't root it or flash another custom recovery.
I wish you guys can help me. Sorry if I written something wrong or if the text is too long, I haven't finished my English course yet.

Which stock rom have you flashed? I've tried to use fastboot on a V10 rom couple of weeks ago and I coudn't do it. I think that it works just with V20 roms.

ViniLima said:
Which stock rom have you flashed? I've tried to use fastboot on a V10 rom couple of weeks ago and I coudn't do it. I think that it works just with V20 roms.
Click to expand...
Click to collapse
I'm using now V20A_00_4.1.2.EURO.
I could acess the recovery (original) but adb sideload doesn't work. It says: "Error: more than one device and emulator."
About fastboot, I've already tried to flash the recovery using this, but it just keep with one message, I guess is waiting phone, or something like that.

ssgabriel said:
I'm using now V20A_00_4.1.2.EURO.
I could acess the recovery (original) but adb sideload doesn't work. It says: "Error: more than one device and emulator."
About fastboot, I've already tried to flash the recovery using this, but it just keep with one message, I guess is waiting phone, or something like that.
Click to expand...
Click to collapse
I didn't know that error more than one device and emulator. I can't help you on this error.
About Fastboot still waiting phone, that is phone driver's problem. Try to install P880 fastboot drivers and try again.
Try these drivers: http://forum.xda-developers.com/showpost.php?p=38953792&postcount=17

ViniLima said:
I didn't know that error more than one device and emulator. I can't help you on this error.
About Fastboot still waiting phone, that is phone driver's problem. Try to install P880 fastboot drivers and try again.
Try these drivers: http://forum.xda-developers.com/showpost.php?p=38953792&postcount=17
Click to expand...
Click to collapse
I figued out about the error: "Error: more than one device and emulator."
It's an incompatibility with Bluestacks, after close it, it works, but I had to turn off the phone and couldn't flash.
And about fastboot, I could acess this too (Didn't knew that I needed to be on Bootloader mode). But I can't flash the recovery, it says that my bootloader is locked (using fastboot reboot bootloader).
It isn't, or at least wasn't before it all happen. Using ADB command to reboot in bootloader mode (adb reboot oem-unlock I guess), I can flash the .img of clockwork mod and TWRP without error messages, but I still can't boot into it by adb reboot recovery.
Thanks for trying. Today I could acess Android original recovery by hardware keys and install another recovery and ROM.

Me and my HTC Vivid are stuck in Limbo, somewhere between custom ROM and Root.

Here are all of the procedures I followed to see if you can help me any. Believe me, I've tried searching everywhere.
1. I downloaded the latest version of the Windroid toolkit, found here (http://forum.xda-developers.com/showthread.php?t=2499926). I saw it worked with HTC Vivid on 4.0.3, which was an old shattered phone I had lying around. That tool is pretty old, so I had no idea what the TWRP version it flashed for me, nor the version of the SuperSU it tried installing. (it downloaded it onto the device but can't install it.)
2. I unlocked the bootloader via the tool, then proceeded to flash the TWRP version it had to the device, it currently works fine (loading into recovery). But I opted not to create a backup for the stock ROM, so that's gone forever. And at this point I can't install the SuperSU because of an error in TWRP "Error executing updater binary in zip" (which I googled extensively to no avail, none of the fixes worked). And for some reason, my computer recognizes when the device is connected, but I can't adb push or fastboot flash recovery "file".img to the phone. I am exasperated and stuck.
Takeaway notes: No stock ROM, Unknown TWRP and Supersu versions. I can't install the SuperSu zip because of "Error executing updater binary in zip". I am not sure how to--if i can--push any other ROMs to my device, because it seems like I can't communicate at all with my device through my PC. Although the fastboot does say "FASTBOOT USB"
This is the stage I'm at. I tried flashing a new image of TWRP, the most recent version that works on my phone, via fastboot. So I have a folder with the adb crap and fastboot crap and the image. I type "fastboot flash recovery twrp.img" and it just goes to the next line without doing anything.
I know this information was all over the place, but I'm not really sure what information you guys need to help point me in the right direction.
Thanks.

Fixing the "boot" partition instead of recovery

Hey there!
I am trying to flash TWRP 3.1.1-0 into my Xperia SP using ADB and apparently it cannot find the "recovery" partition. I've found out I can flash into "boot" instead but my question is, is there a way ( or should I even try) to fix this? I've tried Emma but my device is not supported. It's bootloader is unlocked and I am using Lineage OS 7.1
As far as I've searched in the forums ( https://forum.xda-developers.com/xperia-z-ultra/help/recovery-partition-xz-ultra-flashing-t3453568 ), at least for Xperia Z, it means the bootloader I originaly flashed used a "boot" partition instead of "recovery", right?
The final goal of this quest is to relock my bootloader so Sony Companion can reinstall the original firmware and get it as original as possible.
I am new here and, I hope I am posting this in the right section and I did my research right. This forum is so big it is a little overwhelming.
Thanks in advance!

flash recovery into boot
Hi,
I have a similar question: I want to flash LineageOS 14.1 to my Xperia SP Android 4.3 Build 12.1.A.1.205. I have unlock the Bootloader with the Code from developer.sonymobile.com/unlockbootloader
When I want to flash "fastboot flash recovery twrp-3.1.1-0-huashan.img" , it can not find the recovery partition.
Is it really possible to "fastboot flash boot twrp-3.1.1-0-huashan.img"??? After I have done this, I can reboot normally and TWRP will start? Then I will be able to install LineageOS?
Thanks!

FuchsXSP said:
Hi,
I have a similar question: I want to flash LineageOS 14.1 to my Xperia SP Android 4.3 Build 12.1.A.1.205. I have unlock the Bootloader with the Code from developer.sonymobile.com/unlockbootloader
When I want to flash "fastboot flash recovery twrp-3.1.1-0-huashan.img" , it can not find the recovery partition.
Is it really possible to "fastboot flash boot twrp-3.1.1-0-huashan.img"??? After I have done this, I can reboot normally and TWRP will start? Then I will be able to install LineageOS?
Thanks!
Click to expand...
Click to collapse
Yeah that's pretty much where I'm at right now. Whenever I flash TWRP into my Xperia SP using " fastboot flash boot twrp****.img" it works but when the phone boots the TWRP is all that is on the phone. It will not boot into the system. But then, when I install the OS using TWRP, the OS overwrites TWRP and I am back to the old cyanogenmod bootloader.
So answering your questions:
FuchsXSP said:
Is it really possible to "fastboot flash boot twrp-3.1.1-0-huashan.img"???
Click to expand...
Click to collapse
Yeah that's pretty much how it is done. At least on my Xperia SP. ( I love this phone btw XD)
FuchsXSP said:
After I have done this, I can reboot normally and TWRP will start?
Click to expand...
Click to collapse
Yeah it will only boot into TWRP. You probably wont have access to to your system anymore.
FuchsXSP said:
Then I will be able to install LineageOS?
Click to expand...
Click to collapse
Yeah, just press Install, select the file, and swipe that cool looking safety slider and it should be fine. Beware though older versions of LineageOS had some problems with zip signatures, just make sure to have the newest nightly version (07/12/2017 I guess) and you should be fine.
I have to say though, as anything with android modding, do at your own risk =p.

Here is the solution (at least, the one that worked for me)
I had similar problem - my phone was booting either into Lineage or TWRP, but I had to switch these using ADB commands.
Then I found an application in the Google Play store which can repair this. Look for "TWRP Manager (Requires ROOT)" - from Jmz Software. Free version is good enough.
I installed it and then when I tried to select the option to install TWRP, it tried to install, then complained that there is some problem with my configuration and it looks that it has been repaired. (I'm sorry for not repeating exact messages here, I was doing this about month ago, but when you install this application, the rest is quite self - explanatory).
Anyway, try this. Now my Xperia SP is booting flawlessly - Lineage or TWRP, of course "Reboot to Recovery" option in Lineage also is working correctly !

Xperia SP does not have a dedicated recovery partition like most of other Android phones and a newer Xperia variant. To workaround, the developers of this device have been using different ways of implementing recoveries, the latest and working one is by loading the recovery into our FOTAKernel partition, which is a partition that plays an important role during Stock OTA updates.
Since such a partition serve absolute no purpose when you ventured into custom ROMing, the idea of making use of it for recovery is quite neat. This "feature" is Adrian DC's implementation.
To answer to your question, no, you cannot flash a recovery using fastboot (or any other tools that makes use of fastboot). The options provided by the tool is only limited to partition names, not addresses. You can though, download the FOTA zip from the TWRP thread, and then flash them in the recovery (the one that you booted into because it was installed in /boot). Then re-flash the ROM zip so that the boot image of the ROM gets flashed properly.

It works
Hi,
I have success. On my Xperia SP is now LineageOS 14.1
1. Unlock Bootloader via Sony
2. fastboot flash boot twrp-3.1.1-0-huashan.img
3. reboot SP into twrp
4. wipe and install lineagesOS and opengapps
5. reboot
Now, i can access twrp with second recovery mode (FOTA)
Thanks for your help!! :good:

solved !
sorry to need to bump this thread, but i am having similar issues - i have successfully flashed twrp-huashan as shown in the post above, but on rebooting into twrp, wiping and installing adrian's oreo build, i lose access to twrp
attempting to boot to recovery shows a very brief droid on its back, and then tells me to choose to boot to system or recovery, neitherof which get me back to twrp
any suggestions, as i do not understand why this is so
edit : all is revealed !!
[Recovery][OFFICIAL][UBL] TWRP 3.2.1 Touch Recovery for Xperia SP
https://forum.xda-developers.com/xperia-sp/orig-development/recovery-twrp-3-0-0-touch-recovery-t3309938

Xperia z wont go into recoverymode. blue light with black screen
Hi im having a problem with my xperia z. i have rooted it fisrt then unlocked the bootloader but it wont show a recovery screen when i try and go into recovery mode to flash abd install lingeage. it just shows a blue light with black screen every time i try and go into recovery mode. cant seem to install twrp either. what do i do?

Blue light indicating fastboot mode on Sony Xperia Z5
Karimano24 said:
Hi im having a problem with my xperia z. i have rooted it fisrt then unlocked the bootloader but it wont show a recovery screen when i try and go into recovery mode to flash abd install lingeage. it just shows a blue light with black screen every time i try and go into recovery mode. cant seem to install twrp either. what do i do?
Click to expand...
Click to collapse
Well, that's it. The blue light indicates fastboot/recovery mode on the Xperia Z. You can now connect the Xperia to a computer via USB, then run e.g. 'fastboot devices' and it should list your Xperia. Or run 'fastboot flash recovery <image filename>' to flash TWRP onto the Xperia.

Serious help needed; completely broken 3T

UPDATE: I was able to install stock recovery through BOOTLOADER (it started working again) and I tried sideload 4.1.7.zip that way. It seemed to work for a while, but unfortunately, sideloading crashed. Same for 4.1.6, update fails around 45%. Phone says INSTALLATION FAILED. Any thoughts?!
Hi guys,
I'm a longtime flasher of phones, but my wife today jacked up her 3T beyond the point that I know what to do. In short:
Her phone was rooted, had an unlocked bootloader and TWRP installed. She updated (despite my endless begging never to do that) the OTA, which crashed her phone. Duh. Not smart. The problem: the phone would not restart the OS anymore. Upon restarting, the phone immediately jumped to TWRP and hung at the splash screen (which takes a while to load, but she doesn't know that). She panicked, rebooted the phone a bunch of times before giving it to me.
I was able to get into TWRP eventually, and figured I'd manually install the newest 3T firmware. This is what I did:
First, I updated TWRP through TWRP, to the most recent version. This was successful. Then, this happened:
Downloaded 4.1.7 from the OnePlus website
Placed it on the phone's internal storage
Went into TWRP, wiped Dalvik, Cache, System etc. (leaving Internal Storage in tact)
Flashed the firmware
I've done this thousands of times, never fails. Except now.
After flashing (which was supposedly successful, as I did not receive error messages), I hit 'reboot' and TWRP told me 'NO OS INSTALLED - WANT TO REBOOT ANYWAY?'
That is bad, right? So, I did not reboot, stayed in TWRP and ended up trying to wipe internal storage, thinking I could then add the .zip with the firmware again later and try flashing again. Just a clean phone, you know? I was wrong. I cannot copy anything to the phone right now, so I can't flash anything (because I can't put anything on the phone).
I'm trying to sideload things now through TWRP (adb sideload) and regular fastboot (either the firmware 4.1.7 or 4.1.6 - I've even tried flashing the stock recovery through fastboot to try and get the stock back, so I can sideload the firmware through there), but nothing works.
If anyone knows what to do, or can give me an outline on what to try, I'd be very helpful. The situation right now:
3T, without OS or ANYTHING on the phone
With functioning TWRP
Only recognized in the command prompt when in TWRP, not when in BOOTLOADER
Phone does not allow things to be copied to the phone via my laptop.
On behalf of my extremely upset wife, I thank you!

@Donaghy
copy the downloaded 4.1.7 to a usb pendrive.
connect it to the phone using otg cable.
wipe Dalvik, Cache, System in TWRP.
select install, storage (pendrive), click on the OOS 4.1.7 zip file.
After the flashing is completed, reboot to recovery (not system).
Phone will boot again to TWRP.
Wipe cache and dalvik, reboot. (ignore NO OS INSTALLED - WANT TO REBOOT ANYWAY?)
If you see the rotating red dot, then all's ok. leave it for 5-10 mins to boot.

Siddk007 said:
@Donaghy
copy the downloaded 4.1.7 to a usb pendrive.
connect it to the phone using otg cable.
wipe Dalvik, Cache, System in TWRP.
select install, storage (pendrive), click on the OOS 4.1.7 zip file.
After the flashing is completed, reboot to recovery (not system).
Phone will boot again to TWRP.
Wipe cache and dalvik, reboot. (ignore NO OS INSTALLED - WANT TO REBOOT ANYWAY?)
If you see the rotating red dot, then all's ok. leave it for 5-10 mins to boot.
Click to expand...
Click to collapse
Thanks for your response. Unfortunately, as per my update (in green, above the post) I have returned the phone to stock recovery. I have tried sideloading 4.1.7 and 4.1.6, but both installations (via adb sideload, via stock recovery) crash around 46%. Phone says installation failed.

Donaghy said:
Thanks for your response. Unfortunately, as per my update (in green, above the post) I have returned the phone to stock recovery. I have tried sideloading 4.1.7 and 4.1.6, but both installations (via adb sideload, via stock recovery) crash around 46%. Phone says installation failed.
Click to expand...
Click to collapse
Try connecting ur phone to a different usb port and then sideload.
If stills fails, get back from stock to twrp recovery and follow the steps i mentioned.
Sent from my OnePlus3T using XDA Labs

Siddk007 said:
Try connecting ur phone to a different usb port and then sideload.
If stills fails, get back from stock to twrp recovery and follow the steps i mentioned.
Click to expand...
Click to collapse
Thanks, I will. I did just realize my bootloader is still unlocked, so this may be causing the crashing of the sideloading of the official firmware (who knows). I am now going to try to lock the bootloader again, ADB sideload the firmware, and then unlock the bootloader again.

Donaghy said:
Thanks, I will. I did just realize my bootloader is still unlocked, so this may be causing the crashing of the sideloading of the official firmware (who knows). I am now going to try to lock the bootloader again, ADB sideload the firmware, and then unlock the bootloader again.
Click to expand...
Click to collapse
Check this, if in stock recovery there is option to install from USB? It it does, then update using otg pendrive
Sent from my OnePlus3T using XDA Labs

Siddk007 said:
Check this, if in stock recovery there is option to install from USB? It it does, then update using otg pendrive
Click to expand...
Click to collapse
I don't own an OTG cable. The only USB option there is, is within the ADB menu in the recovery.
EDIT: locking the bootloader seemed to have made things worse, as I now cannot get the .zip files with the firmware on it to be accepted by ADB/the phone... God, this is a gigantic mess..

I remember there was some adb version (don't remember which one exactly) that had sideloading of large files broken. Try using the newest version from Android SDK.
Edit: just realized you locked your bootloader. Not a good step at all.

C3C076 said:
I remember there was some adb version (don't remember which one exactly) that had sideloading of large files broken. Try using the newest version from Android SDK.
Edit: just realized you locked your bootloader. Not a good step at all.
Click to expand...
Click to collapse
Yeah, some douche somewhere else on the internet said it should be locked. In someone else's thread... I'm trying to unlock it now again through fastboot.
UPDATE: alright, bootloader is unlocked again. I think I have the most recent minimal ABD and fastboot, but I'll check to be sure.

Donaghy said:
Yeah, some douche somewhere else on the internet said it should be locked. In someone else's thread... I'm trying to unlock it now again through fastboot.
UPDATE: alright, bootloader is unlocked again. I think I have the most recent minimal ABD and fastboot, but I'll check to be sure.
Click to expand...
Click to collapse
Btw, which stock recovery are you using?
It should be of the version 4.1.7 you are going to sideload
Sent from my OnePlus3T using XDA Labs

Siddk007 said:
Btw, which stock recovery are you using?
It should be of the version 4.1.7 you are going to sideload
Sent from my OnePlus3T using XDA Labs
Click to expand...
Click to collapse
Whichever is the most recent one that is on the OnePlus website. I downloaded the .img off of their website.

I've had a similar issue, and I tried a billion times on trying to reflash Stock OOS 4.1.0, and sadly nothing happened. I then tried LineageOS by SultanXDA, nada.
So then, I said "Scr*w my data, I'm going to start anew", and I tried the Unbrick Tool, and Voila, new phone with OOS 3.5.X. Not the latest, but it's working.
I suggest you try that mate, you can find it over here.
Cheers!
P.S. - Love your profile pic.

If you sucessfully flashed 4.1.7 then I'd just reboot into system. TWRP sometimes says "No OS installed" if /system was wiped prior to flashing.
Regardless, I recommend you do these things now (if you havent already) and report back:
-Unlock bootloader (fastboot oem unlock)
-Flash TWRP* recovery, not stock. (fastboot flash recovery twrp.img)
-Boot recovery (fastboot boot twrp.img)
-Wipe data + system + cache + dalvik from TWRP
-ADB sideload in advanced section of TWRP
-from your PC: "adb sideload oos417.zip"
-from TWRP: reboot into system (ignore "No OS installed")
If you follow this and its succesful, everything will be fixed
* flash the twrp by xda member eng.stk, not the official one: the only place I can find his TWRP is in the 3/3t toolkit zip. So extract the v5 zip and use the "TWRP_recovery.img": https://drive.google.com/drive/u/0/folders/0B1cephDrsyt_ZzJ1cXpUUlVhSzg
Edit: Instead of doing all this manually, you may want to use the toolkit. See if your device is recognised

Thanks for the help, everybody!
I used the unbrick tool, which worked! I got the phone 'alive' again.
New problem: Right after successfully booting the phone again, I set up the phone (so: clean install, no root, stock recovery, straight out of the box, you know what I mean) and then proceeded to download the OTA that OnePlus pushed to the phone (4.1.7). It downloaded quickly, but the installation has been stuck for almost an hour.
The phone says 'Updating, please wait - do not turn off your phone', and the blue bar is filling. Well, not filling, as it has been stuck at about 10% for an hour.
Is this normal? If not, what can I do? Thanks again!

I turned the phone off and was able to successfully sideload 4.1.7 via ADB. Upon updating, the phone gave me a notification (blue and white letters) that the "DECRYPTION IS UNSUCCESSFUL. The password you entered is correct, but you have to perform a factory reset to use your phone".
So I did another factory reset in recovery, rebooted, and it's up and running, with 4.1.7 on it! I can't believe we got it back from the dead. Thanks everyone, for your help! Really appreciate it!