Database Users

Regarding flashing Glitch.v14-pre5 bootloop fix

Hi all
since i cannot post in Developer's apropriate forum i share with you here..
I have tried all ICS rom there is (not that many yet..) with Glitch v14 pr5 kernel, and they ALL give me bootloops... if not right away then after some period of time, and there is NO way to enter CWM
So i reflashed many many times in odin with different stock and other roms, but always with same result bootloops or a glitch screen logo that dont go any further.
Only if i go in recovery and format ALL options avalible and do a wipe data/factory reset afterwards + run the reset nstools zip avalible (off course only if you have been installing the glitch kernel )
Only then i get a error free install + i can boot in CWM and reboot whitout getting these errors......
Then im able to install > [ROM]SGS ICS 4.0.3 Doctor's ROM [01-12-2012]
and running on day 2 whit out any errors now..
Using nstools to oc and undervolt, is working fine selecting one of the 2 new goveneurs interactiveX or smartassv2 and DIDDLE deep sleep working perfect, BUT nstools wont tel you i always shows 0 in idle time (its nstolls fault) but voltage control EXTREME shows the right numbers
EDIT: Forgot to say that i pulled the externel sd card before going into CWM ! and do NOT deactivate nctools in app maneger !
Hope its ok posting this here ? plz delete or move else admins
Greets to all

[Q] cpu locked at 300mhz with quarx build 20 Feb

Hi,
I was running cyanogenmod 10, quarx's build from 24 Sep 2012 just fine.
Then I upgraded to 2ndboot build (the 20 Feb 2013 one), and now my cpu is locked at 300 mhz.
In the performance options, the min is set to 300 and the max to 0.
I have searched the forums already, and found the approaching post: http://forum.xda-developers.com/showthread.php?t=1764477&highlight=300+mhz
Sadly, I can not change the cpu frequency even in the bootmenu. When I try to do so and reboot, the change is not made.
When I go back in the cpu frequency menu, the settings are reverted back to "boosted", I can not enable or disable the cpu governor.
It seems that the cpu is locked at boot.
I did the upgrade fine I think, wiping cache, dalvik, flashing the rom then gapps, then wiping cache and dalvik again.
The funny thing is, when I try to restore a nandroid backup that I did from my 24/09 rom, it brings me with an empty desktop (not restoring my
data and system at all) which is buggy and eventually crashes.
So I can still flash the 20 Feb 2013 2ndboot build from quarx, but it would be locked at 300 mhz...
Could you please help me ?
(Motorola Defy, green lens)

I would go all way back to stock then do it all again but remember you should factory reset data and wipe caches jus to be 100% sure that its a clean flash but back all ya apps 1st tho
Sent from my MB525 using xda app-developers app

