Database Users

[Q] CM6 / CM7 - CM7 won't work.

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?

[TELUS T959D Fascinate]-Running ONECOSMIC'S ICS

Hello.
This is where you can look at the tutorial and get the files to install if you feel like jumping into it ...
ICS Step by step and files
Note: if you do flash this and it hangs at the boot screen, pull the battery and flash it again and it should work. Some have had to do it 3 times.
I take no credit for this ROM and full props go to the developers of the above post and all those working to make this happen.
First the look and feel of ICS is nothing short of superb. The speed as of now is similar to all the other ROMS I have tried with a little chop here and there but nothing major.
Yes lots of little issues and items that do not work like the camera and GPS but not a huge deal for me so I am willing to stick to it.
Battery so far is decent. 13 hours and 43 min. on the first charge to calibrate and sitting at 24% still. This included allot of playing with the phone and reboots to test jigs
As for the issues that are somewhat bothersome, they include the following.
1. No home or search button. I know same as usual when installing an i9000 ROM but the key mappings from the GB ROMS does not work.
2. BLN (issue all around) will remain lit until you wake the phone to get the notification.
3. They had to do some funky stuff to get 3G to work so it lags to start. Not a huge deal cause it does start and remain working.
I will be continuing to use this ROM and hopefully everything will be working soon (these guys are flying. Also I have been told that the folks over at Glitch are already working on the kernels for the ICS port so that is promising as well.
If there are any other out there running this on our phone chime in with your thoughts or fixes if you have any.
Thanx
Bucky

Thanks for starting this thread. Can't wait to hear about your progress.

Alpha 7
Hey here is the update ...
Installed the Alpha 7 update today and I have to say this rom is fantastic.
1. Camera is fixed and works like a charm.
2. GPS locked in seconds and accurate indoors!! Big improvment over all other roms I have used.
3. HW Acceleration is fixed and working from what I can tell
4. You Tube is fixed and can watch video
Still on the not working list
1. Can not plug the phone in while off as it just restarts. this is a work in progress and known issue
2. Can not record video
3. Will not read a SIM card for contacts and so on (thank god for Google sync)
4. Still no home or search buttons (I think I may need to work on that on myself unless a kernel is released)
SO my review so far ...
No real issues with the general use of the phone. Text, phone, email and web are solid, I have installed apps from the market with no issues and not one FC yet. Battery life is good and nothing is taking over. I have been able to use the phone all day and still have lots left over before going to bed and plugging in. I have not been through a full battery as of yet but that is what I am working on now.
Memory - Last I looked I had 174MB of memory remaining which is the highest I have seen.
ICS is really smooth and fast while moving around. I am going to continue to play with it and report back here for everyone.
I don't use a whole lot of apps so there won't be much regarding those.
Thanx for stopping by and I will post pics when I can.
Bucky

Nevermind
Sent from my SCH-I500 using XDA App

Thanks for the update. From your review, it sounds like an awesome rom. Can't wait to try it but need them to fix the video recording first. Although I might just cave and try it out just to see what the fuss is all about
Can always restore my current setup... lol.

Update ...
been getting the SOD today and not sure why, I mentioned above that the HW acceleration was working, I misunderstood and it is not fully working yet.
I found that the system partition is very small. There was an update which required copying libs and there was not enough space left to do this (2MB). Not too sure if this is due to coming from MIUI or just a ROM issue.
Alpha 8 was released but had quite a few issues so not flashing that one.
Daily use has been great so far (except for the SOD) with no reception or data issues.
I am still working on the home and search buttons but I think that will get fixed with a kernel update. I tried the keymap file but these buttons do not even register in recovery so I get nothing in the ROM either.
More to come ...

Haven't tried this (likely won't as I need the phone for work) but buck have you tried the manual key fix - some directions in our thread on putting on Darkys 10.3.
Sent from T959D running Miui

Yup been there done that no go
Sent from my GT-I9000 using XDA App

