Database Users

T-Mobile Updating Baseband/Modem?

It's been a while since I last did this, and I'm afraid I'm quite confused...
I am running a custom ROM (Bliss Beta 6) but remembered that updating my ROM doesn't update my baseband/modem.
Are baseband and modem the same thing?
https://support.t-mobile.com/docs/DOC-10398
Using this site here I see that my current baseband (G900TUVU1CNK2) is super outdated. It tells me that G900T3UVU1FOG6 or G900TUVS1FOL1 are the latest, but I don't get why there are two. Which one should I install?
All that being said, can I install using TWRP and a zip, or do I need to ODIN it?
Any help would be appreciated, as I said I've done this before but can't find any updated tutorials that explain the questions I'm asking (I've tried searching google and XDA, if I missed something obvious I would appreciate a link!).
cheers

More research has helped me answer my own question! Sharing what I've found in case anyone else comes across this thread:
Baseband and Modem are effectively the same thing in this context.
G900T3UVU1FOG6 was released in August 2015 and has the fix for stage-fright.
G900TUVS1FOJ4 was released in November 2015
G900TUVS1FOL1 is pretty much brand new (released in December 2015) so there's not a lot on it. This is the one I'm going to try installing.
Followed the instructions from this thread http://forum.xda-developers.com/tmo.../compilation-s5-g900t-stock-firmware-t3042400 to figure it out.
More use information found here:
https://ohthehugemanatee.org/blog/2...m-slash-baseband-firmware-on-a-samsung-phone/

lioncat55 said:
More research has helped me answer my own question! Sharing what I've found in case anyone else comes across this thread:
Baseband and Modem are effectively the same thing in this context.
G900T3UVU1FOG6 was released in August 2015 and has the fix for stage-fright.
G900TUVS1FOJ4 was released in November 2015
G900TUVS1FOL1 is pretty much brand new (released in December 2015) so there's not a lot on it. This is the one I'm going to try installing.
Followed the instructions from this thread http://forum.xda-developers.com/tmo.../compilation-s5-g900t-stock-firmware-t3042400 to figure it out.
More use information found here:
https://ohthehugemanatee.org/blog/2...m-slash-baseband-firmware-on-a-samsung-phone/
Click to expand...
Click to collapse
i've been wondering this myself, so did you update your baseband & is there any change in battery or signal quality? (or i guess stagefright detector?)
also wondering if downgrading is no problem or if it affects anything like that (which stock samsung or other device kernels/ROMs do, sometimes blocking root etc)

Hey, so I actually updated to G900TUVS1FOL1 using ODIN. It nuked everything and installed regular TouchWiz which I wasn't a fan of, but I have no problem installing my own ROM later.
If you're doing the T-Mobile one, then there is no issue with rooting, installing kernels, custom ROMs, etc. I don't really know about "downgrading" the baseband or modem, but I don't think you would need to in this case.
Note that if you have Verizon or At&T you probably want to be SUPER careful, because they lock down everything.

lioncat55 said:
Hey, so I actually updated to G900TUVS1FOL1 using ODIN. It nuked everything and installed regular TouchWiz which I wasn't a fan of, but I have no problem installing my own ROM later.
If you're doing the T-Mobile one, then there is no issue with rooting, installing kernels, custom ROMs, etc. I don't really know about "downgrading" the baseband or modem, but I don't think you would need to in this case.
Note that if you have Verizon or At&T you probably want to be SUPER careful, because they lock down everything.
Click to expand...
Click to collapse
it's a g900t yes
i am going to look into upgrading it more directly rather than the complete samsung image... maybe... so you're confirming the official tmobile samsung 5.1.1 complete installation still lets you flash TWRP then cyanogen without a problem? i came from november 2014 samsung 4.4 to CM originally

