I have the S3 sgh-i747m which I guess corresponds to the d2att version. I rooted my phone with odin and that installed the clockworkmod as well. I tried to install cyanogenmod via the installer but then I ran into the "root may be lost, fix?" message at the end, and no matter what I chose the phone always reverted back to stock. I deleted all instances of KNOX wtihout backup using bloat free (read somewhere that this might be the problem) , but to no avail the issue is still persistent. I then tried to manually install it by downloading the zip version adding it to the sd card and wiping user data/cache/dalvik cache but then when I tried to install from the zip (I also tried it with the d2att paranoid android zip) the android on the screen would drop with the red logo after a few lines of code and say "operation aborted."
What is the issue here and how do I install either cm or pa on my phone?
What is the error message displayed on your screen when the install fails?
Are you using the latest CWM? You should flash ROMs for the d2lte.
Yes, it's the latest package I got from their site cm-11-20140217-NIGHTLY. Also fwiw, everytime I go into recovery mode now the cm blue man appears with the samsung logo (I'm guessing from their one click installer which said it was successful even though following the reboot message it reverted back to stock). The full message I'm getting is:
...
Installing update...
assert failed: getprop("ro.bootloader") == "I747
UCDMG2" | | getprop("ro.bootloader") == "I7
47UCUEMJ2" | | getprop("ro.bootloader") ==
"I747UCUEMJB" | | getprop("ro.bootloader")
== "I747MVLDMF1" | | getprop("ro.bootloader")
== "I747MVLUEMK5" | | getprop("ro.bootloader")
== "I747MUMUEMK3"
E: Error in /storage/sdcard1/cm-11-20140217-NIGHTLY-d2att.zip
(Status 7)
Installation aborted.
So you mean I should use the d2lte package instead of d2att? Because on their site I saw that my model corresponded with the d2att package.
You should be flashing d2lte ROMs, not d2att or d2can.
You are getting an assert error because your bootloader may not be supported. What is the bootloader or baseband on your phone?
Are you running the latest CWM?
audit13 said:
You should be flashing d2lte ROMs, not d2att or d2can.
You are getting an assert error because your bootloader may not be supported. What is the bootloader or baseband on your phone?
Are you running the latest CWM?
Click to expand...
Click to collapse
My cmw recovery is v6.0.4.7
So I should try it with this package then? download.cyanogenmod.org/?device=d2lte
Yes.
ROMs for the d2can and d2att were unified under d2lte. ROMs labelled as being for a d2att or d2can could be considered "old" in the s3 Android world.
Wow thanks a bunch, that was the issue. Posted this on the cyanogenmod forums 2 days ago and nobody answered with any input.
You're very welcome. We're all here to share our experience and knowledge so everyone can learn and help others:victory:
Also was thinking of changing the cm11 kernel to something that allows the device to be overclocked to 1800mhz or so, since this one goes to 1500 only. Are there any current inherently superior kernels out there working with the cm11 version that are worth switching to? (since from a quick search I see most of these have only been tested with cm10). Or is it better to not mess with it and leave it as is, since the only 2 uses I want is to underclock for battery life, which you already have, and overclocking since before I had some apps running slow (but again don't know if the boost to 1800 is a huge step up, and whether at the same time there are any risks of crashing or something running it at this speed).
I'm can't recommend a particular kernel since I tend to leave things as is. The only thing I change under performance tweaks is settings the phone to ondemand and noop.
Since you are running CM11, you must ensure the kernerl is for CM11 and not AOSP.
Related
i'm getting a very strange error when trying to flash any 4.03 rom. so far i've tried buglessbeast, and codename android, also a rom from p3droid, and he fixed the error when removing the line from the build.prop
assert failed: getprop("ro.product.device") == "
maguro" || getprop("ro.build.product") ==
"maguro"
E:Error in /sdcard/pete_maguro_ota_02-17-12.zip
(Status 7)
Installation aborted
evidently if you remove the line from the build.prop as p3droid did it can be fixed. but i don't want to have to ask every single dev to do this just for me,
and obviously theres something up with my device thats screwing this up.
so how can i make my device work here.
I had/have android revolution hd installed right now, but i am making sure to do a full wipe through CWM before flashing the new roms
Are you running a Touch Enabled beta version of CWM by any chance?
MArk.
mskip said:
Are you running a Touch Enabled beta version of CWM by any chance?
MArk.
Click to expand...
Click to collapse
yes i am. 5.044 i think i know it's beta.
neok44 said:
yes i am. 5.044 i think i know it's beta.
Click to expand...
Click to collapse
That error is consistent with an earlier beta of Touch CWM but was fixed in the latest version.
Flash 5.8.0.2 either from zip or via my ToolKit which includes it and it should fix your flashing problems
Mark.
mskip said:
That error is consistent with an earlier beta of Touch CWM but was fixed in the latest version.
Flash 5.8.0.2 either from zip or via my ToolKit which includes it and it should fix your flashing problems
Mark.
Click to expand...
Click to collapse
fixed everything. thanks!
I'm rooted multiple devices, and while the process is rarely an easy straight shot for me, this sprint gs2 of my wife's has proven to be my hardest. I've managed to at this point get it rooted though oden plus get cwm installed on it through oden as well.
Now my issue is whenever I try to install cm through cwm I'm getting the same error, regardless of if it's cm7, 9, and 10.
It is as follows:
-- Installing: /sdcard/cm-9.1.0-epicmtd.zip
Finding update package...
Opening update package...
Installing update...
assert failed:
getprop("ro.product.device") == "epic" ||
getprop("ro.build.product") == "epic" ||
getprop("ro.product.device") == "epicmtd" ||
getprop("ro.build.product") == "epicmtd" ||
getprop("ro.product.device") == "SPH-D700" ||
getprop("ro.build.device") == "SPH-D700"
E:Error in /sdcard/cm-9.1.0-epicmtd.zip
(Status 7)
Installation aborted.
If I try to have rom manager install it from within the app, it gets stuck at the point where I tell it yes, reboot into recovery.
I've gotten to the point of being able to use cwm after quite a bit of non-straightforward steps, mostly revolving around walkthroughs and zip references that referred to older ota builds.
Not complaining, just saying the point I'm out now is not as reliable as I'd like it to be.
I'm pretty familiar with pulling logs, not so familiar with adb but fine with command prompt. I'll be happy to try whatever anyone thinks of and if someone has the time I'd be happy to webcast the screen as I follow someone's instructions.
PS. I did find this explanation as a possible cause of the issue so food for thought -
http://forums.androidcentral.com/ep...p-fixing-wifes-phone-root-rom-sd-problem.html
Its been quite some time since I've messed with the Epic 4g but you flashed to the EpicMTD ROM. When you did this you changed your phones file partitioning to a completely different format.
In simple terms the Epic 4g and most devices of its time comes formatted in RFS format and along came EXT 4 format with many custom ROMs which allowed faster write times, speed improvements etc. Then they discovered this MTD format which again changes things.. I believe the problem your running into is when the device was formatted over to this MTD your having issues doing restores and such because your old recovery data is in RFS or EXT 4 format. Bottom line it won't work.
You will have to use the guide below to restore your device back a working state and remove the MTD formatting.
Thanks
Flash through odin the el26 repack from chris41g. I believe the format of system is what is causing that as well. I use the twrp packed up by chris which can be foumd on goo.im personally. Has never resulted in a brick. For me.
sent from MY BAD A$$ ET4G
are you sure you're using ROMs for the sph d710?
Also, rom manager apparently bricks this phone...don't use it
yea you're definitely using the wrong ROMs...note that there is an epic 4g and epic 4g touch
best way to flash a rom (unless stated otherwise in OP of ROM)
install odin
download el26 cwm kernel http://www.mediafire.com/?hkydca9ob98z89m
turn ur phone off. hold volume down and power to get into download mode
once in download mode plug it in pc (make sure drivers are installed)
open odin
click pda option and select that el26 cwm
hit start
after it finishes and the phone starts to reboot hold volume up and power
you'll be in cwm recovery.. from there clear data clear cache clear dalvik cache
flash ROM
flash gapps if u want
reboot
Your flashing roms for the wrong device. Sph-d700= epic4g/galaxy s sph-d710=epic 4g touch/galaxy s2
We are legion, for we are many
replies to op
Thanks everyone. I'll start from the top and work my way down. I'll go search this sub-forum for the specific packages you mentioned, and then google if that doesn't work. If you know they are hard to find or there are variations that I might choose accidentally, please pm or post up the page/link you would go to for it. Know that sounds needy, but like I said I've managed to find only half-right walkthroughs thus far, so apparently I'm not too bright.
Thanks
Read evils post. I didn't even notice that.
sent from MY BAD A$$ ET4G
got it done
okay I went back, started from the beginning again with
SPH-D710.FF18_CL663858_ROOTED-OneClick to redo the root (yeh, I know, once it's rooted it's rooted so no need, but I like to trial and error with similar starting points)
then use odin3 v1.85 from GalaxyS2Recovery.zip to install CWM
- this time I knew about the pageup, pagedown, pageup, pagedown to unlock the power button - I didn't last time and resorted to installing AGAT's recovery, which may have confused the process
used the cm build and gapps from http://e4gtcm.blogspot.com/ and was able to get it to install
- even though I did a [factory wipe, wipe partition, wipe dalv cache, and wipe batt stats], it got stuck on the cm animation, so did the [ ] again and I made it in
one question - with my htc hero, gs3, and different tablets, there was a steady stream of builds...nightlies, stables, etc
with this phone I'm seeing almost nothing now that I'm search for d710...is this device not that heavily developed for? thanks
idk if you know but there are tons of ROMS for this phone on XDA
a thread title with [ROM] in it means it's a ROM
go here..
http://forum.xda-developers.com/forumdisplay.php?f=1734
http://forum.xda-developers.com/forumdisplay.php?f=1284
So I am an HTC owner but doing some root & ROM work for a friend of mine. Normally, I load a ROM onto the SD card, boot into recovery, wipe, flash zipped ROM from SD card, reboot, enjoy. However, The GS3 I am working on does not recognize the SD card within recovery. Everytime I try to flash a ROM (CM10 & MIUI thus far) none of them work. I get the following when trying to flash:
-- Installing /sdcard/miuiandroid_d2tmo_jb-3.1.11.zip
Finding Update package
Opening update package
Installing Update
assert failed: getprop("ro.product.device") == "d2tmo" || getprop("ro.build.product) == "d2tmo"
E: Error in /sdcard/miuiandroid_d2tmo_jb-3.1.11.zip
(Status 7)
Installation Aborted
Now, this tells me that my download is corrupt somehow. However, I get this exact same message when trying to flash CM10. Furthermore, both ROMs were acquired directly from the dev download links. Has anyone else had a similar problem and can provide a solution?
Update CWM. Link in my signature.
Aerowinder said:
Update CWM. Link in my signature.
Click to expand...
Click to collapse
Wow! I feel like a moron! I use TWRP on my LTEvo so it has been a long time since I've even touched CWM. Looks like the update did the trick. Flashed MIUI and accompanying gapps perfectly! Thank you!
One more question, is there a generic gapps that I can flash across ROMs or no? For instance, I have the gapps that was posted next to MIUI. However, I'd like to see how CM10 runs. Am I able to flash the gapps posted with MIUI or is there a specifically designed gapps file for CM10? I ask because with the Evo gapps are generic and can be interchanged with AOSP ROMs.
1. I own three Samsung Galaxy S3 SGH-i747m. I was able to successfully Odin flash TWRP or ClockworkMod recoveries on all of them. Then install my preferred CyanogenMod 10.1.3 stable.
2. Problem is on the third phone purchased from Rogers network late 2012 so firmware is likely a bit more outdated. I can only flash CyanogenMod 10.0.0 on it. Anything newer fails
3. 20130812 gapps installs just fine.
4. Below are the phone details and errors in TWRP and ClockworkMod as I've tried using both recoveries.
5. I desperately need help to figure out what is stopping CyanogenMod 10.1.3 from installing on this phone. I used the exact same package on the other two phones and worked great.
About Phone
Android version 4.1.2
Baseband version I747MVLUEMK5
Kernel version 3.0.48-cyanogenmod-ge67063c
[email protected] #1
Tue Nov 13 08:44:53 PST2012
CPU ARMv7 Processor rev 4 (v7I)
Memory 1622 MB
CyanogenMod version 10.0.0-d2att
Build date Tue Nov 13 08:31:49 PST 2012
Build number cm_d2att-userdebug 4.1.2 JZO54K eng.20121113.083104 test-keys
ClockworkMod Recovery v6.0.4.5
Finding update package...
Opening update package...
Installing update...
E:Error in /data/media/cm-10.1.3-d2att.zip
(Status 6)
Installation aborted.
Team Win Recovery Project v2.6.3.1
Wipe Davlik and Cache
Installing '/external_sd/cm-10.1.3-d2att.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
E:Error executing updater binary in zip '/extern
Error flashing zip '/external_sd/cm-10.1.3-d2att
Updating partition details
Failed...
exhaust2000 said:
1. I own three Samsung Galaxy S3 SGH-i747m. I was able to successfully Odin flash TWRP or ClockworkMod recoveries on all of them. Then install my preferred CyanogenMod 10.1.3 stable.
2. Problem is on the third phone purchased from Rogers network late 2012 so firmware is likely a bit more outdated. I can only flash CyanogenMod 10.0.0 on it. Anything newer fails
3. 20130812 gapps installs just fine.
4. Below are the phone details and errors in TWRP and ClockworkMod as I've tried using both recoveries.
5. I desperately need help to figure out what is stopping CyanogenMod 10.1.3 from installing on this phone. I used the exact same package on the other two phones and worked great.
About Phone
Android version 4.1.2
Baseband version I747MVLUEMK5
Kernel version 3.0.48-cyanogenmod-ge67063c
[email protected] #1
Tue Nov 13 08:44:53 PST2012
CPU ARMv7 Processor rev 4 (v7I)
Memory 1622 MB
CyanogenMod version 10.0.0-d2att
Build date Tue Nov 13 08:31:49 PST 2012
Build number cm_d2att-userdebug 4.1.2 JZO54K eng.20121113.083104 test-keys
ClockworkMod Recovery v6.0.4.5
Finding update package...
Opening update package...
Installing update...
E:Error in /data/media/cm-10.1.3-d2att.zip
(Status 6)
Installation aborted.
Team Win Recovery Project v2.6.3.1
Wipe Davlik and Cache
Installing '/external_sd/cm-10.1.3-d2att.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
E:Error executing updater binary in zip '/extern
Error flashing zip '/external_sd/cm-10.1.3-d2att
Updating partition details
Failed...
Click to expand...
Click to collapse
Download total commander from the play store. Then open the rom using that app. Rom/META-INF/com/google/android and edit updater-script and remove the line with the smileys and the at&t code thing. then save and flash the rom. I experienced the same problem before, but that technique fixed it.
Weird because your baseband is 4.3 and your OS is 4.1.2.
http://www.sammobile.com/firmwares/1/?model=SGH-I747M&pcode=RWC#firmware
Did not work
So far none of the suggestions made a difference. I'm still stuck with CyanogenMod 10.1.0. Is it possible to get more help on this? Step by step instructions would be much appreciated. I'm stuck Thanks!
I would use the latest version of Philz Touch from here: http://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2att Download the zip version and install it from CWM.
Boot into CWM, then wipe cache, system, data, dalvik, and flash the ROM. Boot into the ROM, set things up, boot into CWM, flash GAPPs.
PhilZ Touch 6 also fails
I followed these steps flashed and booted into PhilZ Touch 6 but still errors out
PhilZ Touch 6
Clockworkmod v6.0.4.7
Installing: /storage/sdcard1/cm-10.1.3-d2att.zip
Finding update package...
Opening update package...
Installing update...
assert failed: getprop("ro.bootloader") == "I747UCDLK3" ||
getprop("ro.bootloader") == "I747UCDMG2"
getprop("ro.bootloader") == "I747MVLDLK4"
getprop("ro.bootloader") == "I747MVLDMF1"
getprop("ro.bootloader") == "I747MUMBLK3"
getprop("ro.bootloader") == "I747MUMBLL1"
E:Error in /storage/sdcard1/cm-10.1.3-d2att.zip (Status 7)
Installation aborted
press any key to continue.
I also tried editing the updater-script text file by deleting the first line but it errors out too with (Status 6).
assert(getprop("ro.product.device") == "d2att" || getprop("ro.build.product") == "d2att");
I don't want to give up as the cm-10.0.0-d2att.zip on it has problem connecting to camera. The camera cannot be used. Thanks please let me know what else I can try.
Instincts tell me that I have to get to the bottom of why my baseband is 4.3 and OS is 4.1.2 just like what Audit13 commented. I'm still puzzled and stuck why that is the case and how to get around "force" flashing a newer cm-10.1.13-d2att. Help please!
You bootloader isn't listed in the updater script. Try flashing CM11.
CM-11 flashed but new problems introduced
audit13 said:
You bootloader isn't listed in the updater script. Try flashing CM11.
Click to expand...
Click to collapse
What a great tip, I was finally able to install a newer cyanogenmod on my d2att.
Downloaded cm-11-20140210-SNAPSHOT-M3-d2att.zip
Camera works most of the time but there is now a new bigger problem. Phone battery overheats daily and discharges instantly from full to low batt and shuts down. I'm going to try the latest nightly.
Apologies for bringing a dead thread back alive, hoping someone can help me. I want to install 10.1.3 but my bootloader is at I747MVLUEMK5. Can I edit the updater script to include this bootloader and then try the install? I don't know if that would mess anything up. If anyone could shed some light on it that'd be great.
The reason for doing this: Wireless Display is crashing on 10.2.1 with my phone but my buddy who has his S3 on 10.1.3 is able to share his screen with my smart TV without any issues. If there is a workaround that'd be great too.
Thanks !
imran025 said:
Apologies for bringing a dead thread back alive, hoping someone can help me. I want to install 10.1.3 but my bootloader is at I747MVLUEMK5. Can I edit the updater script to include this bootloader and then try the install? I don't know if that would mess anything up. If anyone could shed some light on it that'd be great.
The reason for doing this: Wireless Display is crashing on 10.2.1 with my phone but my buddy who has his S3 on 10.1.3 is able to share his screen with my smart TV without any issues. If there is a workaround that'd be great too.
Thanks !
Click to expand...
Click to collapse
If the bootloader is not supported, I do not advise editing the updater script to include your bootloader. Development of 10.1 probably stopped before the 4.3 bootloader was made available to the general public.
imran025 said:
Apologies for bringing a dead thread back alive, hoping someone can help me. I want to install 10.1.3 but my bootloader is at I747MVLUEMK5. Can I edit the updater script to include this bootloader and then try the install? I don't know if that would mess anything up. If anyone could shed some light on it that'd be great.
The reason for doing this: Wireless Display is crashing on 10.2.1 with my phone but my buddy who has his S3 on 10.1.3 is able to share his screen with my smart TV without any issues. If there is a workaround that'd be great too.
Thanks !
Click to expand...
Click to collapse
How do you do to share your screen in cm10.1.3 i have a lg smart tv and also share videos & pictures using wifi direct in stock rom.
Enviado desde mi SAMSUNG-SGH-I747 mediante Tapatalk
I'm trying to install StockMOD ROM using the instructions here: http://forum.xda-developers.com/showthread.php?t=2504903
I flash the modem, do a factory reset, flash the ROM, then flash the insecure kernel. When I reboot, I get stuck on the SG3 load screen and it won't go any further. I've left it sitting for over 15 minutes, so I'm pretty sure it's stuck. I tried rebooting, but I still get stuck. I've also repeated the instructions 3 times so far with the same results. I also redownloaded the ROM to make sure there weren't any problems (the download is 1.14GB on both)
One thing that I've noticed is when I install the ROM, the AROMA loads fine and I'm able to make all of my selections. When I install, it finishes within a couple of seconds. It says it successfully installed, but I get the message: assert failed: getprop("ro.product.device") == "d2tmo" ||
get prop("ro.build.product") == "d2tmo" || get prop("ro.build.product") == "d2att" || get prop("ro.build.product") == "d2att" || get prop("ro.build.product") == "d2att"
Has anyone else had this problem? I'm running a rooted AT&T Galaxy S3, coming from CM11. My CWM is v6.0.4.7 if it matters. I have the stock boot loader.
Can @saranhai or someone else on Team Inferno give me a little help?
Thanks.
It's not installing properly because your device is not supported. Did you try deleting the assert lines from the updater script to see if that helps?
audit13 said:
It's not installing properly because your device is not supported. Did you try deleting the assert lines from the updater script to see if that helps?
Click to expand...
Click to collapse
That's the updater script in META-INF\com\google\android? I'll try that.
Thanks!
That did it. Thanks!
kragar00 said:
That's the updater script in META-INF\com\google\android? I'll try that.
Thanks!
Click to expand...
Click to collapse
That's it. Glad you got it to work.