Database Info

[Q] How can I convert a Stock ROM to CWM?

I want to build an own ROM, well at least try.
After few experiments -with different success- I modded existing custom ROMs.
Now I want to release an own modded ROM and for that I need a CWM-version of Stock ROM OR -better- Ho I can convert StockROM to CWM-zip.

Rodsengard said:
I want to build an own ROM, well at least try.
After few experiments -with different success- I modded existing custom ROMs.
Now I want to release an own modded ROM and for that I need a CWM-version of Stock ROM OR -better- Ho I can convert StockROM to CWM-zip.
Click to expand...
Click to collapse
I think after you extract and mod system.rfs you should use dsixda kitchen to make the rom and add the boot.img file to zip file created then use CWM to Install the rom

The most important thing is after u have created your system,boot.img and other folder if u added a new folder in your base rom then u need to make a updater script .B-)
Sent from my GT-S5830 using xda premium

Yea but still if I place extracted system rfs AND boot.img from CSC how do I get a running updatescript, respectively what has to be in such an update script?
Don´t tell me "just place metainf folder from out of any other rom into it", cuz in that early dev-phase the metainfs of all other roms are useless, cuz they are almost ext4 and the "just extracted stock" isn´t ext4 so the metainfs of the other ROMs won´t work. ^^
Anyone else to help here?

from some Update-script i think you should do those step:
Remember end each script with ";"
Code:
unmount ("/system")[COLOR="red"];[/COLOR]
1-Format all system like you install new Windows
Code:
format("[COLOR="red"]ext4[/COLOR]", "EMMC", "/dev/block/stl[COLOR="Red"]12[/COLOR]")
Change the red with right values: rfs,ext2,3,4(file system), 12 or 13 or 14( system,data,cache partition)
With ext4 you must have a kernel support ext4
2-After format you have to mount them to copy files
Code:
mount("[COLOR="red"]ext4[/COLOR]", "EMMC", "/dev/block/stl[COLOR="red"]12[/COLOR]", "/[COLOR="red"]system[/COLOR]")
3-Extract files from zip to ROM
Code:
package_extract_dir("[COLOR="red"]system[/COLOR]", "/[COLOR="red"]system[/COLOR]")
extract system folder in ZIP to /system
Do same thing to data, cache if you have them in ZIP.
4-Fix permission
nah i dont know to much about this
You have to change permission to right state if not i dont know what happen next
Code:
set_perm([COLOR="Red"]0[/COLOR], [COLOR="red"]0[/COLOR], [COLOR="red"]0777[/COLOR], "[COLOR="red"]/system/bin/a2sd[/COLOR]")
Set permission to one file or one folder(not its contain)
Code:
set_perm_recursive ([COLOR="red"]0[/COLOR], [COLOR="red"]0[/COLOR], [COLOR="red"]0755[/COLOR], [COLOR="red"]0644[/COLOR], "[COLOR="red"]/system[/COLOR]")
Set permission to it and all thing in it
5- Link file
ahh hard to know
You should ask someone else but me
Code:
symlink [COLOR="red"]busybox[/COLOR] [COLOR="red"]SYSTEM:xbin/zcip[/COLOR]
6- Unmount partition
Code:
unmount("[COLOR="Red"]/system[/COLOR]")
And if you have your own boot.img
Code:
assert(package_extract_file("boot.img", "/tmp/boot.img"),
write_raw_image("/tmp/boot.img", "boot"),
delete("/tmp/boot.img"));
This is really basic. So may be it wont work
For advance: update-script syntax - A guide for ROM devs, modders, and themers
Anyone: how to compile kernel for fit? I almost give up cause i dont know much about linux, I tried samsugn source but my device never boot. If anyone could help this Noob, Noob 's very thank you

Thank you very much. This should be helpful

Add kernel cm10(no zip) question

