Develop Bugs

Various CM versions wont flash to sgh 1747

I am trying to flash Cm10 preview, Cm9 nightly, or cm10 jellybro by euroskank. After flashing this to the root of internal storage and booting into recovery and installing zip from sd card during the installation im getting an error that reads:
-- installing: /emmc/cm-10-20120803.1630-SKANK-D2att.zip (varies on different builds of course)
- Finding update package...
- Opening update package...
- Installing update package...
assert failed: getprop("ro.product.device")=="
d2att" I I getprop("ro.build.product") == "d2att"
E: Error in /emmc/cm-10-20120803.1630-SKANK-D2att.zip
(status 7)
installation aborted
Does anyone have any ideas about this? I have successfully flashed a few other roms and really would like a CM build any help would be greatly appreciated
Thanks Garrett

Update your recovery using ROM Manager.

I have the same problem. Tried to edit my build.prop but still won't flash

Charleszan said:
I have the same problem. Tried to edit my build.prop but still won't flash
Click to expand...
Click to collapse
Why are you editing your build.prop?
Just update your recovery ..

I have the latest version already from this thread http://forum.xda-developers.com/showthread.php?t=1737446
---------- Post added at 11:42 PM ---------- Previous post was at 10:56 PM ----------
Rom manager shows me a list to confirm my phone model but it isn't in there.
BUT! I found a work around.
The updater-script checks if "ro.product.device" or "ro.build.product" is "d2att".
Those of us having the issue OP described have "ro.product.device" = "d2spr"
So you can open the flashable CM zip file, go in META-INF\com\google\android edit updater-script and replace d2att by d2spr.
Booted in CM10 Jellybro right now [uploading latest Jellybro build if someone needs it]
---------- Post added 4th August 2012 at 12:14 AM ---------- Previous post was 3rd August 2012 at 11:42 PM ----------
Here's the modified zip file
https://www.dropbox.com/s/lcdijd68eavgecf/cm-10-20120803.1630-SKANK-d2att.zip

Charleszan said:
I have the latest version already from this thread http://forum.xda-developers.com/showthread.php?t=1737446
---------- Post added at 11:42 PM ---------- Previous post was at 10:56 PM ----------
Rom manager shows me a list to confirm my phone model but it isn't in there.
BUT! I found a work around.
The updater-script checks if "ro.product.device" or "ro.build.product" is "d2att".
Those of us having the issue OP described have "ro.product.device" = "d2spr"
So you can open the flashable CM zip file, go in META-INF\com\google\android edit updater-script and replace d2att by d2spr.
Booted in CM10 Jellybro right now [uploading latest Jellybro build if someone needs it]
---------- Post added 4th August 2012 at 12:14 AM ---------- Previous post was 3rd August 2012 at 11:42 PM ----------
Here's the modified zip file
https://www.dropbox.com/s/lcdijd68eavgecf/cm-10-20120803.1630-SKANK-d2att.zip
Click to expand...
Click to collapse
Thanks for the heads up I have been wondering what d2att was referring too. I tried to do what you said by replacing d2att by d2spr and it still failed. I downloaded your zip file, my question is does it have the necessary changes for flashing? Thanks for your help.

Thanks for all the help everyone I will try these suggestions when I get home and report back!

Thanks for the zip file, I went ahead and flashed the rom on my ROGERS GS3 and it works. I appreciate you creating the zip file for us. Hopefully you release more when updates occur or post instructions on how we can do it ourselves since I had issues. For anyone who is installing this ROM here are inverted GAPPS with google now which kills SIRI and that silly iphone.
https://www.dropbox.com/s/0rnx097of6nxol0/inverted_gapps2-jb-20120715.zip

