Database Info

Can not connect to the camera. Still no solution? CM10.0.

Hi, I can't seem to find my way around this issue. Every time I try to open any camera app, it doesn't allow me and says it's unable to connect. Is there no sure solution to this yet? I tried flashing new cameras through recovery. Nothing works at all. I have tried flashing fixes from several threads on a clean start, different camera apps, clearing caches, clean wiping, and other things I can't even remember at this point with all the frustration. What's up with this?
TW based ROMs work. AOSP seems to not. I lost the thread explaining how to dial the codes into a TW based ROM, but another problem with this for me is, I am extremely confused as to how to do some of the steps explained in that thread (hence why I closed it, looks like that should be the way out for me though?).

Same problem
CZory91 said:
Hi, I can't seem to find my way around this issue. Every time I try to open any camera app, it doesn't allow me and says it's unable to connect. Is there no sure solution to this yet? I tried flashing new cameras through recovery. Nothing works at all. I have tried flashing fixes from several threads on a clean start, different camera apps, clearing caches, clean wiping, and other things I can't even remember at this point with all the frustration. What's up with this?
TW based ROMs work. AOSP seems to not. I lost the thread explaining how to dial the codes into a TW based ROM, but another problem with this for me is, I am extremely confused as to how to do some of the steps explained in that thread (hence why I closed it, looks like that should be the way out for me though?).
Click to expand...
Click to collapse
I am having the same problem you are. I am running paranoid android and cant get the camera / gallery to work. I hope somebody can help. I had it working on Beans rom build 13 but that is TW. I am going to have to bail on pa if there isn't a fix

bmanderle said:
I am having the same problem you are. I am running paranoid android and cant get the camera / gallery to work. I hope somebody can help. I had it working on Beans rom build 13 but that is TW. I am going to have to bail on pa if there isn't a fix
Click to expand...
Click to collapse
It's an AOSP problem based on the firmware of your camera when getting the phone from what I've seen.
http://forum.xda-developers.com/showthread.php?p=37072484#post37072484
Here's the thread I was talking about, however I'm confused about how to go about zipping and unzipping these files. Or even how to get to them to place the files in to begin with considering internal SD card is the only thing that comes up for USB storage. Unless you're supposed to move them in and out from within android.

Would really like a confirm on whether or not this works for the Verizon version, and whether or not it's a different process/if this even works at all, rather not break it fully
Why is this not more of a widespread issue? it seems so crucial that many are having but nobody seems to be talking about it or wanting to find a definite fix for it?

