[ 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....
Related
hey
I have an orange phone which a while ago i flashed with a generic rom and rooted. because of this i was unable to install the OTA so i did a manual upgrade to this rom:
RUU_Bravo_HTC_WWE_1.21.405.2_Radio_32.36.00.28U_4.06.00.02_2_release_126984_signed.exe
This installed fine (it seems), but as i am on orange, when i rebooted the phone it was network locked. I read that flashing an older radio solved this problem so i went and flashed this radio:
update-bravo-radio-32.30.00.28U_4.05.00.11-signed.zip
This now makes my phone boot and work fine with no lock, HOWEVER, the software version still says it is on 1.15.405.4 and not the updated version!!!!
I have tried testing one of the bugs that was fixed in the new ota (i sms'd myself from skype and it still says it was sent by a facebook contact) and so that fix clearly wasnt present and the upgrade just hasnt seemd to work. Can anyone shed any light on this? could it have anything to do with what is installed on my phone during step 1 of the root? the root package i am using is called r5-desire-root-alt
Thanks for anyone who can help on this
Rooting the phone puts the 1.15.405.4 ROM back on your device, if you want 1.21 you'll have to then buy an unlock code to free up the device...
There is an update ZIP in the ROM dev forum which updates the system but leaves the radio alone so might wanna try that...
thanks for this, but the only update i have been able to find in the dev forum is the one on this page:
http://forum.xda-developers.com/showthread.php?t=695667
but there is a note at the top saying they all contain radio updates
do you have a link to one without the radio update?
Didn't look hard did you??
http://forum.xda-developers.com/showthread.php?t=694564
thank you sooo much, this has finally sorted out my problem
Hey guys, I was hoping I would'nt have to do this but i'm at a loss now.
I own the blue xperia play 4g phone and currently using it with straight talk service with their unlocked sim. Everything was fine until I decided to start trying out custom roms.
No matter what I tried, I could get them to load, work , function ect BUT I had weird issues where people could not hear me for the 1st call, but if I called them right back they could. It just seemed to be random and I could'nt put my finger on it.
So I flashed back to the stock 2.3.3 R800AT firmware, and then updated thru their Sony patch they made me do on the phone...and everything was fine again.
Well I got adventurous again, and UNLOCKED my bootloader. So NOW....after doing custom roms, I CANNOT reload my old R800at 2.3.3 firmware and get the OFFICIAL update from them. So i'm stuck with an upgradeable working 2.3.3 (this is the 2.3.3 before the update they put out, I know it does'nt go to 2.3.4. but its some kinda 2.3.3 update) with NO further updates.
So after tons of research i'm HOPING its the baseband I need ??? I dont know what else to do. Only other option is if some kind soul wants to send me over their AT&T r800AT 2.3.3 UPDATED firmware I'll just go back to stock but i'd prefer to keep using my custom roms!!!
***maybe if someone who has the blue xperia play 4g version, would post the "baseband" version they see on their phone, even that would help!!!***
Any help would be great and more than appreciated.
God bless and thanks guys,
Jason
jaygrae said:
Hey guys, I was hoping I would'nt have to do this but i'm at a loss now.
I own the blue xperia play 4g phone and currently using it with straight talk service with their unlocked sim. Everything was fine until I decided to start trying out custom roms.
No matter what I tried, I could get them to load, work , function ect BUT I had weird issues where people could not hear me for the 1st call, but if I called them right back they could. It just seemed to be random and I could'nt put my finger on it.
So I flashed back to the stock 2.3.3 R800AT firmware, and then updated thru their Sony patch they made me do on the phone...and everything was fine again.
Well I got adventurous again, and UNLOCKED my bootloader. So NOW....after doing custom roms, I CANNOT reload my old R800at 2.3.3 firmware and get the OFFICIAL update from them. So i'm stuck with an upgradeable working 2.3.3 (this is the 2.3.3 before the update they put out, I know it does'nt go to 2.3.4. but its some kinda 2.3.3 update) with NO further updates.
So after tons of research i'm HOPING its the baseband I need ??? I dont know what else to do. Only other option is if some kind soul wants to send me over their AT&T r800AT 2.3.3 UPDATED firmware I'll just go back to stock but i'd prefer to keep using my custom roms!!!
***maybe if someone who has the blue xperia play 4g version, would post the "baseband" version they see on their phone, even that would help!!!***
Any help would be great and more than appreciated.
God bless and thanks guys,
Jason
Click to expand...
Click to collapse
Oh my friend, you are in the same boat as me. xD
All you need to do is get the stock 2.3.3 AT&T firmware, But you can also use r800i firmwares and update to 2.3.4 with the latest firmware.
Theres a thread somewhere containing the firmware, if not you can find it on google.
(Which is what im doing right now with straight talk) only negative thing I see is so far H instead of H+.
Dito on the baseband, the flashtool links with FTF 2.3.3 is down my phone is softbricked though
Cetus90 said:
Dito on the baseband, the flashtool links with FTF 2.3.3 is down my phone is softbricked though
Click to expand...
Click to collapse
If alejandrissimo unlocked your phone you should have OTA updates. If you unlocked it with another method then im not sure what to tell you, gotta find the updated FTF files.
Guys good news here
I was correct in thinking it was the baseband on our phone that is causing the problem. I think its due to the fact we are 4g rather than 3g.
So how did i fix this problem??? Simple. I was able to use the doomkernel v13 (any seem to work), actually install the rom of choice, (i'm using Jokawild 2.5), and then downloaded/installed baseband file -36.
I also installed the -36 libs package that was somewhere posted on here its the new .386 version.
Everything is working now and i'm happy. Going to save the baseband/lib files so i have them forever incase something happens.
Take care, God bless and thank you for your input/time. I could'nt go another day with them stock at&t roms!!!!
jaygrae said:
Guys good news here
I was correct in thinking it was the baseband on our phone that is causing the problem. I think its due to the fact we are 4g rather than 3g.
So how did i fix this problem??? Simple. I was able to use the doomkernel v13 (any seem to work), actually install the rom of choice, (i'm using Jokawild 2.5), and then downloaded/installed baseband file -36.
I also installed the -36 libs package that was somewhere posted on here its the new .386 version.
Everything is working now and i'm happy. Going to save the baseband/lib files so i have them forever incase something happens.
Take care, God bless and thank you for your input/time. I could'nt go another day with them stock at&t roms!!!!
Click to expand...
Click to collapse
Hello hello, I need your help. I've got the generic North Am. 2.3.4 (.42) and I'm having this problem. I've got an unlocked bootloader and I want to install the baseband file. Can I do that with a generic rom? What is the process for installing a baseband file and libs package? Where can I get these files? Thanks.
SonyFanboy said:
Hello hello, I need your help. I've got the generic North Am. 2.3.4 (.42) and I'm having this problem. I've got an unlocked bootloader and I want to install the baseband file. Can I do that with a generic rom? What is the process for installing a baseband file and libs package? Where can I get these files? Thanks.
Click to expand...
Click to collapse
I think I have the same or a similar problem. I frequently encounter a similar situation where it could take 10+ seconds before the other person can hear me speak, but I can hear them the whole time. By now most of my friends and family know how to deal with it, but before they would just hang up on me. Then they could hear me if I called them. If I reboot the phone, it fixes it for a while, but then it comes back after some time and takes another reboot to resolve.
My phone is a SIM unlocked, bootloader locked Xperia Play R800a model from last year's Google I/O. It uses the same frequencies as AT&T for 3G and 2G and I'm using it on AT&T as well. I have the Generic North America 4.0.2.A.0.42 (Android 2.3.4) ROM installed, and it has Baseband 8x55A-AAABQMAZM-203028D-56.
I found a separate thread with the -36 Baseband here:
http://forum.xda-developers.com/showthread.php?t=1469473
I'm considering flashing this over my current -56 Baseband to see if it improves the situation. As I recall, I never had this sort of trouble when I first got the phone. It's really only been since I updated to Firmware .42 that I've had these problems. Is it safe to do this?
Thanks!
MechaBouncer said:
I think I have the same or a similar problem. I frequently encounter a similar situation where it could take 10+ seconds before the other person can hear me speak, but I can hear them the whole time. By now most of my friends and family know how to deal with it, but before they would just hang up on me. Then they could hear me if I called them. If I reboot the phone, it fixes it for a while, but then it comes back after some time and takes another reboot to resolve.
My phone is a SIM unlocked, bootloader locked Xperia Play R800a model from last year's Google I/O. It uses the same frequencies as AT&T for 3G and 2G and I'm using it on AT&T as well. I have the Generic North America 4.0.2.A.0.42 (Android 2.3.4) ROM installed, and it has Baseband 8x55A-AAABQMAZM-203028D-56.
I found a separate thread with the -36 Baseband here:
http://forum.xda-developers.com/showthread.php?t=1469473
I'm considering flashing this over my current -56 Baseband to see if it improves the situation. As I recall, I never had this sort of trouble when I first got the phone. It's really only been since I updated to Firmware .42 that I've had these problems. Is it safe to do this?
Thanks!
Click to expand...
Click to collapse
I wanted to add that on Friday I installed the -36 baseband with mine and I'm getting 4G+ (I hit 12MBs at mobilespeedtest.com). And my calls have stopped being cut off.
SonyFanboy said:
I wanted to add that on Friday I installed the -36 baseband with mine and I'm getting 4G+ (I hit 12MBs at mobilespeedtest.com). And my calls have stopped being cut off.
Click to expand...
Click to collapse
Awesome! That's also funny because I also installed the -36 baseband last night. So far, so good. Calls and data both work as normal. I'll need to do more testing to be sure whether it fixed my problem or not.
Now did you just install the baseband or did you also flash or push the libs to it as well? All I did was use Flashtool to flash the baseband .ftf file.
Hello all
I am really hoping someone can explain this to me please. I have recently purchased a Samsung Galaxy Note 2 (N7100) from Vodafone in the UK direct. I was under the impression from this site, and general research on the Net, it has an unlocked boot loader and my experience with it thus far seems to validate that. I want to place a custom ROM on it.
Here is what I have done thus far. The device is rooted and is working fine from that perspective. Root checker and such like all say this is fine. Additionally, it supposedly has the correct and latest version of CWR on it, 6.0.1.9. This was done using the ROM Manager from the Play store. It is the non touch version, at present. However upon booting in to CWR I have no advanced options on the main menu. I would upgrade to the touch version. However, that is not free and whilst I have no issue paying for it, in principle, I am reluctant to, in case I end up in the same position with that version. It does not state what the upgrade version is. It states on the upgrade introduction page, it is also available as a free download from the clockworkmod website. However. after much digging through their website I land up back at the ROM Manager page in the Play store, which quite rightly says it is already installed. The only manual download I can find is for, yes you guessed it, 6.0.1.9 and that when expanded is simple an SU.apk and a few such related files. How that will flash the correct version of CWR with touch enabled etc. is anyone's guess? The device is currently running JB 4.1.2 and was pushed out to my device by OTA update just before XMAS. The baseband version is N7100BUDLL1 and the build number is JZ054K.N7100XXDLL4. The kernel is shown as 3.0.3-679347 and is dated December 11 2012.
I am at a total loss here. I have flashed phones a number of times and have never come across anything so seemingly utterly baffling. Is it actually possible to get a full version of CWR for this build please and, if so how please? I am very reluctant to wipe the phone and install a custom ROM until I can verify CWM is running correctly. Surely I cannot be the first person in the UK on Vodafone to want a custom ROM and the boot loader is supposedly unlocked too?
Yours desperately trying to understand what is actually going on here please. Any help and\or enlightenment will be gratefully received.
Many thanks in advance.
Regards,
Paul Lemonidis.
Use TWRP recovery for Note2 instead of CWM.
Flash it using odin.
nm8 said:
Use TWRP recovery for Note2 instead of CWM.
Flash it using odin.
Click to expand...
Click to collapse
Many thanks for your quick reply. I was wondering about that. I'll give it a try. It seems from what you're saying to ditch CWR as it does not work properly with my device for some reason? Just mine or all UK Vodafone models is my next question. So I am also left asking did CWR's own program to install CWR downloaded the wrong version of it for my model, despite being installed directly from the Play Store? Obviously I chose the correct model in the menu. Do I take it there is no CWR version that will work properly in my device, unless it is just my device, of course? I am just trying to understand what is going on here. It is more the lack of any sensible logic to this I find frustrating, more than actually not being to Flash the phone to be honest. Or is it just a dodgy installation? Although I have tried installing it by ODIN and Rom Manager the result is always the same. Everything says its installed fine but it just doesn't work upon booting in to it??!! I will try the other way now.
Paul-Lemonidis said:
Hello all
I am really hoping someone can explain this to me please. I have recently purchased a Samsung Galaxy Note 2 (N7100) from Vodafone in the UK direct. I was under the impression from this site, and general research on the Net, it has an unlocked boot loader and my experience with it thus far seems to validate that. I want to place a custom ROM on it.
Here is what I have done thus far. The device is rooted and is working fine from that perspective. Root checker and such like all say this is fine. Additionally, it supposedly has the correct and latest version of CWR on it, 6.0.1.9. This was done using the ROM Manager from the Play store. It is the non touch version, at present. However upon booting in to CWR I have no advanced options on the main menu. I would upgrade to the touch version. However, that is not free and whilst I have no issue paying for it, in principle, I am reluctant to, in case I end up in the same position with that version. It does not state what the upgrade version is. It states on the upgrade introduction page, it is also available as a free download from the clockworkmod website. However. after much digging through their website I land up back at the ROM Manager page in the Play store, which quite rightly says it is already installed. The only manual download I can find is for, yes you guessed it, 6.0.1.9 and that when expanded is simple an SU.apk and a few such related files. How that will flash the correct version of CWR with touch enabled etc. is anyone's guess? The device is currently running JB 4.1.2 and was pushed out to my device by OTA update just before XMAS. The baseband version is N7100BUDLL1 and the build number is JZ054K.N7100XXDLL4. The kernel is shown as 3.0.3-679347 and is dated December 11 2012.
I am at a total loss here. I have flashed phones a number of times and have never come across anything so seemingly utterly baffling. Is it actually possible to get a full version of CWR for this build please and, if so how please? I am very reluctant to wipe the phone and install a custom ROM until I can verify CWM is running correctly. Surely I cannot be the first person in the UK on Vodafone to want a custom ROM and the boot loader is supposedly unlocked too?
Yours desperately trying to understand what is actually going on here please. Any help and\or enlightenment will be gratefully received.
Many thanks in advance.
Regards,
Paul Lemonidis.
Click to expand...
Click to collapse
First of all update your firmware. You are vulnerable to sds.
Secondly as for your problem.
Go to cwm page in desktop mode and download the recovery for your phone. Touch or non touch anything would work. Then rename the downloaded file to recovery.img and flash it in recovery option via mobile odin and you are done.
Sent from my GT-N7100 using xda app-developers app
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,
Hi guys,
I got my HTC 10 last week - phone is a big improvement from the m8.
I am running Telstra's latest firmware - Have s-off already...
Telstra's latest firmware is 1.53.841.6 with Leedroid ROM - have been trying to get VOLTE.
I never got VOLTE with stock because I rooted so fast and S-OFF and installed custom ROMs.
So I had to install stock system image 1.53.841.6, reinstall stock recovery and factory reset and VOLTE icon shows up instantly. Install TWRP and VOLTE remains. But if you install a custom rom and do a full wipe seem to lose VOLTE. Also have to have the telstra firmware to VOLTE to work, I tried with WWE and no go. Also had to ring up telstra as it wasn't activated. So if you are having trouble getting it - might be best to double check. Even though my provisioned flag was on. *#*#4636#*#* to check - tap phone info.
@xlrate reported not wiping data and installing VIPER was able to keep VOLTE. (Updated the customize folder in the rom with my Telstra back up, also the build prop to do this) Also TELST001 cid has to be on.
Has anyone got VOLTE working on a custom ROM on WWE Firmware?
So Aussies... Who's got their new HTC 10?
Update - 15/10/16
Thanks to @brantp for providing TWRP backups & OTAs
https://drive.google.com/drive/folders/0B6MWrHVBWC-xZlBQN1BqYUNPRW8
TWRP Backup (untouched System Image + Boot)
- 1.21.841.8 (+ Recovery)
- 1.53.841.6
- 1.80.841.1
- 1.95.841.3
Stock Recovery
- 1.53.841.6
- 1.80.841.1
- 1.95.841.3
OTA
1.21.841.8 --> 1.53.841.6
1.53.841.6 --> 1.80.841.1
1.80.841.1 --> 1.95.841.3
Firmwares- Refer to http://forum.xda-developers.com/htc-10/how-to/2016-05-27-fastboot-flashing-firmware-t3387520 for more info
https://docs.google.com/spreadsheets/d/1EdAHLDDxqf9jH65me_8bY9oXdaYusI0eedpwO6yUY2s/pubhtml
Thanks to @Sneakyghost
Roms- Leedroid, ICE and Viper now support Telstra with carrier support.
If anyone has any of the other australian carriers firmware please post and I will add them to OP.
15/08/16
https://www.androidfilehost.com/?w=files&flid=60869
Telstra RUU provided by @Sneakyghost - Will restore OTA's if anyone has broken them
12/03/18
Telstra OREO update
http://fotadl-az.htc.com/secure/OTA....48.841.31_release_519847tp9bagwfkglchg5u.zip
@Sneakyghost isn't doing the firmware updates anymore.
If you need to use the firmware.zip out of the OREO zip and need to a custom recovery either replace the recovery.img with twrp.img (rename it of course) in the firmware.zip - or flash one after installation.
I got mine about a month ago.. All I've done so far is root it.. (even after all these years, it still sounds wrong)
I normally run ARHD, but, Mike hasn't mentioned developing for the 10, so, I'm stuck atm, not really interested in running a massively modded ROM. But, last night the OTA notification popped up for 1.53.841.6.. So, I'm going to have to do something - the notification is annoying me. So, I guess I have to work out how to update it.
I hadn't even considered the VoLTE requirements.. I just assumed it would all work, even on a custom ROM. 4G did, I didn't think this would be any different.
Is VoLTE worth hanging on to? I don't really get it.. Is it like VOIP for mobiles?
Vampyric said:
I got mine about a month ago.. All I've done so far is root it.. (even after all these years, it still sounds wrong)
I normally run ARHD, but, Mike hasn't mentioned developing for the 10, so, I'm stuck atm, not really interested in running a massively modded ROM. But, last night the OTA notification popped up for 1.53.841.6.. So, I'm going to have to do something - the notification is annoying me. So, I guess I have to work out how to update it.
I hadn't even considered the VoLTE requirements.. I just assumed it would all work, even on a custom ROM. 4G did, I didn't think this would be any different.
Is VoLTE worth hanging on to? I don't really get it.. Is it like VOIP for mobiles?
Click to expand...
Click to collapse
I have had VoLTE working with Leedroid after I used the telstra 1.53 system/customize & parts of the build.prop on the 1.30 base... Haven't been able to get it working on 1.80 base.
Have had to use the telstra firmware for it work, doesn't work on WWE. So it is kinda a pain to get working.
VoLTE is better call quality and if you are on a call you can use LTE/4g to use the internet... Without VoLTE when on calls your phone 3g
EDIT - don't think OTA will work since you are rooted unless you went systemless root
I guess I don't 'appreciate' VoLTE as much as I should, because I rarely make phone calls..
Sadly, not Systemless root. So, I think I need to go back to stock, update and re-root. It's not something I've had to worry about before. So, it's kinda frustrating, and a little too complicated for me to totally understand.
I was going to de-brand it, and just run the WWE RUU.. But, maybe I'll wait for the 1.80 Telstra update and worry about it then.
I got rid of the notification
**Sent from a uranium powered typewriter**
Anyone experiencing an issue with NFC? While on stock 1.21.841.8 (and locked), worked without issue. Since updating to 1.53.841.6 (and unlocked), can't read my Opal card now ie no vibration, no sound, no anything. Haven't tested my tap & pay banking app yet (which did work without issue prior to updating).
Yes I also had and issue with NFC. Would not read opal card and was an absolute pain to try and read my Amex and Visa card.
Ended up getting another issue with it and returned the phone under warranty for NFC and the other issue.
Still waiting to get a phone back ?
Sent from my HTC One_M8 using Tapatalk
Yeah NFC doesn't work with mine now on 1.53.
I did get a vibrate and a sound when I was on earlier firmware but not now.
Just hoping that the 1.8 update fixes this stuff.......
pablo11 said:
Yeah NFC doesn't work with mine now on 1.53.
I did get a vibrate and a sound when I was on earlier firmware but not now.
Just hoping that the 1.8 update fixes this stuff.......
Click to expand...
Click to collapse
Thats if we get 1.8
I have a feeling we will miss that and get the one after that.
xlrate said:
Thats if we get 1.8
I have a feeling we will miss that and get the one after that.
Click to expand...
Click to collapse
Aparently they have stoped rolling the 1.80 update. Im on vodafone and there website has no update for the htc 10 so i agree that we wont get it
yldlj said:
Aparently they have stoped rolling the 1.80 update. Im on vodafone and there website has no update for the htc 10 so i agree that we wont get it
Click to expand...
Click to collapse
Tried reflashing the 1.53 firmware again (twice) to see if it fixes it, but it's still not working ie Can switch it on and off, but it does not respond to my opal card.
It's only taken Telstra until this month to push out 1.53, so who knows when (or if) 1.80 will happen. Now I'm trying to decide whether it's worth sending back for another handset or waiting to see if the next OTA will fix it. My biggest concern is that the replacement could be on 1.21 and I could possibly end up with the same issue all over again!
pablo11 said:
Yeah NFC doesn't work with mine now on 1.53.
I did get a vibrate and a sound when I was on earlier firmware but not now.
Just hoping that the 1.8 update fixes this stuff.......
Click to expand...
Click to collapse
I just tried to NFC on 1.53 and it isn't working very well, hardly at all. I got it to work 3 times in about 15 mins...
Previously I think when I was on 1.30 firmware it was working well before but just had to hold it near the head phone jack.
Any Telstra users want to test out the Telstra firmwares
http://forum.xda-developers.com/htc-10/how-to/2016-05-27-fastboot-flashing-firmware-t3387520
Make sure you back-up the rom & back up internal storage refer to later posts in that thread.
https://crowdsupport.telstra.com.au/t5/Device-Updates/Software-Updates-01-07-2016/td-p/585953 Telstra 1.80.841.8 firmware is coming 25-Jul
Leedroid is the best rom for Telstra users. Running it myself and working perfectly, now supports Telstra with carrier support & VoLTE working - thanks @LeeDroid
*Only works on Telstra firmware.
Install Ice yesterday (only got my phone Friday ), really like it over the stock rom.
Some people complained about the LED but I like it. My only complaint about my M8 was how bright the LED was specially in the dark when you're trying to get to sleep.
Another problem I'm having is file transfers freeze when using a USB 2 port on Windows 10.
I like my new M10 but not sure if I like it over the M8 as of yet. I preferred the speaker arrangement on the M8 and having the home, back buttons etc on the screen rather then down the bottom.
I have to admit I'm not a fan of the "Samsung" look at all which is why I bought HTC in the past to begin with. I didn't want to be a part of the flock.
Hey guys,
I'm looking to get the 10 but imported, could someone (especially looking for someone with Optus) check their box to see what specific model it is (e.g. 10h or 10u)?
Thanks guys
The Telstra model is a HTC 10h
ICE (InsertCoin) v2.0.6 supports Telstra also now too. Thanks @baadnewz
morgy59 said:
The Telstra model is a HTC 10h
Click to expand...
Click to collapse
Awesome, thanks morgy59
Found out that Telstra's policy for DOA/ELF replacements are within 30 days of purchase. Since a return will result in a repair, I'll wait to see if the OTA will fix the NFC issue first before sending back.
Has anyone experienced an NFC issue on Telstra stock, only to have it disappear after switching to a cusom ROM?
brantp said:
Found out that Telstra's policy for DOA/ELF replacements are within 30 days of purchase. Since a return will result in a repair, I'll wait to see if the OTA will fix the NFC issue first before sending back.
Has anyone experienced an NFC issue on Telstra stock, only to have it disappear after switching to a cusom ROM?
Click to expand...
Click to collapse
I found it worked perfectly fine on wwe 1.30 firmware using Leedroid. Now I'm on 1.53, hardly works at all
Sent from my SM-P605 using Tapatalk
It's doesn't read card on 1.53 on Optus build 710