Moot Master
Posted 10 July 2013 - 10:17 PM
but make sure its the FXZ that I posted for u not any of the ones in my OPok yeah u can't boot ok open the FXZ an delete all the files that start with "mbm" an then try flashing again
Sent from my GT-I9505G using Tapatalk 2
n00b
Posted 10 July 2013 - 10:41 PM
I did what you said i removed the mbr and this is what i got
Untitled.png 304.09KB
22 downloads
n00b
Posted 10 July 2013 - 10:43 PM
where could i find the one you posted for me? i removed the mbr from p2d_targa_cdma_targa-user-2.3.4-5.5.1_84_dbn-55-110814-release-keys-verizon-us.
n00b
Posted 10 July 2013 - 11:32 PM
I deleted everything and started all over and followed the steps. I ran FIXCDT.dat and also Motofail. Here are the result. Maybe this could help us find the solution my problem.
FIXCDT.png 250.76KB
14 downloads
Motofail.png 335.89KB
14 downloads
Android Warrior
Posted 11 July 2013 - 02:01 AM
Non potest esse nisi unus
Moot Master
Posted 11 July 2013 - 05:57 AM
thank you Sam I totally forgot the XML editingIn order to use the jb fxz with rsd you have to edit the xml file. I'm barely awake right now but I'll provide instructions later this morning. Basically you have to remove the two oem commands or it'll fail.
Sent from my Xoom using Tapatalk 4 Beta
Android Warrior
Posted 11 July 2013 - 06:00 AM
No problem. Here's a link to a fixed xml file to replace in the FXZ:
That should allow it to flash fine.
Non potest esse nisi unus
n00b
Posted 11 July 2013 - 07:20 AM
Am i doing this correctly? I just copied and pasted it to a note pad and it looks like this. I'm not sure where to go from here.
The Link.png 459.11KB
12 downloads
Moot Master
Posted 11 July 2013 - 07:27 AM
just move the file into the FXZ an copy an replace the fileAm i doing this correctly? I just copied and pasted it to a note pad and it looks like this. I'm not sure where to go from here.
Android Warrior
Posted 11 July 2013 - 07:37 AM
Please don't use notepad to edit xml files. It may cause you problems. Just replace the file, as Sarge said.
Non potest esse nisi unus
Android Warrior
Posted 11 July 2013 - 08:00 AM
Um.....no? Where are all the files from the FXZ???? The xml has to be in the same folder as all the files in the FXZ.
Non potest esse nisi unus
n00b
Posted 11 July 2013 - 08:12 AM
Sorry
Was trying it on
p2d_targa_cdma_targa-user-2.3.4-5.5.1_84_dbn-55-110814-release-keys-verizon-us
instead o fcdma_targa_9.8.2O-72_VZW-22_cfc.xml
Give me a second so i could edit the HTML
n00b
Posted 11 July 2013 - 08:31 AM
Seems like everything went well. My android turned on and is stuck on a screen saying droid. The RSD says please manually power up this phone. Should i diconnect the phone? reflash it again?
Android Warrior
Posted 11 July 2013 - 08:33 AM
Just let it sit for a bit. I wouldn't touch it for at least 20 minutes. If it's still stuck, let us know. Means it's boot looping and we'll have to fix that.
Non potest esse nisi unus
n00b
Posted 11 July 2013 - 09:08 AM
Its been about 35 mins. Its still says droid.
Android Warrior
Posted 11 July 2013 - 09:20 AM
So you're boot looped. That's not a good place to be. Boot into recovery (Power off, hold volume up and down while pressing power, volume down to recovery, volume up to select....when the droid icon comes up, hold volume down and press volume up to get the menu). Once there perform a factory data reset.
Non potest esse nisi unus
n00b
Posted 11 July 2013 - 09:30 AM
factory data reset completed rebooting system now
I get the motorola sign and back to droid.
Edited by theman423, 11 July 2013 - 09:31 AM.
Android Warrior
Posted 11 July 2013 - 09:32 AM
Reflash the FXZ and this time show me the RSD log. swdl.txt.
Non potest esse nisi unus
0 members, 1 guests, 0 anonymous users