CZory91 said:
Would really like a confirm on whether or not this works for the Verizon version, and whether or not it's a different process/if this even works at all, rather not break it fully
Why is this not more of a widespread issue? it seems so crucial that many are having but nobody seems to be talking about it or wanting to find a definite fix for it?
Click to expand...
Click to collapse
I had the camera problem on MIUI...
Before flashing, I made a backup of my system with CW
I extracted the SlimISP_ZH.bin from my backup and
copied it to my /data directory and it worked fine.
Link: d-h.st/dwx
(I can't post links yet)
maybe... someone post the fix in this forum and make it sticky... lol

Ughhhhhhhhh. This is getting irritating. Going to revive the thread.
I flashed the new firmware (MD3) for this phone. I had everything good and working with CM10... Guess what, borken camera, same issues...
I can't post links yet, but it's in the android development thread with this title:
★ [Rom][I535VRBMD3][4.1.2] Stock Root Odex/Deodex [05/29/13]★
Except... this time I cannot do the simple copy/paste of the bin files this time, why is that?
At this point I just want my VRBLK3 (I think?) firmware back.. Where can I get it to reverse what I just downloaded, in essence?
Also.. What the heck kind of hurdles am I going to have to go through when CM10.1 is complete?.. I don't think I'll be updating my phone past 10.1 at this rate if this continues, really irritating.

CZory91 said:
Ughhhhhhhhh. This is getting irritating. Going to revive the thread.
I flashed the new firmware (MD3) for this phone. I had everything good and working with CM10... Guess what, borken camera, same issues...
I can't post links yet, but it's in the android development thread with this title:
★ [Rom][I535VRBMD3][4.1.2] Stock Root Odex/Deodex [05/29/13]★
Except... this time I cannot do the simple copy/paste of the bin files this time, why is that?
At this point I just want my VRBLK3 (I think?) firmware back.. Where can I get it to reverse what I just downloaded, in essence?
Also.. What the heck kind of hurdles am I going to have to go through when CM10.1 is complete?.. I don't think I'll be updating my phone past 10.1 at this rate if this continues, really irritating.
Click to expand...
Click to collapse
did you flash this after flashing the rom?
http://forum.xda-developers.com/showthread.php?t=1788313
---------- Post added at 04:47 AM ---------- Previous post was at 04:41 AM ----------
dandydon414 said:
did you flash this after flashing the rom?
http://forum.xda-developers.com/showthread.php?t=1788313
Click to expand...
Click to collapse
my advice, odin back to stock (4.1.2), root and install this rom
http://forum.xda-developers.com/showthread.php?t=1788313
has been great for me, no issues whatsoever

dandydon414 said:
did you flash this after flashing the rom?
http://forum.xda-developers.com/showthread.php?t=1788313
---------- Post added at 04:47 AM ---------- Previous post was at 04:41 AM ----------
my advice, odin back to stock (4.1.2), root and install this rom
http://forum.xda-developers.com/showthread.php?t=1788313
has been great for me, no issues whatsoever
Click to expand...
Click to collapse
Yes, that is the post. I also tried MB1 out of curiosity, no dice on either of them. I had a perfectly working CM10. I dun goofed :\.
That was my next step (rerooting, installing that firmware AIO, and then installing CM10). However my question is this, what happens when more firmware comes out? I have to re root and start over again?

If you flashed md3 just flash back mb1 and you will fix that problem. I had the issue. Pulled the firmware from invisiblek for mb1 and back to normal on liquid smooth
Sent from my GT-P5113 using xda premium

bbqsfire said:
If you flashed md3 just flash back mb1 and you will fix that problem. I had the issue. Pulled the firmware from invisiblek for mb1 and back to normal on liquid smooth
Sent from my GT-P5113 using xda premium
Click to expand...
Click to collapse
for some reason I haven't good luck running cm roms on the s3........have much better luck with tw based rom. that's why I recommend a restock and basically start all over from scratch

dandydon414 said:
for some reason I haven't good luck running cm roms on the s3........have much better luck with tw based rom. that's why I recommend a restock and basically start all over from scratch
Click to expand...
Click to collapse
Yeah I think a clean slate is definitely needed from time to time. I swap roms frequently but liquid gives me the best battery life right now from my tests so I keep going back. I Get scared telling people to odin because so mant people soft brick while screwing up a flash inodin or hard brick because they flash a non Verizon rom
Sent from my GT-P5113 using xda premium

bbqsfire said:
Yeah I think a clean slate is definitely needed from time to time. I swap roms frequently but liquid gives me the best battery life right now from my tests so I keep going back. I Get scared telling people to odin because so mant people soft brick while screwing up a flash inodin or hard brick because they flash a non Verizon rom
Sent from my GT-P5113 using xda premium
Click to expand...
Click to collapse
good point. saw where someone flashed an i9300 s3 rom on the verizon s3 and brick city. my problem with aokp, cm, liquid, carbon, baked bean, I've tried them all, is constant freezing forcing me to pull the battery. I love the features of those roms but I hate having to pull the battery all the time

Hmm, over the past couple days I've tried out a few different ROMs on my girlfriend's S3 here, and on each one I would get this "Could not connect to the camera" error, every single time upon opening the camera app. One of the Paranoid Android ROMs, Liquid Smooth, and Synergy (even the Touchwiz camera was broken on that!).
I can restore to the original backup I made of the stock ROM, and the camera works fine again. But as soon as I try a different ROM, no camera.
I'd love to get an AOSP ROM running on this phone, but having a working camera is a requirement, and I can't figure out what I'm doing wrong. Searching the individual threads for the ROMs yields little help, and I'm getting exactly the same error on different ROMS, so I feel like I'm doing something wrong on a higher level. Any chance that switching from TWRP to CWM would make a difference? I don't see why it would, but I suppose it's something I could try.

bbqsfire said:
If you flashed md3 just flash back mb1 and you will fix that problem. I had the issue. Pulled the firmware from invisiblek for mb1 and back to normal on liquid smooth
Sent from my GT-P5113 using xda premium
Click to expand...
Click to collapse
Yep, I'm saying I tried that, still nothing :\ I'm going to flash MB1 and get the stock files again to see if it will do anything but I doubt it.

CZory91 said:
Yep, I'm saying I tried that, still nothing :\ I'm going to flash MB1 and get the stock files again to see if it will do anything but I doubt it.
Click to expand...
Click to collapse
Have you tried odin back to MB1 or even LK3 and letting it go through the OTA's? Those OTA's also update rpm, and other partitions, that as far as I know don't get updated when we flash these stock files on xda unless we flash them ourselves. Maybe something screwed up and is being persistent since those partitions aren't getting updated along the way?

Watanuki-Kun said:
Have you tried odin back to MB1 or even LK3 and letting it go through the OTA's? Those OTA's also update rpm, and other partitions, that as far as I know don't get updated when we flash these stock files on xda unless we flash them ourselves. Maybe something screwed up and is being persistent since those partitions aren't getting updated along the way?
Click to expand...
Click to collapse
I'm honestly just going to restart from scratch and re root when CM10.1 is fully done (hopefully soon...) Nothing is working. Flashed to MB1 firmware on CM 10. Tan MB1 CleanROM. Camera worked in CleanROM, copy/pasted onto my CM10 after the restore, still nothing... Seriously mind boggling.

CZory91 said:
I'm honestly just going to restart from scratch and re root when CM10.1 is fully done (hopefully soon...) Nothing is working. Flashed to MB1 firmware on CM 10. Tan MB1 CleanROM. Camera worked in CleanROM, copy/pasted onto my CM10 after the restore, still nothing... Seriously mind boggling.
Click to expand...
Click to collapse
Probably best, that would be my first thing to try if I had that problem, restarting from scratch. If all else fails, restarting from scratch will wipe out everything. If that failed, I would probably suspect hardware issue.

Watanuki-Kun said:
Have you tried odin back to MB1...
Click to expand...
Click to collapse
Flashing the MB1 firmware fixed the camera for me on AOSP. I flashed this zip in recovery after the ROM was installed:
http://invisiblek.org/sch-i535/firmware/
Link was obtained from here (FAQ about it):
http://rootzwiki.com/topic/34053-firmware-vrbmd3-modemrpmtzsbl-verizon-sgs3-sch-i535/

dandydon414 said:
good point. saw where someone flashed an i9300 s3 rom on the verizon s3 and brick city. my problem with aokp, cm, liquid, carbon, baked bean, I've tried them all, is constant freezing forcing me to pull the battery. I love the features of those roms but I hate having to pull the battery all the time
Click to expand...
Click to collapse
Well I would recommend liquid 2.5 with the kernel that comes with it and I never change any of the overclocking settings. I don't have to pull the battery at all on this one.
Sent from my SCH-I535 using xda premium

TunedReference said:
Flashing the MB1 firmware fixed the camera for me on AOSP. I flashed this zip in recovery after the ROM was installed:
http://invisiblek.org/sch-i535/firmware/
Link was obtained from here (FAQ about it):
http://rootzwiki.com/topic/34053-firmware-vrbmd3-modemrpmtzsbl-verizon-sgs3-sch-i535/
Click to expand...
Click to collapse
Yep, that's what I tried. Nothing.

I Give Up: 4.3 Camera Issues

Hey guys been searching and reading and searching and reading for the past two days and I cannot get a fix for this camera issue. "Camera Error: Can't connect to the camera.". It seems to only be with Android 4.3 Roms (I.E. Paranoid Android, Slimbean, CarbonRom etc) as when I rooted and installed CleanRom there was no issue. Stock rooted camera also works. I am currently utilizing CWM for all of my flashes/recoveries/backups
Here are the things I have tried based off of search and other threads;
Reflashing Roms and their Gapps multiple times with no luck
Odin'd to stock TWICE and reflashed utilizing the soft brick method VRALEC and VRALF Boothchains as well as stock.vzw_root66.zip.
Reflashed my baseband from MB3 to MB1 to MF1 with no change.
I've tried uninstalling the gallery.apk using TiBackup and reinstalling with different galleries with no luck.
My next step it to attempt to flash a different Kernel.
I honestly love the 4.3 Paranoid Android 3.99 Rom but don't think I can sacrifice not having a camera. Any help from the Gurus would be greatly appreciated and thanks will be given!
Chris

Kennedy87 said:
Hey guys been searching and reading and searching and reading for the past two days and I cannot get a fix for this camera issue. "Camera Error: Can't connect to the camera.". It seems to only be with Android 4.3 Roms (I.E. Paranoid Android, Slimbean, CarbonRom etc) as when I rooted and installed CleanRom there was no issue. Stock rooted camera also works. I am currently utilizing CWM for all of my flashes/recoveries/backups
Here are the things I have tried based off of search and other threads;
Reflashing Roms and their Gapps multiple times with no luck
Odin'd to stock TWICE and reflashed utilizing the soft brick method VRALEC and VRALF Boothchains as well as stock.vzw_root66.zip.
Reflashed my baseband from MB3 to MB1 to MF1 with no change.
I've tried uninstalling the gallery.apk using TiBackup and reinstalling with different galleries with no luck.
My next step it to attempt to flash a different Kernel.
I honestly love the 4.3 Paranoid Android 3.99 Rom but don't think I can sacrifice not having a camera. Any help from the Gurus would be greatly appreciated and thanks will be given!
Chris
Click to expand...
Click to collapse
Try flashing the latest Paranoid Android, Latest BMS or Ktoonsez Kernel, and the supported GAPPS.

macman159 said:
Try flashing the latest Paranoid Android, Latest BMS or Ktoonsez Kernel, and the supported GAPPS.
Click to expand...
Click to collapse
Tried flashing withe the BMS Kernel and still no luck. Can't connect to camera. Very frustrating. Thanks for the attempt.

In this thread on Rootz, I was trying to help a user out and they somehowe got their camera to work despite my suggestion which is a little more involved than what you have done so far. The user somehow got it working by doing a factory reset and wiping caches, then flashing their AOSP rom and VRBMF1 firmware in the same session then booting into the rom.
Here is my more involved suggestion as well.

SlimSnoopOS said:
In this thread on Rootz, I was trying to help a user out and they somehowe got their camera to work despite my suggestion which is a little more involved than what you have done so far. The user somehow got it working by doing a factory reset and wiping caches, then flashing their AOSP rom and VRBMF1 firmware in the same session then booting into the rom.
Here is my more involved suggestion as well.
Click to expand...
Click to collapse
Thank you Slim just saw you're suggestions. I guess I will first try doing what OP of the post you linked did first if all else fails I guess could try the ODIN method as described in the XDA Link you provided...Youre suggest was the ODIN method utilizing the PIT method correct? I guess I'l re-odin to root66 stock and try the method stated.:good:

FYI I am currently running CleanRom 7 with ZERO camera issues. 4.1.2.

Kennedy87 said:
FYI I am currently running CleanRom 7 with ZERO camera issues. 4.1.2.
Click to expand...
Click to collapse
Ahh, this is good. I misread and was thinking it stopped working entirely which has happened to people as well. I'm so used to people having it permanently stop working even after flashing back to TW.
Kennedy87 said:
Thank you Slim just saw you're suggestions. I guess I will first try doing what OP of the post you linked did first if all else fails I guess could try the ODIN method as described in the XDA Link you provided...Youre suggest was the ODIN method utilizing the PIT method correct? I guess I'l re-odin to root66 stock and try the method stated.:good:
Click to expand...
Click to collapse
Yea, but since it's only an AOSP issue and not permanently broken, idk how likely this is to resolve it for you. It's a shot anyway.
Sent from my SCH-I535 using Tapatalk 4

Success: G900F rom on G900V S5

Hi!
First I want to thank the developers and Goldie and Hashcode. I could not thank us topics because I am newbie here.
My wife bought a Galaxy S5 of a person who did not disclose that it was the 900V version, and only possessed a few languages.
Tried my best to translate or to enable more languages​​, all without success.
I managed to do the following to resolve the problem, and it can serve other people from other languages ​​that are at hand with this device, since the installed rom (AllianceRom) has support for multiple languages​​. The phone now appears like a 900F.
1) I root with https://towelroot.com/ towelroot
2) I copied this file from AllianceRom to the microSD card. http://forum.xda-developers.com/showthread.php?t=2716535
3) I installed the following safestrap this post http://forum.xda-developers.com/showthread.php?t=2793891
4) I enabled a custom rom 1 using the default options.
5) I installed the rom usually at recovery.
6) I waited a few minutes, booted, and FINALLY got to choose the option Brazilian Portuguese.
caveats:
Do not know if it's bug or something the ROM installing a rom that is not the phone itself, but the device does not turn off. He gets the LED on the physical and lighted keys and switches itself off. I have to take off and put the battery back.
If I had to fix something, which will not do out of sheer laziness, would change the standard sizes of custom rom, because I never want to see the original rom from Verizon. The custom rom ended up with little virtual space.
Sorry for the english but blame Google Translator!

