Database Develop

Converting CWM v2 scripts/zips to CWM v3

There has been a lot of discussion on what works on ClockWorkMod v3 and what doesn't. One of the biggest problems (besides ROM installations) is how to apply existing ZIP files that don't work in CWM3 because they are outdated.
So, if you have upgraded to CWM v3 and want to use some old zips there is an answer
nubecoder in the Android Development and Hacking > Android Software Development forum came up with an excellent tool for converting the old update-script to the new updater-scrip and binary needed for CWM3
Give it a look:
http://forum.xda-developers.com/showthread.php?t=903598

Thanks for the link..
I just wish all these devs didn't always use friggin Windows!

CCrew said:
Thanks for the link..
I just wish all these devs didn't always use friggin Windows!
Click to expand...
Click to collapse
I hear ya. If I didn't need Windows for work I would be 100% linux

so how exactly do i use this?

IIDIncII said:
so how exactly do i use this?
Click to expand...
Click to collapse
Extract the zip to a folder. Run it. Select open then the zip or script you want to convert. then save it.

Great find Nils. I guess I need to convert mine.
EDIT: It converted them all perfectly, once I realized I needed to choose "Incredible" from the device menu. LOL

If you want an alternative to using the script converter I attached 2 zip files. One is for updates to the /system/app/ folder and the other is /system/framework/ folder
All you need to do is use 7zip to copy (drag and drop) your files to the appropriate sub folder in the zip file.
You can then name the zip file to whatever you like.

Sorry to muck up the thread with this question but since it's on topic... how do i flash back to the old version of CWM? since rom manager just comes up with an error...
nevermind I got one of the older 2.5 to work

This app was updated just this morning with the option to convert scripts for the incredible. I've tried it on a few zips and it works perfect

NilsP said:
I hear ya. If I didn't need Windows for work I would be 100% linux
Click to expand...
Click to collapse
I agree, if Trimble would embrace Linux I could avoid windowz for the rest of my life...
Sent from my ADR6300 using Tapatalk

Kernel Manager

TeamWIN has now made their Kernel Manager app work with the XOOM. What it allows you to do, is flash kernels inside android. No more booting into fastboot, or even running update.zips.
https://market.android.com/developer?pub=Team+Win

Just downloaded and just what we need, it is awesome, will get the paid version as promised in the irc LOL
bwcorvus said:
TeamWIN has now made their Kernel Manager app work with the XOOM. What it allows you to do, is flash kernels inside android. No more booting into fastboot, or even running update.zips.
https://market.android.com/developer?pub=Team+Win
Click to expand...
Click to collapse

It corrupted my kernel just fyi to the devs

sfld said:
It corrupted my kernel just fyi to the devs
Click to expand...
Click to collapse
it didn't corrupt your kernel. Just manually push the BCM4329.ko file through adb.
or just to be safe just push everything again manually. That way you know everything was done right.

sfld said:
It corrupted my kernel just fyi to the devs
Click to expand...
Click to collapse
if there are issues, please join us in #kernel-manager on irc.freenode.net. we encourage all devs to participate in troubleshooting any outstanding issues on all devices.

this broke my wifi. what do i do? i have no idea how to do the steps above with adb

grasshoxda said:
this broke my wifi. what do i do? i have no idea how to do the steps above with adb
Click to expand...
Click to collapse
Download and run the one click root file, it will repatch with the kernel that comes in it or you can place the files from the latest kernel release into it. I think thats the best option for you if you are not comfortable using adb.
Get the one click root here.
http://forum.xda-developers.com/showthread.php?t=1011196

i reran rootmyxoom and have wifi back. how to i use this then without losing wifi?

slatejones said:
Download and run the one click root file, it will repatch with the kernel that comes in it or you can place the files from the latest kernel release into it. I think thats the best option for you if you are not comfortable using adb.
Get the one click root here.
http://forum.xda-developers.com/showthread.php?t=1011196
Click to expand...
Click to collapse
lol just finished doing exactly that thanks tho

