Related
I am getting a really long error trying to apply the OTA 2.2. I have not seen this anywhere on here and google is taking me to many different phones and not quite the same errors.
Code:
assert failed: apply_patch_check("/system/bin/reboot", "723277108cbd2d5E:unknown command[c41a12e055052004932e70fac",]
E:Error in /cache/ota_supersonic_3.26.651.6-1.47.651.1_releasexjg0a0vqdw5cor7z.zip
(Status 7)
Installation aborted.
I am running 2.1 updated on a rooted phone. (Rooted version of same.) I just updated my radio and PRI so that I have current radio .9 (or something) and PRI 1.77.
The download of the update seems to have gone fine and then I clicked the install and it is not working.
If I use Astro I can get to the reboot file but I have no idea how to open it. (ADB won't let me see anything in the system folder which is aggravating.)
If I use Astro I can get to the cache folder but it shows it empty. If I use ADB then I can see the OTA in there. (WTF?)
HELP....
What else? Let me know if I need to provide more info, I'll find it on the phone.
No one got a thought on this one? If search is up this morning I'll try that in a bit.
Hey all!
I have Korean LG SU640. When trying to install any rom, e.g. CM9, 9.1, 10, i have the same error:
assert failed: getprop ("ro.product.device") =="su640" ll getprop ("ro.build.product") == "su640"
E: Error in/sdcard/cm-9.0.0-su640.zip
(status 7)
Installation aborted.
As I found, this error appears when you're trying to install rom from another device
Installation of ROMs from P930 goes ok, but wifi doen'ts works and screen oriebtation is wrong.
Tried to flash CWM for SU640 from here, but this didn't help.
Solution I found is to put into SU640 rom META-INF and system\build.prop from P930. Rom installed successfully and everything works.
However, making this manipulation for each update is quite annoying.
Does anybody knows how to make my phone 'think' he is SU640, not P930?
chukerer said:
Hey all!
I have Korean LG SU640. When trying to install any rom, e.g. CM9, 9.1, 10, i have the same error:
assert failed: getprop ("ro.product.device") =="su640" ll getprop ("ro.build.product") == "su640"
E: Error in/sdcard/cm-9.0.0-su640.zip
(status 7)
Installation aborted.
As I found, this error appears when you're trying to install rom from another device
Installation of ROMs from P930 goes ok, but wifi doen'ts works and screen oriebtation is wrong.
Tried to flash CWM for SU640 from here, but this didn't help.
Solution I found is to put into SU640 rom META-INF and system\build.prop from P930. Rom installed successfully and everything works.
However, making this manipulation for each update is quite annoying.
Does anybody knows how to make my phone 'think' he is SU640, not P930?
Click to expand...
Click to collapse
All you need to do is go to CWM, select "Install zip from sdcard", then select "toggle script asserts" (so that the setting is disabled).
drumist said:
All you need to do is go to CWM, select "Install zip from sdcard", then select "toggle script asserts" (so that the setting is disabled).
Click to expand...
Click to collapse
Doesn't help. The same error
chukerer said:
Doesn't help. The same error
Click to expand...
Click to collapse
Solution found!
Download the latest recovery for LG Optimus LTE from http://www.clockworkmod.com/rommanager/.
Flash it with Android Terminal Emulator how it was described here
Reboot into recovery and install any rom for SU640.
The only problem is that Rom Manager still wants to flash recovery for P930
chukerer said:
Hey all!
I have Korean LG SU640. When trying to install any rom, e.g. CM9, 9.1, 10, i have the same error:
assert failed: getprop ("ro.product.device") =="su640" ll getprop ("ro.build.product") == "su640"
E: Error in/sdcard/cm-9.0.0-su640.zip
(status 7)
Installation aborted.
As I found, this error appears when you're trying to install rom from another device
Installation of ROMs from P930 goes ok, but wifi doen'ts works and screen oriebtation is wrong.
Tried to flash CWM for SU640 from here, but this didn't help.
Solution I found is to put into SU640 rom META-INF and system\build.prop from P930. Rom installed successfully and everything works.
However, making this manipulation for each update is quite annoying.
Does anybody knows how to make my phone 'think' he is SU640, not P930?
Click to expand...
Click to collapse
It's really easy. what you need to is delete(
"ro.product.device") =="su640" ll getprop ("ro.build.product") == "su640")of META-INF then pack and sign zip,this will work well.
Sent from my LG-SU640 using xda premium
flash recovery 6.0.1.2
Sent from my LG-SU640 using xda app-developers app
HELP!!!!!!
pxrphj said:
flash recovery 6.0.1.2
Sent from my LG-SU640 using xda app-developers app
Click to expand...
Click to collapse
I just flashed recovery 6.0.1.2 but it still error. I want to try flashing rom by deleting ("ro.product.device") =="su640" ll getprop ("ro.build.product") == "su640") of META-INF, but I don't know how to do. Could you please help me? I want to flash custom rom.
Used to have this problem... but it was solved when I flashed cwm 6.0.1.4
http://me.zing.vn/apps/sharefile?params=/download/downloadfile/file/NzEzMys2NjAyMzkzMQ==
Sent from my LG-SU640
navik said:
It's really easy. what you need to is delete(
"ro.product.device") =="su640" ll getprop ("ro.build.product") == "su640")of META-INF then pack and sign zip,this will work well.
Sent from my LG-SU640 using xda premium
Click to expand...
Click to collapse
Please can you tell me how to delete ("ro.product.device") =="su640" ll getprop ("ro.build.product") == "su640")of META-INF
Some ROMs will give an error: "assert failed getprop(ro.product.device==SU640)" or something like that.
Open that ROM using Winrar, go to "META-INF\com\google\android " and open the file named "updater-script" and remove the first line and save.
On closing the text editor, winrar will ask you if you want to replace the edited file, click "Yes" or "OK" . and flash the ROM again. This time, it will work.
Ref: http://wiredsoup.blogspot.com/2013/02/lg-optimus-su640-comfirmed-working.html
TeamWin Recovery Project
Restore in the old 2.4.1 version doesnt work for me. I build from source, now it works, I share.
Download
http://dualhoki.vim.hu/bubor/dev/twrp-i927/
http://rpi.bubor.hu/bubor/dev/twrp-i927/
Current Issues:
display timeout blank screen disabled
Issue report:
Give everything I need to reproduce the problem (logs, guide, dumps etc), I wont reply useless reports.
Changelog:
Changelog can be found : http://www.teamw.in/project/twrp2
2.6.1 wipe data make smaller data partition, that need for encyption. Encypt mount support.
2.6.3 removed superuser, compiled with cm-10.2
2.6.3-2 add fuse, it should support extfat
2.6.3-3 remove encypt, puth superuser (Rooting)
2.6.3-4 put security fs, selinux, it will need for flash cm-11.0
2.6.3.1 update twrp from git (actually its 2.7.0, but you will see 2.6.3 in the corner)
2.7..1: update twrp, compiled with cm-10.2
2.8.4: compild with cm-11.0, fix MTP
Credit:
Terinfire(Source)
Dman(Source)
thegreatergood
TWRP TEAM
Install
Install zip from TWRP or ClockworkModRecovery
Put device to download mode ( power on, while hold volume up, hit volume up again when asked to do ), and use odin (included in the zip, browse to pda, dont flash other)
Changelog: http://www.teamw.in/project/twrp2
You may want to install older rom, you must change assert tag in rom zip file META-INF/com/google/android/updater-script:
Code:
assert(getprop("ro.product.device") == "i927" || getprop("ro.build.product") == "i927" ||
getprop("ro.product.device") == "SGH-I927" || getprop("ro.build.product") == "SGH-I927" ||
getprop("ro.product.device") == "SGH-I927R" || getprop("ro.build.product") == "SGH-I927R" ||
getprop("ro.product.device") == "SGHI927" || getprop("ro.build.product") == "SGHI927" ||
getprop("ro.product.device") == "SGHI927R" || getprop("ro.build.product") == "SGHI927R" ||
getprop("ro.product.device") == "n1" || getprop("ro.build.product") == "n1" || abort("This package is for \"i927,SGH-I927,SGH-I927R,SGHI927,SGHI927R,n1\" devices; this is a \"" + getprop("ro.product.device") + "\"."););
Awesome! Thanks so much for fixing this for Team Glide!
Sent from my Rooted Samsung SGH-i927 Captivate Glide
Running @ndroid JB4.2.2 CM10.1 & TWRP 2.4.4.0 using xda-dev app.
They just released a newer version 2.5.0.0
Sent from my Rooted Samsung SGH-i927 Captivate Glide
Running @ndroid JB4.2.2 & TWRP 2.4.4.0 using xda-dev app.
*thanks bubor for keeping twrp up to date.
*please keep twrp up to date since it can then use rom manager to do all the wipes, flash and install roms and gapps package an dother patches along he way.
*can the img extension just be use through adb to get that to the phone or not?
*how is this done and steps pleas?
dd if=recovery.img of=/dev/block/mmcblk0p8
You can find recovery.img inside the zip.
update to 2.6.1
Oh my...
I think this is one of the best finds for the Cappy Glide since CM10.1...
Thank you! Thanks SOOOOO MUCH!
I was about fed-up with CWMR, having to spam the volume buttons, but now with touch controls, I mean, COME ON! How much better could it get to flash and recover and restore and backup stuff! Thank you! BIG THUMBS UP!
:good::good::good::good::good:
great thanks, its time to udate it. i see we have a version from odin and one to flash via CWMR.
Initially got some strange "assert getprop" errors when flashing stock Samsung flashable packs (CWM does the job), but flashing CM and PAC looks alright. Just why does the stock flashables all require ro.product.device=SGHI927... (normally it would be SGH-I927)
Sent from Samsung Captivate Glide @ CM10.1.2
AndyYan said:
Initially got some strange "assert getprop" errors when flashing stock Samsung flashable packs (CWM does the job), but flashing CM and PAC looks alright. Just why does the stock flashables all require ro.product.device=SGHI927... (normally it would be SGH-I927)
Sent from Samsung Captivate Glide @ CM10.1.2
Click to expand...
Click to collapse
assert tag changed a year ago, old custom 4.0/4.1 doesnt work with newer recoveries.
New roms test both assert tags. You can change test in rom's zip file.
Well after upgrading to 2.6.3 I get fail to create directory & failed to backup? This is to either internal or external. On 2.6.1 I was getting fails to restore? Anyone else having these issues?
Sent from my Rooted Samsung SGH-i927 Captivate Glide Running Android ICS 4.0.4 LiteRom 0.9.0 & TWRP 2.6.3 using xda-dev app.
amppcguru said:
Well after upgrading to 2.6.3 I get fail to create directory & failed to backup? This is to either internal or external. On 2.6.1 I was getting fails to restore? Anyone else having these issues?
Sent from my Rooted Samsung SGH-i927 Captivate Glide Running Android ICS 4.0.4 LiteRom 0.9.0 & TWRP 2.6.3 using xda-dev app.
Click to expand...
Click to collapse
could you write detail? uploading /tmp/recovery.log helps lot.
I just made a backup and restore, and it works.
TWRP 2.6.3 bu failure
bubor said:
could you write detail? uploading /tmp/recovery.log helps lot.
I just made a backup and restore, and it works.
Click to expand...
Click to collapse
Hm I don't see a tmp folder in root or twrp. I did a search for all recovery.log files & only found the ones from 2.6.1 backups
I had to go back to 2.6.1 & got it to backup & restore.
I've attached one of those.
When trying using 2.6.3 it says it "Unable to create Folder: /external_sd/TWRP/..."
"Failed to make backup folder"
I am running TGG Literom 0.9.0
amppcguru said:
Hm I don't see a tmp folder in root or twrp. I did a search for all recovery.log files & only found the ones from 2.6.1 backups
I had to go back to 2.6.1 & got it to backup & restore.
I've attached one of those.
When trying using 2.6.3 it says it "Unable to create Folder: /external_sd/TWRP/..."
"Failed to make backup folder"
I am running TGG Literom 0.9.0
Click to expand...
Click to collapse
try to rename TWRP to TWRP2,and lets it creates new one.
2.6.3 backup unable to create folder
bubor said:
try to rename TWRP to TWRP2,and lets it creates new one.
Click to expand...
Click to collapse
I tried renaming them & reflashed 2.6.3 but still get the same error messages of it not being able to create backup folders? Very strange.... I could have sworn it was working the first time I flashed it? But now these repeated errors have me mystified?
Edit: I also tried redownloading 2.6.3 & reflashing but still getting the same error messages?
Ive had to reflash 2.6.1 & it works perfectly!
2.6.3
Doesn't seem capable of mounting 64gb exfat formatted SDXC card.
Just says failed to mount or something along those lines, mounted a 8gb FAT32 card, wouldn't mount an old FAT 512mb card.
I know for a fact the 2.6.1 is capable of mounting the 64gb exfat card. Flashed back to it and no issues.
amppcguru said:
I tried renaming them & reflashed 2.6.3 but still get the same error messages of it not being able to create backup folders? Very strange.... I could have sworn it was working the first time I flashed it? But now these repeated errors have me mystified?
Edit: I also tried redownloading 2.6.3 & reflashing but still getting the same error messages?
Ive had to reflash 2.6.1 & it works perfectly!
Click to expand...
Click to collapse
I had the same error, so i just downloaded nandroid backup from the play store, and it works wonders if you choose TWRP as your recovery.
Sent from my SGH-I927 using XDA Premium 4 mobile app
I also had the same problem, but with d2att - changed the auto generated backup name and it worked (also fixed permissions but not sure if it was necessary to or not).
bubor said:
assert tag changed a year ago, old custom 4.0/4.1 doesnt work with newer recoveries.
New roms test both assert tags. You can change test in rom's zip file.
Click to expand...
Click to collapse
Went to older recovery, still not able to flash.
WTF?
Sent from my SGHI927 using Tapatalk
Changing the auto-generated name fixed for me too.
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.
Q&A for [ROM][UNOFFICIAL] CyanogenMod 12 Nightlies
FAQ:
Q: I tried to flash the ROM and got this:
Code:
Installing update...
set_metadata_recursive: some changes failed
E:Error in /sdcard/..path od ROM.zip
(Status 7)
Installation aborted.
Or I'm having other recovery issues.
A: Update your recovery to supported one. See the list below.
TWRP 2.8.1.2 ACE or newer
Q: I've used HTC Dev unlock and flashed the rom but it won't boot. What should I do?
A: You need to extract boot.img from the zip and flash it via fastboot. If you don't have fastboot executable anymore from flashing recovery, install Android SDK platform tools (Linux users should find it from distro's package management) and then reboot to bootloader, open command prompt and navigate to the location you extracted your boot.img and type:
Code:
fastboot flash boot boot.img
You need to repeat this everytime you flash new version of this rom to ensure everything will work fluently as long as you have just basic HTC Dev unlock.
Q: Where are my developer and performance options?
A: http://goo.gl/jpS8r
Q: Where is my root?
A: http://www.cyanogenmod.org/blog/all-about-l-part-2 (Read under "Superuser where?")
Q: Feature X doesn't work, let's make 1000 posts about it to annoy everyone.
A: Please, dont. Use search and then use search again and only then report your problem with necessary logs. [Logcat guide, thanks to MusikMonk for the link]
Q: I hate you for not fixing this issue X!!!
A: I love you too.
Q: How I can build CM12.0 myself?
A: Setup a basic Android build environment.
Code:
mkdir cm12
cd cm12/
repo init -u git://github.com/CyanogenMod/android.git -b cm-12.0
mkdir -p .repo/local_manifests
wget https://github.com/OpenDesireProject/android/raw/cm-12.0/local_manifest.xml -O .repo/local_manifests/cm_ace.xml
repo sync
. build/envsetup.sh
lunch cm_ace-userdebug
mka bacon
Once the build finishes you'll find your goods from out/target/product/ace/ directory.
Q: Something about something something something.
A: Ask the guy/gal next to you.
Thanks..reserved?
Sent from my ATRIX HD using Tapatalk
Home button not working. Have to use back button
Camera Bug
Camera is in the Apps not listen and it dont work from Lockscreen.
Sorry for my English and a big Thanks from Germany / EinfachAleks
No sounds.
---------- Post added at 11:32 AM ---------- Previous post was at 11:14 AM ----------
I don't have camera at all
Sent from my Desire HD using Tapatalk
Great job Tested on my Inspire 4G with alpha gaps all - so all works good but one problem at startup setting after ten minutus of thinking it cant set up my GSM career and tell me to set up it next time I'll think okay wait when all google sutups done ..... go to setting /mobile wireless/operator settings ... and at this moment I have a crash. I hawe an Ukrainian operator maybe this thing cause such problem Thank you a lot for you futer job at this rom And WiFi works greate ))))
For me the Home Key just working fine...im waiting for the next Snapshot
I'm gonna download zip again and flash again. Maybe bad flash.
Doge2 and recovery
Doge2 Installation doesn't work with 4EXT Recovery Touch v1.0.0.6 RC 3.
ApplyParsedPerms: lsetfilecon of /system/lost+found to ubject_r:system_file:s0 failed: Operation not supported on transport endpoint
script aborted: set_metadata_recursive: some changes failed
set_metadata_recursive: some changes failed
E:Error in /sdcard/ROM CM12/cm-12-20141130-UNOFFICIAL-DOGE2-ace.zip
(Status 7)
Installation aborted.
With TWRP 2.8.1.0 it installs but these TKruzze gapps (https://s.basketbuild.com/devs/TKruzze/Android 5.0 GApps/Micro-Modular GApps/) gives error
E: Error executing update binary zip "gapps location.zip"
INSTALLATION FAILURE: Your device does not have sufficient space available in
the system partition to install this GApps package as currently configured.
You will need to switch to a smaller GApps package or use gapps-config to
reduce the installed size.
Finnaly old bug for me.
Does anyone have same problem like I do? I can't make partitions with TWRP 2.8.1.0 partition editor! With 4ext recovey I can make partition but with TWRP I can't.
http://forum.xda-developers.com/htc-desire-hd/help/qa-twrp-2-8-1-0-cwm-6-0-5-1-unofficial-t2952947
first i want to thank you for this amazing rom
and i want to ask if i update from doge 1 to doge 2 should i flash boot.img again after installing the rom
marek287 said:
Doge2 Installation doesn't work with 4EXT Recovery Touch v1.0.0.6 RC 3.
ApplyParsedPerms: lsetfilecon of /system/lost+found to ubject_r:system_file:s0 failed: Operation not supported on transport endpoint
script aborted: set_metadata_recursive: some changes failed
set_metadata_recursive: some changes failed
E:Error in /sdcard/ROM CM12/cm-12-20141130-UNOFFICIAL-DOGE2-ace.zip
(Status 7)
Installation aborted.
http://forum.xda-developers.com/htc-desire-hd/help/qa-twrp-2-8-1-0-cwm-6-0-5-1-unofficial-t2952947
Click to expand...
Click to collapse
I have the same error
marek287 said:
Doge2 Installation doesn't work with 4EXT Recovery Touch v1.0.0.6 RC 3.
ApplyParsedPerms: lsetfilecon of /system/lost+found to ubject_r:system_file:s0 failed: Operation not supported on transport endpoint
script aborted: set_metadata_recursive: some changes failed
set_metadata_recursive: some changes failed
E:Error in /sdcard/ROM CM12/cm-12-20141130-UNOFFICIAL-DOGE2-ace.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
Try to format your system partition manually. If that doesn't help, contact 4EXT dev. Generally I can't fix recovery related issues like this seems to be.
marek287 said:
With TWRP 2.8.1.0 it installs but these TKruzze gapps (https://s.basketbuild.com/devs/TKruzze/Android 5.0 GApps/Micro-Modular GApps/) gives error
E: Error executing update binary zip "gapps location.zip"
INSTALLATION FAILURE: Your device does not have sufficient space available in
the system partition to install this GApps package as currently configured.
You will need to switch to a smaller GApps package or use gapps-config to
reduce the installed size.
Click to expand...
Click to collapse
You'll probably need even smaller gapps. Our system partition is getting very small as the base system size has increased a lot since gingerbread. I haven't tried any gapps yet as they are irrelevant to our roadblocker issues so I can't give any recommendations.
desire hd user said:
first i want to thank you for this amazing rom
and i want to ask if i update from doge 1 to doge 2 should i flash boot.img again after installing the rom
Click to expand...
Click to collapse
Yes, if you are S-ON. There are some kernel related changes which are included in the boot.img so it needs to be updated too.
Mustaavalkosta said:
Try to format your system partition manually. If that doesn't help, contact 4EXT dev. Generally I can't fix recovery related issues like this seems to be.
Click to expand...
Click to collapse
That was mine second throught but main goal was to anounce others that problem. I posted it to 4EXT recovery Q/A threat
http://forum.xda-developers.com/showpost.php?p=57171180&postcount=2
and recontacted (PM) to jrior001 TWRP recovery partition bug.
rom not working
help me. Excuse, but apparently I'm the only one that failed to install the rom.
during installation sticking a message like warnig and then something about the sound and would not start more
I've already checked MD5
DOGE2 + PA GApps ALPHA1 flash succeeded
Thank you Musta and the team for great job!
http://forum.xda-developers.com/showthread.php?p=56560109
I flashed DOGE2 + PA GApps ALPHA1, and they work fine.
(cm-12-20141130-UNOFFICIAL-DOGE2-ace.zip + pa_gapps-micro-5.0-ALPHA1-20141117a-signed.zip)
Before flashing, I made .gapps-config which containing the text "NanoGApps", and placed it in the same folder as the GApps zip.
Then, flashing has succeeded.
I didn't try "PicoGApps" option, but it will also succeed, I suppose.
matbeta said:
help me. Excuse, but apparently I'm the only one that failed to install the rom.
during installation sticking a message like warnig and then something about the sound and would not start more
I've already checked MD5
Click to expand...
Click to collapse
Install TWRP 2.8.1.0 then install the rom again. http://forum.xda-developers.com/showthread.php?t=2780164
After downloading writes: "sim card added restart your device".
bratmarat said:
After downloading writes: "sim card added restart your device".
Click to expand...
Click to collapse
Yeah, it's a bit wonky. Just hit back to skip it for now. Telephony code is still undergoing some changes.
Very good job. I wait for doge3
hello Mustaavalkosta, Great job, say thanks to you and all the dev team.
I am chinese user, i found doge 3 always crash when i install most common app.
such as baidunews, baidu market, zhihu
please check it, hope doge 4 coming as soon as possible.