Hey guys,
I flashed Cyanide L on Friday morning with a clean install etc.. and my phone seems to have bricked itself while on the charger from Friday night into Saturday morning. I used it most of the day Friday and it seemed fine other than 1 random reboot. My phone will not boot past the Galaxy Note II screen when the phone first turns on, I can boot into recovery (Philz) but I don't see anything on the screen when I do (I get haptic feedback when I touch anywhere on the screen but I can't do anything.)
I tried for about 5 hours to use Odin in download mode and return to either 4.1.1 stock or 4.1.2 (I know using Odin to restore 4.3 will lock my bootloader which I am not interested in doing). However, Odin keeps failing when trying to write the recovery image to the phone. Does anyone have any tips or suggestions for what I could do next?
ozo012 said:
Hey guys,
I flashed Cyanide L on Friday morning with a clean install etc.. and my phone seems to have bricked itself while on the charger from Friday night into Saturday morning. I used it most of the day Friday and it seemed fine other than 1 random reboot. My phone will not boot past the Galaxy Note II screen when the phone first turns on, I can boot into recovery (Philz) but I don't see anything on the screen when I do (I get haptic feedback when I touch anywhere on the screen but I can't do anything.)
I tried for about 5 hours to use Odin in download mode and return to either 4.1.1 stock or 4.1.2 (I know using Odin to restore 4.3 will lock my bootloader which I am not interested in doing). However, Odin keeps failing when trying to write the recovery image to the phone. Does anyone have any tips or suggestions for what I could do next?
Click to expand...
Click to collapse
Here's an older post with links that might be helpful ( http://forum.xda-developers.com/showthread.php?p=57944591 ).
Make sure you're using the pit file when flashing the appropriate firmware in Odin.
Some common issues with Odin also are to make sure you're using a USB 2.0 port on your computer and use the phone's original USB cable or a good quality one if you don't have the original any longer. Also run Odin with Administrative privileges, make sure that Kies is not running in the background because it interferes with ODIN, and disable antivirus programs when running Odin.
Yeah something went wrong in Odin when I flashed the stock recovery the last time and I corrupted my EMMC as Product Name: (Blank) is showing up now.
RIP Note II it was nice knowing you.
ozo012 said:
Yeah something went wrong in Odin when I flashed the stock recovery the last time and I corrupted my EMMC as Product Name: (Blank) is showing up now.
RIP Note II it was nice knowing you.
Click to expand...
Click to collapse
Man... that sucks! I wonder if it was actually Odin, or if the EMMC chip just died. Either way, it doesn't really matter now. RIP Note 2.
Related
I installed SafeStrap 3.70 and tried to install RLS12 (on MK2). Things did not go so well. It booted to a black screen. Figured I would just ODIN back to stock and now my phone is really unhappy.
I tried flashing both of the firmwares from here (full did not work so I tried no-wipe):
http://forum.xda-developers.com/showthread.php?t=2578209&highlight=mk2
I can boot into download mode but not recovery. When I first flash a ROM via ODIN the phone will show the Samsung logo and even get to the Verizon splash screen. Problem is it will power off after a minute or so. If the phone is connected via the USB cable the charging battery screen appears. If I try to go into recovery it just powers off (verified by plugging in USB cable and getting charging screen).
One thing I have noticed is that even after flashing with Odin the Samsung custom splash screen still shows up. Usually that goes away.
I am open to any and all suggestions. My last two things to try is going through Kies Revovery. Next it to try downloading a firmware from sammobile.com.
diaftia said:
I installed SafeStrap 3.70 and tried to install RLS12 (on MK2). Things did not go so well. It booted to a black screen. Figured I would just ODIN back to stock and now my phone is really unhappy.
I tried flashing both of the firmwares from here (full did not work so I tried no-wipe):
http://forum.xda-developers.com/showthread.php?t=2578209&highlight=mk2
I can boot into download mode but not recovery. When I first flash a ROM via ODIN the phone will show the Samsung logo and even get to the Verizon splash screen. Problem is it will power off after a minute or so. If the phone is connected via the USB cable the charging battery screen appears. If I try to go into recovery it just powers off (verified by plugging in USB cable and getting charging screen).
One thing I have noticed is that even after flashing with Odin the Samsung custom splash screen still shows up. Usually that goes away.
I am open to any and all suggestions. My last two things to try is going through Kies Revovery. Next it to try downloading a firmware from sammobile.com.
Click to expand...
Click to collapse
I've seen someone else with this problem..
Think they took the battery out for like 5-10 minutes then they were able to boot into recovery then did a factory reset and cleared Cache then that either fixed it or they Odin back. Have you tried that? Sounds like you know what you're doing. I had to do that with my s4 as well after running into some issues
Edit:
Is this all on your stock slot or is hd12 on a rom slot???
Reason I ask is I had this happen to me and even after full Wipe in Odin my s4 was doing same thing as yours it sounds and mine was all on stock slot. My phone was really pissed at me.
Verizon Galaxy S4
Safestrap 3.7
HYPERDRIVE 11
Mistertac said:
I've seen someone else with this problem..
Think they took the battery out for like 5-10 minutes then they were able to boot into recovery then did a factory reset and cleared Cache then that either fixed it or they Odin back. Have you tried that? Sounds like you know what you're doing. I had to do that with my s4 as well after running into some issues
Edit:
Is this all on your stock slot or is hd12 on a rom slot???
Reason I ask is I had this happen to me and even after full Wipe in Odin my s4 was doing same thing as yours it sounds and mine was all on stock slot. My phone was really pissed at me.
Verizon Galaxy S4
Safestrap 3.7
HYPERDRIVE 11
Click to expand...
Click to collapse
Yes, this is in the stock slot. I had been running in the stock slot since RLS8(9?) without any problems but something has definitely changed.
Some good news! I went to bed at around 12:30 with Kies left running. It had stated the download process of the restore. When I checked on it this morning I had a red light on the phone which I had not had before (charging indicator). I unplugged the phone and powered it on. Low and behold I got a setup wizard. Looks like Keis does something that Odin does not. So when in doubt restore the stock image with Keis if you are stuck. BTW, when doing that I did the "Firmware Upgrade and Initialization" method. It asks for the model # and it is case sensitive for some reason. It took "SCH-I545" but was not taking "sch-i545".
diaftia said:
Yes, this is in the stock slot. I had been running in the stock slot since RLS8(9?) without any problems but something has definitely changed.
Some good news! I went to bed at around 12:30 with Kies left running. It had stated the download process of the restore. When I checked on it this morning I had a red light on the phone which I had not had before (charging indicator). I unplugged the phone and powered it on. Low and behold I got a setup wizard. Looks like Keis does something that Odin does not. So when in doubt restore the stock image with Keis if you are stuck. BTW, when doing that I did the "Firmware Upgrade and Initialization" method. It asks for the model # and it is case sensitive for some reason. It took "SCH-I545" but was not taking "sch-i545".
Click to expand...
Click to collapse
Well that's good news. Yea like I said that happened to me as well... I just didn't use kies. But looks like you're back up and running so you're good.
Verizon Galaxy S4
Safestrap 3.7
HYPERDRIVE 11
Hello All!
My first post here, even though I have long been a lurker. I hope I'm posting in the right place. If not, apologies, and Mods - please redirect me, and I shall re-post in the correct place.
Phone: SAMSUNG GALAXY S3 GT-I9300 International version
Last known installed/running OS: Official SAMSUNG JB ROM (Unsure WHICH version) after having run on CM 4.4 for a couple of weeks.
PROBLEM:
a few months after going back to stock, Phone suddenly developed issues of random reboots. These would happen at any point in time, with no predictability whatsoever. One fine day, it rebooted, and wouldn't get past the Samsung splash screen. Pulling the battery and trying to restart phone resulted in the same stuck at Samsung logo issue.
Left the phone alone for a couple of months after this as I had a spare, but finally decided to try and revive the S3.
Phone does not charge when connected to charger. At least, it shows no visible signs of it. It DOES, however, try booting itself when plugged in, but gets stuck on the first screen of ODIN Download mode, instead of the Samsung logo splash screen as it used to earlier. Also note that this screen it gets stuck on is a pixellated screen, not the clear normally seen screen when entering ODIN mode.
The Vol UP, Home and power button combo brings me to this very same screen, there is no recovery menu to be seen, as would be normally. The Vol DOWN, Home and power button combo brings me to the regular clear ODIN mode as usual.
The headings at this screen read:
ODIN MODE
PRODUCT NAME: GT-I9300
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
I have read through most posts regarding similar issues on XDA as well as other forums, and tried flashing stock firmwares (single AND multiple part ones) through ODIN, with no success. The error i always get is as in the attached screen captures.
I've tried ALL versions of ODIN, and many PIT files. All were failures.
So, is this a dead for all purposes phone, or do I still have hope since ODIN mode is still available?
I don't think USB debugging was checked before bricking, because ADB toolkits just keep waiting for phone to be detected.
All drivers are up to date and installed correctly. Kies is not installed.
Any help is welcome.
@Mohanms04: if you flash a 3part-PIT, what result views ODIN after finishing?
I have a Device here which seems to have the same or at least a similar problem, however, i got it for free from someone else to experiment with, so there is no urgent need to repeir it.
I tried flashing a pit and erasing nand, but when i start to do it, odin just gets stuck at "erasing", if i try to flash a full firmware it just hangs at "getting pit for mapping" so i assume the nand is gone for good... however, i have one more dead s3 arround that seems to have a burned cpu, probably i manage to solder over the nand or the cpu
rp158 said:
@Mohanms04: if you flash a 3part-PIT, what result views ODIN after finishing?
Click to expand...
Click to collapse
ODIN stays at "Setup Connection" without any progress. I've left it overnight a few times, just to ensure I was giving it enough time.
When the cable is pulled, it reads "there is no pit partition"
@Mohanms04: I suppose, it's hardbricked
rp158 said:
@Mohanms04: I suppose, it's hardbricked
Click to expand...
Click to collapse
Aargh.. was afraid of that. Well, guess its JTAG to try next, and then paperweight if that dont fix it.
Thanks anyways!!
Mohanms04 said:
Aargh.. was afraid of that. Well, guess its JTAG to try next, and then paperweight if that dont fix it.
Thanks anyways!!
Click to expand...
Click to collapse
Try this recovery firmware, if not the jtag is required.
http://forum.xda-developers.com/showpost.php?p=30087735
Hi all, long time browser of XDA, first time poster. Up until now, every phone I've had, I've found the answers on this forum. I recently picked up a Samsung Galaxy Mega (SGH-I527M) which was non functional due to what I believe was an interrupted OTA update. When I first turned it on it said ']image size too large!! w:1080 h:1920 display image fail secure fail: kernel' I downloaded stock 4.4.2 from the sammobile website, and flashed it through odin, this got rid of the message, but sent the phone into a bootloop, I couldnt enter recovery, couldn't boot, just download mode. I then tried to use the Kies software to recover it, which brought back the image size error again. Anything stock i try to flash from sammobile results in a bootloop, the only rom that boots is a pre rooted stock 4.2.2. However, with this rom I have no wifi, bluetooth, sound, or USB. In an attempt to fix this I flashed the modem file from a 4.4.2 pre rooted stock rom. This returned my sound and bluetooth, but i still cant enable wifi, and no computer ive tried can connect to the phone via usb. As of now, I still have no wifi or usb. The hardware is completely fine, according to the previous owner, it worked right up until the failed flash. I've been trying to figure this out for 2 days straight now, and I'm at a loss. Does anybody have any ideas what might be causing this? I very much appreciate any help with this situation
Hi..try flashing this rooted rom by @krazykipa with odin 3.09 and it is a 4.4.2 kitkat rom NE5 ..download the rom with the link that is at the bottom of that post.
Link: http://forum.xda-developers.com/showthread.php?p=56268871
Sent from my SGH-I527M using XDA Free mobile app
Thank you for your reply. I had already tried the ROM from that thread to no avail. However, I did manage to restore this phone to working order. It turns out that all of my issues stemmed from an aftermarket screen replacement. Upon searching various forums, I cam! e across one that said to unplug the screen, boot the phone, and plug it back in once the screen would have normally timed out. Lo and behold, the LED turned blue and it didnt bootloop. Upon plugging the screen back in I was presented with my lockscreen, with no touch response. That confirmed my suspicions of an aftermarket screen. Browsing the web with new leads, I came across a video explaining how to fix, flashed megafire v16 as suggested, and the phone lives again! Seems samsung doesnt like when they cant take you for more money on OEM parts
Thanks again for the reply, and may I say just how lost I'd be without XDA?
Hello everyone, i need some help recovering my verizon gs4 i545 here's the quick background.
bought it refurbed with lollipop 5.0.1 already installed. After a few jabs with kingroot i got it rooted.
All is good until i decided to unroot and install an update (don't ask why!), phone restarted after the update and is now stuck on the verizon splash screen.
I am able to get into download mode which i'm 100% is doing absolutely nothing.
I installed odin 3.09 but odin is not seeing my phone it IS seeing COM:6 port? first USB cable wouldn't show anything at all, 2nd USB cable showed the COM:6 but again Odin is not recognizing or seeing the phone. Phone is 88% charged.
My question is where am i at this point and is there hope for recovery?
Thanks in advance,
I thought Odin wasn't seeing mine and kept trying over and over. Finally I just added the tar file and let it sit. Turns out it was seeing the phone but I was not letting Odin do its thing. Long way to say, just put the file in and don't touch anything and see if it works.
fudplayers said:
I thought Odin wasn't seeing mine and kept trying over and over. Finally I just added the tar file and let it sit. Turns out it was seeing the phone but I was not letting Odin do its thing. Long way to say, just put the file in and don't touch anything and see if it works.
Click to expand...
Click to collapse
Fudplayers, thanks for the response! I was having issues finding the OC1 .tar file but i found this but it's concerning me..."I545_Downgrade_tC1.tar.md5"
i loaded into odin to observe odin behavior and going off what you said, see what odin does....
So far under ID:COM
0:9[COM3] 1:[COM8]
it's a good thing i have my S3 still.
Alright I recovered my phone via Verizon service repair, so lucky. It loaded OF1
Sent from my SCH-I545 using XDA Free mobile app
Hello everyone.
Last week my phone got an OTA update from Sprint and went to android 4.4.2 . I have a stock Samsung Galaxy Note 2 never rooted or rommed it before. After the update the phone acted weird right away. It would freeze up or restart or icons disappeared. About an hour after it shut down then went into this loop of it starts goes to the Samsung Note 2 Model splash and that was it. I would have to pull the battery to turn it off. I tried restarts about 2 dozen times yanking battery holding start button then reinserting battery same thing every time. I also tried 4 different batteries to make sure it wasn't a battery issue.I made sure to pull my sd card to make sure that wasn't an issue. Finally I figured oh well Ill just do a full factory wipe and install. It took a bit but I was able to get into the recover panel.. Its weird when I went in there it went through a whole bunch of red talking about E:failed to mount/cache no such file ...or something to that. I went ahead choose wipe data/factory reset.....This said that failed.....I tried to wipe the cache which seemed to work then tried reset again...same thing failed.. I tried powering off and do this a few times but nothing. I then went on to see if maybe odin would work.. I have odin 3.10, have my samsung drives loaded,kies is not on my machine. I found the sprint tar fil for my note 2 believe its 4.3 . I put my phone in odin dl mode...I opened odin as admin....I selected AP (in new vesion its this old versions was pda)..I went ot my unzipped tar file loaded that in...phone is shown on com4..odin says md5 completed successful so I hit start.....It sits for awhile log says something to likes of communicating..Then after about 15 minutes I get the failed sign.......Can anyone help me fix this and tell me what happened. The phone was fine until that damn ota.....Below are a few images showing the different times I mentioned....I do notice when I put my phone in odin dl mode I have 2 lines I dodnt see if I look at others images of their phone in odin dl mode... One is something about Knox Warranty Void:0 and under that AP:SVREV:A3 .........OK I dont see how to put images in here .I click the add image and it wants a link so I cant getr them from my computer...If anyone knows how Ill add them
Flash 4.3 oder 4.4 Fule via odin. But you need the 3-part firmware and the PIT. Then it works perfectly.
battlekaier said:
Flash 4.3 oder 4.4 Fule via odin. But you need the 3-part firmware and the PIT. Then it works perfectly.
Click to expand...
Click to collapse
Can you explain more Im not real sure how to do what your saying? Where do I get the files your talking of? Thanks for responding....ps just for updates I can not longer get into recovery mode only odin DL mode
Bump..anyone?