Related
I apologize in advanced.
A friend handed me her vibrant and asked me to flash it so she could have the wi-fi hot spot ability.
I rooted it, then foolishly put one of the ROM's and now the phone is soft bricked... meaning I can get into recovery mode with the volume keys and power, but that's it.
I've tried to install a different rom from the external sdcard through recovery and it failed. (That is the only way I can get access a new update.zip file on the phone)
Can someone tell me exactly what to do to get a froyo rom on this phone working? I'd really really appreciate it.
P.S. I am on a mac, so I'm really looking for a solution that requires installing something from the external sd card. Is that even possible?
jameskever said:
I apologize in advanced.
A friend handed me her vibrant and asked me to flash it so she could have the wi-fi hot spot ability.
I rooted it, then foolishly put one of the ROM's and now the phone is soft bricked... meaning I can get into recovery mode with the volume keys and power, but that's it.
I've tried to install a different rom from the external sdcard through recovery and it failed. (That is the only way I can get access a new update.zip file on the phone)
Can someone tell me exactly what to do to get a froyo rom on this phone working? I'd really really appreciate it.
P.S. I am on a mac, so I'm really looking for a solution that requires installing something from the external sd card. Is that even possible?
Click to expand...
Click to collapse
Well you can go back to stock with Odin and try again...but since you're on a Mac....i think the Odin alternate is called Heimdall or something
EDIT: Found it....http://forum.xda-developers.com/showthread.php?t=834195
I'm sure it works just like Odin.....get the files needed to go back to stock here
http://forum.xda-developers.com/showthread.php?t=848737
this is good loool when can we expect to see i bricked my moms friend friends moms her sons phone
I'm glad someone is getting a kick out of this. I just downloaded Heimdall. I need to reboot and see if this can fix the problem. More to come...
I have to download something called qt which is a gig. Sucking internet from my epic at work... not going to happen today.
Note to self: NO MORE FLASHING FOR FRIENDS.
jameskever said:
I have to download something called qt which is a gig. Sucking internet from my epic at work... not going to happen today.
Note to self: NO MORE FLASHING FOR FRIENDS.
Click to expand...
Click to collapse
Thats weird... I dont even think Odin is more then 1MB, find it hard to believe that the Mac's alternate is so big. If you can find any windows machine it would be very easy to direct you on how to get her phone back up and running.
QT, which seems to be an environment like Java, is nearly a gig, and is necessary to run Heimdall on my mac.
The instructions for Odin says...
1. Open Odin3_v1.0
2. Load .512 into the PIT placeholder
(In this case s1_odin_20100512)
3. Load *FILE.tar* into PDA placeholder
(In this case Eugene_2E_JK2_Froyo.tar.md5)
4. Make sure COM port has a number in it
This means your phone is connected, if your phone is not connected make sure you have the correct drivers)
5. Press Start!
Click to expand...
Click to collapse
Using the image I've attached of Heimdall, which PDA/Code should I load the .md5 file under?
Thank you Odin, thank you Samsung USB drivers (which I had to google to find) and thank you mom's PC. I got my friend's phone working, unfortunately all her contacts were on the phone and not synced to google, and I didn't back her up. Whoops. Why would T-mobile transfer numbers from a black berry to an Android phone and not have it sync with google?
Heimdall was a waste of time and memory. I'm sure the developers worked very hard on it, but it totally didn't work for my mac book pro complicating a tense situation.
Problem solved.
I've searched everywhere and can't find an answer to my problem.
GT-I9100 (Sprint)
I hate to admit I am somewhat of a noob. But pretty good at following instructions. I tried to install ics using Odin.
PDA –—> I9100_CODE_I9100XXKPA_CL51925_REV02_user_low_ship.tar.md5
Phone –—> MODEM_I9100XXKPA_REV_02_CL1094591.tar.md5
CSC –—> GT-I9100-MULTI-CSC-OXAKPA.tar.md5
The first instructions I read din't say to do the pit file. So I didn't. I have read later that I should have. The process failed. And when I restarted the phone I can only get to the download screen. When I try to get to recovery I get "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." I also get the same message if I simply plug the usb into the phone while off, before any buttons are pushed.
Neither Kies or Odin recognize the phone anymore. I've tried different USB ports, a different computer. And I've hooked up a friends AT & T Galaxy S2 and it's recognized fine. Neither computer I've used even makes the beep when you hook up the phone.
The short is since it connected before the flash, and the other phone is showing I'm confident it's not PC related. But not being able to get anywhere besides the download screen has my hands tied to do anything else.
Any ideas would be greatly appreciated! And I have searched all over and can only find similar problems that turn out to be PC related.
thelonnie said:
I've searched everywhere and can't find an answer to my problem.
GT-I9100 (Sprint)
I hate to admit I am somewhat of a noob. But pretty good at following instructions. I tried to install ics using Odin.
PDA –—> I9100_CODE_I9100XXKPA_CL51925_REV02_user_low_ship.tar.md5
Phone –—> MODEM_I9100XXKPA_REV_02_CL1094591.tar.md5
CSC –—> GT-I9100-MULTI-CSC-OXAKPA.tar.md5
The first instructions I read din't say to do the pit file. So I didn't. I have read later that I should have. The process failed. And when I restarted the phone I can only get to the download screen. When I try to get to recovery I get "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." I also get the same message if I simply plug the usb into the phone while off, before any buttons are pushed.
Neither Kies or Odin recognize the phone anymore. I've tried different USB ports, a different computer. And I've hooked up a friends AT & T Galaxy S2 and it's recognized fine. Neither computer I've used even makes the beep when you hook up the phone.
The short is since it connected before the flash, and the other phone is showing I'm confident it's not PC related. But not being able to get anywhere besides the download screen has my hands tied to do anything else.
Any ideas would be greatly appreciated! And I have searched all over and can only find similar problems that turn out to be PC related.
Click to expand...
Click to collapse
Firstly... Being from Sprint... Are you 100% SURE that you have the GT-I9100? What does your device look like? Does it have a middle "hard button" at the bottom?
Product Name
It shows:
PRODUCT NAME: GT-I9100
at the top of the download screen. There are the four buttons across the bottom. Not what I call physical buttons, because they don't move. I guess they would be called soft buttons below the screen.
You don't have an I9100 and are in the wrong forums.
Do you know what I have then?
Probably http://forum.xda-developers.com/forumdisplay.php?f=1281
But you might want to check under your battery before blindly flashing stuff for the wrong device.
open odin look that kies process is not runing on the background.
Try to boot your phone the message from firmware upgrade failed will come on the screen, when you're on this screen plug yor phone it will be recognized on odin, then leave it plugged in and shutdown the phone and get on download mode it will be recognized
last flash stock firmware complete i always use the XXKI3 with pit file, all of this if u phone is gt i9100
this was what i did, have the same problem in a bad flash of stock GB firmware (2 days ago) same screen and same problem, doing that (read it on a post somewhere) helped me
I was wrong. Its not the i9100. Its the galaxy s2 epic touch. Yeah.... Im kicking myself now. I did try what you said and it didnt work. I posted in the correct thread and was told im bricked.
thelonnie said:
I was wrong. Its not the i9100. Its the galaxy s2 epic touch. Yeah.... Im kicking myself now. I did try what you said and it didnt work. I posted in the correct thread and was told im bricked.
Click to expand...
Click to collapse
aw that sucks! i guess you have to buy an usb jig now! Dont worry, its cheap and very usefull it also resets your flash counter
Can you point me in the direction of where to get a USB jig?
Just figured out what the USB jig does. Wont work for me. I cant take the phone back. I cancelled my plan with sprint. I use this phone as a second device. I may have to do JTag... But its going to be $50.
Silly me...I tried to flash the chainfire repack (ROM for Galaxy Note) using PC ODIN but...instead of selecting the file for 'PDA' I selected it for 'Phone' without realising until the FAIL message came up, now I can't flash the chainfire repack from 'PDA', my phone is still in download mode so please help me if I have done something wrong...which I know I have, thank you.
Btw...the repack is not working now using 'PDA' from PC Odin
SealsNavie said:
Silly me...I tried to flash the chainfire repack (ROM for Galaxy Note) using PC ODIN but...instead of selecting the file for 'PDA' I selected it for 'Phone' without realising until the FAIL message came up, now I can't flash the chainfire repack from 'PDA', my phone is still in download mode so please help me if I have done something wrong...which I know I have, thank you.
Btw...the repack is not working now using 'PDA' from PC Odin
Click to expand...
Click to collapse
You probably have thought of, and tried this but......
I have a galaxy nexus and found myself stuck in a very simalar situation.
I came accross a galaxy nexus toolkit by WugFresh, and i managed to get stock back on through the adb interface.
The toolkit automatically detected my phone and what version of the firmware it needed, downloaded it and flashed it on to my phone. It can also use the fastboot interface but adb is by far better in my personal opinion...
Maybe this could help you out, or maybe could even find a galaxy note version.
As your in a non working state atm, you have nothing to lose by at least giving it a go.
May not help, but i thought i would try and give some assistance.
Ictcreations said:
You probably have thought of, and tried this but......
I have a galaxy nexus and found myself stuck in a very simalar situation.
I came accross a galaxy nexus toolkit by WugFresh, and i managed to get stock back on through the adb interface.
The toolkit automatically detected my phone and what version of the firmware it needed, downloaded it and flashed it on to my phone. It can also use the fastboot interface but adb is by far better in my personal opinion...
Maybe this could help you out, or maybe could even find a galaxy note version.
As your in a non working state atm, you have nothing to lose by at least giving it a go.
May not help, but i thought i would try and give some assistance.
Click to expand...
Click to collapse
I forgot about this post, sorry. I also posted in the Galaxy Note general section where I replied, I thought I would risk it and reboot my phone and it rebooted as normal...phew!...and when I when back into download mode and tried flashing the ROM again...it worked! A little wierd but i'm happy I haven't done anything damanging to my phone, watch something happen tomorrow like my phone not turning on
glad you got it working again. there is nothing worse than banging your head against a brick wall with a broken phone!!
luckily these days, it is near impossible to brick a phone completely. thank heavens for small mercys!!
Ok
Trying to Unroot.
But today I have this giantic issue.
My recovery mode just doesnt appear anything like before.
I have tried unrooting using a Root_Remover.zip file. But I can't find at all the "install zip" menu in recovery mode I had when I had to root it first ! Now it just wont appear at all. I only have :
Reboot system Now
Apply update from external Storage
Wipe Data/Factory REset
Wipe Cache Partition
and nothing more. I even tried the second menu (apply update from ext.stor.) but im not using any external storage.
I thought "all right, Ill get through it with ODIN >>> WRONG !!!!!! No download mode ...
So right now I'm completely screwed since theres no way I can perform an unroot under such conditions.
Please someone help me out with this, sorry for being a bit too straightfoward but after 72h spent on that @#%? I find it pretty unrelevant that this ****ing menu wont show the hell up. Even though I guess Im just doing something wrong, I need help.
EDIT : All right. So I figured out most tutorials are written by incompetent people whom mostly release pseudo tutorials that are just here to show the world that they can perform this or that, but in fact, can't take a single second to make a point where you don't get access to DOWNLOAD MODE the same way on a Tab2 than with a S2 -_-. We don't enter DOWNLOAD mode the same way ... geez ... so I figured out that using the Up volume button instead of the down volume button would eventually get me there. Which it did. Come on ... how is it possible that after 15 tutorials, not ONE did mention that ?
Also, ODIN doesn't want to do @#%? right now. I browsed the right firmware, plugged my tab to my laptop ... hit START and it ends in 5 seconds after "all thread completed (0 succeed/0 failed)
I've tried multiple stock firmwares (all the same but form different locations or mirrors) and ... nothing. So ...
First, please clarify these couple of questions. What device do you have? What version of recovery do you have? And one more out of curiosity. Where did you get that root remover zip?
Sent from my GT-P7500 using Tapatalk 4
Most of the tutorials are written for the GT-P75xx. Being that it's also the device for the section you posted this rant in, I can see why the tutorials were not what you needed. Just my two cents but condemning the authors of the tutorials will most likely get you very little help. Not to mention this section isn't for your device.
Sent from my GT-P7510 using XDA Premium HD app
Benzoman said:
Most of the tutorials are written for the GT-P75xx. Being that it's also the device for the section you posted this rant in, I can see why the tutorials were not what you needed. Just my two cents but condemning the authors of the tutorials will most likely get you very little help. Not to mention this section isn't for your device.
Sent from my GT-P7510 using XDA Premium HD app
Click to expand...
Click to collapse
Don't know what happened to my last reply but anyway :
All the threads I read were for Tab2 p51xx or SII.
As explained in first reply (which disappeared), I had and have my damn good reason to condemn people who spam the net with their useless blogs. Won't waste time explaining again a reason which won't certainly arent interested in. But it was costy in term of $.
That said I then realized XDA still exists so I launched a quick google search and fell on this subboard. Reading "Samsung Tab 10.1", unfortunatly didn't mean to me it is a seperated sub forum from the Samsung tab2 10.1. My bad ... do I have to get this thread transfered to the right place or admins will find it useless ?
_____________
My ROM is none. I unrooted but didn't install any ROM. After that I simply figured out I don't need one. But today I need to upgrade to anything above 4.0.4 after the very bad experience I had late friday eve which is quite costy.
I have one more minor trouble I didn't speak of in my first post :
I bought my tablet in September 2012 in the Netherlands GT P5110, ICS 4.0.4. So after checking on the XDA page where all of the stock firmwares are listed, I realized there is no "perfect" match. The only firmware for the Netherlands and for P5110 is from April 2012 and ICS 4.0.3, not 4.0.4 ; yet it is the one I downloaded. Should I get another one ?
About the Root remover, I uploaded to my tab one I downloaded from a website which I can't recall or find on google right now because I downloaded two from two different websites and only remember this one : www techbloggerzone com/2012/09/how-to-unroot-galaxy-tab-2-101-gt html [dots for WWW | COM and HTML were removed since I'm not allowed to post external links yet]
I think there's nothing else missing, but tell me if there is.
IMPORTANT EDIT : I just realized the factory usb plug I have for the Samsung must be damaged. It charges on sector, but isn't identified properly on my laptop and thus won't let me connect it by wire. Didn't figure this out earlier as I did all transfers by Kies wifi. Damn ... but it only explains why Odin can't upload anything to my tab, not why I can't use find the zip install option in Recovery mode for the root_remover.zip
As already stated you're in the wrong place but we all try to help each other here...but no more rants or you might find a stoney silence will be your only reply....
Problem with Odin is more likely laptop drivers and/or windows version and not your cable...
Samfirmware has many 4.0.4 roms for your "area", they have a 4.1.2 version for Netherlands and 4.0.4 for Belgium, Luxembourg etc. As long as you find an XX version it will have Dutch language option.
The recovery you described when you eventually got into it sounded like stock recovery so you wouldn't be able to choose and flash zip from there
Calm down, take a deep breath, get your laptop and drivers sorted first or you'll not get anywhere... Did you have a yellow indication with com port number in the Odin window, if not it is surely drivers. Does windows in any way recognise the tab when connected? (warning tone, does device manager show anything?)
sent from my still superb Google I/O 7510 (xda hd)
stinky73 said:
As already stated you're in the wrong place but we all try to help each other here...but no more rants or you might find a stoney silence will be your only reply....
Problem with Odin is more likely laptop drivers and/or windows version and not your cable...
Samfirmware has many 4.0.4 roms for your "area", they have a 4.1.2 version for Netherlands and 4.0.4 for Belgium, Luxembourg etc. As long as you find an XX version it will have Dutch language option.
The recovery you described when you eventually got into it sounded like stock recovery so you wouldn't be able to choose and flash zip from there
Calm down, take a deep breath, get your laptop and drivers sorted first or you'll not get anywhere... Did you have a yellow indication with com port number in the Odin window, if not it is surely drivers. Does windows in any way recognise the tab when connected? (warning tone, does device manager show anything?)
sent from my still superb Google I/O 7510 (xda hd)
Click to expand...
Click to collapse
I thought I had all my drivers updated (for the samsung tab, installed like two or three weeks ago), so if it's about drivers, then I don't get it . I checked that in the first place. The cable sometimes fails the connection to my laptop, but today it just won't work. :/. Windows recognizes the device as an external object which can't properly install and such connect (yellow pop up message in right corner, over the task bar). I do not exactly undersatnd what you mean by a yellow indication with "com port" number in the Odin window, but I don't think I had that ... in fact I'm pretty sure about it.
If it's just about drivers, where can I go to find the latest ?
Try looking in Samsung site for drivers here http://www.samsung.com/us/support/
What version of odin are you using? Would recommend 1.3 for the tab 2.
The indication of com port in odin is as in attached image, if you haven't got that then the computer is not recognising your tab, either because of drivers, or cable, but as we've said, you should start with the drivers, probably by downloading the latest from Samsung, deleting all drivers you have at the moment then re-installing.
If the tab is not recognized by the computer then programs like odin cannot do anything as they use the computers' usb bus...
stinky73 said:
Try looking in Samsung site for drivers here
What version of odin are you using? Would recommend 1.3 for the tab 2.
The indication of com port in odin is as in attached image, if you haven't got that then the computer is not recognising your tab, either because of drivers, or cable, but as we've said, you should start with the drivers, probably by downloading the latest from Samsung, deleting all drivers you have at the moment then re-installing.
If the tab is not recognized by the computer then programs like odin cannot do anything as they use the computers' usb bus...
Click to expand...
Click to collapse
Thank you very much !! I was using Odin 1.85 and Odin 3.7 (used 1.85 for rooting), I'll try a downgraded version.
Keep you in touch if problems are resolved or not after that. Thank you again.
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?