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!
Related
I recently installed cm10 on my fathers S3 and everything went smooth until root checker said I did not have root access. I dont see how I missed it, I used the steps from the guide on androidauthority.com as well as the steps from the links the guide provided to install clockworkmod and cm10. My S3 is rooted with cm10 with no issue. but my fathers isnt after the install when i used the same guide. Is there a way to root on cm10 without having to wipe and install the stock rom and then root?
simba33 said:
I recently installed cm10 on my fathers S3 and everything went smooth until root checker said I did not have root access. I dont see how I missed it, I used the steps from the guide on androidauthority.com as well as the steps from the links the guide provided to install clockworkmod and cm10. My S3 is rooted with cm10 with no issue. but my fathers isnt after the install when i used the same guide. Is there a way to root on cm10 without having to wipe and install the stock rom and then root?
Click to expand...
Click to collapse
Just reflash the CM10 zip, its pre-rooted. I don't know why its saying you're not rooted in the first place really. Do you see the "Superuser" app in the app drawer?
prscarp said:
Just reflash the CM10 zip, its pre-rooted. I don't know why its saying you're not rooted in the first place really. Do you see the "Superuser" app in the app drawer?
Click to expand...
Click to collapse
thats the weird part! haha I see super user, it opens and everything but it never pops up when i open apps that require root, and root checker says it isnt rooted. Ive wiped and installed CM10 twice, as well as the superuser.zip file the guide says to install with clockworkmod.
In the superuser app, try updating the su binary. Maybe that will fix it.
prscarp said:
In the superuser app, try updating the su binary. Maybe that will fix it.
Click to expand...
Click to collapse
I dont know why it fails but it doesnt like me getting root access. failed at: "gaining root access.... Fail!" when i clicked update
everything is green and says okay until gaining root access then i get the red fail! I took a screenshot but I dont have enough posts to insert the image
What recovery did you install?
I would redownload the CM10 zip, put it on your sd card, reboot into recovery, make a nandroid if you prefer, wipe system, dalvik, and cache, then flash the newly downloaded CM10 zip and gapps again.
This is definitely a strange problem lol
tonymtl said:
What recovery did you install?
Click to expand...
Click to collapse
the zip file says cm-10-20120925-NIGHTLY-d2att.zip
prscarp said:
I would redownload the CM10 zip, put it on your sd card, reboot into recovery, make a nandroid if you prefer, wipe system, dalvik, and cache, then flash the newly downloaded CM10 zip and gapps again.
This is definitely a strange problem lol
Click to expand...
Click to collapse
dang it didnt want to but oh well I'll give it a shot in a few. and yes very strange i never have the normal problems -__-
simba33 said:
the zip file says cm-10-20120925-NIGHTLY-d2att.zip
Click to expand...
Click to collapse
Thats the CM10 zip. Are you using clockwork mod recovery? or TWRP? I haven't had any issues with TWRP.
simba33 said:
dang it didnt want to but oh well I'll give it a shot in a few. and yes very strange i never have the normal problems -__-
Click to expand...
Click to collapse
As long as you dont wipe data you won't lose anything. The only effect this will have is, hopefully, fix root.
prscarp said:
Thats the CM10 zip. Are you using clockwork mod recovery? or TWRP? I haven't had any issues with TWRP.
As long as you dont wipe data you won't lose anything. The only effect this will have is, hopefully, fix root.
Click to expand...
Click to collapse
I'm using Clockworkmod recovery as advised by the guide.
ok i'll give it a shot in a few minutes
Did you flash any custom recovery ??? That cm10 doesn't install it. Also get a more recent cm10 at get.cm
---------- Post added at 01:21 PM ---------- Previous post was at 01:15 PM ----------
What version of cwm?
prscarp said:
Thats the CM10 zip. Are you using clockwork mod recovery? or TWRP? I haven't had any issues with TWRP.
As long as you dont wipe data you won't lose anything. The only effect this will have is, hopefully, fix root.
Click to expand...
Click to collapse
ok well i get an error:
assert failed: getprop("ro.product.device") == "d2att" || getprop("ro.build.product") == "d2att"
E:Error in /sdcard/cm-10-20121009-NIGHTLY-d2att.zip
(status 7)
installation aborted
I downloaded the 2nd latest which was added to the site yesterday from the other guys site he suggested. I got this same error on my phone and somewhere when googling someone said download notepad++ and erase the top line within the zip file and it installed for me. but i shouldnt have to do that. whats going on? i wiped everything you told me except factory/data
tonymtl said:
Did you flash any custom recovery ??? That cm10 doesn't install it. Also get a more recent cm10 at get.cm
---------- Post added at 01:21 PM ---------- Previous post was at 01:15 PM ----------
What version of cwm?
Click to expand...
Click to collapse
Yes i ave clockworkmod recovery and I downloaded that cm-10 a couple of weeks ago and I have root. its the same zip. but I downloaded the more recent, (2nd most recent on the site you referred) and it wont install as i stated in my previous post
simba33 said:
ok well i get an error:
assert failed: getprop("ro.product.device") == "d2att" || getprop("ro.build.product") == "d2att"
E:Error in /sdcard/cm-10-20121009-NIGHTLY-d2att.zip
(status 7)
installation aborted
I downloaded the 2nd latest which was added to the site yesterday from the other guys site he suggested. I got this same error on my phone and somewhere when googling someone said download notepad++ and erase the top line within the zip file and it installed for me. but i shouldnt have to do that. whats going on? i wiped everything you told me except factory/data
Click to expand...
Click to collapse
That has also never happened to me lol. Right before you flash the zip, select the "Toggle script asserts" option then try to flash.
A little explaination: When you go to flash the zip, it checks your current build.prop to make sure you're flashing the right rom to the right device. Since we wiped system before flashing, the build.prop is gone and it is unable to check. TWRP might not check which is why it has never happened to me. I don't know for sure that this is the case but I am just guessing.
You need to update recovery.
prscarp said:
That has also never happened to me lol. Right before you flash the zip, select the "Toggle script asserts" option then try to flash.
A little explaination: When you go to flash the zip, it checks your current build.prop to make sure you're flashing the right rom to the right device. Since we wiped system before flashing, the build.prop is gone and it is unable to check. TWRP might not check which is why it has never happened to me. I don't know for sure that this is the case but I am just guessing.
Click to expand...
Click to collapse
I tried the toggle idea and it didnt work, can you link me to a TWRP download? this is getting annoying lol I appreciate the help so far though
lol well this is annoying.
http://www.teamw.in/project/twrp2/104
Here is the link to TWRP for the AT&T SGS3. Grab the .img file near the bottom and flash it with fastboot. I assume you are familiar with fastboot?
fastboot flash recovery openrecovery-twrp-2.2.2.0-d2att.img
I love this recovery btw, so much easier to use than CWM
prscarp said:
lol well this is annoying.
http://www.teamw.in/project/twrp2/104
Here is the link to TWRP for the AT&T SGS3. Grab the .img file near the bottom and flash it with fastboot. I assume you are familiar with fastboot?
fastboot flash recovery openrecovery-twrp-2.2.2.0-d2att.img
I love this recovery btw, so much easier to use than CWM
Click to expand...
Click to collapse
uhm actually no im not familiar with it. ive heard of it but not sure how it works, i just tried doing my own research on it for about 20 minutes and still not sure how it works. can you point me in the right direction here?
You will need to get the android sdk, run it and install the tools. You should then have a platform-tools folder that includes fastboot.exe. place the recovery img in that directory, open a command prompt to that directory, put your phone in fastboot mode and run the command I wrote above.
Sorry about being brief about it, I'm on my phone right now. I can help more later when I'm at a pc.
prscarp said:
You will need to get the android sdk, run it and install the tools. You should then have a platform-tools folder that includes fastboot.exe. place the recovery img in that directory, open a command prompt to that directory, put your phone in fastboot mode and run the command I wrote above.
Sorry about being brief about it, I'm on my phone right now. I can help more later when I'm at a pc.
Click to expand...
Click to collapse
what is fastboot mode? is that download mode? lol sorry but I havent messed with fastboot at all. Ive rooted a bunch of phones and flashed quite a few but never worked with fastboot
I keep trying to install pacman rom into my galaxy s3 on tmobile tried every rom avilable on the page and nothing works keeps failing tried smoothliquid , and carbon rom and those install great. Not sure what i'm doing wrong
You need to update your bootloader
Sent from my SGH-T999 using Tapatalk 4 Beta
Read this.
http://forum.xda-developers.com/showthread.php?t=2282603
I recommend flashing the slightly older UVDLJC package. I think some people find aosp/cm based roms seem to run better with it.
Sent from my SGH-T999 using xda premium
Thanks i'll try your advice right away. I'll post a update on how it went.
I went ahead and followed your instructions went to the link i was sent and tried all 3 files but i got a status 7 and failed the installation. I will like to aplogize ahead of time i i'm a noob just learned how to root my phone a day ago but i spent 6 hours reading forums trying to figure this out before i posted.
roxus256 said:
I went ahead and followed your instructions went to the link i was sent and tried all 3 files but i got a status 7 and failed the installation. I will like to aplogize ahead of time i i'm a noob just learned how to root my phone a day ago but i spent 6 hours reading forums trying to figure this out before i posted.
Click to expand...
Click to collapse
No problem. So what's the error message?
ok so i download this file : Flashable UVDMD5 Bootloader / Firmware / Modem update.zip
followed the instructions placed it in my sd card root folder , and went into recovery and went to install from sd and this is the status 7 message i got.
E: Error in /sdcard/t999_uvdmd5_FIRMWARE_V4.ZIP(status 7)
Installation abort
roxus256 said:
ok so i download this file : Flashable UVDMD5 Bootloader / Firmware / Modem update.zip
followed the instructions placed it in my sd card root folder , and went into recovery and went to install from sd and this is the status 7 message i got.
E: Error in /sdcard/t999_uvdmd5_FIRMWARE_V4.ZIP(status 7)
Installation abort
Click to expand...
Click to collapse
Take out the battery on your phone. There should be a model number under that. Tell me the model number.
Aerowinder said:
Take out the battery on your phone. There should be a model number under that. Tell me the model number.
Click to expand...
Click to collapse
SGH-T999
roxus256 said:
SGH-T999
Click to expand...
Click to collapse
What version of what recovery are you using?
Aerowinder said:
What version of what recovery are you using?
Click to expand...
Click to collapse
cwm-based recovery v5.5.0.4
roxus256 said:
cwm-based recovery v5.5.0.4
Click to expand...
Click to collapse
Flash the new CWM zip from my signature. You can flash it with your CWM, just reboot recovery after you're done.
Aerowinder said:
Flash the new CWM zip from my signature. You can flash it with your CWM, just reboot recovery after you're done.
Click to expand...
Click to collapse
ok thank you will do right away
Aerowinder said:
Flash the new CWM zip from my signature. You can flash it with your CWM, just reboot recovery after you're done.
Click to expand...
Click to collapse
ok got the latest one flashed
thank you so much after i installed the new recovery i just followed your previous instructions on the bootloader and retried flashing pacman , and flash successful
Hello all,
I'm also having trouble flashing Pac-Man. im running 4.3 jellybean with Knox disabled through SU.
I've got a SGH-T999L with a baseband of LUVUBMK4.
Ive tried the latest TWRP as well as the latest CWM.
Still getting an error 7 message after factory reset and SD card reformat.
Help is appreciated.
D
---------- Post added at 06:59 PM ---------- Previous post was at 06:38 PM ----------
Just tried again through TWRP.
E: Error executing updater binary in zip '/external
Error flashing zip '/external_sd/pac_d2tmo-night
I was trying to install the CyanogenMod[1] Firmware (CM) for my Samsung SPH L710 (Sprint) using these instructions[2]. I was using Mac OS X / Heimdall command line binary, downloaded here[3], version 1.4.0. The CM instructions for my phone recommended 1.4RC1 but this package had me using a non-standard library location on my computer whose path wasn't in my standard PATH. Regardless, the Heimdall binary I'm using works as expected.
I installed ClockworkMod (CWM) recovery image using Heimdall. The CM page recommends I use 6.0.3.1 which I installed without unexpected results. I rebooted my phone into "recovery" mode (Vol Up, Home Power) where I followed the step to backup my phone; which I did. Next, I did the "wipe/factory reset" an unnerving step, given how I've customized my phone. Next I proceeded to install CM itself. I tried installing two versions: cm-10.2.0-d2spr.zip[4] and cm-10.1.3-d2spr.zip[5] I downloaded both zip files using the Android File Transfer utility on Mac. The location, from the boot's perspective, is /scard/0/cm-10.1.3-d2spr.zip. The CWM Recovery / zip installer failed to both, throwing an assert error. I followed the instructions here[6], essentially stripping out the assert (first line). Nevertheless, the installer still failed.
I wanted to restore my backup and give up on the venture. However, I was unable to do so. I was getting the MD5 checksum error when trying to restore my backup via CWM. My restore directory was missing a "nandroid.md5" file, so using the "adb shell" I restored[7] it using these instructions. Now I could run my backup, but, my data configuration fails to restore. (I believe there's system, data, and two other categories) It seems the backup is corrupt? Over on this[8] CWM page they recommend 6.0.4.5, not the 6.0.3.1 version, which I flashed my phone with. Afterwards, after booting to recovery mode, CWM shows an odd message "root access is missing. Root device? This can not be undone" My impulse is "NO" since rooting is simply adding complexity to this already out of control problem. I click "No"
This is when the phone is now stuck on "Samsung" at boot.
I restored 6.0.3.1, to no avail. Yes, I can still adb into my phone, access the boot downloader screen and recovery screen, but I can not get past "Samsung" Reverting to 6.0.3.1 leaves me with a backup I can not restore.
I profoundly appreciate any ideas or help on this matter.
Update: my current (broken) system info:
Code:
adb shell getprop ro.build.version.release
4.3.1
adb shell cat /proc/version
Linux version 3.4.66-cyanogenmod-g34da3e6 ([email protected])(gcc version 4.7 (GCC) ) #1 SMP PREEMPT Wed Nov 27 13:54:11 PST 2013
Obfuscated links to the above references (replace '-' with '.' in the domains)
1: wiki-cyanogenmod-org
2: wiki-cyanogenmod-org/w/Install_CM_for_d2spr
3: bitbucket-org/benjamin_dobell/heimdall/downloads
4: download-cyanogenmod-org/get/jenkins/49849/cm-10.2.0-d2spr.zip
5: download-cyanogenmod-org/get/jenkins/42488/cm-10.1.3-d2spr.zip
6: youtube-com/watch?v=QW1znjDLe-k
7: geekyzz-blogspot-com/2013/02/how-to-fix-nandroid-md5-mismatch-in_23.html
8: clockworkmod-com/rommanager
i'd flash the latest cwm > http://download2.clockworkmod.com/recoveries/recovery-clockwork-6.0.4.5-d2spr.img
then reflash the cm 10 zip (you may want to download it again)
then flash gapps from here http://forum.xda-developers.com/showthread.php?t=2397942
good luck!
For what it's worth, Philz Touch is probably the best recovery out there right now, it is awesome enough that it made me switch from TWRP, a recovery that I swear by.
http://forum.xda-developers.com/showthread.php?t=2446393
Mr. Struck said:
For what it's worth, Philz Touch is probably the best recovery out there right now, it is awesome enough that it made me switch from TWRP, a recovery that I swear by.
http://forum.xda-developers.com/showthread.php?t=2446393
Click to expand...
Click to collapse
+1 - I use it
Thanks for the recommendations
I appreciate your agreeing on Philz Touch for recovery. However, my more fundamental problem remains, that I cannot boot past the Samsung screen. A friend recommended using this stock ROM: rwilco12-com/downloads.php?dir=Files/Devices/Samsung%20Galaxy%20S3%20%28SPH-L710%29/Stock%20ROMs/JB/LJ7 but that failed to install. I copied the zip file via adb push to /scard/0 and tried using CWM to install via the recovery screen; but it failed, saying "installation aborted."
Thanks! — Kyle
I think what we are all getting at is that part of your problem might be your choice of recovery. If you aren't currently using Philz, maybe try switching and starting over.
Sent from my SPH-L710 using Tapatalk
So I've installed Philz Touch 6.00.8. Tried to install CyanogenMod, same assert error. Elsewhere http://forum.xda-developers.com/showthread.php?t=2303308 is talk that I need Fre3's MD4. So, I installed it, and now the device won't power at all.
Screen Ack said:
So I've installed Philz Touch 6.00.8. Tried to install CyanogenMod, same assert error. Elsewhere http://forum.xda-developers.com/showthread.php?t=2303308 is talk that I need Fre3's MD4. So, I installed it, and now the device won't power at all.
Click to expand...
Click to collapse
Status 7 error (assert issue) means the assert lines in the zip don't recognise your bootloader because all the bootloaders in the standard updater-script for any ROM aren't current enough for MK3. You need to delete those lines or change one of them to reflect your current boot loader.
Sent from my SPH-L710 using Tapatalk
---------- Post added at 09:19 PM ---------- Previous post was at 09:15 PM ----------
Mr. Struck said:
Status 7 error (assert issue) means the assert lines in the zip don't recognise your bootloader because all the bootloaders in the standard updater-script for any ROM aren't current enough for MK3. You need to delete those lines or change one of them to reflect your current boot loader.
Sent from my SPH-L710 using Tapatalk
Click to expand...
Click to collapse
Sent from my SPH-L710 using Tapatalk
---------- Post added at 09:21 PM ---------- Previous post was at 09:19 PM ----------
Mr. Struck said:
Status 7 error (assert issue) means the assert lines in the zip don't recognise your bootloader because all the bootloaders in the standard updater-script for any ROM aren't current enough for MK3. You need to delete those lines or change one of them to reflect your current boot loader.
Sent from my SPH-L710 using Tapatalk
---------- Post added at 09:19 PM ---------- Previous post was at 09:15 PM ----------
Sent from my SPH-L710 using Tapatalk
Click to expand...
Click to collapse
Sorry Tapatalk not cooperating. So I assume you are aware of this based on your first post in this thread. Did you delete all the asserts up to the part that says "mount..."?
Sent from my SPH-L710 using Tapatalk
"He's dead, Jim."
The phone no longer response to the power button. The MD4 firmware update hosed something in a big way.
Screen Ack said:
"He's dead, Jim."
The phone no longer response to the power button. The MD4 firmware update hosed something in a big way.
Click to expand...
Click to collapse
If you had taken the 4.3 update with KNOX, you can not downgrade the bootloader to MD4 - this WILL brick your phone.
There are a number of threads highlighting this eventuality.
Anyway downgrade bootloader from 4.3 to 4.1?
[STOCK] 4.3 and up Discussion Thread (NOT CM or AOSP)
3-4 others in General. I've not found a "debrick" image for this phone as of yet.
There is this thread : [GUIDE]Unbrick a Hard Bricked SPRINT Galaxy S3 (Without JTAG) but I am not sure that would work for you.
I'm sorry this happened and I hope you can get your phone fixed.
jdelano said:
If you had taken the 4.3 update with KNOX, you can not downgrade the bootloader to MD4 - this WILL brick your phone.
There are a number of threads highlighting this eventuality.
Anyway downgrade bootloader from 4.3 to 4.1?
[STOCK] 4.3 and up Discussion Thread (NOT CM or AOSP)
3-4 others in General. I've not found a "debrick" image for this phone as of yet.
There is this thread : [GUIDE]Unbrick a Hard Bricked SPRINT Galaxy S3 (Without JTAG) but I am not sure that would work for you.
I'm sorry this happened and I hope you can get your phone fixed.
Click to expand...
Click to collapse
I second that sorry as well. I hate to say it, but from what I have read and researched, when Knox prevents a bootloader change, it is the ultimate brick, as in not even a JTAG can fix it. Very crappy, and I think Samsung is going to take a small hit in the future from previous owners who move away from them the next time a device update is in store thanks to the garbage known as Knox that was forced on a lot of unsuspecting device owners.
Just to provide all the information I have on hand, I have the
T-Mobile SGH-M919
android version 4.3
baseband version M919UVUEMK2
Current Recovery: ClockworkMod 6.0.4.7
My issue is that regardless of what rom I attempt to download i get the error below. Specifically, I've tried to download virginROM 2.3, which seems to be compatible with my device. From what I understand status 7 is in place to keep you from flashing an incompatible rom and so I'm not too sure how to proceed from here. Any and all help would be appreciated.
flash flash flashin things
format() expects 5 args, got 4
E: Error in /data/media/0/virginROM_v2.4.1.zip
(status 7)
Installation aborted.
/tmp/recovery.log was copied to /sdcard/clockworkmod/recovery.log.
Please open ROM manager to report the issue.
Try using TWRP
My S4 Is Insane
Deviant Team Member
could be the signature veridicatrion, try disabling in recovery
aisarang said:
Just to provide all the information I have on hand, I have the
T-Mobile SGH-M919
android version 4.3
baseband version M919UVUEMK2
Current Recovery: ClockworkMod 6.0.4.7
My issue is that regardless of what rom I attempt to download i get the error below. Specifically, I've tried to download virginROM 2.3, which seems to be compatible with my device. From what I understand status 7 is in place to keep you from flashing an incompatible rom and so I'm not too sure how to proceed from here. Any and all help would be appreciated.
flash flash flashin things
format() expects 5 args, got 4
E: Error in /data/media/0/virginROM_v2.4.1.zip
(status 7)
Installation aborted.
/tmp/recovery.log was copied to /sdcard/clockworkmod/recovery.log.
Please open ROM manager to report the issue.
Click to expand...
Click to collapse
I just ran into this a few minutes ago using Philz Touch. The solution I found was under the install zip menu, you should see "Don't Allow Old update-binary. It should have a check-mark; simply untick that option and try again.
lordcheeto03 said:
I just ran into this a few minutes ago using Philz Touch. The solution I found was under the install zip menu, you should see "Don't Allow Old update-binary. It should have a check-mark; simply untick that option and try again.
Click to expand...
Click to collapse
I'm using CWM and I don't see the option to check "donm't allow old update-binary." When I turn toggle signature verification off I get
E:footer is wrong
E: signature verification failed
Installation aborted.
and then get prompted to ask if i want to install an untrusted package. I attempted to download and apply the new 4.4.2 Google Edition by Davnh, haven't tried TWCP yet but i feel like it should still be doable via CWM.
This is simply an info thread on the latest developments in recovery for the d710. I did not compile any of the aforementioned files. I and a few other users only tested the "adjustments / tweaks" our recognized developer @Lanchon made so it would be fully functional on the d710.
Please don't post here for kernel issues or with recovery support. Post in their respective threads.
Info:
So basically, Lanchon has figured out a way to take the Cm 11 kernel and add a feature that allows a separate recovery (inside the actual recovery partition which was never used in the stock TW firmware) to boot instead of the recovery attached to the kernel. It is respectively called the "Isorec kernel" (isolated recovery).
This was originally created for the S2 i9100 and then adapted for the i777 and d710 because they are in the same chipset family. So the thread is located in the i9100 section.
The thread and links are located here:
http://forum.xda-developers.com/gal...t/isorec-isolated-recovery-galaxy-s2-t3291176
I suggest that you go there first and read the Original Post to better understand it.
Then recently, developer arnab and Dees_Troy made TWRP 3.0.2.0 official for the i9100 and they've enabled it to accept isorec requirements in order to boot inside the "recovery partition."
Thread and links here:
http://forum.xda-developers.com/galaxy-s2/development-derivatives/recovery-twrp-3-0-0-0-t3330457
Last, Lanchon modded TWRP slightly so it will work on the d710, i777, and i9100 alike with a crossflash version and uploaded it to his androidfilehost.com developer profile.
Links to that are also in his kernel thread above.
Note: you must have a kernel that will support isorec booting or it will not work.
How to:
1. Kernel
Download Lanchon's CM11 Isorec kernel from the links in his thread and flash it in cwm. Make sure it's for your device (d710)
or
Have the latest CM11 nightly running on your phone already (it already has isorec merged into it)
2. Recovery
download TWRP 2.8.7.0 i9100.zip and flash
flash TWRP patcher.zip (D710)
reboot recovery
from TWRP recovery flash TWRP 3.0.2.0 img
flash TWRP patcher.zip (D710) again
reboot recovery
You should have TWRP 3.0.2.0 on your d710 and should be able to flash any ROM that supports isorec without having to reflash your recovery.
Currently, we (d710 users) only have Dastin's Cyanogenmod 11 nightly builds. Lanchon's isorec kernel code will work in any AOSP or AOKP ROM but that maintainer would have to adopt it into his kernel.
There is also a "Disabler.zip" that will erase the recovery partition if you want to go back for whatever reason.
Please give credit and thanks to the people who gave their time and knowledge in order to make this possible.
Great summary. Thanks!
I'm guessing we download TWRP from here?
https://www.androidfilehost.com/?w=files&flid=54335
What's the difference between "lanchon-twrp-patcher-20160417-crossflash-d710.zip" and "lanchon-twrp-patcher-20160417-d710.zip"?
Any known bugs?
Old I know, but I was recently looking into this myself. Per this page
The standard version will only let you flash packages for your device. The crossflash version will additionally let you flash packages for the i9100. Use crossflash at your own risk.
Click to expand...
Click to collapse
unknownsoldierx said:
What's the difference between "lanchon-twrp-patcher-20160417-crossflash-d710.zip" and "lanchon-twrp-patcher-20160417-d710.zip"?
Click to expand...
Click to collapse
shar88 said:
Old I know, but I was recently looking into this myself. Per this page
Click to expand...
Click to collapse
well you need two files to start when switching from cwm to twrp. this what i used:
modified arnab's twrp-3.0.2-0-i9100.zip
/META-INF/com/google/android/updater-script
Code:
getprop("ro.product.device") == "SPH-D710" || getprop("ro.build.product") == "SPH-D710" ||
d710 twrp patcher you don't really need crossflash
then update to official TWRP i9100 build
and flash the patch again
Maromi said:
well you need two files to start when switching from cwm to twrp. this what i used:
modified arnab's twrp-3.0.2-0-i9100.zip
/META-INF/com/google/android/updater-script
Code:
getprop("ro.product.device") == "SPH-D710" || getprop("ro.build.product") == "SPH-D710" ||
d710 twrp patcher you don't really need crossflash
then update to official TWRP i9100 build
and flash the patch again
Click to expand...
Click to collapse
Ok now it's gotten a little confusing . The OP says flash one file and it's done but your showing two files and a script . Which is it for a d2spr running the latest CM 11 with cwm recovery going to twrp ? Also does the fact the crossfire patch that allows to flash packages for the i9100 mean we could flash lollipop or MM and it would work on the D710 ? Telephony and data work or not work ? thanks
SuperGoober said:
Ok now it's gotten a little confusing . The OP says flash one file and it's done but your showing two files and a script . Which is it for a d2spr running the latest CM 11 with cwm recovery going to twrp ? Also does the fact the crossfire patch that allows to flash packages for the i9100 mean we could flash lollipop or MM and it would work on the D710 ? Telephony and data work or not work ? thanks
Click to expand...
Click to collapse
the OP is referencing TWRP-3.0.2.d710.zip which i couldn't find anywhere so i modified the the i9100 recovery referenced in my post, flashed it, and the patcher, reboot recovery, then flashed the official twrp i9100 build and flashed the patcher again.
Maromi said:
the OP is referencing TWRP-3.0.2.d710.zip which i couldn't find anywhere so i modified the the i9100 recovery referenced in my post, flashed it, and the patcher, reboot recovery, then flashed the official twrp i9100 build and flashed the patcher again.
Click to expand...
Click to collapse
lanchon-twrp-patcher-20160417-crossflash-d710.zip
I think he was referencing this like Unknownsoldier posted up above. OP lanchon-twrp-patcher-20160417-crossflash-d710.zipsays you can flash this and your done in the instructions . You said something different is why I asked because I don't want to brick my device . Not trying to split hairs with you . Just want to be careful . https://www.androidfilehost.com/?w=files&flid=54335
Hopefully @Mavrikmeercat will come back and clarify . You have sort of muddied the waters for me and perhaps thats a good thing until I find out for sure . Might have save my device . Thanks
update: The thing I find most odd is his instructions say to flash lanchon-twrp-patcher-20160417-crossflash-d710.zip and your done but that file is only 7.2 KB . I don't see how TWRP could possibly be contained in a 7.2 kb file . I hope he will clear this up and give us a link to correct file doe D710 .
SuperGoober said:
lanchon-twrp-patcher-20160417-crossflash-d710.zip
update: The thing I find most odd is his instructions say to flash lanchon-twrp-patcher-20160417-crossflash-d710.zip and your done but that file is only 7.2 KB . I don't see how TWRP could possibly be contained in a 7.2 kb file . I hope he will clear this up and give us a link to correct file doe D710 .
Click to expand...
Click to collapse
the OP instructions don't mention patcher but a full TWRP build that doesn't exist unless you build/patch it yourself
1. Run the latest nightly of CM11 for d710(contains isorec kernel)
2. Patch i9100 TWRP 3(isorec)package (info post #3) http://forum.xda-developers.com/devdb/project/?id=14252#downloads
3. flash from cwm to TWRP(isorec)package
4. IMPORTANT flash twrp-patcher for d710 before the next step
5. reboot recovery to verify twrp
6. use instructions to update to official i9100 builds https://github.com/Lanchon/TWRP-Patcher-SGS2
SuperGoober said:
update: The thing I find most odd is his instructions say to flash lanchon-twrp-patcher-20160417-crossflash-d710.zip and your done but that file is only 7.2 KB . I don't see how TWRP could possibly be contained in a 7.2 kb file . I hope he will clear this up and give us a link to correct file doe D710 .
Click to expand...
Click to collapse
We found that the TWRP website download link doesn't work on some mobile browsers.. (Go figure!)
It downloads an html file that's 7.2KBs. the actual recovery is like 9.x MB
Maromi is correct. Lanchon changed a few things around since I created the OP.
download TWRP 2.8.7.0 i9100.zip and flash
flash TWRP patcher.zip (D710)
reboot recovery
from TWRP recovery flash TWRP 3.0.2.0 img
flash TWRP patcher.zip (D710) again
reboot recovery
OP updated.. Sorry guys, Been busy at work.
It's to bad twrp can't just replace cwm officially and the builds be packaged with it instead of cwm . If twrp were built for the epic and submitted to cm gerrit for approval then all the patching would be obselete because twrp seems the recovery of choice by far .
how do I flash the TWRP patcher?
Maromi said:
well you need two files to start when switching from cwm to twrp. this what i used:
modified arnab's twrp-3.0.2-0-i9100.zip
/META-INF/com/google/android/updater-script
Code:
getprop("ro.product.device") == "SPH-D710" || getprop("ro.build.product") == "SPH-D710" ||
d710 twrp patcher you don't really need crossflash
then update to official TWRP i9100 build
and flash the patch again
Click to expand...
Click to collapse
Wow. That's awesome. Thanks Maromi! And more thanks to Mavrikmeercat, Lanchon, Arnab. So nice to have the latest TWRP running on the old D710!
Just follow Maromi's guide. To reiterate: 1. Download "Arnab's TWRP" for i9100 ("twrp-3.0.2-0-i9100.zip" here, see Downloads tab). 2. Download latest "TWRP" official for i9100 (here). 3. Download latest Lanchon's "TWRP Patcher" for D710 (here, see Downloads link). 4. Modify "Arnab's TWRP": unzip, find "updater-script", open in text editor, modify as specified (add "SPH-D710" line), save, zip everything back. 5. Copy files to device. 6. Boot into recovery (CWM if on CM 11). 7. Flash modified "Arnab's TWRP". 8. Flash "TWRP Patcher". 9. Reboot into recovery. 10. Flash "TWRP" official for i9100. 11. Flash "TWRP Patcher". 12. Enjoy. Thank. Donate to them.
That means we now have powerful TWRP recovery (over old CWM). Can now run things like REPIT to partition (gain much more room for app storage). And many more benefits. But it's now necessary to make sure any new OS supports IsoRec before flashing. And remember to flash "TWRP Flasher" after updating TWRP every time. I will probably be leaving my D710 as it is now for a long while...