XT925, JBBL and CWM 6.0.4.4
Has been running cm-12-20150408-NIGHTLY-xt925_jbbl for a long time.
Decided it was time to update, being JBBL there is only cm-12-20150417-NIGHTLY-xt925_jbbl which is newer.
Flashed that without issue and it appeared to be fine, however no wifi.
SIM, Bluetooth, NFC all ok, but when you turn on wifi nothing happens. Change screens and wifi is back to being turned off.
Hunted around, found a CM13 build for XT925, installs fine, everything works well ... still no wifi.
Went to a CM11 version ... still no wifi.
Rolled back to cm-12-20150408-NIGHTLY-xt925_jbbl which it has been on for about a year ... yep, no wifi.
Checked the baseband version each time and it is always vanquish_u_bp_100700.250.66.01P
I can get my way around flashing some roms, but I am no expert, so not sure if the baseband should change or if it is even related to this issue.
Any ideas or help would be appreciated.
Definite baseband problem
So after a lot more messing around, and reimaging and trying a bunch of stuff, I am now at "Unknown baseband" and have no radio connectivity at all.
There are a bunch of posts about this mostly for Samsung phones, the general theme is to get a stock image and reflash it. Or to try and erase the modem/ modemst1/ modemst2 partitions.
The issue is I cannot find a suitable stock image. Most of the links etc are dead as razr HD is pretty old now.
Its originally an Australian version of the XT925, though really that should not matter, any XT925 firmware should work I think, although I found the Rogers firmware and it bricked the phone pretty badly and took a while to recover it.
So if anyone has a lead on where I can find an image for the radio/modem or patch of that nature or has any good ideas on how to recover from this problem I would be grateful to hear.
Thanks.
some progress
well after more research, got a stock image installed, the trick was to use mfastboot.exe not the regular adb and fastboot.
Now have a baseband version back (same as before found a stock AU image eventually) however same issue as originally had which is now have mobile data connection but wifi doesn't work, auto disables when you turn it on.
Nailed down the problem to the persist partition, it was dead/corrupt.
Problem now is I need to get the files for it somewhere, I have created the wifi/bt mac addresses as there are some guides out there for that, but looks like I am missing some bin files as well.
Anyone able to have a look in their /persist and tell me what SHOULD be there?
finally fixed
After about a day of screwing around, its fixed.
Root cause, corrupt /persist partition.
The fix involved a combination of this guide
http://forum.xda-developers.com/google-nexus-5/general/guide-to-fix-persist-partition-t2821576
and eventually finding a copy of WCNSS_qcom_wlan_nv.bin and a decent stock firmware. As well as a lot of reading, swearing and experimenting.
After running so hot for so long it now has a bit of a bulge at the back, I think after 4years the battery is now going ... lol.
However now successfully running CM13 and I think everything is working.
Related
ok here goes, first off, i apologize if this is in any way redundant to someone's else question. with the amount of people whose phone got wrecked with the 2.3.6 update im sure somebody has had the problem im having.
like many people i just clicked "install" when google pushed the 2.3.6 ota. my phone was running 2.3.4. rooted. when it rebooted, i was greeted with the android exclamation mark.
i happened to have a clockwork backup so i tried restoring my backup. and restore it did, but not the radio. after the google update my radio was something like NO GSXXK1 or so. i tried the radio fix here:
http://forum.xda-developers.com/showthread.php?p=14564429&mode=linear#post14564429
i tried reflashing the stock 2.3.3 rom from google, wiping the bootloader and all. ive in fact tried many many things that ive read on xda and google forums.
now, ive managed somehow to have a running 2.3.4 with cell signal. using the efs file copy method in he link above. that restored my 3g and ability to place phone calls but sms arent working. i did the *#*#4636#*#* thing and notice that smsc is 00, i tried to set to the right value of +17057969300 for Rogers canada but all i get is an update error followed by a crash.
and now, funny, my search button is acting weird, like an eye that keeps twitching.
im not very knowledgeable in this stuff, just enough to get by and install custom roms but clearly im in over my head now.
why did copying my 3 efs file in the root of the sd card restore signal? i dont think these files really belong there, so just what the heck happened?
is there a way i can restore my nexus S to google stock rom when they shipped the phone? i mean, a complete wipe, sd, boot, radio...everything.
if i can start back with the stock phone, i can re-root again and start fresh.
any ideas please??
im physically tired of reading everything, misleading information and constantly flashing back and forth hoping its gonna work. oh and mandatory angry comment: thank you google for effing up my phone!
edit:
the only stock rom i tried i the 2.3.3 stock update available in clockwork. made no results.
current specs:
my phone is a i9020a
current baseband : NO DGSXXKD1
current build: GRJ22
android ver: 2.3.4
core: 2.6.35.7-ge382d80 [email protected] #1
Follow my last thread posted
Sent from my Nexus S using xda premium
Thanks dude, i had actually done that and did manage to get a signal back. its SMS that just wont work and when do the INFO thing to set the right value, i either get update error or a crash.
i installed stock rom 2.3.4 and install radio uckd1. that made my signal work even without having to move the efs files on the root of the sdcard. but still no sms.
is anybody else getting sms problems? this was working before the 2.3.6 fiasco.
im with rogers canada, in ottawa.
ok, just to loop the loop on this one and hoping it will be of use to somebody else.
my sms issue wasnt related to my phone at all, once i had a signal back, that's as far as the phone was concerned.
i placed a call to rogers to let them know i couldnt sms anymore.
long story short, they tried many things but ultimately, its doing the "hard" reset on the network for my phone that did it. im sure there a better name for it but basically they erased my phone from their network, i had to wait about an hour for the change to propagate. when i powered the phone back, it resynced everything and sms was back online without a single thing to do.
Before I post in the CM forum, thought I would try here first.
I am a very experienced flash/mod user and have never had a "brick" issue in many years of tinkering with dozens of devices. I have been using Cyanogen and AOSP roms since 2008.
Today, I thought I would try a CM12 build on an XT1031(cdma) knowing that even though CDMA is not operational, CM builds are unified anyway. I figured it wouldnt be like flashing a GSM ROM onto a CDMA device. Well, I guess I was wrong...
It appears that CM12 builds are indeed GSM specific, and though the ROM installed and ran correctly, it seems to have corrupted both wifi and cellular radio at very deep level.
I fastboot flashed back to 4.4.2 stock, and it boots fine. Wifi connects and grabs an IP but doesn't transfer data, and cellular stays as a black triangle. It seems to grab MIN and phone# and has correct MEID.
Eventually, after 60-120 seconds the phone will crash and reboot.
I have tried flashing stock radios from the thread here, and have also tried several other falcon stock and CM11 roms. They all exhibit the same behavior...boot fine, no networks, and crash after a minute or two.
I find it hard to believe that flashing a ROM would physically damage BOTH wifi and cellular radios. One or the other I could understand. But this seems like a deeper problem at a base level of the phone...below ROM or firmware.
Is it possible that changes were made at at the /persist level? Is there any way to reflash the /persist partition with a stock image?
I have access to bootloader and recovery (currently TWRP). Any suggestions are greatly appreciated.
I really just want to get wifi working... plan on using it wifi-only anyway. But it would probably be good for the community to document the problem and see if we can figure out what caused it and if it is fixable or "brick-worthy"
Thanks!
Sent from my XT1028 using XDA Free mobile app
Got it fixed.
I didn't notice, but the CM12 build automatically upgraded the bootloader to 41.13. I was not able to fastboot flash the motoboot.img and boot.img files because they were the wrong version. Once I flashed it with a 4.4.4 version of motoboot.img and boot.img, I was able to flash the system partition back to 4.4.4 stock and it is working 100%.
So, if you are reading this and are in a similar situation with "preflash validation failed" or other "downgrade" errors, check your bootloader version. If it is 41.13, you will need to manually flash 4.4.4 images.
Now, I am just stupid enough to try this again...this time with a custom modem/radio image
Hi guys,
Tried to flash OxygenOS 1.03 through twrp 2.8.7 after getting some annoying problems with OPO on the latest CM11s.
Done many flashes before so didn't really expect much problems. Then OPO couldn't boot up at all with black screen. I followed the instruction here to unbricked with factory tool to clash an old edition of ColorOS and I thought that was the end of it. Flash OxygenOS again, bricked again.
Then I recovered and flashed COS 12.1. Didn't really want to make the jump but I had too. I immediately noticed I am unable to connect to 4G. Thinking that the OS 1.03 from OP didn't contain any modem update and thus the hard brick, I flashed 1.03 again and worked. Again no 4G or any cellular connection. I went out side and finally got a very weak 4G connection (I usually have full bar around my home). Really desperate, I flashed back to official CM12s, and flashed the correct radio for it. Same thing.
It has been a week now. I could get some connection if force it to 3G but still very spotty. It is hard to use. I tried different modems, even one from ColorOS because I am in China and I got the phone in US.
Any tips on solving this?
I fixed it by reflash raido of xnph52q found here. The zip contains more than the radio firmware.
http://forum.xda-developers.com/oneplus-one/development/rom-stock-rooted-xnph52q-t3025399
I flashed it before but it didn't work. The only difference is I used TWRP 2.8.6. I remember reading somewhere online that 2.8.7 has issue with OPO.
I will changed it to resolved and save it as reference for others
So ever since yesterday I've been able to use WiFi. I was chromecasting something and while it was casting my phone went through a reboot, thought nothing of it since its happened lately. Well i think it did it a few times. Well I check my phone after my show is over and my WiFi is off., and I can't turn it on. I rooted my phone last night since it was unlocked already from when I had it rooted before. It's on Android 6.0 right now. I was just wondering if anyone had any ideas of how to fix it. I was getting a logcat error in reference to the wifistatemachine.
Did you try flashing an older stock rom?
I have a phone with the same problem and it believe it is a hardware problem because stock and custom kk, lp, and M ROMs do not solve the problem. After swapping out the motherboard, everything was fine.
I have not yet. I was trying to create a nandroid backup first, but NRT doesn't seem to want to let me do that because i don't have a modified boot image.
Hi guys,
I wrote a thread over on zukfans.eu, basically I factory reset my phone on one of the stock roms and it has corrupted my modem, or destroyed my data in my CQN. The long and the short of it is that i have no service and the radio is off, i can't fix it, and no one is helping me over there so maybe someone here will know. How can i flash the modem to my phone, do i just do it in fastboot? Does anyone have a modem file? Can someone backup their CQN for me so i can see if that will fix it (instructions in the thread at zukfans.eu here)?
I've tried flashing stock roms in both QPST & MiFlash and also tried installing via twrp, no luck on any of it. I'm currently on the indian rom 2.0.111 ST with unlocked bootloader and TWRP. I'd really appreciate it if someone could tell me what to do or point me in the right direction.
Cheers
it seems that there are so many people having the same problem.
My modem has been corrupted today on the original room mounted from bangggod, I had bought it 1 month ago.
As you did, I tried several other roms and also the QFIL solution without luck.
I have written a mail to zuk and to banggod asking for an explanation....
It looks like an hw problem.
Flashing modem, which one, updates?
Same here as sooooo many people. Done many things, nothing working yet. I am still hoping not hardware problem.
I see many posts about reflashing modem. Never sure which modem file to download though, and from where.
Also, not obvious to me (new at this) when I flash the ROM does it automatically flash a new modem file? Or does it see one is there and not flash it? I have tried Mokee and others, went back to locked stock 1.9 and now I am downloading official Nougat update and hoping it will flash/fix modem in process. Great phone otherwise. I am crushed.
(edit: I update to AICP instead, nice!, but still no working modem. I do get a switch to turn on radio in phone info though, but nothing. Looking like hardware indeed, but I am still hoping someone will find an answer)