Related
Recently have been using the CM10 Jellybean ROM until the ROM manager update ruined my music and galleries. In any case I found it a a little laggy and buggy for the time being. I decided to restore from CMW back to my previous rascream and after reboot, got the Google screen bootloop. I had the battery pull to stop it but after one battery pull, the Nexus S no longer turns on. Plugging into the charger, nothing shows up. I have tried to pull battery again and enter recovery mode but nothing's happening.
Have I properly borked it?
- battery was fully charged at the time
- using clockwordmod 5.0.1.4 (old)
- i9023
Can you still boot into fastboot? You should still be okay if you can at least get there.
These phones are very hard to brick. I'd there any lights at all?
Sent from my Nexus S 4G using Tapatalk 2
thanks for the replies.
I can't get into anything on the phone. Pressing any combination of buttons doesn't light soft keys nor screen up. Also charging the phone for periods doesn't heat up the battery like some others have had.
I've put linux onto one of my old computer and tried the software AdamOutler mod to no avail. Both the Mode detector and Unbrickresurrector don't recognise my phone....
If you have the Problem with the gallery, you simply have to clear the Cache and Dalvik cache.....
=> Next time ? ,-)
No response at all.....I believe your last chance is JTAG.
hmmmm....... my last resort was to take it to a repairer and see what they think. Hopefully they can get it to power on and then I can sort out the rest.
RisinT96 said:
No response at all.....I believe your last chance is JTAG.
Click to expand...
Click to collapse
what's JTAG ?
JTAG video
qtwrk said:
what's JTAG ?
Click to expand...
Click to collapse
check out this video
http://www.youtube.com/watch?v=Ecp8jKmm48k
Here's a JTAG service if you want to give it a shot in the meantime go with a prepaid phone or a backup.
http://www.youtube.com/watch?v=Ecp8jKmm48k
Pirated Android said:
Here's a JTAG service if you want to give it a shot in the meantime go with a prepaid phone or a backup.
http://www.youtube.com/watch?v=Ecp8jKmm48k
Click to expand...
Click to collapse
it is very cool , but i don't have that tool that shows on video ...
Just an update on this. I returned my phone to warranty to be fixed. According to the repair notes, there seemed to be a problem with the board (not software related) thus was replaced. It also says in the warranty notes that the i9023 has quite a few of these board related problems.
Anyway, got Jellybean running OTA from Vodafone and it's working fine.
I never had a random reboot on ICS now on JB I'm having it at least once a week...not a lot, I know but still something is not right. The last time this happened I tried looking further into it and the only thing I see that may be causing the issue is signal loss. I am 100% stock and have maybe 25 downloaded apps, if that. Is there an app for STOCK that will backup some of my data? I really don't think a factory reset will help but I'll give it a shot. Any other ideas? I freaking love this phone and this is my only complaint....would love to fix the problem. Thanks.
Here's a shot of the signal before the reboot.
Is it worth trying a factory reset? I feel the chances of it doing any good are very slim. Switch to a different modem?
Sent from my SCH-I535 using xda premium
I'm having the same issue, and a reset did not help.
Sent from my SCH-I535 using xda app-developers app
Thanks for the reply. As long as it does not get worse it's not a huge deal. Maybe the next update will fix it?
Sent from my SCH-I535 using xda premium
Not sure what the right word is (hotboot?) but today my phone rebooted (not fully) while I was using it. No fc's or freeze ups, just the reboot. I'm currently on the no wipe leak which ended up being the official ota.... Since the no wipe was modified would it make any sense to install the full wipe version to see if the problem is resolved?
Sent from my SCH-I535 using xda premium
Flashed full wipe via Odin. In case anyone else has this problem I will post back with results in a week or so.
Sent from my SCH-I535 using xda premium
I'm having the same issue. It seems that something is causing JellyBean-enabled SGS3's to just jump into "interrupt heaven". It's always a quick boot, never resets the "Up time" counter, and only takes a few seconds to get back to normal, but it's a real pain in the arse!
Any ideas what the culprit is, guys? I'm running a newly replaced (ordered it on January 2nd and the first thing it does was download and upgrade to JellyBean "VRBLK3" before I could even start get it loaded, basically as soon as I activated the phone, it started to download the OTA before I could even get to anything else). I know in my case I have a couple of mods installed - maybe one or more of these is common amongst those of us having issues? I have the "4x5 scrolling" mod and the "BLK3 Logo fix" mod that removes the stupid VZW drum-beating and pulsating display on boot-up. Other than that, my phone is rooted (using method involving loading the older ICS bootchain so you can install the latest CWM recovery), has CWM Touch 6.0.2.3 and that's about it, other than your usual rooted toolkit programs. Anything common to the rest of you?
Oh, by the way - I've already tried reformatting the cache, blowing away the dalvik cache and even a complete factory reset, which seems to make it less jumpy, but it always comes back within a day or two if not just a few hours.
I had the same problem with mine rebooting when I had very bad signal. Last Friday I did a factory reset then Odin to 4.0.4 and let the phone update to 4.1.1 and the problem seems to have gone away. I am not willing to call it cured yet, but it hasn't rebooted since. This went from where I was rebooting constantly all day long at work and when on the road in bad signal areas.
So far so good.
By the way, I looked EVERYWHERE and couldn't find anyone complaining of this earlier so I figured it had to be a bad download of the update.
It's something in Jelly Bean update itself. I tried booting my phone in "Safe Mode" - which only loads factory programs, and it still happens. I sure wish I could put a finger on anything in the way of a pattern, but - so far there's nothing I can single out that seems to make any difference. I'll do the system/factory reset and re-install everything one more time just to see if it helps.
Weird...
Factory reset (and everything else) - it still reboots
ratledge said:
It's something in Jelly Bean update itself. I tried booting my phone in "Safe Mode" - which only loads factory programs, and it still happens. I sure wish I could put a finger on anything in the way of a pattern, but - so far there's nothing I can single out that seems to make any difference. I'll do the system/factory reset and re-install everything one more time just to see if it helps.
Weird...
Click to expand...
Click to collapse
Well, something in a factory reset helps, but it doesn't last. First, just to be thorough, I used "ROM Manager" to 'fix permissions', then I did a complete flush of the system, removed the micro-SDXC card, did a format of the cache partition, flushed the Dalvik cache, then did a factory reset and reinstalled everything. I seemed to help for a while, but eventually it started to reboot randomly - sometimes when it was just sitting idle not even being used at all.
That indicates to me there's something funky in the JB (VRBLK3) firmware, especially since I was seeing reboots even while I was booted in safe mode, where nothing loads except factory-installed programs.
Fortunately, it never reboots while it's in recovery or download mode... :silly:
Ah, I forgot to note: this is the second phone that acts exactly the same way with the VRBLK3 (Jelly Bean) ROM update. Symptoms of the problem are identical, down to the spontaneous combustion that started this thread. Mine's not "in pocket" as per the OP, but - I don't think that has anything to do with it.
ratledge said:
Well, something in a factory reset helps, but it doesn't last. First, just to be thorough, I used "ROM Manager" to 'fix permissions', then I did a complete flush of the system, removed the micro-SDXC card, did a format of the cache partition, flushed the Dalvik cache, then did a factory reset and reinstalled everything. I seemed to help for a while, but eventually it started to reboot randomly - sometimes when it was just sitting idle not even being used at all.
That indicates to me there's something funky in the JB (VRBLK3) firmware, especially since I was seeing reboots even while I was booted in safe mode, where nothing loads except factory-installed programs.
Fortunately, it never reboots while it's in recovery or download mode... :silly:
Ah, I forgot to note: this is the second phone that acts exactly the same way with the VRBLK3 (Jelly Bean) ROM update. Symptoms of the problem are identical, down to the spontaneous combustion that started this thread. Mine's not "in pocket" as per the OP, but - I don't think that has anything to do with it.
Click to expand...
Click to collapse
Thanks for thoroughly trying different things to try and figure out the issue. Your problem seems worse than mine... I was getting reboots every few days. All day today was fine after installing full wipe but that's not a thorough test for what I was experiencing.
Sent from my SCH-I535 using xda premium
Ryno77 said:
Thanks for thoroughly trying different things to try and figure out the issue. Your problem seems worse than mine... I was getting reboots every few days. All day today was fine after installing full wipe but that's not a thorough test for what I was experiencing.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
You could also try getting a new sim from Verizon to see if that helps with connectivity to towers. You've already Odin flashed stock images and wiped pretty much everything significant at that.
New SIM?
SlimSnoopOS said:
You could also try getting a new sim from Verizon to see if that helps with connectivity to towers. You've already Odin flashed stock images and wiped pretty much everything significant at that.
Click to expand...
Click to collapse
Well, unfortunately I've done that - twice in the past ten days, the latest one came Tuesday afternoon. No change, still just reboots while I'm not even using the phone, and it's not the phone, it's the software. I can't say for absolute certain that it is in the VRBLK3 / JB code, but I can say for sure it _is_ something I am running, but the fact that it does reboot in safe mode indicates it's not anything downloaded or added to the base system as shipped.
ratledge said:
It's something in Jelly Bean update itself. I tried booting my phone in "Safe Mode" - which only loads factory programs, and it still happens. I sure wish I could put a finger on anything in the way of a pattern, but - so far there's nothing I can single out that seems to make any difference. I'll do the system/factory reset and re-install everything one more time just to see if it helps.
Weird...
Click to expand...
Click to collapse
Irrelevant question -- can't help my curiosity. How is it that you're on your 6th GS3? You get a new one every month?
6 Pebble Blue 32MB phones in about 8 months
jaymattt said:
Irrelevant question -- can't help my curiosity. How is it that you're on your 6th GS3? You get a new one every month?
Click to expand...
Click to collapse
Heheh... Well, I got one on "day 1" by pre-ordering it from Verizon, after two months the power button fell off. They sent me a "CLN" one, it lasted ten days and started randomly rebooting (even if reloaded with 'virgin' unrooted OS), the third (another "CLN") was delivered with no power button and the volume rocker fell off while I was taking it out of the box. At that point, I got kind of pizzed and did the 'good customer for 10 years' and elevated it through three levels until I finally got them to ship me a brand new one. That one lasted two months until my wife left it on top of my car and I backed over it in my driveway. I used my Asurion (insurance) to get #5, which arrived rebooting from the moment I started it up. Within a few days after monkeying around with their tech support (they ain't the brightest bulbs - instructions include "remove the battery and dial yourself and hit the 'Send' key three times" - not kidding) I managed to get #6 shipped out, and it's first act of life was to suck down the VRBL3 (Jellybean) software update and I've mucked around with it for two weeks, tried loading it with various combinations of "No Wipe" and "Factory Reset" versions of VRBLK3, removed a bunch of programs I've had installed but never really used and it still just vibrates about once an hour (and it's totally random, sometimes lasts 6 hours, sometimes 6 minutes before rebooting), jumps to the "warm/quick start" and recycles without resetting the "time up" counter. I'm thinking it's something I fed it (i.e. a nasty program or interaction between programs) - but I've come up empty-handed so far as running it to ground.
Does anyone have any knowledge of known interactions or "bad programs" that just don't play well together under JB?
Sadly my friend, you need CLN #7. Nothing here is going to resolve that.
Sent from my SCH-I535 using xda app-developers app
SlimSnoopOS said:
Sadly my friend, you need CLN #7. Nothing here is going to resolve that.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Well, normally - I would agree. But this makes three phones that act exactly the same in a row. The first of which was my 2nd "New" GS3, updated OTA to Jellybean - which immediately started the rolling reboots. The problem with the "CLN" phones are that they were all defective in one way or another, or they wouldn't be recertified. I don't really think VZW does a good job recertifying these phones, there are just too many of them coming out every single day, and - lord knows Asurion probably is behind that curve. :silly:
All three phones have been identical in their behavior - "down to the letter" since VRBLK3 was released. :fingers-crossed:
Question: now that I've used my insurance, do I _have_ to go back to Asurion for replacement, or since I'm still in my first year, will VerizonWireless entertain sending me another? It seems like reading the information that comes with the Asurion phones, they are the ones that are now guaranteeing my phone for a full year from the time it was sent (that would be this past Monday).
The phone has an Asurion sticker inside it, not a VZW one...
And the winner is: battery replacement. Every single VZW marked battery causes it to reboot, but a plain old Samsung battery (made in Korea - I've noticed almost all the VZW branded SKUs are made in China) works 100% and gives me an average of 12 hours moderate usage. The batteries I had from previous phones, VZW and Asurion all have the Verizon markings on them, and every single one of them causes it to reboot. This new one I got today straight from Samsung does not.
Curious, huh? I have one out of five batteries with VZW markings, and it does the same as the other four "made in China" ones. You've gotta wonder...
Glad you found a fix. Is it possible the new battery is slightly larger? Wondering if the old batteries were maybe a bit loose.
Sent from my SCH-I535 using xda premium
Hello,
I'm having trouble with the camera of my TF700. When i try to open the camera, the camera still show up but with the black screen. After waiting for a while, it got frozen and i got a message "Gallery isn't responding. Do you want to close it". When i close it and reopen it, it shows the message "Camera error: Can't connect to the camera"
My gallery is still working fine. I still can be able to access to the picture on my SD card.
My Infinity is rooted and ROM CROMi-Xenogenesis 4.5
I did the factory reset, cold boot, wipe cache, fix permission. None is working.
I installed Skype to see whether the video is working. It's NOT. I tried 3rd party camera apps. They dont work either.
I'm lost and do not know how to fix this problem. If anybody knows any method that i can try out to fix this, i would really appreciate it
Thanks
koolvn said:
Hello,
I'm having trouble with the camera of my TF700. When i try to open the camera, the camera still show up but with the black screen. After waiting for a while, it got frozen and i got a message "Gallery isn't responding. Do you want to close it". When i close it and reopen it, it shows the message "Camera error: Can't connect to the camera"
My gallery is still working fine. I still can be able to access to the picture on my SD card.
My Infinity is rooted and ROM CROMi-Xenogenesis 4.5
I did the factory reset, cold boot, wipe cache, fix permission. None is working.
I installed Skype to see whether the video is working. It's NOT. I tried 3rd party camera apps. They dont work either.
I'm lost and do not know how to fix this problem. If anybody knows any method that i can try out to fix this, i would really appreciate it
Thanks
Click to expand...
Click to collapse
Did your camera work before rooting and/or installing CROMIX? Did it ever work on CROMIX? If its not the ROM it sounds like broken camera hardware. If so you'll have to send it back to Asus for repair. Unfortunately you are unlocked and have voided your warranty hence the only reason I'm still locked for the warranty period.
elfaure said:
Did your camera work before rooting and/or installing CROMIX? Did it ever work on CROMIX? If its not the ROM it sounds like broken camera hardware. If so you'll have to send it back to Asus for repair. Unfortunately you are unlocked and have voided your warranty hence the only reason I'm still locked for the warranty period.
Click to expand...
Click to collapse
I got this from a friend. It work once when i did the factory reset. After that time, it didnot work. Thus, i was thinking if i root it and use different Custom rom it might fix the problem.
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
koolvn said:
I got this from a friend. It work once when i did the factory reset. After that time, it didnot work. Thus, i was thinking if i root it and use different Custom rom it might fix the problem.
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
Click to expand...
Click to collapse
Sounds like you need to do a full wipe. If it ever worked doing a factory reset then its not a hardware problem its a software problem. But you said "it worked once". I assume you mean that it opened and took some pictures, but only once or did it work for awhile? Are you saying when you opened it a second time like that same day and every time after that it never worked again? If that's the case it still sounds like a hardware failure but possibly something else corrupted your camera software shortly after your factory reset. I would do a nandroid backup (Online Nandroid Backup rocks) then a full wipe then a nandroid restore. I would suggest you also get some other inputs on this problem as I am far from an expert and don't want to steer you in the wrong direction.
elfaure said:
Sounds like you need to do a full wipe. If it ever worked doing a factory reset then its not a hardware problem its a software problem. But you said "it worked once". I assume you mean that it opened and took some pictures, but only once or did it work for awhile? Are you saying when you opened it a second time like that same day and every time after that it never worked again? If that's the case it still sounds like a hardware failure but possibly something else corrupted your camera software shortly after your factory reset. I would do a nandroid backup (Online Nandroid Backup rocks) then a full wipe then a nandroid restore. I would suggest you also get some other inputs on this problem as I am far from an expert and don't want to steer you in the wrong direction.
Click to expand...
Click to collapse
Its exactly what u said. It work once. I took some pictures with it. I closed it and reopen it shortly after in the same day and the problem starts. At that time my device not even rooted. How do u do a full wipe. I used CWM to wipe but it doesnt go away. Im suspecting its the hardware problem however there is no way for me to be sure. If its the hardware problem, would replacing the camera will solve the problem? I cant send it to asus. Not much of the option here
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
koolvn said:
Its exactly what u said. It work once. I took some pictures with it. I closed it and reopen it shortly after in the same day and the problem starts. At that time my device not even rooted. How do u do a full wipe. I used CWM to wipe but it doesnt go away. Im suspecting its the hardware problem however there is no way for me to be sure. If its the hardware problem, would replacing the camera will solve the problem? I cant send it to asus. Not much of the option here
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
Click to expand...
Click to collapse
If you already wiped from recovery then that's the one. And you did a factory reset. And the problem occurred before you rooted and on the same day it once worked. I'd say its hardware. But it could be anything from a bad controller chip to a bad shutter motor to a loose or bad ribbon cable. You'd have to trouble shoot the all aspects of the camera hardware platform to fix the problem. You could take it apart to see if you saw something obvious like a loose ribbon, but its not as easy as just swapping out the camera itself.
Asus does non warranty repairs, they are just costly. You certainly can send it back to Asus. That's what I would recommend.
elfaure said:
If you already wiped from recovery then that's the one. And you did a factory reset. And the problem occurred before you rooted and on the same day it once worked. I'd say its hardware. But it could be anything from a bad controller chip to a bad shutter motor to a loose or bad ribbon cable. You'd have to trouble shoot the all aspects of the camera hardware platform to fix the problem. You could take it apart to see if you saw something obvious like a loose ribbon, but its not as easy as just swapping out the camera itself.
Asus does non warranty repairs, they are just costly. You certainly can send it back to Asus. That's what I would recommend.
Click to expand...
Click to collapse
I sort of figure out my problem but still have no cure for it. I downgrade it back to ICS and the camera once again works for a bit and when i tried to open and use it again in the same day, it said the firmware need to be updated. However, asus firmware update failed. I cannot update the camera firmware. I went through the upgrade again to lastest jellybean from asus website. It still shows that the camera firmware need to be updated.
I notice that during the time i flash back and forth, the camera firmware did not change at all. It shows TF700T-FFFFFFF. I think it's the camera firmware problem
However, i could not find a way to update the firmware manually. Any thought on this one?
Thanks
Hi,
I don't think this has been covered on here so I'd appreciate it if anyone can help.
When I am scrolling through screens, or watching tv on my Z3, the image of the previous screen is captured and displayed on the new screen for a couple of seconds over the new screen - example shown in the attached image. This has started in the last day or so and is not clearing with restart, reset or deletion of recent apps.
I haven't seen this problem before and I'll take it back to the shop if I need to but if anyone can advise what the problem might be - hardware or software - or how I might be able to fix it without it going off for repair, I'd be grateful.
Thanks in advance
Phil
I would try a factory reset first.
Thanks
CentaXx said:
I would try a factory reset first.
Click to expand...
Click to collapse
Thanks. Any ideas on what's causing it?
Probably faulty scren
Sent from my C6903 using XDA Free mobile app
Back up all your stuff and do a factory reset. If that doesn't fix your issues, I would reflash to stock firmware. If your issues still persist, it's obviously a hardware issue and you'll have to contact Sony to arrange a replacement. :good:
Thanks for all the answers. We have a winner it seems with faulty screen!
Yep happened to my G2 after Gophermods did a bad replacement job 3 times in a row, exact same issue. The screen is probably hosed, that is what happened with mine. Eventually got a money back and a free fixed screen.
You need to replace your phone in Sony
This is manufacture error
It was happend to me in old XPERIA Z
Hello,
I have an HTC U11, 4GB RAM, 64GB storage and for unknown reason it displays this message: Android System.UI has stoppedn working. I tried factory restet, I cleared cache partition, I installed a new kernel (cleanslate). It comes back to normal after I reboot the device (I cannot do anything on it because nothing will work)
Hello, I'm experiencing the same error. I thought it's from some app that I installed but it's not. It does crash about at least once a day. The screen just blinks on and off in the lock screen if I try to turn it on.
The only solution is to soft reset it.
kvrx said:
Hello, I'm experiencing the same error. I thought it's from some app that I installed but it's not. It does crash about at least once a day. The screen just blinks on and off in the lock screen if I try to turn it on.
The only solution is to soft reset it.
Click to expand...
Click to collapse
Same here, can't find the reason and only restart can fix it until the next crash... Spooky!?
Sent from my [device_name] using XDA-Developers Legacy app
Maybe you have damaged phones? I know that when my phone fell on the top left edge and screen cracked, also SIM was affected. It works but only without PIN code. If I have pin code I get system UI errors, cannot use the device at all.
Sent from my HTC U11 using Tapatalk
Platoon said:
Maybe you have damaged phones? I know that when my phone fell on the top left edge and screen cracked, also SIM was affected. It works but only without PIN code. If I have pin code I get system UI errors, cannot use the device at all.
Sent from my HTC U11 using Tapatalk
Click to expand...
Click to collapse
Same issue here, occurs one in a week, since I realize hard reset, not happen again.
Simply can't unlocked the phone, lock screen blinks, and the only solution is soft reset, I hope this not happen again.
Hi,
I have the same issue - it's been happening once a week for a few months now - the screen is blinking and the only way to "fix" it (temporarily) is to [soft] reset the phone. The error I get (when I can see it) is what the OP mentioned.
I too thought that it might be one of my apps but it's been happening even after I disabled a few apps.
I haven't ever dropped my phone...
Could it be a hardware issue (my phone is still under warranty with my company)?
Has anybody tried a hard reset?
Cheers
adita.cr said:
Hi,
I have the same issue - it's been happening once a week for a few months now - the screen is blinking and the only way to "fix" it (temporarily) is to [soft] reset the phone. The error I get (when I can see it) is what the OP mentioned.
I too thought that it might be one of my apps but it's been happening even after I disabled a few apps.
I haven't ever dropped my phone...
Could it be a hardware issue (my phone is still under warranty with my company)?
Has anybody tried a hard reset?
Cheers
Click to expand...
Click to collapse
I try a hard reset two weeks ago, not happen again, for now.