kn00tcn said:
it's a g900t yes
i am going to look into upgrading it more directly rather than the complete samsung image... maybe... so you're confirming the official tmobile samsung 5.1.1 complete installation still lets you flash TWRP then cyanogen without a problem? i came from november 2014 samsung 4.4 to CM originally
Click to expand...
Click to collapse
yes, I installed G900TUVS1FOL1 with Odin, had root and TWRP installed just fine (couldn't get xposed to work because it was not a deoxdex rom of course). I just installed BlissPop ROM last night which is based on CM13. So yes, it didn't lock me down or anything.

Questions xt1265 Prime

Hi everyone,
I have the Moto G4 xt1625 Amazon Prime variation. Nevertheless, I took the regular steps to receive the unlock code on Motorola Website and they simply sent it to me. No idea if the fact that I live outside US and / or that my carrier is, obviously, from outside US had anything to do with it or if I was just lucky. I got the code, but I still never used it, which means I have the stock 6.0.1 android.
Now on to my questions:
1-My build number is MPJ24.139-64. What does that really means? I see people discussing this everywhere, some are 65. What difference does each build have?
2-I never heard of Firmware when speaking of mobiles. I always heard/changed the OS, but now you guys are changing firmware and OS. How do I know which firmware I have? How do I get the latest one?
3-Since I have the unlock code for the boot loader, does it virtually means I have a regular xt1625 Moto G4? I mean, as of now I still have the adds, but should I opt to unlock the boot loader and say flash CM 14.1 it would be the same as non Prime xt1625 or does the Prime version have other differences (build, firmware, etc)?
4-Can Moto G4 use the same ROMs as Moto G4 Plus? I've seen different answers regarding this matter. Would I have to flash base bands and/or soak test?
5-Is CM 14.1 (cm-14.1-20161225-NIGHTLY-athene.zip) the latest AOSP ROM for Moto G4?
Thank you in advance for your help and time! =]
Andre

Anyone? ^^

Maybe i can help you
1- This is like the version of firmware, or OS if you want to call like this way, (correct me if i am wrong)
2- Firware and OS are the same, i guess. Better call it ROM
3- Yes, the same. But i have the prime version locked so i cant tell you with 100% of security
4- Yes and no. the board is the same thing, you can install it but maybe you have problems like heat (not so much, of course)(because moto g+ have the cores boosted to 100%, and moto g non plus have 4 to 100% and 4 energy saver cores.)
5- NIGHTLY is a buggy software, this is not the software 100% tested. Maybe you have to wait a SNAPSHOT. This is more secure
Sorry for my English. I speak spanish better <3s

Thank you!!
What about the Indian 7.0 ROM? Can we install it without problems?

engandresr said:
Thank you!!
What about the Indian 7.0 ROM? Can we install it without problems?
Click to expand...
Click to collapse
If you have unlocked the bootloader of course! Yes!
But maybe you want to make a backup of everything before!
I will recommend to you wait until the official software for your smartpone arrive..
For some reason Motorola has not released it, maybe the Indian 7.0 is buggy and they are just testing with india...
But you can try without problems!
PD: Remember when i said without problems, Problems may appear like overheating, WiFi problems, etc etc. But you can have a taste of nougat! Just search a little, i know people who have Nougat in theirs XT1625, and is working "well" (overheating againg)
try this
->
https://forum.xda-developers.com/moto-g4/development/moto-g4-india-official-nougat-7-0-ota-t3533078

Hi,
I'm not a newbie here, but I think I can help u with some info since I have the same amz prime unlocked bootloader
Now on to my questions:
1-My build number is MPJ24.139-64. What does that really means? I see people discussing this everywhere, some are 65. What difference does each build have?
This is the latest build, that it's available for this phone version, this FW is the one that I had before I moved to RR.
2-I never heard of Firmware when speaking of mobiles. I always heard/changed the OS, but now you guys are changing firmware and OS. How do I know which firmware I have? How do I get the latest one?
FW es the specific version of a OS, the one that's meant to be on your phone
3-Since I have the unlock code for the boot loader, does it virtually means I have a regular xt1625 Moto G4? I mean, as of now I still have the adds, but should I opt to unlock the boot loader and say flash CM 14.1 it would be the same as non Prime xt1625 or does the Prime version have other differences (build, firmware, etc)?
Unlocking the bootloader means that it can support non official software, a custom recovery and after that you can root it, install a custom rom or mostly anything that you can think. But it still an specific branch oh the moto g4 the prime edition. So you can install Nougat from a TWRP, but not directly as an update or any other procedure
4-Can Moto G4 use the same ROMs as Moto G4 Plus? I've seen different answers regarding this matter. Would I have to flash base bands and/or soak test?
The moto G4 plus uses the same Hardware, custom roms can be used in any of those, not official roms
5-Is CM 14.1 (cm-14.1-20161225-NIGHTLY-athene.zip) the latest AOSP ROM for Moto G4?
CM is now gone, the new version of it would be Lineage OS, I personally use Resurrection Remix as my daily driver, it has TONS of customizations and it tells you whenever an update it's available.
Be carefeul with installing anything on your phone just have always a recovery back up in the micro sd and on a usb o pc available in case anything went wrong.
Hope this could help
Pardon my english.

omaktl said:
Hope this could help
Click to expand...
Click to collapse
Thank you for this! Also very helpful!

