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
Related
OK, so I got Boost 1031 and I flash them to Verizon 1028 firmware so we can use them on PagePlus.
I have flashed sever with this great guide but yesterday after flashing I allowed it to take te 4.4.4 ota and it worked fine but no 3G. I tried a few things without luck and decided to reflash the 4.4.2 firmware through fastboot. Apparently partition changes and such make this not work well. I guess I'm now stuck with parts of each and I can't seem to get either one back complete.
Symptoms: Reboots every minute or 2 and no wifi service.
I've tried sideloading the 4.4. ota, installing it from recovery and I also installed CWM, rooted and flashed a couple 4.4.4 roms and still wifi not happening and very unstable.
I began with unlocked bootloader, but stock otherwise. I really want to get it back to stock 4.4.2 or 4.4.4
I'm no expert by any means, but no noob either...any help would be much appreciated. I guess when someone release a complete 4.4.4 package I may be ok. Maybe a kernel or radio would work but I haven't found any packaged radios for 4.4.2
Fastboot & recovery are very stable...I'm back on stock recovery now.
BTW I flashed another today for a friend and updated it to 4.4.4 and everything worked fine...even 3G! I think I had a setting wrong in DFS is why 3G would work on the f'd unit.
Moral...Don't try to flash 4.4.2 over the top of 4.4.4
I'm having an odd issue. I've been running the latest Hyperdrive ROM release on my S3 for about a year now, but I can't stand Touchwiz ROM's so I've tried flashing AOSP ROM's such as CM, AOKP, even Beanstalk. I love all of these ROMs for tons of reasons but I keep running into the same problem, everything works great but I can't receive mobile data. My mobile network state is Disconnected and I have no idea how to fix that. I can text, call, and connect to wifi fine, but no mobile data. I've backed up my EFS but I'm not sure that's connected to the same thing. I have the network set to "CDMA/LTE" (would be more specific but each ROM has it different), but for whatever reason the APN settings are inaccessible. The menu option is clearly there but I cannot open it to ensure I'm using the LTE APN. I decided to give this another go yesterday, and still no dice. However upon restoring my CWM backup of Hyperdrive, I have now lost 4G and am stuck on 3G. My network type now shows eHRPD and while I can access my APN's (I was always able to on Touchwiz ROMs) I can tap on the Verizon LTE APN, but it seems to make absolutely no change to the actual APN. In fact when I reboot it it defaults back to eHRPD all over again.
So, 1. have I somehow screwed myself over? and 2. what am I missing with AOSP based ROMs?
Thanks for any and all help.
TheCing said:
I'm having an odd issue. I've been running the latest Hyperdrive ROM release on my S3 for about a year now, but I can't stand Touchwiz ROM's so I've tried flashing AOSP ROM's such as CM, AOKP, even Beanstalk. I love all of these ROMs for tons of reasons but I keep running into the same problem, everything works great but I can't receive mobile data. My mobile network state is Disconnected and I have no idea how to fix that. I can text, call, and connect to wifi fine, but no mobile data. I've backed up my EFS but I'm not sure that's connected to the same thing. I have the network set to "CDMA/LTE" (would be more specific but each ROM has it different), but for whatever reason the APN settings are inaccessible. The menu option is clearly there but I cannot open it to ensure I'm using the LTE APN. I decided to give this another go yesterday, and still no dice. However upon restoring my CWM backup of Hyperdrive, I have now lost 4G and am stuck on 3G. My network type now shows eHRPD and while I can access my APN's (I was always able to on Touchwiz ROMs) I can tap on the Verizon LTE APN, but it seems to make absolutely no change to the actual APN. In fact when I reboot it it defaults back to eHRPD all over again.
So, 1. have I somehow screwed myself over? and 2. what am I missing with AOSP based ROMs?
Thanks for any and all help.
Click to expand...
Click to collapse
I would try flashing a stock ROM such as the one on ScottsROMs.com
The 4.3 stock rooted, OTA disabled, UNlocled boot loader and no Knox.
See if you can get data with that. Firmware for the radio may have gotten messed up, and this would re-write that data (long shot, but worth a try). Another option would be to re-flash the radio maybe.
And now that I think of it, which radio are you on? MF1, ML1, NE1? Because I think I read somewhere that certain ROMs require a certain radio newer than _____ (don't remember which radio).
XdrummerXboy said:
I would try flashing a stock ROM such as the one on ScottsROMs.com
The 4.3 stock rooted, OTA disabled, UNlocled boot loader and no Knox.
See if you can get data with that. Firmware for the radio may have gotten messed up, and this would re-write that data (long shot, but worth a try). Another option would be to re-flash the radio maybe.
And now that I think of it, which radio are you on? MF1, ML1, NE1? Because I think I read somewhere that certain ROMs require a certain radio newer than _____ (don't remember which radio).
Click to expand...
Click to collapse
Thanks for the help. I flashed a 4.3 ROM as you suggested, and no difference. I then chased some threads around and decided to just factory reset it as if I was going to return it. Still nothing, I get 3G, not LTE. I was using MB1 before I flashed an AOSP ROM, at which point I flashed the MF1 firmware and then the ML1 modem. That did nothing to fix my issue. I'm not quite sure what else I can do at this point.
TheCing said:
Thanks for the help. I flashed a 4.3 ROM as you suggested, and no difference. I then chased some threads around and decided to just factory reset it as if I was going to return it. Still nothing, I get 3G, not LTE. I was using MB1 before I flashed an AOSP ROM, at which point I flashed the MF1 firmware and then the ML1 modem. That did nothing to fix my issue. I'm not quite sure what else I can do at this point.
Click to expand...
Click to collapse
Hmm... ML1 should be new enough.
That's a bizarre issue.
For me, I mainly get 3G. It seems as if either Verizon pulled some LTE towers near me, or my data antenna doesn't have very good contact. Maybe you're having the same issue.
Do you EVER get 4G? Or literally never?
Hey guys, I just flashed the CM13 nightly from stock 5.0 and now I'm showing no sim card. I saw a couple threads saying that newer twrp builds have issues with flashing radios, so I reverted to twrp 2.8.6 and did a clean flash, with no love. Tried flashing the radio zip, no love. Tried flashing the 3 most recent radios through fastboot, no love.
Any assistance would be greatly appreciated
Are you flashing both the bootloader and radio? If this doesn't work, I suggest flashing the latest stock MM to make sure the phone is working, then flash CM13.
Good call, trying it now
okay, flashed to stock 6.0.1, worked like a champ, flashed back to cm, now it connects to the network, but drops to no service after a second or two. Progress! Now that I know that you have to flash bootloader and radio, i'll try some different combos and see if i can get something to work. If nothing else, i can always go back to stock MM
Thanks!
Have you tried CM13 with a custom kernel? This may solve the issue.
You need to do alot of reading, no insult intended. Don't run b4 you can walk. If you didn't know to flash the radio and bootloader you need to learn alot. Luckily it's a bullet proof phone. Nightlies are not stable and not for daily drivers. They are works in progress and buggy as a result. Not for noobies, IMHO
The OP did flash different radios. It is not always necessary to flash a modem and bootloader to have a working phone.
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.
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)