Database Users

[Q] Can i repair cwm recovery?

Hello,
Ive magldr cwm recovery installed, and a magldr NAND rom.
Yesterday i tried to play with rom manager.
I didnt know it only work with clk, and i made the mistake to update recovery throug rom manager.
So it broke my MAGLDR cwm recovery :-(
My question is : can i repair my MAGLDR cwm recovery without wiping my rom?(because i didnt recently do a nandroid backup)
Thx for your help.

Unfortunately, no you can't.
The only way to fix your cwm is to re install cwm. And that will wipe off your rom, data and everything else.
Edit:
wow, i never knew about that !

denseye said:
Hello,
Ive magldr cwm recovery installed, and a magldr NAND rom.
Yesterday i tried to play with rom manager.
I didnt know it only work with clk, and i made the mistake to update recovery throug rom manager.
So it broke my MAGLDR cwm recovery :-(
My question is : can i repair my MAGLDR cwm recovery without wiping my rom?(because i didnt recently do a nandroid backup)
Thx for your help.
Click to expand...
Click to collapse
I think you can do it.
If your phone still don't boot, reflash your Rom without wipe maybe can help
Sent from my GT-I9100 using xda premium

get a version of cwm that loads from sd card,
put it on your sd
from magldr choose 'ad sd'
flash a new cwm.zip using 'instal zip from sd' option.

samsamuel said:
get a version of cwm that loads from sd card,
Click to expand...
Click to collapse
where can I find one ???
samsamuel said:
put it on your sd
from magldr choose 'ad sd'
flash a new cwm.zip using 'instal zip from sd' option.
Click to expand...
Click to collapse
won't it wipe my rom data ???

We are just writing an image to the already created recovery partition,, not using daf to write a partition layout. It's just like flashing a rom, but only the recovery partition is affected.
In the android nand section, titled something like "clockworkrecovery, nand,SD, ver 5.0.2 yes/no stable" or something, (currently top post
Get both
recovery_5.0.2.6_leo_sd.zip (3.93 MB, 1153 views)
and
recovery_5.0.2.6_leo_CWR.zip (4.25 MB, 3415 views)
Extract and copy the SD card ver onto SD card (copy the two files to SD, done)
And then copy the whole cwr.zip to SD card too.
Then, into magldr, "ad SD" will boot into the cwm files you placed on SD, and choose instal zip from SD,,, choose zip,, and select the cwm.zip you also placed on SD.
This will write the cwm image into the recovery partition without reflashing the cwm partition layout, so nothing lost.

it worked
thank you for your help and your very precise explanations

welcome. Its worth leaving those two files on the SD in case recovery fails for whatever reason, since you can backup and restore just like in nand cwm recovery.

samsamuel said:
welcome. Its worth leaving those two files on the SD in case recovery fails for whatever reason, since you can backup and restore just like in nand cwm recovery.
Click to expand...
Click to collapse
yes indeed
I will keep those to files on my sdcard

Many thanks to samsamuel !
i could not get into the CWM menu, but with your help i was able to flash to a new custom rom.

In attempting this, I get the following error:
Writing recovery partition...
assert failed: write_raw_image("/tmp/recovery.img", "recovery")
E:Error in /sdcard/recovery_5.0.2.6_leo_CWR.zip
(Status 7)
Installation aborted.
Any help?

Perhaps the recovery partition is too small? Perhaps you don't have a recovery partition? Check the flash.cfg you last used for partition sizes you used.
Alternatively, use the SD cwm to make a backup and do a fresh flash.

samsamuel said:
Perhaps the recovery partition is too small? Perhaps you don't have a recovery partition? Check the flash.cfg you last used for partition sizes you used.
Alternatively, use the SD cwm to make a backup and do a fresh flash.
Click to expand...
Click to collapse
I have the same error as the person above you. Do you recommend using the SD cwm to flash Recovery_150M_system_44M_cache[v3.0.2.4].zip? I cannot recall what flash.cfg I used.
I think I may have no recovery partition if I recall correctly. I digged through my old files I think this was the flash.cfg I usd:
misc ya 1M
recovery rrecov|ro|nospr filesize recovery-raw.img
boot yboot|ro 5M
system ya 150M
cache ya 44M
userdata ya|asize|hr allsize
Click to expand...
Click to collapse

I had the same error. I made a copy of the recovery_5.0.2.6_leo_CWR.zip and copied my original CWMRecovery's recovery-raw.img on top of the new zip's recovery_leo.img file. That got me past the error and AD recovery works now.

Thanks for that just fixing mine as well now

does not work for me, boot AD SD = ssSD Kernel open failed, no idea.
But manage to reinstall the recovery without wipe with Windows version software - HD2 Toolkit, connect USB cable to PC, while phone staying in Andriod, run Toolkit > MAGLDR update recovery > click "update" and done.

gl7 said:
does not work for me, boot AD SD = ssSD Kernel open failed, no idea.
But manage to reinstall the recovery without wipe with Windows version software - HD2 Toolkit, connect USB cable to PC, while phone staying in Andriod, run Toolkit > MAGLDR update recovery > click "update" and done.
Click to expand...
Click to collapse
Same problem here??? Why?

I have the same problem. Add sd dir does not work. I only get back in the menu.
Using the toolkit and update the recovery shows this fault.
Look attachment.
I want to flash the new ics nexus rom without loosing data. Normal i would flash in ad recovery and make a update. Poorly i tried this Tom manager and now my recovery is broken.
Anyone can help? Sry for my german-english.

Wow, I didn't know that

Your radio links are blank
samsamuel said:
get a version of cwm that loads from sd card,
put it on your sd
from magldr choose 'ad sd'
flash a new cwm.zip using 'instal zip from sd' option.
Click to expand...
Click to collapse
Kindly check on the status of your radio links as the seem to lead to a dead end.

[Q] Please help me, error while flashing

Hi guys, I hope you can help me.
I have just rooted + flashed my motorola defy plus for the first time (on any device for that matter)
I installed 2nd init, version 0.6.... or something.
Put a rom, kernel and google apps on my sd-card
Then I turned usb-debugging off and rebooted my phone.
Now I can get into bootmenu, and this is what I do:
1) go to recovery
2) select custom recovery
3) then it says: Clockworkmod Recovery v2.5.1.8
E: Can't open /tmp/recovery.log
4) I then select wipe data/factory reset
5) then it says this: Formatting DATA
Formatting CACHE
FORMATTING SDEXT
No app2sd partition found. Skipping format of /sd-ext
Formatting SDCARD:/.android_secure
Data wipe complete
E: Can't open /tmp/recovery.log
6) After that i select install zip from sdcard
7) then I select choose zip from sdcard
8) then I select the zip file containing the rom
9) And it says: Finding update package
Opening update package
Installing update
E: Can't make /tmp/update_binary
Installation aborted
Now I can't go any further and can't use my phone at all
I hope u guys can help me, and that I haven't F*ed up my phone

