Related
Hello all,
I have recently upgraded from my g1 to an HD2. HD2 is a great phone but still miss android . Anyways, today I wanted to get my g1 to work without a sim or data plan and was about to start working on it when my g1 screen dimmed to just the blacklight with a black screen. I turned it off and tried turning it back on but it just comes up with the backlight on a black screen. It does not even get to the G1 screen. I cannot get to recovery mode or any other mode for that matter. I have searched around but not found any real solution to this problem (if there is one). I am thinking my phone is bricked but have heard possibilities using ADB. I have never used ADB before and if anyone knows if this is a possible fix to my problem that would be great. It would be nice to know if it actually could fix my problem before looking into it and learning it all while finding out it has no chance of fixing my problem. I have tried using my sim card and a different sd card so those are not causing the problems.
So the background of what I am running on my g1. Right before I got my HD2 I was using Cyanogen version 4.2.14.1 with and ext 3. I had no problems with it until now. I got my HD2 a week ago and my g1 has been on about twice in that time without a sim card just for comparing purposes to the HD2. Then just today (about 2-3 days since I last turned it on) the screen just went black and I had my problems. I cannot return my phone because it has been over a year and I dont have insurance on the phone so these are not possibilities for me unfortunately. I also don't really want to get parts from other g1's and take apart and put my g1 back together. I am just looking for something with ADB or any other possible solution to the problem (if one exists).
Any help would be greatly appreciated!
I had this happen to me before. Apparently, it was a hardware GPU problem that would cause a boot loop because it couldn't draw anything on the screen. This happened on SuperD, AOSP, Cyanogen, and stock Donut.
If your problem is the same, you should be able to get into recovery, regardless of your ability to see what you're doing. Easy way of telling is to hit Camera+End on boot. If it doesn't vibrate, you're able to flash still. You may be able to get the screen back temporarily by either pulling the battery or letting the battery die and recharging.
Anyways, I ended up flashing the DREAIMG.nbh, and trying to upgrade back to 1.6 to remove traces of hacking. (Be careful if you have DangerSPL, you want to restore the default before flashing DREAIMG.nbh) I eventually got the screen working on 1.6, but it died again, so I sent it in to T-Mobile and got a replacement. I'm now using AOSP with no problems.
One small note, however, I did start having my problems using Cyanogen's mod. May want to bring it up with him?
Sorry if this sounds scatterbrained, it's a bit late and I should be asleep right now.
e:Just realized you said the warranty was void. You may be able to get something out of what I did, though? Good luck, in any case.
Thanks very much for the help even though it was really late. I did understand pretty much everything you said and I tried the camera plus power button and it didn't vibrate so it should mean I probably can flash things still. I have drained the battery and am charging it back up to see if that helped.
I have a friend who knows ADB so I am going to have him look at it to see if we can't get it working through there. Also the G1 screen has been popping up but then fading right when its about to change to the boot animation. So we will see how things go and I'll try a couple different things and report back if anything seems to work or open up more possibilities.
Thanks again for your information.
Ok, so my friend and I were going to flash a rom through fastboot. It was responding and such so we knew we were able to get it in there.
Anyone know what the command to flash a rom in fastboot is and if there are specific instructions to follow?
Any help would be greatly appreciated!
coolookoo said:
Ok, so my friend and I were going to flash a rom through fastboot. It was responding and such so we knew we were able to get it in there.
Anyone know what the command to flash a rom in fastboot is and if there are specific instructions to follow?
Any help would be greatly appreciated!
Click to expand...
Click to collapse
google it. i did and got about 100 links telling me how to do it. "unroot g1 with fastboot."
sorry i have the same problem, but my g1 is not rooted nor has it been flashed before, my friend messed it up somehow? wen i turn it on all there is is a blank highlighted black screen. What do yall suggest i should do
r3s-rt said:
google it. i did and got about 100 links telling me how to do it. "unroot g1 with fastboot."
Click to expand...
Click to collapse
First of all we are not trying to unroot the phone just flash another rom
Secondly we already tried your "fantastic" method of using google before coming to the forums
Ok I think I just bricked my G1
I was following the steps on theunlockr.com and was following the steps to the T like I always do.
The problem incurred after flashing the spl. I flashed the correct radio then ir rebooted and went back into recovery mode. Then I flashed the spl all seemed well home+back and never rebooted. It stayed on a black screen for over 30 mins. So I took out the battery and waited a few mins and put battery back in and same thing. Just a black screen nothing I can do. I have tried holding home+power and camera+power and back+power nothing. I am stuck have looked it up and this is the best forum I have found to post in.
Any input would be great.
thanks
nate
I for the life of me cant figure out why my camera is completely dead! I have FULLY wiped all caches,everything under 'WIPE' via AMONS and even formatted my SD card as well as trying an alternate SD card(both 8GB--C6speed)--never had a problem w either card on ANY ROM...ALL OF A SUDDEN the past 2days my camera goes to a FULL BLACK SCREEN,when pressing the CAMERA icon. Occasionally the taskbar will remain uptop but will timeout when screen display shutsoff. Now if i launch CAMERA via DESIRE ROM(KING),ill get the notice about clicking trackball to resume camera but as soon as i click it,the message dissapears and the screen will go back to black screen again...and repeat. I SWEAR i have DONE MULTIPLE COMPLETE WIPES AND REFORMATS so im left to believe its THE HARDWARE itself! CAN ANYBODY PLEASE LEND ME A HAND IF the similar problemhas occured...On the Nandroid backups that ive restored from FULLY FUNCTIONING bkups,if i launch NEXUS TORCH it will say CANNOT ACCESS LED---this is THE ONLY info besides the "camera wake message"mentioned earlier that i can provide. Thanks in advance and pleas edont flame for NOT being in Q&A bc this is more of a DEV related restore question.
**oh and BTW--I DID TRY TO INSTALL the DESIRE R2 cam fix and does nothing. I tried it when all was working fine early in the week and it did nothing to help FLASH timing for me,so i NAN restored back to prior state and CAMERA continued working until about THURSDAY night--regardless--PHONE is in OUT OF BOX STATE--MINUS UNLOCKED and it STILL doesnt work!---PEACE and Happy Mothers Day to any Mothers out there in XDA world!
***Captain Obvious to the Rescue!!***
Your hardware has malfunctioned. Contact HTC for a repair.
1. you may have a broken camera, try a stock rom
2. your caps lock button is definitely broken
3. you posted in the wrong section
ghostrida said:
1. you may have a broken camera, try a stock rom
2. your caps lock button is definitely broken
3. you posted in the wrong section
Click to expand...
Click to collapse
1. i should have known you were from Philly and cant read--I TRIED STOCK ROM
2. CAPS is to put highlights on key terms so idiots dont read over the fact that I DID TRY STOCK ROM---see how that helps?
3. Thanks for your informative responses---any suggestions from CAPTAIN OBVIOUS how to get service on a ROOTED device without being charged full price on the phone?? Ahhh--thought not!--So i tried here to see if anyone else had similar situation. AGAIN-thanks for your help as well SERIAL TOON--geez
If it's a hardware failure they won't charge you.
I think it will help if you go through Google Cust service first...they will end up redirecting you to HTC repair. Provide all truthful information on your issue, proving that you have done some legitimate trouble shooting and they will realize that it is a hardware issue, not the ROM flashing or bootloader unlocking that caused the problem. Someone else on the xda forums had a rooted phone with bluetooth problem and was able to send to HTC for repair for free...with a 4 day turnaround!
Good luck!
What do you base this on...Heresay?
BlueScreenJunky said:
If it's a hardware failure they won't charge you.
Click to expand...
Click to collapse
I didnt intend to sound rude,im just a little pissed right now..I Only ask bc i already had an issue in January days after receipt of phone. Issue was solved by sending me a new battery bc other was causing random shutdowns (ive since forwarded this info to another XDAmember that had exact same issue and they give him replacement phone at 1st but issue continued to occur--i told him about my story after he posted his problem, he contacted them this weekend and confirmed with me today that a new battery was on the way..see my public IM's for info). Anyway,when i was dealing with the battery issue they said they would definately NOT be able to fix under warranty bc the phone is rooted and unlocked. I can attest to the few people on here that said theyve been successful in such cases,but either way,IVE ALREADY STATED that i tried the DESIRE R2 camera kernal to see if that helps,so im not going to be dishonest and tell them i havent tried anything other than custom roms. Again..positive suggestions or similar experiences with warranty info would be appreciated....trollers looking for a funny post or to degrade people can eat one!
joshlusignan said:
I think it will help if you go through Google Cust service first...they will end up redirecting you to HTC repair. Provide all truthful information on your issue, proving that you have done some legitimate trouble shooting and they will realize that it is a hardware issue, not the ROM flashing or bootloader unlocking that caused the problem. Someone else on the xda forums had a rooted phone with bluetooth problem and was able to send to HTC for repair for free...with a 4 day turnaround!
Good luck!
Click to expand...
Click to collapse
Thanks JOSH, ill look into it tommorrow--as i stated tho--i feel im being dishonest for trying the DESIRE R2 cam and saying that they should cover it---uninformed people will assume THAT couldve caused it,even though i used phone afterwards for a few days w no side effects
Hey Milton, like others have mentioned in here might want to try flash back to stock and seeing if the problem persists. If it does then your looking at a hardware problem and you should contact HTC/google for repair.
Yea...i was thinking that from get go--(hardware prob). Im on cheesy STOCK ROM right now and have been for cpl hrs...but its obvious its gotta be hardware...NOW comes the crappy part of trying to explain it to HTC when attempting to get an RMA!--Yee Haa!
MOD PLEASE CLOSE OR DELETE---THANKS!
Milton, among the items on the very small list of things folks around here want in return for helping you is that you lay off the caps. Doesn't highlight anything that you'd want to highlight.
Doug
Okay,,,this is weird!!..My TORCH hadnt been working at all either, the whole time ive had the camera problem. Now ,the torch will work for ONE TURN ON, then if i launch CAMERA, the cam still doesnt work. i have to HOME and HOME only to get back to home screen..BACK ARROW does nothing except vibrate,indicating touch response. If i then re-launch TORCH, it doesnt work....!??SOMETHING is ODD--and im split whether its hardware- or some sorta SYSTEM file that stays stuck even after all STOCK FLASHES and everything!--again,reminder..the LED TORCH hadnt worked up until this point--unit has NEVER been dropped,slid out of pocket from 1foot high onto superthick carpet,so i doubt its a loose internal cable...Hmmm...
milton007 said:
Okay,,,this is weird!!..My TORCH hadnt been working at all either, the whole time ive had the camera problem. Now ,the torch will work for ONE TURN ON, then if i launch CAMERA, the cam still doesnt work. i have to HOME and HOME only to get back to home screen..BACK ARROW does nothing except vibrate,indicating touch response. If i then re-launch TORCH, it doesnt work....!??SOMETHING is ODD--and im split whether its hardware- or some sorta SYSTEM file that stays stuck even after all STOCK FLASHES and everything!--again,reminder..the LED TORCH hadnt worked up until this point--unit has NEVER been dropped,slid out of pocket from 1foot high onto superthick carpet,so i doubt its a loose internal cable...Hmmm...
Click to expand...
Click to collapse
That seriously hurts my eyes to look at. Try using proper punctuation and grammar. It's very simple and still gets your point across.
As for your phone. Call Google which will probably have you call HTC. People have gotten their rooted devices fixed for free if it's a genuine hardware problem and nothing caused from the rooting process.
milton007 said:
Okay,,,this is weird!!..My TORCH hadnt been working at all either, the whole time ive had the camera problem. Now ,the torch will work for ONE TURN ON, then if i launch CAMERA, the cam still doesnt work. i have to HOME and HOME only to get back to home screen..BACK ARROW does nothing except vibrate,indicating touch response. If i then re-launch TORCH, it doesnt work....!??SOMETHING is ODD--and im split whether its hardware- or some sorta SYSTEM file that stays stuck even after all STOCK FLASHES and everything!--again,reminder..the LED TORCH hadnt worked up until this point--unit has NEVER been dropped,slid out of pocket from 1foot high onto superthick carpet,so i doubt its a loose internal cable...Hmmm...
Click to expand...
Click to collapse
You should send it to HTC for repair. Charging fee or not, but thats the only option to you right now because its a hardware failure.
mikroN1 said:
That seriously hurts my eyes to look at. Try using proper punctuation and grammar. It's very simple and still gets your point across.
Click to expand...
Click to collapse
I was thinking the exact same thing, don't know where he must have learned how to type. Then you criticize people from Philly, or whatever its called somewhere, for not knowing how to read. I would say mirror that advice and learn how to type.. type properly.
Torch will work until camera app is used then it wont work again until i reboot. After reboot, torch will work ONLY on regular/lower setting. MAX brightness will not work. Toggle back to LOW setting and torch will work again. Im going to try what DOUG suggested bc that is the only thing i havent tried yet...but the way torch and camera are acting up and requiring reboots keeps me willing to try software tricks first...WHAT ties the TORCH's HI setting to the camera app adn yet keeps the LOW setting seperate!??..ill try the TORCH dev real quick for some insight on how the two work hand in hand.Thanks for anyone using their time to help instead of criticize. Sorry for mocking ones ability to read but i was quite [email protected] time bc i lost a major function on my phone.My apologies to all
Seriously Milton? More?
milton007 said:
Please DONT lend assistance to someone like this. IF they cant bither to read THE MOST SIMPLEST instructions, they should NOT be attempting this in the first place...thats just sheer ignorance...
Click to expand...
Click to collapse
The attitude, hostility and the caps are not welcome here.
Along with the others I have no sympathy for you. Learn proper grammar and get a better attitude.
Troll much? Go tell your mother happy mothers day if you have that much time to pull up old posts from people asking questions in a 'kernal forum' about basics. Basics that anyone should know, if not they stand a much better chance on damging their phone. It wasnt being ignorant. Since you know everything there is to know about everyones posts, tell me where the topic dealing with my specific camera issue has been previously posted and ill be glad to read and search thru that forum. I wasnt the one asking questions about something mentioned in the OP (uh oh i used caps--oh geesh-someones gonna be saaad now!)and numerous pages before. Im sorry i dont spend all my life on forums to know that only words approved for caps are indeed CAPITALIZED. Petty little boy-and by the way, i was trying to stress your good advice by typing your name in caps so people would credit you with the help-Sorry to have taken your precious time sir. Good day.
So I got some bad news
There is an area on my Nexus 4 that receives no touch input. Either that, or it is extremely inconsistent. This is the section right about where the bottom row of icons are located, directly above the on-screen navigation buttons.
I tried installing this "fix" for touch sensitivity, but it did not fix the specific problem I am having. And I noticed this problem before I tried that fix, so it was not a result of that.
I am about to try a full system reset to see if that helps. Hopefully it will. I will post back if it does.
If I have to send it back to Google, what process would I need to go through to make sure they don't know I rooted? Just unroot? Or would I also have to lock the bootloader as well? And would a full system reset do all of that? Or do I need to go back and use the toolkit?
Here is a video I just shot showing the problem:
EDIT: And unfortunately a full reset just made it worse
strausd said:
So I got some bad news
There is an area on my Nexus 4 that receives no touch input. Either that, or it is extremely inconsistent. This is the section right about where the bottom row of icons are located, directly above the on-screen navigation buttons.
I tried installing this "fix" for touch sensitivity, but it did not fix the specific problem I am having. And I noticed this problem before I tried that fix, so it was not a result of that.
I am about to try a full system reset to see if that helps. Hopefully it will. I will post back if it does.
If I have to send it back to Google, what process would I need to go through to make sure they don't know I rooted? Just unroot? Or would I also have to lock the bootloader as well? And would a full system reset do all of that? Or do I need to go back and use the toolkit?
Here is a video I just shot showing the problem:
Click to expand...
Click to collapse
very interesting......
I would definitely RMA that. It's clearly an issue. I just ran the same touch tests you did in the video and have none of those same problems. The screen recognizes my touch even at the very bottom of the screen where the nav bar starts.
As for unrooting/re-lockingt he bootloader, just use Wug's toolkit:
http://forum.xda-developers.com/showthread.php?t=2015469
This worked flawlessly for me to unroot and re-lock the bootloader of my first N4 before sending it back to them. The toolkit is very straight forward.
I tried using the Nexus 4 toolkit to restore to a factory image, but I am getting an error every time it tries to download it
EDIT: I am about to try that other toolkit posted above ^^^
i tested mine no problem at all..
kanariya said:
i tested mine no problem at all..
Click to expand...
Click to collapse
Dang, I guess its just me. I am about to restore to a factory image. I am hoping that fixes the problem. Otherwise I will have to send it back to Google.
strausd said:
Dang, I guess its just me. I am about to restore to a factory image. I am hoping that fixes the problem. Otherwise I will have to send it back to Google.
Click to expand...
Click to collapse
Hope it works out for you!
strausd said:
I tried using the Nexus 4 toolkit to restore to a factory image, but I am getting an error every time it tries to download it
EDIT: I am about to try that other toolkit posted above ^^^
Click to expand...
Click to collapse
Just make sure you follow the step by step guide for installing the proper drivers and uninstalling rogue ones before trying to unroot/lock the bootloader. It is super easy just make sure you read all the instructions and follow them to a T. After doing that the toolkit will work perfectly for you moving forward. Even with your next N4. I used it again today to root my replacement N4.
I encountered a MAJOR problem!
I did the flash stock + unroot part and that worked fine. But I am completely stuck on the last part.
Now I need to lock the bootloader again. In order to do that, I have to have USB debugging turn on. The problem is that in order to turn it on, I have to get into the phone. But I am stuck on the initial phone setup! The only way to move past the stage I am stuck on is to click an arrow, but the arrow is in the dead zone and the dead zone just got worse! I can't move on!
Anybody have any advice? I am totally stuck.
EDIT: Got it! At that stage I put the phone in landscape to avoid the dead area. Then the Android tutorial came out and I couldn't get out of it to go to settings and enable USB debugging mode. So I went to the lockscreen, after 20 tries got Google now pulled up, and was able to type in settings to open it up and enable USB debugging mode. Finally got the bootloader locked. Should I be good to send it back to Google now?
Please repeat this bug while holding the phone in your hand, a video would be nice.
wideasleep1 said:
Please repeat this bug while holding the phone in your hand, a video would be nice.
Click to expand...
Click to collapse
Haha you want a third video?
strausd said:
Haha you want a third video?
Click to expand...
Click to collapse
Sure! This is a well-known issue across a LOT of Android phones, YT is awash of vids like yours, all sitting flat on a surface.
wideasleep1 said:
Sure! This is a well-known issue across a LOT of Android phones, YT is awash of vids like yours, all sitting flat on a surface.
Click to expand...
Click to collapse
Already got an RMA on it and another one should be here in less than a week.
strausd said:
Already got an RMA on it and another one should be here in less than a week.
Click to expand...
Click to collapse
Odd it's so zone-specific... I'd suspect the grounding short is right near that lower micro-USB area. Thank Gawgle for quick RMA supply!
wideasleep1 said:
Odd it's so zone-specific... I'd suspect the grounding short is right near that lower micro-USB area. Thank Gawgle for quick RMA supply!
Click to expand...
Click to collapse
I hava the same issue
I have same issue in the same area of display, but my is sporadic, it's not present all the time. It comes and goes. I removed front protector, issue was still present. Then I removed back protector and did a factory reset, and now it's gone for 5 days. It's bought in Canada, and I'm from Serbia so it's a little tricky for me to send it for RMA because now I am not sure if the issue is realy hardware type. I run it in safe mode and it behave same.
Sometimes if goes totaly crazy with tens of simoultanous touches around non working stripe. Lock unlock and it's gone.
Tafak?!?? Don't know what to do...
I already trouble shot it with Google but I figured I would ask here as most of you know more than they.
I already did a factory reset 3 days ago because I deleted a file I shouldn't have. But now it has come down to them recommending me do another and then getting back if it still persists.
The problem is when I turn my screen back on I see white spots all over the screen for 2-3 seconds. I can't imagine why, or even why a factory reset is going to fix.
I have NEVER dropped (cross fingers) or got it wet, and truthfully have no idea how to tell and wouldnt want to begin taking the back off.
I am most certain there is no water damage
So I have tried:
Switched Wallpapers
Turned phone off then on
Switched from Apex to Launcher
Still there. I am posting a pic below. If anyone could help I would be most grateful.
Again you prolly know more than most of their employees
One time when I had a problem, but eventually got fixed, this is what I was told, they will do an advanced replacement, BUT I have to pay $350, then get it back when they get and verify the phone I send
I am not working so would not be able to do that. I suppose I could switch to my phone of choice I have here and just send it in?
Or I was told contact LG where there is no downpayment needed.
In either case, back then I was told there was stock for this type of situation, now I am told they no longer have any? You have any idea when they will catch up
THANKS for even taking time to read this, and even more if you can help
Eric
Hi
eric0668 said:
I already trouble shot it with Google but I figured I would ask here as most of you know more than they.
I already did a factory reset 3 days ago because I deleted a file I shouldn't have. But now it has come down to them recommending me do another and then getting back if it still persists.
The problem is when I turn my screen back on I see white spots all over the screen for 2-3 seconds. I can't imagine why, or even why a factory reset is going to fix.
I have NEVER dropped (cross fingers) or got it wet, and truthfully have no idea how to tell and wouldnt want to begin taking the back off.
I am most certain there is no water damage
So I have tried:
Switched Wallpapers
Turned phone off then on
Switched from Apex to Launcher
Still there. I am posting a pic below. If anyone could help I would be most grateful.
Again you prolly know more than most of their employees
One time when I had a problem, but eventually got fixed, this is what I was told, they will do an advanced replacement, BUT I have to pay $350, then get it back when they get and verify the phone I send
I am not working so would not be able to do that. I suppose I could switch to my phone of choice I have here and just send it in?
Or I was told contact LG where there is no downpayment needed.
In either case, back then I was told there was stock for this type of situation, now I am told they no longer have any? You have any idea when they will catch up
THANKS for even taking time to read this, and even more if you can help
Eric
Click to expand...
Click to collapse
Can't imagine what sort of hardware issue or fault would cause that, it looks like some sort of effect done by software.
You need to reset your phone and go back to the stock ROM (if not already using that) and then see if it still does it, I suspect it will not.
Regards
Phil
So this was present before the factory reset 3 days ago? If not then do it again
Sent from my Nexus 4 using Tapatalk 2
PhilipL said:
Hi
Can't imagine what sort of hardware issue or fault would cause that, it looks like some sort of effect done by software.
You need to reset your phone and go back to the stock ROM (if not already using that) and then see if it still does it, I suspect it will not.
Regards
Phil
Click to expand...
Click to collapse
Thanks to everyone, as you were responding, my friend Macky (maybe you know him LOL) suspected it had to be software/app because it showed up on the screen shot. So he said it wasnt hardware
I reset again and no problem
Thanks
lets say it wasn't the app, what could have caused it. (btw I dont root so dont know all the basics you prolly do) Just simple things like the computer that get messed up??
Hey XDA, Really need some help here, i'll bullet point my problem for ease of reading:
- 1st Nexus 4 bought from google had wi-fi issues so got replacement
- 2nd replacement nexus 4 was good for about 2 weeks
- randomly screen touches weren't recognized by phone so reboot fixed that
- got worse and more frequent
- now my phone does not recognize screen touches at all
- phone is completely unusable, power volume buttons work though.
- need to ask XDA before another replacement ///
WHAT I'VE TRIED:
- i was on stock, so i tried to reflash stock to get rid of gravity stock and stock kernel
- rebooting phone 3950280359283 times.
- cleared caches.
- asked google play support, they're clueless.
- problem was here before i was unrooted, on complete stock 4.4.2
- also wondering whether its a software or hardware problem. i assume hardware however.
- i still have warranty
ANY IDEAS?!? thanks.
Does a touch recovery recognize touches? If so, it could be a problem of your rom/kernel. Otherwise I think it's a hardware problem.
Creepyficate said:
Does a touch recovery recognize touches? If so, it could be a problem of your rom/kernel. Otherwise I think it's a hardware problem.
Click to expand...
Click to collapse
My screen works now. However it will still come back every now and then and is fixed by a reboot. When i made this thread it did not work for a whole day, so my device will probably breakdown again. When I use TWRP it does not recognize touches. A good decider. So i guess it is hardware?
I think so, but wait for another reply confirming that.
I'd say it's a hardware issue. Definitely get it replaced again.
Kaleptik said:
I'd say it's a hardware issue. Definitely get it replaced again.
Click to expand...
Click to collapse
Lmao. You're definitely right. It's really annoying they sent me another device with a WORSE problem. Gonna ask google for some sort of compensation. I don't really have time to fiddle with devices re-rooting them transferring all my data again and so on. Too much work.