(solution at the bottom of this post)
Hey, ive searched for a little while now and i havnt found a solution, so if i missed it im sorry just point me in the rigth direction. In the mean time, here is my issue:
Its the same issue with:
4.5
4.9
5.0
(these are the only onces ive used)
all downloaded from:
http://code.google.com/p/sapphire-port-dream/
now ive wiped before flashing each update, and even wiped after the update, ive even gone back to rc29 and then trying again
when i get the phone to finish booting up, my radio gives me issues, it will show full bars, then none, then full, then none, never showing edge, so i go into wireless settings and realize that every 20 seconds or so, airplain mode is coming on for a half a second then going back off, without me clicking it, but when it does this, it never shows the airplane icon where it does if i click it myself in the top status bar
now if i manage to dial out a call at the right time, it will keep the full bars, and dial out properly, i can have a half hour phone call or longer without a problem, when i hang up, i have full bars AND edge for atleast a hour or so, and then i drop edge all of the suddon and go back into the airplane loop, inwhich a simple phone call (even to voicemail) fixes it temporarily
this issue happens as soon as i reboot the phone as well, as it starts up, it shows no connection, then emergency calls only, then tmobile, and repeats
when under mobile settings when trying to select a network manually if im lucky for it to show tmobile and at&t, 90% of the time it tells me it cant connect to tmobile due to my sim. if i keep clicking it it will say registering to network, but it will stay in the loop with the airplane mode flickering on and off
again, if this is something stupid im missing, or if its been explained elsewhere, my bad just point me in the right direction, but either im not searching for the right thing or ive just completely missed it, either way, someone help me before i have to go back to JF 1.42, im really enjoying this magic port
Ok, so thanks to the suggestion to "update the radio" and Google for pointing me in the right direction. I did as follows, and so far, so good.
Download this file to SD card
http://sapphire-port-dream.googlecode.com/files/Saphire-Radio-Update (rc33).zip
Saphire-Radio-Update (rc33).zip Sapphire Radio 2.22.19.23
Rename it update.zip
Reboot Phone in Recovery
(I wiped, this may not be needed, but I did anyway)
Alt + S to install the update
the phone will ask you to do the home + back to reboot, press it and it will do a few other things, including reboot into a screen with a arror pointing at a microchip, then it will reboot back into recovery
hit the home + back yet again to perform another reboot and it will boot up normally and so far, ive yet to have an issue with my radio after this
wootroot-
THANK GOD I AM NOT ALONE!!!!
This problem has been plaguing me as well with all of these new builds!!!
Ultimately I ended up going back to JF 1.42 MOD because I needed a working phone.
I flashed to 5.0G tonight... and its doing the same thing... radio on then radio off. I tried flashing to the new Sapphire radio... nothing works.
I would love for someone to come up with a working solution.
Thanks!
Web
webgrafix said:
wootroot-
THANK GOD I AM NOT ALONE!!!!
This problem has been plaguing me as well with all of these new builds!!!
Ultimately I ended up going back to JF 1.42 MOD because I needed a working phone.
I flashed to 5.0G tonight... and its doing the same thing... radio on then radio off. I tried flashing to the new Sapphire radio... nothing works.
I would love for someone to come up with a working solution.
Thanks!
Web
Click to expand...
Click to collapse
i feel the same way, i thought it was just me
there has to be something im missing, so many other people use these builds without issues like this, there is no way someone could put up with this issue and use the phone as a daily phone reliably
if you want to have 5.0 (well i flashed H not G but im sure it would work regardless) time a phone call to your voicemail when your radio flashes on and when it vibrates saying the call connected, hangup, and everything will be fine for a few hours
do me a favor though, read over the stuff i just added to my first post, see if your phone is doing anything different than mine, that way when someone who comes in here and is able to help, they know exactly what our phones are doing, and hopefully its not just us with this issue and it will get others in the trend of explaining in detail what is wrong with theres, maybe this will help speed up getting a solution lol (wishful thinking?)
I am redoing things once again.... reflash, etc.
Keeping my fingers crossed.
But it's late and I am tired and annoyed.
If it happens again... I will try to make a video of whats happening so others can actually see it.
I thought I was going crazy I'm on 5.0G now the new one which adds busybox but I've been having the same exact problem as the OP but I haven't tried the Sapphire Radio yet but we all seem to experience different issues anyway.
Land Of The Trill said:
I thought I was going crazy I'm on 5.0G now the new one which adds busybox but I've been having the same exact problem as the OP but I haven't tried the Sapphire Radio yet but we all seem to experience different issues anyway.
Click to expand...
Click to collapse
no fun, sorry your having issues too, you say we are having different issues, could that be because we are using the HTC code and your using the GOOGLE code? or did i misunderstand you?
can you explain a little more about the sapphire radio vs other radios? ive been trying to understand what the difference is, and how to switch between them, but so far im unable to find a clear answer, so can you tell me the difference and how to switch between them?
thanks for your help
EDIT:
oh and what do you use busybox on the g1 for? i just read up on it (http://en.wikipedia.org/wiki/BusyBox) and i have a general idea of what it is now, but whats the use of it on the g1? do you use it as kind of a DOS for the g1? is it more for developers than end users?
This problem has happened to me but seems as all I needed to do was to reupdate the radio. It worked for me!
Mast3rmatt said:
This problem has happened to me but seems as all I needed to do was to reupdate the radio. It worked for me!
Click to expand...
Click to collapse
thanks man, i just did that using this radio update, so far (on 5.0) im not having any issues, for the record i did a wipe before updating the radio just to make sure i started fresh
i used this update:
http://sapphire-port-dream.googlecode.com/files/Saphire-Radio-Update (rc33).zip
Saphire-Radio-Update (rc33).zip Sapphire Radio 2.22.19.23
http://sapphire-port-dream.googlecode.com/files/Saphire-Radio-Update (rc33).zip
download this.. all is resolved.
it has been discussed over a hundred times in the original thread.
Still having issues!!!
I am still having these same issues!!!
I posted a video here....
http://www.youtube.com/watch?v=0-j5x953Vkw
Its driving me nuts! I downloaded and flashed the Sapphire Radio RC33 twice! Still acting up.
It runs fine in JF1.42MOD.
Any ideas??? Any other radio ROMS I can try?
webgrafix said:
I am still having these same issues!!!
I posted a video here....
http://www.youtube.com/watch?v=0-j5x953Vkw
Its driving me nuts! I downloaded and flashed the Sapphire Radio RC33 twice! Still acting up.
It runs fine in JF1.42MOD.
Any ideas??? Any other radio ROMS I can try?
Click to expand...
Click to collapse
try reflashing the rom, then do the radio update
Hi all, I've just rooted my phone (Australian release on Optus) and i was wondering if the radio update has regional limitations or not? Because i've heard positive things about it but I don't want to screw my phone up.
webgrafix said:
I am still having these same issues!!!
I posted a video here....
http://www.youtube.com/watch?v=0-j5x953Vkw
Its driving me nuts! I downloaded and flashed the Sapphire Radio RC33 twice! Still acting up.
It runs fine in JF1.42MOD.
Any ideas??? Any other radio ROMS I can try?
Click to expand...
Click to collapse
did you get it working right? i tried the 5.0h as well and did the sapphire radio update and mine was doing that as well so i went back to jf. i wouldn't mind trying it again if i could actually use my phone. lol
Related
Hi. I've had these problems with my htc hd2, I've had the sms probs, but that got fixed after talking to you guys And now when people call me, or I call other people it freezes, im able to stop the conversation (which doesn't actually start), reset the machine (red button on the back or pull-out-battery) and then call back... This is really annoying, it has happened twice today, one time yesterday, and one time every day before.. I don't call people or receive alot of calls, but always the first call "****s up". Then its ok for the next call. Doesn't happen to anything else (yet), only calling. It's not that big of a problem, but my bills are keeping to get longer seeing that I have to call back all the time. :/
Jnygaard
I think the information you are providing is just a bit to little. you have explained your problem but you are not telling what radio and rom you are using.
in general have you tried a hard reset? or is the problem also there with your sd card in the phone? people have problems with phone freezes because of sd cards. especially the larger cards.
Oh yeah, sorry, I'm abit new to this.
Rom: 1.66.409.1 (NOR)
OS: 5.2.21869
Radio: 2.06.51.07
I always use a SD-card which is the standard 2gb which came with the phone, i could go some days without, and see if it works. Unless you have any other ideas?
Haven't tried a hard reset, doesn't that mean I'd have to upgrade it again?
I suffered from this last week & almost tested the bounciness of the phone I got so annoyed with it. As you'll see from my postcount I am an absolute noob but...I removed a couple of custom taskbars I had installed & bizzarrely everything returne to normal. probably a complete coincidence which I'm sure the experts here will confirm
Clever.. But "Custom taskbars" what did you mean by that, I'm more of a noob than you ;b
Hi, the taskbar is the info' strip display at the top of the phone. The standard one is a "clunky" black & white design. I installed some fancy, coloured ones which I now know should only be installed on HD2s with winmo6.5."whatever number it's at now" installed. Mine is a stock 1.66 ROM with winmo 6.5 device. Like I said the two may be completely unconnected but - touch wood(Ooh err missus), I've not had a call freeze since uninstalling them. I can't believe I've been outnoobed either lol! Best of luck...
Oh, yeah I've got the stock "black 'n white chunky" one :/ so there must be something else
I'll keep an eye on this thread for updates, of course I tempted sodding fate & the bloody thing locked up on me about half an hour after posting my reply. Cover off & soft reset & we're off again but this is soooooooooooo annoying when it does happen. best of luck to you.
Dunno if this is alowed, but Bump? (bring up my post )
Jnygaard said:
Oh yeah, sorry, I'm abit new to this.
Rom: 1.66.409.1 (NOR)
OS: 5.2.21869
Radio: 2.06.51.07
I always use a SD-card which is the standard 2gb which came with the phone, i could go some days without, and see if it works. Unless you have any other ideas?
Haven't tried a hard reset, doesn't that mean I'd have to upgrade it again?
Click to expand...
Click to collapse
what upgrades are you talking about? if you've installed any apps or customisations then you'll have to reinstall those after a hard reset, but otherwise it will just blow away all your info and give you a clean slate to start from with whatever ROM/Radio combo you have. definitely worth doing if you haven't done that yet.
otherwise maybe try upgrading the radio? or another ROM if that doesn't work...
Jnygaard said:
Hi. I've had these problems with my htc hd2, I've had the sms probs, but that got fixed after talking to you guys And now when people call me, or I call other people it freezes, im able to stop the conversation (which doesn't actually start), reset the machine (red button on the back or pull-out-battery) and then call back... This is really annoying, it has happened twice today, one time yesterday, and one time every day before.. I don't call people or receive alot of calls, but always the first call "****s up". Then its ok for the next call. Doesn't happen to anything else (yet), only calling. It's not that big of a problem, but my bills are keeping to get longer seeing that I have to call back all the time. :/
Click to expand...
Click to collapse
Try flashing to one of the latest Radios.
I had this problem when I was on a very old Radio 2.04 with the latest custom Roms.
Well, I have the latest rom, and thats the only rom I can get :S and isn't the radio upgraded with the rom ? if not, where do I upgrade the radio ? (radio: 2.06.51.07)
radios are in one of the stickies in the ROM forum
http://forum.xda-developers.com/showthread.php?t=611787
if you want info on how to flash it then read thru the relevant stickies
Finally understood and downloaded/flashed a new radio (2.08), after hours of reading and decrypting "nerd language" (no offence of course). We'll see if it helped tomorrow, if I have no probs tomorrow it *might* have been fixed!
TMOUS user here. Have had the HD2 for a total of 5 days. Making phone calls, it freezes repeatedly. I will receive a phone call(feel it vibrate, try to answer, and it just locks. Can still hit the Home button and hit HD2SoftReset, but this really sucks.
R:2.08.50.08?2
G 15.34.50.07U
D 2.10.82076 8G
Hopefully that's the radio info you need. It is a stock TMOUS rom. Installed a handful of Apps, and loaded up some music on my microSD card. Any suggestions?
Rooted my Hero and it doesn't matter which custom Rom I've tried(Fresh, Damage, others) my phone will shut off most of the time it goes into sleep. I don't know its off until I go to wake it up by hitting the end button. When I restore back to the stock Rom(still rooted) it works fine. I do a wipe and a Dalvick wipe prior to flashing. I'd like to get this figured out so I can use one of the nice Roms. Thanks.
If you're running A2SD and you have the Dalvisk on a slow sd card you phone can reboot or shut off. Try moving it off of the SD
patkin said:
Rooted my Hero and it doesn't matter which custom Rom I've tried(Fresh, Damage, others) my phone will shut off most of the time it goes into sleep. I don't know its off until I go to wake it up by hitting the end button. When I restore back to the stock Rom(still rooted) it works fine. I do a wipe and a Dalvick wipe prior to flashing. I'd like to get this figured out so I can use one of the nice Roms. Thanks.
Click to expand...
Click to collapse
WOW! You are the first person that has had the same problem I have...I was never able to resolve the issue. I used that bastard 2.1 test leak.......read my posts and what I went through.
http://forum.xda-developers.com/showthread.php?p=6268366#post6268366
My phone works fine now with gumbo 1.5, but I cant use any 2.1 roms or the problem comes back......
kyouko said:
If you're running A2SD and you have the Dalvisk on a slow sd card you phone can reboot or shut off. Try moving it off of the SD
Click to expand...
Click to collapse
I am not positive what A2SD is. I have a new 8MB SD card that came today. If I pop that in what will happen. Should it be partitioned? Thanks.
Chaid said:
WOW! You are the first person that has had the same problem I have...I was never able to resolve the issue. I used that bastard 2.1 test leak.......read my posts and what I went through.
http://forum.xda-developers.com/showthread.php?p=6268366#post6268366
My phone works fine now with gumbo 1.5, but I cant use any 2.1 roms or the problem comes back......
Click to expand...
Click to collapse
Thank God I thought I was the only one. I searched but didn't see your thread. Weird problem.
Same problem here too since the new leaked 2.1 test ruu from damaged. The only 2.1 Rom that works for my needs without rebooting every 3rd or 4th time I wake it using the end call/power button is Damagedtrev 2.01, the updated 2.05 Rom in his thread just makes my phone reboot as described above. I don't have a link to his thread, but it would be interesting to see if it worked on your phone too. Other's have claimed a battery shorting might be causing this issue, but I'm not buying that. I've looked at /proc/lastkmsg for clues, but nothing obvious there. I hope the official Sprint update doesn't have this bug or sprint will be giving me a new phone. /end rant
I can't seem to find Damagedtrev 2.01
So I can't test it.
Here's the link to the thread.
I cannot post links, because of some restrictions,but here is the last part of the url.
forum.xda-developers.com/showthread.php?t=653622
here's the link for the full rom
Oops cannot post link to rom on 4shared, look in the bottom of the first post in the thread for a link to the full rom of DamagedTrev_v201
Please let us know if the rebooting stops for you. Maybe one of the devs could find where the problem is. Pretty please!! I could post any info needed.
Ok, downloading......stay tuned.
I really hope this 2.1 ROM works.....I'm kinda sick of 1.5.
Edit:
P.S. I'm reading that there is a battery issue....do you have that?
kyouko said:
If you're running A2SD and you have the Dalvisk on a slow sd card you phone can reboot or shut off. Try moving it off of the SD
Click to expand...
Click to collapse
Hey good news. I put the new SD card in after backing up the other one, partitioned it and copied the files and folders back on then flashed ALOYSIUS and so far so good. I have woken it up about 10 times in a row. Looking good.
I had tried that perticular Rom before with no success.
Interesting.....I'm using the 2 gig sd card that came with the phone....I wonder if that is my problem?
Well it started again. This was right after setting my Gmail and POP3 mail accounts. It shut off on the first sleep after this. Hmmmmm.
I'm re-flashing now and not setting up the mail accounts. Will report back later.
Waldo447
Please let us know if the rebooting stops for you. Maybe one of the devs could find where the problem is. Pretty please!! I could post any info needed.
Well, my friend. You were correct! full rom of DamagedTrev_v201 works on our phones for some strange reason. And updating his ROM caused the re-booting to start again. So whatever was changed from 2.0.1 to 2.0.5 is causing our particular problem. I'm not a dev by any means and don't know much about his stuff, but this is encouraging. Perhaps someone can figure out what it is?
I did notice that ALL the other 2.1 ROM's I have used that cause my phone to re-boot from sleep mode, is that when I hit the menu or power button to turn it on, the lights turn on, then reboot phone. With DamagedTrev_v201 that doesn't happen. The screen just pops up to unlock it.....don't know if that helps, it's just something I noticed.
Heres to crossing our fingers that someone can fix this!
P.S. I wiped and went back to Gumbo 1.5c as that 2.1 ROM was way to slow for me and I couldn't get bluetooth to work and audio would cut in and out.
reboot
i would like to know if its a full reboot or just a soft like where it hes to the sprint or boot animation
kwajr said:
i would like to know if its a full reboot or just a soft like where it hes to the sprint or boot animation
Click to expand...
Click to collapse
It's a full reboot. The phone actually turns off when it goes into sleep. You don't know it's off until you hit the button to wake it up and the phone boots up.
Now for the good news. After re-flashing and not setting up the email accounts it was still shutting downconfused so I started looking elsewhere so I opened up what I thought was a likely culprit in Autokiller and none of the presets where selected so I picked Moderate and haven't had a shutdown since which has been over an hour. Fingers are crossed. I'll report back later.
That's it I've wasted way too much time on this. Phone works great on the stock ROM. They must have planted some devious anti-flash widget in this phone. I'll leave it rooted for now.
patkin, dude, I felt the same...I gave up on 2.1.
download, wipe then flash Gumbo-1.5c-BARE-signed.zip after it reboots, download and flash Gumbo-Sense-signed.zip.
You flash Gumbo-Sense-signed.zip over the Gumbo-1.5. No need to wipe or anything, it just adds to the ROM. Fast as hell and works PERFECT.
http://www.4shared.com/file/217809392/5fcf1f5d/Gumbo-15c-BARE-signed.html
http://www.4shared.com/file/217811195/3afb5fcf/Gumbo-Sense-signed.html
Give it a shot....I think you will like it......let me know =)
Gumbo thred so you can read up if you like. http://forum.xda-developers.com/showthread.php?t=630221
Chaid said:
Waldo447
Please let us know if the rebooting stops for you. Maybe one of the devs could find where the problem is. Pretty please!! I could post any info needed.
Well, my friend. You were correct! full rom of DamagedTrev_v201 works on our phones for some strange reason. And updating his ROM caused the re-booting to start again. So whatever was changed from 2.0.1 to 2.0.5 is causing our particular problem. I'm not a dev by any means and don't know much about his stuff, but this is encouraging. Perhaps someone can figure out what it is?
I did notice that ALL the other 2.1 ROM's I have used that cause my phone to re-boot from sleep mode, is that when I hit the menu or power button to turn it on, the lights turn on, then reboot phone. With DamagedTrev_v201 that doesn't happen. The screen just pops up to unlock it.....don't know if that helps, it's just something I noticed.
Heres to crossing our fingers that someone can fix this!
P.S. I wiped and went back to Gumbo 1.5c as that 2.1 ROM was way to slow for me and I couldn't get bluetooth to work and audio would cut in and out.
Click to expand...
Click to collapse
Glad to see your rebooting issue was fixed with this rom even though you went back to gumbo 1.5. In my mind, this just confirms that it is not a battery issue. I never use bluetooth and have never experienced any audio loss with this rom, but apparently even people on the same hardware and firmware versions have different problems.
kwajr said:
i would like to know if its a full reboot or just a soft like where it hes to the sprint or boot animation
Click to expand...
Click to collapse
Full Reboot here too.
patkin said:
That's it I've wasted way too much time on this. Phone works great on the stock ROM. They must have planted some devious anti-flash widget in this phone. I'll leave it rooted for now.
Click to expand...
Click to collapse
Yeah, got my phone beginning of march 2010 and I also think there is something in the 2.1 test ruu or hardware that is keeping the phone from functioning properly with an altered 2.1 rom.
Just wanted to let people know what happened to resolve this. I went back to 1.5 then when 2.1 official came out last week I said what the heck if I can't enjoy a rooted custom 2.1 I'll try the official and guess what. Same problem as the other 2.1's.........phone shuts off randomly! Except this time they are replacing it with a new phone. Yeaaah! I'm probably going Evo now though since I found out I can get a new phone. Anyone need a new Hero?
I'm having the same problem.. One question. Does DarchDroid automatically move dalvik-cache to the sd
EDIT: The problem is still occurring. I thought it was fixed.
Myself and a couple other people experienced stange 3g connection problems while running the cm7 nightlies (among other ROMs) with the new HBOOT-0.35.0017. I know it's been said that HBOOT shouldn't have anything to do with your data connection but nonetheless it is causing problems.
Follow the instructions on this thread to downgrade (AMOLED NEXUS OWNERS ONLY!):
http://forum.xda-developers.com/showthread.php?t=726258
After downgrading back to HBOOT 0.33.0012 my connection problems vanished (still running the same CM7 nightly)
Credit goes to user Prgopala for noticing this and posting here:
http://forum.xda-developers.com/showpost.php?p=10902092&postcount=12533
Thanks!
I'm sorry to tell you, but hboot has NOTHING to do with the radio part of the phone: it controls the system partitions table and boots the system... nothing else, it doesn't even touch the RAM parts dedicated to the hardware, the kernel does it.
I almost made up my mind to downgrade until seen the edit part. 3g part of signal is very very frustrating experience on my side while call part rarely let it down. Also signal always in close to100 reading while my Acer liquid on T Mobile stays to perfect 75-80 reading.
I'm on HBOOT-0.35.0017 and sometimes I get x gray bars but after it picks up signal and gets connect to H it seem to work fine. Until I lose the signal or I switch to airplane, etc. Takes a while sometimes to get back signal or the H.
I did notice that when the screen goes off my download stops or sometimes when I download certain files it stops right away. I been updating roms so not sure if it related to them, but overall its been like that.
Tiberx said:
I'm on HBOOT-0.35.0017 and sometimes I get x gray bars but after it picks up signal and gets connect to H it seem to work fine. Until I lose the signal or I switch to airplane, etc. Takes a while sometimes to get back signal or the H.
I did notice that when the screen goes off my download stops or sometimes when I download certain files it stops right away. I been updating roms so not sure if it related to them, but overall its been like that.
Click to expand...
Click to collapse
yes screen off downloading stopping is quite annoying...
I dunno but since I upgraded my Hboot and used CM7... my data sucks. It will work then not work. I typically have to reset to get it back. Even switching in and out of airplane mode will not work.
And by 3G I mean my data connection. I'll have full bars and 3G coverage... but no data from the browser, no pings, no online apps, nothing. Seems like the only way to fix it is to reset the phone.
I also noticed my signal is noticeably less at home. Typically I have full bars but now I notice that it's been dropping out and bouncing.
Could be a carrier issue. But I haven't upgraded my radio since 5.08 first came out. I updated my HBoot for the early builds of GB. So I'm willing to test out this theory.
lol, hboot has nothing to do with the phone's radio. The radio version does.
If you're having a problem with the radio (voice/data) then you should look at the radio version you're running.
Again, hboot has nothing to do with your issue.
Ive had the data sticking problem since I got my n1. Remember reading somewhere that if you go into settings - wireless networks - mobile networks - network operators, when it finishes searching select "automatically select". I got T-Mobile & it works for me until the next time I flash a new rom.
FYI when I was on CM 6.1 I had your problems. I then switched to MicroMod777's Gingerbread and those problems disappeared. I've now flashed Enmother's TheOfficial Nexus1 and I'm testing. Absolutely a ROM problem.
elegos said:
FYI when I was on CM 6.1 I had your problems. I then switched to MicroMod777's Gingerbread and those problems disappeared. I've now flashed Enmother's TheOfficial Nexus1 and I'm testing. Absolutely a ROM problem.
Click to expand...
Click to collapse
Kinda the opposite for me. No data issues when i tried CM 6.1.1 but on MM Gingerbread i had no data connection at all!
"You pays your money and you takes your chances"
then it must the crap of our carriers
DirkGently1 said:
Kinda the opposite for me. No data issues when i tried CM 6.1.1 but on MM Gingerbread i had no data connection at all!
"You pays your money and you takes your chances"
Click to expand...
Click to collapse
Same here. I tried MM and nothing worked! lol. So I went back to the latest CM7 (#24). I'm not sure what the problem is. Now I'm on an older HBoot and an older Radio. I shoulda just left 5.12 and .35 on there.
Once I get my phone pieced back together, I may try one of the older CM6.1 roms to see if that fixes it. I think we are all using Gingerbread roms here, no? Perhaps that just is an issue that comes with it.
youareme7 said:
EDIT: The problem is still occurring. I thought it was fixed.
Myself and a couple other people experienced stange 3g connection problems while running the cm7 nightlies (among other ROMs) with the new HBOOT-0.35.0017. I know it's been said that HBOOT shouldn't have anything to do with your data connection but nonetheless it is causing problems.
Follow the instructions on this thread to downgrade (AMOLED NEXUS OWNERS ONLY!):
http://forum.xda-developers.com/showthread.php?t=726258
After downgrading back to HBOOT 0.33.0012 my connection problems vanished (still running the same CM7 nightly)
Credit goes to user Prgopala for noticing this and posting here:
http://forum.xda-developers.com/showpost.php?p=10902092&postcount=12533
Thanks!
Click to expand...
Click to collapse
Same issue here, wondering if this hboot is incompatible w/ my old radio.
just received my new nightly, will give this method a try as soon as i upgraded.
thanks!
-- just saw the updated post, thanks anyway
Perhaps the OP should change the title and original message to exclude the HBoot details as the problem is with Data connection.
This will let us continue discussion about the data connection problem that we are, I am at least, experiencing.
Using CM7 #24 from 1/30, it seems to be less of an issue. I notice that I'll have 3G and full bars, but no data will work until it changes to an "H". Seems like it might just be the rom. The latest nightly seems to correct the issue better then before. Now if I open a browser, after 30s-1minute, it will start chugging along.
greetings. about a week ago, I noticed I was missing a lot of calls, and not receiving texts. I can call out and send texts, just cant receive anything. well today I had enough and took it to the sprint store. after 3 hours of them working on it, still nothing they went as far as trying my number on a different phone, and even that phone couldnt receive calls then. (never rings). lastly, they gave me a new phone number for my evo, and still cannot get calls. so, I along with them are super confused. is it my evo or the number that's bad? they ordered me a new phone to pick up on Tuesday, but I'm not convinced it'll work. anybody have any idea what on earth could be wrong? I'm running pure stock. oh yeah, Google voice doesn't work either for getting calls, but it can receive texts. wife's phone on our account works just fine. so weird. thanks guys.
Derek
data over 3g and WiFi is working perfectly.
It's network related. They better pay this months bill for you. Call Sprint and find out.
Sent from my PC36100 using XDA App
I've had a similar problem lately of not getting calls. I'm not missing all of them, but at least once or twice a day, all of a sudden I'll get a nerw Voice Mail, yet the phone never rang. And, I've had people tell me that when they call, it goes straight to Voice Mail
I just attributed it to having WiFi only on, although that is just a longshot guess on my part.
Ive been unable to receive texts girl 3 days now. Anybody find a fix?
Sent from my PC36100 using XDA Premium App
what rom? if it's calkulin's evio 1.8, there's your problem.
Cm7 final
Sent from my PC36100 using XDA Premium App
dkdude36 said:
what rom? if it's calkulin's evio 1.8, there's your problem.
Click to expand...
Click to collapse
what's wrong with that Rom? damn, now that I think about it, I ran that Rom and realize my problems started that day. is there a reason why that Rom caused my no calls/texts issue.
dschoenike said:
what's wrong with that Rom? damn, now that I think about it, I ran that Rom and realize my problems started that day. is there a reason why that Rom caused my no calls/texts issue.
Click to expand...
Click to collapse
yea. when calkulin upgraded from 1.77 (great rom) to 1.8, he added a bunch of ## codes directly in the menu. but somehow the defaults were messed up. i had this problem too. it affects any rom you flash after. just full wipe and reflash calkulin's, then get your msl from msl reader, and go to the dialer. then type ##data# and select edit. make sure mode of operation is on auto. then, DO NOT OPEN SETTINGS. just power off phone, and flash something else (maybe even calkulin's 1.7.7.)
dkdude36 said:
yea. when calkulin upgraded from 1.77 (great rom) to 1.8, he added a bunch of ## codes directly in the menu. but somehow the defaults were messed up. i had this problem too. it affects any rom you flash after. just full wipe and reflash calkulin's, then get your msl from msl reader, and go to the dialer. then type ##data# and select edit. make sure mode of operation is on auto. then, DO NOT OPEN SETTINGS. just power off phone, and flash something else (maybe even calkulin's 1.7.7.)
Click to expand...
Click to collapse
thank you for that. sorry if this is a stupid question, but will getting a new phone solve my problem? thanks
derek
dschoenike said:
thank you for that. sorry if this is a stupid question, but will getting a new phone solve my problem? thanks
derek
Click to expand...
Click to collapse
i have no idea. i'd try this first, and if it doesn't work, a sprint tech might be able to fix it.
dkdude36 said:
i have no idea. i'd try this first, and if it doesn't work, a sprint tech might be able to fix it.
Click to expand...
Click to collapse
wish i woulda asked you guys earlier i unrooted, went back to stock, spent 4 hours in a sprint store, now have a different evo coming in from sprint on tuesday. guess ill try what you said tomorrow before doing the exchange. cant today as im not home. thank you again for all that info. really appreciate it.
derek
@OP
the problem isn't with your phone, it's with your account. i ran into this a few times while i worked for Sprint, and there for all the issues that came up, the only fix was to delete the account from the network in its entirety and start from scratch. sometimes there's just some corrupted code that no level of tech support knows how to do anything with that just needs to be re-written.
i'm surprised that they ordered you a new phone even though using a different device didn't work. i think it was just a move to make you feel like they're doing something for you tbh. make sure that your line is comp'ed until the problem is resolved. you could probably get your whole bill paid, but you're more likely to get half of it (i'm assuming you only have two lines) covered. my recommendation is don't get greedy, just ask for your half.
goodluck!
JoshuaD80 said:
@OP
the problem isn't with your phone, it's with your account. i ran into this a few times while i worked for Sprint, and there for all the issues that came up, the only fix was to delete the account from the network in its entirety and start from scratch. sometimes there's just some corrupted code that no level of tech support knows how to do anything with that just needs to be re-written.
i'm surprised that they ordered you a new phone even though using a different device didn't work. i think it was just a move to make you feel like they're doing something for you tbh. make sure that your line is comp'ed until the problem is resolved. you could probably get your whole bill paid, but you're more likely to get half of it (i'm assuming you only have two lines) covered. my recommendation is don't get greedy, just ask for your half.
goodluck!
Click to expand...
Click to collapse
thanks for the info. yeah, only two lines on our account. I'm not gonna be greedy seeing as I'm the one who caused the problem (flashed the rom) I just want a working phone now I'm real curious to how long that's gonna take. I'm mean if its my account, a new phone won't solve the issue right? could take Sprint awhile to figure this all out. grrrr. and its all my fault.
dschoenike said:
thanks for the info. yeah, only two lines on our account. I'm not gonna be greedy seeing as I'm the one who caused the problem (flashed the rom) I just want a working phone now I'm real curious to how long that's gonna take. I'm mean if its my account, a new phone won't solve the issue right? could take Sprint awhile to figure this all out. grrrr. and its all my fault.
Click to expand...
Click to collapse
i'm not convinced it's your fault at all. sometimes funky things happen in the back end on sprint's side.
best of luck to you!
don't think this is a rom specific issue, it's most likely the network.
I'm having the same problem on savage-zen rom rc2...
What may help is updating your radios, prl, etc. I haven't done that in a while, not too sure that it will make a significant difference though.
dschoenike said:
greetings. about a week ago, I noticed I was missing a lot of calls, and not receiving texts. I can call out and send texts, just cant receive anything. well today I had enough and took it to the sprint store. after 3 hours of them working on it, still nothing they went as far as trying my number on a different phone, and even that phone couldnt receive calls then. (never rings). lastly, they gave me a new phone number for my evo, and still cannot get calls. so, I along with them are super confused. is it my evo or the number that's bad? they ordered me a new phone to pick up on Tuesday, but I'm not convinced it'll work. anybody have any idea what on earth could be wrong? I'm running pure stock. oh yeah, Google voice doesn't work either for getting calls, but it can receive texts. wife's phone on our account works just fine. so weird. thanks guys.
Derek
data over 3g and WiFi is working perfectly.
Click to expand...
Click to collapse
I had the same problem running Evio 1.8. I tried a number of things (including different ROMS) but what seems to have fixed it was to reflash the radio. I reflashed the PRI 1.77_003 from this thread http://forum.xda-developers.com/showthread.php?t=715485&highlight=radios and my phone has worked fine ever since. Once you're in recovery (amon or clockwork) flash the zip (PRI 1.77_003) and reboot. It will flash the radio and reboot. It might solve your problem.
nucher said:
I had the same problem running Evio 1.8. I tried a number of things (including different ROMS) but what seems to have fixed it was to reflash the radio. I reflashed the PRI 1.77_003 from this thread http://forum.xda-developers.com/showthread.php?t=715485&highlight=radios and my phone has worked fine ever since. Once you're in recovery (amon or clockwork) flash the zip (PRI 1.77_003) and reboot. It will flash the radio and reboot. It might solve your problem.
Click to expand...
Click to collapse
just letting you know, the pri is different than the radio, and we are talking about evio 1.8 starting problems like this for many, including me.
nucher said:
I had the same problem running Evio 1.8. I tried a number of things (including different ROMS) but what seems to have fixed it was to reflash the radio. I reflashed the PRI 1.77_003 from this thread http://forum.xda-developers.com/showthread.php?t=715485&highlight=radios and my phone has worked fine ever since. Once you're in recovery (amon or clockwork) flash the zip (PRI 1.77_003) and reboot. It will flash the radio and reboot. It might solve your problem.
Click to expand...
Click to collapse
so do u think its worth rooting again, and trying all that, or wait till I get the different evo and see how that goes? to be honest, I didn't want a different phone. I really liked this one and do you think them giving me a new number affects any of these trouble-shooting efforts? thanks.
Derek
dschoenike said:
so do u think its worth rooting again, and trying all that, or wait till I get the different evo and see how that goes? to be honest, I didn't want a different phone. I really liked this one and do you think them giving me a new number affects any of these trouble-shooting efforts? thanks.
Derek
Click to expand...
Click to collapse
If you have the time I would try my suggestion and or dkdude36 suggestion. He is correct in that the PRi is not the radio. I was in a hurry to type out the message. But I do mean the PRI, and I use the 1.77. You'll have to root the phone again, and nan-unlock. Then install a ROM and a recovery. If it doesn't work you'll have to restore it to stock before you return the phone so it will take some time to do all that. I was running Evio 1.8 for a while then one day I couldn't receive calls. I tried many things but the PRI fixed my phone. It's really up to you and how much time you have.
calkulin's evio 1.8
dkdude36 i think is right, i had the same problem a month ago, had to call *2 for help.
want ah guess what rom i was running....evio 1.8!
now i'm on Eternal Prophecy 5.8 got to read the hole thread, zero bugs!
hey everybody I'm not sure if i am putting this in the right section, but here goes. I am currently on deployment with the army in Djibouti Africa, but i still use my hero a lot (obviously just over wifi). i have come up with a strange problem regarding the screen when the phone gets warm the screen becomes unresponsive, when i go into hboot it tests out as failed. Am i just hosed and need a new screen or does anyone have any ideas about a fix. again I am in Djibouti Africa and as such repair tools and materials are severely limited. '
thanks in advance.
Might want to add what rom,recovery,kernel and extra mods your running firerats or data2ext. Also if your s-off and if so what method and what radio/baseband and prl are you on. And what service provider are you with. Also what are have your tried to fix the issue and what are you doing when the phone gets warm and the screen becomes unresponsive. Also if you have access to adb or not. This info will help members assist you in solving your issue.
#Root/Hack-Mod_Always*
hmm let me see i nandroided between about 10 different rom/ kernal variations yesterday seeing if that was the problem, none of it helped. right now i left it on cyaqnogen 7.0 RC2 with the cyanogen kernal. radio version 2.42.02.10.29 my recovery is the latest clockwork and as for s off i really dont remember. i have had this phone since it was very first introduced so i cant remember if that is something ive done or not.
it could be overheating maybe i know when im out biking and my screen gets sweat on it itll become unresponsive for a minute or so but after i wipe it down its good.
Are you running an overclock app???
#Root/Hack-Mod_Always*