Related
I am using the UCKH7 one click w/root tool.
I start download mode by holding volume up and down while plugging in USB. I click the start button but the program hangs at 'factoryfs.img'
Please help. Thanks.
AT&T galaxy s2
Deenybird said:
I am using the UCKH7 one click w/root tool.
I start download mode by holding volume up and down while plugging in USB. I click the start button but the program hangs at 'factoryfs.img'
Please help. Thanks.
AT&T galaxy s2
Click to expand...
Click to collapse
I use heimdall personally. Never had any problems with it. Do you have all the sgs2 drivers installed?
Also check md5 sums to make sure your download is ok.
Sent from my SGH-I777
I'll try heimdall. Drivers should be fine as kies is installed. Rom should be good as I've tried 2 different download sources
Make sure you install the libusb drivers for heimdall before flashing. The instructions are in the heimdall readme. Good luck
Sent from my SGH-I777
Just wanted to post that my problem is solved.
Summary: My AT&T Galaxy SII showed an error on boot (software upgrade failed. connect to kies...). Kies wouldn't even recognize the device so that route was a no go. So as everyone's recommended method of last resort, I decided to flash the device back to stock via odin. I entered download mode (volume up + volume down and plug in usb) and Odin would recognize the device, I would load the stock rom in the PDA slot and hit start and it would begin normally, but it would always fail after a few seconds on 'NAND write start', or 'factoryfs.img'. So I got a 1 click download solution using odin for reverting my phone back to stock. Same thing, it would recognize the phone, but stall out and fail. I also tried flashing clockworkmod via odin but and same problem. People recommended I try heimdall. It would recognize my device, and then fail after 'kernel 100%'.
I tried both programs on 3 different computers, and must have tried 12 different USB slots amongst all of them. I'm fairly handy with this stuff and I worked for hours on it.
xtra info: I had successfully used odin on my computer to flash a kernel just a week ago so I know my stock usb cable was working etc...
Resolution: So I hung my head and drove to the ATT store. After pressing a few buttons on the device and not getting anywhere they sent me to a nearby Device Support Center. I told the girl at the counter that my phone booted to this error screen and that connecting it to Kies did nothing. She asked if it was ok that in the case that she couldn't fix it she would offer me a replacement. I said that was fine and after 10 minutes in the back room she came out with a replacement (free of charge).
Well that was the good news. For the bad news, unfortunately I still don't know how to fix the problem I had, and don't really know how to avoid it in the future. I thought phone's could only get truly bricked if you messed with PIT files and such. There didn't seem to be anything more I could do than flash with odin or heimdall as those were already last resorts. I know I had the right files, the right drivers, and working usb. No matter how crazy I got with my iphone, a full restore was only a click away by plugging in to iTunes. Somehow I messed up my phone so bad that even the device support center couldn't fix it....? Shouldn't have had to be like that.
Thank yous: Thanks to ATT for having a walk-in store and for so easily offering up a replacement. Thanks to the many people on the web who offered remedies.
tl;dr - phone broke, att replaced, still a mystery
Here is the problem:
My phone is stuck on the screen you see immediately after pressing the power button, which has a big "Vibrant" and a smaller "Samsung" both white on black. Whatever I do, it won't get past that.
Here is what happened:
- I had Eclair on it for a long while, and updated to Froyo via Kies, also a long while ago. Then, tired of bad performances, I followed a tutorial to install ICS on it. It worked fine for a month and I was very pleased of the newly gained performances. However this week, (while I was on vacation away from my computer and even internet in fact) it started giving me messages saying something about "Memory low, close some applications" (paraphrasing), even thought my memory indicator said that I was using around 160 MB, which should not be that bad. Then, after a couple of hours like that, applications started to crash (because of low memory I assume). I killed applications not that useful, but it did not change the message. Then, the core application also started to crash, whatever I did. I rebooted several times to get it to start fresh, but as soon as I booted, I got the low memory message and the core crashing. At one point, it would get stuck on the ICS 3D flying boot scene, and not past that.
- So, I rebooted in recovery mode and tried to see if I had an option to just restore part of the ROM so I could use my phone anew. I wanted to avoid restoring it completely since I did not have the information about my APN (I have the T-Mobile Vibrant, but I live in Canada and I'm on Videotron's network), and performances before ICS where really bad (lagging, freezing, name it). Also, I figured it was only a booting problem, so (biggest mistake is here I believe) I tried to restore the boot only. I found somewhere in the advanced options of Clockwork an option to restore parts of the backed-up ROM. So I did it, but I got an error saying something about the checksum I think. There I realized that I was trying to restore an Eclair boot backup to an ICS ROM, so the checksum error probably came from that. I try it a second time... same result. Then, when I rebooted it stopped at the Vibrant screen I described above.
What I tried to resolve it:
- Tried to go back to recovery mode by holding the three buttons as usual. Cannot get in. The only thing that "works" is that if I hold the power button for 6-8 second, it will reboot. And get stuck at the same place.
- Search intensively on the web to see if anyone had the same kind of issue. Saw a lot of the "Exclamation mark bricked" type, resolved by going in recovery mode. Not useful to me.
- Tried to connect it to my computer and see where I could go from there. I am unable to mount the device. If the phone is powered down, as soon as I connect it, it starts to boot (and get stuck you know where). Windows does not recognizes the device, and gives me the message "This device cannot start. (Code 10)". I tried to use the drivers from ADB and those from Kies with the same results.
- I tried to install Android Debug Bridge, but without the phone mounted, it doesn't work.
- I tried to see if Odin would detect it, with the same results
- I tried to pray, but there is no answer there yet. :crying:
So here I am, with the following things still untried:
- I would try the "resistor" way of booting in download mode it that could help. However, I don't have soldering iron, don't know how to solder and don't have the parts required, so that would take me a lot of time just the try this option, without any clue that I would resolve my problem with this. I am willing to go that way if I am pretty sure it will work
- I haven't tried using the Riff Box, and I have no idea what it is and where it would get me. I would not even know where to get access to that.
On a final note, this is my only phone in the house, and to make the matter worse, I changed providers with this phone, so my older cell phones don't work with Videotron's SIM card... I would rather have the issue resolved fast if possible, because otherwise, I'll have to buy a new phone. Let's say that I would have better uses for that cash, so I hope it does not come to that.
So that concludes my sad story for today.
Any clues welcome. If the answer is "get a new phone", I would rather do it that trying stuff for two weeks and having to buy a new phone anyway.
Try reinstalling the drivers and add the nexus drivers since some people report that you may need it. Then get into download mode for Odin, on my phone its both volume buttons, but now power, then keep holding while put the USB in. The pit and pda and reparation should be selected, since that's what I do.
Sent from my SGH-T959 using xda app-developers app
pbeaumont said:
- I would try the "resistor" way of booting in download mode it that could help. However, I don't have soldering iron, don't know how to solder and don't have the parts required, so that would take me a lot of time just the try this option, without any clue that I would resolve my problem with this. I am willing to go that way if I am pretty sure it will work.
Click to expand...
Click to collapse
This method should work for you, what your talking about is called a "USB Jig". You can buy one for around $5 online, I would recommend www.mobiletechvideos.com to buy from. Before you buy the jig I would try booting into download mode with the gingerbread button combos just in case you somehow installed them. Download mode is volume + and power button. Recovery is volume - and power.
Sent from my SGH-T959 using Tapatalk
iKoolkid said:
Try reinstalling the drivers and add the nexus drivers since some people report that you may need it. Then get into download mode for Odin, on my phone its both volume buttons, but now power, then keep holding while put the USB in.
Click to expand...
Click to collapse
I uninstalled and reinstalled the drivers several times, to no effect. In fact, whatever driver there is, it does not matter since Windows always give the message about device not able to start. So I just can't use Odin.
iTz KeeFy said:
This method should work for you, what your talking about is called a "USB Jig". Before you buy the jig I would try booting into download mode with the gingerbread button combos just in case you somehow installed them. Download mode is volume + and power button. Recovery is volume - and power.
Click to expand...
Click to collapse
I just tried the gingerbread combo buttons, but no more results. I will try to get a Jig assembled asap, it would still be faster than ordering it and waiting 10 days to get it. I'll let you know how it goes.
I went and made myself an USB Jig and tada!, it worked!
So I'll now reinstall something with Odin and report a last and final time to confirm everything went right.
Many thanks guys!
Still no joy, I now only get the following message while connection the phone to the computer "windows has stopped this device because it has reported problems. (code 43)". I tried to use the drivers from Kies, the ones from ADB (unsigned, therefore cannot install them on my Windows 7 x64).
Tried to uninstall, then reinstall. Rebooted and reinstalled, and finally tried every USB port on my computer. Always the same result. Anyone has a clue?
Will try tomorrow on the computer @ work...
pbeaumont said:
Still no joy, I now only get the following message while connection the phone to the computer "windows has stopped this device because it has reported problems. (code 43)". I tried to use the drivers from Kies, the ones from ADB (unsigned, therefore cannot install them on my Windows 7 x64).
Tried to uninstall, then reinstall. Rebooted and reinstalled, and finally tried every USB port on my computer. Always the same result. Anyone has a clue?
Will try tomorrow on the computer @ work...
Click to expand...
Click to collapse
Have you tried a different usb cable?
Sent from my SGH-T959 using Tapatalk
Tried it on a different computer, with a different USB cable. Both cables and computer used to work to connect the phone.
I am at a loss for options to try right now... Any suggestion?
Just to clarify, if Odin is up and you connect your phone to the computer, does Odin give you a com port?
sent from my magic box to yours
samsgun357 said:
Just to clarify, if Odin is up and you connect your phone to the computer, does Odin give you a com port?
sent from my magic box to yours
Click to expand...
Click to collapse
Nope, not at all. The OS never gets to the point where it detects correctly the phone and mounts it.
First thing I have to ask is do you have a stock front facing camera?
sent from my magic box to yours
samsgun357 said:
First thing I have to ask is do you have a stock front facing camera?
sent from my magic box to yours
Click to expand...
Click to collapse
^^^You learn fast my friend. I'll hit you up a bunch of thanks later on when I get off work. I've hit my limit for the day already on my PC and I can't whip out my phone while I am here.
OP, I am following this thread cause I have a spare Vibe that is doing somethings similar and not being recognized by my PC. I have actually read your OP more than a few times and tried all that you have, even sent it away to a developer friend of mine. He hasn't been able to get it to recognize yet either. Xenoism is in the same boat too. Keep trying and if you get Odin to see it, please come back here and post how. We'll do the same.
Here is another thread about it (Help please! Unique problem!!!)
samsgun357 said:
First thing I have to ask is do you have a stock front facing camera?
sent from my magic box to yours
Click to expand...
Click to collapse
No, it is a T-Mobile Vibrant, and thus has only one camera facing the back. However, I fail to see how it could be relevant...
Woodrube said:
^^^You learn fast my friend. I'll hit you up a bunch of thanks later on when I get off work. I've hit my limit for the day already on my PC and I can't whip out my phone while I am here.
OP, I am following this thread cause I have a spare Vibe that is doing somethings similar and not being recognized by my PC. I have actually read your OP more than a few times and tried all that you have, even sent it away to a developer friend of mine. He hasn't been able to get it to recognize yet either. Xenoism is in the same boat too. Keep trying and if you get Odin to see it, please come back here and post how. We'll do the same.
Here is another thread about it (Help please! Unique problem!!!)
Click to expand...
Click to collapse
Ok, thanks for that. Today, Ill go buy myself a new phone (probably SIII) since I don't seem to have much other choices. I'll still try to get this one to work and keep you posted if I get any results.
Hello, First off i am fairly new to Odin and kernels as on my actual device is a HOX (The note is my mothers). I have been trying to flash the pda.tar from http://forum.xda-developers.com/showthread.php?t=1504218 and am just getting the following error.
File analysis..
SetupConnection..
Initialzation..
Get PIT for mapping..
Firmware update start..
?
NAND Write Start!!
Complete(Write) operation failed.
All threads completed. (succeed 0 / failed 1)
I have also gotten ahold of the other pda.tar folder from galaxynoteroot.com (Or somthing like that) and it did succeed but i did not gain root. Any help is appreciated :thumbup:. This is a Telus Galaxy note (I171D) on GB.
Driver issue ???
PC antivirus issue ???
Odin copy could have an issue also ...
First ....kill the antivirus program when using Odin.
Then use a powered rear port for USB ...
And the factory cable ...
P.S.
Cable issues are common ...g
gregsarg said:
Driver issue ???
PC antivirus issue ???
Odin copy could have an issue also ...
First ....kill the antivirus program when using Odin.
Then use a powered rear port for USB ...
And the factory cable ...
P.S.
Cable issues are common ...g
Click to expand...
Click to collapse
Well I don't have anti virus in here and the drivers are installed. As for factory cable, it's a couple thousand miles away as I'm on vacation so I'm just using another line for my HOX. Also this is a mac book with windows installed (also not mine).
Sent from my HTC One XL using xda premium
Ah ...
I see 2 issues ...
The mac pc/Odin conflict ....(not always, but some odin errors exist )
Not using the factory cable ....( this is pretty much a requirement )
Dang it ....you may be hosed without that cable.
Do you have any available electronics outlets ?
If so ....a gold plated USB cable may solve the problem. But the PC environment is semi adequate ...and the cable may not help anyway .
My emergency suggestion, is to download the needed files again, and attempt a reflash.
This go around ...place the .tar files to desktop only, Odin also.
Then run Odin as administrator only.
The readout you gave shows a possible error with Odin locating the .tar from the directory , and I'm trying to side step that condition. At this point I don't know about the cable ...it's just too vague to be sure.
I'm sorry you are having trouble ...and I really am trying to solve this for you ....g
gregsarg said:
Ah ...
I see 2 issues ...
The mac pc/Odin conflict ....(not always, but some odin errors exist )
Not using the factory cable ....( this is pretty much a requirement )
Dang it ....you may be hosed without that cable.
Do you have any available electronics outlets ?
If so ....a gold plated USB cable may solve the problem. But the PC environment is semi adequate ...and the cable may not help anyway .
My emergency suggestion, is to download the needed files again, and attempt a reflash.
This go around ...place the .tar files to desktop only, Odin also.
Then run Odin as administrator only.
The readout you gave shows a possible error with Odin locating the .tar from the directory , and I'm trying to side step that condition. At this point I don't know about the cable ...it's just too vague to be sure.
I'm sorry you are having trouble ...and I really am trying to solve this for you ....g
Click to expand...
Click to collapse
Well good news My aunt has a GS3 which basicly uses the exact same cables as the Note. As for the .tar folder I will try your suggestions tommrow with my sisters mac (Currently on the the other side of the world). I might just be able to visit a Internet cafe but then administrator permissions will be a pain to get... Well thanks for helping, I will report back tommrow/tonight
Sent from my HTC One XL using xda premium
Talk to ya then....g
I don't see why the factory cable thing matters, I use other cables all the time and have never had a problem, just use a real windows machine and not a parallel and you should be fine
Its not that it has to be the factory cable, but when people are having unexplained errors you use known good cables and it eliminates things as you troubleshoot. If everything works, good. If problems, eliminate a typical problem causer, like the cable or the usb port, etc.
Not all usb cables are charging cables but you can't tell by just looking at it.
Yeah I can see that, I would just think almost any cable would work (even those $1 ebay ones work for me), the Windows parallel is the big red flag here though if you had to isolate an issue.
Alas all your tips didn't work... And now I have the gapps error so I'm now urgently looking to somehow get root or a recovery in. Also rangercaptain seems Korean Starbuck doesn't have free wifi....
Sent from my HTC One XL using xda premium
TheNightHawk223 said:
Alas all your tips didn't work... And now I have the gapps error so I'm now urgently looking to somehow get root or a recovery in. Also rangercaptain seems Korean Starbuck doesn't have free wifi....
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Okay,
please tell us your current device state:
do you have a stock recovery ?
do you have a working rom ?
We need to know where your device is, with respect to software as of today.
And if in your location, I would revert to stock until you get to a location with proper connections, wifi, etc.
If we can get you that far...
We need to flash a stock odin .tar file if possible, to get you running again...IMHO
TheNightHawk223 said:
Alas all your tips didn't work... And now I have the gapps error so I'm now urgently looking to somehow get root or a recovery in. Also rangercaptain seems Korean Starbuck doesn't have free wifi....
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Ok you're in the ROK. Who would have guessed that? What model of phone? There is a Korean, international, and North American model.
rangercaptain said:
Ok you're in the ROK. Who would have guessed that? What model of phone? There is a Korean, international, and North American model.
Click to expand...
Click to collapse
Oh I have the American model, only here on vacation, actually live at Canada.
Sent from my HTC One XL using xda premium
gregsarg said:
Okay,
please tell us your current device state:
do you have a stock recovery ?
do you have a working rom ?
We need to know where your device is, with respect to software as of today.
And if in your location, I would revert to stock until you get to a location with proper connections, wifi, etc.
If we can get you that far...
We need to flash a stock odin .tar file if possible, to get you running again...IMHO
Click to expand...
Click to collapse
Okay, I am stock on the telus RUU, I'm almost sure that I have stock recovery but as I had tried flashing cwm I'm not sure and don't know how to get into recovery (First Sammy I played with) with this phone I cannot be sure. I am on Telus gb stock.
Sent from my HTC One XL using xda premium
If your phone is working, and you cannot get a good PC environment to use, then wait until you get home, and we can continue.
Recovery is gained by powering off the device, ( no cable attached) and pressing the volume up, and down buttons together, and then pressing the power button. Once you feel a single vibration, then release the power button while holding the volume buttons until the recovery screen appears.
If you verify your recovery is stock, then we should wait...IMHO (it will say 3e recovery if stock)
If the flash of CWM is a success, then we can proceed...g
gregsarg said:
If your phone is working, and you cannot get a good PC environment to use, then wait until you get home, and we can continue.
Recovery is gained by powering off the device, ( no cable attached) and pressing the volume up, and down buttons together, and then pressing the power button. Once you feel a single vibration, then release the power button while holding the volume buttons until the recovery screen appears.
If you verify your recovery is stock, then we should wait...IMHO (it will say 3e recovery if stock)
If the flash of CWM is a success, then we can proceed...g
Click to expand...
Click to collapse
Soo sorry for wasting your time... I realized that the recovery did flash and it was my idiacy that i did not figure out how to get into fastboot/recovery with this phone... Thank you very much for your time!
Dont sweat it...
you didnt waste my time...
I'd rather spend the time up front, to avoid the potential of creating a brick later on.
If you need more help, just ask.....g
P.S.
If you are good at this point, please place the word "SOLVED" in the title of your thread.
It will steer users to the solution faster, and helps keep the threads clean.
Thank you....g
Hey all.... Long time lurker and reader here. I usually find all my answers through previous posts but I'm a little stuck here and cannot find the appropriate guide to help me out.
I have a GT-P7510 which has always been rooted and has had a few ROM lifes, so I'm no stranger to CWM and download mode, Odin Etc... (But I'm certainly no expert by any means)
Last week I tried a flash and ended up bricked. (Soft brick) I tried several times to flash back to stock with the current as well as last known good firmware from SamFiles, but ODIN would fail partially through the flash. I got the message "Can't open the specified file. (Line: 1876)", so I checked here: http://forum.xda-developers.com/showthread.php?t=1370433 But that didn't help me.... And now, my tab is not recognized in any of the laptops or desktops I plug it into. (WinXP, WinVista, Win7 -- Kies drivers all fresh from Samsung)
I can get into Download mode. I can get into recovery, (I have done a wipe/re-format Factory reset in recovery a few times now) but nothing seems to help. I'd be willing to learn how to probe around with ADB, but haven't tried for lack of a driver being recognized. I have a few Linux boxes here at the house and haven't tried them. I wouldn't know where to start if the device was recognized by them.
Any suggestions on how to get the device recognized? Or, maybe what I can do from CWM (Sideload?). or even if I get an ADB connection from one of my linux boxes, would I be able to re-flash the firmware?
Thanks in advance.
first thing is to check your cable, then your pc drivers, if u can get in to cwm, try a new cable and mount the usb from there, put in a new rom, and flash it.
hope this helps, dude. Good luck.
If you foobarred the tab by a failed flash using Odin as you described logic would dictate that it has absolutely nothing too do with pc drivers suddenly not being good if they worked before, same for pc and cable.
You need to reinstall using Odin as you say you can get into download, using a .pit file, ticking repartition, and a stock firmware file. If that works you can go on to play another day....
If you're not sue about stuff you're using, good version of Odin (not all versions flash the 7510 properly) for 7510 and drivers are here http://forum.xda-developers.com/showthread.php?t=1518895
I'll put a .pit file up here when I get to a computer and get yourself a STOCK rom from samfirmware to flash thro Odin and you should be good to go
Sent from my GT-P7510 using XDA Premium HD app
stinky73 said:
If you foobarred the tab by a failed flash using Odin as you described logic would dictate that it has absolutely nothing too do with pc drivers suddenly not being good if they worked before, same for pc and cable.
You need to reinstall using Odin as you say you can get into download, using a .pit file, ticking repartition, and a stock firmware file. If that works you can go on to play another day....
If you're not sue about stuff you're using, good version of Odin (not all versions flash the 7510 properly) for 7510 and drivers are here http://forum.xda-developers.com/showthread.php?t=1518895
I'll put a .pit file up here when I get to a computer and get yourself a STOCK rom from samfirmware to flash thro Odin and you should be good to go
Sent from my GT-P7510 using XDA Premium HD app
Click to expand...
Click to collapse
That sounds great man.... THANKS! I do have the correct Odin, and I have a clean firmware from SamFiles. But I have tried looking for a pit for the 7510 and haven't had much luck. If you could post one, I'd be forever in your debt.
Here y'are
stinky73 said:
Here y'are
Click to expand...
Click to collapse
Thank you brother! I'll report back in a day or so.
Good luck!
sent from my still superb Google I/O 7510
stinky73 said:
Good luck!
Click to expand...
Click to collapse
Back to the drawing board I guess... I have a new cable on-order. However I was able to get the driver loaded by utilizing the dreaded "Plug - Unplug" routine several times until I just got lucky.
Odin can see it as COM5, and I used your pit (Again, TY!) I tried using the "P7510XABLPL_P7510UELPL" file I got from Samsung, but Odin is locked up at this point. (See screen cap)
I'll keep beating my head against this wall
:silly:
Odin 1.85 is just about the most random version of the prog when it comes to the 7510...
Try the one I have posted below (v1.3) it has never let me down (whereas 1.85 often has done to me what it is doing to you)
Worth a try
stinky73 said:
Odin 1.85 is just about the most random version of the prog when it comes to the 7510...
Try the one I have posted below (v1.3) it has never let me down (whereas 1.85 often has done to me what it is doing to you)
Worth a try
Click to expand...
Click to collapse
Yes. Sorry I forgot to mention that.
I saw your other post and did grab that 1.3 version. However, When I get the drivers loaded (When windows "sees" the tablet after plugging and unplugging numerous times) It will show up as COM3 or COM5 in any version of odin Except 1.3.
I tried various versions of Odin and when they all see the com port, 1.3 does not. Truly bizarre to me.... With 1.85 and or 1.7 I was successful in just loading the pit file, but if I try to load a PDA, it just freezes.
I installed Android SDK and started playing with ADB yesterday. I haven't had much success in addressing the Tablet. Also, I cannot get into recovery any more. It appears that the tablet is stuck in download mode, as if it's in a loop. ('the device states that it's downloading even after a reboot with no cable attached.)
My new cables will be here in a couple of days. Until then, I'm letting the battery die completely and will try again with the new cables.
P-tek said:
Yes. Sorry I forgot to mention that.
I saw your other post and did grab that 1.3 version. However, When I get the drivers loaded (When windows "sees" the tablet after plugging and unplugging numerous times) It will show up as COM3 or COM5 in any version of odin Except 1.3.
I tried various versions of Odin and when they all see the com port, 1.3 does not. Truly bizarre to me.... With 1.85 and or 1.7 I was successful in just loading the pit file, but if I try to load a PDA, it just freezes.
I installed Android SDK and started playing with ADB yesterday. I haven't had much success in addressing the Tablet. Also, I cannot get into recovery any more. It appears that the tablet is stuck in download mode, as if it's in a loop. ('the device states that it's downloading even after a reboot with no cable attached.)
My new cables will be here in a couple of days. Until then, I'm letting the battery die completely and will try again with the new cables.
Click to expand...
Click to collapse
That's an odd one for the download reboot.... As normally you should get choice of recovery or download as first step... Would tend to signal a failed download
I've often seen people say here "have you tried a different computer?" and scoffed a bit at that but maybe in your case...
However to be scientific you should only change one variable at a time so as to know where the result comes from, so start with the cable and we can see where you go from there
sent from my still superb Google I/O 7510 (xda hd)
Victorious
stinky73 said:
That's an odd one for the download reboot.... As normally you should get choice of recovery or download as first step... Would tend to signal a failed download
I've often seen people say here "have you tried a different computer?" and scoffed a bit at that but maybe in your case...
However to be scientific you should only change one variable at a time so as to know where the result comes from, so start with the cable and we can see where you go from there
sent from my still superb Google I/O 7510 (xda hd)
Click to expand...
Click to collapse
Thank you again for all your help!
My new cables arrived and appeared to be at the center of the issue. Once plugged in, the drivers properly loaded and I was successful with Odin. I used the pit you gave me for a re-partition, and the UELPL PDA from Samfiles.
It was initially stuck in a boot loop after the successful flash, but I was able to reboot to recovery, F/R, wipe and clean it up and now it's ALIVE! :victory:
Yeeee. Haaaaah!!!!
sent from my still superb Google I/O 7510 (xda hd)
My Verizon Wireless Galaxy S7 fails to boot and bootloops even after flashing the correct stock firmware using Odin3, and when trying to use the Verizon Wireless Software Upgrade Assistant, the first error shows up as 'DVIF!!' and the second being 'Unsupport dev_type.' The phone was working perfectly fine with no signs of an issue up until some random point about a week ago where it started to bootloop, showing the splash screen, turning off, restarting with the vibration, splash screen, and repeat. The phone ONLY boots into Odin mode, and i've only gotten it into Maintenance Boot mode once on accident. Which did nothing to help.
Some more info:
Model #: SM-G930V
Hardware Revision: 0.6(as read by the OS settings before it bricked)
CPU: Snapdragon
CSC: VZW
Some more issues i've encountered while trying to rig it back together:
When draining the battery to 0 and plugging it in, No battery level indicator or charging light appears. The only real indication i have is when it tells me to plug the phone in, and the lightning bolt above an empty gauge, not even displaying a battery percentage. After a few seconds to a couple minutes, it will try to boot again. Which of course, ends up in a bootloop.
sometimes, when booting, the entire screen will appear "screwed-up", the colors being off or the screen being blurry and mis-matched like a jigsaw puzzle.
This phone was purchased shortly after the launch, and has not had a reset or any need of replacement components.
Before it bricked, i had done these four things:
Install Mobile Performance Meter(data app, sells your information but you get credit for it)
Install My TruConnect(the current carrier i'm on and their app, since the phone was unlocked and i didn't use verizon anymore)
Enable developer mode
Allow USB Debugging
I used to have one of these a few years ago, I still have the Samsung firmware packages many different versions - from what I recall, the device let me downgrade firmware as long as I flashed them in succession, so as long as I could find the next lower version, it would let me flash it, but if I tried to skip any firmware versions, then it would fail to flash with Odin. Why am I telling you this? Because if you say you can still get into Odin mode, you may have a shot at unbriking if you were to successfully flash the next lower version firmware than the current firmware version that you have on it presently - it's worth a shot.
I also remember it was super sensitive to using a non-samsung branded usb cable, vs a real Samsung cable. Seriously, it's no BS. ODIN would stall or fail with one cable tested good on other devices, then using original samsung cable would finish the same operation successfully. Also, sensitive to being used attached to a VM, vs connected to a real PC. I was on a Mac using a Parallels VM running ODIN in Win7, and ODIN would fail even though it would mount the USB device correctly in the Win7 VM and in ODIN - then I ran same setup connected to my Lenovo Win7 laptop, and ODIN had no problems. And of course I'm assuming you're using a version of ODIN compatible with S7.
Although I haven't touched Samsung for a while It's probably the same old routine..
Flash stock rom with odin, straight into fastboot, wipe data/factory reset, turn off, flash AGAIN the stock rom. Its IMPORTANT that you don't let it boot the OS between flashes. Reboot after the second flash and it should go into OS. If it doesn't then the nand has died, which a known Samsung thing, ESPECIALLY if it was rooted.
Artifacting on the screen (dodgy broken looking colours) is most likely a dead nand.
shivadow said:
...If it doesn't then the nand has died, which a known Samsung thing, ESPECIALLY if it was rooted.
Artifacting on the screen (dodgy broken looking colours) is most likely a dead nand.
Click to expand...
Click to collapse
This is what I've been thinking from the start, a dead/corrupted internal memory NAND - But I have experienced this device and other Samsung models that display signs of NAND corruption, but after stubborn ODIN flashing using proper USB cable, the right chosen firmware version, the right USB port, and a fitting version of ODIN, I have unbricked, after repeated failed ODIN flashing attempts. I'm not saying this is your case, only that there is a chance (however small) that it could be your case. If you need to download a few different firmware versions ODIN packages, let me know in a PM.
shivadow said:
Artifacting on the screen (dodgy broken looking colours) is most likely a dead nand.
Click to expand...
Click to collapse
Typically the broken-up artifacting happens when the phone bootloops multiple times for me. Also, the vibration will keep going even after it's attempt to boot. Afterwards it tries to fix itself by restarting, which of course starts up the process again.
Now i might doubt that the NAND is dead, but i wouldn't be surprised. 7 years old, tossed and thrown in a thick rubber case as a work phone in the Home Depot, and pre-1.0 hardware revisions all point towards some problem. Surprisingly the only thing damaged is the front lens cover.
So are you able to hold vol-down or up, HOME button, or POWER btn keys and get it in ODIN mode after it restats trying to "fix itself"? Are you able to get it in ODIN mode by any means?
imonxda said:
So are you able to hold vol-down or up, HOME button, or POWER btn keys and get it in ODIN mode after it restats trying to "fix itself"? Are you able to get it in ODIN mode by any means?
Click to expand...
Click to collapse
Yes. ODIN Mode works perfectly fine with no issue, the only thing that does not work whatsoever is booting. Some smaller things do not work normally but still appear to function, at least i hope.
imonxda said:
I also remember it was super sensitive to using a non-samsung branded usb cable, vs a real Samsung cable. Seriously, it's no BS. ODIN would stall or fail with one cable tested good on other devices, then using original samsung cable would finish the same operation successfully. Also, sensitive to being used attached to a VM, vs connected to a real PC. I was on a Mac using a Parallels VM running ODIN in Win7, and ODIN would fail even though it would mount the USB device correctly in the Win7 VM and in ODIN - then I ran same setup connected to my Lenovo Win7 laptop, and ODIN had no problems. And of course I'm assuming you're using a version of ODIN compatible with S7.
Click to expand...
Click to collapse
I don't have the samsung OEM cable anymore, but i have a decent, although small cable that came with another one of my USB Devices. i've been using that one since, and for now it hasn't provided any fails related to the cable. Only downgrades and recovery using the Verizon Upgrade Assistant appear to fail on the phone's end.
ApolloFJ said:
I don't have the samsung OEM cable anymore, but i have a decent, although small cable that came with another one of my USB Devices. i've been using that one since, and for now it hasn't provided any fails related to the cable. Only downgrades and recovery using the Verizon Upgrade Assistant appear to fail on the phone's end.
Click to expand...
Click to collapse
I can't stress the importance of the cable enough. I had the same situation and I had used other cables that worked fine and showed no signs of having anything wrong, but they failed with ODIN flashing - the same cables worked fine for the S7 to do charging and MTP file transfers, the S7 would say "fast charging" when plugged in, but when used with ODIN, they would fail - untill I got a samsung cable, then ODIN flashing worked.
imonxda said:
I can't stress the importance of the cable enough. I had the same situation and I had used other cables that worked fine and showed no signs of having anything wrong, but they failed with ODIN flashing - the same cables worked fine for the S7 to do charging and MTP file transfers, the S7 would say "fast charging" when plugged in, but when used with ODIN, they would fail - untill I got a samsung cable, then ODIN flashing worked.
Click to expand...
Click to collapse
What I'm saying is, get a samsung cable, get to ODIN mode and flash a proper Samsung firmware - if it's successful, then you're good, if it fails, then you're looking at what @shivadow said, a dead NAND. But if you keep using that cable and using Verizon Upgrade Assistant, and not ODIN flash firmware through proper cable, getting the "phone failing" doesn't prove anything, - you must eliminate the possiblity of your S7 not "liking" the USB cable and eliminate the possibility that your NAND has corruption from bad previous flashing or from Verizon Upgrade Assistant doing something bad because of your USB cable.
Patched Odin 3.13.1
For those looking for a modified, modded, or patched odin that is a newer build than all the fake and renamed prince comsy 3.12.3 versions floating around. I patch recent Odin versions to offer similar functionality to the princecomsy; in that...
forum.xda-developers.com
Maybe help with Odin problems
joke19 said:
Patched Odin 3.13.1
For those looking for a modified, modded, or patched odin that is a newer build than all the fake and renamed prince comsy 3.12.3 versions floating around. I patch recent Odin versions to offer similar functionality to the princecomsy; in that...
forum.xda-developers.com
Maybe help with Odin problems
Click to expand...
Click to collapse
Wow, super cool, thanks! @ApolloFJ definitely get one of these for use with your S7, I think the 3.13.1 should work fine
imonxda said:
though I see jrkruse recommends Odin3_v3.14.1_3B_PatcheD.7z, so maybe get that instead
Click to expand...
Click to collapse
imonxda said:
Wow, super cool, thanks! @ApolloFJ definitely get one of these for use with your S7, I think the 3.13.1 should work fine
Click to expand...
Click to collapse
Currently trying it out. It passed without issue the first time, working on a second flash to be absolutely sure it works. I Should probably tick the NAND Erase and the Re-partition bits.
I'm starting to be fairly certain the NAND is dead. I've tried almost everything, even writing TWRP to it but that didn't change the recovery system whatsoever. I've even started to give up hope for it. Maybe she'll just rest on a shelf for awhile before i try again, to the same result.
EDIT: I just tried booting into ODIN Mode, and the screen appeared to be on, but no vibration and a few slightly miscolored white dots appeared on the upper-left-center of the screen, the upper-left of the screen, and the bottom to bottom-left of the screen. Are these more indications of a dead NAND? I've never seen this before except for when it does it's crazy weird screen thing, but now it's just the pixels.
EDIT 2: Now i tried completly wiping the NAND with no firmware and it still hasn't changed, splash screen still appears and it still won't boot.
Well I guess it's dead, sorry.
imonxda said:
Well I guess it's dead, sorry.
Click to expand...
Click to collapse
Is there any software/hardware you've found that'll make it boot from the SD Card? Maybe i'll have a chance to save or even give it new life that way.
ApolloFJ said:
Is there any software/hardware you've found that'll make it boot from the SD Card? Maybe i'll have a chance to save or even give it new life that way.
Click to expand...
Click to collapse
On S7 there is nothing I know of. Multirom can install/boot roms from external SD, but it only runs on a minimal number of devices, like many HTC devices and a few google devices, also a few one+ devices and some others, but not S7.
But if your NAND is corrupt, you won't be able to do anything anyway, even if you find something that can boot from external because your internal NAND memory has to be healthy enough to at least have the Samsung firmware installed and working.
You're looking at a paperweight at this stage.
If you want, you can mail it to me and I might be able to succeed to get firmware flashed on it and bring it back to life, but that's a SUPER long shot because if the NAND is too far gone, NOTHING can fix it, short of taking it apart and replacing the main board that contains the NAND chip - this is NOT fun to do at all, and not even worth it 'cause you'd have to find some cheap ebay S7 for parts only that has a Clean IMEI and poach the main board - you might as well buy a used WORKING S7, right?