Hi, yesterday I have installed Cyanogen Froyo CM6-Latest (based on MiniCM) - v6.0 from this link http://forum.xda-developers.com/showthread.php?t=1059361
and phone didn't boot. After 15 minutes, when it has black screen and vibrate sometimes, I put out batery.
Why it can not boot to system?
Sorry for my english, I am from Slovakia
you need to wait a litle bit longer tihis is knowing bug and is mentioned in the MiniCM v6.0 thread only read a little and you'll all learned
Ok, but how much time I have to wait?
around 30minutes to 1 hur :/ You must be patient it takes so long only for first boot
Thanks a lot Now I have put same ROM into my mini pro as you have, so I am waiting
I am disappointed About 3 hours from installing ROM FroyoComb v1.6, and nothing happend Only black screen with backlight, no vibrating
Hallooooo, does anybody know what to do with it????? PLEASE HELP!
now you have fixed MiniCM v6.1 and you can install it without problems
Thanks a lot bro Works great!
/edit: THERE IS ONE BIG PROBLEM WITH THIS ROM!!! I CAN NOT INSTALL ANY APP PHONE REBOOTING!!!
Yes is knowing bug like in cyanocomb v 1.2
Go to recovery wipe dalvik cache, partition cache, ful wipe (factory reset) and try.
If stil didnt work backup your sd card and format it
Sent from my U20i using XDA Premium App
Thanks again It is fine now. I can install apps. But when somebody calls me, the slider to recieve and reject call is broken I almost can not see recieve slider.
But I have some more questions: Is it possible to change battery indicator in status bar? How?
yes that need to be fixed:/
for battery you can change it with another theme
look at here
http://forum.xda-developers.com/showthread.php?t=1148635
I have installed the Cyanogen Froyo CM6 v6.01 successfully, but when I try to change sound notifications (from Settings -> Sound or from any app) I get an error saying that the application has stopped unexpectedly.
What should I do? I created the ringtones folder in my microSD and rebooted but still nothing.
Sorry, but I do not know what are you doing bad, because it works for me
Just in case anyone is interested, it was the sound picker. I installed Rings Extended and the problem is solved
Before, make and full wipe factory rester, clear cache, dalvic cache, wipe cache partition, before flashing new rom, try again this method and then flash, i think it 99.3% helps.
Related
Just to report that for me i couldn't get network(no service) signal for 1 or 2 minutes even after crashing the system server
http://forum.xda-developers.com/showthread.php?t=1037855
I can't post in there yet, if someone can do that for me, i appreciate that.
I don't if it is connected but the signal showed up when i went to the system update on settings.
Settings> System > About Phone > System updates> Then it crashes in here and FC
Once it gets back to the home everything gets alright.
The rom seems a bit laggy yet, but maybe is something configuration or procedure i did wrongly.
Also from time to time, the screen gets lighted (bright) and after that dark again when i am not using it, not even near.
Just flashed it 20min ago.
you should attempted to reflash the ROM. Make sure you are on basebrand.49 or .52. Wipe data, cache, dalvik cache, and battery stats, then flash the custom zip ROM. Crash system server like you said and you should have a clean ROM
If you want a GB ROM you may try this one http://forum.xda-developers.com/showthread.php?t=911364
You're gonna get more suport from J with this ROM =)
what I did and it worked for me was flash TripNMIUI_BTS_02.zip first, then I rooted it again and installed xRecovery. I then flashed bb.52, booted into xRecovery, cleaned the cache, dalvik, battery, etc. and then flashed this ROM. Do a system crash and once it reboots it should pick up a signal within 10 sec.
aval1392 said:
you should attempted to reflash the ROM. Make sure you are on basebrand.49 or .52. Wipe data, cache, dalvik cache, and battery stats, then flash the custom zip ROM. Crash system server like you said and you should have a clean ROM
Click to expand...
Click to collapse
As i said before, after the last FC in the settings, it did work normally i have the rom working perfectly fine, what i wanted was to someone that can post there to do this for me, or that trip could see this to add to the install steps so people can try also what worked for me may work for others.
ironjose said:
If you want a GB ROM you may try this one http://forum.xda-developers.com/showthread.php?t=911364
You're gonna get more suport from J with this ROM =)
Click to expand...
Click to collapse
I normally try every rom for one or two weeks at least so i can be sure which one is better, so far i've tried one based in this rom, but is wasn't faster than TripNMIUI version.
In TripNMIUI i got 36,5 in Linpack without using any APP2SD tool, also got in Quadrant from 1100 to 1200.
The other roms i tried hardly passed up than 32k in linpack and normally near 900 in quadrant.
Hi, I installed the MiniCM-6 v3 custom ROM using xrec and everything seems to be going smoothly, until the new screen which says, "Please touch the android to begin"... and I found that my touchscreen is NOT working. All other buttons work.
I am using Sony Ericsson X10 Mini Pro originally running SE Android 2.1.
Please help? Thanks
a full wipe might help? i didnt have problems with the touch.
I have wiped out the cache, dalvik (sp?) cache, made a factory reset, formatted system/data/cache etc. all through xRecovery to no avail. The touchscreen is still NOT working at all. Any other advice?
remove the multitouch module from /system/lib using ADB
same thing happens to me. touchscreen is not working anymore, i flash stock software back and same problem happening again, maybe hardware problem
Everything works OK whenever I restore my stock Android using xRecovery, so the touchscreen is NOT faulty.
I concur with and like the idea of disabling dualtouch but do not know how to do it... is ADB = Andro File Manager?
btw ruifang & asranash, you both fm KL?? I'm fm SG and coming up sometime next week.
UPDATE
I installed FroyoComb 1.32 and I also have the SAME PROBLEM - No touchscreen. It *must* be the Dualtouch driver...
I learnt that MiniCM6 v5.0 is a Stable Release and installed it. However, the dualtouch died on my phone again after 1 week of use. The dualtouch driver is truly defective and might be the cause of the reboots, hangs and total blackouts reported by others in these forums.
First update to official, then make full wipe, factory reset, clear cache, clear dalvic cache. After flash rom and it will work.
ruifung said:
remove the multitouch module from /system/lib using ADB
Click to expand...
Click to collapse
how to do that plz
name's multitouch module plz
i got a “fix” for those who cannot install the ROM due to faulty dual touch. AFTER downloading “XXX ROM” delete the file cyct8ma_ser.ko (the dual touch module) at the zip file. ii is somewhere the “lib/module” folder.. NO NEED TO UNZIP just delete it.. then install there you have it.
use 7zip or winrar to open those files.
hope someone will FIX our problem with dualtouch.
I recently flashed alien 4 with the theme and all was good for a few hours but then i suddenly couldnt answer calls. when i get a call the phone vibrates nonstop without a ringtone but i cant answer or decline it and com.android.phone eventually force closes.
i reflashed the rom with no luck, fixed permissions flashed the old radio.
I have now flashed the cwm backup of my stock unlocked rom and the problem still persists.
pls help
ps I have an unlocked att atrix
anyone? ... Ive had to resort to switching to my old bb, feel like I jumped back a generation techwise
Do a full fastboot wipe. People often flash things without doing a proper wipe then are confused why things are broken. This means /system, /data, /boot, /cache, /preinstall, /webtop. All wiped. Then go into cwm and for good measure do a factory reset and wipe dalvik. Then flash alien, reboot, let it build system files, then reboot and flash the theme . Bam. Done.
Sent from my MB860 using Tapatalk
did another wipe according to the above instructions and seems to be working for now. Thanks
I have asked a few times on the forum if this could be related to the baseband of my device. Basically what happens is in call, he proximity sensor seems to cause the touchscreen to go haywire. I receive what amounts to phantom button presses. Basically voiding the functionality of the proximity sensor to begin with, the calls get put on hold, muted, dropped or whatever. A new symptom has now appeared, the dreaded black screen bug. When a call gets dropped, screen goes black and nothing but a battery pull solves this. Contacts are suddenly missing and I need to resync to get them back
I have tried many different roms, every single kernel. The only solution I personally can think of, is disabling the proximity sensor altogether. Can anyone tell me which line in the build.prop would disable this?
Its my everyday phone, so this is rather urgent, any help would be appreciated
You need to add either of these 2 lines (not sure which, or if it matters):
gsm.proximity.enable=false
gsm.proximity.enable=0
Oh, and apparently MIUI ROMs have that option in the settings.
I can spend 20 min to try solving this or just give you a clue
Try this:
-install ROM Manager and install the custom recovery for your phone if you already haven't got one
-go into recovery, wipe dalvik cache and cache, and most importantly WIPE DATA...
Now flash the custom rom and wait for it to boot...
Wiping data should delete everything from the old rom, so incompatible data when sw roms will be erased...
Backup your sd apps, contacts trough google servers - do not forget...
Sent from my LG-P500, GingerSnap 2.3 using xda premium !
Left4DeadMW said:
I can spend 20 min to try solving this or just give you a clue
Try this:
-install ROM Manager and install the custom recovery for your phone if you already haven't got one
-go into recovery, wipe dalvik cache and cache, and most importantly WIPE DATA...
Now flash the custom rom and wait for it to boot...
Wiping data should delete everything from the old rom, so incompatible data when sw roms will be erased...
Backup your sd apps, contacts trough google servers - do not forget...
Sent from my LG-P500, GingerSnap 2.3 using xda premium !
Click to expand...
Click to collapse
I usually mount and format /system when i do flash a new rom. Thanks for your reply, but as I stated before, this happens on every rom I have flashed before
Hello everyone!
I request your help please, because sometime my phone goes stuck and I have to reboot each time.
First, here is my configuration :
XWLSW NeatRom Lite 4.8 installed with full wipe (Philz kernel) + Blue Ginger Plus Theme + Apex Launcher + Fancy Widget (clock + weather) on my main page.
I have to precise, that before installing the NeatRom, I had an older ICS ROM (CriskeloServanTeam V12), and this kind of stuck used to happening on my device, that's why I decided to install a new ROM.
Here is the 2 last situtations when my phone was stuck :
- I'm charging my phone just before going to sleep (in fly mode), and in the middle/end of the night, surely after my battery reach 100%, I'm looking to the clock of my phone : it display 2h31 (instead of the real time 5h23), probably at the time when my phone goes stuck.
Symptoms : Time was stuck, Apex Launcher close, Status bar is missing on the lockscreen, impossible to goes through the lockscreen, but it is possible to reboot (luckily!).
- In the daily use of my phone, I decided to activate the data by the status bar on the lockscreen, then I switch off the screen. 15-20 min later, I want to unlock my screen, but impossible, it is stuck.
Symptoms : Status bar is missing on the lockscreen, impossible to goes through the lockscreen, but it is possible to reboot (luckily!).
So my questions :
Why this is happening?
Is anyone else already have this kind of stuck with this configuration?
What can I do to fix that?
Thanks a lot!
Sound like a sod to me. What kernel are you using? Did you do format before you changed to neat rom from ics rom??
Kernel is responsible for these actions.I had so many and also random freezes with DorimanX kernel...ahh ...Now I have Apolo Kernel and eveything is okay.No freezes,and awesome battery.Try out Apolo kernel And also do a factory reset,and don't install themes or mods...run it clean for a few days,see iif it still presists.
First, thank you both for your answers.
Then, my kernel is the one that goes with the NeatRom Lite version 4.8 : XWLSW-5.06.1-PhilZ.
I think my problem is a Sleep of Death too. Yes I did a wipe data, wipe cache, wipe dalvik cache, format system, and format preload before installing the Rom. Is it normal I have a SoD after I did all of this?
Else ok for the Kernel, I will try the Apolo. Is it ok to install it with the NeatRom lite 4.8 ?
Well you did the install ok so I dont see the problem philz kernel is good for neat rom. You should try apollo kernel reg first. But I would say test the rom with out the mods and then flash mods one by one. But like I said philz is good for neatrom. Try factory reset which will clear the mods and test it with philz first.
Ok thanks I will try that.
Just another question, is the Apex Launcher is considered as a "mod" and should I use the TW launcher some days instead, or can I still use the Apex Launcher (the freeze cannot come from this app) ?
I shouldn't think apex would cause this. Probably, clock widget is but not to sure.
I just noticed I had the debug mode activated on my phone (I don't know why? maybe I activate it by mistake? but I don't remember). Could the recurring Sleep of Death happens because of this?
Nope. SOD's are not caused by usb debugging. Follow andrewwright's advice, he knows what he's talking about.
Sent from a galaxy far, far away
simply go back to stock rom
Yes but ... no I like custom Roms, so I will try all I can before going back to a stock Rom
I did some research and I think this is not really SoD that happening to to my phone.
Effectively I read that SoD is the behavior in which the phone goes into "sleep" mode... typically screen off, and then won't wake up with power button.
However, when my lockscreen is frozen, I can still push the power button and access the power menu to reboot my phone, I don't have to remove the battery.
So if this is not a SoD, what is it?
So what did you try? If its still happening and it was me I would now format the lot,reinstall the rom with nothing on it. No mods and no apps and see if it happens again. So no apex no widget and no flashing of any mods. Then test that for two days. If problems are still there I would try a different rom to rule out software. I no neat is solid and so is philz kernel. Im
I changed the battery (it was recent, less than 1 year, but you never know, maybe defective).
I reinstalled the same rom, but with no mods, no themes, and no restoring apps from Titanium (but I installed them by downloading them by the Playstore).
Almost 2 days fine, but yesterday it froze again.
So now I will try to format, but before, do you think a scandisk plus a defragment on my SD Card could help?
Yes that help clear out any crap left over from different roms.
andrewwright said:
Yes that help clear out any crap left over from different roms.
Click to expand...
Click to collapse
I did a chkdsk/scandisk on my intern SD Card, and installed the last version of Philz kernel (5.11.2).
Atm, I still had no freeze. If I have one, I will try to format the lot and reinstall the rom with nothing on it as you said.
Fingers crossed mate :thumbup:
that`s happened with the problem with the base rom i mean the stock rom that`s i flashed with odin i changed it an every thing is ok now
I finally format my phone, not because I had freeze again, but because some of my app had strange behavior.
So now I just have the NeatROM Lite version 4.8 installed, with no mods nor theme. Waiting some days to see if it is still stable.
Hard thing to do if you have it set up the way you want but the best way mate. You should find neat Rom is solid. Do you have stock kernel? Philz?