Hey buck , was doing some searching in teamhacksung's thread about their ICS port, and someone suggested to change the following and then the key mapping for our phones will work properly. Not sure if the file system is the same for both, but definitely a bit of info if it isn't!
All you have to do is change this part on**arch/arm/mach-s5pv210/mach-aries.c*
*Original**(line 1216~1221)
static const int touch_keypad_code[] = {
#if defined (CONFIG_SAMSUNG_GALAXYS) || defined (CONFIG_SAMSUNG_GALAXYSB)
KEY_MENU,
KEY_BACK,
*0,*
*0*
----------------------------------------------------------------------------*
*Edited*
static const int touch_keypad_code[] = {
#if defined (CONFIG_SAMSUNG_GALAXYS) || defined (CONFIG_SAMSUNG_GALAXYSB)
KEY_MENU,
KEY_BACK,
*KEY_HOME,*
*KEY_SEARCH*
Sent from my GT-I9000 (T959 mod) using XDA App

Thank for the input. After flashing bata 1 all the buttons are working. More to come: )
Sent from my GT-I9000 using XDA App

Hey, have a telus fascinate too. Know how to flash and all that fun stuff. Just don't fully follow where you make the changes for key mapping...if you could just guide me in the right direction, I can figure the rest out...
changes in the kernel zip? the beta zip? after flashing? something completely different?
thanks a lot!

There are no changes to be made with this ROM, they are built in. Just flash and all good.
I will post update tonight after work.
Sent from my GT-I9000 using XDA App

yeah sorry realized that immediately after posting / flashing to the new rom.
have you tried out BT audio? I can connect to different devices but audio won't stream

havoksupertwit said:
yeah sorry realized that immediately after posting / flashing to the new rom.
have you tried out BT audio? I can connect to different devices but audio won't stream
Click to expand...
Click to collapse
There are allot of BT related posts in the QA. I personally do not use any BT but I do have a headset that I will try when I get home.
Seems to be a battery drain issue too as my phone is now dead but I have not calibrated so we will see after I do that.

bucknetbucky said:
Seems to be a battery drain issue too as my phone is now dead but I have not calibrated so we will see after I do that.
Click to expand...
Click to collapse
Calibrated my phone this morning. Heavy use today configuring everything but about 52% now (sooo 5 hours or use?)

Why god! Whhyyy!!
bucknetbucky said:
There are allot of BT related posts in the QA. I personally do not use any BT but I do have a headset that I will try when I get home.
Seems to be a battery drain issue too as my phone is now dead but I have not calibrated so we will see after I do that.
Click to expand...
Click to collapse
AT LEAST YOU GUYS HAVE IT RUNNING!!
I am having a hell of a time trying to get it to work. I have tried so many different ways to get it up and running but no luck.
I've tried installing it from MIUI 3 times but all I get when trying to boot into ICS for the first time is a Black Screen after the FuguMod boot screen.
The funny thing is that the 4 soft buttons at the bottom light up still.
So I then decided to try the JVT way:
-Flashed JVT DARKYROM (ODIN)
-Lagfix OFF
-FULL WIPEs (factory reset, cache, dalvik)
-FLASHED CM7.1 STABLE
-FULL WIPEs (factory reset, cache, dalvik)
-Flash ICS BETA1
-Flash kernel
-FOR THE SECOND TIME:
-Flash ICS BETA1 AGAIN
-Flash kernel AGAIN
Same issue, black screen after the FuguMod boot screen, buttons still light up.
So i tried a couple more times in a few different ways based off what I have already tried, but this time, before booting into ICS for the first time, I installed the 'Superuser-3.0.6-efgh-signed.zip' package.
Same issue. I'm not having any luck here.

iwebsource said:
AT LEAST YOU GUYS HAVE IT RUNNING!!
I am having a hell of a time trying to get it to work. I have tried so many different ways to get it up and running but no luck.
I've tried installing it from MIUI 3 times but all I get when trying to boot into ICS for the first time is a Black Screen after the FuguMod boot screen.
The funny thing is that the 4 soft buttons at the bottom light up still.
So I then decided to try the JVT way:
-Flashed JVT DARKYROM (ODIN)
-Lagfix OFF
-FULL WIPEs (factory reset, cache, dalvik)
-FLASHED CM7.1 STABLE
-FULL WIPEs (factory reset, cache, dalvik)
-Flash ICS BETA1
-Flash kernel
-FOR THE SECOND TIME:
-Flash ICS BETA1 AGAIN
-Flash kernel AGAIN
Same issue, black screen after the FuguMod boot screen, buttons still light up.
So i tried a couple more times in a few different ways based off what I have already tried, but this time, before booting into ICS for the first time, I installed the 'Superuser-3.0.6-efgh-signed.zip' package.
Same issue. I'm not having any luck here.
Click to expand...
Click to collapse
OK so here is what I did ...
Started from MIUI 1.11.18
1. Do a nandroid backup
2. download all the files to the SD card. This includes the ROM, Kernel and super user fix
Links:
Kernel:http://ice-cream-sandwich-sgs.googlecode.com/files/FuguModICS_GT-I9000_update.zip
ROM:http://ice-cream-sandwich-sgs.googlecode.com/files/ICS_4.0.1_r1-Beta1-i9000.zip
Super User:http://ice-cream-sandwich-sgs.googlecode.com/files/Superuser-3.0.6-efgh-signed.zip
3. Boot to recovery and do factory reset, wipe cache and davlik cache
4. Install the Kernel first and reboot now
5. Boot into recovery factory reset and wipe cache and Davlik and Install the ROM then reboot now
6 Boot back to recovery and install the Kernel again with out the wipe
7. If after reboot you do not have root then boot to recovery and flash super user fix
8. reboot and it should be working at least it was for me
It seems to me that you are missing the first flash of the kernel before the ROM. It sets up the file system from what I gather
Note: If needed flash the kernel and rom then kernel again with all the wipes as mentioned above.
I know there are allot of folks having issues getting it to run. Not too sure if it was the way I installed MIUI that might have made the difference.
My battery is charging now so I can calibrate it and see how it goes after that (it drained pretty quick today) lol.
I hope you can get it going cause it truly is awesome
Still not working:
Can not charge with the phone off
Google TTS stops working
Phone will not vibrate for SMS or email when in silent mode
BLN stays on for notifications until the phone is taken out of sleep (can be turned off)
Compass is why off (have not attempted to calibrate yet though)
11 MB left in the system partition (not much but I do not think there will be many changes there)
Video play back is choppy and some will not play
Bucky

regarding the black screen:
- had that too... I let it sit on the black screen for 2-3 minutes and then it went to the boot screen animation (a multi-coloured )...that for a few minutes...then finally booted.
How i got it working:
a) Started on MIUI...booted into clockwork
b) Backup
c) Wipe data / factory reset and cache and dalvik cache
d) Install rom and then kernel
e) Restart
f) Install rom and then kernel
g) Restart and wait very patiently for a little while
h) Once it all works, can reboot into clockwork and install superuser
Good luck! I really think the rom is nearly stable enough for daily use...
-------
Also have the no vibrate on silent... haven't tried the other stuff yet.
Oh and TTS hasn't crashed on this version yet for me...
Astrid glitches a little to a lot.

