[ROM] CM10 for RAZR HD XT925

Good work!

I can't try it currently, I need my wifi... :$
Do you know if Play Store works ?

I know you must write this

Disclaimer:
I'm not responsible by phone bricks of any kind, or any other damage this firmware may cause to you, to your phone or any accessories conected to your phone

Click to expand...

Click to collapse

But it scares me a little

So I'm guessing this doesn't work for cdma version because there's no unlocked boot loader for cdma right?' I have a safe strap and a custom Rom on now but no unlocked boot loader x and there's no other kernal so I guess that's why we need unlocked loaders.

CDMA is XT926 no ? they don't have the same radio, you can't use GSM roms on CDMA phone and vis versa...

Epinter,

I'm new to Motorola as a brand, but not to CWM, unlocked bootloaders or custom ROMs. I asked you on the CWM thread on what to press in order to have the CWM menu. As soon as someone tell me, I will test your ROM, as I don't need for now my camera or WiFi.

I have an unlocked bootloader, XT925 model and when I press power and vol +/- I boot to the stock Motorola recovery. I followed the instructions on the CWM thread to load it using mfastboot, but I can't load CWM after a reboot.

Thank you very much for your help.

Edit: Nevermind, I found the answer here http://www.theandroidsoul.com/twrp-and-clocworkmod-cwm-recovery-for-motorola-droid-razr-hd-xt926/

I will try CM10 now.

Also, you mentioned that call service was broken. Is it already fixed on this version? I can live without Wifi or camera, but can't live without voice calls.

Thank you.

Great !!!!

Just need wifi/(camera)/(thetering) ^^ What about hardware acceleration ?

It work with Safestrap Recovery ?