From what I understand, the various devs are still in the process of unifying our devices and installation process but there is still a couple of thing that are different on the canadian models.
If I'm not mistaken, the d2att and d2spr are values stocked in the recovery that helps identify our device (d2att SIII from AT&T, d2spr SIII from sprint etc). Now here you can find a zip file you can flash that will simply tell you what your "ro.product.device" or "ro.build.product" value is. (Post #124) It might be different than d2att or d2spr. Write it down.
Take whatever rom you want to flash. Open it with winrar or 7zip and go in META-INF\com\google\android. You will find the "updater-script" file there. Copy it to your desktop and delete the one in the archive.
Now it is a simple text file, you should be able to open it in notepad or whatever. Simply change "d2att" on the first line and replace it by the one found earlier.
Copy it in the archive where the file is supposed to be (META-INF\com\google\android).
It will flash
Hope this helps.
EDIT
Turns out neubauej is right. I had an old CWM recovery. You can see the version when in recovery mode. I had the same issue trying to flash from TWRP though.

ggranson91 said:
I am trying to flash Cm10 preview, Cm9 nightly, or cm10 jellybro by euroskank. After flashing this to the root of internal storage and booting into recovery and installing zip from sd card during the installation im getting an error that reads:
-- installing: /emmc/cm-10-20120803.1630-SKANK-D2att.zip (varies on different builds of course)
- Finding update package...
- Opening update package...
- Installing update package...
assert failed: getprop("ro.product.device")=="
d2att" I I getprop("ro.build.product") == "d2att"
E: Error in /emmc/cm-10-20120803.1630-SKANK-D2att.zip
(status 7)
installation aborted
Does anyone have any ideas about this? I have successfully flashed a few other roms and really would like a CM build any help would be greatly appreciated
Thanks Garrett
Click to expand...
Click to collapse
I HAD THIS SAME ISSUE EVERTIME I TRIED TO FLASH ANY CM10 ROM! As for any other rom they all worked. This was using cwm recovery as per usual. I was advised some of the above options but changing to TWRP RECOVERY was best. Now mind u I had bit of issue getting it installed on my phone cuz I dont have the at&t model but good ol terminal emulator worked and now I have the beautiful touchscreen capable twrp recovery and ALL my problems flashing vanished!! And I was able to flash any and all CM10 JB ROMS with no damn Assert failed errors!
Some of the above options suggested will work but if u can get TWRP on your phone u could probably get around this issue in a flash! Lol and get a better recovery module to boot. Good luck
Sent from my SGH-I747M using xda premium

Charleszan said:
From what I understand, the various devs are still in the process of unifying our devices and installation process but there is still a couple of thing that are different on the canadian models.
If I'm not mistaken, the d2att and d2spr are values stocked in the recovery that helps identify our device (d2att SIII from AT&T, d2spr SIII from sprint etc). Now here you can find a zip file you can flash that will simply tell you what your "ro.product.device" or "ro.build.product" value is. (Post #124) It might be different than d2att or d2spr. Write it down.
Take whatever rom you want to flash. Open it with winrar or 7zip and go in META-INF\com\google\android. You will find the "updater-script" file there. Copy it to your desktop and delete the one in the archive.
Now it is a simple text file, you should be able to open it in notepad or whatever. Simply change "d2att" on the first line and replace it by the one found earlier.
Copy it in the archive where the file is supposed to be (META-INF\com\google\android).
It will flash
Hope this helps.
EDIT
Turns out neubauej is right. I had an old CWM recovery. You can see the version when in recovery mode. I had the same issue trying to flash from TWRP though.
Click to expand...
Click to collapse
I went through your instructions and still had no success flashing the new CM10 that was updated on august 04. I flashed the tool to find out what build and product and it showed d2spr for both. I replaced the d2att in the zip file on the first line and flashed with an error 6. I tried replacing just one of the two and still a error 6. I flashed from my external memory card. I had zero troubles with your edited file which seems strange as I am doing the same things you are I assume.
Thanks for your help

Updated cwm via rom manager, problem fixed! Thanks for the support!

need help flashing

