Gi guys.
I have a problem. I want to install a Custom ROM on my Motorola Dey Mini (XT320) - TNBST_4_0A.1F.10RPS_flex_WE_Orange_Poland - using RSD Lite. I'm following the tutorial - running RSD Lite, opening the ROM file, turning my phone on into the recovery mode, connecting it to computer, clicking "Start" in RSD Lite. Then, unfortunately, the ROM isn't flashed The process is failed, there is an information about this:
"Failed flashing process. Failed flashing process. Unable to retrieve interface handle. (0x7027); phone connected"
What do I have to do to successfully flash my Motorola Defy Mini?
Please, help me!
Its not a custom rom and you must not boot into recovery. You must have your phone turned on normally and then click start. It will reboot to flash mode automatically.
Sh0m1 said:
Its not a custom rom and you must not boot into recovery. You must have your phone turned on normally and then click start. It will reboot to flash mode automatically.
Click to expand...
Click to collapse
I'm doing like you wrote and still the same...
Related
Okay so im using defy. I flashed MIUI rom before using recovery>stable recovery. And then I reboot. After I reboot, the phone wont start and it just show the MOTOROLA logo.
And then I pulled out my battery and run 2nd innit (press volume down when LED light up). And when I try to re flash ROM and I try to enter Custom Recovery or Stable Recovery, it state below
" E:Error in/system/bootmenu/script/recovery.sh
(Result: No such file or directory) "
Can this be resolved or my defy is bricked ? Argh PLEASE HELP ME PLEASEE
Well... there is always RSDLite... Check General section - sticky threads for details
You might be using old boot menu, try to flash new boot menu and recovery, at least 5.0.3.1+.
You can go back to your original stock using RSD Lite, then root and install 2nd init. After it installs the recovery, download the latest recovery (you can search the dev threads for this).
Hi, same problem here!
I instaled cm9 on my defy. Now when I try to turn it on, can't. Also cant open recovery, cause there is error: "busybox was not created in footfs". And when I open recoveri, it says: "E:Error in /system/bootmenu/script/recovery.sh (result: no such file or directory) Could someone please help me?
Also rsd doesn't recognize my mobile...
i had an issue updating from one CNA nightly to a newer one the other day, and was left with no option but to flash the original .sbf for my version of the phone & carrier etc. That worked fine, and i have a bootable stock phone, but when trying to install any rom, either through CWM recovery or fastboot, i get issues.
if i try through CWM the correct method, i get stuck on the Moto Dual Core screen forever, until i battery pull and have to sbf flash through RSD Lite again.
If i try through Fastboot, i get error Failed to process command flash: xxxxxxxxxx error (0x0003)
can anyone help please? i've been using various CM7/9 ROMS for months now, and cant deal with being stuck back on MotoBlur stock junk
many thanks in advance!
ishamm said:
i had an issue updating from one CNA nightly to a newer one the other day, and was left with no option but to flash the original .sbf for my version of the phone & carrier etc. That worked fine, and i have a bootable stock phone, but when trying to install any rom, either through CWM recovery or fastboot, i get issues.
if i try through CWM the correct method, i get stuck on the Moto Dual Core screen forever, until i battery pull and have to sbf flash through RSD Lite again.
If i try through Fastboot, i get error Failed to process command flash: xxxxxxxxxx error (0x0003)
can anyone help please? i've been using various CM7/9 ROMS for months now, and cant deal with being stuck back on MotoBlur stock junk
many thanks in advance!
Click to expand...
Click to collapse
Reflash the gingerbread pudding .sbf, you're bootloader isn't unlocked anymore.
Sent from my MB860 using xda premium
the sbf i flashed was from the pudding page, and i unlocked the bootloader again fine, have the unlock sign on the Moto boot logo, just cant get any further than that with ROMs anymore..
EDIT: i am also getting the issue when flashing any kernels,
I can flash a recovery through fastboot, which it says is successful, but when i try to boot into recovery i get failed to boot 2, entering RSD mode.
My milestone 2 is completed bricked and can't be recognized by PC. But I can log in the official recovery screen. I have downloaded a update.zip file from a link （not sure if it is an official link, as I can't find it through Motorola website). It prompted "signature error" when installed. Not sure anyone can provide an update.zip file, so that I can try if I can save my Milestone2. Thanks in advance!
as long as you can enter the stock recovery. your device isn't bricked. did you try to do a full wipe in stock recovery? did you try to use another usb port in bootloader mode? sometimes you get a black screen in bootloader mode, but you pc recognizese your device very well. did you install all drivers on your pc?
lulli1 said:
as long as you can enter the stock recovery. your device isn't bricked. did you try to do a full wipe in stock recovery? did you try to use another usb port in bootloader mode? sometimes you get a black screen in bootloader mode, but you pc recognizese your device very well. did you install all drivers on your pc?
Click to expand...
Click to collapse
1. I have tried full wipe, but didn't work. The machine reboot again and again;
2. I have tried another usb port, another PC and even another operating system (win7 and winXP), also didn't work.
3. I am sure I have installed the drivers, as PC can recognize my phone when it is OK before;
As I can only entered the official recovery screen, I think I can try if it worked when I update with an official update file. Anyway, thanks for your suggestions and reply!
hi,guy.i think you should do the curect usb driver for your pc recongnizing first. than choose a ringt bootlaoder offical ROM. curse your phone can login the rockrecovery screen means its ok! isn't?
I think the only way for you to get an update.zip is with another milestone 2 running froyo, that way you can update it via OTA, and before the phone reboots, take the update.zip from the /cache partition.
Sent from the U
Edit: All happy now, a change of pc solved the problem of not detecting the device!
Hi all! I have another challenge for you!
Right, I've got myself in a tizz with my Defy +. While updating between CM10.1 versions I found myself in a situation where I couldn't get past the boot animation. So I loaded the TWRP restore I had made prior to updating...
Except it wouldn't, instead it came up with 'Failed' each time I tried any of the TWRP backups I had created. So the next step was to wipe partitions and start flashing various ROMs until I found one what worked. Except they didn't work either. Eventually I thought the best idea would be to just turn the phone off and see where I was with booting.
So power on, boot logo, blue light, red light then... nothing. Just the boot logo static. Went into the custom bootloader to go into recovery again, nothing. Pressing Custom recovery simply loops back to the top bootloader screen.
Ok next step, flash .sbf and start from scratch. So into the Moto bootloader it is to plug in and flash except... it's no longer detected by my computer.
"Ok" I think, "We'll just flash files from the SD card after I use an external SD card reader.
Except now when I enter Moto recovery to flash the TWRP recovery I get:
-- Install /sdcard ...
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verifiaion failed
Installation aborted
So to recap:
1) Tried to flash and update, failed
2) Tried to recover, recoveries wouldn't write (I think this is becaue I'd changed to EXT4 on /data and /cache and had forgotten to go back to EXT3 before trying to recover)
3) Tried to boot, epicly failed
4) Tried to flash .sbf, Defy+ won't appear in RSDLite 5.7 with latest driver
5) Tried to flash from SD card, sig verification failed
6) Googletastic for the last four days
Notes:
a) I CAN charge the Defy+ using the wall charger but I get '?' for the battery level indicator but...
b) In Cmod bootloader 2.1 (Which I can use a little) it shows the correct battery level
c) I /was/ getting some errors with not being able to mount /cache from the moto recovery but I've since used the cmod bootmenu 2.1 to set it back to ext3 and it's all happy now, those errors aren't appearing
d) Plugging in my Defy red lens I get W8 x64 detecting the correct portal drivers and such but when I go to moto bootloader this device also doesn't appear in RSDLite
e) Both devices prompt windows to install a Motorola Flash Interface driver in Device Manager when plugged in in moto bootloader mode and neither device appears in RSDLite despite the fact the program is running in Admin mode
f) Looking at the logs in bootloader, it appears that I might not have formatted anything from ext4 to 3, everything I select in the cmod bootmenu returns .E:Error in /system/... , (Result: Invalid arguement) , Done..
So at the moment I think I need to acheive one of the following:
1) Find a file that allows me to write any useful data to /system like a recovery or some of those bootmenu files that passes the signature verification
2) Find a way to troubleshoot RSDLite so I can actually flash .sbf and get out of this hellhole
Many regards!
Alexis
If your custom recovery is not working, then you cannot do anything other than flash an sbf(nothing except data and cache wipe can be done via stock recovery): this is due to the locked boot loader(recoveries cannot be simply flashed from the stock recovery as you're trying to do)
Sent from my MB526 using Tapatalk 2
Success (ish)!
Yes I swapped to a different machine and then upgraded the version of RSD Lite installed on it from 4.7 to 6.1.5
[URL="http://forum.gsmhosting.com/vbb/f166/rsdlite-6-0-mtk-patch20-rsd-lite-6-0-a-1545012/index2.html#post8988239"]http://forum.gsmhosting.com/vbb/f166/rsdlite-6-0-mtk-patch20-rsd-lite-6-0-a-1545012/index2.html#post8988239
And flashed the 'lower' of the two .sbf's from the links on this forum for the British variant. After a DEA1 error (Phone is dead, code corrupt and all the bad things) I managed to flash the file.
As of yet I've not managed to get out of the bootloop but I've not carried out the requisite steps as mentioned in the "So you think you've bricked your Defy/Defy+" thread.
Lessons learned:
1) Motorola drivers and RSD Lite are pennickety, you will probably need to mix them up in order to get them to behave properly
2) If all else fails, use a different computer
3) You will probably need to flash over and over, while making every effort to not muck them up. Be aware the efuse system only has limited uses before it's useless though...
My saga continues, from no USB support hopefully to a fully working device again
In the end switching PC then doing the factory reset from moto recovery let the phone boot, all standard but the dodgy USB stuff at the first post is what sent me away from the right track.
Very good friends. I have a motorola defy MB525 bricked. not start. when I connect to PC, LED lights in white and does not recognize me from zero to flash firmware with RSD Lite (I hope you can give me some solution.
note: buy another battery thinking it was the battery but does not work. nor I can enter bootloader mode.
charge the battery in another defy or external charger, then try again RSD
help
snmatias said:
charge the battery in another defy or external charger, then try again RSD
Click to expand...
Click to collapse
use a motorola defy+ firmware and now I can not go down to froyo 2.2 any idea to go back?
If you used too high version of original SBF, it may be impossible to downgrade. Compare your SBF version with list from this post: http://forum.xda-developers.com/showpost.php?p=11588065&postcount=1 .
thrackanomir said:
If you used too high version of original SBF, it may be impossible to downgrade. Compare your SBF version with list from this post: http://forum.xda-developers.com/showpost.php?p=11588065&postcount=1 .
Click to expand...
Click to collapse
my device is a motorola defy and put a firmware defy motorlola not exactly what I had my defy time as it makes you install cyanogenmod 7. I've tried many original SBF and are stock and some just turns the screen on the logo then automatically enters bootloader mode but not always start stays in bootloader mode.
this was the last to use:
DEFYPLUS_U3_4.5.1-134_DFP-231_CEE_ROOTED_No_Signed.sbf
which I use to work then again my motorola defy?
this puts me in the bootloader:
Bootloader
09.10
Err:A5,69,35,00,27
Batery OK
OK to Program
Connect USB
Data Cable
thanks in advance for the help.
Does flashing dfp 231 give bl error or blank screen?
If so then your defy is unfixable
Sent from my MB526 using Tapatalk
thekguy said:
Don't use stock now, is dfp 231 sending you to bl error?
Sent from my MB526 using Tapatalk
Click to expand...
Click to collapse
explain better, I understand nothing.
thekguy said:
Does flashing dfp 231 give bl error or blank screen?
If so then your defy is unfixable
Sent from my MB526 using Tapatalk
Click to expand...
Click to collapse
my motorola defy only lights on the M logo and freezes there then putting me back to bootloader the following:
Bootloader
09.10
Err:A5,69,35,00,27
Batery OK
OK to Program
Connect USB
Data Cable
thanks in advance for the help.
lildark7 said:
my motorola defy only lights on the M logo and freezes there then putting me back to bootloader the following:
Bootloader
09.10
Err:A5,69,35,00,27
Batery OK
OK to Program
Connect USB
Data Cable
thanks in advance for the help.
Click to expand...
Click to collapse
try this
http://forum.xda-developers.com/showthread.php?t=1595013
atulclassic said:
try this
http://forum.xda-developers.com/showthread.php?t=1595013
Click to expand...
Click to collapse
as I do the wipe?
I had exact same error as you today, and had to reflash DFP-231 more than one time, but in the end it worked.
i followed instructions from here:
http://forum.xda-developers.com/showthread.php?t=1542956
so, using RSD Lite version 6.1.5 i flashed DEFYPLUS_U3_4.5.1-134_DFP-231 (when it tries to reboot i get the same error as you, but i continue process and go ahead and flash the second ROOTED sbf)
http://sbf.droid-developers.org/umt..._USAJRDNGIBRRTCEE_P022_A022_Service1FF.sbf.gz
then i flashed same version firmware as above but ROOTED from this link ..
http://www.mediafire.com/?76z12j1at3etf4j
if stuck in bootloop Motorola-logo after flashing ROOTED SBF, just follow "stuck in bootloop advice" in first post here:
http://forum.xda-developers.com/showthread.php?t=1618718
so basically i did ..
1. flash SBF with RSD Lite
2. got strange error message: "Bootloader 09.10 Err:A5,69,35,00,27 Batery OK OK to Program Connect USB"
3. flash ROOTED SBF with RSD Lite
4. stuck in motorola-logo bootloop
5. take out battery
6. hold power button and VOL+ pressed when putting battery back to enter "stock android boot menu"
7. restore factorysettings + wipe cache
8. boot notmal into "horrible motoblur"..
9. install SndInitDefy_2.3.apk
10. install defy_twrp_recovery.2.3.6.0.zip
11. install update-recovery.zip (from quarx kit kat thread)
12. i installed cm-11-20140326-NIGHTLY-mb526.zip ( http://forum.xda-developers.com/showthread.php?t=2515036 )
13. SUCCESFUL REBOOT !
Seems direct to CM11 is ok nowdays http://forum.xda-developers.com/showpost.php?p=51101948&postcount=731
Useful threas if u get stuck with other things during the process:
http://forum.xda-developers.com/showthread.php?t=1828639
http://forum.xda-developers.com/showthread.php?t=2568325
slstr said:
I had exact same error as you today, and had to reflash DFP-231 more than one time, but in the end it worked.
i followed instructions from here:
http://forum.xda-developers.com/showthread.php?t=1542956
so, using RSD Lite version 6.1.5 i flashed DEFYPLUS_U3_4.5.1-134_DFP-231 (when it tries to reboot i get the same error as you, but i continue process and go ahead and flash the second ROOTED sbf)
http://sbf.droid-developers.org/umt..._USAJRDNGIBRRTCEE_P022_A022_Service1FF.sbf.gz
then i flashed same version firmware as above but ROOTED from this link ..
http://www.mediafire.com/?76z12j1at3etf4j
if stuck in bootloop Motorola-logo after flashing ROOTED SBF, just follow "stuck in bootloop advice" in first post here:
http://forum.xda-developers.com/showthread.php?t=1618718
so basically i did ..
1. flash SBF with RSD Lite
2. got strange error message: "Bootloader 09.10 Err:A5,69,35,00,27 Batery OK OK to Program Connect USB"
3. flash ROOTED SBF with RSD Lite
4. stuck in motorola-logo bootloop
5. take out battery
6. hold power button and VOL+ pressed when putting battery back to enter "stock android boot menu"
7. restore factorysettings + wipe cache
8. boot notmal into "horrible motoblur"..
9. install SndInitDefy_2.3.apk
10. install defy_twrp_recovery.2.3.6.0.zip
11. install update-recovery.zip (from quarx kit kat thread)
12. i installed cm-11-20140326-NIGHTLY-mb526.zip ( http://forum.xda-developers.com/showthread.php?t=2515036 )
13. SUCCESFUL REBOOT !
Seems direct to CM11 is ok nowdays http://forum.xda-developers.com/showpost.php?p=51101948&postcount=731
Useful threas if u get stuck with other things during the process:
http://forum.xda-developers.com/showthread.php?t=1828639
http://forum.xda-developers.com/showthread.php?t=2568325
Click to expand...
Click to collapse
thanks for the help served me.
by wilderness as installed CM11? I did the wipes, then install the rom and Gapps but then says setup.service first start is stoped. how can I fix that?
lildark7 said:
thanks for the help served me.
by wilderness as installed CM11? I did the wipes, then install the rom and Gapps but then says setup.service first start is stoped. how can I fix that?
Click to expand...
Click to collapse
First boot without gapps and configure phone, then re-boot into twrp and install gapps. Many people use minimal gapps (by banks ?..) because of defy low memory specs..
you find link to BANKS' minimal gapps in Quarx's CM11 kitakat thread, first post i think. or just use search.
best of luck!