firmware help. sm-s902l (g900v/kltevzw) - Verizon Galaxy S 5 Q&A, Help & Troubleshooting

Hi all. I have been having huge amounts of trouble getting the marshmallow bootloader, and modem on my phone. I have tried to Flash and Odin. I have tried to flash with flash fire. I have tried with TW RP. I always get failure messages. Error messages. Or the phone just boot loops and will not start up. My phone is an SM - s902l, which is Straight Talk's version of the g900v. My bootloader is not locked, I have been flashing ROMs on this thing for years now. Am I not going to be able to get the g900v modem and boot loader on this phone? Are they really two different animals? I would love to be able to flash all of the newly available marshmallow ROMs, but they usually require marshmallow bootloader and modem.Need some help, as I have run into wall after wall on this... Thanks in advance

Also, I cannot download firmware from Sam mobile.com I'm given either an upgrade super member status ship type thing, or nothing else.

Related

S4 DUOS, GT-I9502, can´t finish “Odin updating” even for stock roms

Hi everyone, I´m really pissed about that issue; I´d really appreciate any help and thanks in advance to you all.
Story: I was using Sva´s rom for kitkat, everything normal, then I´ve seen Sasikas´s for lollipop and decided to try it out. I flashed the original firmware and then the custom, both via odin, used them normal as usual. For some reason, I decide to compare the new sva´s, also for lollipop and when I tried to flash, THE ISSUE BEGAN!
Issue: after doing the normal odin process, when the message “complete” shows up and the phone reboots, the bar of updating progress stop about 25% and the phone reboot to the normal mode, but only with a black screen. This is the screen I´m talking about: 3w generacionandroid.com/wp-content/uploads/2014/09/Android_updating.jpg
What I already tried and it didn´t work:
1 – factory reset after the “boot”; I think the problem is that the “system isn´t being write” so …
2 – different roms, both custom and stock; something interesting about this is that the point of the bar that resets the phone varies according to the rom I use, just as follow:
Rom lollipop: at 25% of the bar the system restarts;
Rom kitkat: the bar jumps from 25% to the end and boots the system until Samsung logo. I noticed that the carrier logo sound is cutted in the end.
I can freely install any recovery and enter dl mode.
By the way, the bootloader file must be flashed at pda or bl in odin?
Flash the bootloader file in the BL slot.
about the bootloader...
I´ve installed a bootloader to try the new lollipop in sva´s rom, maybe because of this I can´t flash anymore? I´ve found this info about bootloaders, could someone tell me if I´m thinkg right about it?
"In literal terms, bootloader is code that is executed before any Operating System starts to run. "
This way what I need is a bootloader for kitkat or previous? Where can i find it?
cry for help
almost givin up...
so, happy new year to everyone, I´ll wait until January to check any replies, otherwise selling for parts. ='[.
Shortening: I can enter recovery and dl mode BUT not getting to install roms;
I know I fixed selinux permissions once and installed a bootloader said to be to install a version of lollipop, that´s all new stuff I did.

G900V firmware on my G900A phone

