Assert failed: getprop("ro.bootloader" during flashing of LiquidSmooth 2.37 T999 - T-Mobile, Samsung Galaxy SIII

Assert failed: getprop("ro.bootloader" during flashing of LiquidSmooth 2.37 T999
Assert failed: getprop("ro.bootloader" showed up when I tried to flash LiquidSmooth 2.37 4.3.1 onto my T-Mobile T999. Any help please?
http://forum.xda-developers.com/showthread.php?t=2313175 < same thing with mine except I'm running stock on 4.3 right now.

Did you receive and install the Stock OTA update to 4.3 ? The process to resolve your issue depends on that answer.

yes I was on stock and everything was normal when I updated and installed to stock 4.3.

xTheOne23 said:
yes I was on stock and everything was normal when I updated and installed to stock 4.3.
Click to expand...
Click to collapse
In that case, first make sure you have the latest version of the custom recovery of your choice. If its not then update it and try. If it is latest then read on.
Best if you take the rom zip and open it on pc with winzip or similar. Then go to
/Meta-Inf/com/google/android/ folder. There you will see a file called updater script. Open it with Wordpad and NOT NOTEPAD! Inside first few lines, you will see something like
Code:
assert(getprop("ro.bootloader") == "T999UVDLJA" ||
getprop("ro.bootloader") == "T999UVDLJC" ||
getprop("ro.bootloader") == "T999UVDMD5" ||
getprop("ro.bootloader") == "T999VVLDLL1" ||
getprop("ro.bootloader") == "T999LUVAMB7" ||
getprop("ro.bootloader") == "T999VVLDMF2");
show_progress(0.500000, 0);
There, delete the part before
show_progress(0.500000, 0);
Close the file and save it back to the zip. Put the zip on your External sd card and flash via recovery.

Perseus71 said:
In that case, first make sure you have the latest version of the custom recovery of your choice. If its not then update it and try. If it is latest then read on.
Best if you take the rom zip and open it on pc with winzip or similar. Then go to
/Meta-Inf/com/google/android/ folder. There you will see a file called updater script. Open it with Wordpad and NOT NOTEPAD! Inside first few lines, you will see something like
Code:
assert(getprop("ro.bootloader") == "T999UVDLJA" ||
getprop("ro.bootloader") == "T999UVDLJC" ||
getprop("ro.bootloader") == "T999UVDMD5" ||
getprop("ro.bootloader") == "T999VVLDLL1" ||
getprop("ro.bootloader") == "T999LUVAMB7" ||
getprop("ro.bootloader") == "T999VVLDMF2");
show_progress(0.500000, 0);
There, delete the part before
show_progress(0.500000, 0);
Close the file and save it back to the zip. Put the zip on your External sd card and flash via recovery.
Click to expand...
Click to collapse
What do you mean by version of custom recoery? Sorry, I'm a noob. And when you say delete the part before, 'show_progress((0.500000, 0);, do i delete everything before it lesving only that ?

Yes you delete all the Assert statement before that. But before you do that, please check the Version of your Custom Recovery.
When you boot to Custom Recovery, CWM or TWRP, you will see its version at the top.

Perseus71 said:
Yes you delete all the Assert statement before that. But before you do that, please check the Version of your Custom Recovery.
When you boot to Custom Recovery, CWM or TWRP, you will see its version at the top.
Click to expand...
Click to collapse
My CWM version is 6.0.4.5.

Yes that's the correct version. You should try removing the Asserts.

installation aborted
i cant install., i did what u said in the post.. installation aborted.
this is what my updater script file looks like.
assert(getprop("ro.product.device") == "d2tmo" || getprop("ro.build.product") == "d2tmo");
assert(getprop("ro.bootloader") == "T999UVDLJA" ||
getprop("ro.bootloader") == "T999UVDLJC" ||
getprop("ro.bootloader") == "T999UVDMD5" ||
getprop("ro.bootloader") == "T999UVUEMJC" ||
getprop("ro.bootloader") == "T999VVLDLL1" ||
getprop("ro.bootloader") == "T999LUVAMB7" ||
getprop("ro.bootloader") == "T999VVLDMF2");
mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "/system");
package_extract_file("system/bin/backuptool.sh", "/tmp/backuptool.sh");
package_extract_file("system/bin/backuptool.functions", "/tmp/backuptool.functions");
set_perm(0, 0, 0777, "/tmp/backuptool.sh");
set_perm(0, 0, 0644, "/tmp/backuptool.functions");
run_program("/tmp/backuptool.sh", "backup");
unmount("/system");
show_progress(0.500000, 0);
i deleted the part before show_progress

Did you try adding your bootloader to the updater script? Is the phone running the latest release of twrp?

Related

LT15a Unable to install custom rom

I get the following error when I try to flash CM and I read around people saying to "flash stock" but I downloaded LT15a arc_v2.3.4, 4.0.2.A.0.42_Generic America.ftf and it won't flash via the flash tool (dragged and dropped into the window and it just fails to install)
Does anyone have any suggestions on which stock rom I need or a way around this?
-------------------------
--Installing: /sdcard/FXP127-cm-9-20120630-UNOFFICIAL-anzu.zip
Finding update package...
Opening update package...
Installing update...
assert failed: getprop("ro.product.device") == "LT18i" || getprop("ro.build.product") == "LT18i" || getprop("ro.product.device") == "LT18a" || getprop("ro.build.product") == "LT18a" || getprop("ro.product.device") == "LT15i" || getprop("ro.build.product") == "LT15i" || getprop("ro.product.device") == "LT15a" || getprop("ro.build.product") == "LT15a" || getprop("ro.product.device") == "anzu" || getprop("ro.build.product") == "anzu"
E:Error in /sdcard/FXP127-cm-9-20120630-UNOFFICIAL-anzu.zip
(Status 7)
Installation aborted
Murmur95 said:
or a way around this?
-------------------------
--Installing: /sdcard/FXP127-cm-9-20120630-UNOFFICIAL-anzu.zip
Finding update package...
Opening update package...
Installing update...
assert failed: getprop("ro.product.device") == "LT18i" || getprop("ro.build.product") == "LT18i" || getprop("ro.product.device") == "LT18a" || getprop("ro.build.product") == "LT18a" || getprop("ro.product.device") == "LT15i" || getprop("ro.build.product") == "LT15i" || getprop("ro.product.device") == "LT15a" || getprop("ro.build.product") == "LT15a" || getprop("ro.product.device") == "anzu" || getprop("ro.build.product") == "anzu"
E:Error in /sdcard/FXP127-cm-9-20120630-UNOFFICIAL-anzu.zip
(Status 7)
Installation aborted
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1884746
XperienceD said:
http://forum.xda-developers.com/showthread.php?t=1884746
Click to expand...
Click to collapse
Thanks for the reply. I actually tried that before posting and it just gets stuck at the sony logo on boot.
-Flash via sony update service
-Flash kernel 562
-Doomlord root
-flash 587 kernel
-install CWM via flashtool
-modify the buildprop
-copy to SD
-Reboot recovery
-Installs & fails to reboot properly
Murmur95 said:
Thanks for the reply. I actually tried that before posting and it just gets stuck at the sony logo on boot.
Click to expand...
Click to collapse
That's because you haven't flashed the FXP kernel.
XperienceD said:
That's because you haven't flashed the FXP kernel.
Click to expand...
Click to collapse
Ok, so I downloaded the kernel and when I read the guide it says put the phone is fastboot mode but I have no idea how to do that and when I try to reboot into fastboot via flashtool it just reboots the phone normally (cmd adb reboot fastboot = reboots the phone normally) . When I use the command fastboot flash boot <kernel>.img it just says waiting for phone.
Anything else I read just tells me to unlock the bootloader (which I did via zerg rush)
I really appreciate the help but this phone is a co-workers and I am trying to install a custom rom for them and I hope to get it done ASAP so they can get it back. I never had this much issue with my Gal S & S3...
To use fastboot you must first unlock your bootloader.this cannot be done via Zergrush,only rooting your phone can be done with Zergrush,now,put the 4.0.2.a.0.42 file(unzipped)into the 'firmwares' folder that came with flashtool then press the lighting icon to flash your phone,when done,use Zergrush to root it and install x-parts from the market which helps you can install CWM which you need to install a custom ROM.
Sent from my LT18i

[Q] A partially bricked Xperia Arc

So I have a bricked Xperia Arc(LT15i) here. It's not completely bricked as I can enter fastboot mode. So here's my problems.
Only info I could find about installing cwm from fastboot is using recoveryArc.img (CWM 5.x) - It flashs fine, and boots into recovery. The problem is when I try to install a rom zip, the first assert line of script fails. (My phone is not LT15i? But it's written clearly under the battery. Is there a version of Arc not mentioned in the assert line given below?)
Code:
assert(getprop("ro.product.device") == "LT18i" || getprop("ro.build.product") == "LT18i" ||
getprop("ro.product.device") == "LT18a" || getprop("ro.build.product") == "LT18a" ||
getprop("ro.product.device") == "LT15i" || getprop("ro.build.product") == "LT15i" ||
getprop("ro.product.device") == "LT15a" || getprop("ro.build.product") == "LT15a" ||
getprop("ro.product.device") == "anzu" || getprop("ro.build.product") == "anzu");
Well then, I tried also flashing boot.img from FXP147-cm-10-20121118-UNOFFICIAL-anzu.zip and cm-9.1.0-anzu.zip. They also flash fine but does not boot into recovery. I mean not right after installing. I can't get into it manually either. There is no blue led, no luck with spamming back key either.
The third stunt I pulled was to remove assert line from cm-9.1.0-anzu.zip, flash recoveryArc.img, get into recovery, flash cm-9.1.0-anzu.zip (now suceeds), wipe cache/data/dalvik then flash boot.img from cm-9.1.0-anzu.zip via fastboot. This doesn't work either. Boot doesn't get past the flash image.
I'm just wondering if there was someone who have experienced this problem before and how they fixed this.
Read the thread a few below this, the one that uses the actual error message as the thread title.
Sent from myushi
Try to repair the phone with SUS.
http://www.sonymobile.com/global-en/tools/update-service/
Note:
all data on phone will be lost! So make backup from SD with other phone or PC with cardreader if you need some data from SDCard.
I always recommend to use SUS(formerly SEUS) for flashing original firmware, cause PCCompanion often causes problems.
Also remove SIM; When i bought my ArcS i directly updated it from GB to ICS with SUS and i already have inserted SIM when doing this,
after updating all servicenumbers storaged on SIM were lost

[Q] can't upgrade my 1747 to CM10.1*

whenever i try to upgrade my phone, i get assert errors:
Code:
-- Installing: /sdcard/cmupdater/cm-10.1.3-d2att.zip
Finding update package...
I:Update location: /sdcard/cmupdater/cm-10.1.3-d2att.zip
I:using /data/media for /sdcard/cmupdater/cm-10.1.3-d2att.zip.
Opening update package...
Installing update...
Warning: No file_contexts
script aborted: assert failed: getprop("ro.bootloader") == "I747UCDLK3" ||
getprop("ro.bootloader") == "I747UCDMG2" ||
getprop("ro.bootloader") == "I747MVLDLK4" ||
getprop("ro.bootloader") == "I747MVLDMF1" ||
getprop("ro.bootloader") == "I747MUMBLK3" ||
getprop("ro.bootloader") == "I747MUMBLL1"
assert failed: getprop("ro.bootloader") == "I747UCDLK3" || getprop("ro.bootloader") == "I747UCDMG2" || getprop("ro.bootloader") == "I747MVLDLK4" || getprop("ro.bootloader") == "I747MVLDMF1" || getprop("ro.bootloader") == "I747MUMBLK3" || getprop("ro.bootloader") == "I747MUMBLL1"
E:Error in /sdcard/cmupdater/cm-10.1.3-d2att.zip
(Status 7)
Installation aborted.
i've applied the firmwares in this thread so that my unlocked phone works on tmobile. my bootloader reads as:
Code:
C:\Users\IncogNegro\android developer toolkit\sdk\platform-tools>adb shell getprop ro.bootloader
T999UCALJ2
i keep trying to install stable roms from here using this guide. i have successfully upgraded the bootloader by following all the steps under the section titled "Installing a custom recovery on Galaxy S III (AT&T)". as a result, my recovery is CWM v6.0.3.1.
i've even gone as far as editing the updater script by removing all the assert tags. when i try to install, the installation fails without ANY ERROR MESSAGES.
what is the big deal!?
I'm having the same problem as well, My phone is rooted im stuck on stock 4.3 and really want to try the new custom roms out there.
aepowerlifter said:
I'm having the same problem as well, My phone is rooted im stuck on stock 4.3 and really want to try the new custom roms out there.
Click to expand...
Click to collapse
i am stuck in the same situation. i want to flash beanstalk sooo bad but it keeps failing. you can flash slimbean though. that's the only rom that i found that is flashable.

[q] cant update to cm10.2.1(hox)

Hey guys today an update to cm10.2.1(stable) came out. I have the htc one x. So my problem is that whenever i try to flash it it gives me status 7 error. I managed to ger around it by editing the updater-script file. I've deleted the following line: assert(getprop("ro.product.device") == "endeavoru" || getprop("ro.build.product") == "endeavoru");
assert(getprop("ro.bootloader") == "1.28.0000" || getprop("ro.bootloader") == "1.31.0000" || getprop("ro.bootloader") == "1.33.0000" || getprop("ro.bootloader") == "1.36.0000" || getprop("ro.bootloader") == "1.39.0000" || getprop("ro.bootloader") == "1.72.0000" || getprop("ro.bootloader") == "1.73.0000"); now im actually able to install it but my phone goes into a loop. It turns on and is stuck at the htc logo. Ive already tried clearing cache and dalvik cache and it didnt help. Any sugestions?
btw i get the status 7 error
Did you use recovery that is written to use?
Use TWRP 2.6 or Official Touch CWM 5.8.4.0
Sent from my One X
Same issue but on different devices, S3, S4 and S4 mini, save error messages on all, I think there's a problem with the package, btw I have different recoveries on all 3 devices, all fail
Use an older version of philz recovery like 5.15
Sent from my HTC One X using XDA Premium 4 mobile app

[Q] TWRP installation on T999 Galaxy S3 - which file?

Hello - I have just downloaded TWRP Manager and am preparing to install the custom recovery on a Canadian Wind Galaxy S3 (model number SGH-T999V). I would appreciate it if someone could confirm which file I should use for this purpose. Is it the d2can file?
Thanks,
Mvt926
You can use d2can, d2tmo or d2lte.
I recommend d2tmo if you plan on flashing any if the roms we have. Ensures better chances of successful flashing.
DocHoliday77 said:
You can use d2can, d2tmo or d2lte.
I recommend d2tmo if you plan on flashing any if the roms we have. Ensures better chances of successful flashing.
Click to expand...
Click to collapse
Thanks. I used d2tmo and it seems to have worked.
Mvt926
mvt926 said:
Thanks. I used d2tmo and it seems to have worked.
Mvt926
Click to expand...
Click to collapse
I've just completed my first system backup under TWRP and,owing to space limitations, excluded the data option. How useful is the backup with this exclusion? If I need to re do the backup with data included, is there a way to delete the first backup before completing the second?
Thanks,
Mvt926
Data includes your apps/data and settings. It should be under the TWRP folder on your sd card.
DocHoliday77 said:
Data includes your apps/data and settings. It should be under the TWRP folder on your sd card.
Click to expand...
Click to collapse
Thanks - as I have already run a titanium backup on all apps and data, would it be safe to assume that I can exclude the data option under TWRP backup?
Another thing I have found is that choosing the restore option under TWRP (to see whether the backup I have made is available for restore) causes an immediate crash (of TWRP).
Thanks,
Mvt926
That is up to you. Backing up system and boot partitions is basically just backing up the rom, just so you know. I make a clean nandroid before doing anything, and keep it on my computer. Then I generally just backup the data partition and keep the rom handy. At least I used to. I don't do it much anymore because I use titanium and it kinda seemed a little redundant to me. I still keep an initial backup on my computer though....just in case.
Everyone is different. Its boils down to what you are most comfortable having as your backup.
DocHoliday77 said:
That is up to you. Backing up system and boot partitions is basically just backing up the rom, just so you know. I make a clean nandroid before doing anything, and keep it on my computer. Then I generally just backup the data partition and keep the rom handy. At least I used to. I don't do it much anymore because I use titanium and it kinda seemed a little redundant to me. I still keep an initial backup on my computer though....just in case.
Everyone is different. Its boils down to what you are most comfortable having as your backup.
Click to expand...
Click to collapse
Thanks. I have realized that TWRP permits backups to the external SD card so will use that for a full backup, including data, and then make a duplicate on my computer for additional security.
Mvt926
I need some help please
This might not be the best place to post this but I am stuck.
I have been forced to update after my GS3 took a dump. The power control chip went bad. I have now taken over my wife's old GS3. I had not rooted and installed a custom rom in so long it took me a while to figure it out. I have rooted it. I have superuser. I installed CWM. However, I cannot get CM 10.2.1 to install. I have 4.3.1 on my device and wanted to stick with that os. I did not want to go to kit kat. I try to install through cwm and keep getting installation aborted. I uninstalled KNOX as I thought that might be the issue but I am guessing from reading this that it is a bootloader issue. I don't know how to fix/change any of that and very much need someones help. I am on a TMO SGH T999 build number JSS15J.T999UVUENC2. Kernel 3.0.31. I would very much like someone to help me figure out how to get CM 10.2.1 to install on my device. Please if you or if you know someone who can help me.
Thanks,
TIDE
[email protected]
Flash the rom again and when it fails go back and copy log to sd. The info you'll want will be towards the bottom. Let us know what it says is the reason for failure.
follow up
DocHoliday77 said:
Flash the rom again and when it fails go back and copy log to sd. The info you'll want will be towards the bottom. Let us know what it says is the reason for failure.
Click to expand...
Click to collapse
Please excuse my ignorance, how do I create the log to copy. Is that done with a specific app?
I think I figured out how to create a log. Please see my follow up post.
I think I found the log
DocHoliday77 said:
Flash the rom again and when it fails go back and copy log to sd. The info you'll want will be towards the bottom. Let us know what it says is the reason for failure.
Click to expand...
Click to collapse
I think this is what you wanted. I know I am flashing the correct version for my phone sgh t999 which from what I understand a status 7 error could mean that I was not. I was thinking it had something to do with the boot loader and knox on this version 4.3.1.
-- Installing: /sdcard/0/0/cm-10.2.1-d2tmo.zip
Finding update package...
I:Update location: /sdcard/0/0/cm-10.2.1-d2tmo.zip
I:using /data/media for /sdcard/0/0/cm-10.2.1-d2tmo.zip.
Opening update package...
Installing update...
Warning: No file_contexts
script aborted: assert failed: getprop("ro.bootloader") == "T999UVDLJA" ||
getprop("ro.bootloader") == "T999UVDLJC" ||
getprop("ro.bootloader") == "T999UVDMD5" ||
getprop("ro.bootloader") == "T999UVUEMJC" ||
getprop("ro.bootloader") == "T999VVLDLL1" ||
getprop("ro.bootloader") == "T999LUVAMB7" ||
getprop("ro.bootloader") == "T999VVLDMF2" ||
getprop("ro.bootloader") == "T999VVLUEMK5"
assert failed: getprop("ro.bootloader") == "T999UVDLJA" || getprop("ro.bootloader") == "T999UVDLJC" || getprop("ro.bootloader") == "T999UVDMD5" || getprop("ro.bootloader") == "T999UVUEMJC" || getprop("ro.bootloader") == "T999VVLDLL1" || getprop("ro.bootloader") == "T999LUVAMB7" || getprop("ro.bootloader") == "T999VVLDMF2" || getprop("ro.bootloader") == "T999VVLUEMK5"
E:Error in /sdcard/0/0/cm-10.2.1-d2tmo.zip
(Status 7)
Installation aborted.
result was NULL, message is: assert failed: install_zip("/sdcard/0/0/cm-10.2.1-d2tmo.zip")
I:using /data/media for /sdcard.
Yup. Thsts what I thought we'd see. Open the rom and find the updater script. Using Notepad++, edit it by replacing any of those builds with T999UVUENC2. If the one you choose to replace is listed more than once, replace it in all instances.
Delete the 3 signature files in the meta-inf folder, rezip and flash.
additional question
DocHoliday77 said:
Yup. Thsts what I thought we'd see. Open the rom and find the updater script. Using Notepad++, edit it by replacing any of those builds with T999UVUENC2. If the one you choose to replace is listed more than once, replace it in all instances.
Delete the 3 signature files in the meta-inf folder, rezip and flash.
Click to expand...
Click to collapse
Please excuse my ignorance, but I have never modified a script. I figured out how to pull out just the updater script file but I want to make sure I modify it correctly. Here is what the top bunch of lines look like in my script. If I understand correctly I am just going to replace any one of the "T999….." with "T999UVUENC2" It should make no difference which one? Also What are the signature files? I have three files in the META-INF folder, CERT.RSA, CERT.SF, and MANIFEST.MF. I presume you are talking about those three files? Please confirm that I am correct. If I need to modify anything else in the script below please let me know.
Thank you once again.
assert(getprop("ro.product.device") == "d2tmo" || getprop("ro.build.product") == "d2tmo");
assert(getprop("ro.bootloader") == "T999UVDLJA" ||
getprop("ro.bootloader") == "T999UVDLJC" ||
getprop("ro.bootloader") == "T999UVDMD5" ||
getprop("ro.bootloader") == "T999UVUEMJC" ||
getprop("ro.bootloader") == "T999VVLDLL1" ||
getprop("ro.bootloader") == "T999LUVAMB7" ||
getprop("ro.bootloader") == "T999VVLDMF2" ||
getprop("ro.bootloader") == "T999VVLUEMK5");
You are correct on both. To make it even easier, replace the build ending in MJC. All you'd have to do is change MJC to NC2.
And don't worry too much about any of this. If you happen to do something wrong it would most likely fail w/o flashing anything.
DocHoliday77 said:
You are correct on both. To make it even easier, replace the build ending in MJC. All you'd have to do is change MJC to NC2.
And don't worry too much about any of this. If you happen to do something wrong it would most likely fail w/o flashing anything.
Click to expand...
Click to collapse
I got through that and now I get a status 4 error. I know I have more than enough internal memory. I did store the CM file on the internal memory to flash it. Would that have anything to do with it? Do I have to install it from an external sd?
Here is the log file. I think also for some reason my changes are not getting saved to the name when I change EMJC to ENC2 based upon what I'm seeing below. The signature files also don't seem to delete and when I remove the .txt at the end of the file name to save it back to the zip file I also think it stays there regardless.
-- Installing: /sdcard/0/0/cm-10.2.1-d2tmo.zip
Finding update package...
I:Update location: /sdcard/0/0/cm-10.2.1-d2tmo.zip
I:using /data/media for /sdcard/0/0/cm-10.2.1-d2tmo.zip.
Opening update package...
Installing update...
Warning: No file_contexts
script aborted: assert failed: getprop("ro.bootloader") == "T999UVDLJA" ||
getprop("ro.bootloader") == "T999UVDLJC" ||
getprop("ro.bootloader") == "T999UVDMD5" ||
getprop("ro.bootloader") == "T999UVUEMJC" ||
getprop("ro.bootloader") == "T999VVLDLL1" ||
getprop("ro.bootloader") == "T999LUVAMB7" ||
getprop("ro.bootloader") == "T999VVLDMF2" ||
getprop("ro.bootloader") == "T999VVLUEMK5"
assert failed: getprop("ro.bootloader") == "T999UVDLJA" || getprop("ro.bootloader") == "T999UVDLJC" || getprop("ro.bootloader") == "T999UVDMD5" || getprop("ro.bootloader") == "T999UVUEMJC" || getprop("ro.bootloader") == "T999VVLDLL1" || getprop("ro.bootloader") == "T999LUVAMB7" || getprop("ro.bootloader") == "T999VVLDMF2" || getprop("ro.bootloader") == "T999VVLUEMK5"
E:Error in /sdcard/0/0/cm-10.2.1-d2tmo.zip
(Status 7)
Installation aborted.
result was NULL, message is: assert failed: install_zip("/sdcard/0/0/cm-10.2.1-d2tmo.zip")
I:using /data/media for /sdcard.
Can you get the log and paste the error here again? Not familiar with status 4 right off hand.
It shouldn't matter if its on internal or external sd. But you can try flashing from external.
DocHoliday77 said:
Can you get the log and paste the error here again? Not familiar with status 4 right off hand.
It shouldn't matter if its on internal or external sd. But you can try flashing from external.
Click to expand...
Click to collapse
I did , see above message. I am definitely not doing something right. I am on a Mac and using text editor to modify the file. That was my second try, the first time I did get a status 4 and I remodified and tried again and now I got a status 7 again.
It looks like the edit you made didnt take. Did you unzip the rom, make the edit and then rezip into a new file?
I don't know what text editor you should use on a mac. Go to Notepad++ website to see if they support it. If not you will have to find an editor that preserves the EOL formatting (End of Line) as Unix style. Not sure if a mac is able to do that with a built in editor.
You could make the edits on device I suppose, but its just a little more time consuming and easier to make mistakes.
DocHoliday77 said:
It looks like the edit you made didnt take. Did you unzip the rom, make the edit and then rezip into a new file?
I don't know what text editor you should use on a mac. Go to Notepad++ website to see if they support it. If not you will have to find an editor that preserves the EOL formatting (End of Line) as Unix style. Not sure if a mac is able to do that with a built in editor.
You could make the edits on device I suppose, but its just a little more time consuming and easier to make mistakes.
Click to expand...
Click to collapse
I found a way to edit the file and I know it is taking the edit. I have tried again and it still fails. However, when I view the log and it says saved in the CWM folder and I go to retrieve it, it is not there. There is no saved log that I can upload. Any thoughts?
Can I install kitkat on the SGH T999, it is the older model, not the LTE. And have you tried CM for KitKat? How is it, reasonably stable? Would that resolve my issues?

Categories

Resources