Database Info

[Q] Safestrap 3.65 and CyanogenMod 10.2

Hi Guys,
I have a few questions about cyanogenmod, safestrap, and the lovely ATT MF3 bootlocker that is ruining my day. By the way, thanks for all the information you all give, it's helped me understand this process. Even though many people don't post, I'm sure they're glad to have your opinions as well. I have an ATT MF3 SGH-I337. I'm trying to install Cyanogenmod 10.2 using safestrap 3.65. I run into difficulty when I install the 10.2 zip file on the second partition. I've installed the kernel module and was able to successfully install 10.2 (according to SafeStrap), however when I restarted my phone it simply sat on the "Samsung Galaxy S4" screen. It was only soft bricked and I was able to reinstall the stock ROM. I'm about to start the entire process over and I thought that it would be really nice to get an expert opinion on where I'm going wrong.
I have a few questions:
1. Does CyanogenMod 10.2 work with Safestrap 3.65? If not, will 10.1?
2. Should I also install the kernel module on my stock partition?
3. Is there any way that I can limit the stock partition to barely usable? I plan on going Cyano and never looking back.
Thanks in advance,
Grija

I ended up getting SafeStrap on my phone, but I still can't get cyanogenmod on there. Also, my phone's 4G on the stock rom isn't working, despite having the kernel modules.
Any thoughts?

Grija said:
I ended up getting SafeStrap on my phone, but I still can't get cyanogenmod on there. Also, my phone's 4G on the stock rom isn't working, despite having the kernel modules.
Any thoughts?
Click to expand...
Click to collapse
Alright, I've got the modem back. I had to Odin my modem (phone) and CSC. This killed the settings I just set up, but it did fix the modem issue. Back to Cyanogenmod.
I should just be grabbing the latest RC, installing a new virtual ROM, applying the kernals, and flashing the ZIP... correct?
Thanks,
Brandon

[Q] When Flashing AOSP/AOKP/CM/PA Roms

Hey, sorry for such a noob question, I do lots of reading on here and tried to post within a certain rom, C-Rom Kit-Kat 4.4.2 5/13/14, and it won't allow me since I have never posted anything on XDA. I have the Verizon HTC ONE M8 and it is bootloader unlocked, s-off, and on the stock rom with build number 1.56, with lots of customization but I found a new rom I wanted to try. It is an AOSP rom like mentioned above but I never seemed to find what build number it is on? I know with a SENSE rom you have to be careful of what build number your phone is, whether it is 1.54 before the update or 1.56 after the update.
My question is, when flashing an AOSP/AOKP/CM rom through TWRP, does the build number matter? In all the AOSP roms I never haven't been able to find where the OP states which it is, making me wonder if I need to worry about it or not? I want to flash away from the stock rom but only to an AOSP type rom.. I want to be careful because since we don't have a removable battery, I am worried I will be stuck in bootloop and I am not sure how to get out of it without a battery pull.. (I know holding power and volume up will restart the phone but how would you get back into recovery to restore a backup?)
Also while I am at my first post, do you recommend TWRP, CWM, or Philz touch recovery? I would like to stick to one recovery throughout the tenure of the rooted ONE M8, makes keeping backups
Thanks for the help and I greatly appreciate it! And I apologize again for such a noob question..

pahlerc1 said:
Hey, sorry for such a noob question, I do lots of reading on here and tried to post within a certain rom, C-Rom Kit-Kat 4.4.2 5/13/14, and it won't allow me since I have never posted anything on XDA. I have the Verizon HTC ONE M8 and it is bootloader unlocked, s-off, and on the stock rom with build number 1.56, with lots of customization but I found a new rom I wanted to try. It is an AOSP rom like mentioned above but I never seemed to find what build number it is on? I know with a SENSE rom you have to be careful of what build number your phone is, whether it is 1.54 before the update or 1.56 after the update.
My question is, when flashing an AOSP/AOKP/CM rom through TWRP, does the build number matter? In all the AOSP roms I never haven't been able to find where the OP states which it is, making me wonder if I need to worry about it or not? I want to flash away from the stock rom but only to an AOSP type rom.. I want to be careful because since we don't have a removable battery, I am worried I will be stuck in bootloop and I am not sure how to get out of it without a battery pull.. (I know holding power and volume up will restart the phone but how would you get back into recovery to restore a backup?)
Also while I am at my first post, do you recommend TWRP, CWM, or Philz touch recovery? I would like to stick to one recovery throughout the tenure of the rooted ONE M8, makes keeping backups
Thanks for the help and I greatly appreciate it! And I apologize again for such a noob question..
Click to expand...
Click to collapse
Correct me if im wrong, but the sense build is just telling what that ROM is based on. Once your S-OFF, you can flash them as you please. I know the bootloader version was what would cause bricks in the past (flashing a 4.2.2 rom in a 4.3 bootloader) but i havent seen anything like that for the M8 yet.
Vol DOwn and power will get you to hboot which will let you get to recovery. I use CWM but theyre all comparable, just personal preference.