If you look at the alliance thread a lot of people are having problems installing on a rom slot I used the stock slot and no problems
http://bit.ly/1brshoa

bad bone said:
If you look at the alliance thread a lot of people are having problems installing on a rom slot I used the stock slot and no problems
Click to expand...
Click to collapse
you installed AllianceROM SM-G900F on a sm-g900v and it worked just fine?

suburbano said:
you installed AllianceROM SM-G900F on a sm-g900v and it worked just fine?
Click to expand...
Click to collapse
Umm no I'm on the 900V?
I just read in step#4 that he put it on a rom slot I've read that people are having problems when they use a rom slot instead of the stock slot and thought that might help no clue? I was just suggesting that by installing it on the stock slot might fix the following problems.
4) I enabled a custom rom 1 using the default options.
caveats:
Do not know if it's bug or something the ROM installing a rom that is not the phone itself, but the device does not turn off. He gets the LED on the physical and lighted keys and switches itself off. I have to take off and put the battery back.
If I had to fix something, which will not do out of sheer laziness, would change the standard sizes of custom rom, because I never want to see the original rom from Verizon. The custom rom ended up with little virtual space.
I believe it's on page 13 of the alliance thread where they start talking about the rom slot issue.
http://bit.ly/1brshoa

bad bone said:
Umm no I'm on the 900V?
I just read in step#4 that he put it on a rom slot I've read that people are having problems when they use a rom slot instead of the stock slot and thought that might help no clue? I was just suggesting that by installing it on the stock slot might fix the following problems.
4) I enabled a custom rom 1 using the default options.
caveats:
Do not know if it's bug or something the ROM installing a rom that is not the phone itself, but the device does not turn off. He gets the LED on the physical and lighted keys and switches itself off. I have to take off and put the battery back.
If I had to fix something, which will not do out of sheer laziness, would change the standard sizes of custom rom, because I never want to see the original rom from Verizon. The custom rom ended up with little virtual space.
I believe it's on page 13 of the alliance thread where they start talking about the rom slot issue.
http://bit.ly/1brshoa
Click to expand...
Click to collapse
this thread is decieving.. he didnt get g900f on g900v he just installed alliance rom and enabled his language lol
Sent from my SM-G900V using XDA Free mobile app