I have a quite similar problem.
On a defy+,rooted 2ndinit installed, backup-ed first, download the new quarx05/03 ICS, put the zip on sd, wipe data, reboot and start to install ics, but the message was
''Finding update package
Installing update
E: Can't make /tmp/update_binary
Installation aborted"
Thanks to the previously backup I can use may phone as usual.
What I have done wrong with de ICS installation?
Thanks
PS. Sorry for probable a dummie question:What we have to do with md5 zip near the CM9 Jordan.zip?

A little help please about the subject?
Thank you

ics
The entire process
ClockworkMode v2.5.1.8
Wipping data...
Formatting DATA...
Formatting CACHE...
Formatting SDEXT..
No app2sd partition found.Skipping format of /sd-ext.
Formatting SDCARD: /.android_secure...
Data wipe complete
E: Can't open /tmp/recovery.log...
Installing: SDCard:download/CM9-ICS-MR1-120305-jordan.zip
Finding update package
Opening update package
Installing update
E: Can't make /tmp/update_binary
Installation aborted
if try Wipe Dalvik Cache:
E: Can't mount /dev/block/mmcblk0p2
(No such file or directory)
I guess that this is a simple and many times occured error, since nobody has any answer....

Does you disabled the usb debugging before flashing?

Yes I do, but nothing change,
Thanks

if I'm not mistaken the last release of 2nd init is not compatible with defy. Try to check this on the development forum. I hope I have been of help.

I'd tried with both 1.0.7 latest and 0.6.1.
With latest, the phone is blocked.
Thanks

