I have combed every thread for the keywords relating to the 807t and have only come across one beta type rom and a few posts that state restoring a stock kernel and modem enables data on the 807t after installing some but not all 805 roms.
Right now I am running SweetRom with the stock kernel and modem from my 807t stock image.
My question is if there is any hope of a kernel (or rom) that still allows for data on this model or are there no devs with this device (or is any part of the 807t source not relesed, like the HTC radio on the HTC Rezound in regards to when CM was being developed)?
In relation to the kernel question I am particarly interested in why it seems restoring the modem and kernel does not work to acheive data on all 805 roms. I noticed the Iron rom does not seem to have data but a few others, sweetrom obviously included, do work. Are there reqiured files missing from the roms that this method does not work on?
Sorry, just trying to get a bit more performance and customization out of this device but having data is a must.
Thanks for any information available and happy Thanksgiving to everyone!!!
Badumpabump
NXLTrauma25 said:
Badumpabump
Click to expand...
Click to collapse
I was in the process of comparing T807T and IronRom T805 files. Could it also be some APN settings and all that? Perhaps changing it somewhere in settings.. I dont really know. Ill definetly take a look at the differences. Maybe a test port build of IronRom if I can manage to do it.
Sent from my SM-T800 using Tapatalk
DUHAsianSKILLZ said:
I was in the process of comparing T807T and IronRom T805 files. Could it also be some APN settings and all that? Perhaps changing it somewhere in settings.. I dont really know. Ill definetly take a look at the differences. Maybe a test port build of IronRom if I can manage to do it.
Sent from my SM-T800 using Tapatalk
Click to expand...
Click to collapse
I would be more than happy to test. I am laid up for weeks after another major surgery so you can throw whatever you want at me haha. Thanks for the precursory look.
DUHAsianSKILLZ said:
I was in the process of comparing T807T and IronRom T805 files. Could it also be some APN settings and all that? Perhaps changing it somewhere in settings.. I dont really know. Ill definetly take a look at the differences. Maybe a test port build of IronRom if I can manage to do it.
Sent from my SM-T800 using Tapatalk
Click to expand...
Click to collapse
Also just out of curiosity do you know if a android also backs up foldermount mounts? I have so much mounted to the ext sdcard that I was just curious if formatting cleanly to try out different Roms and apns would negate the band road I have in that when I restore it the foldermount will need to be redone all over again.
NXLTrauma25 said:
I have combed every thread for the keywords relating to the 807t and have only come across one beta type rom and a few posts that state restoring a stock kernel and modem enables data on the 807t after installing some but not all 805 roms.
Right now I am running SweetRom with the stock kernel and modem from my 807t stock image.
My question is if there is any hope of a kernel (or rom) that still allows for data on this model or are there no devs with this device (or is any part of the 807t source not relesed, like the HTC radio on the HTC Rezound in regards to when CM was being developed)?
In relation to the kernel question I am particarly interested in why it seems restoring the modem and kernel does not work to acheive data on all 805 roms. I noticed the Iron rom does not seem to have data but a few others, sweetrom obviously included, do work. Are there reqiured files missing from the roms that this method does not work on?
Sorry, just trying to get a bit more performance and customization out of this device but having data is a must.
Thanks for any information available and happy Thanksgiving to everyone!!!
Click to expand...
Click to collapse
You're disregarding the fact that Samsung use the EFS partition to hold a lot of important data regarding radio.
It doesn't necessarily have to be the rom or the kernel.
ashyx said:
You're disregarding the fact that Samsung use the EFS partition to hold a lot of important data regarding radio.
It doesn't necessarily have to be the rom or the kernel.
Click to expand...
Click to collapse
I understand that. It's been a bit since I switched Roms on the tab but I believe you also have to restore the stock EFS as well. Could the EFS and modem be left alone entirely or would that negate the ability to really do much?
NXLTrauma25 said:
I would be more than happy to test. I am laid up for weeks after another major surgery so you can throw whatever you want at me haha. Thanks for the precursory look.
Click to expand...
Click to collapse
Okay, can you perhaps test this one for me? https://www.androidfilehost.com/?fid=24269982087006147 I have replaced many system files from IronRom with some from T807T. Be sure to make a backup of your device (including EFS too) and let me know if data works fine. Thanks!
DUHAsianSKILLZ said:
Okay, can you perhaps test this one for me? https://www.androidfilehost.com/?fid=24269982087006147 I have replaced many system files from IronRom with some from T807T. Be sure to make a backup of your device (including EFS too) and let me know if data works fine. Thanks!
Click to expand...
Click to collapse
Going to grab it now. You think it will mess up my folder mount stuff if I restore back after?
NXLTrauma25 said:
Going to grab it now. You think it will mess up my folder mount stuff if I restore back after?
Click to expand...
Click to collapse
Perhaps you can use titiaium back to backup the mount data from folder mount. I never used folder mount so... I cant give much informatiom on it.
Sent from my SM-T800 using Tapatalk
Backing up and flashing now buddy . Will update, thanks for helping either way.
DUHAsianSKILLZ said:
Perhaps you can use titiaium back to backup the mount data from folder mount. I never used folder mount so... I cant give much informatiom on it.
Sent from my SM-T800 using Tapatalk
Click to expand...
Click to collapse
Flashed it, chose stock kernel in aroma. Did not restore EFS, boot, or radio as I wanted to just see if it booted first. It did and the apn was of course empty although it didn't seem to send any messages about the sim card not being detected.... Might be a good thing. Just restored EFS, boot and radio and will update shortly if that brought data in.
No go, although it said nothing in terms of errors, there is a full signal bar. Can you post the apn for t-mobile on the tab? I can try creating that and seeing if that works which I'd imagine would.
NXLTrauma25 said:
No go, although it said nothing in terms of errors, there is a full signal bar. Can you post the apn for t-mobile on the tab? I can try creating that and seeing if that works which I'd imagine would.
Click to expand...
Click to collapse
Here is the apn stuff for T807T https://support.t-mobile.com/docs/DOC-19139
Hopefully its just an apn problem. When you flashed the T805 ironrom (not the one by me that i posted) did it have any sim card issues?
Sent from my SM-T800 using Tapatalk
No go. I honestly don't remember, for the vast majority of Roms yes it had an error. I'll download iron rom for 805 now and double check
DUHAsianSKILLZ said:
Here is the apn stuff for T807T https://support.t-mobile.com/docs/DOC-19139
Hopefully its just an apn problem. When you flashed the T805 ironrom (not the one by me that i posted) did it have any sim card issues?
Sent from my SM-T800 using Tapatalk
Click to expand...
Click to collapse
Alright reflashing the original 805 IronRom now. Out of curiosity do you have the modem, kernel and bootloader tags for Odin? I'm wondering if there is any difference in doing it that way rather then doing it via twrp and a backup.
DUHAsianSKILLZ said:
Here is the apn stuff for T807T https://support.t-mobile.com/docs/DOC-19139
Hopefully its just an apn problem. When you flashed the T805 ironrom (not the one by me that i posted) did it have any sim card issues?
Sent from my SM-T800 using Tapatalk
Click to expand...
Click to collapse
Upon activating mobile data on a clean flash of IronRom 805 (not your special version) without restoring any 807 files, a pop comes up and says "insert sim card to access network services. "
NXLTrauma25 said:
Upon activating mobile data on a clean flash of IronRom 805 (not your special version) without restoring any 807 files, a pop comes up and says "insert sim card to access network services. "
Click to expand...
Click to collapse
Great to know! So my special build fixed sim card but no data is coming through. Did adding the apn on my build fix the connection? (Thanks alot for the help)
Sent from my SM-T800 using Tapatalk
---------- Post added at 11:29 PM ---------- Previous post was at 11:27 PM ----------
NXLTrauma25 said:
Alright reflashing the original 805 IronRom now. Out of curiosity do you have the modem, kernel and bootloader tags for Odin? I'm wondering if there is any difference in doing it that way rather then doing it via twrp and a backup.
Click to expand...
Click to collapse
Flashing/restoring through twrp is the same as odin except the bootloader stuff. (Most times you dont need to mess with it)
Sent from my SM-T800 using Tapatalk
DUHAsianSKILLZ said:
Great to know! So my special build fixed sim card but no data is coming through. Did adding the apn on my build fix the connection? (Thanks alot for the help)
Sent from my SM-T800 using Tapatalk
Click to expand...
Click to collapse
OK so adding the apn did nothing. Now the last time I tried using iron rom and restoring efs/radio/boot I would either get a bootloop or that error about the sim card. All those times were on older builds.
Well good news. Flashing ironrom and restoring the stock files I mentioned above worked as far as bringing data back. Not sure what was changed in ironrom that allowed this to happen but yeah it works.
Now as for other Roms and your fixes, may still be a no go but it looks like it depends on certain files being added or removed from the rom which ironrom and sweetrom seem to have exactly what is needed.
BTW just because iron works now I am still totally down to still test for you if you want to develop a 807t rom.
The only issue left is a custom kernel for 807t. I think the biggest performance gains would come from that in terms of the choppiness in games and any possible battery saving. You wouldn't happen to be or or know of anyone interested in just playing around with making a kernel or porting a kernel to this?
DUHAsianSKILLZ said:
Great to know! So my special build fixed sim card but no data is coming through. Did adding the apn on my build fix the connection? (Thanks alot for the help)
Sent from my SM-T800 using Tapatalk
---------- Post added at 11:29 PM ---------- Previous post was at 11:27 PM ----------
Flashing/restoring through twrp is the same as odin except the bootloader stuff. (Most times you dont need to mess with it)
Sent from my SM-T800 using Tapatalk
Click to expand...
Click to collapse
You wouldn't happen to have any experience with kernels would you?
Related
Please Note: No other method listed in the GN2, GS3 forums work for this particular problem. I, as well as a few others have had this happen when flashing different ROMs. I have no idea what causes it but I do have an idea as to how to fix it. I just can't because what I need seems to be disabled in the phone.
Also, I did make a backup of my EFS and a restore does not fix this particular problem.
Problem #1:
After flashing a ROM, the GN2 is unable to activate the radio/modem. The following read "Unknown" in the "About Phone" menu:
Baseband, Network, Mobile Network Type, MEID, IMEI, ICCID.....etc. Basically anything to do with the mobile network.
Problem #2:
When booted up and running, PC will not recognize the phone as usual (unable to copy files to phone).
Problem #3:
And probably the biggest problem: ADB does not recognize the phone. ADB debugging is enabled on the phone in Developer Options but the icon on the notification button doesn't appear. Nor does ADB recognize the phone in recovery. So therefor I cannot transfer files this way either. "nvbackup/nvrestore" can not be used because of this either.
The following methods have all been tried and have failed. Yes, I know what I am doing,
http://forum.xda-developers.com/showthread.php?t=1867442
http://forum.xda-developers.com/showthread.php?t=1852255
http://forum.gsmhosting.com/vbb/f606/tutorial-galaxy-s3-backup-restore-imei-without-root-1513909/
I fell victim to #1 the IMEI wipeout I had to take my phone back for a replacement
Sent from my SPH-L900 using xda premium
Me too. ..
Sent from my MASSIVE Galaxy Note® II...*
mackentosh said:
I fell victim to #1 the IMEI wipeout I had to take my phone back for a replacement
Sent from my SPH-L900 using xda premium
Click to expand...
Click to collapse
but how did it happened ? can u please explain steps what u did that wiped yr imei?
t3project said:
Please Note: No other method listed in the GN2, GS3 forums work for this particular problem. I, as well as a few others have had this happen when flashing different ROMs. I have no idea what causes it but I do have an idea as to how to fix it. I just can't because what I need seems to be disabled in the phone.
Also, I did make a backup of my EFS and a restore does not fix this particular problem.
Problem #1:
After flashing a ROM, the GN2 is unable to activate the radio/modem. The following read "Unknown" in the "About Phone" menu:
Baseband, Network, Mobile Network Type, MEID, IMEI, ICCID.....etc. Basically anything to do with the mobile network.
Problem #2:
When booted up and running, PC will not recognize the phone as usual (unable to copy files to phone).
Problem #3:
And probably the biggest problem: ADB does not recognize the phone. ADB debugging is enabled on the phone in Developer Options but the icon on the notification button doesn't appear. Nor does ADB recognize the phone in recovery. So therefor I cannot transfer files this way either. "nvbackup/nvrestore" can not be used because of this either.
The following methods have all been tried and have failed. Yes, I know what I am doing,
http://forum.xda-developers.com/showthread.php?t=1867442
http://forum.xda-developers.com/showthread.php?t=1852255
http://forum.gsmhosting.com/vbb/f606/tutorial-galaxy-s3-backup-restore-imei-without-root-1513909/
Click to expand...
Click to collapse
i got the same problem with tmobile ver the problem is the partition i did tried to repartition in odin with gt-7100 pit file it did not work
can you see your storge and see your internal sd space
sorry for my english
An fyi when u get ur baseband back 3g will not work. I was able to get mine all back and working but I was always on 1x. T3 hit me up in gtalk.
Sent from my SPH-L900 using Tapatalk 2
gotojanoo said:
but how did it happened ? can u please explain steps what u did that wiped yr imei?
Click to expand...
Click to collapse
Well I was testing a rom for someone, I wont tell which rom but he said it was the "in call recorder" he added. He's got it fixed now but it did wipe everything. I managed to restore it back to stock with no root but it bricked after that. Now I see why carriers dont like to unlock bootloaders cause of people bricking their phone and taking them back
Sent from my SPH-L900 using xda premium
t3project said:
Please Note: No other method listed in the GN2, GS3 forums work for this particular problem. I, as well as a few others have had this happen when flashing different ROMs. I have no idea what causes it but I do have an idea as to how to fix it. I just can't because what I need seems to be disabled in the phone.
Also, I did make a backup of my EFS and a restore does not fix this particular problem.
Problem #1:
After flashing a ROM, the GN2 is unable to activate the radio/modem. The following read "Unknown" in the "About Phone" menu:
Baseband, Network, Mobile Network Type, MEID, IMEI, ICCID.....etc. Basically anything to do with the mobile network.
Problem #2:
When booted up and running, PC will not recognize the phone as usual (unable to copy files to phone).
Problem #3:
And probably the biggest problem: ADB does not recognize the phone. ADB debugging is enabled on the phone in Developer Options but the icon on the notification button doesn't appear. Nor does ADB recognize the phone in recovery. So therefor I cannot transfer files this way either. "nvbackup/nvrestore" can not be used because of this either.
The following methods have all been tried and have failed. Yes, I know what I am doing,
http://forum.xda-developers.com/showthread.php?t=1867442
http://forum.xda-developers.com/showthread.php?t=1852255
http://forum.gsmhosting.com/vbb/f606/tutorial-galaxy-s3-backup-restore-imei-without-root-1513909/
Click to expand...
Click to collapse
You care to clarify which ROM you flashed in particular caused this to happen so that we don't replicate your problem? I want to assume it's your own ROM but just want to make sure.
mackentosh said:
Well I was testing a rom for someone, I wont tell which rom but he said it was the "in call recorder" he added. He's got it fixed now but it did wipe everything. I managed to restore it back to stock with no root but it bricked after that. Now I see why carriers dont like to unlock bootloaders cause of people bricking their phone and taking them back
Click to expand...
Click to collapse
Uhh.. no offense to anyone, but if we have a rogue ROM that's bricking phones, we need to know in case it's floating around somewhere.
Also, (and again, not to start any negativity, just curious) the general feel of this thread was random bricking from flashing any ROM, which is very scary and cause for alarm. But according to the quoted post I'm gathering now that this is an issue directly related to accidents within a specific ROM?
ffolkes said:
Uhh.. no offense to anyone, but if we have a rogue ROM that's bricking phones, we need to know in case it's floating around somewhere.
Also, (and again, not to start any negativity, just curious) the general feel of this thread was random bricking from flashing any ROM, which is very scary and cause for alarm. But according to the quoted post I'm gathering now that this is an issue directly related to accidents within a specific ROM?
Click to expand...
Click to collapse
i did flash the s3 rom and after that i lost everythng my phone i need to know how to restor the orgenal sd card cuz im looking with rootexplore it sdcard0
when i go to setting storge it only show 266mb used and 0.00 avilabel any body can help please
mackentosh said:
Well I was testing a rom for someone, I wont tell which rom but he said it was the "in call recorder" he added. He's got it fixed now but it did wipe everything. I managed to restore it back to stock with no root but it bricked after that. Now I see why carriers dont like to unlock bootloaders cause of people bricking their phone and taking them back
Sent from my SPH-L900 using xda premium
Click to expand...
Click to collapse
Which ROM had the "In Call Recorder"? I've been looking for a replacement to that functionality after dropping HTC/ Qualcomm with the 2WCR patch on the kernel. ..
Sent from my SPH-L900 using xda app-developers app
You cant flash a s3 rom the partitions are different. Even the partitions forbthe international note 2. Tmo. Att. Verizon and sprint note 2 are different.
Try flashing the stock tar from sex tape or viper boy. This should fix those issues. Then update the phones prl. Profile. Software. And firmware. And see if u have 3g and everything else.
Then start over.
Sent from my SPH-L900 using Tapatalk 2
ffolkes said:
Uhh.. no offense to anyone, but if we have a rogue ROM that's bricking phones, we need to know in case it's floating around somewhere.
Also, (and again, not to start any negativity, just curious) the general feel of this thread was random bricking from flashing any ROM, which is very scary and cause for alarm. But according to the quoted post I'm gathering now that this is an issue directly related to accidents within a specific ROM?
Click to expand...
Click to collapse
it wasnt a rogue rom. it was two seperate private roms that were never released to the public
there is a very simple fix to this, i've fixed 2 phones this morning already with it. i'll post it up in a few
gotojanoo said:
but how did it happened ? can u please explain steps what u did that wiped yr imei?
Click to expand...
Click to collapse
it didnt actually wipe our imei. it repartitioned the phone.
t3project said:
it wasnt a rogue rom. it was two seperate private roms that were never released to the public
there is a very simple fix to this, i've fixed 2 phones this morning already with it. i'll post it up in a few
Click to expand...
Click to collapse
Good to know it wasn't released here publicly. Happy to hear you found a solution to the problem too.
dc13 said:
You cant flash a s3 rom the partitions are different. Even the partitions forbthe international note 2. Tmo. Att. Verizon and sprint note 2 are different.
Try flashing the stock tar from sex tape or viper boy. This should fix those issues. Then update the phones prl. Profile. Software. And firmware. And see if u have 3g and everything else.
Then start over.
Sent from my SPH-L900 using Tapatalk 2
Click to expand...
Click to collapse
Try this.
ffolkes said:
Uhh.. no offense to anyone, but if we have a rogue ROM that's bricking phones, we need to know in case it's floating around somewhere.
Also, (and again, not to start any negativity, just curious) the general feel of this thread was random bricking from flashing any ROM, which is very scary and cause for alarm. But according to the quoted post I'm gathering now that this is an issue directly related to accidents within a specific ROM?
Click to expand...
Click to collapse
I said I was testing a rom which means I was the only person he released it to at the time. I dont want to reveal the rom or the dev because I dont want any negativity towards him he's a great dev and your probably running his rom right now. So dont worry there isnt a rogue rom floating around
Sent from my SPH-L900 using xda premium
t3project said:
it wasnt a rogue rom. It was two seperate private roms that were never released to the public
there is a very simple fix to this, i've fixed 2 phones this morning already with it. I'll post it up in a few
Click to expand...
Click to collapse
whats the fix cuz im going thru this problem right now ...i cant get any service (radios)
EDIT: NVM I JUST FLASHED TO STOCK RECOVERY THEN FLASHED STOCK LJ1 THRU ODIN AND ALL IS WELL NOW
mccurt29 said:
whats the fix cuz im going thru this problem right now ...i cant get any service (radios)
EDIT: NVM I JUST FLASHED TO STOCK RECOVERY THEN FLASHED STOCK LJ1 THRU ODIN AND ALL IS WELL NOW
Click to expand...
Click to collapse
simple, wasnt it? lol..................
mackentosh said:
I said I was testing a rom which means I was the only person he released it to at the time. I dont want to reveal the rom or the dev because I dont want any negativity towards him he's a great dev and your probably running his rom right now. So dont worry there isnt a rogue rom floating around
Sent from my SPH-L900 using xda premium
Click to expand...
Click to collapse
Was it mine? I can tell you that if any of the previous stuff happened to you, it wasn't from the ROM. Could have been a bad download, coinsidence, etc. The ROM flash wouldn't have caused it.
Sent from my SPH-L900 using Tapatalk 2
Since it appears the One also can potentially lose its IMEI upon flashing an AOSP rom like a few other devices, I have a couple of questions...
#1 - will "adb reboot nvbackup" and nvrestore work on the One, or was that a Samsung only thing for the S3?
#2 - I was about to ask about backing up EFS via recovery, but it appears, at least with TWRP, that's not an option yet
#3 - is there any other way to backup the IMEI before flashing an AOSP rom? I've had no issues with CM, but after NOT backing up my IMEI when I had a GS3 and going through the massive headache to get that working again, I'd prefer to have a backup before trying any others
TIA!
jntdroid said:
Since it appears the One also can potentially lose its IMEI upon flashing an AOSP rom like a few other devices, I have a couple of questions...
#1 - will "adb reboot nvbackup" and nvrestore work on the One, or was that a Samsung only thing for the S3?
#2 - I was about to ask about backing up EFS via recovery, but it appears, at least with TWRP, that's not an option yet
#3 - is there any other way to backup the IMEI before flashing an AOSP rom? I've had no issues with CM, but after NOT backing up my IMEI when I had a GS3 and going through the massive headache to get that working again, I'd prefer to have a backup before trying any others
TIA!
Click to expand...
Click to collapse
yuuup.... I jumped the gun and installed GPE without even considering this... now no VZ signal even after the restore. am I totally screwed without a backup?
Wait what's going on? I've flashed a few aosp ROMs already and back to sense and haven't lost anything g yet as far as I can see
Sent from my One using Tapatalk now Free
crazyg0od33 said:
Wait what's going on? I've flashed a few aosp ROMs already and back to sense and haven't lost anything g yet as far as I can see
Sent from my One using Tapatalk now Free
Click to expand...
Click to collapse
Same here - well only CM so far. But others are reporting what sounds like IMEI loss after flashing AOSP. Doesn't sound as widespread as it was with the S3 - but if there's even a remote chance, I don't want to mess with it! Just hoping to get more info... hopefully it's not as big of a concern.
jntdroid said:
Same here - well only CM so far. But others are reporting what sounds like IMEI loss after flashing AOSP. Doesn't sound as widespread as it was with the S3 - but if there's even a remote chance, I don't want to mess with it! Just hoping to get more info... hopefully it's not as big of a concern.
Click to expand...
Click to collapse
what happens with an IMEI loss? we lose cell service?
BaBnkr said:
yuuup.... I jumped the gun and installed GPE without even considering this... now no VZ signal even after the restore. am I totally screwed without a backup?
Click to expand...
Click to collapse
If you are S-OFF, flash the RUU posted, and that will fix you up.
Yikes. I've flashed GPE (didn't enjoy so much), bonestock (LOVE) and am now on CM (like so far) and haven't had any issue. Hopefully I don't!
Sent from my HTC One.
Has anybody figured this out yet and is it still an issue??
Sent from my HTC6500LVW using xda app-developers app
andybones said:
If you are S-OFF, flash the RUU posted, and that will fix you up.
Click to expand...
Click to collapse
Yuup. That worked .
Sent from my stock (but rooted) VZW HTC One now Free
andybones said:
If you are S-OFF, flash the RUU posted, and that will fix you up.
Click to expand...
Click to collapse
Where is the RUU posted at?
Hey guys, I think I screwed up. I think that I lost my IMEI through flashing it and I didn't make a back up. It says 0 and only very few of the *# codes work, the *#7285# and #22745927 codes do absolutely nothing and the only one that I know of that works is *#*#4636#*#* which doesn't help me at all. Most programs that I use don't detect the phone correctly or my phones just downright wrecked. Example is DFS says CPS N/A in every section and Samsung MEID Repair says "Unhandled exception has occurred in your application" when I try to connect it to my phone.
I'm running CM11 4.4.1 and I had the problem when I was running a 4.3 ROM. Also I have data and I can make calls. Its just that I cant send MMS and I drop to edge over time and stay on edge until I restart.
Any help would be greatly appreciated. Everyone I call is saying it'll cost $65 - $75 IF they can even fix it.
Try to use nv writer to inject the imei.
http://forum.xda-developers.com/showthread.php?t=1804117
Note that if you reinject IMEI, it might screw up your network
audit13 said:
Try to use nv writer to inject the imei.
http://forum.xda-developers.com/showthread.php?t=1804117
Click to expand...
Click to collapse
I wish I could, When I try to use it, it says "Failed.. phone does not answer". Keep in mind that *#7284# doesnt do anything at all.
Did you know that you need to be completely stock in order to use the code?
Sent from my SAMSUNG-SGH-I747 using Tapatalk
pcshano said:
Did you know that you need to be completely stock in order to use the code?
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
I did not. That helps a LOT. Thank you so much. I havent tried going back yet, I'm gonna be more cautious about what i do now. Can I go back to stock from CM11 4.4.1 without screwing anything up? I keep seeing that you cant downgrade. Is that the case or is it just the case with official android roms?
Thank you so much, I feel like with your help I may be able to fix this. What im thinking that I have to do (I'll wait for your opinion) is that I should flash to stock, use the nv reader/writer, then ill be able to reroot it? When you say that it could screw up the network, what exactly do you mean?
chasetacos said:
I did not. That helps a LOT. Thank you so much. I havent tried going back yet, I'm gonna be more cautious about what i do now. Can I go back to stock from CM11 4.4.1 without screwing anything up? I keep seeing that you cant downgrade. Is that the case or is it just the case with official android roms?
Thank you so much, I feel like with your help I may be able to fix this. What im thinking that I have to do (I'll wait for your opinion) is that I should flash to stock, use the nv reader/writer, then ill be able to reroot it? When you say that it could screw up the network, what exactly do you mean?
Click to expand...
Click to collapse
I'm not sure what bootloader are you using
but IF your phone is fully unlocked, it doesn't matter, just flash 4.3 Stock and you're good to go
check out this post if you need help getting back to stock http://forum.xda-developers.com/showthread.php?t=2658486
the reason why you see people keep saying you can't "Downgrade" is mostly due to the bootloader you have, and it only apply to if and only if you're downgrading from MJB bootloader to a older version of Touchwiz (ie. Touchwiz 4.3 which will obviously come with MJB, thus you can't downgrade to 4.2 or 4.1 versions of touchwiz), not AOSP. if you're on AOSP in which CM is one, yes you can go from one AOSP to another, but no one does it because most of the time newer > older =D
pcshano said:
I'm not sure what bootloader are you using
but IF your phone is fully unlocked, it doesn't matter, just flash 4.3 Stock and you're good to go
check out this post if you need help getting back to stock http://forum.xda-developers.com/showthread.php?t=2658486
the reason why you see people keep saying you can't "Downgrade" is mostly due to the bootloader you have, and it only apply to if and only if you're downgrading from MJB bootloader to a older version of Touchwiz (ie. Touchwiz 4.3 which will obviously come with MJB, thus you can't downgrade to 4.2 or 4.1 versions of touchwiz), not AOSP. if you're on AOSP in which CM is one, yes you can go from one AOSP to another, but no one does it because most of the time newer > older =D
Click to expand...
Click to collapse
Cool. Im using CWM 6.0.4.3. Youre saying flash back to stock, then use the codes and the NV reader/writer? Also, when using the ZIP. am I using this through CWM "install zip"?
chasetacos said:
Cool. Im using CWM 6.0.4.3. Youre saying flash back to stock, then use the codes and the NV reader/writer? Also, when using the ZIP. am I using this through CWM "install zip"?
Click to expand...
Click to collapse
Yes.
but again you might want to update it to latest version since according to this http://forum.xda-developers.com/showthread.php?t=2658486, he mentioned version 6.0.4.5 and 6.0.4.7 though he didn't say if it's necessary to be but to be safe, you should so that you won't run into any issues.
though again, let me warn you, Reinjecting your IMEI, will work, BUT at the same time, it might screw up with your broadband
I experienced it once with one of my S3 and it stuck on either E or G network.. and I had to fix it by copy my efs folder to that phone in order to fix(and unless you have a good friend with S3 phone with same model, or own more than 1 S3, you won't be able to do it since nobody want to share, apply to me as well)
pcshano said:
Yes.
but again you might want to update it to latest version since according to this http://forum.xda-developers.com/showthread.php?t=2658486, he mentioned version 6.0.4.5 and 6.0.4.7 though he didn't say if it's necessary to be but to be safe, you should so that you won't run into any issues.
Click to expand...
Click to collapse
Cool. I Will do this and I will keep you updated. Itll be just a few moments before I complete the process
pcshano said:
Yes.
but again you might want to update it to latest version since according to this http://forum.xda-developers.com/showthread.php?t=2658486, he mentioned version 6.0.4.5 and 6.0.4.7 though he didn't say if it's necessary to be but to be safe, you should so that you won't run into any issues.
though again, let me warn you, Reinjecting your IMEI, will work, BUT at the same time, it might screw up with your broadband
I experienced it once with one of my S3 and it stuck on either E or G network.. and I had to fix it by copy my efs folder to that phone in order to fix(and unless you have a good friend with S3 phone with same model, or own more than 1 S3, you won't be able to do it since nobody want to share, apply to me as well)
Click to expand...
Click to collapse
So when I try to flash the stock I get an error status 7. Any advice?
chasetacos said:
So when I try to flash the stock I get an error status 7. Any advice?
Click to expand...
Click to collapse
funny a lot of people who use CWM got this error when trying to get back to stock lol
try TWRP.. it should definitely fix it
Cool. It may not be till tonight or tomorrow till I respond, I'm about to have a project m competition. I'll let you know how it goes as soon as I get a chance.
pcshano said:
funny a lot of people who use CWM got this error when trying to get back to stock lol
try TWRP.. it should definitely fix it
Click to expand...
Click to collapse
So now that Ive restored to stock, I have a transparent window with yellow text in it. it reads a bunch of info on the phone. It also said that it was in factory mode?
pcshano said:
funny a lot of people who use CWM got this error when trying to get back to stock lol
try TWRP.. it should definitely fix it
Click to expand...
Click to collapse
So despite being stuck in factory mode I was able to write the NV and luckily I dont have any new network problems as far as I know. However my IMEI now says / 00 and in the phone info it says "unknown"
So this is my progress so far. I have made connection with the NV items reader and I have saved the NV file. when i rewrote it i noticed that my imei is / 00 and it says unknown in the phone info. I have my imei and my converted imei and i was going to insert it into line 00550 but that line says "00550 (0x0226) - Inactive item". Factory mode is still on, I have edited the text files for both factory mode and keystr from ON to OFF and back again rebooting my phone each time and getting no result.
So im stuck in factory mode with / 00 imei. I can however make connection with programs now, I feel like im moving forward.
I feel like it may be worth noting that ive never ever seen a nv_data.bin in my phone....
chasetacos said:
So this is my progress so far. I have made connection with the NV items reader and I have saved the NV file. when i rewrote it i noticed that my imei is / 00 and it says unknown in the phone info. I have my imei and my converted imei and i was going to insert it into line 00550 but that line says "00550 (0x0226) - Inactive item". Factory mode is still on, I have edited the text files for both factory mode and keystr from ON to OFF and back again rebooting my phone each time and getting no result.
So im stuck in factory mode with / 00 imei. I can however make connection with programs now, I feel like im moving forward.
I feel like it may be worth noting that ive never ever seen a nv_data.bin in my phone....
Click to expand...
Click to collapse
make sure that you take your SIM out before injecting imei... then try again
and nv_data.bin is in your efs folder which you can only see it if you have some sort of root explorer
pcshano said:
make sure that you take your SIM out before injecting imei... then try again
and nv_data.bin is in your efs folder which you can only see it if you have some sort of root explorer
Click to expand...
Click to collapse
Still nothing, im getting the same result. This Nv data bin file is not in there. i mean, unless i dont know where to look, but ive checked the whole EFS folder and its not in there...
Hi try flash UCUEMJB 4.3 stock rom via odin .. I have same problem and the stock ROM fix my problem
Sent from my GT-P5113 using XDA Premium 4 mobile app
---------- Post added at 06:24 PM ---------- Previous post was at 06:06 PM ----------
I fix mine with this .....
Ok... I hated to see the posts about the tar file bricking a couple of phones. I had taken it down so not to brick anyone else's phone. But with over 400 downloads and only 2 reports I feel that it was fine, but in either case I have redone it. I have flashed it many many time now and my phone is fine.
Please only use Odin 3.0.7 http://forum.xda-developers.com/showthread.php?t=1722686
Make sure Auto Reboot and Re-Partition are checked. Uncheck F. Reset Time and anything else that might be checked.
Check and load the file in the PDA slot.
Start Flash and wait till it the phone reboots.
I747UCUEMJB 4.3 Odin flashable tar.
http://www.androidfilehost.com/?fid=23329332407590581
Sent from my GT-P5113 using XDA Premium 4 mobile app
elcocolo50 said:
Hi try flash UCUEMJB 4.3 stock rom via odin .. I have same problem and the stock ROM fix my problem
Sent from my GT-P5113 using XDA Premium 4 mobile app
---------- Post added at 06:24 PM ---------- Previous post was at 06:06 PM ----------
I fix mine with this .....
Ok... I hated to see the posts about the tar file bricking a couple of phones. I had taken it down so not to brick anyone else's phone. But with over 400 downloads and only 2 reports I feel that it was fine, but in either case I have redone it. I have flashed it many many time now and my phone is fine.
Please only use Odin 3.0.7 http://forum.xda-developers.com/showthread.php?t=1722686
Make sure Auto Reboot and Re-Partition are checked. Uncheck F. Reset Time and anything else that might be checked.
Check and load the file in the PDA slot.
Start Flash and wait till it the phone reboots.
I747UCUEMJB 4.3 Odin flashable tar.
http://www.androidfilehost.com/?fid=23329332407590581
Sent from my GT-P5113 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Unfortunately that did nothing . I might just have to cry about it
Is any method of root or custom ROM compatible with our T Mobile Samsung Note tablet? Coming from a HTC one m7 where all rom were compatible other then CDMA/ GSM
I've used the towelroot but really looking to install aosp on this thing already
Sent from my One using XDA Free mobile app
law16 said:
Is any method of root or custom ROM compatible with our T Mobile Samsung Note tablet? Coming from a HTC one m7 where all rom were compatible other then CDMA/ GSM
I've used the towelroot but really looking to install aosp on this thing already
Sent from my One using XDA Free mobile app
Click to expand...
Click to collapse
Your best bet is to ask in the rom thread. I have yet to flash anything on my P607T other then rooting. It looks like Dev work is very slow for this tablet. So you may not get a 100% working AOSP rom any time soon. Stock rom is really fast and sable once you root and deboat it. That is what I am sticking with for awhile.
Prod1702 said:
Your best bet is to ask in the rom thread. I have yet to flash anything on my P607T other then rooting. It looks like Dev work is very slow for this tablet. So you may not get a 100% working AOSP rom any time soon. Stock rom is really fast and sable once you root and deboat it. That is what I am sticking with for awhile.
Click to expand...
Click to collapse
I'm looking for ROMs too. But I think I'll stay with stock for now. Any recommendations on what apps to debloat?
dmunjal said:
I'm looking for ROMs too. But I think I'll stay with stock for now. Any recommendations on what apps to debloat?
Click to expand...
Click to collapse
Your best way is to just use TB and froze whatever you do not want. If you run into problems just unfroze it. If you uninstall and you run into a bootloop you will need to have the stock Odin firmware ready. here is a link to get the stock odin file.
http://www.sammobile.com/firmwares/3/?download=29807
I just uninstalled whatever I did not want. If you google What apps are safe to remove on a Note 3 to debloat, it will pretty much be the same as the 10.1. Both the note 3 and the 10.1 are pretty much the same other then screen.
Edit: I got this list from here
https://docs.google.com/spreadsheet...ZzBfWlR4MC03aDMyZ1BDUFNqU0E&usp=sharing#gid=0
Here is a a list for the GS4 which as a lot of the apps we have as well
http://forum.xda-developers.com/showthread.php?t=2317714
unlocking bootloader
I think we need to get the bootloader unlocked to get development on this thing rollin'
I'm willing to lend my device to a well-reputed senior-member/developer and pay shipping both ways if they think they can work some magic for the SM-P607T
Should I make a new post with regards to this?
Was able to root using this method no Knox either
http://forum.xda-developers.com/showthread.php?t=2785804
Sent from my SM-P607T using XDA Free mobile app
TG2008 said:
I think we need to get the bootloader unlocked to get development on this thing rollin'
I'm willing to lend my device to a well-reputed senior-member/developer and pay shipping both ways if they think they can work some magic for the SM-P607T
Should I make a new post with regards to this?
Click to expand...
Click to collapse
bootloader is unlocked and there is no problems getting root and current Twrp can be installed which says the bootloader is unlock. if the bootloader was locked you wouldn't be able to flash Twrp. from the looks of it no one has a p607. it is all 605 or the wifi only one p600 and 601. stock rom with root and debloated works great. try a 605 rom. hopefully CM starts to pick up more then we are set.
Sent from my HTC One_M8 using Tapatalk
Do P605 ROMs even work on a P607T? I've been wondering that myself. I have a 607T and although I am very impressed with the stock ROM it just is never going to measure up to CM for me.
I've been thinking about giving the P605 CM 11 port a try in a few weeks when it's just a bit more stable, but I have no idea how similar they are or if my device would even boot after flashing it!
amirite said:
Do P605 ROMs even work on a P607T?
Click to expand...
Click to collapse
Yes.
kcrudup said:
Yes.
Click to expand...
Click to collapse
Anyway to flash the "modem.bin" and "NON-HLOS.bin" flash partitions yet?
kcrudup said:
Yes.
Click to expand...
Click to collapse
And how do i install a dialer app to make voice call with my haedset on my note 10.1 2014 edition (T-Mobile) p607t..is it possible at all??
TG2008 said:
Anyway to flash the "modem.bin" and "NON-HLOS.bin" flash partitions yet?
Click to expand...
Click to collapse
Guys... Did you even read that thread in the link?
You should be asking these questions there... That whole thread is dedicated to making calls on the P607T.... And if you read the thread you'll know the author hit a brick wall and a boot loader hack is needed to flash the proper modem files for phone calls.
amirite said:
Guys... Did you even read that thread in the link?
Click to expand...
Click to collapse
Reading is Fundamental, amirite? (... sorry, couldn't resist )
But yeah, go there for any updates.
kcrudup said:
Reading is Fundamental, amirite? (... sorry, couldn't resist )
But yeah, go there for any updates.
Click to expand...
Click to collapse
Haha. Thank you kcrudup for pointing to that thread, gave me some useful info on using P605 Roms on a P607T.
Any idea about what sort of problems may pop up from doing this? I got a reply in the CM thread that their P605 version of CM should work fine on my P607 but... Surely it can't be that simple? Any idea what differences there are between thecode of the two tablets or is it really that similar?
amirite said:
I got a reply in the CM thread that their P605 version of CM should work fine on my P607- but surely it can't be that simple?
Click to expand...
Click to collapse
I'm 95% sure the only difference physically is the radio "front end" hardware is tuned for the T-Mo LTE frequencies so the modem baseband SW reflects that, and software-wise all that's new is a few pre-installed apps like the "My T-Mobile" app and that (loud-and-annoying-as-hell-and-quickly-removed) T-Mobile "jingle" on startup; I've put several P605 ROMs on my 607T and everything's worked OK ('cause the bootloader won't let me overwrite the radios and potentially-dangerous bootloader files anyway).
kcrudup said:
I'm 95% sure the only difference physically is the radio "front end" hardware is tuned for the T-Mo LTE frequencies so the modem baseband SW reflects that, and software-wise all that's new is a few pre-installed apps like the "My T-Mobile" app and that (loud-and-annoying-as-hell-and-quickly-removed) T-Mobile "jingle" on startup; I've put several P605 ROMs on my 607T and everything's worked OK ('cause the bootloader won't let me overwrite the radios and potentially-dangerous bootloader files anyway).
Click to expand...
Click to collapse
Awesome info thanks so much!! So if I understand correctly, any differnces that would render my tablet completely inoperable are already protected from flashing? So I don't need to meet with the TARs for the Roms to remove the modem files or anything?
I mean, I don't mind if my radio breaks or something, I can handle flashing back to stock I am just never sure when I start flashing a new Android device what risks there are of bricking it completely (which, with Knox in the picture, could totally screw me).
So with that I will probably be going flash crazy tonight and tomorrow to test our some different 605 Roms starting with Cyanogen. I'll try to post any findings or quarks here or in those threads!
amirite said:
So I don't need to [mess?] with the TARs for the Roms to remove the modem files or anything?
Click to expand...
Click to collapse
You will have to remove all the "*.mbn" and "*.bin" files from (Samsung-supplied) non-P607T ROMs, though- Odin will abort the flash if it receives a bad status from the bootloader when the bootloader rejects the flash operation. But it should be a straightforward unzip/rm/zip operation to repack, and I'm sure the CM flashes are just "boot" and "system" (and possibly "recovery") partitions anyway.
kcrudup said:
You will have to remove all the "*.mbn" and "*.bin" files from (Samsung-supplied) non-P607T ROMs, though- Odin will abort the flash if it receives a bad status from the bootloader when the bootloader rejects the flash operation. But it should be a straightforward unzip/rm/zip operation to repack, and I'm sure the CM flashes are just "boot" and "system" (and possibly "recovery") partitions anyway.
Click to expand...
Click to collapse
so is it necessary to remove the above mentioned files. I can't just flash a p605 rom with twrp?
stoehner said:
so is it necessary to remove the above mentioned files. I can't just flash a p605 rom with twrp?
Click to expand...
Click to collapse
Yes it is necessary, the .mbn files relate to the bootloader and the .bin files is the modem and NON_HLOS, being that they are for a different ROM it could cause major problems and maybe even bricking. @kcrudup even mentioned the bootloader conflicting with Odin if the device models don't match, so it seems you won't get the 605's installed without removing said files.
Prod1702 said:
Your best bet is to ask in the rom thread. I have yet to flash anything on my P607T other then rooting. It looks like Dev work is very slow for this tablet. So you may not get a 100% working AOSP rom any time soon. Stock rom is really fast and sable once you root and deboat it. That is what I am sticking with for awhile.
Click to expand...
Click to collapse
I have been looking for a guide for flashing twrp onto my sm-p607t but i cant find one. I mainly need the correct twrp img.tar file for odin. I found this one ( openrecovery-twrp-2.6.3.3-lt03wifiue.img ) but I don't know if it is the right one. I used towelroot to root it and i used the proper supersu to disable knox so i just need the custom recovery now.
I was having a problem trying to find the modem for my D851 here on XDA. There were many plainly listed for D855 and other models of the G3. I am using Paranoid/ASOP 5.1.1 Rom and I accidentally flashed a D855 radio. Rookie mistake, I know... And thought I backed up the modem along with the system files. Well I didn't and lost my imei, apn, signal and all... So while searching and again not obviously placed easy to find I read a thread and found one, flashed it, and it returned everything to normal without having to flash back to stock rom and blah blah blah... From what was listed, this for L 5.0 and up.
1. Boot phone into recovery, preferably TWRP
2. Flash the modem zip DOWNLOAD: https://www.dropbox.com/s/xz26z91hej9ryz3/LGD851.20B.MODEM-iNb4TMO.zip?dl=0
3. Reboot
I didn't make the radio, nor take any credit for its creation. I'm just trying to make it easier for T-Mobile D851 users on Lollipop to find incase they have deleted or lost theirs like I did...
I am not responsible for any issues or problems that may be encountered by using this.
I hope this help those in need like it helped me... Please let me know...
Im currently having a major issue with the lollipop update. I had my d851 with t mobile and I wouldn't lose lte when I would make a phone call... I currently switched to metropcs and now when I make a phone call I lose lte and my signal drops to 4g. I tried everything... APN, restoring the phone, called metro like a thousand times and nothing. Any help would be greatly appreciated.
Tito622 said:
Im currently having a major issue with the lollipop update. I had my d851 with t mobile and I wouldn't lose lte when I would make a phone call... I currently switched to metropcs and now when I make a phone call I lose lte and my signal drops to 4g. I tried everything... APN, restoring the phone, called metro like a thousand times and nothing. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Make sure you have volte enabled.
That's on too.
RussianBear said:
Make sure you have volte enabled.
Click to expand...
Click to collapse
I actually have the same issue, how do you enable volte?
firemedic0911
Model: T-Mobile D851/LG G3
Rom: Paranoid ASOPL
Version: 5.1.1
Build: May 28th, 2015
Sent on XDA Mobile Pro
firemedic0911 said:
I actually have the same issue, how do you enable volte?
firemedic0911
Model: T-Mobile D851/LG G3
Rom: Paranoid ASOPL
Version: 5.1.1
Build: May 28th, 2015
Sent on XDA Mobile Pro
Click to expand...
Click to collapse
Go to options - call.
Guys, what's the current latest radio version for our phone and does anyone have a link?
Tito622 said:
Im currently having a major issue with the lollipop update. I had my d851 with t mobile and I wouldn't lose lte when I would make a phone call... I currently switched to metropcs and now when I make a phone call I lose lte and my signal drops to 4g. I tried everything... APN, restoring the phone, called metro like a thousand times and nothing. Any help would be greatly appreciated.
Click to expand...
Click to collapse
did you ever figure this out or did you get a new phone?
psantos1091 said:
did you ever figure this out or did you get a new phone?
Click to expand...
Click to collapse
Flashing the 30D modem seemed to help quite a bit, the signal will drop to 4g while you're on a phone call but the data is alot faster. Give it a try, it worked for me.
Tito622 said:
Flashing the 30D modem seemed to help quite a bit, the signal will drop to 4g while you're on a phone call but the data is alot faster. Give it a try, it worked for me.
Click to expand...
Click to collapse
Where do you get the 30D modem?
kfcherry said:
Where do you get the 30D modem?
Click to expand...
Click to collapse
Here is one place:
https://forum.xda-developers.com/tm...ock-d851-30d-kdz-flashable-zips-imgs-t3367371
christoophat said:
Here is one place:
https://forum.xda-developers.com/tm...ock-d851-30d-kdz-flashable-zips-imgs-t3367371
Click to expand...
Click to collapse
Well, I went camping over the weekend and of course the phone dropped service again. The cell signal was weak and the data was almost non-existent. Luckily I brought an old phone, re-activated it, and was good with LTE signal. My question is would flashing a different modem help? I have the LG-D851 with SW version D85130e so I assume that has the 30e modem. Is that correct and would the 30d modem be better? Thanks.
kfcherry said:
Well, I went camping over the weekend and of course the phone dropped service again. The cell signal was weak and the data was almost non-existent. Luckily I brought an old phone, re-activated it, and was good with LTE signal. My question is would flashing a different modem help? I have the LG-D851 with SW version D85130e so I assume that has the 30e modem. Is that correct and would the 30d modem be better? Thanks.
Click to expand...
Click to collapse
No idea. Could be something else (mechanical) causing the issue. 30e is the latest for our phones. You can also drop it down to 30d & see if it is any better.
christoophat said:
No idea. Could be something else (mechanical) causing the issue. 30e is the latest for our phones. You can also drop it down to 30d & see if it is any better.
Click to expand...
Click to collapse
That's what I was hoping to do but was trying to see if there was a way to just install the 30D modem instead of loading the entire phone with the older SW version and having to re-install all of my apps. I downloaded the modem file but after doing some research I couldn't figure out the procedure to install it. I saw a few videos about a TWRP recovery but I prefer not to root my phone. If I have to root it in order to get it working then I will...I just wish I could figure out what the issue is. I saw a few other people mention issues with the LTE setting defaulting back to WCDMA/GSM (which I experience) and they said the 30E modem could be the issue. The phone was just wiped clean a few months ago before I bought it from the previous owner.
kfcherry said:
That's what I was hoping to do but was trying to see if there was a way to just install the 30D modem instead of loading the entire phone with the older SW version and having to re-install all of my apps. I downloaded the modem file but after doing some research I couldn't figure out the procedure to install it. I saw a few videos about a TWRP recovery but I prefer not to root my phone. If I have to root it in order to get it working then I will...I just wish I could figure out what the issue is. I saw a few other people mention issues with the LTE setting defaulting back to WCDMA/GSM (which I experience) and they said the 30E modem could be the issue. The phone was just wiped clean a few months ago before I bought it from the previous owner.
Click to expand...
Click to collapse
yeah without having root, your options are limited. If you own the phone, I would say go for it, if you are leasing it, then take it back to where you got it & tell them it's reception sucks.
I own it and bought it second hand. According to the previous owner he didn't have any issues with it but who knows. I assume if I root it and load the 30D SW I will have to load everything from scratch? Is there an LG backup program for this phone? Thanks for the help.
Restore from SD card
From any home screen, tap Apps.
Tap Settings.
Scroll down to 'DEVICE,' then tap Backup & reset.
Tap LG Backup service > Backup & restore.
Tap Restore from backup.
Locate and tap the SD card backup.
Tap Next.
Review the warning information, then tap OK to confirm.
---------- Post added at 12:51 PM ---------- Previous post was at 12:45 PM ----------
I have the TMo version (D851) & the first thing I did was root it & install a custom ROM to get rid of all the Tmo crap that is stuck onto it. ugh! I don't use my phone all that much for calls, mostly emails data & music playing, so losing the stock Wifi Calling function wasn't an issue for me. Currently on the OctOS Nougat weekly builds, tremendous ROM, great battery life fast & smooth & decluttered. Since you already own the phone & do not have a warranty, you've nothing to lose here. Do some reading in the threads on how to do it, you'll be very happy once you see how much better your phone can be. You put on it only what you want to put on, less junk, less memory hogging.