This is not a similar thread asking what to do and you all tell me to go to repair shop, I need answers if anyone has them, cause there is no thread on any forum on the internet that describes this:
I purchased NEW bricked Desire (Bravo) from a guy that got it from Belgium as a gift, for very cheap money. Guy turned it on for the first time here in Serbia and the phone worked 3-4 days, and then died. never rooted, everything stock.
I took the phone, and pushed Power button - and it turned on (Oh, how I regret I didnt use "volume down" at that point) and it got stuck at green HTC.
I took out the battery and after that - not once did it turned on, or LED turned on when charging or anything. No boot.
then I read all the threads I could find, and the conclusion is that it's bricked and it needs JTAG, and nothing else will help. But, after some time without battery in the phone, I putt it in, and the phone vibrated 7 times and not even a flicker from the screen.
I actually opened the device (it has Belgium warranty but with serbian custom regulations, sending it and receiving it back is more expensive than brand new Desire) and checked everything - good solder, battery good (it has voltage), everything is in place.
My question is, as I dont understand software part of the phone - HOW does it even vibrate 7 times, and if it's bricked - WHAT is giving the phone instructions to do so ... ? If it is able to vibrate in a pre-defined manner, then something is working inside the device. And that something acts random (didnt turn on with the guy, turned on once with me, now wont turn on again) so Im asking - what part of the SoC is actually working to enable that 7 vibrates, and why is it acting random .. ?
note: HTC NEVER gave ANY explanation on those 7 vibrations. phone-repair forums from Russia dont know the story behind that also.
I will eventually take it to a service shop where JTAG would be preformed, but I would so much like if there was another solution ... If it turned on once, how do I make it turn on again ... (so I could use ADB to sort out everything)
anyone with advanced knowledge on this one .. ?
Try to charge the battery in another phone and then try to turn it on using power+vol down. If that works 2.3 ruu is a solution for everything.
In my signature you have the explanation how HTC works, go to the thread and download the image.
Thanks nloooo but as I already said it - battery is ok. Tried it in another Desire - works, tried battery from another Desire in mine - phone wont work. Believe me - If there was a way for me to get into bootaloder or fastboot, I would do so by now. I am trying everything to avoid JTAG, and I wanna know why it will start once in 100 times, and why is this even happening.
looking for a motherboard online - boy those are expensive! they cost more than whole used unit ...
Ok, anyone please help -
I managed to "push" it into bootloader/fastboot by freezing the phone (good old technique) and now I can enter fastboot/bootloader but recovery doesnt work.
In order to run RUU I need to connect phone with PC, but every time I try to do that it says: USB device not recognized
If I run RUU, it says: Error [170]: USB Connection error
phone is S-ON and I only have RUU as a solution, but cant run it, cause PC wont recognize phone. I have HTC drivers installed, with Sync uninstalled, but still it wont work.
Could it be maybe that I need older Sync version, I read that somewhere .. ?
I think sync needs to be installed to run a ruu. Not 100% sure tho
Sent from my HTC Desire
jmcclue said:
I think sync needs to be installed to run a ruu. Not 100% sure tho
Sent from my HTC Desire
Click to expand...
Click to collapse
+1
HTC Sync or HTC drivers.
I installed SYNC but now im freezing phone again (so I could enter HBOOT), will post results in couple of minutes.
As im figuring out - device surely has Hardware failure, being that only frozen is able to boot. since freezing shrinks matter, my conclusion is that EMMC or CPU solder got melted by the working temperature, thus making Tin (or whatever is used for soldering these days) touching somehow on two sepparate solders, but when is frozen, they "go apart".
Once I start it, will check this -
http://forum.xda-developers.com/showthread.php?t=1284196
to determine if EMMC is fried or unsoldered.
Not sure about that thread, it points to problem with eMMC chip that Desire S has not regular Desire. For Desire the most common hardware problem is overheating motherboard issue, usual for PVT1 devices.
And that's just what im going to do - it lays opened on my table now, and there is a big design flaw - NOTHING disperses heat from the CPU cover!!!
I cant believe that HTC did this, this is just like not plugging a CPU cooler onto the motherboard of a PC.
all things aside, the problem lays in bad motherboard, and even if I purchase another one, same thing will happen over time cause CPU cant get rid of the heat.
- reflow solder (im good with that, have proper tools)
- thermal paste over cpu, before covering it back with metal
Im pretty sure this will work. phone is brand new, could get out of the factory if it had such a big flow, it must be overheating problem caused by high CPU usage. will post results later this evening, when I do a reflow soldering.
Well, I have mine for almost 2 years, used it with advance roms (sense 3.0 and 3.5) usually overclocked, sometimes it gets hot, but I can't say I had overheating issue.
The problem is not related to all devices, it's usually connected to PVT1 version of device (which was the first series) that later got fixed.
havent checked my version, but the fact is - it works! (partially) Oh, and on that topic - how do I find out my version .. ? is there a hard print .. ?
After hot air gun (reflow pin by pin could not be done, this shi* is small!) and after putting thermal paste onto the CPU - it goes past HTC logo, tries to load Sense, and then freezes. So all this trouble with software/firmware was for nothing, I guess .. I just need to reflow it a bit more, I got scared that those small pins would melt fast. Boy, I really hope this will work, cause when HW is the problem, I know my stuff, or at least I think I do ..
EDIT: well FOK MI! I dont believe this ...
I am the first to ever open this unit. I removed all the warranty stickers. On top of CPU, there IS NO METAL COVER! Nothing to act as a Heat sink! this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I guess this gray plate is Aluminum or iron, and the other one small is copper, but I dont have none. No wonder phone hangs 10sec after boot. Im off to make a cover, damn you HTC, how did this ever got out of the factory .. ?
Hi Igoritza, Just been reading this thread as I have a Desire with exactly the same symptoms as you describe.
Did you ever solve the problem?
ludemon said:
Hi Igoritza, Just been reading this thread as I have a Desire with exactly the same symptoms as you describe.
Did you ever solve the problem?
Click to expand...
Click to collapse
same here.. ANY SOLVE ?
Igoritza said:
Ok, anyone please help -
I managed to "push" it into bootloader/fastboot by freezing the phone (good old technique) and now I can enter fastboot/bootloader but recovery doesnt work.
In order to run RUU I need to connect phone with PC, but every time I try to do that it says: USB device not recognized
If I run RUU, it says: Error [170]: USB Connection error
phone is S-ON and I only have RUU as a solution, but cant run it, cause PC wont recognize phone. I have HTC drivers installed, with Sync uninstalled, but still it wont work.
Could it be maybe that I need older Sync version, I read that somewhere .. ?
Click to expand...
Click to collapse
pl explain in detail how to push into fastboot.... My phone is not switching on!!
---------- Post added at 01:20 AM ---------- Previous post was at 01:03 AM ----------
Igoritza said:
This is not a similar thread asking what to do and you all tell me to go to repair shop, I need answers if anyone has them, cause there is no thread on any forum on the internet that describes this:
I purchased NEW bricked Desire (Bravo) from a guy that got it from Belgium as a gift, for very cheap money. Guy turned it on for the first time here in Serbia and the phone worked 3-4 days, and then died. never rooted, everything stock.
I took the phone, and pushed Power button - and it turned on (Oh, how I regret I didnt use "volume down" at that point) and it got stuck at green HTC.
I took out the battery and after that - not once did it turned on, or LED turned on when charging or anything. No boot.
then I read all the threads I could find, and the conclusion is that it's bricked and it needs JTAG, and nothing else will help. But, after some time without battery in the phone, I putt it in, and the phone vibrated 7 times and not even a flicker from the screen.
I actually opened the device (it has Belgium warranty but with serbian custom regulations, sending it and receiving it back is more expensive than brand new Desire) and checked everything - good solder, battery good (it has voltage), everything is in place.
My question is, as I dont understand software part of the phone - HOW does it even vibrate 7 times, and if it's bricked - WHAT is giving the phone instructions to do so ... ? If it is able to vibrate in a pre-defined manner, then something is working inside the device. And that something acts random (didnt turn on with the guy, turned on once with me, now wont turn on again) so Im asking - what part of the SoC is actually working to enable that 7 vibrates, and why is it acting random .. ?
note: HTC NEVER gave ANY explanation on those 7 vibrations. phone-repair forums from Russia dont know the story behind that also.
I will eventually take it to a service shop where JTAG would be preformed, but I would so much like if there was another solution ... If it turned on once, how do I make it turn on again ... (so I could use ADB to sort out everything)
anyone with advanced knowledge on this one .. ?
Click to expand...
Click to collapse
Pl explain how to get it into fastboot. My htc desire x is not booting at all.
I did a factory reset and it was working fine , then i went into twrp(2.7 the new one) and in advanced i selected restore original image.Then when i reboot it vibrated many times so i removed my battery now the phone is not switching on.... the only thing i see is the orange light when i connect usb/power cord.
Begin12 said:
pl explain in detail how to push into fastboot.... My phone is not switching on!!
---------- Post added at 01:20 AM ---------- Previous post was at 01:03 AM ----------
Pl explain how to get it into fastboot. My htc desire x is not booting at all.
I did a factory reset and it was working fine , then i went into twrp(2.7 the new one) and in advanced i selected restore original image.Then when i reboot it vibrated many times so i removed my battery now the phone is not switching on.... the only thing i see is the orange light when i connect usb/power cord.
Click to expand...
Click to collapse
Post in the desire x forum they will help you.
Sent from my HTC Desire using XDA Free mobile app
even my htc desire x has same problem
before this happened i dropped my phone 3 times in 2 months...but the phone was still normal..but suddenly it did'nt start then i gaved my phone to a private phone repairing shop..the man told me that therz a circuit problrm in the phone and difficult to fix it.....before it i tried by power+vol down but any option does not work..same it keeps on vibrating 7 times ...what should i do now...
Related
Hi,
My Universal fail to power on.
It do not enter boot loader with light + power + reset and show no signs of life. Batteries are both new and tested in other working units.
When connected to USB, PC reports "USB device not recognised"
I had ROMS flashed but failed at 99%. When reset the units did not power on or showed any signs of life.
It had been working fine up until the unsucssesful flash update.
I would like to be able to use it for work .
Please either post replies here or email me [email protected]
Your time and efforts will be greatly appreciated.
Regards,
quou
quou2006 said:
Hi,
My Universal fail to power on.
It do not enter boot loader with light + power + reset and show no signs of life. Batteries are both new and tested in other working units.
When connected to USB, PC reports "USB device not recognised"
I had ROMS flashed but failed at 99%. When reset the units did not power on or showed any signs of life.
It had been working fine up until the unsucssesful flash update.
I would like to be able to use it for work .
Please either post replies here or email me [email protected]
Your time and efforts will be greatly appreciated.
Regards,
quou
Click to expand...
Click to collapse
Please try to enter the bootloader mode in a bright room as it is very difficult to see in poorly lit environment. Till you enter the bootloader mode your device will not be recognised. Perhaps one of the three keys is getting released..the light button is the usual culprit. Once you are in the bootloader you can reflash.
Thank d_ranade for your answer.
I am sure the screen is 'all black' and I've tried to press the buttons several times.
I think the main problem now is how to enter the Bootloader.
I sometimes find it takes several goes to get into Bootloader mode. If not, have you tried a hard reset?
I've tried whatever i can do. Hard reset is useless too.
quou2006 said:
Hi,
My Universal fail to power on.
It do not enter boot loader with light + power + reset and show no signs of life. Batteries are both new and tested in other working units.
When connected to USB, PC reports "USB device not recognised"
I had ROMS flashed but failed at 99%. When reset the units did not power on or showed any signs of life.
It had been working fine up until the unsucssesful flash update.
I would like to be able to use it for work .
Please either post replies here or email me [email protected]
Your time and efforts will be greatly appreciated.
Regards,
quou
Click to expand...
Click to collapse
I have sent you a pm, it should help you.
-Jwrightmcps
Thank Jwrightmcps for your help, but i can not enter the Bootloader ,so can not use mtty to do more.
Unable to start/see bootloader
I seem to have the same problem with my upgraded universal which was working fine for about ten days. Then I installed TomTom on it and again it was all working that evening.
Then, when I turned it on the screen went blank (white), so I re-flashed it, but, part way through the screen went black, so I left it connected for further hour and nothing. I have since been unable to get it to do anything, it is not recognised by activesynch, it will not charge (either from the mains or the USB on either of the batteries) nor will it turn on or respond in any way.
I have unset ‘allow usb connections’. I have tried solidly for +/-10 minutes doing the backlight + on/off button and reset bit - repeatedly, with my wife helping to ensure all buttons were being pressed. All I got was a message from MicroSoft telling me that ‘One of the USB devices attached to this computer has malfunctioned and Windows does not recognize it’. The only positive thing is that every time I do it and depress the reset, the red LED flashes (provided I leave the USB cable in) but at no point have either of us been able to see any writing on the screen.
Any guidance (apart from where to take it for recycling) would be welcome…
It happened to me several times too. Even in the old ROMS. But had learned many things out of it. I removed the battery. Wait for several seconds or maybe minute before placing it back. And after placing it back wait again for some time before doing the "power + light + reset" (bootloader). At some point when I am in the bootloader mode already and reflashing, connected to the PC already, the screen went blank again. So I'm sure that something went wrong again. I repeated the procedure again (removing battery, placing it back etc...) and the reflashing continued. It takes patience (maybe).
After having experienced this so many times, I'm beginning to assume that it is not because the battery is "bad" or there is a problem on the ROM being reflashed. It is on how it (the battery) is connected to the unit. The reason why it does not turn on, charge even if connected to the charger, does not hard reset, does not react to anything... I just don't know.
One thing more, the procedure I said above sometimes does not work at once. But at least I managed to "resurrect" my device several times.
This I am sure, it is not in the ROM that is being flashed or the update...
Hope this helps,
Lelen
lelen, Thanks for your assistance. I tried last night, but it still could not enter the bootloader mode...
I have the same problem =( and i don't know what to do, someone told me that i have to change motherbord to resolve this problem, i hope there are some other solutions.
Dead Uni
I too had this problem. With the device not responding at all and not able to enter bootloader stops mtty from working.
Only way i could get it to work was to take it to an O2 shop to send it away for repair (luckily the O2 XDA range has a 2 year warranty and because its completely dead they cant tell the OS has been modified).
Unfortunatly like the previous post i think it can only be fixed by replacing the mainboard.
Hi all, i found this thread http://forum.xda-developers.com/showthread.php?t=291097&page=6
so many people have the same problem , and nobody found a solution? i can't believe that on all this universals died motherboard, and there is no way to fix it with some special cable or some programm.
yes,i post the last reply of the thread you mentioned above, but nobody can resolve it.
I recommend you remove the battery and leave it over night. Put the battery back on, ensure it is properly mouted and try booting it.
It worked for some, no idea why though. I'm actually suspecting a bad battery mounting, which results in the motherboard unable to detect a battery is iserted, thus refusing to boot.
finally managed to get mine fixed, mine was out of warranty too and sent it off to carphone warehouse express service, took 3 weeks but was fixed with a standard chargeable repair charge of £40
I have a somewhat similar problem but not from upgrading. I accidentally dropped the device after a successful upgrade and the screen got damaged. Someone picked it up, opened it and noticed it was on even though the screen was damaged, and then closed it back. By the time I got it back it was dead and could not come on again. I have since replaced the damaged screen, but the device will not come on and cannot enter bootloader either. The device get warm if the battery is left on.
coolbeans252 said:
finally managed to get mine fixed, mine was out of warranty too and sent it off to carphone warehouse express service, took 3 weeks but was fixed with a standard chargeable repair charge of £40
Click to expand...
Click to collapse
i guess thats what i will have to end up doing
anyone goten repairs done in north america?
( i live in western canada)
got the same problem
sofene said:
I have a somewhat similar problem but not from upgrading. I accidentally dropped the device after a successful upgrade and the screen got damaged. Someone picked it up, opened it and noticed it was on even though the screen was damaged, and then closed it back. By the time I got it back it was dead and could not come on again. I have since replaced the damaged screen, but the device will not come on and cannot enter bootloader either. The device get warm if the battery is left on.
Click to expand...
Click to collapse
hi..please let me know if your device is fixed and how you managed to fix it. my email id is [email protected]
http://forum.xda-developers.com/show...6&postcount=52
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!
My friend is running CM 7 on his Tmobile G2.
He was describing that yesterday was acting weird with market downloads.
Here is what he he emailed me on what happened.
the phone was acting normal throughout my day until the evening towards the night, i noticed it failed to finish downloading the update for google earth along with google maps. the phone was fine, and then i pulled it out of my pocket a few times and saw multiple times that it was randomly turned off. i would turn it back on and it would still give me the same issue. when i got home and plugged it in to charge, it would boot and then get to the main home screen telling me that google maps is downloading to update. however the update would be frozen, and a few seconds later the phone would freeze altogether, forcing me to turn it off by pulling out the battery. this happened about 4 times, and now has reached the point that it has become a brick and refuses to turn on or show the charging light
any suggestions on what might be wrong with the phone? Thanks in advance. Im running Cm7 on my phone and never experienced this issue.
same happend to me 3days ago, phone running then freezed... bootloop after batterypull... recovery worked for 2 times but had problems with flashing new rom/backing up -> errors with cache partition...
after 4hours of letting it stay off -> it wont turn on again und wont charge (no LED)
tried it with another dz battery+charger... no change... i wrote htc and they answered within 1hr that i have to send it in without battery...
i guess its a known problem (or why wouldnt they want to have me sending in charger+battery .. if its a power-on problem..)
there are semibrick threads here and in other forums.. but they all don't suffer from the power on problem... so i guess i did the right thing sending it in
edit: never had heat issues, never had random reboots, no overclock, no indication of an update from any app did any harm to my phone, running cm7 for 3 weeks without any problems, no hboot flash, no radio flash ... nothing that would indicate a risk of brick (according to guides & forum threads)... first htc that ever failed for me ;(
Thanks for the reply. I will forward it to my friend. I think he is going to try to exchange it at the store and if it all fails we are going to try HTC.
have any of you tried to boot into recovery? did you have eng-hboot on your devices? go to #g2root
its complete dead as in dead... no LED light, no turn on, no hboot mode (or what its called when you press vol+power key).... i dont have a g2 but a unbranded european dz.. hboot and radio was never touched by me
Similar thing happened to me. My phone kept frozing on me running cm7..was fine for a week though.
So I booted into recovery..wiped cache,factory reset flashed another rom got bunch of erros recovery thing rebooted stuck i n htc logo for like 20min yanked out battery rebooted and it never rebooted back. No hboot,no nothing.
My light indicator still worked though but no hboot or anything.. got a new one now have to send the old one back to tmobile but I'm scared that they're gonna charge me for removing void stickers.
Even though I checked twice that removing void sticker won't avoid warranty according to tmobile customer chat sevice..
So I'm thinking about swiping out the sticker that contains serial number and such on back of our phone with the old one and tell them the new one came without a void sticker lolol
Sorry I got way off topic rofl..
Sent from my HTC Vision using Tapatalk
We went to the store today and exchanged it for another g2. The guy didnt ask any questions and exchanged it happily for a new one.
This very same thing happened to me today. Updated to CM 7.0.3 from 7.0.1 and the phone was freezing when installing items from the market. Pulled the battery and the phone was stuck on the boot animation. Pulled the battery again, and now it will not start at all. No charging light, no nothing. Had more than 50% charge, and now it seems entirely unresponsive. I can't use the power w/ volume button technique either, because the phone does not respond.
Seems like somehow I have bricked the phone, or the phone just coincidentally died just after updating to CM 7.0.3? (seems unlikely)
just a short update on my case:
i got the mobile back from HTC repairs.
they exchanged my "mainboard" (changed IMEI) under warranty.
i don't know what emmc chip i had before cause it died so fast, but my usb deviceIDs changed completely and are now simmilar to the ones in the cm wiki.
my current emmc is now:
$ cat /sys/devices/platform/msm_sdcc.2/mmc_host/mmc0/mmc0:0001/name
SEM04G
Click to expand...
Click to collapse
might help ppl.
Hi everybody!
I have an almost 2 years old DHD which I think is completely bricked. It was working for approximately one years perfectly and then suddenly it stopped working. Whenever I tried to turn it on, it only vibrated once and did nothing more. Sometimes it turned on and these working periods were enough to restore to stock condition (It was rooted and had Eng S-OFF before.). I had brought it to service and they said they was not going to repair it as the device got water damaged. I'm pretty sure it was not! After a few weeks, it started working again. I was using it for 3 months then it bricked again and it's the situation today as well.
Previous week I looked into the development thread and saw all of these new amazing roms. So I took my DHD to see if it's working or not. The situation is the same. Everytime I power it on, the phone only vibrates once and nothing happens. I'm not able to get into hboot mode. At some very rare occassions the phone turns on and works flawlessly till reboot. When I connect it with USB, the computer doesn't recognize it. Battery is charged, I even tried another battery.
Does anybody know what happens with the phone? I'm open to any possible solutions to try. Please don't suggest to bring it to service or repair it, because I have another phone, just want to try to recover it and ask your ideas about the problem.
Thanks in advance!
Greetings,
Adam
So you say you cant enter in fastboot or recovery?
Since it's intermittent, my guess is it is a hardware problem. Some kind of bad contact/loose connection. Make sure everything looks good on your battery door and the battery contacts inside the phone.
paescheh said:
So you say you cant enter in fastboot or recovery?
Click to expand...
Click to collapse
I cannot enter into hboot mode. Didn't try recovery, but assume it's the same.
waterbox said:
Since it's intermittent, my guess is it is a hardware problem. Some kind of bad contact/loose connection. Make sure everything looks good on your battery door and the battery contacts inside the phone.
Click to expand...
Click to collapse
I also think it's a hardware problem. Will take a more careful look at the battery.
Sent from my CM10-powered GT-I9103
need help
im having trouble finding post option on page.i recently rooted my phone.all was well until i used font app sms pro and emoji plug in.i also forgot o disable auo update.worked for 10 minutes then apps wouldnt load.whil attempting to uninstall via recovery...since no other options worked...i wiped my system....now recovery says E:no os...please help...im using vm htc 1 v cdma...
goofed again said:
im having trouble finding post option on page.i recently rooted my phone.all was well until i used font app sms pro and emoji plug in.i also forgot o disable auo update.worked for 10 minutes then apps wouldnt load.whil attempting to uninstall via recovery...since no other options worked...i wiped my system....now recovery says E:no os...please help...im using vm htc 1 v cdma...
Click to expand...
Click to collapse
Wrong sub forum buddy, post in the One V Forum.
Its possible that there isn't "water damage", but there could be moisture getting into the phone causing it to act erratic. To cancel out that possibility, submerge it in a closed container full of rice for a few days
Sent from a satellite
Ok guys, so I'm having an issue with my Note 10.1 2014 Edition. Whenever the screen times out, or you lock it, the screen will not come back on. The buttons will light up, but the screen is unresponsive. Hold the power button for a reboot and it reboots, screen works fine until the next lock. So obviously first thing, wiped everything, and reloaded Hypderdrive, only to get the same issue. So I go in again to recovery, and while I'm doing some research, TWRP times out and the screen goes black, and again, I'm unable to "wake" the device. Now I'm thinking hardware, but the power button is being recognized to lock it, so it should be recognized to unlock it as well and it is because the button lights come on. I've gone in, did a complete wipe including /system and /data and I'm currently trying to load a new rom to my microsd card to load, but the screen timed out again and I have to reboot the device back into recovery each time to get the screen to work. I'm pretty sure the root method I used, voided my warranty, so sending it in is probably not an option. When I reboot into download to check the status, It just says Downloading... Do not turn off target!! and I see no information in the top left of the screen. Anyone have any idea as to what could be causing the screen to do this? I'm kinda lost at this point! Thanks in advance.
P.S. So I was able to get into Download, and found my Current Binary is Custom, my System Status is Custom, and my Warranty Bit is 1, so I'd assume warranty is out of the option.
P.P.S I got a new rom loaded everything flashed fine, booted, let it set, when the screen timed out, again won't turn on. I can almost say 100% it's not a rom/Kernel issue. But beyond that I'm lost!
scoot05redss said:
Ok guys, so I'm having an issue with my Note 10.1 2014 Edition. Whenever the screen times out, or you lock it, the screen will not come back on. The buttons will light up, but the screen is unresponsive. Hold the power button for a reboot and it reboots, screen works fine until the next lock. So obviously first thing, wiped everything, and reloaded Hypderdrive, only to get the same issue. So I go in again to recovery, and while I'm doing some research, TWRP times out and the screen goes black, and again, I'm unable to "wake" the device. Now I'm thinking hardware, but the power button is being recognized to lock it, so it should be recognized to unlock it as well and it is because the button lights come on. I've gone in, did a complete wipe including /system and /data and I'm currently trying to load a new rom to my microsd card to load, but the screen timed out again and I have to reboot the device back into recovery each time to get the screen to work. I'm pretty sure the root method I used, voided my warranty, so sending it in is probably not an option. When I reboot into download to check the status, It just says Downloading... Do not turn off target!! and I see no information in the top left of the screen. Anyone have any idea as to what could be causing the screen to do this? I'm kinda lost at this point! Thanks in advance.
P.S. So I was able to get into Download, and found my Current Binary is Custom, my System Status is Custom, and my Warranty Bit is 1, so I'd assume warranty is out of the option.
P.P.S I got a new rom loaded everything flashed fine, booted, let it set, when the screen timed out, again won't turn on. I can almost say 100% it's not a rom/Kernel issue. But beyond that I'm lost!
Click to expand...
Click to collapse
So I was messing with it some more after work today and found a few more pieces to the puzzle. After rebooting it in a bright room, I found the screen is on, but the backlight isn't. The screen is usable and responsive. Second thing is the brightness slider no longer works, it's just one brightness level and can't be adjusted. I've read online, that there maybe a loose ribbon cable, so I'm going to look into that alittle bit. I'm really hoping the backlight and LCD aren't shot! Again if anyone has any experience or ideas, please let me know!
SO I was using Triangle Away to try to clear the flash counter, as I was filling out a service request form from Samsung, and after the reboot the screen was brighter. I then tried the brightness slider..it worked and locked and unlocked it and the screen came back on. IDK what fixed it (maybe Triangle Away????) but it's working now! I'm hoping it sticks! I hope no one else has this issue, but maybe this will help!
Sorry for bumping this old thread, but I have found a solution! (at least for me)
There is suprisingly little to find about this issue, so that's why I've made this quick post.
I had this issue as well, but after flashing the stock modem (NON-HLOS.bin) it was resolved. (fastboot flash modem NON-HLOS.bin)
Currently I'm on CM11S XNPH05Q with stock kernel, OnePlus One.
I think it had to do with me going back from CM12 (Lollipop-based) to CM11S (KitKat-based).
help urgently needed
awesomTNT said:
Sorry for bumping this old thread, but I have found a solution! (at least for me)
There is suprisingly little to find about this issue, so that's why I've made this quick post.
I had this issue as well, but after flashing the stock modem (NON-HLOS.bin) it was resolved. (fastboot flash modem NON-HLOS.bin)
Currently I'm on CM11S XNPH05Q with stock kernel, OnePlus One.
I think it had to do with me going back from CM12 (Lollipop-based) to CM11S (KitKat-based).[
hello awespmeTNT
i on on kitkat 4.4.2
can you please explain me stepwise how to flash stock modem to galaxy note 10.1 2014th edition SM-P601
my base band is : P601XXUCNJ1
kernel version is 3.4.39-3098518 thank u
need the help urgently
Click to expand...
Click to collapse
ranzzzit said:
hello awespmeTNT
i on on kitkat 4.4.2
can you please explain me stepwise how to flash stock modem to galaxy note 10.1 2014th edition SM-P601
my base band is : P601XXUCNJ1
kernel version is 3.4.39-3098518 thank u
need the help urgently
Click to expand...
Click to collapse
I'm sorry man, but I have no experience with the Galaxy Note 10.1 2014...
I tried to search for a solution, but I couldn't find much since there are all these different versions of the Note 10.1.
I think you have to use Odin to flash custom zips and such for your device.
I couldn't find the modem for the P601 (NON-HLOS.bin), but you could open a new thread asking for it?
I really hope you'll find a solution.
Also, have you tried a factory reset?
If you haven't done anything like rooting, flashing costom ROMs etc, your warranty shouldn't be void and you could return your device.
That's what I'd do.
Best of luck.
scoot05redss said:
So I was messing with it some more after work today and found a few more pieces to the puzzle. After rebooting it in a bright room, I found the screen is on, but the backlight isn't. The screen is usable and responsive. Second thing is the brightness slider no longer works, it's just one brightness level and can't be adjusted. I've read online, that there maybe a loose ribbon cable, so I'm going to look into that alittle bit. I'm really hoping the backlight and LCD aren't shot! Again if anyone has any experience or ideas, please let me know!
Click to expand...
Click to collapse
can you help scoot05redss
Sorry, I haven't flashed any modems to my Note 10.1, wish I could be of more assistance
scoot05redss said:
Sorry, I haven't flashed any modems to my Note 10.1, wish I could be of more assistance
Click to expand...
Click to collapse
can u give any alternative way to solve the problem
like
can u upload the apk file of triangelaway that solved your problem
and can u mention what was your firmware version
thanx
Sorry buddy, I really can't. Since, my tablet had been damaged and I had flashed roms since. I can't remember what version I was using. Triangle away apk can be found from a Google search but I don't have the apk for the one I used. Sorry again! I know it's a PITA!
Hello mates!
I just had this problem some days ago, when i accidentaly dropped my sm p601. It was working fine so i wasnt worried at that time.
Next day it presented the exact symptoms that you guys described. The screen couldn't be turned on after being turned off, brightness controls not working.
I realized it could be a hardware problem because of the drop that the device suffered, then i stumbled in this topic where our friend scoot05redss mentioned:
I've read online, that there maybe a loose ribbon cable
Click to expand...
Click to collapse
Well, since i live in Brazil and we have little to none authorized customer service support from Samsung, i decided to open the device.
(I searched for a disassembly video in youtube. There are one or two avaliable)
It happens that the mentioned LCD ribbon cable is the first thing to pop up when you open the device, so i decided to give it a try, and guess what, it worked.
I just opened the device, lifted the cable lock (that black plastic thing that sits upon the cable) and i gently moved the cable inside the conector (I didn't even had to remove it).
Closed, turned on, everything working as before.
Ps.: Its kinda hard to open the device without the appropriate tool shown in the video, but i managed to open it with a knife, taking maximum care not to leave marks in the screen (the silver frame however couldnt be spared from some scratches.
Thanks for the help!
I can confirm that disconnecting the LCD ribbon cable while the unit is on, reconnecting it, and then rebooting the device fixed the issue for me. My wife accidentally knocked it off her nightstand and while using it during the middle of the next day the screen suddenly faded to black. After noticing that the screen was still on but the back light wasn't working, I popped it open and tried disconnecting the battery but didn't try the LCD ribbon, didn't think that'd make a difference. But I'm glad that's all it was!
Ive got this issue on a grand prime sm-g361h as soon as i lock the screen or it times out thats it, doesn't turn back on until i hard reboot it. super frustrating.. going to try flash a modem to see if it fixes
fredquintao said:
Hello mates!
I just had this problem some days ago, when i accidentaly dropped my sm p601. It was working fine so i wasnt worried at that time.
Next day it presented the exact symptoms that you guys described. The screen couldn't be turned on after being turned off, brightness controls not working.
I realized it could be a hardware problem because of the drop that the device suffered, then i stumbled in this topic where our friend scoot05redss mentioned:
Well, since i live in Brazil and we have little to none authorized customer service support from Samsung, i decided to open the device.
(I searched for a disassembly video in youtube. There are one or two avaliable)
It happens that the mentioned LCD ribbon cable is the first thing to pop up when you open the device, so i decided to give it a try, and guess what, it worked.
I just opened the device, lifted the cable lock (that black plastic thing that sits upon the cable) and i gently moved the cable inside the conector (I didn't even had to remove it).
Closed, turned on, everything working as before.
Ps.: Its kinda hard to open the device without the appropriate tool shown in the video, but i managed to open it with a knife, taking maximum care not to leave marks in the screen (the silver frame however couldnt be spared from some scratches.
Thanks for the help!
Click to expand...
Click to collapse
I had the same problem and fixed it in the same way.
n3xus5 said:
Ive got this issue on a grand prime sm-g361h as soon as i lock the screen or it times out thats it, doesn't turn back on until i hard reboot it. super frustrating.. going to try flash a modem to see if it fixes
Click to expand...
Click to collapse
Ok Issue Was MODEM i dd modem.img to modem partition from another phone exact same that working and its now 100% up n running only issue now is i have duplicate IMIE numbers
Color issue after screen off
My Note 10.1 2014 (P605) is ruining smoothly for 3.5+ years without much trouble. Now, it's screen is giving some color issue. Tab boots fine and colours shown correctly. Once screen is off, it start to invert (not sure whether the correct word) colours. Later I observed screen not switching on but accepting touch commands.
I tried color invert setting, it seems not effective. Flex cable was not loose but sometimes reconnecting resolved temporally. Re-flashed the OS but issue came up after few days. This may seems like screen fault, but screen working fine at boot till screen off.
Does anyone have similar experience or advice to help me out.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Important Experience !!!
scoot05redss said:
Ok guys, so I'm having an issue with my Note 10.1 2014 Edition. Whenever the screen times out, or you lock it, the screen will not come back on. The buttons will light up, but the screen is unresponsive. Hold the power button for a reboot and it reboots, screen works fine until the next lock. So obviously first thing, wiped everything, and reloaded Hypderdrive, only to get the same issue. So I go in again to recovery, and while I'm doing some research, TWRP times out and the screen goes black, and again, I'm unable to "wake" the device. Now I'm thinking hardware, but the power button is being recognized to lock it, so it should be recognized to unlock it as well and it is because the button lights come on. I've gone in, did a complete wipe including /system and /data and I'm currently trying to load a new rom to my microsd card to load, but the screen timed out again and I have to reboot the device back into recovery each time to get the screen to work. I'm pretty sure the root method I used, voided my warranty, so sending it in is probably not an option. When I reboot into download to check the status, It just says Downloading... Do not turn off target!! and I see no information in the top left of the screen. Anyone have any idea as to what could be causing the screen to do this? I'm kinda lost at this point! Thanks in advance.
P.S. So I was able to get into Download, and found my Current Binary is Custom, my System Status is Custom, and my Warranty Bit is 1, so I'd assume warranty is out of the option.
P.P.S I got a new rom loaded everything flashed fine, booted, let it set, when the screen timed out, again won't turn on. I can almost say 100% it's not a rom/Kernel issue. But beyond that I'm lost!
Click to expand...
Click to collapse
"Ok guys, so I'm having an issue with my Note 10.1 2014 Edition. Whenever the screen times out, or you lock it, the screen will not come back on. The buttons will light up, but the screen is unresponsive. Hold the power button for a reboot and it reboots, screen works fine until the next lock."
I was been displayed dark screen (Death screen) by shock on road. Because I put my tablet Samsung note 10.1 P601 (2014 edition) in basket of motorbike. These are solutions:
- Case 1:
If dark screen and the buttons are light up like this question then you need unplug only LCD cable inside tablet and plug again.
- Case 2:
If Death screen and it's no light then you need plug and replug power cable and LCD cable inside table.
" 2 these case you can search and see YouTube How to open and fix black screen Samsung note 10.1 2014"
udeshjr said:
My Note 10.1 2014 (P605) is ruining smoothly for 3.5+ years without much trouble. Now, it's screen is giving some color issue. Tab boots fine and colours shown correctly. Once screen is off, it start to invert (not sure whether the correct word) colours. Later I observed screen not switching on but accepting touch commands.
I tried color invert setting, it seems not effective. Flex cable was not loose but sometimes reconnecting resolved temporally. Re-flashed the OS but issue came up after few days. This may seems like screen fault, but screen working fine at boot till screen off.
Does anyone have similar experience or advice to help me out.
Click to expand...
Click to collapse
Living after few months with this problem I can conclude following.
1. It is very difficult to find a pattern for screen to go pink or black. However, I noticed that problem comes frequently when it was used by my baby.
2. Disconnecting and reconnecting LCD cable temporarily resolve problem every time. May be hoangctm is more accurate on procedure.
3. I use this tablet every day. 45min video, 2 x 15min streaming and 1 h reading. Steady use of tablet does not give problems.
4. It is possible to replace LCD flex cable without dismantling screen and this is my next step.
I was also experiencing this issue. What would happen is that my Samsung Galaxy Note 14.1 would work well after a reset but as soon as it locked you couldn't see the screen.
I tried the solution posted in this forum. I opened up the tablet and repositioned the LCD ribbon cable while the screen was active. The tablet is now working well. I can activate the tablet properly after the screen has locked. Thank you all.