HI..... my question is ... how i put this kernel(http://forum.xda-developers.com/showthread.php?t=1823671) in cm10 ...... i want that my build when finshided say kernel:francoblabblabala
thanks

You can manually put it in the ZIP and modify the updater-script to flash this to /dev/block/platform/sdhci-tegra.3/by-name/LNX.

sgt. Meow said:
you can manually put it in the zip and modify the updater-script to flash this to /dev/block/platform/sdhci-tegra.3/by-name/lnx.
Click to expand...
Click to collapse
thanks for the answer..... I don't wanna flash the kernel in recovery or something like that,,,,
i want build my rom whit that kernel........ You know how?
I have make 1 build...... And now i'm going to made some modifications and one is the kernel...... I hope put my rom over here..... Thanks my friend for the answer

You can put it in the ROM ZIP too if that's what you were asking.

But how?? Thanks
Sent from my Nexus 7 using xda app-developers app

Just put the boot.img in the ROM ZIP and edit the updater-script to include these lines:
Code:
mount("ext4", "EMMC", "/dev/block/platform/sdhci-tegra.3/by-name/APP", "/system");
assert(getprop("ro.product.device") == "grouper" || getprop("ro.build.product") == "grouper" ||
getprop("ro.product.device") == "tilapia" || getprop("ro.build.product") == "tilapia");
run_program("/sbin/sh", "-c", "mkdir /system/etc/init.d");
set_perm_recursive(0, 0, 0755, 0755, "/system/etc/init.d");
unmount("/system");
assert(package_extract_file("boot.img", "/dev/block/platform/sdhci-tegra.3/by-name/LNX"));
That's how Franco does it. You could also try dd'ing the contents of boot.img to /dev/block/platform/sdhci-tegra.3/by-name/LNX, but I don't know the exact syntax for that. You can check other kernel ZIPs and see how they install the kernel in recovery. Add the boot.img to your ROM ZIP and then edit the updater-script to include the required lines. That should do it!

Thanks you are great!!! I think that if a want add .apk is something similar??
Sent from my Nexus 7 using xda app-developers app

Yes, but for apps you don't have to change anything in the updater-script.

sgt. meow said:
Yes, but for apps you don't have to change anything in the updater-script.
Click to expand...
Click to collapse
OK ITS JUST PUT THE APPS IN SYSTEM/APP AND GIVE PERMISSIONS?
i hope don't be a fastidious man..... but you know some build.prop tweaks?? i'm copy a few tweaks for internet but......tweaks(build.prop) really makes better the performance and the battery? or just are lie?

to edit the zip of cm10, i will uncompress and edit and compress again?
thanks!!

If you are on Ubuntu, just drag and drop the files you need. And I don't think tweaks really help a lot. Just my opinion though.

alonsoch said:
to edit the zip of cm10, i will uncompress and edit and compress again?
thanks!!
Click to expand...
Click to collapse
No need. Just open the zip via Winrar and edit the file.

[ROM-FIX][JB4.2.2] Google Maps Soft Reboot Fix

Hello everyone!
I just found a temporary solution to the soft reboot problem when using Google Maps.
After searching I found this on a Galaxy Tab 7 forum, and decided to try it out... and it works!!!
I extracted and pushed the file manualy to the lib folder (fixing the permissions, of course)... and it work like a charm!
No more soft reebots.
Note I use the 6.14.4 version of Google Maps
I tested this solution on this following rom's:
[ROM][JB4.2.2][unofficial]PAC-man ROM v22.2.0 [BETA][CM/AOKP/PA]~12-05-13~
[ROM] [JB 4.2.2 JDQ39E] CM10.1 Beta 6 --- Kernel 3.4
[ROM] [JB 4.2.2 JDQ39] Unofficial ROOT-BOX Beta 6 --- kernel 3.4
I hope my solution helps everyone until this problem gets a more final fix.
Enjoy!!!
View attachment libsensorservice.zip
IMPORTANT! I remove the flashble zip and added a new one. Extract and push it manualy to \system\lib and change the permissions to (rw-r--r--)
THIS IS NOT A FLASHABLE ZIP
IF YOU PREFER A FLASH ZIP YOU CAN FIND IT HERE.. many thanks to Krislibaeer that made this file!!!
http://forum.xda-developers.com/showpost.php?p=41485703&postcount=12
(If it helped you, please press thanks)

thanks for that now i know where the problem is
the new changes to get gyroscope/photosphere working on other devices then google devices breaks gmaps and other apps like this

I see that its flashable
But with you file and source got failed

As he wrote, you must change this file manually, ZIP is only a source of the correct lib.

sv2hqx said:
I see that its flashable
But with you file and source got failed
Click to expand...
Click to collapse
thats the wrong updater script
Code:
assert(getprop("ro.product.model") == "GT-P3100" ||
getprop("ro.product.name") == "espressorfxx" ||
getprop("ro.product.device") == "espressorf" ||
getprop("ro.product.model") == "GT-P3110" ||
getprop("ro.product.model") == "GT-P3113" ||
getprop("ro.product.name") == "espressowifixx" ||
getprop("ro.product.device") == "espressowifi" ||
getprop("ro.product.model") == "GT-P5100" ||
getprop("ro.product.name") == "espresso10rfxx" ||
getprop("ro.product.device") == "espresso10rf" ||
getprop("ro.product.model") == "GT-P5110" ||
getprop("ro.product.model") == "GT-P5113" ||
getprop("ro.product.name") == "espresso10wifixx" ||
getprop("ro.product.device") == "espresso10wifi");
mount("ext4", "EMMC", "/dev/block/mmcblk0p9", "/system");
package_extract_dir("system", "/system");
set_perm(0, 0, 0644, "/system/lib/libsensorservice.so");
unmount("/system");
i provide a new one
do not flash this it can cause damages on the phone
please take the link down

I've just tried to replace "libsensorservice.so" that you provided in "/system/lib/" and the phone doesn't reboot anymore. I have to come back to my backup!

I have upgraded to PAC-Man v22.2.0 and in recovery after the fresh installation I copied the file to the right location (zip didn't worked for me too).
I am trying right now...
gMaps and Ingress works

SFCMouco said:
Hello everyone!
I just found a temporary solution to the soft reboot problem when using Google Maps.
After searching I found this forum http://forum.xda-developers.com/showpost.php?p=40701377&postcount=2090 and decided to try it out... and it works!!!
I extracted and pushed the file manualy to the lib folder (fixing the permissions, of course)... and it work like a charm!
No more soft reebots.
Note I use the 6.14.4 version of Google Maps
I tested this solution on this foluing rooms:
[ROM][JB4.2.2][unofficial]PAC-man ROM v22.2.0 [BETA][CM/AOKP/PA]~12-05-13~
[ROM] [JB 4.2.2 JDQ39E] CM10.1 Beta 6 --- Kernel 3.4
[ROM] [JB 4.2.2 JDQ39] Unofficial ROOT-BOX Beta 6 --- kernel 3.4
I hope my solution helps everyone until this problem gets a more final fix.
Enjoy!!!
View attachment 1966705
(If it helped you, please press thanks)
Click to expand...
Click to collapse
Worked for me. Pushed the lib-file to the /system/lib directory. Set permissions to 644. Downloaded the newest Google MAPS. Working like hell ....... :good:

dece27 said:
I've just tried to replace "libsensorservice.so" that you provided in "/system/lib/" and the phone doesn't reboot anymore. I have to come back to my backup!
Click to expand...
Click to collapse
nevertheless thanks again to show this post to get fixed the issue
i upload the new file now it is compiled with carbon source so try and give feedback --> few minutes it is ready
gmaps_fix

sv2hqx said:
I see that its flashable
But with you file and source got failed
Click to expand...
Click to collapse
Dont flash the zip file... I take that one down and put a new one. Just extract the file and push manuly the file changing the permissions to rw-r--r--

I push it manually and works
Updated maps too and works perfect
SFCMouco said:
Dont flash the zip file... I take that one down and put a new one. Just extract the file and push manuly the file changing the permissions to rw-r--r--
Click to expand...
Click to collapse

here i made a flashable zip gmaps_fix

krislibaeer said:
here i made a flashable zip gmaps_fix
Click to expand...
Click to collapse
Does this work with your AOKP rom?

krislibaeer said:
here i made a flashable zip gmaps_fix
Click to expand...
Click to collapse
Good work! I've flashed on CM 10.1 Beta 6.1 by davidteri91 and it works very well; thanks a lot

Melombine said:
Does this work with your AOKP rom?
Click to expand...
Click to collapse
If you use the now flash file and push it manualy... Yes it does!

SFCMouco said:
If you use the now flash file and push it manualy... Yes it does!
Click to expand...
Click to collapse
Yeah, works like charm! Thanks, because I really have use for the Google Maps now that I have my driving licence

Thanks!
Inviato dal mio GT-P3110 con Tapatalk 2

"Just extract the file and push manuly the file changing the permissions to rw-r--r--"
Well, flashable zip works, but how can i change the permission. I have root explorer and can do that in system but not on my sd card because I have to do it because when i copied without changing permission I have a reboot and have to restore a Backup or flash the zip.
Someone knows how to copy it manually? Thanks.

Thanksss!
Enviado desde mi MB526 usando Tapatalk 2

KingKuno said:
"Just extract the file and push manuly the file changing the permissions to rw-r--r--"
Well, flashable zip works, but how can i change the permission. I have root explorer and can do that in system but not on my sd card because I have to do it because when i copied without changing permission I have a reboot and have to restore a Backup or flash the zip.
Someone knows how to copy it manually? Thanks.
Click to expand...
Click to collapse
with my flashable zip it fix the permission and all works well
just the other flashable zip had a wrong updater-script

Difference between klte and kltespr?

As we know, Cyanogenmod has released official nightlies for the Samsung Galaxy S5 Sprint (or kltespr in their words). I tried to flash the latest nightly and it fails with the statement "This is for kltespr devices. This device is a klte." So I am wondering... if the nightlies are for the Sprint Galaxy S5, what is the difference between the klte and kltespr? Also, how can I flash this "safely" if I can at all?

Delete the top section of the updater script so that the first line starts withe the word mount

vinman12 said:
Delete the top section of the updater script so that the first line starts withe the word mount
Click to expand...
Click to collapse
Sorry, I'm not on that level yet. How would you do that?

Still Doesn't Work
ethomas94 said:
Sorry, I'm not on that level yet. How would you do that?
Click to expand...
Click to collapse
Normally, you would extract the zip file of the rom, then navigate /META-INF/com/google/android/updater-script (open with Notepad++ or Sublime Text) and then delete the first couple of lines until the first word is mount. I've tried this and it doesn't seem to work though. The installation is still aborted with no error messages whatsoever.

All you need to do is remove the following from the "META-INF\com\google\android\" folder. It's the first line, just remove it and it will install.
Line to remove:
Code:
assert(getprop("ro.product.device") == "kltespr" || getprop("ro.build.product") == "kltespr" || abort("This package is for \"kltespr\" devices; this is a \"" + getprop("ro.product.device") + "\"."););

MorningStarGG said:
All you need to do is remove the following from the "META-INF\com\google\android\" folder. It's the first line, just remove it and it will install.
Line to remove:
Code:
assert(getprop("ro.product.device") == "kltespr" || getprop("ro.build.product") == "kltespr" || abort("This package is for \"kltespr\" devices; this is a \"" + getprop("ro.product.device") + "\"."););
Click to expand...
Click to collapse
This doesnt work. Ive removed that code and continue to get other errors. I will try to upload a log. Im not familiar with twrp but cwm doesnt have an official recovery for this phone yet. Ill post back if I can get the log or if I can solve the problem.
---------- Post added at 01:14 PM ---------- Previous post was at 12:42 PM ----------
God I hate twrp. So after editing the zip file I get "error flashing zip (gives the location of zip here)
Updating partition details
Failed.
After copying the recovery log to the phone I open it up and its blank. Just wish there was a cwm recovery that had backup and restore options. I can care less if its touch.

hastack97 said:
Normally, you would extract the zip file of the rom, then navigate /META-INF/com/google/android/updater-script (open with Notepad++ or Sublime Text) and then delete the first couple of lines until the first word is mount. I've tried this and it doesn't seem to work though. The installation is still aborted with no error messages whatsoever.
Click to expand...
Click to collapse
weinerwad3000 said:
This doesnt work. Ive removed that code and continue to get other errors. I will try to upload a log. Im not familiar with twrp but cwm doesnt have an official recovery for this phone yet. Ill post back if I can get the log or if I can solve the problem.
---------- Post added at 01:14 PM ---------- Previous post was at 12:42 PM ----------
God I hate twrp. So after editing the zip file I get "error flashing zip (gives the location of zip here)
Updating partition details
Failed.
After copying the recovery log to the phone I open it up and its blank. Just wish there was a cwm recovery that had backup and restore options. I can care less if its touch.
Click to expand...
Click to collapse
MorningStarGG said:
All you need to do is remove the following from the "META-INF\com\google\android\" folder. It's the first line, just remove it and it will install.
Line to remove:
Code:
assert(getprop("ro.product.device") == "kltespr" || getprop("ro.build.product") == "kltespr" || abort("This package is for \"kltespr\" devices; this is a \"" + getprop("ro.product.device") + "\"."););
Click to expand...
Click to collapse
I've done it multiple ways with multiple programs on multiple operating systems. I still only the "error" message and the "Failed" message in red on top. It doesn't tell me why either. I wonder if it's just a 900P thing. It does suck, though.
I used a Mac and used Gedit, EZ7z, Zipeg and it didn't work. On my phone, I used Es File Explorer and Winzip for Android. Both didn't work. This is getting to be very annoying.

ethomas94 said:
I've done it multiple ways with multiple programs on multiple operating systems. I still only the "error" message and the "Failed" message in red on top. It doesn't tell me why either. I wonder if it's just a 900P thing. It does suck, though.
I used a Mac and used Gedit, EZ7z, Zipeg and it didn't work. On my phone, I used Es File Explorer and Winzip for Android. Both didn't work. This is getting to be very annoying.
Click to expand...
Click to collapse
The file is called "updater-script" it is in the "META-INF\com\google\android\" folder inside the nightly zip file. Just remove the first line in that file the line to remove should read the following:
Code:
assert(getprop("ro.product.device") == "kltespr" || getprop("ro.build.product") == "kltespr" || abort("This package is for \"kltespr\" devices; this is a \"" + getprop("ro.product.device") + "\"."););
You have to extract the file, remove that line, and then put the modified file back into the zip file. It works I have done it several times now. If it is indeed failing saying you need a kltespr device and you do have a Sprint S5(AKA SM-G900P) this is the only thing that is preventing your install.

MorningStarGG said:
The file is called "updater-script" it is in the "META-INF\com\google\android\" folder inside the nightly zip file. Just remove the first line in that file the line to remove should read the following:
Code:
assert(getprop("ro.product.device") == "kltespr" || getprop("ro.build.product") == "kltespr" || abort("This package is for \"kltespr\" devices; this is a \"" + getprop("ro.product.device") + "\"."););
You have to extract the file, remove that line, and then put the modified file back into the zip file. It works I have done it several times now. If it is indeed failing saying you need a kltespr device and you do have a Sprint S5(AKA SM-G900P) this is the only thing that is preventing your install.
Click to expand...
Click to collapse
I'll try that and get back to you. I was extracting the entire zip and altering it, then re-zipping the whole thing.

I fixed it.
What I was doing wrong was that after I extracted everything from the zip and edited the updater-script file, I would zip the extracted folder with all of the files in it, thus making a zip file, then a folder, then all of the files and stuff inside. That prevented the phone from flashing it, so it gave me the "error" message with no description (probably because it didn't know why it failed).
I was supposed to only zip the files that were in the extracted folder together into one zip, not the entire extracted folder with everything in it.

Also, a lot of people were saying that the edited updater-script file would not stay saved and would just revert as soon as you left the editor no matter what. I've got around this by using Gedit (for linux or mac, I don't know about pc) and hitting "save as...", keeping the original name, then simply replacing the original file with the edited one.

It would be nice if one of these sharp guys would post them already altered.

ethomas94 said:
I fixed it.
What I was doing wrong was that after I extracted everything from the zip and edited the updater-script file, I would zip the extracted folder with all of the files in it, thus making a zip file, then a folder, then all of the files and stuff inside. That prevented the phone from flashing it, so it gave me the "error" message with no description (probably because it didn't know why it failed).
I was supposed to only zip the files that were in the extracted folder together into one zip, not the entire extracted folder with everything in it.
Click to expand...
Click to collapse
Im sorry but this is very hard to understand. I still cant get it flashed. Step by step this is what I did.
1.) Extract the zip file.
2.) Locate the updater script file.
3.) Edit script file so mount is the first word in the code.
4.) Save edited script file.
5.) Rezip the entire extracted file.
What am I doing wrong? It will not flash.

