CyanogenMod is a free, community built, aftermarket firmware distribution of Android 2.3 (Gingerbread), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Instructions:
First time flashing CyanogenMod 7 to the Motorola Droid 2 Global, or coming from another ROM?
Root the device and install ClockworkMod Recovery. Instructions are available here.
Perform a NANDroid backup of your current ROM.
Format the system, data & cache partitions of your device.
Perform a factory reset.
Flash CyanogenMod.
Optional: Install the Google Apps addon package.
Upgrading from earlier version of CyanogenMod 7?
Perform a NANDroid backup of your current ROM.
Flash CyanogenMod (your Google Apps will be backed up & restored automatically).
Issues?
Experience issues? Please provide the following info:
If the device was hard reboot, please provide the file "/proc/last_kmsg".
If the device was soft reboot or is "bootlooping", please run a logcat and provide the full output.
Please use Pastebin when possible.
Download Links:
Official post
CyanogenMod:
Latest version: update-cm-7.1.0-DROID2WE
Download: link
Mirror: link
MD5sum: 96fc1288449d9f6dd468efd4fc509f39
Google Apps addon:
Version: gapps-gb-20110828
Mirror: link
Mirror: link
Version: Google Talk with video addon
Mirror: link
Mirror: link
The CyanogenMod team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
First!!
Haha,
Do we need to flash to Gingerbread .SBF first??
Or is going from stock rooted to this ok?
Bugs so far:
**Edit. Went fine going from stock. However I do not get Any usb mode connection when connecting the usb cable??
-Alt Lock on keyboard does not work?
FYI - the link to the office post is broken
what the hell!!
update complate.. but
I korean korea use cdma 3G
go to cdma. forace working airplane mode and err phone
what the hell!!
USB not working
Just installed and USB is not working for me either. Anyone found a solution for this?
stays stuck at m logo for me
Me two. Red M, stuck. I didn't do a factory reset though (step 4). How do I boot into recovery?
Edit: Got into regular recovery, factory reset, wiped cache, still stuck on red M. Did a nandroid backup before attempting to install, but I can't get into CWM to restore it.
HELP!
None of the info on the CM7 website seems to say they have a version for the D2G(WE). I sure hope we do get some CM7 love.
Overall I am happy with Venus for now....
Installed via rom manager, wiped data, and dalvik cache, and it threw me into a bootloop. cannot boot into stock recovery to flash the backup
what button combo will boot me into CWM, or what can i flash via bootloader
ive never had problems with htc or samsungs, this is the first moto ive worked on, its a friends.
Windst said:
Installed via rom manager, wiped data, and dalvik cache, and it threw me into a bootloop. cannot boot into stock recovery to flash the backup
what button combo will boot me into CWM, or what can i flash via bootloader
ive never had problems with htc or samsungs, this is the first moto ive worked on, its a friends.
Click to expand...
Click to collapse
You can always flash the .sbf stock image using Rsd Lite.
2.4.29 SBF Download - http://www.megaupload.com/?d=MD5K1YY8
RSDlite 5.0 DOWNLOAD http://www.megaupload.com/?d=BCA2LDFX
Pass: alabama
If you are not familiar on how to use RSDLite here is a brief overview
Method 1: While phone is on
Switch your device to PC mode
Turn on debugging mode (settings>applications>development>debugging mode)
Launch RSDLite (make sure device appears in window)
Select SBF
Start
Device will switch to bootloader and begin the flashing process and will reboot when it is complete.
Method 2: While phone is off
To manually put your device in bootloader mode:
Turn off device
press and hold the up and down volume buttons
power on device (continue to hold the up and down volume buttons)
wala - you are in bootloader mode
Launch RSDLite (make sure device appears in window)
Select SBF
Start
Usb enable
texas-saluki said:
Just installed and USB is not working for me either. Anyone found a solution for this?
Click to expand...
Click to collapse
Good for those who do not recognize it as mass storage, yesterday restart the cell with the data cable connected to the computer and when I start my usb recognized as mass storage. Hopefully this info will serve. but hopefully the developers fix this little problem. In the rest of me is going great rom.
Are you all sure this is a rom for driod 2 global and not droid 2 because if you look on CyanogenMod web site there is no mention of droid 2 global. This rom is for 2.2 and not 2.3.
I wouldnt update to this rom if you are a D2G until this is confirmed with CyanogenMod people.
kurpter said:
Are you all sure this is a rom for driod 2 global and not droid 2 because if you look on CyanogenMod web site there is no mention of droid 2 global. This rom is for 2.2 and not 2.3.
I wouldnt update to this rom if you are a D2G until this is confirmed with CyanogenMod people.
Click to expand...
Click to collapse
Dev thread: http://rootzwiki.com/showthread.php?3546-DEV_THREAD-Droid-2-Global-CM7-with-Gingerbread-Leak-Kernel
Sorry, but even searching through the internet there is one point I'm still missing..
has the D2G bootloader been unlocked with the official GB update (like the Atrix) or not?
If you install using rom manager you have to install the recovery from rom manager which in my experience over-rides boot strap. With that said, I was unable to use the backup made with the CWM recovery nandroid. When installing via rom manager, it doesnt seem to wipe correctly and I was stuck at the "M" logo. I pulled the batter, held power and x until the little droid symbol showed up then hit the search button to boot into stock recovery. Wiped data and cache from there and CM booted up just fine.
The problem I am having is once I am in CM I can no longer use Boot strap recovery and make nandroids so essentially I am stuck. The rom manager cwm doesnt create usable nandroids and once i reinstall bootstrap in CM and flash bootstrap recovery I end up stuck at the M symbol at which wiping in stock recovery will not allow me to boot back up and have to SBF all the way back to stock
Something is broke but I cannot determine what.
I tried installing this and got stuck on red M.
How does one access CWM? all my attempts have taken me to stock recovery....
Can somebody tell me if Cyanogen is installed with its own kernel or if it runs on Motorola signed Gingerbread kernel?
In other words.. I ask again, is D2G bootloader unloked like Droid and Atrix or not?
phoenixs4r said:
I tried installing this and got stuck on red M.
How does one access CWM? all my attempts have taken me to stock recovery....
Click to expand...
Click to collapse
Hate to be "That guy" and quote myself, but since this wasn't my phone, I couldn't waste a bunch of time. I had to SBF back to stock and do the OTA back to gingerbread. I don't know what went wrong exactly, but I couldn't get into recovery. Maybe cause I updated recovery via rom manager? I don't quite know.
as a heads up, the rootzwiki link is for the build using the GB kernel (leaked, or ota), and the one from the official cmod site (listed under "cdma_droid2we" on the cyanogen download site, sorry cant post links til i get 8 posts!) is using the froyo codebase. if you're on .330 or below, use the offical cm build, if you've already got gingerbread from moto, then use the rootzwiki dev thread version!
This is for the froyo kernel, if you want to use it you'll need to sbf back to 2.2. Although I'd would say go to the rootzwiki thread for the gingerbread version and use that, it works a lot better, except for gsm is flaky. Oh and if you have GB you can just use Rom Toolbox and download it there.
Related
Can someone please help me. I just rooted the Samsung fascinate and had a problem with installing CWM. I flashed it via rom manager and it wouldnt let me do a nandroid so I then installed the CWM red via odin and was able to make my nandroid backup fine.
I wanted to theme the phone.apk gradient backgrounds and did so using ninjamorph. I put in my new background files and rebooted and everything was fine. The phone.apk would call out but when I would end a call it would force close. I decided I wanted to restore my backup so via rom manager I selected reboot into recovery. The phone rebooted and got stuck at the Samsung Logo screen and has been.
Ive pulled the battery and tried to boot again normall but it remains stuck at the logo. I let the phone sit for over 30 min and nothing happened. Am I bricked? If so, how do I fix the phone? I just need to get into recovery to restore my nandroid backup. Please someone help?
Sorry if this is a stupid question but did you already try holding volume up and down after pulling the battery and holding power?
Sent from my SCH-I500 using XDA Premium App
dgwood12 said:
Can someone please help me. I just rooted the Samsung fascinate and had a problem with installing CWM. I flashed it via rom manager and it wouldnt let me do a nandroid so I then installed the CWM red via odin and was able to make my nandroid backup fine.
I wanted to theme the phone.apk gradient backgrounds and did so using ninjamorph. I put in my new background files and rebooted and everything was fine. The phone.apk would call out but when I would end a call it would force close. I decided I wanted to restore my backup so via rom manager I selected reboot into recovery. The phone rebooted and got stuck at the Samsung Logo screen and has been.
Ive pulled the battery and tried to boot again normall but it remains stuck at the logo. I let the phone sit for over 30 min and nothing happened. Am I bricked? If so, how do I fix the phone? I just need to get into recovery to restore my nandroid backup. Please someone help?
Click to expand...
Click to collapse
If you are unable to get into recovery, then you will have to odin back to stock.
As stated above, holding vol up + vol down + power (Until you see the logo pop up) should take you there. If that doesn't work, Odin is now your new best friend.
ClockWorkMod 3.x.x Doesn't Play Well with the Samsung Fascinate
USB Port Got Confused
I am having much the same problem. I still haven't gotten a working solution. But, I thought I'd put together in one place all the Information that I've found so far regarding this problem from other users on the XDA Forums. The USB Port on my Fascinate seems to have gotten confused. When I connect to Computer, the Computer Doesn't Recognize the Fascinate. And when I connect via USB to an AC Outlet and Hold Volume Down key, only then can I access the Yellow DownLoading Screen that Odin needs. However, the Computer still won't Recognize the Fascinate, so I Can't get Odin to find the Fascinate to do a return to a Stock ROM.
My Facinate seems to need ClockWorkMod Version 2.5.1.2, but I can't access the USB Port to Change this, so the StartUp Screen Shows "SAMSUNG", unless I use the "Recovery_UpDate.zip" made with ClockWorkMod, but then Hangs at the ClockWorkMod Logo, (the Hat and Orange Circle). Reasons for this hang are given below. Any Help you send me also would also be appreciated.
The USB Port seemed to have gotten Confused when the Computer wanted to Install Verizon Wireless Software Utility Application for Android - Samsung to make my Computer Communicate better with the Fascinate and I Declined this option. I have more than one Computer and on the other Computer I Accepted, and although I don't use the VZ Media Manager, it didn't interfere with the Cell Phone Communicating with the Computer, and must be a Help.
All of the Following is Copied, so when it reads, "in my testing" or "I highly recommend", please understand that these are not my Words or Expertise, but are copied from the Link Below the Paragraph. Also, I found that if the Screen Freezes on ReBoot that if the Menu Button is Pushed, {Bottom Left Corner ~ Pop-Up Menu Icon ~ Looks like Paper Coming out of a Printer), it will Toggle to another Menu to see the UnderLying Reasons for Incompletion, (ie... Signature Not Recognized, etc.).
* * * * *
ClockworkMod Version 3.0.2.5
Please note: Some People have had the Samsung Recovery appear after this Flash, and in my testing, in some circumstances, the Stock Kernel can actually Flash back the Stock Recovery. Due to this, I highly recommend that anyone flashing the new CWM with this Flash, please also Flash my Clean Kernel, located here: Clean Kernel EC05 1.03d thread Also note, that the One Click Version of this should not have this problem, since it takes away the ability of the Stock Kernel to Flash the Samsung Recovery.
http://forum.xda-developers.com/showthread.php?t=1074324
* * * * *
ROM Manager
{New Users ~ ROM Manager is the Name of an Application that can be DownLoaded from the Android Market that can Flash ClockWorkMod}.
Samsung Users: You must Flash a ClockWork Compatible Kernel First (see XDA forums)
http://forum.xda-developers.com/showthread.php?t=1074324
* * * * *
Note, using Reboot Recovery or ADB Reboot Recovery will take you to a "Stock" Recovery. Simply Apply the UpDate.zip on your SD card and ClockWorkMod will start up. (This method is better known as FakeFlash)
http://forum.xda-developers.com/showthread.php?t=788251
* * * * *
ClockWorkMod Version 2.5.1.2 ~
At the moment the Latest Versions of ClockWorkMod Recovery are Orange with Build Numbers 3.x.x. Unfortunatley this CAN NOT be used because in order to install any Flashable .zip file a script of code is required to direct the installation. At the moment almost everything written for Fascinate has been written in a language called Amend. The most recent version 3.x.x ONLY Accepts a Language called Edify, in Previous Versions of Clockwork (anything under 3.x.x) were Compatible with both Amend and Edify.
http://forum.androidcentral.com/ver...-clockworkmod-recovery-w-screen-captures.html
* * * * *
ClockWorkMod Compatible Kernel and ROM Manager Support
[Recovery] ClockWorkMod 3.0.2.5 Upgrade RFS - Ext4 Compatible!!! - XDA-Developers
CWM3.0.2.5.zip
http://forum.xda-developers.com/showthread.php?t=1074324
* * * * *
CWM3.0.2.5_Reboot_Recovery_&_Rom_Manager
DRockstar.Clean.Kernel.EC05.v1.04.zip
[Kernel][GPL]Clean Kernel Ec05 V1.04 Cwm3.0.2.5 Reboot Recovery & Rom Manager!!! - XDA-Developers
http://forum.xda-developers.com/showthread.php?t=1053252
* * * * *
How to Restore you Samsung Fascinate to Factory?
http://www.nyneaxis.com/2010/11/how-to-restore-you-samsung-fascinate-to-factory/
JollyChollie said:
USB Port Got Confused
I am having much the same problem. I still haven't gotten a working solution. But, I thought I'd put together in one place all the Information that I've found so far regarding this problem from other users on the XDA Forums. The USB Port on my Fascinate seems to have gotten confused. When I connect to Computer, the Computer Doesn't Recognize the Fascinate. And when I connect via USB to an AC Outlet and Hold Volume Down key, only then can I access the Yellow DownLoading Screen that Odin needs.
My Facinate seems to need ClockWorkMod Version 2.5.1.2, but I can't access the USB Port to Change this, so the StartUp Screen Shows "SAMSUNG", unless I use the "Recovery_UpDate.zip" made with ClockWorkMod, but then Hangs at the ClockWorkMod Logo, (the Hat and Orange Circle). Reasons for this hang are given below. Any Help you send me also would also be appreciated.
The USB Port seemed to have gotten Confused when the Computer wanted to Install Verizion Wireless' Verizon Wireless Software Utility Application for Android - Samsung to make my Computer Communicate better with the Fascincate and I Declined this. I have more than one Computer and on the other Computer I Accepted and although I don't use the VZ Media Manager, it didn't interfer with the Cell Phone Communicating with the Computer and must be a Help.
All of the Following is Copied, so when it reads, "in my testing" or "I highly recommend", please understand that these are not my Words or Expertise, but are copied from the Link Below the Paragraph.
* * * * *
ClockworkMod Version 3.0.2.5
Please note: Some People have had the Samsung Recovery appear after this Flash, and in my testing, in some circumstances, the Stock Kernel can actually Flash back the Stock Recovery. Due to this, I highly recommend that anyone flashing the new CWM with this Flash, please also Flash my Clean Kernel, located here: Clean Kernel EC05 1.03d thread Also note, that the One Click Version of this should not have this problem, since it takes away the ability of the Stock Kernel to Flash the Samsung Recovery.
http://forum.xda-developers.com/showthread.php?t=1074324
* * * * *
ROM Manager
Samsung Users: You must Flash a Clockwork Compatible Kernel First (see XDA forums)
http://forum.xda-developers.com/showthread.php?t=1074324
* * * * *
Note, using Reboot Recovery or ADB Reboot Recovery will take you to a "Stock" Recovery. Simply Apply the UpDate.zip on your SD card and ClockWorkMod will start up. (This method is better known as FakeFlash)
http://forum.xda-developers.com/showthread.php?t=788251
* * * * *
ClockWorkMod Version 2.5.1.2 ~
At the moment the Latest Versions of ClockWorkMod Recovery are Orange with Build Numbers 3.x.x. Unfortunatley this CAN NOT be used because in order to install any Flashable .zip file a script of code is required to direct the installation. At the moment almost everything written for Fascinate has been written in a language called Amend. The most recent version 3.x.x ONLY Accepts a Language called Edify, in Previous Versions of Clockwork (anything under 3.x.x) were Compatible with both Amend and Edify.
http://forum.androidcentral.com/ver...-clockworkmod-recovery-w-screen-captures.html
* * * * *
ClockWorkMod Compatible Kernel and ROM Manager Support
[Recovery] ClockWorkMod 3.0.2.5 Upgrade RFS - Ext4 Compatible!!! - XDA-Developers
CWM3.0.2.5.zip
http://forum.xda-developers.com/showthread.php?t=1074324
* * * * *
CWM3.0.2.5_Reboot_Recovery_&_Rom_Manager
DRockstar.Clean.Kernel.EC05.v1.04.zip
[Kernel][GPL]Clean Kernel Ec05 V1.04 Cwm3.0.2.5 Reboot Recovery & Rom Manager!!! - XDA-Developers
http://forum.xda-developers.com/showthread.php?t=1053252
* * * * *
How to Restore you Samsung Fascinate to Factory?
http://www.nyneaxis.com/2010/11/how-to-restore-you-samsung-fascinate-to-factory/
Click to expand...
Click to collapse
You Know all of those links are for Epic 4g right??
Fascinate doesn't like Rom Manager as well.
For OP
Just Odin back to Stock and work your way up.
JollyChollie said:
USB Port Got Confused
I am having much the same problem. I still haven't gotten a working solution. But, I thought I'd put together in one place all the Information that I've found so far regarding this problem from other users on the XDA Forums. The USB Port on my Fascinate seems to have gotten confused. When I connect to Computer, the Computer Doesn't Recognize the Fascinate. And when I connect via USB to an AC Outlet and Hold Volume Down key, only then can I access the Yellow DownLoading Screen that Odin needs. However, the Computer still won't Recognize the Fascinate, so I Can't get Odin to find the Fascinate to do a return to a Stock ROM.
My Facinate seems to need ClockWorkMod Version 2.5.1.2, but I can't access the USB Port to Change this, so the StartUp Screen Shows "SAMSUNG", unless I use the "Recovery_UpDate.zip" made with ClockWorkMod, but then Hangs at the ClockWorkMod Logo, (the Hat and Orange Circle). Reasons for this hang are given below. Any Help you send me also would also be appreciated.
The USB Port seemed to have gotten Confused when the Computer wanted to Install Verizon Wireless Software Utility Application for Android - Samsung to make my Computer Communicate better with the Fascinate and I Declined this option. I have more than one Computer and on the other Computer I Accepted, and although I don't use the VZ Media Manager, it didn't interfere with the Cell Phone Communicating with the Computer, and must be a Help.
All of the Following is Copied, so when it reads, "in my testing" or "I highly recommend", please understand that these are not my Words or Expertise, but are copied from the Link Below the Paragraph.
* * * * *
ClockworkMod Version 3.0.2.5
Please note: Some People have had the Samsung Recovery appear after this Flash, and in my testing, in some circumstances, the Stock Kernel can actually Flash back the Stock Recovery. Due to this, I highly recommend that anyone flashing the new CWM with this Flash, please also Flash my Clean Kernel, located here: Clean Kernel EC05 1.03d thread Also note, that the One Click Version of this should not have this problem, since it takes away the ability of the Stock Kernel to Flash the Samsung Recovery.
http://forum.xda-developers.com/showthread.php?t=1074324
* * * * *
ROM Manager
{New Users ~ ROM Manager is the Name of an Application that can be DownLoaded from the Android Market that can Flash ClockWorkMod}.
Samsung Users: You must Flash a ClockWork Compatible Kernel First (see XDA forums)
http://forum.xda-developers.com/showthread.php?t=1074324
* * * * *
Note, using Reboot Recovery or ADB Reboot Recovery will take you to a "Stock" Recovery. Simply Apply the UpDate.zip on your SD card and ClockWorkMod will start up. (This method is better known as FakeFlash)
http://forum.xda-developers.com/showthread.php?t=788251
* * * * *
ClockWorkMod Version 2.5.1.2 ~
At the moment the Latest Versions of ClockWorkMod Recovery are Orange with Build Numbers 3.x.x. Unfortunatley this CAN NOT be used because in order to install any Flashable .zip file a script of code is required to direct the installation. At the moment almost everything written for Fascinate has been written in a language called Amend. The most recent version 3.x.x ONLY Accepts a Language called Edify, in Previous Versions of Clockwork (anything under 3.x.x) were Compatible with both Amend and Edify.
http://forum.androidcentral.com/ver...-clockworkmod-recovery-w-screen-captures.html
* * * * *
ClockWorkMod Compatible Kernel and ROM Manager Support
[Recovery] ClockWorkMod 3.0.2.5 Upgrade RFS - Ext4 Compatible!!! - XDA-Developers
CWM3.0.2.5.zip
http://forum.xda-developers.com/showthread.php?t=1074324
* * * * *
CWM3.0.2.5_Reboot_Recovery_&_Rom_Manager
DRockstar.Clean.Kernel.EC05.v1.04.zip
[Kernel][GPL]Clean Kernel Ec05 V1.04 Cwm3.0.2.5 Reboot Recovery & Rom Manager!!! - XDA-Developers
http://forum.xda-developers.com/showthread.php?t=1053252
* * * * *
How to Restore you Samsung Fascinate to Factory?
http://www.nyneaxis.com/2010/11/how-to-restore-you-samsung-fascinate-to-factory/
Click to expand...
Click to collapse
If your phone is rooted, ODIN your way to this ROM.
http://forum.androidcentral.com/ver...tom-roms-w-root-clockwork-updated-3-25-a.html
From there you can be voodoo converted or not, your choice. I would choose to be converted, FYI. From there you can upgrade your CWM using ODIN. Here is the latest CWM that I use.
http://forum.xda-developers.com/showthread.php?t=1046905
Now from there, DON'T use ROM Manager. I will say it again so you get the point. DON'T use ROM Manager. Download all your ROMs or Kernels for the Fascinate here and read about them. You will learn a lot and knowledge is power. I know I have learned a lot and now wish I didn't pay for ROM manager when I got started in this fun game.
A list of all the ROMs and Kernels is here.
http://forum.xda-developers.com/showthread.php?t=1013312
The Fasinate has two main types of ROMS. AOSP and Touchwiz. Touchwiz is what the phone was shipped with and has a lot of development done on it. It is favored a lot because everything generally works. AOSP is faster and Google's original source code modified to work on our phones. Not everything works however. We do have great developers that work on our phones and they have a great IRC channel to you can ask questions on about their ROMs.
This thread is from march..
good day.
chopper the dog said:
This thread is from march..
good day.
Click to expand...
Click to collapse
The thread originally is, however, the recent post has another person asking the same question because he couldn't get the answer he needed.
When I try to download the ROM from ROM manager, it tells me that I need install Clockworkmod Recovery, but when I pressed install, it came up with a Confirm Phone Model page which does not have Galaxy 5 as a option. So I am now just stuck here, what should I do, or is the free version of ROM manager pure not very useful?
hozza94 said:
When I try to download the ROM from ROM manager, it tells me that I need install Clockworkmod Recovery, but when I pressed install, it came up with a Confirm Phone Model page which does not have Galaxy 5 as a option. So I am now just stuck here, what should I do, or is the free version of ROM manager pure not very useful?
Click to expand...
Click to collapse
did you root your phone?
what rom are you actually using?
did you try to update Rom Manager to an earlier version?
I assume your phone is rooted already. Don't continue if it's not.
I thought there was an official one released for the phone. Are you using the newest version of ROM Manager?
If yes, and our phone model is still not listed, then you'll need to install Clockworkmod Recovery by following this thread:
http://forum.xda-developers.com/showthread.php?t=1151396
It involves downloading a program called ODIN. You need to flash (transfer) the Clockworkmod file to your phone through USB. It's all in the thread above.
I had the same problem - installing the latest Rom Manager (free version) from the store didn't have Galaxy5 listed as a ClockworkMod possibility.
I flashed the whole thing by hand with ODIN and installed CyanogenMod - and presto; the version supplied with it had Galaxy5 support and I had no problem doing the "read only partition" installation.
Rom Manager is pretty crappy anyway - I prefer manual installation over it...
DO NOT - i repeat - DO NOT USE ROM MANAGER.
Theres no compatible version of CWMR it does offer. Flashing any of the other versions, which are made for other phones, might brick your device to the state that Im currently trying to revert (d/l mode only, but seemingly unflashable).
Rigardi said:
DO NOT - i repeat - DO NOT USE ROM MANAGER.
Theres no compatible version of CWMR it does offer. Flashing any of the other versions, which are made for other phones, might brick your device to the state that Im currently trying to revert (d/l mode only, but seemingly unflashable).
Click to expand...
Click to collapse
Why did you say that??? If the phone is rooted you can download CWM by RomManager without fear.. the important is that when the popup with phones versions come up, you choose only - ONLY! - Galaxy 5 voice! If this voice is not present into the popup, don't choose nothing at all! Choosing another phone might brick yours!
I downloaded and installed and even only update CWM by RomManager a lot of times and everything was always fine! No problem at all!!
You cannot scare people for nothing: your problems are not bug or issues, but only YOUR problems! and YOUR errors!!!
So, boyz, don't worry installing CWM by RomManager.. but remember to choose only Galaxy 5 voice, no other phone, 'cause you could brick your phone selecting a CWM that is not compatible with our GT-I5500..
Hello,
Device: Razr XT910 GSM
Stock soft: Android 4.0.4
It was my first attempt to install a custom rom on my Razr.
I followed instructions from wiki.cyanogenmod.org/w/Install_CM_for_umts_spyder
I rooted razr, installed safestrap and flashed it with stable version of CyanogenMOD
And here the problem occurs: boot loop
I tried to install other versions of CM - RC5, nightly; it did not change anything - boot loop
Now I have no idea what to do.
Please help
Try doing a full wipe and clear caches !!
Please hit the thanks :thumbup: if i ever helped ya !!
jacek607 said:
Hello,
Device: Razr XT910 GSM
Stock soft: Android 4.0.4
It was my first attempt to install a custom rom on my Razr.
I followed instructions from wiki.cyanogenmod.org/w/Install_CM_for_umts_spyder
I rooted razr, installed safestrap and flashed it with stable version of CyanogenMOD
And here the problem occurs: boot loop
I tried to install other versions of CM - RC5, nightly; it did not change anything - boot loop
Now I have no idea what to do.
Please help
Click to expand...
Click to collapse
Delete and recreate your rom-slot. And try againI assume you're installing in on slot1
Sent from my XT912 using Tapatalk 2
neo.ank said:
Delete and recreate your rom-slot. And try againI assume you're installing in on slot1
Sent from my XT912 using Tapatalk 2
Click to expand...
Click to collapse
Yes, I tried to delete and create again slot. Yes, I'm using slot1.
Here's (step by step) how I'm trying to install CM:
1. I'm rooting phone with Razrs Edge Windows
2 Innstaling Safestrap 3.11 app. When running it it has superuser access
3 Clickin in "Install recovery" -> "Recovery state: Installed"
4 Reboot phone
5 Safestrap splashscreen appears -> hitting menu button
6 I'm in safestrap menu
7 "Boot options" -> "Rom-Slot-1" -> I'm choosing 2GB of data partition size -> "Create Rom Slot"
8 I'm waiting a few minutes
9 Everything looks fine
10 Going to main menu -> "Wipe"
"Cache"
"Dalvik Cache"
"Factory reset"
11 Going to main menu -> "Install"
12 Looking for zip with rom (I tried CM stable, RC5 and latest nightly)
13 Flashing rom. Everything looks fine
14 Going to main menu -> "Wipe"
"Cache"
"Dalvik Cache"
"Factory reset"
15 Going to main menu -> "Reboot"
Then Moto logo appears, later Safestrap splashscreen, after 10 seconds CM logo
It spinning
1 minute
2min
3min
5
It still spinning
10
15
30
WTF
What am I doing wrong?
Does anybody can confirm I'm flashing CM right?
I'm trying over and over again and it's not working
You're doing it right. Thats the correct procedure. Though step 14 is unnecessary.
However there might be a chance that your downloads are corrupted. Try redownloading the files.
Sent from my XT912 using Tapatalk 2
I have the same problem. I could use any rom before. Then after restoring phone with flash IT i cant install any of cm10.1 based roms. I tried about 15 roms: different versions of cm and aokp - same result. Rom just cant boot bootloop or just black screen forever. Same result with bootmenu and with safestrap.
neo.ank said:
You're doing it right. Thats the correct procedure. Though step 14 is unnecessary.
However there might be a chance that your downloads are corrupted. Try redownloading the files.
Sent from my XT912 using Tapatalk 2
Click to expand...
Click to collapse
I tried without step 14 - it not helps
I checked md5sum of downloaded roms - it is OK.
I also tried install LiquidSmooth ROM - after Safestrap splashscreen blank screen appears and the system did not start :/
jacek607 said:
I also tried install LiquidSmooth ROM - after Safestrap splashscreen blank screen appears and the system did not start :/
Click to expand...
Click to collapse
I have excatly the same problems for CM10 and LiquidSmooth . The only rom that I can flash is the MIUI V4
Any ideas?
sanieth said:
I have excatly the same problems for CM10 and LiquidSmooth . The only rom that I can flash is the MIUI V4
Any ideas?
Click to expand...
Click to collapse
How do you install Miui? With safestrap?
Sent from my XT910 using xda app-developers app
I got into boot loop when i tried CM for the first time. Then tried another ROM, again boot loop. Then downloaded and pushed EU Jelly Bean using RSD Lite and its working great now.
Sent from my Nexus 7 using xda app-developers app
All I can infer from posts above is it appears as a kernel incompatibility issue. Looks like your kernel won't allow kexec to boot the Rom. Its consistent with all kexec based ROMs so thats the only thing that could affect.
Since there aren't many people flashing CM over ICS kernel, this might not have been reported.
Sent from my XT912 using Tapatalk 2
same here on Razr "umts_spyder" (Euro Version)
neo.ank said:
All I can infer from posts above is it appears as a kernel incompatibility issue. Looks like your kernel won't allow kexec to boot the Rom. Its consistent with all kexec based ROMs so thats the only thing that could affect.
Since there aren't many people flashing CM over ICS kernel, this might not have been reported.
Sent from my XT912 using Tapatalk 2
Click to expand...
Click to collapse
Where in the last days I switched between(ish) cm-10.1.0 cm-10.1.2 and cm-10.1-20130715-NIGHTLY-umts_spyder.zip. Wasn't too stable (perhaps Navigon problems?) so I went on trying those versions.
This night I tried to install the cm-10.1-20130717-NIGHTLY-umts_spyder.zip and since got stuck in bootloop since.
Safe Strap: Wipe / Factory reset didn't get me out of there.
Hi again,
I just found solution for my problem with boot loop:
I just removed my sd card
and CM boots correctly
Something is wrong with sd card - it is visible and working well with stock ics, but when I start CM and insert card, CM can't see this card
Sent from my XT910 using xda app-developers app
removed safestrap....
Since I like to use the memory of the external card I:
removed safestrap and back on "Stock" XT910 / 4.1.2
updated to 982.124.14.xt910.Retail.en.EU
So I got all the Memory and a working system back.
Even though I kinda "love" CM I couldn't warm up to the (still genius) memory management of safestrap.
Also I didn't get a really smooth running CM - system.
Perhaps it is Navigon related that I now and then really depend on. And no, not in every part of the country the google maps gets its info via online.
My next step is to root.... http://forum.xda-developers.com/showthread.php?t=2202695
And in a couple of months I hope to find myself with a completely cracked (bootloader without safestrap) + CM stable.
format system is work
CM 10.1 boot loop
All,
Thanks in advance for any help. My XT912 was working great on the Cyanogenmod 10.1, until it became stuck in boot loop. I've tried all the steps mentioned above, to include wiping cache, FDR and removing the SD card - all to no avail.
I've also pushed the libskia.so file via: adb push ~/path/to/libskia.so /system/lib. http://forum.xda-developers.com/showthread.php?p=38591638#post38591638 - is there a similar file for the RAZR?
I'm able to use safestrap to go back to the stock ROM but i've had the taste of CM and can't get it out of my mind now!
Phil
Safestrap Bricked my Bionic Wednesday night
I used to run CM on my OG. I have always rooted my phones, relying completely on exploits found on these forums. I lost my Bionic in the forest last week and got my replacement Tuesday. After rooting it, I became nostalgic for a ROM that is devoid of bloatware. Casting around, I found good references for CM. So, I installed Safestrap 3.11 and downloaded the latest stable version of CM and booted into Safestrap recovery. So far, so good. I then configured a ROM slot 1 and tried to install CM into it. That may have been a mistake on my part since I have no experience with Safestrap and other users' posts seemed to indicate that they could switch between OS's by switching between ROM slots. Anyway, it didn't work and I couldn't boot back into my phone. So, I tried to restore my backup into Stock. That image didn't load. Presently, I could no longer get to Safestrap recovery and just got a black screen. That was late Wednesday night or early Thursday morning (8/15/2013). I tried getting to the normal recovery application and I could boot into the menu but, when I tried to select recover, instead of allowing me to navigate to my backups (or any other recovery file), I was presented with the dead robot image. After each dead end, only a battery pull would power off the phone. After messing around for a while with the recovery tools menu, I found that the sbf flash option appeared to be functional.
So, after researching how to use it, I downloaded the latest version of RSD Lite that I could find (along with the MKT patch, whatever that does) and tried to push the Verizon published zip file for the 4.1.2 OTA. Somewhere during the process and before it started pushing images, it hit an XML error and stopped. So, then I did some more research and found that someone had created a file with a patch for the XML error. Again using RSDLite, I pushed that file to my phone. It worked and, after it flashed the image, I had what was basically a factory reset phone. So I reconfigured it an rooted it using the Ubuntu exploit again.
However, when I boot into recovery and select the recovery option, I still get the dead robot icon. I tried reinstalling and uninstalling Safestrap but I still get the same dead robot behavior. With Safestrap recovery installed, I can boot into recovery and see my original backup files but I am afraid to use any of the functionality because Safestrap borked up my phone so badly the first time and I don't want to try to recover from a bricked device state. But I would like to get the recovery program working again just in case I need it to apply a package someday.
Warning: I'm a total n00b. I'm afraid I permanently wrecked my phone and I want to know if I can get it back to normal again.
Here is a step by step of what I think happened:
I tried flashing CyanogenMod 10.1 by using the ClockWork ROM Manager. I went to the Download ROM section of ROM Manager and found Cyanogen 10.1. It gave me the prompt "Backup existing ROM" and "Wipe Data and Cache," and I selected both. My phone started downloading the ROM. After it finished downloading the recovery menu popped up and I pressed Reboot System Now which I think was my first mistake.
It rebooted into Samsung's TouchWiz, not CyanogenMod, and asked me to sign into my Google account, which I did. I knew I had made a mistake so I went back to the ClockWork Recovery menu to start over. I made a backup of my ROM (which at this point was not even useful due to my first attempt), wiped the data/Factory Reset, wiped the cache, and wiped the Dalvik Cache. Then I tried to install the CyanogenMod ROM by going to "choose zip from sd card," however I couldn't find any ROM saved! I then tried to restore from a safe point, but no files could be found to restore from. At this point I panicked and hit "reboot system now" not knowing what it would do.
It rebooted into TouchWiz again, except this time with zero of my contacts, apps, anything. And it kept freezing every couple of seconds. I tried booting into the stock recovery image but instead of the menu it asked me if I was sure I wanted to download a custom OS. First I said no and it just froze again. Then I said yes and it started downloading something. My phone currently has the green android in the middle, and up top it says Odin Mode/Custom Binary Download: No/Current Binary: Samsung Official. It hasn't changed in about 20 minutes.
At this point I just want to get out of the jam I created and hopefully get some files back, especially the photos I have saved. Can anyone help me?
ps sorry for the long post
Well the good news is that as long as your phone is booting all the way into ANY OS, you're doing okay. Here at XDA, the ROM MANAGER method is frowned upon. From this point, your best (safest) bet is a clean slate, and I think that the best way for you to get there is to ODIN to stock touchwiz jellybean 4.1.2 (UCMD8) -then start the root - ROM process over again.
Odin 1.85 or 3.07 will both work
the UCMD8 firmware can be found in creepyncrawly's download repository
---------- Post added at 07:35 AM ---------- Previous post was at 07:23 AM ----------
gschmutz said:
...I tried booting into the stock recovery image but instead of the menu it asked me if I was sure I wanted to download a custom OS. First I said no and it just froze again. Then I said yes and it started downloading something. My phone currently has the green android in the middle, and up top it says Odin Mode/Custom Binary Download: No/Current Binary: Samsung Official. It hasn't changed in about 20 minutes...
Click to expand...
Click to collapse
What you describe here indicates that you booted into download mode, not recovery. Although it seems as though the phone is actively downloading something, it's just entered a ready-to-receive mode until you actively tell ODIN to send data (from a PC).
the keypress to get into download mode or recovery:
download mode: usb cable PLUGGED IN; vol- & vol+ & power --> until the prompt appears, then release and follow the instructions on screen
recovery: usb cable UNPLUGGED; vol- & vol+ & power --> until bootlogo appears, then release, and the phone should continue to boot into recovery.
---------- Post added at 07:43 AM ---------- Previous post was at 07:35 AM ----------
Once you're comfotably back to stock, this is the easiest way to get from stock to custom recovery on the i777:
Framaroot <-- tool to establish root-access to the device
Mobile Odin Lite <-- tool that uses root-access to install...
Custom Kernel <-- a custom kernel (there are many available) installed primarily to provide cwm recovery, but are also commonly used to:
-install a different ROM
-provide additional functionality to the existing ROM
-backup your ROM install
-install a different kernel
-flash cleanup scripts
-and many many other things
The ROMs are usually packaged with their own kernels, so the kernel used above only remains in place until another ROM is flashed, which will overwrite the existing recovery with one specifically designed for the ROM flashed.
This guide will walk you through the steps, but read through the thread carefully to be sure that you understand everything before leaping.
-happy flashing
Great thank you so much! I will try to flash Jelly Bean when I get home from work. You lifted a weight from my chest.
Here's another update before I go any further. Late last night my phone stopped its bootloader cycle and seemed to be stably running TouchWiz on 4.1.2, and it is still rooted. It has been running stable all day. Do you think I still need to flash stock TouchWiz using ODIN before trying anything with my phone?
gschmutz said:
...running TouchWiz on 4.1.2, and it is still rooted. It has been running stable all day. Do you think I still need to flash stock TouchWiz using ODIN before trying anything with my phone?
Click to expand...
Click to collapse
probably not, I'm glad to hear that things have stabilised.
From here, my strongest recommendation is that whenever you flash firmware, do some house-cleaning:
-either run a rom-wipe script before-hand
OR (at least)
-factory reset
-format /system
I want to give the awesome Android 5.1 experience to every Galaxy S2 user. I am here to help, so if you need help just post a new replay.
I will upload all I can on my own Google Drive, so when the Link is down someday send me a message.
This thread is ONLY for the Galaxy S2 GT-i9100 modell! Check it by going into settings -> about phone -> modell!
I am here to help, so if you have questions or problems post a reply here and I will give my best to help you.
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired because the alarm app failed. Please
do some research about all the things I tell you
before doing it! YOU are choosing to make these modifications, and if
you point the finger at me for messing up your device, I will laugh at you. Hard. A lot.
Pre-requisits:
A1. Download Odin 3.07: HERE
A2. Download CWM Recovery:
A3. Download Phone Drivers [most not needed so only download when your phone doesn' get detected from your PC]: COMING SOON!
B1. [Optional - only if you need root on your Stock Rom] SuperSu: HERE
B2. [Optional - only if you don't want to have a so called Triangle which says that your device doesnt have OFFICIAL software anymore, check more!] Triangle Away: HERE
C1. Download your Android 5.1 Rom, here you can find some, but there will be some more:
- CyanogenMod 12.1 Unofficial [Most known Rom]: HERE
- CyanogenMod 12.1S Unofficial [Much more features from OnePlus One and more]: HERE
- Nameless Rom [Smoothes of all, and for me the stablest]: HERE
- Resurrection Remix Official [Most features of all these Roms, very smooth]: HERE
- OmniRom Unofficial [Simple but clever ]: HERE
C2. [Optional but really recommended!] Download Google Apps: HERE [TAKE ONE FOR ANDROID 5.1!]
C3. [Optional!!!] Download Apollo Custom Kernel (VERSION 8!), this will also bring TWRP Recovery to your phone (what I do prefer much than CWM):HERE and don't forget to install the Config App on your PHONE: HERE
A. So first let us start with giving you a new Recovery. I decided to show you because this is the most known one and there is no TWRP for it.
- Go to your PC and open Odin307.zip, now extract it somewhere and open Odin3 v.3.07.exe
- Take your S2 and bring it in Recovery Mode by shutting it down and then press Power+Home+Volume Down
- Now take your i9100 Galaxy S2 and connect it to PC with a USB Cable [it is recommended to use the cable which was delivered with the device]. Odin should now says something at ID:COM and under message should stand: "Added!".
- Check in Odin if ONLY THE FOLLOWING is crossed under Option: - Auto Reboot; F. Reset Time! NOTING MORE
- Now click in Odin on PDA and search your downloaded file called something like: "CWM-KitKatCompatible-i9100.tar"
- Let Odin check the md5 and after this is finished press "Start". Give your phone some time (up to 10 minutes) and wait until there is "Passed" in Odin.
- Your device has now lost garantee (only when you don't use Triangle Away) and you have a custom recovery
B. [OPTIONAL!] When you want to use Triangle Away or need root a last time on your Stock Firmware you have to root it first.
- Open AutoRoot S2 i9100.zip, now extract it somewhere and open Odin3 v.3.07.exe from inside the folder
- Take your S2 and bring it in Recovery Mode by shutting it down and then press Power+Home+Volume Down
- Now take your i9100 Galaxy S2 and connect it to PC with a USB Cable [it is recommended to use the cable which was delivered with the device]. Odin should now says something at ID:COM and under message should stand: "Added!".
- Now click in Odin on PDA and search your downloaded file called something like: "CF-Auto-Root-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"
- Let Odin check the md5 and after this is finished press "Start". Give your phone some time (up to 10 minutes) and wait until there is "Passed" in Odin
If you now want to use Triangle Away read more at @Chainfire 's Official XDA Thread, linked at pre requisits!
C. Now we are at the Step to get your new Android Vanilla 5.1 Software. Go to the threads upside and take the Rom you most like, if you need help to decide I can help you
I would recommend you to use Resurrection Rom because for my S2 this was the smoothes one.
- Copy your downloaded Rom.zip and Gapps.zip to your micro SD Card from your S2
- Shut down your phone, then boot into Recovery by Holding Power+Home+Volume Up, release Power as soon as you see the "Samsung Galaxy S2 i9100" Logo, otherwise it will maybe reboot again.
- [Optional but recommended] You will see the TWRP Logo, then go to Backup and Restore and do a backup!
- Go to Factory Reset and do a factory reset, then go to wipe cache and wipe cache, then go to advanced and wipe Dalvik, then go to mounts and storage and wipe System, Data, Cache, boot and Internal Storage (default)
- Now go to install and choose you directoy where your downloaded zip's are, and choose your Rom, then press install again and choose your Gapps.zip and wait until it has finished
- [Optional] After finished installation go to Advanced and Wipe Dalvik again. Then reboot your phone.
Finished! You have now the newest Android 5.1 on your S2!
OPTINAL you can now install a custom Kernel but this is really OPTIONAL! First read something about custom kernels before doing so!
Download the zip and flash in Recovery, finished, then install the Config app on your phone. CHECK FIRST IF THE KERNEL WORKS FOR YOUR ROM! Apollo works for CyanogenMod, Resurrection Remix, the rest I don't know.
Please press THANKS if you find this Thread usefull!
-------------------------------
Also Check:
- How to Root Galaxy S6 SM-G920F: HERE
- How to Root and install Android 5.1 on i9300 Galaxy S3: HERE
- How to Root and install Android 5.1.X on i9505 Galaxy S4: HERE
RESERVED
RESERVED
Hallo I have a galaxy s2 model i9100 which was on stock official android 2.3.6 gingerbread and I upgraded it to CWM 12.1 ANDROID 5.1 Custom rom....and then got these bugs.....
1.....the BACK button, OPTIONS button dont work...also the MENU/HOME [middle] button works as back button. .....its not a hardware problem coz they worked very well on Gingerbread the previous rom
2....when I call some one...he doesnt hear me and I also dont hear him....its the same issue when I activate loud speaker or insert HEADSETS.....
ITS NOT A HARDWARE PROBLEM because things were working well when on official android 2.3.6 stock......and also all the speakers work well on other apps....also, people dont hear me during calls and yet the mic WORKS VERY WELL FOR VOICE and VIDEO RECORDING FOR OTHER APPS including camera and voice recorder.....BUT STILL PEOPLE DONT HEAR ME DURING CALLS......
I then took it back to official android 4.1.2 jellybean AND I STILL HAVE THE SAME ISSUES......STILL THE BUTTONS DONT WORK and also i dont hear people during calls and they dont hear me either......PLEASE HELP ME...this is a software problem.....I have tried factory reseting the phone and wiping all data on phone and still the same issue. ........AM NOT AN EXPERT TO ANDROID
THANKS....
[email protected]
Sent using XDA Free mobile app
can i root my SG S2 GT-I9100 with kingo root apk or farmaroot then flash cwm recovery from "Rom Manager" app ??