Hi,
Can anyone share (again...) a good version of a RTFR 4.1.2 ROM please?
thanks up front
Did you try this ?
http://xdaforums.com/showthread.php?t=2032284
"Branding: Retail France/Retail Central Europe"
[ROM] CM 11.0 (Android 4.4) for RazrHD XT925/XT926
- Thread starter epinter
- Start date
Did you try this ?
http://xdaforums.com/showthread.php?t=2032284
"Branding: Retail France/Retail Central Europe"
Hi,
Can anyone share (again...) a good version of a RTFR 4.1.2 ROM please?
thanks up front
also http://sbf.droid-developers.org/index.php
Hi guys,
sorry to be a pain in the a**, but have following situation:
* CM11 jbbl
* RSD lite v 6.1.4
* Motorola drivers: ok (v 2.4.5)
* WIN 7
* JB ROM (Europe), changed the xml already
* both CWM & Philz recoveries
* latest CM11 KK
* debugging on
....but....
When launching RSD it doesn't see my device! As indicated, debugging OK, drivers (incl ADB) OK...what am I missing?
Have been doubting a long time before finally wanting to upgrade, but now I can't....
Any help's appreciated
cheers
sorry to be a pain in the a**, but have following situation:
* CM11 jbbl
* RSD lite v 6.1.4
* Motorola drivers: ok (v 2.4.5)
* WIN 7
* JB ROM (Europe), changed the xml already
* both CWM & Philz recoveries
* latest CM11 KK
* debugging on
....but....
When launching RSD it doesn't see my device! As indicated, debugging OK, drivers (incl ADB) OK...what am I missing?
Have been doubting a long time before finally wanting to upgrade, but now I can't....
Any help's appreciated
cheers
It is not really the goal of the current thread
You should create a topic and ask for help in the good section : http://xdaforums.com/droid-razr-hd/help
You should create a topic and ask for help in the good section : http://xdaforums.com/droid-razr-hd/help
Would be nice if Moto did the same thing HTC did (iirc, anyways) where they offered a OS upgrade outside of carriers because carriers (at the time) weren't being forced into providing better upgrade schedules, etc.
Moto should just release a int'l SBF for the XT925 for us to RSD.
Still waiting on Rogers to release their update. Still running my frankenstein build courtesy of @Orphee
Only thing I'm missing is LTE.
Probably list is made before Google play service update
http://www.androidauthority.com/worst-performance-sapping-apps-564689/
http://www.androidauthority.com/worst-performance-sapping-apps-564689/
Probably list is made before Google play service update
http://www.androidauthority.com/worst-performance-sapping-apps-564689/
Ha! Or maybe google secretly made the list. The only Google app on the list is Chrome and that just for storage.
I've seen a couple people posting about using f2fs with CM on our phone. Is there anything I need to do besides reformat partitions as f2fs? I thought something had to be changed in the rom itself, but I can't find any information in the razr hd forums about it.
Flash the F2FS compatible TWRP Recovery
Boot into Recovery
Backup > Data
Save your internal SD card with one of the following options
Either reboot to system and copy files to your PC via USB (MTP)
Or pull files via adb (adb pull /data/media sd_backup)
Wipe > Advanced Wipe > Data > Repair or Change File System > Change File System > F2FS
Wipe > Advanced Wipe > Cache > Repair or Change File System > Change File System > F2FS
Copy the saved SD card content back to your device with: adb push sd_backup /data/media/0/
Afterwards the folder structure should look like this: /data/media/0/…Folders like DCIM, Music, Downloads, …
You can check with: adb shell ls -R /data/media
Restore > Choose backup > Data (the warning about ext4 backup doesn’t matter)
Advanced > Fix Permissions
Flash the sdcard Fix Permissions script with: Install > Choose sdcard fix zip
found here http://xdaforums.com/showthread.php?t=2239421 (not sure if this is needed or not for cm kernel)
Wipe > Advanced Wipe > Cache & Dalvik Cache
Reboot to system
Boot into Recovery
Backup > Data
Save your internal SD card with one of the following options
Either reboot to system and copy files to your PC via USB (MTP)
Or pull files via adb (adb pull /data/media sd_backup)
Wipe > Advanced Wipe > Data > Repair or Change File System > Change File System > F2FS
Wipe > Advanced Wipe > Cache > Repair or Change File System > Change File System > F2FS
Copy the saved SD card content back to your device with: adb push sd_backup /data/media/0/
Afterwards the folder structure should look like this: /data/media/0/…Folders like DCIM, Music, Downloads, …
You can check with: adb shell ls -R /data/media
Restore > Choose backup > Data (the warning about ext4 backup doesn’t matter)
Advanced > Fix Permissions
Flash the sdcard Fix Permissions script with: Install > Choose sdcard fix zip
found here http://xdaforums.com/showthread.php?t=2239421 (not sure if this is needed or not for cm kernel)
Wipe > Advanced Wipe > Cache & Dalvik Cache
Reboot to system
Okay it is that simple then. maybe I'm confusing it with all-f2fs on my nexus 7. Thank you for the help.
Test build (CM11 kkbl) that should be hopefully able to get the GPS lock even when you left stock with GPS engine disabled:
http://d-h.st/aIM
Please let me know how it works for you, thanks.
http://d-h.st/aIM
Please let me know how it works for you, thanks.
Will report back on this...as I have to back up what am currently on, then refresh.
Your effort is much appreciated sir. In my case regardless of how I moved on from 4.1.2 or 4.4.2 gps on or off I ended up with a barely working gps on 4.4.4
It will connect to few sats, then drop connection afterwards...
Looking and hoping for a fix... Will definitely try your attempted fix.
Your effort is much appreciated sir. In my case regardless of how I moved on from 4.1.2 or 4.4.2 gps on or off I ended up with a barely working gps on 4.4.4
It will connect to few sats, then drop connection afterwards...
Looking and hoping for a fix... Will definitely try your attempted fix.
Last edited:
I second this, many thanks kabaldan for your continued efforts.
As I'm on an Australian career, we're still stuck on JBBL with the promise of KK "coming soon"... whatever that means now.
GPS has never been stable for me. When it works, it works well enough and can keep going for an hour or so but then it loses lock and when it does, a restart or a long wait brings it back.
GPS+ shows no sats in view at all when the lock is lost, so things have always been a bit rocky on the XT925.
This came at precisely the right time for me. Literally about to RSD back to stock because of this very issue.
Will give it a go and see if I can get a GPS lock.
---------- Post added 11th November 2014 at 12:40 AM ---------- Previous post was 10th November 2014 at 11:56 PM ----------
Hmm seems like it didnt work on my 925
Formatted system and cache, kept data. Am I doing it wrong or it shouldnt matter?
SystemUI crashes
It's been said before in this thread, and I'm probably repeating myself right now, but SystemUI crashes seem to be CM11's Achille's heel.
CM10 surely held to its own pet bugs to the end ("DSP Manager has stopped" anyone?) but it was rock-solid system-wide, at least in my experience. I'm afraid the same can't be said about CM11, which is already close to its final form. I suspect the deep theming engine that was introduced in CM11 might be behind this instability.
Freezes and system-wide crashes are some of the reasons android was considered the geeky/rough alternative in its early days, especially when compared to the relatively more stable feature phones and iOS (stock) devices. When you're tinkering with every possible advanced setting and hack, they're to be expected, but when they happen in casual, day-to-day tasks, they make you trust your device a bit less.
CM is usually a remedy against those crashes, lagging and spontaneous reboots, but the current version can't seem to hold a stable enough system UI, at least on my devices. Don't get me wrong, I'm not playing cry baby, I'm just intrigued as to why this keeps happening after so many iterations (and I'm certainly not the only one, check an earlier post from this thread about bug CYAN-5402).
I ran into one of these odd issues just tonight: turned NFC on to connect the Razr to a headset and made a long voice call. Everything went fine. When done, I turned bluetooth off on the phone and boom, no system bars, no lock screen, nothing but a static screenshot. It's a very specific scenario, but I'd done that many times before without any hassle. Go figure. If anyone is curious, I've attached a log.
Coincidentally, I've read today that the die-hard Defy has a somewhat similar issue:
It's been said before in this thread, and I'm probably repeating myself right now, but SystemUI crashes seem to be CM11's Achille's heel.
CM10 surely held to its own pet bugs to the end ("DSP Manager has stopped" anyone?) but it was rock-solid system-wide, at least in my experience. I'm afraid the same can't be said about CM11, which is already close to its final form. I suspect the deep theming engine that was introduced in CM11 might be behind this instability.
Freezes and system-wide crashes are some of the reasons android was considered the geeky/rough alternative in its early days, especially when compared to the relatively more stable feature phones and iOS (stock) devices. When you're tinkering with every possible advanced setting and hack, they're to be expected, but when they happen in casual, day-to-day tasks, they make you trust your device a bit less.
CM is usually a remedy against those crashes, lagging and spontaneous reboots, but the current version can't seem to hold a stable enough system UI, at least on my devices. Don't get me wrong, I'm not playing cry baby, I'm just intrigued as to why this keeps happening after so many iterations (and I'm certainly not the only one, check an earlier post from this thread about bug CYAN-5402).
I ran into one of these odd issues just tonight: turned NFC on to connect the Razr to a headset and made a long voice call. Everything went fine. When done, I turned bluetooth off on the phone and boom, no system bars, no lock screen, nothing but a static screenshot. It's a very specific scenario, but I'd done that many times before without any hassle. Go figure. If anyone is curious, I've attached a log.
Coincidentally, I've read today that the die-hard Defy has a somewhat similar issue:
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
56This is a CM11.0 (KitKat, Android 4.4) ROM for Razr HD.
This rom requires an unlocked bootloader. Recent versions (July/2014) requires an updated (KitKat) bootloader
DEVELOPERS (razrqcom-dev-team):
EPinter - Kernel Development, Build Setup, XT925 & MB886 Support
DHacker - Kernel Development, Build Setup, XT926 Support
Hashcode - Kernel Development, Build Setup, XT926 Support
Nadlabak - Kernel Development, Build Setup, XT897 Support
Skrilax_CZ - Kernel Development, Build Setup, XT897 Support
Download links and information about what is working can be found on the website:
https://sites.google.com/site/linuxmobileorg/razrhd/cm11
Instructions:
Download the zip (cm-11-*-UNOFFICIAL-epinter-xt*.zip) and copy to your sdcard.
Boot into recovery.
Backup your firmware and data!
Format /system.
Install the firmware (install zip from...).
Install gapps (install zip from...).
Wipe data/cache
Reboot.
Developers builds:
Epinter: http://goo.im/devs/epinter
DHacker: http://androidhosting.org/Devs/Dhacker29/
An updated CMW recovery version is required, download:
http://www.clockworkmod.com/rommanager/
Gapps:
http://wiki.cyanogenmod.org/w/Google_Apps
2014-08-02
Everyone with JellyBean firmware/bootloader should use moto_msm8960_jbbl builds. Users who updated to KitKat firmware/bootloader need to use the moto_msm8960 builds.
Sources:
https://github.com/razrqcom-dev-team
https://github.com/CyanogenMod37Hi,
Is not everyone who can use cm11 based on the new kernel, so I will build with old kernel that supports JB bootloader, so you can stay up-to-date while the bootloader is not updated.
https://goo.im/devs/epinter/cm-11-20140708-NIGHTLY-moto_msm8960-epinter.zip21I've finally pushed the commit to enable HDR in CM camera (and other generic camera apps) for both jbbl and kkbl builds:
http://review.cyanogenmod.org/75212
together with a change needed for it in kkbl builds:
http://review.cyanogenmod.org/75213
Both HDR and ZSL (zero shutter lag - default since the last cam related commits) modes seem to work fine on my devices (kkbl xt925 and jbbl xt897).
Feedback will be welcome (as in the case of flash enable>shot>flash disable>shot killing JB cam in ZSL mode that I completely missed the last time - https://jira.cyanogenmod.org/browse/CYAN-5583 )
An unfortunate side-effect of this change is that the HDR mode will stop working correctly in Motorola specific camera apps.
Unless I'll find a way how to detect (in camera wrapper) that a Motorola cam app is being used...
As I'm currently focused on getting the cam working right specifically in CM camera app, I'm ready to merge it despite its breaking of Motorola cam apps at this point.18Everyone with JellyBean firmware/bootloader should use moto_msm8960_jbbl builds. Users who updated to KitKat firmware/bootloader need to use the moto_msm8960 builds. Thanks to kabaldan for setting up the build.18It needs to be euro LTE xt925, because:
1. there are BP crashes reported by european xt925 CM users (not happening on stock fw) that I want to look into
2. there's no core developer with euro xt925 (David has xt926, Emerson has Latin American xt925)
3. 3G coverage in CZ is the worst in Europe and it won't ever get better. Only the LTE coverage is being expanded by the mobile operators here now. So if I should get a new old device for whatever purpose, it should better be euro LTE capable, or I'll rather pass
KK update for xt925 seem to be set in stone and released soon, so that aspect should be fine.
Hopefully, there will be a 170€ xt925 deal done soon, so if you want to donate to this case, feel free to help. Íf not, no problem.
Please note that I'm leaving for two weeks vacation with my children and wife and my internet connection will be very spotty, so please expect me to be rather non responsive during that time.
Status update: I've received 129 USD on donations so far, so a part of the 170 EUR xt925 transaction has been covered by them.
Thanks!
The device should be on its way to me already.
As soon as I return from holidays (+/- 10 days), I should be able to start debugging the moto_msm8960 builds (kk bl - hopefully the official xt925 kk release will happen in time).
