Related
Hi!
Every time I try to flash a rom through CWM it gives me this "E:Can't open sdcard/rom.zip (bad)" error. I thought it's because of a corrupt download, but I downloaded it again and again, and it still ain't working. I also tried different roms and zips, but always the same error.
I formatted my SD card. I actually did it three times. Still no luck.
I hope someone can help. Thanks.
ArmorD said:
Hi!
Every time I try to flash a rom through CWM it gives me this "E:Can't open sdcard/rom.zip (bad)" error. I thought it's because of a corrupt download, but I downloaded it again and again, and it still ain't working. I also tried different roms and zips, but always the same error.
I formatted my SD card. I actually did it three times. Still no luck.
I hope someone can help. Thanks.
Click to expand...
Click to collapse
i have found that "bad" generaly means a problem with the zip. what have you been trying to flash?
Pvy.
I hope it was the problem. But I have tried downloading the same file a couple of times and tried different zip files, but none of 'em works. Also I can't install zips through Rom Manager.
Ugh, now what it does is when I go to flash a zip file, it just stucks into the "Opening update package"... It does it on every rom I try to install, even with matching kernels...
ArmorD said:
Ugh, now what it does is when I go to flash a zip file, it just stucks into the "Opening update package"... It does it on every rom I try to install, even with matching kernels...
Click to expand...
Click to collapse
can you show me the zips also have you got a diff SDcard to try?
Pvy.
pvyParts said:
can you show me the zips also have you got a diff SDcard to try?
Pvy.
Click to expand...
Click to collapse
Unfortunately I have no spare card anymore...
I tried
http://forum.xda-developers.com/showthread.php?t=1515148
http://forum.xda-developers.com/showthread.php?t=1537717
http://forum.xda-developers.com/showthread.php?t=1308849
roms.
Great, now I can't even flash CM9 anymore. I think I've made helluva expensive book weight.
Did you format it with windows or via cwm?
sinkster said:
Did you format it with windows or via cwm?
Click to expand...
Click to collapse
I don't use Windows, but I formatted it with Ubuntu. And yes, I also formatted it with CWM(which wasn't a good idea)
Okay, now when I try to flash CM9 Nightly, I got this:
Code:
Installing update...
assert failed: getprop("ro.product.device") ==
"| | getprop(ro.product.device") == "LT18i"
a" assert failed: getprop("ro.product.device") ==
"| | getprop(ro.product.device") == "LT18i"
a" getprop("ro.product.device") == "LT15i" || getprop("ro.product.device) == "LT15a"
E:error in /sdcard/update-cm-9-20120404-NIGHTLY-anzu-signed.zip
[B](Status 7)[/B]
Installion aborted.
Geez...
Any way to restore phone to complete stock? I could start from a clean table...
Allright, got that one fixed. Just needed to erase "getprop" lines from roms updater-script.
Now my phone isn't a brick anymore Able to boot it to CM9. Still, can't flash any roms...
It's alive!
I don't know what I did exactly to get it work, but I think formatting SD card via CWM had something to do with it...
(and sorry for double posts)
Maybe you have formatted in nfts instead of fat32..
Sent from my LT18i using XDA Premium App
Anyone who knows a solution to this? It just appeared on my CWM screen as well out of nowhere. Didn't do anything in MGLDR menu for weeks but it just happened?
fixcho
I want to install custom rom but it shows me that error. Before 1 weak i install cm7 and naw i am with it. Naw i try to install megatron but error then i try void but again error I am with lg p500.
Motorola Defy Mini XT320/XT321 all-in-one script/utility
I've ported mattlgroff's DROIDRAZR all-in-one Script to the Motorola Defy Mini XT320/XT321. This will make life easier and it will do it for you.
Make sure you have fastboot mode if not please refer to this guide for fastboot but there is a fastboot checker in option 6 but it won't install fastboot for you.
Link: http://forum.xda-developers.com/showpost.php?p=36199694&postcount=3
Options available:
1. Root your Motorola Defy Mini XT320/XT321
2. Install 2nd-init/TWRP Recovery
3. Overclock installation
4. Unroot Device
5. Wipe Data/Factory Reset
6. Fastboot checker.
7. Exit Utility
Instructions:
NEW PACKAGE & instructions
1. Download the EXE file at http://www.mediafire.com/?c81fnrtrki65e9i
2. Double click on the exe.
3. Choose an option by entering a number from 1 to 7
OLD PACKAGE & instructions
1. Download package at [REMOVED OLD LINK]
Please Download the fixed package at http://www.mediafire.com/?krxtemrthsz5ier
EXE Version: http://www.mediafire.com/?0kwmx4whjj1ua8c
2. Extract the zip file making sure all the files are in the same place.
3. Click on the batch file named 'DefyMiniUtility.bat'
4. Choose an option by entering a number from 1 to 7.
Credits to:
- Bernd.Defy for overclock module and Guitwo2 for init.d script
- Guitwo2 and jkkk88 for TWRP and aweosomeabhjeet for 2nd-init
- DoOMLoRD for unroot script
- Mattlgroff for the original DROID RAZR all-in-one script
If anyone knows if I missed a member for the credits, please PM me. Thanks
Make sure press thanks if it works
Guys please don't repost it as your own work, otherwise I'll report it and you will get banned from XDA.
NOTE: If you have previously used the old EXE to install TWRP then please remove the old folders by using these instructions using cmd before using updated exe to install TWRP;
1.
Code:
adb shell
2.
Code:
su
3.
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock11 /system
4.
Code:
rm -R /system/bootmenu
Then use the updated exe to install TWRP.
NOTE: If you don't like TWRP, you can download Guitwo2's Permanent CWM at http://forum.xda-developers.com/attachment.php?attachmentid=1875373&d=1365682716
Temporary CWM Recovery: http://forum.xda-developers.com/attachment.php?attachmentid=1875299&d=1365680458
2nd-init does NOT work in CWM Recovery
Thanks to @Guitwo2 for CWM Recovery.
Instructions on how to install Permanent CWM Recovery:
1. Make sure stericson-busybox is installed
2. Put XT320_bootmenuV2.zip in the root of your sdcard
3. Reboot into fastboot mode by typing this command in cmd:
Code:
adb reboot bootloader
4. Then type this command in cmd:
Code:
fastboot boot recovery.img
5. Then use volume keys to navigate and power button to select option. Select install zip from sdcard, then select XT320_bootmenuV2.zip and select yes to install the zip file
6. Then reboot device by selecting reboot device now.
CWM 6 has a bug where it asks you to 'disable recovery flash' when you select reboot system now make sure you select NO or you will soft brick your device.
Changelog:
-v2 No need to mount /sdcard in CWM Recovery. Fixed TWRP installation issues.
-v2.0.1 Released an .exe version of script, to simplify installation
-v2.0.1.1 Fixed bootmenu.zip
This can install a custom recovery?
This can install a custom recovery?
Thank you
The root process worked for me. Now i can install link2sd and set up a swap partition.
I cant install TWRP and i think the reason is that the bat was having some problem to send that bootmenu.tar file to my sd card. I tried to send that file myself before starting the entire process and it didnt worked.
I took a picture of the error i'm getting . Thank you again, i was really mad about that low internal space xD
same problem... someone can fix it? please
fca.sjc said:
The root process worked for me. Now i can install link2sd and set up a swap partition.
I cant install TWRP and i think the reason is that the bat was having some problem to send that bootmenu.tar file to my sd card. I tried to send that file myself before starting the entire process and it didnt worked.
I took a picture of the error i'm getting . Thank you again, i was really mad about that low internal space xD
Click to expand...
Click to collapse
sfoot13 said:
same problem... someone can fix it? please
Click to expand...
Click to collapse
Ok, I've made a fixed script here. The error was that the sdcard is a directory so it will refuse to push files into it.
Here's the updated script below. Just put the .bat file in the same place as the other files.
Thanks
rootdefyxt320 said:
Ok, I've made a fixed script here. The error was that the sdcard is a directory so it will refuse to push files into it.
Here's the updated script below. Just put the .bat file in the same place as the other files.
Click to expand...
Click to collapse
Ty for the quickly answer.
Btw, my gsm network wasnt working after the root process. If the same thing happens to someone else, just do a master reset and it will work again.
pull command is working now
That sdcard copy part is working now. The TWRP process is still not working for me. I tried to do myself the commands using the adb interface and when i use the command to intall the tar, i got the message 'tar: no space left on device" . I hope you can help me with that and i'm sorry about all this questions xD .
fca.sjc said:
That sdcard copy part is working now. The TWRP process is still not working for me. I tried to do myself the commands using the adb interface and when i use the command to intall the tar, i got the message 'tar: no space left on device" . I hope you can help me with that and i'm sorry about all this questions xD .
Click to expand...
Click to collapse
You must have more than 5MB free in your /system partition. Please move your apps to the /flex partition or delete the useless apps in /system.
rootdefyxt320 said:
You must have more than 5MB free in your /system partition. Please move your apps to the /flex partition or delete the useless apps in /system.
Click to expand...
Click to collapse
Thank u so much to everyone who make it possible xD
(can i do now a overclock to 720 without problems?)
sfoot13 said:
Thank u so much to everyone who make it possible xD
(can i do now a overclock to 720 without problems?)
Click to expand...
Click to collapse
Yes but it sometimes gets unstable so you should overclock to 700MHz which is the highest I got without reboots. pll2_l_val=73 gives you 700MHz.
rootdefyxt320 said:
Yes but it sometimes gets unstable so you should overclock to 700MHz which is the highest I got without reboots. pll2_l_val=73 gives you 700MHz.
Click to expand...
Click to collapse
Thank u so much and TWRP doesn't work xD i have 8.5 mb free on system but it can't create the folders on bootmenu
sfoot13 said:
Thank u so much and TWRP doesn't work xD i have 8.5 mb free on system but it can't create the folders on bootmenu
Click to expand...
Click to collapse
I've released an .exe version of my script. This should work now .
Link: http://www.mediafire.com/?0kwmx4whjj1ua8c
Thank u bro and sorry but i can't overclock it to 700 =/
i installed TWRP but it doesn't work and when i turn on my mobile it freezes on home screen :/ is a mess.... it's possible install it via recovery (temportal CWM)?
OFF TOPIC.
Congrats on your well deserved mention on the portal.
sfoot13 said:
i installed TWRP but it doesn't work and when i turn on my mobile it freezes on home screen :/ is a mess.... it's possible install it via recovery (temportal CWM)?
Click to expand...
Click to collapse
It worked for others but in your situation the only thing I can advise is to do a data wipe and relfash SBF file. Just go to Guitwo2's there to install permanent CWM.
Link: http://forum.xda-developers.com/showthread.php?t=2229233
rootdefyxt320 said:
It worked for others but in your situation the only thing I can advise is to do a data wipe and relfash SBF file. Just go to Guitwo2's there to install permanent CWM.
Link: http://forum.xda-developers.com/showthread.php?t=2229233
Click to expand...
Click to collapse
:good: Working! Thank u so much, now i have CWM working on my defy mini, i'm really thankful, thanks again
Hi, it's me again... i have a new trouble
i installed the xt320_bootmenu.zip (from this thread http://forum.xda-developers.com/showthread.php?t=2229233) the first time that i rebooted works fine, but the on the second reboot it doesn't work, then i went to data to check if test.log was there and here's the problem... no test.log...
init.d was working fine until that i did it, i guess that my phone have troubles making work init.d
some solution for this annoying guy? thanks in advance!
sfoot13 said:
Hi, it's me again... i have a new trouble
i installed the xt320_bootmenu.zip (from this thread http://forum.xda-developers.com/showthread.php?t=2229233) the first time that i rebooted works fine, but the on the second reboot it doesn't work, then i went to data to check if test.log was there and here's the problem... no test.log...
init.d was working fine until that i did it, i guess that my phone have troubles making work init.d
some solution for this annoying guy? thanks in advance!
Click to expand...
Click to collapse
Looks like 97bootmenu deleted itself, please reinstall the CWM zip again and it should work.
o/
Trying to flash F4k's awesome kernel here http://forum.xda-developers.com/showthread.php?t=2636890
(I'd post there but it won't let me before I have 10 posts).
I'm using ROM manager: Install ROM from SD card - I select the zip from my SD card - confirm.
However, it doesn't seem to work. What seems to happen is that wlan configuration files (system/etc/firmware/wlan/prima/) do flash, but kernel remains unchanged. Options - About Device says that kernel version is 3.4.0-1266356 which is what my Mini came with.
As a result I end up with old kernel and broken wlan.
Recovery does report that "some operations fail". Attaching recovery.log
Halp? Am I doing this wrong? Should I apply the .zip using some other tools?
Thanks!
[edit] attachment is invisible (yet?) so here's an alternative copy of recovery.log: https://www.dropbox.com/s/7g2378naa4bhbdy/recovery.log
sysKin said:
o/
Trying to flash F4k's awesome kernel here http://forum.xda-developers.com/showthread.php?t=2636890
(I'd post there but it won't let me before I have 10 posts).
I'm using ROM manager: Install ROM from SD card - I select the zip from my SD card - confirm.
However, it doesn't seem to work. What seems to happen is that wlan configuration files (system/etc/firmware/wlan/prima/) do flash, but kernel remains unchanged. Options - About Device says that kernel version is 3.4.0-1266356 which is what my Mini came with.
As a result I end up with old kernel and broken wlan.
Recovery does report that "some operations fail". Attaching recovery.log
Halp? Am I doing this wrong? Should I apply the .zip using some other tools?
Thanks!
[edit] attachment is invisible (yet?) so here's an alternative copy of recovery.log: https://www.dropbox.com/s/7g2378naa4bhbdy/recovery.log
Click to expand...
Click to collapse
What ROM are you using?
Installation is suppose to be simple with CWM:
1. Boot to CWM
2. Wipe cache and dalvik cache
3. Install kernel ZIP (do not extract the zip or modifiy it)
4. Reboot.
TNCS said:
What ROM are you using?
Click to expand...
Click to collapse
Stock.
By which I mean I9195TDVUAMH1, the stock for Australian I9195T.
Should be fine, right? Or did I misunderstand?
TNCS said:
Installation is suppose to be simple with CWM:
1. Boot to CWM
2. Wipe cache and dalvik cache
3. Install kernel ZIP (do not extract the zip or modifiy it)
4. Reboot.
Click to expand...
Click to collapse
Yup, that's effectively the same thing I did (only I used ROM Manager app to avoid pressing volume down button lol). Fails on the same assert and produces that same recovery.log as I've shared.
minzip: Can't create containing directory for "/system/etc/init.d/90hardlimit": Not a directory
set_perm: chown of /system/etc/init.d/90hardlimit to 0 0 failed: Not a directory
set_perm: chmod of /system/etc/init.d/90hardlimit to 755 failed: Not a directory
script aborted: set_perm: some changes failed
Click to expand...
Click to collapse
Looking at this, should the script mkdir /system/etc/init.d? Or should I simply do it beforehand? It's not there on my stock filesystem.
sysKin said:
Stock.
By which I mean I9195TDVUAMH1, the stock for Australian I9195T.
Should be fine, right? Or did I misunderstand?
Yup, that's effectively the same thing I did (only I used ROM Manager app to avoid pressing volume down button lol). Fails on the same assert and produces that same recovery.log as I've shared.
Looking at this, should the script mkdir /system/etc/init.d? Or should I simply do it beforehand? It's not there on my stock filesystem.
Click to expand...
Click to collapse
I assume you have rooted your phone.. I have no idea why it does that, I think you should redirect the quuestion at F4k's post for stock ROM.
TNCS said:
I assume you have rooted your phone.. I have no idea why it does that, I think you should redirect the quuestion at F4k's post for stock ROM.
Click to expand...
Click to collapse
Thanks for your help TNCS. Five more posts and I'll be able to post in that thread
In the meantime I hope F4k doesn't mind a private message.
Hi, I have been flashing nightlies since CM11 came out with no issues (maybe once a week, so quite a few times).. The version I currently have installed is 11-20140204. I have been just dirty flashing manually in CWM, installing from SD card / install ZIP.
For some reason I cannot update anymore ? Any of the new Nightly versions give me a STATUS 7 and to my knowledge nothing on my phone has changed ?
I have updated to the latest CWM - 6.0.4.7. and still wont work.
Here is the error I am getting :
Installing Update:
Assert failed:
getprop (“re.bootloader”) == “I747UCDMG2”
getprop (“re.bootloader”) == “I747UCUEMJ2”
getprop (“re.bootloader”) == “I747UCUEMJB”
getprop (“re.bootloader”) == “I747MVLDMF1”
getprop (“re.bootloader”) == “I747MVLUEMK5”
getprop (“re.bootloader”) == “I747MUMUEMK3”
E: Error in /data/media/0/cm-11-20140216-NIGHTLY-d2att.zip (STATUS 7)
Installation aborted.
Please help, Thanks
I was having the same problem and if you look around a little you can try editing the updater script.... There is a whole step by step tutorial somewhere in this forum. You have to unzip the ROM and edit the updater-script file but here is the link just copy and paste it, its a couple comments down and it has worked for a ton of people, I'm still having issues but its helped a ton of people to flash successfully.
http://forum.xda-developers.com/showthread.php?p=38880428
Is your bootloader included in the list of supported loaders?
Use TWRP instead.
Flash this, http://invisiblek.org/d2firmware.html
Format /cache, dalvik, /system, /data, and your internal SD card, then try again.
Sent from my SGH-I747 using Tapatalk
RJantu said:
Use TWRP instead.
Flash this, http://invisiblek.org/d2firmware.html
Format /cache, dalvik, /system, /data, and your internal SD card, then try again.
Sent from my SGH-I747 using Tapatalk
Click to expand...
Click to collapse
Won't formatting your internal SD card delete your nandroid backups if that's where your cwm stuff is? I'd like to find a solution for my issue to I have the new bootloader from 4.3 UCUEMJB and I successfully rooted it and installed philz cwm and removed Knox with the Knox remover zip and then I successfully flashed beanstalk 4.4.1 which I'm still running and with no issues......but I haven't been able to flash anything else.... So I was considering trying twrp because at first I was getting those errors then edited the updater scripts in the ROMs I was trying to flag just for it to abort installation again and not because of a status 7 error I think it said something about data/0 / volume or something crazy like that which is all foreign to me.
I am trying to automate my nandroid backups but apparently a/b devices mount /data/cache as /cache so I don't know how to make twrp read my openrecoveryscript file from /data/cache. Any help would be greatly appreciated.
darkfire404 said:
I am trying to automate my nandroid backups but apparently a/b devices mount /data/cache as /cache so I don't know how to make twrp read my openrecoveryscript file from /data/cache. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Have you solved this problem? if yes how did you solve your problem?
mauronofrio said:
Have you solved this problem? if yes how did you solve your problem?
Click to expand...
Click to collapse
I haven't yet. I don't know if it's possible without modifying TWRP to read from /data/cache on startup since the cache partition doesn't exist on a/b devices
I doubt it will help or not...
But I noticed when sideloading an OTA, that whatever the .zip file would be called would "extract" to the folder "sideload" (in the /sdcard, but there's a good chance that it's its own folder in the root directory...) as sideload.zip (i believe...I can easily be wrong....but I remember it was a simple and obvious one-word name....). I remember having issues with TWRP processing the initial .zip file, so I would extract the initial OTA .zip file, then manually input what was extracted into that folder under that specific name and TWRP was able to automatically start processing the OTA....
I'm not sure, but maybe you might find this process beneficial and/or interesting/inspiring...
darkfire404 said:
I am trying to automate my nandroid backups but apparently a/b devices mount /data/cache as /cache so I don't know how to make twrp read my openrecoveryscript file from /data/cache. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Have you tried to put the script in /data/cache/recovery/openrecoveryscript ? if the folder doesn't exist try to create it
mauronofrio said:
Have you tried to put the script in /data/cache/recovery/openrecoveryscript ? if the folder doesn't exist try to create it
Click to expand...
Click to collapse
I did that. It didn't work
I'm encountering the same behavior. OpenRecoveryScripts are not being executed.
Running TWRP-3.2.3-0, Pixel 2 on Android 9.0.
UncertainSpin said:
I'm encountering the same behavior. OpenRecoveryScripts are not being executed.
Running TWRP-3.2.3-0, Pixel 2 on Android 9.0.
Click to expand...
Click to collapse
I'm having the same problem too. I have been using Tasker to write to /cache/recovery/openrecoveryscript because that's all I could find online.
I intend to have this in the Run Shell command in Tasker.
chmod 0777 /cache/recovery
echo "backup SDCRBM weeklybackup" > /cache/recovery/openrecoveryscript
echo "reboot" >> /cache/recovery/openrecoveryscript
chmod 664 /cache/recovery/openrecoveryscript
I have verified that it is writing the file, and TWRP seems to be erasing it which from what I gather it is supposed to do. But it is not executing the command when TWRP starts.
LineageOS 16.0 unofficial/ TWRP 3.2.3 on Samsung Galaxy S7.
We need to bring TWRP developers awareness for this issue, it's already reported on GitHub (https://github.com/omnirom/android_bootable_recovery/issues/221) but not acknowledge by TWRP team... If you have a GitHub account, vote for that issue, if you know someone from TWRP, bring them attention to that.
IMO, having this script working is very important for truly automated backups of our devices, let's get this issue fixed...
rfgamaral said:
We need to bring TWRP developers awareness for this issue, it's already reported on GitHub (https://github.com/omnirom/android_bootable_recovery/issues/221) but not acknowledge by TWRP team... If you have a GitHub account, vote for that issue, if you know someone from TWRP, bring them attention to that.
IMO, having this script working is very important for truly automated backups of our devices, let's get this issue fixed...
Click to expand...
Click to collapse
Yup indeed needs to be fixed..