found a fix !
Ok I managed to change the cpu settings in the bootmenu !
Let me explain: the cpu settings menu is too long for the screen, and it doesn't scroll when I reach the bottom.
So I changed options (from boosted to smartass for example), and then selected "blindly" the last line of the menu, to "Go back".
I tried again, this time not selecting the last line but the previous line (by guessing because the menu doesn't scroll...)
This time it helped and keeped the "smartass" setting !
I'm not so sure that this thing did the trick, it might also have to do with disabling the debug mode in the developpers options of the phone.
So after rebooting, the phone was smooth and fast as before... But one last weird thing is that in the performance menu,
min freq is set to 300, max to 1000 this time, but still on "boosted" instead of the "smartass" that I have selected in the bootmenu
Anyways, now it runs at 1000mhz, which is good enough for me !
I am sorry if I disturbed the forums with my question, then finding a fix myself so shortly, but the phone was almost unusable at 300 mhz.
cheers,
micmac

Cpu scaling that's work good and stable for now is "Interactive".
And yes, after changing things in Bootmenu's Cpu settings you need to choose "Save" before going back, or it won't keep your change.

wifi issue

Is there any way i can extract wifi component from one ROM and use it another?
i've installed cyanogenmod 7.2 but can't connect to hidden wifi at work. I don't have access to access point to enable broadcast.
I've tried different ROMs and was able to finally get it to work with DARKSIDE SENSE v4.0 ROM with thederekjay's Kernel. But my phone keeps randomly booting and is really slow compared to cyanogenmod (200 vs 400 free mem).
So I flashed back to cyanogenmod and tried wifi module (bcm4329.ko) from DARKSIDE SENSE v4.0 ROM. But wifi doesn't work, I can't even enable wifi connection.
Any help would be greatly appreciated.
Thanks

That module is compiled for a very particular kernel, i.e. the one it came with. To regain some RAM you could de-sense the ROM and maybe run v6 supercharger to make the OS more aggressive about closing apps.

so I switched back to Darkside snese but my phone keeps randomly rebooting. I've tried flashing the ROM multiple times, clearing cache and formatting partitions. nothing seems to work. I was able to get 3 (of approx 30+ reboots) kernel panic logs: (/proc/last_kmsg )
h**ps://dropbox.com/s/u44a6eccgl257pd/1364486847908.txt
h**ps://dropbox.com/s/1mzy7a1l30vc74p/1364503975830.txt
h**ps://dropbox.com/s/mmpyv4ouowwclg0/1364746269337.txt
Can some one look at these logs and see what's causing the reboots.
thanks for the help

Upgrading Sammy 4.1.2 to Sammy 4.3 and kind of dual booting

OK, as you know an official 4.3 is out and after Wanam got a NON-WIPE version based on it the temptation was too big.
I was running for a very long time a dual-boot system based initially on Siyah kernel and lately on Googy-Max kernel, and the main ROM was a Sammy 4.1.2 (which also happens to be quite customized, with a lot of bloatware removed and the rest frozen in Titanium or Greenified; also using Apex as launcher and DialerEx as dialer).
FIRST STEP - make a good EFS backups (as in save it in more than in one place) - I was running with an older EMF1 modem (which I found to be VERY power-efficient for my needs) using the old EFS format, (for the moment) it is said that 4.3 Sammy ROMs will need the newer EFS format and will upgrade you (probably by installing the new modem). Also in this step it is a good idea to backup your ROM(s) from recovery (and direct that to the external SD). It is also a good idea to have around "just in case" the kernel(s) and whatever else you think you might need to restore things in case something goes wrong. Also having a Titanium Backup of your LATEST stuff on the external SD is a very good idea.
2nd STEP - get a NON-WIPE ROM based on the Sammy 4.3 - I used GT-I9300_WanamLite.XXUGMJ9.V7.2.NO-WIPE.zip
3rd STEP (optional stuff) - in case you want to keep your old Sammy configuration and/or dual-boot - copy (in the special dual-boot recovery) your Sammy main ROM on both slots - I normally have my main 4.1.2 as the 2nd ROM (which is set as default = primary), and I do all the tests on the 1st ROM (mostly since some aroma installers work best on 1st ROM). So I kept my main 4.1.2 as the 2nd ROM and I made a copy of it to 1st ROM.
4th STEP - install the NON-WIPE 4.3 (in my case from Philz Recovery over the 1st ROM as an upgrade). It worked pretty well but it took a rather long time (10+ minutes). At the end I encountered 2 minor problems - during the upgrade of the Sammy Calendar items it kind of remained forever there (with the circle rotating but after 10 more minutes I decided it was a little too much and I forced a power off by keeping the power button pressed 7-9 seconds; after restart it went over OK; at a later time I got a message that media scanner crashed but after updates it seems OK).
5th STEP - update everything in the new ROM and configure it to your taste. IMHO you MUST try Xposed + Wanam Xposed - that one is great.
After a large number of updates, restarts, Wanam-related configurations + obligatory restarts and Greenify-related stuff I got EVERYTHING to work PERFECTLY in the new 4.3, so a few impressions on that:
- things are definitely a little snappier in 4.3
- the new settings are kind of different but not that much
- for me it was a major point that EVERYTHING was kept/upgraded - all my contacts were still there (with the custom pictures), Sammy calendar items and so on; the one thing that I had to restore manually were the custom ringtones;
- this version does not repartition and does not change your bootloader/recovery, but the Sammy official one is said to do that and to replace your bootloader; the free space is kind of low in /system without the repartition but IMHO is still perfectly usable;
- battery life over night looks OK for a Sammy kernel but is a far cry from what I was getting with custom kernels in 4.1.2 - about 8% discharge over night vs. only about 2%
- the best two new features for me - the torchlight in lockscreen (with volume up 2 seconds) and the 3-tap-zoom (standard Android stuff since 4.2.x)
- there is a very tiny delay when unlocking - some people claimed it was like 2 seconds but they are delusional, it is well under 0.5 seconds and I am not bothered by that AT ALL; EDIT: OK, I have now seen a few times something clearly longer than one second, it seems to be a little variable, I have yet to determine on what
- what bothers me a little is the PIN-unlock dialpad - I have seen the same in CM/AOSP before and it is kind of ultra-laggy (and pretty small) compared to the 4.1.2 Sammy PIN-unlock dialpad; on the other hand the 4.3 Sammy keyboard feels a lot better/faster than the ported Note2 keyboard that I am using in 4.1.2 :good:
- camera also works OK, the new Sammy media player is also OK (but voice commands are tricky on it); for the moment the lockscreen for me is "stuck" in the 'safe mode" enforced by Sammsung by some setting of policy; for me is not a problem but I would like to know more about this.
KIND OF DUAL-BOOTING
Googy-Max is not yet fully dual-booting the new Sammy 4.3 (but IMHO is VERY close - 4.3 boots and seems to be seen over USB, only the video driver is not correctly initialized), but there still is a way to get a kind of dual-booting - it is no longer a 2-click 10-seconds thing but instead a 10-click 50-seconds thing but still works - I have Googy-Max-Kernel_1.7.8_CWM.zip and Archi_Flasher_Repacked_Wanam_Stock_XXUGMJ9_Kernel.zip in the root of the internal SD and I only need to restart to recovery and write the 6-8 MB of kernel; when the Sammy stock 4.3 is written it automatically starts the 1st (standard) ROM = 4.3, when Googy-Max is written it was set as default for the 2nd ROM so it goes automatically to my old 4.1.2
REMEMBER - everything on internal SD is the new "4.2.x and newer" style - in 4.3 it goes to /data/media/0 and in 4.1.2 it goes to /data/media. Eventually specific configuration for that must be done in Philz Recovery and Titanium Backup.
I am still doing some battery tests over the next days - this night I want to test if the new BUUGMJ3 modem is part of the power-consumption differences so I will test it in the old 4.1.2 and with Googy-Max. There are many other small things to test, I will eventually add those here once done.
EDIT: A BETTER KERNEL FIXES THE LAGS
I have now tried a beta kernel (different than the stock one) and the lags are gone, tomorrow I will report on battery life.
http://yank555-lu.net/viewtopic.php?p=4594#p4594
Also it might not be impossible that a true dual-boot Googy Max might be ready after the weekend or so.

Quite confuse here
How you dual boot for stock 4.3 as primary Rom & stock 4.1.2 as secondary Rom?
I know latest googy kernel not supporting stock 4.3 yet
Sent from my GT-I9300 using XDA Premium 4 mobile app

MsElise said:
Quite confuse here
How you dual boot for stock 4.3 as primary Rom & stock 4.1.2 as secondary Rom?
I know latest googy kernel not supporting stock 4.3 yet
...
Click to expand...
Click to collapse
It is not the very easy "2-click 10-seconds" dual-boot with a special dual-boot kernel, it is the more complex "10-click 50-seconds" dual-boot where you have two kernels as zip that you can install from recovery (it still takes like 10 seconds to write the kernel but since you must boot in recovery you are going to lose closer to 50 seconds when you decide to switch) - the stock Sammy 4.3 kernel (pre-rooted and processed by Wanam and repackaged by Archi) will always boot to the 1st ROM, while the existing Googy-Max (1.7.8 as we speak) will go to whatever is set as default for it - and in my case I have Sammy 4.1.2 set as default in 2nd ROM slot.

A BETTER KERNEL FIXES THE LAGS
I have now tried a beta kernel (different than the stock one) and the lags are gone, tomorrow I will report on battery life.
http://yank555-lu.net/viewtopic.php?p=4594#p4594
Remember that if you encounter root-related problems (or eventually you are left at the Samsung boot logo) you probably need to write this from your recovery:
http://download.chainfire.eu/345/
Also it might not be impossible that a true dual-boot Googy Max might be ready after the weekend or so.

xclub_101 said:
...
I have now tried a beta kernel (different than the stock one) and the lags are gone, tomorrow I will report on battery life.
...
Click to expand...
Click to collapse
OK, I am now really impressed with the latest yank.lu kernel :good:
With the default (zzmove) governor and almost all default settings from the beta2+ aroma (except no quick charge and only 400 MB zram) I got about 1% over night, I am now keeping this configuration for extra testing for a few more days :good:

can run the stock rom 4.1.2 and **** rom with 4.3 ????? :fingers-crossed:

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 ;-(