i need help!
i downloaded the rom(the miui rom). pushed it to sd card.
went to recovery, wiped cache, dalvic cache, factory reset, and went to system/format.
next i flashed the rom and it gave me an error having to do with the zip. and aborted!
i rebooted the phone and now it doesnt get past the "samsung galaxy s3" screen. i can turn it off but nothing happens after i turn it on, it just doesnt get past the logo screen!
i was coming from stock.
any help!??!
---------- Post added at 11:01 PM ---------- Previous post was at 10:53 PM ----------
im getting this message once i try to flash this rom:
error in /sdcard/miuiandroid_d2att-2.9.29.zip (status 7) aborted
---------- Post added at 11:02 PM ---------- Previous post was at 11:01 PM ----------
im getting this message once i try to flash this rom:
error in /sdcard/miuiandroid_d2att-2.9.29.zip (status 7) aborted
---------- Post added at 11:05 PM ---------- Previous post was at 11:02 PM ----------
so if im stuck at the logo screen and i need to update my cwm, how would i b able to do that since my phone doesnt even boot up?
i have the tool kit, idk if that would help

You can flash this recovery with Odin http://db.tt/QYcH2jBM
That's a 6.0.1.2 version for att. Its not a touch version but it's the only one I found that you can flash with Odin and it works.

THANK YOU SO MUCH !!! it seems to b working. i flashed it and now flashed the rom! it works! thankSS!!!!!!!!!!!!!
i have been out of a phone for the last 2 hours! thanks!!!

Please help me, guys. Afraid I turned my phone into an expensive brick.

Long story short, little to no knowledge of phone related stuffs, I had my phone rooted and whatnot. Wanted to increase personalization and features, so I unlocked the bootloader, installed TWRP and tried flashing the CM nightly rom.
But after wiping everything, including the system partition, my Zenfone2 (ZE551ml WW version) simply refuses to flash anything zipped. It gives me the "E: Error executing updater binary in zip 'file name.zip'.
I tried flashing different TWRP images and it works. Can you guys guide me on how to restore my Zenfone 2 to its stock version? Apparently it refuses to flash any zip files, I am trying right now to flash the stock firmware provided by Asus but it gives me some error related to WW version and also the above error...
ADB sideload also doesn't work. Please guys help me, I am kind of desperate.

Flash through bootloader, read the thread for changing from CN to WW, it will give you complete instructions for flashing
Sent from my ASUS_Z00AD using Tapatalk
---------- Post added at 10:36 PM ---------- Previous post was at 10:34 PM ----------
Thread by vivid, I would post the link but can't copy the link from tapatalk
Sent from my ASUS_Z00AD using Tapatalk

I followed the guide here http://forum.xda-developers.com/zenfone2/help/how-to-upgrade-cn-version-to-ww-t3101556 but now my device is stuck on the "Asus in search of incredible" screen for like 30 minutes..

Hawtpants said:
I followed the guide here http://forum.xda-developers.com/zenfone2/help/how-to-upgrade-cn-version-to-ww-t3101556 but now my device is stuck on the "Asus in search of incredible" screen for like 30 minutes..
Click to expand...
Click to collapse
Select wipe data/factory reset, followed by wipe cache partition in recovery mode after performing adb sideload. Then, restart your phone. This worked for me.

[SOLVED] Can't boot into System

I can't boot into system after flashing a bad ROM. Using 'fastboot reboot' doesn't work, nor does reboot from recovery. Rebooting brings me into the recovery. I tried restoring my backup, but once it gets to 100%, TWRP freezes, and I can't navigate through TWRP.
I really need help!! PLEASE HELP!

Can you get into the bootloader?

Rogue8o8 said:
Can you get into the bootloader?
Click to expand...
Click to collapse
Yes

Why not try and revert back to stock recovery then sideload one of the Official Stock ROMs...that tends to fix everything normally...you'll need to backup your data.
---------- Post added at 02:43 AM ---------- Previous post was at 02:40 AM ----------
https://forum.xda-developers.com/oneplus-3/development/toolkit-oneplus-3-toolkit-unlock-t3398799
Use this toolkit
---------- Post added at 02:52 AM ---------- Previous post was at 02:43 AM ----------
Some easy tools but for this, I think all you'll need is to flash stock recovery then follow the instructions on the OP site to sideload 3.2.8
http://downloads.oneplus.net/oneplus-3/oneplus_3_oxygenos_3.2.8/
The Download link is also on the same page
Your bootloader will remain unlocked....after the phone boots, you can flash TWRP again and then SuperSu to get root on that ROM

