I've got a Tracfone Galaxy S5 SM-S902L that I previously had Lineageos 15.1 up and running on, but it had the issue with some bluetooth devices that I understand is an issue with Lineageos 15.1. We were going to give the phone to our son, but I wanted to "roll it back" to Lineageos 14.1, which doesn't appear to have that issue.
I have flashed a couple of different ROMs (Resurrection Remix, and the afforementioned Lineageos 14.1) being the main ones tried, with a foray back to 15.1, but the phone is stuck on the boot-up animation and never gets past that, no matter which one I try. I've done the standard wipe, flash the ROM, flash GAPPS, flash SuperSU routine, and still no luck.
One gotcha I need to make clear is that the SD card slot on this phone is inoperable for some reason (gifted to us phone). So, I didn't have the storage space (via a MicroSD card) to run a Nandroid backup like I have run on my Galaxy Note 3.
In the process of trying to flash the different ROMs, the last time I tried, I apparently did what I later saw described as a "super wipe", and I think I've wiped the firmware from the phone.
In an attempt to roll back to the stock ROM, I have gone to sammobile.com and looked up the SM-S902L. Go through the process of getting the download link. Click on the download link (after the 30 second advertisement delay), and get the dreaded "404 we can't find it" error message.
So, does anyone have a link to the stock Tracfone firmware and/or ROM for the SM-S902L, or a link to a Verizon-model ROM and firmware that from what I've read will work with this particular model? If you do, I would be very appreciative. If you can even tell me which Verizon model I would need to look for, I would be grateful.
Related
Hello! Recently T-Mobile launched MM 6.0.1 for the Galaxy Note 4. I was originally running CM Remix, that was meant for the international version of this device, and all but sim card did not work, (I don't have this device activated, I just use it on the side). When I got bored of the CM Remix I just went to Samsung Kies, and restored the phone to its factory default. When I finished setting up the phone I was pleased to find that I was running 6.0.1, as opposed to 5.1.1. All good? No! I have used Odin to put on the latest version of TWRP recovery, and i flashed v2.76 of SuperSU. All works well in terms of rooting and flashing files, but here is my big issue. NO MATTER WHAT rom that I flash on this damn phone, wifi doesnt work, nor do the service bars show I have signal. I have flashed 6 different roms, and all of them have to same issue, stock 4.4.4, 5.0, 5.11 CM 12,12.1 13, Ressurection Remix. The only thing holding me together is my TWRP nandroid backup that i revert to after every rom I flash. In settings, my phone just says "Turning wifi on" and it stays there. SO WHAT THE @#$% IS GOING ON? Is this something T-MObile implemented when it did the update on my N4, I restored to 5.1.1 with kies all the time before this and after each time, i flashed roms with no issue. Can someone please point me in the right direction here, am I doing something wrong? Is something patched that wasn't previously? WHAT CAN IT BE?
Hi guys. I very narrowly (somehow) managed to recover from almost bricking my phone.
I successfully S-Off'd my phone, and previously successfully installed TWRP. I tried to install this ROM:
https://forum.xda-developers.com/ve...m-perfumewl-m60-dev-edition-unlocked-t3442969
When I tried the to flash the ZIP for firmware and for the ROM, the firmware wouldn't install. I tried some other stuff and basically almost bricked my phone. Some how got it to suddenly start being able to use the htc_fastboot commands (????????) and was able to start installing the zip for stock... but it ran an error, I ran it again and it froze... then I forced my phone to reboot and somehow I'm back to having a stock system. No clue what I did.
My question is, can I take a software update on my phone normally (to 7.0) , and then install just that ROM? Or so I need to flash the firmware separately with a command line command? I just don't want to give myself another heart attack tonight. Current firmware version is 1.82.605.6, not rooted, don't believe my recovery is TWRP right now (but I know how to install that one).
I'm just looking for root access and the ability to remove pre-installed Verizon crap (VZW Messager, My Verizon, etc). Thanks guys.
CritKlepka said:
Hi guys. I very narrowly (somehow) managed to recover from almost bricking my phone.
I successfully S-Off'd my phone, and previously successfully installed TWRP. I tried to install this ROM:
https://forum.xda-developers.com/ve...m-perfumewl-m60-dev-edition-unlocked-t3442969
When I tried the to flash the ZIP for firmware and for the ROM, the firmware wouldn't install. I tried some other stuff and basically almost bricked my phone. Some how got it to suddenly start being able to use the htc_fastboot commands (????????) and was able to start installing the zip for stock... but it ran an error, I ran it again and it froze... then I forced my phone to reboot and somehow I'm back to having a stock system. No clue what I did.
My question is, can I take a software update on my phone normally (to 7.0) , and then install just that ROM? Or so I need to flash the firmware separately with a command line command? I just don't want to give myself another heart attack tonight. Current firmware version is 1.82.605.6, not rooted, don't believe my recovery is TWRP right now (but I know how to install that one).
I'm just looking for root access and the ability to remove pre-installed Verizon crap (VZW Messager, My Verizon, etc). Thanks guys.
Click to expand...
Click to collapse
I recommend you install this one instead:
https://forum.xda-developers.com/ve...m-1-85-605-9-aroma-root-root-debloat-t3529732
Follow instructions in OP...or:
1)fastboot flash FW w/o Boot w/ TWRP (htc_fastboot oem rebootRUU, fastboot flash zip...)
2)htc_fastboot reboot-bootloader
3) Finally, go into recovery-- backup and flash ROM (choose root w/ Magisk and debloat)
Thanks, I figured out why it wasn't working before. Used official TWRP, thats why it wasn't working. Wouldn't have thought that'd made that much of a difference.
New problem though; something I really would like to use the Google versions of contacts and dialers. Trying to flash those just made my phone app unusable. So I turned to LineageOS but it REFUSES to boot. Hangs on their little vertical line with a moving circle. Found out AOSP roms don't like VZW firmware? Flashed global firmware, updated through WiFi as much as possible, and then ran into issues with radio, even though I flashed the VZW one. So I reverted those changes, am going through with what you said above to have a working phone (after not having one all day), but any advice on getting Google dialer and contacts? I'd like to use LineageOS but I couldn't get it work at all.
CritKlepka said:
Thanks, I figured out why it wasn't working before. Used official TWRP, thats why it wasn't working. Wouldn't have thought that'd made that much of a difference.
New problem though; something I really would like to use the Google versions of contacts and dialers. Trying to flash those just made my phone app unusable. So I turned to LineageOS but it REFUSES to boot. Hangs on their little vertical line with a moving circle. Found out AOSP roms don't like VZW firmware? Flashed global firmware, updated through WiFi as much as possible, and then ran into issues with radio, even though I flashed the VZW one. So I reverted those changes, am going through with what you said above to have a working phone (after not having one all day), but any advice on getting Google dialer and contacts? I'd like to use LineageOS but I couldn't get it work at all.
Click to expand...
Click to collapse
You've got to read OPs, search threads, etc. Some ROMs work w/ our phone, and some do not. Check out the latest versions of ice and leedroid. Your most likely want to grab the SVN versions is the official versions may not yet support Verizon N firmware
Antny6 said:
You've got to read OPs, search threads, etc. Some ROMs work w/ our phone, and some do not. Check out the latest versions of ice and leedroid. Your most likely want to grab the SVN versions is the official versions may not yet support Verizon N firmware
Click to expand...
Click to collapse
I have been doing a lot of searching, but I've found so many different, conflicting sources of information. For example, one website told me to install LineageOS, was to be on latest Verizon OTA and just normally flash it; that obviously didn't work.
So from what I can see, our choices are Viper, Ice, LeeDroid, NuSense and the one you linked. I'm going to try out LeeDroid... out of curiousity, is there any reason, for example, LeeDroid or Ice haven't posted in this Verizon section with links to their ROMs?
*Edit Two* Dialer wouldn't work out of the "box" so to speak, so I had to go to Phone settings at the bottom, there is a menu called Calling Accounts. Had to go there and tap Receive Incoming Calls... why is that disabled in the first place..? But that seems to be an issue going even as far back as the Nexus 5. But that's how you find the option in the HTC 10 for anyone who comes across this issue too...
Not sure why your having issues with the flashing. Are you doing a full wipe? Not just factory reset. Going from stock to lineage requires a complete format of internal SD card. On the stock roms, most will ask if you are still on marshmallow firmware & are working fine. Again, we need more info on what firmware version your on, version of twrp& how your wiping your device. Most AOSP roms work, but no advanced calling
LOS ROMs will work without issue IF you have flashed the US unlocked firmware at some point in time. This is the only information that we have found from a VzW device with LOS booting and VzW device without. We started a thread awhile ago and is the only known method we currently know of to get LOS booting. Also works for Sprint users.
https://forum.xda-developers.com/verizon-htc-10/how-to/how-to-cm-booting-vzw-vzw-firmware-t3500900
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
Hi...
So as of last night my phone doesn't have sound. I've been flashing roms/gapps all day yesterday and today I figured I'd settle on a rom for now given that my model is sparse for roms that actually work.
Having no sound started with putting LineageOS 15.1 on my phone (Oreo) which was working previously so I don't know what happened, so I tried to flash LineageOS 14 / CM 14 (individually) on my phone and LineageOS worked but without audio and I believe CM 14 either kept crashing and/or also had no audio. I then flashed Resurrection Remix Oreo for my phone as I remember in the past the audio worked fine, again it doesn't.
Before the events above, like I said, I had been flashing numerous roms on my phone, lots of the roms either worked for a few minutes and while updating Google Play they would crash or the rom would be stuck at its boot screen.
I've also been flashing a modem on my phone, through Odin, because some Kitkat and Lollipop roms I got didn't have working WIFI. I noticed with that, that the roms would work for a few minutes then crash (maybe because I was trying to use a 5Ghz network?)
I was also trying to flash custom kernels and even though they would say they flashed successfully I'd be stuck at the boot screen that said "Samsung Galaxy Note 3" with it also saying the Kernel or Recovery isn't SEandroid Enforcing.
(I've also been switching between TWRP 3.2.1.1 and 2.8.7.0 because roms with "Aroma installer" would crash TWRP 3.2.1.1)
I'm quite the novice at all this, and maybe it shows? I'd just like my audio back and it's quite evident that flashing roms isn't the solution I had hoped it to be.
Flash the latest stock ROM for your phone to see if everything goes back to normal.
I'm not sure what the latest stock rom would be. My phone originally had lollipop on it which had samsung's touchwiz.
sammobile or updato.com for firmwares .
Okay, thank you. I'm downloading one now. Does choosing the correct carrier matter? I ask because I'm not sure who the original carrier is and the phone is also unlocked and since it is, I would think that choosing a specific carrier doesn't matter.
I flashed the original firmware and got sound on my phone again, and just now as I type, I got finished re-rooting and putting TWRP on my phone and flashed RR Oreo and I have sound.
This is all so very interesting and I can't help but wonder why I lost sound to begin with. Any thoughts?
Bad download or flash or wrong file for model are usual whys.
Oh, I see.
Well, my model is a sm-n900w8 and when searching for roms specific to that one, I've encountered some people saying, on this very site, that the sm-n900w8 is a Canadian model and it isn't widely supported, but went further to speculate that roms that work with the sm-n9005 should work with the sm-n900w8. I even found a forum post about a kernel that helps give compatibility for n9005 roms to n900w8 roms. I'm not sure if "compatibility," is the right word to use, but I hope you get what I mean.
Personally, every time I go to flash a rom, TWRP says it is successful but when I actually reboot my phone it gets stuck on the logo screen, usually with the text "Kernel is not SEandroid Enforcing" and I've even had similar text with 'recovery' instead of 'kernel' pop up.
hey, ive been crushing on this for half a day: I have a note3 n900t and am trying to get lineage on it. the rom is installed, but it wont read the sim. The sim works in other phones. the sim worked on the stock rom. I tried the reddit thread of flashing a diff baseband/modem, but it wont take, even tho odin says it succeeds. the lineage addon wont root it, so this might be part of it. thoughts?
its worth noting I never got heimdall working either, I used download mode to flash latest twrp, then used that to flash the rom.
Try the forum for your model .
https://forum.xda-developers.com/showthread.php?t=2574886