I had used this. Try with it
P.S. sorry for my bad english.

Tried, the same errors,
Thanks

I don't know. Sorry. By the time i had used that.

I think you need to go to stable recovery after you wipe your data from custom recovery
Sent from my MB525 using xda premium

I think you need to go to stable recovery after you wipe your data from custom recovery
What do you mean by "stable recovery"? You talk about version 0.6. of 2nd init or something else?
Can you show a step-by step procedure?
Thank you in advance.
However, which is the procedure to un-root a defy+ and to have it with the original, fresh system?

I had flash a new SBF, root with Unlockroot v2.3, anything else doesn't work, 2ndinit v2.0 stable, wipe data/cache/dalvik (same errors), try to install cm9-ics, the same error "Can't make /tmp/update_binary"
What the f.....?

cretu22 said:
I had flash a new SBF, root with Unlockroot v2.3, anything else doesn't work, 2ndinit v2.0 stable, wipe data/cache/dalvik (same errors), try to install cm9-ics, the same error "Can't make /tmp/update_binary"
What the f.....?
Click to expand...
Click to collapse
Hi, I have exactly the same problem.. Trying to find a solution but is quite difficult. First I thought it has something to do with the partitioning, as stated in THIS topic. But, in THIS topic, people say that partitioning the SD card is not necessary at all..

@Cretu22: Yes stable recovery is CWM 0.6
Don't install stable recovery! I too faced this issue when I flashed using stable recovery. In snd init install Latest recovery and then try flashing your ROM. That should work..

I did choose the stable version indeed 0.6.7.
Now i did uninstall it and installed the latest 1.0.7, but when I reboot my phone it won't get into the boot menu but just boots into android. Tried it several times, but only with 0.6.7 I seem to be able to get in the menu

fokkeh said:
I did choose the stable version indeed 0.6.7.
Now i did uninstall it and installed the latest 1.0.7, but when I reboot my phone it won't get into the boot menu but just boots into android. Tried it several times, but only with 0.6.7 I seem to be able to get in the menu
Click to expand...
Click to collapse
Okay!! I hope you were pressing the volume down button when the blue LED came?? Try doing this again all over.. I mean reinstall 2nd init and then latest recovery.. I remember doing this once(instal latest recovery after I installed stable recovery)..

pranks1989 said:
Okay!! I hope you were pressing the volume down button when the blue LED came?? Try doing this again all over.. I mean reinstall 2nd init and then latest recovery.. I remember doing this once(instal latest recovery after I installed stable recovery)..
Click to expand...
Click to collapse
Yes, its working Pressing the volume down button was not necessary with 0.6.7, that was what went wrong. Now the zips installed like a charm

i know the answer and is very simple
the problem is that you cannot create that specific folder.... because it already exist, cmp (connected music player) creates it, just delete it from SD and done!

[Q] error mounting system, soft bricked. please help asap..

Hi guys!
I did a backup of stock rom using cwm. then restored a backup of cm7. on restoring, it gave me this error:
ERROR MOUNTING /SYSTEM!
RESTORE FAILED.
so i rebooted my phone. now it get soft bricked. i can open recovery. in stock recovery, i can see all the recovery options but at the bottom its written
APPLING MUTI-CSC
RFS- FAILED TO MOUNT /SYSTEM (INVALID ARGUMENT)
yes.. spellings are written wrong on recovery.
if i goto cwm and restore nandroid backup of stock recovery, its giving error that
ERROR MOUNTING /SYSTEM
RESTORE FAILED
i tried formatting system via cwm, but it gave me error that
ERROR MOUNTING /SYSTEM
SKIPPING FORMAT..
DONE.
i tried flashing other kernels via cwm but it didnt help. also i cannot use odin (it takes upto 1-2 hrs trying for odin to detect my phone)
i am going to flash cm7.. i dont know if it will help or not..
pleaseeeeeeeeeeee help..
UPDATE: I think dat it will help if anyone could give a backup of /system dir in form of flashable zip (with commands like mkdir etc to remake system dir),, then it would be gr8..

If you a restoring a nandriod backup of cm7 you need to flash percys kernel first (I presume you were using that kernel when you were using cm7 as that is required) then reboot to recovery wipe system data cache then you can restore your nandriod backup