how do i go about placing the new files into it?

grasshoxda said:
lol just finished doing exactly that thanks tho
Click to expand...
Click to collapse
It could be an issue with the download. Find the file with astro or root explorer and delete it then redownload, or download to your computer and place it on the xoom and have the app install from the sd card instead of downloading it.
If it still doesnt work for you, just reflash the one click root and give it a day or two for the devs to update the app or something.
Hope everything works out for you

grasshoxda said:
how do i go about placing the new files into it?
Click to expand...
Click to collapse
Well.... Uhhh.... Thats not something I tried myself. But I think it would be pretty easy... When you extract the root my xoom folder to your computer, open it up and find the kernel files... then replace them with the updated files from the 1.3.2 zip file. Just unzip the 1.3.2 folder and copy and paste.
Hope this helps

ive opend the rootmyxoom folder and i dont know where to put the contents from the zip

grasshoxda said:
ive opend the rootmyxoom folder and i dont know where to put the contents from the zip
Click to expand...
Click to collapse
I dont have a current version of the one click root, but I would think to look inside either the wifi root folder or the tiamat folder (inside the rootmyxoom folder). Whichever one has the same files from the 1.3.2 folder, copy and paste them over to that folder inside the rootmyxoom folder and you should be golden.

ive looked thru them all , i dont see any files in any of those folders that look like the ones that come in the zip

open up the tiamit files in the root my xoom folder and replace with whatever kernel you want to use. I did this three times with tiamit 1.3.0, and .1 and .2. You can try to just replace the entire file or go in and replace the indiviual files from within the tiamit kernel folder. Be careful though if you replace the wrong files or mix them up could be bad results, usually just no wifi or bootloops.
Oh by the way i always did all this on a windows based computer that way the files look the same or similar
grasshoxda said:
ive looked thru them all , i dont see any files in any of those folders that look like the ones that come in the zip
Click to expand...
Click to collapse

This works great, now if only there can be a similar app that installs themes

Wow, Kernel manager just solved my problem of flashing the new tiamat 1.4.0 kernel.
Was having issues in CWM, instead of pulling my hair out in testing it out via trial by error. Had a (status 0) error while flashing kernel in CWM.
It was resolved by using Kernel Manager!!!

Can't access link to download apk? Anyone have this problem?
Edit: got it downloaded
Sent from my Xoom using Tapatalk

worked great with 1.3 but as soon as i tried 1.4 it broke my wifi, gonna wait till next update and try again, dont like the 1click root method

[SOLVED]How to convert system.sin to system.img?

Been looking around and I cannot get info(or I may have missed it) on how to convert system.sin to system.img.
The reason I want the system.img is I'd like to try deodexing my own JB(HKversion) stock rom.
how can I manage it in dsixda's kitchen, it says I need a system.img or either one of the following:
The format for each ROM must be one of the following:
- system.img + optional boot.img/lib.img (e.g. stock ROM or Nandroid)
- ZIP file for a custom ROM (e.g. update.zip)
- ZIP file containing *.img (e.g. stock rom.zip)
- ZIP file containing shipped ROM in SYSTEM + BOOT folder format
- Working folder made with this kitchen (e.g. WORKING_old_rom)
What I've already done so far was pulled out the system.sin from an FTF and made it system.ext4 in flashtool. And I also have extracted all the system files but I don't know how to go from here LoL.
Thanks in advance for any inputs guys.