Unlocked Amazon XT1625 to retail firmware?

So, I have a 32gb Amazon-variant XT1625 on MPJ24.139-48 with an unlocked bootloader and root. I want to update to Nougat, but it's looking like setting up to take the Amazon update is going to be a fair amount of effort; I'm wondering if it's possible to just flash the retail version of Nougat since it's looking like I'm going to have to go to a fair sum of effort anyway.
I've also heard that Moto G4 Plus ROMs will work on the G4, but I don't know the specifics on that.

i dont see why not as long as you already unlocked the bootloader prior to Moto(Lenovo) disallowed unlocking of amazon varients of the g4. heres a link to the stock nougat firmware
https://androidfilehost.com/?fid=673368273298955218

I flashed -64 retus software on mine and it immediately had two nougat updates afterwards. Still waiting for one that fixes the aboot sector vulnerability too but never know when that may come

Travisholt92 said:
I flashed -64 retus software on mine and it immediately had two nougat updates afterwards. Still waiting for one that fixes the aboot sector vulnerability too but never know when that may come
Click to expand...
Click to collapse
then you was able to flash retail version in a amazon prime phone? I have one and it dont boot if i instal a retail version.

di anybody actually get this working? I had the same issue as @iurd2007 I was able to unlock the bootloader just fine. The flash appeared to have taken successfully. But it just gets caught in a boot loop when trying to reboot the system after the flash. I followed the instructions here:
https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138

okay, so i've tried various roms both official and unofficial, as well as even the stock Nougat and Oreo flashable roms found here:
https://forum.xda-developers.com/moto-g4-plus/development/rom-oreo-8-1-0-soak-test-t3873367
So far, the only ROM i've been able to get installed is omni rom 9, but it keeps crashing several apps over and over on the setup wizard. I've read somewhere that using a different version of TWRP recovery image might help. I've tried the official TWRP recovery from twrp.me, the patched arm64 version found here: https://sourceforge.net/projects/tw...3-r1-athene-arm64_rajatgupta1998.img/download , also the latest version patched for efs backup/restore here: https://forum.xda-developers.com/devdb/project/?id=29106#downloads. So far the the one that seems to work the best is the third version of TWRP. It would be nice if all these custom patches made it back into an official release, but it's probably asking a lot of a phone that is almost 4 years old at this point. and a budget friendly phone at that.

Confused Noob+H990DS - Unlock/Root+TWRP Official Custom ROM possible (W/ 2. Screen)?

hi folks!
I am pretty confused now. I am looking to get the V20 H990DS, but i am more confused now after reading here. My questions:
1. Is Bootloader unlock possible?
2. Can i install TWRP?
3. Can i root?
4. There is LOS official i know, but is the problem with 2. screen now fixed / going to be fixed?
Seems so good of a device, but i am insecure about it now after reading here. My old Mi4/Cancro is one of the best supported phones out there, so i dont expect it to be the same with V20, but i need working LOS with Root and working 2. screen (or the outlook on it working in the future) to be confident in buying it.
I hope you forgive me my nood questions,
Greetings

With sadly no replys, let me add what i know now:
1. + 2. + 3. Still no easy way in sight AFAIK. EDIT: To be clear: There IS a way, Dirty Santa, but the instructions are somewhat too complicated to be confident with trying. Have had rooted Phones with custom ROMs since over 5 years and never again a stock device, but i dont dare it. The 300€ i payed are much to much to have spend it on a bricked device. Will try to find more dirty Santa noob friendly explanations and post them here. EDIT2: For those who DO dare it, here the thread: https://forum.xda-developers.com/v20/development/dirtysanta-h990-t3624296
4. Second screen still a problem, nothing new heard for quite a long time.
Anyone with knowledge to add or correct, please help! Stock ROM is not as bad as i thought, but without Root, Android is not fully usable for me.

thank you pro for this thread
very useful for me.