Change kernel to stock using hell fusion and format system and mount
Gửi từ Galaxy Y bằng cách sử dụng tia X truyền từ mặt trời!

If you have a nandroid backup of percy's cm7 then try flash stock rom via odin. Then go to stock recovery and flash percy's CyanogenMod7#2 kernel. Reboot phone and go to recovery again... You will must see CWM recovery and then try restore your nandroid backup.
Sorry for bad English

1. Flash percy's kernel.
2. then reboot recovery
3. format system. format data. format cache. mount all of them (system may not mount)
4. flash cm7 rom
5. reboot system.. (still bricked)
6. take out battery and re insert
boot into cwm, u will see many errors
7. flash cm rom again (3 times) (see steps3&4 for info)
8. reboot (still bricked)
9. boot into cwm. now all errors gone. format all and mount all of them (system will mount)
9. flash hyperion rom
10. fix permissions
11. reboot system now
12. fixed!

techmentry said:
1. Flash percy's kernel.
2. then reboot recovery
3. format system. format data. format cache. mount all of them (system may not mount)
4. flash cm7 rom
5. reboot system.. (still bricked)
6. take out battery and re insert
boot into cwm, u will see many errors
7. flash cm rom again (3 times) (see steps3&4 for info)
8. reboot (still bricked)
9. boot into cwm. now all errors gone. format all and mount all of them (system will mount)
9. flash hyperion rom
10. fix permissions
11. reboot system now
12. fixed!
Click to expand...
Click to collapse
thanks!!!!! that worked

Say, i come from another ROM.
I was using resurrection remix kitkat the final version and i actually used the CM theme chooser to change some styles and boot animations.
I am aware it can cause system crashes but the last time it crashed, it gave me the exact same errors with a frozen s III logo. Refused to boot, soft brick with access to both odin mode and cwm recovery of resurrection, unable to mount /sdcard (E
Will this procedure work on my device GTi9300 or should i keep looking for more?
I tried flashing
1) stock rom but connection hangs
2) Stock recovery NANDWRITE fails
3) PIT file but gets stuck on Get pit mapping thingy
4) and occasionally it just freezes at establishing connection
I tried pushing the file through abd but it doesn't detect once it reboots to bootloader on fastboot.

MavPinch said:
Say, i come from another ROM.
I was using resurrection remix kitkat the final version and i actually used the CM theme chooser to change some styles and boot animations.
I am aware it can cause system crashes but the last time it crashed, it gave me the exact same errors with a frozen s III logo. Refused to boot, soft brick with access to both odin mode and cwm recovery of resurrection, unable to mount /sdcard (E
Will this procedure work on my device GTi9300 or should i keep looking for more?
I tried flashing
1) stock rom but connection hangs
2) Stock recovery NANDWRITE fails
3) PIT file but gets stuck on Get pit mapping thingy
4) and occasionally it just freezes at establishing connection
I tried pushing the file through abd but it doesn't detect once it reboots to bootloader on fastboot.
Click to expand...
Click to collapse
Please check where you are posting before you post - this forum is for the galaxy y 5360
As a general rule when restoring backups
1- restore the backup using the same kernel to which the backup was made
2- restore the backup using the same recovery version to which the recovery was made
When flashing stock rom via odin make sure you have the Samsung USB driver installed
Never flash bootloader or pit unless you know what you are doing - they are not needed for typical stock rom flashing
Goto your own phone forum for support on flashing stock rom for your device

marcussmith2626 said:
Please check where you are posting before you post - this forum is for the galaxy y 5360
As a general rule when restoring backups
1- restore the backup using the same kernel to which the backup was made
2- restore the backup using the same recovery version to which the recovery was made
When flashing stock rom via odin make sure you have the Samsung USB driver installed
Never flash bootloader or pit unless you know what you are doing - they are not needed for typical stock rom flashing
Goto your own phone forum for support on flashing stock rom for your device
Click to expand...
Click to collapse
Gotcha. Just poking around here and there because i haven't been able to work it.

