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....
Hey guys. I just got a galaxy s3 from virgin mobile SPH-L710 last week and I managed to install cyanogenmod 11 m10 on it. But to go to cm11 m11 asI've recently learned needs the latest bootloader and baseband.
I know there's two threads in the development section on how to get the latest stock nd8 update.
One had a link to download and open in Odin however the link doesn't seem to be good anymore.
The second thread is for the Odin one click full restore but when I run it it fails on aboot.nbm. I've tried using different USB cables too but it doesn't seem to do any good. Any ideads on how else to upgrade?
I can assure you this is false. I have a Virgin Mobile SPH-L710 on baseband MK5 and I am running a nightly build that is newer than M11 and have no issues.
You should be fine with a dirty flash over M10. Just wipe the cache before flashing.
OK that's intriguing. How did you get MK5 baseband? I just got my s3 last week and its on NF4 which I have no idea where that is in relation to any of the others i've seen around.
I've used the cm updator in settings to try one of the m11 nightlys earlier last week but I had no service so I restored a recovery of m10. Would performing a dirty flash of a nightly build be any different?
Erunur said:
OK that's intriguing. How did you get MK5 baseband? I just got my s3 last week and its on NF4 which I have no idea where that is in relation to any of the others i've seen around.
I've used the cm updator in settings to try one of the m11 nightlys earlier last week but I had no service so I restored a recovery of m10. Would performing a dirty flash of a nightly build be any different?
Click to expand...
Click to collapse
My phone came with MK5 on it, when the phones were shipping with 4.3 installed.
To be honest with you, I would disregard the modem/baseband concerns altogether if I were you. These phones do come with KNOX on them and flashing bootloaders and modems is seriously a huge risk. Flashing a bootloader older than the one you are currently on will trip the killswitch and you will have an irreparable hard brick.
The only time I could possibly think considerations with the bootloader would need to be made is if you were looking to flash a rooted stock TouchWIZ ROM that needed newer bootloaders/modems. But, I really can't speak to that, as I am trying to avoid TouchWIZ and am only familiar with AOSP ROMs.
You may need to flash an APN fix in addition to the ROM and GAPPs. I also use @decimalman's custom kernel, the DKP kernel and have no issues. Basically, when I am clean flashing nightlies the order goes like this:
In PhilZ Recovery found here: https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
ROM
GAPPs
Kernel
APN fix
Re-Root system for SuperSU
Reboot
I sent you the link for the APN fix, available in another active VM S3 forum, in your inbox. Download and flash the zip and that should fix any service-related issues you're having.
OK I did a clean flash of the latest nightly, flashed the apn fix then booted. Still no service. No apn are on the device nor is it able to save any I manually put in. And settings shows the baseband version as unknown as well as anything else that has to do with cell service.
Erunur said:
OK I did a clean flash of the latest nightly, flashed the apn fix then booted. Still no service. No apn are on the device nor is it able to save any I manually put in. And settings shows the baseband version as unknown as well as anything else that has to do with cell service.
Click to expand...
Click to collapse
And, you tried flashing all of those with the lateat version of PhilZ recovery?
Yes. I tried it with the latest version of philz and flashed all the zips you had listed in order but still the same old issues. However I noticed that WiFi still works. I can also go back to M10 and have no service issues. The other thing im noticing is that CyanogenMod thinks this is a SPH-L710 but apperently its really a SPH-L710T. The difference being that my phone has a tri-band radio for something to do with Sprints Spark.
Erunur said:
Yes. I tried it with the latest version of philz and flashed all the zips you had listed in order but still the same old issues. However I noticed that WiFi still works. I can also go back to M10 and have no service issues. The other thing im noticing is that CyanogenMod thinks this is a SPH-L710 but apperently its really a SPH-L710T. The difference being that my phone has a tri-band radio for something to do with Sprints Spark.
Click to expand...
Click to collapse
When you're on M11, have you checked in system root --> /etc folder to see if the apns-conf.xml is there? You might tru copying that over from the M10 build.
In the meantime, I'll look into the modem a bit more. The CM forum users all seemed to agree on that as a fix.
I was happily using 4.4.2 stock on my rooted SGH-i747M, however rooting it tripped the warranty bit, then I had the phone unlocked and changed carriers from Rogers to Bell and because of either of those my device is blacklisted from getting OTA updates.
I decided to try CM and was advised on the CM IRC channel to update the modem firmware first. I updated (or perhaps downgraded?) to I747MUMUEND3 per this thread (http://forum.xda-developers.com/showthread.php?t=1831898) and rebooted but found that I no longer had sound or WIFI and the SIM card wasn't detected. I tried other versions from that same thread with no luck.
I went ahead and flashed CM 12.1 nightly for D2ATT which worked well, however still no sound or SIM. WIFI works but slowly. I also tried 11.2 for D2LTE but got the same result, and flashing 10.1 for D2ATT gave me an assert error. In 12.1 I experimented with other modem firmware versions (I747MVLUEMK5, I747MUMUEND3, I747MVLUEND2) but it made no difference.
I'm not quite sure where to go from here. According to a CM12.1 debug log my boot loader is I747MVLUFNF2. Do I need to match the modem firmware version with this, and if so, where can I get this version? Would flashing stock from sammobile do it, would I lose root while doing so, and how can I get root back? I forget how I rooted it originally but soft bricked it but fixed it with chainfire.
Anything else I can try at this point? I might just be happy back on stock with cellular connectivity.
The latest modem for the i747m is FOB1. The END2 modem is about a year behind the FOB1.
The assert error occurred because d2lte or d2can ROMs are to be flashed to the i747m.
Fixed
I flashed the stock ROM that matched up with my current bootloader version. Inside the stock ROM everything worked as normal. I then installed TWRP and flashed 12.1 and everything worked in there as well.
I'm getting error status 7 when trying to install gapps on my Rogers sgh-i747m. Here is the file I'm using gapps-lp-20141212-signed.
I'm trying to get CM 12.1 running smoothly on this device if thats even possible. So far all I've been able to do is get 12.1 running no wifi, receive messages but can't send them. If there a version of CM 12.1 specifically made for the Canadian version of this phone? Right now I'm running the sprint version, it wouldn't let me install att version, saying my phone was d2spr.
Any help would be greatly appreciated.
What bootloader and modem are on the phone? Are you using the latest release of twrp?
Your phone is identified as an i747m in download mode?
audit13 said:
What bootloader and modem are on the phone? Are you using the latest release of twrp?
Your phone is identified as an i747m in download mode?
Click to expand...
Click to collapse
Gapps installs fine using TWRP but I've still got no WIFI using Canadian version of Galasy s3. I've tried installing a few att, verizon and tmobile versions, all give me network connection but no wifi. Wifi works fine using stock rom.
Which bootloader and modem are on the phone?
The wifi is working now. Not sure why but it seems to take a bit for the wifi to kick in after the software has been loaded. I'd say it took about 30 minutes. I experience the same issue if I let the battery die. It always comes on though so I'm happy with the way CM 12.1 is running on my S3.
What bootloader and modem are on the phone? Wifi should turn on immediately with all ROMs IMHO.
hey all, i'v searched a bit but i could not find any ROM for S4 mini (serranolte) no LTE, no dual sim, eurpe version.. i tryed to flash lineageOS serranoltexx but it's not working (error 7, serranoltexx is not for serranolte). Also I am wondering why there is serranolte, because i have no LTE/4G option in system i recently flashed.. phone was wiped completely due to company policities, so maybe I flashed non LTE version of stock rom with ODIN? Is that possible?
## CLOSE PLEASE##
I don't notice that TWRP is not working with lineageOS. clockworkmod works.
lapeno022 said:
hey all, i'v searched a bit but i could not find any ROM for S4 mini (serranolte) no LTE, no dual sim, eurpe version.. i tryed to flash lineageOS serranoltexx but it's not working (error 7, serranoltexx is not for serranolte). Also I am wondering why there is serranolte, because i have no LTE/4G option in system i recently flashed.. phone was wiped completely due to company policities, so maybe I flashed non LTE version of stock rom with ODIN? Is that possible?
## CLOSE PLEASE##
I don't notice that TWRP is not working with lineageOS. clockworkmod works.
Click to expand...
Click to collapse
I think you may have flashed the wrong ROM (or your company did), error 7 normally means it has failed when checking you have a compatible ROM for your phone model.
You say "ROM for S4 mini (serranolte) no LTE" but as the name serranoLTE implies it IS for LTE version, LTE =i9195. If your phone only has 3g then you need the serrano3gxx ROM not the LTE, 3g variant is the I9190 (there are other s also). So something is wrong, not sure if it is you or your company that is wrong. You need to check model number shown under battery and flash the correct ROM, if it's the wrong ROM you may get lots of errors, or heat, short battery life etc
TWRP does work and is the preferred recovery as it is actively supported while CWM is no longer supported, maybe that's why it may have allowed you to flash wrong ROM or maybe TWRP thought the phone was the other model as your company had already flashed wrong ROM so gave you the error when it checked compatibility even though you tried to flash he correct ROM.
If your phone is the 3g version then even though you flashed the LTE ROM you will not have LTE as your phone does not have the LTE hardware. Someone did this before, I think they said it does not even show the option in settings, but I could be wrong.
NOTE: flashing the wrong ROM can brick your phone! (though as they are so similar it's unlikely but possible, you are probably the first to flash the wrong version of LinageOS, if that is indeed what you/your co. have done!. So unknown risk.)