Stele88 said:
With sadly no replys, let me add what i know now:
1. + 2. + 3. Still no easy way in sight AFAIK. EDIT: To be clear: There IS a way, Dirty Santa, but the instructions are somewhat too complicated to be confident with trying. Have had rooted Phones with custom ROMs since over 5 years and never again a stock device, but i dont dare it. The 300€ i payed are much to much to have spend it on a bricked device. Will try to find more dirty Santa noob friendly explanations and post them here. EDIT2: For those who DO dare it, here the thread: https://forum.xda-developers.com/v20/development/dirtysanta-h990-t3624296
4. Second screen still a problem, nothing new heard for quite a long time.
Anyone with knowledge to add or correct, please help! Stock ROM is not as bad as i thought, but without Root, Android is not fully usable for me.
Click to expand...
Click to collapse
i dont get about your complain. you said already using phone with root for 5 years so i guess you've been here on xda for a while. if you really want a phone which support custom rom go with phone which support unlock bootloader like HTC, Oneplus, or even xiaomy. its not that hard finding them on XDA. 300euro for briked devices? well, if you read v20 section carefully you knew most people here bought this devices for the camera, audio, and other things like removable battery, etc. i never found someone who bricked their devices while rooting here, even if they do we already had flasher tools like LG up which already tested fully working by some members. and whats the problem with second screen? its working for whatever it made for. are you expecting to watch movie on those 2.1 inch display? i had lg v20 h990ds rooted with magisk and had no problem so far. bought some apps like grenify and titanium backup for debloated and my phone rocking solid for abouth 2 month. if you cant wait for LOS just bought lenovo zuk2 or oneplus 3t on the same price range.

No problem doing 1+2+3 with DirtySanta exploit/procedure. It's not as complicated or dangerous as it might seem from the instructions. I thought I had soft-bricked my phone twice after rebooting normally with the old kernel instead of straight to TWRP to update the kernel first, but it was easy to re-flash the 10d factory firmware file I had and start over again without any issues both times.
Basic summary of procedure:
1. Flash factory firmware version earlier than 31 December 2016 (only needed if installed firmware version is after 1 January 2017).
2. Do DirtySanta exploit to unlock bootloader and install TWRP and root.
3. Use kdzwriter to update phone's system/modem/cust partitions to latest firmware version without overwriting unlocked bootloader/TWRP, reinstall root (SuperSU or Magisk) from TWRP.
4. Disable automatic OTA updates so that any future firmwares won't automatically install and overwrite bootloader/recovery and remove root and set ARB 1. If that ever happens then TWRP/root will probably be gone forever.

provided you follow the instructions carefully, it's safe to root with DirtySanta.

xoose said:
No problem doing 1+2+3 with DirtySanta exploit/procedure. It's not as complicated or dangerous as it might seem from the instructions. I thought I had soft-bricked my phone twice after rebooting normally with the old kernel instead of straight to TWRP to update the kernel first, but it was easy to re-flash the 10d factory firmware file I had and start over again without any issues both times.
Basic summary of procedure:
1. Flash factory firmware version earlier than 31 December 2016 (only needed if installed firmware version is after 1 January 2017).
2. Do DirtySanta exploit to unlock bootloader and install TWRP and root.
3. Use kdzwriter to update phone's system/modem/cust partitions to latest firmware version without overwriting unlocked bootloader/TWRP, reinstall root (SuperSU or Magisk) from TWRP.
4. Disable automatic OTA updates so that any future firmwares won't automatically install and overwrite bootloader/recovery and remove root and set ARB 1. If that ever happens then TWRP/root will probably be gone forever.
Click to expand...
Click to collapse
Using the steps on #3, would it be safe to say that we can update the device to oreo and still keep root?

nurse_chuck said:
Using the steps on #3, would it be safe to say that we can update the device to oreo and still keep root?
Click to expand...
Click to collapse
No, right now if you update you'll lose root as the engineering aboot isn't compatible with Oreo and you have possibly non working data, invalid sim issues etc
Sent from my LG-H910 using XDA Labs

cnjax said:
No, right now if you update you'll lose root as the engineering aboot isn't compatible with Oreo and you have possibly non working data, invalid sim issues etc
Sent from my LG-H910 using XDA Labs
Click to expand...
Click to collapse
Too bad. Your earlier post actually got me excited. Hehe. Anyway, hopefully someones starts working on rooting the oreo firmware.