mempho69 said:
It would be nice if one of these sharp guys would post them already altered.
Click to expand...
Click to collapse
weinerwad3000 said:
Im sorry but this is very hard to understand. I still cant get it flashed. Step by step this is what I did.
1.) Extract the zip file.
2.) Locate the updater script file.
3.) Edit script file so mount is the first word in the code.
4.) Save edited script file.
5.) Rezip the entire extracted file.
What am I doing wrong? It will not flash.
Click to expand...
Click to collapse
I'm only a new member (well, I was inactive for a long time) so I can't post large files.
Here's what you do.
1. Extract the zip file.
2. Navigate to the updater-script.
3. Edit it so that "mount" is the first thing it says (delete everything before that word).
4. Save it (or replace the file with the new one, which is how I got the save to stick)
5. ZIP ONLY THE FILES INSIDE THE MAIN FOLDER INTO ONE FILE. Don't zip the folder that came about after the extraction, only zip the files inside the folder (meta, img, etc) into one zip. If you zip the folder also, it will create a zip file, then the folder, then the contents. It will confuse the flash, that expects the contents to be directly after the zip layer, and not a zip, then a folder, then the contents; and the flash will fail without reason.
6. After the zip, it's ready.
If that did not work, then try only extracting the updater-script, then editing it, then putting it back in the zip (you may have to replace the original, do it)
The former is how it worked to me. Also, if you are using the 900P (Sprint Variant), get KT Recovery! It worked for me and now I can flash directly from cyanogenmod without editing the updater-script. There is a link in the KLTESPR general forum (It says Cyanogenmod is officially supporting us!). Simply flash it and it will replace the current recovery for your rooted phone as long as it already has a custom recovery. KT Recovery is a modded TWRP, just so you know. It works!
Also, it may not look like there is a folder after the zip if you zip the folder, but it won't flash if you zip the folder. That's why i say only zip the contents (meta, img, etc) into one zip!

