Hey guys!
Got a little problem here!
Here's the situation, I'm perfectly able to flash CM6.10 (? - The latest stable for Wildfire anyway), but I've had no luck when trying to flash CM7. Either, it gets stuck at the white HTC splash after flashing and rebooting, or it gets stuck at the CM splash screen. The arrow just stops moving around in circles and freezes!
Not completely sure what this could be, I clear everything before I flash CM7 so ... And I ofc admit that I'm no sort of expert in this area, as almost every single flash has been perfectly fine to me, so I thought that you guys could figure this one out .
Regards
Try flashing kernel v4.1 from the HCDR.Kernel thread from the Wildfire Android Development Zone. Since you say you have cleared everything as stated by the first post in CM7, guess I wont be going into that.
I actually tried that as a last resort before going to bed yesterday, and that solved the problem! So thanks anyway, you were right !
Later on I installed the Gapps for CM7, but then when i booted my phone, i got the "Low Memory"-warning that wants you to remove some apps, and all the apps started to crash all the time. Especially the browser, not entirely sure of what's causing all this!
Hi,
I had the same boot problem and 4.1 also fixed it for me. I've not had any low memory issues but I only really have the google applications... One problem I do have is that I don't seem to be able to pair with any Bluetooth devices, I just don't get long enough to type in the PIN!
Can't post a report on the dev thread as I'm new here...
Andy
PS Which 6.10 have you been using? Did you have any Bluetooth issues?
Related
hey guys, just wanted to ask if somebody has experienced something similar..
i had jacxhero running on my 32a without problems. tonight i had the phone on the charger, and in the morning it turns off everytime after the first splash screen. i can access the bootloader mode etc normally, just loaded cyans rom and it works. but...why this sudden inusability? i havent added any program or changed settings for the last 2 days or something...
I had the same problem but with a different ROM. It was the TIM ROM which can be found in the Sapphire Android Developement section here at Xda-Dev. I'm not quite sure if it's a nandroid backup or if it's an Update.zip, but as I had it installed it seemed to be the exact same ROM my device has been shipped with and it read the same numbers in the About-System dialog thingie and so on, it was like if it was the shipping ROM.
Always after about a day of usage or so it suddenly froze though, then the device reset itself and then endlessly looped at the bootscreen. Very annoying. It didnt happen with any other ROM since then...
Mineee..
That's weird..
But, you had any data connection?.. maybe it tried to update something!
Mine started rebooting after entering on suspend mode(not on the splash screen)! The program settings from the overclock just was pulled after I run out of battery (with the "forced" reboot) and started making conflict with the specs of the myhero rom.
Whats the developmental aspect of this thread??
None.........so please post in General.
Warning given.
seems like i got more problems since this "crash"
after reflashing to cyan after this startup error and then reflashing jacheroski 1.4, im able to load hero roms like jacheroski 1.4 on my magic and they work fine, but im not able anymore to load any roms without hero kernel it seems..
i tried with several roms like different versions (working before versions!!) of cyanmod, hofo,..they all loop at the last splash screen or stay black when it should come to the actual os(one step after the last splash).
am i "doomed" to stick to hero roms forever?^^
im using eng spl .2005...should i try to reflash something? or have you guys got any other ideas?
Hi all, i have been having a very bazaar problem lately...When my phone boots up i get a pop-up message indicating that the gapps process shutdown unexpectedly...and sometimes i may even get a acore crash too. Applications from the market do not download...when i select my download i will end up getting a gapps crash and then the supposed download just sits there saying "starting...". Google talk doesn't even open! It will just say that the process quit unexpectedly. Even after a fresh install with factory data reset all these problems will continue. The initial boot up screen/tutorial will even show a gapps crash. I have tried with 3 different versions of cyanogenmod all with the exact same problem..Each version i've tried with a2sd enabled and disabled, formatting the partition each time before a new install to ensure no data carry-over issues. I don't know what to do. To me it seems like it make be something on googles side...but i can't for the life of me figure out whats causing these wild problems. Help would be very much appreciated.
ANDROID Market problems
I've recently had the same problem with the market getting stuck on "starting download". I thought it was something I modified as I'm putting together a STARGATE theme of my own based on kron2's work with this site and the theme for "Open Home" for DWANG's newest ROM. What worked for me was going back 1 restore point at a time till I found one that didn't have the problem (NANDROID backup). I also had luck with flashing DWANG's original unmodified ROM 1.17.1. I had the same problem when I flashed 1.16 ..weird. Up till 2 days ago I didn't have any problems changing anything in it. Others have said that they tried opening G-Talk at the same time and some how going between the 2 the problem would right itself. If you find out anything definite about what the exact problem is let me know as I'm going to keep looking for the answer myself.
six6star said:
I've recently had the same problem with the market getting stuck on "starting download". I thought it was something I modified as I'm putting together a STARGATE theme of my own based on kron2's work with this site and the theme for "Open Home" for DWANG's newest ROM. What worked for me was going back 1 restore point at a time till I found one that didn't have the problem (NANDROID backup). I also had luck with flashing DWANG's original unmodified ROM 1.17.1. I had the same problem when I flashed 1.16 ..weird. Up till 2 days ago I didn't have any problems changing anything in it. Others have said that they tried opening G-Talk at the same time and some how going between the 2 the problem would right itself. If you find out anything definite about what the exact problem is let me know as I'm going to keep looking for the answer myself.
Click to expand...
Click to collapse
I have searched and it seems many people have the Market/Gtalk problem.
I have the same problem (with an Eclair 2.1 Cyanogenmod rom) and I've not been able to find a solution. Wiping the cache makes nothing.
Anyone knows how to solve it?
Huh. I had a problem with the market at first with cyan 5.0.8 . I went in the terminal and ran fix_permissions after su and haven't had any problems since. Might try that
Sent from my HTC Magic using XDA App
Hey all, been poking around the forums and trying out various WM and Android ROMS and they all seem to work beautifully, kudos to the devs.
I seem to be running into a bit of a problem though.
My phone is an MP6900 (Vogue 100) from Bell. And while the roms work great, the second my phone goes into standby mode (when not attached to my comp) the phone resets.
I have tried four different roms, two android and two WM and the problem persists.
Also hard resets, battery removal etc etc to no avail.
I also tried to roll back the radio as that got updated when I went to my stock rom previously.
And to boot I can't seem to flash back to the stock ROM anymore, while I was able to even just yesterday. I get Error 262, for whatever reason.
I was wondering if anyone else has run into this issue and could point me in the right direction.
And I did a search on the forum (pre-registration) but couldn't find anything, sorry if this has been brought up before.
Again, great work on all of the ROMs! I had no idea phones had come this far. (Sad to say but true lol)
JustinHTC said:
Hey all, been poking around the forums and trying out various WM and Android ROMS and they all seem to work beautifully, kudos to the devs.
I seem to be running into a bit of a problem though.
My phone is an MP6900 (Vogue 100) from Bell. And while the roms work great, the second my phone goes into standby mode (when not attached to my comp) the phone resets.
I have tried four different roms, two android and two WM and the problem persists.
Also hard resets, battery removal etc etc to no avail.
I also tried to roll back the radio as that got updated when I went to my stock rom previously.
And to boot I can't seem to flash back to the stock ROM anymore, while I was able to even just yesterday. I get Error 262, for whatever reason.
I was wondering if anyone else has run into this issue and could point me in the right direction.
And I did a search on the forum (pre-registration) but couldn't find anything, sorry if this has been brought up before.
Again, great work on all of the ROMs! I had no idea phones had come this far. (Sad to say but true lol)
Click to expand...
Click to collapse
Sounds like a dying battery to me.
It worked fine in the original Windows though so that's why I am a bit baffled.
what happens if you put your device in bootloader and try to flash to stock? Error 262 is a connection error. basically happens whenever some event interrupts the flashing process (a dead battery will cause this). If you haven't yet, try to flash to stock via the method in this post (bootloader and then flash)
Tried that, didn't work. Just gets to 31% and pops 262 no matter how I try to do it.
The odd thing is though that I can flash any other ROM just fine.
Would reformatting the SD card work?
Figured it out. I used the 0.41 ROM to unlock the phone which was causing the issues. I reflashed with the 2.3.1 and everything works fine.
JustinHTC said:
Figured it out. I used the 0.41 ROM to unlock the phone which was causing the issues. I reflashed with the 2.3.1 and everything works fine.
Click to expand...
Click to collapse
0.41 was reportedly having tons of issues, you should have started from there
Glad you got it working.
I am writing on this thread as i still cannot add to the development thread yet
I am using Elelinux-7.0.0-Hero-v2.0. Thanks Ele for a great rom.
So far the only problem i have had is once the unlock screen went invisible on me.
I had to use the patch which worked fine. no black screen. everything else works great so far.
Just trying to contribute to the developers what i can to help.
Any one else has any issue yet.
Elelinux-7.0.0-Hero-v2.0
RADIO VERSION:63.18.55.06SU_6.35.17.03
Kernel: Herokernel-12a
I've had the same issue with the lockscreen but like yourself it was a once off.
Generally the ROM is great (however, this is the first ROM that I've flashed to my hero)
The only other issue im getting is with linking facebook with my contacts; for some reason FB keeps crashing. But keep in mind that I'm a retard in comparison to what you lads know about custom roms etc..... but slowly learning!
Sent from my Hero using XDA App
same problems
I have had the same problems as you. lock screen went invisible a couple of times. and my facebook does not work quite right.
Apart from that has been very stable. no problems or reboots. works great.
Running gingerbread with honeycomb theme on my hero. running at 691mhz is well good.
I have got widgets running on every screen to.
Elelinux RC4 version 7.0 V2.0
kernel 12a
691mhz
clockworkmod.
Thanks Ele for a great rom
After installed 2.0 patch, I still get blank screen (wall paper ok, no any widgets).
The only way to solve is restart
Any thing wrong with my installation? (same spec as above post)
The Bug seems to affect some phones and not others. Might be due to different hardware but not sure.
I am a network engineer. Not a developer.
There is a patch that fixes the black screen bug which might help. You might have to delete dalvik cache first though. But as said not a developer.
I just wanted to try some different roms and loaded cronos rom yesterday and is very good. So running that at the moment.
It is really fast and stable. The fastest i have used so far. But i have not tested everything yet like GPS. But admit i am becoming a cronos fan.
Cheers.
P.s i always backup my phone first and do a complete wipe before trying a new rom. Otherwise could get problems.
I use clockwork mod.
Unfortunately the bug your getting with black screens, invisible menus etc.. is an aosp bug that affects some devices which Google are unable to fix, if you had read through the thread you would have seen this. Ele is working hard on a fix for this but as CM no longer support the hero, its unlikely many cm7 roms will see many updates.
Sent from my HTC Hero using XDA App
Everyone is hoping that Google will fix the memleak and invisible manus problem. To fix it, one needs to undersatand the big picture on how these things are managed. I think it can be done only by experienced coder.
It's a real shame. i love gingerbread and did not want to go back to 2.1 or 2.2.
But might have to if they do not fix it.
I know Ele is working hard on a fix. using his rom at the moment. Was using cronos. But suddenly started getting random reboots and battery started only lasting a few hours and could not find out why.
Thanks to all devs and help.
Elelinux 7.0 v2.1 GPS reboot issue
Hi all,
I found Elelinux 7.0 v2.1 to be almost perfect.
The only major issue so far for me is that when running applications such as sportstracker that use GPS and are running in the background, that as soon as the GPS connection is lost (for whatever reason) the phone always seems to crash.
I wonder whether anyone else has seen this issue and whether there's a way to investigate it.
E.g. is it possible ot redirect logcat to the sdcard and then analyze the log file?
Regards,
MJ
Her0 V2.1 - USB problem
This is a weird one...
I flashed to Elelinux 's fab 2.1 the usual way....
I booted into the ClockworkMod Recovery V2.5.0.7
-- wipe cache partition
-- Advanced - Wipe Dalvik Cache
-- reboot
Then again within Clockwork Recovery I choose 'Install zip from sdcard'
I select the Hero rom and it flashes perfectly...
Now the problem ----> I cant get the usb port working to enable transfer of files?
When the phone boots up it shows 'preparing sd card'
Then when i connect usb lead to pc it shows 'usb connected'
When i then pull the screen down, i see 'usb connected - select to copy files to/from your computer'
When i select that tab, it just crashes back to the home page?
I see the icon at the top of the screen but when i pull down the screen and select as above, it crashes back to home screen again?
In settings, i have both USB debugging and USB debugging notify - all enabled.
Can anyone provide a solution to this issue for me..
thank you
The only way around this problem i think is to mount usb storage from recovery.
Sent from my HTC Hero using XDA App
Hey, hello to all readers!
I am pretty new in this thing of modding the telephone, but I think it is going pretty well.
Last night I installed CM7 nightly build and I am very happy so far. Only thing I really would like to fix are the following:
- I would like to have 720p recording again.
- Fix the issue with the compass (it keeps turning around crazy)
Another question I have is:
I've read in this and in other forums that installing that fixed-sbf could lead to a problem when rebooting, it stays in the red M and wont boot.
Since I was doing my stuff along with another user and saw that he couldn't fix that, I haven't applied the patch.
What would that do? It will update / fix something? is completely necessary to apply this?
Thanks a lot!
Jorixine said:
Hey, hello to all readers!
I am pretty new in this thing of modding the telephone, but I think it is going pretty well.
Last night I installed CM7 nightly build and I am very happy so far. Only thing I really would like to fix are the following:
- I would like to have 720p recording again.
- Fix the issue with the compass (it keeps turning around crazy)
Another question I have is:
I've read in this and in other forums that installing that fixed-sbf could lead to a problem when rebooting, it stays in the red M and wont boot.
Since I was doing my stuff along with another user and saw that he couldn't fix that, I haven't applied the patch.
What would that do? It will update / fix something? is completely necessary to apply this?
Thanks a lot!
Click to expand...
Click to collapse
If you are using CWM 3.x, it's necessary to flash fixed-sbf. Because CWM 3.x is unable to flash kernel.
Solution for compass issue not found yet.
Sorry for this lame question, but how can I confirm which CMW I have?
I've rebooted the device several times and I have not had any issue and didn't install the fixed_sbf.