The short answer? @Stele88
Yes. To all of it.
The long answer starts with the Dirty Santa root process. Believe me, I was daunted by it as well, but as long as you follow it (or the noob version of the guide you can find by searching around the same section the original guide is in) and take your time, you'll be okay. It's what I did and I'm now where I am today.
I'll address a couple things since I have the same device as you. If you want to get your device working properly on LineageOS/ResurrectionRemix (LOS with more customisation) then it's a long process.
1. Start by following the bootloader unlock process for Dirty Santa. Depending on what firmware your device gets shipped with, you may need to downgrade to (in the case of the H990DS) the v10c firmware. Once done, then you can Dirty Santa the bootloader and get it unlocked.
2. Once that's done and you're rooted with the initial TWRP from the thread installed, you'll want to look into KDZWriter. It's a program by the same emdroidle who did the Dirty Santa process for us that allows you to update your STOCK system software to newer versions and keep root. You can use it for example with the H990DS firmware KDZ files and go from rooted 10c -> rooted 10f -> rooted 10xx -> etc. until you're on the latest available 7.0 KDZ for the H990DS. This will be the longest part of your process, but it ensures that everything is up to date before going to AOSP/Lineage/Resurrection, specifically the modem partition. I recommend using the TWN region of firmwares if you're just going to convert to a custom ROM anyway, but any region will work fine (the only real difference is that, for example, the Australia region of firmwares comes with more bloat than the TWN region).
2b. You can also use KDZWriter from an updated TWRP you can get in the thread by Phoenix591, his latest TWRP versions have KDZWriter built-in so you don't have to run it off the computer, you can do it all with the kdz files in recovery.
3. Yes, you can root using the Dirty Santa method on v10c kdz firmware. I recommend Magisk for root over SuperSU.
4. There's no official LineageOS that is as up to date as the unofficial ones, and there's no official ones with second screen enabled full stop. That being said, the unoffcial LineageOS 15.1 by x86cpu has been my rock solid daily driver for about 2 months now and I've never had any issues that stop me from using it. The same can be said for ResurrectionRemix 6.2 by Blaises. To use either of these, you will need the updated TWRP from Phoenix591.
4. Second-screen enabled builds of LineageOS and ResurrectionRemix do exist, and in this case ResurrectionRemix is (as of this post) more up-to-date than the LineageOS 15.1 second screen version. If you find yourself needing additional features that aren't in the stock kernels for those ROMs (such as KCAL configuration to help with burn in, among other things), then I maintain the second-screen version of the Gamma Kernel by Omar-Avelar. People are successfully using this with second-screen ROMs and have full functionality. You can purchase the app BoredSigns from the play-store to add additional functions to the second-screen.
As I said at the start, it is a long process, but a very worthwhile one. The jump from stock to custom-ROMs is absolutely incredible. Again, in short, yes. You can get everything you want.
Just do your searching around the forums for the processes I outlined above, ask any questions you have, pre-download your kdz firmwares from HERE and any software you need, and just take your time. It's maybe a couple hours to get setup with a rooted stock system that's up-to-date, and maybe another hour or so to go from stock to Lineage/Resurrection.
P.S: If all goes well with the Dirty Santa process, but you get screen distortion after rebooting when flashing the TWRP from Dirty Santa, just pull the battery instead of rebooting.
Good luck, good searching, and remember to not be afraid to ask questions in the relevant threads.
---------- Post added at 04:50 AM ---------- Previous post was at 04:49 AM ----------
nurse_chuck said:
Too bad. Your earlier post actually got me excited. Hehe. Anyway, hopefully someones starts working on rooting the oreo firmware.
Click to expand...
Click to collapse
It's highly doubtful this will happen, but one can hope. Right now the best way to get Oreo is through a custom ROM, purely because of how security is implemented by LG in the stock Oreo ROMs.

iDefalt said:
It's highly doubtful this will happen, but one can hope. Right now the best way to get Oreo is through a custom ROM, purely because of how security is implemented by LG in the stock Oreo ROMs.
Click to expand...
Click to collapse
Actually it is possible runningnak3d has already said awhile ago he has a process to root stock oreo he's just not releasing it yet so LG can't patch it before the Oreo roll out is complete
Sent from my LG-H910 using XDA Labs

Rooted H990DS. Can it be upgraded to oreo? Development is still going on?

I've been looking out in the forums for info about H990DS development. But I find much less info than other models that got their updates earlier.
Last year I rooted with DirtySanta and updated to the lastest kdz available for my region (twn) with help of KDZ Writer by @emdroidle. Who seems unactive since april.
There was also this H990DS info bank thread that has a bunch of information about H990DS development. Like kdz merging for updates & much more stuff.
But the OP got mad because someone implied that was other developer's work and not his. He made a tantrum and deleted all the information to never be seen again.
I know how to follow instructions, but sadly, I am not a developer myself. Also I don't own many smartphones so I could just change devices if I screw this one up.
But I want to know if there is someone still working on this or if it can be done already. Maybe set a bounty or donations if needed?
Is there a way to upgrade rooted stock rom devices to Oreo without making the device unusable in process?
Would it be possible to keep root when upgrading to Oreo? Maybe flashing certain partitions or files?
Or does it has to be a modified stock rom that is root enabled?
I hope at least get a clear answer about if it can or can't be done. Thanks.