Develop Bugs

[Q] Unbootable green and red pixelated screen on boot and CWM6/5 load

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

Where in the world am I going wrong?

Okay, I don't know what the deal is but I've now screwed my second device lol
I have a T-Mobile H811 on 10H, my second to be exact, and after I follow instructions for low level root and flashing a recovery, everything works fine! For as long as I stay on that rooted stock image...
The moment I flash anything other than the rooted stock image my device looses sound, becomes extremely slow and unresponsive, with the SystemUI crashing constantly and restarting. Shows lock screen, doesn't respond to touch, and if it does it's only for a brief moment before it freezes and then shows "Optimizing Android", rinse, repeat.
This persists through returning to stock with a kdz. Once it begins, it doesn't stop, which is why I had to return my first device...... and it looks like I'll be returning this one as well :crying:
I am no stranger to the game, I was not on 10N, I made sure to use the right COM port (the diag one), I make sure to only flash things for the H811, so what in the world is happening to my device when I flash other roms? My first device I flashed BlissPop nightlies and thought that might have been the reason, this time I just flashed a modified stock image. I for the life of me cannot figure out what I'm doing wrong or how to undo the damage once it's been done.
I still have access to download mode and TWRP
I am desperate for help... I cannot seem to find anyone else who's had this issue. Missing those Nexus 5 days D:
Thanks in advanced
EDIT: I flashed back to stock and took the 10N update (it was like pulling teeth) and everything seems to be working again... but I'd really still like some insight as to what I did wrong lest I do it again.
And now I flashed Bliss and everything is working just fine... strange

I Bricked and Unbricked my day one V30 in one night (How to not be completly screwed)

I picked up my UK V30 H930 yesterday all fine and saw that LG have unlocked the bootloader on my model so I went ahead and tried it along with trying the alpha TWRP build
So I thought id write about what went wrong and how I recovered from it.
I made the mistake of letting the phone auto update to 10v software verion before I did this. As I had 10f on before when I bought the phone.
I went to load in all the software needed to unlock the bootloader and proceeded to do so but in my haste of the user data being wiped taking a longer then I thought it would I unpluged the phone to try "fastboot flash unlock unlock.bin" again . No such luck already unlocked. It booted back in fine so I thought everything was ok but that was the moment I thought could have caused my entire night to be ruined.
I thought with the bootloader saying it was unlock it was now fine to flash TWRP on now so went to do that and discovered it would no longer boot into the rom anymore coming up with the LG V30 Logo and just staying put. Thought it must be my 10v software version messing it up. Ok ill try to flash a 10f stock kdz. After about an hour or so of 'Finding my feet' with the phones boot methods for download mode, Fastboot and recovery I found that twrp was being strange with mounting the phone tried otherways eventually got the phone talking to the pc by using uppercut with LGUP and having the phone in download mode and the port com channel in device mananger set to com 41. After about 4 tries of flashing KDZ's to the phone it would just come with a "erasing" circle and proceed to get stuck on boot logo again so I messed about with .dlls and tried to other methods. Still nothing.
Now I tried LG Bridge's "Update error recovery" and I was actually talking to the phone for the 1st time so i let it do its thing which took well over an hour to download the kdz file. "Fine just work please". it got to the updating stage at 5% and froze and the phone being in download mode hadnt done a thing. I tried again but still nothing. Eventually now at 6am and having been up all night I went to give up but I manged to get it on to fastboot mode and by chance came across "flashing lock_bootloader" tried and it and it locked tthe bootloader back up (this thing of LG saying it cannot be undone must be rubbish?) now before I tried anything I rebooted the phone . IT BOOTED! onto the fresh 10v KDZ i had installed on it but before anything I wanted to see if it would now run with a unlocked bootloader on its own with no TWRP installed. It works! Now i just need a method of rooting but im now ready at least.
Hope this helps anyone with simular troubles.

