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.
Related
Hey all, need a quick hand with my T-Mo LG G2 d801- 4.4.2 stock rom.
Process so far: towelroot>supersu>autorec>twrp>...
Tried flashing CM11, but after about 20min I figured I did something wrong, lol.
What version of cyanogenmod should I be flashing, 10 or 11? From the description of what AutoRec does to deal with the bootloader, it downgrades to the last vulnerable rom to install/enable custom recovery, correct? If so, does it stay downgraded or is that just to get the custom recovery in place?
Don't want to brick my phone experimenting, so here I am. Thanks in advance!
Also should have waited till after work, as I have no more time tonight to mess with it unfortunately. Back in 8hrs! :silly:
Nevermind, I got it working.
fleshybits said:
Nevermind, I got it working.
Click to expand...
Click to collapse
Consider that while others might not have had an answer to your question, your thread could have been frequented in order to see the answer.
So, how did you resolve your issue? ?
fleshybits said:
Hey all, need a quick hand with my T-Mo LG G2 d801- 4.4.2 stock rom.
Process so far: towelroot>supersu>autorec>twrp>...
Tried flashing CM11, but after about 20min I figured I did something wrong, lol.
What version of cyanogenmod should I be flashing, 10 or 11? From the description of what AutoRec does to deal with the bootloader, it downgrades to the last vulnerable rom to install/enable custom recovery, correct? If so, does it stay downgraded or is that just to get the custom recovery in place?
Don't want to brick my phone experimenting, so here I am. Thanks in advance!
Also should have waited till after work, as I have no more time tonight to mess with it unfortunately. Back in 8hrs! :silly:
Click to expand...
Click to collapse
Autorec just flashes an older boot loader, with a stock based KK kernel that's compatible. Once up and running any stock based kernel can be flashed if running a stock ROM. It also supports running any after market ROM, however, if running a jb based ROM one needs to be on a jb modem, and if running KK a compatible modem. These are pretty much the only prerequisites.
Sorry, that was rather rude of me wasn't it? Apologies. Not fair to ask for help if I can't return the favor when I can.
Well, instead of looking around on the CM downloads page to get the most stable release, I just got the most recent snapshot of CM 11. Silly me
Turns out the right file to flash first was, of course, the last stable release for the G2 D801, which was CM 10.2.0 (at least at the time of this writing, as far as I know.) After getting the right file and trying again, I was rocking my first custom ROM. Go me! :good:
I have not yet tried the snapshot again to see if I could upgrade to CM11, as I hit another snag: I can't connect to my carrier anymore. I can see T-Mobile in the list for networks but selecting them does nothing, I get no service. Restoring the stock ROM works just fine, its like nothing happened, but running CM I can't connect. Any suggestions?
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
1. TWRP is up
2. baseband G920R4TYU2BOF7/HW version G9020R4.02
3. No Mods
4. Rooted
So I tried flashing the Vader ROM, I was getting boot loops at the language selection screen. I go back and restore from backups my original stuff. Boot back up and now I'm getting the lovely "process.com.google.gapps has stopped" error. I'm assuming that I may need to find gapps for 5.1.1? I also tried flashing XtreStoLite ROM with the Aroma add on. Everything seemed to be working great with the exception of the data and no signal, which I am to assume is because I'm not using the correct carrier-specific stuff.
Go to download the stock ROM for my phone, and I keep getting an error as well. Odin won't flash it. One thing that I noticed is that the stock rom was 5.0.2 where when I got the phone 3 days ago it came with 5.1.1.
At this point, I'd like to be able to get it back to stock if possible. I jumped the gun and started flashing all sorts of things without checking to see if it would even for with a USCC galaxy s6. Any help would be much appreciated.
UPDATE: Problem seems to have resolved itself with the last restore. no more problems with gapps. However I am curious as to if any of these custom roms will work with a USCC variant
I've searched the forums beforehand, so if someone finds something I missed, I apologize.
I have a Straight-Talk Samsung Galaxy S5.
Model Number from within Android says SM-S902L
Model Number on the battery cover says SM-G900P (B)
Currently running 4.4.2
I was wondering if someone would be able to show me how to root this, install a custom recovery, and tell me which roms I can install. The two different model numbers are confusing me.
EDIT: I rooted via CF Auto root using the sprint ktle .tar. Does this mean that most SM-G900P roms will work? I'm still confused on how to get from 4.4.2 to Android 5 or 6, if it's even possible.
Thank you very much.
i put a version of MOAR built for the vzw G900v on a 902L a few mos ago and its working fine. Just get TWRP on it and you can flash pretty much any snapdragon based ROM on it barring incompatible kernels and so forth
I got TWRP installed and it works fine, made sure the first thing I did was back everything up. It's just that, every post I've seen, the OP's Straight Talk S5 was just a rebranded Verizon S5, while mine is a rebranded Sprint S5. I just want to be certain flashing a Verizon ROM won't bork my "Sprint" phone. I can't find APN settings or anything. So I can't even copy them to change them later. So should I only try Sprint ROMs?
Tats the weird thing about the 902L, it says g900p on it, but i had to flash the vzw version of MOAR instead of the G900Ps version for it to work. But its seriously hard to bork your phone in such a manner that Odin cant fix it. I cant tell you how many times ive tried to install a ROM that was made for the g900p on my g900p and it failed, so, i just flashed MOAR in TWRP again and viola. Also, the backup thing isnt as vital as some make it seem if you have the tarball for the phone you own. Sure, it makes it easy to restore from an eff-up if you dont have your computer handy, but its just so unnecessary to make a backup of your original setup, just have a backup of a known to be fully working setup. Anyways, give vzw's MOAR a try. Its a great ROM and if anything goews wrong, just odin your phones original tarball back on it and all will be back to stock. You have to flash TWRP after the phones OG tarball tho
I don't have my phones OG tar. And is there a step I have to take before installing M.O.A.R or can I just jump from 4.x.x to 6.x.x?
im not aware of any 6.x.x ROMs that are compatible. MOAR is 5.0. Are you trying to get an app working that isnt compatible with 4.x.x? Like the car synch app? And to flash MOAR, just download it, wipe cache, dalvik and system in TWRP and install MOAR. Firstly tho, get the tarball from sammobile.com/firmwares. Its a super slow d/l, but youre gonna want to have it in case of a nuclear bomb restore necessity (not a likely scenario, but youre gonna want it. I have it and can host it for you on android file host later once i get home)
did you get the tarball for the 902L?
i ended up redownloading it from sammobile.com/firmwares. Took about 90 min because of their horrendous download speeds for non premium members, but i have 7 TB of storage, so im not wasting any space just having it since i have a G900P LoL (well, 2 of em along with the bovy of other phones i have for whatever reason i still keep them)
Thank you so much!, and Happy Thanksgiving if you celebrate. I've installed MOAR and the only thing I did was change the colors of the status bar icons and now all the phone does is boot to lockscreen then cycle back to boot animation. Something I did?
RRSJ392 said:
Thank you so much!, and Happy Thanksgiving if you celebrate. I've installed MOAR and the only thing I did was change the colors of the status bar icons and now all the phone does is boot to lockscreen then cycle back to boot animation. Something I did?
Click to expand...
Click to collapse
wipe all the appropriate caches before installing? and where did you get the version of MOAR youre using? Also happy thanksgiving to you too!
Ironically, I want to go back to 4.X.X for compatibility issues. Do I just wipe Dalvik and Cache and load OG tar through odin? I cant locate OG tar for 902L :/
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.