Develop Bugs

Strange Brick

Hey Guys..
I have a Desire here in my Hands with a strange type of Brick.. (at least one I've never seen before) ..
It just does not react to anything at all. The battery is charged and I tested with another cell to be sure that is not the trivial cause.
No Bootloader, No HTC Logo, No reactions at all..
Did happen while flashing a Froyo 2.2 Rom + Radio + App2SD (from the xda forums) via ClockworkMod Recovery but I wasn't there to witness the actual Flash.
After flashing the device hung desperately in a screen with the robot in front of a box with an arrow .. looked like unpacking or so, but wasn't doing anything at all for at least half an hour.
Then battery removed -> Brick.
Anyone got any Idea?

messywrk said:
After flashing the device hung desperately in a screen with the robot in front of a box with an arrow .. looked like unpacking or so, but wasn't doing anything at all for at least half an hour.
Click to expand...
Click to collapse
I suspect you removed the battery whilst it was flashing the radio. This is insta-brick territory and as far as I'm aware there is no cure other than sending it in to HTC.
Regards,
Dave

If you can access fastboot as opposed to bootloader you might be talking failing that back to HTC it goes

if your phone can not turn off whilst holding either volume down or the back button then yeah it's a brick, send it off to htc, just say it overheated and wont turn on again

foxmeister said:
I suspect you removed the battery whilst it was flashing the radio. This is insta-brick territory and as far as I'm aware there is no cure other than sending it in to HTC.
Click to expand...
Click to collapse
The battery was removed after flashing and rebooting.
Installed in the following order:
32.41.00.32U_5.08.00.04.zip
LeeDrOiD_V1.2b.zip
942_desire_froyo_a2sd-signed.zip
every process seemed to work normal, no error happened.
Then rebooted the Desire and the "Box with Android-Bot" Screen appeared.. this hung for 30 min or more when I could not think of any other solution than removing the battery to reset..
After this -> nothing.
I suppose as you say it has to do something with the Radio ROM..
Been coming from OpenDesire 1.6b - every flash ran perfectly up to this point.
Damn, I think this one has to go back to HTC.
Is there any possibility to unbrick a phone thats not responding at all?
Could HTC be aware of the modifications or will they really just go with the "overheated and won't turn on again" explanation?
Thanks for your help so far guys!

Yea, the little Droid with the box thing is during a radio flash and you should never pull the battery during that as it does result in a brick.
Can you reach fastboot as mentioned up above?

..tried pressing the "back" button with the power button and the vol-down button together with the power button..
even did the "insert the battery while holding the button" method..
I don't think I can get the thing to Fastboot..
But I will look further into this and try..
..
Has anyone had a Radio Brick and sent this to HTC before?
Is the repair covered by warranty?
Do you guys think they even get this is no real HW failure?

messywrk said:
Has anyone had a Radio Brick and sent this to HTC before?
Is the repair covered by warranty?
Do you guys think they even get this is no real HW failure?
Click to expand...
Click to collapse
I know someone who sent their phone back with a pretty much identical issue and the phone was fixed under warranty no problem.
Regards,
Dave

yay!
you know, even one post of you telling me it went allright for another guy is a big relief..
EDIT: just wanted to let you know I tried invoking fastboot via usb and the android PC tools..
just keeps waiting for the device.. and waiting ..
..will analyse USB traffic in general to conclude if there is a little itsy bit of life left in the phone, but I think this is a dead end too.

thank u all for ur help i have managed to unlock the phone as described
thanks alot every1

saifiraq: You seem to have stumbled in the wrong thread or could we help by coincidence?
..UPDATE:
Did usb-sniffer analysis while pulling battery, trying to turn on, plugging usb in etc.
NOTHING at all..
My baby is on it's way to HTC now.. wish me luck guys!

[Q] How to turn Epic screen back on?

My Epic's screen turned black yesterday for no apparent reason however the touch screen still works...
if i touch and scroll the lock up it still makes the sounds and i can guess were to touch to turn my alarm off on the black screen and that works, as all the buttons! i just cant see the screen anymore,
i did not install anything new, last thing i remember doing is just taking a picture. now i have a working phone with a black screen how do i fix this?
also, i cant even see the vol down camera power screen
help please

mrose61692 said:
My Epic's screen turned black yesterday for no apparent reason however the touch screen still works...
if i touch and scroll the lock up it still makes the sounds and i can guess were to touch to turn my alarm off on the black screen and that works, as all the buttons! i just cant see the screen anymore,
i did not install anything new, last thing i remember doing is just taking a picture. now i have a working phone with a black screen how do i fix this?
also, i cant even see the vol down camera power screen
help please
Click to expand...
Click to collapse
Can you get into download mode??
With the phone off .. Press 1 (on the keyboard) and power. If so, maybe try to odin back to EC05 stock
http://forum.xda-developers.com/showthread.php?t=1027904
good luck

If on boot after pulling battery it is still black and download mode shows nothing, and you have tried Odin (it works but you see nothing still) I am afraid you need to head to the Sprint store.

kennyglass123 said:
If on boot after pulling battery it is still black and download mode shows nothing, and you have tried Odin (it works but you see nothing still) I am afraid you need to head to the Sprint store.
Click to expand...
Click to collapse
Update: after ltting my phone sit on the charger for about 3 hours it came back on
BUT it went right back to the previous (working but all black screen) problem wen
i made a call which i now remember is what triggered it yesterday
I just tried getting into download mode and it did not work or show up
anyy further suggestions? if not can i ask the sprint store 4 help if i rooted my phone and unlocked it for boost?
PS. (i been making outgoin calls for months now n this never happened even with it rooted & inlocked)
thanx 4 taking the time to answer my questions

mrose61692 said:
Update: after ltting my phone sit on the charger for about 3 hours it came back on
BUT it went right back to the previous (working but all black screen) problem wen
i made a call which i now remember is what triggered it yesterday
I just tried getting into download mode and it did not work or show up
anyy further suggestions? if not can i ask the sprint store 4 help if i rooted my phone and unlocked it for boost?
PS. (i been making outgoin calls for months now n this never happened even with it rooted & inlocked)
thanx 4 taking the time to answer my questions
Click to expand...
Click to collapse
try to odin to ec05 stock ... leave your phone again for a while and see when you get your screen back if you can get to download mode and odin that stock rom ... this will allow you to see if it is something up with a rom you're running.
if it does it then, you'll be at stock so when you go to the sprint store; it won't be an issue.

jdelano said:
try to odin to ec05 stock ... leave your phone again for a while and see when you get your screen back if you can get to download mode and odin that stock rom ... this will allow you to see if it is something up with a rom you're running.
if it does it then, you'll be at stock so when you go to the sprint store; it won't be an issue.
Click to expand...
Click to collapse
I agree Odin back to stock is your best option and if that dosn't work you probaly stuck with a black screen!

Yes, if you got it to come on once by leaving it you should be able to do it again and Odin before making any calls.

I had no choice but to take it to the sprint store
they fixed it !!!
thankx again guys 4 all ur help!

mrose61692 said:
I had no choice but to take it to the sprint store
they fixed it !!!
thankx again guys 4 all ur help!
Click to expand...
Click to collapse
great news, glad you have a working Epic again.

mrose61692 said:
I had no choice but to take it to the sprint store
they fixed it !!!
thankx again guys 4 all ur help!
Click to expand...
Click to collapse
Hey, I know this is an old post but I have an old Epic I'd like to see if I can trade into for credit towards a Galaxy S III but I'm having the exact same problem as described here:
Softkeys light up, screen hepatic feedback "buzz" can be felt, can swipe to unlock and answer a call based on blind-memory of what to swipe but other than that, the screen is completely black. Not black as in lit up but devoid of any other color except black, but gone dark.
If it weren't for the softkeys being lit, I would assume the screen were either broken or disconnected from the motherboard somehow. There are no cracks in the screen. Phone has seen better days for sure but the screen is intact and all functions were working perfectly before it simply...blipped off in front of my eyes.
I've tried doing as you did: charging it for 3+ hours and seeing if that worked at least temporarily. No go.
Assuming our two phones were experiencing exactly the same issue, can you tell me when you had it repaired, if the issue was a hardware or software issue? If hardware, did they have to replace the screen? or was it merely not connected properly somewhere?
If it was a software issue, how did they repair it? I'm assuming I can, in fact, get the phone into download mode, but without a visible screen, I can't boot off of a zip file or see if any of my actions are successful. Can't be sure I cleared the caches properly before I proceed, etc.
Phone was last running toadlife's CleanGB prior to the FC09 update and I'm pretty sure, prior to EL30 (I can't remember but I'm pretty sure it was).
Again, I know this is old but any feedback would be appreciated.

navkat said:
Hey, I know this is an old post but I have an old Epic I'd like to see if I can trade into for credit towards a Galaxy S III but I'm having the exact same problem as described here:
Softkeys light up, screen hepatic feedback "buzz" can be felt, can swipe to unlock and answer a call based on blind-memory of what to swipe but other than that, the screen is completely black. Not black as in lit up but devoid of any other color except black, but gone dark.
If it weren't for the softkeys being lit, I would assume the screen were either broken or disconnected from the motherboard somehow. There are no cracks in the screen. Phone has seen better days for sure but the screen is intact and all functions were working perfectly before it simply...blipped off in front of my eyes.
I've tried doing as you did: charging it for 3+ hours and seeing if that worked at least temporarily. No go.
Assuming our two phones were experiencing exactly the same issue, can you tell me when you had it repaired, if the issue was a hardware or software issue? If hardware, did they have to replace the screen? or was it merely not connected properly somewhere?
If it was a software issue, how did they repair it? I'm assuming I can, in fact, get the phone into download mode, but without a visible screen, I can't boot off of a zip file or see if any of my actions are successful. Can't be sure I cleared the caches properly before I proceed, etc.
Phone was last running toadlife's CleanGB prior to the FC09 update and I'm pretty sure, prior to EL30 (I can't remember but I'm pretty sure it was).
Again, I know this is old but any feedback would be appreciated.
Click to expand...
Click to collapse
Hm, so you're saying download mode or recovery mode open up but with a black screen? But it still reads touches? My guess is it's hardware, a loose connection to the screen.

Yeeeeah, good luck towards funding your S3 purchase.
Sent from my SPH-D700 using XDA

I'm having this issue have my phone was dropped yesterday, so I'm quite sure it's a hardware issue.
I have two questions: can somebody be so kind as to give me the button sequence for how to make a nandroid of my phone? I have CWM 5.0.2.7 without the 'one confirm' option. That would be awesome. Also, is anyone familiar with taking the phone apart and perhaps how to fix this issue?

chillywings said:
I'm having this issue have my phone was dropped yesterday, so I'm quite sure it's a hardware issue.
I have two questions: can somebody be so kind as to give me the button sequence for how to make a nandroid of my phone? I have CWM 5.0.2.7 without the 'one confirm' option. That would be awesome. Also, is anyone familiar with taking the phone apart and perhaps how to fix this issue?
Click to expand...
Click to collapse
A guide to take it apart is here:
http://forum.xda-developers.com/showthread.php?t=1569701
and steps to nandroid
3 finger salute for about 5 seconds
toggle down 4 times hit cam button 2 times

tazfanatic said:
3 finger salute for about 5 seconds
toggle down 4 times hit cam button 2 times
Click to expand...
Click to collapse
Thanks tazfanatic. I tried the backup procedure and it didn't seem to work, and I think I actually have CWM 5.5. Is the procedure any different?

chillywings said:
Thanks tazfanatic. I tried the backup procedure and it didn't seem to work, and I think I actually have CWM 5.5. Is the procedure any different?
Click to expand...
Click to collapse
not sure 5.5? is that the touch version?

tazfanatic said:
not sure 5.5? is that the touch version?
Click to expand...
Click to collapse
CM9 version.
Sent from my PantechP4100 using xda premium

kennyglass123 said:
CM9 version.
Sent from my PantechP4100 using xda premium
Click to expand...
Click to collapse
Oh i have cm9 that is the direction I gave thought cm9 came with 5.0.2.7 my bag.

tazfanatic said:
Oh i have cm9 that is the direction I gave thought cm9 came with 5.0.2.7 my bag.
Click to expand...
Click to collapse
Indeed. I'm running CM9 beta 2, and I'm pretty sure it came with 5.5. However Taz, I believe if you boot into recovery from ROM Manger or the power menu, it still takes you into your previous recovery version (such as 5.0.2.7). Or vice versa. I don't remember. To my knowledge, this is has something to with the switch to MTD, and the devs just have reroute that command.
But regardless, I'm not getting a new backup on my SD card, so I'm pretty sure I'm on 5.5. Kenny, do you know if there's a different button sequence for 5.5?

5.5 is the same. I would remove the battery to make sure it is powered off. Put the battery back in, hold camera, volume down and power in that order (making sure power is last) for 5 seconds. wait 20 seconds to make sure it booted into CWM 5.5. Then volume down 4 times then camera twice. Depending on how many apps you got I would wait 30 minutes before pulling the sd card to check in clockworkmod\backup directory for a new file with current date code.

URGENT help with boot screen, how to log it?

[Warming up]
I've been having problems lately trying to figure out the problem..
So, first i suspected the SD card, doesn't seem like my original 16GB card was the problem, because i bought 2 new 32GB Micro SDHC cards already, same problem..
[Now the problem]
80% of the times when i reboot and go into recovery and flash a couple of roms, or reboots in general, i for the most part get stuck in Bootscreen, if i try to wipe Cache and Dalvik-Cache, it sometimes solves the problem and 20% of the times i can get into the system, the other 80% of the times that i actually succeed into getting the rom to load up, i mostly get stuck there aswell, untill it reboots the phone, and im back at the imfamous bootscreen...
So, i've figured, is there anyway for me to log the stuff that is happening at the boot screen? because im curious to what the problem might be..
[The things i've done already]
Everything is formated as EXT4, and has been so since Mike introduced it with his rom..
i've tried Mikes rom, Unity, Honey roms, Coredroid, RCmix, all the same on all of them.
I always wipe my phone fully before i boot the rom, mostly with Mikes Super Wipe Script, but sometimes with the wipe zip mentioned from the Rom Dev explicitly telling me to use that..
I always let the rom boot 2 times before i start flashing themes and stuff..
Just going Stock rom doesn't help either, i've tried that aswell, no change.
I've cleaned the phone, from top to toe.. (brushed and cleaned with special liquid)
I've tried different Micro SDHC cards, 1 of em was a counterfeit card, the newest one works just flawlessly, i've benchmarked, checked for errors and even done a Bluff check on it, all working 100% nominal.
CPU running at 998Mhz, just incase..
[Ending]
So, does anyone have any suggestions?.. Does anyone have any way for me to get logs of the Bootscreen (as its a wallpaper, i have no chance in actually seeing what is happening)
Are there any ADB commands i could use to check errors in bootscreen? Any diagnostics tests?
Maybe even a way to refresh the Bootloader with ADB commands?..
ANY help would be greatly appreciated!!

You have some pretty serious problems here. Not that I could diagnose it, but it sounded like hardware related problems to me. Btw, here's the link about boot log you've requested.
http://forum.xda-developers.com/showthread.php?t=1025561&highlight=Boot+logcat
8penned from my blazing fast DHD

drpsyko said:
You have some pretty serious problems here. Not that I could diagnose it, but it sounded like hardware related problems to me. Btw, here's the link about boot log you've requested.
http://forum.xda-developers.com/showthread.php?t=1025561&highlight=Boot+logcat
8penned from my blazing fast DHD
Click to expand...
Click to collapse
Have to agree on that
Do you still have warranty?

drpsyko said:
You have some pretty serious problems here. Not that I could diagnose it, but it sounded like hardware related problems to me. Btw, here's the link about boot log you've requested.
http://forum.xda-developers.com/showthread.php?t=1025561&highlight=Boot+logcat
8penned from my blazing fast DHD
Click to expand...
Click to collapse
Thanks man, very much appreciated!
I'll run some logs tomorrow and see whats up with the phone, i actually got the phone running optimal again with yet another fresh rom flash and it all seems to work, have only restarted the phone 2 times, as im afraid of restarting the phone and get stuck again..
If i do get stuck, im stuck forever, and have to try above mentions i've done before, wipe cache and dalvik-cache, sometimes this works, most of the times it doesn't, and i end up fully wiping a couple of times and reflashing roms untill it works.. (I know this might sound like an SD card problem, but its not, i've gone thrue this with a couple of programs)
Anyway, a thousand thanks for that link, will probably help me quiet some..
madmaxx82 said:
Have to agree on that
Do you still have warranty?
Click to expand...
Click to collapse
Aye, this phone i have in my hands right now has already been in for repairs before and they changed the PCB of the phone, got a new IMEI number and all that..
But i do have warranty left for it, but i have to iron out the problem before i send it in, don't wanna risk being sent back to me and i have to pay lots of $ for their trouble (you know how HTC 3rd party repair centers works).. Plus they might actually scratch my screen some more as they did when i last sent it in...
Well, i have another "minor" problem with the phone aswell, not sure if its my phone or a general new cosmetic problem occurring on phones sent in for repairs, as i haven't noticed it on my earlier phone (Well theoretically the same phone).. Is that when i look at the screen in pitch black moving screens, i can see a distinct line going from Top Right to Bottom Left corner, and the Top Left side of the screen is black, and the lower right part of the screen is black/grey, you can see the difference, but not noticeable when your actually booted up, only in the Bootanimation part is it visible, i've tried different Bootanimations and everyone that has a Black background has this cosmetically problem.
Aah crap, Wall of text..

Haha just gonna add that i installed both apps you mentioned earlier, and the phone feels more like a Dev phone now, but anyway, it all worked great, not sure if it logged anything yet, didnt find anything in the app yet if it does..
I noticed something strange though, Gsensor Enabled, then right before bootup, Gsensor Disabled..
Have no idea why it does that, have no problem with Gsensor though..
Edit:
6 successful restarts!! That's something new!
I have no idea why its behaving this good.. Well time will tell..

ATT Tilt 2 went to red, green, blue, white screen; how can I flash a cooked Rom to it

Hi,
Right in the middle of use, my ATT Tilt 2 went to a basic, dead screen with red, green, blue, and white bars that says Rhod300 32m SS-BC, etc.
The operating system seems have gone down--it won't respond to anything. Hard reset produces the same results.
Can I flash a cooked or official Rom back onto this? I think activesynch is needed for a normal flash and of course I can't use active synch with the phone in this condition.
I think probably what I need is an original ROM install. Is this possible with a normal Windows 7 PC and a dead phone?
I have so many Windows Mobile programs and peripherals that I am trying to avoid going to Windows Phone at all costs--at least until they have basic stuff like file systems, a way to port over notes, etc. Also need a hard keyboard.
Right now using an older Fuze, which works, but is slower, worse screen, smaller, and lacks some of the features I like.
Thanks for your help.

You sound like you're in the bootloader mode. Tri-color screen.
You can flash from USB or from SD at that screen. I'd recommend trying to flash a stock ROM - as it flashes everything. Assuming that works, hopefully you can flash back whatever ROM you were on.
The phone isn't dead if you're at the tri-color screen. It should say 'serial' at the bottom - when you plug in your USB cable, it should say 'USB' and install some drivers. Then with the RUU software that comes with every ROM, you should be able to flash it.

Phone won't reboot--stuck on tricolored boot screen
Hi,
Thanks so much for replying. I appreciate you pros helping us novices.
Just after I posted the first note, I pulled the battery and hit the power button, it rebooted, and everything was still there in the OS--working fine. But whenever the device had to be rebooted, I would have the same problem of it getting stuck in the boot screen. After that, for the last several days once in awhile, randomly, it would finally reboot from the boot screen after I pulled the battery and hit the power button. The rest of the time (about 5/1) it would just sit there in the boot screen no matter what I did. The "Serial"/"USB" thing would change when I plugged it in, but that's all.
Thought it was the OS, so at a lucky moment where the "pull battery, hit power button" strategy actually worked, I installed the latest official HTC/ATT Rom--it's the next to last one issued that ends in .4.
It was gorgeous and I got all excited--started installing stuff thinking my problem was solved.
Had to reboot to install some programs--now it is stuck again on the boot screen. Tried 30x again--no luck with the "pull battery/hit power button"
strategy. Sometime it would flash a white screen really quickly saying something like "Can't read image!" before going into permanent boot screen. The boot screen will switch from "Serial" to "USB" if you connect it to the computer. So, the problem doesn't seem to be in the OS--rather, in the ability of the device to "read" the OS from the boot screen.
I would be grateful if you or anyone else may know what's going on here, and any ideas on how to fix it. Is there any manual way to get it to read the OS from the boot screen when that's not happening?
I have two guesses (both of which may be wrong):
1. It may be something in the hardware is just worn out and is less and less able to read the Rom--any ROM. I got the phone new off Amazon for a profit of $50 ($.01 cost plus a refund for an older phone) in the summer of 2010 when it was already outdated. and WP was replacing WM. I've certainly gotten my money's worth after 18 months!
Of course we now know that a brand new ROM has the same problem as the older one--which suggests to me it's in the hardware. I'm sure the new OS and the stuff I installed is still there on the phone, but something it appears is not reading something in order to allow the boot up.
2. I have a squirrely free program called Rax Reset (from Windows Mobile Marketplace) that does a software-based hard or soft reboot from inside the OS. The very last time the device went down and didn't come back up, I had used that program to soft reset it. Might have been a big mistake. Could this program be causing the problem? If so, just one reboot would allow me to get rid of it or even hard reset to remove everything but the new OS--but can't get it to boot.
If it turns out the phone is just worn out, I've certainly gotten my money's worth.
I still love WM even with all its problems--and especially the newer Sense version. If this one is shot, I'm thinking about just buying a new Touch Pro2 on Ebay to avoid all of the sacrifices and backwards steps involved with Windows Phone.
Thanks for any help anyone can provide.
Phil Butin

Why are you crossposting? I read this EXACT same post in a thread just below this, in the same section. That's pretty low.. Crossposting across forums isn't welcome, crossposting within forums IN THE SAME SECTION is definitely not welcome.
Don't do it again.

Sorry, just trying to get help
Sorry, just trying to get help, not that familiar with the rules.
I searched on "bootloader" and found a thread (wrote a comment there too), but it's old....
Here is the thread. It doesn't really provide any solution.
HomeArrow
Legacy & Low Activity DevicesArrow
HTC Rhodium: Touch Pro2, Tilt 2Arrow
Touch Pro2, Tilt 2 GeneralArrow
issues with bootloader.

Either way, whether you know the rules or not - why would you think copying and pasting the exact same words in the exact same forum help you any more...
Anyhoo, have you tried the usual? Flash stock? Sometimes I've heard you have to flash several times, I never really understood that logic tho.

I'll try to reinstall the HTC/ATT Sense OS again. I guess you're saying active synch doesn't need to be working in order to do that. I'm at work now--have to wait until i get home. Nothing to lose at this point.
But I'm seriously wondering whether the problem is the OS install or whether there is something in the device that is supposed to read the ROM and start the bootup that is just wearing out.
Thanks.

"No Image File"
The quick little flash of white screen has "No image file" in blue letters--goes by so fast you can hardly see it.

[email protected] said:
The quick little flash of white screen has "No image file" in blue letters--goes by so fast you can hardly see it.
Click to expand...
Click to collapse
That error message is 'normal'. Basically the phone checks the SD card for a file labeled "RHODIMG.nbh". If said file exists, it will flash from it. If no file exists, or no SD present - it continues loading bootloader and should say "Serial" at the bottom. This indicates that it's ready to be flashed. If you plug in your USB cable, it will install some drivers and then it should change to "USB" at the bottom instead of "Serial".
Now you should be ready to flash from a normal RUU. I would recommend flashing STOCK, because this flashes everything.
It might also be good to note a lot of people have experienced something similar - the phone getting "stuck" in bootloader mode, and only occasionally making it to WinMo. I'd guess it's failing hardware in some way shape or form, as none of my RHOD's or RAPH's have ever done this.

Good News--at least for now
Good news--I hooked it up to the computer with the USB cable for awhile and the Windows 7 computer did set up some drivers. For some reason after I disconnected it I reset it, and the reboot worked. Then I immediately uninstalled the squirrely reset program and removed it.
Everything I installed yesterday is working fine--I have soft reset it about 5 times now and each time it has rebooted. So I think maybe I'm back in business. Too soon to tell--but we will pray and keep our fingers crossed.
Thanks so much for your time and help. I don't know how to use the thanks meter but I would have if I could have.

[email protected] said:
Thanks so much for your time and help. I don't know how to use the thanks meter but I would have if I could have.
Click to expand...
Click to collapse
You're welcome. Basically if I or someone else posts something helpful, click the "Thanks" button under that post.

15 hours later, Tilt 2 is still working fine on the newly installed Sense OS. I have rebooted freely (using the stylus button on the side) since removing the program "Rax Reset," and everything seems to be going well. I'm keeping my fingers crossed, and will end my contributions to this thread with a warning about using "Rax Reset."
Thanks to all.

Is my 1+3 dead!?

Hi everyone,
I'm experiencing pretty silly situation with my phone.
So the story begins here:
I was surfing the web while listening to music in the bus when suddenly my oneplus3 randomly turned off and I couldn't turn it back on. (I was on something around 15% on battery so it's not a low battery problem) I tried to turn it on several times and after holding the power button for like 10secs it turned on, and after pressing the power button again (because I needed to get past unlocked bootloader screen and dm-verity) I saw a boot screen. The capacitive button leds turned on and after 3 secs it turned off again, so I started worrying... After a while I tried to access the recovery, but no luck at all. It powers it self off after bootscreen. So I started to research. Tried to flash the entire OS, partritions with msmdownload tool. After several unsuccessful flashes (firehosewritedata failed sometimes while writing userimg or system.img or boot.img) I did get the download complete green text message, and after successful flash, the white LED turned on, even the phone was not plugged in USB or charger and turned off. The screen is completely black and the white led just flashes constantly without blinking or anything. I could only turn the led off by pressing the power button for another 10 secs. And after turning the phone off, problem still remains. After oneplus logo phone shuts down...
I can access bootloader.
And after flashing everything should be on stock, because now I only got screen only about bootloader, no dm-verity..
And of course - I still cannot access the recovery.
p.s. I tried to do the power cycle (as the tech support told me) but still no luck at all.

did u tried the full msmdownload tool (1gb) or the 55mb version ?

Mukthar. said:
did u tried the full msmdownload tool (1gb) or the 55mb version ?
Click to expand...
Click to collapse
1GB version

djemm1996 said:
1GB version
Click to expand...
Click to collapse
Are you sure that you did it right? Did your phone show up as mentioned in the instructions?

Puddi_Puddin said:
Are you sure that you did it right? Did your phone show up as mentioned in the instructions?
Click to expand...
Click to collapse
Of course. Everything is done right. I also get that green "download complete" message.
p.s I also opened the phone. water indicators are fine and no major defects what can i see by eye... All connectors are good as well.

Puddi_Puddin said:
Are you sure that you did it right? Did your phone show up as mentioned in the instructions?
Click to expand...
Click to collapse
And yes, phone was connected right. :good: installed drivers with test mode on Win10 and got Snapdragon device in COM devices. As well the MsmDownload tool shows up my device in port #20

Any ideas?

djemm1996 said:
Any ideas?
Click to expand...
Click to collapse
Follow method 2 from the Hard Brick guide by Naman Bhalla and try two or three times.
Sometimes it takes more than once for restoration.

Since you opened the phone, i think your warranty is gone now.
If the msmdownloadtool didnt help you, there is nothing you can do i think.

try to flash again, and if it still maybe something short inside.
if you have disassembly your phone, try disconnecting various flex cable like camera, sim slot etc that connect to the mainboard, that doesn't prevent device from powered on, then try to turning it on.
if it still, check your mainboard, if you don't know how, send it back.

AcidNoteZ said:
Since you opened the phone, i think your warranty is gone now.
If the msmdownloadtool didnt help you, there is nothing you can do i think.
Click to expand...
Click to collapse
Is ir really gone? There is a still warranty void sticker on the screw there, but of course it's possible to see by eye that the phone has been opened.
I have an appointment with Level2 tech support @oneplus, they are going to remotely flash the entire OS, but do you think they are using pretty similar technique as the msmdownloadtool?

djemm1996 said:
Is ir really gone? There is a still warranty void sticker on the screw there, but of course it's possible to see by eye that the phone has been opened.
I have an appointment with Level2 tech support @oneplus, they are going to remotely flash the entire OS, but do you think they are using pretty similar technique as the msmdownloadtool?
Click to expand...
Click to collapse
They are doing the same thing like you did.
I already had a session since i thought they are going to do something "special"
You can try the remote session but im afraid that wont help you if you already did it multiple times.

What about battery? Charged?

drmuruga said:
What about battery? Charged?
Click to expand...
Click to collapse
Yes battery is charged of course. It's just doint the same thing. Turns on, after a while when bootscreen comes it just turns off and white notification led appears, after that nothing.

I tried to flash it with tool using method 2 for like 15 times with "download complete" messages, but still no luck at all. Tried to erase partritions with fastboot, flashing just only recovery, modded recovery etc. but I still cannot access the recovery nor system. I just don't get it why the phone does not boot into recovery if I flash it or boot it straight away, It just only turns off and that's it. nothing more. Only black screen and white led lighting all the time (after a while the phone turns warm).
I have read all the MsmDownloadTool thread in "Mega Unbrick thread" and saw that few people have experienced the very same situation as me, so I was wondering if there is any fix for this? It's so strange that I was just surfing the Web and it just turned off by it self with like static image for miliseconds and after that just black screen.
There should be any fix. I guess that it's just a partition error...

Ok, not good news. I had a little remote session before a while. They says it's already a hardware problem.

AcidNoteZ said:
Since you opened the phone, i think your warranty is gone now.
If the msmdownloadtool didnt help you, there is nothing you can do i think.
Click to expand...
Click to collapse
Pfffft you think manufacturers notice when you take apart phones? Hell I took apart my Xperia Z2 because it was having problems and then glued it back together with cyanoacrylate hahahaha (worst thing to do but wtv) and no one noticed though it was seemless and everything looked perfect

Guys, I've got something for you! Not really the same thing as Naman.
p.s. not saying its original hehehehe keep safe

man i got a very similiar problem but my op3 has a black screen i was also on low battery around 5-15% when my phone went off after i was in twrp

Actually I was on twrp too! Also I have recently noticed that recovery loading speed was far too long than normal one. I'm talking for something about 5-7 minutes after reboot into twrp. So, who knows what did happen. Just made an RMA request. Will see how it goes.
Anyway, I was on stock 7.1.1 and it's just rooted with custom recovery and that's it! Nothing more! Is that just a factory failure or maybe it's caused by drops i have had? Nothing serious for a 4-5 times for a half year. Of course I have used it even in winter when the snowflakes are coming down from the sky and little rain. Btw, these liquid indicators are white, so all safe. ::laugh:
A
makadama said:
man i got a very similiar problem but my op3 has a black screen i was also on low battery around 5-15% when my phone went off after i was in twrp
Click to expand...
Click to collapse