i am having trouble with my video cam not working so did a full wipe and restore. flashed rom gapps kernel ok. radio cant write no space left on device?
By chance, are you using a custom HBOOT with a reduced CACHE partition?
thanks- yes i just changed hboot to oxygen r2 alpharev. i suspected this might have something too do with it. so, what is happening?
ok so i went to flash it through android flasher but it is already on there so thats good. but still im getting still camera working and video force closing as soon as i switch to it.
It says "Sorry. the application Camera(process com.andoid.camera) has stopped unexpectedly"
maybe try another rom, some have Problems with camera. Has it worked and just stopped without you changing things?
Are you sure your Rom fits at this Hboot ?
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.
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
Hi There, I'll try and keep this short, this is regarding my brothers Desire HD:
he's running MIUI 1.7.8 - no problems. Ril 2.2.0018G, Radio 12.54.60.25U_26.09.04.11_M2
We thought we'd try a new ROM, did the usual, wiped data, dalvik cache etc etc. installed Cyanogen 7.0.3 through CWM
He prefers this new ROM. set everything up, then discovered a strange problem, an active call is dropped when the proximity sensor turns the screen off. I looked this problem up (someone else experienced it and did a "fastboot oem eraseconfig" I tried this and it said successful but didnt cure the problem...
I tried to flash the RIL 2.2.0018G in CWM (It said it flashed successful, but when i booted into the ROM, it still had the old RIL installed with the ROM not the new one i just flashed.
One other thing, the Radio that I had was: 12.54.60.25U_26.09.04.11_M2, something strange, the U changed to P after i installed Cyanogen7 ???
I used Nandroid to restore MIUI and the P changed back to a U, the RIL was obviously changed to the one that came with the MIUI ROM and all is now working again.
Q1, Why couldn't i flash a new RIL under Cyanogen (was i doing it wrong - just a normal flash through CWM?)
Q2, Why did the U change to a P in the radio name when i installed Cyanogen?
Q3, Any ideas to the cause of the dropped calls (if not answered in Q1 or Q2)?
I tried, but it still turned into a longer post. sorry.
thanks for your help.
Kevin
I'm not an expert, but I believe RILs can only be flashed in the recovery console. I know I flashed mine there and it worked. No idea why the letter changed
RILs can be safely flashed in CWM, with minimal harm. But do make sure that md5 provided by the dev is matching with yours. If the RIL is restored after rebooting, maybe the RIL is tied with the stock radio. Plus, RIL does not has any effect in AOSP rom.
The radio prefix can change due to rom/radio own setting and region. Read this http://forum.xda-developers.com/showthread.php?t=1068874
Reason of dropped call may caused by dialer that flagged as open application and would kill itself if its clashed with screen off command. Try to reflash/change kernel.
Sent from my HTC Desire HD using XDA App
to use cmd with the phone in fastboot mode you need the "fastboot.exe" file, also you need to make sure the cmd directory points in the correct path. Could be why you didn't actually flash anything.
I have decided to move from my An-droid to MildWild Oxy 4.0. Install freezes at firstboot (white HTC screen stays for 40 min).
I have rooted desire gsm, Oxygen r2 hboot (6.93.1002), wiped everything, formatted SDcard to 512 128 (swap), it's S-OFF
What am I doing wrong?
edit: I was supposed to use data+ hboot, not oxygen r2
Regards,
itchi
Camera problem
I'm writing here because I still don't have permission of writing in Development subforum (I must wrote 10 posts). So if anyone can contact the developers on this issue.
I have problem with camera on Mildwild V-4.0 Based on Oxygen 2.3.2
When I shoot first image, it's ok, but when i go to shoot second image, phone freeze on autofocusing and reboot after about 10 seconds. I looking for solution on forum but not help.
I did check disk memory card, formate fat32 and ext4 particons and flash rom again like as first time. And it's no changes, again is the same problem.
I put the MIUI Camera and it is identical problem.
When I dismounted and re-mount the memory card, I can again shot a single picture, and at the second shot come "before using the camera, insert SD card"
I've never had this problem on other roms.
I test many roms, and this seems fastes and I would like to stay on this rom, but the camera was very important and necessary to me.
How to solve this problem?
Mine works
Mine camera works on my desire on this ROM. Maybe it's a permissions thing that causes this loop?
Btw, I have solved my problem
itchi77 said:
Mine camera works on my desire on this ROM. Maybe it's a permissions thing that causes this loop?
Btw, I have solved my problem
Click to expand...
Click to collapse
And hot to solve problem with this permissions? I actually noticed that I can't write or change anything on the memory card, like as it is locked. I can only read from it.
How to change that?
Camera problem also
My camera doesn't work at all! It used to work like a charm but now it just says Application Camera ICS is not responding