Related
Hey, question. Every single CM from 6.0 I have downloaded I have had issues with. I love the rom, but every time I get the same issue. When I install the rom all worked fine. I wipe all data, clear cache, and have to reinstall of course everything, my issue is that my phone will randomly freeze. Sometimes I get an error message saying the process process.android has failed, other times it just freezes. Does anybody have any ideas?
I loved CM 6.1 best Rom I've had yet. But after a week it started acting up and having problematic auto shutdowns like 8 times a day. I then searched for another stock Rom and tried skyraider vanilla, I hate it. It's basically skinned sense. That's it. I enjoy sense but it eats battery. My favorite roms so far are the desire Hd Rom and
CM but without the shutdowns is be perfect.
Sent from my ADR6300 using XDA App
only people
So this is the only other person I have run into with this problem. Everybody else I have talked to over other forums or IRC has never heard of these issues at all.
The only time I've ever had those shut down issues is when I start screwing with themes or when I start screwing with kernels or overclocking. I'm not sure what you've got going on there though
Well...
Well I have done some of that however I have reverted to "stock" several times. I have Hboot .92 installed also, i saw something online. The latest radio is also installed. I guess has anybody else seen any issues like this?
Try formatting the system in addition to wiping. CM does not format anything when you flash it. In CWM its under mount sd section.
Sent from my Htc Incredible using XDA App
This happened to me today, I am 99% sure it was the kernel I had installed though. I put back invisiblek's #18 and had no problems before or after.
okay I can mess around with that and see what happens then.
justinmburrous said:
okay I can mess around with that and see what happens then.
Click to expand...
Click to collapse
Let us know please.
This morning, I d/l the cyanogen 6.1 stable from ROM Manager, I then rebooted my phone into hboot then into recovery console. I then did a wipe of dalvik and battery stats. I then did the wipe data and then the clear partition cache, I then flashed the Cyanogen 6.1 Inc rom... then went fine... I loaded up into Cyanogen I then did a reboot and that's when my phone would not leave the HTC Incredible screen when rebooting! any ideas that can help me? I really like the Cyanogen ROM
Help!!! please!
neur0tk said:
This morning, I d/l the cyanogen 6.1 stable from ROM Manager, I then rebooted my phone into hboot then into recovery console. I then did a wipe of dalvik and battery stats. I then did the wipe data and then the clear partition cache, I then flashed the Cyanogen 6.1 Inc rom... then went fine... I loaded up into Cyanogen I then did a reboot and that's when my phone would not leave the HTC Incredible screen when rebooting! any ideas that can help me? I really like the Cyanogen ROM
Help!!! please!
Click to expand...
Click to collapse
You need to be a little more specific but do this.
1. Click on the Cyanogen link in my signature and download it.
2. Download google apps
3. Reboot into recovery
4. Wipe Data/Factory Reset
5. Wipe Cache Partition
6. Wipe Dalvik Cache
7. Select install zip from SD card and choose the cyanogen ROM, let it install
8. Select install zip from SD card again and choose the google apps.
9. Reboot your phone and sign into your google account and let everything sync
This is the best way to do it. Not through ROM Manager.
If this doesn't work then I have absolutely no idea. That is the 100% correct way to flash a ROM.
neur0tk said:
This morning, I d/l the cyanogen 6.1 stable from ROM Manager, I then rebooted my phone into hboot then into recovery console. I then did a wipe of dalvik and battery stats. I then did the wipe data and then the clear partition cache, I then flashed the Cyanogen 6.1 Inc rom... then went fine... I loaded up into Cyanogen I then did a reboot and that's when my phone would not leave the HTC Incredible screen when rebooting! any ideas that can help me? I really like the Cyanogen ROM
Help!!! please!
Click to expand...
Click to collapse
I had to revert back to #18 kernel working fine now!
neur0tk said:
I had to revert back to #18 kernel working fine now!
Click to expand...
Click to collapse
Yeah I mentioned it earlier in this thread. For some reason #21 and #22 do not like cyanogen.
I'm running #21 on my phone and I haven't had any issues yet.
Yeah IDK either... I had to revert now it's running like a champ! love the Inexus theme!
ok an update, I have everything working. I an using cm6.1, latest radio (on cm site), kernel 27, hoot .92, and the very latest clockwork that just came out. I know those last two should not matter, just letting you know. As of right now my phone is not freezing and everything works fine, even faster than before. When I first turned it on the phone did freezer and after that yet took a long time for 3g to start working. On reinstall I did a total revert to stock then did a factory reset and cleared all caches and everything on the phone there is to clear. It has been afew hours. I will update this if there are any more problems
Sent from my ADR6300 using Tapatalk
Keeps rebooting more and more time to switch roms
Justinmburrous
Justinmburrous.com
hi, i have been reading up alot today on how to root and install a rom on my xoom, i rooted it fine then i went to the ics thread and downloaded the latest build, v17... put the zip on the sd card and went into recovery mode, choose to install zip from sd and installed it, then went to reboot device and it rebooted but came to a black screen that says android across the middle, its been on that screen for 20 mins now, help please lol
sorry... sorted problem, im guessing its bcos i wasnt installing google apps from zip too, sorry again
Honestly I have run into the same issues...hold down the volume up button + power...your Xoom should reboot.
Then you see the red Motorola logo wait 3 seconds and hit volume down...you should see "Android Recovery Mode" in the upper left corner.
Hit volume up to select....your device should enter recovery mode.
From here wipe data factory reset...wipe cache partition...then go to advanced...and wipe dalvik cache.
Then go to install zip from SD card and reinstall the ROM and Gapps and you should be fine, the first boot can take up to 10 minutes so don't panic...
XOOM Running Team EOS latest ICS build v.17 OC'd @ 1.5Ghz
Sent from my DROIDX using xda premium
Haha never mind...glad you got it working...disregard my previous post ; )
Sent from my DROIDX using xda premium
Boarder277 said:
Haha never mind...glad you got it working...disregard my previous post ; )
Sent from my DROIDX using xda premium
Click to expand...
Click to collapse
No, don't be sorry. That was a great explanation.
I know you got it fixed but I will say this:
Always do a full wipe when flashing a new rom. In this case, the ICS build was a new ROM and you should have wiped.
Usually you do not need to do a full wipe if you are just flashing a new build of the same ROM (if you go to a new nightly for instance). Just need to clear cache/delvik and reinstall gapps.
ok i am learning, i have my bravo rooted now, i have the ginger break on there and all i put the cm-72 nightly rom on the sd card. i booted up with the blue led and held volume down and this is what i got, reboot,boot,system,recovery ,tools and shutdown. how do i get to the sd card for the rom. i dont want to screw up . also is that a stable rom.
You need to install 2nd init defy recovery first. Go here:
http://forum.xda-developers.com/showthread.php?t=1599672
Then go here to figure out how to flash cm7.2:
http://forum.xda-developers.com/showthread.php?t=1595963
Most of the info should be there, don't forget to thank the author for their hard work!
Sent from my MB520 using xda app-developers app
Dr. Orange said:
You need to install 2nd init defy recovery first. Go here:
http://forum.xda-developers.com/showthread.php?t=1599672
Then go here to figure out how to flash cm7.2:
http://forum.xda-developers.com/showthread.php?t=1595963
Most of the info should be there, don't forget to thank the author for their hard work!
Sent from my MB520 using xda app-developers app
Click to expand...
Click to collapse
Yeah, pretty much that.
To answer your other question, yes, that nightly is a stable rom.
I also ported a CM9 release from yesterday over to the Bravo and its working really well in the initial first 24 hours. I'm also an ass who didn't post install instructions either, but they're the same as CM7's which is to install 2nd init, reboot to recovery, wipe data/factory reset, flash rom, flash gapps, reboot. If you're going inbetween releases (like cm7 0605 to say 0610) then all you have to do is wipe cache, wipe dalvik cache, flash rom, flash gapps, reboot.
And if you didn't know, skeevy420 is a freakin' boss and will help with everything you need.
Sent from my Bravo using XDA: Freshmaker
Hi Guys,
I am trying to change my ROM from Criskelo 5.1 (has speedmod kernel but dont think that should make a difference) to LiquidSmooth 3.2. Usually this is a pretty straight froward process but for some reason I just cant get past CWM. Here is what I've done so far.
Reboot into recovery.
Flash AbyssNote 3.2 (redtouch) and reboot into AybssNote.
Wipe everyting (inlcuding dalvik and battery)
Flash LiquidSmooth 3.2
On doing this the phone restarts - as is expected - but then it just reboots in CWM. I've tried various permutations of this (even tried wipes from CWM before going into Abyss) in the hope that it might work but nothing seems to work. Before this I tried to go Criskelo 5 to 8 and got stuck on boot screen.
Thanks God for nandroid or this would have become an extremely frustrating experience. Any ideas ?
EDIT: Used AbyssNote 4.2 and not 3.2 .... sorry about that
tariqsaleem said:
Hi Guys,
I am trying to change my ROM from Criskelo 5.1 (has speedmod kernel but dont think that should make a difference) to LiquidSmooth 3.2. Usually this is a pretty straight froward process but for some reason I just cant get past CWM. Here is what I've done so far.
Reboot into recovery.
Flash AbyssNote 3.2 (redtouch) and reboot into AybssNote.
Wipe everyting (inlcuding dalvik and battery)
Flash LiquidSmooth 3.2
On doing this the phone restarts - as is expected - but then it just reboots in CWM. I've tried various permutations of this (even tried wipes from CWM before going into Abyss) in the hope that it might work but nothing seems to work. Before this I tried to go Criskelo 5 to 8 and got stuck on boot screen.
Thanks God for nandroid or this would have become an extremely frustrating experience. Any ideas ?
Click to expand...
Click to collapse
Bump .... anyone ?
Get a stock gb rom and flash via pc odin.
Sent from my GT-N7000 using xda app-developers app
tariqsaleem said:
Bump .... anyone ?
Click to expand...
Click to collapse
Have you try other ROM besides LiquidSmooth? Since it stuck in CWM, I suspect the installation script for LiquidSmooth is not compatible with Abyss 3.2 CWM.
praetorius said:
Get a stock gb rom and flash via pc odin.
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
I was hoping you wouldn't say that .... I have a really slow net connection at the moment and don't have any GB stock roms saved (next time I'll think twice before I delete stuff ). Is there any other way I can do this or is this the only option I have ?
lenrek said:
Have you try other ROM besides LiquidSmooth? Since it stuck in CWM, I suspect the installation script for LiquidSmooth is not compatible with Abyss 3.2 CWM.
Click to expand...
Click to collapse
I tried to update to Criskelo v8 and in that case I got stuck on the boot screen. Had to do a hard reset and get back into recovery manually.
Sorry about the confusion, I actually used Abyss 4.2 (which I got from the Liquid Smooth thread) so I don't think there should be any compatibility issues.
Go back to abyss42 and factory reset from within abyss42 (red menu). Also do cache and dalvik wipe.
Reinstall your custom rom.
And since you have a slow connection, there is a chance your files are corrupt.
Sent from my GT-N7000 using xda app-developers app
Do a unzip -t <zipfile> to verify the file is not corrupted. As above post stated, it maybe a corrupted zip file.
praetorius said:
Go back to abyss42 and factory reset from within abyss42 (red menu). Also do cache and dalvik wipe.
Reinstall your custom rom.
And since you have a slow connection, there is a chance your files are corrupt.
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
Did all of that i.e Factory reset from within Abyss42, clear cache and dalvik wipe.
I guess I'll try downloading again but why I doubt that would fix anything since this is the 2nd ROM I've had the same issue with. Well not exactly same, in the case of Criskelo 8 it gets stuck on boot screen where as with liquid smooth 3.2 it keeps going back into CWM . Still worth a try though. will update tonight once I get to download again.
Anyway of verifying whether my files are corrupt or not ?
lenrek said:
Do a unzip -t <zipfile> to verify the file is not corrupted. As above post stated, it maybe a corrupted zip file.
Click to expand...
Click to collapse
Thanks...I'll give that a go later today. Currently the rom in on my phone. Can I do something similar via the terminal on my mobile ?
tariqsaleem said:
Thanks...I'll give that a go later today. Currently the rom in on my phone. Can I do something similar via the terminal on my mobile ?
Click to expand...
Click to collapse
Is a zip file, so just get one of those app that can open zip/compressed file from the Google Play. I use AndroZip, FYI. I believe there are more choices in Google Play.
lenrek said:
Is a zip file, so just get one of those app that can open zip/compressed file from the Google Play. I use AndroZip, FYI. I believe there are more choices in Google Play.
Click to expand...
Click to collapse
Tried to open it with ES Zip Viewer and it opens up without any issues, so does that mean that the file is not corrupted ?
tariqsaleem said:
Anyway of verifying whether my files are corrupt or not ?
Click to expand...
Click to collapse
check for MD5 checksum
try abyss 3.9
my phone stuck on bootanimation endlessly with Liquid black 3.2, i was using abysss 4.2 with red interface, i moved on to asylum
rraaka said:
try abyss 3.9
my phone stuck on bootanimation endlessly with Liquid black 3.2, i was using abysss 4.2 with red interface, i moved on to asylum
Click to expand...
Click to collapse
Tried flashing with abyss 3.9 but still have the same issue. The phone reboots into CWM
For the benefit of others....went back to stock Samsung GB image and flashed paranoid android from there and it worked
Sent from my GT-N7000 using xda app-developers app
Hi everyone,
some time ago I flashed a wrong sbf to my Defy and thanks to the All-in-One Defy Beginner's guide
Zephyrot said:
Installed full Gingerbread SBF and can’t go back to another rom: (!) aha! We have a issue here!, latest Stock Gingerbread full SBFs comes with a Version 5 of the CG, meaning until not long ago you were pretty much screwed. But wait, there is hope! A one kind Éclair has been found in China Defys that comes with Version 5 CG!.
How to fix it:
Method 1:
Download this SBF and Flash it
Root your Phone
Download 2nd Init 1.4.2 and Install ClockworkMod Recovery
Download and install this Nandroid Backup << File is Back, thanks Ichibanme again!>>
Enter Recovery, Wipe Data/Cache
After wiping, turn off your phone
Turn it on and get immediately into Bootloader mode
Flash this Fixed SBF
Delete Data/Cache again and reboot.
**NOTE*: I just rephrased the original post since it can be a bit confusing, it is linked as source below.
**NOTE2**: If you are using a non-Chinese defy, DO NOT USE THE CAMERA FLASH while on the Chinese rom, it WILL kill your LED.
Source: ((Original post here))[
Method 2: (BIG thanks to Jebrew again for this one)
NOTE: You are going to need CM7 for this one. CM7 Stable version recommended.
Download this SBF and Flash it.
Root your phone.
Download 2nd Init 1.4.2 and Install ClockworkMod Recovery.
Reboot to CMW recovery, and wipe Data/Cache.
Install CM7 then install Google Apps.
Reboot an go into Stock Recovery (using the vol- button, not from Bootmenu).
Do a Data/Cache Wipe or you won't have any space when you're done.
Flash this Fixed SBF
Reboot into your nice new rom.
Do not Wipe Data anymore or you will have to start again.
You WONT be able to install full SBFs of any Éclair or Froyo since these Androids have lower CG Versions.
Click to expand...
Click to collapse
I'm running CM7 again with a version 5 CG, if I got it right.
So far so good. But now I need to update my ROM to be able to update some apps that won't run on CM7.
So what's the best tactic for updating this messed up phone? Just flashing any CM10+ ROM (I tried several ones) didn't seem to work. I always got stucked at the red Motorola 'M'.
Any ideas?
Thanks a lot!
Cheers,
Martin
smashedup said:
I always got stucked at the red Motorola 'M'
Click to expand...
Click to collapse
factory reset
Thanks for your reply.
Besides the fact that I can't go anywhere to do a factory reset as soon as I've updated to something like CM10, I do a lot of resets/wipes on my way to this state (see quoted guide above).
smashedup said:
Thanks for your reply.
Besides the fact that I can't go anywhere to do a factory reset as soon as I've updated to something like CM10, I do a lot of resets/wipes on my way to this state (see quoted guide above).
Click to expand...
Click to collapse
Use Defy full wiper/AROMA wiper to wipe system, data and cache with EXT4. Then immediately flash CM10 and gapps.
hotdog125 said:
Use Defy full wiper/AROMA wiper to wipe system, data and cache with EXT4. Then immediately flash CM10 and gapps.
Click to expand...
Click to collapse
Tried that, but now I always get a Status 7 error message when trying to install (no matter if I wipe with Aroma or in CWM). I found a lot of people with that same problem but no solution for me... I'm wondering why I did not have that status 7 thing before....
smashedup said:
Tried that, but now I always get a Status 7 error message when trying to install (no matter if I wipe with Aroma or in CWM). I found a lot of people with that same problem but no solution for me... I'm wondering why I did not have that status 7 thing before....
Click to expand...
Click to collapse
For some users flashing DFP-231 helped.
Sent from my Nexus 7 using Tapatalk
hotdog125 said:
For some users flashing DFP-231 helped.
Click to expand...
Click to collapse
Thanks for the hint!
But this is a Defy+ sbf and after flashing I might not be able to go back, or not?
From the thread [Q] defy bricked, not even JORDN_U3_97.21.51.sbf helps :
kirov1045 said:
what are the chances it will work? i'll scared i'll totally brick it. it's 100% not a defy+
Click to expand...
Click to collapse
thekguy said:
Zero percent chance of bricking
Only problem is that there may be problems in the stock rom, which can be fixed by installing cm10 or cm10.1
By problem I mean no camera or battery not charging to the full level but again these can be fixed by upgrading to cm10 or 10.1
Click to expand...
Click to collapse
If - for any reason - CM10+ does not work for me, I don't want to deal with these issues...
Or am I getting this wrong?
smashedup said:
Thanks for the hint!
But this is a Defy+ sbf and after flashing I might not be able to go back, or not?
From the thread [Q] defy bricked, not even JORDN_U3_97.21.51.sbf helps :
If - for any reason - CM10+ does not work for me, I don't want to deal with these issues...
Or am I getting this wrong?
Click to expand...
Click to collapse
Well, it helped some people. You can't go back to 2.2 after flashing GB.
Sent from my Nexus 7 using Tapatalk
hotdog125 said:
Well, it helped some people. You can't go back to 2.2 after flashing GB.
Click to expand...
Click to collapse
Thanks for clarifying.
But I just decided to not mess around another time and will stick to my well running CM7.2 for this device. I found a workaround for my app-prob anyway.
Thanks again for help!