Develop Bugs

[Q] 3G Not Working after Downgrade?

Hey all, long time lurker, first time poster....unfortunately....
So after sitting on MIUI for a good while, and having a blast with it, I decided to try out some other ROMs. I was interested in seeing Cyanogen 6, and so I went about attempting to get the latest stable, non RC ROM onto my EVO. I read into it seeing that I needed to downgrade my hboot, and found the image without a problem (running the .76 right now, had the 9something one before...)
Well, I downgraded my hboot without an issue, flashed the Cyanogen, and got into a splashloop. I figured out it was becaue I hadn't wiped my cache or data before flashing the rom, so I went into the Clockwork Recovery and wiped those, flashed once more, and it booted into Cyanogen perfectly!
Well, almost. I don't have 3G now.
For some reason, I am unable to connect to 3G no matter what I try. My nandroid's broke due to the hboot downgrading, rewiping the cache/data and reflashing cyanogen did nothing, and now for some reason, when I attempt to go back to MIUI, it still will not allow me to connect to 3G. I can send and receive texts, and make and receive calls, but alas, no data connection.
Should I get a fresh RUU and stock hboot, upgrade and restart from scratch? I just want to get back to MIUI at this point with a working, data enabled phone.....
If that's the case, that I do need to start over, where can I find a new hboot for the EVO that isn't .76? I'm pretty saavy when it comes to this stuff, but for some reason right now I just can't figure it out....
HTC EVO running MIUI v0.11 stable
.76 hboot w/ Clockwork recovery
Broken nand backup
whatdo?
Thanks in advance for the help

Sorry for the double post, but I resolved my issue.
I am unsure of what exactly went wrong, but I figured it was somewhere between downgrading my hboot, and flashing the CM 6 stable ROM that my 3G data got scrambled....
So! Using ROM Manager, I made a backup of my working (non 3G) MIUI image, and flashed the Odyxed version of the RUU found here (http://forum.xda-developers.com/showthread.php?t=836728). After flashing in Recovery, it booted into SenseUI, and worked like a charm!
My 3G hath returned, and issues have been solved. It's nice when you're able to fix things on your own, though I couldn't have done it without the help of that handy dandy search button, and the RUU keyword
Oh, yeah, and I guess xxbabiboi228xx as well.....maybe....^_~

[Q] Help please!! anyone.

Trying to install Vaelpak 3.0 and I am having 1 hell of a time. I'm thinking it has something to do with my radio wimax pri nv ect.... because earlier in the week I tried flashing the combo and everything went to hell on my phone. I since then had to flash back to the previous radio and then had vp 2.3 running fine again. After that I learned that it was kernel specific problems with older HTC kernels so I flashed netarchy's and then went back to the radio combo and had this problem with my CPU load at 100% and always running at near 1ghz. Then I learned if your rom is not based on the 3.3 that the newest PRL with continue to overload your CPU the entire time. I hadn't gotten this problem really fixed by the time I found VP 3.0 and figured flashing this would just fix my problem with the newest PRI because its based on the 3.3 update.
After a full wipe (data, 2x cache, 2x dalvik) I flashed 3.0 only to get stuck in a white screen boot loop. So I DLed the file from another link moved it manually to my SD and flashed that... same problem. Then I decided I would restore my 2.3 through RA install rom manager and change my recovery over to clockwork to try to install the rom. No go. Then I flashed a previous version of 2.1 used rom manager to put RA back on (I've found this more reliable but at this point who the hell knows). Went into recovery and restored my backup made as of this friday. Still having the problems with the CPU load so I went back to recovery and flashed the older radio combo but noticed this doesn't have NV on it(not sure what NV is either). But all seemed to be working fine for moment until 2.3 started randomly restarting on me. So now my 2.3 isn't working and can't get 3.0 to flash.
Next thing I thought to do was to wipe all again flash 3.0 and then flash netarchy's kernel over the htc #15. BAM!! I get it to run through the boot into the set up menu asking for my gmail account. I enter my account info and wait, wait, wait, then it says cannot get reliable connection to google servers (also I notice that my data instead of a 3g icon says EvDo). Well now this can't be good. I try to turn on my wifi it says that wifi cannot perform search. I enter my network manually cannot find network. I've tried updated profile pri and everything else from settings and always get same error with communications saying call sprint(don't wanna do this will immediately void my warranty I'm thinking). Now the last thing left for me to check is if I can get 2.3 up again and check my wifi ect... through that.
Wipe, Wipe, Wipe, flash older radio combo, flash previous NV that wasn't in combo as far as I could tell, restore 2.3. All seems to be going well until I try my wifi. Cannot search again. WTF?? then instantly black screen to no where. Pull battery try again, get into the settings and then black screen back to Vaelpak boot animation. I am completely lost here I could really use some help. Like I said in the beginning I have a sneaking suspicion it has something to do with the radios combo ect... but can't figure it out on my own.

Well in case this has happened to anyone else and it is likely to happen somewhere down the road from people upgrading to roms based of the 3.7 update. The quickest fix I found was.
1. DL Unrevoked Forever from web page and flash it
2. Find a stock ruu for the 3.7 or do what I did and just DL Sprint Lovers PC36IMG.zip place in root of SD card and boot into hboot. Install the ruu.
3. Go to settings>software updates and update the PRI and the Profile
4. Remove the PC36IMG.zip from root of your SD card
5.(only applicable if you used the stock ruu) take your recovery of choice name it PC36IMG.zip and place in root of SD card. Boot into HBoot and install
then remove that from root as well.
6. Flash the Rom you were wanting to flash. This will take care of all Radio, Wimax, PRI, NV, and other problems between 3.7 based roms, Kernels and Radios.
Hopes this helps someone along the way.

[Q] Weird problem installing custom ROMs

I've rooted my phone for the first time the other day and started venturing into the custom ROM's realm, but so far all I got were dramas and failures.
I started by downloading Cyanogen 6.1.1 and 7 RC1. I thought I'll try each to see how they perform. So I copied them to the sd-card, along with the radio update that was recommended on the Cyanogen 7 RC1 thread, and rebooted to Clockswork recovery. I wiped my data and cache and went on with the ROM installation followed by the radio update (notice that I skipped the backup stage. stupid, I know).
Upon booting, I immediately noticed that I have no signal, and a force close message that says: "the process com.android.phone has stopped unexpectedly. Please try again" pops up every 2 seconds. Nothing happens when the message is dismissed, mind you, but it still comes up constantly every couple of seconds. This, along with the 'no signal' thing, rendered the phone unusable.
At this point I'm thinking that maybe my phone is just not reacting well to the non-final build of the Cyanogen 7, so I gave the stable Cyanogen 6.1.1 a go. Lo and behold, same thing happens with it also. Now panic kicks in when I realize that I have no backup, and no stock ROM to go back to.
Eventually, I downloaded the latest rooted Desire 2.2 ROM, got it into my sd-card and installed it. Thankfully, everything was working properly again. After some asking around in the Cyanogen forum, it got to my attention that the update to the radio might have caused all of this trouble, and that the installation of the stock ROM brought the previous radio version with it, which solved the problem. But when I tried to install Cyanogen again, without tinkering with the radio, same thing happened. I then tried Oxygen 2, thinking that maybe my device just doesn't like Cyanogen, but the exact same problem persisted.
Anyone have any idea what's the deal here?

Did you wipe dalvik cache after flashing the roms?
Sent from my HTC Desire using Tapatalk

I wiped the cache partition before I flashed. It didn't say 'dalvik' specificaly, just 'cache partition'. I never wiped any type of cache *after* the flashing process.

You should wipe the dalvik cache after (or just before) flashing roms.
You can find it under the advanced menu in clockworkmod recovery.
Sent from my HTC Desire using Tapatalk

Alright, tried wiping the Dalvik Cache after flashing, problem still persists.

You could try downloading another radio and trying it. Even if it's not the recommended one, an older radio works better for some people. There is no such thing as 'the best radio to use', since result may have large variations for different people (in different locations, using different phones and ROMs). Just browse the radios post and pick one
Btw, since the dalvik cache is stored at /data/dalvik-cache, wiping the /data partition implies deleting the dalvik cache

Well, since the radio that I have installed now works, and since it stays the same one after installing a different ROM, it seems to me that the radio is not the problem here. I really would like to stay away from tinkering with the radio stuff...

Bump.
This really bugs me that it wont work. I feel like I'm missing out on the biggest feature of having a rooted phone...

Hmm... I've found that if I force the phone into Airplane mode, the FC messages stop. Of course, I still have no signal.
So, the reason for the FC messages is due to the failure to connect to my mobile network. Now, why would I be able to connect to my network fine on the official Desire ROM, but not on any other ROM?

If all else fails you could always trying flashing the RUU for your phone then start from the beginning and root again if you've tried everything else.
Sent from my HTC Desire using XDA App

Ok, I'll try that.
Just a quick question. After I run the RUU and the device is unrooted, will I be able to recover my nandroid backup fully after I re-root?

The process com.android.phone has stopped unexpectedly

So I've seen other people that have this problem but the difference is usually they get the message when opening this or that, while I get the message constantly. As is, if I force close it, it pops right back up again leaving me no time to actually do anything on my phone.
Any help would be appreciated, I have CM7 installed and this just happened after a reboot.

Did you flash the latest gapps when you flashed CM7?

Yeah, and CM7 had been working great up till this point. Now it says I have no service and I can't do much of anything.

TheUnknowing said:
Yeah, and CM7 had been working great up till this point. Now it says I have no service and I can't do much of anything.
Click to expand...
Click to collapse
Did you flash anything without wiping data? if you did you might have to wipe data. Before you do that try to fix permissions in rom manager and clear the data for the phone app. If those things dont work wipe data. If a data wipe doesnt work you have a problem with the ROM you flashed. If its a nightly you should either flash a different nightly or flash the stable.
As for the service you can try to flash a new radio. If that doesnt work i recommend going back to a sense rom updating your profile, and then your PRL. I wouldnt imagine the radio is the problem, because ROM's shouldnt normally include radio files, but you might as well try to flash the newest radio anyways. Newest radio is 2.15.00.11.19.
flashing a new radio, updating your prl, and updating your profile are about the only things you can do to help your service. updating prl and profile can only be done on sense roms through settings, because those involve sprint code, which is not made public.

Update: I'm not sure how to do most of the things you mentioned but my radio is up to date. I discovered that this problem only occurs after I reboot the phone. It flashes fine, works normally, but once I reboot it the problem starts up.

[Q] Rooted Inc2 Keeps rebooting

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.