Changing from google tts to picco tts solves the problem there. As for the other stuff it is all reported as known.
I am using as a daily on my phone and no issues with general use. Still testing battery and that seems to be a bit of an issue with regard to Android OS as usual
Sent from my GT-I9000 using XDA App

So to install this ROM I would just have to install it as per totallydubbed's instructions? I don't want to flash miui if I don't have to to try this out.
Sent from my GT-I9000 (T959 mod) using XDA App

[Q]Sudden shutdown on 4.2.2

I am experiencing sudden shutdowns (or atleast non-responsive screen) quite often while on 4.2.2. For example, last night, the phone was at 89%. I went to sleep. When I woke up, the phone did not respond to the power button. I am not sure how long I pressed the power button (so I am not sure if I did a reboot or a boot) but the phone did not go to the lock screen, a (re)boot was required. I've had this since the day I had it (came on 4.2.1, currently running 4.2.2 stock).
When I did boot my phone back up, my battery was as indictaed in the screenshot. It was suddenly at 34%! I have no idea what causes this, but would much like to resolve this issue. I'd love to try a different kernel, but on the franco kernel (r82) I was unable to receive notifications (and thus missed alot of Whatsapp messages) unless I would actively turn on my phone with the power button.
I did google this problem but found no solution for me.

If you're using custom kernel, then post this kind of issues on kernel thread. If not then clean phone and stock reflash it.
Some mods (like the awesomeBEATS) breaks 4.2.2 so keep that in mind.
Adam

