SM-G930A failed firmware update. Stuck at blue emergency recovery screen - Galaxy S6 Edge Q&A, Help & Troubleshooting

Hi all,
I am stuck. Here is my sad story.
I have an ATT S7 that I was attempting to load the S7 Tmobile image using Odin. After hitting the encryption error in odin, my searching led to the PrinceComsey version and that got around that problem. I then hit a Fail(Auth) error and tried a few other suggestions that I found. The last part I tired as ticking the "update phone bootloader" option. Odin failed again, this time, the phone was stuck in recovery menu loop. I tried to clear and restore to factory settings, but couldn't get out the loop. Finally, it stopped booting the base menu and now I get the wonderful blue screen exclamation mark that tells me I need to use Samsung's Emergency recovery. I can't even turn the device off now. The only other thing I can get it to do is to get to the download screen.
From all I have read, it seems the next step is to upload a valid stock image with Odin and that should be that. So that's where I am stuck. I have tried a couple different images, but they all fail in one way or another. I think what I need help with is figuring out which image is the right one to install. At this point I just want to get back to a working phone, so an ATT image is fine for now, but would ultimately want to get to a Tmobile image now that I have switched carries.
Any help is much appreciated!

Use smartswitch to restore stock software.
Also, try to use the right forum , you probably get more help

Oh dang... I claim temporary insanity for putting this in the S6 forum. ugh.
In any case, thanks for the response. I got it all figured out. Here are some tidbits in case it is helpful to someone in the future.
1) Yes I tried the emergency recovery using smart switch. It turns out that you need the device serial number. It also turns out that on my ATT supplied S7, there is no s/n etched on the back. And just for laughs, it isn't even printed on the original box. So if you do not have it written down and your device isn't functioning. You are SOL.
2) After several failed attempts, the magic formula was the modified Odin and the Jan'17 SM-G390T build that I found. I selected all four files for flashing and the n-th time was the charm.
3) I am now running the Tmobile build of Nougat on my ATT S7 with everything working as it should. That includes the phone using the tmobile signal booster that the ATT build couldn't find and has wifi calling available. It is exactly as I wanted.

Related

after data wipe, phone boots to black screen, rooted but no CWM recovery - confused

