Related
[ Due to me no longer having a Xoom, this ROM repack is no longer supported / available. Please contact me directly if you have any queries or if you would like the source code to the Baseband Updater. ]
"Fed up with waiting for the UK Xoom 3G update to 3.1"
I got mine first thing this morning following an empty update last night but thanks anyway!
Paul, why do we need to update the baseband?
Paul, thanks for the image, however I'm having some problems and I am hoping you can help.
I have a verizon MZ601 xoom, and did a clockworkmod install of your zip, in an attempt to "switch the baseband" from CDMA to UMTS.
(I believe there are no hardware diferences since MDM6600 is multi-baseband)
Untill now, I was unable to find a different baseband image.
I have however cross flashed (fastboot) EU GSM versions (without baseband updates) and they worked fine. Hence I am not worried taking the risk.
Anyway, the thing is, I had US wifi only version with android 3.2
I installed your zip, with clockworkmod, reboot - stuck at boot screen (with honeycombs)
I did have ADB shell, but dont know what to check... (log?)
I tried cat on /dev/log/... but they are binary or something(?)
Ofcourse I can restore back to US working versions, but I really wanted to try your baseband update!
So I rebooted to recovery, did a wipe/cache clean return factory defaults, and managed to boot.
The problem now is that I dont have root anymore and I can not run your baseband upgrade!
Should I go with typical root steps for UK, 3.1 version ?
Should I drop the whole thing ?
Maybe If I had a baseband update "alone" so I can apply in on a UK fastboot images flash, and hopefully convert my CDMA to UMTS ?
Any feedback is welcome.
Thanks!
UPDATE:
ok I rooted the device, and runned the "baseband update"
It gives me a window asking "Reboot to recovery?" I press "yes" and It takes me to clockworkmod recovery ....
where is the upgrade ? how is it initiated ?
Shouldn't this updated replace the clockworkmod recovery partition ?
Am I missing something ?
nikil511 said:
UPDATE:
ok I rooted the device, and runned the "baseband update"
It gives me a window asking "Reboot to recovery?" I press "yes" and It takes me to clockworkmod recovery ....
where is the upgrade ? how is it initiated ?
Shouldn't this updated replace the clockworkmod recovery partition ?
Am I missing something ?
Click to expand...
Click to collapse
Correct, it should reflash the stock patched recovery - let me look into it.
P
Thanks
I'm really exited ! ...
I'm a few clicks away from either switching the baseband - or bricking my device!
Great
Ok, this is what I did….
I pulled the Baseband update utility apk from the rom, installed it into Verizon 3.1, updated the busybox, and started the Baseband update utility……the xoom booted into the patched version of the stock recovery and the updating started but failed at the middle
assert failed: moto.update_cdma_bp(“/tmp/bp_rdl.bin”, “/tmp/bp.img”)
E:Error in /cache/update.zip
(Status 7)
Installation aborted.
Welcome Paul O'Brien! Anybody from team Tiamat is at your service. If there's anything we can do for you, don't hesitate to ask.
XooModaco
i have just spent the last 4 weeks getting my 3.1 to a standard i call enjoyable and now ' PaulO ' releases a rom!
gota be worth a backup and flash to see how good this is i rekon, here goes ...
.
.
.
i have a3g us verizon xoom. but i'm outside us. may i install this rom ? is there any GSM baseband available? may i use sim card slot for gsm network? does my xoom's hardware support it?
thanks a lot
Hey Paul,
glad to see you providing ROMs for the xoom as well. I started flashing your ROMs on my Hero a long time ago.
Anyway, I have an UMTS/3G issue with your ROM. Unlocking SIM works, entering a new APN for Vodafone Germany works as well. The connection bar on the bottom left shows me a solid (grey) H, but it never turns blue. I can't get any traffic through it. It works on Tiamat 2.0 (euro) and stock.
It's not SIM-card related, because I switched my XOOM SIM card with the one in my DHD, didn'T change anything. Working with my DHD, not working with my XOOM.
It's not APN related, although I thought about it in the first place. I dumped the working APN list from stock ROM (and from CM7 DHD as well) and restored it on your ROM. Rebooted. Nada, still no traffic coming through.
Any ideas? I think it could be baseband related, but how to dump the baseband from unrooted stock?
BTW: do you need some more APNs for your ROM? I made a dump with an app called APN backup.
Guys any news on the baseband update (and potentially switch) app ?
azel said:
Hey Paul,
glad to see you providing ROMs for the xoom as well. I started flashing your ROMs on my Hero a long time ago.
Anyway, I have an UMTS/3G issue with your ROM. Unlocking SIM works, entering a new APN for Vodafone Germany works as well. The connection bar on the bottom left shows me a solid (grey) H, but it never turns blue. I can't get any traffic through it. It works on Tiamat 2.0 (euro) and stock.
It's not SIM-card related, because I switched my XOOM SIM card with the one in my DHD, didn'T change anything. Working with my DHD, not working with my XOOM.
It's not APN related, although I thought about it in the first place. I dumped the working APN list from stock ROM (and from CM7 DHD as well) and restored it on your ROM. Rebooted. Nada, still no traffic coming through.
Any ideas? I think it could be baseband related, but how to dump the baseband from unrooted stock?
BTW: do you need some more APNs for your ROM? I made a dump with an app called APN backup.
Click to expand...
Click to collapse
Some issue here... with difference that my provider Vodafone Netherlands is, good signal, but not connecting, none over 2G and 3G.. what's wrong?
Wrong baseband? wrong Prop.build?
Somebody?
Motorola Xoom @ 1.6GHz
Rom: Team Timat Xoom Rom 2.1 Hammerhead
HoneyComb 3.2
Tiamat kernel 2.1
Build: HTJ85B-Deodexed 1.0
Samsung SGS I
DarkyROM JVQ 10.2 (2.3.4)
Baseband: ZSJPG
has no one cared to continue this project? i am willing to have a go at this, but would like to have a link to those files....
anyone know if there's an updated modem img?
i'm having an issue that could either be the sim card or software related. if there's an updated/newer modem, i'll flash that in addition to getting a new sim. just trying to get this issue cleared up.
i see a package on the boards that contains a modem and some other items but its for color OS. i'm running team gummy. looking for way to just get the modem and update mine.
thanks, all.
no one?
Define what you mean by updated.
Just download the latest 1.2 color os update. It contains the radio binaries.
by updated i mean a newer version than what initially shipped on the phone. i found entropy's package, btw, and have flashed that.
I would post in the developer thread where I am having the problem but I don't have enough posts yet.
I'm attempting to install this ROM:
http://forum.xda-developers.com/gal...-unofficial-cyanogenmod-11-t2885259?nocache=1
onto my SGH-T989 t-mobile. I'm getting an error saying that my radio is not new enough and the ROM won't install. I then went to the Radio thread here:
http://forum.xda-developers.com/showthread.php?t=1895400
to try and download the latest radio listed there, being the UVMC6 for the t-mobile, which would not download. So I tried the Telus TLMC4, which I don't know if that is a problem with the t-mobile phone, and the ROM still said the radio is not new enough.
I'm am guessing that I should install a jelly bean ROM, like Lightspeed to get a newer radio. But is that correct? Do the new ROMs have radios or does that need to be done separately?
Turns out it was the clockworkmod version. Had to update it and that seems to be taking care of everything.
Though my wifi isn't working with any of the ROMs. I'm guessing I need to try the t-mobile RADIO instead. If I can find a copy of it.
I am almost in the same boat as you are.
I tried two 4.4.4 ROMS (CM11 and another one), but I received the same message about the radio. So I updated the radio to TLMC4 and the ROM install got passed the radio error. But then another error occurs, wich I do not understand.
Both 4.4.4 ROMS I tried got stock at the same spot on the install. So I ended up intalling 4.1.2 Ligthspeed. Works fine and is stable for now.
If you can give any input on how you successfully installed a 4.4.4 ROM, any help is appreciated!
I am with Koodo mobile by the way.
Thanks!
sTaLa said:
I am almost in the same boat as you are.
I tried two 4.4.4 ROMS (CM11 and another one), but I received the same message about the radio. So I updated the radio to TLMC4 and the ROM install got passed the radio error. But then another error occurs, wich I do not understand.
Both 4.4.4 ROMS I tried got stock at the same spot on the install. So I ended up intalling 4.1.2 Ligthspeed. Works fine and is stable for now.
If you can give any input on how you successfully installed a 4.4.4 ROM, any help is appreciated!
I am with Koodo mobile by the way.
Thanks!
Click to expand...
Click to collapse
Which error are you getting? I'm same with Koodo, radio TLMC4 and CM11 from Sultanxda works fine.
http://forum.xda-developers.com/gal...rom-kernel-unofficial-cyanogenmod-11-t2885259
Q&A for [Baseband] ALL T999, T999L, T999V, T999N Modems! w/ MAP and Data Tweaks!
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
modem T999VVLUFNH2
Hi everybody,
I try to find the updated modem for my S3 (videotron SGH-T999v)
I have the modem T999VVLUFNF1 (ROM LS 3.1 stable KK 4.4.4, KT747 kernel)
When I unzip the official ROM of samsung (older like 4.1.2 and the last samsung update from september 2014) , I only find the file NON-HLOS.bin
According to sammobile the last videotron modem is T999VVLUFNH2, but I cannot find the file. This is the first time I try to update the modem because I have a poor reception in my house.
Thank you for your help
I haven't decided if I will post those or not. Too great a risk with the 4.4.2 modems. If you want to try the latest I can only recommend fully updating as a safe way to do so.
If you really want to be the one to test if it's safe, I'll get it uploaded for you, but understand there is a chance it could hard brick the phone beyond repair.
Reason for all of this is because we know if you flash a 4.4.2 modem on 4.3 it'll permanently brick it. I have no idea if flashing an older or newer 4.4.2 modem on 4.4.2 firmware (like you want to do) will result in the same. Normally, I would guess it wouldn't be the case, but it seems a lot has changed in these new builds that no one understands, and there have already been too many bricks for me to be comfortable trying something new like this without exercising great caution.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Thank you for your reply and your advise.
As I don't have enought money to take the risk, I will keep my actual modem.
Thank again
Don't blame you a bit! But don't forget, you can still fully update and that may help. (From what I've seen, flashing older modems on 4.4.2 doesn't brick, so i think if you updated, it should be ok to flash the NF1 modem if the newer one doesn't help. It might not work, but I don't think it would cause any harm. Just food for thought, but again, I can't guarantee anything with these latest modems...)
If it's a bad signal issue that you did not have before, call your carrier and ask if there are any tower/network/account issues they are aware of.
Your carrier probably doesn't do this, but Tmobile will sometimes give customers a signal booster for home use only. You can buy them online too, but I'm not sure how my h they are these days. (Just make sure it boosts the frequencies used by your carrier if you look into this.)
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Just noticed today that my phone is on T999VVLUFNF1 but that there is a newer 4.4.2 release for the T999V phone that is T99VVLUFNH2. Would it be good to update via Odin to this? Is it just a newer modem?
I have a T mobile T999 that is currently flashed with CyanogenMod 11-20141008-SNAPSHOT-M11-d2lte which is kitkat 4.4.4. The baseband version is T999UVDMD5. I have a Lebara sim card in it now, and I'm in France. I'm not getting any signal and I suspect it is because the baseband version mismatch. Is there anything I can do to make this setup work or do I have to downgrade to a different version of CM? Is there and updated modem I can flash on this device or any way to make it work?
abetterlie said:
I have a T mobile T999 that is currently flashed with CyanogenMod 11-20141008-SNAPSHOT-M11-d2lte which is kitkat 4.4.4. The baseband version is T999UVDMD5. I have a Lebara sim card in it now, and I'm in France. I'm not getting any signal and I suspect it is because the baseband version mismatch. Is there anything I can do to make this setup work or do I have to downgrade to a different version of CM? Is there and updated modem I can flash on this device or any way to make it work?
Click to expand...
Click to collapse
Latest baseband is NC2, flash it, and if the device still does not pick up service flash back to MD5 firmware and see if it will pick it up. If not then it might incompatible with your provider..
Thanks!!!! Also Those using T999 switched to ATT
Just wanted to say thank you!!!
Also just wanted to say for those who have a T999 that switched to AT&T this works (I wasn't sure if this would work since it didn't say anything about AT&T working with it. To be perfectly honest I didn't read everything but again THANKS!!!!!!
Hi Guys,
I got the OTA update ( T999UVUENC2 ) about a month back and since then, my Wifi has stopped working. It stays greyed out when I try to turn it on. Just won't turn on.
The logcat says that the "WiFi driver is unstable".
What I have tried so far (with no success):
1) Flash the same build again (T999UVUENC2).
2) Flash the root666_T999UVUENC2 build. (Currently, I am on this)
3) Flash Cyanogenmod 11.
4) Factory reset.
5) Pull the battery out when the phone is on and put it back again.
6) Modify/delete the wpa_supplicant.conf file.
Can someone please give any directions on how the "Wifi driver can be fixed"? I understand from going through the forums that downgrading from 4.3 to 4.2 can cause a brick. However, can I downgrade to the previous T-Mobile 4.3 build (T999UVUEMJC ) without causing a brick? Do you guys think that can help fix the Wifi?
Any help would be greatly appreciated.
Could you point me to what one exactly i need for T999LUVUBNF4
SGH-T999L Will Not Mount Ext Sd/No root or load file from .zip to root
I always get stuck at the boot screen where I am supposed to Update from Zip, but my phone NEVER lets me Mount the External SD card, I have a 64GB card, failed, 16 GB card, failed, what am I missing. All the good tutorials, ESPECIALLY yours, get me to that point but being unable to load that .zip file from sd just murders me. The Phone is on 4.3 and I believe I loaded your stock 4.3 firmware after failing to get this part done and then trying every single rom possible (didn't realize this had murdered me) until I managed to get back to this stock rom. Why does it not want to load from ext sd? Is it the file system? I've never had any issues with any of these sd cards, and they aren't generic cards, one is a samsung other a sandisk,
Hello. I have d855 android 5.0 . Wanted to install cm 13. and here are my steps:
1. Rooted my 5.0 , flashed TWRP, and flashed CM13 and gapps. There was a problems with dialer after flash, so i downgraded phone into 4.4.2 V10a (using .tot and .dll files) . .
2. Again tried to flash CM13, but process was aborted and phone bricked.
3. Flashed stock 4.4.2 again. Again no luck to write CM .
4. Flashed stock 5.0 v21a using lg flashtool. Again - if i want to flash CM - phone always bricked (error executing updater binary) . And now, even with stock 5.0 my phone data connection do not work (only wifi works)
Please help .... how to reflash my phone and get CM and back data connection??
Just tried flash 4.4.2 again. Flashed successfully, but still any data connection Tried update into 5.0 using phone software updater, but after few updaters it fails (invalid software package).
Today found, that data connection works perfectly if i set GSM/WCDMA . If LTE is selected, there are no data connection at all. Also, can't flash custom rom, phone always stuck at LG logo. Anybody can help so solve my problems?
imdarex said:
Hello. I have d855 android 5.0 . Wanted to install cm 13. and here are my steps:
1. Rooted my 5.0 , flashed TWRP, and flashed CM13 and gapps. There was a problems with dialer after flash, so i downgraded phone into 4.4.2 V10a (using .tot and .dll files) . .
Click to expand...
Click to collapse
I want to cite only the first point you described, because it's "abominable"!
Sorry for the harsh tones, but... the dialer issues obviously involved the Cyanogen rom, especially because you're using the first nightlies, often unstable.
Why you accused the official firmware (therefore no more existing since you replaced them) and decided to downgrade?
Then you've to known that important downgrades like Lollilop > KitKat may irreversibly corrupt system partitions like "efs", which make your device losing of IMEI code and mobile data!
Now the only thing you can do is updating your device by settings menu until you reach latest firmware (21A).
Since you've to manually confirm each updates (10A, 10E, 20A etc.), the process will take almost 1-2 hour.
When the update process in definitely completed, you can try to root device, install TWRP and flash latest CM13 nightly.
In case of other issues, try the quite stable CM 12.1, or the stock-based FulmicsRom.
If you continue to have troubles, do a CSE flash of 21A firmware and send your device to warranty.
Simone98RC said:
I want to cite only the first point you described, because it's "abominable"!
Sorry for the harsh tones, but... the dialer issues obviously involved the Cyanogen rom, especially because you're using the first nightlies, often unstable.
Why you accused the official firmware (therefore no more existing since you replaced them) and decided to downgrade?
Then you've to known that important downgrades like Lollilop > KitKat may irreversibly corrupt system partitions like "efs", which make your device losing of IMEI code and mobile data!
Now the only thing you can do is updating your device by settings menu until you reach latest firmware (21A).
Since you've to manually confirm each updates (10A, 10E, 20A etc.), the process will take almost 1-2 hour.
When the update process in definitely completed, you can try to root device, install TWRP and flash latest CM13 nightly.
In case of other issues, try the quite stable CM 12.1, or the stock-based FulmicsRom.
If you continue to have troubles, do a CSE flash of 21A firmware and send your device to warranty.
Click to expand...
Click to collapse
Last time I connected my phone to LG mobile support, and it automaticallly updated my phone into newest official 21A firmware. IMEI - OK, data connection - still do not work when LTE is selected. So what i need to do now ? Try to root, install TWRP and flash CM 12.1 or FulmicsRom ?
imdarex said:
Last time I connected my phone to LG mobile support, and it automaticallly updated my phone into newest official 21A firmware. IMEI - OK, data connection - still do not work when LTE is selected. So what i need to do now ? Try to root, install TWRP and flash CM 12.1 or FulmicsRom ?
Click to expand...
Click to collapse
So what's your problem when LTE is enabled?
Mobile data won't work or simply fallback to HDSPA?
Simone98RC said:
So what's your problem when LTE is enabled?
Mobile data won't work or simply fallback to HDSPA?
Click to expand...
Click to collapse
When LTE is enabled, then there are no data connection at all.
imdarex said:
When LTE is enabled, then there are no data connection at all.
Click to expand...
Click to collapse
Surely downgrading the entire firmware to the first release of KitKat broke the radio part of your device.
Probably if you downgraded to latest KitKat firmware (10h maybe, instead of 10a), LTE should works properly.
Have you encountered that connectivity issue even before flashing CM 13 (on official firmware)?
Simone98RC said:
Surely downgrading the entire firmware to the first release of KitKat broke the radio part of your device.
Probably if you downgraded to latest KitKat firmware (10h maybe, instead of 10a), LTE should works properly.
Have you encountered that connectivity issue even before flashing CM 13 (on official firmware)?
Click to expand...
Click to collapse
No, after flashing everything was fine. There is a way to reflash radio part without downgrading again ? Because when i spoted that data connection do not working, i downgraded firstly to 10a (no data connection), then i get 10h update - still no data connection. And after 10h update, my phone got another update, but showed that can't update because package is wrong of something. After that i flashed 21A what i have in my phone now.
imdarex said:
No, after flashing everything was fine. There is a way to reflash radio part without downgrading again ? Because when i spoted that data connection do not working, i downgraded firstly to 10a (no data connection), then i get 10h update - still no data connection. And after 10h update, my phone got another update, but showed that can't update because package is wrong of something. After that i flashed 21A what i have in my phone now.
Click to expand...
Click to collapse
Probably the mobile data issue was related to CM 13.
But when you downgraded to 10A, the radio part was really damaged.
As I said if you want to downgrade, always preger the "less old" firmware you need.
Like you, I downgraded in past to KitKat, but I never looked for 10A! I directly flashed 10H.
Sorry, but at this point I don't know what you have to do.
When you flashed 21A firmware, have you done a CSE flash instead of a normal one?
If not, do it.
If yes, you have to appeal to warranty without any problem, since your device has official firmware.
Simone98RC said:
Probably the mobile data issue was related to CM 13.
But when you downgraded to 10A, the radio part was really damaged.
As I said if you want to downgrade, always preger the "less old" firmware you need.
Like you, I downgraded in past to KitKat, but I never looked for 10A! I directly flashed 10H.
Sorry, but at this point I don't know what you have to do.
When you flashed 21A firmware, have you done a CSE flash instead of a normal one?
If not, do it.
If yes, you have to appeal to warranty without any problem, since your device has official firmware.
Click to expand...
Click to collapse
Yes, i did CSE flash. Ok, thank you. I think there are no more options than warranty.