AdamLange said:
If you're using custom kernel, then post this kind of issues on kernel thread. If not then clean phone and stock reflash it.
Some mods (like the awesomeBEATS) breaks 4.2.2 so keep that in mind.
Adam
Click to expand...
Click to collapse
I have reflashed the custom ROM and kernel. So that can't be the issue.

I just posted this thread:
http://forum.xda-developers.com/showthread.php?t=2153860
Did you get a flashing white led?

As I was very sleepy when I woke up, I'm not sure, but there could have been one, yes!

Anyone ever experienced this? Is this RMA-worthy?
Edit: Just happened again, while I was whatsapping. I turn it on standby, want to turn it on 5 minutes later and I have to reboot it...

I have this problem since 4.2.2 on the nexus 5

[Q] random reboots

hi.
In the last week, I have been experiencing random reboots. It usually happens when the phone is in sleep mode, it just restarts by itself.
When this first happened, I was using Vanir ROM with the AK kernel. (there I got green screen instead of a reboot). So I installed the purified kernel, thinking it might be kernel-related. It did not help.
Then I tried Purity ROM (after a full wipe) with purified kernel. Still the same reboots.
Tried Semaphore kernel, the same.
I did a dirty flash of the ROM before switching between kernels.
So I am completely lost here. I go on a vacation tomorrow, and I really hope to fix the problem before I go. So I would really appreciate your help.
Thanks.

romitkin said:
hi.
In the last week, I have been experiencing random reboots. It usually happens when the phone is in sleep mode, it just restarts by itself.
When this first happened, I was using Vanir ROM with the AK kernel. (there I got green screen instead of a reboot). So I installed the purified kernel, thinking it might be kernel-related. It did not help.
Then I tried Purity ROM (after a full wipe) with purified kernel. Still the same reboots.
Tried Semaphore kernel, the same.
I did a dirty flash of the ROM before switching between kernels.
So I am completely lost here. I go on a vacation tomorrow, and I really hope to fix the problem before I go. So I would really appreciate your help.
Thanks.
Click to expand...
Click to collapse
Try flashing a official image via any Nexus toolkits and then install the rom you want.. bakcup your data and also make a nandroid backup..:good:

Hi
I did that, flashed stock ROM and did a full wipe including the user storage.
Then I flashed Purity ROM and Semaphore kernel.
I still experience the reboots, a few times a day usually...
Should I try a different ROM or kernel?
Sent from my Nexus 4 using xda premium

I'm using Purity ROM for some time now and it's just awesome.
Kernel is purified kernel and as i read many people writing about semaphore having better battery live with purity, i tried it.
just for half a day, because it randomly rebooted twice in this time.
first time while talking with someone, second one while browsing the internet.
any idea why? for now i'm back to purified, but i just get normal battery life. maybe 2hrs screen on.

Defy Green Lense MB525 bootloops/camera problems on Feb/Mar 2014 CM10.2/11 nightlies