Hei all,
I bought my phone off ebay without realizing that there are different models for different markets. However inside the battery case the model number is SM-G900A. Since I off course wanted the latest android version that my wife has on her G900F I went about googling for a solution. After lots of tries and lots of failures, I eventually managed to root my phone with towelroot. I went on to flash a G900V firmware onto my phone (Don't ask why). Now I have a G900V baseband, bootloader and rom entirely. I then went on to update OTA to end up with Android 6.0.1 version only to realize that it cannot be rooted yet. I then went back to 5.0 in order to root and to install custom Twrp 3.0.2.2 recovery and unlock the bootloader to developer mode using sambootloader unlocker.
My question is this: How the h... was I able to transform my G900A to a G900V model to begin with. This is over a year ago, and I cannot remember how I went about it. What I do remember is that I used ODIN, with a G900V pit file and did a complete wipe checking repartition, nand erase all, phone efs clear, and bootloader update.
Now my follow up question is this: If it was possible to "transform" my G900A into G900V, would it be possible to "transform" it into a G900F model given that the hardware on the phone is identical ? I mean what is it that makes the phone a G900V, G900F, G900A model in the first place ?
Would it be possible to completely repartition the internal memory of the phone and flash a complete G900F package with bootloader, recovery, system, modems etc ?
If you are inclined to answer this with a short no, then please be so kind to explain why my phone now only accepts G900V firmware ?
You have done something very risky
Flashing another phone's PIT is a quick way to hardbrick (*i've done it before. what an argue at the service center!*)
Don't try to convert to a G900F... that's an even more different phone
Simply flash G900A PIT+FIRMWARE
Also, NEVER TOUCH any checkboxes in Odin like nand erase all and phone efs clear! Your phone will never work on cell signal again.
There is no way it should not accept ATT firmware because the signing key is in true ROM on Qualcomm S5s I believe
this is risky and dangerous i know all partitions except bootloaders can be flashed with flashfire on a bootloader unlocked phone but ive never heard of someone flashing bootloaders succesfully i wouldnt attempt it and agree with lightning i do remember g900a and g900v modems seem to be compatible but im dangerously curious can you remeber anything else oja60
[email protected] said:
this is risky and dangerous i know all partitions except bootloaders can be flashed with flashfire on a bootloader unlocked phone but ive never heard of someone flashing bootloaders succesfully i wouldnt attempt it and agree with lightning i do remember g900a and g900v modems seem to be compatible but im dangerously curious can you remeber anything else oja60
Click to expand...
Click to collapse
No, not really. All I can remember is best described in the post above. I bought an S5 from ebay, probably delivered from asia somewhere. The back of the phone said G900A and I was curious as to why I couldn't get any OTA-updates. I the downloaded a G900V pit file and a stock G900V ROM from sammobile, and went at it. After installing it all the phone worked like a charm, so I could then go about rooting and unlocking the bootloader with the above mentioned method.
I have now gotten a hold of a G900F phone which I wanted to begin with. That means I could try the procedure again to see If it's possible to convert the now G900V phone into a G900F in the same way. I need to specify this however: We are not talking about running a G900F ROM on an unlocked G900V bootloader here (That's easy!). This is about converting the whole shambam. What I still haven't gotten an answer to is what makes a G900V a G900V and what makes the other models unique ?
Best regards
OJA

Recovering from FRP Lock, did I brick my phone?

