Moved a Verizon Galaxy S5 (G900V) onto T-Mobile's network recently and I'm trying to get as close to a stock G900T as possible.
Specific goals are to have functional:
WiFi Calling (primary goal)
LTE (working on OG5, just APN settings)
VoLTE (nice to have)
WiFi Tethering (optional)
The phone is on the OG5 un-rootable version from Verizon, so rooting and/or CWM flashing are out of the question (stupid VZW!).
I have downloaded full stock firmware for the G900V OG5 release, G900T OF6 / OG6 releases, ZIP format system & boot.img for G900T OJ4.
Things I've tried:
ODIN flash custom OG6.tar.md5 by removing all but system.img.ext4 and cache.img.ext4
ODIN flash custom OG6.tar (skipped MD5 step)
ODIN flash combined OG5 firmware + OG6 system/cache
Both produced errors on the phone's display about "sys rev check failed: no version" or "secure check fail: cache", which I read as a compatibility mismatch between the G900V firmware and G900T software.
QUESTIONS:
Will flashing the G900T full package (modem/boot/system/etc.) cause a hard brick (meaning can't even ODIN back to G900V stock)?
Is there a way around the sys rev check or secure check errors?
What is the PIT file and will it help me here?
I created the custom TAR.MD5 files for ODIN using these commands:
tar -H ustar -c system.img.ext4 cache.img.ext4 > OG6.tar
md5sum -t OG6.tar >> OG6.tar
mv OG6.tar OG6.tar.md5
It will hard brick your phone
I can confirm that doing this will result in a hard brick. No power/charging, lightup, boot. Nothing. Im trying to unbrick using unbrick images, but so far to no avail. If anyone has any ideas or advice that would be great.
deleted
Related
Hey guys
After flashing MJ4 modem from official XXUDMJ6 my camera was not able to record any videos anymore.
Gave me an error and force closed a few seconds after pressing on the record button. Also happened with every other camera app.
Found a possible fix that worked for me, you might want to give it a try if you have the same issues.
What to do:
- Flash official untouched XXUDMJ6 firmware with Odin
- Reboot to download mode
- Flash XXUBMJ1 modem (get it here) via Odin 3.09
- Untick "Auto Reboot" and Flash as CP
- After flashing process is finished reboot in download mode again with 3 button combination and flash modem again (you may need to restart Odin and untick Auto Reboot)
- After flashing is done reboot smartphone
- Smartphone will start but will not ask for PIN and will have no connection, also system process will force close
- Reboot to download mode and reflash the whole untouched XXUDMJ6 firmware again
- Reboot, camera should be working now
I flashed Omega v 3.0 after this and camera still works.
Flashing non-hlos from stock mj6 should be a good solution also
Flashing NON-HLOS.bin and modem.bin wasn't enough in my case. Even adding hidden.img.ext4 and multiple factory resets didn't solve the problem and camera and WLAN kept broken.
The only solution was to include boot.img and recovery.img from the unmodified Samsung tar-file.
Create a tar.md5 including the following files:
NON-HLOS.bin
boot.img
cache.img.ext4 <- created by Universal RDLV
hidden.img.ext4
modem.bin
recovery.img
system.img.ext4 <- created by Universal RDLV
DO NOT INCLUDE THE .MDB FILES!!! DO NOT INCLUDE UNMODIFIED system.img.ex4!!!
Use Odin from the RDLV-Bundle to flash that tar.md5 file and you will be fine. I'm on OXAUDMJ6 now with Knox-Flag 0x0 and working root, camera and WLAN.
Additionally I changed my region from XEF (France) to BTU (UK) with "Galaxy CSC Changer" (PlayStore) to match the region of the CSC file - but that step should be optional.
Using the wrong CSC doesn't change the Knox-Flag - I had to do it to change from XEF to BTU, because they are not in the same multi.csc file.
So, I have 2 phones - both are g900v.
one is at 4.4.2 rooted and another one is at 5, non-rooted and I can't root it, and can't downgrade as at fails at [aboot] fused 2 > Binary 1
or with some other error - basically, failing cuz odin is touching on the bootloader piece of it
So, as I understand, rooting at this point would require flashing separately AP CP CSC and Pit
1. how do I produce them?
2. which button/option in odin each file corresponds?
3. would it work better with sdk and push via cmd?
4. any way to extract these files from a stock tar file ALL_VZW_G900VVRU1ANCG_G900VVZW1ANCG_964333_REV00_user_low_ship_MULTI_CERT.tar.md5 ? I extracted files from it, but they don't look like AP CP CSC and Pit - at least don't start with AP CP CSC and Pit, as someone reported they should.
thanks.
I got this S7, wanted to flash 930U firmware to use T-Mobile but a failed flash has me in a boot loop. I fully updated before trying to flash, so it is I assume on the newest bootloader, etc.
I have attempted the newest firmware files that I can find (G930AUCS4BQL1) but am still getting the SW REV CHECK FAIL through Odin.
Are there files available that will fix this, do I just need to wait for them to come out, or have I bricked this thing?
Thanks for any help and have a great day!
Update:
- Using PrinceComsy Odin results in: FAIL! (Auth)
- USB Debugging is OFF and I am unable to boot to change that
- I am leaving the BL file blank in ODIN
perhaps you should try using offcial odin when flashing official images.
try version 3.12.3. whatever you do, don't use the princecomsy version unless for flashing engboot
Hi,
I have my moms SM-A310F
..fool me I forgot to enable OEM before installing TWRP and flashing the latest LineageOS
After a reboot it shows "Custom binary blocked by FRP lock"
After some research I came to the conclusion that only flashing back to the Samsung firmware could save me.
I'm going to use Odin.
My problem is that the firmware provided by samMobile and samfrew both only provide .img and .bin files.
I found out how to convert them over here: [Script][Tool] how to create a tar.md5 file from img For Odin
But which ones do I need to convert? And where do I need to flash tem to in Odin?
I got:
boot.img
cache.img
cm.bin
hidden.img
modem.bin
recovery.img
sboot.bin
system.img
Odin gives me the options to flash:
BL
AP
CP
CSC
USERDATA
I know that I can ignore USERDATA. But what about the others?
Do in need to flash all the files above? And which file goes where?
Thanks a lot, my mom (and I) will be very thankful for your help.. ;-)
just realised that unzipping the .zip file (firmware) on a Mac caused the issue. If I unzip on Windows i get a tar.md5 that I can flash on AP
on Mac unziping gives me a folder with all the mentioned files.
I have a big problem. Please help. I unknowingly disabled developer mode and when I reboot it says "Custom binary blocked by FRP. (boot.img)" or "Custom binary blocked by FRP. (recovery.img)" in recovery. The worst thing is that Odin mode does not recognize the device. I have also installed the latest samsung drivers. But it is useless. My device is J2 Prime or G532F. Please help me...
Due to issues trying to root my phone I was forced to do a factory reset, now I'm trying to reflash the 4.4.2 stock firmware I got from here.
Here's the command line output from odin:
[[email protected] toolsroot]$ ./odin4 -a mainrom/G900VVRU1ANE9_G900VVZW1ANE9_G900VVRU1ANE9_HOME.tar.md5 -d /dev/bus/usb/003/012
Check file : mainrom/G900VVRU1ANE9_G900VVZW1ANE9_G900VVRU1ANE9_HOME.tar.md5
/dev/bus/usb/003/012
Setup Connection
initializeConnection
Receive PIT Info
success getpit
Upload Binaries
aboot.mbn
Fail request receive -5
FAIL! (Auth)
Fail uploadBinaries
Am I making any obvious mistakes, is my phone unsalvageable, or is this faulty firmware?
Did you have the firmware before rooting that you are flashing now? If you don't know, check the screen in recovery mode.