Rogue8o8 said:
Why not try and revert back to stock recovery then sideload one of the Official Stock ROMs...that tends to fix everything normally...you'll need to backup your data.
---------- Post added at 02:43 AM ---------- Previous post was at 02:40 AM ----------
https://forum.xda-developers.com/oneplus-3/development/toolkit-oneplus-3-toolkit-unlock-t3398799
Use this toolkit
---------- Post added at 02:52 AM ---------- Previous post was at 02:43 AM ----------
Some easy tools but for this, I think all you'll need is to flash stock recovery then follow the instructions on the OP site to sideload 3.2.8
http://downloads.oneplus.net/oneplus-3/oneplus_3_oxygenos_3.2.8/
The Download link is also on the same page
Your bootloader will remain unlocked....after the phone boots, you can flash TWRP again and then SuperSu to get root on that ROM
Click to expand...
Click to collapse
Ok, I'll try that, thanks.
Maybe my boot partition is corrupted? That could be why I'm unable to boot. If you could please upload the a backup of that partition?

Or is my bootloader corrupted? Since I can't boot into system through fastboot or the recovery, isn't it the bootloade's fault? It doesn't send the proper command, and thus it boots into the recovery instead of the OS.

My current connection isn't good enough for an upload. it could be the case but side loading a stock ROM will fix any issue. What ROM did you flash to get you into this situation?
---------- Post added at 03:36 AM ---------- Previous post was at 03:36 AM ----------
And what ROM were you coming from?

Try the most recent TWRP. https://forum.xda-developers.com/devdb/project/dl/?id=22429 I had my problems with a full recovery once, too. In my case it never recovered my /data partition though. If this fails you have to sideload a recent OOS Image by OFFICIAL recovery

What to do when you face TWRP Error 7

Every rom threads is being filled with people asking what to do with error 7. Same questions and same answers over and over.
The solution is simple and straightforward as below:
- Make sure you have latest TWRP.
- Make sure you have the right firmware.
All above can be downloaded if you look at 1st page of each rom threads. If not, go to Lineage 15.1 thread and get it from there.
Even with correct TWRP and firmware, you may still get error 7. In that case,
- Unmount (uncheck) System in TWRP.
I guarantee that those three will fix error 7 issues, especially the last part.

how to unmount twrp..?wrongly i deleted all data,caxhe system , and twrp cant install nothing, if i install linageos, it show error 7, if i instal an eui ZIP, it installs fastes (like 4 sec) and after boot to leeco logo...HELP.

error 7
Hello, I am new and french.
sorry for english do it by translator
I also have error 7 with los15.1 and I was in los14.1 before
I also tried the 3 methods but it did not work
I found on the internet a solution when you are sure to have the right rom
lineageosdownloads fix error 7
I can not link, I'm sorry again
so I looked for what was wrong with "META-INF »com» google »android» updater-script"
and that's the line that was not in the old rom
assert(leeco.verify_modem("2017-01-06 01:40:06") == "1");
I cleared this line and recompile and it works but I can not have the update
normal
who can tell me how it fits this line and how to fix thank you
---------- Post added at 08:04 PM ---------- Previous post was at 08:01 PM ----------
I deleted this line and it works but can not receive updates
who can tell me what this line is
and how to settle it thanks
---------- Post added at 08:14 PM ---------- Previous post was at 08:04 PM ----------
I bought it on grossoshop, 1year ago, there was 18s grossoshop rom I think and I went straight on los14.1
I'll have to put it back, put the 20s 26s
is it the bootlader that has changed? I am not an expert lol
it's not that I hope to help those who have x720