Hi all,
New user here, not much experience rooting or messing with firmware for phones. I was following the guide on how to flash the SM-935U firmware to the verizon model of the Galaxy S7 Edge, and may have bricked my phone. Here's what I did.
Followed the guide to the letter.
Powered off phone, booted to Download mode
Fired up Odin, selected the SM-935U firmware files, and clicked start.
It gave me an Auth error, which research revealed means that I forgot to turn off Reactivation Lock. I figured, "Fine, I'll just disable it. However, I can't get the phone to boot again. Every time I leave download mode, it boots into Android Recovery, where, no matter what I do, it just reboots into Android Recovery. I can't Wipe anything because it can't mount /system - probably due to Reactivation Lock?
I've been research and researching ways around this, and everything I find just points back to flashing it with the stock firmware. But then I read that you can't even do that if Reactivation lock is on, because Odin will still fail with the Auth error. So, I can only get it to boot to recovery mode, and I can't flash it with anything?
I did read somewhere that if I choose to wipe the phone's EFS with Odin that it should override activation lock, but then it clears the phones IMEI, which is an even bigger mess, isn't it?
I feel like I have to be missing something... since it never did the wipe, why is it that I can't get past the recovery mode. Shouldn't I still be able to get into the system somehow?
Does Anyone have any thoughts or suggestions for me? I'd really like to not be stuck with a permanently bricked S7 edge if at all possible....
Solved
Just wanted to post this to help anyone else who might have this issue. Turns out that you can flash the stock firmware, as long as you're flashing at least the same version or newer of the stock firmware as what the phone was running prior to getting stuck in recovery mode. It shows you what version it was running in the recovery mode at the top.
So for me, I googled the exact firmware version that recovery mode said the phone was running, downloaded it, flashed it with ODIN, and it worked just fine. Had to choose to wipe with the recovery mode after I flashed it, but then it booted like normal. - Then I enabled OEM unlocking under the developer menu, and tried flashing the U firmware again with ODIN, and it still failed with the auth error. Huh.
Turns out (maybe I wasn't doing it right or something) that you can't flash older versions of the firmware to the phone. But, as long as OEM unlocking is enabled, you can flash the U (unlocked) version of the current firmware to the phone and it will take just fine. Hint: I was able to determine the "version" number by looking at the last 4-5 characters of the build number... the verizon version I was running for my SM-935V was: VZW-G935VVRU4API3 - So I googled the API3 firmware and found the U (unlocked) version for my carrier (I happen to be using T-Mobile) on this site: https://samsung-firmware.org/model/SM-G935U/ and found the zip file name which was TMB-G935UUEU4API3-20161011161050.zip, googled that, got the rapidgator link, downloaded it, and that flashed just fine to the phone, and now my T-Mobile SIM works perfectly in what was previously the SM-935V, which now identifies as an SM-935U in settings. It's beautiful.
Also, you need the PIT file, but I was able to use the PIT file for the phone model number (again, found at the top of the android recovery menu), which for my phone was: HERO2QLTE_USA_VZW.pit (googled that and got it off androidfilehost) - I was able to use that PIT file for the T-Mobile U version of the firmware and it worked just fine.
Hope this helps someone.

Tracfone SM-S902L: Bad ROM flashes, need to recover stock ROM

Hello all,
I recently discovered that my S5 was only running KitKat despite Marshmallow having been released for it. I checked for OTA updates and it found nothing, so I decided to flash a custom 6.0 ROM onto it (and for some reason I ended up deciding not to make a backup of the phone beforehand, the ultimate mistake).
The problem became that it didn't recognize Tracfone for my service provider and wouldn't connect to the mobile network. I then downgraded it to a 5.0 ROM, and it no longer even recognized the SIM card, saying there was none.
So I tried to flash the original stock ROM a few times, but every time either got errors from ODIN, the phone itself, or the TWRP bootloader.
Long story short, I seem to have screwed up multiple times trying to install a ROM to get around KitKat and now my phone appears to be softbricked. I can get into the TWRP menu and the "download" mode, but when trying to start the phone, it sits on the "Samsung Galaxy S5" screen with the "Set Warrenty Bit : kernel" text at the top left.
I'm just wondering if there's a way to fix it at this point, or if I've completely trashed the phone.
If anybody has suggestions or experience with this, all help is welcome!
Thanks!
MevNav said:
Hello all,
I recently discovered that my S5 was only running KitKat despite Marshmallow having been released for it. I checked for OTA updates and it found nothing, so I decided to flash a custom 6.0 ROM onto it (and for some reason I ended up deciding not to make a backup of the phone beforehand, the ultimate mistake).
The problem became that it didn't recognize Tracfone for my service provider and wouldn't connect to the mobile network. I then downgraded it to a 5.0 ROM, and it no longer even recognized the SIM card, saying there was none.
So I tried to flash the original stock ROM a few times, but every time either got errors from ODIN, the phone itself, or the TWRP bootloader.
Long story short, I seem to have screwed up multiple times trying to install a ROM to get around KitKat and now my phone appears to be softbricked. I can get into the TWRP menu and the "download" mode, but when trying to start the phone, it sits on the "Samsung Galaxy S5" screen with the "Set Warrenty Bit : kernel" text at the top left.
I'm just wondering if there's a way to fix it at this point, or if I've completely trashed the phone.
If anybody has suggestions or experience with this, all help is welcome!
Thanks!
Click to expand...
Click to collapse
Are you sure you have the stock firmware for the 902l and not the 903vl? The reason you didn't get the update for 6.0 is you have the 902l model. If you had the 903vl model you'd have 6.0. Straight talk never released it for the 902l model. No idea why being both models are very similar. Im not sure but if you make it back to stock on kitkat. I think you can use safestrap from the Verizon s5 to use some custom roms that run kitkat. If your bootloader is in fact unlocked and you can install a custom recovery other then safestrap. I believe you can install pretty much anything but I'm pretty sure straight talk ships the phones with the Toshiba chip so the bootloader isn't unlockable

O2U Note 4.... Broken?

So this is a bit of an odd situation my friend is having. He bought his Note 4 off eBay over a year ago, and it was (and still is) a rooted mess. And I mean a big mess. Now I'm trying to help him fix it, because he can't update his phone at all whatsoever from 5.1.1. So I send him 6.0.1 firmware for O2U and have him go into Download mode, odin, all that fun stuff. Download mode says SM-N910T. Settings says SM-N910F. Anyway, he tries flashing the firmware via odin, fails, I have him try multiple things (I'm pretty tech savvy when it comes to this type of stuff) but it always failed. Also, "Current Binary" and "System Status" are both custom, and the KNOX counter is 0x1.
So what I'm asking is, how to fix this problem for him? What steps should he take (or should I help him take)? Is this actually a T-Mobile phone from the USA, but rooted to work with O2 sim cards? The hell is going on here?
Thanks for any replies, and all suggestions will be taken seriously and addressed.
Install the Phone INFO Samsung APK by vndnguyen and see what it's written there.
Get the serial number - example: mine is a 910C with serial RF8H70D.... and so on (obviously I can't write it all here)
With this serial number try with Samsung Smart Switch on the PC and see what info you get. Also you have the possibility to get the latest original firmware installed on the phone.
Good luck.
Gunshots911 said:
So this is a bit of an odd situation my friend is having. He bought his Note 4 off eBay over a year ago, and it was (and still is) a rooted mess. And I mean a big mess. Now I'm trying to help him fix it, because he can't update his phone at all whatsoever from 5.1.1. So I send him 6.0.1 firmware for O2U and have him go into Download mode, odin, all that fun stuff. Download mode says SM-N910T. Settings says SM-N910F. Anyway, he tries flashing the firmware via odin, fails, I have him try multiple things (I'm pretty tech savvy when it comes to this type of stuff) but it always failed. Also, "Current Binary" and "System Status" are both custom, and the KNOX counter is 0x1.
So what I'm asking is, how to fix this problem for him? What steps should he take (or should I help him take)? Is this actually a T-Mobile phone from the USA, but rooted to work with O2 sim cards? The hell is going on here?
Thanks for any replies, and all suggestions will be taken seriously and addressed.
Click to expand...
Click to collapse
Looks like its an refurbished note 4 original motherboard is N910T and faked with N910F software cuz N910F has more value in Market.
So the bottom line is you have N910T Tmobile note 4 and you have to flash N910T firmware but after flash firmware from odin you have to immediately boot into stock recovery by pressing 3 button combo and do factory reset to get clean fresh opreating system otherwise it will get stuck in a bootloop at samsung logo.
First boot after flash and factory reset can take upto 10 minutes.
You can get firmware from www.sammobiles.com/firmwares
Or from link below for faster download.
https://androidfilehost.com/?fid=890129502657581810
Remember once you flash this latest marshmalow firmware there is no way you can ever downgrade to 5.1.1 again.
Good luck
Trex888 said:
Looks like its an refurbished note 4 original motherboard is N910T and faked with N910F software cuz N910F has more value in Market.
So the bottom line is you have N910T Tmobile note 4 and you have to flash N910T firmware but after flash firmware from odin you have to immediately boot into stock recovery by pressing 3 button combo and do factory reset to get clean fresh opreating system otherwise it will get stuck in a bootloop at samsung logo.
First boot after flash and factory reset can take upto 10 minutes.
You can get firmware from www.sammobiles.com/firmwares
Or from link below for faster download.
https://androidfilehost.com/?fid=890129502657581810
Remember once you flash this latest marshmalow firmware there is no way you can ever downgrade to 5.1.1 again.
Good luck
Click to expand...
Click to collapse
Thanks so much! Everything is flashing on his phone right now like it should be. Appreciate it a bunch!
I also used samsung-firmware.org. I would use sammobile but I only had enough on my card for a 48 hour upgrade.

Categories

Resources