Hello, it's been a while since I've stepped into XDA, busy with school and all
So I recently broke my G1, and thanks to insurance, I had it replaced. I quickly went to root it and apply Haykuro's Danger SPL as I did last time to my older G1. However, something happened. I don't recall what, but I remember it not being pretty.
I haven't had MMS since. Come to think of it, I don't think I did even on my last G1. Either way, I think it's due to how the Danger SPL flashed onto my phone. I want to know how I can downgrade to one that's a little more "stable" and get a better radio to see if it's that that's causing the problems. What do you guys think?
There's nothing unstable about the danger spl and it couldn't cause a problem like this. The 26i radio is also the most current and 'best' for the g1, so no point changing. It's more likely a phone configuration or network issue.. you'd be better off speaking to your provider and making sure your settings are right.
Are your MMS settings proper?
goldenarmZ said:
There's nothing unstable about the danger spl and it couldn't cause a problem like this. The 26i radio is also the most current and 'best' for the g1, so no point changing. It's more likely a phone configuration or network issue.. you'd be better off speaking to your provider and making sure your settings are right.
Click to expand...
Click to collapse
I've already spoken to T-Mobile on several occassions. They've done everything from remote access the phone to resetting the network as a whole in my area...nothing. I'm theorizing that it's the SPL because it didn't install pretty and I think perhaps it took MMS down with it.
B-man007 said:
Are your MMS settings proper?
Click to expand...
Click to collapse
What are the "proper" MMS settings?
lukekirstein said:
I'm theorizing that it's the SPL because it didn't install pretty and I think perhaps it took MMS down with it.
Click to expand...
Click to collapse
I don't think that's possible. Once the spl boots the kernel, It doesn't have any further role to play.. I can't imagine any scenario in which it could affect high-level functionality like that. If it'd somehow messed up your internal partitioning, I doubt you could've flashed a rom in the first place, so I really don't think the spl is to blame.
Anyway.. if you want to try it, you can just flash the engineering spl or hardspl through recovery, you don't have to do anything special that way round. Be aware its going to wipe your rom out though so have a copy on the sd ready to flash.
goldenarmZ said:
I don't think that's possible. Once the spl boots the kernel, It doesn't have any further role to play.. I can't imagine any scenario in which it could affect high-level functionality like that. If it'd somehow messed up your internal partitioning, I doubt you could've flashed a rom in the first place, so I really don't think the spl is to blame.
Anyway.. if you want to try it, you can just flash the engineering spl or hardspl through recovery, you don't have to do anything special that way round. Be aware its going to wipe your rom out though so have a copy on the sd ready to flash.
Click to expand...
Click to collapse
Okay, thanks for the details on the role of the SPL, it helps a lot. What about re-flashing the radio?
lukekirstein said:
Okay, thanks for the details on the role of the SPL, it helps a lot. What about re-flashing the radio?
Click to expand...
Click to collapse
You could try it but it sounds like a software config issue to me.. a corrupt radio would cause a lot more problems than failing mms. just make sure you use haykuro's 26i radio if that's the spl you're using.
You can try reflashing the radio as goldenamrz said...for some unknown reason, the radio seems to be affected after many flashes (ive personally never had any problems but i know it happens)
I'm curious what the result of this was. It sounds to me like this is a good way to brick a phone; I didn't think you could revert to a previous SPL after flashing the DangerSPL. Flashing radios willie nilly seems like that could also spell heartache.
From DangerSPL to HardSPL
I just reverted from DangerSPL to HardSPL with no fuss. Placed the HardSPL as update.zip in the sdcard, run the update, restart.
When it rebooted, i had the HardSPL and my rom almost intact. When you go from Hard to Danger, you need to add the rom again, as the installation does a wipe too. But from Danger to Hard it doesn't. So the phone booted straight away.
However, it had some issues, like lost wifi stored info and the home and call keys were unresponsive. So i used nano and a backup and i was up and running at no time.
The issue i had with receiving but not sending MMS was not solved by reverting to HardSPL. Settings are correct, tried with CyanogenMod and AOSP2.4 With Camera, nothing.. unresolved. I'll wait for next Cyanogen release and if nothing, i'll wipe and reinstall cyanogen from scratch..
edit. problem solved: type "default" at the apn type for DATA (not mms). Apparently, it is needed for the mms to ignore that apn and go for the one that has "mms" as an apn type
Related
I was updating my SPL and upon reboot I got the lovely looping T-Mobile G1 screen, camer+power, back+power, and menu+power all work, but I really have no clue what to do as to fix it, I am new to this, no I did not make a recover because I had just upgraded to Cyanogen's backup, wiping didn't seem to work, I think it was possibly because my rom was out of date? I have JFv1.51_CRB43-US, so my question to you guys is, could going out and buying another SD card and dropping a newer rom and putting the new card in my phone fix my problem?
If you were upgrading to the 1.33.2005 SPL, you need to reflash with whatever rom you are using. The SPL effectively wipes the rom out, so you need to put it back.
Yeah, I just read that in the fastboot for noobs thing, thanks for the info!
Edit:
Do I have to reboot with the exact same rom as before the SPL update?
In case you missed the key point, using that hacked SPL has the effect of WIPING ALL YOUR DATA, so how, if the data is shot, could it possibly care that you write the same thing onto it as it had before? Answer is that it DOESN'T. Now go ahead and write whatever you like to it.
Thanks, was just wondering. :x
Gotta learn one way or another.
I am using Cyanogen 4.0.1.
I recently flashed the new radio and then flashed the HardSPL and ever since then I have not been able to scan for Wifi networks. That appears to be the only problem I am experiencing at the moment.
Any one else have similar issues, or know of how to fix this.
Thanks in advance.
The SPL doesn't have anything to do with wifi. What does the baseband say in about phone. wifi, 3g etc. are powered by the radio, try to reflash that. Also link to the new radio you flashed. Doesn't hurt to check the md5 of your download.
I would definitely start with reflashing the radio image from Haykuro's site. If you are going to continue to use Cyanogen's amazing ROM, I would NOT flash Haykuro's SPL. Stay with the HardSPL to reduce chance of bricking on accident.
evilkorn said:
The SPL doesn't have anything to do with wifi. What does the baseband say in about phone. wifi, 3g etc. are powered by the radio, try to reflash that. Also link to the new radio you flashed. Doesn't hurt to check the md5 of your download.
Click to expand...
Click to collapse
I flashed the radio from Haykuro's site, I re-flashed and I still do not get any wifi.
The wifi function will turn on fine but then when I try to scan for my network and it will display a message saying "unable to scan for wifi networks" and then the wifi function will turn itself off.
btw, I am now running CM 4.0.2
I'm running Cyanogen 4.0.1 with Haykuro's radio+HardSPL and wifi works find and everything else. wipe and reflash.
something similar happened to me on my tmobile dash.
i flashed the spl wrong or idk and then my wi-fi broke
People have had similar experiences with wifi on the xROM. Many people weren't able to get wifi up and running with HardSPL, but then upgraded to Haykuro's SPL and it started working fine.
I don't think this is mere coincidence... even though neither dev requires the newest SPL, it seems that wifi doesn't work without it.
For what it's worth, update your radio (I'm sure you're on the latest radio, but for posterity's sake, just do it again), then update to the new SPL, then reflash your ROM.
Report back... I'm guessing you'll be a happy camper.
I've never had a problem but i upgraded to hardspl before cyans newest roms. maybe something in their updates kills the functionality
you should have put the newest radio before you flashed a cupcake rom
Any updates antirock? If it's still not working after a wipe and reflash, I would recommend reflashing the newest radio and flashing Haykuro's SPL. Check my sig for more info.
uansari1 said:
Any updates antirock? If it's still not working after a wipe and reflash, I would recommend reflashing the newest radio and flashing Haykuro's SPL. Check my sig for more info.
Click to expand...
Click to collapse
Ok, here is what I did.
wiped and reflashed radio and it still didn't work.
So I reverted back to Cyanogen 4.0, reflashed radio, reflashed spl, wiped, reflashed CM 4.0.2...and now wifi is working.
However, the vibrate funciton on my soft keyboard doesn't work. I figure that it is the rom, but no one else seems to be having this problem in the CM 4.0.2 thread.
Thanks for all of your help!!
antirock said:
Ok, here is what I did.
wiped and reflashed radio and it still didn't work.
So I reverted back to Cyanogen 4.0, reflashed radio, reflashed spl, wiped, reflashed CM 4.0.2...and now wifi is working.
However, the vibrate funciton on my soft keyboard doesn't work. I figure that it is the rom, but no one else seems to be having this problem in the CM 4.0.2 thread.
Thanks for all of your help!!
Click to expand...
Click to collapse
So you're still on HardSPL? If others aren't having this problem, then try Haykuro's SPL if you meet the requirements.
I had two G1s for a while... one of them flashed to JACxROM fine, but on the other, wifi wouldn't work. They both had the same radio and HardSPL. Flashing Haykuro's SPL to that phone and suddenly everything worked fine.
I don't know why these phones are like that... maybe its some small difference with the actual hardware inside the phone, or the downloaded file you're trying to flash, or maybe whether or not you flash when there's a full moon. Your guess is as good as mine. Point is that MAYBE the newer SPL will work for you.
It's funny how wiping, uninstalling and reinstalling usually fixes everything.
I wannna know what is the right thing to do after you downgrade to Rc29 as in
Keeping your phone up to date to instal the latest cyanogenmod
Cuz it seems to me that everytime I do my mods there is always something wrong
Little but wrong ya know I want my phone to run as good as it can .
I'm currently running RC29 US (not rooted no mods at all)
Just waiting to see what's the best thing to do
Thx in advance
http://forum.xda-developers.com/showthread.php?t=563679
Follow this to the T.
What's the difference bewtween hard spl and haykuros special spl somehow I like hykuros better but I don't really know the difference and you think I can use haykuros spl instead of the hard spl while following that guide?
Haykuros SPL repartitions the phone so the System and Data partitions are both ~90mb
The bigger partition allows you to install bigger roms such as Hero
However, the HaykuroSPL has a high chance of bricking your phone permanently if you dont know what your doing....
The most important thing is to flash the 26I radio before the SPL
However, you can install the HardSPL now and install the HaykuroSPL when you feel your read
Zixx said:
What's the difference bewtween hard spl and haykuros special spl somehow I like hykuros better but I don't really know the difference and you think I can use haykuros spl instead of the hard spl while following that guide?
Click to expand...
Click to collapse
The death spl is the saphires spl. People load it on the g1's to be able to load a hero rom because the hero roms are bigger needing more space. When you load it on the phone it resizes the partitions to make more space. Thats the reason why you have to flash a rom right after the spl because it overwrites the existing rom. If I were you I would load hard spl first to get the hang of everything then try the danger spl. Many people have bricked there phone due to that spl, but if you do try it don't take any shortcuts and read read read.
What to do,what to do?
Well...I would advise you follow a tutorial or go to youtube and follow a video or video's on how to root and all that happy horsecrap.That's how I did it my first time. I watched videos,watched how others did it and then copied what they did on my phone. I successfully came out of it rooted,with the updated radio,Haykuro's SPL, and a Hero ROM that I could depend on at that time.Since then I have flashed so many different ROM's I can't even count all of them anymore. I would definitely root the phone first though. Possibly call T-MO and ask them for an unlock code for the phone as well as that will let you travel overseas with the phone and use it on other carriers too. Rooting is the way to go with the G1 nowadays. A whole new world opens up to you once the phone is rooted! Anyways...good luck at your beginning and keep up the work. If you end up bricking your phone,call T-MO and tell em one of their updates bricked your phone and you want a new one. Take it slow and do things right though man!
I searched around the forums (LOVE THEM!) and couldnt find the answer so I figured it was okay to ask the question
The notification light on my G1 never turns off, it's always set to show the battery status instead of blinking with a missed call/txt/whatever
ideas?
please post your current ROM, Recovery, SPL, Radio, whether or not you use apps2sd...and anything else that we may need to know to diagnose your problem. Thanks...
-BMFC
This happened even on the stock rom, after I wiped everything clean and rooted... and when I flashed the newest Cyanogen
I've looked around and found no mention of this issue anywhere on any forum that I saw
T-Mobile G1
ROM: Cyanogen 4.1.999
SPL: Hard SPL
Radio: ... I havent touched this? Im not evne too sure what it is, so im assuming default/stock ota? how do I check
Recovery: RA-dream-v1.2.3
ThatsMajor said:
This happened even on the stock rom, after I wiped everything clean and rooted... and when I flashed the newest Cyanogen
I've looked around and found no mention of this issue anywhere on any forum that I saw
T-Mobile G1
ROM: Cyanogen 4.1.999
SPL: Hard SPL
Radio: ... I havent touched this? Im not evne too sure what it is, so im assuming default/stock ota? how do I check
Recovery: RA-dream-v1.2.3
Click to expand...
Click to collapse
if you dont know... you should update to the 26I radio
it can be found in the bootloader (cam+power)
for the us g1, last two digits are usually 29 or 26. (26 is the latest)
you can also find this info in the about phone section in settings under baseband
if its happening on the stock rom too, its probably a hardware issue. you wouldnt happen to have any apps that would mess with this setting, would you?
B-man007 said:
if you dont know... you should update to the 26I radio
it can be found in the bootloader (cam+power)
for the us g1, last two digits are usually 29 or 26. (26 is the latest)
you can also find this info in the about phone section in settings under baseband
if its happening on the stock rom too, its probably a hardware issue. you wouldnt happen to have any apps that would mess with this setting, would you?
Click to expand...
Click to collapse
yup I had the 26... what exactly is the radio?
but yea, It happens all the time when im flashing, when im in the spl... whenever
the radio manages all the wireless stuff in the phone such as the phone itself, bluetooth, wifi..etc
it also calls the spl, which loads the whole phone up
if its happening all the time, its a hardware issue and you should contact tmobile and see if they replace it. if so, unroot your phone before sending it in
im thinking this has to be some sort of software issue because it works for battery/charging/whatever... and apps can have their notification pop up over the steady green light
well then its an app. go back to complete stock and see if the problem persists. remove all your applications, and go to the stock RC29 image, update to 1.6 OTA and see if it still happens.....
does the light stay on in the recovery (Home+power) or bootloader mode (cam+power) when your phone is not charging? if it does.....its a hardware problem
hey.
Im almost sure i just bricked my g1, just need to be sure.
I was running Death SPL and the last official radio, and had gsm\umts network connection problems.
Decided to upgrade the radio to the last one that came out recently, i did, the problem seem to be better but it got worse in time.
downgraded the radio, and tried around 15 different roms, all tries with the same outcome.
so after a lot of trial and error, i decided to get back to one the the first radios available, but i was afraid it would brick my phone so i read carefully about it
I had a realy hard time finding something but i everntually came across a couple threads that stated that it was ok to flash any radio, as long as the SPL was flashed first...
after reading that i downloaded a 1xxx radio and flashed via recovery...
result: stuck in the G1 screen...
My question: phone in the crapper right?
thanks for reading guys
mordockcs said:
i everntually came across a couple threads that stated that it was ok to flash any radio, as long as the SPL was flashed first...
Click to expand...
Click to collapse
No, what they said is that it is OK to flash anything as long as you use FASTBOOT INSTEAD OF RECOVERY, and that FULL FASTBOOT (with this ability) depended on having a 1.33.2xxx SPL.
With an SPL and RADIO that are incompatible with each other, it is impossible to successfully boot the kernel. Following a flash-hboot or flash-radio, the system is set (via writing the command field in the MISC partition) to boot-recovery. When in boot-recovery, the phone IGNORES all user inputs. The incompatible radio/spl fails to boot-recovery, and you're bricked.
USING FASTBOOT INSTEAD prevents the misc partition from being set to boot-recovery by writing the SPL or RADIO directly. As a result, when you reboot, though it still won't be able to boot a kernel, IT WILL RESPOND TO USER INPUTS and bring you into FASTBOOT mode... from where it is possible to, again, flash radio or spl.
Your failure is a result of failure to read properly.
SPL/radio compatibility:
0.95.xxxx, 1.33.x003: compatible with 1.x or 2.x radios.
1.33.xxxx (except 1.33.x003): compatible with 2.x or 3.x radios.
No exceptions.
I always suggest using the 1.33.2003 SPL since DREAM should always use either a 1.x or 2.x radio (except robbers in canada, because they are bastards, but you can load those with a 2.x radio just fine). 1.33.2003 is the strongest engineering SPL available, and fully compatible with the proper radios. There is NO ADVANTAGE to any other SPL -- no, you don't need to change your SPL to reallocate storage space.... in fact, limiting yourself to SPL changes to do this will tend to waste a lot more space (15 MB more available than 1.33.2005 gives you).
lbcoder said:
Your failure is a result of failure to read properly.
Click to expand...
Click to collapse
no its not...im pretty sure about what i read...if i stumble on the thread again ill PM you to prove it.
i already have a touch HD on the way so no harm done, i wish this was all the harm in our world...
but anyway now that its dead...lets fix it!
is there a way around it? i hear about jtaging a lot but i have never seen a tutorial on the web...
any insight on that would be delightful...seriously
but hey lbcoder thanks for enlightening me i appreciate it, i really do...thanks man