philourm2.0 said:
Hello, I am new and french.
sorry for english do it by translator
I also have error 7 with los15.1 and I was in los14.1 before
I also tried the 3 methods but it did not work
I found on the internet a solution when you are sure to have the right rom
lineageosdownloads fix error 7
I can not link, I'm sorry again
so I looked for what was wrong with "META-INF »com» google »android» updater-script"
and that's the line that was not in the old rom
assert(leeco.verify_modem("2017-01-06 01:40:06") == "1");
I cleared this line and recompile and it works but I can not have the update
normal
who can tell me how it fits this line and how to fix thank you
---------- Post added at 08:04 PM ---------- Previous post was at 08:01 PM ----------
I deleted this line and it works but can not receive updates
who can tell me what this line is
and how to settle it thanks
---------- Post added at 08:14 PM ---------- Previous post was at 08:04 PM ----------
I bought it on grossoshop, 1year ago, there was 18s grossoshop rom I think and I went straight on los14.1
I'll have to put it back, put the 20s 26s
is it the bootlader that has changed? I am not an expert lol
it's not that I hope to help those who have x720
Click to expand...
Click to collapse
Update your twrp.
Sent from my LEX727 using xda premium

mchlbenner said:
Update your twrp.
Sent from my LEX727 using xda premium
Click to expand...
Click to collapse
I have the newest Trwp (3.2.1-0 by codeworkx), installed 20s firmware from linage thread unmounted /system and still get error 7 (e1001). When i try to install a nougat or marshmallow based rom it either says system cant be unmounted (eventhough i did before) or says it was succesful, but i'm not able to boot. When trying to restore a backup i also cannot boot. Just the Leeco splash screen shows till it goes into recovery.

ok but I have twrp 3.2.1.0

give a trwp 3.1 or 3.0 and try los14.1

philourm2.0 said:
give a trwp 3.1 or 3.0 and try los14.1
Click to expand...
Click to collapse
When flashing LOS14.1 in twrp 3.0.2 it gets stuck at somewhere like 90% (Patching system image unconditionally)

Are you guys getting this error?
If you do update your firmware.
Go get it from codeworkx
Sent from my LEX727 using xda premium

Thanks for your help
I installed twrp-3.2.1-0-20180407-codeworkx-zl1 and still this error 7
it's the line
assert (leeco.verify_modem ("2017-01-06 01:40:06") == "1");
which makes me wrong if I delete it in meta-inf ok
in the forum lost15.1 official on xda, they say firmwaire 20s minimun in red
I have never been in official 20s it would not be that?
or find udapte.zip 20s x720
I can try to put back original, put back 3.2.1 trwp and flash for test
thanks
Storm, you're stuck in any case if I understood
try on the site grossoshop leeco the pro 3
there is an automatic tutorial to put in 18s grossoshop
nothing to lose
then you try los 14.1 ok

Fixed it
I actually got this: "E1001: Failed to update system image." followed by Error 7.
So, i don't know how but it just fixed itself. My ADB Drivers suddenly didn't work correctly and after reinstalling clockworkmods Universal ADB Driver it worked out of nowhere. It could also have been a false USB Port scince i also plugged my cable in somewhere else. Now I can flash anything without problems
Hope this helps...

problem solved my turn
for those who have an error 7 with oreo which is a problem identification
you need the firmwaire 20s minimum if you start the custom rom with 18s or 19s
and the solution and in the tutorial aicp 13
so it's not necessarily the trwp that's always the problem
but thanks for the help

I was having the same error 7.
I just reflashed to stock 20s and the problem was fixed

Ferdinantstr said:
how to unmount twrp..?wrongly i deleted all data,caxhe system , and twrp cant install nothing, if i install linageos, it show error 7, if i instal an eui ZIP, it installs fastes (like 4 sec) and after boot to leeco logo...HELP.
Click to expand...
Click to collapse
Same Here!!

millkyway4 said:
Same Here!![/QUOTE
Is this tread still alive?
Click to expand...
Click to collapse

I read through this post and couldn't get past the error 7 issue. I finally got it solved by updating TWRP to the latest version and then I could flash lineage15 via adb sideload. Thanks for another great, informative, thread from the people of XDA developers.