[Q] HELP! E:Error in/system/bootmenu/script/recovery.sh HELP ! - Defy Q&A, Help & Troubleshooting

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...

Related

[Q] Help me to unbrick my HTC legend

Hi Everybody,
I am a newbie, i was trying to install aliba's gingerbeard rom via rom manager, but i dont know what happenend and just my device stopped working, and hanging on cyanogenmod symbol,
Pls guide me to unbrick, i have read some threads in our XDA itself, i am not so clear from where to start to unbrick,
and i placed some roms in sdcard/update.zip via card reader and used the recovery screen (i knew that recovery is not clockwork mod) but the error is
E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0)
and finally after retry 10 it is showing
E: Can't find /sdcard/update.zip
Installation aborted.
Pls help me to sort out this,
Thanks in advance
This should be in general (I wish I was a moderator, I'd do it myself)
Get clockworkMOD recovery (look for FakeFlash), and flash a STABLE ROM
Hi,
Thanks for your reply,
before installing Aliba's Unstable rom i made a nandroid backup,
Now my legend is booting on phone's recovery where i could not find to restore my nandroid backup,
Already bricked phone, can you please guide me how to get clockwork mod recovery on it,
as i told i am newbie, dont know where to start and how to get clockwork mod recovery
Thanks
FakeFlash. Search. All the info is here.
Hi, Grammarfreak
I tried fake flash, unfortunately no use,
i downloaded clockworkmod recovery and kept in my root of sd card as update.zip
and in the recovery screen i click Apply sdcard: update.zip,
Again same problem,
E: Cant mount /dev/block/mmcblk0p1(or /dev/block/mmcblk0)
No such file or directory
E: Cant find /sdcard/update.zip,
Installation aborted
Please note whenever i go to recovery screen i can see below in yellow letters
E: Cant open / cache / recovery/command
I feel may be problem with my sdcard?
Oh Nooooooooo, i tried 3 different cards, all the cards same error
E: Cant open/ cache / recovery /command
chandramohan1986 said:
...
E: Cant open / cache / recovery/command
I feel may be problem with my sdcard?
...
Click to expand...
Click to collapse
I see the same errors when I go into recovery, but I can still launch the fake flash version of recovery. Make sure the update.zip is the correct version.
Recovery is failing to mount your SD card. I'm not sure what the issue is
Did you try USB Unbrick?
year!
http://www.megaupload.com/?d=RTEY0Q97
get that adb.zip
then you should get some recovery files. Hmmm, how to upload??
pull recovery files to the "files" folder.
just run:
adb push files /
adb shell busybox --install /sbin
adb shell nohup /sbin/recovery &
you could get into recovery and flash rom again.
try searching on youtube
Put the Clockwork Mod update.zip and your backup or another ROM (as zip file) on your SD Card. Then press Volume down + Power Button. Afterwards select Recovery and wait until you see the red triangle. When you see the red triangle press Volume up + Power and wait until the Recovery screen appears. There you select Apply update.zip and your phone should boot into Clockwork Mod Recovery. From there you can flash a new ROM or restore your NANDROID Backup.
heres another way... go download this http://www.megaupload.com/?d=XBAOCSWZ
and find testimage.zip in it. Put it on your phone's sdcard renaming it to LEGEIMG.zip
off the phone and go to boot loader and start back from unrooted eclair...
the link above is form got it form this post http://forum.xda-developers.com/showthread.php?t=894465
but anyway... since you like e2 recovery so much... you did not do a factory reset... go do that and the loop should go away....
@spiritusrector
THANKS SOO MUCH lol...you just saved me 35 bucks
answer
go on youtube and search for androidreviews123....he has a guide on how to unbrick
unbrick
heres the link
http://www.youtube.com/watch?v=lVmH6l0xssA

[Q] a problem withe recovery "ERROR: ERROR: Cannot read ramdisk image"

Hello,
I am running android 2.3.7 [typhone v3.6.9- magldr]. I wanted to upgrade my rom, so I got into magldr and then to recovery, but when I choose "ad recovery" I get an error massage in red "ERROR: ERROR: Cannot read ramdisk image "
plese help ...
How can I solve this problem ?
thank's
Reflash recovery and then see it it's reproduces or not.
If you have do a task29,you have to reflash MAGLDR and the recovery who is needed for this ROM.Task29 delete MAGLDR and Recovery.
Maybe you need reflash your device recovery.
You really don't have to task29 your device.
Just download HD2 Toolbox, connect your HD2 to your PC and hit update in the left corner.
Thats it

Help Please! Image signature verify fail

To install to clockwork recovery manually I replaced the recovery.img file but when i restarted my phone it says:
Image signature verify fail
Your boot/recovery image may have an incorrect signature.
Please update your image to a signature official one
you can remove battery for power down.
muz786 said:
To install to clockwork recovery manually I replaced the recovery.img file but when i restarted my phone it says:
Image signature verify fail
Your boot/recovery image may have an incorrect signature.
Please update your image to a signature official one
you can remove battery for power down.
Click to expand...
Click to collapse
You probably are not rooted. Did you root via superoneclick?
Hmmm. Go into recovery and install a custom rom then flash
Make sure you do not have a stock rom on your phone.
If you flashed B528 (I think) Official ROM, you might have locked bootloader... not sure...
You can flash an unlocked bootloader, it's in the android development forum. I'm not sure if this is the fix though.
http://forum.xda-developers.com/showthread.php?t=1457490
OP, have you got u8800+?
Sent from my U8800
Same here
I have ideos x5 pro and i replaced the img file to this and i have the same prob.
I cant even recovery bot my phone. Always tha same message. Plz help
Please help .. any update for this issue
Kindly help me as i m facing the same problem in my phone ( huawei g510 )
the same message still appearing and i can NOT log into recovery menu or anything else
only tow thing to see
Pink screen instead of the recovery menu
or " Image signature verify fail "
PLZZZZZZZZ HELP
:crying::crying:
Flash rom.
Put the official rom in sd card and use the button combo on your device to flash.
I do not have u8800+, i only have u8860, they are quite similar and i believe this would work

Defy Mini failed flashing process

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...

[Q] Need to unbrick Defy+ - Strange problems

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.

Categories

Resources