Related
I have downloaded one of the roms in this thread:
http://208.100.42.21/showthread.php?t=781149
I decided to edit the JI2 version and removed the games that came with it and repacked it in the correct formats in store compression (uncompressed)
When odin wants to flash the new .tar file it seems to take forever on amss download.
Any ideas?
With the original rom I get a big partition size!! warning or something, then amss download starts, and I have my phone flashed well.
So how do I edit the rom to change the language? I know it is in CSC.
Can I replace the bootloader in the JI2 ROM? How do I do that?
I want to install custom kernels
What is the risk of flashing it with a i5800 ROM which has nicer UI ?
With Epsylon3 brilliant work, a new idea of flashing custom firmwares came to surface, allowing custom /system partition to be flashed directly from RSD Lite! This way you don't need to flash fixed SBFs and waste time with rooting and recovery install in case of system screw-up.
What you need:
1) MotoAndroidDepacker. With it, unpack sbf of the firmware you use as base.
2) Leave CG35(boot) and CG61(devtree) partition files, delete other smgs. Other files are not that important. You can delete all partition files if you're making backup for yourself...
3) Replace CG39(system) with your system dump:
adb shell:
su
dd if=/dev/block/system of=/sdcard/CG39.smg
copy CG39.smg from sd card to your firmware folder.
4) Compile sbf with MotoAndroidDepacker.
5) Flash your sbf in case of failure.
MAJOR CAVEAT: This sbf will work ONLY on devices with have same full SBF version applied last as your device. I.e. if you have flashed 3.4.2-107 and then upgraded it with nandroid to 3.4.2-177, the sbf you created from your system dump will work only for devices which flashed still 3.4.2-107 sbf last. To install such (custom) sbf, one would need to flash full 3.4.2-107 sbf first.
Technical: this is possible because of bug/feature in flashing process: system signature partiton is not checked if phone signature is already present. Phone signature is generated when flashing full genuine sbf and is verified aganist copy in sp partition and obviously differs for each firmware. It is stored at the end of the system partition.
Great news.
Some question:
If I install a full sbf. IE: 3.4.2-117 and then apply a custom ROM over it (CM).
So can I make a backup of my system and flash it again in case of any brick?
You can make a backup for yourself and flash it again all you want until you flash another full motorola sbf. Don't forget to make data backups as well, this method can't replace nandroid / titanium!
Interesting...
So I can flash my base sbf, integrate call recording, 720p playback, wvga recording, root, swype on my language and other mods and create a new sbf only to apply these mods.
It will be usefull....
Oh great all of us asked this question when this section began in xda. So essentially we can make an sbf out of our phones and keep it and not worry about any nandroid backups.
This is a great discovery, thanks a ton.
Cheers
So would it be possible creating custom bootmenus as these are updated by sbf's too?
If your current system contain boot menu. The custom sbf also, it is identical with the current system.
i think you can create a Full SBF with all original partitions and your "signed" CG39
I think it is not a bug... the thing is : i'm not sure sbf can work on other devices ... but anyway... it can be really usefull to recover device or to create a full backup with the good kernel made for the /system and /devtree
mbr and ebr are needed too, if the partition table has changes, you will have problems..
So the question is whether the signature is related to the specific part of every device, or it is universal as official sbf. Need to be verified .
Does this means that someone could create a sbf wich flashs dierctly CM7 or MiUi?
IE-coRe said:
Does this means that someone could create a sbf wich flashs dierctly CM7 or MiUi?
Click to expand...
Click to collapse
It's possible too.
Where i can finde the MotoAndroidDepacker?
Great news! But why are Android systems so complicated when it comes to flashing and banking up? I mean, with computers it's easy. You make an image of the system partition and you're done. Restoring is as simple as writing the backup back to the partition. So, why is it so hard to just make an entire nand backup that we can simply write back to go to a working state after failure?
Sent from my MB525 using Tapatalk
I made a custom sbf with nightly build in it . Then wipe and flash it, stuck at M logo. Bootmenu works, but it seems that it can't mount some partition , it's the same symptom when wipe in stock recovery in cm7.
Does it really need to flash a full sbf before the custom sbf ?
So if i wanted to do this i split my sbf, delete everything only leaving,
CG35.SMG
CG61.SMG
firmware.hmg
Then system dump and add that CG39.smg in and build and flash?
Have i missed anything?
Well you forgot RAMDLD... One CG39 is enough if you'll flash this SBF over ver 4 froyo (not Chinese or Korean) but i recommended CG35 and CG61 to make such sbf enough to flash over system downgraded with fixed sbf + nandroid.
Is it possible to keep all files and just replace CG39? Or are files removed for a reason? Thanks for replying.
You can keep all files, theoretically.
Well i made an sbf version of miui and it works
Wonder if it works on other peoples Defy?
Tested by formatting system and then applying sbf. Booted back into MIUI like a dream
EDIT:
Shame the SBF comes out at 300+mb May take a while to upload these things lol.
If I mount the CG39 as a loopback device in a linux box,
Can I just replace the contents and it will retain the signature?
Or the signature is based in a checksum?
New to Android, about 3 weeks now with my Rogers 1727R. I've been trying to grab all the good files and build my understanding of returning my phone to it's stock ROM if I have to return it or if I brick it etc. But I seem to have downloaded, from this forum, so many files, with different names and files sizes, I'm confused about what does what. So I'm asking any senior people here if they can tell me what I have, what it does, and whether I need it. Here goes:
Stock_ROM_SGH-I727R-UCKJ2-k0nane.7z - Think this is a stock ROM but un-bloated. It's 257 MB.
i727_stock_kernel_odin.tar - It's 10 MB, appears to be a stock AT&T ROM, but perhaps just the kernel, not the whole ROM?
Stock Recovery.tar - It's 6.08 MB. Downloaded it today.
Nandroid backup - 841 Megs with data.ext4.tar, system.ext4.tar, boot.img and recovery.img which I thought was a complete image of my ROM.
Look at the size differences. From 6 MB up to 841 MB. What the heck are all these files?
harry_fine said:
New to Android, about 3 weeks now with my Rogers 1727R. I've been trying to grab all the good files and build my understanding of returning my phone to it's stock ROM if I have to return it or if I brick it etc. But I seem to have downloaded, from this forum, so many files, with different names and files sizes, I'm confused about what does what. So I'm asking any senior people here if they can tell me what I have, what it does, and whether I need it. Here goes:
Stock_ROM_SGH-I727R-UCKJ2-k0nane.7z - Think this is a stock ROM but un-bloated. It's 257 MB.
i727_stock_kernel_odin.tar - It's 10 MB, appears to be a stock AT&T ROM, but perhaps just the kernel, not the whole ROM?
Stock Recovery.tar - It's 6.08 MB. Downloaded it today.
Nandroid backup - 841 Megs with data.ext4.tar, system.ext4.tar, boot.img and recovery.img which I thought was a complete image of my ROM.
Look at the size differences. From 6 MB up to 841 MB. What the heck are all these files?
Click to expand...
Click to collapse
the .7z file is a 7zip archive of the stock UCKJ2 rom...you would need to use 7zip to extract the contents before flashing with ODIN
the .tar file you listed is indeed just the kernel, not the entire rom, and it is from the AT&T version
stock recovery.tar is exactly that. its the stock recovery to replace clockwork mod should you need to return to that.
your nandroid backup is the entire system, a direct image of everything you had on your phone when you created it. this includes all settings, installed apps, etc
the .7z file is a 7zip archive of the stock UCKJ2 rom...you would need to use 7zip to extract the contents before flashing with ODIN
your nandroid backup is the entire system, a direct image of everything you had on your phone when you created it. this includes all settings, installed apps, etc
Click to expand...
Click to collapse
So let's say I wanted to get back to my ROM the way it was the day I bought it. The Nandroid backup was done after rooting the day I bought it. So if I uncompressed the .7z file, is that what I would flash to get me back to square one, or the Nandroid backup?
harry_fine said:
So let's say I wanted to get back to my ROM the way it was the day I bought it. The Nandroid backup was done after rooting the day I bought it. So if I uncompressed the .7z file, is that what I would flash to get me back to square one, or the Nandroid backup?
Click to expand...
Click to collapse
the nandroid will get you back to the way YOU set it up. it wouldnt do squat for getting it back to stock.
the 7z file should take you back to stock.
its not complicated, you are just overthinking it.
a nandroid backup is YOUR backup, nobody elses. its an image of YOUR phone as YOU set it up. if you made the nandroid after rooting, and you restore from the nandroid, you will still have root, because its a direct image of your rooted phone. it will include all your settings, installed apps, and configurations.
That is very helpful. Last question.
What is a Stock Recovery file? You referred to it, and I see it's a rather small file, so it's not a ROM or Kernel. The name makes it sound like it's my stock ROM.
I know it has to do with CWM.
Any edification would be helpful.
Please keep questions in the Q&A section.....Thank you.
No recovery is not the rom. Recovery is like if u owned a computer around 1995 you had ms dos and windows well dos would allow you to make changes to windows that would not affect dos. Pretty much same thing. Recovery is where you flash the roms from but the roms do not change recovery. Cwm is clock work mod recovery . If you used odin to flash stock firmware tar tht woukd change your recovery from cwm to the stock recovery but i do now see we have a recovery tar where u can just flash the recovery tar but not the entire stock firmware tar.... to be honest id suggest doing alot of reading before you start messing with these things
---------- Post added at 07:32 PM ---------- Previous post was at 07:27 PM ----------
Get on youtube and look up videos by qbking you can learn alot from them there for the epic not our device but u can more understand the basics if u watch them
hello guys,
First thing is I'm a noob here, totally noob, altough I have used galaxy fit for almost one year now and have tried many, many custom roms here, I think it is already the time that I'm making my own.
So I read many tutorial how to make a custom rom, with dsixda kitchen. I read there on the original thread that dsixda kitchen didn't support our device, but I was persistent, downloaded all the requisites, and skip skip, finally I understand now why, because the file system of DXKT7 is rfs (system.rfs), it must be converted into ext4, or at least has system.img (am I wrong?), so I search every tutorial about converting file system into ext4, and almost all suggest it should be done on the device itself, or should I say, flashing this stock rom via ODIN, root it, and then u can convert it into ext4.
isn't there any way to make it done in PC so I can start edit this rom in kitchen?
I read it somewhere about extracting initframs.cpio from zimage, please, if anyone know this way, please teach me how
any explanation are appreciated, thank u in advance guys, n sorry for my english
edit:
pratyush.creed said:
not very hard ,just extract initramfs.cpio from the zImage ,add this line
CONFIG_EXT4_FS=y in filesystems,then change Mount points in init.rc of Ramdisk
and then Format All Dev Blocks e.g. System,Data,Cache to ext4 !!
Click to expand...
Click to collapse
Prodai said:
hello guys,
First thing is I'm a noob here, totally noob, altough I have used galaxy fit for almost one year now and have tried many, many custom roms here, I think it is already the time that I'm making my own.
So I read many tutorial how to make a custom rom, with dsixda kitchen. I read there on the original thread that dsixda kitchen didn't support our device, but I was persistent, downloaded all the requisites, and skip skip, finally I understand now why, because the file system of DXKT7 is rfs (system.rfs), it must be converted into ext4, or at least has system.img (am I wrong?), so I search every tutorial about converting file system into ext4, and almost all suggest it should be done on the device itself, or should I say, flashing this stock rom via ODIN, root it, and then u can convert it into ext4.
isn't there any way to make it done in PC so I can start edit this rom in kitchen?
I read it somewhere about extracting initframs.cpio from zimage, please, if anyone know this way, please teach me how
any explanation are appreciated, thank u in advance guys, n sorry for my english
edit:
Click to expand...
Click to collapse
copy system.rfs and csc.rfs from a stock rom and boot.img from custom rom to ur original_update folder and extract it...follow onscreen instructions in the kitchen and use magiciso to extract system folder and then do the mods and all u want and pack it now it will work meta-inf folder will be autogenertaed but replace the update-binary in ur created rom from anyother custom rom and it will surely work
yeshwanthvshenoy said:
copy system.rfs and csc.rfs from a stock rom and boot.img from custom rom to ur original_update folder and extract it...follow onscreen instructions in the kitchen and use magiciso to extract system folder and then do the mods and all u want and pack it now it will work meta-inf folder will be autogenertaed but replace the update-binary in ur created rom from anyother custom rom and it will surely work
Click to expand...
Click to collapse
I have unpacked boot.img using advanced options in kitchen's menu, now I have folder ramdisk and zImage, what to do now to convert it to ext4?
oh, I followed ur instruction, extract system.rfs with magicIso and put them together with boot image (the one from stock) and others in original update folder and now I can deodex it.
my question, should I change the boot.img with custom rom's boot image so it can support ext4 file system or just go with the stock?
or how can I change the kernel?
edit : oh, after hours searching I just found this thread, everything I need is here--> http://forum.xda-developers.com/showthread.php?t=1414534
anyway thank u guys.
Prodai said:
oh, I followed ur instruction, extract system.rfs with magicIso and put them together with boot image (the one from stock) and others in original update folder and now I can deodex it.
my question, should I change the boot.img with custom rom's boot image so it can support ext4 file system or just go with the stock?
or how can I change the kernel?
edit : oh, after hours searching I just found this thread, everything I need is here--> http://forum.xda-developers.com/showthread.php?t=1414534
anyway thank u guys.
Click to expand...
Click to collapse
ur boot.img from stock is rfs format so it wont work if u use that...use boot.img from any custom rom that is also based on ur baseband version(DXKT7)man..the boot.img will automaticaly have the ext4 filesystem(in custom boot.img not stock)....kernel is later part of ur rom man better not go into that now .....copy boot.img from custom rom of ur baseband version then system.rfs and csc.rfs file from stock rom and do as i said above and dont forget to replace update-binary in ur rom after creating the output_zip file from any other custom rom or ur rom wont install
Hi guys, i have a question...
Is possible create a custom rom (remove vendor apps) from XXXXXXXX.tar.md5 file downloaded from sammobile and make your own tar.md5 flasheable Odin file?
For example:
Original firmware:
XXXXXX.tar.md5
1.5 Gb
Removing vendor apps:
XXXXXX_my_firm.tar.md5
800 mb
I am interested in doing this without custom recovery, not zip flashable file, and not root.
xTxMIGUELxTx said:
Hi guys, i have a question...
Is possible create a custom rom (remove vendor apps) from XXXXXXXX.tar.md5 file downloaded from sammobile and make your own tar.md5 flasheable Odin file?
For example:
Original firmware:
XXXXXX.tar.md5
1.5 Gb
Removing vendor apps:
XXXXXX_my_firm.tar.md5
800 mb
I am interested in doing this without custom recovery, not zip flashable file, and not root.
Click to expand...
Click to collapse
Yes, you can do this, but things have changed a bit since this guide was written, you'll have to do some research to see what things have changed in this process from kit kat up to the current available android version. There have been some stock security changes that this guide doesn't cover and won't work with these new securities, but you should be able to figure out how to make this work with those securities if you learn to look in the right places.
https://www.rwilco12.com/forum/showthread.php?tid=92
This will help you create the .tar, you'll just have to figure out how to make the changes you want to make. You'll mostly be working with your system.img once you get it extracted.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE