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?
Related
I have an Evo (003 Hardware) and while switching ROMs, at least twice now, I've had trouble restoring some apps using Titanium Backup. The weird thing is, I'ts only some apps, that are having the restore problem, while others seem to be restored, but without their settings saved. (Google Listen is an example of the former, while AdwEX is of the later.
I've verified the backups themselves, and they come back without errors, I've also tried flashing different ROMs like Myn's new Warm Z, MIUI, and Koni's Elite II. Those have no trouble restoring. Seems the problem is confined to the nightlies, as I'd installed RC1 before without issues.
Anybody have an idea what's wrong?
When re-flashing the roms, try a clean install, and also flashing the latest gapps. Not flashing them has been seen lately to cause a few apps not restoring, or some just missing completely. Best to do it in 2 recovery sessions, backup, flash rom, reboot, flash gapps, reboot.
teh roxxorz said:
When re-flashing the roms, try a clean install, and also flashing the latest gapps. Not flashing them has been seen lately to cause a few apps not restoring, or some just missing completely. Best to do it in 2 recovery sessions, backup, flash rom, reboot, flash gapps, reboot.
Click to expand...
Click to collapse
I always do a fresh install. Wipe data, cache and Dalvik, plus flash Calkulin's Format All.
I haven't tried flashing ROM and gapps in different sessions, as that brought trouble pre-rc1, I'll try that now, though.
Well I practice the 2 recovery session as a standard, sometimes it works in 1 session, but when it doesn't the 2 session step bring me no problems; but let me know what happens.
turns out, that wasn't the problem. Two-session flashing didn't bring any issues, which I was glad to see (although it did switch the wallpaper, that's just weird). What did help was this post from the rc1 thread http://forum.xda-developers.com/showpost.php?p=11722822&postcount=1603, where this exact problem is described, but I happened to miss it while searching somehow. anyways, it finally restored the apps, but not their data. I guess that's better than nothing, but again, just plain annoying.
Ah I see. Well now backup the apps and data and you should be set now.
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.
Alright. My Inc is having some problems. Here are some facts
Bought on December 23, 2010
Rooted it somewhere in January
Ran CM6 till CM7 came out
Here's what's was going down after I flashed to CM7
Flash CM7
Every 15 minutes my google maps app will randomly crash. No matter what I'm doing a "GOOGLE MAPS HAS STOPPED RESPONDING" sign will appear.
Random reboots in the middle of doing nothing
Re-flashed to stock, then back to CM7 and everything seemed okay... until a few days ago
Suddenly while browsing the internet EVERYTHING CRASHES. EVERYTHING.
The browser, music, messaging, screenshot it, even google frameworks.
wtfman.jpg
reboot my phone, this occurs again after a few hours.
Next day it happens again. Now, my phone got stuck in a boot-loop
So I flash back to CM6. Now here's my phone's symptoms.
Home button won't work. It vibrates on press, but doesn't do anything.
Search button won't work
No lock screen will ever come up. Ever. It's set, but it never appears.
I cannot receive calls. People will call me, and it will immediately show up in my call log, but the answer screen simply doesn't show up.
What did I do wrong? How do I fix this?
Alternatively, how can I flash back to stock and make it look like I never rooted it? I believe I'm still within my warranty.
What hboot and radio are u on? I know if your not using a gingerbread radio with cm7 it likes to go all wonky at times. I would wipe everything try a fresh install of cm7 and flash a gingerbread radio as well.
Sent from my Droid Incredible
sounds like you didn't wipe everything correctly. Did you wipe cache, devcache (probably spelled that wrong), data, datadata? Also did you restore apps through TI backup or any other backup app?
jackbtha1 said:
What hboot and radio are u on? I know if your not using a gingerbread radio with cm7 it likes to go all wonky at times. I would wipe everything try a fresh install of cm7 and flash a gingerbread radio as well.
Sent from my Droid Incredible
Click to expand...
Click to collapse
hboot 0.92.0000
radio-2.15.00.07.28
POQbum said:
sounds like you didn't wipe everything correctly. Did you wipe cache, devcache (probably spelled that wrong), data, datadata? Also did you restore apps through TI backup or any other backup app?
Click to expand...
Click to collapse
I did not wipe errything the first few flashes. But my last flash I wiped my cache, data, etc.
Try flashing the 7.07 Gingerbread radio, get it here http://pvillecomp.com/?page_id=18 and see if that helps.
Are there any alternatives to that?
Try flashing another ROM and see what happens. Make sure you wipe cache, dalvik, format system, and boot. Nandroid before you attempt that. Give Joelz Prime Xl 3d a try.
Sent from my HTC Droid Incredible using XDA App
First update that old Froyo radio with the new stock not leaked and totally safe because Verizon officially released it radio that jackbtha1 suggested.
Second, boot into recovery and run "fix permissions." That option always helps me when my phone decides to FC everything. It has helped me so that I run it after every rom flash now
Everything has been fine until yesterday morning, when at work I realised my phone was rebooting every 3 or 4 minutes.
I hadn't changed anything, I hadn't flashed anything, I don't O/C my phone. I'm usins AOKP Milestone 3 with Immoysen Kernel.
I've tried -
Reflashing AOKP with no custom kernel
Wipe & flashing CM9 Kang
Wipe & flashing MCR
When I tried to make a Nandroid of MCR (as it seemed to be okay for an hour or so) it gave an error when it got to backing up the data partition. Could their be a corrupt bit of memory there?
Also, at one point I think it might have reset while in recovery, which makes me think it's hardware, not software.
Today I've tried -
locking and unlocking the bootloader
Android_Revolution_HD_Super_Wipe_Lite
Wipe and flash AOKP B23
Generally it seems to be better after a wipe and a fresh install, for a little while, but then seems to start rebooting again later.
I locked and unlocked again around an hour and a half ago and all seems good at the moment, but I thought I'd post still to see if anyone else has had this happen or see if anyone has ideas of how to de-bug it should it come back?
I had this problem after upgraded to 4.0.2. Fresh install did solved this somehow but last week it came back again when dial starts...
Tho it seems un-checked all options in location services would not reboot during or after the call
Hope this info could help u
Thanks. Well, 6 hours since I locked the bootloader and unlocked it again (to wipe everything, including the SD storage) and it's not rebooted once. Looks like it's fixed *touch wood*
I have random turn offs... dunno if it relates. Its a little unnerving...and annoying. No roots, no unlocks, just vanilla 4.0.2.
Sent from my Galaxy Nexus using XDA App
I have been searching throughout this forum and across many other websites to no avail before asking this.
For the last month, WiFi and Bluetooth has not been working on my Desire HD, and no matter what I do I cannot get them to work again - I have tried factory resets, many different roms, restoring my first nandroid backup (just after the phone had been rooted, still stock rom), replacing the bcm4329.ko driver with a couple of others, but no joy.
My logcat reports:
Code:
E/rmt_storage( 3308): rmt_storage wait even ioctl failed
I/WiFiHw ( 1465): wifi_load_driver end error 2
E/WiFiService( 1465): Failed to load Wi-Fi driver.
I desperately need help with this, it is becoming incredibly frustrating as I used to use WiFi a large amount on a daily basis - any help would be extremely useful!!
what rom are you currently running? have you done a full cache/dalvik/full wipe before installing and make sure u restore nothing before testing? what radio are you running? a corrupted radio img file is possible
also, what did you do RIGHT before you lost your wifi?
Darunion said:
what rom are you currently running? have you done a full cache/dalvik/full wipe before installing and make sure u restore nothing before testing? what radio are you running? a corrupted radio img file is possible
also, what did you do RIGHT before you lost your wifi?
Click to expand...
Click to collapse
I am currently on Android Revolution HD 7.0.3, but just before that I was on Playground ICS and before that SmartDroid, and the problem has occurred on all of them.
I haven't been restoring any backups at all, I always do a full wipe before installing a new rom and I have tried cache and dalvik cache wipes as well.
Currently the radio I am using is 12.62.60.27U_26.13.04.19_M but I have tried a couple! Do you have any suggestions of any particular radios, or anything else worth trying?
Thanks for the assistance!
sam_w said:
I am currently on Android Revolution HD 7.0.3, but just before that I was on Playground ICS and before that SmartDroid, and the problem has occurred on all of them.
I haven't been restoring any backups at all, I always do a full wipe before installing a new rom and I have tried cache and dalvik cache wipes as well.
Currently the radio I am using is 12.62.60.27U_26.13.04.19_M but I have tried a couple! Do you have any suggestions of any particular radios, or anything else worth trying?
Thanks for the assistance!
Click to expand...
Click to collapse
im at work currently so forgive my quick typed replies. Dumb idea, turn off your phone, remove the sd card and then boot up without it. Ive seen cases where the sd card has caused connectivity issues.
the radio i use is 12.56.60.25U_26.10.04.03_M
been using it a long time, not the greatest d/l speeds, but most reliable (yes we all know its case by case basis for radios)
other thing i would try, is check all you antenna connections. each door functions as an antenna for a different device on the desirehd.
if it is repeating this same error across the board, it becomes more possible its hardware.
Hmm, this is very bizarre:
Clearing the cache and dalvik cache seems to make the WiFi work for a while (it lasted for about 3 or 4 hours yesterday), but after a while it will go back to saying "WiFi error".
I have tried formatting my memory card, but it still goes back to not working again, so I am going to see what happens when I leave the card out entirely and then report back on my findings.
Thank you for all the suggestions, I just really want my WiFi working again permanently!