I've spent a couple days searching, but there doesn't appear to be a relevant enough thread to help me here, so I've resorted to asking for help, hopefully you guys can help me figure this out.
I got my girlfriend a used Telus SGH-T959D (same thing as the T-mobile version pretty well) several months back. It was on stock 2.1 and worked fine but was very laggy compared to my rooted HTC Desire on oxygen 2.3.2. So I rooted it and installed a 2.2 rom with Voodoo sound control (but no lagfix), and she's been using it this way for months now. It was better than stock but still laggy. I can't remember what rom it was but it was based on Samsuck firmware, hence why it's still laggy I guess.
For some reason, when I originally rooted it I had trouble with CWM recovery not installing, I can't even remember now what exactly was happening, but I managed to get the rom installed without a proper custom recovery, so when I go into recovery it's just the stock Samsung recovery, with no options for nandroid backup, restore, flash zip from sd card, etc. Basically I can't do anything useful in recovery.
Anyways lately, worse and worse she has been getting the Android text message to wrong recipient bug. If you aren't aware of it, it causes messages you sent to go to a different person in your text message message list. No it is not user error.
So I decided to try and data wipe. After this there is basically no launcher when it boots up. The notification pulldown is there and working, and it shows the phone has a signal and wifi is turning on and working, capacitive buttons light up when you press them, but you can't do anything except grab the pulldown.
It won't connect to USB when booted up, phone shows a message that you must close running processes first, or something like that. But I cannot flash a rom from recovery anyways, since it only brings up a stock recovery.
I can get it into download mode, if I hold my tongue just right and try several times, but not sure what to try to flash with Odin. I already downloaded an ICS Passion rom, but then reading the tutorial saw that I must first download CM7 and install that, then upgrade the bootloaders to the GB ones, then flash the ICS rom. I would really like to at least upgrade to 2.3 and something not based on Samsung fw, but the main priority is to get it working again.
Anyways, whatever you guys can suggest to try would be greatly appreciated. Thanks.
Honestly bro, everything I'm seeing in Google makes it seem like that phone is more on par with the Galaxy S Fascinate than with our Vibrant. Although on the exterior they all look so similar... I dunno, maybe check out their forums and see if you get anymore help there?
Here's the link:http://forum.xda-developers.com/forumdisplay.php?f=718
Goodluck!
The title of this thread looks similar to my problem with my Samsung Vibrant. So I would ask it here, too.
I'm not sure if I bricked my vibrant, it's still power up, only to to first screen, which has the words Vibrant (and) Samsung and stay there forever.
I first rooted my Vibrant successfully.
Then, I've followed the instructions below:
1. Download the latest version of the ROM from the original development page.
2. Transfer the downloaded zip file to the root of the internal SD card on your phone.
3. Turn off your phone and wait for complete shutdown (wait for capacitive button lights to go off).
4. Then, boot into Clockworkmod (CWM) recovery. To do so, press and hold these 3 buttons together: Volume Up, Volume Down, & the Power button till the screen turns on, then let go of the buttons. In recovery, use Volume keys to scroll up and down and power key to select an option.
5. Perform a full Wipe (this will not wipe your SD cards)
a. Wipe data / factory reset –> then Select Yes - Wipe data/Factory reset on the next screen.
b. Select “mounts and storage“, then select “format system” -> select “Yes” on next screen to confirm. Then, select “go back” to go back to the main recovery menu.
6. Now scroll to “Install zip from sdcard” and select it.
7. Select “Choose zip from sdcard”. Scroll to the file you transferred in Step 2 and select it.
8. Now confirm installation by selecting “Yes — Install **your_rom_file_name**.zip – The ROM will start installing.
9. The phone will reboot to recovery in the middle of the installation, then continue installing the ROM.
When I got to step 7, instead of running the zip file downloaded on step 1. I run the update.zip (something like that). And I couldn't get back to the CWM recovery screen anymore. Only I can boot it to the regular recovery screen, where it let you:
reboot the system
reinstall packages
delete all user data
delete cache data.
Or boot up to the screen described at the beginning of this post.
So what should/can do to fix this problem?
I think my phone is t959 (it's t-mobile Samsung Vibrant)
Thanks for the reply. As far as I thought the only similarity between this and the at t fascinate was the name fascinate. There's is the i5000 and mine is the t959d? Should this post be moved over there? I found a thread there with someone having partly. the same issue as mine not being able to install cwm but its been there for days and likely will not be replied to.
I've spent a lot of time trying to fix messed-up installs. Seems to me that if for any reason you can't rrflash the rom, or reflashing and wiping doesn't work, just Odin-ing back to JFD and going from there is the best bet.
Well I was about to go ahead and download stock JFD and try flashing that but it appears that Mega upload has been shutdown by the FBI for fraudulent activity, and Rapid share is not working either. Maybe they're too busy because of the mega Upload shutdown or they were owned by the same people and have also been shut down. So now I'm not sure where to even find files that are safe to flash.
I just spent another hour on here and Android forums, and basically all the the threads are one or two posts, with no resolution to the OP, and none of the downloads links anywhere are working. I'm pretty patient but I'm ready to give up. Does anyone want to trade a soft bricked T959D in mint condition for any old beatup HTC that works? I've had my fill of Samsung's now.
No trade sorry but if you want to donate shoot me a pm.
Before you dump it, give me some time to look into this and I'll see if I can get you up and running with some files. Sammys are way user friendly unless you aren't doing something right, then you could always go back to stock.
Hold the phone. Haha. I'll get back to you.
You too ciditin
Thanks Woodrube, I will definitely wait patiently as long as I know I'm going to be able to sort it out eventually. I'm busy with schoolwork so even though I enjoy this kind of thing I hate spending hours upon hours on it just trying to get the phone operational again.
I've been spoiled by my htc desire, it's been almost foolproof to do anything after spending a short time reading a few FAQ's and there have been no close calls. Soon I'll probably try an ICS rom once they get a bit more stable.
I will definitely do a donate if you can help me get it going with a decent rom. I would love to have lag fix on it since my girlfriend is a bit annoyed at the lag.
Since I got my first Android phone in August 2010, I've rooted and rom'd an LG Shine Plus, LG Optimus One, HTC Desire, the T959D and Galaxy S2 T989D (sold after I got it on an early renewal). I also had to fix my sisters I9000M after a failed 2.3 update operation. So I'm no expert on this, but I've got a little bit of experience messing around with stuff. Just they all require different processes, different programs to do the job, so you have to relearn it for every new phone.
The Samsung's have been the biggest pain compared to the others, but I think it's mostly because the Canadian versions are always slightly different than the Tmobile version, but besides that Samsung always has several different versions of the same.
If I get this thing up and running again I will probably check out your GPS fix thread, cause the GPS on this phone would lock on but it was way out to lunch. Like 6 streets away from us out to lunch.
I found the way to fix my problem, hopefully it'll fix yours.
I was able to restore my stock.
Here is what you have to do.
WARNING!!! THIS WILL WIPE ANY DATA ON YOUR DEVICE, IT WILL REPLACE YOUR BASEBAND, KERNEL, RECOVERY AND OS.
DOWNLOADS:
ODIN application
512 PIT file - I can't post link so pm me
T-Mobile Vibrant JFD Image – I can't post link so pm me
USB Drivers from the Samsung Galaxy S – 32 Bit Windows Download \ 64 Bit Windows Download (again I can't post link, yet)
INSTRUCTIONS:
1. Turn off your phone (remove battery, and usb cable to pc).
2. Plug usb cable to your phone (this is just for easy to connect to the PC in the next step), do NOT connect it to your pc just yet.
3. Get your phone into DOWNLOAD mode by holding the Volume Up, Volume down, and plug your usb cable to your PC. A yellow digging Android sign should be on the screen of your phone. This may take a few tries to get it right.
3. Launch ODIN.The third box dow from the top-left box should then say a COM port (the box under the top-left box should be yellow).
4. In ODIN, load each file with its corresponding field:
___a. Click PIT and select *.pit file extracting from the 512 PIT file above.
___b. Click PDA and select the *.tar, stock JFD file.
5. Don’t check anything else, the other two boxes should be checked by default (Auto Reboot and Reset Time)
6. Hit “start.” Be patient for a couple minutes! (The bar under the top left box should show the progress, and on you phone, too)
7. You should have your Vibrant back in with stock configuration.
Good luck!
NOTE: COM3 worked fine for me. COM should not matter as long as you are using the correct drivers.
350Rocket said:
I will definitely do a donate if you can help me get it going with a decent rom. I would love to have lag fix on it since my girlfriend is a bit annoyed at the lag.
Click to expand...
Click to collapse
Ok. I wasn't soliciting for a monetary donation, I was just going off that you wanted to trade. I can't trade but if you ever want to donate your phone then just PM me.
I have to agree with kawika that everything I have read has been that your model number is for the Fascinate. Easy tip off would be; does your phone have a sim card? It is probably a CDMA phone with no sim slot. I suggest getting the files you need from the Fascinate forums as I am almost positive that the T959 files will not work on the T959d. Since you have modded a I-9000m you know that they are slightly different than the I-9000. Same thing goes with this circumstance.
Good luck and sorry that there wasn't more I could do but it is just a different phone.
@Citidin - Good to see you got yours solved. If you have questions, please ask (in the correct thread for your question a this one will probably be closed out).
It definitely has a sim card and it's HSPA, I pulled the Sim card out and put it in my HTC Desire for her to use, and put my SIM card in this crappy little LG Optimus One that's too small for me to type on. So I guarantee it has a sim card and is nothing like the Verizon phones which will not work on any of the Canadian carriers AFAIK. I think nobody understands what the phone is, and that's why almost every thread with a problem like this ends in 0 replies. I think from now on I will stay away from Samsung's abortion phones that they sell in Canada. Or at least I will research community support before getting one.
Ours is called the Fascinate, but its completely different model # than theirs, it is the T959D. Just like how the new Telus galaxy S2x is the T989D, same phone as the T mobile T989_.
For some reason there seems to be a few posts in the Fascinate section, for Telus only, I think that only started because of confusion about what the phone was, but the phone has nothing in common with the Verizon CDMA version. Actually I think if you look up, just about every phone that Telus or Bell (same network basically) gets, is a phone that T mobile got first. HTC Amaze being another one. HTC Desire Z is the same as the Tmobile G2.
Sorry I misunderstood you about donating the phone itself. My last effort will be the JFD file that Citidin sent me a link to. Hopefully that gets it going. If not I will stash it away until I have extra time to try again.
Well once I got the JFD file downloaded and put phone in download mode, turned on Odin, realized the PC recognizes the device attached and being malfunctioned, so I cannot flash with Odin.
I tried Heimdall which I downloaded yesterday, but the program won't load as it says I'm missing a DLL file.
I tried Android flasher which I downloaded who knows when, and tried to just install a recovery image with it, but it gets stuck while pushing recovery image and the program locks up.
I decided to try my girlfriends Laptop instead of mine after maybe 40 failed attempts to get Odin to communicate on mine, and to my surprise it recognized it right away. I transferred my files, with the JFD to this computer and then flashed with Odin. It took about 2 minutes and it was up and running. I checked about phone and it said 2.3.3 firmware. Really confused I looked back at odin and realized I flashed the I9000M stock 2.3.3 firmware (KG3) that I flashed on my sisters phone back around xmas. I forgot I did that on this laptop.
Anyways it is working as it should except for the home button not working (which I had already read about in a thread about using I9000M or Vibrant roms on the T959D).
While it is unfortunately stock again, the 2.3.3 should fix the original problem of sending to texts to the wrong recipient, and it also seems a lot less laggy. I think I'll just let her try it as is and hope she is happy.
If you use the JFD file from the link I sent you, it should be the stock Tmobile Vibrant.
Similar problem
Sorry dont mean to hijack your thread but I think I am having a similar problem - posted in the wrong spot before so hopefully I am ok here...
Have a Vibrant and some how got crossed up on it.
I have been able to use Odin to update the phone, however after it says its done, it does a reboot as it supposed to, shows the samsung screen then just shuts down.
After about a hundred tries, someone pointed me to Eugene's no brick. I tried that and it will fix it so it will boot and go into recovery, but I can't seem to do much once I get there. My only options are to update, wide data and wipe cache. Can't get to the point where I can load an update onto the unit.
I tried wide data and reset, then reboot. It shows the samsung vibrant logo, then the splash screen, then the big S and then screen goes black and the cap buttons stay lit.
If I try to go back and load the stock pit and jfd file, it just goes back to not booting at all and shutting down after the logo
I cant seem to get it into recovery unless I do Eugene's fix
In one of my earlier attempts, I did check to repartition as direct in one of the other threads - been chasing this a while now!
Edit: It was originally a bell phone - does this matter?
If it was a Bell phone than it should be the I9000M. It sounds like your problem is a bit different than mine was. I was able to get into recovery mode and download mode just fine. I just didn't know which files to flash with.
I intended to flash the JFD that citidin sent me, but I accidentally use the KJ3 (latest I9000M 2.3.3 firmware). The I9000 and Vibrant roms are compatible with the T959D Telus Fascinate though, only problem being no home or search button.
It sounds like the Eugene thing (whatever that is, I'm not familiar) gets you into stock recovery. Like my original issue, you cannot flash or mount the sd card, or much of anything with the stock recovery.
Do you know that the file your flashing is compatible with your phone (the I9000M I assume)? More info that would probably help, is what firmware did you have on it before, was it JFD? What update did you try on it? Bootloader version - there are gingerbread bootloaders, and froyo bootloaders I think?
Have you tried different files other than the one that doesn't seem to boot up for you? I think most of the tutorials I've looked at, said not to check repartition. When i finally got this T959D working with the I9000 rom I did not check repartition and did not select a pit file, just the PDA, phone, CSC.
Yes it is a I9000M - I was trying to load the JFD tar file along with the 512 pit file. I followed a thread in the I9000 section and loaded a JPD tar file onto it, now it shows up as a I9000B - maybe I should stop
I can now get into recovery and or download (i think the steps are differant than hold both volume buttons - mine is holding the volume one way for recovery and the other way for download, along with home and power)
Wondering if I am in this bind because it isnt really what most are calling a Vibrant - maybe under Bell it is something else.
Bootloader? didn't know I had to do anything there
I just picked up the phone used from someone - I assumed it was stock and didn't do a good check to see what was on it.
I9000m is not the Vibrate but rather the Bell version of the Captivate. There is a dev section for the I9000m in the I9000 group.
I would definately stop what you are doing and read over there.
******
Also 350 you can re-map your keys to work but I am mobile now and cant search it for you. Reason being that the. Vibrant keys are laid out differently in, ahh can't think right niece where they are, but it is fixable. Just search key remap or remapping.
Thanks very much for the help - have to wonder why they cant call them the same names regardless of where they are sold - guess thats why they get the big bucks

[Q] Samsung S4 I9502 root / flash failed - NEED HELP

Hey Guys,
I tried to root my Samsung S4 GT-I9502 (OS Android 4.3), for that I found this website:
http://marrkdaviid.com/2013/08/fix-caller-id-install-google-play-on-the-galaxy-s4-i9502/
But it failed (more information below) and I had the following error message and no wifi.
I am able to put the device into download mode, though I keep getting this error message when I try flashing the device in Odin.
(here someone with a similar problem: http://androidforums.com/international-galaxy-s4-all-things-root/768632-sos-cannot-open-gt-i9502-after-failed-boot.html)
"Complete(Write) operation failed."
When attempting to flash the device, it quickly goes through boot.img, recovery.img and system.img (when it should take longer for each step, and you should see the little green progress bar move), before failing. Does this mean that Odin is having issues writing to the device?
I live in China and I just bought the phone, I needed 5 days to download the necessary files, because most download pages are blocked in China. So I am loosing my last nerve right now.
I am pretty confident that I have the correct Samsung drivers installed. I don’t have Samsung Kies installed. I have even tried using a different computer (Laptops), and two different ROMs.
I have tried flashing the below ROMs:
I9502ZNUCMG2_I9502CHUCMG2_I9502ZNUCMG2_HOME.tar.md5
I9502ZNUEMK3_I9502CHUEMK3_I9502ZNUEMK3_SVA.tar.md5
Someone with a the same problem tried the 'Firmware upgrade and initialization' option in Samsung Kies, but it didn’t work, so I didn’t try. (Here the link: http://forum.xda-developers.com/showthread.php?t=2382979)
Instead I tried a recovery. I used Odin 3.07 and the following file:
i9502-cwm-recovery.tar.md5
I got my phone back to work for a while, I reset the phone, just in case. But know I can’t switch the Wifi on and the phone wants to Reboot.
So I allowed the phone to Reboot, I clicked on “reboot system now” and then on “Yes – (I forgot what was written behind the Yes, but I didn’t just click on the normal Yes, I clicked on the Yes - …)
The problem here: The Phone changed to a China Unicom Screen and stayed like that. After 5 h I took the battery out, but I couldn’t restart the phone.
So I did an cwm recovery and know I am afraid to reboot. The Wifi is not working and I can’t find any information about how to fix it.
So please help me. Do I reboot? Can I already install SVA ROM, although I couldn’t flash the Stock Firmware? Do I send the phone back and give up?
Please let me know if you need any other information to be able to help me.
PS: This is the first time that I flash a smart phone. And although I already spent several days now, searching the internet for how-to-dos, tips & tricks, guidelines, Q&As and god knows what, I still do not fully understand what exactly I am doing here. Hence, I would be very happy to receive somewhat easy understandable answers.
Thank you so much for your help!
Anna

Bricked i545 - "Device memory damaged"

This is my first post to a forum, so please bear with me...
So a few days ago, a friend of mine got a Verizon Samsung Galaxy S4 from someone, for free. He got it for free because the screen's glass is cracked a bit, and the phone is bricked; the previous owner didn't know what to do with it. I decided I would try to fix it, because if I do, I might be able to buy it off him and give it to my little sister, who currently has a dying iPhone 5C.
When I turn on the phone, it boots, showing the samsung logo, showing the red Verizon screen, and playing the boot tune. Then, just when you'd expect it to go to the OS, it shows a screen which at the top reads "Device memory damaged". Below that, it says "The data partition has been corrupted. You need to reset your phone to factory defaults. This will erase all your data." And below that is a button, which says "RESET PHONE". Tapping on it does nothing.
I have worked with android phones before (rooting, ROMs, locked bootloaders, bricked phones; even all these things on a Galaxy Gear smartwatch), and I know what the data partition is. I remembered that the recovery on samsung phones have an option to wipe the data partition. So I tried to access the recovery menu by holding Power, Home, and Vol+ when the phone is off. It doesn't work either . It shows the Andy robot laying on its back with a door open on its belly, with a warning icon popping out. So the recovery is dead...
I thought I could try to fix the recovery by flashing it with Odin :fingers-crossed:; Didn't work. It is blocked because the phone can't verify version . Then, after a little more research, I realized I might be able to fix the recovery by flashing a whole stock ROM. I don't know what firmware the phone is running, because I can't ask the previous owner. So I tried a few KitKat ones, and they were all rejected by the phone. Then I booted the phone back up, and I realized the RESET PHONE button acted like it was part of a Lollipop UI (There is a darker circle that extends from the part of the button where you tap). So I went back into download mode and tried to flash the 2 OTA versions of Lollipop (OC1 and OF1). The error this time was "SW REV. CHECK FAIL : fused : 8 , Binary : 6". This may or may not be the error I got before with the KitKat ROMs. I don't remember, and I'm not at my desktop to try the old ROMs.
After looking up this error, I found no exact results, but there were ones with a similar error. People said that it means a ROM is being flashed that is too old to pass the downgrade prevention system. I've been trying to flash what seems to be the latest firmware revision for this phone (OF1). Any ideas? Are the OSs I'm trying to flash somehow too new for the phone (even though I've tried all of the stock Lollipop ROMs. Should I give the phone back to my friend and tell him it's dead?
Thanks in advance!
I can't post images because I haven't posted here (or on any forum, for that matter) before.
Well, it seems really bad but you can try Samsung Smart Switch or Verizon Wireless Software Upgrade Assistant to repair the phone, else way JTag it's another option
Fuse 8 is OF1
Matthew M. said:
Fuse 8 is OF1
Click to expand...
Click to collapse
Thanks for the info. I tried flashing that version. Didn't work. I ended up taking my own broken S4 I had laying around, which had a smashed screen but a supposedly good Mainboard, and transferred the mainboard to my friend's bricked S4. Now it boots fully, and I made use of my old phone that was laying around.
BTW, do you know where or how you found out which version Fuse 8 represented? I'd like to learn more about this kind of stuff.
you probably needed to flash a lowship odin tar and repartition
Legitsu said:
you probably needed to flash a lowship odin tar and repartition
Click to expand...
Click to collapse
Sorry, what do you mean by "lowship"? I did use a PIT file to repartition, which didn't work, possibly because the OS being flashed with it wasn't being accepted...
evanzolman said:
Sorry, what do you mean by "lowship"? I did use a PIT file to repartition, which didn't work, possibly because the OS being flashed with it wasn't being accepted...
Click to expand...
Click to collapse
a normal odin tar will not fix a bad partition regardless of the .pit you need a tar that s a _user_Low_ship todo a full format odin was failing because the partitions where screwed and you weren't using the correct image
go to sammobile.com they have all the s4 all variants roms.
evanzolman said:
Thanks for the info. I tried flashing that version. Didn't work. I ended up taking my own broken S4 I had laying around, which had a smashed screen but a supposedly good Mainboard, and transferred the mainboard to my friend's bricked S4. Now it boots fully, and I made use of my old phone that was laying around.
BTW, do you know where or how you found out which version Fuse 8 represented? I'd like to learn more about this kind of stuff.
Click to expand...
Click to collapse
I am not aware of a definitive guide on the fuses. I found it by trial and error
Envoyé de mon SM-G903F en utilisant Tapatalk

i cant post on this goddamn thread my god

[SORRY FOR TITLE BUT IT DIDNT WORK FOR ME LIKE 10 TIMES]
Hi guys, quick information:
Yesterday tried to autoroot my s7 edge with chain fires autoroot. Unfortunately I heard that it wont work on latest firmware after I tried to root it.
So I just wanted to reset my whole Phone. (Accidently) Downloaded wrong Firmware, tried to install it with odin. didnt work. writing failure. Boot loop.
Left it over night (kept it loading over night). Woke up. Phone is VERY hot. Couldnt touch it. ok. removed cable. cool down.
Ok. Noticed I picked wrong one. Downloaded correct one tried again. Didn't work.
Phone wont let me hard reset (wipe cache/ Home Button + Volume Up + Power Button doesnt work)-
Can't even get to Boot Logo-
Can only get into download mode but screen goes black after a while.
Everytime I try to install the stock firmware , progress bars in odin and on phone goes to a third and then phone screen goes black and the bar doesnt move at all. if i normally try to boot it this text shows up: an error has occurred while updating the device software. use the emergency recovery function in the smart switch pc software. Cant use it because it want me to use a serial number i dont have / people on internet said its iemi number but it wont work. on videos on yt i saw people with iemi number AND serial number. in my buying papers no information about this serial number. not on my backcover of my phone.
Don't know what to do.. please anyone help
Information about Phone: SM-G935F
First remove your imei. Never post that openly on a forum or you could end up getting your device cloned.
The serial number is on the box.
You might have very well full bricked your device. Flashing the wrong firmware is a short road to a brick.
The buttons won't work due to partially written software. The wrong software at that.
Your only hope is finding the box and flashing the right software or you will have to send it in for repairs which might cost you a bit.
zelendel said:
First remove your imei. Never post that openly on a forum or you could end up getting your device cloned.
The serial number is on the box.
You might have very well full bricked your device. Flashing the wrong firmware is a short road to a brick.
The buttons won't work due to partially written software. The wrong software at that.
Your only hope is finding the box and flashing the right software or you will have to send it in for repairs which might cost you a bit.
Click to expand...
Click to collapse
sry found a topic with same problem. I guess my s7 edge is now a piece of scrap laying around. no way to fix it.
Laune_ said:
[SORRY FOR TITLE BUT IT DIDNT WORK FOR ME LIKE 10 TIMES]
Hi guys, quick information:
Yesterday tried to autoroot my s7 edge with chain fires autoroot. Unfortunately I heard that it wont work on latest firmware after I tried to root it.
So I just wanted to reset my whole Phone. (Accidently) Downloaded wrong Firmware, tried to install it with odin. didnt work. writing failure. Boot loop.
Left it over night (kept it loading over night). Woke up. Phone is VERY hot. Couldnt touch it. ok. removed cable. cool down.
Ok. Noticed I picked wrong one. Downloaded correct one tried again. Didn't work.
Phone wont let me hard reset (wipe cache/ Home Button + Volume Up + Power Button doesnt work)-
Can't even get to Boot Logo-
Can only get into download mode but screen goes black after a while.
Everytime I try to install the stock firmware , progress bars in odin and on phone goes to a third and then phone screen goes black and the bar doesnt move at all. if i normally try to boot it this text shows up: an error has occurred while updating the device software. use the emergency recovery function in the smart switch pc software. Cant use it because it want me to use a serial number i dont have / people on internet said its iemi number but it wont work. on videos on yt i saw people with iemi number AND serial number. in my buying papers no information about this serial number. not on my backcover of my phone.
Don't know what to do.. please anyone help
Information about Phone: SM-G935F
Click to expand...
Click to collapse
Okay Guys, small update: Just Made my phone work again.
Had no opportunity to install stock firmware somehow for a long time- Tried to install TWRP multiple times with odin failed alot.
Worked a few minutes ago. Why it didnt work? Download Mode stops after a while.
So TWRP installed- Now i can finally open Recovery mode. It told me that there was no os installed. true. I tried to install my os again. it worked.. soo. yea.
what do we learn?
dont root if you dont know anything about your phone :good:
sincerly,
me, the noob.

Galaxy S8+ (G955U) bootloop

I switched to samsung from apple and i stupidly tried to flash some firmware without really knowing what i was getting into. I ended up getting my phone stuck on the ATT logo and only being able to get there and download mode, cant even turn it off.
I've googled, tried everything i can find, and used all sorts of combinations to no avail. I've gotten to the point that when the phone boots up, it shows the android man and says "no command". WHen i try and go into recovery mode from there it tells me that i dont have a recovery mode.
From what i've read the best step is to flash stock rom but i cant seem to get anything to work, and although i've been messing with this for a grand total of(probably over) 24 hours, im still as lost as i was in the beginning.
I've got Prince Comsey, Odin3 V3.12.3, Odin3 V3.12.7
With firmwares that APs are
AP_G955USQS3CRE2_CL13001792_QB18008668_REV01_user_low_ship_MULTI_CERT_meta.tar.md5
AP_G955USQS5CRI4_CL13889051_QB19733321_REV01_user_low_ship_MULTI_CERT_meta.tar
AP_G955U1UEU5CRJ2_CL13889051_QB20199591_REV01_user_low_ship_MULTI_CERT_meta.tar
AP_G955USQU1AQC9_CL10895874_QB12856072_REV00_user_low_ship_MULTI_CERT_meta.tar
I've done the trick of, when starting the flash, rebooting the phone back into download and starting again. Which actually let odin flash some software(which is how i am now at the android "update" screen) but that was all it did.
Some software give me "Fail (Auth)"
Some say "complete write fail"
But none have worked.
EDIT: to add; I've eddited the configuration settings for all odins to be able to use the "UMS" option for the "USERDATA" file, which seemed to help odin but nonetheless still didnt fully help me.
Someone please help me get my phone working again. WHat else can i do?
Please also, if you have a solution or question, explain what you mean or need in detail because as i said i am very new to android

Categories

Resources