Database Info

110 Error RUU 1.56 Fix - 100% unroot too!

Update - 2/21/2011
If you have bricked an HTC EVO this will likely NOT work for you and this is the wrong info to be reading. I have gotten a few emails from this link about EVO 110 errors.
12/26/2010 - This thread is super old now:
If you ran the 1.56 RUU and your phone no longer turns on visit htc.com, go to support, choose Hero (Sprint) and download the 2.1 system update.
Remove battery from your phone and start it up again, then run the exe file that you just downloaded -
http://member.america.htc.com/downlo...2.27.651.6.exe
------All the info below is kept for reference -------
(As of 3/31/2010 - I am 10 for 10 for getting these back and working!! 3/3 of going back to 100% stock)
Edit: I have no longer kept track... its been over a month and I know personally I've done about 15 more of these... with about half being return to stock.
If you need to contact me, PLEASE EMAIL instead of using private messages, it'll probably turn into a google talk chat anyways, so add me on there, [email protected] (Its just easier than having to log in here and reply to private messages, since I get emails on the go as well.)
So you just ran the 1.56 RUU and got a 110 error. Now your screen turns on and stays black and if you plug the phone into USB you see the HTC logo. Unplug it and see the RUU menu.
Like you, I decided to attempt to roll back using the RUU 1.56. I was hit with the 110 error, and nothing but fastboot would work, I was able to launch ./fastboot-mac oem boot to get into the system.
I tried ./fastboot-mac boot image/bootname.img and a billion other things like everyone else who is having the issue, but just like them I had no success. In the second post below are the steps to resolve this issue. This will either take you to your first Nandroid backup or to whatever ROM you choose to flash once you get recovery back. I have not found a way to get back to 100% stock, but at least your phone wont be a brick.
EDIT:As of 3/30/2010 @ 8:30 PM I was able to get my phone completely 100% to stock. I was able to do this by retrieving a Nandroid restore from someone who used flashrec to make their initial backup. This restore does not touch the recovery image but I was able to boot into my recovery then write the HTC recovery back on top of it. I now have 100% un-rooted phone. See Post number 2 for the right way to do this.?
I've helped a few people over log me in now.
I'm willing to continue doing this but it is cutting into my family time, I will do this for a "respectable" amount of money.
Feel like I've helped you??
Buy me some coffee!

(Zip attached includes fix and stock folders. Use the fix folder FIRST to get completely booted. You can use the stock folder if you want to get 100% stock after you have a running unrooted system but have RA recovery.)
Steps to resolve:
(You SHOULD have a Nandroid backup of some sort, if not download a ROM... Fresh1.1??)
1) Boot the phone to black screen
2) Plug phone into PC/MAC - The HTC logo should appear at this point
---- If you've been doing anything else, rerun the RUU and let it fail and reboot to the HTC logo.
3) PC - fastboot oem boot | MAC - ./fastboot oem boot
(Make sure you turn on USB Debugging under Settings --> Applications --> Developer)
4) Root your phone using asroot2
Code:
adb push asroot2 /data/local/
adb shell chmod 0755 /data/local/asroot2
adb shell
/data/local/asroot2 /system/bin/sh
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cd /system/bin
cat sh > su
chmod 4775 su
5) This is where your Nandroid backup comes into play.
(Browse to your nandroid folder, find your first backup and copy all of the .img files except system and cache to your SD card root directory)
NOTE: At this point you should dismount the SD card if you mounted inside of Android OS(Sense/Launcher)
6) run adb shell (PC - adb shell | Mac - ./adb shell)
7) type su
8) Run the following commands (if you get out of memory errors, type su again and try once more)
NOTE: Do not copy the "#"'s in the commands, the # just means you are running as SU, as opposed to the "$"
Code:
# flash_image recovery /sdcard/recovery.img
# flash_image boot /sdcard/boot.img
# flash_image misc /sdcard/misc.img
9) now... type reboot recovery
This time you should get your recovery menu, should have been RA or whatever you used... from there I did a complete nandroid restore and my system booted.
Also, after I did this I did try to let it boot without doing a recovery and it wouldnt go anywhere... but I'm fairly impatient... it may have wanted to load. I figured it best to do an entire Nandroid restore though.
-------------------------------------------------------------
100% Stock Configuration Work Around
-------------------------------------------------------------
Non-Rooted Nandroid Backup:
nandroid.7z
I was able to get my phone completely 100% to stock. I was able to do this by retrieving a Nandroid restore from someone who used flashrec to make their initial backup. This restore does not touch the recovery image but I was able to boot into my recovery then write the HTC recovery back on top of it. I now have 100% un-rooted phone. I'm not sure how to go about posting a 127MB file, what do you think it the best place?
After restoring the Nandroid backup I tried this:
Code:
Dustan-Bonneys-MacBook:tools dustanbonney$ ./adb shell
$ su
su: permission denied
Then I rebooted to recovery (I used RA 1.5.2)
Code:
Dustan-Bonneys-MacBook:tools dustanbonney$ ./adb remount
remount succeeded
Dustan-Bonneys-MacBook:tools dustanbonney$ ./adb shell
/ # mount -a
mount: mounting /dev/block/mmcblk0p2 on /system/sd failed: No such file or directory
/ # cd /sdcard
/sdcard # flash_image recovery /sdcard/Stock/recovery.img
flashing recovery from /sdcard/Stock/recovery.img
/sdcard # reboot recovery
I was booted to the Triangle and exclamation mark... I pulled the battery and booted up normally.
Stock Kernel - 2.6.27-533ce29d [email protected] )
Stock Build - 1.56.651.2 CL85027 release-keys