KT Recovery is a modded TWRP, just so you know. It works!

ethomas94 said:
I'm only a new member (well, I was inactive for a long time) so I can't post large files.
Here's what you do.
1. Extract the zip file.
2. Navigate to the updater-script.
3. Edit it so that "mount" is the first thing it says (delete everything before that word).
4. Save it (or replace the file with the new one, which is how I got the save to stick)
5. ZIP ONLY THE FILES INSIDE THE MAIN FOLDER INTO ONE FILE. Don't zip the folder that came about after the extraction, only zip the files inside the folder (meta, img, etc) into one zip. If you zip the folder also, it will create a zip file, then the folder, then the contents. It will confuse the flash, that expects the contents to be directly after the zip layer, and not a zip, then a folder, then the contents; and the flash will fail without reason.
6. After the zip, it's ready.
If that did not work, then try only extracting the updater-script, then editing it, then putting it back in the zip (you may have to replace the original, do it)
The former is how it worked to me. Also, if you are using the 900P (Sprint Variant), get KT Recovery! It worked for me and now I can flash directly from cyanogenmod without editing the updater-script. There is a link in the KLTESPR general forum (It says Cyanogenmod is officially supporting us!). Simply flash it and it will replace the current recovery for your rooted phone as long as it already has a custom recovery. KT Recovery is a modded TWRP, just so you know. It works!
Also, it may not look like there is a folder after the zip if you zip the folder, but it won't flash if you zip the folder. That's why i say only zip the contents (meta, img, etc) into one zip!
Click to expand...
Click to collapse
Thank you. I installed the recovery and the file worked. I tried downloading the recovery a few days ago but I got a 404 error from the link. I couldn't stand the stock os so you helped me out tremendously. Thanks again.