Abe21599 said:
Correct me if im wrong, but the sense build is just telling what that ROM is based on. Once your S-OFF, you can flash them as you please. I know the bootloader version was what would cause bricks in the past (flashing a 4.2.2 rom in a 4.3 bootloader) but i havent seen anything like that for the M8 yet.
Vol DOwn and power will get you to hboot which will let you get to recovery. I use CWM but theyre all comparable, just personal preference.
Click to expand...
Click to collapse
Thanks for the reply! I can't wait to flash this new AOSP rom so I can remove all the bloatware put on by Verizon and Sense.. Just want to vierfy, so if the build number no longer matters since I am s-off, you're saying I can flash the ARHD rom on my phone even though it states the build number 1.54 and I have 1.56? Because I would also love to have a stock sense rom with lots of optimizations and tweaks for performance with less bloatware.
Thanks again

pahlerc1 said:
Thanks for the reply! I can't wait to flash this new AOSP rom so I can remove all the bloatware put on by Verizon and Sense.. Just want to vierfy, so if the build number no longer matters since I am s-off, you're saying I can flash the ARHD rom on my phone even though it states the build number 1.54 and I have 1.56? Because I would also love to have a stock sense rom with lots of optimizations and tweaks for performance with less bloatware.
Thanks again
Click to expand...
Click to collapse
I just read that if you have the newest 1.55.6.. firmware and baseband and try to flash roms with the older baseband (1.54) then you might run into problems with losing root and and other issues..
Can someone please verify this? Currently on stock rom, rooted, s off, bootloader unlocked, with baseband 1.55.6.. Looking into flashing either AOSP rom or Sense rom but does it matter if its based on 1.54 or the newest 1.56?
Thanks, the help is greatly appreciated

pahlerc1 said:
I just read that if you have the newest 1.55.6.. firmware and baseband and try to flash roms with the older baseband (1.54) then you might run into problems with losing root and and other issues..
Can someone please verify this? Currently on stock rom, rooted, s off, bootloader unlocked, with baseband 1.55.6.. Looking into flashing either AOSP rom or Sense rom but does it matter if its based on 1.54 or the newest 1.56?
Thanks, the help is greatly appreciated
Click to expand...
Click to collapse
you're just gonna end up with whatever baseband you flash as the latest baseband. where are you seeing people lose root bc of flashing a different baseband?

Abe21599 said:
you're just gonna end up with whatever baseband you flash as the latest baseband. where are you seeing people lose root bc of flashing a different baseband?
Click to expand...
Click to collapse
It was in a different thread, can't recall which.. I have been doing way too much reading I think it was in one last few pages of the venom rom thread.. I'll just wait for Venom and Skyfall to update their baseband to the latest 1.56 build. No worries. Thanks.

Updated to the latest VZW firmware, and have had no issues using the multi-variant roms, which use the non-Verizon versions. My radio base still reflects the updated version (0321). On Viper right now with no issues, waiting for AOKP. Been using 2.7.0.2 TWRP with no problems. If you have a concern about flashing any ROM (and/or gapps if you are trying an AOSP ROM), just make sure you make a backup in recovery before anything else, and if the new stuff doesn't work well or borks your device, just learn how to get back into recovery and restore your backup. Read first, try second.

ebb said:
Updated to the latest VZW firmware, and have had no issues using the multi-variant roms, which use the non-Verizon versions. My radio base still reflects the updated version (0321). On Viper right now with no issues, waiting for AOKP. Been using 2.7.0.2 TWRP with no problems. If you have a concern about flashing any ROM (and/or gapps if you are trying an AOSP ROM), just make sure you make a backup in recovery before anything else, and if the new stuff doesn't work well or borks your device, just learn how to get back into recovery and restore your backup. Read first, try second.
Click to expand...
Click to collapse
Okay thanks for the help. I always make sure to read first and create a backup, I've made the mistake once and took a long process to get it solved and won't let that happen again that's for sure! Thanks for the response, I just flashed Skyfall 2.5 and it is amazing!

