Related
Well this is odd...Since the GB Radio issue, I opted to revert back to Froyo after about a week of GB and have been running Bamf 1.7 overclocked at 1.4 smartass. Since reverting I've not had one single issue with reboots or what have you (GB I was getting reboots a few times a day). Everything seemed to be running quit nice on Bamf 1.7 and very smooth.
Well just a few moments ago while talking with a co-worker, I feel my phone vibrate and look at the screen and was in the process of rebooting!? Now it won't stop rebooting...It gets to the point where it's almost all the way loaded up to use and shuts itself off continually. Anyone have any ideas? Not liking this at all...
Taykiin said:
Well this is odd...Since the GB Radio issue, I opted to revert back to Froyo after about a week of GB and have been running Bamf 1.7 overclocked at 1.4 smartass. Since reverting I've not had one single issue with reboots or what have you (GB I was getting reboots a few times a day). Everything seemed to be running quit nice on Bamf 1.7 and very smooth.
Well just a few moments ago while talking with a co-worker, I feel my phone vibrate and look at the screen and was in the process of rebooting!? Now it won't stop rebooting...It gets to the point where it's almost all the way loaded up to use and shuts itself off continually. Anyone have any ideas? Not liking this at all...
Click to expand...
Click to collapse
Possible overheating issue (You probably had it set to OC automatically on reboot). Turn your phone off (In your case battery pull), leave the battery out for about 10 minutes then try it again.
Did you flash the Froyo radio as well?
Sent from my ADR6400L using XDA App
Im pretty sure he would have noticed not having data
Yes I've been on Froyo for the past 2 weeks with no issues whatsoever and now this morning BAM, it won't stop rebooting...The phone is not warm at all and don't know what could possibly cause an overheating issue. I haven't been on it hardly at all this morning except for 30 minute conference call about 2 hours ago.
I'm going to try a battery pull as suggested and leave it out for the time being and try getting her going again in a little bit. Hopefully this is some kind of fluke...
I can save you, i had the very same issue. I freaked out, mostly because i wasnt at home to move files on my sd card. I can almost gurantee your going to have to flash a backup or clean install if you dont have a backup ready. If you can get into your sd card on a pc via a card reader...make sure you dont have a pg05img sitting on there. Then boot into hboot with vol down and power. Then boot recovery and your good to go. If you dont have access to that, u can unclick your micro sd, and put the battery agasint the contacts while holding it at an angle so that it doesnt fully push the sd card into place. Boot into hboot select recovery, and then carefully fully insert the battery...this will cause the card to go into a readable position and you can flash a rom.
mastibeta said:
I can save you, i had the very same issue. I freaked out, mostly because iw asnt at home to move files on my sd card. I can almost gurantee your going to have to flash a backup or clean install if you dont have a backup ready. If you can get into your sd card on a pc via a card reader...make sure you dont have a pg05img sitting on there. Then boot into hboot with vol down and power. Then boot recovery and your good to go. If you dont have access to that, u can unclick your micro sd, and put the battery agasint the contacts while holding it at an angle so that it doesnt fully push the sd card into place. Boot into hboot select recovery, and then carefully fully insert the batter...this will cause the card to go into a readable position and you can flash a rom.
Click to expand...
Click to collapse
Ok thank you for the response...it's been given a few moments to "Call Down" and gonna give this a shot. Thanks for the response and I'll see if I can get her fired back up. Thanks again...I'll post my results after giving this a go
mastibeta said:
I can save you, i had the very same issue. I freaked out, mostly because i wasnt at home to move files on my sd card. I can almost gurantee your going to have to flash a backup or clean install if you dont have a backup ready. If you can get into your sd card on a pc via a card reader...make sure you dont have a pg05img sitting on there. Then boot into hboot with vol down and power. Then boot recovery and your good to go. If you dont have access to that, u can unclick your micro sd, and put the battery agasint the contacts while holding it at an angle so that it doesnt fully push the sd card into place. Boot into hboot select recovery, and then carefully fully insert the battery...this will cause the card to go into a readable position and you can flash a rom.
Click to expand...
Click to collapse
**Worked like a charm! Thanks again...Back to GB now! LOLzzz...**
Taykiin said:
**Worked like a charm! Thanks again...Back to GB now! LOLzzz...**
Click to expand...
Click to collapse
No problem, glad I could help, i am back on GB as well...lol
It's different for everybody, I never got a reboot since I got the phone.
Hey guys quick question I've been working worth my brother in laws t bolt.
When you flash a radio from hboot is that like fast boot before recovery?
and since he is rooted what rom its solid and should I flash so I don't have to revisit it again I had das bamf 1.63 running but have had a few reboots and gps locking issues
Sent from my Nexus S 4G using XDA Premium App
BAMF 1.6.3 is pretty solid, you may want to try a few different radios...or make the jump to GB...in such case go with gingeritis imo, and use the latest GB radio leak...has been working flawlessly for mine...well aside from the wifi tether dropping mobile network randomly after bout 30 minutes.
First off, thanks for xda. Favorite place for Android information. Droid charge is my 4th android phone and my knowledge of these phones isnt the greatest. Most I do is root and rom thanks to your guides.
Well anyways I just got my phone back from samsung after they repaired my Charge. It was in a boot loop, tried using CWR to install other roms but always stuck at samsung screen. Well I sent it in after unrooting and putting the stock rom back on. Here is what samsung said they did.
11/10/2011 6:20 PM-Melvin Garcia: The unit has left the technician. SOLUTION: Replaced PBA - PRL Updated - S/W Updated - Passed All
*11/10/2011//19:21:27//0001773863//Telephone//ASC*
SOFTWARE DOWNLOAD
PASSED RADIATION TEST
PASSED FINAL TEST
Well phone is working fine except the flashing triangle icon was on it, even with the stock factory rom. I romed humble 5.0 and the icon is still there. After research it appears its that I'm roaming, which im not. Same place I always lived. So I figured something maybe is wrong with my SIM card, so i took my girlfriend's Thunderbolt and swapped SIMs to test. My Charge still showed that icon while the Thunderbolt was fine. Is there any solution to this icon? Its rather annoying, a message pops up when doing certain things warning me that I am roaming and I should be careful of additional fees.
Any help would be greatly appreciated!
I randomly get this while 2 other charges that I'm next to don't.
Sent from my Gummy Charged GBE 2.1 using XDA App
It is 100% of the time though.
this may be late but I have the same issue. I sent it in again to fix this issue and it still came back with the blinking roaming triangle. Anyone that has had this ever had the issue resolved?
Hello everyone,
im new here,
I just bought Nexus S from some1,
it had a problem which later showed up.
The touchscreen works all by itself suddenly,
the left part of the screen is misbehaving, it starts touching on screen when its not.
it was on GB when i bought, then i updated it to ICS to see if the problem gets fixed but it gets more crazy, now updated to Jelly Bean, worked fine for a while, but now again its starting.
Any help will be appreciated
I think it is a problem with your touch screen hardware and not the android software. That being said, unless someone else has had the problem, no one can really help you.. Personally, since I've never heard of this problem, I'd recommend you get it repaired, even if it costs some $$. Hopefully someone else who has had the problem can help you out, but until then, best of luck!
FirePoncho86 said:
I think it is a problem with your touch screen hardware and not the android software. That being said, unless someone else has had the problem, no one can really help you.. Personally, since I've never heard of this problem, I'd recommend you get it repaired, even if it costs some $$. Hopefully someone else who has had the problem can help you out, but until then, best of luck!
Click to expand...
Click to collapse
first of all, thank you very much for replying,
Is there any way to fix it? there is not a single scratch on screen, phone is like gud as new, no bump, no scratches.
I wonder wat is making screen to hit by itself.
any way to fix it?
do u think its the digitizer troubling??
Raptor9142 said:
first of all, thank you very much for replying,
Is there any way to fix it? there is not a single scratch on screen, phone is like gud as new, no bump, no scratches.
I wonder wat is making screen to hit by itself.
any way to fix it?
do u think its the digitizer troubling??
Click to expand...
Click to collapse
take a backup and format sdcard, copy fresh rom to ur sdcard and flash it again may be it works.
abhidoT38 said:
take a backup and format sdcard, copy fresh rom to ur sdcard and flash it again may be it works.
Click to expand...
Click to collapse
Already tried all flashing. nothing helped.
but recently i did some wierd things with phone,
i burned my nexus s screen side, not actually burned it, but kept it to a distance from fire, just to heat it up,
i thought if there was any moisture that was causing the trouble might end up from burning,
after the phone cooled down, i placed battery and started phone..
wow amazing... it worked fine!!
but in the next step i inserted SIM card, i was going happy and was thinking "oh yes... saved the day!!!"
but boom, touchscreen started misbehaving again!!!!
i removed SIM card, but problem persists!!!
sad...
but i tried again,
removed battery and sim card,
burned phone again with more temperature as i was angry, wanted it to burn completely, but i guess i saved it.
now currently, without the SIM card, phone is working perfect as it was.
I dont know wat it has to do with the SIM card or burning
any1 knows wats its problem?? how can i use my SIM card with phone now???
Raptor9142 said:
Already tried all flashing. nothing helped.
but recently i did some wierd things with phone,
i burned my nexus s screen side, not actually burned it, but kept it to a distance from fire, just to heat it up,
i thought if there was any moisture that was causing the trouble might end up from burning,
after the phone cooled down, i placed battery and started phone..
wow amazing... it worked fine!!
but in the next step i inserted SIM card, i was going happy and was thinking "oh yes... saved the day!!!"
but boom, touchscreen started misbehaving again!!!!
i removed SIM card, but problem persists!!!
sad...
but i tried again,
removed battery and sim card,
burned phone again with more temperature as i was angry, wanted it to burn completely, but i guess i saved it.
now currently, without the SIM card, phone is working perfect as it was.
I dont know wat it has to do with the SIM card or burning
any1 knows wats its problem?? how can i use my SIM card with phone now???
Click to expand...
Click to collapse
i think the burning issue it was sim problem did u try another sim card? lolzs
abhidoT38 said:
i think the burning issue it was sim problem did u try another sim card? lolzs
Click to expand...
Click to collapse
tried another, no luck
Ok there was another problem, some part of left side of screen is not responding on touching,
previously i flashed a kernel which fixed the issue,
now i don know which kernel was it, lost it,
can any body help me on this issue?
miracle happened
yo guyz i cant believe it... everything is fine now.. phone works with sim too... i guess burning did help... and gues wat.. that left part of screen which was not responding.. its fixed by netarchy kernel.. i m currently using GB 2.3.6 with netarchy kernel.. can any1 give me Jelly Bean ROm? i tried some JB ROM but status 7 error occurs.. need help
Raptor9142 said:
yo guyz i cant believe it... everything is fine now.. phone works with sim too... i guess burning did help... and gues wat.. that left part of screen which was not responding.. its fixed by netarchy kernel.. i m currently using GB 2.3.6 with netarchy kernel.. can any1 give me Jelly Bean ROm? i tried some JB ROM but status 7 error occurs.. need help
Click to expand...
Click to collapse
you can update like this, one by one to get force update jb.. this trick works for me like charm http://bit.ly/Ok1EHa
Problem is back... and i think i found wat is troubling, its the SIM card, when i insert SIM card it does troubles, but when i use airplane mode, everything gets better.
tried different SIM cards, but no change.
so guyz tell me possible fix of the SIM card?
noticed another problem,
phone takes a very long time to recharge
and when i plug the recharger, sometimes battery indicates 10% or more Additional battery suddenly
i don understand wat is the problem?
Battery? Recharger? or SIM Slot??
im getting crazy now!!
Finally Its Fixed without spending any money
it seems baseband was troubling... as it was something like this i9020A this A is meant for AT&T thus its preferred network was WCDMA (my network is only on GSM).. i saw a code to see my phone info.. *#*#4636#*#*
This code showed up a window where i saw a button called radio... i switched it off.. i thought it was meant for FM Radio lol.. but it actually turned off my Cellular network.. i turned it back on and then i saw that the problem was gone... i went to see baseband and now its I9020XXX .. that A is gone..
Issue is fixed but there is one thing i don't understand at all.. how did fixing radio band fixed the touch issue? I think this conflict was causing Operating System to go crazy, hardware was never at fault..it was all software confliction.. I'm very happy its fixed..
If some1 have the same issue go here
*#*#4636#*#* turn radio off then turn on again.. hope it helps..and if it doesn't then at least it helped me
Sent from my Nexus S using xda app-developers app
I have a Nexus S and I have the exact same problem since last few days. I enabled "show touche" from the developer options to track the screen touch. Now I can clearly see that one column on the left side of the phone gets a random series of touches (in that one column only) from top to bottom. The issue I think is a HW issue, nothing to do with sim card, or ROM or anything related to SW. I have tried GB, ICS, JB and even "touch" version of the clockwork. It happens even in clockwork. It seems to me that I need to buy a Galaxy nexus unless someone knows of an easy way to fix this.
Same Problem
Hey man,
I got the same problem.
I tried so much things but it's absolutely a hardware problem, I found on the internet that there is some netarchy kernel modified by someone, but that's not up to date anymore. The kernel only works with a old version of android.
I update my android almost every month, it helps a bit but not much.
I am trying to learn all about building and modifying roms and kernels, but that is not that easy as I thought so that will take some time before I can publish a kernel for you.
Maybe if you can building kernels, try it by yourself?
Or google Nexus s unresponsive touchscreen, i found there some helpful answers. But they all not really up to date.):
I hope you'll find a way!
Sorry for my bad English
So, while I'm no expert I'm not new to rooting and flashing. Did it quite a bit on my older Droid Inc 1, and have performed a few on my new SG3.
I have 3 backed up ROMs on my SD, Synergy, Beans and CM10. I was running Synergy and decided to give CM10 another shot to see if I could figure out what was killing NFC. So, flashed it up with ROM Manager (Used Odin previously) and everything went swimmingly. ROM was running, NFC was working, all my apps were reinstalled, no problems.....
Decided to see if I could get Wallet working on this install, so flashed it in, made the changes to build.prop and rebooted.
Heeerreeee's where the trouble started. Part way through the reboot the phone just shut down. Completely. 100%. Dead.
I had 87% battery when I started so it 'shouldn't be a battery problem. No power, no LED when I plug in the charger, no vol-up, home, power to get into recovery.
One interesting thing did happen while I was trying to get the phone up, I removed the battery for a bit, and plugged the USB cable in and got a red charging light. Put the battery back in, light still there. 1 minute later, light goes off and still nothing happening with the phone at all.
Anyone have any ideas beyond all the stuff I've given a shot to?
Will it show up when plugged in on your CPU?
Sent from my Nexus S 4G using xda app-developers app
nexus995743 said:
Will it show up when plugged in on your CPU?
Sent from my Nexus S 4G using xda app-developers app
Click to expand...
Click to collapse
Unfortunately not. Only thing that seems to show up is in the device manager, a QHSUSB_DLOAD device that's banged.
Hmmmm
Sent from my Nexus S 4G using xda app-developers app
nexus995743 said:
Hmmmm
Sent from my Nexus S 4G using xda app-developers app
Click to expand...
Click to collapse
Well, I called Verizon and they've shipped me a replacement. I guess throwing all my bit and pieces into a new main body should work fine...
Oh no. Another one sending a phone back because of rooting. That's why they lock bootloaders.
Sent from my Galaxy Nexus using xda app-developers app
+1
Have you tried borrowing someone's battery to see if you can also least boot? I have four samsung batteries for the S3 and would consider sending it to you before getting a replacement. I think the cost of a battery is $3 on Amazon.
Sent from my SCH-I535 using xda premium
The reasons were different but i had the same thing happen to me, my phone wouldn't boot, wouldn't show up in the computer. Nothing, i tried my wife's battery, no change there either. I left it on the charger overnight and tried turning it on in the morning and after messing with it it came back on. Haven't had an issue since. Don't know what caused it, the phone just freaked out, turned off and wouldn't turn back on.
You can also try the resistor trick to see if that will bring your phone back. Here is a cheap way to do it.
http://hackaday.com/2012/09/03/saving-a-bricked-phone-with-a-pencil-lead/ Otherwise you can go to radio shack and pick up a resistor.
If Verizon sends you your phone back cause you messed with it, there is a brick repair service for like $60 bucks PM for the link if it comes to that.
Congrats on the new phone
Sent from my Nexus S 4G using xda app-developers app
nexus995743 said:
Congrats on the new phone
Sent from my Nexus S 4G using xda app-developers app
Click to expand...
Click to collapse
hehe.. I can't say I was pleased with having to go that route, (can't stand being defeated by electronics) but all in all I can't imagine a simple software change causing the entire unit to just go dead. Not booting properly, or locking up and such, sure... but not just dead.
By this morning I had tried another battery (a friend has an SG3 also) to no effect, but I didn't try leaving it plugged in overnight. I did check the battery with an external charger I have and it was showing fully charged....
So, I'll get a replacement and stay away from CM10 at the very least.
**ihavenewnike - Not sure why you're on an android developers forum really...
Ok, so the new phone got here at about 12:30. Plugged all my stuff into it and it fired right up.
Rooted and unlocked it, put my latest Synergy backup (1 day old) on the SD card and restored it.
Ahhhh... It's just like it never left. :victory:
keno1964 said:
Ok, so the new phone got here at about 12:30. Plugged all my stuff into it and it fired right up.
Rooted and unlocked it, put my latest Synergy backup (1 day old) on the SD card and restored it. . .
Click to expand...
Click to collapse
. . . and then the display went black and it wouldn't power on! What the heck?!
. . .
Oh, sorry: I was just imagining a funny ending to this topic.
- ooofest
ooofest said:
. . . and then the display went black and it wouldn't power on! What the heck?!
. . .
Oh, sorry: I was just imagining a funny ending to this topic.
- ooofest
Click to expand...
Click to collapse
Don't like you.......
Same thing happened to me when I tried to mess with the NFC hack on my SGS III.
What saved me was a USB Jig I happened to have handy when I...accidentally... soft bricked a friend's Samsung Captivate a few months back. The USB Jig is used to put the SGS III into download mode when all else fails that tiny little gadget saves the day.
tekrhino said:
Same thing happened to me when I tried to mess with the NFC hack on my SGS III.
What saved me was a USB Jig I happened to have handy when I...accidentally... soft bricked a friend's Samsung Captivate a few months back. The USB Jig is used to put the SGS III into download mode when all else fails that tiny little gadget saves the day.
Click to expand...
Click to collapse
I have looked into those and will most likely make one very soon. (I think I have everything I'd need, just may need to cobble some resistors together).
Couple of things I noticed throughout this 'process', regarding the CM10 (9-15 nightly) ROM, NFC and google wallet....
At first install of CM10 I noticed that NFC was active and working normally. It could read my tags without issue. After Wallet was installed though, NFC disappeared. It wasn't just disabled, it simply wasn't there any more. It was after noticing this that I decided to reboot, at which point my original problem started.
The reboot never came close to completing though, it shut down before it actually made it to the 'boot' phase, as in, while it was shutting down.
The actual cause of the power off is still a mystery to me, as I can't see a simple app change causing hardware failure.
So you bricked your phone, just like a few of us did yesterday.
What did you call Verizon saying in order for them to send you a new phone?
AB_ said:
So you bricked your phone, just like a few of us did yesterday.
What did you call Verizon saying in order for them to send you a new phone?
Click to expand...
Click to collapse
I told them what happened, just left out a few bits of info.
"I rebooted it, and it never came back on." and that was that.
Nice.
I should have gone that method, but ended up paying for the repair service from MobileTechVideos
A friend has the qhsusb-dload showing up as well.. phone won't turn on.. flashed a bad kernel or rom I forget which.. red light comes on.. that's it.. its a Verizon i535 .. tried the resistor jig and nothing happens.. any ideas to fix?
---------- Post added at 12:03 PM ---------- Previous post was at 11:59 AM ----------
Guess he had aokp rom then flashed neak kernel and that's when it died..
Delimma:
I have a stock 4.0.4 OTA A2 and is rooted, and any time I go into SQlite, and alter the entitlement check to "0" and restart it. It freezes at the "rethink possibilities" and never fully boots. It cannot be turned off until i pull the battery..
Now I've ensured that nothing else is changed because I've done a hard reset 2 times after trying this for the last day.. and id like some help before I attempt this a third time. So anyone have any ideas? And yes I checked the right directory: com.Motorola.Android.providers.settings and I altered the correct terms, I have not tried "disabled" yet and I'm confused… any ideas?
-Colin
Edit1: title
Edit 2: so, i changed the entitlement check to disabled and last night i forgot to put my phone on the charger so this morning, the battery was and is completely drained. Thinking things would be fine, i plugged it in and waited for quite some time, to no avail. I can finally get the screen on and it stays at the "M: Dual core Tech" screen, and i believe that I have soft bricked my device, can i get a second opinion on this, and if so, would the macgyver method be the best idea currently? Ive searched around a little bit, and ive came to a couple conclusions: 1. do the macgyver method and hope to put some charge in the battery and recover via boot menu, or try and FXZ back to OTA ICS?
Sent from my TF101.
you must change it to disabled, 0 didnt work for me either
sent from the gray stuff inside my skull
Thank you!! And then its okay to reboot right? Yours didn't stick at the splash screen?
Sent from my MB865 using Tapatalk 2
boots just fine
sent from the gray stuff inside my skull
demonoid phenomenom said:
you must change it to disabled, 0 didnt work for me either
sent from the gray stuff inside my skull
Click to expand...
Click to collapse
Weird mine always worked set at 0.... I never updated past leak 1 tho so must be something was changed...
Sent from my MB865 using xda app-developers app
new issue, read post #1
Sent from my Transformer TF101 using Tapatalk 2
try out macgyver stuff, then do wipes all over the place fix permissions, i think fxz would be too riskier cauze you wont know how much juice you put into battery and risk an awful hard brick
sent from the gray stuff inside my skull
So temporarily fixed my soft brick, got no power, but had a white led when plugged in, read a bit online, and heard to plug it into an outlet after a little bit, and that solved it for a while, so today, tried to access the phone, it locked up on me. I pulled the battery, trying to boot up, and that failed. stuck at the moto flash screen, each time I try to power it up. so now that im here, should I try to fxz back to stock 4.0.4 using: http://forum.xda-developers.com/showthread.php?t=1961310 since I was already on OTA, or is there another idea someone else has?
Colin31 said:
So temporarily fixed my soft brick, got no power, but had a white led when plugged in, read a bit online, and heard to plug it into an outlet after a little bit, and that solved it for a while, so today, tried to access the phone, it locked up on me. I pulled the battery, trying to boot up, and that failed. stuck at the moto flash screen, each time I try to power it up. so now that im here, should I try to fxz back to stock 4.0.4 using: http://forum.xda-developers.com/showthread.php?t=1961310 since I was already on OTA, or is there another idea someone else has?
Click to expand...
Click to collapse
Yes use that fxz that you linked. That is what you want it you took the ota, that should fix you up. Good luck!
jimbridgman said:
Yes use that fxz that you linked. That is what you want it you took the ota, that should fix you up. Good luck!
Click to expand...
Click to collapse
I FXZ'd back using that link, and I can't boot fully, it still stays at the flash screen, and I cant even boot into recovery. Just reflash?