Samsung SM-G355HN bricked after flashing - Android Q&A, Help & Troubleshooting

I had the fabric format Android (4.2.2) and my friend helped me to upgrade to Cyanogenmod by using TWRP. It didn't work so we kept it in the lastest official 4.2.2 from Samsung. After a pair of days of working perfectly, I woke up and my phone was in the "Samsung" loading screen. I kept it for a couple of minutes and nothing happened, so I pulled out the battery and put it in again, same thing happened. Tried again, then it started normally and worked fine for a few seconds, until it froze, so I repeated the battery thing. Samsung loading screen a pair of times, then it loaded again, froze... And it kept doing that
Then I tried to format it with TWRP, but the OS was deleted too (guess I selected the wrong choice?) and it's not loading anymore.
Today I've been trying to re install the firmware via Odin with a friend, but it keeps failing at the system.img file and the error is not very descriptive...
Also, sorry for the repost, nobody replied in the last one, so I just copied the message. I hope you can help me, please :/ Is it hard bricked? Should I just forget about it and get another phone? Or is there any way to install another OS?

Related

Bootloop problem :(

Hi.
I have a SGS3 i9300. It has CWM Recovery 6.0.4.6 installed, and a CM nightly from a couple of weeks back. The thing is, everything was working ok until a couple of hours ago. I needed to turn the phone off so I did (and I left it charging), and later I unplugged it and when I turned it on, it was stuck in the Samsung i9300 screen.
I tried to do a factory reset but when I try it reboots. I tried flashing a Paranoid Android ROM from 2 months ago that I had in the SD card to see if it worked, and nothing (it shows a 'installation complete' message, though). I try wiping cache, and even though it gets wiped, the problem persists.
What can I do?
Well I managed to go back to stock (the last firmware, 4.3). My idea was then rooting the phone and going back to CM. The thing is, somehow I can't root the phone. I am using CF-Root, as it has worked for me before, but I can't get root access.
Am I doing it wrong?

Weird behavior in fastboot mode

Good night everybody! my dad got this phone a while ago, after like 2 months he told me the phone was going crazy, I checked and was getting FC´s everywhere so get into recovery mode to wipe everything and there´s where problems started. I downloaded stock firmware and installed it but phone wouldn´t boot up, so my dad gave it to a guy that ``fixed it´´ but the problem came back after two weeks or so, the guy ´´fix it ´´ again but when I looked into the phone had no IMEI so didn´t recognized the sim card, the third time the guy got back the IMEI, that was long ago and today when I booted up the phone is having a weird behavior, sometimes gets stucked at the bootloader unlock warning, I restart it and after a couple of times starts the boot up animation but gets stucked at the M and like waving part.
I´ve tried getting into recovery mode but when I press any of those options boots to the warning bootloader. I got it to completley turn on when I pressed the recovery option; not expecting that to happened, but again some force close windows and decided to reboot it to see if would fix it but again to the same place stuck at the warning.
I´ve read many posts here im xda and outside but can´t find a solution. I tried to side load the firmware but looks like the pc doesnt recognize the phone´, when i got it boot up I connected it to the pc but didn´t recognized it, I installed the drivers and still the same.
Guess I need to get it recognized by the pc in order to try to side load a firmware. Sorry for the long post and any mistake, if someone can help to bring back to life this little fella.

Bricked i9100 after latest CM13 update

Greetings Everyone,
Yesterday i installed the last CM13 nightly via the CM updater in this phone.
But after the phone restarted, a green android and a "installing system update" appeared for a few seconds then after it went black, the screen blinks each 5 seconds or so, but nothing ever happens. I left the phone on overnight to see if something came up, but to no avail.
Furthermore, now i cannot enter recovery mode, only download mode and my computer does not recognize the phone. I tried pretty much everything, the basic guide on rooting i9100, KIES, Odin, Heimdall flashing, offering corpses to the Old Ones and nothing works.
Does anyone have any insight on what might be happening? I installed CM13 on my two phones (a z3c and a Note 4) and everything went smoothly. Now with this i9100 i was using 6.0.1 but everything went to hell after i tried this update.
Thanks in advance
I'm in a same boat
Hey Mate ....!
I'm in a same boat i have tried almost everything Odin seems worked for 30 seconds and than it shows failed. I love this perticuilar handset allot it was gifted to me by very special it was awarded to me by my last company i want to save it please help me if anyone has the solution . What exactly happen to you , Same happen to me exactly same. please update if you get solution. Thanks in Advance.
Regards
Fazal
argethalm said:
Greetings Everyone,
Yesterday i installed the last CM13 nightly via the CM updater in this phone.
But after the phone restarted, a green android and a "installing system update" appeared for a few seconds then after it went black, the screen blinks each 5 seconds or so, but nothing ever happens. I left the phone on overnight to see if something came up, but to no avail.
Furthermore, now i cannot enter recovery mode, only download mode and my computer does not recognize the phone. I tried pretty much everything, the basic guide on rooting i9100, KIES, Odin, Heimdall flashing, offering corpses to the Old Ones and nothing works.
Does anyone have any insight on what might be happening? I installed CM13 on my two phones (a z3c and a Note 4) and everything went smoothly. Now with this i9100 i was using 6.0.1 but everything went to hell after i tried this update.
Thanks in advance
Click to expand...
Click to collapse
You might find your answer here I'm not clever enough to post the link so you get it "Longhand".
Go To Forum Galaxy SII General.
Scroll to [Guide} Fix an unflashable or soft bricked GSII (i9100G/P/T/ versions included)
Have a good read through it and if you dare go for it . It's a "back to the future" sort of thing, takes you back to "jellybean" and android 4.1.2. (The route I took anyway)! Good Luck!
same problem here! please help me get my phone back :crying:
argethalm, fazallfrd, ThiagovGuerra
I had same problem - but ....... it was software bricked. Like yours.
If I repair then all of you can repair like me.
http://forum.xda-developers.com/galaxy-s2/development-derivatives/rom-cyanogenmod-13-t3223808
Everything i take from this link.
You can rebuild with patient.

Samsung SM-G355HN bricked after flashing

I had the fabric format Android (4.2.2) and my friend helped me to upgrade to Cyanogenmod by using TWRP. It didn't work so we kept it in the lastest official 4.2.2 from Samsung. After a pair of days of working perfectly, I woke up and my phone was in the "Samsung" loading screen. I kept it for a couple of minutes and nothing happened, so I pulled out the battery and put it in again, same thing happened. Tried again, then it started normally and worked fine for a few seconds, until it froze, so I repeated the battery thing. Samsung loading screen a pair of times, then it loaded again, froze... And it kept doing that
Then I tried to format it with TWRP, but the OS was deleted too (guess I selected the wrong choice?) and it's not loading anymore.
Today I've been trying to re install the firmware via Odin with a friend, but it keeps failing at the system.img file and the error is not very descriptive...

Boot Verification Fail

Hey guys, not sure if there was another thread with this issue but I couldn't find it.
Yesterday at work my phone suddenly froze and then restarted into a bootloop and this is what I did:
I pulled the battery out for a good 10 minutes and tried it back again and it was the same thing again with the bootloop.
I tried to put it in Safe Mode and it started up and then after awhile it froze again and jumped back into the bootloop and wouldn't go back into Safe Mode again.
This time I tried clearing the cache and that didn't work.
Next thing I tried was to Factory Data Reset the phone and it came up after that where I had to go through the whole setup wizard and everything like it was a new phone again. But not long after the phone was running fine it started restarting every couple minutes or if I go in What's App or something else.
I figured that something is wrong with the system itself so I downloaded the 22A update for the VS990 on my laptop (where the version 11B was currently on the phone) to try and update it and honestly that was a bad move because when I tried to flash VIA LGUP, the phone restarted during the process and now I'm getting this on at the top left corner of the logo screen then it reboots continously:
Boot verification failed!!
- cause: MISMATCH_SIG_LEN
Can anyone please help me out, love this phone so much and not looking to get a new one or change it anytime soon :crying::crying:
Are you in warranty or have insurance with extended warranty? Sounds like you'll have to contact VZW and get a replacement. Hopefully you're covered.
Sent from my VS990 using Tapatalk
I'm really not sure as I bought the phone 2nd hand from Ebay, bought it in August so probably., so would have to contact the original owner and see what he has to say. Sigh only if I could get it to stay on the logo screen at least without restarting I could try flashing it again.

Categories

Resources