I've had the trouble described in
http://forum.xda-developers.com/showpost.php?p=49962954&postcount=1775
What's worse, more recent builds have a kernel that bootloops for me. This thread has a solution.
Originally I was unsatisfied with CM11 nightly, because the camera crashed with a hard reset - heavy use of the gallery or taking a photo after a long time had triggered this hard reset reliably. So this problem was reproducable.
I upgraded CM11 nightly to latest 2014-03-30, just to find out recent kernels won't start at all or bootloop the green lense defy.
After that I wiped anything - flash SBF, Framaroot, 2ndinit, twrp_recovery_2.6.3.0.zip.
To confirm the device was working I flashed a couple of roms (CM9, CM10) builds from October 2013, they worked.
While testing I realized that these roms were a lot snappier than the CM11 one I was dissatisfied with, noticing that besides hard reset on camera usage I also had a lagging UI. I assume that SELinux might be one of the reasons for the camera hard resets I experienced, but have no proof for this..
Then I spent a couple of days debugging the problem and it turns out, that all of the problems arise indeed from the kernel used.
Atm, I run a butter smooth CM10.2 nightly rom dating 2014-03-31, but running on a kernel dating 2014-01-20 (ripped out of CM11-nightly!).
For this to happen, simply exchange zImage under /system/bootmenu/2nd-boot/
Extract zImage from 2014-01-20 rom beforehand, put it on sdcard.
After installing the latest rom, before rebooting, do
- Mount /system with TWRP
- Go to Tools > Filemanager
- Select the 2014-01-20 zImage in TWRP Filemanager
- Let TWRP copy it to /system/bootmenu/2nd-boot/ (overwriting the one that's in there)
- Wipe cache/dalvik
- Reboot
I have tested this setup and it runs amazingly! I tested GPS turning on an off, Camera works (except video with stock app), Wifi works - no reboots and the UI is a breeze. It simply behaves as it should. Neither zRAM or zCache is activated, battery consumption is low, as is CPU usage.
Conclusion: The latest nightly kernels suck hard for green lense defy, but I still do not know exactly why.
Fazit: Can confirm that zImage from 2014-01-20 is tried and tested.
===================================
How solution was found: I read in the forums, that update-recovery.zip contains a kernel. Since after flash of CM10.2-2014-03-31 I had bootloop problem, I went to TWRP recovery on blue led, which still worked, and installed update-recovery.zip AFTER rom. Normally, you do not do this, since this DOWNGRADES kernel. But if latest kernel does not work, there is a chance succeeding with this method.
Ok, after flashing update-recovery.zip zImage dating 2013-11-07 was in place and phone booted with CM10.2-2014-03-31 image. I thouhgt I had found the solution, but soon noticed, that this kernel had issued with GPS (it would hang and not turn off, once activated). The immediate next step was to look for a kernel built after 2013-11-07 - I tried with 2014-01-20, since this was the latest version offered by defy.bytekiste.de here:
http://defy.bytekiste.de/cm11-nightly-defy+/
Since, on defy.bytekiste.de CM10.2 listing stopped at 2013-10-30, and with update-recovery.zip I already had a kernel from 2013-11-07, I jumped to CM11 roms, as I did not know about existence of defy.svolkov.name at that time.
defy.svolkov.name lists CM10.2 nightly builds from 2014-01-09 on. One could probably try the kernels directly from these roms. However, I think the difference in kernels between CM10.2 and CM11 is neglectible. What matters is the timestamp of the builds - different timestamp, different kernel config and that seems to decide whether it's working on defy green lense or not.
===================================
I did not further bisect the problem yet, i.e. trying each nightly kernel built after 2014-01-20 in succession to see which build first caused the bootloop problem. However I've checked some of the roms and the file structure on quarx2k.ru and defy.bytekiste.de (you can find complete structure of both on http://defy.svolkov.name/), it's borked:
versions for cm-11-20131229-NIGHTLY-mb526.zip
886b1bfdeadada2f45c695e34e126d0c http://defy.bytekiste.de/cm11-nightly-defy+/cm-11-20131229-NIGHTLY-mb526.zip
886b1bfdeadada2f45c695e34e126d0c http://defy.svolkov.name/quarx2k.ru/cm11.0-nightly-defy+/cm-11-20131229-NIGHTLY-mb526.zip
versions for cm-11-20140117-NIGHTLY-mb526.zip
a936c82ad55fa488079b2a8796838678 http://defy.bytekiste.de/cm11-nightly-defy+/cm-11-20140117-NIGHTLY-mb526.zip
a936c82ad55fa488079b2a8796838678 http://defy.svolkov.name/quarx2k.ru/cm11.0-nightly-defy+/cm-11-20140117-NIGHTLY-mb526.zip
6e05a8e9205f30a212be5aafc6e4bc01 http://defy.svolkov.name/quarx2k.ru/roms/defy-cm11.0/cm-11-20140117-NIGHTLY-mb526.zip
now, from the above, if you thought
"defy.bytekiste.de/cm11-nightly-defy+" and
"defy.svolkov.name/quarx2k.ru/cm11.0-nightly-defy+"
were mirrors wrt same-named files, think again.
versions for cm-11-20140120-NIGHTLY-mb526.zip
0602c6090ffa169dcf249b49f3c1d2be http://defy.bytekiste.de/cm11-nightly-defy+/cm-11-20140120-NIGHTLY-mb526.zip (appears to have a different ramdisk-recovery, other files in 2nd-boot dir are identical to rom below)
d9a88dde07c06474d60dc353c53babc8 http://defy.svolkov.name/quarx2k.ru/cm11.0-nightly-defy+/cm-11-20140120-NIGHTLY-mb526.zip
also note,
"defy.svolkov.name/quarx2k.ru/roms/defy-cm11.0/"
holds the most recent list of nightlies, while the listing starts with
20140109 version, and continues until
20140117 version (see versions above)
it omits 20140120 completely, and then continues from
20140123 version.
===================================
I actually wanted to post this in dev forums CM10.2 on defy thread, but do not have more than 10 posts on xda-dev, so are not allowed to. This is why I post it here.

Thanks!
cmuelle8 said:
...
- Let TWRP copy it to /system/bootmenu/2nd-boot/ (overwriting the one that's in there)
...
I tried with 2014-01-20, since this was the latest version offered by defy.bytekiste.de here:
h t t p : / / d efy.bytekiste.d e/cm11-nightly-defy+/
...
Click to expand...
Click to collapse
Thanks for posting your findings. I first thought "it will be fixed soon" when my camera didn't work after a update. Then, because no one was complaining, i thought the camera in my Defy is broken.
I have almost done the same and now the camera is working again
1) extracted the zImage from 2014-01-20
2) "adb push" it to the sdcard
3) mount -o remount,rw /dev/block/mmcblk1p21 /system/
4) cd /system/bootstrap/2nd-boot
5) cp /sdcard/zImage .
6) reboot
7) happy

