Device: AT&T Galaxy S5 OS 4.4.2 (carrier locked)
Background: Applied AT&T OTA 4.4.4 update (device showed it available from AT&T), once update finished applying the device couldn't connect to AT&T mobile data (WiFi worked and incoming/outgoing calls worked). I tried several different troubleshooting methods and ended up doing a factory reset. This didn't resolve issues. So I tried flashing the ROM; this is where things took a massive turn south.
Issue: Device boots to Samsung logo and hangs (logo partially loads before hanging). I can get to recovery and to download mode for Odin. I've used the following guides for flashing: (I don't have enough posts to set links so I posed them below)
galaxys5root(.)com - Downloaded flashing files and Odin twice to ensure no issues. Got the same result flashing all of these. I couldn't flash blootloader, I assume because it is still locked.
galaxys5update(.)com - I used this guide with files from sammobile(.)com for "AP" on Odin. I'm currently downloading the files hosted on GalaxyS5Update's guide, but I still have another few hours before they finish.
This isn't my first go around with flashing ROMs on Android, however it is my first try with locked Samsung phones (I've always used Nexus devices prior to this).
I'm at a loss where go go from here. I'm not sure exactly what I'm doing wrong nor am I sure where to look to move forward.
I appreciate any help anyone can provide. Let me know if I didn't provide enough information or wasn't clear enough.
Thanks!
J
Just in case the links don't work:
Guide 1 - galaxys5root(.)com/galaxy-s5-unroot/how-to-unroot-galaxy-s5-with-odin-and-stock-firmware/
Guide 2 - galaxys5update(.)com/unbrick-att-galaxy-s5-sm-g900a-soft-brick-fix-restore-to-stock-firmware/
SamMobile - sammobile(.)com/firmwares/download/28224/G900AUCU1ANCE_G900AATT1ANCE_ATT/
Quick update. The download I referenced waiting on in my original post finished and I tried the flash again.
Screenshot of Odin: imgur.com/XaUWQ1V,Tz0EjvM
Image of Odin Mode on Phone: imgur.com/XaUWQ1V,Tz0EjvM#1
Below is the output from Odin:
Code:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> AP_G900AUCU1ANCE_964333_REV00_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CP_G900AUCU1ANCE_964333_REV00_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CSC_ATT_G900AATT1ANCE_964333_REV00_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> boot.img
<ID:0/005> NAND Write Start!!
<ID:0/005> recovery.img
<ID:0/005> system.img.ext4
<ID:0/005> persist.img.ext4
<ID:0/005> modem.bin
<ID:0/005> Transmission Complete..
<ID:0/005> Now Writing.. Please wait about 2 minutes
<ID:0/005> Receive Response from boot-loader
<ID:0/005> cache.img.ext4
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Removed!!
<ID:0/005> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Any ideas?
I should add, I've used several different USB cables (including the 3.0 cable included with the phone) on different ports on my Windows 8.1 machine. It doesn't seem to make a difference.
jharder01 said:
Any ideas?
I should add, I've used several different USB cables (including the 3.0 cable included with the phone) on different ports on my Windows 8.1 machine. It doesn't seem to make a difference.
Click to expand...
Click to collapse
Try to do Factory Reset after flashing firmware dedicated to your phone?
To do this - flash STOCK firmware via ODIN again allow auto reboot and ahone get into bootloop again - pull out battery.
Then wait 30 seconds and enter to STOCK recovery - VOL+ + HOME + POWER (Almost the same like download mode but instead vol- is vol+) and do format data and format cache few times.
Try to boot it up, if not work and phone will get into bootloop again, flash stock firmware and try.
jharder01 said:
Any ideas?
I should add, I've used several different USB cables (including the 3.0 cable included with the phone) on different ports on my Windows 8.1 machine. It doesn't seem to make a difference.
Click to expand...
Click to collapse
Please check the att s5 general section, there are threads with files and instrctions.
Sent from my SM-G900A using Tapatalk
qubbus said:
Try to do Factory Reset after flashing firmware dedicated to your phone?
To do this - flash STOCK firmware via ODIN again allow auto reboot and ahone get into bootloop again - pull out battery.
Then wait 30 seconds and enter to STOCK recovery - VOL+ + HOME + POWER (Almost the same like download mode but instead vol- is vol+) and do format data and format cache few times.
Try to boot it up, if not work and phone will get into bootloop again, flash stock firmware and try.
Click to expand...
Click to collapse
Qubbus,
I tried the same thing minus multiple formats after imaging before. Today, I ran Odin, let it run all its processes until it froze again, then I went into recovery and formatted data and cache both 3 times. Still seeing the same issues however
Thanks for the suggestion though! I feel like I'm one mistake/step from a working phone.
Rakuu said:
Please check the att s5 general section, there are threads with files and instrctions.
Sent from my SM-G900A using Tapatalk
Click to expand...
Click to collapse
I checked around, and didn't see anything for the AT&T variant. Seems most people are posting about F or H models unfortunately.
jharder01 said:
I checked around, and didn't see anything for the AT&T variant. Seems most people are posting about F or H models unfortunately.
Click to expand...
Click to collapse
There is a section specifically for the at&t variant http://forum.xda-developers.com/att-galaxy-s5/general
Sent from my SM-G900A using Tapatalk
Still locked
I'm having the same issue - exactly as defined here... and have tried the same things outlined here and have not resolved my issue. Any progress or success out there??? I've been reading/searching for several weeks now and haven't found a solution yet.
Update: FIGURES - I wait and search for two weeks on a fix... post a message and within 20 minutes, actually find the answer!
HERE is what fixed it for me (for anyone else having this problem):
http://forum.xda-developers.com/att...w-to-unbrick-flash-to-stocknce-g900a-t3077652
(I had already tried a different Downgrade to NCE file as archie87 wrote in the above - but this one actually worked for me!)
Related
Apologies if this has been asked before, but I tried checking everywhere for a solution and couldn't come up with anything.
I have an AT&T Galaxy S4 I337. I rooted it, but now I want to unroot it. I used Odin 3v185 and this is what I get:
Screenshot: i.imgur.com/XRBVjH6.jpg
The white box on the bottom left says:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337UCUAMDL_I337ATTAMDL_I337UCUAMDL_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
My phone says:
START [224, 1440]
SW REV. CHECK FAIL : fused : 2 , Binary : 1
I've tried it multiple time with the I337UCUAMDB_I337ATTAMDB_I337UCUAMDB_HOME.tar.md5 and I337UCUAMDL_I337ATTAMDL_I337UCUAMDL_HOME.tar.md5 firmware. I am using the original Samsung USB cord. I've also tried it only 3 different USB ports on my computer. I am running XP. Can anyone help me?
Your on the mf3 firmware. Odin won't work. I can tell because of the "fused 2" in the Odin printout
Thanks. Is there a way to unroot it?
tcow24 said:
Thanks. Is there a way to unroot it?
Click to expand...
Click to collapse
Can you boot now? If you can unroot in super su.
tcow24 said:
Thanks. Is there a way to unroot it?
Click to expand...
Click to collapse
Yes there is, I'm guessing you are able to boot to your phone?
Here's a link and instructions you can follow. Good luck and report to us how it goes
http://forum.xda-developers.com/showthread.php?p=45340743#post45340743
It worked! Thanks JD and haremmon. I feel like an idiot for not seeing that thread.
I need some help please?
I have a Galaxy s4 rooted and I wipe the system and rebooted... I was installing a rom and did not even think anout restoring my old ones. so know I am stuck and the phone will not go into twrp, all it dose is beeps evey 3 seconds. I can get to odin download and i have downloaded stock fimware md5 files and only had one not fail on me using odin3. but it dose the same thing beeps and still can not get to recovery.. please help this is frustrating.
markdthor28 said:
I have a Galaxy s4 rooted and I wipe the system and rebooted... I was installing a rom and did not even think anout restoring my old ones. so know I am stuck and the phone will not go into twrp, all it dose is beeps evey 3 seconds. I can get to odin download and i have downloaded stock fimware md5 files and only had one not fail on me using odin3. but it dose the same thing beeps and still can not get to recovery.. please help this is frustrating.
Click to expand...
Click to collapse
pull battery,
put battery back in,
boot into odin using the physical keys (home+volume down+power),
then when it says press volume up to boot into odin, or volume down for cancel choose volume down.
Might boot up normally, i have the issue to where to recovery is messed up, all i need is the 'install-recovery.sh' but no one who has a rooted S4 running MF3 has responded to me yet..ill let you know if i fix the recovery that way.
h11wiscan said:
pull battery,
put battery back in,
boot into odin using the physical keys (home+volume down+power),
then when it says press volume up to boot into odin, or volume down for cancel choose volume down.
Might boot up normally, i have the issue to where to recovery is messed up, all i need is the 'install-recovery.sh' but no one who has a rooted S4 running MF3 has responded to me yet..ill let you know if i fix the recovery that way.
Click to expand...
Click to collapse
At this point, I don't know if you'd be able to fix it that way. The only option that many users have been doing is going to best buy with a Samsung experience area and having them reflash the MF3 firmware.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
tcow24 said:
Apologies if this has been asked before, but I tried checking everywhere for a solution and couldn't come up with anything.
I have an AT&T Galaxy S4 I337. I rooted it, but now I want to unroot it. I used Odin 3v185 and this is what I get:
Screenshot: i.imgur.com/XRBVjH6.jpg
The white box on the bottom left says:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337UCUAMDL_I337ATTAMDL_I337UCUAMDL_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
My phone says:
START [224, 1440]
SW REV. CHECK FAIL : fused : 2 , Binary : 1
I've tried it multiple time with the I337UCUAMDB_I337ATTAMDB_I337UCUAMDB_HOME.tar.md5 and I337UCUAMDL_I337ATTAMDL_I337UCUAMDL_HOME.tar.md5 firmware. I am using the original Samsung USB cord. I've also tried it only 3 different USB ports on my computer. I am running XP. Can anyone help me?
Click to expand...
Click to collapse
Mine is same issue, except my phone says: Unsupport dev_type, I am using samsung galaxy s3 I9300 with binary count 2.
Please help me to resolve this and unroot my device.
srikanthkata said:
Mine is same issue, except my phone says: Unsupport dev_type, I am using samsung galaxy s3 I9300 with binary count 2.
Please help me to resolve this and unroot my device.
Click to expand...
Click to collapse
Not trying to be rude but please go post this question under the GS3 forum. The GS3 forum can be found here http://forum.xda-developers.com/galaxy-s3
Good morning all.
I need to unroot (or just put stock firmware back on my device). I have Cyanogen 11, and i need to swap phone numbers on my phone. The code Sprint wants me to enter does not work with Cyanogen mod so i need to put stock firmware back on the device so sprint can have me put in the codes they need to change the phones telephone number.
Long story short, i have done a lot of research on Google and on here, and i am running into a problem.
First i am using the original (actually i have tried three different ORIGINAL (white) Samsung) USB Cable, i have tried several different USB ports.
I've have downloaded my drivers (actually had them from when i rooted in the first place), i have odin (several different versions, tried them all same result), and stock firmware .tar.md5.
The problem is after i click START in odin, it does its thing for like 10 seconds, then reports a FAIL, this is what Odin reports (this report is from using an Odin v3.185, i have tried v3.07 and 3.09 as well, same end result, but the oden report is slightly different, as it checks the MD5 in the other versions when you enter the file into Odin, vs checking the MD5 when you hit start):
<ID:0/016> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> L720VPUAMDC_L720SPTAMDC_L720VPUAMDC_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/016> Odin v.3 engine (ID:16)..
<ID:0/016> File analysis..
<ID:0/016> SetupConnection..
<ID:0/016> Initialzation..
<ID:0/016> Get PIT for mapping..
<ID:0/016> Firmware update start..
<ID:0/016> aboot.mbn
<ID:0/016> NAND Write Start!!
<ID:0/016>
<ID:0/016> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
And on the PHONE itself, i get a sliver of the progress bar, and in the upper top left some red text that's very difficult to read, but it says something like:
START [ZZ4.1440]
SV REV. CHECK FAIL : found : 4 . Binary : 1
It says all that in red... i have a suspicion THAT is the problem (my phone) and not Odin.
Any help on this would be appreciated, as this is a WORK phone that i need to get the new number ported to before i give it back to my work! LOL
Thanks in advance.
(After previewing my post in the forum.... WOW that's an OLD signature! LOL please disregard the sig info!)
You're trying to Odin an outdated tar. Go to www.sammobile.com and download the NG2.tar.
Thank You! That worked.
I was under the impression that i had to go back to an older version, then update to the latest version. <Shrug>
Anyhow, the first flash went to about 97,98%, then failed. I cleared everything i was doing on the computer (I was running 6 instances of an MMO i play at the same time on the one computer, plus some other stuff that was taxing my computer), RE-Flashed in ODIN, successful Flash. First boot hung at yellow sprint screen. I Pulled the battery, cleared cache, reset (in recovery), and it was a Success! So again, thank you kindly, i knew i just needed a nudge in the right direction. =)
CASE CLOSED. Heh.
Hey guys,
I'm kinda lost here, I bought this phone a few months ago on a black friday sale in the US.
A few weeks it started bootlooping (the 'preboot logo' kept flashing) it got worse and worse. Remember, I never tried to root, install a custom recovery/OS, nothing!
The only way to get it out of the bootloop was to do a factory reset or sometimes a clear dalvik. But it got worse and worse, and booting into recovery was getting harder and harder...
5 factory resets further, and dozens of dalvik clears, it it bootlooping again!! And it is now impossible to boot into recovery, only download mode.
So I reinstalled the os through odin using these files: https://forum.xda-developers.com/att...4eqc6-t3596180
When that didn't work, I used these files: https://forum.xda-developers.com/att...build-t3576469
Same bootloop, and still impossible to boot into recovery via power+vol up+home.
You might ask, why don't you repair it under warranty?
Well, I live in france and samsung france refuses to even touch an american device!
Ps: here are the options I had ticked in odin:
1st time: F reset and re-partition
2nd flash: NAND erase, F reset and re-partition
3rd flash: bootloader update, NAND erase, F reset and re-partition
Here is a log, md5 checks included, in case you wonder:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin engine v(ID:3.1207)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> NAND Write Start!!
<ID:0/006> SingleDownload.
<ID:0/006> sboot.bin
<ID:0/006> param.bin
<ID:0/006> cm.bin
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> system.img
<ID:0/006> userdata.img
<ID:0/006> modem.bin
<ID:0/006> Transmission Complete..
<ID:0/006> Now Writing.. Please wait about 2 minutes
<ID:0/006> Receive Response from boot-loader
<ID:0/006> cache.img
<ID:0/006> RQT_CLOSE !!
<ID:0/006> RES OK !!
<ID:0/006> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
I would greatly appreciate your help as I'm lost,
Many thanks in advance,
nxss4
which model do you have? you might have erased your EFS And imei and did you use a pit file when you flashed?
MjdHa or MjdHa1 said:
which model do you have? you might have erased your EFS And imei and did you use a pit file when you flashed?
Click to expand...
Click to collapse
Hello, and thank you for replying!
Yes, I used a pit file, it's a G928A (att).
I saw this was a risk when using nand erase all, but I just want it to show some signs of life again before doing hardware repairs.
I will very probably buy a new motherboard anyway. If possible I'd like to put a G928F motherboard into my G928A, this should be possible, right?
In this case I could install samsungs stock firmware and have better developer support.
Thank you in advance,
Try flashing su..... I guess you have drk damaged
You can simply send the device to USA's Samsung's warranty repair center.. Of course Samsung France won't touch it, they're only familiar with devices that originated from France and no where else..
Samsung USA won't touch a French device or any others that wasn't originally one from here, since they won't have the resources or knowledge to fix it.
It just makes sense this way, especially with phones like the S6, which have 16 or so variants, that differ mostly due to region/carrier specs. Not to mention access to all the various firmware for each specific phone/carriers..
It just wouldn't be cost effective or sensible if each repair center worldwide has the ability to repair a different regions device, considering they may get a handful of handsets for repair from other regions.
Its kind of silly to think otherwise...
At this point however, not sure whether your device still falls within their warranty restrictions w/ all the flashing you've done?
Too bad, Id go w/ the warranty claim every time, if it's available, heck some of us pay extra money to have extended coverage, as a "safety net.."
InkTry install twrb using download mod after that wipe every thing and then install any coustom rom after installing the rom make sure install DM virety zip this important step after that hit reboot and see if loop again
The second way is to install the stock firmware and then go into download mod and install twrb after that reboot to recovery again and then install DM virety zip and when finish hit reboot and see if loop
I hope works for u
So I tried to root using an old youtube tutorial (which I since have learned is a bad idea), now it's stuck in a boot loop. Tried to factory restore from boot menu, didn't work. Took my S7 SM-G930V to Geek Squad at Best Buy, and the Samsung guy basically told me he couldn't fix it and neither would Samsung, as a punishment for trying to root. Maybe if he comes into the ER needing life-saving treatment, I'll tell him I won't help him as punishment for doing one of the stupid things I see every day.... I was just going to throw the damn thing away and buy a new phone, but he pissed me off, so now I want to fix it just to spite him.
Tried kies (said to use smart switch), smart switch (unsupported device), and Odin, all fail. Used the links for the correct firmware here. Tried Verizon's software assistant... also fails. During flash with Odin, it gets about 3 seconds into the bar that goes across the bottom of the phone, then Odin says failed. I'm on android 7.0 snapdragon.
I can get it into download mode, but flashing fails nearly immediately. In download mode, at the top left it says: "ODIN MODE (HIGH SPEED), PRODUCT NAME: SM-G930V, CURRENT BINARY: Samsung Official, SYSTEM STATUS: Official, FRP LOCK: OFF, QUALCOMM SECUREBOOT: ENABLE, AP SWREV: B4(2,1,1,1,1) K1 S3, SECURE DOWNLOAD: ENABLE
Also, I wrote down the Build # and baseband in case they help... Build #: NRD90M.G930VVRS4BRA1 Baseband: G930VVRS4BRA1
Im sure you experts need additional more specific information, so ask away. And thank you!
Just tried Odin PrinceComsy version and the firmware on the tutorial thread in here for unrooting Verizon Galaxy S7, and failed again. Here's the log:
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1203)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> emmc_appsboot.mbn
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Anybody???
I'm sure you're tired of walking noobs through this crap, but I'm sure you can sympathize the idea of suddenly losing access to your smart phone. Does anyone have any ideas on what to try next? I've read for hours and tried dozens of tutorials and I'm just not getting anywhere. FRUSTRATING AS HELL!!! I can stop a heart attack or a tension pneumothorax in my sleep, but trying to program a damn smart phone correctly... you might as well tell me to try to fly.
ERDOC76 said:
So I tried to root using an old youtube tutorial (which I since have learned is a bad idea), now it's stuck in a boot loop. Tried to factory restore from boot menu, didn't work. Took my S7 SM-G930V to Geek Squad at Best Buy, and the Samsung guy basically told me he couldn't fix it and neither would Samsung, as a punishment for trying to root. Maybe if he comes into the ER needing life-saving treatment, I'll tell him I won't help him as punishment for doing one of the stupid things I see every day.... I was just going to throw the damn thing away and buy a new phone, but he pissed me off, so now I want to fix it just to spite him.
Tried kies (said to use smart switch), smart switch (unsupported device), and Odin, all fail. Used the links for the correct firmware here. Tried Verizon's software assistant... also fails. During flash with Odin, it gets about 3 seconds into the bar that goes across the bottom of the phone, then Odin says failed. I'm on android 7.0 snapdragon.
I can get it into download mode, but flashing fails nearly immediately. In download mode, at the top left it says: "ODIN MODE (HIGH SPEED), PRODUCT NAME: SM-G930V, CURRENT BINARY: Samsung Official, SYSTEM STATUS: Official, FRP LOCK: OFF, QUALCOMM SECUREBOOT: ENABLE, AP SWREV: B4(2,1,1,1,1) K1 S3, SECURE DOWNLOAD: ENABLE
Also, I wrote down the Build # and baseband in case they help... Build #: NRD90M.G930VVRS4BRA1 Baseband: G930VVRS4BRA1
Im sure you experts need additional more specific information, so ask away. And thank you!
Just tried Odin PrinceComsy version and the firmware on the tutorial thread in here for unrooting Verizon Galaxy S7, and failed again. Here's the log:
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1203)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> emmc_appsboot.mbn
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
I finally figured it out. Thanks for all your help!
:good: but what was your solution?
edit: I think you didn't get much attention because your title likely turned people off -- it's kind of petty to call attention to someone's background if it's not part of the discussion. I saw you had another post where you didn't do that, and got help, so :good:
chill,
Procrastinatron
What's with the title of your post? We don't need that BS on these forums.
ERDOC76 said:
So I tried to root using an old youtube tutorial
Click to expand...
Click to collapse
You'll be fine man go to sammobile look up your G930V in firmware. You can get your current or update to oreo (no root method for oreo yet) unzip
Make sure you have all samsung drivers and adb uninstall kies maybe reboot your computer and make sure your cable is mtp compatible not just a charging cable. Reboot into download mode flash the BL, AP, CP, and CSC .md5 files in their respective Odin slots. Let recovery do its thing first boot will take some time.
Rooting is even quicker and easier so if you're still confident in yourself look up the methods here on here xda. G930V, G930A, G930T, G930U and G930P pretty much use the same root methods as far as nougat goes.
this is probably the biggest thread all credit to those guys that developed it and shared the files, this is probably the best place to start before you discover safestrap and what mods you can actually do (dual speaker ect.). Rooting, like everything else in life is always at your own risk
https://forum.xda-developers.com/tm...eres-how-rooted-nougat-s7-edge-g935t-t3567502
I've searched the heck outta this - and tried everything. I simply don't understand why I am getting nowhere. There is some fundamental thing I must be doing wrong but I don't know what.. I am sure that minds superior to mine can fix this.... I just need someone to take pity on me....
The phone is a SM-N900W8 (Bell Canada) that was completely stock running Android 5. After a battery pull, I got Set Warranty Bit : kernel error. Or if I try to get to recovery I get Set warranty Bit : recovery. I 'should' be able to flash stock ROM and fix, correct? Well, flashing stock ROM does not work. I tried flashing a TWRP too. Nothing. I tried flashing just a recovery or a boot, even tried flashing a N900T version (I read that works on my model too). I've tried latest Odin (3.13) or earlier versions (esp. 3.09, or 3.10). Nothing. It shows a pass in ODIN, but it's still not getting past these warranty bit errors. I can not get to any recovery...
The phone remains undaunted by my feeble attempts.
I'm using the original Samsung USB cable, attached to my motherboard ports (tried different ones too) and the ODIN downloads appear to load (I get the blue bar that increases across the screen). It reboots and then we're back to the error.
I have NOT tried ticking the re-partition box - is that the way to go? Isn't there a pit file contained in the stock ROM?
Should I be trying to flash using an image on the SD card?
Help me Obi-wan....
Here's a fix to where you are
I have exact same model and was where you are
Step 1 remove battery
Step 2 hold home button power button volume button
Step 3 continue holding all 3 buttons and put battery back in voila you get to recovery
Eastcoastguido said:
I have exact same model and was where you are
Step 1 remove battery
Step 2 hold home button power button volume button
Step 3 continue holding all 3 buttons and put battery back in voila you get to recovery
Click to expand...
Click to collapse
Thanks for the reply. I have tried what you suggest - device will not boot into recovery. It says Recovery booting at top of screen followed by Set Warranty Bit: recovery....
askelly35 said:
Thanks for the reply. I have tried what you suggest - device will not boot into recovery. It says Recovery booting at top of screen followed by Set Warranty Bit: recovery....
Click to expand...
Click to collapse
Try this :
- Turn off the phone.
- Enter Download mode.
- At the first download mode screen where it says you can press Volume-down to boot normally, press volume-down to boot normally.
Does Odin show any error message ??
JJEgan said:
Does Odin show any error message ??
Click to expand...
Click to collapse
ODIN shows a pass...
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1301)..
<ID:0/005> File analysis..
<ID:0/005> Total Binary size: 2303 M
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> NAND Write Start!!
<ID:0/005> SingleDownload.
<ID:0/005> aboot.mbn
<ID:0/005> sbl1.mbn
<ID:0/005> rpm.mbn
<ID:0/005> tz.mbn
<ID:0/005> sdi.mbn
<ID:0/005> NON-HLOS.bin
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img.ext4
<ID:0/005> persist.img.ext4
<ID:0/005> modem.bin
<ID:0/005> Transmission Complete..
<ID:0/005> Now Writing.. Please wait about 2 minutes
<ID:0/005> Receive Response from boot-loader
<ID:0/005> cache.img.ext4
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Removed!!
<ID:0/005> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
I have now read about a eMMC Chip failure issue... maybe this is the problem?
That tends to read in Odin as Nand Write Fail .
Did it successfully flash twrp?
audit13 said:
Did it successfully flash twrp?
Click to expand...
Click to collapse
No it did not.
I have not tried to re-partition (the box has not been ticked in ODIN) - would that be something worth trying?
No not without be 100% prepared for dead phone.
Repartition you really need to know what you are doing with PIT etc.
askelly35 said:
No it did not.
I have not tried to re-partition (the box has not been ticked in ODIN) - would that be something worth trying?
Click to expand...
Click to collapse
What is the Odin error in the log window when you try to flash Odin?
You are flashing the latest stock ROM from sammobile.com in Odin?
audit13 said:
What is the Odin error in the log window when you try to flash Odin?
You are flashing the latest stock ROM from sammobile.com in Odin?
Click to expand...
Click to collapse
There was no ODIN error - it said "pass".
I was using the latest stock ROM from sammobile.com (bell Canada version for Ontario).
Try flashing again with a pit file. Without a pit file, you won't be able to re-partition.