[Q] VZW M8 - Sunshine S-Off - CM12 / GPE / Custom ROMs

I need some assistance please! I am truly baffled by what I am experiencing and would like to know why and hopefully how to fix it. Here's the details:
CARRIER: Verizon
MODEL: HTC One M8
S-OFF: Yes (Sunshine)
ROOT: Yes
HBOOT: 3.19
RADIO: 1.09.20.0926
OpenDSP: 46.2.2
OS: 3.28.605.4
First off, sorry for the book, but I figured more details would be better at this point to figure out what is up, so I appreciate any assistance in advance! PS: I bolded the key items to the story for those that like to skim.
Prior to S-Off and Root, I was on OTA version 4.4.4 waiting in anticipation for 5.0 to come to my device. Was unsure about spending $25 for Sunshine's method, but finally decided to take the plunge. At first things seemed great and very smooth. Following all instructions from Sunshine I was finally with S-Off status. I then used WeakSauce2 to gain temp root of the Stock ROM so that I could install Flashify and TWRP. Rebooted and loaded up TWRP Recovery and completed the first Nandroid. SUCCESS! Next up was Titanium Backup and such and copied everything off to my computer for safe keeping. So far so good and then loaded up a few ROM files and whatnot to the External SD Card so I could start flashing a new ROM. Feeling good up to this point, but here's where the troubles begin...
I have had great success with CyanogenMod in the past on previous devices and always very pleased. I read CM12 for others was great and stable and performed well, so I decided to grab the latest CM12 Nightly and the GApps package. Did the normal Wipe / System Wipe for initial flash of a new ROM and then installed both ZIPs no problem. The ROM boots up and everything seems okay, only I do not have LTE at all, only 3G. I also tried the GPE rom by Digitalhigh and experienced the same thing! Restoring from Nandroid also did not fix LTE, so at this point I got worried I broke my phone somehow.
To make a long story short after lots of testing I found a fix for getting LTE back on my original ROM. I found the 4.4.4 RUU and placed the 1.7 GB zip file (0P6BIMG.zip) on the root of my external SD Card, booted into HBOOT and ran the update. It did it's thing and booted up into the Stock ROM. Still no LTE! So then I found a comment somewhere about once that is done, do a Factory Reset from HBOOT using the Stock Recovery and it is supposed to reset the NV Radio Partition, so I did this and when it booted back up, SUCCESS! I have LTE back.
Once that was done I can now flash GPE, (but unusable because SMS is not working for some reason... I am using Google Voice BTW), so I am back to my original 4.4.4 TWRP Recovered ROM. I tried just for kicks to see if after the "fix" if I could make CM12 work, but again will bring it down to an unworking LTE status. Rinse and repeat the "fix" and got LTE back and did Nandroid Recovery. I paid the money to get S-Off and Root access so I could enjoy the Custom ROM's, but now I feel I am stuck...
All that being said... Can someone please explain to me what is going on?? And is there any way I can fix this so I can use CM12 and have LTE, and even then some other ROMs? I will post in Digitalhigh's forum for resolution to the SMS issue, but I have never had this much trouble with a device before and do not know enough about the different partitions and how they work and such. Any assistance and advice is MUCH appreciated!
Thank you!

Nobody has any advise or explanation?

I don't know the version numbers you posted from you bootloader off the top of my head but did you update your firmware to one of the unofficial ones around before flashing one of the lollipop roms? Is so, are you sure it took completely as sometimes you have to flash it twice.
Alternatively you could wait for our official firmware to drop any minute now and have pretty good odds of working for you.

cntryby429 said:
I don't know the version numbers you posted from you bootloader off the top of my head but did you update your firmware to one of the unofficial ones around before flashing one of the lollipop roms? Is so, are you sure it took completely as sometimes you have to flash it twice.
Alternatively you could wait for our official firmware to drop any minute now and have pretty good odds of working for you.
Click to expand...
Click to collapse
Yes I did use official firmware, and flashed twice per recommendations. I have it working with GPE, but every time I flash CM12 it breaks LTE. I have seen articles and posts of others running CM12 on their M8's with VZW and stating "zero issues"... Lack of LTE sounds like an issue to me. So my big question at hand is, why does CM12 break LTE, and is there a fix? Everything else seemed to work great otherwise.

