Database Users

[q] unable to start - urgent help please

HI
As of y'day i had Revosoft latest firmware and having problems with Samsung Galaxy S5 Live wallpapers.
Suddenly phone freezes, removed battery and this is what I did and what happens
First, reloaded Revosolft = It goes up to the logo then freezes
I have
1) wiped EVERYTHING (data, system, cache dalvik) and reloaded a few firmwares FIRST VIA RECOVERY (such as Omega v17, V20, Revo, Bat, AICP, =
While loading the rom i get the errors
E: Failed to Mount /efs(invalid Argument
E: Failed to Mount / efs(invalid Argument)
then after loading the rom i get W: Failed to verify - whole file signature - AND 3 OTHER LINES AROUND THE SAME TYPE.
THEN it starts go thru ALMOST (I BELIEVE, NOT SURE) the full Samsung logo and tune AND IT FREEZES
2) Used DOWNLOAD METHOD AND LOADED SEVERAL ROMS FROM SAMSUNG-FIRMWARE SITE. SAME
3) Used DOWNLOAD AND ADDED THE PIT FILE - SAME RESULT - UP TO LOGO AND TUNE AND FREEZE
4) Installed TEAMWIN recovery, wiped EVERYTHING AND REINSTALLED ALL THE ABOVE mentioned ROMS - same result - UP TO LOGO AND TUNE AND THEN FREEZE
PLEASE PLEASE SOMEONE WITH A BIT MORE IDEAS TO HELP ME, I don't think it is completely bricked but at 70, disable after a full WHITE NIGHT, I am losing faith in me
Any one? PLEASE? MUCH APPRECIATED

more troubles?
So i found a suggestion to download an efs.tar file and load it -
Downloaded "efs-1.34-pkg" and started odin
XCEPT now Odin reads
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> pkginfo/MANIFEST.efs
<ID:0/004> NAND Write Start!!
.
AND IT'S BEEN THERE FOR A WHILE NOW =- WHAT TO DO =
exlaval said:
HI
As of y'day i had Revosoft latest firmware and having problems with Samsung Galaxy S5 Live wallpapers.
Suddenly phone freezes, removed battery and this is what I did and what happens
First, reloaded Revosolft = It goes up to the logo then freezes
I have
1) wiped EVERYTHING (data, system, cache dalvik) and reloaded a few firmwares FIRST VIA RECOVERY (such as Omega v17, V20, Revo, Bat, AICP, =
While loading the rom i get the errors
E: Failed to Mount /efs(invalid Argument
E: Failed to Mount / efs(invalid Argument)
then after loading the rom i get W: Failed to verify - whole file signature - AND 3 OTHER LINES AROUND THE SAME TYPE.
THEN it starts go thru ALMOST (I BELIEVE, NOT SURE) the full Samsung logo and tune AND IT FREEZES
2) Used DOWNLOAD METHOD AND LOADED SEVERAL ROMS FROM SAMSUNG-FIRMWARE SITE. SAME
3) Used DOWNLOAD AND ADDED THE PIT FILE - SAME RESULT - UP TO LOGO AND TUNE AND FREEZE
4) Installed TEAMWIN recovery, wiped EVERYTHING AND REINSTALLED ALL THE ABOVE mentioned ROMS - same result - UP TO LOGO AND TUNE AND THEN FREEZE
PLEASE PLEASE SOMEONE WITH A BIT MORE IDEAS TO HELP ME, I don't think it is completely bricked but at 70, disable after a full WHITE NIGHT, I am losing faith in me
Any one? PLEASE? MUCH APPRECIATED
Click to expand...
Click to collapse

flash touch philz Recovery via Odin
then wipe data & cache & dalvik
then reboot
while on boot screen remove the battery and put it again
go to download mode and flash the firmware

thanks not yet
followed step by step - still stuck at samsung white logo with blue flashing -
RubbaBand said:
flash touch philz Recovery via Odin
then wipe data & cache & dalvik
then reboot
while on boot screen remove the battery and put it again
go to download mode and flash the firmware
Click to expand...
Click to collapse

[Q] Please help me unbrick my s4 TB bricked CWM can't help.

