Please help, my phone randomly bricked!!!! - Galaxy S6 Q&A, Help & Troubleshooting

Ok, this sounds a bit unbelievable, even to me but here goes.....
Got my s6 sm-g920v Verizon and I rooted it with ping-pong root. Everything was going great, fully rooted, until I tried to run an app that needs root. I don't remember exactly what app it was but it wasn't anything huge like tibu because I was still running king root su instead of super su.
When I ran the app, it behaved like it WASN'T rooted, so I ran root checker and it said I DON'T have root. I decided to reboot the phone before I jump into anything yet but when it finished showing me the Samsung splash screen.....the phone screen went completely black!!!
Now the only thing I can do with the phone is boot into recovery or boot into the bootloader. But no matter what, it won't boot into the OS, even if I do a factory reset in recovery
I downloaded the t-mobile firmware and tried to flash it to the phone with Odin 3.10.6 (because even though it's a Verizon s6, I'm actually using it on t-mobile) but that flash just fails. I can't seem to find the Verizon firmware anywhere online so I can't flash that firmware in Odin!
Can anybody please help me with this problem?
Sent from my Nexus 6 using XDA Free mobile app

Ok, for anyone that had this problem i managed to figure out out myself.
I found the original Verizon firmware on the Verizon galaxy s6 forums here on xda.
I was able to successfully flash this file using Odin 3.10.6 and the phone booted up just fine when it was done.
Sent from my SM-G920V using XDA Free mobile app

Related

[Q] Unroot Verizon Galaxy S3

Hello all,
I recently rooted my Galaxy S3 only to have my Mic fail on me 2 weeks later... Very dissatisfied with my Samsung about that - even though I am loving the phone. Anyways, back to the issue. Verizon has agreed to send me a replacement and I have to send them mine back. The problem is that I know that if I send them a rooted phone they will not honor the warranty, and I am having a very hard time flashing the Verizon Stock rom.
More specifically, and to see if I am doing anything wrong.. I used ODIN to flash a custom rooted rom onto my phone which worked perfectly, and now I am once again trying to use ODIN in order to flash the stock rom which I downloaded from goo.im - the file that I am using is HOME_I535VRALF2_I535VZWALF2_618049_REV09_user_low_ship.tar.md5
Simple steps - reboot into downloading mode -> check auto-reboot and reset time on ODIN and choose the file above under PDA. All works fine, the phone reboots and I get a PASS, and yet my phone is stuck on the Verizon 4G loading intro. I think that's what they call a soft brick.
The first time this happened, I flashed a different rom and the phone loaded properly but it had the open lock symbol under Samsung which I think means that it was unlocked.. Either way, it was not the unrooted and official stock rom which is what I need on my phone in order to keep my warranty. The file that DOES work is COMBINATION_I535VRBLJ1_I535VZWBLJ1_381038_REV09_user_low_ship(NO_WIPE).tar.md5
I have followed the above steps over and over again and I always get the same result - stock doesn't work, the other one does.
Any ideas? What could the issue be?
http://forum.xda-developers.com/showthread.php?t=1762709
Personally I would try the files found in section 5 of this thread.
According to Droidstyles guide before his recent edits, if it freezes on the boot logo after a successful Odin factory flash then you're supposed to pull the battery, boot into recovery, and do a factory reset. Try that.
Sent from my SCH-I535 using xda app-developers app
SlimSnoopOS said:
According to Droidstyles guide before his recent edits, if it freezes on the boot logo after a successful Odin factory flash then you're supposed to pull the battery, boot into recovery, and do a factory reset. Try that.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Yes this works, also had this happen to me, and to boot to recovery just hold home+volume up+power button. It should work.
Sent from my SCH-I535 using xda premium
You should probably factory reset after flashing, for you don't want to be running a buggy phone.
Sent from my Nexus 7 using xda app-developers app
Use a full wipe version and this would not happen...part of the reason why i removed nowipe versions such as f2. But yes as slimsnoop said, data wipe /factory reset will fix that.
So I bought the s3 Verizon it was rooted and switched to cricket pre paid before my friend sold it to me he tried to root back to Verizon but of course he failed, is there anyway to get the phone completelyback to stock even though he switched providers cuz the phone is stuck on the activating part I'm no noobe at rooting just don't know much bout this phone
Sent from my LT28at using xda app-developers app
FhtmChandley85 said:
is there anyway to get the phone completelyback to stock even though he switched providers cuz the phone is stuck on the activating part I'm no noobe at rooting just don't know much bout this phone
Sent from my LT28at using xda app-developers app
Click to expand...
Click to collapse
Follow section 5 of Droidstyle's (the guy above you) guide. Click the link in his signature. I'm not sure about how this handles modified network configuration though, that's not something I remotely know anything about.
I thought there was a way to bypass the activation screen? On older phones, you could tap the four corners of the screen or something like that? Anyone ever heard that before?
Sent from my SCH-I535 using xda app-developers app