That's just wonderful epinter! Thanks. I'll give it a try (but can't keep it installed permanently since I rely exclusively on wifi...)

ROM: Stock ICS 4.0.4 (rooted)
Recovery: TWRP v2.2.2.1

I'm getting an error trying to flash CM10:

-- Install /external_sd/Download/cm10/cm-10-20121115-UNOFFICIAL-epinter-xt925.zip ...
Finding update package...
I:Update location: /external_sd/Download/cm10/cm-10-20121115-UNOFFICIAL-epinter-xt925.zip
Opening update package...
Installing update...
script aborted: assert failed: getprop("ro.product.device") == "xt925" || getprop("ro.build.product") == "xt925" ||
getprop("ro.product.device") == "vanquish_u" || getprop("ro.build.product") == "vanquish_u" ||
getprop("ro.product.device") == "vanquish" || getprop("ro.build.product") == "vanquish"
assert failed: getprop("ro.product.device") == "xt925" || getprop("ro.build.product") == "xt925" || getprop("ro.product.device") == "vanquish_u" || getprop("ro.build.product") == "vanquish_u" || getprop("ro.product.device") == "vanquish" || getprop("ro.build.product") == "vanquish"
E:Error in /external_sd/Download/cm10/cm-10-20121115-UNOFFICIAL-epinter-xt925.zip
(Status 7)

Click to expand...

Click to collapse

Double checked /system/build.prop and ro.product.device is set to vanquish_u.

Any idea?

---------- Post added at 12:39 AM ---------- Previous post was at 12:25 AM ----------

All right, I googled the problem and it seems the best way to handle this is to get rid of the "assert" command in /META-INF/com/google/android/updater-script.

Let's try this...

---------- Post added at 01:09 AM ---------- Previous post was at 12:39 AM ----------

For those wondering, the zip file needs to be updated; NOT extracted / re-zipped.
What I did (on Debian):

7za x cm-10-20121115-UNOFFICIAL-epinter-xt925.zip META-INF/com/google/android/updater-script
kate META-INF/com/google/android/updater-script [remove the assert line]
7za u cm-10-20121115-UNOFFICIAL-epinter-xt925.zip META-INF/com/google/android/updater-script

Click to expand...

Click to collapse

---------- Post added at 01:13 AM ---------- Previous post was at 01:09 AM ----------

First boot... "CyagenMod" cycling logo... for 5 minutes... seems to be stuck somehow...
Fed up with waiting any longer... Forcing reboot... Same story... Stuck on CyagenMod cycling logo...

Ouch... Almost out of battery... Restoring backup... Will give CM10 another try later...

---------- Post added at 01:26 AM ---------- Previous post was at 01:24 AM ----------

epinter said:

Did you wipe the /data ?

Click to expand...

Click to collapse

I think you got it... I wiped cache/dalvik but forgot data... n00b mistake... I'll give it another shot this week end.

i did a full wipe, booted within 2 minutes.

---------- Post added at 06:37 PM ---------- Previous post was at 06:07 PM ----------

Just one thing. Gapps installed but no calendar is installed.

Sent from my XT925 using xda premium

---------- Post added at 06:39 PM ---------- Previous post was at 06:37 PM ----------

Just got Google calendar from Google play. All good.

Sent from my XT925 using xda premium

Alright... CM10 up and running... Voice seems to be fine. All in all very very smooth...
WIFI is indeed not working... Once you manage to nail the bugs down, I might keep CM10 permanently on my device.

In the meantime, I'll test it as much as I can considering that I don't have mobile data for now...

---------- Post added at 10:39 AM ---------- Previous post was at 10:36 AM ----------

Torch is not working ("failed unexpectedly" upon flash light activation).

---------- Post added at 10:48 AM ---------- Previous post was at 10:39 AM ----------

App drawer becomes unstable after playing a little with the phone... Keeps on switching back to home screen after a short moment (< 2s).
The more I use the phone, the more unstable the app drawer gets...

---------- Post added at 10:57 AM ---------- Previous post was at 10:48 AM ----------

Odd keyboard behaviour noticed in Messaging app. Upon creation of a new text msg, keyboard pops up and lets me enter a phone number in the "To" field. But once I switch to the "Message" field, keyboard disappears very quickly and I need to tap the "Message" field a few times to show the keyboard back... I can't reproduce this strange behaviour each time...

---------- Post added at 11:24 AM ---------- Previous post was at 10:57 AM ----------

In "Settings / Status bar", when using "text" instead of "Icon" for "Signal status style", it shows a long integer number... Not sure if that's the intended behavior (but this looks useless to me...).

---------- Post added at 11:32 AM ---------- Previous post was at 11:24 AM ----------

I don't know if Apollo is supposed to display thumbnails embedded in my locally stored m4a audio files, but it doesn't.
No controls within Apollo to start/stop/pause/forward/rewind??? I have to use the controls in the status bar.

---------- Post added at 11:41 AM ---------- Previous post was at 11:32 AM ----------

Applying live wallpapers does not work at all (or just a short moment), then reverts to the standard wallpaper.

---------- Post added at 01:51 PM ---------- Previous post was at 01:41 PM ----------

Now homescreen is getting unstable as well... Sliding left/right, then homescreen restarts.... Even standing by, untouched, seems to restart on its own from time to time.
I think I'm gonna have to reboot every couple of hours or so, homescreen/app drawer way too unstable.

---------- Post added at 02:16 PM ---------- Previous post was at 01:51 PM ----------
Bluetooth is not working, can't switch it on (similar to WIFI)

---------- Post added at 02:25 PM ---------- Previous post was at 02:16 PM ----------
After a reboot, I run of Apollo and play a song. Apollo gets stuck for about 10s. The system displays a message "Apollo is not reponding. Wait or Close? Upon Close, Apollo restarts and I can then play any song...

@epinter

Is such a report any useful? Do want to me to look into a particular direction?

epinter said:

Yes, it's useful, I will save this. But now I want to focus on wifi and other critical bugs. The minor bugs I will try to debug later. Thanks very much!

The wifi it's being very hard to make work. I'm working on wifi with dhacker29.

Click to expand...

Click to collapse

I understand.

Let me know if you need specific testing.

epinter said:

When you have a time to test again, add this line to your build.prop:
ro.telephony.ril_class=QualcommSharedRIL

This should fix the signal bug.

Click to expand...

Click to collapse

Will do.