elliwigy said:
this thread is decieving.. he didnt get g900f on g900v he just installed alliance rom and enabled his language lol
Sent from my SM-G900V using XDA Free mobile app
Click to expand...
Click to collapse
Definitely deceiving if that's the case:what: either way he should re do it on the stock slot
http://bit.ly/1brshoa

Alright so I thought I would shed a little light on this. I saw this thread a few days ago and decided to test this for myself. I have a verizon version of the S5 and the 900f version of the rom installed fine in the stock rom slot. The only issue at first was the keyboard was chinese. I had to activate the English one and things were fine. All the customization stuff works. I've basically tested everything and have been using it constantly for a few days now. So it does work. I haven't tried any other 900f roms yet.

DJNads said:
Alright so I thought I would shed a little light on this. I saw this thread a few days ago and decided to test this for myself. I have a verizon version of the S5 and the 900f version of the rom installed fine in the stock rom slot. The only issue at first was the keyboard was chinese. I had to activate the English one and things were fine. All the customization stuff works. I've basically tested everything and have been using it constantly for a few days now. So it does work. I haven't tried any other 900f roms yet.
Click to expand...
Click to collapse
Yes!
My wife exchanged the Verizon Galaxy S5 black by a white version. This time I installed the rom slot: stock, and everything is working perfectly. :laugh::good:

I would like to thank you all, specially amonteiro, only a Brazilian would need insert Portuguese language inside a Verizon Galaxy S5.
I have successfully flash the rom at stock rom slot.

I have a stock T-MOBILE rom running on my g900V with no problems or patches. Even installed mobile odin

what version did flash
strongcel said:
I would like to thank you all, specially amonteiro, only a Brazilian would need insert Portuguese language inside a Verizon Galaxy S5.
I have successfully flash the rom at stock rom slot.
Click to expand...
Click to collapse
Did you flash the lollipop verison

genica said:
I have a stock T-MOBILE rom running on my g900V with no problems or patches. Even installed mobile odin
Click to expand...
Click to collapse
hey could you let me know how you did this? did you flash the stock rom via odin? Did it not fail when trying to write the aboot? im trying to get ANY stock rom whether it be G900A/I/T/F onto my G900P

bug??
I think it's the the phones themselves. I have tried many custom roms and they all have worked but when I us a rom slot that isn't stock my g900v won't shut off either and I have to take the battery out. I even put a non rooted rom on every rom slot and none would shutoff other than stock slot.
amonteiro said:
Hi!
First I want to thank the developers and Goldie and Hashcode. I could not thank us topics because I am newbie here.
My wife bought a Galaxy S5 of a person who did not disclose that it was the 900V version, and only possessed a few languages.
Tried my best to translate or to enable more languages​​, all without success.
I managed to do the following to resolve the problem, and it can serve other people from other languages ​​that are at hand with this device, since the installed rom (AllianceRom) has support for multiple languages​​. The phone now appears like a 900F.
1) I root with https://towelroot.com/ towelroot
2) I copied this file from AllianceRom to the microSD card. http://forum.xda-developers.com/showthread.php?t=2716535
3) I installed the following safestrap this post http://forum.xda-developers.com/showthread.php?t=2793891
4) I enabled a custom rom 1 using the default options.
5) I installed the rom usually at recovery.
6) I waited a few minutes, booted, and FINALLY got to choose the option Brazilian Portuguese.
caveats:
Do not know if it's bug or something the ROM installing a rom that is not the phone itself, but the device does not turn off. He gets the LED on the physical and lighted keys and switches itself off. I have to take off and put the battery back.
If I had to fix something, which will not do out of sheer laziness, would change the standard sizes of custom rom, because I never want to see the original rom from Verizon. The custom rom ended up with little virtual space.
Sorry for the english but blame Google Translator!
Click to expand...
Click to collapse