Other things that should be mentioned:
If you used RA 1.6.2 - I was unable to get my boot.img or the stock boot.img from the RUU's rom.zip to flash back to the recovery partition. I had to use the RA 1.6.2.img and "flash_image recovery /sdcard/recoverynamegoeshere.img"
It seems that if you've flashed the radio update, the RUU does not write the radio back successfully. Others have had issues going back to the stock radio using the upgrade.zip option as well.
I attempted to use the boot.img, recovery.img, from the RUU's rom.zip with no success. I might try it again. I was able to get to stock recovery (Triangle and exclamation) and to the Hboot menu... but from hboot I had to run the RUU and rebrick the device cause I couldnt get anything at that point, even fastboot oem boot wouldnt load.
There have been times when I get weird issues writing the flash recovery, boot, or misc and when you reboot and load "fastboot oem boot" it wont look like it goes anywhere.... check "adb devices" and your device should be listed. From there do an "adb remount" and then "adb shell" and reflash once more and then "reboot recovery".
If all else fails, I'm available for a small fee.
[email protected]

Anxiously waiting your news. Just encountered this problem today.

Updated ...
imekul said:
Anxiously waiting your news. Just encountered this problem today.
Click to expand...
Click to collapse

Wow! If you've fixed this, I think you're everyone's hero now. We won't have to worry about using the RUU now

I was going to try something similar to this today, but i was unable to brick my phone using the 1.56.651.2 RUU. I was running Flipz updated radio and DamageControl v2.0r2.. The RUU completed successfully..
I was reading over the forum post in http://forum.xda-developers.com/showthread.php?t=645002 and i read that you could boot the system using the command 'fastboot oem boot' I was going to try to use FlashRec to do the work of Flashing the recovery, then booting into recovery and use nandroid.. but you beat me to it! Good work!

I attempted flashing a new recovery image this way with no avail... I also attempted only
Code:
flash_image recovery /sdcard/recovery.img
and still was unable to boot the phone into recovery. I think it had to have been something with doing boot.img and recovery.img at the same time... I dont know what the misc.img does and I'm assuming data.img is userdata... but I did them all and then it worked...
Other users also tried flashrec and with no success... right track though.
chavo2005 said:
I was going to try something similar to this today, but i was unable to brick my phone using the 1.56.651.2 RUU. I was running Flipz updated radio and DamageControl v2.0r2.. The RUU completed successfully..
I was reading over the forum post in http://forum.xda-developers.com/showthread.php?t=645002 and i read that you could boot the system using the command 'fastboot oem boot' I was going to try to use FlashRec to do the work of Flashing the recovery, then booting into recovery and use nandroid.. but you beat me to it! Good work!
Click to expand...
Click to collapse

What do u mean by 3) PC - fastboot oem boot | MAC - oem boot?

blankd3ckskat3r said:
What do u mean by 3) PC - fastboot oem boot | MAC - oem boot?
Click to expand...
Click to collapse
if your using a pc type fastboot oem boot
if your using a mac type ./fastboot oem boot