Rycon33 said:
Been looking around and I cannot get info(or I may have missed it) on how to convert system.sin to system.img.
The reason I want the system.img is I'd like to try deodexing my own JB(HKversion) stock rom.
how can I manage it in dsixda's kitchen, it says I need a system.img or either one of the following:
The format for each ROM must be one of the following:
- system.img + optional boot.img/lib.img (e.g. stock ROM or Nandroid)
- ZIP file for a custom ROM (e.g. update.zip)
- ZIP file containing *.img (e.g. stock rom.zip)
- ZIP file containing shipped ROM in SYSTEM + BOOT folder format
- Working folder made with this kitchen (e.g. WORKING_old_rom)
What I've already done so far was pulled out the system.sin from an FTF and made it system.ext4 in flashtool. And I also have extracted all the system files but I don't know how to go from here LoL.
Thanks in advance for any inputs guys.
Click to expand...
Click to collapse
Just rename it.
That works if you want to use system.sin in dsixdas kitchen to make your own rom.
The instructions say to rename system.sin to system.img
PS, in fact you can just use system.sin, check in the first post for supported devices, it tlks about what to do for sony phones

gregbradley said:
Just rename it.
That works if you want to use system.sin in dsixdas kitchen to make your own rom.
The instructions say to rename system.sin to system.img
PS, in fact you can just use system.sin, check in the first post for supported devices, it tlks about what to do for sony phones
Click to expand...
Click to collapse
- If using stock FTF for kitchen:
1) Unzip FTF file, extract the system.sin
2) Dump system image from system.sin w/ Flashtool
(Advanced-> SIN Editor)
3) Rename dumped file to system.img
mate, I tried renaming it and put it on "original_update" folder but still the file cannot be detected I still cannot create a working folder and says
CREATE WORKING FOLDER FOR ROM
==============================
Ensure there is at least one ROM under the 'original_update' folder!
Select an option:
s - Show supported formats
x - Abort, don't create working folder
Or press Enter to continue
?
I also tried renaming the flashtool's dumped data(system.ext4) to system.img but still to no avail.
Any other way aside from system.img thing?

Rycon33 said:
- If using stock FTF for kitchen:
1) Unzip FTF file, extract the system.sin
2) Dump system image from system.sin w/ Flashtool
(Advanced-> SIN Editor)
3) Rename dumped file to system.img
mate, I tried renaming it and put it on "original_update" folder but still the file cannot be detected I still cannot create a working folder and says
CREATE WORKING FOLDER FOR ROM
==============================
Ensure there is at least one ROM under the 'original_update' folder!
Select an option:
s - Show supported formats
x - Abort, don't create working folder
Or press Enter to continue
?
I also tried renaming the flashtool's dumped data(system.ext4) to system.img but still to no avail.
Any other way aside from system.img thing?
Click to expand...
Click to collapse
wait, let me boot into linux and I will check

gregbradley said:
wait, let me boot into linux and I will check
Click to expand...
Click to collapse
mate, btw I'm only using cygwin in win7 if that matters on my issue

Rycon33 said:
mate, btw I'm only using cygwin in win7 if that matters on my issue
Click to expand...
Click to collapse
No, it doesnt matter, I did it with that setup, but its much easier with a ubuntu dual boot.
What you did should work.
Extract system.sin
Dump it with flash tool to get system.ext4, rename to system.img and put in original input folder.
then choose create working folder....
try it again,

gregbradley said:
No, it doesnt matter, I did it with that setup, but its much easier with a ubuntu dual boot.
What you did should work.
Extract system.sin
Dump it with flash tool to get system.ext4, rename to system.img and put in original input folder.
then choose create working folder....
try it again,
Click to expand...
Click to collapse
thanks mate, after I re-do the dump-data in flashtool, now system.img(renamed from system.ext4) can be detected
got another question again, just to confirm what's the API level? is it 16 for Android 4.1.2? coz I only see 4.1.1 for level 16

Rycon33 said:
thanks mate, after I re-do the dump-data in flashtool, now system.img(renamed from system.ext4) can be detected
got another question again, just to confirm what's the API level? is it 16 for Android 4.1.2? coz I only see 4.1.1 for level 16
Click to expand...
Click to collapse
if you have the latest version of everything it should be OK.
Just give it a go and see...
I used the same setup I have for my latest release as I did for my original ICS release, so the api level should be OK
EDIT
I do love your sig pic, where did you get it from? Or did you make it yourself?

