Hi all.
So, looking in the general forums I saw threads blow up because people thought that a maintenance thread was the ICS update.
Seeing that their had been a maintenance update I myself went to my settings and pressed "Software Update" only to see a message saying "No Firmware"
So I connected my phone wirelessly to kies and went on my browser to see if I could find something on there and there was nothing on kies either?
Can someone help me?
Here is what my about phone says:
Android Version: 2.3.6
Baseband Version: T989UVKL1
Kernel Version: 2.6.35.11
Build Number: GINGERBREAD.UVKL1
and YESSSS. I am stock unrooted. I have rooted before but flashed back to stock in hopes of the ICS update like a week ago. Can someone please shed some light on this for me please? I am concerned that TMobile is like excluding me or something.
Searching does wonders...
http://forum.xda-developers.com/showthread.php?t=1615590&page=135
see post #1345
Haha, TMobile excluding you.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Related
I have a Samsung Epic,
Model: SPH-D700
Firmware: 2.2.1
Kernel Version: 2.6.32.9
Build number: FROYO.EC05
Hardware Version: D700.0.5
I have flashed this and put roms and what not to it. I thought I had it flashed back to original and updated it so it can be OTA update from Sprint.. But honestly the phone feel super buggy and lags. I feel that im still not use a clean version.. Can someone help? Besides from going to sprint and getting a new phone. I don't know what else i can do.
Thanks!
Go to the development section and open the thread about returning to stock. Then follow the directions.
sooooooooooooo i just got my evo today (from the sprint store) and have been doing some reading about rooting. i went to a wiki and saw that the current build can't be rooted yet. in my device information it says i have build number 4.22.651.2. that can't be rooted yet right? I also would like to know where the best place is to start learning about rooting and roms and everything (kernals and everything i need to know so I don't mess this bad boy up). I used to have a TP2 that I knew how to flash but this is a totally different ball game. thanks in advance for the help. everybody at xda is and has always been great and very helpful.
Go to the forum portal page and look for the android section and go to chef central
Sent from my PC36100 using XDA Premium App
also meant to mention my currents software info:
Android version 2.3.3
kernel version:2.6.35.10-g4e39384
build number 4.22.651.2 cl60865 release-keys
software number: 4.22.651.2
PRI version:2.13_003
PRL version: 01115
Hey all, mega n00b here
My story; I was running Froyo on my P1000 until last week, Kies told me there was an upgrade available to 2.3.3 GB which I undertook.
I took exception to the navigation button lights always on. I looked and searched all over for fixes and tried in vain to root my tab. I even installed a new Kernel that was supposed to be rooted - it installed but no root!? PLUS my WIFI was now f***ed and either would not connect or continuously dropped.
Anyway, the installed kernel had CWM Recovery in it.
I found another post that led me to the Overcome ROM & Kernel.
I installed the Kernel first and was shi**ing bricks when all that happened was the word "andriod" flashing on the screen!
After friggin about with CWM I found I could load the ROM from the external SD which I duly did and Voila a working Tab, and boy is it slick.
Now, I have two questions - any and all help greatly recieved:
1.) What is up with the website for the install guide and other files?
2.) What do I need to do to install a modem and which one is most suitable for my tab I am in UK on Vodafone.
Device Details:
Model Number: GT-P1000
F/W version: 2.3.3
Baseband version: P1000XXJPZ
Kernel version: 2.6.35.7 Overcome-v4.0.0 #40
Build number: Overcome 7 Series v4.0.0
IDK and no
OK
So, no modem needed? ...I've not tested the 3G data on the Tab yet.
I found the issue with the w/s...
http://forum.xda-developers.com/showpost.php?p=18751328&postcount=131
...from the horses mouth so to speak.
EDIT: Tested 3G and all is perfect!
Hello,
I just decided to flash Cyanogenmod 9 to my phone to get 4.0.4 and noticed that the signal indicator was hollow and had an x in it after waking up. I then abandoned Cyanogenmod 9 and flashed the 4.0.4 stock image to my phone. Now I can't seem to keep the device connected via mobile voice and data and all I seem to be able to do is reboot the device. I am kind of new to the GSM scheme, but the APN list is empty and I can't seem to scan for mobile networks. To me it seems like the radio is completely disabled. Here are the specs, if anyone has any advice I would appreciate it. I am going to try to restore my backup of my previous rom. Alternatively if anyone has the stock radio image for the yakjuxw, I could also just try to restore that. Thank you for reading my post ^_^.
model: galaxy nexus
android: 4.0.4
baseband: I9250XXLA2
kernel: 3.0.8-g034fec9
build: IMM76D
dosmage said:
...
Alternatively if anyone has the stock radio image for the yakjuxw, I could also just try to restore that....
model: galaxy nexus
android: 4.0.4
baseband: I9250XXLA2
kernel: 3.0.8-g034fec9
build: IMM76D
Click to expand...
Click to collapse
grab the radio of ICL53F from http://code.google.com/intl/en-EN/android/nexus/images.html
that is the same one you had on yakjuxw.
4.0.2
Thank you. About an hour after my post I tried flashing the yakku stock firmware. I appear not to be having the issue on 4.0.2! I have a sneaking suspicion that the problem is the kernel. I base my hypothesis on the fact that 4.0.2 yakju works fine and Cyanogenmod 9 had similar issues with the same baseband. I'm going to try flashing the newer baseband and staying with 4.0.2 to see if it recurs. Thank you again for confirming the yakjuxw used the same baseband as the yakju! This is all new to me and I appreciate the advice.
dosmage said:
I'm going to try flashing the newer baseband and staying with 4.0.2 to see if it recurs. Thank you again for confirming the yakjuxw used the same baseband as the yakju!
Click to expand...
Click to collapse
I'm afraid of you won't learn anything from this. The 4.0.2 ROM(!) is sticked to GSM/CDMA, but 4.0.4 is sticked to WCDMA preferred...
Hello,
I think the problem comes from Android 4.0.4 itself. I have the same problem with a stock 4.0.4 flashed from the factory image provided by Google.
Other people have the same issue and are talking about it here : http://forum.xda-developers.com/showthread.php?p=24304822
Same problem here. After update to 4.0.4 I always lost the cellular signal when screen has gone down. I tried with different radios (xxkk6, xxkl1) but it didn't help. Anytime I move back to 4.0.2, problem disappears.
Originally my Gnex was yakjuxw.
My GN was yakju
Strange.. I suspected until now it is related to the difference of yakju and its variants...
Sent from Galaxy Nexus
I've checked and my phone is a Yakju, I tweeted a pic when I got it : https://twitter.com/#!/mephissto/media/slideshow?url=http://yfrog.com/kicn0p
Hi guys,
I have seen a few threads like this so my bad for repeating this. I have tried the given options.
So i've had my GSM galaxy nexus for 2 months. she runs 4.0.2 and is rooted. I have received the stock update 8 times but it failed to install each time. There was a little droid bot lying on his back with a red "caution" triangle stickin out of his belly.
I then tried to flash the ROM myself but got the same problem after trying a couple methods. i'm not sure what's wrong. please help. here are my specs:
Model number: Galaxy nexus
Android Version: 4.0.2
Baseband version: SC04DOMKKD
Kernel version: 3.0.8-gaaa2611
[email protected] #1
Build number: ICL53F.I9250ZSKL2
Efrant made a great guide.
http://forum.xda-developers.com/showthread.php?t=1419170
The Android you're seeing is stock recovery...
You might also need fastboot and such.
If you don't have them.
Check my guide (siggy) for info on setting that up.
Haha gotta love your thread tittle "dead android bot " Hahaha
And Yeah follow efrant guide... Its awesome..
Galaxy Nexus AOKP m5 Franco kernel m3