This!
Thanks Regaw
regaw_leinad said:
if your using a pc type fastboot oem boot
if your using a mac type ./fastboot oem boot
Click to expand...
Click to collapse

Trying this right now.
So far, am getting lots of "mtd: write error" and "mtd: re-read error" Out of memory errors for flashing the recovery image. Guess I'll give this some time, and try to su again and reflash? Or should I kill it as soon as the Out of memory errors pop up and try again?

If you get errors like...
adb shell
su
flash_image recovery .........
(out of memory... etc)
Then...
just su again... so you really su twice
its what I had to do.
imekul said:
Trying this right now.
So far, am getting lots of "mtd: write error" and "mtd: re-read error" Out of memory errors for flashing the recovery image. Guess I'll give this some time, and try to su again and reflash? Or should I kill it as soon as the Out of memory errors pop up and try again?
Click to expand...
Click to collapse

Trying it a second time, and so far am getting a bunch of Out of memory errors. After the first one "finished," I did as you recommended and typed "su" a second time, and then typed the "flash_image recovery /sdcard/recovery.img" command.
So far, looks like it's giving the same errors the second time around.

This second attempt, it ended with "error writing recovery: No space left on device."
Just to be sure, I checked the SD card, and that has over 1 GB of free space.

If you're willing to allow something like logmein.com or some way for me to remote assist you, I would like to try. [email protected] if you're in.
imekul said:
This second attempt, it ended with "error writing recovery: No space left on device."
Just to be sure, I checked the SD card, and that has over 1 GB of free space.
Click to expand...
Click to collapse

Sounds awesome. Thanks. I'll e-mail you now.

Dun Dun Dun... The results are in!
imekul said:
Sounds awesome. Thanks. I'll e-mail you now.
Click to expand...
Click to collapse

dfbonney is the man!!
After a friendly little session on LogMeIn Express, I am good as new! How awesome!!

imekul said:
dfbonney is the man!!
After a friendly little session on LogMeIn Express, I am good as new! How awesome!!
Click to expand...
Click to collapse
We ended up just needing to run
Code:
adb shell
reboot
fastboot oem boot
adb shell
su
//flash commands here
that seemed to do it. so make sure if you're having issues to restart the device and try again!
Edit: Also, we didnt get data.img to work so we only did boot, recovery, and misc.img's

[Q] adb shell "exec '/system/bin/sh' failed: No such file or directory (2)"

Hey,
Ok so a little backstory before my problem: So I was in the middle of putting a new ROM on my captivate. I had one before but i wanted to change so I put the rom in update.zip and installed it will clockworkmod recovery. It installed fine I think but then when I tried to boot it gets stuck on the boot screen. So i tried to boot in recovery mode. I geld down both the volume buttons and the power button until it reboots twice, then I let go of the power button. but it still gets stuck on the boot screen and does not go into recovery mode. So i plugged it into my computer and using
Code:
adb devices
it shows up under recovery mode. So far so good. I can use the
Code:
adb reboot
and
Code:
adb push
commands fine. but when i try to use
Code:
adb shell
it says
Code:
exec '/system/bin/sh' failed: No such file or directory (2)
So i can not reflash the recovery image. I read that I just needed to mount the /system file. But i do not know how to do this. the "mount" command does not work with adb. I would appreciate anything to help me to either reflash the rom or restore to factory or anything where i can work off of. thanks

I have exactly the same problem.
Did you get to a solution to this?
Good luck, dude.

Is there a solution to this without using a Motorola Factory cable? I don't have the resources to make one and I don't have money to buy one.

I'm not sure putting the rom into "update.zip" was the right choice.
adb shell could fail because the partition is not mounted, the sh binary is not installed, or not at the correct location
If you can still get the captivate into download mode, you could use odin/heimdall to flash a working ROM.

First of all...thanks to everyone that has EVER posted in the XDA forums! I've spent days reading them and I came across one that had a suggested solution for my problem. So let's start...
1) Bricked
2) ADB is finally working again...so..not a problem any longer
(Don't ask me how I got it to work again....I have no idea. System was wiped while using TWRP from a bootloop)
3) Now...with system wiped I have no '/system/bin/sh'
4)adb shell will not work because of this. adb root does not work because of production model. adb remount is not permitted.
Now....I came across a thread that suggest using r2.6.2.kindlefire.boot.insecure.img and zergRush. I have the zergRush file, but I need the r2.6.2.kindlefire.boot.insecure.img to push with adb.
Does anyone know where I can get the r2.6.2 at? Filesonic is disabled and Multiupload will not return page.
Link I came across: addictivetips /mobile/gain-root-adb-access-with-insecure-boot-image-for-kindle-fire/