Also had some trouble yesterday after trying out some Magisk modules.
On reboot it sometimes got stuck in the LG V30 screen, and sometimes even the bootanimation came up, but it didnt finish the boot lol
Only installed and adblock btw, and tried the Xposed module. Uninstalled that again btw. Now only using Adblock.
Phone also seems to need Power + Vol- to force shutdown for me, not only Power like other phones. Also didnt manage to find a way to boot into recovery when the phone is off, only found a way to get into the factory reset screen ?
sadly i dont have a working sdcard currently (my 3 year old 128GB one is read only for some reason, atleast changes dont get applied), so ill wait for a new one to mess around more ^^
Also working on a LOS14.1 build atm (it compiled, but didnt adapt all parts of thr device tree yet, and no idea if i have all vendor files lol)

SGCMarkus said:
Also had some trouble yesterday after trying out some Magisk modules.
On reboot it sometimes got stuck in the LG V30 screen, and sometimes even the bootanimation came up, but it didnt finish the boot lol
Only installed and adblock btw, and tried the Xposed module. Uninstalled that again btw. Now only using Adblock.
Phone also seems to need Power + Vol- to force shutdown for me, not only Power like other phones. Also didnt manage to find a way to boot into recovery when the phone is off, only found a way to get into the factory reset screen
sadly i dont have a working sdcard currently (my 3 year old 128GB one is read only for some reason, atleast changes dont get applied), so ill wait for a new one to mess around more ^^
Also working on a LOS14.1 build atm (it compiled, but didnt adapt all parts of thr device tree yet, and no idea if i have all vendor files lol)
Click to expand...
Click to collapse
Ive just managed to get 10f on so ill retry flashing twrp now.
Are you sure your sdcard doesnt have a little read/write switch on it . Im sure i remember so of them used to have one.

Dreamxtreme said:
Ive just managed to get 10f on so ill retry flashing twrp now.
Are you sure your sdcard doesnt have a little read/write switch on it . Im sure i remember so of them used to have one.
Click to expand...
Click to collapse
nope, doesnt have one. Neither windows nor Linux fail at writing on it, or when deleting files, but as soon as I re-insert the SDCard all changes are reversed. Formatting doesnt work anymore, unknown error. Tried that in Windows, Linux and in the Phone (Androids formatting crashed, TWRPs produced an error after it timed out)

Stuck on google logo boot screen after twrp recovery & then factory reset

Hi guys, bit of a saga here so bear with me...and also it should be mentioned I have little experience/understanding of tech stuff, so that isn't helpful either lol
I've had a Nexus 5x running 7.1.2 for not quite a week; it came with an unlocked bootloader (strangely). Tried to do the usual install twrp & root as I've done with previous phones (all pre-nougat) but all attempts failed. Couldn't boot into stock recovery from the bootloader at all, it would just boot into the system. OK, next thought was that an OTA upgrade to Oreo might work to restore a recovery - but got the BLOD (naturally lol). I found a fix in a modded 4-core Twrp 3.2.1 -0 fbe img + workaround injector zip from osm0sis & XCnathan32 which by some miracle worked.
So far, so good. Ffwd a few days and google play store keeps crashing on opening; I had the feeling that some glitch happened while it was updating, so I tried all the usual fixes like app cache/data wipes and uninstall updates/renistall google play, delete google account etc which failed. Next I tried a cache & data device wipe through twrp - also unsuccessful. Finally, I thought the only thing left to try would be to restore a backup I made on twrp - this led to the current issue of not booting, stuck on the google logo screen. I even thought what the hell! and attempted a factory reset with twrp - same result, where I am now. Google logo screen, however I still have an unlocked bootloader.
Would anyone be able to suggest where I might go from here? I'm pretty sure the version is N2G48C, if that helps.
Any suggestions very much appreciated...wouldn't mind getting to the 1 week mark with a functioning phone lol

