Develop Bugs

NO LONGER AVAILABLE: non US 3G Xoom 3.1 repack (Telstra) inc Baseband Updater

[ 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....

flashing back 2.3.4 build to a Sprint Photon 4G with latest xxx254_13 OTA update

Hi, this is a question that has not been asked so far (searched and read many links) --
I have MB855 Photon 4G from Sprint, and want to leave them, but use it as GSM on a different network (T-Mobile or ATT).
So far I know:
1) I need to have the bootloader unlocked to flash a new radio (http://forum.xda-developers.com/showthread.php?t=1664212)
2) have to actually do it...
But, the problem is that I unknowingly updated to xxxx 245_13 (latest as of today) OTA (over the air) update from Sprint sometime in July or August.. and now I can no longer unlock the bootloader, or can I?
What if I just used RSD update to flash the stock SBF to xxxx_198_7 (sunfire Sprint rom)?
Would that bring me back to "2.3.4" build? Has someone done it?
(I see no relevant answers that are more recent than July/August)
Please, help me understand why that would not work?
My phone is rooted and has the bootstrap recovery, can I flash something through it instead?

[Q] Will PagePlus Flash be ruined by flashing ROM?

Hello all. Been a computer geek for 25+ years, and an android geek for a little over a year. I have done numerous flashes on Continuum, Fascinate, Nexus, and various other phones. I cannot seem to get a "clear and defined" answer on this question:
I have a TOTAL nandroid backup via ClockworkMod Recovery v6.0.1.2
I have a TOTAL system & app backup via Titanium Backup Pro 6.0.1
I am rooted with Chainfire's SuperSU v1.34
Phone
Sprint Samsung Galaxy S3 SPH-L710
Android Version:
4.1.2
Baseband Version:
L710VPBMD4
Kernel Version:
3.0.31-1130792
Build Number:
JZO54K.L710VPBMD4
Hardware Version:
L710.14
I did ALL the OTA updates from 4.0.1 to 4.1.2 prior to PagePlus flash. Had phone flashed to PagePlus with 100% working 3G, text, talk, and MMS. IF I flash a custom ROM (ie: CyanogenMod Nightly build, MOAR, etc...) will it render my PagePlus inoperable or require reflashing to PagePlus with every custom ROM flash? At $50.00 per flash that can get expensive. IF it DOES screw up the PagePlus flashing, can I just do either of the previously mentioned backups, and have my PagePlus flash settings magically re-appear? Or will it require a visit to my local PagePlus retailer for another flashing? My previous phones didnt require "flashing to PagePlus" since they were verizon phones and can be updated by simply dialing *228 or *22890.

Short answer: No
You don't lose your phone number when flashing roms, right?
APN settings may need to be modified manually though for MMS, etc

PagePlus flashing woes.....
TODAY 11:20 AM
CNexus
Short answer: No
You don't lose your phone number when flashing roms, right?
APN settings may need to be modified manually though for MMS, etc
-----------------------------------------------------------------------------------------------------------
I knew you didnt lose your number or carrier settings when you flash a custom rom to a verizon based 3g phone (not sure about verizon 4g LTE phones tho), since PagePlus uses verizon towers, and to update roaming capabilities, and PRL is easily accomplished by the *228 or *22890. BUT when using a Sprint based 4g phone, if you flash a new rom, or go backwards to an older oem rom, I was under the impression that EVERYTHING goes back to the default Sprint settings, and that the PagePlus side of things is forever gone. But noone can give me a definitive YES or NO on this, and at $50 a pop for mistakes can get expensive quickly
I have flashed the following Verizon phones with with "multiple" OEM & Custom ROMS with NO problems: Continuum SCH-I400, Fascinate SCH-I500, Droid X, HTC Incredible, HTC Vogue Touch (installed android instead of win 6.x), Verizon Nexus SCH-I515 . None of these required anything other than OTA programming to work 100% with Page Plus (except the Nexus which I could NEVER get on PagePlus no matter how hard we tried).

You may want to check out THIS THREAD.

Please read forum rules before posting
Questions and help issues go in Q&A and Help section
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator

Page Plus Mystery Solved?
First off..... sorry for posting in the "general" area with a question. I'll try to be more careful in the future......
Second.... Answer to my own question, and for anyone else in the "not knowing".
I bit the bullet yesterday and flashed 3 custom roms. Cyanogenmod, Miui, and MiBox, and then flashed back to my nandroid oem 4.1.2 JB I had 100% working Talk, Text, and MMS on ALL 3 roms, as well as the oem.
So, the answer to my question, YES, you can flash custom roms without losing PagePlus flash. I did NOT do an Odin flash, but I did do a factory reset, and still had all my settings intact.
Thanks to all the helpful people who gave opinions/pointers. Your work with the devices is GREATLY appreciated!!!! Keep up the good work.
Al