gregbradley said:
if you have the latest version of everything it should be OK.
Just give it a go and see...
I used the same setup I have for my latest release as I did for my original ICS release, so the api level should be OK
EDIT
I do love your sig pic, where did you get it from? Or did you make it yourself?
Click to expand...
Click to collapse
with regards to my sig banner, i got it from one of the post from G+ last time, here's a copy of the actual file -> https://dl.dropbox.com/u/28587036/Android/Android_Evolution.jpg
ok I used 16, another question , what will I do to the one file that was never deodexed? it is the playstationcertified.odex
Could not deodex the following (you can try to deodex these files again):
playstationcertified.odex
A summary of the deodexing has been logged in deodex_040813_020606.log
71 *.odex files remain in system/app
1 *.odex files remain in system/framework

Rycon33 said:
with regards to my sig banner, i got it from one of the post from G+ last time, here's a copy of the actual file -> https://dl.dropbox.com/u/28587036/Android/Android_Evolution.jpg
ok I used 16, another question , what will I do to the one file that was never deodexed? it is the playstationcertified.odex
Could not deodex the following (you can try to deodex these files again):
playstationcertified.odex
A summary of the deodexing has been logged in deodex_040813_020606.log
71 *.odex files remain in system/app
1 *.odex files remain in system/framework
Click to expand...
Click to collapse
I have always just left it in for my releases, but seeing as I dont use it, i have personally deleted both the file and the odex file.
I think its the same for all stock based roms...there will be some aditional sony security on that file as it enables you to download sony play station games so the kitchen is not set up to integrate the odex file into the original one.

gregbradley said:
I have always just left it in for my releases, but seeing as I dont use it, i have personally deleted both the file and the odex file.
I think its the same for all stock based roms...there will be some aditional sony security on that file as it enables you to download sony play station games so the kitchen is not set up to integrate the odex file into the original one.
Click to expand...
Click to collapse
oh ok.
mate, apologies for many questions, this is my first try so I'm still confuse of many things
so after I de-odexed, what's next?
> ADVANCED OPTIONS
11 - De-odex files in your ROM
12 - Tools for boot image (unpack/re-pack/etc.)
13 - Add /data/app functionality
14 - Add /etc/init.d scripts support (busybox run-parts)
15 - Unpack data.img
16 - Sign APK or ZIP file(s)
17 - Convert update-script or updater-script
18 - Plugin scripts
99 - Build ROM from working folder
0 - BACK TO MAIN MENU
basically I only want a deodexed ROM and the CWM and root retained

Rycon33 said:
oh ok.
mate, apologies for many questions, this is my first try so I'm still confuse of many things
so after I de-odexed, what's next?
> ADVANCED OPTIONS
11 - De-odex files in your ROM
12 - Tools for boot image (unpack/re-pack/etc.)
13 - Add /data/app functionality
14 - Add /etc/init.d scripts support (busybox run-parts)
15 - Unpack data.img
16 - Sign APK or ZIP file(s)
17 - Convert update-script or updater-script
18 - Plugin scripts
99 - Build ROM from working folder
0 - BACK TO MAIN MENU
basically I only want a deodexed ROM and the CWM and root retained
Click to expand...
Click to collapse
What do you want to do?
You cant do (12) use championshipswimmers kernel kitchen for that.
But i do suggest adding 14, and rooting it (thats in the main menu)
also, zipalign apks...but it will ask you to do that when you compile it
Other than that its up to you. Just try some different options out and see what you think...thats the best way to learn, if you see my releases, the first two versions were not released because I was learning and playing around with it
Make sure though that you dont use the updater script it produces, its wrong for our phones.
"Borrow" one from a working ROM in our dev section, just ask permission first.

