Related
My Friend has a HTC Wildfire, he's on a tour with his friends
Problem starts now , He was talking with his friend and suddenly screen went blank. He's using VillianROM on it now when he switches on he can't see the screen at all, but phone it self works when someone calls he's still able to answers it. he cant flash new ROM Also. he can't see screen so
Any Help ? anyone had such kind of a problem with HTC ?
maheshpatel said:
He was talking with his friend and suddenly screen went blank. He's using VillianROM on it now when he switches on he can't see the screen at all, but phone it self works when someone calls he's still able to answers it.
Click to expand...
Click to collapse
This is certainly not related to VillianROM in any way.
I think it's a hardware problem - there's something wrong with display panel. If the backlight is dead you should barely see very dark image on the screen in bright lightning conditions.
Anyway, looks like there's nothing you nor your friend can do to fix it. You need to send it to service.
maheshpatel said:
he cant flash new ROM Also. he can't see screen so
Click to expand...
Click to collapse
If the phone has USB debugging enabled by accident (I guess it's hard to turn it on blindly) then you can access it using adb shell. If you have custom recovery image installed, such as Clocwork or Amon_RA, you can boot to it and fave full access to your phone through USB using adb (or fastboot) so you can flash new ROM images.
oyah said:
If you have custom recovery image installed, such as Clocwork or Amon_RA, you can boot to it and fave full access to your phone through USB using adb (or fastboot) so you can flash new ROM images.
Click to expand...
Click to collapse
Yes, what he said ^^.
I'll just add one more thing. To get to custom recovery easily, pull the battery out and put it back in again. Then perform what ever key combination to boot custom recovery.
Good luck to your friend!
You might also have more luck posting in the Wildfire sections where they me able to help. It does seem like a Hardware issue with the screen to me? Was it dropped or anything?
It seems like hardware. Probably connection between screen and PCB.
ya his phone dropped many times, ya it seems like hardware issue to me also..
Hello people, thanks for reading and trying to help in advance hehe
ok here it goes ....
i bought a galaxy tab 10.1v "Australian Vodafone Version" a while back, and since me and other users that own this pices of **** didn't get updates and stuff i decided to "unlock+Root+rom". I did that successfully after following guieds:
unlock :http://forum.xda-developers.com/showthread.php?t=1064793
root+room: http://forum.xda-developers.com/showthread.php?t=1079781
Everything wsa fine and i had the super user and everything, but in the second guide it says it is recomended or something like that to download ROM Manager from the market which i did, and i started the app and and did a backup. My Tab rebooted to a blank screen , i waited for a while but with no luck so i turned off and tried to go to DW mode or recovery mood so i can at least connecte it to odin3 and do something. When press V- + Power theres no DW nor recovery mode all i see is one smmall line on the left top corner that says "Booting Recovery Kernal Image#"
When i plug the usb into my computer nothing happenes no sound , no new device installing no nothin. but since i have been reading alot regarding this issue, i read something about APX mode and NVflash here and many other websites but i followed this guide :
http://forum.xda-developers.com/showthread.php?t=1130574
i got my tab connected but i couldn't do NVflash because whenever i do
"--sync" or "nvflash --bl bootloader.bin --go"
i get this :
Nvflash started
rcm version 0X4
Command send failed (usb write failed)
some say that that means the device is locked eventho i pretty sure it not because i had the lock logo. anyway ...
just to answer every possible question in advnce and give more info :
*its a 10.1v "Vodafone Australia Version"
*was working fine after root/rom
*stoped working after using the app "ROM Manager" (i think its not compactible)
* the device on somekinda boot loop, the screen would turn on and off "blank screen with nothing in it no sound also"
* pressing Volum down + Pwer will taking me to a blank screen with one little line that says "Booting Recovery Kernal Image#"
*when i plug the usb to the computer nothing hapenes
* in APX mod is working but i cannot do anytning since the NVflash won't work.
* I followed everything step by step
Does that mean my device is useless ? is there anyway to get it back to life ?
Thank you and sorry for the spilling mistakes as im using a F'ed up keyboard
one more thing i did :
I let the battery drain overnight and pluged charged it again hopeing that will help, the battery logo won't even show up, just a blank screen
thanks
Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums & Read the Forum Rules
Moving to Q&A
lufc said:
Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums & Read the Forum Rules
Moving to Q&A
Click to expand...
Click to collapse
ops sorry about that, my bad
Hi Barry. Welcome to XDA. One quick suggestion: If you want to get help in an enthusiasts forum, don't call the object of everyone's affections a "pices [sic] of ****."
We all understand the stress of having non-responsive electronics; but you'll catch more flies with honey...
***edit. Wrote some stuff for you only to realize that you're on a 10.1v. Not sure how I missed that in your title (and thus, I suppose I can't comment on whether or not it really is a POS!). Until just now I never realized how different your tab is from the regular 10.1 (guides are much more difficult to follow!) Anyways, I found these threads that might be useful to you:
http://forum.xda-developers.com/showthread.php?t=1083517
and
http://forum.xda-developers.com/showthread.php?t=1232664
Good luck!
slack04 said:
Hi Barry. Welcome to XDA. One quick suggestion: If you want to get help in an enthusiasts forum, don't call the object of everyone's affections a "pices [sic] of ****."
We all understand the stress of having non-responsive electronics; but you'll catch more flies with honey...
***edit. Wrote some stuff for you only to realize that you're on a 10.1v. Not sure how I missed that in your title (and thus, I suppose I can't comment on whether or not it really is a POS!). Until just now I never realized how different your tab is from the regular 10.1 (guides are much more difficult to follow!) Anyways, I found these threads that might be useful to you:
http://forum.xda-developers.com/showthread.php?t=1083517
and
http://forum.xda-developers.com/showthread.php?t=1232664
Good luck!
Click to expand...
Click to collapse
i apologize for that, but i was referring to my tab only ... anyways
thanks for your reply and for the links you gave me .. but still the biggest problem is i'm unable to connect my tab to odin, and downloading mode and recovery mode are not even there .. theyre all gone, only APX mode is working and even with that, NVflash won't work and i would give me this error
"Nvflash started
rcm version 0X4
Command send failed (usb write failed)"
if i could connect to odin i could actually do something, or even NVflash i could run bootloader and it would install image files and all.
i'm not sure if i can do anything with APX other than NVflash .. or if i could somehow bypass Nvflash error ..
i just have a feeling that my tab won't make it
Just an idea... did you try to do the work with another pc?
For example a fresh XP 32bit install on another pc.
This "usb write error" seems strange.
Max
gfreeman86 said:
Just an idea... did you try to do the work with another pc?
For example a fresh XP 32bit install on another pc.
This "usb write error" seems strange.
Max
Click to expand...
Click to collapse
Thanks for replying. .. Yes i tried with anither pc. . I have read in this forum and others that this error means that the tablet is somehow locked even tho it wasnt before i root/rom it
Its like not writable, ill install a freah xp pro and givr it another try since i tried only win win 7
Did you try to drain completely the battery and then charge?
http://forum.xda-developers.com/showpost.php?p=19519586&postcount=15
seems it worked for someone
gfreeman86 said:
Did you try to drain completely the battery and then charge?
http://forum.xda-developers.com/showpost.php?p=19519586&postcount=15
seems it worked for someone
Click to expand...
Click to collapse
Yes i did as i metioned in my post, didnt help
When i charged it after i drained the battery, the screen light will turn on but no battery logo or anything.. The only thing that would show up on the screen is when i try to enter downloading mod/recovery mod by pressing power+volume is a little line on the top right corner which says : " booting recovery image# "
thank you for your reply, what do you guys recommend since i can access APX mod, will i be able to do anthing other than nvflash in APX mod?
Since you are getting a usb write error as well as no charge indicator, is it possible that your USB cable is bad?
sgip2000 said:
Since you are getting a usb write error as well as no charge indicator, is it possible that your USB cable is bad?
Click to expand...
Click to collapse
thanks for your reply
when i charge, the tablet does charge but no Battery logo, i can tell its charging because the screen lights will go on.
what i have tried so far :
* installed APX but when i try to nvflash it says something like writing failed
* tried both windows XP and windows 7
* drained the battery twice for 2 days
* changed USB cable
* tried to connect it to different versions on odin but computer only recognise the device in APX mode
* device still showing ( booting recovery kernel image#) when a try to access DW mod.
it all started when i used a backup program after rooting it, i don't get .. is its a backup it shouldn't delete everything (the system) and brick the tablet...
whats Kernel ? << noob
any new ideas guys ? is there any other programs/methods out there ?
anyone have the same problem ?
thanks
-Bazza
When it says booting recovery kernel image, did you try to just wait for about 15 to 20 minutes to find out if it boots again, or try logcat command?
djden said:
When it says booting recovery kernel image, did you try to just wait for about 15 to 20 minutes to find out if it boots again, or try logcat command?
Click to expand...
Click to collapse
yes, i left it like that till the next morning
** update **
Today i disassembled my tab after i read somewhere in this forum that i might get it back if i take the battery out or unplug the screen cables. Some claim that the touch screen could cause the tab to go into a boot loop; however that didn't work
i decided anyway to buy a new tab either Asus Transformer or Galaxy 8.9, even tho I'm kinda worried that this thing could happen to my new tab when i try to root it and install roms. I don't want to spend that much money until i figure out the problem, so i'm making this tablet "A testing Device" i'm gonna test every possible way to revive it for me and and others. I'll do my best with your help guys to solve this so we can provide help for others.
There was a Guide here in this forum about JTAGing that tablet along with a software that some company use to unbrick devices but i cold not find it, my cousin owns a hardware store and i could use everything i need .. i just need someone to guide me.
Thanks
Sounds like a cool project, sorry it cost so much.
zBarry, You should try this while you can, It sounds simple as it is but it worked for both my tablets that had the 0x4 aka locked bootloader. Sorry if you had already "Lego" lized your tablet into pieces but this may help. :]
http://forum.xda-developers.com/showthread.php?t=1478361
bumb!
im still looking with no luck ... please help ?
can i do anything with linux ?
zBarry said:
bumb!
im still looking with no luck ... please help ?
can i do anything with linux ?
Click to expand...
Click to collapse
As far as I know linux won't help, what % is your tablet charge at? Since you've opened it already why not just de-attach the battery and reattach it back and try to power it directly into fastboot. Normally draining is the same as stopping the flow of current into the tablet. Unlike phones where you can pop out the battery you can't do it to the tab unless you've opened it.
Can you please let me know what steps have you tried so far? Would be nice to know in detailed So I can help you out at best.
Misledz said:
As far as I know linux won't help, what % is your tablet charge at? Since you've opened it already why not just de-attach the battery and reattach it back and try to power it directly into fastboot. Normally draining is the same as stopping the flow of current into the tablet. Unlike phones where you can pop out the battery you can't do it to the tab unless you've opened it.
Can you please let me know what steps have you tried so far? Would be nice to know in detailed So I can help you out at best.
Click to expand...
Click to collapse
i think i have third every possible way out there... and the steps that i did to revive the device your way was :
i taped the power button and left it for like 2 days, then i plugged it to the computer in APX mode to check if its drained or not, but i think it was charging off the computer. So i repeated the first step and left it for 3 days, then plugged it into the socket. after couple of mins the screen turned on, but no logo or anything, just black screen (same issue). i decided to disassemble the device to take the battery out which i did and yet same result. i had hope so i re-did the battery drain thing and left it for a week and when i plugged it i pressed pwr+ vlo + and something.
my tab turns on, but just a black screen it won't that up, and power + volume up will show me a kernel message.
thanks so much, i aprreciate your trying to help any other way you think i should try ?
What sort of kernel message do you get? As far as I know maybe perhaps the contact's arent touching properly? Seems to me you did everything right but when it turns on you don't get the charging icon.
The good part is the display works and atleast you can boot up *Somehow* the bad part is you can't get it into Fastboot mode.
As far as I know the tablet is supposed to light up but have you checked if you get the offline charge icon (That green battery that sits in the middle of the screen and charges?) once you get it to drain/disconnect you should leave it to charge via wall socket for about 5-10secs for that icon to pop up. If you get that icon atleast then you know you are getting somewhere
I wish I had the tablet in hand so I could see what's going on. The whole oceans away solution makes it hard to guess what's happening
Hey guys,
I have a galaxy s3 (I9300) and I've had it rooted for some time now. I started using CyanogenMod 10.2 nightlies a few months ago and they've mostly been fine. The odd issue comes up but I've been able to work it out. So, a few hours ago my phone just turned off of its own accord and started to bootloop, but on the "Samsung Galaxy S3 GT-19300" screen, not the CyanogenMod screen (to clarify, this screen comes up first then the cyanogenmod one usually). I've tried booting into recovery (CWM 6) but it just shows the CWM boot logo thing (that cog with the hat) and then loops back to the galaxy s3 page. I've also tried putting it in download mode, and it seems to stay on the warning page longer than it does anywhere else, but it wont let me actually put in it download mode from there.
I had a look around google and saw people have had the same problem, but everything I could find was when people had flashed a new rom/kernel etc. and something had gone wrong in the process. The weird thing about mine is that I haven't changed anything, even downloaded any new apps, for maybe a week, so it's not like something suddenly changed. I also wasn't using it when it started, it was just sitting on the table next to me.
Usually I can work these things out, but I'm stumped here. Any help would be really appreciated.
Thanks in advance!
danielbollom said:
Hey guys,
I have a galaxy s3 (I9300) and I've had it rooted for some time now. I started using CyanogenMod 10.2 nightlies a few months ago and they've mostly been fine. The odd issue comes up but I've been able to work it out. So, a few hours ago my phone just turned off of its own accord and started to bootloop, but on the "Samsung Galaxy S3 GT-19300" screen, not the CyanogenMod screen (to clarify, this screen comes up first then the cyanogenmod one usually). I've tried booting into recovery (CWM 6) but it just shows the CWM boot logo thing (that cog with the hat) and then loops back to the galaxy s3 page. I've also tried putting it in download mode, and it seems to stay on the warning page longer than it does anywhere else, but it wont let me actually put in it download mode from there.
I had a look around google and saw people have had the same problem, but everything I could find was when people had flashed a new rom/kernel etc. and something had gone wrong in the process. The weird thing about mine is that I haven't changed anything, even downloaded any new apps, for maybe a week, so it's not like something suddenly changed. I also wasn't using it when it started, it was just sitting on the table next to me.
Usually I can work these things out, but I'm stumped here. Any help would be really appreciated.
Thanks in advance!
Click to expand...
Click to collapse
can you at least enter download mode after a long time you said? if not, try pulling out the battery for 5 minutes or more and re-insert and enter download mode. i hope it's not sds! good luck
sriram231092 said:
can you at least enter download mode after a long time you said? if not, try pulling out the battery for 5 minutes or more and re-insert and enter download mode. i hope it's not sds! good luck
Click to expand...
Click to collapse
Nope, if I press the volume up button to go into it, it just goes back to the bootloop. I'll try the battery thing though, thanks!
Nope, it didnt work, I left it out for maybe half an hour and nothings changed :/ anyone else got any ideas?
SDS thread and BootLoop identical questions posted .
What does Product Code say in download mode .
But if you cannot get to download mode then you need a service centre repair .
looks like u are facing SDA but a bit diffrend than a normal SDS.. mine still can go into download mode with blank product name..
If product name is blank in download mode then you got sudden death, consider a phone as a brick. Nothing will help, including repartitioning.
You need to contact service centre.
I'll check it in a minute, but if it is bricked, will any service center actually help me seeing as it's rooted and all?
danielbollom said:
I'll check it in a minute, but if it is bricked, will any service center actually help me seeing as it's rooted and all?
Click to expand...
Click to collapse
AFAIK if it's sudden death then it's not possible to detect root and other modified things, or in other words - nobody has money to prove that you have been using unofficial firmware .
JustArchi said:
AFAIK if it's sudden death then it's not possible to detect root and other modified things, or in other words - nobody has money to prove that you have been using unofficial firmware .
Click to expand...
Click to collapse
Ahhhh, well that is handy then
In terms of a service centre, will samsung have a list of them somewhere so I can find one near me?
So I contacted samsung and they gave me the link to book into a service centre etc, but I just realised that when I try to go into recovery mode, the CWM recovery logo comes up before going back to bootloop. Is there any way to get rid of that so that my root is completely untraceable?
danielbollom said:
So I contacted samsung and they gave me the link to book into a service centre etc, but I just realised that when I try to go into recovery mode, the CWM recovery logo comes up before going back to bootloop. Is there any way to get rid of that so that my root is completely untraceable?
Click to expand...
Click to collapse
If you can't flash anything with Odin (stock software) then you're screwed. Eventually you can try to enter recovery and flash "eraser" of recovery, but this requires working recovery... So if you actually can enter recovery then you can also flash anything, which will literally delete everything.
In other case, no, no way. But if you're lucky enough you may break it just by leaving your phone on for some hours in bootloop, haha.
JustArchi said:
If you can't flash anything with Odin (stock software) then you're screwed. Eventually you can try to enter recovery and flash "eraser" of recovery, but this requires working recovery... So if you actually can enter recovery then you can also flash anything, which will literally delete everything.
In other case, no, no way. But if you're lucky enough you may break it just by leaving your phone on for some hours in bootloop, haha.
Click to expand...
Click to collapse
Is there any way to wipe it with magnets or anything? hahah I'm clutching at straws now, but otherwise I'm just left with an expensive paperweight so I'm trying to find anything I can
danielbollom said:
Is there any way to wipe it with magnets or anything? hahah I'm clutching at straws now, but otherwise I'm just left with an expensive paperweight so I'm trying to find anything I can
Click to expand...
Click to collapse
To be honest think twice before physically crashing your internal memory, as it may void your warranty at all.
I'd try flashing stock firmware through odin, if it doesn't work I'd try flashing anything through recovery. If both of these methods fail just leave your phone in bootloop and hope that it'll automatically destroy everything... :laugh:
Seriously though, you can either physically destroy internal memory or leave it in bootloop and hope for the best, eventually send them device in current status. Up to you, because you won't have a possibility to do anything else.
JustArchi said:
To be honest think twice before physically crashing your internal memory, as it may void your warranty at all.
I'd try flashing stock firmware through odin, if it doesn't work I'd try flashing anything through recovery. If both of these methods fail just leave your phone in bootloop and hope that it'll automatically destroy everything... :laugh:
Seriously though, you can either physically destroy internal memory or leave it in bootloop and hope for the best, eventually send them device in current status. Up to you, because you won't have a possibility to do anything else.
Click to expand...
Click to collapse
If I send it back to them as it is now it'll take them about 20 seconds I reckon before they see the CWM logo, realise its rooted and send it straight back, so I dont know what I'm gonna do hahah
Hi internet users,
I would like to solicit your help regarding a quite strange problem with my phone.
As indicated in the title, It is a Samsung GT-S5839I.
In order to create coherent whole i will sum this up with questions and answer.
What is it that, for me, is very likely to be the origin of the problem ?
I think i can say that the origin of the problem might be caused by an installation of a wrong ROM.
In other words, immediately after the installation of this one, the problem appeared.
What happens when i turn on the phone?
If i try to turn it on normally using the power button ; the phone turns on correctly but the screen turns out to be black and backlighted.
I mean by this that i can't see anything, the buttons are enlightened, there is light on the screen (maybe caused by the backlighting), but there is no way to know what is going on.
The only clue i have is the noise that the animation done at boot up.
When the phone ends his booting task, it is likely that it reached the unlocking screen.
If i try to turn it on normally using the volume up, down and the power button ; It happens the exact same thing that when i try to turn it on normally.
If i try to turn it on using the volume up, down, home and the power one ; It happens the exact same thing that when i try to turn it on normally.
In other words, the recovery mode doesn't work.
What can i do ?
I can access to the files on my SD CARD using the Samsung Kies 2.6 software.
I can access to the unlocking screen without visual returns.
What i can't do ?
Use the phone's touch keys .
Access to the ADB module.
Access to the download mode.
Access to the recovery mode
Thanks in advance for the attention you will bring me.
@chikamtsu, You do officially hard bricked your device ( both modes are not accessible ) .
There is so little remained to do mate, you can get a little device called "USB jig" as a last resort to force your phone into Download mode ( may or may not work,even if i provide instructions). As for your LCD blackness/dimness it goes, your symptoms might be caused by water/dust/corrosion damages more likely rather than flashing a wrong firmware ! in s5830i which is very similar to your device, replacing IC light u 503 part will solve problems in most cases ( I am not so sure of IC part of your device). Be cautioned though disassembling your device is not for fainthearted, you need expertise to open such a delicate case; hence I can't ask for critical information such as measuring voltage IC . One more thing mate, for the future record could you kindly provide a link to firmware you did flash from sammobile.com database preferably. Your original CSC/MODEM/PDA , Android version/ Kernel is also needed .
Raakib zargar said:
the symptoms you have told state that you have hard bricked your device
Click to expand...
Click to collapse
Sure, but, what are my options ?
@chikamtsu, Just looking to the pattern he has been posting in this section mate >> indeed typical spammer without proper knowledge/insight of what is really happening under the hood of our Android device
As for your problem, I have already explained all of the possible solutions in details ! ( you may check my comment here too )
P.s: Report his ass for disturbing peace ( Report button ),, Really this dude make assistance impossible by reviving old topics; and such an odd way to increase post count ,, he even quoted my comment ,, pretty Hilarious
chikamtsu said:
Sure, but what are my possibilities ?
Click to expand...
Click to collapse
Well if you can tell me that which rom you had flashed because some roms for Galaxe Ace after flashing need to press the Home button to avoid blacksceen.
Well your possibilities are to give your phone a usb jugg service/Heimdall and after that take it to download mode and flash back using odin.
Hai guyz i bricked my phone.I need help i could have resolved it easily and i have done it earlier too.
but the problem is broken home button(home button does not work) and i am unable to get in recovery.
I have a copy of the rom in my phones internal memory(custom rom) which i can flash if gets in recovery mode.
ADB doesnot work as usb debugging is not activated.
So help any other way to get in recovery mode
Install any terminal emulator and type reboot recovery
rp158 said:
Install any terminal emulator and type reboot recovery
Click to expand...
Click to collapse
Bro thanks for the reply I said my phone is bricked doesnot start( struck in boot loop)
Kumarm93 said:
Bro thanks for the reply I said my phone is bricked doesnot start( struck in boot loop)
Click to expand...
Click to collapse
If adb isn't working to reboot recovery and your home button is not working then about the only way I see you recovering is to connect to kies or Smart Switch and see if the recovery options there help.
If you can get retired to stock you can flash a recovery again via Odin then restore your backups or flash a ROM.
Sent from my SCH-I535 using Tapatalk
There is an easier way, if your home button has a malfunction and not the main board itself.
If this is the case, then open your s3 remove all the screws and cables from the main board and flip it to the other site. You will see nearly to the bottom 2 little golden squares which are the contact for the home button.
Get yourself two copper wires and tape them to each of them. Put the s3 together, turn it on, press power+volume up and let the ends of the two wires have contact with each other.
You should be able to enter recovery. I had the same problem once. I let the two wires permanently stick out of the s3 in case I will have to manually enter recovery again. Have fun
Sounds like will work thanks a lot +1
And one more question I wish to change the full housing panel of my s3 what would be the price
Will try both the ways thanks guys+1 to both
Kumarm93 said:
Sounds like will work thanks a lot +1
And one more question I wish to change the full housing panel of my s3 what would be the price
Click to expand...
Click to collapse
Depends on how much work you will put in this "color change". The front-color depends on the glass.
You could buy only the glass for about 10$ which is a little of work cuz you could probably break your
display while removing the old glass and you'll need UV Glue to put the new glass on. You see a bit
annoying. Or you could buy a whole LCD+glass in your desired color which will cost about 60$.
The backcover is 2-3$ and the innerpart is not necessary to change cuz it's not visible