Hello everybody.
I tried to root my xt925 with Droid HD Utility, but it failed, and now I am stuck at AP fastboot with this message:
Device is LOCKED. Status code: 0
Battery OK
Connect USB
Data cable
Partition (boot) Security Version Downgraded
Fastboot reason: Boot failure
All the options of the AP fastboot menu bring me to the AP fastboot...
I tried to fix it with RSD Lite (6.1.5) with the latest french (I'm french btw, and on SFR) and brasilian versions, which I've read it is the miracle solution, found on the sbf droid developers website.
I removed the getvar lines, and the result is I cannot even pass the first step, about the partition_signed.
I removed that line and I still can't pass the step about boot_signed.
Do you have any idea to fix it?
EDIT: I tried the Calro Puerto Rico 9.8.2Q-50-XT925_VQLM-24_AmericaMovil_PR_SIGNED_S12_USAVANQUCLAPRLA020.0R_VANQJBCLAPRLA_P008_A010_S1FF_CFC_fb.xml.zip
and I passed the partition signed step, but I stopped at devtree_signed...
up!
Gnafougna said:
up!
Click to expand...
Click to collapse
you can try this https://www.dropbox.com/s/bpjghbbv0v6r4v5/DROID_RAZR_HD_Utility_1.3.gpt fix.rar but YOU MUST SWAP THE FILES FOR THE ONES IN THE SBF YOU USE FIRST OR IT WILL BRICK YOUR PHONE.
just edit the xml file, swapping the md5's for the ones from your sbf.
then, swap out those files in the main directory with yours from the sbf.
shouldn't take you more than 5 minutes, its pretty easy, just copy and paste (make sure you don't put any spaces when pasting the md5's).
Thank you for this advice!
I downloaded the file, made sure that the drivers and the RSD were the same I haved installed before
But when it came to editing the .xml, I noticed the one present in the utility and the one I have to use, which is the last one I had on my phone, are not edited the same way.
There is no gpt_main0.bin line in the SFR SBF, but it has the getvar lines. and many more...
Here is its name : 9.8.2Q-8-XT925_VQU-22_USERSIGNED_S7_UCAVANQU02NA02F.0R_LSAVNQJBRTFR_P007_A004_CFC.xml
Code:
<?xml version="1.0" encoding="UTF-8"?>
<flashing>
<header>
<phone_model model="VANQUISH_U" />
<software_version version="XT925_vffr-user 4.1.2 9.8.2Q-8-XT925_VQU-22 1356075910 release-keysVANQUISH_U_BP_100700.250.66.01P" />
<interfaces>
<interface name="AP" />
</interfaces>
</header>
<steps interface="AP">
<step operation="getvar" var="max-download-size" />
<step operation="oem" var="fb_mode_set" />
<step operation="flash" partition="partition" filename="partition_signed" MD5="80ed27f9dbe459defefb819e92f1ea33" />
<step operation="flash" partition="sbl1" filename="sbl1_signed" MD5="880c035fc39d4e7c912f9115cca95474" />
<step operation="flash" partition="sbl2" filename="sbl2_signed" MD5="09e3f77464f1928ac86c4f1f89f58248" />
<step operation="flash" partition="sbl3" filename="sbl3_signed" MD5="30004967585b863d1f289766c84dd38b" />
<step operation="flash" partition="rpm" filename="rpm_signed" MD5="b10a918c890890e087e288bc3fa70ad7" />
<step operation="flash" partition="tz" filename="tz_signed" MD5="d49d8b9e2e04ff12cef3fb85f9bb656f" />
<step operation="flash" partition="aboot" filename="aboot_signed" MD5="65c80c1bb08c11c30473d211de4261d7" />
<step operation="flash" partition="modem" filename="modem_signed" MD5="d3026a789c4105bf49036ea0ccf76ac2" />
<step operation="flash" partition="fsg" filename="fsg_signed" MD5="2b71737990a3d15c396d3e08b590be17" />
<step operation="erase" partition="modemst1" />
<step operation="erase" partition="modemst2" />
<step operation="flash" partition="logo" filename="logo" MD5="6463dc057abf889f3b83a4d3da4cdd1e" />
<step operation="flash" partition="devtree" filename="devtree_signed" MD5="7d0c02350ac2b47bc17aa963f8cafcd9" />
<step operation="flash" partition="boot" filename="boot_signed" MD5="a1d34630cf93466491436a8473fbf0d5" />
<step operation="flash" partition="recovery" filename="recovery_signed" MD5="90e703f78451fb57961c6cf7fb013e2a" />
<step operation="flash" partition="system" filename="system_signed" MD5="c4074020cce6a50b8c1567c57e3a6ba6" />
<step operation="flash" partition="cdrom" filename="cdrom_signed" MD5="db97fe7f66377bf706e8263007ca4a53" />
<step operation="erase" partition="tombstones" />
<step operation="erase" partition="cache" />
<step operation="erase" partition="userdata" />
<step operation="oem" var="fb_mode_clear" />
</steps>
</flashing>
Do you have any idea on how I have to proceed with this?
Gnafougna said:
Thank you for this advice!
I downloaded the file, made sure that the drivers and the RSD were the same I haved installed before
But when it came to editing the .xml, I noticed the one present in the utility and the one I have to use, which is the last one I had on my phone, are not edited the same way.
There is no gpt_main0.bin line in the SFR SBF, but it has the getvar lines. and many more...
Here is its name : 9.8.2Q-8-XT925_VQU-22_USERSIGNED_S7_UCAVANQU02NA02F.0R_LSAVNQJBRTFR_P007_A004_CFC.xml
Code:
<?xml version="1.0" encoding="UTF-8"?>
<flashing>
<header>
<phone_model model="VANQUISH_U" />
<software_version version="XT925_vffr-user 4.1.2 9.8.2Q-8-XT925_VQU-22 1356075910 release-keysVANQUISH_U_BP_100700.250.66.01P" />
<interfaces>
<interface name="AP" />
</interfaces>
</header>
<steps interface="AP">
<step operation="getvar" var="max-download-size" />
<step operation="oem" var="fb_mode_set" />
<step operation="flash" partition="partition" filename="partition_signed" MD5="80ed27f9dbe459defefb819e92f1ea33" />
<step operation="flash" partition="sbl1" filename="sbl1_signed" MD5="880c035fc39d4e7c912f9115cca95474" />
<step operation="flash" partition="sbl2" filename="sbl2_signed" MD5="09e3f77464f1928ac86c4f1f89f58248" />
<step operation="flash" partition="sbl3" filename="sbl3_signed" MD5="30004967585b863d1f289766c84dd38b" />
<step operation="flash" partition="rpm" filename="rpm_signed" MD5="b10a918c890890e087e288bc3fa70ad7" />
<step operation="flash" partition="tz" filename="tz_signed" MD5="d49d8b9e2e04ff12cef3fb85f9bb656f" />
<step operation="flash" partition="aboot" filename="aboot_signed" MD5="65c80c1bb08c11c30473d211de4261d7" />
<step operation="flash" partition="modem" filename="modem_signed" MD5="d3026a789c4105bf49036ea0ccf76ac2" />
<step operation="flash" partition="fsg" filename="fsg_signed" MD5="2b71737990a3d15c396d3e08b590be17" />
<step operation="erase" partition="modemst1" />
<step operation="erase" partition="modemst2" />
<step operation="flash" partition="logo" filename="logo" MD5="6463dc057abf889f3b83a4d3da4cdd1e" />
<step operation="flash" partition="devtree" filename="devtree_signed" MD5="7d0c02350ac2b47bc17aa963f8cafcd9" />
<step operation="flash" partition="boot" filename="boot_signed" MD5="a1d34630cf93466491436a8473fbf0d5" />
<step operation="flash" partition="recovery" filename="recovery_signed" MD5="90e703f78451fb57961c6cf7fb013e2a" />
<step operation="flash" partition="system" filename="system_signed" MD5="c4074020cce6a50b8c1567c57e3a6ba6" />
<step operation="flash" partition="cdrom" filename="cdrom_signed" MD5="db97fe7f66377bf706e8263007ca4a53" />
<step operation="erase" partition="tombstones" />
<step operation="erase" partition="cache" />
<step operation="erase" partition="userdata" />
<step operation="oem" var="fb_mode_clear" />
</steps>
</flashing>
Do you have any idea on how I have to proceed with this?
Click to expand...
Click to collapse
Provide me with a link to your sbf file and I'll have a look at it later when I get home.
Tappin G2 Style
I found it on this website : sbf.droid-developers . org/vanquish_u/list.php
It's the third one from the bottom.
You'll find a screen of its content as an attachment.
Thank you so much for your time.
Gnafougna said:
I found it on this website : sbf.droid-developers . org/vanquish_u/list.php
It's the third one from the bottom.
You'll find a screen of its content as an attachment.
Thank you so much for your time.
Click to expand...
Click to collapse
after looking at the file, unfortunately, i can only suggest you swap only the files i have used in the utility and do it at your own risk.
i just dont know much about the 925 software and dont want to be responsible for making your phone worse.
i thought i could be of more help, sorry, i can not.
Related
i would like to ask whether anyone can help me with this or at least tell me whether it is possible to edit or not.
Volume Step sound in Sense 4.0 is "do re mi fa so la ti", total/max 'steps' count is 7. Original files name in '/system/media/audio/ui' are 'Volume-1.aac' to 'Volume-7.aac'
But after changing Volume Step in Tweak to "Finest", the max count became 15. Then the Volume Step sound became "do re mi fa so la [(ti) x 9]"
I wish to customize/add Volume Step sound of 8th step and above, so i played around with those "Volume-*.aac" in '/system/media/audio/ui/'. I tried duplicating those files and rename up to "Volume-15.aac" and restarted device, but there is no effects.
Which file (for example build.prop) in '/system/' should i edit, in order to make 'Volume-8.aac' to 'Volumn-15.aac' work?
Thanks in advance.
In order to add that resource I'm guessing you'll need to edit Settings.apk>res/xml/soundsettings.xml
The device will not play a resource that doesn't exist in the base.
Thanks for your quick response. =)
I google-ed around and installed apktool.
Below are the codes from the xml files, but i don't know which to edit. Any help here?
Code:
<?xml version="1.0" encoding="utf-8"?>
<com.htc.preference.HtcPreferenceScreen android:title="@string/sound_settings" android:key="sound_settings"
xmlns:android="http://schemas.android.com/apk/res/android"
xmlns:settings="http://schemas.android.com/apk/res/com.android.settings">
<com.htc.preference.HtcPreferenceCategory android:title="@string/sound_category_sound_title" android:key="sound_group" />
<com.htc.preference.HtcListPreference android:persistent="false" android:entries="@array/profile_item_list" android:title="@string/silent_list_title" android:key="silentlist" android:summary="@string/silent_mode_summary" android:dialogTitle="@string/profiles_dialog_title" android:entryValues="@array/animations_values" />
<com.htc.preference.HtcPreference android:persistent="false" android:entries="@array/profile_item_list" android:title="@string/silent_list_title" android:key="customize_silentlist" android:summary="@string/silent_mode_summary" android:dialogTitle="@string/profiles_dialog_title" android:entryValues="@array/animations_values" />
<com.htc.preference.HtcListPreference android:title="@string/musicfx_title" android:key="musicfx">
<intent android:targetPackage="com.android.musicfx" android:targetClass="com.android.musicfx.ControlPanelPicker" />
</com.htc.preference.HtcListPreference>
<com.android.settings.RingerVolumePreference android:persistent="false" android:title="@string/all_volume_title" android:key="ring_volume" android:summary="@string/volume_setting_summary" android:dialogTitle="@string/all_volume_title" android:streamType="ring" />
<com.htc.preference.HtcPreference android:persistent="true" android:title="@string/htc_beats_audio_settings_title" android:key="htc_sound_enhancer" />
<com.htc.preference.HtcCheckBoxPreference android:persistent="true" android:title="@string/vibrate_title" android:key="vibrate" android:summary="@string/vibrate_summary" android:dependency="silentlist" android:defaultValue="true" />
<com.htc.preference.HtcPreferenceCategory android:title="@string/sound_category_calls_title" android:key="sound_category_calls">
<com.htc.preference.HtcPreference android:persistent="true" android:title="@string/ringtone_title" android:key="ringtone" android:summary="@string/ringtone_summary" android:dependency="silentlist" android:dialogTitle="@string/ringtone_title" />
<com.htc.preference.HtcPreference android:persistent="true" android:title="@string/ringtone_title" android:key="ringtone_slot2" android:summary="@string/ringtone_summary" android:dependency="silentlist" android:dialogTitle="@string/ringtone_title" />
<com.htc.preference.HtcPreference android:persistent="true" android:title="@string/htc_ringtone_virbrate_title" android:key="ringtone_vibrate" android:summary="@string/htc_ringtone_virbrate_summary" android:dialogTitle="@string/htc_ringtone_virbrate_title" />
<com.android.settings.framework.preference.sound.HtcBePolitePreference android:dependency="silentlist" />
<com.android.settings.framework.preference.sound.HtcPocketModePreference android:dependency="silentlist" />
<com.android.settings.framework.preference.sound.HtcFlipToSpeakerPreference android:dependency="silentlist" />
</com.htc.preference.HtcPreferenceCategory>
<com.htc.preference.HtcPreferenceCategory android:title="@string/sound_category_notification_title" android:key="category_notification" />
<com.htc.preference.HtcPreference android:persistent="true" android:title="@string/htc_notification_sound_title" android:key="notification_sound" android:summary="@string/htc_notification_sound_summary" android:dependency="silentlist" android:dialogTitle="@string/htc_notification_sound_dialog_title" />
<com.htc.preference.HtcPreference android:persistent="true" android:title="@string/htc_notification_sound_vibrate_title" android:key="notification_sound_vibrate" android:summary="@string/htc_notification_sound_vibrate_summary" android:dialogTitle="@string/htc_notification_sound_vibrate_title" />
<com.htc.preference.HtcCheckBoxPreference android:persistent="false" android:title="@string/notification_pulse_title" android:key="notification_pulse" android:summary="@string/notification_pulse_summary" />
<com.htc.preference.HtcPreferenceCategory android:title="@string/sound_category_feedback_title" />
<com.htc.preference.HtcCheckBoxPreference android:title="@string/dtmf_tone_enable_title" android:key="dtmf_tone" android:defaultValue="true" android:summaryOn="@string/dtmf_tone_enable_summary_on" android:summaryOff="@string/dtmf_tone_enable_summary_off" />
<com.htc.preference.HtcListPreference android:persistent="true" android:entries="@array/htc_cdma_dtmf_tone_entries" android:title="@string/dtmf_tone_enable_title" android:key="htc_cdma_dtmf_tone" android:dependency="silentlist" android:defaultValue="0" android:entryValues="@array/htc_cdma_dtmf_tone_values" />
<com.htc.preference.HtcCheckBoxPreference android:title="@string/sound_effects_enable_title" android:key="sound_effects" android:defaultValue="true" android:summaryOn="@string/sound_effects_enable_summary_on" android:summaryOff="@string/sound_effects_enable_summary_off" />
<com.htc.preference.HtcCheckBoxPreference android:title="@string/lock_sounds_enable_title" android:key="lock_sounds" android:defaultValue="true" android:summaryOn="@string/lock_sounds_enable_summary_on" android:summaryOff="@string/lock_sounds_enable_summary_off" />
<com.htc.preference.HtcListPreference android:persistent="false" android:title="@string/powersaver_haptic_feedback" android:key="haptic_feedback_list" android:summary="@string/haptic_feedback_enable_summary_on" android:dialogTitle="@string/profiles_dialog_title" />
<com.htc.preference.HtcCheckBoxPreference android:title="@string/powersaver_haptic_feedback" android:key="haptic_feedback" android:defaultValue="true" android:summaryOn="@string/haptic_feedback_enable_summary_on" android:summaryOff="@string/haptic_feedback_enable_summary_off" />
<com.htc.preference.HtcCheckBoxPreference android:persistent="false" android:title="@string/roaming_ringtone_title" android:key="button_roaming_ringtone" android:summary="@string/roaming_ringtone_summary" android:dependency="silentlist" android:defaultValue="false" />
<com.htc.preference.HtcListPreference android:entries="@array/emergency_tone_entries" android:title="@string/emergency_tone_title" android:key="emergency_tone" android:summary="@string/emergency_tone_summary" android:entryValues="@array/emergency_tone_values" />
</com.htc.preference.HtcPreferenceScreen>
I'd need to search around for it. Keep looking for now, I won't have time until the weekend.
Sent from my HTC Sensation 4G using Tapatalk 2
GROGG88,
after cross-checking titles in '\res\xml\sound_settings.xml' with '\res\values\strings.xml', I found out that editing sound_settings.xml doesn't help.
Can you please check it out?
Thank you very much =)
I'll put it on my list of things to do. I'm out of town right now...
I hope that this helps someone.
I had a Motorola Droid Razr HD that was stuck in a boot loop. This is what I did to fix the issue.
1. Download RDS Lite
2. Put Phone into Fastboot mode.
a. Hold power and volume down for 10 seconds, then hold power, volume down, and volume up. When phone restarts release all buttons and quickly press and hold power, volume down, and volume up
3. Connected the phone to the PC and start RDS
4. Make a custom partition formatting xml file to be used with RDS. Here is the code that I used.
<?xml version="1.0"?>
<flashing>
<header>
<phone_model model="VANQUISH_CFC_IFLASH" />
<software_version version="vanquish_vzw-user 4.1.1 9.8.1Q_39 41 release-keysVANQUISH_BP_100700.210.64.05P" />
<interfaces>
<interface name="AP" />
</interfaces>
</header>
<steps interface="AP">
<step operation="erase" partition="modemst1" />
<step operation="erase" partition="modemst2" />
<step operation="erase" partition="cache" />
<step operation="erase" partition="userdata" />
<step operation="erase" partition="tombstones" />
</steps>
</flashing>
(In RDS)
4. selected the phone
5. browsed to that xml file just created
6. Run the xml file
(btw I just realized how fast I was wrting the whole topic ,try to read whoel text fast lol ;right now I charge my moto g)
Hi.I have battery Trouble with my Motorola Moto G(XT1032 UMTS)) after Flashing Original firmware
(yes I selected Proper 4.4.2 one:
Blur_Version.176.44.1.falcon_umts.EURetail.en.EU).
After Unplugging my moto g from Charger it worked for 2h 35 min
and then it soudenly restarterd and dropped to 1%.
Plugger is SilverCrest(yeah supermarket charrger 1A).
I've plugged it one more time
and Battery magicilly REcharged superb fast(4 minutes) up to 75% ,and right now is charging slowly(update it stayed at 75% slowly charged ,a bit faster at 80% and then go like a ****ing rocket up to 100%) ,what the hell??
There is some fix or I should Flash Stock Radio Kernel ,or stock kernel?
I used This guide to install stock rom:
Code:
http://forum.xda-developers.com/showthread.php?t=2542219
Btw I didn't had those files:
Code:
mfastboot flash system system.img_sparsechunk1
mfastboot flash system system.img_sparsechunk2
mfastboot flash system system.img_sparsechunk3
instead of them I had.
Code:
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
So I flashed Them instead.
And I tryed to do it on windows installed only the ADB/Fastboot minimal ,because I had the Motorola Device Manager ,but some troubles accures when I tryied to flash it(fastbootapi.dll not found).
I was flashing it using Linux standard Adb/Fastboot debian Packages(android-tools) Becasue using mfastboot didn't ,work same to Linux-fastboot; also when i look at *.xml file:
Code:
[B] <step operation="getvar" var="max-sparse-size" />
<step operation="oem" var="fb_mode_set" />
[I] <step operation="flash" partition="aboot" filename="emmc_appsboot.mbn" MD5="7ab4571da9966ecbe0455984ebe5d277" />[/I]
<step operation="reboot-bootloader" />[/B]
<step operation="flash" partition="partition" filename="gpt.bin" MD5="f31b7c507d3a5b76c949ff679d52a9e9" />
<step operation="flash" partition="motoboot" filename="motoboot.img" MD5="b4cb31c6b875dbb13ae2a155ae44e305" />
<step operation="flash" partition="logo" filename="logo.bin" MD5="187908e994f5b42710d13dbb5126d6d2" />
<step operation="flash" partition="boot" filename="boot.img" MD5="bf7f6c10474fe7925e0a5714c38e7128" />
<step operation="flash" partition="recovery" filename="recovery.img" MD5="b38dcca547511c0bfc1a746b61e63aed" />
<step operation="flash" partition="system" filename="system.img_sparsechunk.0" MD5="6b2d2ff1d5b588bd74420aa0da2671b4" />
<step operation="flash" partition="system" filename="system.img_sparsechunk.1" MD5="5f666cfcef3735fe9e774feed7ba4e2b" />
<step operation="flash" partition="system" filename="system.img_sparsechunk.2" MD5="0a1558ad2e1047a634483d05d6845911" />
<step operation="flash" partition="modem" filename="NON-HLOS.bin" MD5="0a7d2b8567f36e7552b52a01c776b47e" />
<step operation="erase" partition="modemst1" />
<step operation="erase" partition="modemst2" />
<step operation="flash" partition="fsg" filename="fsg.mbn" MD5="86b9e08048d0f5bb79ab32420cd483e8" />
<step operation="erase" partition="cache" />
<step operation="erase" partition="userdata" />
[B] <step operation="oem" var="fb_mode_clear" />[/B]
[U] <step operation="reboot-bootloader" />[/U]
I hadn't done bolded parts,I had done those parts ,and I restarted right into system in parts
It kinda seems like it is about Locking/unlocking bootloader ,but i dunno.
Should I Lock Bootloader and send phone to my brand carrier(I had no Carrier/Brand stuff ,and I've checked my system version before flashing CWM etc. ,btw you can even check whenever there is orther version
Counteryoland
Brandlay;P4).
Actually I could Use CWM Recovery image instead of that flashing from fastboot(I'm dumb) ,but at the orther hand I deleted all User stuff so I have more space...
So what should I do Flash CWMR reboot to recovery flash Backup or lock bootloaderr and send it to my carrier or flash some magical fixes(lol).
FAQ - Q25: Abrupt Drop Battery Issue (Battery suddenly drops to 0%)
You can flash the 4.4.3 US firmware image or 4.4.4 Retail Brazil image or wait for Retail Europe.
US_retail_XT1032_KXB21.14-L1.32_CFC.xml.zip (XT1032 - 4.4.3 Retail US)
XT1032_RETAIL-BR-SS_4.4.4_KXB21.14-L1.40_42_cid12_CFC_1FF.xml.zip (XT1032 - 4.4.4 Retail Brazil)
Flashing a custom kernel such as Faux will also help with battery life.
lost101 said:
FAQ - Q25: Abrupt Drop Battery Issue (Battery suddenly drops to 0%)
Flashing a custom kernel such as Faux will also help with battery life.
Click to expand...
Click to collapse
Thx I will first try to install Custom Kernel ,then Try Bra /U.S. 4.4.3(4.4.4. have some issues with apps),then install kernel on Bra .u.s ,and then install complete stock lock bootloader and send it to carrier.
Still it's easiest thing ever compared to finding correct Proloader after flashing wrong MTK6572 Preloader(yeah sure MTK 6572 is completly unbrickable ,but finding corect Preloader that's hardcore and tha's why I just don't have power for searching anything) ,btw thx sorry for oftopic.
I will post here if everything works fine.
The point I was trying to make was that your experience is common. Motorola released a patch that is included in 4.4.3 / 4.4.4. A custom kernel will improve battery life but as long as you remain on 4.4.2 - the sudden battery drop can occur at any time. Returning to carrier will not solve this, only updating will; and even then Motorola are still taking feedback on whether the issue has actually been fixed.
I had never drops on 4.4.2(In whole month peroid) you know ,and I throught it was because I flashed something incorrectly ,but on stock(4.4.2) there was like 3/8 mb fix from motorola(not 4.4.3).
Btw I got 4.4.4 eu update kernel is going to be replaced right(faux) I don't need to change boot.img back to stock or anything?
I am going to just flash the update I think topic can be closed.
A while ago I flashed CEE firmware to my Rogers xt925. Today I received KK over OTA. I flashed then cleared data and cache partitions thru recovery. Now WiFi is not working. I cannot connect to my WiFi anymore.
UPDATE: I was so stupid to try to flash 4.1.2 on the new KK using RSD and now I am stuck at fastboot. I should have ready previous posts carefully. I hope someone have a copy of the new KK so that I can flash it back.
Concerning the wifi issue. I forgot to mention that one time I needed to copy file called "WCNSS_qcom_wlan_nv.bin" in order to have WiFi back because I deleted a partition (forgot the name). But this was when on 4.1.2.
My wifi and other stuffs are working more than fine, but I lost root access
Carcass.br said:
My wifi and other stuffs are working more than fine, but I lost root access
Click to expand...
Click to collapse
I was able to start my RAZR but when I turn it off then reboot it goes back to fast boot and the only way to start it is from recovery.
The WiFi shows all available connections but nothing happens when I click on connect even if I enter a wrong password.
Please help.
Carcass.br said:
My wifi and other stuffs are working more than fine, but I lost root access
Click to expand...
Click to collapse
Can you try Towelroot to see if it works ?
Thank you
---------- Post added at 01:04 PM ---------- Previous post was at 01:01 PM ----------
goldfinsh said:
I was able to start my RAZR but when I turn it off then reboot it goes back to fast boot and the only way to start it is from recovery.
The WiFi shows all available connections but nothing happens when I click on connect even if I enter a wrong password.
Please help.
Click to expand...
Click to collapse
Remove 2 lines from the XML RSD lite file : partition_signed & tz_signed
then flash 4.1.2 RTFR. (or do it with your original 4.1.2 ROM if you wish)
Then Wipe your phone
Boot and download OTA from update menu and flash it.
You probably currently have the stick bit enabled because of your failed flash. You can try this with fastboot :
Code:
fastboot oem fb_mode_clear
Orphee said:
Can you try Towelroot to see if it works ?
Thank you
---------- Post added at 01:04 PM ---------- Previous post was at 01:01 PM ----------
Remove 2 lines from the XML RSD lite file : partition_signed & tz_signed
then flash 4.1.2 RTFR. (or do it with your original 4.1.2 ROM if you wish)
Then Wipe your phone
Boot and download OTA from update menu and flash it.
You probably currently have the stick bit enabled because of your failed flash. You can try this with fastboot :
Code:
fastboot oem fb_mode_clear
Click to expand...
Click to collapse
I did not find the two lines you mentionned in RSDLite.xml. the fastboot command did not do any change.
I thought we cannot downgrade from 4.4.2 to 4.1.2!
goldfinsh said:
I did not find the two lines you mentionned in RSDLite.xml. the fastboot command did not do any change.
I thought we cannot downgrade from 4.4.2 to 4.1.2!
Click to expand...
Click to collapse
Well, if your bootloader is not unlocked, I guess you can't downgrade.
Orphee said:
Well, if your bootloader is not unlocked, I guess you can't downgrade.
Click to expand...
Click to collapse
My bootloader is unlocked.
goldfinsh said:
My bootloader is unlocked.
Click to expand...
Click to collapse
So you can downgrade.
But "partition_signed" (GPT) & "tz_signed" (Trusted zone) can never be downgraded.
Here is the default RSD lite RTFR 4.1.2 xml file
Code:
<?xml version="1.0" encoding="UTF-8"?>
<flashing>
<header>
<phone_model model="VANQUISH_U" />
<software_version version="XT925_vffr-user 4.1.2 9.8.2Q-8-XT925_VQU-22 1356075910 release-keysVANQUISH_U_BP_100700.250.66.01P" />
<interfaces>
<interface name="AP" />
</interfaces>
</header>
<steps interface="AP">
[B][COLOR="Red"] <step operation="getvar" var="max-download-size" />[/COLOR][/B]
<step operation="oem" var="fb_mode_set" />
[B][COLOR="Red"] <step operation="flash" partition="partition" filename="partition_signed" MD5="80ed27f9dbe459defefb819e92f1ea33" />[/COLOR][/B]
<step operation="flash" partition="sbl1" filename="sbl1_signed" MD5="880c035fc39d4e7c912f9115cca95474" />
<step operation="flash" partition="sbl2" filename="sbl2_signed" MD5="09e3f77464f1928ac86c4f1f89f58248" />
<step operation="flash" partition="sbl3" filename="sbl3_signed" MD5="30004967585b863d1f289766c84dd38b" />
<step operation="flash" partition="rpm" filename="rpm_signed" MD5="b10a918c890890e087e288bc3fa70ad7" />
[B][COLOR="Red"] <step operation="flash" partition="tz" filename="tz_signed" MD5="d49d8b9e2e04ff12cef3fb85f9bb656f" />[/COLOR][/B]
<step operation="flash" partition="aboot" filename="aboot_signed" MD5="65c80c1bb08c11c30473d211de4261d7" />
<step operation="flash" partition="modem" filename="modem_signed" MD5="d3026a789c4105bf49036ea0ccf76ac2" />
<step operation="flash" partition="fsg" filename="fsg_signed" MD5="2b71737990a3d15c396d3e08b590be17" />
<step operation="erase" partition="modemst1" />
<step operation="erase" partition="modemst2" />
<step operation="flash" partition="logo" filename="logo" MD5="6463dc057abf889f3b83a4d3da4cdd1e" />
<step operation="flash" partition="devtree" filename="devtree_signed" MD5="7d0c02350ac2b47bc17aa963f8cafcd9" />
<step operation="flash" partition="boot" filename="boot_signed" MD5="a1d34630cf93466491436a8473fbf0d5" />
<step operation="flash" partition="recovery" filename="recovery_signed" MD5="90e703f78451fb57961c6cf7fb013e2a" />
<step operation="flash" partition="system" filename="system_signed" MD5="c4074020cce6a50b8c1567c57e3a6ba6" />
<step operation="flash" partition="cdrom" filename="cdrom_signed" MD5="db97fe7f66377bf706e8263007ca4a53" />
<step operation="erase" partition="tombstones" />
<step operation="erase" partition="cache" />
<step operation="erase" partition="userdata" />
<step operation="oem" var="fb_mode_clear" />
</steps>
</flashing>
The 1 red line must be deleted
The 2 other red lines must be deleted if you come from newer ROM like 4.4.2.
Orphee said:
So you can downgrade.
But "partition_signed" (GPT) & "tz_signed" (Trusted zone) can never be downgraded.
Here is the default RSD lite RTFR 4.1.2 xml file
Code:
<?xml version="1.0" encoding="UTF-8"?>
<flashing>
<header>
<phone_model model="VANQUISH_U" />
<software_version version="XT925_vffr-user 4.1.2 9.8.2Q-8-XT925_VQU-22 1356075910 release-keysVANQUISH_U_BP_100700.250.66.01P" />
<interfaces>
<interface name="AP" />
</interfaces>
</header>
<steps interface="AP">
[B][COLOR="Red"] <step operation="getvar" var="max-download-size" />[/COLOR][/B]
<step operation="oem" var="fb_mode_set" />
[B][COLOR="Red"] <step operation="flash" partition="partition" filename="partition_signed" MD5="80ed27f9dbe459defefb819e92f1ea33" />[/COLOR][/B]
<step operation="flash" partition="sbl1" filename="sbl1_signed" MD5="880c035fc39d4e7c912f9115cca95474" />
<step operation="flash" partition="sbl2" filename="sbl2_signed" MD5="09e3f77464f1928ac86c4f1f89f58248" />
<step operation="flash" partition="sbl3" filename="sbl3_signed" MD5="30004967585b863d1f289766c84dd38b" />
<step operation="flash" partition="rpm" filename="rpm_signed" MD5="b10a918c890890e087e288bc3fa70ad7" />
[B][COLOR="Red"] <step operation="flash" partition="tz" filename="tz_signed" MD5="d49d8b9e2e04ff12cef3fb85f9bb656f" />[/COLOR][/B]
<step operation="flash" partition="aboot" filename="aboot_signed" MD5="65c80c1bb08c11c30473d211de4261d7" />
<step operation="flash" partition="modem" filename="modem_signed" MD5="d3026a789c4105bf49036ea0ccf76ac2" />
<step operation="flash" partition="fsg" filename="fsg_signed" MD5="2b71737990a3d15c396d3e08b590be17" />
<step operation="erase" partition="modemst1" />
<step operation="erase" partition="modemst2" />
<step operation="flash" partition="logo" filename="logo" MD5="6463dc057abf889f3b83a4d3da4cdd1e" />
<step operation="flash" partition="devtree" filename="devtree_signed" MD5="7d0c02350ac2b47bc17aa963f8cafcd9" />
<step operation="flash" partition="boot" filename="boot_signed" MD5="a1d34630cf93466491436a8473fbf0d5" />
<step operation="flash" partition="recovery" filename="recovery_signed" MD5="90e703f78451fb57961c6cf7fb013e2a" />
<step operation="flash" partition="system" filename="system_signed" MD5="c4074020cce6a50b8c1567c57e3a6ba6" />
<step operation="flash" partition="cdrom" filename="cdrom_signed" MD5="db97fe7f66377bf706e8263007ca4a53" />
<step operation="erase" partition="tombstones" />
<step operation="erase" partition="cache" />
<step operation="erase" partition="userdata" />
<step operation="oem" var="fb_mode_clear" />
</steps>
</flashing>
The 1 red line must be deleted
The 2 other red lines must be deleted if you come from newer ROM like 4.4.2.
Click to expand...
Click to collapse
Thanks Orphee. I am again at 4.1.2 and wifi works just fine. I am downloading 4.4.2 but will install it later to see if someone else have the same wifi issue.
Thanks
WiFi not working
I managed to get back to JB and WiFi worked fine. I then upgraded to KK thru OTA then did a factory reset but WiFi is not working. As I mentioned, I can select a connection then I enter a password but nothing happens whether the password is correct or not.
Orphee said:
Can you try Towelroot to see if it works ?
Click to expand...
Click to collapse
I tried but it did not work. I could root flashing a custom recovery and applying SU when I tried to reboot via recovery
Can anyone confirm then that rogers has indeed the ota out for the 925...thx
Sent from my RAZR HD using XDA Free mobile app
Is there a SBF floating around I can flash with RSD for Rogers? I'm currently running the CEE 4.4.2 test/beta partitions using @Orphee's method from a while back.
goldfinsh said:
I managed to get back to JB and WiFi worked fine. I then upgraded to KK thru OTA then did a factory reset but WiFi is not working. As I mentioned, I can select a connection then I enter a password but nothing happens whether the password is correct or not.
Click to expand...
Click to collapse
It's same for me too
goldfinsh said:
I managed to get back to JB and WiFi worked fine. I then upgraded to KK thru OTA then did a factory reset but WiFi is not working. As I mentioned, I can select a connection then I enter a password but nothing happens whether the password is correct or not.
Click to expand...
Click to collapse
I managed to get wifi back by deleting everything in /persist...
I had the issue on jelly bean from clearing that partition, and then copying WCNSS_qcom_wlan_nv.bin to persist fixed it, but on kitkat it seems to be the opposite. Make sure you have your root explorer set to show hidden files, clear everything in persist, then reboot.
Hi,
I have same problem as topic starter. So, do we have any chance to fix that problem?
I try few 4.1.2 stock roms (CEE, O2, RTFR) and nothing. On 4.1.2 i have wifi conection but after i do 4.4.2 OTA update wifi doesnt work
Also, on 4.4.2 when i check system update via my LTE it show me: "we have system update which one will fix your wifi, but you can install it only via wifi" ... Funny joke (
Hi Motorola users
in this post i want show how to make your Razr HD XT925 kitkat updateable
1st you need to download and install Motorola USB Drivers windows user can download from there http://www.mediafire.com/download/28vykc1yb39dwb7/MotorolaDeviceManager_2.4.5.exe and mac user can download from there http://www.mediafire.com/download/qos8avzbmi0aqbf/MDM_Installer_2.1.8.dmg
2nd you need you have last version on RSDLite (can found in forum)
3rd download this Firmwares : http://www.mediafire.com/download/fxyqwhepfdpn0n1/S27+4.1.2+Retail+Central+Europe+updateable.zip
4th when your download is complete extract the zip file and open .xml (action script file) with world pad or notepad++
then delete all line you can use Ctrl+A keys :laugh:
copy this line to keyboard and past in .xml file than save it
Code:
<?xml version="1.0" encoding="UTF-8"?>
<flashing>
<header>
<phone_model model="VANQUISH_U" />
<software_version version="XT925_vffr-user 4.1.2 9.8.2Q-8-XT925_VQU-22 1356075910 release-keysVANQUISH_U_BP_100700.250.66.01P" />
<interfaces>
<interface name="AP" />
</interfaces>
</header>
<steps interface="AP">
<step operation="oem" var="fb_mode_set" />
<step operation="flash" partition="sbl1" filename="sbl1_signed" MD5="880c035fc39d4e7c912f9115cca95474" />
<step operation="flash" partition="sbl2" filename="sbl2_signed" MD5="09e3f77464f1928ac86c4f1f89f58248" />
<step operation="flash" partition="sbl3" filename="sbl3_signed" MD5="30004967585b863d1f289766c84dd38b" />
<step operation="flash" partition="rpm" filename="rpm_signed" MD5="b10a918c890890e087e288bc3fa70ad7" />
<step operation="flash" partition="tz" filename="tz_signed" MD5="d49d8b9e2e04ff12cef3fb85f9bb656f" />
<step operation="flash" partition="aboot" filename="aboot_signed" MD5="65c80c1bb08c11c30473d211de4261d7" />
<step operation="flash" partition="modem" filename="modem_signed" MD5="d3026a789c4105bf49036ea0ccf76ac2" />
<step operation="flash" partition="fsg" filename="fsg_signed" MD5="2b71737990a3d15c396d3e08b590be17" />
<step operation="erase" partition="modemst1" />
<step operation="erase" partition="modemst2" />
<step operation="flash" partition="logo" filename="logo" MD5="6463dc057abf889f3b83a4d3da4cdd1e" />
<step operation="flash" partition="devtree" filename="devtree_signed" MD5="7d0c02350ac2b47bc17aa963f8cafcd9" />
<step operation="flash" partition="boot" filename="boot_signed" MD5="a1d34630cf93466491436a8473fbf0d5" />
<step operation="flash" partition="recovery" filename="recovery_signed" MD5="90e703f78451fb57961c6cf7fb013e2a" />
<step operation="flash" partition="system" filename="system_signed" MD5="c4074020cce6a50b8c1567c57e3a6ba6" />
<step operation="flash" partition="cdrom" filename="cdrom_signed" MD5="db97fe7f66377bf706e8263007ca4a53" />
<step operation="erase" partition="tombstones" />
<step operation="erase" partition="cache" />
<step operation="erase" partition="userdata" />
<step operation="oem" var="fb_mode_clear" />
</steps>
</flashing>
5th open RSDLite and brows new .xml file put your XT925 device in fastboot mode and flash it wait to pass
6th now you can connect your XT925 to internet access (WiFi or Mobile Data) and go to setting - about phone - check for update
and enjoy the 4.4.2 official
good luck
Uprade finger in the nose.
Thanks too you.
Heyho, thanks for the Tut, i will give it a shot
One Question, is this way deleting your internal or external sd-files?
greetz Esok44
esok44 said:
Heyho, thanks for the Tut, i will give it a shot
One Question, is this way deleting your internal or external sd-files?
greetz Esok44
Click to expand...
Click to collapse
yes when you use the RSDLite for Flash your device for this commend :
<step operation="erase" partition="tombstones" />
<step operation="erase" partition="cache" />
<step operation="erase" partition="userdata" />
but when you try update from internet (OTA) dose not delete your personal files
s27moto said:
yes when you use the RSDLite for Flash your device for this commend :
<step operation="erase" partition="tombstones" />
<step operation="erase" partition="cache" />
<step operation="erase" partition="userdata" />
but when you try update from internet (OTA) dose not delete your personal files
Click to expand...
Click to collapse
So Backup all Pictures and stuff is advised...
Damn this gonna take a long time xD
Does this procedure work for any razrd hd xt925 region? I'm from Argentina, need to know if this firmware/modem will work with our region band. Thanks in advance!
s27moto said:
Hi Motorola users
in this post i want show how to make your Razr HD XT925 kitkat updateable
1st you need to download and install Motorola USB Drivers windows user can download from there http://www.mediafire.com/download/28vykc1yb39dwb7/MotorolaDeviceManager_2.4.5.exe and mac user can download from there http://www.mediafire.com/download/qos8avzbmi0aqbf/MDM_Installer_2.1.8.dmg
2nd you need you have last version on RSDLite (can found in forum)
3rd download this Firmwares : http://www.mediafire.com/download/fxyqwhepfdpn0n1/S27+4.1.2+Retail+Central+Europe+updateable.zip
4th when your download is complete extract the zip file and open .xml (action script file) with world pad or notepad++
then delete all line you can use Ctrl+A keys :laugh:
copy this line to keyboard and past in .xml file than save it
Code:
<?xml version="1.0" encoding="UTF-8"?>
<flashing>
<header>
<phone_model model="VANQUISH_U" />
<software_version version="XT925_vffr-user 4.1.2 9.8.2Q-8-XT925_VQU-22 1356075910 release-keysVANQUISH_U_BP_100700.250.66.01P" />
<interfaces>
<interface name="AP" />
</interfaces>
</header>
<steps interface="AP">
<step operation="oem" var="fb_mode_set" />
<step operation="flash" partition="sbl1" filename="sbl1_signed" MD5="880c035fc39d4e7c912f9115cca95474" />
<step operation="flash" partition="sbl2" filename="sbl2_signed" MD5="09e3f77464f1928ac86c4f1f89f58248" />
<step operation="flash" partition="sbl3" filename="sbl3_signed" MD5="30004967585b863d1f289766c84dd38b" />
<step operation="flash" partition="rpm" filename="rpm_signed" MD5="b10a918c890890e087e288bc3fa70ad7" />
<step operation="flash" partition="tz" filename="tz_signed" MD5="d49d8b9e2e04ff12cef3fb85f9bb656f" />
<step operation="flash" partition="aboot" filename="aboot_signed" MD5="65c80c1bb08c11c30473d211de4261d7" />
<step operation="flash" partition="modem" filename="modem_signed" MD5="d3026a789c4105bf49036ea0ccf76ac2" />
<step operation="flash" partition="fsg" filename="fsg_signed" MD5="2b71737990a3d15c396d3e08b590be17" />
<step operation="erase" partition="modemst1" />
<step operation="erase" partition="modemst2" />
<step operation="flash" partition="logo" filename="logo" MD5="6463dc057abf889f3b83a4d3da4cdd1e" />
<step operation="flash" partition="devtree" filename="devtree_signed" MD5="7d0c02350ac2b47bc17aa963f8cafcd9" />
<step operation="flash" partition="boot" filename="boot_signed" MD5="a1d34630cf93466491436a8473fbf0d5" />
<step operation="flash" partition="recovery" filename="recovery_signed" MD5="90e703f78451fb57961c6cf7fb013e2a" />
<step operation="flash" partition="system" filename="system_signed" MD5="c4074020cce6a50b8c1567c57e3a6ba6" />
<step operation="flash" partition="cdrom" filename="cdrom_signed" MD5="db97fe7f66377bf706e8263007ca4a53" />
<step operation="erase" partition="tombstones" />
<step operation="erase" partition="cache" />
<step operation="erase" partition="userdata" />
<step operation="oem" var="fb_mode_clear" />
</steps>
</flashing>
5th open RSDLite and brows new .xml file put your XT925 device in fastboot mode and flash it wait to pass
6th now you can connect your XT925 to internet access (WiFi or Mobile Data) and go to setting - about phone - check for update
and enjoy the 4.4.2 official
good luck
Click to expand...
Click to collapse
Great stuff! Done!
Now...any suggestion about what to do when you download OTA KK several times but it always fails to install?!? Cell phone turns off, starts the install with the android screen and all of sudden, it restarts itself in the middle of install. When into 4.1.2 again, there is a message saying the installation has failed!
Edit: I kept trying and smetimes it dont even finish the download process...i.e.: The download bar progress goes up to 75-90% and then the download process restarts itself. On top of that, it seems that these uncompleted downloads are being kept in memory since my available storage get smaller afer every attempt!
When I try to download it using Device manager it says my cell phone is up to date running 4.1.2!
Is there a way to install OTA KK via RSD lite?!?
no kk via rsdlite ,but you can flash it from sd card using Orphee update script. All is in this thread.
Flash european 4.1.2 cee then flash Kabalan OTA with Orphee script
hbenz2008 said:
no kk via rsdlite ,but you can flash it from sd card using Orphee update script. All is in this thread.
Flash european 4.1.2 cee then flash Kabalan OTA with Orphee script
Click to expand...
Click to collapse
no need to do this part
"flash Kabalan OTA with Orphee script"
So i rsd from cm11 jbbl to claro pr jb i now have the ota do i modify it or just flash in recovery, any need to wipe b4 flashing?
Sent from my XT925 using XDA Free mobile app
I'm trying to flash the KK OTA RE DE but it always fail while attempting to flash via JB custom recovery in the applying "updater binary from zip" step. Is there someone who can take a look at this updater file in order to find any anomalies?
https://mega.co.nz/#!x1YmSQoI!-6OU77-xBNNFODwNOyE30kpnW1AsderimMrRBlOf3bU
P.S.: This link is to the original OTA with the stock script. I'm not sure if the problem is in the modified updater script and or if it has something to do with those 3 lines we have to delete from the XML file!
Solved!
http://forum.xda-developers.com/showthread.php?p=56598858
Sent from my Razr HD/Unlocked KKBL/TWRP2.8.1.0/Latest CM11 M11 Nightly/ART Runtime
Diffs?
What's different about this method with flashing CEE European stock to trigger the OTA?
Did this, but after the update, the boot sequence is stuck at the Motorola Dual Core screen. Going to the recovery menu does not seem to help. How do I troubleshoot from here? Thank you.
Clear davlik cache
It's showing the following error for me:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now i'm stuck on fastboot screen. What to do?
is your bootloader unlocked?
hbenz2008 said:
is your bootloader unlocked?
Click to expand...
Click to collapse
Yes. It's unlocked. I was using the last cm11 nightly for jbbl.
Edit. So I finally managed to install an old firmware via android through RSDlite, but when I turn on the phone shortly after the warning unlocked bootloader, the screen goes black.
Ok, give rsd lite 6.1.5 a shot or 6.1.6
hbenz2008 said:
Ok, give rsd lite 6.1.5 a shot or 6.1.6
Click to expand...
Click to collapse
Finally worked with rsd lite 6.1.5. Thank you!