Develop Bugs

Stuck in a boot loop

Very strange. My phone was working perfectly yesterday. But this morning when I powered it on, it's stuck in a boot loop (going over and over to the first splash screen).
I can't get it into recovery either, which also seems odd.
I'm sure I can get it out of it by flashing a ROM or perhaps factory reset (goes into hboot fine). Will experiment a bit later (no time this morning) to see if I can get it out of the loop without flashing a ROM though - e.g. I will probably try just flashing Clockwork via fastboot.
Just putting this up there for info. I flashed a new radio yesterday, but as I said the phone was working perfectly, so I don't see why that should have anything to do with it.

I had issues flashing CWM recovery via fastboot... I was able to "fastboot boot recovery.img" From there, you can flash a ROM with ROM Manager and reflash your recovery.
Let me know if you run into the same issues.

steviewevie said:
Very strange. My phone was working perfectly yesterday. But this morning when I powered it on, it's stuck in a boot loop (going over and over to the first splash screen).
I can't get it into recovery either, which also seems odd.
I'm sure I can get it out of it by flashing a ROM or perhaps factory reset (goes into hboot fine). Will experiment a bit later (no time this morning) to see if I can get it out of the loop without flashing a ROM though - e.g. I will probably try just flashing Clockwork via fastboot.
Just putting this up there for info. I flashed a new radio yesterday, but as I said the phone was working perfectly, so I don't see why that should have anything to do with it.
Click to expand...
Click to collapse
You might have to flash a rom via bootloader/fastboot. Just remember you can't flash one with a older hardboot version. If you have the eng bootloader, you shouldn't have a problem. What a pain though, I hope it isn't the radio either as I flashed a different one earlier tonight also, lol!
Crap, I flashed the same damned radio as you did too. Ha! Although, I do find this ironic after our little debate about the forum merge yesterday I'm sure you can try reflashing recovery via fastboot and if that fails reflash stock rom through fastboot. Its not bricked for sure...

Did you reboot (properly) after you flashed the new radio? (i.e. after it powered on once).
I did worry that anyone with radio s-off will have issues like this when they tried to flash a new radio.

Lennyuk said:
Did you reboot (properly) after you flashed the new radio? (i.e. after it powered on once).
I did worry that anyone with radio s-off will have issues like this when they tried to flash a new radio.
Click to expand...
Click to collapse
He must have had a bad flash... I flashed the same radio with no problems and several powering off attempts and reboots, checking compatiblity, and backups. No issues and have already reflashed a few roms and kernels. The radios are safe... at least the lastest desire z one from Eygpt and the two stock tmobile usa ones are too.