kjparenteau said:
So my big question at hand is, why does CM12 break LTE, and is there a fix? Everything else seemed to work great otherwise.
Click to expand...
Click to collapse
I was reading the CM12 m8 thread earlier this week and many reported that LTE did not work on builds from late Feb. early March. CM12 is in no way stable and results will vary from phone to phone. Even the speaker issues have not been fully resolved. Bummer, because I'd really like it to be more stable.
http://forum.xda-developers.com/htc...genmod-12-0-nightlies-htc-one-t2998070/page75

Thank you for your reply. Definitely wanting CM since I used to run that regularly on my older devices with no troubles at all. The speed and simplicity are what I am going for. Sense is okay, but the difference of less than 300 megs with CM compared to over a gig for stock is unreal. WAY less overhead.

I need some help with installing a custom rom

I've done everything correctly, followed every tutorial, and I'm still not having any luck. I started on stock rooted Lollipop, and all I was getting as installation aborted errors with using Lollipop Autorec. I've since flashed back to stock rooted Kitkat, which I've got the closest with. I've been trying to flash one of the newer nightly updates from Cyanogenmod (20150709 specifically). I've also tried using the first stable release, to no avail. I used one click root to root, which worked fine, and Autorec Kitkat installer for TWRP, which also installs fine, and I can get into recovery no problem. I wipe, I flash, and it boots up, but then it never loads. It ends up being stuck on a boot loop, and it's very frustrating because of how close I'm getting. A Cyanogenmod 11 snapshot flashed correctly, but I'd like to figure out the newer update problem. I'm on LG D800. I'm a complete noob at this stuff, and need a sensei to guide me, please. Thanks in advance.
(Update): I've just now tried installing the newest Resurrection Remix for LG G2, and that sticks me in a boot loop as well, so I have no idea what I have to do. Will update again in a moment because I'm going to try downloading stock Lollipop and the newest TWRP.
(Update 2): So, I've just done what I said I'd do earlier. I flashed the LP bootstack, then Resurrection Remix, then Gapps, and I'm getting a bootloop for that, as well, so I'm calling it a night, and going to bed. Someone please respond. I really need help.

Did you update TWRP? You need to be on the latest version, 2.8.7.1 to flash the newest roms. http://blastagator.ddns.net/twrp.html Put this on your phone and go into recovery and flash it. No wipes needed. Don't reboot when it's done, back arrow to the first screen and select reboot and then select recovery. After that reboots you'll be on the latest TWRP and can flash the LP roms and necessary files or just reboot system and you'll boot up the rom you currently have installed.

Yeah, I ended up trying that, and flashing Resurrection Remix, and I was still getting a boot loop on that, as well.

Really now said:
Did you update TWRP? You need to be on the latest version, 2.8.7.1 to flash the newest roms. http://blastagator.ddns.net/twrp.html Put this on your phone and go into recovery and flash it. No wipes needed. Don't reboot when it's done, back arrow to the first screen and select reboot and then select recovery. After that reboots you'll be on the latest TWRP and can flash the LP roms and necessary files or just reboot system and you'll boot up the rom you currently have installed.
Click to expand...
Click to collapse
I just read what you said again, and no, I didn't actually try that version. I'm on TWRP normal version 2.8.6.1. I will probably try what you said, soon, and report back when I do.
(EDIT): Also, am I supposed to flash a baseband and/or a different bootloader? I'm really new to this stuff, and I don't 100% know everything to do, and some tutorials aren't 100% clear, because I guess they're assuming the viewer knows what they're doing.

Wezurii4694 said:
I just read what you said again, and no, I didn't actually try that version. I'm on TWRP normal version 2.8.6.1. I will probably try what you said, soon, and report back when I do.
Click to expand...
Click to collapse
Yeah, from what I'm reading in all the latest LP threads you have to be on the latest TWRP. I am and I've had zero issues flashing the different roms. Follow the OP of each one exactly and you'll be fine.

Really now said:
Yeah, from what I'm reading in all the latest LP threads you have to be on the latest TWRP. I am and I've had zero issues flashing the different roms. Follow the OP of each one exactly and you'll be fine.
Click to expand...
Click to collapse
Alright, man, thanks a lot! I'll report back when I test this out. Also, am I supposed to flash a baseband and/or a different bootloader? I'm really new to this stuff, and I don't 100% know everything to do, and some tutorials aren't 100% clear, because I guess they're assuming the viewer knows what they're doing.