Any later kernels that show the same stability?
Edit: My Defy will not boot after replacing the kernel. I'm on cm-11-20140611 now.

I think you are refering to camera bug #44?
I have the same with my Defy green lense (MB525). I've found out that the bug was introduced in CM11 with the ROM from 2014-03-15. So the camera worked for me without problem until the ROM from 2014-03-13. Since then I have to set the minimum frequency at least to 600MHz. Below that value e.g. 500MHz I get indeed bootloopss when using camera or gallery. Disabling the HWA settings for the most apps (besides the camera) delayes only the unavoidably bootloop for some seconds.
Do you think it's possible to use the newest CM11 nightly ROM together with the last working ROM from 2014-03-13?

The camera-bug #44 still exists since the ROM_2014-03-15. But I think I could narrow down the problem a little. It seems to be the kernel, means the file "zImage" under /bootstrap/2nd-boot. When I took that file from the last working ROM_2014-03-13 and apply it to a later problematic ROM, then the bug #44 is gone (for me). I've successfully tested this workaround until the ROM-version from 2014-03-25. Since ROM_2014-04-01 and later this doesn't work because the phone wont start, maybe to much has changed within the ROM. The replacement (camera2.apk, MediaProvider.apk) or the deletion (wallpapper, etc.) of some system-apps leads to no success. Deactivating the autofocus-function or the GPS-tagging for the pictures doesnt help either. However, until now the phone reboots fairly fast when I scroll the taken pictures within the camera-app. Maybe it has something to do with my sdcard (read performance, whatever)?!?!? But the chance is very small, because it had worked outstanding until the ROMs before 2014-03-14 ;-(