So just to state the lead up to the unbootable phone.
Condensed version:
Flashed to Bio360 (ONLY working rom that was running for me thus far)
After a week of use, phone would boot for 5 seconds until screen turned pixelated
reflashed but did nothing
flashed to ICS using download mode again and worked but with limited function as when I first flashed ICS before Bio360
flashed using CWM6 back to Bio360 but still same problem
now will not boot into CWM6 and gets the pixelated screen either way
WILL go into download mode so I tried a few more ROMs to hopefully write over whatever issue there is with the software but nothing
reflashed using ODIN the CWM to 5 and 6 but same problem (will not load to CWM at all now
tried a few more times in the precise order as the first time I ever got the phone working with Bio360 (STILL a messaged up screen)
More detailed account of things:
I originally tried updating to the ICS upgrade a few weeks ago but got stuck on the boot screen and other issues. I finally flashed the CWM6 and updated the rom via that to the Bio360 rom. I finally had a working phone again after countless hours of trying to get it working. I locked my screen after timeout to a pin number but actually found it was a pain in the behind so tried to switch back. However I used the 'settings' feature which was present on the home screen after boot that comes with the Bio360. Then I deleted the icon an could no longer find the one that I was originally using, but found the other newer icon in the applications. So I took the lock feature off. Though it did nothing and the phone still required the pin. I tried changing it etc etc etc and nothing worked.
So, I flashed the Bio360 rom again and tried to start fresh, only to find that most of the settings that I originally were using before the re-flash were still present. This lead me to believe the settings are not completely wiped and flashing through CWM6 does not do a pristine clean update. Then I read that I should have to clear any and all settings by factory reset, clear cache, partition or whatever other clear functions I found within CWM6. So I did that and everything was back in good order again.
That is until I woke up 3 days ago and found my phone 'bricked'. Not literally as I am told it is almost impossible to brick one of these. Upon rebooting the phone I found that it was booting to the Samsung logo and after about 5 seconds, the screen becomes pixelated with red and green colours, sometimes lines all over. The longer I leave it, the more the screen becomes a wash out.
So I tried flashing the rom again using CWM6 hoping this would fix, but the same thing occured. So I tried to use CWM5 hoping that would fix it but still the same. I tried flashing back to gingerbread, then ICS, then Bio360 as I originally did to get the phone working with Bio360 but the only thing that I can do now is boot into download mode. Anything else causes the screen to become pixelated and wil not boot past the messed up screen no matter how long I leave it.
I searched for other threads but only found threads based on a single large pixel or a physically damaged screen. However, the screen is still functional as when I boot to download mode or just before the screen becomes pixelated, everything looks great. Plus there was one time when I flashed to ICS I got into the blank screen with limited functional capacity as when I first flashed ICS and the pixelated screen disappeared. So this leads me to believe this is a software issue.
I believe that there is an issue with files being left behind that are corrupted or something similar but I cannot even boot to CWM in order to clear everything possible.
ANY IDEAS? I have explored every option that my limited understanding of software could.
picture of what it looks like
This is a crappy picture from my old phone of something like what it looks like.
https://plus.google.com/photos/111944628817208100010/albums/5793637254528885841
This is a capture after it was turned off even and I plugged it into my computer, displaying the battery charging animation, though turned pixelated after a few seconds.
My gut says hardware damage, like something inside the Tegra itself is fried, ESPECIALLY since it's happening sometimes while still in the bootloader (charging animation).
Try Kies emergency recovery. If it flashes successfully but still won't boot, or glitches out like this during the flash, you'll have to start the RMA process.
I am unsure if it would be a hardware issue though since the screen is fine during the 'download mode' and did boot into the stock recovery after a flash a while back, then flipped back to not getting past the Samsung logo and pixelating again.
Would I be able to load the download mode portion of the phone if it was a hardware issue?
I ask because my gut says the opposite.
flashing CWM 6 causes my phone to be unbootable and pixelated screen
So, I have tried to update the phone into whatever other ROM that I can possibly get working only to find out that after flashing a ROM that flashes the original recovery program included with Android, voilà! The phone works again and boots into the black screen with pull down menu. Back to square one for me.
Why would CWM6 be causing such a thing?
EaglesIII said:
So, I have tried to update the phone into whatever other ROM that I can possibly get working only to find out that after flashing a ROM that flashes the original recovery program included with Android, voilà! The phone works again and boots into the black screen with pull down menu. Back to square one for me.
Why would CWM6 be causing such a thing?
Click to expand...
Click to collapse
I'm on CWMR6 since the begining without any issue. Did you flash the touch or the non touch version ? Also whcih odin version are you using, maybe that makes a difference. The 1.82 and 1.85 are tested to be working fine with both cwmr 5 and 6. Also by reading your thread is seems you've never been able to flash through ICS one click, if possible try doing that.
ninthsense said:
I'm on CWMR6 since the begining without any issue. Did you flash the touch or the non touch version ? Also whcih odin version are you using, maybe that makes a difference. The 1.82 and 1.85 are tested to be working fine with both cwmr 5 and 6. Also by reading your thread is seems you've never been able to flash through ICS one click, if possible try doing that.
Click to expand...
Click to collapse
I have been using the cwm5/6 touch and non touch. I have tried flashing them both. I have been using the most suggested version of ODIN 1.85 to flash. I do not think that it would make a difference as to which ODIN version I use, but then again I am quite ignorant on software.
The first thing that I did was tried the flashing using the one click method. I could only get to a black screen with the pull down menu containing the turn wifi on/off etc. I read that the problem may be permissions but I have tried that using the CWM when it worked and I was still stuck at the black screen with pull down menu. Without CWM I have no way of doing anything really since everything is in zip form and without CWM you cant use the zips.
EaglesIII said:
I have been using the cwm5/6 touch and non touch. I have tried flashing them both. I have been using the most suggested version of ODIN 1.85 to flash. I do not think that it would make a difference as to which ODIN version I use, but then again I am quite ignorant on software.
The first thing that I did was tried the flashing using the one click method. I could only get to a black screen with the pull down menu containing the turn wifi on/off etc. I read that the problem may be permissions but I have tried that using the CWM when it worked and I was still stuck at the black screen with pull down menu. Without CWM I have no way of doing anything really since everything is in zip form and without CWM you cant use the zips.
Click to expand...
Click to collapse
Well then probably a logcat output to a developer would help understand the problem you're facing. Find some knowledgeable developer who can help you read the logcat and find the issue. Or post it here and maybe somebody would give you a clue.
EaglesIII said:
So just to state the lead up to the unbootable phone.
Condensed version:
Flashed to Bio360 (ONLY working rom that was running for me thus far)
After a week of use, phone would boot for 5 seconds until screen turned pixelated
reflashed but did nothing
flashed to ICS using download mode again and worked but with limited function as when I first flashed ICS before Bio360
flashed using CWM6 back to Bio360 but still same problem
now will not boot into CWM6 and gets the pixelated screen either way
WILL go into download mode so I tried a few more ROMs to hopefully write over whatever issue there is with the software but nothing
reflashed using ODIN the CWM to 5 and 6 but same problem (will not load to CWM at all now
tried a few more times in the precise order as the first time I ever got the phone working with Bio360 (STILL a messaged up screen)
More detailed account of things:
I originally tried updating to the ICS upgrade a few weeks ago but got stuck on the boot screen and other issues. I finally flashed the CWM6 and updated the rom via that to the Bio360 rom. I finally had a working phone again after countless hours of trying to get it working. I locked my screen after timeout to a pin number but actually found it was a pain in the behind so tried to switch back. However I used the 'settings' feature which was present on the home screen after boot that comes with the Bio360. Then I deleted the icon an could no longer find the one that I was originally using, but found the other newer icon in the applications. So I took the lock feature off. Though it did nothing and the phone still required the pin. I tried changing it etc etc etc and nothing worked.
So, I flashed the Bio360 rom again and tried to start fresh, only to find that most of the settings that I originally were using before the re-flash were still present. This lead me to believe the settings are not completely wiped and flashing through CWM6 does not do a pristine clean update. Then I read that I should have to clear any and all settings by factory reset, clear cache, partition or whatever other clear functions I found within CWM6. So I did that and everything was back in good order again.
That is until I woke up 3 days ago and found my phone 'bricked'. Not literally as I am told it is almost impossible to brick one of these. Upon rebooting the phone I found that it was booting to the Samsung logo and after about 5 seconds, the screen becomes pixelated with red and green colours, sometimes lines all over. The longer I leave it, the more the screen becomes a wash out.
So I tried flashing the rom again using CWM6 hoping this would fix, but the same thing occured. So I tried to use CWM5 hoping that would fix it but still the same. I tried flashing back to gingerbread, then ICS, then Bio360 as I originally did to get the phone working with Bio360 but the only thing that I can do now is boot into download mode. Anything else causes the screen to become pixelated and wil not boot past the messed up screen no matter how long I leave it.
I searched for other threads but only found threads based on a single large pixel or a physically damaged screen. However, the screen is still functional as when I boot to download mode or just before the screen becomes pixelated, everything looks great. Plus there was one time when I flashed to ICS I got into the blank screen with limited functional capacity as when I first flashed ICS and the pixelated screen disappeared. So this leads me to believe this is a software issue.
I believe that there is an issue with files being left behind that are corrupted or something similar but I cannot even boot to CWM in order to clear everything possible.
ANY IDEAS? I have explored every option that my limited understanding of software could.
Click to expand...
Click to collapse
I have the same problem, i bought mine in ebay, (i live outside USA so i cant get money back) my problem start when i try to install a apk, then, i try to restore with wipe in cwm (sometimes works, sometimes no) and eventually, only download mode work. I dont know what i do, but in one of my trys, ICS 4.04 works everything, but i was network lock,i try to downgrade to Gingerbread and the problem come back, i dont know what to do, i feel like i waste te money.
PD: I have the roger version
EDIT: I just flashed ICS from ATT And works, but i w ould like to root and i cant, every time that i flash CWM, the problem come back
EDIT 2: I use the one click to install ICS from att and works, its seem the problem is when i use a custom rom or the CWM, dont know why, its seems that is not hardware because ICS works perfect, but Every custom rom or CWM, cause the problem
Maybe is there a way torecreate all the internal partition, i dont know, or something like that, to make a clean install, I am starting to regret for buying this phone, maybe the problem is because is from rogers (a security rule maybe?)
Sorry for my english
EaglesIII : your phone has hardware malfunction.
It is basically trash.
*sorry*
Sent from my SGH-I927 using xda app-developers app
ericpeacock79 said:
EaglesIII : your phone has hardware malfunction.
It is basically trash.
*sorry*
Sent from my SGH-I927 using xda app-developers app
Click to expand...
Click to collapse
I dont Know, its happen similar to me, but if i use ICS from ATT, everything works right
---------- Post added at 03:05 AM ---------- Previous post was at 02:45 AM ----------
Ok, i learned something, when a flash the Gingerbread version, there is a error while booting (the first time that boot lik recovery) , the error is can't access to /system/csc/ATT/system/
When i use the ICS from ATT, that doesnt happen, maybe that is the problem? i dont know, maybe someone can tell us what are these files
There is a working solution, http://forum.xda-developers.com/showthread.php?t=1953672 thanks to Rawr0w0,its works when you flash in that order, my phone is rooted and full working in ICS, i hope that helps you
OK, I seem to be having a hell of an issue with my note 2. I rooted it about a week ago and installed TWRP, a couple days ago I decided to try a new rom. It booted up and everything seed fine except that I would keep getting some type of out of service error, so I decided to try a different rom, SwampMonster. I installed it though the TWRP (obviously) and it was successful, at least so TWRP said anyways. So Upon first boot it seemed to be booting fine with the Orange circle and after about 20 seconds it stops and the screen went black. As I have seen this plenty of times before I let it sit for over five minutes. Also when the Orange circle disappeared the computer beeped to indicate that it had been disconnected. Now I can only get into recovery and kies will not connect. I also cannot access TWRP.. can anyone give my a bit of advice. I was thinking of using a rom that I can install with oden but I can only find zip file based roms. Thanks in advance. Oh also, ODIN does make a connection
For some reason my phone isn't booting up all the way to the rom/OS. It gets stuck on the boot animation and goes on forever and hasn't been able to boot up since yesterday, when my powered off at 20% battery, which is something normal for my phone. I was rooted and on android 4.3/MK4, but when I put it to charge and tried booting it back up, the phone would boot up, but would get stuck on the boot animation, going on forever. It wouldn't freeze it would just continue to play the animation. I tried removing the battery, factory wiping it, and installing a new rom, which I found out was for a different baseband. When i finished installing it it still wouldn't boot up all the way through.:crying: I then tried installing the previous rom, and still no good. After all that I installed a stock firmware using odin, hoping it would work. I installed the 4.4.2 NE2 firmware, which isn't for my phone but watching zedomax's video, he said to download the latest build date, which is what I did. Well, downloaded it and flashed it through Odin with a PASS and everything going good. Although, when it was rebooting-even after a factory and cache wipe-it still wouldn't boot up. I tried installing other firmwares aswell, but still no luck. I'm just waiting for it to finally boot up, so if anyone can help me out, I WOULD GREATLY APPRECIATE IT, otherwise, anything is going to help at this point. Since I flashed the firmware, I now have a stock recovery and rom(I hope). I've been through these types of situations, but not to this point.. :crying:
It seems odds, but you may want to try a new battery. I recently went through a total disaster with my device and it ultimately was the battery. You may want to try booting with it connected to the a/c wall charger. It may give you an indication.
Have you tried the quick fix posted? My phone did the same thing when i had the stock recovery it showed error mounting efs folder. I noticed after installing clockwork that error didnt show up. It was still the same problem though. Wouldnt hurt to check it out. I got my note two from a friend who described the issue starting the same way you said happend to yours. The phone had never been rooted though. Good luck to you in trying to fix it.
Sent from my SM-T217S using XDA Free mobile app
I have the ATT sgh-i747. I was using it as normal. The battery was low and i could not charge it before it got to 0%. After it died, I connected the charger and started it back up. When the screen came on, the "no sim-emergency calls only" message was there and the touch screen did not work. Also, the time and date were off. it said 3:59 September 15th. I tried the normal reset (take battery out, replace, turn back on) several times and still the same thing. I had just replaced the sim reader a month ago, as well as the rear camera and speaker, and everything was working as normal. I opened the phone up to make sure all connections were set. Still the same message. I did a factory reset and after I turned it on, still, the touchscreen does not work and it says no sim. I find it odd that both these things would stop working at the exact same time. Also the phone is long past its warranty. Any ideas on what this could be?
Anyone?
Have you tried flashing another ROM?
I don't know how to do that, if you could point me in the right direction I'd appreciate it.
Before anyone can give you advice, we need as many details as you are able to provide.
Was your phone running a stock ATT ROM? What ROM was it running? Are you able to boot into download mode?
Stock Rom, phone is not rooted and I can boot to download
What stock ROM? It's important that anything you flash does not try to downgrade the bootloader if you were on stock 4.3 or 4.4.
I'm not 100% sure. I want to say 4.3. There was a software update for the phone that automatically downloaded about a week ago but im not sure if that is related.
Since you received an update a week ago, you may be on KK.
I suggest flashing Philz Touch recovery via Odin and see if you can boot into recovery. In recovery you can see if the digitizer responds.
Flash the latest tar version from here in Odin: https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
Okay, so I'm not new to flashing roms or anything on this tablet. Been doing it on this particular tablet for years now.
But I think I really screwed up this time. I had been running an older version of Resurrection Remix ( I think it might have been lollipop, around '16 is when I installed it) and the battery was draining really bad suddenly. So after I installed a new battery I thought I'd put on a fresh new OS. Installed Lineage 14.1 and it worked wonderfully.
Then I tried to install TWRP because, I dunno... I didn't like the Cyanogen recovery that was on it.
I installed Rashr, went to install TWRP. Things looked okay, then it reboot. Got stuck at the downloading screen. Said at the top "Could not boot in normal mode."
Installed Kies, wouldn't connect to the tablet.
Installed Odin. Made a connection with the tablet. Still couldn't get rid of the "normal mode" error. Kept messing around with different button combos, popped the tablet open and disconnected the battery. Waited for a minute, put it back in and nothing different.
Finally I managed to get it to not show the "normal mode" error, but it might as well because Odin still doesn't work.
I remember a few years back I had to do some stuff on it to get the newer android OSes working on it, I think it involved repartitioning memory and stuff. So I don't know if I can try to go full KitKat stock rom or if it'll really mess things up.
I just want my tablet working with a recent rom.
I've literally spent 5 hours with this damn thing trying to get it working again and I'm at a total loss, here. Any help from you wonderful XDA folks would be so greatly appreciated!
EDIT:
Okay, so I let the battery drain overnight (the screen wouldn't turn off so it drained pretty quick) and while it's still stuck in Odin mode now it says at the bottom in red Unknown dev_type.
Have no clue what that means but yeah...