Wezurii4694 said:
Alright, man, thanks a lot! I'll report back when I test this out. Also, am I supposed to flash a baseband and/or a different bootloader? I'm really new to this stuff, and I don't 100% know everything to do, and some tutorials aren't 100% clear, because I guess they're assuming the viewer knows what they're doing.
Click to expand...
Click to collapse
No baseband, just the bootloader the OP specifies. You just need to read, read and read some more. It may be confusing at first but you'll figure it out. A good thing to have on your computer is here, http://forum.xda-developers.com/showthread.php?t=2663369 . It makes it very easy to go back to KK and start over if you need to. I've used this a number of times and have gone back from LP without a problem. Once again, read the OP until you understand what you need to do.

Really now said:
No baseband, just the bootloader the OP specifies. You just need to read, read and read some more. It may be confusing at first but you'll figure it out. A good thing to have on your computer is here, http://forum.xda-developers.com/showthread.php?t=2663369 . It makes it very easy to go back to KK and start over if you need to. I've used this a number of times and have gone back from LP without a problem. Once again, read the OP until you understand what you need to do.
Click to expand...
Click to collapse
What if the OP doesn't specifie? Because I didn't even know I needed to flash that, till this point, haha. Yeah, I've used that, and have that. This past weekend I soft bricked my phone, probably around 10 times, and I used that each time, haha.

Wezurii4694 said:
What if the OP doesn't specifie? Because I didn't even know I needed to flash that, till this point, haha. Yeah, I've used that, and have that. This past weekend I soft bricked my phone, probably around 10 times, and I used that each time, haha.
Click to expand...
Click to collapse
I don't know of any of the caff LP versions that don't state that you need to flash the correct bootstack. If in doubt, don't flash it. If you were trying to install cyanogenmod 12 it doesn't require a bootstack flash but 12.1 does. You have to be sure of what you're trying to install. You might try running this http://forum.xda-developers.com/att-g2/development/rom-stock-lollipop-30b-stripped-t3144195 . Same dev that builds TWRP that I sent you to put this together. It's an all in one flash! And since it's in the at&t section it's not bloated with issues from users of different G2 variants. Just a thought.

Really now said:
I don't know of any of the caff LP versions that don't state that you need to flash the correct bootstack. If in doubt, don't flash it. If you were trying to install cyanogenmod 12 it doesn't require a bootstack flash but 12.1 does. You have to be sure of what you're trying to install. You might try running this http://forum.xda-developers.com/att-g2/development/rom-stock-lollipop-30b-stripped-t3144195 . Same dev that builds TWRP that I sent you to put this together. It's an all in one flash! And since it's in the at&t section it's not bloated with issues from users of different G2 variants. Just a thought.
Click to expand...
Click to collapse
Alright. I got around to trying what you suggested. Still a boot loop on Resurrection Remix, and I don't know why. I flashed the bootstack for my phone, that the post said to, then the rom, then Gapps. So I have no idea what I have to do to get this to work.

Wezurii4694 said:
Alright. I got around to trying what you suggested. Still a boot loop on Resurrection Remix, and I don't know why. I flashed the bootstack for my phone, that the post said to, then the rom, then Gapps. So I have no idea what I have to do to get this to work.
Click to expand...
Click to collapse
I'm assuming that you're on stock rooted LP and you've only tried flashing the RR rom. I haven't flashed that one in a long time but I see on the last few pages of the thread that there are several people getting stuck in bootloops. Is it the rom or their installation? I don't know but I'd seriously try a different rom. The latest Cloudy G2 3.3 is an excellent rom and everything works. It's my go to backup rom. The least confusing way to install it is to follow this,
http://forum.xda-developers.com/showpost.php?p=61396344&postcount=465 although you'd be flashing the 3.3 version not the 3.1. On the aosp side, I've been using Vanir https://androidfilehost.com/?w=files&flid=28988 with TK Gapps https://www.androidfilehost.com/?w=files&flid=31524 and this bootstack https://androidfilehost.com/?fid=24052804347760740 . Right now I'm running Slim Saber http://forum.xda-developers.com/lg-g2/development/rom-slimlp-alpha-0-4-t3135141 . It's a very nice rom too. Other than that I don't know how else to help.