No problem!
Sent from my SM-G900P using XDA Free mobile app

So, now I'm stuck. I was rooted, had plain old cwm installed and was able to flash the nightlies of CM11 to my lil hearts content. Then, for... reasons, I had to Odin back to stock and reroot, reflash recovery. Upon flashing Philz touch using Odin, and trying to flash 10/3 nightly, I start getting the error message I am seeing in this thread. First: I'd like to not have to do the fix shown in here. Is there a version of CWM that I can flash that will bypass all of this unpleasantness? Second, I tried, using Notepad++ to remove this line, ya know, the one that is supposedly the fix for all of this?. I highlight it, and nothing works to get rid of it. I hit cut, delete, kb shortcuts, you name it. Nothing works. So, either fix would be helpful, although my first choice would be just going back to the CWM that worked without all this added aggravation. Thanks in advance guys.

AuGmENTor said:
So, now I'm stuck. I was rooted, had plain old cwm installed and was able to flash the nightlies of CM11 to my lil hearts content. Then, for... reasons, I had to Odin back to stock and reroot, reflash recovery. Upon flashing Philz touch using Odin, and trying to flash 10/3 nightly, I start getting the error message I am seeing in this thread. First: I'd like to not have to do the fix shown in here. Is there a version of CWM that I can flash that will bypass all of this unpleasantness? Second, I tried, using Notepad++ to remove this line, ya know, the one that is supposedly the fix for all of this?. I highlight it, and nothing works to get rid of it. I hit cut, delete, kb shortcuts, you name it. Nothing works. So, either fix would be helpful, although my first choice would be just going back to the CWM that worked without all this added aggravation. Thanks in advance guys.
Click to expand...
Click to collapse
May be a little late, but i put up a custom version of TWRP that will allow installing, and updating via their update section in settings. Its in the dev section of sprint gs5 here at xda. Will try to post a link if i remember.
http://forum.xda-developers.com/showthread.php?p=52260413