I never did a second reboot after flashing the new radio, but it did reboot after flashing it from fastboot of course, and it worked perfectly for the rest of the day (I'm positive I was getting a better signal).
I just tried fastboot to flash CW recovery - same problem (stuck in boot loop).
I then tried fasboot boot with the CW recovery image - same problem.
Then I used fastboot to reflash the radio. It worked ! The phone is back up and running.
So that's odd. Could just be a bad flash, as has been suggested ?

steviewevie said:
I never did a second reboot after flashing the new radio, but it did reboot after flashing it from fastboot of course, and it worked perfectly for the rest of the day (I'm positive I was getting a better signal).
I just tried fastboot to flash CW recovery - same problem (stuck in boot loop).
I then tried fasboot boot with the CW recovery image - same problem.
Then I used fastboot to reflash the radio. It worked ! The phone is back up and running.
So that's odd. Could just be a bad flash, as has been suggested ?
Click to expand...
Click to collapse
Sounds like it... I've seen this happen on some old WM phones before.

Well my phone has exactly the same problem this morning after being left powered off overnight.
I tried flashing the recovery image and radio image again, via fastboot, like last time, but it didn't help.
Going to reflash the stock ROM. I'm starting to think there is something wrong with my phone and it's going to have to go back

Shizzer! Again? You went back to stock after using Visionary didn't you?.. Done Rage from clean yeah?

ddotpatel said:
Shizzer! Again? You went back to stock after using Visionary didn't you?.. Done Rage from clean yeah?
Click to expand...
Click to collapse
No I didn't use Visionary lol.
Yesterday, after first having the problem, all I did was flash CW recovery and flash the new (Egypt) radio again. Then the phone was back to life, I rebooted it several times and all was 100%.
This morning though it was stuck again but flashing CW recovery and the radio (both via Fastboot) didn't help at all.
So I've just flashed the stock UK/Europe ROM. Will root again via rage, install ROM Manager, flash Clockwork and restore the nandroid backup I did last night.
I will stay back on the stock ROM/radio combination for a bit because I'm starting to wonder if my phone has a problem. No-one else has reported an issue with this radio.
Edit - back up and running fine now after doing the above.

I'm still newbie in these phone things but really sounds like something is corrupting your files.
Device working perfectly after a flash and getting into boot loop later sounds like a hard ware problem to me. (also I have understood that /system is r-only if you don't remount it?)

AnyDone said:
I'm still newbie in these phone things but really sounds like something is corrupting your files.
Device working perfectly after a flash and getting into boot loop later sounds like a hard ware problem to me. (also I have understood that /system is r-only if you don't remount it?)
Click to expand...
Click to collapse
Yeah I know what you mean. I'm going to stick with the stock radio (even though it's worse than the newer one) for a while to check that the problem goes away. Then I will probably try flashing it again to see if the problem comes straight back again.
I also did wonder about whether I can just "dd" the new radio to the correct partition instead of using fastboot to flash it, though I'm not going to do that unless someone can confirm that's ok.

[Q] Oddities of rebooting CWM

Sooo, I got my OTA update for Tiny's CM rom today from GooIM. And low and behold... now I can't seem to access my Clockwork Recovery Mod. I enter Rom Manager, order it to reboot to Recovery, and comes to Fastboot. Or, the two finger salute, Pwr/DnVol yields the same result.
Now the phone insists that it's still Soff, Hboot 0.92, and the like... Rom Manager insists that ~it~ can detect CWM 5.0.2's presence, but any attempt to actually boot into it just results in me ending up on the Fastboot screen.
After various attempts at battery pulls and and at reinstalling RomManager and CWM, I tried instead to flash in an image for TWRP both from the GooIM app, and from ADB. That went nowhere as the phone just keeps returning remote access denied type errors in ADB, and merely booted to fastboot and stayed there till I rebooted it normally when done via the app.
Also, the refresh feature seems to have gone kerplooey. From within the rom it just restarts and sends me to the fastboot screens when I ask it to go nuclear, and if I try it from the fastboot screen, it just restarts.
So, I could use some help at this point on how to retake control of my Dinc. Right now I can't change rom's, wipe the caches, etc...

eoraptor said:
Sooo, I got my OTA update for Tiny's CM rom today from GooIM. And low and behold... now I can't seem to access my Clockwork Recovery Mod. I enter Rom Manager, order it to reboot to Recovery, and comes to Fastboot. Or, the two finger salute, Pwr/DnVol yields the same result.
Now the phone insists that it's still Soff, Hboot 0.92, and the like... Rom Manager insists that ~it~ can detect CWM 5.0.2's presence, but any attempt to actually boot into it just results in me ending up on the Fastboot screen.
After various attempts at battery pulls and and at reinstalling RomManager and CWM, I tried instead to flash in an image for TWRP both from the GooIM app, and from ADB. That went nowhere as the phone just keeps returning remote access denied type errors in ADB, and merely booted to fastboot and stayed there till I rebooted it normally when done via the app.
Also, the refresh feature seems to have gone kerplooey. From within the rom it just restarts and sends me to the fastboot screens when I ask it to go nuclear, and if I try it from the fastboot screen, it just restarts.
So, I could use some help at this point on how to retake control of my Dinc. Right now I can't change rom's, wipe the caches, etc...
Click to expand...
Click to collapse
Reflash cwm http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/PB31IMG.zip thru hboot.
How to flash - http://pvillecomp.com/?page_id=79.
Then see if you can access it. If you can do a full wipe, and then either restore a backup or flash a rom of your choosing.

I would aslo recommend using Team Wins recovery now its more user friendly has some tools you might find handy and well touch based lol
Sent from my rooted GameBoy Color!!! ^¬^

Took me a month, but I finally got past both my frustration and some meat-space interruptions. Yes, the instructions provided by cmlusco did the trick, thank you SOOOO much.
And ironically, I WAS going to install TWRP onto the device, elzimmer, but when I booted it up, it said it had the OTA update to install, so I let it do that first *rolls my eyes* On reboot I found out that that had tanked the recovery mod before I could even begin doing the factory resets and so forth.
Either way, thanks again both of you.

Possibly bricked One X - need assistance!

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

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

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

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

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

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

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

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

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

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

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

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

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

Alright ! Hope i don't see you here again

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

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

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

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

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

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

STUCK ON REBOOT [LOGCAT included]

hi everyone
when i reboot my device by any means (from inside of android, recovery, even adb reboot-bootloader), the device never finishes the reboot. interestingly, when i have it plugged into windows by usb, when doing the reboot i hear the usb disconnect sound, then the usb connect sound, then it just stays black screen and is unresponsive. only fixed by holding power or power+down button.
some info:
bootloader v 4.02 // twrp 2.7.1.1 // liquidsmooth current nightly
however, this problem happens on stock rooted as well as all custom roms
i have included a logcat of the issue (never made one before but i think i did it right) if someone can please help me, i'm thinking i may need to return my model.
thank you! :fingers-crossed:

Vember31 said:
hi everyone
when i reboot my device by any means (from inside of android, recovery, even adb reboot-bootloader), the device never finishes the reboot. interestingly, when i have it plugged into windows by usb, when doing the reboot i hear the usb disconnect sound, then the usb connect sound, then it just stays black screen and is unresponsive. only fixed by holding power or power+down button.
some info:
bootloader v 4.02 // twrp 2.7.1.1 // liquidsmooth current nightly
however, this problem happens on stock rooted as well as all custom roms
i have included a logcat of the issue (never made one before but i think i did it right) if someone can please help me, i'm thinking i may need to return my model.
thank you! :fingers-crossed:
Click to expand...
Click to collapse
Have you tried flashing stock images using fastboot?
It seems like the system can't write to /data directory, maybe flashing everything again will fix that issue.

alresave said:
Have you tried flashing stock images using fastboot?
It seems like the system can't write to /data directory, maybe flashing everything again will fix that issue.
Click to expand...
Click to collapse
I did flash the stock images (the latest 4.4.4) and unfortunately still had the same problem. i'll give it another shot today though to see what happens
EDIT: performed the fastboot flash with the factory images and had the same issue. tried philz recovery and wouldn't turn back on after selecting reboot. checked permissions on /data and /system and everything was RW. i tried remounting both as well to no avail. must be a hardware issue i feel like at this point

*Try flashing through a different custom recovery.
* figure out how to use the flashall.bat script to flash a new recovery, bootloader, ROM and kernel.
*Try fastboot boot for the recovery as opposed to fastboot flash. (I'm not sure if this will do anything)
*try wugfresh toolkit soft brick unroot+flash stock
Ps: this is just a list of ideas. Flashing a working ROM should mount all of your directories.

mugzylol said:
*Try flashing through a different custom recovery.
* figure out how to use the flashall.bat script to flash a new recovery, bootloader, ROM and kernel.
*Try fastboot boot for the recovery as opposed to fastboot flash. (I'm not sure if this will do anything)
*try wugfresh toolkit soft brick unroot+flash stock
Ps: this is just a list of ideas. Flashing a working ROM should mount all of your directories.
Click to expand...
Click to collapse
Thanks for the suggestions, though trying those methods unfortunately hadn't done it either. Eventually, the ability to reboot simply showed up just the other day. I'm not too sure why it did and wasn't working before, but I kind of think it needed about 1-2 days of being powered on while connected to a charger. Previously, I would charge it only every few days with the power off and unplug it to use it. That's the only difference I can spot for anyone else who runs into this problem. Keep it connected to the charger for a day or two with the power on.

Stuck on team win recovery project please help

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

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

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

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

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

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

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

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

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

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