So is there a special way you have to flash the rom on the gs3. Everytime I try I get this weird abort message.. I even wiped the cache and factory reset the user data before..
Also, I saved the recovery log of the rom aborting how can I upload it here so you can see it?(I used cwm btw)
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
There are entirely too many variables for anyone to guess without you providing some useful information. My advice would be to read the OP/FAQ of the ROM you're attempting to flash. If you have questions in your reading, Google searches will almost always yield useful advice.
CamFlawless said:
There are entirely too many variables for anyone to guess without you providing some useful information. My advice would be to read the OP/FAQ of the ROM you're attempting to flash. If you have questions in your reading, Google searches will almost always yield useful advice.
Click to expand...
Click to collapse
Sorry I didnt mean to be vague on my information.. basically when I hit install from sd this is what happens..
-- Installing: /sdcard/Root/cm-10.0.0-d2tmo.zip
Finding update package...
I:Update location: /sdcard/Root/cm-10.0.0-d2tmo.zip
Opening update package...
Installing update...
script aborted: assert failed: getprop("ro.product.device" ) == "d2tmo" || getprop("ro.build.product" ) == "d2tmo"
assert failed: getprop("ro.product.device" ) == "d2tmo" || getprop("ro.build.product" ) == "d2tmo"
E:Error in /sdcard/Root/cm-10.0.0-d2tmo.zip
(Status 7)
Installation aborted.
I am rooted, I have the samsung gs3 for at&t sgh-i747.
Im using cwm and when I downloaded the rom I made sure it was specifically for sgh-i747 and it just says to flash it through cwm. I've tried other roms and the same thing happens..
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Looks like you're trying to flash cm10 for tmobile instead of att
kirkgbr said:
Looks like you're trying to flash cm10 for tmobile instead of att
Click to expand...
Click to collapse
:what: wow.. good eye.. thanks.. but on the website I got it from it says specifically for the at&t :/ must've done something wrong..
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
So It wasn't the rom that was messed up something else is wrong.
-- Installing: /sdcard/Root/cm-10-20121202-NIGHTLY-d2att.zip
Finding update package...
I:Update location: /sdcard/Root/cm-10-20121202-NIGHTLY-d2att.zip
Opening update package...
Installing update...
script aborted: assert failed: getprop("ro.product.device" ) == "d2att" || getprop("ro.build.product" ) == "d2att"
assert failed: getprop("ro.product.device" ) == "d2att" || getprop("ro.build.product" ) == "d2att"
E:Error in /sdcard/Root/cm-10-20121202-NIGHTLY-d2att.zip
(Status 7)
Installation aborted.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Looks to me like you need to update your recovery. Either update CWM through ROM Manager or install TWRP using GooManager from the Play Store.
Task650 AOKP 4.1.2 JB 12/2/12
Underwear Kernel (Intellidemand / Deadline)
CamFlawless said:
Looks to me like you need to update your recovery. Either update CWM through ROM Manager or install TWRP using GooManager from the Play Store.
Task650 AOKP 4.1.2 JB 12/2/12
Underwear Kernel (Intellidemand / Deadline)
Click to expand...
Click to collapse
That's exactly what it was.. thanks.
Are those the only two recoveries available for this phone?
On my old phone I had the wcx and I liked it a lot.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
eddied042092 said:
That's exactly what it was.. thanks.
Are those the only two recoveries available for this phone?
On my old phone I had the wcx and I liked it a lot.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
To be honest, I'm not sure if they're the only two. They are, however, the only 2 I've ever seen mentioned around here.
Task650 AOKP 4.1.2 JB 12/2/12
Underwear Kernel (Intellidemand / Deadline)
CamFlawless said:
To be honest, I'm not sure if they're the only two. They are, however, the only 2 I've ever seen mentioned around here.
Task650 AOKP 4.1.2 JB 12/2/12
Underwear Kernel (Intellidemand / Deadline)
Click to expand...
Click to collapse
Yeah same here.. well thanks anyways :thumbup:
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Whenever I try to install a custom d2tmo ROM from XDA on my T999v GS3, I get this error:
assert failed: getprop("ro.build.product") == "d2tmo"
E:Error in /emmc/_Download/pa_d2tmo-2.52-27OCT2012-163709.zip
(status 7)
What do I need to do to fix this? I've tried using both TWRP and CWM with the same result. Also I've formated the phone and still no positive results.
moving to right section. I suggest to use search function. Regards,
You need to change your build.prop to reflect a t999, you either flashed a rom from a different section or a Google wallet fix that changed your build.prop probably
Sent from my SGH-T999 using Tapatalk 2
bfranklin1986 said:
You need to change your build.prop to reflect a t999, you either flashed a rom from a different section or a Google wallet fix that changed your build.prop probably
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
How do i do this! sorry, im to new to rooting
Search. Reading is the foundation of knowledge.
They call me "Jelly" cuz jam don't shake like this!
Download ROM manager. Install clockwork.
I'm pretty good at this stuff, but I wouldn't be running the latest cm10 nightly on an island if I hadn't given koush his 5 dollars.
Better than editing build prop
Sent from my SGH-T999 using xda premium
Android_Monsters said:
Download ROM manager. Install clockwork.
I'm pretty good at this stuff, but I wouldn't be running the latest cm10 nightly on an island if I hadn't given koush his 5 dollars.
Better than editing build prop
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
ive already tried this and it didnt work
Hi guys,
Can you guys give me a direct link to downloading the latest version of pacman rom for the galaxy nexus on android 4.3? Thanks
Sent from my Nexus 7 using xda app-developers app
http://pacman.basketbuild.com/download.php?file=main/maguro/nightly/pac_maguro-nightly-20131021.zip
As you requested, this is the latest available nightly on BasketBuild. Nightlies aren't stable (especially for PACman) so actually you shouldn't want them at all.
And you have hours of patience waiting for a spoon-fed answer but don't have the 10-minute patience searching for the links in the Dev subforum? Come on man, this is XDA - help yourself next time
Sent from Google Nexus 4 @ CM10.2
My phone isn't able to flash the ROM. Do I need to do a factory reset then flash?
Sent from my Nexus 7 using xda app-developers app
speedsolve said:
My phone isn't able to flash the ROM. Do I need to do a factory reset then flash?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
1) You have a custom recovery (CWM, TWRP), right? Stock recovery doesn't flash custom ROMs.
2) What error does it give? Details needed.
Sent from Google Nexus 4 @ CM10.2
AndyYan said:
1) You have a custom recovery (CWM, TWRP), right? Stock recovery doesn't flash custom ROMs.
2) What error does it give? Details needed.
Sent from Google Nexus 4 @ CM10.2
Click to expand...
Click to collapse
And to add to that, make a back up in cwm/twrp, then wipe, then flash rom+gapps. The latest nightly of pacman was uploaded to the pacman site last night and appears to be running really well compared to the 10/7 release. It is also android 4.3.1
It tries to flash the rom then it just stops in the first half second of the flash and says error.
Sent from my Galaxy Nexus using xda app-developers app
How does a device "earn" or end up with official cyanogenmod nightlies? Would love to see that for our device for CM11 as we had it for CM10.2.
Melamunna said:
How does a device "earn" or end up with official cyanogenmod nightlies? Would love to see that for our device for CM11 as we had it for CM10.2.
Click to expand...
Click to collapse
They should start tonight. Check the CM11 thread.
Sent from my GT-N5110 using Tapatalk
I always fail upgrading to official cm11
I also tried deleting the assert line but it still failed.
how can we fix this?
Hwoarang04 said:
I always fail upgrading to official cm11
I also tried deleting the assert line but it still failed.
how can we fix this?
Click to expand...
Click to collapse
Install a recovery specificly for your device only
Sent from my GT-N5100 using xda app-developers app
Just started learning this stuff about a month ago. Decided to use my Infuse and Captivate as sacrificial phones to learn on before I do anything on my S3. I have been successful with rooting the Infuse and Captivate along with installing several custom roms on each.
A couple of weeks ago I sucessfully rooted my S3 which had the AT&T 4.3 OTA update on it. I rooted using this method by Loxla http://forum.xda-developers.com/showthread.php?t=2562802.
I have enjoyed the advantages of a rooted S3. Now I would like to install a custom rom on this S3. In consideration of the bootloader dangers, what are my options for installing a custom rom?
Many thanks. And thanks to Loxla for a successful root.
Maybe I need to rephrase my question. I rooted my S3 AFTER I did the 4.3 AT&T OTA update. What ROM's can I flash from this point forward? Any rom that is based on 4.3 or higher? I understand that there is an issue if the bootloader is downgraded. But what about going UP? I have done extensive searching on this scenario but can't come up with an answer.
Thanks.
kevinga said:
Maybe I need to rephrase my question. I rooted my S3 AFTER I did the 4.3 AT&T OTA update. What ROM's can I flash from this point forward? Any rom that is based on 4.3 or higher? I understand that there is an issue if the bootloader is downgraded. But what about going UP? I have done extensive searching on this scenario but can't come up with an answer.
Thanks.
Click to expand...
Click to collapse
For me, I used cyanogenmod 10.2 d2att stable rom and it flashed successfully with twrp recovery. My phone was a samsung s3 i747m and it had android 4.3 OTA update and it was also rooted.
kevinga said:
Maybe I need to rephrase my question. I rooted my S3 AFTER I did the 4.3 AT&T OTA update. What ROM's can I flash from this point forward? Any rom that is based on 4.3 or higher? I understand that there is an issue if the bootloader is downgraded. But what about going UP? I have done extensive searching on this scenario but can't come up with an answer.
Thanks.
Click to expand...
Click to collapse
You could try Dandroid 5, its 4.3 touchwiz with asop looks.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
kevinga said:
Just started learning this stuff about a month ago. Decided to use my Infuse and Captivate as sacrificial phones to learn on before I do anything on my S3. I have been successful with rooting the Infuse and Captivate along with installing several custom roms on each.
A couple of weeks ago I sucessfully rooted my S3 which had the AT&T 4.3 OTA update on it. I rooted using this method by Loxla http://forum.xda-developers.com/showthread.php?t=2562802.
I have enjoyed the advantages of a rooted S3. Now I would like to install a custom rom on this S3. In consideration of the bootloader dangers, what are my options for installing a custom rom?
Many thanks. And thanks to Loxla for a successful root.
Click to expand...
Click to collapse
I answered this question in a different thread here.
dntesinfrno said:
I answered this question in a different thread here.
Click to expand...
Click to collapse
Thanks for the reply and the link. Could I install the Beanstalk 4.4 rom? I can't find any information regarding the bootloader. Here is the link to the rom http://forum.xda-developers.com/showthread.php?t=2485628
Cooro said:
For me, I used cyanogenmod 10.2 d2att stable rom and it flashed successfully with twrp recovery. My phone was a samsung s3 i747m and it had android 4.3 OTA update and it was also rooted.
Click to expand...
Click to collapse
I am assuming that you rooted AFTER you did the 4.3 OTA?
Cooro said:
For me, I used cyanogenmod 10.2 d2att stable rom and it flashed successfully with twrp recovery. My phone was a samsung s3 i747m and it had android 4.3 OTA update and it was also rooted.
Click to expand...
Click to collapse
I thought once someone updated to 4.3, installing custom recovery would crash the device?
I know Verizon and at&t are different, I was just curious.
Sent from my SCH-I535 using XDA Premium 4 mobile app
No, custom recovery won't brick your phone. Just trying to downgrade the boot loader will.
To the OP, most custom ROMs do not change the boot loader. If know of no ROM that changes the boot loader when you install thru recovery.
Sent from my SAMSUNG-SGH-I747 using XDA Premium HD app
indymx said:
No, custom recovery won't brick your phone. Just trying to downgrade the boot loader will.
To the OP, most custom ROMs do not change the boot loader. If know of no ROM that changes the boot loader when you install thru recovery.
Sent from my SAMSUNG-SGH-I747 using XDA Premium HD app
Click to expand...
Click to collapse
So could I flash a 4.4 ROM? I miss cm 11.
Sent from my SCH-I535 using XDA Premium 4 mobile app
XXDroidZillaXX said:
So could I flash a 4.4 ROM? I miss cm 11.
Sent from my SCH-I535 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Certainly, the only potential road block would be the bootloader assert in the updater script. If the list of acceptable bootloader's doesn't include MJB then it wont flash. The updater script is located under \META-INF\com\google\android in the rom zip. Here is a sample of the code :
assert(getprop("ro.product.device") == "d2att" || getprop("ro.build.product") == "d2att");
assert(getprop("ro.bootloader") == "I747UCDLK3" ||
getprop("ro.bootloader") == "I747UCDMG2" ||
getprop("ro.bootloader") == "I747MVLDLK4" ||
getprop("ro.bootloader") == "I747MVLDMF1" ||
getprop("ro.bootloader") == "I747MUMBLK3" ||
getprop("ro.bootloader") == "I747MUMBLL1");
If your bootloader isn't listed you can either add a new line for it to add it to the check, or delete the entire segment. Be warned that this will force and/or skip the check and go straight into installing the ROM regardless of the bootloader on your device, do so at your own risk. From what i've read the only functional difference between MJB and the earlier bootloaders is the addition of the Qfuse disallowing bootloader downgrading, adding the warranty bit counter, and implementing KNOX support in the security chain of trust so it shouldn't be a big deal but just sayin.
OK thanks, I'm not real comfortable getting in to code just yet I'm still learning.
I just didn't want to brick my phone, I couldn't care less about the KNOX warranty or whatever. I'm due for a new phone in a few months anyway.
Sent from my SCH-I535 using XDA Premium 4 mobile app
---------- Post added at 06:07 PM ---------- Previous post was at 06:05 PM ----------
dntesinfrno said:
Certainly, the only potential road block would be the bootloader assert in the updater script. If the list of acceptable bootloader's doesn't include MJB then it wont flash. The updater script is located under \META-INF\com\google\android in the rom zip. Here is a sample of the code :
assert(getprop("ro.product.device") == "d2att" || getprop("ro.build.product") == "d2att");
assert(getprop("ro.bootloader") == "I747UCDLK3" ||
getprop("ro.bootloader") == "I747UCDMG2" ||
getprop("ro.bootloader") == "I747MVLDLK4" ||
getprop("ro.bootloader") == "I747MVLDMF1" ||
getprop("ro.bootloader") == "I747MUMBLK3" ||
getprop("ro.bootloader") == "I747MUMBLL1");
If your bootloader isn't listed you can either add a new line for it to add it to the check, or delete the entire segment. Be warned that this will force and/or skip the check and go straight into installing the ROM regardless of the bootloader on your device, do so at your own risk. From what i've read the only functional difference between MJB and the earlier bootloaders is the addition of the Qfuse disallowing bootloader downgrading, adding the warranty bit counter, and implementing KNOX support in the security chain of trust so it shouldn't be a big deal but just sayin.
Click to expand...
Click to collapse
OK thanks, I'm not real comfortable getting in to code just yet I'm still learning.
I just didn't want to brick my phone, I couldn't care less about the KNOX warranty or whatever. I'm due for a new phone in a few months anyway.
Sent from my SCH-I535 using XDA Premium 4 mobile app
Sent from my SCH-I535 using XDA Premium 4 mobile app
XXDroidZillaXX said:
OK thanks, I'm not real comfortable getting in to code just yet I'm still learning.
I just didn't want to brick my phone, I couldn't care less about the KNOX warranty or whatever. I'm due for a new phone in a few months anyway.
Sent from my SCH-I535 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I've installed CM11.. I had minor issues going back to stock after, but installing CM11 on top of the OTA 4.3 boot loaders is no problem.
indymx said:
I've installed CM11.. I had minor issues going back to stock after, but installing CM11 on top of the OTA 4.3 boot loaders is no problem.
Click to expand...
Click to collapse
Awesome! Thanks, I really wanted to know if anyone out there had done successfully. Will it make a big difference since I'm on Verizon?
Sent from my SCH-I535 using XDA Premium 4 mobile app
XXDroidZillaXX said:
Awesome! Thanks, I really wanted to know if anyone out there had done successfully. Will it make a big difference since I'm on Verizon?
Sent from my SCH-I535 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Shouldn't.. CM11 doesn't change the boot loader.
I've heard good things about the CM11 version for your phone. I'm not happy with it on mine, but my buddy who's got a Verizon S3 says it runs great on his.
indymx said:
Shouldn't.. CM11 doesn't change the boot loader.
I've heard good things about the CM11 version for your phone. I'm not happy with it on mine, but my buddy who's got a Verizon S3 says it runs great on his.
Click to expand...
Click to collapse
Its great. I was on cm11 before I lost all good sense and updated to stock 4.3.
Sent from my SCH-I535 using XDA Premium 4 mobile app
XXDroidZillaXX said:
Its great. I was on cm11 before I lost all good sense and updated to stock 4.3.
Sent from my SCH-I535 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
There are some things in TW I like.. Like the calendar app.. I love that thing.. But, there are features of CM11 that rock too..
The camera in CM11 on ATT S3 sucks balls. TW's is a lot better. I use Nova Launchers, So the interface is mostly the same. And I'm currently running without any of the bloat. Also, TW has emoji working right.. I don't think CM11 does.
Minor issues true, but still..
The major issue I had with CM11 is the battery. CM11 took forever to charge, and would only charge with the screen off. They may have fixed that by now, but I'm thinking I'll wait a bit before I try again. It's too much hassle to get back to 4.3 Stock TW for me to want to try it too quickly.
indymx said:
There are some things in TW I like.. Like the calendar app.. I love that thing.. But, there are features of CM11 that rock too..
The camera in CM11 on ATT S3 sucks balls. TW's is a lot better. I use Nova Launchers, So the interface is mostly the same. And I'm currently running without any of the bloat. Also, TW has emoji working right.. I don't think CM11 does.
Minor issues true, but still..
The major issue I had with CM11 is the battery. CM11 took forever to charge, and would only charge with the screen off. They may have fixed that by now, but I'm thinking I'll wait a bit before I try again. It's too much hassle to get back to 4.3 Stock TW for me to want to try it too quickly.
Click to expand...
Click to collapse
I agree about the camera on CM.. It sucks. That is my only real issue.
How difficult was it to return to stock?
Sent from my SCH-I535 using XDA Premium 4 mobile app
Well, its not horrible. Just have to have a nandroid backup plus a backup of all of your app data.
When I booted up after restoring my nandroid, I got a million FC's. Only good way out of it was a reset.
Sent from my SAMSUNG-SGH-I747 using XDA Premium HD app
So far the latest nightly of CM11 is pretty good.. Camera is working as good as stock, battery seems to charge normally, and no other oddities.. I'll keep my eye on it for a day or so and see how it goes. No fancy calendar, but I can live with that.