G900TUVU1DOB1 ROM on G900V
I switched to T-Mobile from Verizon a couple months ago and kept my G900V to use on the T-Mobile network. I kept having apn issues with the Verizon (KK and 5.0) based rom and decided to flash in recovery the Beanstown 4.4.2 G900T rom and had great success . If you want KK I can confirm that both Beanstown 4.4.2 G900T and G900F roms work on the G900V kernal if installed on recovery (wipe everything first). I now am using [ROM]ViSiON-X US TMO[Android L 5.0][G900TUVU1DOB1][02-18-15] rom flashed by the installation method for the Verizon Lollipop to Keep Root. Steps are full wipe in recovery, flash rom in recovery (CANNOT, I REPEAT CANNOT HAVE AROMA), flash Verizon OA8 5.0 with Odin, boot 10 min wait... I believe any stock lollipop rom can be flashed, probably anything without Aroma... I have working Wifi-Calling feature, working Volte, everything works but no Wanam yet bummer...

This is excellent.
Question: Were you on 4.4.4 when you installed AllianceROM?, because it now has the 5.0 version, so I am wondering if i should update to stock 5.0 first and then use your method?, or maybe on 5.0 the method won't work? (towelroot, safestrap)
Thanks
Update:
I went back to 4.4.4, rooted, flashed the rooted Lollipop, but now safestrap won't load because it's Kitkat safestrap, so I can't manage to flash Alliance, any solution?

Flash the 4.4.2 stock kernel in Odin. Safestrap only works on kk kernel, then flash back to 5.0. Same instructions used in the forum to upgrade to Verizon 5.0, you just need to switch back and forth with the Verizon version of kk and lollipop kernels through Odin to access Safestrap.
Edit: Flash the visionx tmobile rom, it's amazing.

stock T-Mobile rom on G900V
genica said:
I have a stock T-MOBILE rom running on my g900V with no problems or patches. Even installed mobile odin
Click to expand...
Click to collapse
Do tell. I have been looking for instructions for putting a t-mobile rom on my G900V
Please share.
Also, does the wifi calling feature now show up?
Cheers!

