So I looked in the bricked section and the bootup sections and couldn't find my answer. I am sure it is somewhere but my search didn't turn it up. I have been using the sprint SII for about 8 months now, no real problems. I rooted it and flashed over using Odin an older version of Calkin's EG4T rom, it worked fine, I updated it about 3 months ago to the newest version (honestly I forget which but it was right before ICS started coming out). Today I come home from work and find my phone black screen off when I hadn't turned it off. I try and turn it on and nothing. So I pop out the battery and restart it, it loads up but everytime I try something it comes up with provider error and crashes the program, even when calling. So I boot into recovery and delete the cache and try again, same problem. Try to reinstall using recovery from the old update.zip file, it goes through but now it only boots into recovery, no booting into a new ROM at all. I check to see if I can still enter the download option and I can but I haven't gotten the newest tar file to push from odin so I quit. I try one last time to use android commander to copy over a new ROM, it appears to copy and I try the install and it claims it completed and now my phone only boots to the Samsung Galaxy SII screen. It won't go any further, I can't enter recovery OR download screen. I have tried leaving the battery out for 5 minutes and still stuck at the same screen. I can reboot from the screen but nothing else. Odin is unable to push the newest rom onto the system. Anyone who has any ideas I welcome it as I really do need this phone tomorrow.
thanks and I do hope I didn't miss an obvious thread covering this exact problem, but I do not believe i did.
you say you can't get into recovery or download, but also say that odin won't push newest rom onto system. Are you sure you're holding right buttons to get into download mode? (power+vol dwn, then volume up once the screen comes up to bootloader)
Well update, still fun. I pulled the battery for 10 minutes and now am able to get to the download screen (I was clicking for it correctly before I swear), and I pushed the newest Calkin's rom and it went through. But I am still stuck on load at the samsung screen. And what is even more fun is it won't actually turn off. I hold the power button for power off and it just restarts the sucker. I am going to try and push the stock rom next. Any other ideas?
thanks
If you can't get into download you're bricked. What update.zip did you flash? Usually that only works if you flash an authentic sprint/Samsung update or created a signed update.zip on your own. Also, did you flash it from stock recovery or clockwork mod?
Sent from my SPH-D710 using XDA
dante32278 said:
If you can't get into download you're bricked. What update.zip did you flash? Usually that only works if you flash an authentic sprint/Samsung update or created a signed update.zip on your own. Also, did you flash it from stock recovery or clockwork mod?
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
I did the update through cwm just as I had done previously so I figured it would work, but it seems I figured wrong
I am now able to get back into CWM but still unable to actually load past the samsung screen (yes I have left it going for a while), any ideas? Also trying to determine which specific kernal is the newest stock kernol for the sprint s II, any links? I am seeing lots of modified but nothing stock (in tar format).
thanks
edit- When I access the phone through android commander (it finds it) the folders it shows as being on the phone are all incorrect. Some of the titles are correct but the actual files within are missing or it is claiming the folders were made in 2000. I know I have not wiped the SD card as I can see it via cwm but can't seem to edit it on commander.
Also I am unable to actually view the phone when in cwm through android, only finding it in commander when it is stuck in the loading samsung screen
Final edit:
Finally got a stock one click to fully complete through Odin! back to stock, now to reroot and get my old stock on there
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
So, a few days ago I flashed the Vanilla Root Box rom from a rooted & unlocked stock rom. Couldn't get a GPS lock so I read that some people had luck by flashing a ZVB rom, getting a GPS lock, and flashing back to Root Box. Well, when I flashed back to a stock rooted ZVB rom, my LGOG got stuck on the LG logo and wouldn't boot completely. So I went back into recovery, Hard Reset and Wiped Cache and Dalvik, Fixed Permissions, and tried to reboot..... still stuck.
Then I tried to flash back to Root Box and it wouldn't boot passed the startup screen either. So I said screw it and tried to use LGNPST with a ZVB teenybin. It seemed to load the software fine, but the phone would not boot or let me get to the fastboot screen so I couldn't get into recovery. After another attempt, I used LGNPST with a complete stock ZVB bin.
The phone finally booted completely but then I realized the home button had lost ALL functionality and the phone, when connected to the computer, wouldn't pull up the options to change from Charge Only to MTP/PTP. I had to manually go to PC Connection and change it from there. After rooting and then unlocking using FreeGee, tried to boot back into recovery and got stuck in ANOTHER boot loop at the LG screen. Decided to use LGNPST to downgrade to ZV9 and then LGNPST again to ZVB. I have now regained my home button and the device recognizes when connected to the computer.
However, my main problem now is, between all that flashing it looks like my device created a second storage partition. I now have a completely new internal storage file system and It took my regular storage and put it under a folder named "0". Has anyone ever seen this? Can I just pull off what I need from the old stuff and delete the "0" folder?
I have attached a picture to what my files look like now. It's in a .7z because the size of the image was too large. On the left is the new system with the "0" folder highlighted and on the right is what's inside the "0" folder.
Okay buddy.
So my fast boot screen doesn't let me display the options I toggle so I have to wing it to get into recovery.
The sdcard is emulated so the internal folders will be /0 and /0/0 and so on. So you just need to travel those directories until you find you ROM and gapps.
I'm not used to the way the LG OG emulates the sdcard but I'm getting there.
Sent from my Nexus 7 using xda app-developers app
Thanks man. Im just gonna backup what I need and delete the 0 folder. But I realized I have a new problem now. My device refuses to boot into the bootloader so I cant get into recovery. Every time I try, my device gets stuck at the LG screen and I have to use a TeenyBin to get the device to boot all the way.
Sent from my LG-LS970 using xda app-developers app
I have a T999 that is locked up. I would like to try and restore this phone if I can. The buttons do nothing anymore. I cant get it into recovery (was TWRP) or download.
I found someone who had made a debrick image to boot from the SDcard. I have it on a 32G sdcard and can kind of get it to boot with the sdcard. Usually it only stays in recovery or download for a few seconds. I cant get Odin to connect to the T999. Odin sees my Galaxy S4 fine though.
Any ideas of how to recover this phone or should I just forget it? I am about sick of Windows 7 (64) so I am about to go back to Linux if that would help. Thanks for any tips.
I was able to get TWRP installed, kind of. Im not sure which TWRP. It was on another debrick image. Now it is working with the buttons though. It just wont make it past the logos on recovery, boot, or download. I was able to make it to the TWRP rom image install one time but, I didnt have any roms on an sdcard. By the time I got a rom loaded on a card the phone rebooted.
Any ideas on what is so messed up on this phone or how I can get the correct TWRP or CWM installed correctly?
Getting Close
I have TWRP 2.8.6.0 installed and kind of working. I have a T999TMBEMJC rom installed that kind of works. Random reboots though. I do get errors in recovery about writing to /data even after formatting in TWRP. I even installed Docs PIT.
Im starting to wonder if it isn't because I replaced the glass with a cheap replacement that floats over the display? It seems to be working a little better if I don't touch it.
Update: I think its the power button. If I so much as brush it (no click), the screen goes off or it tries to reboot. Only took 56 recovery installs and 6 sdcard debrick recovers.
Any ideas on how to fix the power button?
Update 2: Got it. It was the small piece of felt between the power button and the frame. Removed that and it works fine now. TWRP, Download and custom Rom all work fine now.
Hope this might help someone else. I think this can be closed. Thanks.
I have Sprint Galaxy Note 4 which is behaving very weird. When I touch with finger the response is not where the finger is but at some other location.
If I use Pen everything is perfect. I have tried resetting is, Had screen protector which removed. but no Luck
Any help will be appreciated.
Sounds like you need to recalibrate the touch screen. Flash the wrong recovery, maybe? Either way, recalibrate it by downloading following the sequence below. If it fails the first time, you may need to Odin the stock tar and redo the steps at earliest opportunity.
Open dialer type *#2663# and then tap TSP FW update.
Sent from my SM-N920P using Tapatalk
Im getting the same issue... but the dialer codes dont work...
I flashed the Emotion 7.1 update and now my screen is all messed up. It wont select unless I press in odd areas of the screen. Its like the screen calibration is way off. I think I might have installed the wrong TWRP. I have installed the correct one now, but cant seem to fix the screen issue. Can anyone help?
Tenacious--M said:
Im getting the same issue... but the dialer codes dont work...
I flashed the Emotion 7.1 update and now my screen is all messed up. It wont select unless I press in odd areas of the screen. Its like the screen calibration is way off. I think I might have installed the wrong TWRP. I have installed the correct one now, but cant seem to fix the screen issue. Can anyone help?
Click to expand...
Click to collapse
The dialer code works with stock or stock-ish ROMs. You'll have to revert to stock with Odin to fix it.
Edit: you can find the Sprint Note 4 stock tars here:
https://forum.xda-developers.com/showthread.php?p=63868221
You may have to wipe internal memory in order to get stock tar to boot after being on CM. Not sure but it could cause a boot loop booting after Odin flash.
The latest TWRP for Note 4 is here:
https://dl.twrp.me/trltespr/twrp-3.0.2-0-trltespr.img.tar
Flash that in Odin in AP slot to get back to custom ROM or CM. Don't forget to uncheck auto reboot and pull battery, wait at least and boot directly into recovery to get TWRP to stick on subsequent boots to recovery.
Sent from my SM-N920P using Tapatalk
Samep... you saved my life, thank you! I have been at this all day and could have been a week. The piece I was missing was a stock-ish rom to get to the menu. The post you made was so helpful, saved me countless hours. Once I had the Sprint stock rom tar installed via Odin, the code worked and the menu popped up. Back in action...Thank you, thank you!