Hi everyone.
What happened to my phone is the weirdest thing and so far it seems nothing can work to fix it.
It's a GT-i9500 international model. Rooted and with KitKat 4.4.2.
How I messed things up:
- Was in Titanium Backup, tried to convert one game app I previously made "system app" back to "user app". The process was taking over 20 minutes... I figured must be some kind of a freeze. Then I held the power button to shut it off.
- I then powered on again, and realized that the device is not booting! There was no "Samsung" logo.
How I tried to fix it:
- I went to the CWM recovery and tried installing my latest backup (with a custom ROM). Did that after wiping all cache (with dalvik included) and data wipe system restore in CWM. After restoring the device that way -> It boots to "samsung" animation where it stays and gets warm when left for over an hour.
- I went back to CWM this time tried to flash the custom ROM again - so I picked the custom ROM zip file after wiping cache/system restore in CWM again and waited till it finishes. Rebooted the device -> It boots to "samsung" animation where it stays and gets warm when left for over an hour.
- Again in CWM tried to this time restore the stock rom which I have backed up with CWM after I have rooted the phone. -> The weirdest thing happened after restore. The phone booted into the carrier "boot animation", then it showed "Samsung gt-9500" (first time ever I've seen this screen on this device, it was never shown before), then it went once more to "samsung" letters being lit (but without the "samsung" boot animation with that purple thing and sound).
- I tried formatting the partitions within CWM except for the EFS and external SD partition and repeating each of the above all to no avail.
When I returned the stock firmware in third example (it was stock, but that backup made by CWM recovery ofc) CWM asked on reboot if I want to get back to stock recovery, I said no since I don't want to lose CWM esp now that the phone doesn't work as it should.
Currently I'm trying to:
- Flash stock firmware with ODIN through the download mode. Sadly so far I've seemed to have downloaded the Jelly Bean ROM instead of KitKat for it because ODIN gave me (nand write) error on flashing PDA and device showed:
check fail device:3 binary:2
So yeah, downloading firmware and will try ODIN with the KitKat one (the other I tried with ODIN didn't have version written in so that's why I assumed it must be KitKat too, took it from XDA guide, but seems it was JB after all).
I also want to stress that all previous steps in CWM were all done using KitKat builds so that couldn't be the problem.
So any of you have any idea what's going on with my phone?
I find it really weird that CWM which is supposed to restore phone in case of emergencies like this failed to do so. Perhaps nandroid backup would be a better choice next time? What do you think?
EDIT:
OMG this seem bad. Tried to flash through ODIN with another ROM and this is what I got:
<ID:0/007> Added!!
<OSM> Enter CS for MD5...
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9500XXUFNC1_I9500YDDFNC2_I9500DDUFNA4
<OSM> Checking MD5 finished sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialization..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> sboot.bin
<ID:0/007> NAND Write Start!!
<ID:0/007> param.bin
<ID:0/007> boot.img
<ID:0/007> recovery.img
<ID:0/007> system.img
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<ID:0/007> Added!!
<OSM> All threads completed. (Succeed 0 / failed 1)
---
Interestingly after this - now I don't have Chinese "download" mode anymore (the phone was bought through a friend and worked for over a year fine rooted btw) now it's in English... and, if I just try to boot it it says nicely:
"Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
It would also seem recovery is gone too now... :/
hmm...
EDIT2:
Tried a different USB cable - same result.
Tried Odin 3.10 - same.
EDIT3:
WOW... the strangest thing!
So... after reading tons of threads I have found a suggestion to change the USB port. So I did (from USB 2.0 on my laptop to a USB 3.0 one if that matters). That's on org Samsung USB cable + reinstalled USB drivers to latest + ODIN 3.10. And then... it worked. Instead of "fail" on "system.img" this time it showed progress on the "system" stage. After a while it DID finish with a "PASS".
Next boot I was told that "Device memory damaged" and asked to factory reset it. Which I did. Next boot - Booted the first run settings and the system... next boot - booted the "Black Edition" (with different boot animation sound and then theme) and it's working now fine O_O will proceed to root it and then take care of everything again discarding the old backups and backing up stuff again.

[Q]Flashing Lollipop help

i have been trying to install stock Lollipop on my device. i have followed both http://www.androidpit.com/how-to-get-android-5-0-lollipop-on-the-galaxy-note-3 and http://techbeasts.com/2015/02/14/update-galaxy-note-4-n910f-android-501-lollipop-official/ to the letter. This is also my fourth or fifth time using Odin. Every attempt has failed. i have tried Odin 3.10, 3.09, and 3.07 and got the same results:
Code:
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> sbl1.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
My phone's download screen gave thisd message:
Code:
Secure Check Fail : sbl1
until i switched from "N9005XXUGBOB6_N9005XEOGBOA4_XEO" to "N9005XXUGBOA5_N9005XEOGBOA4_XEO" and also freezing any anti-theft app that may be locking my device somehow. Now the screen says:
Code:
Secure Check Fail : aboot
i am rooted (running Omega 24) and to be sure, i re-flashed auto-root
i have tried 4 different USB cables
No USB hubs, i am connected directly to my PC
Firewall, AntiVirus, and Anti Malware software are all off.
i have run Odin as admin
Reactivation Lock is not ticked
Some other things me screen says that may be of some help are:
Code:
QUALCOMM SECUREBOOT: ENABLE
followed by some coupling of letters and numbers and:
Code:
Write Protection: Enable
i am hoping that a factory reset can be my very last resort. i am contemplating reflashing my current Omega ROM and then retrying this.
Any ideas?
EDIT: Factory Reset did not change anything

Is your device unlocked or branded?

Joku1981 said:
Is your device branded or unlocked?
Click to expand...
Click to collapse
It should be unlocked. i unlocked it a while ago when i flashed my first ROM. i have been flashing Omega roms ever since. i cannot imagine my phone would lock itself back up...

billybag said:
It should be unlocked. i unlocked it a while ago when i flashed my first ROM. i have been flashing Omega roms ever since. i cannot imagine my phone would lock itself back up...
Click to expand...
Click to collapse
Odin gave you fail in the NAND. This mean that you have lost plenty of files in EFS. Try to restore your OMEGA backup.

Joku1981 said:
How you unlocked it? By IMEI or other method?
Click to expand...
Click to collapse
Damn, i don't remember. It seemed so long ago. i don;t suppose there is a way to check...
EDIT: while attempting a restore of a nandroid backup, i noticed something. The following backup files were missing:
.android_secure.vfat.tar and
.android_secure.vfat.tar.a

i REALLY appreciate your time and help, by the way. This is so frustrating. One person told me that they repartitioned and selected bootloader when they flashed, but was not advising me to do so.

billybag said:
i REALLY appreciate your time and help, by the way. This is so frustrating. One person told me that they repartitioned and selected bootloader when they flashed, but was not advising me to do so.
Click to expand...
Click to collapse
Do you have any EFS backup?

billybag said:
i REALLY appreciate your time and help, by the way. This is so frustrating. One person told me that they repartitioned and selected bootloader when they flashed, but was not advising me to do so.
Click to expand...
Click to collapse
If you want to flash stock LP, I would just bite the bullet and do it and first get a working system. Then install Recovery and re-root - I use TWRP.tar file so I can flash it in Odin and the SuperSU zip file that I then flash in Recovery.
You don't say which N3 you have but are you sure you have the right ROM for it?
Did you turn off the phone and remove the battery for a bit THEN go into download mode?
Are you using v3.09 of ODin PC?
I've done mine twice for other reasons since LP came out - I untick the auto-reboot so after I flash the stock firmware I can flash TWRP - then it's boot into Recovery and install my custom ROM (I use Temasek's CM12) PA GApps and the SuperSU.zip, then set up the phone - usually I then Restore only Data from my latest TWRP backup but on occasion I've DL'd Titanium from Ply and used that to Restore my apps from extSD.

Journyman16 said:
If you want to flash stock LP, I would just bite the bullet and do it and first get a working system. Then install Recovery and re-root - I use TWRP.tar file so I can flash it in Odin and the SuperSU zip file that I then flash in Recovery.
You don't say which N3 you have but are you sure you have the right ROM for it?
Did you turn off the phone and remove the battery for a bit THEN go into download mode?
Are you using v3.09 of ODin PC?
I've done mine twice for other reasons since LP came out - I untick the auto-reboot so after I flash the stock firmware I can flash TWRP - then it's boot into Recovery and install my custom ROM (I use Temasek's CM12) PA GApps and the SuperSU.zip, then set up the phone - usually I then Restore only Data from my latest TWRP backup but on occasion I've DL'd Titanium from Ply and used that to Restore my apps from extSD.
Click to expand...
Click to collapse
That is what i am having problems with. i know how to flash custom roms. i was also able to flash stock KK when it came out. It is stock lollipop that i cannot get to flash. i am using an SM-n9005 (tmobile). i am going to try different firmware downloads (CSCs) and see what that does.
Also, i have tried Odin versions 3.07, 3.09, and 3.10

billybag said:
That is what i am having problems with. i know how to flash custom roms. i was also able to flash stock KK when it came out. It is stock lollipop that i cannot get to flash. i am using an SM-n9005 (tmobile). i am going to try different firmware downloads (CSCs) and see what that does.
Also, i have tried Odin versions 3.07, 3.09, and 3.10
Click to expand...
Click to collapse
Do you know your original firmware? I'm wondering because some versions have different sized partitions and flashing another type causes fails. i.e. I had a HK S3 and had to flash a PIT file before I could use European firmware. Might it be something along those lines?

Have practically the same situation...
The furthest I've got is the following
Code:
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sbl1.mbn
<ID:0/003> aboot.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sdi.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
But again, with any version of odin and any firmware (lollipop or kitkat) i'm trying to flash, it stucks with
Code:
<ID:0/003> Complete(Write) operation failed.
PS I also have
Code:
QUALCOMM SECUREBOOT: ENABLE
Write Protection: Enable
and my phone was originally locked to spanish vodafone.

Sorry for the delay. i just got around to giving it another shot and it worked. i found an official, made for TMOBILE, version of the firmaware.
Code:
N900TUVUFOB6_N900TTMBFOB6_TMB
for anyone else that may be having trouble. You can find it here: http://www.sammobile.com/firmwares/download/43850/N900TUVUFOB6_N900TTMBFOB6_TMB/
i was using n9005 firmwares, which is usually fine except int his case i needed a tmo one.
Thanks again for everyone's input. Hopefully this post can help someone else out now.

Reflashing stock rom

I have a Samsung galaxy J5 (2016, SM-J510FN/DS) whose OS I carelessly deleted (while not having a backup nonetheless ) while fixing a boot loop issue. I managed to reinstall Android 6.0 (Marshmallow) from opengapps.org (Arm architecture, 6.0 Android, Full version). The install was successful (I used TWRP to reinstall from my SD card) but I am now stuck on the boot loop. The phone either stays stuck on the Samsung logo or boots into recovery. I have wiped the Davik cache and performed a factory reset with success but I am still getting stuck on this boot loop. I have reinstalled the OS a few times but it #1 fails on zip verification and #2 repeats the boot loop after zip verification is turned off. I have a feeling that this is probably the root of my problem, however, my tool box of solutions is spent. I respectfully ask for assistance from more knowledgeable individuals and offer my thanks in advance.

mrnice10033 said:
I have a Samsung galaxy J5 (2016, SM-J510FN/DS) whose OS I carelessly deleted (while not having a backup nonetheless ) while fixing a boot loop issue. I managed to reinstall Android 6.0 (Marshmallow) from opengapps.org (Arm architecture, 6.0 Android, Full version). The install was successful (I used TWRP to reinstall from my SD card) but I am now stuck on the boot loop. The phone either stays stuck on the Samsung logo or boots into recovery. I have wiped the Davik cache and performed a factory reset with success but I am still getting stuck on this boot loop. I have reinstalled the OS a few times but it #1 fails on zip verification and #2 repeats the boot loop after zip verification is turned off. I have a feeling that this is probably the root of my problem, however, my tool box of solutions is spent. I respectfully ask for assistance from more knowledgeable individuals and offer my thanks in advance.
Click to expand...
Click to collapse
1) Boot in TWRP.
2) Wipe /system, /data, /cache & /dalvik-cache.
3) Power off the phone.
4) Reflash stock ROM with Odin.