miked63017 said:
May be a little late, but i put up a custom version of TWRP that will allow installing, and updating via their update section in settings. Its in the dev section of sprint gs5 here at xda. Will try to post a link if i remember.
Click to expand...
Click to collapse
I flashed PacMan ROM, which for some reason worked. So for now I'm stable. But I will be looking to go back to my first true love.... Cyanogenmod!

How to make patch/[noob friendly]

HERE IS MY PORTING TECHNIQUE : CLICK ME
WHY WE NEED PATCH
Porting a ROM lot of bugs are coming
and using a patch we can fix them easily because we do not have to flash the whole ROM again
Click to expand...
Click to collapse
This tutorial show you how to make patch ::
At first make a folder name patch ::
Next step ::
Copy META-INF folder from any other working ROM of your device
Click to expand...
Click to collapse
Open the meta-imf/com/google/
Click to expand...
Click to collapse
Next Step ::
In this step you need notepad++ :fingers-crossed:
open the updater-script and delete all the lines
Click to expand...
Click to collapse
And then add this lines ::
Code:
ui_print("Mounting System...");
mount("ext4", "EMMC", "[COLOR="Red"]/dev/block/mmcblk0p6[/COLOR]", "/system");
package_extract_dir("system", "/system");
unmount("/system");
ui_print("extract boot.img");
package_extract_file("boot.img", "/dev/bootimg");
The red line depend upon your mount point of your device
NEXT STEP ::
now create a system folder in the patch folder and Next steps i hope you can understand
Place the files you want with proper address
And zip the file and flash it
You can find a example zip bellow :: :victory:
Give a tums up if it is helpful :good:

Thank u sir! i will try soon on MIUI

I don't understand how to make patch
Pleas bro I don't understand the method can't you repeat me with details pleas and if you can do an exemplary