Hello,
This morning I try to install a Custom ROM so I follow a tutorial on XDA Developer. First, I installed TWRP Recovery with Linux (I have a dual boot computer I use for windows for all). After I formated my device with the tab : Wipe, I delete /dalvik /system /cache and all others. Then, try to install lot of Custom ROM (like POISON v2.2, OmniROM, etc..). And every time, it write : "checking MD5 file ... no MD5 file found" and it reboot TWRP.
Can someone help me ? Sorry for my English speaking, I'm french and I'm not very good in English and on the computer..
Thank you beforehand
Untick the MD5 thing in settings. You don't need it.
Oel said:
Untick the MD5 thing in settings. You don't need it.
Click to expand...
Click to collapse
I don't find where is he tick..
How can I untick him ?
In setting I have only these option:
- Zip signature verification
- Reboot after installation is complete
- Use rm -rf instead of formatting
- Disable free space check before backup
- Skip MD5 generation during backup
- Enable MD5 Verfication of Backup files
- Use 24-hour clock
- Reversed navbar layout
- Prompt to install TWRP app if not installed
- Simulate actions for theme testing
And there are all untick except "Prompt to install TWRP app if not installed" and "Skip MD5 generation during backup"..
Thank you
Related
This is a beta version of Boot Menu Manager v0.3.0~
Note : Version ending with alphabet is considered as beta/test version.
New features/changes:
- CWM 6.0.1.x & CyanogenMod 10.0 as code base.
- Touch button for recovery
- kexec boot support
- auto ramdisk convert (STS-Dev-Team based ROM only)
- advance backup/restore (partition is selectable)
- Change recovery partition mount point for storage.
/sdcard -> /ext (external storage)
/emmc -> /int (internal storage)
- virtual system (add extra 4 system)
specify each system setting in bootmenu.prop.
you can mixed internal/external storage to store partition image.
Todo :
Recovery
- fix installer zip filemanager (for now, use keypad to browse & select)
- add zip install queue
Bootmenu
- ramdisk cache
Bootmenu Manager App
- too many to list.
- priority : Easy Installer & Rebooter
Bugs/Issues :
- sync disk after a backup took long time. fix by optimizing IO scheduler??
If anybody want to help, try optimize /system/etc/bmm/conf/recovery.rc
Installer/Download:
If coming from 0.2.8 & below:
- backup your 2nd-system before begin.
- on first boot, choose setting, system_2, partition setup, activate CDROM.
- then go to recovery & restore your data.
For best result, start from a fresh install ROM. (use ROM not converted by older BMM)
If coming from 0.2.9/0.3.0a:
- move 1st-system /data/media/cache.img to /data/media/virtual/system_1/cache.img
- move 2/3/4/5 system data from /{internal/external storage}/bmm/system_* to /{internal/external storage}/clockworkmod/virtual/system_*
If coming from 0.3.0b & ++
- Just boot to system 1 & run install.bat. No need to backup/reinstall ROM
Install/upgrade method :
ADB push - Please boot to stock system
(APK installer is not done yet)
I'll edit this page as time permits. Please provide feedback for improvement.
Don't re-upload this file. I'll watch the download count to justify priority for further improvement
If you're going to post it on your local forums, blog, etc. please just use xda download link.
This dev thread is abandon.
Development progress is not updated in here anymore.
Download link :
- Download link removed to push everyone to download from Google Play.
Credits
Change logs
[21/11/2012] - 0.3.0.c
Bugs fix
-Instal long zip file name --> error mounting
-Can't switch back to system 1 in recovery.
-Sometime kexec ROM won't boot.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
[26/11/2012] - 0.3.0.d
Bugs fix
-Flash radio firmware --> error mounting
-Fix ROM booting with 2nd-init disable (aka Normal booting).
New
- Re-Implement /data/.recovery_mode file check as trigger to recovery boot.
- Add reboot command (/system/etc/bmm/sbin/bb reboot [ -p | recovery | bootloader | 1 | 2 | 3 | 4 | 5 | 6 ])
- Auto naming system name upon restore/install (read props ro.build.display.id & ro.modversion (prefered))
- Integration with tweakerz app (reboot function only)
Click to expand...
Click to collapse
Click to expand...
Click to collapse
[26/11/2012] - 0.3.0.e
Critical Bugs fix
-Fix re-installation of BMM on system 1.
New
- Removed /data/.recovery_mode file check as trigger to recovery boot
Check unnecessary, it's only working for system 1.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
[3/12/2012] - 0.3.0.f
Bugs fix
-Fix workaround for erased CID devices. (just temporary fix)
-Remove sio as default scheduler for recovery, now is noop
-Remove pattern.sed file. Every logic for STS rom convert now stored in boot.sh
New
- Add overclock menu at boot setting
- includes new overclock module & governor.
Recommended kernel : 3.0.8-gc00ba37 ([email protected]) (Mon Jul 16 11:28:41 CST 2012)
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Mini Q&A
Q : How to restore cdrom partition back to stock
A :
Code:
fastboot flash cdrom cdrom.img (cdrom_signed)
Q : How to uninstall BMM manually
A : boot to system 1
Code:
adb shell "su -c 'mount -o rw,remount /system'"
adb shell "su -c 'rm -r /system/etc/bmm'"
adb shell "su -c 'mv /system/bin/logwrapper.bin /system/bin/logwrapper'"
Thank you Whirleyes love to experiment
Looking good so far
Sent from my DROID RAZR CDMA XT912 using Tapatalk 2
Is this version compatable with d-wiz ROM?
If coming from 0.2.8 & below, backup your 2nd-system before begin.
On first boot, choose setting, system_2, partition setup, activate CDROM.
Then go to recovery & restore your data.
i came from 0.2.8 and seems every thing fine after activate CDROM. when i push recoervy button just boot to main system only, nothing happen, something wrong with me?
mydoom said:
If coming from 0.2.8 & below, backup your 2nd-system before begin.
On first boot, choose setting, system_2, partition setup, activate CDROM.
Then go to recovery & restore your data.
i came from 0.2.8 and seems every thing fine after activate CDROM. when i push recoervy button just boot to main system only, nothing happen, something wrong with me?
Click to expand...
Click to collapse
same here but i have installed this from fresh install.
Thanks!!
I think i will try when apk is ready!
i3enz said:
same here but i have installed this from fresh install.
Click to expand...
Click to collapse
Does it work after 2nd reboot? Any more details?
Some bugs I found :
-Instal long zip file name --> error mounting
-Can't switch back to system 1 in recovery.
-sometime kexec won't boot.
I'll upload 0.3.0.c in few hours
I got it. You need to create cache before go to recovery.
now trying to flash some rom
Brilliant very promising. Glad we can use the EXT.
Will it be able to recover backups from other recovery systems, like 2.7 was able to do?
Sent from my DROID SPYDER using Tapatalk 2
ok it looks like 0.3.0c has ability to create cache itself.
now i'm trying to flash some rom again.
i3enz said:
I got it. You need to create cache before go to recovery.
now trying to flash some rom
Click to expand...
Click to collapse
thanks i got it too.
It should be create cache system1 before revovery section can be work.:good:
BTW. Awsome work to whirleyes
And where is BMM? Have plan to write it?
Sent from my XT910
Thanks whirleyes for your work. Its time for me to come back to your great recovery. One question, anyone tried restoring twrp (safestrap) backup?
Sent from my XT910 using Tapatalk 2
Did a migration from 0.2.7, everything was pretty smooth.
Sometimes second system won't boot, it just reboots to boot. choice menu.
How to set 2nd to be default without bmm apk?
Sent from my XT910 using Tapatalk 2
AndroidOL said:
And where is BMM? Have plan to write it?
Sent from my XT910
Click to expand...
Click to collapse
read OP he said he will, but it will take somes times because he have to rewrite lot of things.
Thanks for your work Whirleyes!
desperex said:
Did a migration from 0.2.7, everything was pretty smooth.
Sometimes second system won't boot, it just reboots to boot. choice menu.
How to set 2nd to be default without bmm apk?
Sent from my XT910 using Tapatalk 2
Click to expand...
Click to collapse
Go to /system/etc/bmm/conf/bootmenu.prop
Edit
"default=1"(for stock) 2(for second)
Oops. it's amazing new BootMenu!
Nice work!
Sent from my XT910S using Tapatalk 2
This is a great modern recovery and definitely a step forward over SafeStrap 3, thanks!
It is possible to edit slot layouts and keep compatibility with further development (e.g. the app)? I intend to mimic v0.2 behaviour, so that the stock firmware layout is left untouched ([email protected],data:[email protected],cache:[email protected]), and the other system is completely contained within webtop partition (system:[email protected],data:[email protected],cache:[email protected]), the other four slots will be unused. Will it work (especially redirecting everything to webtop)?
So i am trying to create a backup through recovery(twrp) -
i select backup
boot, data and system are checked (cache,recovery are unchecked, is that correct?)
i am unsure if i should be selecting enable compression or skip md5 generation
i swipe to backup and get the following message " E: Unable to locate storage device"
I forgot to enable usb debugging and tried to sideload zip
this is the error i get
Any solution
subashkarki said:
I forgot to enable usb debugging and tried to sideload zip
this is the error i get
Any solution
Click to expand...
Click to collapse
You don't have to enable USB debugging for adb to work in recovery. As a first measure, I'd check the md5 or sha checksum of your ROM file and re-download when in doubt. This specific error looks like something went wrong while updating your current system. Try formating /system first (mounts and storage -> format system) before sideloading your ROM.
Cheers
Michael
Thank you
Thank you for all your help.
finistere said:
You don't have to enable USB debugging for adb to work in recovery. As a first measure, I'd check the md5 or sha checksum of your ROM file and re-download when in doubt. This specific error looks like something went wrong while updating your current system. Try formating /system first (mounts and storage -> format system) before sideloading your ROM.
Cheers
Michael
Click to expand...
Click to collapse
Hi all. I keep getting this error after rooting, installing SuperSu and TWRP. When I try to flash a ROM (any ROM), I get stuck. I've tried the latest Resurrection and CM ROMS. Will someone please help me past this last hurdle? Thank you!
I can't upload or link the screenshot but here's the info:
Can't install this package on top of incompatible data. Please try another package or run a factory reset.
Which I have done several times.
Backup ==> select all ==> Swipe to Backup
Wipe ==> Advenced Wipe ==> /System + /Data + /Cache Confirm "Swipe to Wipe" . Try installing again ROM
maxprzemo said:
Backup ==> select all ==> Swipe to Backup
Wipe ==> Advenced Wipe ==> /System + /Data + /Cache Confirm "Swipe to Wipe" . Try installing again ROM
Click to expand...
Click to collapse
That did the trick! I put Resurrection OS on there and all is well except for finding a stable GAPPS build.
Not working for me, my device is KII-L21 on stock rom and I'm trying to install official CM13, my device is rooted and have twrp
If your device is wiped It isnt rooted.. Wipe it dont forget Cache partitions try again.
maxprzemo said:
Backup ==> select all ==> Swipe to Backup
Wipe ==> Advenced Wipe ==> /System + /Data + /Cache Confirm "Swipe to Wipe" . Try installing again ROM
Click to expand...
Click to collapse
Bro, me sirvió. Muchas gracias
It really works, thanks dude
I think it all boils down to doing a format /system.
Next time I will try that!
Edit: I was wrong, the format /data is needed.
If I don't to the reset I am one of those that always gets error 7.
unmount ->system, data, cache :good:
As I already posted at https://forum.xda-developers.com/showpost.php?p=70851854&postcount=534,
I am able to avoid the Error 7 (inconsistend data) by switching to gapps mini before installing the update.
Since the experiental build, I do the following within one TWRP session: install latest gapps mini, install the upgrade to latest lineage-nightly and reinstall latest gapps stock.
So far it works for me.
Do a clean install wiping system, data, cache and dalvik cache before flashing a new ROM is adviced, it will avoid most of problems. For the GApps, I recommend OpenGapps Pico version to install the minimal needed, then you can install the other Google apps you need from the Play Store.
Guys I need some help here. I'm running into the same TWRP error 7 situation. The phone is unlocked, and I've installed kiwi_twrp_3-21_recovery. The model of the device is Honor X5 (KIW-CL00)
I've tried flashing both ResurrectionRemix-M-v5.7.4-20161220-kiwi & lineage-14.1-20170419-nightly-kiwi-signed ROM, whether it's flashing from the phone's storage or from the SD card, both ROM are giving me the same error code.
I tried formatting the system, advance wipe function (Dalvik & Cache & Data & System), now I don't even have the default factory ROM on my phone, but I'm still getting the error 7 code.
Please help. Thanks in advance.
U need to edit updater script to remove assert for device check
Error7 and then "could not find meta inf..."
Huawei KIWI Honor 5x
KIW-L21 EMUI 3.1
I installed
TWRP3.0.2-0 lineage-14.1-20170607-nightly-kiwi-signed.zip ->Error 7
then
cm-13.0-20160904-NIGHTLY-kiwi.zip and cyanogen recovery the same -> Error 7
Error 7 and if I try to delete assert, the next message is "could not find meta inf/com/google/android/update-binary"
My last problem
If I unzip and zip without change anything the Install message is "could not find..." I try it whit Linux 16.4 Win10 Win7 and 7Zip. all the same.
I can not change the updater-script without unpacking the File
Can anybody Help
robert_web said:
Huawei KIWI Honor 5x
KIW-L21 EMUI 3.1
I installed
TWRP3.0.2-0 lineage-14.1-20170607-nightly-kiwi-signed.zip ->Error 7
then
cm-13.0-20160904-NIGHTLY-kiwi.zip and cyanogen recovery the same -> Error 7
Error 7 and if I try to delete assert, the next message is "could not find meta inf/com/google/android/update-binary"
My last problem
If I unzip and zip without change anything the Install message is "could not find..." I try it whit Linux 16.4 Win10 Win7 and 7Zip. all the same.
I can not change the updater-script without unpacking the File
Can anybody Help
Click to expand...
Click to collapse
Did you try this?
Backup ==> select all ==> Swipe to Backup
Wipe ==> Advenced Wipe ==> /System + /Data + /Cache Confirm "Swipe to Wipe" . Try installing again ROM
robert_web said:
Huawei KIWI Honor 5x
KIW-L21 EMUI 3.1
I installed
TWRP3.0.2-0 lineage-14.1-20170607-nightly-kiwi-signed.zip ->Error 7
then
cm-13.0-20160904-NIGHTLY-kiwi.zip and cyanogen recovery the same -> Error 7
Error 7 and if I try to delete assert, the next message is "could not find meta inf/com/google/android/update-binary"
My last problem
If I unzip and zip without change anything the Install message is "could not find..." I try it whit Linux 16.4 Win10 Win7 and 7Zip. all the same.
I can not change the updater-script without unpacking the File
Can anybody Help
Click to expand...
Click to collapse
Pleasw upgrade to TWRP 3.1.1
Sent from my Honor 8 using XDA Labs
robert_web said:
Huawei KIWI Honor 5x
KIW-L21 EMUI 3.1
I installed
TWRP3.0.2-0 lineage-14.1-20170607-nightly-kiwi-signed.zip ->Error 7
then
cm-13.0-20160904-NIGHTLY-kiwi.zip and cyanogen recovery the same -> Error 7
Error 7 and if I try to delete assert, the next message is "could not find meta inf/com/google/android/update-binary"
My last problem
If I unzip and zip without change anything the Install message is "could not find..." I try it whit Linux 16.4 Win10 Win7 and 7Zip. all the same.
I can not change the updater-script without unpacking the File
Can anybody Help
Click to expand...
Click to collapse
U need to edit and repack everything . And do remember that if u mess a single letter it will give an error
Thanks
Sure I wipe advanced by every attempt.
Twrp 3.1.1 the same problem.
But you have right, the Solution for me is not to unzip and zip the file for delete the "assert". Only the way to edit without unpack the File in the Ubuntu "ARCHIVMANAGER" works.
Now it is installed but now I am in a bootloop But this is an other Problem. One step after another.
robert_web said:
Thanks
Sure I wipe advanced by every attempt.
Twrp 3.1.1 the same problem.
But you have right, the Solution for me is not to unzip and zip the file for delete the "assert". Only the way to edit without unpack the File in the Ubuntu "ARCHIVMANAGER" works.
Now it is installed but now I am in a bootloop But this is an other Problem. One step after another.
Click to expand...
Click to collapse
try again by making a clean flash
robert_web said:
Thanks
Sure I wipe advanced by every attempt.
Twrp 3.1.1 the same problem.
But you have right, the Solution for me is not to unzip and zip the file for delete the "assert". Only the way to edit without unpack the File in the Ubuntu "ARCHIVMANAGER" works.
Now it is installed but now I am in a bootloop But this is an other Problem. One step after another.
Click to expand...
Click to collapse
So , plz upload the updater-script here . I will edit and forward u . Later repack everything as is, lets see if that works . If not , i will build a rom for u especially
Thanks its work fine now. It was my fault, I updated from Lollipop not from Nougat. So I used Huawei Firmbootextraktor extract system.img cust.img recovery.img and boot.img and on my SD I copy ../dload/update.app version B140 Android 5.1.1. Then the Handy started I updated EMUI 4.0 and Android 6.1. Now works my Handy with all zip files where I delete the asserts.
Maybe was the problem, in the assert is wrote "kiwi" and my Handy is a "KIW-L21"
Hi guys , I was trying to install a firmware on my phone(Galaxy Core 2 SM-G355H) but im not able to. Dont know what am I missing. I am using TWRP v2.8.5.0 . I know that the firmware is made for my phone (G355HXXUOAOB1) but whenever I try to install it :
Updating partition details...
...done.Full SELinux support is present.
MTP Enabled
Installing '/external_sd/rom.zip'...
Checking for MD5 file. . .
Skipping MD5 check: no md5 file found
Error flashing zip '/external_sd/rom.zip'
Updating partition details. . .
. . . done
I dont know why isnt it being installed coz I know that it is compatible with my device.