Rycon33 said:
thanks mate, after I re-do the dump-data in flashtool, now system.img(renamed from system.ext4) can be detected
got another question again, just to confirm what's the API level? is it 16 for Android 4.1.2? coz I only see 4.1.1 for level 16
Click to expand...
Click to collapse
For android 4.1.2 api must be set @16 othervise it wont boot
Sent from my LT29i using xda app-developers app

gregbradley said:
What do you want to do?
You cant do (12) use championshipswimmers kernel kitchen for that.
But i do suggest adding 14, and rooting it (thats in the main menu)
also, zipalign apks...but it will ask you to do that when you compile it
Other than that its up to you. Just try some different options out and see what you think...thats the best way to learn, if you see my releases, the first two versions were not released because I was learning and playing around with it
Make sure though that you dont use the updater script it produces, its wrong for our phones.
"Borrow" one from a working ROM in our dev section, just ask permission first.
Click to expand...
Click to collapse
asterix005 said:
For android 4.1.2 api must be set @16 othervise it wont boot
Sent from my LT29i using xda app-developers app
Click to expand...
Click to collapse
ok mates, thank you very much, I managed to de-odexed my stock ROM:good:

This is what I did. Using flashtool, I dumped my system.sin file to get a ext4 file. Then I open it with ext4 reader and extracted the contents. I then placed it in a folder called 'system' and proceed with the android kitchen.
Humans have evolved to be smarter, but there's one thing we can't get rid off. It's human stupidity.

If you still want to deodex playstationcertified.odex rename it to com.playstation.playstationcertified.odex.
That did the trick for me in earlier firmware versions.
Sent from my phone using XDA Premium

i try many times but it's all show this
CREATE WORKING FOLDER FOR ROM
==============================
Ensure there is at least one ROM under the 'original_update' folder!
Select an option:
s - Show supported formats
x - Abort, don't create working folder
Or press Enter to continue
any idea or should i press enter to continue?
i try with system.img from xperia TX rom 1.67

lucky92 said:
i try many times but it's all show this
CREATE WORKING FOLDER FOR ROM
==============================
Ensure there is at least one ROM under the 'original_update' folder!
Select an option:
s - Show supported formats
x - Abort, don't create working folder
Or press Enter to continue
any idea or should i press enter to continue?
i try with system.img from xperia TX rom 1.67
Click to expand...
Click to collapse
why don't you press it an see?
anyway, have you used flashtool to extract the system.sin into an ext4 extension yet?

gregbradley said:
why don't you press it an see?
anyway, have you used flashtool to extract the system.sin into an ext4 extension yet?
Click to expand...
Click to collapse
i tried extract thee system.sin into ext4 and rename it to sysmtem.img but no luck
update: after re-dump system.sin and press countinue, it's seem ok, maybe my fault.
Thank you anyway :laugh:

Sorry but I have another question, after i make a flashable zip and flash through CWM, it always stuck at Sony logo, any idea ?

[Q]Porting MiniCM 10 to golfu

Hey everybody,
I just learnt the method for porting ROMs...
So i am trying to port MINICM 10 from HTC Explorer to Desire C and i want to know whether there is no harm in doing so, i would be using cm 10 build 3 as a base ROM, so i hope when i complete the base rom and when i flash it, it doesn't brick my phone !
I am still very junior over here in this section but i still want to port this ROM...Please everybody give me your suggestions so as to if there is any harm in doing so !
Thanks in advance

warrior1208 said:
Hey everybody,
I just learnt the method for porting ROMs...
So i am trying to port MINICM 10 from HTC Explorer to Desire C and i want to know whether there is no harm in doing so, i would be using cm 10 build 3 as a base ROM, so i hope when i complete the base rom and when i flash it, it doesn't brick my phone !
I am still very junior over here in this section but i still want to port this ROM...Please everybody give me your suggestions so as to if there is any harm in doing so !
Thanks in advance
Click to expand...
Click to collapse
It's perfectly safe. Plus it's easy to port from HTC Explorer!
Just extract both
- Delete from golfu and Copy Apps, Media, Framework, and Fonts from pico to Golfu
- The go to etc>init.d, delete all except banner or something and don't copy the ones from pico yet
- Go to etc>permissions Copy the permissions from pico except platform and handheld_hardware
- Go to system>lib and copy over libmedia, libandroid and libandroid_runtime
Change the boot.img's over, zip and flash, if it flashes and boots, great! Go back an edit the build.prop using notepad++
If you get errors like set_perm failure, open the updater script in the meta inf folder, and copy the set_perm para from pico and paste in golfu
Reflash.
If it boots, add in the init.d scripts and reflash, may or may not boot.
it may or may not have root access.
Use NOPE boot.img

