Ok Guys,
after playing a little bit with my Razr running the T-Mobile ICS Leak i got it finaly bricked
< CRACKFLASHER
Don't ask how i did this, that doesn't matter
I tryed to restore my Backup that i did before in CWM, but get an Error restoring the System.
So my only way back to an working Phone was RSD an here I'm.
I'll post you my .XML-File for the T-Mobile 2.3.6, so maybe you can do it the same way > Just Copy & Paste.
<?xml version="1.0" encoding="UTF-8"?>
<flashing>
<header>
<phone_model model="UMTS_SPYDER"/>
<software_version version="umts_spyder-user 2.3.6 6.5.1-167_SPU-15-M2-1-DE 1328517836 release-keysSPYDERBP_U_03.1C.91P"/>
<interfaces>
<interface name="AP"/>
</interfaces>
</header>
<steps interface="AP">
<step operation="flash" partition="mbm" filename="allow-mbmloader-flashing-mbm.bin" MD5="3BD5A466807C6BD4170BA22518C03DA7"/>
<step operation="reboot-bootloader"/>
<step operation="flash" partition="mbmloader" filename="mbmloader.bin" MD5="9D88A534DC24ABB24757BD8C357E82A0"/>
<step operation="flash" partition="mbm" filename="mbm.bin" MD5="E718C75A0163E255C96E0B2A3E32F70C"/>
<step operation="reboot-bootloader"/>
<step operation="erase" partition="cache"/>
<step operation="erase" partition="userdata"/>
<step operation="erase" partition="emstorage"/>
<step operation="flash" partition="logo.bin" filename="logo.bin" MD5="06c07c2970460a4e656a3206859a3617"/>
<step operation="flash" partition="ebr" filename="ebr_signed" MD5="3d655a67765d001a89d73a3dab34d413"/>
<step operation="flash" partition="mbr" filename="mbr_signed" MD5="d45a2d3d3d440fed6840aa1f0188e67e"/>
<step operation="flash" partition="system" filename="system_signed" MD5="8d087c352a7d7c97039d37714de03489"/>
<step operation="flash" partition="emstorage" filename="emstorage.img" MD5="F248FF87BFAB03E3278891AD151ADDE7"/>
<step operation="flash" partition="webtop" filename="webtop_signed" MD5="7ad932b66a7ec9935a93cc3a4b1645b6"/>
<step operation="flash" partition="radio" filename="radio.img" MD5="9a833b62d4f3574dc8b41141f4c5b731"/>
</steps>
</flashing>
Delete these 3 Lines, if you don't want to loose your data!
I prefere an clean install, that's your choice
After flashing with RSD turn off your Device and boot into Recovery via AP Fastboot!
Flash the leaked Update.zip from there and reboot your Device.
Ofcourse there's no Root anymore!
Edit: I've used an Factory Cable for flashing...
This is perfectly right
But in case of wiping userdata, if you don't want to loose your data, you may delete the lines "erase userdata" and "emstorage". If the phone won't come up, then perform a full wipe.
In most cases it's enough to flash only "system" with RSD.
RSD isn't the only solution!! yes, RSD is easy to solve your problem but sometimes there is another way.
If you have install the bootstrap, there is a big chance to revive your phone without RSD & you will not lose root. But now, it's too late.
i got error on RDS lite Status 6/18.
Failed flashing process. Failed flashing process. 6/18 flash cdt.bin "cdt.bin_signed" -> Phone returned FAIL.;phone connected
I wiped full data/factory reset before I follow your method
LOOK @ the XML I've posted. You have to delete the Lines, that give you failures.
BTW: I've tried to restore my Nandroid of this Leak via CWM. But only get the Error restoring System. I got 2 Nandroid-Backups on my SD. One clean, right after flashed the Leak and one complete Setup'd. But both of them wouldn't work.
Gesendet von meinem XT910 mit Tapatalk 2
Yes, i DELETED two line as you posted.
It doesn't work for me.
HSD-Pilot said:
Ok Guys,
after playing a little bit with my Razr running the T-Mobile ICS Leak i got it finaly bricked
< CRACKFLASHER
Don't ask how i did this, that doesn't matter
I tryed to restore my Backup that i did before in CWM, but get an Error restoring the System.
So my only way back to an working Phone was RSD an here I'm.
I'll post you my .XML-File for the T-Mobile 2.3.6, so maybe you can do it the same way.
<flashing>
<header>
<phone_model model="UMTS_SPYDER"/>
<software_version version="umts_spyder-user 2.3.6 6.5.1-167_SPU-15-M2-1-DE 1328517836 release-keysSPYDERBP_U_03.1C.91P"/>
<interfaces>
<interface name="AP"/>
</interfaces>
</header>
<steps interface="AP">
<step operation="flash" partition="mbm" filename="allow-mbmloader-flashing-mbm.bin" MD5="3BD5A466807C6BD4170BA22518C03DA7"/>
<step operation="reboot-bootloader"/>
<step operation="flash" partition="mbmloader" filename="mbmloader.bin" MD5="9D88A534DC24ABB24757BD8C357E82A0"/>
<step operation="flash" partition="mbm" filename="mbm.bin" MD5="E718C75A0163E255C96E0B2A3E32F70C"/>
<step operation="reboot-bootloader"/>
<step operation="erase" partition="cache"/>
<step operation="erase" partition="userdata"/> Delete these 2 Lines, if you don't want to loose your data!
<step operation="erase" partition="emstorage"/> I prefere an clean install, that's your choice
<step operation="flash" partition="logo.bin" filename="logo.bin" MD5="06c07c2970460a4e656a3206859a3617"/>
<step operation="flash" partition="ebr" filename="ebr_signed" MD5="3d655a67765d001a89d73a3dab34d413"/>
<step operation="flash" partition="mbr" filename="mbr_signed" MD5="d45a2d3d3d440fed6840aa1f0188e67e"/>
<step operation="flash" partition="system" filename="system_signed" MD5="8d087c352a7d7c97039d37714de03489"/>
<step operation="flash" partition="emstorage" filename="emstorage.img" MD5="F248FF87BFAB03E3278891AD151ADDE7"/>
<step operation="flash" partition="webtop" filename="webtop_signed" MD5="7ad932b66a7ec9935a93cc3a4b1645b6"/>
<step operation="flash" partition="radio" filename="radio.img" MD5="9a833b62d4f3574dc8b41141f4c5b731"/>
</steps>
</flashing>
After flashing with RSD the Phone boots into Recovery, as you know.
Flash the Update.zip from there and reboot your Device.
Ofcourse there's no Root anymore!
Edit: I've used an Factory Cable for flashing...
Click to expand...
Click to collapse
Also the this line "<step operation="flash" partition="emstorage" filename="emstorage.img" has to be deleted, if you want to retain your data.
---------- Post added at 01:08 AM ---------- Previous post was at 01:07 AM ----------
kenosis said:
Yes, i DELETED two line as you posted.
It doesn't work for me.
Click to expand...
Click to collapse
You have to delete the following lines: cdt.bin, devtree, cdrom, boot, recovery. And as I can see in your post you didn't delete the line cdt.bin! Please a bit more attention next time..
Not just the two lines.
LOOK @ your XML and then @ mine. There's no cdt.bin in mine.
Maybe just copy and paste
Gesendet von meinem XT910 mit Tapatalk 2
I copied your XML and trying. Seems like it is working. i will let you know again
Thanks for the guide.
HSD-Pilot said:
Not just the two lines.
LOOK @ your XML and then @ mine. There's no cdt.bin in mine.
Maybe just copy and paste
Gesendet von meinem XT910 mit Tapatalk 2
Click to expand...
Click to collapse
@HSD-Pilot: Don't forget the third line, read above
If you have backup root using Vodoo OTA RootKeeper, it will make file su-backup immutable. The problem with the CWM restore is, it tries to delete all files in /system and failed at this file. That y u got "Error restoring System". But actually, the restore process is done until complete. You should just restart after that.
I restarted my phone after that error. Screen was black and no display.
Hmmm... Ok , but now it's too late or not?
If I restore my Nandroid now, would it work?
I'[email protected] right now, so there's no PC in case of brick.
No Crackflash without my PC
Gesendet von meinem XT910 mit Tapatalk 2
Screen turns BLACK after MOTO logo and shows nothing.
HSD-Pilot said:
Hmmm... Ok , but now it's too late or not?
If I restore my Nandroid now, would it work?
I'[email protected] right now, so there's no PC in case of brick.
No Crackflash without my PC
Gesendet von meinem XT910 mit Tapatalk 2
Click to expand...
Click to collapse
How you want to restore a nandroid?? There's no root on your device..
dtrail1 said:
How you want to restore a nandroid?? There's no root on your device..
Click to expand...
Click to collapse
Yesssss, I forgot
Gesendet von meinem XT910 mit Tapatalk 2
HSD-Pilot said:
Yesssss, I forgot
Gesendet von meinem XT910 mit Tapatalk 2
Click to expand...
Click to collapse
And by the way: Better mark the second line ("flash emstorage") to retain userdata, else someone try this and perhaps will get chaotic data partition...(now the third time I've said this ) There are THREE lines to delete for retaining userdata!!!
kenosis said:
Screen turns BLACK after MOTO logo and shows nothing.
Click to expand...
Click to collapse
Maybe put the Lines to delete Data back in the XML and try again
Gesendet von meinem XT910 mit Tapatalk 2
Our experience might be differ. But My phone survived that.
As long as you got these files in your /system, there is still a chance to fix without RSD.
Code:
/system/bin/hijack
/system/bin/logwrapper
/system/bin/logwrapper.bin
/preinstall/recovery/
HSD-Pilot said:
Maybe put the Lines to delete Data back in the XML and try again
Gesendet von meinem XT910 mit Tapatalk 2
Click to expand...
Click to collapse
Do you mean "Put deleted 3 lines back" to get data back?
Related
Hello,
I wanted to add Advanced Reboot Menu on my RAZR HD.
Max_choco did it for the RAZR I (+ some other stuffs) http://forum.xda-developers.com/showthread.php?t=2393777
I used his work to build my own framework-res.apk and android.policy.jar
{
"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"
}
I made a flashable zip for CWM Recovery.
I SUGGEST YOU TO MAKE A FULL NANDROID BACKUP BEFORE DOING ANYTHING. I'M NOT RESPONSIBLE OF ANY DAMAGE YOU COULD DO TO YOU OR YOUR PHONE. USE IT AT YOUR OWN RISK.
Modified files are (make a backup at least) :
/system/framework/framework-res.apk
/system/framework/android.policy.jar
/system/framework/android.policy.odex (original deleted with flashable zip)
My ROM is DEODEXED, It should work on ODEXED ROM too, but I can't be sure.
Built with Retail FR 4.1.2 based ROM.
Thanks to max_choco for his work on the Razr I.
Right on. I've been planning on doing this for the 926. This ought to be a big help. Thanks for the hard work.
Sent from my DROID RAZR HD using Tapatalk 4
unfortunately didnt work on odexed o2 Rom.
Got a bootloop right now, now i got some work to do, to fix it
Hope, i can fix it, without installing backup
esok44 said:
unfortunately didnt work on odexed o2 Rom.
Got a bootloop right now, now i got some work to do, to fix it
Hope, i can fix it, without installing backup
Click to expand...
Click to collapse
erf, sorry...
Did you try wipe cache & dalvik ?
Orphee said:
erf, sorry...
Did you try wipe cache & dalvik ?
Click to expand...
Click to collapse
Yepp did, but it seems like my odex files for android policy and framework-res are lost...
esok44 said:
Yepp did, but it seems like my odex files for android policy and framework-res are lost...
Click to expand...
Click to collapse
Yes, the flashable zip must delete android.policy.odex as there are deodexed (framework-res.apk does not have odex).
I should had odex to the #1 list
Orphee said:
Yes, the flashable zip must delete android.policy.odex as there are deodexed (framework-res.apk does not have odex).
I should had odex to the #1 list
Click to expand...
Click to collapse
Well alright, so i need to get a hand on the .odex file, do you have it or do you now how to get it
Hope it will help you.
All files come from Retail FR original ROM.
Orphee said:
Hope it will help you.
All files come from Retail FR original ROM.
Click to expand...
Click to collapse
I will let you know
Have you any idea, how to extract stuff from the motorola OTA-updates.
Maybe I'm wrong, but OTA updates are only patch files modifiyng the original from the ROM.
Because of this you must have original ROM to update OTA, any modified file will fail the update.
You need to find the full RSD Lite flashable ROM.
Orphee said:
Hope it will help you.
All files come from Retail FR original ROM.
Click to expand...
Click to collapse
I'm not sure, should i set permissions to 0644?
Cause it's still not booting up
Anyone got an idea??
---------- Post added at 02:23 PM ---------- Previous post was at 02:20 PM ----------
Orphee said:
Maybe I'm wrong, but OTA updates are only patch files modifiyng the original from the ROM.
Because of this you must have original ROM to update OTA, any modified file will fail the update.
You need to find the full RSD Lite flashable ROM.
Click to expand...
Click to collapse
I got the Flashable RSD-Lite .zip, i managed to get the system_signed, but i cant do nothing with it oO
Yes the files should be 644, but maybe O2 and RTFR aren't compatible... Did you make a nandroid backup ?
Orphee said:
Yes the files should be 644, but maybe O2 and RTFR aren't compatible... Did you make a nandroid backup ?
Click to expand...
Click to collapse
Of course not, you now the deal, it always goes wrong when u dont make a backup.
is it possible to compile the odex files from the apk's?
Then i would just pull the apk and make a new one
You have your original O2 rom for RSD Lite ?
If yes, unzip it, open XML file
Here a exemple :
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_VQUL-16 1354498168 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="374c5ce95704791927c2b72543cc7f16" />
<step operation="flash" partition="sbl1" filename="sbl1_signed" MD5="04faedb3ac5e2401f233856b801eab73" />
<step operation="flash" partition="sbl2" filename="sbl2_signed" MD5="131ff66e7d861bfedfd2c7b5ca428381" />
<step operation="flash" partition="sbl3" filename="sbl3_signed" MD5="52bafe485a64f12ed2fda312c60f0a34" />
<step operation="flash" partition="rpm" filename="rpm_signed" MD5="919d0b340cfdd5fc7c541803db65c2d6" />
<step operation="flash" partition="tz" filename="tz_signed" MD5="ed1c505e36e769ccf0bb3c10e46dd62b" />
<step operation="flash" partition="aboot" filename="aboot_signed" MD5="61ddd4c78a3d1ff64567740446f803fd" />
<step operation="flash" partition="modem" filename="modem_signed" MD5="af7fa6a2a496fe4d89778829bf40bb4a" />
<step operation="flash" partition="fsg" filename="fsg_signed" MD5="74031834280d2e5cec7f40d620c4024d" />
<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="5d27060578eca132919570e9208885e4" />
<step operation="flash" partition="recovery" filename="recovery_signed" MD5="21cdb4fd40b8d9ebb9aa9565c68eeb5f" />
<step operation="flash" partition="system" filename="system_signed" MD5="fd6b6dc463e2a03b8d507eb51e7eda8b" />
<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>
Remove from it the following lines :
<step operation="getvar" var="max-download-size" />
<step operation="flash" partition="logo" filename="logo" MD5="6463dc057abf889f3b83a4d3da4cdd1e" /> (if your bootloader is unlocked and you flashed custom boot logo. And don't want it to be restored to WARNING UNLOCKED BOOTLOADER)
<step operation="flash" partition="recovery" filename="recovery_signed" MD5="21cdb4fd40b8d9ebb9aa9565c68eeb5f" /> (Remove if if you are unlocked and have a custom recovery like CWM)
<step operation="erase" partition="userdata" /> (VERY IMPORTANT, WITHOUT REMOVING THIS LINE, YOU LOST ALL YOUR DATA)
Exemple when all stuff removed :
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_VQUL-16 1354498168 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="partition" filename="partition_signed" MD5="374c5ce95704791927c2b72543cc7f16" />
<step operation="flash" partition="sbl1" filename="sbl1_signed" MD5="04faedb3ac5e2401f233856b801eab73" />
<step operation="flash" partition="sbl2" filename="sbl2_signed" MD5="131ff66e7d861bfedfd2c7b5ca428381" />
<step operation="flash" partition="sbl3" filename="sbl3_signed" MD5="52bafe485a64f12ed2fda312c60f0a34" />
<step operation="flash" partition="rpm" filename="rpm_signed" MD5="919d0b340cfdd5fc7c541803db65c2d6" />
<step operation="flash" partition="tz" filename="tz_signed" MD5="ed1c505e36e769ccf0bb3c10e46dd62b" />
<step operation="flash" partition="aboot" filename="aboot_signed" MD5="61ddd4c78a3d1ff64567740446f803fd" />
<step operation="flash" partition="modem" filename="modem_signed" MD5="af7fa6a2a496fe4d89778829bf40bb4a" />
<step operation="flash" partition="fsg" filename="fsg_signed" MD5="74031834280d2e5cec7f40d620c4024d" />
<step operation="erase" partition="modemst1" />
<step operation="erase" partition="modemst2" />
<step operation="flash" partition="devtree" filename="devtree_signed" MD5="7d0c02350ac2b47bc17aa963f8cafcd9" />
<step operation="flash" partition="boot" filename="boot_signed" MD5="5d27060578eca132919570e9208885e4" />
<step operation="flash" partition="system" filename="system_signed" MD5="fd6b6dc463e2a03b8d507eb51e7eda8b" />
<step operation="flash" partition="cdrom" filename="cdrom_signed" MD5="db97fe7f66377bf706e8263007ca4a53" />
<step operation="erase" partition="tombstones" />
<step operation="erase" partition="cache" />
<step operation="oem" var="fb_mode_clear" />
</steps>
</flashing>
Now flash it with RSD lite (point XML file with RSD Lite) and cross fingers.
Edit : Or you can do the minimum :
Take system_signed file and flash it with fastboot in AP :
fastboot.exe flash system system_signed
Orphee said:
Edit : Or you can do the minimum :
Take system_signed file and flash it with fastboot in AP :
fastboot.exe flash system system_signed
Click to expand...
Click to collapse
This didnt work, it told me something about, errors and so on...
'load_file: could not read 775675996 bytes from 'system_signed'
error: cannot load 'system_signed''
Thats the error i get
Edit: Flashing via RSD Lite, doesn't work because: "Unknown Fastboot command. (oem); phone connected"
Edit2: Got it, just had to delete the line with the oem oO
Edit3: "Failed to flash System: Phone returned False" thats strange oO
Edit4: Maybe it works when i wipe /system oO
Don't know, search for a fastboot for motorola ? seems some guys need this one...
My fastboot comes from android sdk http://dl.google.com/android/android-sdk_r22.0.5-windows.zip
Launch SDK manager and download Android SDK Plateform-tools
Orphee said:
Don't know, search for a fastboot for motorola ? seems some guys need this one...
Click to expand...
Click to collapse
Didn't work either, tried this one before...
well i guess its time to flash a custom rom then oO
thanks for your try dude, but reflash seems to be the better option for me now
---------- Post added at 04:05 PM ---------- Previous post was at 03:41 PM ----------
Orphee said:
Don't know, search for a fastboot for motorola ? seems some guys need this one...
My fastboot comes from android sdk http://dl.google.com/android/android-sdk_r22.0.5-windows.zip
Launch SDK manager and download Android SDK Plateform-tools
Click to expand...
Click to collapse
Thats the one i use too...
have heard, that there may be some kind of problem because of bootloader-stuf and so on oO
as i said, i try to just install a custom rom now, thought about it for a long time, so this is a good option...
Edit:
It needed RSD 6.x that worked really really good
Is this actually working on xt925 4.1,2, or is there any Xposed Framework apk that works with the motorola xt925?
Good day everyone! I would like to ask some help..
I'm actually noob in motorolla droid and this is my first motorolla phone ever. lol
Yesterday my brother gave me this XT912 since he got a new phone.
One of his colleagues rooted and changed the ROM to ECLIPSE 1.5.1 and it's running Android ICS 4.0.4 firmware.
When he gave the phone to me, I couldn't install some applications more specifically google hangouts coz it gives me an error:
E: signature verification failed
I downloaded the ff. firmwares from this site http://sbf.droid-developers.org/phone.php?device=9
Android 4.1.2 Blur_Version.98.72.165.XT912.Verizon.en.US
Android 4.1.2 Blur_Version.98.72.16.XT912.Verizon.en.US
Android 4.0.4 Blur_Version.6.16.211.XT912.Verizon.en.US
flashed them using the custom recovery option from the device (hold vol - & vol + keys while android logo appears) but eventually it gave me an error:
signature verification failed installation aborted
After series of google search I found this post by matt : http://www.droidrzr.com/index.php/t...xt912-jellybean-windows-mac-linux-all-in-one/
But it made my situation worst
Downloaded the latest version, DroidRAZRUtility1.82 Jellybean.
Installed the drivers for 32bit since I'm running W7 32bit OS.
Ran the WindowsUtility.bat and chose option 1 to completely wipe and install JB.
After running the utility I cannot boot up to recovery and normal boot-up anymore. In other words, it bricked my XT912.
It gave me this error:
When in AP Fastboot Mode:
AP Fastboot Flash Mode (S) (Flash Failure)
0A.74
eMMC Info: Size 16G
To return to normal mode - first press power key to power down
Device is LOCKED. Status Code:0
Battery OK
OK to Program
Connect USB
Data Cable
---------------------------
When in Normal Bootup and Recovery:
Invalid Flash Mode (S) (Boot Failure)
0A.74
eMMC Info: Size 16G
To return to normal mode - first press power key to power down
Device is LOCKED. Status Code:0
Invalid CG OTV (CG: system): Invalid SP Data
Invalid CD Version (CG: system)
Invalid CG OTV (CG: system)
As another try, I used Motorola RSD Lite 6.1.5 + MTK Patch and tried using the fastboot files (firmwares) that I downloaded earlier:
Android 4.1.2 Blur_Version.98.72.165.XT912.Verizon.en.US
Android 4.1.2 Blur_Version.98.72.16.XT912.Verizon.en.US
Android 4.0.4 Blur_Version.6.16.211.XT912.Verizon.en.US
But it gave me this error:
Failed flashing process. 6/16 flash motoboot "motoboot.img" -> Phone returned FAIL.
I really don't know how to fix this.. I really need your help guys...
Thanks,
Josh
Hi Josh,
Sorry to hear that....first of all, can you access fastboot mode? or you cant do absolutly anithing with the droid?
joshua3001 said:
Hi Josh,
Sorry to hear that....first of all, can you access fastboot mode? or you cant do absolutly anithing with the droid?
Click to expand...
Click to collapse
Hi joshua3001,
Yes, I could still boot in to fastboot mode.
joswa said:
When in Normal Bootup and Recovery:
Invalid Flash Mode (S) (Boot Failure)
0A.74
eMMC Info: Size 16G
To return to normal mode - first press power key to power down
Device is LOCKED. Status Code:0
Invalid CG OTV (CG: system): Invalid SP Data
Invalid CD Version (CG: system)
Invalid CG OTV (CG: system)
As another try, I used Motorola RSD Lite 6.1.5 + MTK Patch and tried using the fastboot files (firmwares) that I downloaded earlier:
Android 4.1.2 Blur_Version.98.72.165.XT912.Verizon.en.US
Android 4.1.2 Blur_Version.98.72.16.XT912.Verizon.en.US
Android 4.0.4 Blur_Version.6.16.211.XT912.Verizon.en.US
But it gave me this error:
Failed flashing process. 6/16 flash motoboot "motoboot.img" -> Phone returned FAIL.
I really don't know how to fix this.. I really need your help guys...
Thanks,
Josh
Click to expand...
Click to collapse
Are you trying to flash all three of these at the same time?
You won't be able to flash the 4.0.4 firmware, you are obviously already on the JB kernel(4.1.2), so you won't be able to go back to ICS(4.0.4)
That is what the screenshot you provided is telling you. The firmware it is failing on is the 4.0.4
You need to choose ONE of the 4.1.2 firmwares and flash it via RSD lite. Make sure you have plenty of battery when you do it.
Draxin is right dude, you cant flash all of them, i wll recomend you to flash JUST the .165 ...let me now (Y)
have the same problem
Draxin said:
Are you trying to flash all three of these at the same time?
You won't be able to flash the 4.0.4 firmware, you are obviously already on the JB kernel(4.1.2), so you won't be able to go back to ICS(4.0.4)
That is what the screenshot you provided is telling you. The firmware it is failing on is the 4.0.4
You need to choose ONE of the 4.1.2 firmwares and flash it via RSD lite. Make sure you have plenty of battery when you do it.
Click to expand...
Click to collapse
Hi Draxin,
I am having the same problem with my XT912 as well.
I have tried both the 4.1.2 options available at http://sbf.droid-developers.org/phone.php?device=9 and i am getting different errors with both of them.
For one i am getting flashcdt.bin 'cdt.bin_signed' > Phone returned Fail and for the other one i am getting Failed flashing process: 6/16 flash motoboot 'motoboot.img'' Phone returned Fail.
Can you please help?
I have been trying different things now and nothing is really working with my phone
need help please
joshua3001 said:
Draxin is right dude, you cant flash all of them, i wll recomend you to flash JUST the .165 ...let me now (Y)
Click to expand...
Click to collapse
Hi ,
I am having the same problem with my XT912 as well.
I have tried both the 4.1.2 options available at http://sbf.droid-developers.org/phone.php?device=9 and i am getting different errors with both of them.
For one i am getting flashcdt.bin 'cdt.bin_signed' > Phone returned Fail and for the other one i am getting Failed flashing process: 6/16 flash motoboot 'motoboot.img'' Phone returned Fail.
Can you please help?
I have been trying different things now and nothing is really working with my phone
nishanchi said:
Hi Draxin,
I am having the same problem with my XT912 as well.
I have tried both the 4.1.2 options available at http://sbf.droid-developers.org/phone.php?device=9 and i am getting different errors with both of them.
For one i am getting flashcdt.bin 'cdt.bin_signed' > Phone returned Fail and for the other one i am getting Failed flashing process: 6/16 flash motoboot 'motoboot.img'' Phone returned Fail.
Can you please help?
I have been trying different things now and nothing is really working with my phone
Click to expand...
Click to collapse
Hello,
Well regardless I would stick with the .165. Did you make sure debugging was enabled before trying to flash with RSD Lite? Did you make sure your phone was connected as a mass storage device?
Another option is Matt's Utility Make sure to follow his directions and thank him.
Same issue plz help me...
joswa said:
Good day everyone! I would like to ask some help..
I'm actually noob in motorolla droid and this is my first motorolla phone ever. lol
Yesterday my brother gave me this XT912 since he got a new phone.
One of his colleagues rooted and changed the ROM to ECLIPSE 1.5.1 and it's running Android ICS 4.0.4 firmware.
When he gave the phone to me, I couldn't install some applications more specifically google hangouts coz it gives me an error:
E: signature verification failed
I downloaded the ff. firmwares from this site http://sbf.droid-developers.org/phone.php?device=9
Android 4.1.2 Blur_Version.98.72.165.XT912.Verizon.en.US
Android 4.1.2 Blur_Version.98.72.16.XT912.Verizon.en.US
Android 4.0.4 Blur_Version.6.16.211.XT912.Verizon.en.US
flashed them using the custom recovery option from the device (hold vol - & vol + keys while android logo appears) but eventually it gave me an error:
signature verification failed installation aborted
After series of google search I found this post by matt : http://www.droidrzr.com/index.php/t...xt912-jellybean-windows-mac-linux-all-in-one/
But it made my situation worst
Downloaded the latest version, DroidRAZRUtility1.82 Jellybean.
Installed the drivers for 32bit since I'm running W7 32bit OS.
Ran the WindowsUtility.bat and chose option 1 to completely wipe and install JB.
After running the utility I cannot boot up to recovery and normal boot-up anymore. In other words, it bricked my XT912.
It gave me this error:
When in AP Fastboot Mode:
AP Fastboot Flash Mode (S) (Flash Failure)
0A.74
eMMC Info: Size 16G
To return to normal mode - first press power key to power down
Device is LOCKED. Status Code:0
Battery OK
OK to Program
Connect USB
Data Cable
---------------------------
When in Normal Bootup and Recovery:
Invalid Flash Mode (S) (Boot Failure)
0A.74
eMMC Info: Size 16G
To return to normal mode - first press power key to power down
Device is LOCKED. Status Code:0
Invalid CG OTV (CG: system): Invalid SP Data
Invalid CD Version (CG: system)
Invalid CG OTV (CG: system)
As another try, I used Motorola RSD Lite 6.1.5 + MTK Patch and tried using the fastboot files (firmwares) that I downloaded earlier:
Android 4.1.2 Blur_Version.98.72.165.XT912.Verizon.en.US
Android 4.1.2 Blur_Version.98.72.16.XT912.Verizon.en.US
Android 4.0.4 Blur_Version.6.16.211.XT912.Verizon.en.US
But it gave me this error:
Failed flashing process. 6/16 flash motoboot "motoboot.img" -> Phone returned FAIL.
I really don't know how to fix this.. I really need your help guys...
Thanks,
Josh
Click to expand...
Click to collapse
I have same issue in RSD and it always fails in motoboot.img
please give me solution
@xda -developers @Razr MAXX
NabeelSaleem said:
I have same issue in RSD and it always fails in motoboot.img
please give me solution
@xda -developers @Razr MAXX
Click to expand...
Click to collapse
Windows version?
Rsd lite version?
Firmware version?
Bootloader version?
Sent from my XT894 using Tapatalk
sd_shadow said:
Windows version?
Rsd lite version?
Firmware version?
Bootloader version?
Sent from my XT894 using Tapatalk
Click to expand...
Click to collapse
Thanks for reply
windows 8.1 pro
RSD 6.1.5
versions is tried:
VRZ_XT912_9.8.2O-72_VZW-16-5_1FF.xml
VRZ_XT912_6.7.2-180_DHD-16_M4-31_1FF.xml
and what is bootloader version? where can i find this?
NabeelSaleem said:
Thanks for reply
windows 8.1 pro
RSD 6.1.5
versions is tried:
VRZ_XT912_9.8.2O-72_VZW-16-5_1FF.xml
VRZ_XT912_6.7.2-180_DHD-16_M4-31_1FF.xml
and what is bootloader version? where can i find this?
Click to expand...
Click to collapse
AP Fastboot screen has bootloader version.
Windows 8 doesn't work well with rsd lite
Sent from my XT894 using Tapatalk
sd_shadow said:
AP Fastboot screen has bootloader version.
Windows 8 doesn't work well with rsd lite
Sent from my XT894 using Tapatalk
Click to expand...
Click to collapse
It's written
AP Fastboot Flash Mode (S)
0A.77
eMMC Info: size 16g
should i use windows 7?
and what about xml versions? are they ok
NabeelSaleem said:
It's written
AP Fastboot Flash Mode (S)
0A.77
eMMC Info: size 16g
should i use windows 7?
and what about xml versions? are they ok
Click to expand...
Click to collapse
Window 7 is a better option.
verifiy Moto driver are installed.
try RSDLite 6.2.4
0A.77 means only Jellybean firmware can be used.
This is latest
4.1.2 Verizon US 9.8.2O-72_VZW-16-5
614 MB (644,076,403 bytes)
Md5: 410F338706C1AD599E839DDE4FD60A23
cdma_spyder_9.8.2O-72_VZW-16-5_cfc.xml
Verify md5 checksum for firmware
also the DROID RAZR Utility XT912 Jellybean UPDATED is a good option
sd_shadow said:
Window 7 is a better option.
verifiy Moto driver are installed.
try RSDLite 6.2.4
0A.77 means only Jellybean firmware can be used.
This is latest
4.1.2 Verizon US 9.8.2O-72_VZW-16-5
614 MB (644,076,403 bytes)
Md5: 410F338706C1AD599E839DDE4FD60A23
cdma_spyder_9.8.2O-72_VZW-16-5_cfc.xml
Verify md5 checksum for firmware
also the DROID RAZR Utility XT912 Jellybean UPDATED is a good option
Click to expand...
Click to collapse
Can you give me link for this firmware or this one correct > http://motofirmware.center/files/file/44-vrz_xt912_982o-72_vzw-16-5_cfcxmlzip/
size is 614.2MB
and what is Md5 and cdma lines you wrote? how can i check them?
and really thanks for your help... please guide me these things too ...
NabeelSaleem said:
Can you give me link for this firmware or this one correct > http://motofirmware.center/files/file/44-vrz_xt912_982o-72_vzw-16-5_cfcxmlzip/
size is 614.2MB
and what is Md5 and cdma lines you wrote? how can i check them?
and really thanks for your help... please guide me these things too ...
Click to expand...
Click to collapse
See Moto Drivers, RSD Lite, and other Unbricking Tools
http://forum.xda-developers.com/general/rooting-roms/motorola-usb-drivers-rsd-lite-firmware-t3042687
Sent from my XT894 using Tapatalk
sd_shadow said:
See Moto Drivers, RSD Lite, and other Unbricking Tools
http://forum.xda-developers.com/general/rooting-roms/motorola-usb-drivers-rsd-lite-firmware-t3042687
Sent from my XT894 using Tapatalk
Click to expand...
Click to collapse
I know this and i downloaded RSD lite 6.2.4
Installed moto drivers
also checked razr utility tool
I downloaded firmware as you said but in my laptop its also failed to flash with this firmware > http://motofirmware.center/files/file/44-vrz_xt912_982o-72_vzw-16-5_cfcxmlzip/
and here is XML code
Code:
<?xml version="1.0"?>
<flashing>
<header>
<phone_model model="SPYDER_CFC" />
<software_version version="9.8.2O-72_VZW-16-5" />
<interfaces>
<interface name="AP" />
</interfaces>
</header>
<steps interface="AP">
<step operation="flash" partition="cdt.bin" filename="cdt.bin_signed" MD5="D9F76350C7A9694FEA32D84AF1C4AA39" />
<step operation="reboot-bootloader" />
<step operation="flash" partition="emstorage" filename="emstorage.img" MD5="081640654B9F45CD31C3903180A72BD1" />
<step operation="reboot-bootloader" />
<step operation="flash" partition="mbm" filename="allow-mbmloader-flashing-mbm.bin" MD5="55D703D1D8D8631F31BE89A6069AD68E" />
<step operation="reboot-bootloader" />
<step operation="flash" partition="mbmloader" filename="mbmloader.bin" MD5="42F7110DE49D6D28EA0540F1C02F9F1B" />
<step operation="flash" partition="mbm" filename="mbm.bin" MD5="F541F64F56739D65C19557E33F8AEF3C" />
<step operation="oem" var="fb_mode_set" />
<step operation="reboot-bootloader" />
<step operation="flash" partition="motoboot" filename="motoboot.img" MD5="D25F83E68E3BD76AE7F9405581E49B41" />
<step operation="reboot-bootloader" />
<step operation="erase" partition="cache" />
<step operation="erase" partition="userdata" />
<step operation="erase" partition="userdata" />
<step operation="flash" partition="logo.bin" filename="logo.bin" MD5="CD111CC7B675E62A7D85A50632FB88E8" />
<step operation="flash" partition="devtree" filename="device_tree.bin" MD5="04E2F24447783A0FF32E86E0DCA1D0C0" />
<step operation="flash" partition="system" filename="system.img" MD5="923FC8E9A3848744EACC8E98BE43DABE" />
<step operation="flash" partition="boot" filename="boot.img" MD5="D89B288A78E43CDAAFA55B6545A2FAEA" />
<step operation="flash" partition="recovery" filename="recovery.img" MD5="E8CA4889CF1DC7236526F628D2FCF948" />
<step operation="flash" partition="cdrom" filename="cdrom" MD5="FD1D40C2B40F0222EB8EF98AEB3AA87C" />
<step operation="flash" partition="preinstall" filename="preinstall.img" MD5="619C6B45BBB62D13FD272A22DD19D63C" />
<step operation="flash" partition="radio" filename="radio.img" MD5="596BA902DB1F52CD97DC0466B2C88E24" />
<step operation="oem" var="fb_mode_clear" />
</steps>
</flashing>
flash fails on cdt.bin ... please tell me what to do @sd_shadow
NabeelSaleem said:
I know this and i downloaded RSD lite 6.2.4
Installed moto drivers
also checked razr utility tool
I downloaded firmware as you said but in my laptop its also failed to flash with this firmware > http://motofirmware.center/files/file/44-vrz_xt912_982o-72_vzw-16-5_cfcxmlzip/
and here is XML code
Code:
<?xml version="1.0"?>
<flashing>
<header>
<phone_model model="SPYDER_CFC" />
<software_version version="9.8.2O-72_VZW-16-5" />
<interfaces>
<interface name="AP" />
</interfaces>
</header>
<steps interface="AP">
<step operation="flash" partition="cdt.bin" filename="cdt.bin_signed" MD5="D9F76350C7A9694FEA32D84AF1C4AA39" />
<step operation="reboot-bootloader" />
<step operation="flash" partition="emstorage" filename="emstorage.img" MD5="081640654B9F45CD31C3903180A72BD1" />
<step operation="reboot-bootloader" />
<step operation="flash" partition="mbm" filename="allow-mbmloader-flashing-mbm.bin" MD5="55D703D1D8D8631F31BE89A6069AD68E" />
<step operation="reboot-bootloader" />
<step operation="flash" partition="mbmloader" filename="mbmloader.bin" MD5="42F7110DE49D6D28EA0540F1C02F9F1B" />
<step operation="flash" partition="mbm" filename="mbm.bin" MD5="F541F64F56739D65C19557E33F8AEF3C" />
<step operation="oem" var="fb_mode_set" />
<step operation="reboot-bootloader" />
<step operation="flash" partition="motoboot" filename="motoboot.img" MD5="D25F83E68E3BD76AE7F9405581E49B41" />
<step operation="reboot-bootloader" />
<step operation="erase" partition="cache" />
<step operation="erase" partition="userdata" />
<step operation="erase" partition="userdata" />
<step operation="flash" partition="logo.bin" filename="logo.bin" MD5="CD111CC7B675E62A7D85A50632FB88E8" />
<step operation="flash" partition="devtree" filename="device_tree.bin" MD5="04E2F24447783A0FF32E86E0DCA1D0C0" />
<step operation="flash" partition="system" filename="system.img" MD5="923FC8E9A3848744EACC8E98BE43DABE" />
<step operation="flash" partition="boot" filename="boot.img" MD5="D89B288A78E43CDAAFA55B6545A2FAEA" />
<step operation="flash" partition="recovery" filename="recovery.img" MD5="E8CA4889CF1DC7236526F628D2FCF948" />
<step operation="flash" partition="cdrom" filename="cdrom" MD5="FD1D40C2B40F0222EB8EF98AEB3AA87C" />
<step operation="flash" partition="preinstall" filename="preinstall.img" MD5="619C6B45BBB62D13FD272A22DD19D63C" />
<step operation="flash" partition="radio" filename="radio.img" MD5="596BA902DB1F52CD97DC0466B2C88E24" />
<step operation="oem" var="fb_mode_clear" />
</steps>
</flashing>
flash fails on cdt.bin ... please tell me what to do @sd_shadow
Click to expand...
Click to collapse
Does your device have Verizon on front and back?
Sent from my XT894 using Tapatalk
---------- Post added at 07:36 AM ---------- Previous post was at 07:33 AM ----------
How to use md5
http://forum.xda-developers.com/showthread.php?t=
Sent from my XT894 using Tapatalk
sd_shadow said:
Does your device have Verizon on front and back?
Sent from my XT894 using Tapatalk
---------- Post added at 07:36 AM ---------- Previous post was at 07:33 AM ----------
How to use md5
http://forum.xda-developers.com/showthread.php?t=
Sent from my XT894 using Tapatalk
Click to expand...
Click to collapse
Yes written on both side.
4g LTE verizon
NabeelSaleem said:
Yes written on both side.
4g LTE verizon
Click to expand...
Click to collapse
What is complete text on AP Fastboot Flash Mode screen?
hi everyone,
first of all i tried search same problem but there is different i can enter to AP fastboot and can goes in to recovery press power +up+down
( i have installed on my xt910 cm 11 (4.4.4) using safestrap 3.65 after the offical 5.0.2 rom cm12 come out (http://forum.xda-developers.com/droid-razr/development/rom-cyanogenmod-12-0-t2950906)
i update safestrap to 3.75 then uninstall recovery then reinstall it reboot
delete rom slot and re install now one and then install 5.0.2 rom +gapp reboot (take about 10 min ) and then setup steps goes fine but the Device became annoyingly slow so I tried
to delete rom slot again but this time i select rom slot 2 and wipe then install 5.0.2 rom +gapp then reboot )
motorola logo Appears then no thing black screen actually black light screen (there is no safestrap logo Appear)
i tried ap fastboot and thats what i got
battery low
cannot program
connect usb
data cable
cant charge battry any more dont know why
i can go to recovry by press power +up+down
but every time i tried to install (( cm11 4.4.4)) i got install field
thanks and sorry for bad english XD
Abdoobood said:
hi everyone,
first of all i tried search same problem but there is different i can enter to AP fastboot and can goes in to recovery press power +up+down
( i have installed on my xt910 cm 11 (4.4.4) using safestrap 3.65 after the offical 5.0.2 rom cm12 come out (http://forum.xda-developers.com/droid-razr/development/rom-cyanogenmod-12-0-t2950906)
i update safestrap to 3.75 then uninstall recovery then reinstall it reboot
delete rom slot and re install now one and then install 5.0.2 rom +gapp reboot (take about 10 min ) and then setup steps goes fine but the Device became annoyingly slow so I tried
to delete rom slot again but this time i select rom slot 2 and wipe then install 5.0.2 rom +gapp then reboot )
motorola logo Appears then no thing black screen actually black light screen (there is no safestrap logo Appear)
i tried ap fastboot and thats what i got
battery low
cannot program
connect usb
data cable
cant charge battry any more dont know why
i can go to recovry by press power +up+down
but every time i tried to install (( cm11 4.4.4)) i got install field
thanks and sorry for bad english XD
Click to expand...
Click to collapse
Try
Power off, Hold volume buttons (or M key/droid 4), Power on, release buttons at
Boot Mode Selection Menu> Scroll down with volume down button, to BP Tools, Select with Volume UP button, should boot directly to SafeStrap (if it's still there).
Or Try
Booting from AP fastboot to charging mode
If the Device will only boot to AP Fastboot and it says Battery Low
Connect the phone/Device ato a Wall Charger (not PC)
-In AP Fastboot Mode hold Volume down& power buttons at the same time for +10 seconds
- When screen goes black...release power button
-Then IMMEDIATELY press and hold Vol - and Vol+ to boot to Boot Menu.
- In Boot Menu scroll down with volume down to BP Tools, press volume up to select
- Device should boot to Charging Mode with battery icon
- Once battery is charged, try flashing in AP Fastboot again
This will only work if battery charging Firmware is still preset and not corrupted
If Motorola Device will not boot to Charging Mode, a Fastboot cable will be needed.
http://goo.gl/QllP1j
{
"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"
}
Sent from my XT907 using Tapatalk
sd_shadow said:
Try
Power off, Hold volume buttons (or M key/droid 4), Power on, release buttons at
Boot Mode Selection Menu> Scroll down with volume down button, to BP Tools, Select with Volume UP button, should boot directly to SafeStrap (if it's still there).
Or Try
Booting from AP fastboot to charging mode
If the Device will only boot to AP Fastboot and it says Battery Low
Connect the phone/Device ato a Wall Charger (not PC)
-In AP Fastboot Mode hold Volume down& power buttons at the same time for +10 seconds
- When screen goes black...release power button
-Then IMMEDIATELY press and hold Vol - and Vol+ to boot to Boot Menu.
- In Boot Menu scroll down with volume down to BP Tools, press volume up to select
- Device should boot to Charging Mode with battery icon
- Once battery is charged, try flashing in AP Fastboot again
This will only work if battery charging Firmware is still preset and not corrupted
If Motorola Device will not boot to Charging Mode, a Fastboot cable will be needed.
Sent from my XT907 using Tapatalk
Click to expand...
Click to collapse
I done this before but battry still low so how can i make cable i cant buy cable cus i live in egypt and there is no motorola suports there
Can u plz Explain to me how to make 1 in easy Easy Language
Thanks alot for ur time
edit: http://goo.gl/1glUry
sd_shadow said:
edit:
Click to expand...
Click to collapse
ok dude i got batrry ok
ok to program
conect usb
date cable
rsd lite 6.1.6 cant fine my xt910
is there any driver should i install or something
i got the sound on my pc (usb connected sound)
but rsd cant find my phone
thank you $_$
Abdoobood said:
ok dude i got batrry ok
ok to program
conect usb
date cable
rsd lite 6.1.6 cant fine my xt910
is there any driver should i install or something
i got the sound on my pc (usb connected sound)
but rsd cant find my phone
thank you $_$
Click to expand...
Click to collapse
Download and Install Drivers (Motorola_End_User_Driver_Installation...)
Motorola Drivers for Windows http://goo.gl/mIsi4h
It’s a good idea to reboot pc after installing drivers
Sent from my XT907 using Tapatalk
sd_shadow said:
Download and Install Drivers (Motorola_End_User_Driver_Installation...)
Motorola Drivers for Windows
It’s a good idea to reboot pc after installing drivers
Sent from my XT907 using Tapatalk
Click to expand...
Click to collapse
XD ok the pc fine my xt910 when i press start
rsdlite is stoping at step 1 and i got
failed flashing process. 1/19 flash mbm "allow-mbmloader-flashing-mbm.bin" -> usb error occurred while reading/writing
my fastboot 0a.74
i use 9.8.2O-124_SPUEM-14_S7_USASPDRICS01RUKE1007.0R_USASPDRJBRTGB_P011_b57374ab5a_p2b_S1FF_fb_CFC.xml
win8-64bit
last version :5.0.1 cm12
but i think there is no more system in phone cuz i got black screen after motorola logo
I'm sorry for being annoying and thank you very much
Abdoobood said:
XD ok the pc fine my xt910 when i press start
rsdlite is stoping at step 1 and i got
failed flashing process. 1/19 flash mbm "allow-mbmloader-flashing-mbm.bin" -> usb error occurred while reading/writing
my fastboot 0a.74
i use 9.8.2O-124_SPUEM-14_S7_USASPDRICS01RUKE1007.0R_USASPDRJBRTGB_P011_b57374ab5a_p2b_S1FF_fb_CFC.xml
win8-64bit
last version :5.0.1 cm12
but i think there is no more system in phone cuz i got black screen after motorola logo
I'm sorry for being annoying and thank you very much
Click to expand...
Click to collapse
bootloader 0A.74 should just be ICS, so you should be able to use a ICS or Jellybean stock XML file
fail at flashing-mbm.bin" is likely that stock XML file is for a different carrier/region that what is currently on device
what carrier do you use, what country?
sd_shadow said:
bootloader 0A.74 should just be ICS, so you should be able to use a ICS or Jellybean stock XML file
fail at flashing-mbm.bin" is likely that stock XML file is for a different carrier/region that what is currently on device
what carrier do you use, what country?
Click to expand...
Click to collapse
I had purchased it from Saudi Arabia in the Middle East
Is there any way to know or get that from DEVICE (i mean to know what country come from)
Abdoobood said:
I had purchased it from Saudi Arabia in the Middle East
Click to expand...
Click to collapse
OK, you need to edit the .XML file
unzip/extract files
in folder will be another .XML file something like 9.8.2O-72_VZW-16-5_cfc.xml
open with notepad++
remove lines that are like
<step operation="flash" partition="cdt.bin" filename="cdt.bin_signed" MD5="D9F76350C7A9694FEA32D84AF1C4AA39" />
and
<step operation="flash" partition="radio" filename="radio.img" MD5="596BA902DB1F52CD97DC0466B2C88E24" />
do not leave empty line
save the changes in notepad++ and close notepad++
in RSD Lite make sure you select the unzipped .XML
Windows 8? A lot of people has problems with Windows 8,find somewhere Windows 7.
Sent from my Razr XT910
sd_shadow said:
OK, you need to edit the .XML file
unzip/extract files
in folder will be another .XML file something like 9.8.2O-72_VZW-16-5_cfc.xml
open with notepad++
remove lines that are like
<step operation="flash" partition="cdt.bin" filename="cdt.bin_signed" MD5="D9F76350C7A9694FEA32D84AF1C4AA39" />
and
<step operation="flash" partition="radio" filename="radio.img" MD5="596BA902DB1F52CD97DC0466B2C88E24" />
do not leave empty line
save the changes in notepad++ and close notepad++
in RSD Lite make sure you select the unzipped .XML
Click to expand...
Click to collapse
sorry but there is a same step name this is what xml countan
Code:
<?xml version="1.0" encoding="UTF-8"?>
<flashing>
<header>
<phone_model model="SPYDER_U" />
<software_version version="umts_spyder_mmi_emea-user 4.1.2 9.8.2O-124_SPUEM-14 1362039991 release-keysSPYDERBP_U_04.10.00R" />
<interfaces>
<interface name="AP" />
</interfaces>
</header>
<steps interface="AP">
<step operation="flash" partition="mbm" filename="allow-mbmloader-flashing-mbm.bin" MD5="55d703d1d8d8631f31be89a6069ad68e" />
<step operation="reboot-bootloader" />
<step operation="flash" partition="mbmloader" filename="mbmloader.bin" MD5="42f7110de49d6d28ea0540f1c02f9f1b" />
<step operation="flash" partition="mbm" filename="mbm.bin" MD5="f541f64f56739d65c19557e33f8aef3c" />
<step operation="reboot-bootloader" />
<step operation="flash" partition="cdt.bin" filename="cdt.bin_signed" MD5="7efbcdf1bb0128b241865dab3bb50f58" />
<step operation="erase" partition="cache" />
<step operation="erase" partition="userdata" />
<step operation="erase" partition="emstorage" />
<step operation="flash" partition="logo.bin" filename="logo.bin" MD5="cd111cc7b675e62a7d85a50632fb88e8" />
<step operation="flash" partition="ebr" filename="ebr_signed" MD5="dfa61c2c9858a22b5fb9e53b912a44e1" />
<step operation="flash" partition="mbr" filename="mbr_signed" MD5="2600bab8703dc908168471590bb76ae8" />
<step operation="flash" partition="devtree" filename="devtree_signed" MD5="baffc70d6bfb1f60718a41ad56f1bfa2" />
<step operation="flash" partition="system" filename="system_signed" MD5="e7b648a75e897c359b26585b898ee105" />
<step operation="flash" partition="boot" filename="boot_signed" MD5="dfbf43445f5128bf692a8a97cdfa2dc5" />
<step operation="flash" partition="recovery" filename="recovery_signed" MD5="9508ac0f92d22fdeaa325f0ac5b59f7e" />
<step operation="flash" partition="cdrom" filename="cdrom_signed" MD5="f23887e8b903cce684544a981f56b0aa" />
<step operation="flash" partition="emstorage" filename="emstorage.img" MD5="f248ff87bfab03e3278891ad151adde7" />
<step operation="flash" partition="radio" filename="radio.img" MD5="611e25a2d2e132e78acdcc849754e15d" />
</steps>
</flashing>
plz edit it and re post XD
welder73 said:
Windows 8? A lot of people has problems with Windows 8,find somewhere Windows 7.
Sent from my Razr XT910
Click to expand...
Click to collapse
sd_shadow said:
OK, you need to edit the .XML file
unzip/extract files
in folder will be another .XML file something like 9.8.2O-72_VZW-16-5_cfc.xml
open with notepad++
remove lines that are like
<step operation="flash" partition="cdt.bin" filename="cdt.bin_signed" MD5="D9F76350C7A9694FEA32D84AF1C4AA39" />
and
<step operation="flash" partition="radio" filename="radio.img" MD5="596BA902DB1F52CD97DC0466B2C88E24" />
do not leave empty line
save the changes in notepad++ and close notepad++
in RSD Lite make sure you select the unzipped .XML
Click to expand...
Click to collapse
lol u are right it was win problem it work on my sis laptop win 7 XD finaly i got my phone back god bless u guys thx so much sd_shadow
and welder
last qustion did i have re root phone to install rom ?
Abdoobood said:
lol u are right it was win problem it work on my sis laptop win 7 XD finaly i got my phone back god bless u guys thx so much sd_shadow
and welder
last qustion did i have re root phone to install rom ?
Click to expand...
Click to collapse
yes need to re-root
Hi,
My phone is currently unstable. It is rebooting pretty often with no obvious trigger. Also having reboots which return to the initial Google-setup. My settings.apk disappear yesterday, so I did another clean install. I'm on PAC-Rom at the moment, but was running Markox89's CM11 builds beforehand, and having issues there.
When wiping recently I've been doing a full system/data/cache wipe, as well as wiping cache/dalvik after installation. However I have not been formatting /sdcard/. Could this solve the issue?
Phone: i9300
ROM: PAC-i9300 Latest KK Nightly (20150128)
Kernel: Boeffla Kernel 2.7 NG CM11 Final
Modem: I9300XXUGND1
Bootl: I9300XXUGOA2
The following is a logcat which I started ~15 mins before a reboot occured.
Logcat (adb logcat *:E -v long > errors.log): http://pastebin.com/raw.php?i=1akST61A
PS: I have an exam tomorrow afternoon so I may not get around to too much testing in the next 24 hours.
Any help would be greatly received!
Thanks,
David
Try the freezing thread in general forum, test the memory for bad blocks.
Thanks for the reply,
I was following that process before a few months ago, and it might have improved the phone slightly so I'll keep on it for a bit.
My phone was most stable around a month ago where I had zero reboots in a week or two, but they started to appear again after a while.
It seems to be an error on a2dp, audio. Looks like driver loading failed but I'm no expert.
Sent from a stolen phone!
I've been playing around with a few more roms, both KK and LP but my phone is still getting reboots.
I'm now on PAC rom, the most recent KK nightly (from January '15)
I've started recording catlogs so I can now upload them here for every reboot in case there is something that can be helped.
Log from this morning, with filter set to errors: http://pastebin.com/raw.php?i=PpWqx6Xy
Thanks!
Flash back to stock and start again. If you need help let me know
When I flashed PAC ROM recently I did a full wipe including system and data and internal SD.
Wouldn't going back to stock have no effect?
Unless my modem and/or boot-loader may be causing issues?
Cheers
By going back to stock it resets all of your parameters and kernel, and boot files. This will resolve your issues if there is something wrong with the Bootloader also. I can help you if you need it
Also, I just noticed your running a lollipop Bootloader, with KitKat kernel and system. This could be an issue as well
KaosMaster said:
Also, I just noticed your running a lollipop Bootloader, with KitKat kernel and system. This could be an issue as well
Click to expand...
Click to collapse
Okay sounds like a good idea. I'm confident with adb and odin etc so shouldn't need any particular help.
I'm assuming this guide conforms to the standard approach: http://forum.xda-developers.com/galaxy-s3/general/fix-s3-to-factory-unroot-stock-recovery-t2323847
Cheers
Here are the complete ODIN Service files to restore your International GT-I9300 16GB device to I9300XXUGNJ2_I9300OXXGNJ1-OXX (Open) STOCK:<br />
<br />
CSC-OXX-I9300XXUGNJ2_I9300OXXGNJ1_2793257_REV00_user_low_ship.tar.md5<br />
<br />
https://drive.google.com/file/d/0B4RU_ZH5QUASenlHVlctVEZfUFE/view?usp=sharing<br />
<br />
This is ODIN v.3.10:<br />
https://drive.google.com/file/d/0B4RU_ZH5QUASSWhaMmdiaFJ1Tm8/view?usp=sharing<br />
<br />
This package is straight from Samsung and includes the PIT for partitioning!! <br />
<br />
These files are intended to be used with ODIN ONLY!! If at any time ODIN FAILS, pull battery, re-insert battery, go back to ODIN and try again.<br />
<br />
Download the two items, charge device to 100% battery, Download and install Device drivers from samsung if needed.<br />
<br />
www.samsung.com/support<br />
<br />
Unzip the CSC-i9300****.zip file.<br />
<br />
Unzip and Open "ODIN v.3.10.exe" as an "Administrator" on a Windows PC.<br />
<br />
Click on each of the 4 buttons below and browse to find matching file in extracted image folder:<br />
<br />
BL = BL-****.tar.md5<br />
AP = AP-****.tar.md5<br />
CP = MODEM-****.tar.md5<br />
CSC = CSC-****.tar.md5<br />
<br />
Check the following boxes:<br />
<br />
Auto-Reboot<br />
Re-Partition<br />
F. Reset Time<br />
NAND Erase All<br />
<br />
Put 100% charged device into ODIN Mode, and connect to PC USB with Original Cable.<br />
<br />
Check there two boxes in ODIN:<br />
<br />
Phone Bootloader Update<br />
Clear EFS Partition<br />
<br />
Hit the "Start" button<br />
<br />
Once the Device reboots, perform Two [2] FDR (Factory Data Reset).<br />
<br />
Phone is back to complete stock...
Well, device bootloader is unlocked and after trying install magisk, the phone can't boot, i just flash a stock rom running these commands:
Code:
<step operation="getvar" var="max-sparse-size"/>
<step operation="oem" var="fb_mode_set"/>
<step MD5="dbf272771d89f41981d153dafe2991ac" filename="PGPT" operation="flash" partition="gpt"/>
<step MD5="c98f7a52308d75d0378e7fff690b74a8" filename="preloader.bin" operation="flash" partition="preloader"/>
<step MD5="54264b95885650ef4d641a0012840f84" filename="lk.img" operation="flash" partition="lk_a"/>
<step MD5="5178cb15479e9c05df419cd3f4861186" filename="tee.img" operation="flash" partition="tee_a"/>
<step MD5="9a68979789b47296a767e023d8a88fee" filename="md1img.img" operation="flash" partition="md1img_a"/>
<step operation="erase" partition="nvdata"/>
<step MD5="2db2aac5ca670899cccf7bdec37ba4d0" filename="spmfw.img" operation="flash" partition="spmfw_a"/>
<step MD5="b46e7f1b9ca40d33dfe0a2b987d6df33" filename="scp.img" operation="flash" partition="scp_a"/>
<step MD5="a13640f4a7872c5196c9e5a79c32590b" filename="sspm.img" operation="flash" partition="sspm_a"/>
<step MD5="a627e53271c640d4ce1735ccc6775ebe" filename="cam_vpu1.img" operation="flash" partition="cam_vpu1_a"/>
<step MD5="7c4e3ece0d002120d56251220c835cb6" filename="cam_vpu2.img" operation="flash" partition="cam_vpu2_a"/>
<step MD5="623a68f928862c76cb965f4bd1e5427c" filename="cam_vpu3.img" operation="flash" partition="cam_vpu3_a"/>
<step MD5="43e0c261acce37a784b60e7b7cdc9254" filename="vbmeta.img" operation="flash" partition="vbmeta_a"/>
<step MD5="76dd1e64bf71aa9a3e2e3f5303a1f35b" filename="oem.img" operation="flash" partition="oem_a"/>
<step MD5="806b8d64e8b11bd4c9c0dacedfbc7ff9" filename="logo.bin" operation="flash" partition="logo_a"/>
<step MD5="ba915886970313fe3f5b2f8616a9bb6d" filename="boot.img" operation="flash" partition="boot_a"/>
<step MD5="19cee299062c4d9fc6a1dcbe2bb19d37" filename="dtb.img" operation="flash" partition="dtb_a"/>
<step MD5="0e30583060052df04b9f77bbf4959443" filename="dtbo.img" operation="flash" partition="dtbo_a"/>
<step MD5="a8b3093300b6d7c39e6c7b77a84dccb5" filename="system.img_sparsechunk.0" operation="flash" partition="system_a"/>
<step MD5="65afd7ea3e95c0a084d540da85adbd40" filename="system.img_sparsechunk.1" operation="flash" partition="system_a"/>
<step MD5="52f33dd534af15fac3b9dc76eb89e669" filename="system.img_sparsechunk.2" operation="flash" partition="system_a"/>
<step MD5="d8c3e01e9588b15675171c6f0d128c7e" filename="system.img_sparsechunk.3" operation="flash" partition="system_a"/>
<step MD5="f5f95285c0ea411bdded6609d6804e91" filename="system.img_sparsechunk.4" operation="flash" partition="system_a"/>
<step MD5="fab703c97214f212c4f368ea8868df07" filename="system.img_sparsechunk.5" operation="flash" partition="system_a"/>
<step MD5="20aee3663d8aba2e0870fa1b86e63f52" filename="system.img_sparsechunk.6" operation="flash" partition="system_a"/>
<step MD5="5fd014761125a7783a3b1a97376cfec8" filename="system.img_sparsechunk.7" operation="flash" partition="system_a"/>
<step MD5="78a9e3caea85137ae6f8c000d2aa1f03" filename="system.img_sparsechunk.8" operation="flash" partition="system_a"/>
<step MD5="f731c4bdb1ee305d6646e500a5d4ca55" filename="system.img_sparsechunk.9" operation="flash" partition="system_a"/>
<step MD5="e9a86e148fe2f4461478a47ed7c2bacb" filename="system_other.img_sparsechunk.0" operation="flash" partition="system_b"/>
<step MD5="f86f415a22c7ea33944890dc00e47829" filename="system_other.img_sparsechunk.1" operation="flash" partition="system_b"/>
<step MD5="713bf69057b43ab04158c4d5dadccee8" filename="vendor.img_sparsechunk.0" operation="flash" partition="vendor_a"/>
<step MD5="8c0f78ebf3681a35a5167c16c3f28464" filename="vendor.img_sparsechunk.1" operation="flash" partition="vendor_a"/>
<step operation="erase" partition="userdata"/>
<step operation="erase" partition="metadata"/>
<step operation="oem" var="fb_mode_clear"/>
But the phone still in boot loop, im losing the hope guys, please need help :\
Something that i know so far:
if i run fastboot erase cache:
erasing 'cache'...
(bootloader) erase permission denied
FAILED (remote failure)
helloitu said:
Well, device bootloader is unlocked and after trying install magisk, the phone can't boot, i just flash a stock rom running these commands:
Code:
<step operation="getvar" var="max-sparse-size"/>
<step operation="oem" var="fb_mode_set"/>
<step MD5="dbf272771d89f41981d153dafe2991ac" filename="PGPT" operation="flash" partition="gpt"/>
<step MD5="c98f7a52308d75d0378e7fff690b74a8" filename="preloader.bin" operation="flash" partition="preloader"/>
<step MD5="54264b95885650ef4d641a0012840f84" filename="lk.img" operation="flash" partition="lk_a"/>
<step MD5="5178cb15479e9c05df419cd3f4861186" filename="tee.img" operation="flash" partition="tee_a"/>
<step MD5="9a68979789b47296a767e023d8a88fee" filename="md1img.img" operation="flash" partition="md1img_a"/>
<step operation="erase" partition="nvdata"/>
<step MD5="2db2aac5ca670899cccf7bdec37ba4d0" filename="spmfw.img" operation="flash" partition="spmfw_a"/>
<step MD5="b46e7f1b9ca40d33dfe0a2b987d6df33" filename="scp.img" operation="flash" partition="scp_a"/>
<step MD5="a13640f4a7872c5196c9e5a79c32590b" filename="sspm.img" operation="flash" partition="sspm_a"/>
<step MD5="a627e53271c640d4ce1735ccc6775ebe" filename="cam_vpu1.img" operation="flash" partition="cam_vpu1_a"/>
<step MD5="7c4e3ece0d002120d56251220c835cb6" filename="cam_vpu2.img" operation="flash" partition="cam_vpu2_a"/>
<step MD5="623a68f928862c76cb965f4bd1e5427c" filename="cam_vpu3.img" operation="flash" partition="cam_vpu3_a"/>
<step MD5="43e0c261acce37a784b60e7b7cdc9254" filename="vbmeta.img" operation="flash" partition="vbmeta_a"/>
<step MD5="76dd1e64bf71aa9a3e2e3f5303a1f35b" filename="oem.img" operation="flash" partition="oem_a"/>
<step MD5="806b8d64e8b11bd4c9c0dacedfbc7ff9" filename="logo.bin" operation="flash" partition="logo_a"/>
<step MD5="ba915886970313fe3f5b2f8616a9bb6d" filename="boot.img" operation="flash" partition="boot_a"/>
<step MD5="19cee299062c4d9fc6a1dcbe2bb19d37" filename="dtb.img" operation="flash" partition="dtb_a"/>
<step MD5="0e30583060052df04b9f77bbf4959443" filename="dtbo.img" operation="flash" partition="dtbo_a"/>
<step MD5="a8b3093300b6d7c39e6c7b77a84dccb5" filename="system.img_sparsechunk.0" operation="flash" partition="system_a"/>
<step MD5="65afd7ea3e95c0a084d540da85adbd40" filename="system.img_sparsechunk.1" operation="flash" partition="system_a"/>
<step MD5="52f33dd534af15fac3b9dc76eb89e669" filename="system.img_sparsechunk.2" operation="flash" partition="system_a"/>
<step MD5="d8c3e01e9588b15675171c6f0d128c7e" filename="system.img_sparsechunk.3" operation="flash" partition="system_a"/>
<step MD5="f5f95285c0ea411bdded6609d6804e91" filename="system.img_sparsechunk.4" operation="flash" partition="system_a"/>
<step MD5="fab703c97214f212c4f368ea8868df07" filename="system.img_sparsechunk.5" operation="flash" partition="system_a"/>
<step MD5="20aee3663d8aba2e0870fa1b86e63f52" filename="system.img_sparsechunk.6" operation="flash" partition="system_a"/>
<step MD5="5fd014761125a7783a3b1a97376cfec8" filename="system.img_sparsechunk.7" operation="flash" partition="system_a"/>
<step MD5="78a9e3caea85137ae6f8c000d2aa1f03" filename="system.img_sparsechunk.8" operation="flash" partition="system_a"/>
<step MD5="f731c4bdb1ee305d6646e500a5d4ca55" filename="system.img_sparsechunk.9" operation="flash" partition="system_a"/>
<step MD5="e9a86e148fe2f4461478a47ed7c2bacb" filename="system_other.img_sparsechunk.0" operation="flash" partition="system_b"/>
<step MD5="f86f415a22c7ea33944890dc00e47829" filename="system_other.img_sparsechunk.1" operation="flash" partition="system_b"/>
<step MD5="713bf69057b43ab04158c4d5dadccee8" filename="vendor.img_sparsechunk.0" operation="flash" partition="vendor_a"/>
<step MD5="8c0f78ebf3681a35a5167c16c3f28464" filename="vendor.img_sparsechunk.1" operation="flash" partition="vendor_a"/>
<step operation="erase" partition="userdata"/>
<step operation="erase" partition="metadata"/>
<step operation="oem" var="fb_mode_clear"/>
But the phone still in boot loop, im losing the hope guys, please need help :\
Something that i know so far:
if i run fastboot erase cache:
erasing 'cache'...
(bootloader) erase permission denied
FAILED (remote failure)
Click to expand...
Click to collapse
I have almost the same issue, but you can try this:
Boot into fastboot and from cmd type the command:
fastboot getvar all .Then scroll down and look for the line : ro.carrier . If you don`t see ro.carrier = unknown, then just download Motorola Rescue and smart assistant ,boot into fastboot , connect your device to PC and in the program choose rescue and follow the instructions.My issue is that i cannot rescue my phone because of that ro.carrier: unknown ... And if somebody knows how to change ro.carrier to RETEU ,please help to save my device!
nikoman1987 said:
I have almost the same issue, but you can try this:
Boot into fastboot and from cmd type the command:
fastboot getvar all .Then scroll down and look for the line : ro.carrier . If you don`t see ro.carrier = unknown, then just download Motorola Rescue and smart assistant ,boot into fastboot , connect your device to PC and in the program choose rescue and follow the instructions.My issue is that i cannot rescue my phone because of that ro.carrier: unknown ... And if somebody knows how to change ro.carrier to RETEU ,please help to save my device!
Click to expand...
Click to collapse
Hello, so atm anything workks, even LMSA, its says that my device isn't supported, and i have the ro.carrier
helloitu said:
Hello, so atm anything workks, even LMSA, its says that my device isn't supported, and i have the ro.carrier
Click to expand...
Click to collapse
If there was a custom recovery for this device, we could fix the issue ,but unfortunately there is no TWRP or any other custom recovery for this device ,so i have tested everything ,that i could find the issue is that some critical partitions are locked ,i was using several GSI`s but the cameras were not working properly ,so i have decided to switch back to stock .After using the same command, i ended in a constant bootloop. So i have tested everything that i could find in the web without luck.And i have lost adb authorization ,so i`m stuck in a deep hole right now. Motorola Device manager was the first thing ,that i have tried ,but for several days i get the message that the server is down during maintanence. Hopefuly it will be up soon. That`s my second and last MTK device, i have made the mistake not to backup the whole device before starting to mess with the the phone. If i figure out something ,i will let u know.
BTW: I didn`t asked... Which version of firmware are you trying to flash? For unbricking the device ,you need the exact version of software, that you have used on the device before the brick.
Do you have TWRP for XT2016-2 ?
VD171 said:
Do you have TWRP for XT2016-2 ?
Click to expand...
Click to collapse
Unfortunately there is no custom recovery for this device , otherwise we wouldn't be in this situation.
nikoman1987 said:
Unfortunately there is no custom recovery for this device , otherwise we wouldn't be in this situation.
Click to expand...
Click to collapse
Try to flash rom pmds29.70-81-5. it's the latest release.
Did you try to use lenovo rescue assitant ? https://support.lenovo.com/downloads/ds101291
VD171 said:
Try to flash rom pmds29.70-81-5. it's the latest release.
Did you try to use lenovo rescue assitant ? https://support.lenovo.com/downloads/ds101291
Click to expand...
Click to collapse
Yes ,already tried lenovo smart assistant ,fastboot flash,tested with version 29.70-81-5 ,RSD lite won't read any xml file included ,Motorola device manager couldn't recognise the version of the software installed on device. The problem is that there are some partitions that are protected from rewriting. I have tested with locked and unlocked bootloader,Lenovo Smart Assistant is giving me the error that ro.carrier is missing. When i try to config ro.carrier with the fastboot command : fastboot oem config ro.carrier RETEU , i get OKAY ,everything is successful ,but when i use the command fastboot getvar all , ro.carrier is still set as unknown . Even with unlocked bootloader ,i don't have full permissions over boot.img. Tested almost everything that i can think of. Even on Windows 7 and 10 . Blankflash file doesn't help too. If there is a compatible custom recovery fore One Macro ,there is a 99% chance to recover the device ,because i will have the premission to format ,even fix partitions if necessary. But i am starting to lose hope for successful unbricking ,because there is no support nor development for this device at the moment...
Hello,
Today I had the same problem of you.
I've uninstalled some applications from system and then restarted the phone.
So, the phone never went back.
I've had flashed a blank flash to my phone, and then I've flashed the system again.
After it, the phone was unbricked and booted perfectly without data losses.
I've translated the tutorial to english and to portuguese.
Please, give a try: https://forum.xda-developers.com/mo...recover-how-unbrick-bricked-motorola-t4145191