#Henkate said:
1) Boot in TWRP.
2) Wipe /system, /data, /cache & /dalvik-cache.
3) Power off the phone.
4) Reflash stock ROM with Odin.
Click to expand...
Click to collapse
Do just like he said, Wiping is not totally required just make sure you perform factory data reset from stock recovery.

#Henkate said:
1) Boot in TWRP.
2) Wipe /system, /data, /cache & /dalvik-cache.
3) Power off the phone.
4) Reflash stock ROM with Odin.
Click to expand...
Click to collapse
unfortunatly, I've tried this multiple times and still cannot get it out of the boot loop. I'm not booting back into recovery but rather to the Samsung logo now.

Wizardlysense said:
Do just like he said, Wiping is not totally required just make sure you perform factory data reset from stock recovery.
Click to expand...
Click to collapse
I've done this as well with no success.

And if you are not waiting for the necessary time you need to load the system? .. since after installing the stock you have to leave this in the samsung logo about 10 to 20 minutes at least

One thing to note is that you should be flashing AP, BL, CP, and CSC, and not the HOME package only (not sure if your variant has it in the first place!). Also, ensure that the "NAND Erase All" option is ticked before performing the flash.

thank you, I have not tried ticking nand flash before but I will try it.

Wizardlysense said:
Do just like he said, Wiping is not totally required just make sure you perform factory data reset from stock recovery.
Click to expand...
Click to collapse
This is what I'm seeing on Odin
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1
I have switched from Odin 3.12 to 3.04 and tried different stock files but no success yet.

mrnice10033 said:
This is what I'm seeing on Odin
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1
I have switched from Odin 3.12 to 3.04 and tried different stock files but no success yet.
Click to expand...
Click to collapse
Are you sure you have got the correct files for your device? Usually, when it errors out at aboot.mbn it is because the files are for another device/variant. What's your device model? I will try downloading for you the stock files and see whether it is successful.
P.S. Just saw that you noted your device model in the OP. Sorry about that! Give me a moment and I will get the files for you!

https://drive.google.com/drive/folders/0B8346PsUO8X8cUE1QkZMOGI2SmM?usp=sharing
Try this!

Rizzed said:
Are you sure you have got the correct files for your device? Usually, when it errors out at aboot.mbn it is because the files are for another device/variant. What's your device model? I will try downloading for you the stock files and see whether it is successful.
P.S. Just saw that you noted your device model in the OP. Sorry about that! Give me a moment and I will get the files for you!
Click to expand...
Click to collapse
Thank you so much. I appreciate it.

SM-G935T bootlop after succesful flash with odin

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?