Related
Welcome to the Darker Side of Jelly Bean!
What's working
Calls
SMS (MMS doesn't work yet)
WiFi
USB Storage
Internal storage
SuperUser/ SU binary (thanks ChainsDD)
Mobile Data
ADB
Displaying Network on both the Lockscreen and Notification Bar
What's not working
MMS
What's Included
Beats Audio (Thanks DroidVicious)
Latest Trinity Kernel (1384 MHz) (Thanks morfic)
All the latest and greatest Jelly Bean goodness
How to Install
Factory reset
Wipe system partition
Wipe Dalvik Cache/Cache
Install from Internal Storage
Reboot
Thanks
Morfic for letting me use the Trinity Kernel
b1six for the original leak
shabbypenguin/breamsforgotten for giving me a great base to start modifying
CyanogenMod for the ringtones and the notification sounds
My lovely wife for being a great beta tester of the ROM at every iteration
Disclaimer
I AM NOT RESPONSIBLE IF YOUR PHONE SETS ON FIRE AND BURNS DOWN YOUR HOME FROM FLASHING THIS ROM, NOR IF YOU HARDWARE BRICK IT. I WILL TRY TO HELP SOMEONE UNBRICK THEIR DEVICE, BUT I AM STILL NOT RESPONSIBLE FOR GETTING IT THERE.
Click HERE to Download
Reserved
Just in case
Nice to see another JB ROM for the sprint GNEX and first!
Sent from my Galaxy Nexus using xda app-developers app
Giving it a try will report back
Sent from my Galaxy Nexus using xda premium
Aside from what you mentioned in the OP, what's different from the ACS ROM?
Is there any theming in this ROM? The name suggests a bit of a Gothic theme.
Sent from my Galaxy Nexus using xda app-developers app
ajonesma said:
Is there any theming in this ROM? The name suggests a bit of a Gothic theme.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
No its stock it just says Gothic because this his username
Sent from my Galaxy Nexus using xda premium
Download not working
Sent from my Galaxy Nexus using xda premium
Will the MMS fix used on the ACS jb ROM work on this one? If no one has tested I will
Sent from my Galaxy Nexus using xda premium
Jeez whats up with the low rating already? Some of you people are harsh. Thanks for the rom man, I'll report back if I have any issues.
I get bad sideload when trying to flash the zip.
Thanks for the ROM!
Sent from my Galaxy Nexus using Tapatalk 2
Is this flashing? Also, is the telephony.db fix working on this?
Has anyone tried the telephony fix yet for MMS?
I'll try it when I get home and post that.
Thanks for the ROM by the way!
bodi524 said:
I get bad sideload when trying to flash the zip.
Click to expand...
Click to collapse
It aborts when I flash as well.
Sent from my Galaxy Nexus using xda premium
cool, hopefully in time you expand and add more than someones kernel and someones beats mod, but a great start nonetheless. always good to have some friendly competition, it increase production in the hopes to beat out the other guys
one minor tidbit tho. its Dreamsforgotten with a D
clj575 said:
It aborts when I flash as well.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Same here not flashing through CWM (aborted Status 6.....I think that's what it said), I'm checking the updater-script now to see if that's the hang-up... Will report back...
UPDATE:
Let me preface this comment by saying that I am not a Developer, but I've sometimes been able to fix aborted flash attempts in CWM by making corrections in the updater-script in cases that the updater-script calls for a different device (such as Maguro, Toro, etc) by changing the wrong device to "Toroplus"..
For the other Themes/ROM's in which I've updated the updater script (the updater-script is located in the META-INF > com > google > android folder, with "update-binary" file) there's only been two files in the android folder, 1) update-binary and 2) updater-script, but your ROM has three files; 1) update-binary, 2) updater-script and 3) updater-script~. I've attached three PDF's that compare the updater-script files in Gothic Rom and the updater-script file from ACS Jelly Belly Rom that I downloaded through GooManager today but I can't figure out the issue(s) but maybe someone else can. Here are the files:
DOWNLOAD PDF Comparison between the "updater-script" file and "updater-script~" files from Gothic Rom.
DOWNLOAD PDF comparison between the "updater-script" file from the Jelly Belly Rom and the "updater-script" file from Gothic Rom.
DOWNLOAD PDF comparison between the "updater-script" file from the Jelly Belly Rom and the "updater-script~" file from Gothic Rom.
Can someone make sense of this?
shabbypenguin said:
cool, hopefully in time you expand and add more than someones kernel and someones beats mod, but a great start nonetheless. always good to have some friendly competition, it increase production in the hopes to beat out the other guys
one minor tidbit tho. its Dreamsforgotten with a D
Click to expand...
Click to collapse
Spoken like a true gentleman :thumbup::thumbup:
Sent from my Galaxy Nexus using Xparent ICS Tapatalk 2
MoSeriouS said:
Same here not flashing through CWM (aborted Status 6.....I think that's what it said), I'm checking the updater-script now to see if that's the hang-up... Will report back...
Click to expand...
Click to collapse
Getting the Same Error
(Status 6)
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
Ok now that I'm confident in my ability to flash ROMS and Kernels in the new Linux 3.0 & 3.4 versions that came with JB, is there anyone who could help me out with finding modems and flashing them and what each modem is for and etc? I really don't understand the new system as i came over from the OG EVO and from what i understand thus far, its not exactly the same as flashing radios as it was with GB or ICS. Any help would be greatly appreciated. Tried looking through stickies but couldnt find anything.
Sent from my SPH-L710 using xda premium
This thread will guide you http://forum.xda-developers.com/showthread.php?p=38172219
Posts #1 through #5 where you will find links to modems. LJ7 and MD4 seem to work best. But these devices are not like HTC devices so don't put that much concern into it.
Sent from the future via Tapatalk 4
Ok thanks for the help. About updating the PRL on AOSP roms though.... I downloaded the script and ran the scripts using script manager exactly as the guide said to do so, but i cant enter diagnostics mode. Any idea why?
Sent from my SPH-L710 using xda premium
hawke591 said:
Ok thanks for the help. About updating the PRL on AOSP roms though.... I downloaded the script and ran the scripts using script manager exactly as the guide said to do so, but i cant enter diagnostics mode. Any idea why?
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
Won't really work on the S3... Best and easiest thing to do is make a nandroid then flash tw rom update prl and profile and then restore nandroid
Sent from the future via Tapatalk 4
Ok, was just curious about that. I know about the nandroid backup and all. Its basically the same as it was with the old aosp/sense system. But thanks a lot for your help. And hopefully I'll see an improvement in my signal strength and quality. Do you have any other tips that could help?
Sent from my SPH-L710 using xda premium
Nope other than stick to TW roms, signal strength will be better and lte, 3g exchange is much better.
Sent from the future via Tapatalk 4
Yea well it wouldnt make too much of a difference with 3G and LTE considering I'm in an area that doesnt have LTE coverage yet. And just curious here, but the synergy port from verizon IS considered a TW rom right?
Sent from my SPH-L710 using xda premium
yeah no lte it makes no difference. I don't know about synergy but just look in the OP it's either TW, AOSP or AOKP. If you don't have to flash gapps it's TW.
Sent from the future via Tapatalk 4
Ok thanks for your help.
Sent from my SPH-L710 using xda premium
All AOSP are 3.4 kernel's now. CM needs MD4 to flash. It's in freeza's thread
hawke591 said:
Ok now that I'm confident in my ability to flash ROMS and Kernels in the new Linux 3.0 & 3.4 versions that came with JB, is there anyone who could help me out with finding modems and flashing them and what each modem is for and etc? I really don't understand the new system as i came over from the OG EVO and from what i understand thus far, its not exactly the same as flashing radios as it was with GB or ICS. Any help would be greatly appreciated. Tried looking through stickies but couldnt find anything.
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
I flashed the md4 after edfunkycold told me where to find and DL them. But i am on md4 modem and am running cm. It IS on the 3.4 but the scripts still dont work so im just going to do the touchwiz trick.
Sent from my SPH-L710 using xda premium
hawke591 said:
Ok thanks for the help. About updating the PRL on AOSP roms though.... I downloaded the script and ran the scripts using script manager exactly as the guide said to do so, but i cant enter diagnostics mode. Any idea why?
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
Since the update to the 3.4.x kernel the scripts don't work anymore. Flash a TW ROM and follow those instructions
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.
can someone show me the way to install CM10.2.1 and how to adapt the build T999UVUENC2 for CM
Im running Android 4.3 thanks
You should be able to install a recovery via ODIN and and flash the ROM from there. The stock build shouldn't matter.
GS³: Carbonized, LeanKernel'd, Philz'd
I have CWM but when i tried to install it with TWRP it said an error with error with all the builds but my build wasnt in the list
Sent from my SGH-T999 using XDA Free mobile app
CM doesn't update their updater-scripts when new builds are released. So even though it'd probably work just fine, NC2 isnt included in the asserts and so it refuses to flash.
You'll have to edit the updater-script and add your build to get it to flash. Be aware though, the asserts are there for a reason, and if you are not absolutely 100% certain its safe to flash on your device, you shouldn't edit it to allow the flash.
Just the Updater script? Are u sure
Can u do it for me
Sent from my SGH-T999 using XDA Free mobile app
Yes I am sure. You are getting a status 7 error about the assert right?
I can do it but I cant promise it'll be before late tomorrow.
All you have to do is this:
Open the updater-script with notepad++ (regular text editors will not work).
At the very top you'll see assert lines with different build numbers. There may be two for each build. Replace one (or two if there are two already) with your current firmware build.
Delete the 3 signature files in meta-inf.
Rezip
Flash
If you dont know your firmware build, open terminal emulator and enter this:
getprop ro.bootloader
I will try it, I will let you know thanks
Sent from my SGH-T999 using XDA Free mobile app
But can u modify the ROM for me because maybe if I do it it I will mess up that so u could do it and upload the rom fixed
Sent from my SGH-T999 using XDA Free mobile app
Id only be uploading the updater-script. Its the only thing that'd be changed. Dont be intimidated by it though. Its a very quick, easy edit. Just replace one or two of the builds in the asserts with your own. If you search xda for updater-script asserts you'll probably find numerous examples.
Just make sure you use Notepad++, and remember to delete those 3 signature files.
Someone else may have already done so btw. Have you searched through the roms thread? CM11 might be more likely to already have it done.
Im going to wait for you to upload the file and I just copy the Updater script to the Zip and where are the signature files?
Sent from my SGH-T999 using XDA Free mobile app
In the meta-inf folder.
CERT.RSA CERT.SF and MANIFEST.MF? Those?
Sent from my SGH-T999 using XDA Free mobile app
Like this?
Sent from my SGH-T999 using XDA Free mobile app
Hey I just flashed my phone with the latest CM 11 4.4.4 Nightlies.
I got the same error however I didn't need to change any script.
Just use the latest CW Recovery
http://true-android.blogspot.com/2014/01/install-cwm-6045-advance-edition-on-t.html
You could install the CM M8 version
Here is the latest nightly version
http://download.cyanogenmod.org/?device=d2lte&type=nightly
And here is the latest M8 version
http://download.cyanogenmod.org/?device=d2lte&type=snapshot
I know you asked for version 10, however I'm using version 11 now and it's amazing so far
Yeah I'm running 10.2.1 now and maybe will install 11 when the stable version rolls out
Sent from my SGH-T999 using XDA Free mobile app
Alfred1516 said:
Yeah I'm running 10.2.1 now and maybe will install 11 when the stable version rolls out
Sent from my SGH-T999 using XDA Free mobile app
Click to expand...
Click to collapse
You are missing out on the KK awesomeness!! Try it, you might like it... You can always nandroid back if you don't like it... Just sayin. ?
GS³: Carbonized, LeanKernel'd, Philz'd
I want to try an Stable version cuz I hate downloading every apps when a new rom is installed, do you know when an CM11 stable version comes out?
Sent from my SGH-T999 using XDA Free mobile app
No idea when a stable version is coming out... I'd imagine soon though, they are on milestone builds. And you know you don't need to download apps everytime right? That's what app backup apps like Titanium Backup are for... And you can also dirty flash too... That allows you to keep your apps installed... Just wipe cache and dalvik after dirty flashing and most of the time you'll be OK. Keep in mind dirty flashing should only be done on the same ROMs with only minor changes...
GS³: Carbonized, LeanKernel'd, Philz'd
Oh okey thanks for the tip I will try CM11 someday but not now cuz Im loving Android stock
Samsung Touchwiz is too common
Sent from my SGH-T999 using XDA Free mobile app
Alfred1516 said:
Like this?
Sent from my SGH-T999 using XDA Free mobile app
Click to expand...
Click to collapse
Yes. Sorry I didnt get back to you yesterday. Got caught up with too many other things and just didn't get around to downloading and editing the script.
But that does look right to me, so you should be good to go. And if you did make some mistake, it'll simply just not flash, so there's not too much to really worry about.
Do you still need help on this?
Sent from my SGH-T999 using Tapatalk