bionicsquirell said:
It's perfectly safe. Plus it's easy to port from HTC Explorer!
Just extract both
- Delete from golfu and Copy Apps, Media, Framework, and Fonts from pico to Golfu
- The go to etc>init.d, delete all except banner or something and don't copy the ones from pico yet
- Go to etc>permissions Copy the permissions from pico except platform and handheld_hardware
- Go to system>lib and copy over libmedia, libandroid and libandroid_runtime
Change the boot.img's over, zip and flash, if it flashes and boots, great! Go back an edit the build.prop using notepad++
If you get errors like set_perm failure, open the updater script in the meta inf folder, and copy the set_perm para from pico and paste in golfu
Reflash.
If it boots, add in the init.d scripts and reflash, may or may not boot.
it may or may not have root access.
Use NOPE boot.img
Click to expand...
Click to collapse
Yaa thanks buddy i know how to port was just thinking if there was no harm to flash it...
Thanks once again !

warrior1208 said:
Hey everybody,
I just learnt the method for porting ROMs...
So i am trying to port MINICM 10 from HTC Explorer to Desire C and i want to know whether there is no harm in doing so, i would be using cm 10 build 3 as a base ROM, so i hope when i complete the base rom and when i flash it, it doesn't brick my phone !
I am still very junior over here in this section but i still want to port this ROM...Please everybody give me your suggestions so as to if there is any harm in doing so !
Thanks in advance
Click to expand...
Click to collapse
theres always a risk of soft brick, which is bootlooping. Its an easy fix, just reboot into recovery and restore your backup or flash cm10 for you device
P.S: do a full wipe before flashing port roms as a dirty flash causes bootloops

I have successfully ported minicm 10...check my signature!
Thanks for your support !

Accidentally Parsed "ro.build.description" (In Dire Need Of Help)

Hello ladies and gents. As you may have been able to tell from the title, I made a huge mistake when playing around with my phone's build.prop file. I had tapped on the ro.build.description file and it pulled up the keyboard. I accidentally input an "r", so I deleted it, then saved and left the prop file, thinking everything was fine and proper. Unfortunately, that was not so. Upon my next reboot, I discovered several problems. The Playstore and gallery crash upon every open, and even worse, my internal memory isn't being recognized. I know the problems must be originating from the build description prop file, since that was the only prop file change that had happened since my last reboot. If anyone could give any tips on how to fix this or mount the external sd as internal, that would be wonderful. I need to be able to screnshot, install apps, and perform other functions that require internal storage. Please help me out ASAP.

Lincsbro said:
Hello ladies and gents. As you may have been able to tell from the title, I made a huge mistake when playing around with my phone's build.prop file. I had tapped on the ro.build.description file and it pulled up the keyboard. I accidentally input an "r", so I deleted it, then saved and left the prop file, thinking everything was fine and proper. Unfortunately, that was not so. Upon my next reboot, I discovered several problems. The Playstore and gallery crash upon every open, and even worse, my internal memory isn't being recognized. I know the problems must be originating from the build description prop file, since that was the only prop file change that had happened since my last reboot. If anyone could give any tips on how to fix this or mount the external sd as internal, that would be wonderful. I need to be able to screnshot, install apps, and perform other functions that require internal storage. Please help me out ASAP.
Click to expand...
Click to collapse
extract the build.prop file from your rom.zip
make a flashable zip & flash it. will work normal again
(ifm u dont know how to make flashable zip, just get any flashable mod,
extract all files, delete all files , only leave the meta-inf folder with its data inside untouched & a folder called "system",
put build.prop into system folder, now mark both folders --> right click --> send to zip, put on sd & flash)
good luck!

