Hello Everybody!
I'm sure this has been covered but I haven't found a tutorial or guide for the samsung captivate. I had ACL surgery today and I've decided i have the time to invest in creating a rom based on the things I like from other roms. Where do I start this process? Can i just mix files from within the .zips from other roms? or is there a file that tells the rom which files to install/access?
I've really enjoyed a lot of the ROM's that I have been flashing on my phone but I keep running into the same problem on all of them except one. Text messages occasionally go to the wrong person...and this is scary and unacceptable for me.
Some links to other threads or websites would be greatly appreciated.
Thank you for your time.
sdp07d said:
Hello Everybody!
I'm sure this has been covered but I haven't found a tutorial or guide for the samsung captivate. I had ACL surgery today and I've decided i have the time to invest in creating a rom based on the things I like from other roms. Where do I start this process? Can i just mix files from within the .zips from other roms? or is there a file that tells the rom which files to install/access?
I've really enjoyed a lot of the ROM's that I have been flashing on my phone but I keep running into the same problem on all of them except one. Text messages occasionally go to the wrong person...and this is scary and unacceptable for me.
Some links to other threads or websites would be greatly appreciated.
Thank you for your time.
Click to expand...
Click to collapse
Well, rom cooking is pretty easy.
As long as you know that component x is compatible with rom y, all you need to do is open the ROM in winrar/7z and drop the new file in, replacing the old one. No reason to unpack / repack. The only thing that can be a problem is the update-script, which resides in META-INF/com/google/android. It's a script that tells the phone "this is what you're doing with all of the stuff in this zip", if you modify a ROM like Axura or Perception, the update-script shouldn't need to be changed.
If you DO want to unpack and repack it, that's fine. Make sure you don't compress them into a sub directory (Update.zip > update > updates/system/meta-inf). Compress the updates/system/meta-inf/data whatever into it's own folder named whatever.zip, then sign the .zip via SignApk;
Code:
java -jar Signapk.jar certification.pem key.pk8 update.zip updatesigned.zip
Then flash it with CWM. Be aware however that in order for kernels(zImage) and modems(Modem.bin) and SBL(secondary boot loader) to be installed via CWM, the redband_ua exploit must be present in the updates folder; and the necessary commands for red_band must be present in the update-script.
I wanted to layout what I did to achieve a backup and was hoping that one of the understanding ones could give me feedback about the method and any guidance on a better way.
1. Device is untouched
2. Superonclick for Root Access
3. Copied and manually installed ROM Manager.APK
4. Copied and manually install Verizon Bootstrapper.APK
This installed ClockWork Mod 3 and a full backup of the system was made with the following files:
Boot.img
Cache.img
data.img
datadata.img
nandroid.md5
recovery.img
system.img
So … given that I have these files from a virgin tab with no data entered …. No google account etc.. this should be a base image set correct?
Now what is the best way to extract from the IMG files what everyone needs from the various posts?
P.S. I did try rotobackup, I tried the exe file and the scripts that people made …. Apparently that is one above my pay grade as I could not get them to work.
Tell me I am an idiot … tell me it is a waste of time ….. or teach me to fish ….. open to any feedback.
Thanks,
Tony ~ mnpolock
I don't believe your image is really a base image, since you have installed Clockworkmod. So even if you flash back to that image, and then do a factory reset (which would wipe out root) you'll still have CWM on there.
Good point ..... I was looking at it from the standpoint (but didn't say) that I would have everything stock and blank but the kernel ( I think that is correct CWM is a kernel mod).
Tony
best way to back up anything you wan is to use Titanium Backup app you can back anything you want by just picking it from apps or system files and then but the back up you made on your pc or safe place ..
Hi all,
My question is aimed to head deep into the Android OS and the flashing process itself. I know that if I flash my phone with a new ROM that system files are replaced and also some other files too. My question is how is this done? Is there an exact order in which the files have to be replaced, and are they "just" overwritten or are they deleted first and then the new ones put in place?
Forgive me if this question has already been answered. I really tried my best to find answers on Google and in here.
Thanks in advance for any enlightening comment.
Open up an update-script and your dilemma will be solved
Sent from my GT-I9000 using Tapatalk
Essentially, like the previous reply mentioned the android OS is heavily partitioned, but has a lot of sneaky mount points to hide this fact.
Really all a CWM flashable zip does is follow a script, easily readable in the zip, to copy files throughout the OS partition.
If you look in the zip you'll see a few things, the biggest thing here is the /System folder. It contains the entirety of the system partition that makes your ROM /Your ROM/. Also you'll see boot.img which is the kernel (and CWM). A modem.bin file is also present, but to my understanding is only flashed if one is not currently present.
When looking at CM9's zip, you'll see an updater.sh. This is the shell script that's run on using CWMs install function.
It's process checks a few environment things and installs (copys over /system) based on this.
Check out the script, it's really interesting.
Thanks to all of you
I will have a look inside a script then.
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.
Hello community,
I'm currently trying to modify the stock rom for my GT-I8200n. I didn't find cwm for the S III mini VE, and the version of twrp I found was very buggy. So I need an odin-compatible flash file for my rom. I tried to modify the stock rom by downloading the .tar.md5 from sammobile, unpacked it with winrar and copied the system.img into an ubuntu-VM. After that I created a sys.img (or sys.raw, same problem) out of system.img using the simg2img-file I found somewhere here on xda, mounted sys.img (or sys.raw) and modified it. Then I unmounted it and used img2simg to create my system_new.img. Copied it to my windows system, into the unpacked stock rom folder, renamed it to system.img, overwriting the old system.img and packed everything into a .tar file using ZArc. Now while flashing my ROM, odin works on the system.img for some minutes and then shows a fail.
Does anyone know what I'm doing wrong?
P.S.: I tried simply using simg2img on my stock system.img and then - without mounting and modifying - used img2simg kn the sys.img file. Same problem with odin and I noticed that my new system.img is approximately 50 mb smaller than the stock img, although I didn't modify it.
I hope I described my problem well (I'm not an english native speaker, but did my best to make this text understandable )
Any ideas or hints that could maybe solve this problem are welcome.
Thank you,
Chris
I have the same problem
any solution ?