Related
I recently rooted my incredible 2 successfully and got CM7 on with no problem. I was trying to install a new splash screen, but accidentally installed my existing radio (1.09.01.0722) instead. Now I can't get any wireless signal or dial *228. I've tried different radios, but none of them work now. Any ideas?
thanks
You're able to still use the phone, but you don't get any data or anything?
Sent from my ADR6350 using xda premium
It's not bricked if you can turn in on.....
Did you remove the radio file after you flashed?
Had same issue on build 109 I placed a call and it fixed it. Yes placed a call with no 3g or 1x and no baseband showing in software. 3g then showed up and baseband updated.
Sent from my Incredible 2 HD using XDA App
kubes069 said:
It's not bricked if you can turn in on.....
Did you remove the radio file after you flashed?
Click to expand...
Click to collapse
Ya that's what I was thinking too. Didn't make sense to me about what he was saying.
Sent from my ADR6350 using xda premium
Try reflashing your original stock ROM and everything... Do the Ruu if nothing else works.. you'll lose root, but your phone will most likely work again... Then if you really want to, reroot.
Sent from my ADR6350 using xda premium
faehsemc said:
reflash...stock ROM, RUU if nothing else works.. etc. etc.
Click to expand...
Click to collapse
This is what I was about to say. seems like your only option and hope it fixes it.
I always thought that the flashing your Radio twice thing was just a rumor cause I can never find any answer as to why this would brick your device.
guess it doesn't care it just does!
Hope you can get an insurance replacement being rooted. Verizon wouldn't even cover my week old battery that was bad from the factory and wouldnt take a complete charge because the VZW dip behind the counter noticed the custom boot screen and started asking questions. guess I should have hidden my mods!
I really wish you guys would look up the definition of "brick" if you don't understand what a BRICK is. please refer:
Bricked
Bricked refers to ANY hardware that is unable to start up due to bad software; Usually because of a bad software flash, a modification done improperly, loss of necessary files, being overheated from overclocking or overuse if the item is a lemon, a short-circuiting, or a Trojan that deletes necessary files for a few examples.
The noob bricked his PSP because he took out the battery while running a firmware update.
andybones said:
I really wish you guys would look up the definition of "brick" if you don't understand what a BRICK is. please refer:
Bricked
Bricked refers to ANY hardware that is unable to start up due to bad software; Usually because of a bad software flash, a modification done improperly, loss of necessary files, being overheated from overclocking or overuse if the item is a lemon, a short-circuiting, or a Trojan that deletes necessary files for a few examples.
The noob bricked his PSP because he took out the battery while running a firmware update.
Click to expand...
Click to collapse
^ this
Sent from my Incredible 2 using Tapatalk
Thanks for all the help. I tried switching to a different rom and that worked. I'm afraid to go back to CM7, but MIUI works just fine, so I'm sticking with it.
morenone said:
Thanks for all the help. I tried switching to a different rom and that worked. I'm afraid to go back to CM7, but MIUI works just fine, so I'm sticking with it.
Click to expand...
Click to collapse
No reason to be afraid... Do a full wipe and everything.. will he just fine.. and my real advice.. stay away from radios...
Sent from my ADR6350 using xda premium
has anyone experienced the clock changing itself by going ahead an hour or two by itself. it's done that to me twice since i update to ei22, and have no idea how to fix it. it's annoying.
Works fine for me. You can go to settings, date and time, and set the time manually. I use automatic and it works fine.
Send from my SPH-D700 (Samsung Epic 4G)
What were you running prior to updating to ei22?
Sent from my SPH-D700 using xda premium
mrwireless1 said:
has anyone experienced the clock changing itself by going ahead an hour or two by itself. it's done that to me twice since i update to ei22, and have no idea how to fix it. it's annoying.
Click to expand...
Click to collapse
dont have that prob either. i was on ei22 stock system dump. then flash deodex ei 22 over it and update modem to ei22.
Sent from my SPH-D700 using Tapatalk
Clock issue from Sprint Towers
I have had this issue on and off, so it is not just you. I had it on EC05 all the way to EI22. My wife has it as well on her unmodded, unrooted, completely 100% bone factory Nexus S (in case anyone thought is was from modifications).
I think the issue comes from the Sprint towers, specifically WiMax. I only have the issue after I have been using 4g. I have not played with my wife's phone enough to test it, but called Sprint and they said something like "you aren't the first to complain, we are looking into it". The did ask me if my phone was at all modified.
I think it has a lot to do with where you are as well. I am right on the edge of a timezone (between CST and EST) and sometimes my phone hits the EST tower. If I pull the time from the tower I have this problem intermittently.
Good luck.
are u goin in and out of roam? if so might be changing something around possibly
no, i don't go in and out of roam. and i odin back to eh17, and i haven't had the problem with clock since i went back to eh17. so it has something to do with ei22. now can i use eh17 rom and flash or odin another modem? is that possible? or will there be any complications? the modem is the kernel right? (sorry, still a noob in the learning process)
by the way, i do appreciate everyones help. thankyou very much.
Modem and kernel are different beasts. Not sure if you can Odin the EH17 modem after you upgrade to EI22 and new ROM. I did run EC05 on an EF02 ROM, and EF02 modem on an EC05 ROM.
Sent from......well I would rather not say
Well if they are not compatible, what exactly would happen? Cuz the eh17 modem sucks
Sent from my SPH-D700 using xda premium
Eh17 modem I noticed has a lot of lag.
Sent from my SPH-D700 using xda premium
My phone all of a sudden stopped ringing when I got calls, text, etc.... noticed it while trying to watch a video...no sound. Then one day it rang for an IM. So I knw now the speaker isn't busted like I originally thought. Its worked fine until now. Anybody have any input? Feel free 2 pm me
Sent from my SPH-D700 using XDA
Must be something in the water. Had same thing. Try plugging in a wired headset while watching a youtube, then unplug. This worked for me for 2 hours then nada. Reflashed rom and even reformated to mtd but no difference. Something is hosed in nvram. Replaced unit under tep as I also had cracked screen so didn't get too much into.
Sent from my CleanGB/MTD Epic
I believe I still have the cm9 file on my sd. Wouldn't I need to reflash my kernel? To my knowledge handles the sound etc.
Sent from my SPH-D700 using XDA
Or maybe flash shadow 4 again.
Sent from my SPH-D700 using XDA
None of that worked for me. If you figure it out, please post a solution cause there are quite a few threads on the issue.
Sent from my CleanGB/MTD Epic
Odin back to stock EL30 and see if you still have issue. If you do it is a hardware issue. that is what happened to my wife. The repair center fixed it for free because I have the insurance.
Edit:
all files can be found here:
http://forum.xda-developers.com/showthread.php?t=1052813
What all will that do? I assume I will loose root and cm9?
Sent from my SPH-D700 using XDA
It assures that you do not have corrupted data. Yes you will have to root and then flash CM9. Do not restore anything. See if your issue is gone, then load apps and set up your phone.
Sent from my PantechP4100 using xda premium
My phone was rooted remotely. I used to have odin on an sd card. I know I would understand it if I seen it done. Originally I just wanted root on stock rom and kernel but he asked me if I wanted gb or ics so naturally I wanted 2 try out ics. He set it up with shadow 4 kernel then I flashed shadow 5 on my own. I dnt understand y it would work fine for like a month or 2 then nothing.
Sent from my SPH-D700 using XDA
debage39 said:
My phone was rooted remotely. I used to have odin on an sd card. I know I would understand it if I seen it done. Originally I just wanted root on stock rom and kernel but he asked me if I wanted gb or ics so naturally I wanted 2 try out ics. He set it up with shadow 4 kernel then I flashed shadow 5 on my own. I dnt understand y it would work fine for like a month or 2 then nothing.
Sent from my SPH-D700 using XDA
Click to expand...
Click to collapse
Lulz =] I'm sorry.. you should have asked me to help ya out... add me on gtalk [email protected] if you ever need anything. Or PM me.
THE most ironic thing is someone else I rooted I suggested the shadow kernel for has had this same issue.... he even flashed back wiping data but to no avail tomorrow ill have to odin y'all back to stock and re root ya and give you the proper cm9's and kernels and you should be good to go if of course the speaker isn't out. =]
Sent from my SPH-D700 using xda premium
speaker still not working
I tried reflashing cm9 and shadow 5, then tried cm9 and included stock kernel alone with gapps, then tried shadow 6. no sound on all. but doesnt explain it working for a bit then going back out. idk
Mine works and I have always used shadow. Shadow has no speaker mods other than voodoo. Have you blown it with volume+?
Sent from my SPH-D700 using Tapatalk
You will have to Odin to get it working then reinstall everything without restoring data.
Sent from my PantechP4100 using xda premium
No I've never messed with the audio settings.
Sent from my SPH-D700 using XDA
Marcusant and kenny, is there a way of accessing any of the nvram settings for audio, like telling it to use speaker vs audio jack so these can be reset somehow? I recently went through similar situation. Plugged wired headset in and out while watching youtube. This made my speakers come alive again for short time so they weren't blown. I factory reset, flashed stock, all ota's, rooted and went mtd cleangb. None of this brought back speakers. Something was telling them not to come on. Got new device so moot point 4 me now...
Epic powered by CleanGB/MTD 1.1.2
Sounds more like it was the hardware jack itself that was bad and getting stuck on. Might have been junk in the jack.
Sent from my SPH-D700 using xda premium
Hey goron, ill b home all day if wanna try 2 tackle this problem with the speaker. I have faith. Lol let me knw if ur free anytime 2day. I would say email me. Ill probly get it faster. Thanx for all ur help!
Sent from my SPH-D700 using XDA
Big Goron said:
Lulz =] I'm sorry.. you should have asked me to help ya out... add me on gtalk [email protected] if you ever need anything. Or PM me.
THE most ironic thing is someone else I rooted I suggested the shadow kernel for has had this same issue.... he even flashed back wiping data but to no avail tomorrow ill have to odin y'all back to stock and re root ya and give you the proper cm9's and kernels and you should be good to go if of course the speaker isn't out. =]
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
Odin him back to stock to see if he still has the problem I suspect he will. My wife had this issue when on cm no custom kernel it was a hardware issue. I am not saying CM caused it **** happens and her hardware failed.
One way to tell if it is hardware is does it vibrate? If it doesn't vibrate then it is hardware if it does then it might be a setup issue.
Yea it vibrates. Phone sitting on the table with vibrate.....kinda like a ringtone right? Sad but true lol
Sent from my SPH-D700 using XDA
debage39 said:
Yea it vibrates. Phone sitting on the table with vibrate.....kinda like a ringtone right? Sad but true lol
Sent from my SPH-D700 using XDA
Click to expand...
Click to collapse
Then it might not be hardware. When my wife's speaker stopped working it wouldn't even vibrate. When I spoke with the person at Sprint that fixed it he said it is the same unit. Of course I am not sure if it did vibrate at first because the wife didn't tell me for like 3 weeks that it was happening.
Having trouble getting the camera to work thru stock app or any other for that matter. The rear and front camera stoppd working as well as the flash. No water damage or anything and I was on deodex stock EI22 then I just upgraded to FC07 cuz I was tired of the update notifications and I thought it would fix my cameras and flash but no such luck. Anyone know what the problem may be or how to fix it. Thanks
Sent from my SPH-D700 using XDA
iNv8r said:
Having trouble getting the camera to work thru stock app or any other for that matter. The rear and front camera stoppd working as well as the flash. No water damage or anything and I was on deodex stock EI22 then I just upgraded to FC07 cuz I was tired of the update notifications and I thought it would fix my cameras and flash but no such luck. Anyone know what the problem may be or how to fix it. Thanks
Sent from my SPH-D700 using XDA
Click to expand...
Click to collapse
Try to odin to stock fc09 and see if you still have the issue if you do then it is hardware issue. Go here to get stock FC09 and all instructions.
http://forum.xda-developers.com/showthread.php?t=1592994
Thanks Taz. I forgot to mention I am rooted fc09. And I used odin. I'm starting to think its hardware too but I didn't think BOTH cameras and the LED would all go out together. I was hoping someone else who was rooted would know a fix or know of some app that was known to conflict wit the camera operation. I'm tryin not to have to unroot and take it back to the store for repair.
Sent from my SPH-D700 using XDA
iNv8r said:
Thanks Taz. I forgot to mention I am rooted fc09. And I used odin. I'm starting to think its hardware too but I didn't think BOTH cameras and the LED would all go out together. I was hoping someone else who was rooted would know a fix or know of some app that was known to conflict wit the camera operation. I'm tryin not to have to unroot and take it back to the store for repair.
Sent from my SPH-D700 using XDA
Click to expand...
Click to collapse
If you odin to stock and it still happened its hardware... your going to have to bring it to sprint... you shouldn't techniically have to unroot because their policy states that if its hardware they still have to work on your phone... if its software they still have to also but they are supposed to bring you back to stock first... but better safe than sorry, unroot and bring it to sprint for repair... only way if it happened on stock unrooted also...
Am I the only one whom finds mostly all FF18 builds unresponsive at times? The touch keys don't work randomly... on the latest ota and the leak? Is this kernel related? I hope so.... I find myself constantly trying to find the right one buy no luck... this is perhaps a useless thread but I feel as if this ICS for phone is not even worth it at times
Sent from my SPH-D710 using Tapatalk 2
I get th. Touch key part as we.
Sent from my SPH-D710 using Tapatalk 2
Then use an aosp build
Sent from my SPH-D710 using xda app-developers app
cp320703 said:
Then use an aosp build
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
Or this
http://forum.xda-developers.com/showthread.php?t=1748208
"PROJECT:PLACEBO" - now up to you
Sent from my SPH-D710 using xda premium
pyrostic said:
I get th. Touch key part as we.
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
Yeah that just makes using any ICS ROM a turn off at the moment... hope source can fix this.
Sent from my SPH-D710 using Tapatalk 2
cp320703 said:
Then use an aosp build
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
I love AOSP, I'm just not going that route at the moment till kernel is tweaked and modified now that they have source. Plus not all of us like to run aosp.
Sent from my SPH-D710 using Tapatalk 2
Why is it that all of these types of things are always categorized as ICS issues when the majority of us dont suffer from often if at all...?
Just make a checklist of consistent variables....
You
Your phone
Your settings
An operaring system succesfully applied to most of the world made by top-notch developers then supplemented by equally great devs that just always happens to brake for you =p
PhAkEer said:
Why is it that all of these types of things are always categorized as ICS issues when the majority of us dont suffer from often if at all...?
Just make a checklist of consistent variables....
You
Your phone
Your settings
An operaring system succesfully applied to most of the world made by top-notch developers then supplemented by equally great devs that just always happens to brake for you =p
Click to expand...
Click to collapse
I've had this on both stock and AOSP. I know my way around rooms and completely wipe before every flash even. its been happening to me since the early FF** kernel based builds. Frankly I think Samsung could have worked longer on this but something tells me it was rushed at the end.
Sent from my SPH-D710 using Tapatalk 2
Was mostly just flippin $#!t
Ive just been lucky I guess.. Ive got a big lib folder I carry around with me...
Any little problem Ive gotten has been easily remedied, and Ive never once had the weird problems that some get no matter what.
Maybe because mine was assembled in the states? Idk...
I do know that Placebo, placebo you want.. Worst case the flash doesnt take and you have to flash a backuo...
Most likely youll say, "this is a stock kernel?!"
Lol
Sent from my SPH-D710 using xda premium
PhAkEer said:
Why is it that all of these types of things are always categorized as ICS issues when the majority of us dont suffer from often if at all...?
Just make a checklist of consistent variables....
You
Your phone
Your settings
An operaring system succesfully applied to most of the world made by top-notch developers then supplemented by equally great devs that just always happens to break for you =p
Click to expand...
Click to collapse
Fixed for ya.
Agree 100% though.
Sorry to say this but I'm running my super nova rom and haven't had any problems what so ever. Nothing looked what you're describing at all. Any chance the phone is having a hardware factory issue since so many others have experienced the same thing?
No its definitely an ICS issue on certain devices. As it doesn't happen on Gingerbread roms based at all. Ive noticed certain users complain about the issue, maybe its different hardware models? Ill wait a bit to see what the developers cook up.... I'll give your super Nova ROM a try.. once all that fails I'll go get a device exchange LOL
Sent from my SPH-D710 using Tapatalk 2
Febby said:
No its definitely an ICS issue on certain devices. As it doesn't happen on Gingerbread roms based at all. Ive noticed certain users complain about the issue, maybe its different hardware models? Ill wait a bit to see what the developers cook up.... I'll give your super Nova ROM a try.. once all that fails I'll go get a device exchange LOL
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
Lmfao.
When it fails, ill buy your broken phone for like 20 bucks, you say you flushed it so insurance covers it... Ill flash that same rom on your phone and have no issues =) everybody wins!
Sent from my SPH-D710 using xda premium
PhAkEer said:
Lmfao.
When it fails, ill buy your broken phone for like 20 bucks, you say you flushed it so insurance covers it... Ill flash that same rom on your phone and have no issues =) everybody wins!
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Who said anything about insurance? I'm very good friends with the store manager. He always performs a device exchange as long as it hasnt had water damage. And no, I'm pretty sure the issues I'm having are real as pressing the power button and having the unlock screen process done but captive buttons not work for 5 seconds or more, isn't a bad flash. Even on shubs one click to FF18.
Btw check list done.... settings are always left stock. Phone seems okay unless I can surgicly open it to check on internals lol... ! Yes I'm okay myself.other than my messed up fist from a drunk fist fight.
I've had the same issue with most ICS E4GT roms, and doubt it is anything user related. Don't pay attention to the trolls. I've fully wiped my phone and it made no difference. Hopefully someone can figure it out. It's pretty annoying having to turn the screen on a off twice to get the capacitive buttons working.
Febby said:
Who said anything about insurance? I'm very good friends with the store manager. He always performs a device exchange as long as it hasnt had water damage. And no, I'm pretty issue the issues I'm having are real as pressing the power button and having the unlock screen process done but captive buttons not work for 5 seconds or more, isn't a bad flash. Even on shubs one click to FF18.
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
The only thing I notice is a bit of lag. I didn't have this issue before but it isn't so horrendous that I wanna destroy it. Ill be switching to a rom after I find one with absolutely no bugs. Oh an can I flash ICS to ICS now?
Sent from my SPH-D710 using Tapatalk 2
proxy0 said:
The only thing I notice is a bit of lag. I didn't have this issue before but it isn't so horrendous that I wanna destroy it. Ill be switching to a rom after I find one with absolutely no bugs. Oh an can I flash ICS to ICS now?
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
No you still can't flash ics to ics the emmc bug is still present
Sent from my Epic Blazer ICS 3G Touch
riggs170 said:
No you still can't flash ics to ics the emmc bug is still present
Sent from my Epic Blazer ICS 3G Touch
Click to expand...
Click to collapse
You think they'll push an update to the phone to fix the issue?
Sent from my SPH-D710 using Tapatalk 2
phelixian said:
I've had the same issue with most ICS E4GT roms, and doubt it is anything user related. Don't pay attention to the trolls. I've fully wiped my phone and it made no difference. Hopefully someone can figure it out. It's pretty annoying having to turn the screen on a off twice to get the capacitive buttons working.
Click to expand...
Click to collapse
Thank you, glad I'm not the only one who has this issue. The screen on and off is so far the only solution to this so far...
proxy0 said:
Oh an can I flash ICS to ICS now?
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
You can if you use the latest agat kernel built from source but remember not all developers have built in the new safe kernel! So you would always have to odin the kernel if it isnt baked with the ROM.
For reference, here is the link to source built kernel.
http://forum.xda-developers.com/showthread.php?t=1767421
riggs170 said:
No you still can't flash ics to ics the emmc bug is still present
Sent from my Epic Blazer ICS 3G Touch
Click to expand...
Click to collapse
That's been fixed now that we have source for ICS.
Sent from my SPH-D710 using Tapatalk 2
Ok heres my input. I believe that its a combination of software and hardware. Remember response time of soft buttons depends on how stable the rom is and also whats running at the time they where pressed. Ok say like you have a few apps it the background running and you turn off your screen. Once the screen come on the buttons may take a second to come on because the screen has more of a priorty than the soft button. Its all in how you look at it. And with apps running it slows that process down greatly because a combination of the proccesor and ram being used. Remember not notice but our soft buttons have a back light and they are press sensitive. So with them working together plus all the other stuff i explained timing would be off. But think about it. Lol is it really a depressing ordeal lol. I actually witness it and continue on without even thinking about it. Sorry for rambling lol