Related
I picked up this tablet not knowing there is zero community backing. The radio is locked to Rogers and the OS on it is 3.01, v905r-10c baseband. Are there any guides to install newest software? 3.1? The t-Mobile update is only available in US. Only way possible I think is with .kdz file but I've yet to come across one. Help? Input?
Well, there is a bit of development still going on at the rootzwiki site
http://rootzwiki.com/forum/125-lg-g-slate-development/
I also have a rogers v905r but I flashed the t-mobile ota update about a year ago and it ended up screwing up my 3g radio. Since then I believe that they've made a cm10 rom that is flashable without overwriting the radio partition.
Also, if you'd be able/willing to make a copy of your stock v905r baseband it might be the break all of us other v905r users with broken 3g have been waiting for!
When I received my S3, it was on a T-Mobile branded stock firmware 4.1.1. I wanted to try CyanogenMod, so I installed it, but didn't like it.
Here's where my problem begins. Upon wiping my phone back to stock to get rid of CyanogenMod, I find that it's now AT&T branded, despite the physical phone being a T-Mobile T999.
I tried rooting it and using CSC changers, but those tell me that the PreconfigUI is SingleCSC, and thus apparently unchangeable.
What I want to do is somehow get my phone back to T-Mobile branded stock.
P.S. I do not have a MicroSIM yet.
GraphicsApathy said:
When I received my S3, it was on a T-Mobile branded stock firmware 4.1.1. I wanted to try CyanogenMod, so I installed it, but didn't like it.
Here's where my problem begins. Upon wiping my phone back to stock to get rid of CyanogenMod, I find that it's now AT&T branded, despite the physical phone being a T-Mobile T999.
I tried rooting it and using CSC changers, but those tell me that the PreconfigUI is SingleCSC, and thus apparently unchangeable.
What I want to do is somehow get my phone back to T-Mobile branded stock.
P.S. I do not have a MicroSIM yet.
Click to expand...
Click to collapse
Can you go to your phone's settings => about device and check what the firmware settings are? Let's see what you have under firmware version, baseband version & build number. If possible, you may post a screen shot. Did you say you returned to stock by wiping your phone? Hardly seems likely and you would have probably needed to flash some firmware. Would you recall what you flashed?
Thanks for stepping up. My phone's info is:
Android Version is 4.1.1
Baseband is I747UCDLK3
Build is JRO03L.I747UCDLK3
I did not flash any firmware, as I had no reason to.
GraphicsApathy said:
Thanks for stepping up. My phone's info is:
Android Version is 4.1.1
Baseband is I747UCDLK3
Build is JRO03L.I747UCDLK3
I did not flash any firmware, as I had no reason to.
Click to expand...
Click to collapse
It's definitely on AT&T firmware. Apologies if I sound like I'm doubting you but are you certain it had T-Mobile firmware when you acquired it? I'd guess it was probably already an AT&T phone. If you bought it in the secondary market, there could have been some previous repairs involving parts swaps. Your safest bet may be to leave it as is and unlock for you use on T-Mobile. Trying to force on T-Mobile firmware now could result in a brick. As it is on 4.1.1, you can easily free unlock it by following the well tested method you'll find elsewhere in this forum.
No apologies needed. I forgot to state that the phone was purchased with the T-Mobile boot animation and bloatware already present, and that the model number printed below the battery is T999. I've got no clue if there was a parts swap or not. Is the method to unlock that's posted elsewhere that you're referring to the one that begins with you dialing *#197328640#? If so, i've tried it but never got the unlock message to show.
GraphicsApathy said:
No apologies needed. I forgot to state that the phone was purchased with the T-Mobile boot animation and bloatware already present, and that the model number printed below the battery is T999. I've got no clue if there was a parts swap or not. Is the method to unlock that's posted elsewhere that you're referring to the one that begins with you dialing *#197328640#? If so, i've tried it but never got the unlock message to show.
Click to expand...
Click to collapse
There could have been a previous JTag operation involving forced firmware installation on the MB. I've seen previous hybrid firmware involving one or other partition belonging to a different model - e.g. the modem, bootloader or something else but not the complete system.
Yes, that's the unlock method I was referring to. You won't get any confirmation that the process worked at the end. However, if you did it correctly, you would know it worked when you insert a non-compatible SIM card and it works. You should also be able to install T-Mobile apps especially the Wi-Fi calling app which is a really nice feature of T-Mobile.
I'm getting it microSIM'ed tomorrow. I'll see how that goes.
UPDATE: Successfully obtained and installed T-Mobile microSIM. Still wish to replace AT&T boot animation and bloatware with T-Mobile's, though.
GraphicsApathy said:
I'm getting it microSIM'ed tomorrow. I'll see how that goes.
Click to expand...
Click to collapse
OK. I'd be interested in knowing the outcome but I'll be surprised if it isn't unlocked already. Did some further research and there have been some reports of people successfully 'flashing' AT&T firmware on T-Mobile phones, and vice versa. Not sure why this should happen and conventional logic suggests the result should be a hard brick which is indeed the most common outcome. I'll also suggest you boot into download mode and see the information under bootloader. If the device has a T-Mobile bootloader, it may be possible to remove the OS via custom recovery and re-flash T-Mobile firmware.
Download mode currently gives Product Name as SGH-I747. Wiping AT&T OS via custom recovery and then installing the proper one sounds like a good lead. I eagerly await your instruction
GraphicsApathy said:
Download mode currently gives Product Name as SGH-I747. Wiping AT&T OS via custom recovery and then installing the proper one sounds like a good lead. I eagerly await your instruction
Click to expand...
Click to collapse
If download mode info shows secure bootloader enabled, the phone is, to all intents and purposes, now an AT&T phone. Attempting to flash T-Mobile firmware may likely result in a brick which would require a JTag fix. I was hoping download mode would show it still had a T-Mobile bootloader which could have allowed for safe firmware installation but this does not appear to be the case. Likely the motherboard was previously replaced or it suffered a brick and AT&T firmware was JTagged on. Either way, it would be safer to leave it as is.
Bummer. I'll leave it as is then. Thank you for all the help.
I flashed the t-mobile flashall on my AT&T Z2 and attempted to return to AT&T stock. Now I have no wifi or cellular and fastboot shows "Baseband: <not found> and attempting to punch in the imei code in the dialer causes the app to crash. I can flash the tmo modem and get wifi back, but no cellular, rendering the phone useless. I've attempted to use the moto smart assistant app to run a rescue but that just breaks things again and makes wifi and cellular inoperable.
Is there any way to fix this?
ohht said:
I flashed the t-mobile flashall on my AT&T Z2 and attempted to return to AT&T stock. Now I have no wifi or cellular and fastboot shows "Baseband: <not found> and attempting to punch in the imei code in the dialer causes the app to crash. I can flash the tmo modem and get wifi back, but no cellular, rendering the phone useless. I've attempted to use the moto smart assistant app to run a rescue but that just breaks things again and makes wifi and cellular inoperable.
Is there any way to fix this?
Click to expand...
Click to collapse
I'm surprised it let you flash the tmo image. I guess as long as it's signed for an xt1789 device it doesn't care?
pitchdarkice said:
I'm surprised it let you flash the tmo image. I guess as long as it's signed for an xt1789 device it doesn't care?
Click to expand...
Click to collapse
It didn't exactly flash the whole image, just the bootloader and the modem. It booted into the AT&T rom with a T-Mobile splash screen.
My best guess is that because tmo is on a newer version of the modem package, downgrading to the older one on the att rom is causing my issue. I'm really frustrated because I've turned my brand new phone into a glorified ipod touch until I find a solution. Not to mention I discovered that att hasn't enabled wifi calling on the stock rom yet which renders the phone pretty-much useless for me anyway.
ohht said:
It didn't exactly flash the whole image, just the bootloader and the modem. It booted into the AT&T rom with a T-Mobile splash screen.
My best guess is that because tmo is on a newer version of the modem package, downgrading to the older one on the att rom is causing my issue. I'm really frustrated because I've turned my brand new phone into a glorified ipod touch until I find a solution. Not to mention I discovered that att hasn't enabled wifi calling on the stock rom yet which renders the phone pretty-much useless for me anyway.
Click to expand...
Click to collapse
I have an at&t z2 force that has the exact issue. Earlier this year I made a mistake and flashed the tmobile modem, tried going back to at&t and ended up with a tiny tablet like you. Every new security patch from at&t I try and flash, and every time the same result as yours - no baseband. Flash back to a tmobile modem for wifi and wait... Hopefully they get Pie and it will become a functioning phone once again.
I liked the phone so I ended up getting a sprint version (lesson learned about locked bootloaders), and the at&t mini tablet sits attached to my jbl soundboost for some sleeping white noise and alarm clock.
Not what you wanted to hear, but you're not alone. Maybe with the $99 sale recently on the at&t version increasing ownership someone will find a way past the locked bootloader and give us hope, but I'm not holding my breath.
cubalis said:
I have an at&t z2 force that has the exact issue. Earlier this year I made a mistake and flashed the tmobile modem, tried going back to at&t and ended up with a tiny tablet like you. Every new security patch from at&t I try and flash, and every time the same result as yours - no baseband. Flash back to a tmobile modem for wifi and wait... Hopefully they get Pie and it will become a functioning phone once again.
I liked the phone so I ended up getting a sprint version (lesson learned about locked bootloaders), and the at&t mini tablet sits attached to my jbl soundboost for some sleeping white noise and alarm clock.
Not what you wanted to hear, but you're not alone. Maybe with the $99 sale recently on the at&t version increasing ownership someone will find a way past the locked bootloader and give us hope, but I'm not holding my breath.
Click to expand...
Click to collapse
Just a heads up, but I turned my phone on today to see it trying to install updates. The update wouldn't complete, so I used the Moto Smart Assistant app to install the update and when I booted back into android I now have cellular service again and a new baseband version. Looks like att finally updated their baseband to a newer version than the tmobile one!
In summary, WOOHOO I didn't waste $100!
Ok, two years later, but I had the same problem today on my Moto Z2 Force XT1789-4 (AT&T).
After a a lot of reading, and a lot of failing, I realized that to correct this I have to flash NON-HLOS.bin and fsg.mbn from a NEWER ROM.
In the end I used the files from XT1789-05 Pie Rom, and my Baseband returned.
douglascs77 said:
Ok, two years later, but I had the same problem today on my Moto Z2 Force XT1789-4 (AT&T).
After a a lot of reading, and a lot of failing, I realized that to correct this I have to flash NON-HLOS.bin and fsg.mbn from a NEWER ROM.
In the end I used the files from XT1789-05 Pie Rom, and my Baseband returned.
Click to expand...
Click to collapse
I wouldn't recommend this to anyone. Once you flash a pie modem you can't go back, more so flashing a variant not intended for your phone is often the cause of these problems. ATT is a locked bootloader, so you're limited to what you can flash, and when things go wrong it is extremely difficult to solve those problems because of the locked bootloader, and most times it remains so. Not only that, you're not very specific as to what you're actually using, what your system is, and what carrier you're using. -05 covers a few different countries and modems and US modems tend to be very specific. Not trying to be an ass, but you need to offer a lot of info and specifics about your setup otherwise people might blindly flash some pie modem and that'll be the end of it.
douglascs77 said:
Ok, two years later, but I had the same problem today on my Moto Z2 Force XT1789-4 (AT&T).
After a a lot of reading, and a lot of failing, I realized that to correct this I have to flash NON-HLOS.bin and fsg.mbn from a NEWER ROM.
In the end I used the files from XT1789-05 Pie Rom, and my Baseband returned.
Click to expand...
Click to collapse
Can u update to android 10?
henrywhtin said:
Can u update to android 10?
Click to expand...
Click to collapse
Unfortunately, Motorola do not gave me an unlock code for my phone.
I'm pissed about this. I'm stuck to Android Oreo. My Moto G5 has Pixel Experience Android 10 rom, it's an amazing upgrade.
Hi guys. I got a G8 from a friend whose friend's dad is a radio tower engineer for AT&T that got this phone early. It's a prerelease phone (says "not for sale") on the back, and it comes with software that is seemingly far behind what shipped with the public version of the device. It's Android 9 with the December 2018 security patch, SW version G820UM04b. This version is pretty buggy and doesn't have some features like air motion. It seems like the initial software release for the public phone was G820UM10g.
Whenever I try updating the device, it just says the software is already up to date. I've done more factory resets and tried more tricks than I can even recount. Got a fresh new SIM card. Called AT&T and got them to manually push the update to my IMEI (which is correctly registered), waited a day for the update. Tried LG Bridge but it's incompatible with AT&T devices. Looked for kdz files online for the AT&T version that I can flash using LGUP, but there's no AT&T files available (pls tell me if anyone knows of any out there).
I'm at my wit's end guys. Anyone have any ideas as to how I can get this phone updated? I'm realizing that I really took the ability to just unlock and flash my old OnePlus for granted
Where do you live ?
Mobile AT&T only support to update OTA if you live in US !
minhthien0711 said:
Where do you live ?
Mobile AT&T only support to update OTA if you live in US !
Click to expand...
Click to collapse
Sorry, forgot to clarify that. I live in the USA and I use AT&T.
On the face of it it's not looking good. There aren't any KDZs for ATT as standard, and you can't update OTA - one thing to check here is the S/N field, pre-production LG phones are usually missing this, which is usually why OTAs don't work.
However, pre-production devices can, sometimes, be cross-flashed. You could try using LGUP to flash a more recent US unlocked build. It is likely to give you the IMPL lock / mismatch / crossflashing not allowed error, but it's worth a shot.
If that doesn't work, your best bet will be to ask your friend's dad to take it in to work (when he can...) for whoever looks after devices for his team to flash it to production as a favour.
This may seem like a weird question, but is there is way to convert back to the T-Mobile firmware? Mostly I would like to avoid having to install the modem manually with every update. If this is no longer the case and there is a permanent modem solution then that's all I would need. I found a lemonade tar.gz for the T-Mobile firmware supposedly, however, I don't know how to make that a installable ROM. The link is a github link here, OnePlus 9 Pro Firmware. I've never swapped off of the carrier firmware and had to manually reinstall the modem with every update before. The most annoying part of that for me would be keeping the bootloader unlocked. That's only a minor issue for me as I play Pokemon Go and unlocked bootloader/root can cause issues with that. I don't generally tweak my phones much anymore. I prefer the non carrier ROM to have more current updates. To recap, is it possible to either go back to T-Mobile ROM or is a permanent modem fix for the conversion?
MSM is the easiest way. Just use the MSM tool for LE2127 and you'll be on your way.
I have a flash-all script that you put in a fastboot flashable stock rom zip, and it'll make it so the radio (modem) persists through OTA's. Just gotta dig around for it and see what I did with it.
Thank you both. If I could get back to T-Mobile firmware then swap back to global again that would be great. I think I may be up the proverbial creek though. In my search I came across what seems like an older thread first and I used the India MSM to flip to global. This unfortunately means the T-Mobile MSM is unable to flash to my phone as it sees it as an India phone. I found the other global MSM, and I am able to see the Target directory and choose O2, however, the MSM fails to download. Param Preload error, device not match image.
I've made peace with not being able to get back to T-Mobile firmware, I may have to research the persistent modem more for a fix that will work with India. Is there a modem install for OOS12 that doesn't brick the phone? I use the ones I have from the T-Mobile files, and they work fine for OOS11, but they immediately brick 12 after install.
Bumping this post to ask again about the modem for Android 12. Also, my Bluetooth audio cuts in and out, it's very crackly. This only started after jumping from the T-Mobile ROM.
Edit: Also the voicemail doesn't show in the Phone app. Voicemail service is listed as "Your Carrier" and I can't do anything with it. There are no options that I can toggle at all.
I was looking at the repo of builds for the 9 Pro. I see there is an Android S for all regions in there. Could that possibly change the region of the firmware to, more or less, not associated anywhere and allow a restore to the T-Mobile firmware?
I'm not entirely sure how, but I did manage to get off of the India firmware and onto the EU firmware. At least from there I should be able to get the persistent modem. Working on that process now.
All right, everything has been running fine on the EU firmware, the only thing I'm still having an issue with is Bluetooth. Not connectivity at all, just on phone calls and in one vehicle for audio. It's incredibly choppy. It didn't used to be an issue, it only started after I left the T-Mobile firmware. Is there something I need to flash for the Bluetooth or a setting I'm missing?