Long story short I think I bricked my S7.
Background story was that I was trying to flash the Nougat update via Odin. I downloaded the correct file for my 930V and double confirmed this was the correct file. 100% on this.
I followed directions from Sam Mobile and the process began normally. Seemed like it was going fine/nothing going wrong. Near the end of the first rectangle box loading up in the color green, it said 'PASS' and then suddenly my phone went from the blue downloading "don't turn off target" screen to rapidly bootlooping the Samsung Galaxy S7 screen and vibrating quickly as well--it wouldn't go past that. I tried to put it into recovery and it simply kept flashing "Recovery rebooting" in small blue letters up in the top left in the same rapidness as the Galaxy S7 logo was going earlier. I tried to go through Odin again and nothing worked. I immediately phoned up Samsung to see what they can do and they said to send it in. My question is will they know if I did something to the phone or do they have a way to fix my phone/get me a replacement? Will they deny my request? I didn't root or modify my phone in any way except to try and flash a legal normal software. I'm crossing my fingers here...
I sent my phone in already and followed their directions.
Just got word I'm getting my phone back...so to answer my own question no, Samsung apparently cannot detect that you mess around with Odin. Thank you to myself. You're welcome.
Related
I plugged my phone in, to be greeted by a message from Kies saying an update is available, which is of course froYo. So I started the process of upgrading, and I went away, and came back about an hour later, to find my phone sitting on a blank screen, but the two capacitive lights still lit up when touched. On Kies it said 'Your phone will reboot when process is complete' or something like that, so I assume that the phone attempted to reboot but failed. I pulled the battery and tried manually booting it, and it passed the two boot up screens, but I was again left with a blank screen. I then decided to try and put it into recovery, but I am presented with the 'Downloading...Do not turn of target!!!!!!!!!!!!!' screen. Any help on how to fix this, if it is even possible, would be greatly appreciated.
I would read the guide here and reflash it using Odin.
http://forum.xda-developers.com/showthread.php?t=723596
It's really not difficult and and takes a couple of minutes.
Okay, thanks alot.
Hi All,
OK, I am both new and stuck, I have read every page in the unlocking Atrix thread and the one click root thread but I still do not know what is wrong.
I started off by running the one click root listed here, the root went fine and seemed to work, so I proceeded to install ROM Manager but when I tried to back up my phone the process failed.
I googled the error and it turned out that I did not unlock the Boot Loader, so I followed all the instructions that explained how to do it and nothing worked.
Thinking something must have gone wrong I went back to the one click root tool and unrooted my phone, I checked and everything was working and the phone seemed fine.
So then I started down the longer process of unlocking/rooting here , following the steps to the letter and here is where I come unstuck.
I have a UK carrier free phone so after downloading and installing the RSD Lite software I used the SBF_Flash file but when I selected this file the “Start” button remained greyed out.
I researched this issue and found the international flash called intl-fix-try1.sbf, this file looked like it was going to work, the start button became clickable and the process looked ok.
Once I clicked start the flashing started and percentage done went straight up to 98% in a matter of seconds, then as per the instructions the phone reboots but starts to reboot fully, the process % resets and starts from zero going up in increments of 3%, by the time the process is at 65% my phone has fully booted and is sitting at the lock screen, if I leave it there the process will go up to 100% but the status will still say "in progress" until I swipe the lock screen and then it says complete.
I was doubtful that the root had worked but just to make sure I proceeded to move the phone into Fastboot mode and go through the OEM Unlock process but once I have typed in fastbook oem unlock and hit enter the command prompt just comes up with a message waiting for device to respond and nothing more.
Please help as I am really stuck, I followed your guide to rooting my Galaxy tab 10.1 and had it sorted in minutes, my ICS rom installed and everything backed up via ROM Manager so I am not a total dummy.
Any suggestions?
Kind Regards
Chris
when you tried to flash the sbf on rsd lite did you have the phone pluged into the pc and have it put into rsd lite mode
prolly not if you still seen the lock screen
turn phone off then turn on by holding power button down and volume down
when u see fastboot word on the atrix use volume down to scroll to rsd mode then hit volume up and proceed with rsd lite and the sbf
Here might explain it little more..
http://briefmobile.com/how-to-unlock-the-atrix-4g-bootloader
That is exactly what I did, I have just done it again now . . . .
I clicked start
The console/flash starts,
The phones screen goes black,
Then the Red Motorola M appears
The flash progress jumps to 98%
Console Status says something about USB Pass through/phone rebooting
Then reboots and the Red Motorola M appears again
Then progress carries on and goes up and at 16% by now the phone is now fully in its boot process and by 26% it is at the swipe screen
I have the phone in USB debug mode and the usb connection set to mass storage. Could I be using the wrong SBF file?
Thanks
I have tried that method as well as it is uses a different sbf file called zomgunocklite.sbf when I use that file I an error saying sec_exception: febe, 35, 35 I googled that and it came up with a similar issue but it did not help.
So since my first post I have been speaking to ltdanno360 on here, I just wanted to take the time out to say a MASSIVE THANK YOU.
He has taken me through getting my phone back to a usable state and then all the way through fixing up with the latest bits and pieces.
I have taken up a good few hours of his time and I am now a very, very happy Atrix owner.
It is people like ltdanno360 that make this forum and the internet community such an amazing place. Just imagine driving home from work one day and you car breaks down on the freeway, a stranger stops and spends two hours of his day fixing your car before sending you on your way.
Things like that do not happen often in the real world but people like Danno are great examples of what humanity often misses.
Big Thanks Bro
Awesome guy, awesome forum.
Hi people. I have been running a rooted phone for a while and decided to go back to unrooted recently. I decided I would like to use the barclays app and apply the new updates that samsung rolled out recently. However when I flashed the stock firmware I found that the screen no longer worked. The phone seemed to boot up and play the samsung startup jingle but no splash logo. just a black screen. To test I decided to call it and the call came through ok and answered with the home button, speech all functional???!! Just no screen ... completely black??? Would this likely be a fault with the firmware or is it just uncanny timing with a faulty screen??? confused and wondered if anyone else has come across this before I go but a new screen. I downloaded the firmware from hotfile "I9505XXUDMH8_I9505OXXDMHA_I9505XXUDMH8_HOME"
thanks in advance
jamhot said:
Hi people. I have been running a rooted phone for a while and decided to go back to unrooted recently. I decided I would like to use the barclays app and apply the new updates that samsung rolled out recently. However when I flashed the stock firmware I found that the screen no longer worked. The phone seemed to boot up and play the samsung startup jingle but no splash logo. just a black screen. To test I decided to call it and the call came through ok and answered with the home button, speech all functional???!! Just no screen ... completely black??? Would this likely be a fault with the firmware or is it just uncanny timing with a faulty screen??? confused and wondered if anyone else has come across this before I go but a new screen. I downloaded the firmware from hotfile "I9505XXUDMH8_I9505OXXDMHA_I9505XXUDMH8_HOME"
thanks in advance
Click to expand...
Click to collapse
i would say to stay away from new firmwares at this time....you are stuck in the locked bootloader.
can you boot in recovery or odin modes and see the screen?
wipe data and cache and reflash the MH8 then do the wipe. see if that works
can not determine if it is a HW or SW issue.
if you want to use app that doesnt require root like Barcley and you are rooted, you can hide the root with some available app.
It seems I am able to get the device into download mode, although nothing comes on the screen. I just have to do the procedure blind. No matter what I do nothing comes up. It also seems I can only get the phone to read the internal memory through USB once a flash procedure has completed. It seems to force a boot up but when I try to restart manually it does nothing but vibrate and only seems to be able to put into download mode while blind. I find it very unusual that the screen should suddenly stop working the moment I try and flash the standard firmware. Getting worried now. nothing seems to work
Can anyone help here??? I have tried flashing several times. Just vibrates and does nothing. I can get it into download mode but I don't get any warning screen up. I just go through the button combo's blind and it manages to get into communication with a odin com port. I have tried doing a PIT download. What I was then finding is that the phone can bring up a recovery screen with option to reset, I reset but the phone will just be a black screen and play the samsung start jingle without the splash screen. It then seems to boot and receive notifications with a totally black screen. completely unresponsive.
If you can't see a splash screen or even recovery and download mode screens, then I'd say its a hw issue and no ROM is going to fix it, because those mentioned things are not even tied to the ROM.
Your screen has broken some how, it could be as simple as a flexi connector falling out or as bad as your screen being totally gone.
Sent from my GT-I9505 using xda app-developers app
It doesn't look like hardware problem
i am facing exactly similar situation with a 9505, i tested LCD with another of my 9505, and LCD is ok
is just happened after an Odin flash of stock firmware.
Hello. I was working on a phone, an samsung galaxy s5 (chinese version) sm-g9006v and I tried to root it in order to add playstore and more to the device.
However, I used odin and a CF-autoroot file for this device.
After that the device went in a blocked white screen with a chinese log and on top left it wrote "set warranty bit recovery" and some other text.
Waited a bit since I thought it was a phase that was required for the root process to continue but it didn't do anything for a few good minutes, however i proceded to remove the battery (since the power button wasn't helping to reset the device) and now it won't start and it won't enter in a download state to use odin to eventually flash something else onto it.
Any help is appreciated as I'm kind of desperate at this point. Thank you.
Edit: if I connect it to the pc it gets in a start-up loop i believe.
scimini said:
Hello. I was working on a phone, an samsung galaxy s5 (chinese version) sm-g9006v and I tried to root it in order to add playstore and more to the device.
However, I used odin and a CF-autoroot file for this device.
After that the device went in a blocked white screen with a chinese log and on top left it wrote "set warranty bit recovery" and some other text.
Waited a bit since I thought it was a phase that was required for the root process to continue but it didn't do anything for a few good minutes, however i proceded to remove the battery (since the power button wasn't helping to reset the device) and now it won't start and it won't enter in a download state to use odin to eventually flash something else onto it.
Any help is appreciated as I'm kind of desperate at this point. Thank you.
Edit: if I connect it to the pc it gets in a start-up loop i believe.
Click to expand...
Click to collapse
Use Samsung KIES 3 and select "Emergency Firmware Recovery" or "Firmware Upgrade and Initialization". This worked for me even after a botched recovery flash that prevented me from going into Download mode.
Hi, so, I got this phone from a friend, and he told me that the phone was working prorperly, but after someone factory resetted it, he wasn't able to set it up. Constant force close pop-ups where showing up while setting it up, and you weren't able to accept terms and conditions (button grayed out). Also, one thing I noticed. The phone got into "Factory Mode". Idk what that is, but it wouldn't let me to enable wifi or bluetooth. That little Factory mode thingy got me really confused. Also, I wanted to boot into recovery mode, and I wasn't able to do so. After turning the phone off, and doing the key combo to boot into recovery, the phone rebooted itself (very showrtly after doing the startup vibration) and after that, it seemd to get into recovery, but it stayed at the android logo with an exclamation sign and after 3 seconds it rebooted itself to system.
After that I said, "well, last thing to try is flashing stock rom again". And I did so. Using the Frija software to download the latest version of android for this phone (and using the corect CSC for this phone (CTI)). I used odin 3.12.7 (wich I knew it works because of previously using it with other phones) to flash the stock rom again. I made sure that only Auto-reboot and F.reset time were checked, and started flashing. After it finished, it got to the samsung logo, but got stuck there. Nothing happened (I left the phone there for like 30 min). I decided to hard-reboot the phone and try to factory-reset it, but after shutting it down, it started to be really hard to make the phone turn on. I had to unplug the battery and wait like 10 mins to try again, and I still wasnt able to boot into recovery mode. It just got stuck at the "Galaxy Core 2" logo.
After that first boot, the phone never got passed the "Galaxy Core 2" logo. Just stuck there. After that, things just begun to get worse. It was also hard to get the phone to get into download mode, most of the time it just stayed at a blackscreen (im not shure if the phone ever turned on, but it never vibrated) and did nothing. I decided to try other versions of odin. Tried with 3.09 and 3.04. Nothing, and after every flash, it got harder and harder to make the phone boot.
At this point, I can hardly get the phone into download mode, and if I do so, sometimes I get the odin complete write operation failed error, wich the only way that I've found to solve it is to reboot again the phone into download mode.
I know that the battery is working, I have another core 2 (same exact model) and battery is ok. At this moment I don't know what else to do. Please, help me to get this brick of a phone back to working conditions, I dont want my friend to buy a new phone just to use it to recive calls and charge it.
Some extra notes:
As i've read, sometimes this can be caused by the replacement of the digitizer/screen. This phone seems to have one or both of them replaced, since I can see glue residues on the corners of the glass, where it touches with the plastic frame.
If there is anything hardware related thing to try, I can try to open the phone. I have some experience doing so.
EDIT: As I continued reading through this forum, I found out that some people had luck with Odin3_v3.13.1_3B_PatcheD, so I decided to try it out and see. Still, nothing changed. As today, I can only use this phone to charge the battery (it dosent actually show the percentage, only the battery icon with a loading icon inside) and boot into download mode
Although, I have to say that after flashing the stock rom with that version of odin made the phone not that hard to start in download mode. I think that it could be something that got corrupted on the eMMC module and it has to repartition it all again...? Does anyone know how to do so?
Regards
Well, tried almost everithing I know. Downloaded rom again with binary nature, tried with odin version 3.12.7, 3.13.1_3b patched and 3.13.3, but nothing. Extracted the PIT file from the CSC file, did repartition, NAND wipe, and nothing changed. I have to say that its certaily easier to get the phone in download mode, but thats almost it. One thing to note, when i select the NAND wipe, it dosent seems to do anything. I mean, in odin Log screen some things appear related to NAND wiping and such, but its really fast and there are only 2 or 3 lines dedicated to that. Is that OK?
Anyway, please, any recoomendation or thing to try would be great, since this phone is now trash, it dosent matters if it starts to get worse, or even unusable (more than it is rn).
Regards