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....
I have an At&t version of the Xperia Play (R800at). I have the phone rooted but the bootloader is still locked. I hate the bloated ROM that At&t has and wanted to flash a new one. I really like the Cola rom but it does not work on At&t. Is there a ROM I can flash on the stock At&t kernal that does not have all the bloat? I really just use the phone for calls, texting and games (mostly emulators). Can I go to another stock ROM? I would like 2.3.3 so I can run all of my converted PS1 games, I really don't want to reconvert them for 2.3.4. I do not know what info from my phone I would need to figure out what ROM to download and use. Any information would be greatly appriciated.
I have the same thing except my bootloader is unlocked. I've tried many of the roms on here myself but the baseband from AT&T doesn't give me the "can hear the other person but they cant hear me half the time" problem from the stock rom and I can get 4G on it whereas the other roms do not. Is there any roms that use the baseband from AT&T and get rid of the bloat or is there one that can just use the baseband from the stock rom? I used to have a Galaxy I so not being able to flash different basebands all the time is new to me.
--edit---
After poking around and ignoring some things different stuff said, I was able to get cyanogenmod 7.2 (freexperia) on my phone and I then installed the -36 baseband and libs after and everything appears to be working good so far. Going to test a bit with phone calls yet, but as long as I can get online and my phone calls arent messed up this is exactly what I wanted because I love cyanogenmod, I just know it kept saying I needed to have a specific set up but that never worked for me with the baseband, I just went for it and I think the problem I always had was not having the lib files to upload after flashing cyan
devi59 said:
I have the same thing except my bootloader is unlocked. I've tried many of the roms on here myself but the baseband from AT&T doesn't give me the "can hear the other person but they cant hear me half the time" problem from the stock rom and I can get 4G on it whereas the other roms do not. Is there any roms that use the baseband from AT&T and get rid of the bloat or is there one that can just use the baseband from the stock rom? I used to have a Galaxy I so not being able to flash different basebands all the time is new to me.
--edit---
After poking around and ignoring some things different stuff said, I was able to get cyanogenmod 7.2 (freexperia) on my phone and I then installed the -36 baseband and libs after and everything appears to be working good so far. Going to test a bit with phone calls yet, but as long as I can get online and my phone calls arent messed up this is exactly what I wanted because I love cyanogenmod, I just know it kept saying I needed to have a specific set up but that never worked for me with the baseband, I just went for it and I think the problem I always had was not having the lib files to upload after flashing cyan
Click to expand...
Click to collapse
Sorry, don't mean to hijack the topic, but could you describe the issue where you can hear the other person but they can't hear you a little more? I seem to 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. 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.
The phone itself is a SIM unlocked, bootloader locked 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, but it has Baseband 8x55A-AAABQMAZM-203028D-56 and not -36. Is -36 the best to use with AT&T?
same phone
I have the exact same phone and I had the exact same problem. TrueAncestor v. 1.4 worked wonders. It was easy to do, it was nicely themed, and the bloatware is all gone! I really recommend.
Here is a list of ftf files: http://forum.xda-developers.com/showthread.php?t=1589399
Try flashing a Generic, I dont know how the R800at response to generic R800i, but i have a R800a that has no issues when flashing it with R800i, also i think you could clean the bloatweare with Flashtool, might want to try it.
Last night I installed the -36 baseband from this topic:
http://forum.xda-developers.com/showthread.php?t=1469473
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.
I should also note that all I did was use Flashtool to flash the baseband .ftf file over top of my already installed North American Generic 4.0.2.A.0.42 that I got from this topic:
http://forum.xda-developers.com/showthread.php?t=1326459
There's another topic on this same thing and it sounds like using the -36 baseband with the .42 firmware is a good way to go for the Xperia Play 4G (R800at). You can find that one here:
http://forum.xda-developers.com/showthread.php?p=26972055#post26972055
I live in Croatia where we don't have LTE. So I bought Nexus via my career (Vodafone group) VIP and everything was great until yesterday.
When I entered Nexus Toolkit, I found out that I have Verzon LTE build number of my Nexus. It was IMM76K, and my device was toro (?) insted of maguro (gsm version that I was supposed to have as I understood?).
Ok, that's not big deal, I don't really care if I have toro or maguro, but when I flashed CM or any other ROM for Toro, I got unknown baseband problem. And I can't flash maguro ROMs, only toro ones.
I tried to flash gsm radio via CWM (XXLF1), but baseband is still unknown. I can't make calls, sms or any other career action.
Then I flashed JB following THIS thread, and I made it. I have stock JB that works, but again I can't flash any other custom ROM on my Nexus. I can, but then I can't make calls or sms. Everything other is working normal.
Now I'm on stock JB, waiting for someone to help me solve this problem...
P.S. IMEI was also unknown if it means anything (*#06#)
P.P.S. Sorry for my bad english, I'm Croat...
There is a few yakju builds with the build number IMM76K, not just Verizon Nexus.
And you probably f*cked your imei, restore your phone back to stock and get a new device.
And read up on rooting the manual way, gives you less problems. Not saying toolkit sucks, toolkits are a great way of doing things, but one click apps also comes with great risks should you f*ck your device up.
And if only you took your battery out and look at the label.....
qube310 said:
I live in Croatia where we don't have LTE. So I bought Nexus via my career (Vodafone group) VIP and everything was great until yesterday.
When I entered Nexus Toolkit, I found out that I have Verzon LTE build number of my Nexus. It was IMM76K, and my device was toro (?) insted of maguro (gsm version that I was supposed to have as I understood?).
Ok, that's not big deal, I don't really care if I have toro or maguro, but when I flashed CM or any other ROM for Toro, I got unknown baseband problem. And I can't flash maguro ROMs, only toro ones.
I tried to flash gsm radio via CWM (XXLF1), but baseband is still unknown. I can't make calls, sms or any other career action.
Then I flashed JB following THIS thread, and I made it. I have stock JB that works, but again I can't flash any other custom ROM on my Nexus. I can, but then I can't make calls or sms. Everything other is working normal.
Now I'm on stock JB, waiting for someone to help me solve this problem...
P.S. IMEI was also unknown if it means anything (*#06#)
P.P.S. Sorry for my bad english, I'm Croat...
Click to expand...
Click to collapse
You have a MAGURO device, NOT toro. Toro means Verizon, and Verizon ONLY. You need to go back and flash a maguro radio.
P.S., as was mentioned before, the build number has NOTHING to do with whether your device is toro or maguro. There are maguro devices running IMM76K, and toro devices running IMM76K (although they are different builds: mysid IMM76K vs. yakju** IMM76K).
qube310 said:
I live in Croatia where we don't have LTE. So I bought Nexus via my career (Vodafone group) VIP and everything was great until yesterday.
When I entered Nexus Toolkit, I found out that I have Verzon LTE build number of my Nexus. It was IMM76K, and my device was toro (?) insted of maguro (gsm version that I was supposed to have as I understood?).
Ok, that's not big deal, I don't really care if I have toro or maguro, but when I flashed CM or any other ROM for Toro, I got unknown baseband problem. And I can't flash maguro ROMs, only toro ones.
I tried to flash gsm radio via CWM (XXLF1), but baseband is still unknown. I can't make calls, sms or any other career action.
Then I flashed JB following THIS thread, and I made it. I have stock JB that works, but again I can't flash any other custom ROM on my Nexus. I can, but then I can't make calls or sms. Everything other is working normal.
Now I'm on stock JB, waiting for someone to help me solve this problem...
P.S. IMEI was also unknown if it means anything (*#06#)
P.P.S. Sorry for my bad english, I'm Croat...
Click to expand...
Click to collapse
If you flashed it with a Verizon option, it won't work. You have the GSM version. Verizon is an LTE carrier in USA. Vodafone is a GSM carrier.
Thank you all for replies and help.
Ok, now I understand that I have maguro device, but why I can't flash maguro ROMs (cwm allows me to flash only toro roms)? Is it because of cwm? When I try to flash maguro rom, cwm says that error status 7? Something like 'what is maguro?'. If it's important what error it is, I could write it down?
I don't know if I'm doing something wrong?
Sent from my Galaxy Nexus using xda app-developers app
Chances are, you flashed a toro cwm since you said you used a toolkit and selected the toro option.
Go back to stock using this guide and do everything manually.
Ok, I'll try. Thank you.
Btw, I'm on stock JB right now but I'll revert to ICS and remove all to stock..
Sent from my Galaxy Nexus using xda app-developers app
I solve the problem.
Toolkit flashed toro cwm so it wouldn't let me flash maguro ROM. Now I flashed maguro cwm and it's all fine
Thank you all for tips and help!
Sent from my Galaxy Nexus using xda app-developers app
Hello,
So I tried flashing a ROM for the first time (Android HD 8.0) and after getting it on my phone, I can't get service on my phone. The baseband, network, mobile network type, phone number, IMEI, and IMEI SV are all unknown (The phone is supposed to be Sprint).
When I tried flashing the ROM with the firmware update.zip that is on the Android HD Revolution page, CWM comes up with the error:
assert failed: getprop("ro.product.device") == "maguro" || getprop("ro.build.product") == "maguro"
E: Error in /sdcard/0/update.zip
(Status 7)
Installation aborted
After this, I tried restoring the radio using the FC12 Radio Images (I reinstalled Android HD and then flashed using this after). It appeared to install correctly, but it still didn't fix the problem.
So what should I do now?
silentdeath113 said:
Hello,
So I tried flashing a ROM for the first time (Android HD 8.0) and after getting it on my phone, I can't get service on my phone. The baseband, network, mobile network type, phone number, IMEI, and IMEI SV are all unknown (The phone is supposed to be Sprint).
When I tried flashing the ROM with the firmware update.zip that is on the Android HD Revolution page, CWM comes up with the error:
assert failed: getprop("ro.product.device") == "maguro" || getprop("ro.build.product") == "maguro"
E: Error in /sdcard/0/update.zip
(Status 7)
Installation aborted
After this, I tried restoring the radio using the FC12 Radio Images (I reinstalled Android HD and then flashed using this after). It appeared to install correctly, but it still didn't fix the problem.
So what should I do now?
Click to expand...
Click to collapse
Sprint 4G? Are you sure the ROM is for your device?
Sprint LTE = toroplus
Verizon = toro
GSM International = Maguro
Swype'ed on my CM10 Galaxy Nexus
Herman76 said:
Sprint 4G? Are you sure the ROM is for your device?
Sprint LTE = toroplus
Verizon = toro
GSM International = Maguro
Click to expand...
Click to collapse
I'm pretty sure. I mean, the rom is listed in the Samsung Galaxy Nexus Development forum, so unless there is a hidden fine print label I'm missing, I don't see why it shouldn't be compatible.
I restored my phone to the stock firmware using odin and managed to get back service, but when I tried to download a second ROM that was specifically for the Sprint version of the galaxy nexus(AOKP), I get two problems. What happens is that the rom gets stuck in boot-up, and the only way to remedy this is to do a factory reset from CWM or any other recovery, but in doing so, I get the same radio problems as before. So now, its more of "Why don't ROMS read/detect/use my radio/baseband correctly?" rather than restoring it.
silentdeath113 said:
I'm pretty sure. I mean, the rom is listed in the Samsung Galaxy Nexus Development forum, so unless there is a hidden fine print label I'm missing, I don't see why it shouldn't be compatible.
I restored my phone to the stock firmware using odin and managed to get back service, but when I tried to download a second ROM that was specifically for the Sprint version of the galaxy nexus(AOKP), I get two problems. What happens is that the rom gets stuck in boot-up, and the only way to remedy this is to do a factory reset from CWM or any other recovery, but in doing so, I get the same radio problems as before. So now, its more of "Why don't ROMS read/detect/use my radio/baseband correctly?" rather than restoring it.
Click to expand...
Click to collapse
That's for the gsm your in the WRONG forum. The one for sprint (toroplus) says SPRINT GALAXY NEXUS ANDROID DEVELOPMENT... Your flashing a rom for a gsm Galaxy Nexus. It will never work
ROMs are not compatible from carriers to carrier only Kernels are. All roms are specific to their device carriers.
Odin back to stock make sure it's all fixed and working and go to the right forum.
Sent from my Galaxy Nexus using Xparent Blue Tapatalk 2
Download a new ROM for sprint (toroplus), factory reset and format system, flash it and you'll be all fixed.
Flash the latest radio(FH05).
Sent from my Galaxy Nexus using xda premium
silentdeath113 said:
I'm pretty sure. I mean, the rom is listed in the Samsung Galaxy Nexus Development forum, so unless there is a hidden fine print label I'm missing, I don't see why it shouldn't be compatible.
I restored my phone to the stock firmware using odin and managed to get back service, but when I tried to download a second ROM that was specifically for the Sprint version of the galaxy nexus(AOKP), I get two problems. What happens is that the rom gets stuck in boot-up, and the only way to remedy this is to do a factory reset from CWM or any other recovery, but in doing so, I get the same radio problems as before. So now, its more of "Why don't ROMS read/detect/use my radio/baseband correctly?" rather than restoring it.
Click to expand...
Click to collapse
You have no business flashing your device. Pretty sure...? You don't even know what you're flashing...? Wow.
*The Ninj-ESS*
If you're meid is unknown you've erased your serial from phone. You're jacked. You need to do a repair.
*The Ninj-ESS*
JediNinjafication said:
If you're meid is unknown you've erased your serial from phone. You're jacked. You need to do a repair.
*The Ninj-ESS*
Click to expand...
Click to collapse
Not necessarily. If mismatching files get flashed to the device it may report unknown or generic as long as the files remain mismatched. If the MEID is visible in stock ROM then at least it's not permanently borked.
Is it possible the OP has been installing custom recoveries for the wrong type of GNex? That could explain why tinkering in recovery causes problems.
I really don't know. I know I'm sitting this one out. Having enough troubles setting up my environment without someone who doesn't take time to pay attention to what doing. Not trying to be rude but someone linked me here. You people really need to start reading and paying attention.
I really don't know much about android when in comparison with others but i do know enough to read and find out what I'm flashing onto my device.
*The Ninj-ESS*
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.)