ROM Manager will BREAK YOUR RECOVERY!!! DO NOT USE!!!

Any of us who have installed ROM Manager from the market have gone through some real pain trying to recover from using its recovery. Until it is verified as fully functional by one of this forum's top devs, do not install it! It's not ready for prime time.
Instead, use krylon360's outstanding CWM Recovery here: http://forum.xda-developers.com/showthread.php?t=1099374. Follow the directions in the OP carefully.
Also, check mad_fitter's great thread on steps needed to flash on this phone. Step 12 addresses what happens if you try and flash using ROM Manager's recovery (ODIN):
http://forum.xda-developers.com/showthread.php?t=1122508
I see that contributing members are still having these issues and hope to help drive the point home. ROM Manager will be great when it works for our device, but right now it doesn't.
Sent from my SGH-T959V using XDA Premium App

I was able to use ROM manager on my device. The only thing that CWM doesn't seem to do is:
(might need to remount system as r/w)
// change permission on recovery binary so we can replace it
su
cd /system/bin
chmod 777 recovery
exit
exit
// push new recovery binary
adb push recovery /system/bin
Once this is performed the CWM from ROM manager works fine.
I just did my co-worker's SGS4G and can confirm this.

matthenry87 said:
I was able to use ROM manager on my device. The only thing that CWM doesn't seem to do is:
(might need to remount system as r/w)
// change permission on recovery binary so we can replace it
su
cd /system/bin
chmod 777 recovery
exit
exit
// push new recovery binary
adb push recovery /system/bin
Once this is performed the CWM from ROM manager works fine.
I just did my co-worker's SGS4G and can confirm this.
Click to expand...
Click to collapse
Hmmm. Can you send this to koush

I had to use recovery file from krylon360's CWM Recovery to make my ROM manager work. It works fine for me.
But of late it gets stuck while recovering on the .andriod_secure folder. Which i think is the last step on the recovery.
No big deal, just pull the battery out and power the phone back on and everything is back to normal.

Yeah that last part it hangs on isn't a big deal. I believe that is where the apps2sd apps are stored and it's not a big deal of that isn't wiped.
Anytime you wipe it's gonna hang as well as any time you do a restore. It will hang while restoring that same dir but once you get to that point system and data have already been restored so you can just pull the battery and reboot from recovery.
Sent from my SGH-T959V using XDA Premium App

[Q] Samsung 4g Exhibit framework-res.apk HELP PLEASE ILL GIVE THANKS 2 ALL

i have a Samsung Exhibit 4g phone, rooted and backed up by titanium backup. I tried using the kitchen theme stuff, and i copied the original framework-res.apk file to a folder in the sd card . Then i copied the framework-res.apk file from the UOT zip to the location where the original file was and rebooted the phone. Now my phone is stuck at the Samsung logo screen and it keeps looping. anyway to fix this? :/
P.S: the location i copied the original file doesnt show up in the recovery menu when i go to install package. Also, when i tried the downloading mode, it just says downloading and doesnt do anything. Tried factory restore too. The original file is somewhere on the sd card i just dont know how to access it and put it back into its original location.... no i dont have a copy of it on my computer.

Follow this guide
If you are in a loop, you have to manage this fast or else it will just reboot again, i suggest a copy and paste function for the third command. also I don't know for sure whether /dev/block/st19 is your /system partition, but i'll try.
Code:
adb shell
Code:
su
Code:
mount -o rw,remount /dev/block/st19 /system
Code:
exit
Code:
adb push /pathtoyour"ORIGINAL"frameworkres /system/framework
PS, Do this within 15-20 seconds. (You will have multiple attempts as you can do it after every loop)
once you are done, just hard reboot your phone(using power button)
Also you do this in a terminal/cmd window with your phone plugged in.