Saga #2
Still no idea what's going on. I realised that I'd backed up and recovered the system and vendor .img files, which according to this thread would be a cause of the issue https://forum.xda-developers.com/nexus-6p/help/stuck-google-logo-twrp-backup-restore-t3320840/page3
So I made another backup without those images, did a full wipe and restored it - still does not boot, still only sitting on the google logo. Tried next to open a cmd terminal to see if I could reflash a stock image, but adb could not connect (maybe because the phone would have been on charging and not file transfer mode?)
Last resort as I saw it was to try the NRT, and see if it would flash stock via the bootloop/softbrick option. Process seemed to be OK, judging by the log - but it did not reboot to the system. Now there is a looping bootloop between the google logo and the unlocked bootloader warning.
Following wugfresh's instructions to factory reset from the recovery (the phone won't turn off via the power button so I just booted straight into the bootloader) Looked for the recovery option, selected....and nothing!!
So there isn't a stock recovery??? How does that work?
And what hope is there for this phone now? (I can't think of anything else )
Anyone have an idea? I've never heard of this before tbh!

Well, my problem has been sorted. In the absence of knowing what the hell I should do lol I managed to get a refund for the phone even though it was a refurb to begin with (something to be said for an honest seller who provides a 3 month warranty!) and I picked up a brand new N5x, which was unboxed on Tuesday. Not even 6 hours into setting it up, the phone started to get progressively hotter and then went into bootloop. Got into the bootloader and tried a factory reset - all seemed OK but halfway through the setup process it bootlooped again. Fortunately it was still within the 2 year warranty, and LG didn't argue about authorising a repair for a phone which didn't get even half a day's use on it lol
Authorised Wednesday, walked into the service centre Thursday and a 1 hour wait later had phone in hand with the PCB/motherboard replaced. Has been working fine (and cool!) ever since. Definitely feel lucky to have hopefully dodged a bullet on this one.
Bonus that they upgraded from 6.0 to 7.2.1 while they were at it; apparently LG considers nougat the "latest" stable version for the 5x.

Help troubleshooting a confusing bricking? (Solved)

So previous to yesterday I had a fully working Galaxy S9 G960F, running the latest version of crDroid 11 (from 2021 heh), and something like TWRP 3.5.1? A fairly old version anyway, since I'd been running the same OS for the past year. I recently noticed someone had gotten 13 working on the S9, so I downloaded it and installed it like I'd done every other time installing a custom OS before, rebooted, and then the phone starts automatically going to recovery on boot, but gets stuck on the TWRP splash screen each time.
So I figured maybe the version of TWRP was too old for Android 13, and grab the latest (3.7.0), flash that with Odin, start the phone and I can at least get into recovery this time. So I try installing crDroid again. Same deal, just instantly boots straight back into recovery. So, figuring I'd best just go back to what I was using before, I reinstalled the previous crDroid 11 I had been using, and.. for some reason with that installed it only boots into Download mode unless I force it into Recovery. I try wiping everything and trying again, same deal. I even tried installing a different rom (Evolution X) and that just straight reboot looped.
If I go back to 3.5.1 TWRP it gets stuck on the splash screen btw. I am not sure what to do from here. Can I go back to stock and start over? Is there something else I should be doing? I've changed roms a bunch of times in the past and this is the first time 'just reinstall what worked before' hasn't worked, heh.
(For clarification, with crDroid 13: Phone turns on, shows Samsung Galaxy S9 boot screen, then goes straight into TWRP. With crDroid 11: Phone turns on, Galaxy S9 boot screen, straight into Downloading. With Evolution X: Phone turns on, Galaxy S9 boot screen, shut down and reboot. Buttons don't seem to be pressed in.)

DeiwosN said:
..... Can I go back to stock and start over? Is there something else I should be doing? I've changed roms a bunch of times in the past and this is the first time 'just reinstall what worked before' hasn't worked, heh.
....
Click to expand...
Click to collapse
Similar thing happened to me on a different Samsung device.
I did:
Used at that time SamFirm_Reborn_0.3.6.2 to get latest stock from samsung servers directly after inserting correct device designation and csc code.
Checked "binary nature" to get the full multiple part stock rom.
Flashed that with Odin.
Started from scratch.

Thank you so much! That fixed it.

DeiwosN said:
Thank you so much! That fixed it.
Click to expand...
Click to collapse
Glad I could help.
Perhaps useful for other users that you mark this thread as solved.