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.
I have Samsung Vibrant T959. Currently has clockworkmod 6.0.3.6 .
I'm trying to install the latest unofficial cyanogenmod 11, which will install kitkat 4.4.4, however I run into the error message "set_metadata_recursive: some changes failed" . According to my research all I need to do to solve it is update clockworkmod to a version of at least 6.0.4.5 .
I've searched all over, most sources point towards using rom manager, but this is not working. Rom manager seems to think the latest version is 2.5.1.2. The official clockworkmod site also lists 2.5.1.2 as the latest version for my phone.
So how do I upgrade this clockworkmod so that I can install kitkat? I know others have done it, but I can't find any info how.
Thanks.
I just installed Sada's 4.4.4 today (coming from the official CM 11 [4.4.2]) and what I did was go into CWM and install the rom (which will fail). During the process it will install CWM 6.0.4.9. Reboot. Now you will have 6.0.4.9.
FYI - I had to reformat the internal SD card to get the 4.4.4 install to stick. (factory reset and clearing caches wasn't enough and would throw errors on first boot)
-Mike
Thanks for the advice. Thats the exact thing I was doing. Coming from latest official Cyanogenmod, to the latest unofficial.
So I did exactly what you said, tried to install, it failed, rebooted straight from recovery back into recovery, and I indeed had clockworkmod 6.0.4.9.
So I did the install again, it worked, installed the minimal gapps, but I did not format the SD card. I figured I would try without it first.
Well upon booting I couldn't get past the first screen of the setup wizard, it would just crash. Had a very difficult time getting back into recovery mode, as the typical 3 button combo wouldnt work, but finally figured out a way by sheer luck and experimentation (hold volume down, and power, and plug in a usb cord. Keep the buttons held for about 30 seconds, then release the power button while still holding volume down, after 10 seconds it would go to recovery)
So I did the format of the internal SD card as well, but no luck, the wizard still crashes. Ended up just restoring my old nandroid. I wonder if there was anything else you did different than me. Perhaps different Gapps?
I have an xt912.
I started with the Droid Razr utility by mattlgroff. I ran step one, three, and four to flash a stock rom to the device, root it and finally to install safestrap 3 to the device. From here I pushed a stable release of cyanogen and gapps. The packages that I pushed to the device are cm-10.2.1-spyder.zip and gapps-kk-20140606-signed.zip. I then managed to flash these packages from twrp. However I ran into status 6 a couple of times with different releases.
My keyboard process stops working as soon as the phone boots. I've tried re-flashing cyanogen and gapps. If I do a factory reset followed by a system wipe and then flash cyanogen without gapps my keyboard is fine; however I no longer have access to the play store or anything of the such.
Cyanogen tells me that there is a new update. I can download the update just fine but when I try to flash it through recovery twrp gives a status 6 and fails to flash. When I try to flash a different release of gapps, twrp also gives a status 6 and fails to flash.
A couple of odd bits.
My phone does not have a service provider but I still have the lte sim from verizion.
I pushed the files to /sdcard/ without an sd card in the phone. From what I understand it pushed it to internal storage.
The version of twrp is 2.2.2.1
When I was running the utility it would have trouble detecting my device after a reboot. I would have to unplug and re plug after the reboot for it to recognize it. The phone wouldn't recognize it either until i did the same. The battery icon wouldn't show it connected.
So, what can I do about the status 6 or what causes it and what can I do about the failing keyboard process?
I'm on nightly 3/21, which I installed clean yesterday. I want to update to 3/22, but the update will not work automatically in TWRP. (TWRP cannot mount e:, which is a problem I encountered several times while trying to install CM, and ended in me having to reflash to stock several times before it would work again.... Anyways, that's a separate issue.) I selected the option in Dev options to automatically update CM recovery, but this option does not seem to be working. After having selected that option, then downloading the update and selecting update, the tablet still reboots into TWRP and does nothing.
Which brings me to my question. Can I get the CM recovery img from somewhere and flash it myself in order to get the updates to work? I haven't been able to find it, and TWRP has just been a pain in the neck anyways.
Thanks!
When I updated Cyanogenmod to CM13 my recovery stopped working (I turned on "update recovery with system"). I didn't can apply ANY updates from SD card and from PHONE STORAGE too.
To fix it I tried to update CM to 13 from 10-02-2016 to 13-02-2016. But... It didnt ANYTHING happened! It was only black screen. But now I can't turn on my phone! Recovery mode is not turning on too! I have only not working phone with not working recovery when it will turn on too!
I need my phone tomorrow, please, HELP ME! What can I do?!
Recovery: CM13 recovery.
It is not bootloop, I have:
BLACK SCREEN
After Samsung logo.
It is very important, does somebody know what to do?
I have new news:
After turning on I have samsung logo and for about one second Updating System message! Without loading bar . After it of course black screen!
I didn't do any backups of my phone, but I can wipe all data, but I NEED WORKING PHONE!
@tom790
Try flashing this kernel I attached with odin. Next try rebooting to recovery. If you get a working TWRP recovery, then flash the rom you want to use as normal. Please read this guide if you want to use CM13 and avoid common issues.
Same problem here after trying to update to the newest nightly (also with "update recovery with system" on in developer settings) I assume that this function isn't working correctly. The only alternative is as mentioned above - flash kernel+recovery with Odin and make changes afterwards.
I have same problem. I tried to install this kernel above with ODIN but no luck, after sucessful flash logo and black screen. Any other advice or tips? Is there any chance to recover some data from internal card?
And exactly the same issue here. Will try the workaround from the first answer by noppy22.
OK, succeeded. I used ODIN with the kernel tar file from noppy22, put the S2 into download mode (that was still possible, recovery mode couldn't be accessed), flashed the kernel. Phone rebooted automatically into recovery and started (continued?!) with the installation of CM 13.0. And here I realize the issue. The OTA was the nightly of CM 13.0 which I inadvertently chose to be flashed over the running CM 12.1. Bad idea!
Caveats: I see the yellow triangle now which didn't show up before. No problem for me - it's more than 4.5 years old. And there is still the error that "Google play service was terminated" which showed before I triggered the OTA update of CM 12.1.