milesius said:
Do tell. I have been looking for instructions for putting a t-mobile rom on my G900V
Please share.
Also, does the wifi calling feature now show up?
Cheers!
Click to expand...
Click to collapse
It just need to be done with safestrap recovery (You can not use Odin)
As always make a full backup up of your current rom before flashing anything. Wipe the system, data and cache and flash away. I've flashed g900t, g900f and i think some g900a Roms work as well... Can't remember. You will probably have issues if you still have a Verizon Sim card. And yes, WiFi calling will be there

genica said:
It just need to be done with safestrap recovery (You can not use Odin)
As always make a full backup up of your current rom before flashing anything. Wipe the system, data and cache and flash away. I've flashed g900t, g900f and i think some g900a Roms work as well... Can't remember. You will probably have issues if you still have a Verizon Sim card. And yes, WiFi calling will be there
Click to expand...
Click to collapse
Safstrap wont let me flash the ROM - it says its a mismatch and errors out.
Am I missing a step?

milesius said:
Safstrap wont let me flash the ROM - it says its a mismatch and errors out.
Am I missing a step?
Click to expand...
Click to collapse
Try a different ROM I've always used the ones that say stock. When I get home I'll tell you the exact one I used. If that doesn't work try a different safestrap

Rooting and Custom ROM Problems

So, I'm sure I'm probably doing something incredibly stupid..
I just got my Note 5 today. I've been trying to flash a custom ROM, TEKXodus first and then Dr Ketan's ROM. I managed to get them to boot up (at least Ketans, I've been trying so long today at this point I'm not sure if I ever got TEKXodus to load).
However, after finally getting in, my SIM card isn't being detected, neither is the baseband and IMEI. The phone registers as a N290I instead of N290T.
Did I flash something wrong? Would the wrong version of recovery cause this? Kernels?
This isn't my first time rooting and flashing ROMs, but I can't figure out what I'm doing wrong this time.
Any help would be greatly appreciated.

re: N920T issues
nightfire55 said:
So, I'm sure I'm probably doing something incredibly stupid..
I just got my Note 5 today. I've been trying to flash a custom ROM, TEKXodus first and then Dr Ketan's ROM. I managed to get them to boot up (at least Ketans, I've been trying so long today at this point I'm not sure if I ever got TEKXodus to load).
However, after finally getting in, my SIM card isn't being detected, neither is the baseband and IMEI. The phone registers as a N290I instead of N290T.
Did I flash something wrong? Would the wrong version of recovery cause this? Kernels?
This isn't my first time rooting and flashing ROMs, but I can't figure out what I'm doing wrong this time.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
You need to start from scratch (square one) and odin flash the
official stock Samsung N920T Tmobile Marshmallow 6.0 firmware
before doing anything else.
You can find the N920T Marshmallow 6.0 firmware here:
http://sammobile.com
Good luck,
Have a great day!

The phone came with Marshmallow already installed I believe. Either way I've currently got the stock TMobile installed now and am still having the same problem.

re: phone issues
nightfire55 said:
The phone came with Marshmallow already installed I believe. Either way I've currently got the stock TMobile installed now and am still having the same problem.
Click to expand...
Click to collapse
Perhaps your phone came with the wrong version of Marshmallow 6.0 if the phone was not new when you got it.
Either way I bet you still have NOT Odin flashed the full official stock samsung N920T 6.0 Marshmallow firmware
which can be found at http://sammobile.com
If you finally decide to do the above be sure to do a full wipe and factory data reset before you odin flash.
And forget about roms until you get the phone working properly with the stock N920T odin flash firmware.

Will definitely double check and retry that when I get off of work.

And that worked!
Thank you so much, I was working off a different MM build apparently. Probably would never have figured that out by myself.

Can't install any stock rom at all??

Hi. I have the boost Mobile variant s5. I updated my s5 to marshmallow from odin, and it wouldn't boot, it would just sit at the boost Mobile screen. I went to recovery and factory reset and tried flashing through odin again, and it still sat at the boost Mobile screen. I went always see ''custom'' in device status instead of ''official''. When I flash AOSP Roms they boot up fine, but any stock marshmallow rom whether it's fully stock or rooted never boots. What's the problem?

So no one can help?

SuperBrolySSJ said:
So no one can help?
Click to expand...
Click to collapse
You might have to try another stock, with odin (download) mode saying custom there maybe something wrong with that stock rom, it could have been a stock root, or something in there is custom. Have you checked the sam mobile site?
I don't think there are alot of people on the S5 forum anymore(for sprint atleast). I will try and look around outside the noob forum when I can to see if people need help on their S5s.