bejunk said:
extract the build.prop file from your rom.zip
make a flashable zip & flash it. will work normal again
(ifm u dont know how to make flashable zip, just get any flashable mod,
extract all files, delete all files , only leave the meta-inf folder with its data inside untouched & a folder called "system",
put build.prop into system folder, now mark both folders --> right click --> send to zip, put on sd & flash)
good luck!
Click to expand...
Click to collapse
Alright then. I have 2 questions though. Does the flash mod I use have to be specifically for my phone's model? And what do you mean by marking the folders?

Lincsbro said:
Alright then. I have 2 questions though. Does the flash mod I use have to be specifically for my phone's model? And what do you mean by marking the folders?
Click to expand...
Click to collapse
Hey bro, just tell me ur Rom & i will make a flashable zip for you )

bejunk said:
Hey bro, just tell me ur Rom & i will make a flashable zip for you )
Click to expand...
Click to collapse
I'm really sorry, but I don't know what you mean by my Rom. Generally, I'm pretty knowledgeable about my Android, but I've only been rooted for about a week. If by rom you mean like ClockworkMod or something, I'm just on my stock rom. If you mean something else, I don't know. And which slot in Odin would put this in? I only have experience with .tar and .md5.

Lincsbro said:
I'm really sorry, but I don't know what you mean by my Rom. Generally, I'm pretty knowledgeable about my Android, but I've only been rooted for about a week. If by rom you mean like ClockworkMod or something, I'm just on my stock rom. If you mean something else, I don't know. And which slot in Odin would put this in? I only have experience with .tar and .md5.
Click to expand...
Click to collapse
Check in 'Setting>About> copy everything in here and post it here, so people can help with your problem.

Naimlaaa said:
Check in 'Setting>About> copy everything in here and post it here, so people can help with your problem.
Click to expand...
Click to collapse
Thanks, I should have thought to do that sooner
bejunk said:
Hey bro, just tell me ur Rom & i will make a flashable zip for you )
Click to expand...
Click to collapse
Alright, here's my system info:
Model Number: SAMSUNG-SM-G730A
Android 4.4.2
Baseband: G730AUCUBNG3
Kernel Version: 3.4.0-1670137
[email protected] #1
Thu Jul 24 22:04:06 KST 2014
Build Number (My busybox installer said this was my rom, so it might be what you need): KOT49H.G730AUCUBNG3
Hope this helps you out

Lincsbro said:
I'm really sorry, but I don't know what you mean by my Rom. Generally, I'm pretty knowledgeable about my Android, but I've only been rooted for about a week. If by rom you mean like ClockworkMod or something, I'm just on my stock rom. If you mean something else, I don't know. And which slot in Odin would put this in? I only have experience with .tar and .md5.
Click to expand...
Click to collapse
sorry my llate reply, lets go
he bro u know whats the rom ) you say you are on stock rom, thats all i need.
clockwork mod is no rom, its a recovery.
sorry was a small hazzle for me as you use the AT&T version of the phone, now to the solution:
we need to just replace the damaged build prop with original one.
1. download the system image here: http://www.mrcrab.net/viewstockrom/19845-sm-g730a.html (or anywhere if u find, maybe at SAMMOBILE)
2. (try) to extract the parts of it, we need the system image. if u dont know how just google it, maybe some tools needed for diffrent kind of datas. once all extracted the build.prop is inside system (-folder). copy it to SD & replace via any ROOT explorer, set the right permissions, like in this pic LINK, reboot done.
if you CANT extract that image, make you ready for completly new install of your ROM.
Lincsbro said:
Thanks, I should have thought to do that sooner
Alright, here's my system info:
Model Number: SAMSUNG-SM-G730A
Android 4.4.2
Baseband: G730AUCUBNG3
Kernel Version: 3.4.0-1670137
[email protected] #1
Thu Jul 24 22:04:06 KST 2014
Build Number (My busybox installer said this was my rom, so it might be what you need): KOT49H.G730AUCUBNG3
Hope this helps you out
Click to expand...
Click to collapse
:good:

bejunk said:
sorry my llate reply, lets go
he bro u know whats the rom ) you say you are on stock rom, thats all i need.
clockwork mod is no rom, its a recovery.
sorry was a small hazzle for me as you use the AT&T version of the phone, now to the solution:
we need to just replace the damaged build prop with original one.
1. download the system image here: http://www.mrcrab.net/viewstockrom/19845-sm-g730a.html (or anywhere if u find, maybe at SAMMOBILE)
2. (try) to extract the parts of it, we need the system image. if u dont know how just google it, maybe some tools needed for diffrent kind of datas. once all extracted the build.prop is inside system (-folder). copy it to SD & replace via any ROOT explorer, set the right permissions, like in this pic LINK, reboot done.
if you CANT extract that image, make you ready for completly new install of your ROM.
:good:
Click to expand...
Click to collapse
I can do that, but I have a problem. I can't download the file from the link you provided. Could you find me a different place to download the image from, or maybe even give me a direct download link? Thanks.

Lincsbro said:
I can do that, but I have a problem. I can't download the file from the link you provided. Could you find me a different place to download the image from, or maybe even give me a direct download link? Thanks.
Click to expand...
Click to collapse
You can try Mr Google for that. just kidding, but seriously you can do that.
bejunk said:
sorry my llate reply, lets go ................ set the right permissions, like in this pic LINK, reboot done.:
Click to expand...
Click to collapse
Little help here, did Selinux news to set to permissive to make the permission become permanent? Because sometimes when I change a dir perm it didn't stick, it change back when quit i explorer.
Thanks in advance.

Lincsbro said:
I can do that, but I have a problem. I can't download the file from the link you provided. Could you find me a different place to download the image from, or maybe even give me a direct download link? Thanks.
Click to expand...
Click to collapse
@Naimlaaa is right , google for yor model SAMSUNG-SM-G730A firmware there are plenty sites about samsung, i have limited time at the moment..
Naimlaaa said:
You can try Mr Google for that. just kidding, but seriously you can do that.
:good:
Little help here, did Selinux news to set to permissive to make the permission become permanent? Because sometimes when I change a dir perm it didn't stick, it change back when quit i explorer.
Thanks in advance.
Click to expand...
Click to collapse
1st, whats your rom & phone model, because on my ROM theres no SELinux (enabled) & on my otherhandset it works all fine..
also what kind of perm. ?? system r/w or on files ??

bejunk said:
@Naimlaaa is right , google for yor model SAMSUNG-SM-G730A firmware there are plenty sites about samsung, i have limited time at the moment..
1st, whats your rom & phone model, because on my ROM theres no SELinux (enabled) & on my otherhandset it works all fine..
also what kind of perm. ?? system r/w or on files ??
Click to expand...
Click to collapse
i use slimkat 4.4.4 by android-andi on SGS3 Mini (i8190n).
1. using root explorer, changing perm on the first / (the root dir, i believe).
2. this one is new problem, nothing to do with our recent dialogs, hope can get some idea on this one.
yesterday, i install android tweaker app, and set the auto system/device tweak( can't remember exact) and reboot my device
to apply the setting. and got stuck on boot animation (blinking 'SAMSUNG' anim, after the 'GT I8190N' image on ori ROM). it
didn't loop (no bootloop), just stuck on blinking animation, boot image i guest?
Any idea just throw in please, really want to try and confirm on any solution we got in mind.
thanks in advance everyone.