techmentry said:
1. Flash percy's kernel.
2. then reboot recovery
3. format system. format data. format cache. mount all of them (system may not mount)
4. flash cm7 rom
5. reboot system.. (still bricked)
6. take out battery and re insert
boot into cwm, u will see many errors
7. flash cm rom again (3 times) (see steps3&4 for info)
8. reboot (still bricked)
9. boot into cwm. now all errors gone. format all and mount all of them (system will mount)
9. flash hyperion rom
10. fix permissions
11. reboot system now
12. fixed!
Click to expand...
Click to collapse
Now nothing formats or mounts, any ideas why?

Fota TWRP 2.8.6.0 with f2fs recovery for amami by @o-l-a-v

@o-l-a-v have made latest twrp 2.8.6.0 recovery with f2fs for flashing on fota partition. I publish it here bcs there is no development behind it. It works with latest cm12 nightlies
f2fs is untested report pls
All thanks to @o-l-a-v
Install through fastboot:
fastboot flash recovery
https://mega.co.nz/#!3gRwGZiK!sXMsMx1GGwUVkTCCsr8ntZekCE-o-hB4DDp6wlhVQqA
New version again
You don't need any app for flashing, use fastboot, see above
be careful if you write: fastboot flash boot you won't be able to boot

Cool, what ROMs did you test this on ?

OmarEinea said:
Cool, what ROMs did you test this on ?
Click to expand...
Click to collapse
i´m on liquid, but it works on every no stock rom,i used previous version on all your roms
i have made it bcs @championswimmer has not amami support for twrp in his recovery manager only for philz and i prefer twrp

funiewski said:
I have made latest twrp 2.8.0.1 recovery for flashing on fota partition. I publish it here bcs there is no development behind it.
Install through fastboot:
fastboot flash recovery fotaZ1cTWRP2.8.0.1.img
https://dl.dropboxusercontent.com/u/17658154/fotaZ1cTWRP2.8.0.1.img
Click to expand...
Click to collapse
How does this work? I wasn't aware that the amami had a recovery partition... How is it accessed after installation?

Rekoil said:
How does this work? I wasn't aware that the amami had a recovery partition... How is it accessed after installation?
Click to expand...
Click to collapse
That was TWRP developer @Dees_Troy who found the possibility of using fota partition on xperia devices for recovery flashing. Here: http://forum.xda-developers.com/showpost.php?p=38640389&postcount=2
You access it in usual way, Sony logo+led light press volume+. Advantage of it is that recovery persist new kernel or rom flashing, aosp and cm roms and kernels use different recoverys, a backup made with one recovery is maybe not compatible with new recovery you have just flashed. If you are flashoholic like me it is quite a pain. With recovery on fota partition it is no longer a problem. @championswimmer has made a small paid app for flashing recovery on fota, but as i wrote before it does not support twrp for amami only philz and you can flash it easily with fastboot. This works only on aosp and cm roms, if you want to overwrite recovery on fota you can either use flashtool and flash only fota, uncheck all other boxes or you can use recovery manager i mentioned earlier.

funiewski said:
Advantage of it is that recovery persist new kernel or rom flashing, aosp and cm roms and kernels use different recoverys, a backup made with one recovery is maybe not compatible with new recovery you have just flashed.
Click to expand...
Click to collapse
Nice, expirienced same problems.
Thanx @funiewski

Thanks, finally we can install a persistent recovery after flashing another boot.img. So is this a usual recovery.img or has it a special format for xperia devices?

CoolDevelopment said:
Thanks, finally we can install a persistent recovery after flashing another boot.img. So is this a usual recovery.img or has it a special format for xperia devices?
Click to expand...
Click to collapse
As you know i´m far from developer, you can read about twrp for xperia devices here: http://teamw.in/project/twrp2/144
z1c is not officially supported by teamwin, there is philz touch fota recovery images for xperia devices made by @championswimmer: http://forum.xda-developers.com/crossdevice-dev/sony/recovery-philz-touch-fotakernel-images-t2826333, downloads here:http://files.championswimmer.in/?developer=championswimmer&folder=recovery/philz
what i have done: i used teamwin recovery image for sirius, unpacked it with this tool: http://forum.xda-developers.com/showthread.php?t=2073775 (this is simple enough even for me),edited default.prop with notepad++ (model,device, fingerprint, density and so on) , changed res folder to one from twrp for z1c ( i think i use one from @[NUT] ) than repacked it.
If you can get it to work with your f2fs patch it would be great bcs it´s way over my horizon

