Root rsdlite and 1 click pathsaver will not write sys img

[stretchguy]

First I am very thankful to the devs, moderators and other forum senior members who take time out of their day to help people like me. I am normally very good at reading directions without having to ask for help but I am doing something wrong so here goes:

Phone is originally bought with the .893 build, it took a 901 OTA and later I used RSDlite to flash to .902. I am stock rooted, with some changes to the framework using jrummy16's ROMTOOL BOX tool. I changed battery icons, boot animation and font. I am trying to get to .905, so I first tried the OTA but of course it failed because I changed my framework, so I decided to use Rsdlite to flash a fresh copy of .902. Rsdlite "hangs" on step 15/22 "sending system img". It hangs longer than 45-50min. Eventually I quit Rsdlite, and I rebooted the computer, re-downloaded latest copy of program, moto usb drivers 64 bit, checked to make sure I was using a moto usb cord in back of computer and tried again. Same thing, so i tried a different computer same thing. So i tried the Bionic Path Saver and Restore/Root Utility for 5.9.902. This utility seems to be working great, but i see a 1-sentence error which states: "cannot load cdt.bin" the program continues to write various files but "hangs" on the step "sending system".

So it seems Rsdlite and 1-click pathsaver are hanging when writting the system img. I must be making a big noob mistake somewhere...thank you!

 

[OutOfPhase]

are you unzipping the file before flashing with rsdlite or are you letting rsdlite decompress? You can always try and use moto-fastboot to flash the 5.9.902. It is a longer process but have less issues then rsdlite. I can give you a step by step to use fastboot if you need it.

 

[stretchguy]

I allowed rsdlite to decompress the file and flash. I would love to try moto-fastboot to flash to 5.9.902, that would be great if you could help me with directions thank you!

 

[OutOfPhase]

before you try this you can try and run rsdlite as administrator and see if that makes a difference. The file you are trying to flash also might be bad try the one have linked and see if that works.
Also if you have an older computer rsd can take along time especially on the system image and weptop image

download this file and unzip. moto-fastboot

unzip your 5.9.902 fxz file (or use this one) to the same location

put your phone into fastboot by press and hold the volume down and power button at the same time on the phone. The fastboot menu will appear. plug your phone into your computer.

navigate in windows to the location you have everything unzipped to. click on the file symbol in the top left corner and when the bar becomes highlighted type cmd and enter if you have win 7. A comand prompt will come up. If not go to start and type cmd and hit enter. when the prompt comes up type cd c:\location of file with moto-fastboot and fxz file unziped

type and hit enter after each step

moto-fastboot flash mbm allow-mbmloader-flashing-mbm.bin
moto-fastboot reboot-bootloader
moto-fastboot flash mbmloader mbmloader.bin
moto-fastboot flash mbm mbm.bin
moto-fastboot reboot-bootloader
moto-fastboot flash cdt.bin cdt.bin
moto-fastboot erase cache
moto-fastboot erase userdata
moto-fastboot flash lbl lbl
moto-fastboot flash ebr ebr
moto-fastboot flash mbr mbr
moto-fastboot flash devtree device_tree.bin
moto-fastboot flash system system.img
moto-fastboot flash boot boot.img
moto-fastboot flash recovery recovery.img
moto-fastboot flash cdrom cdrom
moto-fastboot flash preinstall preinstall.img
moto-fastboot flash webtop grfs.img
moto-fastboot flash radio radio.img
moto-fastboot reboot

you should be on 5.9.902
all your data except on your sd-ext will be erased.

 

[stretchguy]

I tried following these directions but the adb device command did not yield any numbers...i shutdown and rebooted and the same thing happened when i punch in "adb device" it will say no device found or it wont list any numbers. I proceeded anyway and on the part where i give it the cdt.bin command it returns an error (i cant remember it word for word) about cdt.bin unable to be written. (<----something to that effect)

I then got the battery to low to program message on the bionic screen. I found an OP on how to splice a USB cable, and once it was powered back up I decided that maybe WIN 7 64bit was causing the issue with the adb.exe, i tried running adb.exe as administrator, nope. I tried running cmd.exe as administrator...nope. I re-installed drivers and rebooted...nope. So I decided to try RSD one more time before bed and it flashed the phone within 15min! Everythings good!

I mentioned this issue on another forum, and a Dev told me that when the battery is too low RsdLite will "Hang" and wont write the sys.img. I was sure my battery was good to go, but if 1-click and rsdlite couldnt write the image, on two seperate computers then maybe it was the bionic battery all along! How frustrating seeing as that i double checked before the battery before starting this whole process...so having the phone hard wired into the usb cable for power source seemed to be the fix.

Thank you for your time and typing those directions out for me I am very appreciative! You helped me, and I learned from you thanks again!

 

[OutOfPhase]

I tried following these directions but the adb device command did not yield any numbers...i shutdown and rebooted and the same thing happened when i punch in &quot;adb device&quot; it will say no device found or it wont list any numbers. I proceeded anyway and on the part where i give it the cdt.bin command it returns an error (i cant remember it word for word) about cdt.bin unable to be written. (&lt;----something to that effect)

I then got the battery to low to program message on the bionic screen. I found an OP on how to splice a USB cable, and once it was powered back up I decided that maybe WIN 7 64bit was causing the issue with the adb.exe, i tried running adb.exe as administrator, nope. I tried running cmd.exe as administrator...nope. I re-installed drivers and rebooted...nope. So I decided to try RSD one more time before bed and it flashed the phone within 15min! Everythings good!

I mentioned this issue on another forum, and a Dev told me that when the battery is too low RsdLite will &quot;Hang&quot; and wont write the sys.img. I was sure my battery was good to go, but if 1-click and rsdlite couldnt write the image, on two seperate computers then maybe it was the bionic battery all along! How frustrating seeing as that i double checked before the battery before starting this whole process...so having the phone hard wired into the usb cable for power source seemed to be the fix.

Thank you for your time and typing those directions out for me I am very appreciative! You helped me, and I learned from you thanks again!

I am glad you got it going.