Related
Hello,
I am having some issues with my S5 G900A (AT&T). Any help I could get in order to get any functionality back out of my phone would be greatly appreciated.
I recently update via OTA to lollipop, but I wanted to get it rooted to try it out. The first thing I attempted to do was to revert the firmware back to 4.4.2 by using Odin. I used three different sources for the G900AUCU1ANCE model, the last of which I got from here, which I found from this post.
However, this did not work, and now I am forever stuck on the firmware update page.
When I ran the Odin program, the program failed and output the following:
<ID:0/007> Odin engine v(ID:3.1005)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> boot.img
<ID:0/007> NAND Write Start!!
<ID:0/007> recovery.img
<ID:0/007> persist.img.ext4
<ID:0/007> system.img.ext4
<ID:0/007> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
On the phone side, I get the following messages on the screen. The messages that appear after running Odin are bolded.
ODIN MODE
PRODUCT NAME: SM-G900A
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
REACTIVATION LOCK: OFF
KNOX WARRANTY VOID: 0x0
QUALCOMM SECUREBOOT: ENABLE (csb)
RP SWREV: S1, T2, R1, A3, P1
SECURE DOWNLOAD : ENABLE
UDC START
SYS REV CHECK FAIL : Refer 2 > Binary 1
SECURE CHECK FAIL : system
(Downloading... Do not turn off target!!)
Click to expand...
Click to collapse
At this point, if I restart by pulling out (the battery), and then turn it back on normally, then I get back to the 'Odin Mode' screen, but with the large message on the bottom: "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again"
This message will appear when the following keypresses are used to turn the phone on:
Volume up + Lock
Volume down + Lock
Lock
Home + Lock
Volume up + Volume down + Lock
Volume up + Lock + Home
The following keypresses don't do anything
Volume up + Volume down
Volume up + Volume down + Home
Volume down + Home
Volume up + Home
Finally, if I do the following keypress:
Volume down + Lock + Home
I get the familiar warning screen:
Warning!!
A custom OS can cause critical problems in phone and installed applications.
If you want to download a custom OS, press the volume up key.
Otherwise press the volume down key to cancel.
Click to expand...
Click to collapse
If I press the volume down key, then I go back to the same Odin Mode screen with the "firmware upgrade encountered an issue" message from before. If I press the volume up key, then I get the Odin Mode screen (that always stays the same), but with "Downloading... Do not turn off target!!" as the message instead.
I also tried using Samsung Kies, though that method seems to be frowned upon by everyone. It clearly downloaded something and looked like it was installing something, but then it told me that I should run the emergency recovery process using an emergency recovery code. In the alert window, there was clearly a space where an emergency code was supposed to be, but there was no emergency code. Therefore, I was not able to get any farther using Kies.
I have read many posts mentioning that Odin can be very fickle, so I took the liberty of trying using two different USB cables and tried all 4 USB ports that are on my laptop, and I tried each of those three times. I also ensured that Kies and its background processes were not running when I utilized odin.
I also tried re-writing the PIT file, which I found from here, but when I did that, I got
<ID:0/007> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
<ID:0/007> FAIL!
<ID:0/007>
<ID:0/007> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
In Odin and "SECURE CHECK FAIL : PIT" on my phone window.
After exhaustive googling, I am not too sure of what to do anymore, and would appreciate if someone could help.
Bootloader is locked, not sure there is anything you can do
*Detection* said:
Bootloader is locked, not sure there is anything you can do
Click to expand...
Click to collapse
2 questions, which error message points out to you that the "bootloader is locked," and does this mean that I would need to take my phone to AT&T to get it serviced?
<ID:0/007> FAIL! (Auth)
Tells me the Secure Boot Key is failing to authenticate
--
From what I've read, AT&T S5s are bootloader locked, as are a few other carrier branded ones
What is actually wrong with the phone? Just that you want to downgrade to Kitkat and root?
Or is there actually something wrong with Lollipop?
It is a very well known fact that after upgrading from KK to LP, you should factory reset the phone, KK leaves behind rubbish files that cause all sorts of issues, resetting cures a lot of them
Oh I see, thanks!
Nothing really wrong with it, I just wanted to try rooting the phone.
Unfortunately the only known method to root Lollipop is via ODIN, but it's still a fairly new OS so never say never about the devs finding an exploit that can be used with a locked bootloader
You cant downgrade from lollipop to kitkat once you take the ota for lollipop, as you can see here. You need to get the oc4(lollipop) firmware files and flash that to unbrick, they are in the att s5 general section.
Sent from my twi5ted SM-G900A using Tapatalk
Thanks, I ended up taking it to best buy and having the guy there reset the firmware. Pretty sure he used something called SMART or something to do it
Apologies for the repost, found this to be a better place to pose the plea for assistance
_____
Hello all. . .
Longtime reader (learner), first time poster. Trying to bring son's GS5 back to life -- it's stuck in boot loop ("Samsung GALAXY S5" splash screen appears, reboots). Unknown cause, not due to any flashes, ROMs, ROOT, etc
All attempts to enter recovery mode (Vol up + PWR + Home) initially successful (get blue text: RECOVERY BOOTING. . . .) then display goes black, repeats. -- never see Recovery screen. Yes, I've cycled power, battery out, wait, etc, etc.
Can successfully enter Download mode, Odin v3.09 recognizes connection, but all attempts to write to memory fail.
GS5 displays:
ODIN MODE:
PRODUCT NAME: SM-G900P
CURRENT BINARY: Samsung Original
SYSTEM STATUS: Official
REACTIVATION LOCK(KK): OFF
KNOX WARRANTY VOID: 0x0
QUALCOMM SECUREBOOT: ENABLE (CSB)
AP SWREV: S1 T3 A1 A3 P1
SECURE DOWNLOAD: ENABLE
UDC START
<press Odin Start button>
Odin displays:
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> SingleDownload.
<ID:0/008> aboot.mbn
<ID:0/008> NAND Write Start!!
<ID:0/008> FAIL! (Auth)
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Device display adds line:
SW REV CHECK FAIL : [aboot]Fused 3 > Binary 1
____
Cannot determine build number and original box long gone. I've downloaded a couple firmware zips from sammobile (Sprint CDMA) using files nearest to best guess for purchase date. Is it necessary to match the exact files which originally came installed or should later firmware releases also normally load? In other words, is the fail due to trying a wrong firmware revision?
Any other info I need to include here? Thanx in advance!
flyyboyy
Hello again:
Zero replies, did I omit important information in my first request -- or am I just rehashing previous inquiries about boot loop problems? (I have read through all posts relating to boot loops but found no answers that solved the to write to Nand failures). Forgive me if it's here and I simply didn't recognize it. . .
So (succinctly) why might Odin fail to write when attempting to reload the original firmware: . . . NAND Write Start!! . . . FAIL! (Auth) . . .Complete(Write) operation failed. . . .All threads completed. (succeed 0 / failed 1)
What might I be doing wrong, or what might I try instead?
Thanks again
flyyboyy said:
Apologies for the repost, found this to be a better place to pose the plea for assistance
_____
Hello all. . .
Longtime reader (learner), first time poster. Trying to bring son's GS5 back to life -- it's stuck in boot loop ("Samsung GALAXY S5" splash screen appears, reboots). Unknown cause, not due to any flashes, ROMs, ROOT, etc
All attempts to enter recovery mode (Vol up + PWR + Home) initially successful (get blue text: RECOVERY BOOTING. . . .) then display goes black, repeats. -- never see Recovery screen. Yes, I've cycled power, battery out, wait, etc, etc.
Can successfully enter Download mode, Odin v3.09 recognizes connection, but all attempts to write to memory fail.
GS5 displays:
ODIN MODE:
PRODUCT NAME: SM-G900P
CURRENT BINARY: Samsung Original
SYSTEM STATUS: Official
REACTIVATION LOCK(KK): OFF
KNOX WARRANTY VOID: 0x0
QUALCOMM SECUREBOOT: ENABLE (CSB)
AP SWREV: S1 T3 A1 A3 P1
SECURE DOWNLOAD: ENABLE
UDC START
<press Odin Start button>
Odin displays:
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> SingleDownload.
<ID:0/008> aboot.mbn
<ID:0/008> NAND Write Start!!
<ID:0/008> FAIL! (Auth)
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Device display adds line:
SW REV CHECK FAIL : [aboot]Fused 3 > Binary 1
____
Cannot determine build number and original box long gone. I've downloaded a couple firmware zips from sammobile (Sprint CDMA) using files nearest to best guess for purchase date. Is it necessary to match the exact files which originally came installed or should later firmware releases also normally load? In other words, is the fail due to trying a wrong firmware revision?
Any other info I need to include here? Thanx in advance!
flyyboyy
Click to expand...
Click to collapse
Same thing with me.. patience gets you through it..
The same thing happened to me, same phone and same contract carrier (Sprint).
I bought my phone from a third party who apparently restores it to near-mint condition. The OS it had was one of the first releases of 6.0 /marshmallow. I tried downgradingit back to 5 / lollipop because i heard that call recording was still enabled with that OS.
I used Odin versions 3.7 thru 3.10 i believe and flashed every version of 5 that was listed on sam mobile and samsung 's site and all of them either failed to initiate- citing the same readings and failure reasons in odin that you mentioned - or they "succeeded" and resulted in boot loops.
I also failed to flash any of the earlier ROM versions of android 6 than the one my SM-G900P phone came with.
Finally, i succeeded in flashing 2 types of ROMS, the version of 6 my phone started with, then subsequently the most recent version released earlier in march 2017 (this month).
Conclusion: i believe the order that you flash these roms for our model phone with our carrier matters. Flash your phone with ROM images from the version that it came with, and continue sequentially and chronologically until your boot screen finally shows something other than that lovely little sprint logo
Good luck with your son's phone, and please let us k ow how it goes..... as i think this may be a recurring theme we may see more often in the future. I imagine the problem lies with either odin, samsung sm-g900p, or the sprint/cdma ROMa we're dealt.
-Rob
Have you tried samsung kies yet? Odin is for rooting your phone. Samsung kies will put updated firmware in your phone. I have used it several times in the past on a sam phone. It will work. Its from samsung company.
Hello, so I'm having a huge problem right now, that seemingly came out of nowhere.
My phone is stuck on "Samsung Galaxy S7 Edge" screen logo and can only enter download mode, nothing else.
All I did was download the firmware update that popped up OTA. Something must have failed and I was greeted with a permanent freeze on that part.
The update that I've downloaded was called - G935FXXU1DQB7/G935FSEB1DQB2/G935FXXU1DQB3 with the file size of 1224.14 MB
It has failed once before but it wasn't a brick. Said something about mounting data error in a recovery mode. A day later I've tried to re-download and install the update again and this is the place I'm in right now.
My phone is the European Exynos variant, not sim locked. I'm from Lithuania, but I somehow doubt my model had the Baltics firmware as I don't think the 7.0 is released there yet.
So far I've tried installing stock firmwares from UK, Poland, Baltics region. Both 6.0.1 and 7.0 yield the same results. Different Odin versions. I can confirm that the USB ports work and there is a connection, because flashing a single random .tar file passes and reboots the phone., but does nothing for me (like installing extracted hidden.img.tar). Ends up at the same splash screen.
Every attempt to flash anything has to be with the download mode rebooted or else it doesn't do anything. (Maybe this is normal)
All threads completed. (succeeded 0 / failed 0)
When I flash the AP, BL, CP, after a while (a minute or so) I get a fail without seemingly any progress.
Complete(Write) operation failed
Usually hangs on the recovery.img, depending on what I try to flash.
When I flash CSC, Pit file, or leave a ticked repartition box without including any of them, I instantly get
Re-Partition operation failed.
So naturally this always triggers if I flash all 4 of the items.
I have also tried Smart Switch. The only problem is I currently don't have my S/N number, because some internals and all of the outside of my phone was changed under the insurance, including the back where I believe the number is found, so I've tried S7 Edge S/N number of a friend of mine. I believe our phones are different, because his firmware is from Baltic region (SEB) which doesn't even have 7.0 out. I'll try getting my S/N number through the carrier I bought the phone in. Anyway, Smart Switch throws an error about "Failed to recognize software update mode" after downloading the (SEB region) firmware and stops there. I'm afraid even my own S/N number won't help.
This is what my download mode says
ODIN MODE
DOWNLOAD SPEED: FAST
PRODUCT NAME: SM-G935F
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
FRP LOCK: ON
Secure Download: Enabled
WARRANTY VOID: 0 (0x0000)
RP SWAEV: B:1 K:0 S:0
I feel like all of this mess is caused mostly by the Factory reset prevention lock?
I don't want to trip Knox and void the warranty by installing a custom recovery, which would maybe help me? Does anyone have any ideas? I'm at this for like 10 hours already and desperate. Hope I don't need to give it in. No ability to even turn off the phone, what BS is this...
Can't post images yet, sadly.
same here. but for me now odin say:
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1203)..
<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> sboot.bin
<ID:0/005> __XmitData_Write
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
bassini said:
same here.
Click to expand...
Click to collapse
greenman from sammobile forums suggests
that "This is looking like you have a damaged emmc. The re-partition should have been successful."
I think we're out of luck on this one. The only strange thing is that we've probably installed the same piece of software that killed it. What are the odds?
Rakanoth said:
greenman from sammobile forums suggests
that "This is looking like you have a damaged emmc. The re-partition should have been successful."
I think we're out of luck on this one. The only strange thing is that we've probably installed the same piece of software that killed it. What are the odds?
Click to expand...
Click to collapse
For me it was a newest XEO firmaware.
And also its after trying re-pa...
OK, so have a Galaxy Tab A 10.1, SM T580. An attempt to drop a rom on it failed(not sure why tbh, plugged into the front usb hub instead of unplugging an external HD to free up a usb port, bad rom, not sure), and I am unable to restore it to default. It now goes straight to the 'Use emergency recovery software' screen which doesn't work for that model, and every attempt I have made to utilize Odin has failed, with both 3.09 and 3.13, utilizing XAR-T580UEU2BQF1-20170623075724 files; inevitably it ends up stuck on the 'Initializing' step with no further activity(up to 2 hours anyway).
Requesting some semi-detailed assistance.
Thaser said:
OK, so have a Galaxy Tab A 10.1, SM T580. An attempt to drop a rom on it failed(not sure why tbh, plugged into the front usb hub instead of unplugging an external HD to free up a usb port, bad rom, not sure), and I am unable to restore it to default. It now goes straight to the 'Use emergency recovery software' screen which doesn't work for that model, and every attempt I have made to utilize Odin has failed, with both 3.09 and 3.13, utilizing XAR-T580UEU2BQF1-20170623075724 files; inevitably it ends up stuck on the 'Initializing' step with no further activity(up to 2 hours anyway).
Requesting some semi-detailed assistance.
Click to expand...
Click to collapse
You need to put it in download mode first.
I have done so with every attempt. It still continues to simply hang at 'initializing'.
Thaser said:
I have done so with every attempt. It still continues to simply hang at 'initializing'.
Click to expand...
Click to collapse
Post a screen shot of your download screen and odin log.
ashyx said:
Post a screen shot of your download screen and odin log.
Click to expand...
Click to collapse
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1301)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 22 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:26244/000> Odin engine v(ID:3.1301)..
<ID:26244/000> FAIL open(COM:4)
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Thaser said:
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1301)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 22 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:26244/000> Odin engine v(ID:3.1301)..
<ID:26244/000> FAIL open(COM:4)
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
looks like your baseband got messed up, download this latest firmware for this tablet and install it using Odin
https://samfrew.com/download/Galaxy__Tab__A⑥__/dzjs/LUX/T580XXU4CSA1/T580LUX4CSA1/
zfk110 said:
looks like your baseband got messed up, download this latest firmware for this tablet and install it using Odin
https://samfrew.com/download/Galaxy__Tab__A⑥__/dzjs/LUX/T580XXU4CSA1/T580LUX4CSA1/
Click to expand...
Click to collapse
It remains stuck at initialization, longest time an hour and a half. No response.
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1301)..
<ID:0/005> File analysis..
<ID:0/005> skip file list for home binary
<ID:0/005> param.bin
<ID:0/005> userdata.img
<ID:0/005> Home Binary Download
<ID:0/005> Total Binary size: 2658 M
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
Thaser said:
It remains stuck at initialization, longest time an hour and a half. No response.
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1301)..
<ID:0/005> File analysis..
<ID:0/005> skip file list for home binary
<ID:0/005> param.bin
<ID:0/005> userdata.img
<ID:0/005> Home Binary Download
<ID:0/005> Total Binary size: 2658 M
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
Click to expand...
Click to collapse
use this odin
https://androidfilehost.com/?fid=890129502657595813
also change your usb cable and install Samsung USB drivers from here
https://developer.samsung.com/galaxy/others/android-usb-driver-for-windows
zfk110 said:
use this odin
https://androidfilehost.com/?fid=890129502657595813
also change your usb cable and install Samsung USB drivers from here
https://developer.samsung.com/galaxy/others/android-usb-driver-for-windows
Click to expand...
Click to collapse
Did the above, still no success. Stuck at initialization
Thaser said:
Did the above, still no success. Stuck at initialization
Click to expand...
Click to collapse
Make sure the cable you are using is short and you see the added message in odin.
Long cables will not work.
If the issue still persists and changing USB port doesn't help then trying another pc is the only option.
ashyx said:
Make sure the cable you are using is short and you see the added message in odin.
Long cables will not work.
If the issue still persists and changing USB port doesn't help then trying another pc is the only option.
Click to expand...
Click to collapse
I will second this. My laptop will not see Odin added at all for most of my devices. And out out of like 6 USB cables only 1 works for Odin downloading but good for everything else
Custom Binaries Blocked by FRP Lock
May I start you over with your diagnostics. Not initializing? Does this mean you cannot boot into recovery, at all? But can get into download mode which you cannot use?
Try booting to recovery and tell me if you see little red letters at the top left that say something about FRP lock. If this is your issue I'll explain what's going on with your device.
There are two types of FRP protection I've seen in this tablet. The first one most of us know of and it can be best described as being able to boot or power on compared to the other one which acts similar to a bootloop and does not power on.
This seems to be a common bug with the current Rootings applied to this device that are using CF-Root or a variation thereof. Samsung insisted that CF-Root shouldn't be used on this device and that's where the problem apparently comes from. The device owner is caught in a bootloop type of mode where the logo comes and goes and somehow accessing recovery is impossible. At the top left side of the screen in fine red letters reads, "Custom Binaries Blocked By FRP Lock. " This apparently shuts off the OEM unlock also leaving you with access to the Bootloader/Downloader, but Odin3 would refuse to flash even the official Firmware. Suddenly the impossible Hard-Brick comes to mind. Fortunately for all of us someone invented Odin3 and Samsung device owners rarely have to deal with a hard bricked device..
Here's what you need.:
Odin3.10 to Odin3,13. Either one works. The following file will give you Odin3.13.
The SM-T580 Binary 4 FRP Unlock file can be obtained here (this is a 1.98GB rar file):
https://drive.google.com/file/d/1Rip0qIGo-GbzFdH55s1vIpe6f1aqYKbD/view
Extract the file, preferably to a folder of its own that you create.
Prep device for flashing (boot to download mode), connect to PC and fire up Odin3. The first section should light up blue means you're connected. Click on AP, go to the extracted 3file and doublr click on the file starting with the word "unlock." Wait til Odin does it's checksum and then you can press start.
This will reset your device to factory!!
Now you're going to want to Bypass the Google Account and remove FRP which is the first FRP I mentioned.
Let me know how it goes for you..
Hi guys, I tried to factory reset my phone by flashing the latest firmware. These are the files that I used:
AP_G935TUVSBCTA2_CL14365146_QB28658134_REV02_user_low_ship_MULTI_CERT_meta.tar.md5
BL_G935TUVSBCTA2_CL14365146_QB28658134_REV02_user_low_ship_MULTI_CERT.tar.md5
CP_G935TUVSBCTA2_CP14916856_CL14365146_QB28658134_REV02_user_low_ship_MULTI_CERT.tar
CSC_TMB_G935TTMBBCTA2_CL14365146_QB28658134_REV02_user_low_ship_MULTI_CERT.tar.md5
HOME_CSC_TMB_G935TTMBBCTA2_CL14365146_QB28658134_REV02_user_low_ship_MULTI_CERT.tar.md5
I am a noob and I accidentally flashed the HOME_CSC file in the USERDATA section but every other file was in its place. Then after the successful flash, the phone restarted and entered a boot loop with the galaxy s7 and t-mobile logo. Also, I could't boot into recovery. It shows " recovery booting..." and stays there. After that, I tried to flash several different firmware versions but I always get errors like "fw ver check failed" and stops flashing. I only managed to reflash the first firmware again with success but the phone still doesn't boot. Does anyone know what is causing the problem? Am I using wrong firmware? can anyone help on this?
regards
bassist82 said:
Hi guys, I tried to factory reset my phone by flashing the latest firmware. These are the files that I used:
AP_G935TUVSBCTA2_CL14365146_QB28658134_REV02_user_low_ship_MULTI_CERT_meta.tar.md5
BL_G935TUVSBCTA2_CL14365146_QB28658134_REV02_user_low_ship_MULTI_CERT.tar.md5
CP_G935TUVSBCTA2_CP14916856_CL14365146_QB28658134_REV02_user_low_ship_MULTI_CERT.tar
CSC_TMB_G935TTMBBCTA2_CL14365146_QB28658134_REV02_user_low_ship_MULTI_CERT.tar.md5
HOME_CSC_TMB_G935TTMBBCTA2_CL14365146_QB28658134_REV02_user_low_ship_MULTI_CERT.tar.md5
I am a noob and I accidentally flashed the HOME_CSC file in the USERDATA section but every other file was in its place. Then after the successful flash, the phone restarted and entered a boot loop with the galaxy s7 and t-mobile logo. Also, I could't boot into recovery. It shows " recovery booting..." and stays there. After that, I tried to flash several different firmware versions but I always get errors like "fw ver check failed" and stops flashing. I only managed to reflash the first firmware again with success but the phone still doesn't boot. Does anyone know what is causing the problem? Am I using wrong firmware? can anyone help on this?
regards
Click to expand...
Click to collapse
What country are you in?
cooltt said:
What country are you in?
Click to expand...
Click to collapse
USA
bassist82 said:
USA
Click to expand...
Click to collapse
Oops! Very temperamental phone, the bootloader is locked.
You can only flash the same firmware that was on the device before you started but if not the latest G935T firmware should work.
p. s. Factory reset is an option in the settings menu, there's no need to flash new firmware.
cooltt said:
Oops! Very temperamental phone, the bootloader is locked.
You can only flash the same firmware that was on the device before you started but if not the latest G935T firmware should work.
p. s. Factory reset is an option in the settings menu, there's no need to flash new firmware.
Click to expand...
Click to collapse
I don't know what firmware the phone had installed before. What are my options now? I can't get into recovery menu, only download menu works. Tried already a bunch of different android 8.0 ROMs for g935t but Odin fails to install them. It only works with just one but it goes into boot loop.
bassist82 said:
I don't know what firmware the phone had installed before. What are my options now? I can't get into recovery menu, only download menu works. Tried already a bunch of different android 8.0 ROMs for g935t but Odin fails to install them. It only works with just one but it goes into boot loop.
Click to expand...
Click to collapse
If the phone is a T Mobile device you just need to install a T Mobile firmware from sammobile.
This is the latest for your device (and I'm assuming it is a G935 edge?)....
https://www.sammobile.com/samsung/g...e/SM-G935T/TMB/download/G935TUVSACSI1/297176/
Sammobile is a little slow for non premium members
cooltt said:
If the phone is a T Mobile device you just need to install a T Mobile firmware from sammobile.
This is the latest for your device (and I'm assuming it is a G935 edge?)....
https://www.sammobile.com/samsung/g...e/SM-G935T/TMB/download/G935TUVSACSI1/297176/
Sammobile is a little slow for non premium members
Click to expand...
Click to collapse
I already tried to flash this rom, I downloaded it from a faster source and fails to flash it.
<ID:0/007> Odin engine v(ID:3.1303)..
<ID:0/007> File analysis..
<ID:0/007> Total Binary size: 4575 M
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> NAND Write Start!!
<ID:0/007> SingleDownload.
<ID:0/007> emmc_appsboot.mbn
<ID:0/007> lksecapp.mbn
<ID:0/007> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/007> Removed!!
bassist82 said:
I already tried to flash this rom, I downloaded from a faster source and fails to flash it.
<ID:0/007> Odin engine v(ID:3.1303)..
<ID:0/007> File analysis..
<ID:0/007> Total Binary size: 4575 M
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> NAND Write Start!!
<ID:0/007> SingleDownload.
<ID:0/007> emmc_appsboot.mbn
<ID:0/007> lksecapp.mbn
<ID:0/007> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/007> Removed!!
Click to expand...
Click to collapse
Fail (auth) means your phone is not in download mode or the firmware file is not in the correct box in Odin.
I think you may be better reading a step by step guide on how to flash firmware.
If you manage to flash and get stuck in a bootloop do the following.
1. No matter what the phone is doing just press volume down+home+power (in that sequence)
2. When the screen goes black quickly move your finger to volume up while still pressing home + power. This will boot you into recovery menu.
3. Choose "wipe cache partition" then "reboot system now"
4. Allow phone to go through the first boot up, it could take 10 minutes just leave it until you get the welcome screen.
cooltt said:
Fail (auth) means your phone is not in download mode or the firmware file is not in the correct box in Odin.
I think you may be better reading a step by step guide on how to flash firmware.
If you manage to flash and get stuck in a bootloop do the following.
1. No matter what the phone is doing just press volume down+home+power (in that sequence)
2. When the screen goes black quickly move your finger to volume up while still pressing home + power. This will boot you into recovery menu.
3. Choose "wipe cache partition" then "reboot system now"
4. Allow phone to go through the first boot up, it could take 10 minutes just leave it until you get the welcome screen.
Click to expand...
Click to collapse
When I press volume down+home+power it gets me to a screen says "warning: a custom o/s can cause critical problems bla bla bla..." and underneath it shows these options: 1) Volume up: continue 2) Volume Down: Cancel (restart phone) 3) Home Button: Show Barcode. If I proceed with the 1st option it goes to download mode where I flash with odin. I tried also the combination volume up+home+power with the phone witched off and it shows the message "recovery booting..." on screen with blue text but then it shows the android icon and says" installing system update, then restarts and falls into boot loop again with the samsung logo.
bassist82 said:
When I press volume down+home+power it gets me to a screen says "warning: a custom o/s can cause critical problems bla bla bla..." and underneath it shows these options: 1) Volume up: continue 2) Volume Down: Cancel (restart phone) 3) Home Button: Show Barcode. If I proceed with the 1st option it goes to download mode where I flash with odin. I tried also the combination volume up+home+power with the phone witched off and it shows the message "recovery booting..." on screen with blue text but then it shows the android icon and says" installing system update, then restarts and falls into boot loop again with the samsung logo.
Click to expand...
Click to collapse
Yes that's fine, just keep trying to get it into recovery, it can take a few attempts for recovery to boot successfully.
The locked bootloader models are a nightmare unfortunately but there's lots of info on the forum about all the different issues and how to resolve.
Sometimes the only solution is to try flash the firmware which was there before you did anything to it eventhough there is a newer version.
cooltt said:
Yes that's fine, just keep trying to get it into recovery, it can take a few attempts for recovery to boot successfully.
The locked bootloader models are a nightmare unfortunately but there's lots of info on the forum about all the different issues and how to resolve.
Sometimes the only solution is to try flash the firmware which was there before you did anything to it eventhough there is a newer version.
Click to expand...
Click to collapse
I tried a lot of times already but it finally gets to a point that says "no command" with the android icon on top and if I press some times the volume up/down or home it finally gives some error messages and stuck there. It seems to me that the recovery menu is missing completely for some reason and the second problem is I don't remember which firmware version it had exactly before my attempt to flash another.
Anyone? Do I need a pit file to fix this problem?