wait
airfluip1 said:
If you are in a loop, you have to manage this fast or else it will just reboot again, i suggest a copy and paste function for the third command. also I don't know for sure whether /dev/block/st19 is your /system partition, but i'll try.
Code:
adb shell
Code:
su
Code:
mount -o rw,remount /dev/block/st19 /system
Code:
exit
Code:
adb push /pathtoyour"ORIGINAL"frameworkres /system/framework
PS, Do this within 15-20 seconds. (You will have multiple attempts as you can do it after every loop)
once you are done, just hard reboot your phone(using power button)
Also you do this in a terminal/cmd window with your phone plugged in.
Click to expand...
Click to collapse
wait, sorry im new to this stuff, but i plug in my phone to the computer and then type all of that into cmd while the phone is turning on right? Ill give it a try, but also, i tried using odin before but my computer just doesnt detect the phone all the drivers are install and everything too... so idk if this willl work but ill try and let you know
edit: i tried it, and umm sorry again for being a noob, i plugged in the phone and the battery screen cameup, i opened cmd.exe, turned the phone on and typed "adb shell" in cmd, but uh it said its not a command...

I am sorry, I assumed you had installed the Android SDK.
Google it.
Sent from my SGH-T959V using xda premium

Then install the Samsung composite drivers. Google them.
Then retry the process.
I can guaranty that it will work.
Sent from my SGH-T959V using xda premium

downloaded
airfluip1 said:
Then install the Samsung composite drivers. Google them.
Then retry the process.
I can guaranty that it will work.
Sent from my SGH-T959V using xda premium
Click to expand...
Click to collapse
http://www.samsung.com/us/support/owners/product/SGH-T759ZKBTMB
i downloaded them 2 weeks ago already.... that is if that is what your talking about... i tried it again and it also gave me the message Samsung Android Modem has already been installed or something

OK, but did you install the sdk?
Dowload and install the JDK(just choose the one for your OS) LINK
Then install the SDK from android LINK

[Recovery]CWM Recovery&Bootmenu 2ndinit for Motorola XT300(Spice)