funiewski said:
As you know i´m far from developer, you can read about twrp for xperia devices here: http://teamw.in/project/twrp2/144
z1c is not officially supported by teamwin, there is philz touch fota recovery images for xperia devices made by @championswimmer: http://forum.xda-developers.com/crossdevice-dev/sony/recovery-philz-touch-fotakernel-images-t2826333, downloads here:http://files.championswimmer.in/?developer=championswimmer&folder=recovery/philz
what i have done: i used teamwin recovery image for sirius, unpacked it with this tool: http://forum.xda-developers.com/showthread.php?t=2073775 (this is simple enough even for me),edited default.prop with notepad++ (model,device, fingerprint, density and so on) , changed res folder to one from twrp for z1c ( i think i use one from @[NUT] ) than repacked it.
If you can get it to work with your f2fs patch it would be great bcs it´s way over my horizon
Click to expand...
Click to collapse
Seems it still (not surprisingly) requires interaction from the boot image to load the recovery from the FOTA partition, making it pretty useless as you can just stick it in the boot partition in that case. Pity, this is about the only irritating thing about Xperia devices, no recovery partition.

How does it work that the phone enters recovery from FOTA partition and not kernels internal recovery?

Rekoil said:
Seems it still (not surprisingly) requires interaction from the boot image to load the recovery from the FOTA partition, making it pretty useless as you can just stick it in the boot partition in that case. Pity, this is about the only irritating thing about Xperia devices, no recovery partition.
Click to expand...
Click to collapse
as i wrote the difference is the recovery on fota partition persist flashing of roms and kernels regardless which recovery they use, thats the point for me

funiewski said:
as i wrote the difference is the recovery on fota partition persist flashing of roms and kernels regardless which recovery they use, thats the point for me
Click to expand...
Click to collapse
Yeah but it is still executing the kernel from the boot partition, so if you **** up boot partition you'll **** up recovery, so it's not much of a recovery. It just loads data from the FOTA partition. A true recovery has its own kernel.

On the TWRP webpage the xperia z2 is "officially" supported. How does this work? recovery?

paulle said:
On the TWRP webpage the xperia z2 is "officially" supported. How does this work? recovery?
Click to expand...
Click to collapse
Exactly in same way as this one.

@funiewski can i post here working boot.img for stock ROM (UB)?
with this boot.img recovery is working very well

russel5 said:
@funiewski can i post here working boot.img for stock ROM (UB)?
with this boot.img recovery is working very well
Click to expand...
Click to collapse
Do you mean fota recovery is working with stock kernel?I thought it was not possible, of course you can post it here

funiewski said:
Do you mean fota recovery is working with stock kernel?I thought it was not possible, of course you can post it here
Click to expand...
Click to collapse
Not stock, but for stock ROM with stock ramdisk (except RIC is disable)
This boot NOT have any recovery, only work with FOTA recovery
View attachment boot.zip

