I flashed 4.0b3 a few days ago and gave it a shot, but I am having a few issues still. I have opted to go back to 3.5 until the brightness bug and other issues are fixed, but I am having a problem reverting back.
I cleaned the dalvik cache, and when I try to flash back to 3.5, I reboot after install is complete, I get as far as the fresh screen and from there it proceeds to boot loop. I am not entirely sure how to handle this.
Flashing roms is still a relatively new process for me so I apologize for the newb question in advance. Any help would be appreciated.
*EDIT* Please ignore this. I ended up reformatting and doing a clean backup instead.
Related
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?
My problem is that I can't seem to flash certain ROMs they just hang on the HTC splash screen on the initial boot. I can use reflextsense 1.8, but I can't run robocik or insertcoins roms. I did have robocik's last rom on there , didn't like the rotation so I tried to move over to insertcoins and that's when the problem started.
I downgraded to a stock rom, then tried again, no joy. Any ideas?
completely formate your card mate then do full wipe and try again i have had this in the past and it was a memory card error
I will give it a go and keep you posted, thanks.
That worked, thanks.
So I am having a really strange problem recently with my phone, was wondering if I should unroot and return it or if it is something I am doing wrong. Basically what it boils down to is if I power my phone off from the menu or pull the battery, etc. upon powering back up it just Hangs on the HTC Evo 4G white splash screen indefinitely. I have let it sit as long as 15 mins without booting before, having seen this before in the past I know not to panic now but I just reboot into Recovery and wipe my cache and dalvik cache every time I reboot and my phone reboots back into sense in no time at all.
I know this is not normal, is there something I can do to troubleshoot this problem or is this is a sign of hardware failure?
ernbrdn said:
So I am having a really strange problem recently with my phone, was wondering if I should unroot and return it or if it is something I am doing wrong. Basically what it boils down to is if I power my phone off from the menu or pull the battery, etc. upon powering back up it just Hangs on the HTC Evo 4G white splash screen indefinitely. I have let it sit as long as 15 mins without booting before, having seen this before in the past I know not to panic now but I just reboot into Recovery and wipe my cache and dalvik cache every time I reboot and my phone reboots back into sense in no time at all.
I know this is not normal, is there something I can do to troubleshoot this problem or is this is a sign of hardware failure?
Click to expand...
Click to collapse
I've never seen that before. Interesting. What rom are you currently using? Do you have an unusually large amount of apps installed? The first thing I would do, is make a nandroid backup of your current setup, and then do a full wipe and flash a format all.zip, then reflash a different rom. Or just simply restore a nandroid of a known good setup, and see if the problem persists. If it stops, I'd say it was something specific to the rom/kernel/setup that you were running before. If it continues happening on a clean install of a different rom, then I'd probably unroot, restore to stock, and then see if the problem continues. If it does, take it to Sprint. If it stops, and everything is fine, re root it and start over. That's just what I would do, but I've never been presented with an issue such as that.
I appreciate the advice, I'm running Sprint Lovers right now been running it for a few months now, I don't have an unusual amount of apps installed but I did notice that the problem seemed to start occuring when I changed the Kernel. I will try your advice and see if that fixes the problem. I've been wanting an excuse to try the new Gingersense rom anyways.
ernbrdn said:
I appreciate the advice, I'm running Sprint Lovers right now been running it for a few months now, I don't have an unusual amount of apps installed but I did notice that the problem seemed to start occuring when I changed the Kernel. I will try your advice and see if that fixes the problem. I've been wanting an excuse to try the new Gingersense rom anyways.
Click to expand...
Click to collapse
If it started happening right after you swapped out the kernel, that could be the culprit. If you want to try the gingersense rom, I'll all for it, and will tell ya that they ran super incredibly smooth for a factory rom. However, if you don't feel like changing roms just yet, maybe try a different kernel. I'd be suspect of that, if the problem started shortly after changing to a different kernel. I say try out a gingersense rom, you shouldn't be disappointed (unless your phone still hangs at the splash screen upon reboot, lol).
Having trouble with the latest LeeDroid HD ROM have flashed many LeeDroid roms before without issue but for some reason aftering clearing all caches and running the latest rom it will install ok but on reboot it just hangs on the White HTC screen and won't boot in.
Any Ideas what could be causing it?
Currently Running LeeDroid HD v3.0.1, LeeDroid Kernel v3.1.1 radio 12.54.60.25_26.09.04.11_M2
Make sure you're deleting all data do a full factory reset (deletes all data does not actually restore to factory condition) then clear the dalvik cache, re apply the ROM make sure its CLEAN and you haven't modified it, don't apply any themes or anything, then let it boot and be patient.
Try downloading it again also it could be a corrupt download.
m3t4lh34d said:
Having trouble with the latest LeeDroid HD ROM have flashed many LeeDroid roms before without issue but for some reason aftering clearing all caches and running the latest rom it will install ok but on reboot it just hangs on the White HTC screen and won't boot in.
Any Ideas what could be causing it?
Currently Running LeeDroid HD v3.0.1, LeeDroid Kernel v3.1.1 radio 12.54.60.25_26.09.04.11_M2
Click to expand...
Click to collapse
I had similar issue few days back. But i had the Leedroid rom (same rom,kernel as urs) already runing flawlessly for a few days. It decided just to hangs at the same HTC Screen... tried to clear caches(all), hard reset, reflash same rom... still stuck same place. I finally had to flash stock 1.32 image, root all over again, etc. ... and flash Leedroid (same) again... works fine now
I got the feeling that I made my friends with their stock DHD and Iphone users drooling and jealous of my phone(csutomised with sense 3.0 stuffs), and they collectively jinxed my phone, and had this crash! lolz
btw. i flashed SAME rom i had on my sdcard, so I think the rom fine(mine at least). just something triggered that crash!
all the best...
Yea i tried reflashing from stock rom the other day loaded up one of the RUU exe's and rerooted etc and tried to reflash with no luck so i'm all out of ideas
raidenxl said:
Make sure you're deleting all data do a full factory reset (deletes all data does not actually restore to factory condition) then clear the dalvik cache, re apply the ROM make sure its CLEAN and you haven't modified it, don't apply any themes or anything, then let it boot and be patient.
Try downloading it again also it could be a corrupt download.
Click to expand...
Click to collapse
Have also done factory reset and cleared dalvik cache etc. no joy
Just managed to find a copy of LeeDroid HD V3.0.2 have installed and found it also crashes but.... it gets to the LeeDroid Android screen, little further but unfortunately still crashes
Managed to get 3.0.3 working on my DHD turns out it was just down the cwm version i had, updated to 3.0.2.5 and boom worked first time =D only problem i have had with both 3.0.1 and 3.0.3 is the camera keeps dropping out, app doesn't force close but the screen keeps going black and all buttons dissapear then all comes back... =( Atleast i'm up to date though
Any Idea's on the Cam issue?
have run logcat and noticed the following in the log
W/mm-camera( 1400): config_proc_CAMERA_STOP_SNAPSHOT: state is not correct ctrl->state = 25 W/mm-camera( 1400): VFE_RESET_ACK illegal ctrl->state 24
dunno if that makes any sense to anyone
tinkered with it a little last night didn't seem to make a difference so left it over night and for some odd reason works fine this morning i think the issue was down the camera app itself but it looks to be working fine now thankfully
UPDATE:
Ok looks like the issue is still there found out what is causing it thought, the camera works fine but...only when wifi is off, if you turn wifi back on you get the same issue as before,
Please anyone got an idea on wtf?
UPDATE2: have worked out it must be the camera app due to the fact i download a different app which appeared to work fine. Not sure why there's a glitch though
I need some assistance please. I have flashed several roms over the years and have never have had to post on here before about issues regarding my phone. I have always used the search engine to find my answers, but today I have came across an issue I can't resolve. I have just recently flashed SkyRaider 4.1 (did the full wipe, cleared cache and so on), but every time I try to log into Facebook for HTC Sense I get an error message. Warning! The service is currently unavailable! Do you want to try gain. Field Stream gives me the same message.
Any help or suggestions would be appreciated.
Phone Droid HTC Incredible
latest radio and H Boot
I am using Skyraider 4.1 also and facebook is working fine. Maybe you could try flashing the rom again.
Still no luck
Already tried that (twice)! I did a clean wipe before installing both times. Came from 4.0 and this is the first problem I have had.
Try fixing permissions? Worth a shot at least.