alaneddy said:
First off..... sorry for posting in the "general" area with a question. I'll try to be more careful in the future......
Second.... Answer to my own question, and for anyone else in the "not knowing".
I bit the bullet yesterday and flashed 3 custom roms. Cyanogenmod, Miui, and MiBox, and then flashed back to my nandroid oem 4.1.2 JB I had 100% working Talk, Text, and MMS on ALL 3 roms, as well as the oem.
So, the answer to my question, YES, you can flash custom roms without losing PagePlus flash. I did NOT do an Odin flash, but I did do a factory reset, and still had all my settings intact.
Thanks to all the helpful people who gave opinions/pointers. Your work with the devices is GREATLY appreciated!!!! Keep up the good work.
Al
Click to expand...
Click to collapse
I'm hoping you can help me with my similar question. I have a used Verizon Galaxy Nexus (SCH-I515) that I successfully programmed to use Page Plus. (I have no idea what I actually did, but I was able to follow the instructions I found online with no problems.) It's currently running JB 4.2.2 and Paranoid Android 3.6, and I'd like to get JB 4.3 on it.
I don't really understand flashing and all that (for instance, what ODIN is or what the ramifications of different operations are), and I can't seem to get an answer to my question.
Ideally, I'd like to get JB 4.3 on it (either stock/rooted or using one of the stable ROMs out there (CM 10?)), AND I'm hoping I don't have to reconfigure all the settings I've spent the last two weeks setting up.
Any insight? Thanks!

Getting back to stock/MobileIron

I've rooted and flashed custom roms many times during the years on many devices, but this is the first time I've needed to go back to stock and it didn't really go as planned.
The reason is I planned to use my old retired One X as work phone and use my work phone for other purposes and our company is using MobileIron which requires an unrooted phone and also adds several other limitations to the phone (requires a five digit pin, doesn't allow stuff on the lock screen etc.).
I was previously running a Resurrection Remix (Android 5.1) on it with the new layout, but I installed an old Philz recovery, reformatted the sd card, flashed this rom http://forum.xda-developers.com/showthread.php?t=1546970, that was supposed to be completely stock, not rooted, no busybox etc. and then also installed the stock recovery after the rom. After that I was able to take an official OTA update to fix the heartbleed bug (4.18.401.4) and I thought everything was fine.
I then registered and installed MobileIron and also that looked fine and I got a nice green checkbox that all was ok, but when I did the final step to try to connect to the corporate Exchange ActiveSync that failed and I got a mail telling me something like "Critical. Your mobile device has been detected as compromized (jailbreaked or rooted). All access to corporate information has been blocked/removed from the device.".
Does anybody know what MobileIron is looking for and if there is any way to be more stock than I currently am? I don't suppose it will check for an unlocked bootloader? I do have an old RUU lying around "RUU_ENDEAVOR_U_JB_45_S_HTC_Europe_3.14.401.31_R_Radio_5.1204.162.29_release_302015_signed". But it feels wrong to use a RUU to downgrade the phone (if that's even possible on a S-ON phone?), and even if I did would I be able to upgrade to the current version using OTA's in that case? If it matters my CID is HTC__Y13.

Lost LTE/Data Radios After Rooting 1.91.617.1

After the recent OTA update, I followed the steps here to restore root: http://forum.xda-developers.com/htc-10/how-to/guide-root-optionally-s-off-radio-t3373025 and mistakenly installed the latest version of SuperSU when I should have installed an encrypted version (or set the encrypt flags).
After losing the radios for mobile data, I tried several methods to restore stock (twrp restore and stock recovery on current and previous versions, 2PS6IMG on SD root dir, RUU updater) but have not been able to recover the radios.
The device is still S-On, I'm thinking going S-Off and flashing an earlier version might get the radios back. Are there any other methods I can try?

I'm not sure if the radios really were affected after rooting. After my last HUU flash, I manually entered the APN for AT&T's HSPA+ I was able to get mobile data with the 4G icon. I don't remember if this phone has anything that indicates LTE, my vague memory says it's only displayed 4G ever since I've used it.
What I don't believe however, is having to manually enter the alternate APN for AT&T. I think the preset NXTGENPHONE APNs are supposed to work. Any other ATT users out there able to use the preset APN for ATT?

Did you happen to decrypt? Have to remain encrypted (forceencrypt) to have working radios.

When I rooted the first time, I installed SuperSU that did not have encrypt flags set. So I figured I'd lost the radios. But every time I restored, I never got the radios back until I decided to manually use an alternate APN rather than the built in configurations.

I just talked to AT&T Customer Service after finding a flag indicating changes were made to my data plan on the day I tried to root using SuperSU without forceencrypt. They said the system updated the service for the device probably because there was an IMEI mismatch. It took maybe 30-40 minutes but the person at the other end added my IMEI to their database and I can now connect to the 'NXTGENPHONE' APN.
I'm guessing my IMEI was never in the database to begin with and when I went to the ATT store to get a new SIM when I bought this phone, the tech at the store did some kind of work around to make the APN work. Maybe somehow the data radios being affected after rooting allowed their system to do whatever correction it was programmed to do. <shrugs>
I did also put the SIM into my old Galaxy Nexus just to see if it was able to access data, that being a 3G phone, maybe that could have been the reason for the system booting me off the APN.

First you need the latest supersu, i usually use the stable versions. And you have to advance whipe data in twrp to get encryption working again to get signal back. Don't remember the exact words/buttons because the version used in the rootjunky video has changed with the current version but they are the same buttons.
Sent from my HTC 10 using XDA-Developers mobile app