Hi! Thanks for this
But there seems to be several problems with it. I can boot it, but I'm unable to mount external sd-card, and backup fails. I have not had balls to try anything other than that.
Does the recovery actually work as it should on your phone?
(I'm on CM11 nightly from 21.10.. No custom kernel)

o-l-a-v said:
Hi! Thanks for this
But there seems to be several problems with it. I can boot it, but I'm unable to mount external sd-card, and backup fails. I have not had balls to try anything other than that.
Does the recovery actually work as it should on your phone?
(I'm on CM11 nightly from 21.10.. No custom kernel)
Click to expand...
Click to collapse
Are you on "stock " cm kernel? Bcs I'm on pimped kernel with liquid rom which is cm based and have no problems with ext-sd card or with backup, and it´s same for me with carbon which is aosp

funiewski said:
Are you on "stock " cm kernel? Bcs I'm on pimped kernel with liquid rom which is cm based and have no problems with ext-sd card or with backup, and it´s same for me with carbon which is aosp
Click to expand...
Click to collapse
Yes, stock CM kernel. Hm. I'll try again. Eventually try that custom kernel.

[Q] Small problem when installing SDMerge on LGE400

Small problem, no actually a big one when installing Cyanoid SDMerge 15.4 on my LGE400.
I successfully installed Cyanoid Standard 15.4 and am trying to upgrade to SDMerge using the steps found on the Google site of Cyanoid. I have these three files on my external SD: SDMergE400_Step1.zip SDMergE400_Step2.zip cyanoid15.4sdmerge.zip, first two from given link and last one from ROM Manager.
First I actually found that _ExternalSD on the phone is actually a map and not my SD Card, as I put in the SD Card into the computer I was not able to see the cyanoid154sdmerge.zip I put on it using the phone's file explorer. When storing the other two files on my SD Card using my computer, I could not see them when going to _ExternalSD in my phone's file explorer.
I thought: Let's put those three files in both directories in case it might matter which directory will be chosen by recovery.
Now when I click on install SDMergE400_Step1.zip ; the thing says failed. No idea why, no idea how to solve.
It says: (Not everything is readable)
Updating partition details...
E:Resource type (image) failed to
Installing '/emmc/_ExternalSD/SDMe
Checking for MD5 file...
Skipping MD5 check: no MD5 file fo
assert failed: getprop("ro.product
E:Error executing updater binary in
Error flashing zip '/emmc/_External
So ehm, what do to next?
Thanks in advance.

Does no one have an idea on how to install SDMerge on my E400 given the problems above? I forgot to mention that this package failure did not brick my phone so I am still looking for a way to install SDMerge.
Thanks in advance.

410172 said:
Does no one have an idea on how to install SDMerge on my E400 given the problems above? I forgot to mention that this package failure did not brick my phone so I am still looking for a way to install SDMerge.
Thanks in advance.
Click to expand...
Click to collapse
So first wich recovery are you using?
Anyway re-download the files and download Cyanoid Rom from XDA...
Inviato dal mio LG-E400 con Tapatalk 2

Oh you remind of one more other strange thing: On first boot, back at the stock rom of my LGE400GO, ROM Manager automatically installed CWM recovery. When I restart Cyanoid into recovery, I get to see TeamWin Recovery Project v2.7.0.0. What went wrong? Might it be this recovery that does not allow me to install SDMerge? Is there a way to change recoveries or should I do a total reinstall of Cyanoid?
I found out that it is possible to revert to CWM recovery, yet when I select to do so the phone gets stuck on Flashing.... (ClockWorkMod Recovery)
Used this thread: http://forum.xda-developers.com/showthread.php?t=2405279 to install CWM recovery using the Terminal for Android, it worked. This means that I know run the latest version of CWM recovery. I am going to try the SDMerge installation with this.
It worked. I was able to install step1.zip and step2.zip using CWM recovery. Installed SDMerge after that. Now my phone is rebooting, let's see if it worked. It is booting so I did at least not brick it. Though it is taking a bit long for Cyanoid for start, I think it worked. I will edit this post later this evening if it succeeded. EDIT: It booted. It is still slow, but it booted. This means that I now have Cyanoid 15.4 SDMerge installed.
Thanks.

410172 said:
Oh you remind of one more other strange thing: On first boot, back at the stock rom of my LGE400GO, ROM Manager automatically installed CWM recovery. When I restart Cyanoid into recovery, I get to see TeamWin Recovery Project v2.7.0.0. What went wrong? Might it be this recovery that does not allow me to install SDMerge? Is there a way to change recoveries or should I do a total reinstall of Cyanoid?
I found out that it is possible to revert to CWM recovery, yet when I select to do so the phone gets stuck on Flashing.... (ClockWorkMod Recovery)
Used this thread: http://forum.xda-developers.com/showthread.php?t=2405279 to install CWM recovery using the Terminal for Android, it worked. This means that I know run the latest version of CWM recovery. I am going to try the SDMerge installation with this.
It worked. I was able to install step1.zip and step2.zip using CWM recovery. Installed SDMerge after that. Now my phone is rebooting, let's see if it worked. It is booting so I did at least not brick it. Though it is taking a bit long for Cyanoid for start, I think it worked. I will edit this post later this evening if it succeeded. EDIT: It booted. It is still slow, but it booted. This means that I now have Cyanoid 15.4 SDMerge installed.
Thanks.
Click to expand...
Click to collapse
Unfortunately as i said TWRP is still buggy....Anyway good you solved your problems!!!!
First boot is slow as usual
Inviato dal mio LG-E400 con Tapatalk 2