Really now said:
I'm assuming that you're on stock rooted LP and you've only tried flashing the RR rom. I haven't flashed that one in a long time but I see on the last few pages of the thread that there are several people getting stuck in bootloops. Is it the rom or their installation? I don't know but I'd seriously try a different rom. The latest Cloudy G2 3.3 is an excellent rom and everything works. It's my go to backup rom. The least confusing way to install it is to follow this,
http://forum.xda-developers.com/showpost.php?p=61396344&postcount=465 although you'd be flashing the 3.3 version not the 3.1. On the aosp side, I've been using Vanir https://androidfilehost.com/?w=files&flid=28988 with TK Gapps https://www.androidfilehost.com/?w=files&flid=31524 and this bootstack https://androidfilehost.com/?fid=24052804347760740 . Right now I'm running Slim Saber http://forum.xda-developers.com/lg-g2/development/rom-slimlp-alpha-0-4-t3135141 . It's a very nice rom too. Other than that I don't know how else to help.
Click to expand...
Click to collapse
Alright, I'll try it out. You've been really helpful. I'll let you know how it goes. I had to reflash Kitkat, so I'm about to update to Lollipop again.

Wezurii4694 said:
Alright, I'll try it out. You've been really helpful. I'll let you know how it goes. I had to reflash Kitkat, so I'm about to update to Lollipop again.
Click to expand...
Click to collapse
Good luck! One other thing I was going to say is that if you want a great camera/video and a stock like experience with a lot of features then go with the Cloudy G2 3.3. It's based on the LG firmware so it's a good place to start and get rid of all of the at&t bloatware.

Wezurii4694 said:
Alright, I'll try it out. You've been really helpful. I'll let you know how it goes. I had to reflash Kitkat, so I'm about to update to Lollipop again.
Click to expand...
Click to collapse
Really now said:
Good luck! One other thing I was going to say is that if you want a great camera/video and a stock like experience with a lot of features then go with the Cloudy G2 3.3. It's based on the LG firmware so it's a good place to start and get rid of all of the at&t bloatware.
Click to expand...
Click to collapse
Oh, in what order do I do everything? Just to make sure.
Edit: Never mind.

Wezurii4694 said:
Oh, in what order do I do everything? Just to make sure.
Edit: Never mind.
Click to expand...
Click to collapse
One other thing that occurred to me, are you doing full wipes in TWRP? You have to select Wipe-Advanced Wipe-then check off Dalvik,System,Data,Cache (DO NOT check off Internal Storage) and then swipe the slider. I always do it 3 times, press the back button and Factory Reset 3 times. Probably overkill but it works for me. Then go back and do the install.

Really now said:
One other thing that occurred to me, are you doing full wipes in TWRP? You have to select Wipe-Advanced Wipe-then check off Dalvik,System,Data,Cache (DO NOT check off Internal Storage) and then swipe the slider. I always do it 3 times, press the back button and Factory Reset 3 times. Probably overkill but it works for me. Then go back and do the install.
Click to expand...
Click to collapse
I've always only ever done the advanced wipe. I'll do the three times thing, this time.

Wezurii4694 said:
I've always only ever done the advanced wipe. I'll do the three times thing, this time.
Click to expand...
Click to collapse
I do it 3 times because on my old Galaxy Note I noticed a few times that when I flashed a new rom a few things that I hadn't installed were still there. So I got in the 3 wipe habit.

Really now said:
I do it 3 times because on my old Galaxy Note I noticed a few times that when I flashed a new rom a few things that I hadn't installed were still there. So I got in the 3 wipe habit.
Click to expand...
Click to collapse
Oh, okay. Oh, when do I flash the kernal?

Wezurii4694 said:
Alright. I got around to trying what you suggested. Still a boot loop on Resurrection Remix, and I don't know why. I flashed the bootstack for my phone, that the post said to, then the rom, then Gapps. So I have no idea what I have to do to get this to work.
Click to expand...
Click to collapse
Well you're bound and determined to keep flashing the same rom over and over and it doesn't work. If it were me I'd move on to a different rom.

Really now said:
Well you're bound and determined to keep flashing the same rom over and over and it doesn't work. If it were me I'd move on to a different rom.
Click to expand...
Click to collapse
I meant on Cloudy. I'm trying that out.

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.