Related
HW version 0003
Myns release 4
3.30.651.3
HTC Kernel 17
Washington DC area
for some odd reason i have no data. no 3g, 4g, only wifi. updated profile and prl. Did the ##data# reset in edit mode with the PRL. Shut off and let sit without battry for a while.
Any ideas?
changed kernel to netarchy 4.1.9.1 cfs and put the new radio and wimax radio on...same thing
munsterrr said:
changed kernel to netarchy 4.1.9.1 cfs and put the new radio and wimax radio on...same thing
Click to expand...
Click to collapse
flash a stock rom.
munsterrr said:
changed kernel to netarchy 4.1.9.1 cfs and put the new radio and wimax radio on...same thing
Click to expand...
Click to collapse
Don't resort to flashing radios you can really screw up your 4g.....Did you try factory reseting your phone but back everything up first and see if that works if not try flashing a stock rom or a ruu.
Update Profile/PRL. If that doesn't work, flash a stock RUU and Update Profile/PRL. If that doesn't work do a ##786# reset. That should get you up and running.
If you still have problems post back and I will point you in the right direction to fixing your data profiles.
I also have the same problem using myn rls4, but have net 4.2.1 cfs HAVS more kernal. Out of nowhere the data will just cut out and stop working. I will try some of the suggestions in the thread.
Did any of out suggestions work for you?
h2o-pr00f said:
I also have the same problem using myn rls4, but have net 4.2.1 cfs HAVS more kernal. Out of nowhere the data will just cut out and stop working. I will try some of the suggestions in the thread.
Click to expand...
Click to collapse
well i went back to CM 6.1(newest build) and about 45 minutes ago it happened again while i was at the bar. guess imma go to a non rooted RUU to see what happens
not to be "that" guy but one bump for a hopefully permanent fix.
As much as half of us have a rom flashing addiction. I cannot do this every day lol.
munsterrr said:
well i went back to CM 6.1(newest build) and about 45 minutes ago it happened again while i was at the bar. guess imma go to a non rooted RUU to see what happens
Click to expand...
Click to collapse
If that doesn't work. Call sprint and tell them your phone is having really slow data and it's going in and out tell them it happened after updating your phone through system update then they will say it's due to software update and they will send you a replacement next day.That is my suggestion because you don't want to screw something up that might be noticeable trying to fix your current evo just get a new one and start over with everything updated. I hope I was helpful
I did this, using the debug menu once. I reset all data and then it wouldn't update my profile so I couldn't access my 3G and the web data was gone. I tried to update my profile/prl and it wouldn't, kept timing out.
Every time I would reboot the handset it would try to update automatically but fail. It turns out the rooted rom I was on, (Fresh EVO) was interfering with the update. I flashed the stock RUU...then the phone attempted the same update profile, and afterwards it was back to normal.
So try going back to a stock rom, and then if it doesn't automatically try to update your profile, go to your settings and do so manually, should do the trick.
Basically do what APH noted in his post...sorry must have skipped your posting.
This same thing happened to me on the Hero. I RUU'd back to Sprint's crap and then called them. They walked me through some things and then told me to take it in. The repair guy did the same thing I did (RUU and then data fix) and it started working. So, if all else fails, RUU and bring it back to the store.
thank goodness i have a long weekend. Guess if the new PRL update doesnt fix this then ill head over.
hi all, been following the Epic forums for sometime, finally decided to start getting involved
Im experiencing an issue with EB13. when it first came out I Odined EB13, everything worked great. Since then I have ran into the same issue every time I switch ROMS. I will flash the new rom, about half the time it works great. The other half I get no connectivity at all, and the UI is sluggish. Going into about phone, I see that my baseband is unknown, and my hardware version is unknown.
I can usually get it to connect after re-flashing and re-flashing the rom a few times.
Also, noticed that once I get it to actually connect and I get "bars", I will of course then do a fresh Nandroid, after a full nand backup the issue reappears.
Anyone know what this could be? weird thing is just that its so random. I can get it to work most of the time, just have trouble when switching roms.
Set up:
CWM3.0.0.6/EXT4
Just flashed SyndicateROM today.
EB13 (sometimes)
FIXED
FIXED. all the computers in my home are Macs so odining the modem again is not a quick fix option.
Booted into CWM3 and Fixed Permissions.
Booted up and connected.
Interesting stuff
I've been experiencing the exact same problem as the OP, but for me, running fix permissions in CWM (2.5.1.0) doesn't (always) solve the issue.
It seems to happen anytime I flash a zip from CWM, and goes away randomly (usually after sever flash attempts and modem restores with Odin).
Really hoping someone has an idea what's causing this issue, because it makes flashing things very tedious knowing half the time I'm gonna be stuck with a useless phone until I can get the modem working again.
I'm wondering if it's somehow a hardware issue, since it doesn't seem to affect everybody.
If it helps, I have the stock deodexed EB13 ROM with the Genocide 0.3a kernel.
I'm definately thinking its a cwm issue.. ill even just do a nandroid backup for kicks, reboot and it will do it sometimes.. eventually I might odin back to eb13 and reflash cwm and custom rom and see if I can get it to go away
Sent from my SPH-D700 using XDA App
DrKaotica said:
I'm definately thinking its a cwm issue.. ill even just do a nandroid backup for kicks, reboot and it will do it sometimes.. eventually I might odin back to eb13 and reflash cwm and custom rom and see if I can get it to go away
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Let me know if that works for you, because it happens to me all the time, and it's really annoying.
There also doesn't seem to be a simple way of fixing it.
Seems to just randomly go away as suddenly as it comes on.
Okay, so I just odined back to stock EB13 and I still have modem issues.
Currently going all the way back to DI18 to see if that fixes things, but is it safe to assume it's a hardware issue if even Odin doesn't fix it?
Okay, so the unknown baseband issue is back for me, and I seem to have made some headway on what causes it.
I had just tried to initiate a ROM backup in ROM Manager, but it hung while rebooting into CWM (on the Samsung Boot Logo).
I think I might have been doing something with ROM Manager last time it happened as well.
Can anyone who knows more about this stuff than I do think of a reason it'd happen when using ROM Manager?
I'd very much like to nip this issue for good, because it's making it hard to justify using CWM/root if I'm gonna keep losing the phone part of my phone.
Can I bump this? My battery died, and when I turned it back on, I have the unknown baseband, unknown hardware problem. I've been googling all night, and haven't found a solution.
I have been running ERA Legendary v3 on the EI22 Modem for a few weeks with ACS Recovery that I've had installed since it came out.
Any help would be awesome.
---------- Post added at 07:28 AM ---------- Previous post was at 07:17 AM ----------
And I've tried flashing modems/roms and odining modems/roms. Even Heimdalling modems/roms. No luck. I've mainly tried ec05 and up. I will try older ones right now, if I can find them.
So my wife's Inc2 has been rooted for a few weeks and I installed a 2.3 Sense ROM for her shortly thereafter.
All of the sudden, her phone keeps rebooting and then "freezes" on a screen that has the Exclamation Point inside a triangle with a little green droid character under it. (My wife put a fresh battery in, it boots up into the ROM for about 10 seconds, then says "Powering off: Shutting down..." and goes into the error screen.)
So far, I have tried the following:
Turned airplane mode on.
Booted into safe mode.
Booted into CW Recovery, backed up, then re-flashed the ROM.
Ran a restore from a backup from a couple of weeks ago, which was pre-custom ROM.
Flashed the 2.3 Radio
Flashed a new Kernel
No matter what, I always get it to boot for a split-second and then it boots into Exclamation Point error.
Anyone think of what is causing this to do this after running for two weeks + in the current condition with no issues? What does this mysterious screen mean that it boots into? Any fix I can run via HBoot, Fastboot or Recovery?
WorldOfJohnboy said:
So my wife's Inc2 has been rooted for a few weeks and I installed a 2.3 Sense ROM for her shortly thereafter.
Click to expand...
Click to collapse
Bumping, no one seems to be able to tell me a thing on what this means, what can be done to fix, etc. Any help is appreciated.
Wipe cache, dalvik, and system, then flash a different ROM.
If it continues after that then its likely the phone. And nothing to do with root.
WorldOfJohnboy said:
So my wife's Inc2 has been rooted for a few weeks and I installed a 2.3 Sense ROM for her shortly thereafter.
All of the sudden, her phone keeps rebooting and then "freezes" on a screen that has the Exclamation Point inside a triangle with a little green droid character under it. (My wife put a fresh battery in, it boots up into the ROM for about 10 seconds, then says "Powering off: Shutting down..." and goes into the error screen.)
So far, I have tried the following:
Turned airplane mode on.
Booted into safe mode.
Booted into CW Recovery, backed up, then re-flashed the ROM.
Ran a restore from a backup from a couple of weeks ago, which was pre-custom ROM.
Flashed the 2.3 Radio
Flashed a new Kernel
No matter what, I always get it to boot for a split-second and then it boots into Exclamation Point error.
Anyone think of what is causing this to do this after running for two weeks + in the current condition with no issues? What does this mysterious screen mean that it boots into? Any fix I can run via HBoot, Fastboot or Recovery?
Click to expand...
Click to collapse
Any chance you can take a picture of said screen?
What's weird, it sounds like you're describing the stock recovery screen. But you're still able to access CWM?
You probably want to update CWM on the phone and see if that helps out, one thing you want to do instead of changing kernels is re flash the rom again. Once it reflashes wipe data/cache (Do a factory reset basically) as well as the dalvik cache and boot into the ROM without restoring anything.
Just sign into google and see if it stays up and stable at this point, if it does something that's being restored is probably the culprit or a bad app that continuously tries to run.
By the way, the phone comes with stock sense 2.1, above that is sense 3.0
2.3 is the version of android that runs behind sense. Either 2.3.3/2.3.4/2.3.5 are all versions of gingerbread.
Try a different rom, if it continues, it's probably a hardware problem. My wife's first Incredible rebooted constantly, probably upwards of 2 dozen times a day. We had it replaced and the new one has been fine.
Update: I restored a backup of a previous CWR backup back in July. Shortly after I booted into the restored ROM (it was Stock rooted), it automatically tried to download the OTA software update.
Anyone think that perhaps the phone is automatically DLing the OTA and then rebooting and failing upon doing so? That is the only thing I can come up with at this point. (Though, back when this first started happening, I was on a GB ROM with Sense 3.0, so I wouldn't think the OTA would try to push over that ROM.)
I thought I read some where that other INC2 users were having similiar issues and it was due to the new android market OTA update.
Edit: Nevermind the other thread here in the forum suggests it could be some kind of HTC OTA update that is messing things up.
WorldOfJohnboy said:
Update: I restored a backup of a previous CWR backup back in July. Shortly after I booted into the restored ROM (it was Stock rooted), it automatically tried to download the OTA software update.
Anyone think that perhaps the phone is automatically DLing the OTA and then rebooting and failing upon doing so? That is the only thing I can come up with at this point. (Though, back when this first started happening, I was on a GB ROM with Sense 3.0, so I wouldn't think the OTA would try to push over that ROM.)
Click to expand...
Click to collapse
Weird. OTAs are usually disabled. Did you wipe dalvik/cache and flash a new rom?
klarson said:
Weird. OTAs are usually disabled. Did you wipe dalvik/cache and flash a new rom?
Click to expand...
Click to collapse
I am in the process now, but I have had a GB/Sense 3.0 ROM as well as stock GB Rooted, both have ended up doing the same thing. I think I am going to manually cancel the OTA after flashing a new ROM to see if that will stop it from automatically doing so (if that is the issue).
Pretty sure its the market new market push. I had the same issue, I set the phone to airplane, shut it down before the automated shutdown to retain the airplane mode, then cleared dalvik cache and system cache, and then rebooted. I got some BS message about a failed OTA because no network was detected, told it to cancel, dl'ed the new market APK installed it, not an issue since.
Conduitz said:
Pretty sure its the market new market push. I had the same issue, I set the phone to airplane, shut it down before the automated shutdown to retain the airplane mode, then cleared dalvik cache and system cache, and then rebooted. I got some BS message about a failed OTA because no network was detected, told it to cancel, dl'ed the new market APK installed it, not an issue since.
Click to expand...
Click to collapse
It's not the new market. It has something to do with the OTA's on your phone. Regardless if the OTA was actually downloaded onto your phone or not it's going to fail because the stock recovery is no longer the default recovery which is one of the prerequisites it needs to install.
A wipe is needed to keep this from happening, at least load up the gingersense ROM and that should get rid of the temp OTA file that was downloaded to your phone.
jrizk07: I would agree with you, but this will be the 3rd time I have wiped the phone, the 2nd time loading a Gingerbread based ROM.
I wiped all items twice, and flashed this ROM: [ROM] RMK Gingerbread Sense r1 :: 2.18.605.3 (Rooted/Deodexed/Debloated)
Will let you know the results.
WorldOfJohnboy said:
jrizk07: I would agree with you, but this will be the 3rd time I have wiped the phone, the 2nd time loading a Gingerbread based ROM.
I wiped all items twice, and flashed this ROM: [ROM] RMK Gingerbread Sense r1 :: 2.18.605.3 (Rooted/Deodexed/Debloated)
Will let you know the results.
Click to expand...
Click to collapse
What i'm hoping is that the OTA files are on the phone and will get wiped with a new ROM. However if they're stored on the SD card all the wiping in the world won't help.
I'm not sure where the OTA files are stored and would like someone to verify for certain if that's the case. I'm just speculating right now on where it's stored but I know the market update is done just like the apps not an OTA.
I also know that the OTA will prompt you for the download. You know the whole download and install now or install later deal?
Well, did a wipe of all things (twice) and installed my fresh ROM. This time after installing all my Apps and doing my restores, etc, I went into the Settings under Software Update and did a check new, it says "No New Software Update Available." Also, under status, it just says the Source is Verizon Wireless, the rest are blank. (I believe at one time, all the fields were populated.)
I am holding out hope that this will work for us. Anyone know of a piece of software, etc. that will log all of the phone's operations? I am curious to see if it is trying to auto-update with OTA software updates.
I'm having the same problem. I can't even get it to wipe because when I start in recovery it goes straight to do you want to start update and if I try to start the phone it restarts and I get the exclamation point. Anyone have any ideas? Thanks!
Update
I took the sd card out and was able to boot to recovery and do a wipe. Phone is working normally for now, how would I go about disabling the OTA's so it doesn't happen again?
I can confirm this is being caused by an ota update. Have 2 inc 2's and both locked up. Both running rmk gingersense. Fixed by clearing cache and davlik. Rebooted phone and saw failed ota update error. Renamed otacerts.zip until rom is fixed. Otacerts is located in /system/etc/security.
After successfully installing Alpha 1 and 2 with no problems, Alpha 3 will not let me connect to the Sprint network. On boot up the phone is in airplane mode, and when switched off, it still will not give me any signal. Any help would be greatly appreciated as this is my only phone. Lol. Also, the lock screen sometimes takes ages to light up?
Also, if no one knows how to fix this, can someone point me in the right direction to flashing back to a completely stock rom?
Stock rom.
http://forum.xda-developers.com/showthread.php?t=1433101
GO back to el26/29 and fresh install
Odin to EL26, update Profile and PRL, and then come back. It may also help to switch around your Modem.
Same thing just happened to me.
I just went and updated my profile and it started working again. Not recommending doing anything but it worked for me.
I tried to back up with the tar option within clockworkmod, but the phone reboots during the back up process. Anyone else seeing this?
I nandroided a backup set as well. The one I performed yesterday actually reads with a time/date of 0:00:00 on 1/1/0000 and is unusable; phone resets when attempting the restore. A backup made on 8/24 is fine.
So could just be something w/ the rom, or with the rom + JB. Which JB are you running?
I'm on PhantomPhreak53's latest alpha (4.4). I didn't have issues with any of the previous versions. It was strange I tried creating a backup yesterday (8/28) it created a folder that was dated (8/29).
Hmm, odd.. the date on my restore was really odd in that it showed 0000. It actually did give me a partial image, but not complete.
I don't recall which build I'm on, version shows 20-20120822 unofficial d 710.
Will be nice when this is complete and great and not having a) the airplane mode issue, b) volume / voicemail issue, and c) horrid battery life. Yeah yeah, I know roms aren't necessarily responsible for battery life, but I figure if its sitting doing nothing for an hour, it shouldn't drop 15% of my battery.
I just tried backing it and rebooted while backing up data. The folder has the right date now (2012-08-29.19.40.57), but still incomplete.
I just want to back up, restore my GB room to update prl and profile. I just updated my modem to FH23, hoping it'll cure my slow 4G speed. right now 4G is benching slower than 3G.
Hmm, this may be a lame work around, but try this.
install AppBak, create a 'backup' of your apps (it's just a list of them with an easy way to reinstall one by one)
remove everything you can that is a regular installed app, then try running your nandroid backup.
I ended up flashing 4.3 and create a backup successfully. I updated prl/profile then restored back 4.3. Then updated to 4.4. I didn't make any difference in my 4G speed though.
Good it worked out.
I'm still working on trying to figure out how to restore back to an CM with ICS, so I can triangleaway and update to JB again. Ugh.
They posted that this is a known issue with the backup/restore through recovery best bet is to mobile Odin back to el26 do a backup then Odin restore the stock kernel for cm10 then restart should work
Sent from my SPH-D710 using Tapatalk 2