[Q] Bad Recovery flash? (SOLVED)

I've done some searching, finding similar things that have happened to others here, but nothing that specifically fits what I'm experiencing...
I'm hoping someone has a step-by-step that I can do to get this phone rooted properly... First, I've been on XDA for a while, Droid Eris and HTC Incredible 2, but this is the first Samsung phone I've owned... A few days ago, I tried the Casual Root method and went ahead and rooted, unlocked the bootloader (unsecure ABOOT) and loaded CWM touch as my recovery. All looked fine, but when I went in to recovery to try and backup the stock rom, it threw a ton of Not able to write/Cannot Mount errors... My phone came with the MF1 4.1.2 already running.
Since, I've tried EZ-Unlock 1.2 to check and unlock the bootloader (which it showed as "Unknown" until I clicked unlock) and I've tried installing different recoveries through EZ Recovery (TWRP 2.2.2, CWM variants, etc...). Still, no joy in getting this to work properly.
The last attempt kept the phone in Download mode until I rebooted using the Power, Vol. Down, Menu to bypass it (Not detecting ANY recovery now!?). I'm still able to get back to the original Rom (which is rooted now), but I'm concerned with bricking if I keep trying this.
So, I'm thinking now of just doing an Odin back to stock and reflashing all the original firmware so I can start over with Casual. Was wondering if anyone had any other input which might get the R/W issue fixed so I don't have to go through all the Odin stuff? Compared to HTC phones, this is quite different with Root/Flashing, so I'm a little confused with the whole process of things right now... Any help would really be appreciated! I'm looking forward to deving at some point, once I'm comfortable with the process...
Thanks,
Rich
Anyone?
Sent from my SCH-I535 using xda premium
Never mind...
Macrodroid said:
I've done some searching, finding similar things that have happened to others here, but nothing that specifically fits what I'm experiencing...
I'm hoping someone has a step-by-step that I can do to get this phone rooted properly... First, I've been on XDA for a while, Droid Eris and HTC Incredible 2, but this is the first Samsung phone I've owned... A few days ago, I tried the Casual Root method and went ahead and rooted, unlocked the bootloader (unsecure ABOOT) and loaded CWM touch as my recovery. All looked fine, but when I went in to recovery to try and backup the stock rom, it threw a ton of Not able to write/Cannot Mount errors... My phone came with the MF1 4.1.2 already running.
Since, I've tried EZ-Unlock 1.2 to check and unlock the bootloader (which it showed as "Unknown" until I clicked unlock) and I've tried installing different recoveries through EZ Recovery (TWRP 2.2.2, CWM variants, etc...). Still, no joy in getting this to work properly.
The last attempt kept the phone in Download mode until I rebooted using the Power, Vol. Down, Menu to bypass it (Not detecting ANY recovery now!?). I'm still able to get back to the original Rom (which is rooted now), but I'm concerned with bricking if I keep trying this.
So, I'm thinking now of just doing an Odin back to stock and reflashing all the original firmware so I can start over with Casual. Was wondering if anyone had any other input which might get the R/W issue fixed so I don't have to go through all the Odin stuff? Compared to HTC phones, this is quite different with Root/Flashing, so I'm a little confused with the whole process of things right now... Any help would really be appreciated! I'm looking forward to deving at some point, once I'm comfortable with the process...
Thanks,
Rich
Click to expand...
Click to collapse
If you were able to root your phone successfully, then what I would recommend what to do is download whatever image you want (for me, I downloaded twrp 2.6.3.0) and then flash it through flashify (free in play store).
If you want to get it an easier way, then use goomanager and then install open recovery script (you'll see it when you press menu). It should install the recovery automatically.
If you want clockworkmod touch, then if you want an image, use flashify to flash it. Doing either of the options will give you a working recovery.
david_hume said:
If you were able to root your phone successfully, then what I would recommend what to do is download whatever image you want (for me, I downloaded twrp 2.6.3.0) and then flash it through flashify (free in play store).
If you want to get it an easier way, then use goomanager and then install open recovery script (you'll see it when you press menu). It should install the recovery automatically.
If you want clockworkmod touch, then if you want an image, use flashify to flash it. Doing either of the options will give you a working recovery.
Click to expand...
Click to collapse
Ok, I've gotvtwrp 2.6.3.0 loaded, works... But, I cannot mount anything, backup totally fails. Any ideas? Twrp also asks for a password for some reason...
Btw, nice to see a familiar face on here! How's life treating you these days?
Sent from my SCH-I535 using xda premium
Try this. But download and use the correct and updated cwm recovery from somewhere else.
http://bestandroidtricks.com/how-to...covery-on-the-samsung-galaxy-s3-all-versions/
Sent from my SCH-I535 using xda app-developers app
stolo said:
Try this. But download and use the correct and updated cwm recovery from somewhere else.
http://bestandroidtricks.com/how-to...covery-on-the-samsung-galaxy-s3-all-versions/
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Thanks! After going through Rom Manager and letting it update CWR on it's own, I finally got everything working now! Backup of the Stock Rom is done finally and I can start flashing some Rom's to get comfortable with things... Hopefully, I can start putting out some Rom's for this device soon!! Thanks for all the help, I really appreciate it!
I have been using kitkang cm11, so far really excited and loving 4.4. I have been updating daily.
Sent from my SCH-I535 using xda app-developers app
stolo said:
I have been using kitkang cm11, so far really excited and loving 4.4. I have been updating daily.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Got wicked loaded up! So far, so good. I might try pulling a repo on cm11 sometime soon...
Sent from my SCH-I535 using xda premium

[Q] KitKat ROM Attempt gone horribly wrong!

So after seeing KitKat in action, I hunted down an Android phone eligible for a KitKat ROM. I traded my iPhone for a Verizon Samsung Galaxy S3 (i535) I got it rooted and CWM on it just fine, and the boot loader unlocked. (or so I thought) Went into recovery and did all the steps to install the ROM, got it installed, along with G-Apps and rebooted. My phone came to a screen saying
"system software not authorized by Verizon wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help."
As far as I can tell, the boot loader was not successfully unlocked. So, it's back to stock ROM via Odin, right? :laugh:
NO! All the guides I find say to download an app to reset the binary counter. How do I do that if I have no OS to boot to?
Any Ideas? Did my enticement for KitKat get the best of me?
You shouldn't need triangle away to Odin back to stock. Triangle away would be for if you were trying to take your phone back to Verizon or Samsung for warranty work and didn't want them to know it was previously rooted.
Sent from my SCH-I535 using xda app-developers app
dustin_b said:
You shouldn't need triangle away to Odin back to stock. Triangle away would be for if you were trying to take your phone back to Verizon or Samsung for warranty work and didn't want them to know it was previously rooted.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
O, thanks for clearing that up. So what's my next step to getting it back to a working phone?
jcaauwe said:
O, thanks for clearing that up. So what's my next step to getting it back to a working phone?
Click to expand...
Click to collapse
Follow the instructions in section 5 of this guide: http://forum.xda-developers.com/showthread.php?t=1762709. This will get you back to stock and unrooted. Then you will have to do the root unlock processs again.
Sent from my SCH-I535 using xda app-developers app
dustin_b said:
Follow the instructions in section 5 of this guide: http://forum.xda-developers.com/showthread.php?t=1762709. This will get you back to stock and unrooted. Then you will have to do the root unlock processs again.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
and or use the casual all in one tool and follow root, and flash insecure aboot then download Rom manager from google play and install latest CWM
I just had my s3 replaced under warranty. The new one, I used casual to root/unlock, etc. Worked great! I think I let casual install everything then flashed CM from recovery.
Sent from my SCH-I535 using xda app-developers app
jcaauwe said:
O, thanks for clearing that up. So what's my next step to getting it back to a working phone?
Click to expand...
Click to collapse
Not sure what you are trying to achieve, but once you get it back to functional and rooted, I would recommend you try out some of the wonderful custom TouchWIz ROMs on the forum here. They have most of if not more features than are in Kit Kat and there are no fully functional Kit Kat ROMSs for the S3 yet. Plus thse ROMs are stable and all your Samsung features will work properly . MORA, Hyperdrive, Synergy, and Jelly "beans" are good examples of excellent ROMs.
So I figured out what went wrong, and I'm still kicking myself for how stupid of problem it was. The reason Odin didn't want to work was because I was using the front USB ports on my system, which are not USB 2.0... I spent 6 hours trying to figure it out. So I hooked it up to a rear USB port, flashed it back to stock ROM, redid the Root, unlocked bootloader (which I didn't do in the first place) and now I'm getting Cyanogenmod on it.
Thanks everyone for the help! I hope anyone else who comes across this who where in the same boat I was can figure it out.
Sometimes it's a user-error.
Fix
jcaauwe said:
So after seeing KitKat in action, I hunted down an Android phone eligible for a KitKat ROM. I traded my iPhone for a Verizon Samsung Galaxy S3 (i535) I got it rooted and CWM on it just fine, and the boot loader unlocked. (or so I thought) Went into recovery and did all the steps to install the ROM, got it installed, along with G-Apps and rebooted. My phone came to a screen saying
"system software not authorized by Verizon wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help."
As far as I can tell, the boot loader was not successfully unlocked. So, it's back to stock ROM via Odin, right? :laugh:
NO! All the guides I find say to download an app to reset the binary counter. How do I do that if I have no OS to boot to?
Any Ideas? Did my enticement for KitKat get the best of me?
Click to expand...
Click to collapse
i know you say you are ROOT but why dont you check using ROOT CHECKER download it from the play store its gonna tell you if you are root or not. im using sspencer10 KITKAT 4.4 CM11 and is running pretty smooth why don't you try it out just download the .zip reboot into RECOVERY i preffer you use TWRP (last version) go to whipe>advanced wipe and clear, Dalvik Cache>System>Data>Cache (optional i alwayz check mark Internal storage looking for space and alwayz make a clean flash same as Format Data) make sure you backup everything first using Titatinium Backup go back, then go to Install search for your .zip file on ur SDCard or Internal Storage first select the ROM ADD MORE FILE and add the GAPPS click REBOOT SYSTEM AND ENJOY YOUR NEW KITKAT 4.4 CM11 ON YOUR SGS3.
Don't be scared of Kit Kat! Once u get ur issues figured out and get 4.4 up and running you will see its all worth it!

I Screwed up... Help Please

So... GeoHotz new root works just fine on the latest 4.4 OTA, but if you try to install TWRP you wont be able to boot.
yell at me all you want for "i should have known" but now im stuck at the secure fail kernel yellow triable screen asking me to return to verizon for assistance.
root or no root, can anyone tell me how to get back on track? (im hoping for a way to flash back to stock, but i really dont care, whatever gets me working).
in the end i'd like to get off stock and onto cyanogenmod, but that's a low priority compared to a working phone
4.4 Ota???
Did I miss something?
Assuming this is 4.3, have you looked at any of the recovery threads?? Start here:
http://forum.xda-developers.com/showthread.php?t=2639337
The boot loader hard brick thread linked in the op of the thread I posted is probably useful for you too.
Sent from my SCH-I535 using Tapatalk
I think he has a galaxy s5...
Sent from my SCH-I535 using xda app-developers app
Sorry, I have a galaxy s3 i535 and it is on 4.3 and I managed to get it to boot back up by plugging it into my computer and using jodin3 allowed me to reboot "normal". The phone seemed to for some reason be continuously stuck booting into recovery mode which didn't seem to work because I had tried to install twrp. I have now installed safestrap and everything seems fixed. I haven't tried to directly boot to recovery from a powered off state, but I was able to get booted into safestrap via the app triggering it.
Sent from my XT1060 using Tapatalk
P.s. I had seen the 4.3 threads but for some reason I thought this device was on 4.4. It's the wife's and I wasn't paying close enough attention.
Sent from my XT1060 using Tapatalk

SM-900V Hardbrick? Softbrick?

I have been looking for something similar to what is going on with my phone and I found nothing. I have been rooted for awhile (so I could use all my apps with MW) but decided to flash CM 11 and get all the bloatware off. I followed a youtube tutorial to flash a custom recovery but I seem to have been unsuccessful in unlocking my bootloader first and so I get the following error.
System software not authorized by Verizon Wireless has been found on your phone. Please turn your phone off and go to the nearest Verizon Wireless store for help.
Yeah, that's not gonna happen. Any help would be appreciated.
Can you get to download mode? If so you can try to re flash stock ROM.
Sent from my SM-N9005 using XDA Free mobile app
DeuXGod said:
Can you get to download mode? If so you can try to re flash stock ROM.
Sent from my SM-N9005 using XDA Free mobile app
Click to expand...
Click to collapse
That's exactly what I had to do, problem I had though was Odin would fail as soon as I clicked start. Then for no damn reason my (still without a successful Odin run) my phone boots up like nothing was wrong. But I shot myself in the foot cause towelroot isn't working. Boooo....at least I have a working phone. Thanks for responding.

Categories

Resources