So I finally took the jump and rooted my T-mobile Sensation 4G (including unlocking the bootloader, sim-unlock, S-OFF, root, SuperCID, did I forget anything??). Flashed Cyanogenmod 9.1. Have CWM ROM Manager installed, and Titanium backup.
It works MUCH better than the stock ROM, and I'm very happy with it, EXCEPT, the radio's data connection (very fast when working) stops working for hours at a time. There does not seem to be any trigger for this. The regular non-data connection (phone calls and texts) continues to work. The H by the signal strength indicator will flash on periodically, maybe every few to 10 seconds at best, but you never actually get a connection. (3D and E do not appear at all). The signal strength is full. This happens both at home and out.
I thought it might be the radio, and after looking into that, decided to flash some new firmware. Initially (after the rooting/update), it was reporting firmware (from fastboot getvar version-main) of 1.24.401.1. On the boot screen, it said Juopunutbear (I used that method to get S-off). It was reporting baseband of 11.69A...
So I flashed the 3.33 universal firmware, and used the GetRIL app to update the RIL. It now reported firmware 3.33.401.106 and baseband 11.76A...
But no difference in data connection - not working at all.
So I flashed the 3.32 stock TMO firmware, used GetRIL again to get the right RIL. Now reporting firmware 3.32.531.14 and baseband 11.69A again.
But again, no dice on the data connection.
Wifi connection works fine, so I use that when in range.
Other current info:
bootloader screen:
HBOOT 1.27.1100 (this went down from 1.27.1111 version, which I think the HTC bootloader unlock installed).
Radio 11.23.3504.07_M2
eMMC-boot
firmware version:
3.32.531.14
From the running phone itself:
Android version: 4.0.4
baseband: 11.69A.3504.00U_11.23.3504.07_M2
kernel: 3.0.36-g7290c7f
Cyanogenmod version: 9.1.0-pyramid
The one thing I have not tried is to flash a different ROM than the Cyanogen...worth trying (any recommendations?) or another other ideas of what might be going on?
thanks!
Related
I just bought a MT4GS used on eBay and activated a SIM on T-Mobile. It was loaded with HBOOT 1.45.0013 S-On, so, after rooting, I followed the instructions to install pyr'o'ice 1.1.3 desensed by first flashing its boot.img via fastboot usb. However, after trying this process twice and getting a successful install (amazing ROM, btw) both times, I still don't have any 3G connection. I only see the little "E" which I assume is edge and is mad-slow. Any tips on this? Something I did wrong? Thanks.
that all depends on your location not rom
I am running the same ROM and my connection shows H (which I believe is 3G), but there is a T-Mobile (my carrier) cell site about 1 block away from me
I recall reading that some stock roms lie about the reported connection speeds. You might take that into consideration if you are only looking at what the UI reports as the connection speed before/after the ROM flash.
Samsung Nexus S I9023 (Australian stock)
Baseband version I9020XXKI1 (from bootloader screen)
Baseband version I9023XXKI1 (from System Settings>About phone)
Bootloader version I9020XXKL1 (from bootloader screen)
Kernel version 3.0.8-g6656123
I have been using my Nexus S I9023 with official OTA 4.0.4 (and 4.0.3 before update) with no wifi or network problems. Yesterday however I decided to unlock bootloader, gain root access and flash a custom rom for performance/battery life purposes. I flashed CyberGR-MOD v.11 with the stock kernel and radio with CWM, with no other add-ons flashed.
It went well except for the fact that wifi has not been able to turn on since the first reboot. The switch will attempt to slide to 'On' but flickers, and hangs on 'Turning Wi-Fi on..' It makes no difference whether the SIM is inserted or not, Wi-Fi just does not turn on. Under 'Advanced' WiFi settings, WiFi MAC address and IP address are both Unavailable.
I have been searching for fixes for the last day, such as the WiFix apk found on this thread (http://forum.xda-developers.com/showthread.php?t=1445766) but nothing has worked. I have tried flashing other ROMs, reverting to stock OTA 4.0.3 and relocking the bootloader to return the phone to stock, but WiFi will not turn on in any configuration.
Portable WiFi hotspot also will not work, with merely 'Error' being reported when I try to turn it on.
Is the disparity between bootloader/phone stats regarding baseband version an indicator that I flashed incorrectly? Is it a radio problem?
Would greatly appreciate some speedy responses as I cannot seem to find any solutions to this particular problem.
[EDIT] Fixed problem by installing new kernel, was not able to do this before as my version of CWM was bugged and required an update. From then on was able to flash new files, kernel was the answer!
Hello, I installed the (hopefully) newest firmware from this thread: [RADIO] [FIRMWARE] ICS firmware and radio from WWE RUU
Afterwards, I installed CM10 by nk111, which is running great, besides problems with the download speed on mobile network. The signal is great, as networkcoverage is as well. But the download, even on H (4G equivalent) is very, very slow.
The radio/baseband combination, which came with the new firmware, is: 20.76.30.0835U_3831.19.00.110
Does somebody know, if there is a matching RIL out there? Or are there different radios, which I could try? Maybe even the "old" GB radios?
I checked RIL on my phone manually, which is: HTC-RIL 4.0.0034HM
You can check it via adb (or terminal emulator) with
Code:
getprop "gsm.version.ril-impl"
Did nobody else mess with these things? Which RIL/baseband combination are you using?
So I'm S-on. Hboot 2.15 and not on the supported firmwares to do s-off via moonshine. I'm can never run 4.2.2 or 4.3 roms because when my phone switches between 4g/3g/edge etc it drops service completely and i have to wait for it to restore. I'm on Mckinneys stock latest release of sense from a while back but my data speeds still seem to be incredibly slow and many times get page load errors etc.
I was wondering if it is possible to update my radio or firmware to a different one to see if that helps. Is that possible while still being S-on?
Any help is greatly appreciated.
A little over a week ago I started having the fairly common issue on my (hitherto completely unmodified XT1039 where the radio is turned off and can't be turned back on again.
Following advice from similar threads on this forum, I unlocked the bootloader, installed TWRP and flashed the stock 5.1 ROM found in this thread as Retail EU 5.1 ROM (Optimized) v1.1: https://forum.xda-developers.com/moto-g/4g-development/rom-stock-motorola-4g-lollipop-rom-t3142816
Didn't get anywhere so I flashed the radio firmware provided in that thread. Symptoms remained the same:
5.1: SIM reads fine, WiFi works, radio off, IMEI reads fine
Following another thread, I tried downloading the stock 4.4.4 ROM from https://firmware.center/firmware/Motorola/Moto G (1st gen-2013)/Stock/XT1039/
Being a beginner, I ran into difficulties with manually flashing the xml.zip ROM - but on a hunch I tried flashing the radio firmware only.
Surprisingly, this worked - kinda. Having done that, I had a system where the radio worked - but the SIM wouldn't read, and the WiFi wouldn't turn on. I quickly figured out that I could switch between the two states by flashing the 5.1 or 4.4.4. radio firmware:
5.1: SIM reads fine, WiFi works, radio off, IMEI reads fine
4.4.4: No SIM, no WiFi, radio on, IMEI reads fine
Running out of ideas, I tried flashing LineageOS, only to get yet another configuration:
Lineage: No SIM, WiFi on, radio on, IMEI won't read
However, with Lineage running, I could flash the relevant 5.1 or 4.4.4 radio firmware to get those states back.
Finally, tried installing 4.4.4 from https://forum.xda-developers.com/moto-g/4g-development/rom-stock-motorola-4g-kitkat-rom-t3160127
This gives me the same set of symptoms I had originally (SIM reads fine, WiFi works, radio off, IMEI fine), whatever radio firmware I flash.
I am at this point pretty stumped - this is my personal phone so would be pretty pleased to get it up and running again. Any kind souls have useful ideas on what my next steps should be?