Do it at your risk!
Hi,everybody.
I had successfully ported CWM recovery&Bootmenu 2ndinit for spice,which allows us to use custom rom.
Now,you have two ways to use CWM recovery.One is entering CWM recovery through bootmenu,the another way is entering CWM recovery through stock recovery(Fake flash update zip).
Method 1:Through bootmenu
First of all,you need to root your spice.And then install bootmenu.
Download the bootmenu.tar file(attached).And push it into /sdcard/
Turn on usb debugging on your phone. And use the following commands in adb:
Code:
C:/> adb shell
$ su
# mount -o remount,rw /dev/block/mtdblock1 /system
# mkdir /system/bootmenu
# cd /system/bootmenu
# busybox tar -xf /sdcard/bootmenu.tar
# rm /system/bin/charge_only_mode
# busybox ln -s /system/bootmenu/binary/bootmenu /system/bin/charge_only_mode
# sync
# mount -o remount,ro /dev/block/mtdblock1 /system
# exit
The bootmenu will be installed.
Restart your device once.
Using Boot Menu:
Turn your phone off.
Press the Power Button.
After 1-10 seconds, the red led on your phone will light up for just 3 seconds (Still while the Motorola logo is being displayed).
Exactly when the led lights up, press the volume down button.
You will see the BootMenu, use the Volume Button to navigate up and down, and the power button to select an item.
Then you can select enter CWM recovery.(Someone say CWM's backup&restore cannot work,you can use method 2 for it)
Method 2:Through stock recovery(Fake flash zip)
I found that we can use CWM recovery with stock recovery leak(Fake flash update zip,like OpenRecovery),but this leak is only existed in SESGC_U3_10.10.0_RT firmware.
I have dumped this recovery(Attached file:recovery.img).And flash it by fastboot.It works well with SESLA_U3_01.72.0 firmware.
And then to flash a fake update.zip(Attached file:update.zip) from the root of your sdcard,you will enter CWM recovery!
By the way,if you want to port CM7 for spice,you need to use 2ndinit for your froyo/gingerbread,because it has locked bootloader.
I have compiled CM7 for it,and it can boot up but stuck in white screen after CM bootanimation.If you want to continue my work,you can checkout my github.
Thanks to:
CyanogenMod
koush
...
sorry for my poor English.

With the first method i can't make a nandroid backup, i'll try it with the second!

Nand backup question
GentryLamp said:
Do it at your risk!
Hi,everybody.
I had successfully ported CWM recovery&Bootmenu 2ndinit for spice,which allows us to use custom rom.
Now,you have two ways to use CWM recovery.One is entering CWM recovery through bootmenu,the another way is entering CWM recovery through stock recovery(Fake flash update zip).
Method 1:Through bootmenu
First of all,you need to root your spice.And then install bootmenu.
Download the bootmenu.tar file(attached).And push it into /sdcard/
Turn on usb debugging on your phone. And use the following commands in adb:
Code:
C:/> adb shell
$ su
# mount -o remount,rw /dev/block/mtdblock1 /system
# mkdir /system/bootmenu
# cd /system/bootmenu
# busybox tar -xf /sdcard/bootmenu.tar
# rm /system/bin/charge_only_mode
# busybox ln -s /system/bootmenu/binary/bootmenu /system/bin/charge_only_mode
# sync
# mount -o remount,ro /dev/block/mtdblock1 /system
# exit
The bootmenu will be installed.
Restart your device once.
Using Boot Menu:
Turn your phone off.
Press the Power Button.
After 1-10 seconds, the red led on your phone will light up for just 3 seconds (Still while the Motorola logo is being displayed).
Exactly when the led lights up, press the volume down button.
You will see the BootMenu, use the Volume Button to navigate up and down, and the power button to select an item.
Then you can select enter CWM recovery.(Someone say CWM's backup&restore cannot work,you can use method 2 for it)
Method 2:Through stock recovery(Fake flash zip)
I found that we can use CWM recovery with stock recovery leak(Fake flash update zip,like OpenRecovery),but this leak is only existed in SESGC_U3_10.10.0_RT firmware.
I have dumped this recovery(Attached file:recovery.img).And flash it by fastboot.It works well with SESLA_U3_01.72.0 firmware.
And then to flash a fake update.zip(Attached file:update.zip) from the root of your sdcard,you will enter CWM recovery!
By the way,if you want to port CM7 for spice,you need to use 2ndinit for your froyo/gingerbread,because it has locked bootloader.
I have compiled CM7 for it,and it can boot up but stuck in white screen after CM bootanimation.If you want to continue my work,you can checkout my github(["github . com/gentrylamp").
Thanks to:
CyanogenMod
koush
...
sorry for my poor English.
Click to expand...
Click to collapse
Hello!
Mr GentryLamp, congratulations done, I do not see many people who understand Android programming interested in XT300, you're the man!
I performed all the procedures above, installed bootmenu (but renamed the "charge_only_mode" as "charge_only_mode.bin" the backup purposes), I installed the old recovery with flash_image (command "flash_image recovery path_of_recovery _.img") and put the update.zip on the root of SD.
I can not perform with nand backup recovery from bootmenu (advance notice, and obviously non-functional), and the second way does not work (the leakage update.zip).
When trying to nand backup the nand, the device is the screen backuping ("SD memory free... Backup system...") For about an hour, and then the screen goes white, and end.
You know how I could accomplish this nand backup? You got on your device? Do you know any script that I can use for it?
If you need more information, or something that I test on my device, I place myself at your disposal.
Sorry my english too, Google Translate help much Brazilians.
Hug.

Regisboliver said:
Hello!
Mr GentryLamp, congratulations done, I do not see many people who understand Android programming interested in XT300, you're the man!
I performed all the procedures above, installed bootmenu (but renamed the "charge_only_mode" as "charge_only_mode.bin" the backup purposes), I installed the old recovery with flash_image (command "flash_image recovery path_of_recovery _.img") and put the update.zip on the root of SD.
I can not perform with nand backup recovery from bootmenu (advance notice, and obviously non-functional), and the second way does not work (the leakage update.zip).
When trying to nand backup the nand, the device is the screen backuping ("SD memory free... Backup system...") For about an hour, and then the screen goes white, and end.
You know how I could accomplish this nand backup? You got on your device? Do you know any script that I can use for it?
If you need more information, or something that I test on my device, I place myself at your disposal.
Sorry my english too, Google Translate help much Brazilians.
Hug.
Click to expand...
Click to collapse
I haven't confirmed whether NAND backup will work in bootmenu,but it works well in fake update.zip way.
If your firmware version is SESLA_U3_01.72.0,you need to boot the phone into fastboot mode(bule screen,pressing Vol-up&Vol-down while the phone boots up),and using fastboot to flash recovery.img.
BTW:Some firmware(such as SESGC_U3_10.10.0_RT) do not allow fastboot.You can see some warnings in fastboot bule screen.

More questions...sorry
GentryLamp said:
I haven't confirmed whether NAND backup will work in bootmenu,but it works well in fake update.zip way.
If your firmware version is SESLA_U3_01.72.0,you need to boot the phone into fastboot mode(bule screen,pressing Vol-up&Vol-down while the phone boots up),and using fastboot to flash recovery.img.
BTW:Some firmware(such as SESGC_U3_10.10.0_RT) do not allow fastboot.You can see some warnings in fastboot bule screen.
Click to expand...
Click to collapse
Thanks for reply man o/
My firmware is SESLA_U3_01.72.0, nand backup really not work on first method, and in the second method, also not .
I followed a guide like this: [ht tp:// forum . xda-developers . com/showthread.php?t=918275]. I believe the command is flash_image the same effectiveness as the fastboot, because I could run the CWM_recovery from the update.zip (you said that this gap is only SESGC_U3_10.10.0_RT recovery firmware, and I do not use - no clue of what it is, just know mine, and Chinese MONSTER).
But I saw now that you've lost your XT300 and therefore believe that there is no possibility to test or you do something for it. But anyway, I am grateful and even my disposal device testing, if desired.
Taking advantage ... would be able to put an 'if' that is, the low volume was not pressed, he continued with the 'charge_only_mode', so that the battery could be charged with the device off? I would also like to know if you know if it is possible to make a nand backup from a script, with the connected device, and if you have some kind of script ...
Excuse me for asking so many questions to you is that I know someone who knows and is as interested as you.
Thank you!
Hug.

i had the same problem with NAND backup using method 2

Regisboliver said:
the low volume was not pressed, he continued with the 'charge_only_mode', so that the battery could be charged with the device off?.
Click to expand...
Click to collapse
The phone will not enter charge only mode when you install bootmenu.
In method 2,NAND Backup&Restore works well when I use spice,I'm sorry that it doesn't work with some phone.

GentryLamp said:
The phone will not enter charge only mode when you install bootmenu.
In method 2,NAND Backup&Restore works well when I use spice,I'm sorry that it doesn't work with some phone.
Click to expand...
Click to collapse
I understand that only with bootmenu the device not charge without boot but, my question was would like to know if one can apply this procedure to boot: power button pressed > magenta led light and Motorola logo > {(before bootanimation and bootinstructions) volume down button pressed while red led light? "yes? -> bootmenu" | "no? -> execute the real charge_only_mode binary", execute charge_only_mode.bkp for example, in my case, since renamed the original charge_only_mode for subsequent restoration of boot } > boot. Understand my question? :s
But if there is, I made two scripts, one for installation and uninstallation of another bootmenu (if someone wants I can post), but if you do not give to run the above algorithm, I use the update.zip CWM_recovery the same, so I can recharge my device is switched off, while I find I try to do a custom for 2ndinit.
Mr GentryLamp, you said above, in the opening thread, it has ported a CM7 for XT300 and it crashed after the Motorola logo. I some time ago, I replaced the file libGLES_android.so (in the folder / system / lib / egl), trying to enable the GPU, I fear there is not even in the chipset of XT300 and while on the Motorola logo, the screen was white, blinking. You keep intact the lib folder? Forgive me if I did wrong or very noob question, because I have no expertise in ROM switches, ports, CM, etc...
Regarding the nand backup, searched about it here, to see if I can find at least one script for it, because then I can become more peaceful to test changes more dangerous, not bothering with RDS, SBF ...
Thanks again bro!

Is there a way to port to other Motorola devices? I have a DROID x that I need to try this on because it is stuck in safe mode. How did you port this to flash in stock recovery?
Sent from my DROID4 using Tapatalk 2

Great job, but I think this work is not useful because we don't have a custom Rom for this phone and the stock Rom sucks, I have this xt300 from my carrier iusacell Mexico, and is so slow and to f**king buggy, if is thera a chance to have a good froyo or gingerbread stable Rom will be perfect this phone have some potential but is too capable by the Motorola software
I hope we can some time get a good Rom for this great and cheap phone