So basically i Started Installing roms for like 4 months now, i started the rooting process using this guy's "Mackster248" method, witch was the gfree shown here: youtube.com/watch?v=c4B4y0CQUDo[/url]. I never tried anything more complicated than this aside from installing the genius button with required the need to use button shortcut app.
I've tried a few roms like VU 1.29. and a Vdoubleshoot one witch i hated. I loved vu 1.29.0 but i felt something was missing, so i tried the DARKSIDE Runny v2.1.0 first but found out that the voice recognition in the genius did not work, so i updated to 2.2.0. witch did work with the easy genius fix....Sooo I Loved it & decided to stay with it for good regardless of the ffc issue. So after reinstalling all my apps again i noticed that my power button would not lock and turn off the screen, I thought it was the button cause i had a problem with it being hard and sticking, so on the lock screen i "pulled the battery" yes after now reading in some forums I'm seeing that's a Big NO NO!
After trying to power on i get a Black screen of death where the black light turns on when pressing on the home screen only when the charger is plugged in so yes i am aware that I'm bricked but my question is why? This also happened to my friends "UNROOTED" mytouch 4g, when he was downloading something from the market the froze on him so i pulled the battery out and upon rebooting it was stuck on a line of androids. When sent to HTC they said it was the emmc chip.
So a some questions i have are, 1: Do these phone brick regardless of rooted or not? 2nd: Is pulling the battery out really so dangerous? if so what to do in my 2 scenarios? After i realized my phone was bricked i was thinking i should of used clockward mod before turning it off, but would that had made a difference? Ohh well i already know that HTC repairs rooted phones based on whats been posted in these forums so I'm not worried and i have already my shipped my phone...hopefully it wont take too long to replace that eMMc. Thanks for reading me out!
Maybe change the title of your thread... Your phone was bricked because you installed the Rom...
How r people getting the FFC to work with stock camera
wanabdev said:
So basically i Started Installing roms for like 4 months now, i started the rooting process using this guy's "Mackster248" method, witch was the gfree shown here: youtube.com/watch?v=c4B4y0CQUDo[/url]. I never tried anything more complicated than this aside from installing the genius button with required the need to use button shortcut app.
I've tried a few roms like VU 1.29. and a Vdoubleshoot one witch i hated. I loved vu 1.29.0 but i felt something was missing, so i tried the DARKSIDE Runny v2.1.0 first but found out that the voice recognition in the genius did not work, so i updated to 2.2.0. witch did work with the easy genius fix....Sooo I Loved it & decided to stay with it for good regardless of the ffc issue. So after reinstalling all my apps again i noticed that my power button would not lock and turn off the screen, I thought it was the button cause i had a problem with it being hard and sticking, so on the lock screen i "pulled the battery" yes after now reading in some forums I'm seeing that's a Big NO NO!
After trying to power on i get a Black screen of death where the black light turns on when pressing on the home screen only when the charger is plugged in so yes i am aware that I'm bricked but my question is why? This also happened to my friends "UNROOTED" mytouch 4g, when he was downloading something from the market the froze on him so i pulled the battery out and upon rebooting it was stuck on a line of androids. When sent to HTC they said it was the emmc chip.
So a some questions i have are, 1: Do these phone brick regardless of rooted or not? 2nd: Is pulling the battery out really so dangerous? if so what to do in my 2 scenarios? After i realized my phone was bricked i was thinking i should of used clockward mod before turning it off, but would that had made a difference? Ohh well i already know that HTC repairs rooted phones based on whats been posted in these forums so I'm not worried and i have already my shipped my phone...hopefully it wont take too long to replace that eMMc. Thanks for reading me out!
Click to expand...
Click to collapse
1. I have yet to hear of a non-rooted phone bricking because of the bad eMMc chip, only after you root it does the chip start acting funny. could have been a possibility that you had the bad eMMc, did you check to see before taking the plunge and rooting your phone?(guessing not lol )
2. pulling the battery isnt as dangerous as everyone says it is. its only dangerous if you pull it while trying to flash the stock PD15IMG to return to stock, or during the phones booting process where its loading everything up. Ive pulled my battery plenty of times, but never in those situations.
Maybe hope
Out of curiosity are you able to get into the bootloader to run fastboot at all by holding down the power and the down volume on your phone? If so you could probably flash clockworkmod onto your phone again through fastboot and reflash a new rom.
If you're able to do this you could save your phone
macblaxter said:
Out of curiosity are you able to get into the bootloader to run fastboot at all by holding down the power and the down volume on your phone? If so you could probably flash clockworkmod onto your phone again through fastboot and reflash a new rom.
If you're able to do this you could save your phone
Click to expand...
Click to collapse
DING DING DING we have ourselves a winner.
[OP] are you able to get into the bootloader or recovery?
I remember when I first started rooting my phone it would be titles like this that would scare me away form certain roms. Which is a good and bad thing. Although I would generalize the title a little. Like " dam i messed up installing a sense rom" this way it's a little more inviting to open minded people that want to help and less offending to people that put in time for tutorials and development
Sent using XDA App
aznprodgy said:
1. I have yet to hear of a non-rooted phone bricking because of the bad eMMc chip, only after you root it does the chip start acting funny. could have been a possibility that you had the bad eMMc, did you check to see before taking the plunge and rooting your phone?(guessing not lol )
Click to expand...
Click to collapse
Wrong. To hear this (or actually, to see this), you only need to go to the eMMC thread in General section, and look at the poll. You'll see enough failed non-rooted "bad" eMMCs, and you'll also see some "good" eMMC chips fail, even non-rooted. If you were reading the forum for the last 1/2 year, you'd hear more than enough of stock phones dying with failed eMMC. You can just try searching and reading the threads.
Moreover, you're wrong about the dangers of battery pull too. The danger isn't only when you're writing to sensitive partitions. It's a bit complicated, but I'll try to explain:
When the power is turned off, it doesn't go out at once - it takes a bit of time, several microseconds, maybe less, maybe more, depends on the capacitance of the supply path. During that time the electronic circuits still act, but with gradually diminishing voltage.
Circuits are built to function reliably in certain voltage range. The thing is that under that range, they don't stop functioning immediately - there is a range where they still function, but unreliably. Signals can receive erroneous values that aren't determined by the logic.
During that unreliable functionality period, a sequence of signals might happen that will cause overwriting one of the system partitions in the eMMC - since the logic doesn't function reliably, it can happen. If the phone is currently writing to eMMC (which might easily happen - programs read and write data when they run), you only need a couple of bits to fail in the bus address and write protection mechanism. The probability is very low and there are protections against that, but still, they aren't 100%.
If it happens, the phone is dead.
To add to that, there could be physical effects on eMMC chip from uncontrolled voltage drop.
So, this is why there's a recommendation to avoid pulling the battery, and using it only when really necessary.
Jack_R1 said:
Wrong. To hear this (or actually, to see this), you only need to go to the eMMC thread in General section, and look at the poll. You'll see enough failed non-rooted "bad" eMMCs, and you'll also see some "good" eMMC chips fail, even non-rooted. If you were reading the forum for the last 1/2 year, you'd hear more than enough of stock phones dying with failed eMMC. You can just try searching and reading the threads.
Moreover, you're wrong about the dangers of battery pull too. The danger isn't only when you're writing to sensitive partitions. It's a bit complicated, but I'll try to explain:
When the power is turned off, it doesn't go out at once - it takes a bit of time, several microseconds, maybe less, maybe more, depends on the capacitance of the supply path. During that time the electronic circuits still act, but with gradually diminishing voltage.
Circuits are built to function reliably in certain voltage range. The thing is that under that range, they don't stop functioning immediately - there is a range where they still function, but unreliably. Signals can receive erroneous values that aren't determined by the logic.
During that unreliable functionality period, a sequence of signals might happen that will cause overwriting one of the system partitions in the eMMC - since the logic doesn't function reliably, it can happen. If the phone is currently writing to eMMC (which might easily happen - programs read and write data when they run), you only need a couple of bits to fail in the bus address and write protection mechanism. The probability is very low and there are protections against that, but still, they aren't 100%.
If it happens, the phone is dead.
To add to that, there could be physical effects on eMMC chip from uncontrolled voltage drop.
So, this is why there's a recommendation to avoid pulling the battery, and using it only when really necessary.
Click to expand...
Click to collapse
well damn bro, didnt think it was that serious...
Hey Jack_R1 thanks for the input. I always enjoy getting a snapshot of information to clarify how things work.
wanabdev do you know if you're able to get into the boot loader to get access to fastboot? You really may be able to save your phone if you're still able to do this.
Wi-Fi Calling using Darkside Runny 2.2
Does anyone know how I can resolved my wifi calling issue using this ROM? I've tried about 10 ROMS on my MT4G, and found this to be the nicest. But when I'm on wifi, any calls I make or receive, the person on the other end says they can barely hear me. I can hear them just fine, but they can't. This is also true at multiple hotspots, ie. Starbucks, friends home, etc.
When I flash different ROM, this feature works just fine.
Help!
Chicago T said:
Does anyone know how I can resolved my wifi calling issue using this ROM? I've tried about 10 ROMS on my MT4G, and found this to be the nicest. But when I'm on wifi, any calls I make or receive, the person on the other end says they can barely hear me. I can hear them just fine, but they can't. This is also true at multiple hotspots, ie. Starbucks, friends home, etc.
When I flash different ROM, this feature works just fine.
Help!
Click to expand...
Click to collapse
same here, not rooted. any calls I make or receive, the person on the other end says they can barely hear me. I can hear them just fine, but they can't.
Wi-Fi Calling using Darkside Runny 2.2
glacier1122 said:
same here, not rooted. any calls I make or receive, the person on the other end says they can barely hear me. I can hear them just fine, but they can't.
Click to expand...
Click to collapse
Right, soooooo annoying. There's gotta be a fix out there? I like this ROM the best, it has all the little tweaks that make me happy!
Anyone have any ideas?
Flash the newest version.
http://forum.xda-developers.com/showthread.php?t=1283682
Related
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.
My DX lock screen just froze, I can't get it to do anything; it won't turn off...nothing happens when I hit any of the buttons. I downloaded Liberty 1.0 a couple of days ago. Does any know what to do??
wtivey said:
My DX lock screen just froze, I can't get it to do anything; it won't turn off...nothing happens when I hit any of the buttons. I downloaded Liberty 1.0 a couple of days ago. Does any know what to do??
Click to expand...
Click to collapse
Have you tried to pull the battery? I can't help you about what caused the error, but that should at least reboot the phone.
nvm, i just figured out how to take the battery out. problem solved
yeah I took it out and it worked...i didn't know i could pull the battery but I figured out how to do it
yeah, it's the simplest solution to problems like that. Just be careful not to do that while flashing roms. Even if the rom seems to be stuck. It's best to wait at least 15-30 mins.
What do you mean "flashing ROM?"
The term flashing is basically installing a new rom onto the phone.
I'm use to the computer terms where cmos bios chips were fproms and installing new firmware was called "Flashing"
Just be very careful with your phone. The terms that describe specific actions are golden on these types of forums. If you don't understand the terminology, please double check everything before you proceed with changing things on your phone. I know it is a fun world to play in, but one bad move can ruin your device. I'm not trying to be mean or to discourage you, I just want to make sure you have a fun and safe time without having to reprogram everything because of one "minor" mistake. We all started where you are now, so we understand the mysterious world. Just stay safe out there, friend.
Sent from my DROIDX using XDA App
This is just plain annoying.
Already having a bad day as it is - I was playing on Xbox Live when my 360 decided to throw up the red ring of death. In a pretty bad mood, I went upstairs and I tried ringing my dad so I could have someone to yell at and share my problem with (he's out drinking).
Unable to access my dad, I slammed my G1 against my computer desk, when the screen froze in mid-animation between the Dialler and the Home.
I left it, pressed some buttons, stuck. I took the battery out, back in, boot, fail.
My problem is that the screen is just a plain black screen. The screen itself clearly turns on (you can see the screen lights up slightly) but no g1 logo appears.
I'm pretty f**king annoyed at this, so if anyone can offer me some help, I'd appreciate it.
I'm running the 2708+ radio, the 1.3.003d (or whatever, it's the one with a d on the end) hboot, Amon_Ra recovery 1.7 (cyan style) and COS Gingerbread ROM (latest stable).
Dheano said:
This is just plain annoying.
Already having a bad day as it is - I was playing on Xbox Live when my 360 decided to throw up the red ring of death. In a pretty bad mood, I went upstairs and I tried ringing my dad so I could have someone to yell at and share my problem with (he's out drinking).
Unable to access my dad, I slammed my G1 against my computer desk, when the screen froze in mid-animation between the Dialler and the Home.
I left it, pressed some buttons, stuck. I took the battery out, back in, boot, fail.
My problem is that the screen is just a plain black screen. The screen itself clearly turns on (you can see the screen lights up slightly) but no g1 logo appears.
I'm pretty f**king annoyed at this, so if anyone can offer me some help, I'd appreciate it.
I'm running the 2708+ radio, the 1.3.003d (or whatever, it's the one with a d on the end) hboot, Amon_Ra recovery 1.7 (cyan style) and COS Gingerbread ROM (latest stable).
Click to expand...
Click to collapse
NO GINGERBREAD ROMS ARE STABLE FOR THE DREAM.....no matter what anybody claims. It is impossible for the dream to run GB stable....the hardware requirments just aren't there...it doesn't matter even if your swap is 16gb the phone can't process the info quick enough to run smoothly. The processor lacks the capacity to read the code quick enough do to the lack of internal memory so we use swap space. But no linux based os can operate efficiently in this manner and will cause all types of force closes. Literally after 10 days of normal use with absolutly no bloat.
Edit...can u boot into recovery or bootloader?
Sent from my HTC Vision using XDA Premium App
Edwg318 said:
NO GINGERBREAD ROMS ARE STABLE FOR THE DREAM.....no matter what anybody claims. It is impossible for the dream to run GB stable....the hardware requirments just aren't there...it doesn't matter even if your swap is 16gb the phone can't process the info quick enough to run smoothly. The processor lacks the capacity to read the code quick enough do to the lack of internal memory so we use swap space. But no linux based os can operate efficiently in this manner and will cause all types of force closes. Literally after 10 days of normal use with absolutly no bloat.
Click to expand...
Click to collapse
That is just plain incorrect. You incorrectly claim that *smooth* is a requirement for STABLE. It is NOT.
Dheano said:
so if anyone can offer me some help, I'd appreciate it.
Click to expand...
Click to collapse
I would suggest that you should look into anger management counselling. That seems to be the root of your problem. If you were in better control of yourself, you wouldn't have smashed your phone and broken it.
Your toy broke, so you wanted to YELL at your father. Failing that, you SMASHED your phone. This isn't looking good on you.
Learn to calm down. A few deep breaths.... relax.
And time to buy a new phone.
Edwg318 said:
NO GINGERBREAD ROMS ARE STABLE FOR THE DREAM.....no matter what anybody claims. It is impossible for the dream to run GB stable....the hardware requirments just aren't there...it doesn't matter even if your swap is 16gb the phone can't process the info quick enough to run smoothly. The processor lacks the capacity to read the code quick enough do to the lack of internal memory so we use swap space. But no linux based os can operate efficiently in this manner and will cause all types of force closes. Literally after 10 days of normal use with absolutly no bloat.
Edit...can u boot into recovery or bootloader?
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
I guess we should stop using linux in
mp3 players
dvd players
bluray players
settop boxes
routers
switches
atms
tvs
fridges
microwaves
on and on
wake up man, Linux is very good at almost everything
And GB is running just fine on my G1
in fact I think it runs better than Froyo
Dheano said:
This is just plain annoying.
Already having a bad day as it is - I was playing on Xbox Live when my 360 decided to throw up the red ring of death. In a pretty bad mood, I went upstairs and I tried ringing my dad so I could have someone to yell at and share my problem with (he's out drinking).
Unable to access my dad, I slammed my G1 against my computer desk, when the screen froze in mid-animation between the Dialler and the Home.
I left it, pressed some buttons, stuck. I took the battery out, back in, boot, fail.
My problem is that the screen is just a plain black screen. The screen itself clearly turns on (you can see the screen lights up slightly) but no g1 logo appears.
I'm pretty f**king annoyed at this, so if anyone can offer me some help, I'd appreciate it.
I'm running the 2708+ radio, the 1.3.003d (or whatever, it's the one with a d on the end) hboot, Amon_Ra recovery 1.7 (cyan style) and COS Gingerbread ROM (latest stable).
Click to expand...
Click to collapse
not sure I can help with the current problem
but this may be of help going forward
sorry i didn't read everything but im curious if you tried booting in recovery mode? if thats successful than i would try unrooting than starting from scratch and flashing a diff rom.. no better way to be sure han to go back to the beggining lol besides that i've never really heard of that issue.. sorry i cant help more than that i hope you resolve this problem..
Stupid thing is that I can do everything to it aside from getting it to boot all the way to work! I tried reflashing OEM roms and I tried custom roms. They all work just fine and it just won't boot all the way. I can turn it on and off, use format option, download mode and magldr. I keep my sim out and memory card. Before this all happened I always used OEM OS. Last thing I did was check my bank account, close the browser and click the power button to turn it into sleep mode. Few weeks ago I did have an issue with it for a day. It kept turning on and off constantly boot to random points. Mostly to the AT&T screen. It would boot all the way rarely and I got it to stay on a couple times for about 10 mins to copy all my stuff from it. Is it possibly something to do with the hardware being a POS and Just crapping out for no reason because cell phones are poorly made expensive bricks?
I've seen this issue across the forum several times. Unfortunately, just one case seemed to "return" to life, without understanding the reasons behind the "lapse".
What I can suggest you can do (and feel free to disagree) is get in touch with Cottula (creator of MAGLDR) and see if you can help you. You can send him the phone, maybe he can analyze it and get something out of it.
GL, mate, and if you find a solution, I'm sure other folks here would be glad to hear it.
Ahhh ok thats what I figured. I browsed a bit, but most of what I saw is people couldn't do anything. I didn't see anyone saying they could do as much as what I can do with it. I'll try your advice and see if maybe he could help. I took apart the phone to see if maybe someone came loose, though I saw nothing. Clean as a whistle. What I think maybe happen is it burnt up finally. I notice at times it would run extremely hot, mostly when I'm talking on it for more then an hour.
Well, for your sake I hope it's not burned out (hardware issue). I hope it has some software component that's screwed and that has a chance of being investigated and maybe fixed.
Also, the getting hot while talking/browsing for periods more than 30 min it's a known issue. It's however supposed to be quite warm, but not actually really hot, if you know what I mean. It it however possible that exposing the phone to higher temperatures to cause hardware issues.
In any case, I wish you good luck. Who knows?
I gave AT&T a call to see what they could do. The software warranty is 6 months past and she wasn't able to override anything that much passed over. Though I was able to get my 2 years wavered and get a early upgrade. So I got myself a Xperia Ion. I'm happy I don't have to put up with a flip phone for another 4 months. lol
I tried working on my focus a bit more playing with zune and other programs I found. Though I don't see it coming back to life trying all the different ROMs. I would think to make it work again is to re-flash the actual phone bios itself. Just like a computer starting it still uses DOS then loads the OS. I don't know how a phone works to much, but I'd assume same process. Something to do with the root-root of the phone telling it to be stupid and not boot properly.
Another note, where is the best place to sell this to get some money out of it? Screen and other pieces of its hardware are 100%. Should I try ebaying it?
I had a similar issue, last thing i did was removing the SD card before re-flashing the MGLDR and custom ROM
Hi, I have a LG K20 Plus. I currently can't turn the phone on, so I don't have much software information to give you. The phone was bought at T-Mobile (Metro by T-Mobile) and I had a SafeLink sim card and a 16 gb micro sd card inserted when the issue started. I have since removed both. It says Qualcomm snapdragon on the screen when it starts. It was also rooted and the bootloader is unlocked.
I broke the screen on my phone and I decided to do the repair myself. I have done about 7 or 8 screen replacements and I actually did this phone a year ago with no issues, so I felt I could manage this one as well. I bought an entire display (from ebay) and switched it out with no problems. Initially it worked great! I used it for a few days before realizing that I had no sound. I opened it back up and noticed the loud speaker had fallen out. I found it, put it back in, reassembled it as I normally do and turned it on.
NOTE: when I was reassembling it the second time, I actually tried to put a screw in a hole that wasn't a screw hole. I used a light to normal amount of pressure but I didn't force it. I think it's the hole where the moisture detector is. Picture #1
I turned it on and right after the logo screen I got a message that said "High temperature detected Powering off for your safety" and it immediately shut off. The phone does appear to charge normally but it won't stay on. I did a factory reset (I'm not sure if it's still rooted but the bootloader is still unlocked). I also switched back to the old (broken) display just to check if that would work. I couldn't see any difference in the shielding but I switched them just to be sure. I bought a new battery and installed it. I took a q-tip and 95% Isopropyl Alcohol and cleaned pretty much the entire motherboard, paying special attention to the battery connections. After each one of these things, I tried to start it with the same error message immediately upon start up.
NOTE: At no point has the phone every physically felt hot or even warm. I don't think it's on long enough for it to get hot. But something is wrong and I have no idea what it is. I, literally, took the phone apart, put in the speaker and put it back together in less than 5 minutes. Could it be I just bumped something and knocked it loose?
I searched for any information I could find both here and with google but there is next to no information on the LG K20 Plus. I did find some information on the LG V20 that had overheating issues, and that has been all the luck I've had. I watched several videos and it seems the solution is to apply thermal paste. But my phone doesn't have any evidence that thermal paste was ever on it. I went and bought some but I have no idea where exactly to put it or even if it's needed. Most videos showed people using some kind of aluminum foil but I'm not sure if that is safe. I have several old phone laying around and I managed to get some of the silver tape and a copper square thing but, again, my phone did not have these things to begin with. I don't want to start adding things only to make it worse.
There is a slight difference of the tape that is on my phone now (the display I just bought) as compared to the old one (broken display). Picture #2 Again, I have no idea if that means anything but I thought it worth mentioning. Picture #3 is how it looks now as if I were going to put it back together. Picture #4 is the part (don't know name) where the videos show to apply the thermal paste and the shielding.
I'm really at a loss as to what to do next and I can't really afford to take it in to have it repaired before next month. If anybody has any insight or answers as to what happened, I'd be very grateful for your help. I'm sorry for the long post. I just wanted to tell you everything I have done in detail. Thank you
If you're using Kernel Auditor or any other kernel adjustment simply reset to default and use only ondemand or interactive. There's also options for the thermal portion of the kernel, don't mess with those. If VCC or another thermal option was checked off turn it back on. Putting the GPS to the moderate setting (the one below high accuracy) will keep the temps down as well. Are you using a custom ROM? If you're on Discord you can feel free to message me SCOPE★ BRΞΛD #8460 . I am only offering that so we can get this resolved quickly for you, just copy and paste since I use special characters.
Omgosh, thank you so much for taking the time to respond! Although I'm sure everything you are saying is very smart, I have absolutely no idea what you're saying. I'll do my best to try and answer you. I don't know what SCOPE is or how to send a message there. I don't think I'm using any thing for the "kernal". Also, I don't know what VCC or Discord is. As far as turning off setting for GPS or any other app, the phone will not stay on. I get about 1 sec after the logo when it boots up, then the error message about overheating and it immediately shuts off. I did a factory reset so everything should be good to go as far as apps. I don't think I'm using a custom ROM. The only thing I did was install TWRP, unlocked the bootloader and rooted the phone a year ago but nothing since then. As I stated earlier, this happened right after I did a display repair. Is there something on the MOBO that can get bumped that will make your phone get hot or send a overheating error. My phone doesn't show any sign that there was ever thermal paste on it prior but should I add some now. Will that help?
Update... Now the phone does not power on at all. When I plug it in to charge it I get an error that says "Device temperature is too high or low. Please move to another place to charge. I wonder where you went. I googled SCOPE so I could sign up to message you like you asked me to but nothing but definitions came up. I know I'm out of my league here. You guys all talk so technical. I didn't understand one thing the person asked me for. I know it's rare to get a response as quickly as I did and I was so happy to see someone had responded. Now, I just feel stupid and defeated. I thought this site was inexperienced with cell phones friendly. I'm just trying to get help so I don't have to go out and buy another phone again. Can someone refer me to a site that is more directed toward people who don't know much about the technical side of cell phones... please! Again, thank you for your time.
HelpNeededPlz said:
Update... Now the phone does not power on at all. When I plug it in to charge it I get an error that says "Device temperature is too high or low. Please move to another place to charge. I wonder where you went. I googled SCOPE so I could sign up to message you like you asked me to but nothing but definitions came up. I know I'm out of my league here. You guys all talk so technical. I didn't understand one thing the person asked me for. I know it's rare to get a response as quickly as I did and I was so happy to see someone had responded. Now, I just feel stupid and defeated. I thought this site was inexperienced with cell phones friendly. I'm just trying to get help so I don't have to go out and buy another phone again. Can someone refer me to a site that is more directed toward people who don't know much about the technical side of cell phones... please! Again, thank you for your time.
Click to expand...
Click to collapse
Hey, I just wanted to say sorry this happened to you. The same thing happened to me. My LG K20 Plus, no matter what button combinations I push and for how long I hold them, will not turn on or go into download mode. Plugging it in to a charger or PC does nothing either. Before it got to this state, I got the infamous green screen of death/Demigod crash handler (google this--it's a known issue with some models of LG phones and it happens when they overheat). It's definitely a hardware/build issue, and especially since this issue keeps the phone from turning on or connecting to a computer, I don't see a workable fix short of buying a new phone, unfortunately. Again, I'm in the same boat so I'm not happy about it either. I would say XDA is by far the best site to find a fix to this sort of problem, so if no one here has any suggestions on how to fix it, I think you (we) may be out of luck.
Thank you for letting me know. I'm not sure of some of what you said but I did catch the bottom line. Basically, just hold onto the phone until someone here comes up with a fix or workaround? I have a question for you. Did your problem start after you did some kind of repair? I'm wondering if I bumped something on the mobo to make it give a false overheating error. Do you happen to know where that sensor might be located? Sorry you are having problems to. It really stinks when your phone breaks and no matter how much time and energy you put it to figuring out the problem to fix it, there just isn't any good answers out there. I wish you lots of luck and if you figure anything out, please update here so I can try it too.
You need a whole new phone.
That or you're gonna have to replace the hardware