This question is probably already asked, but I can't find a clear answer for it.
2nd thing is that I can`t see the forest for the trees anymore cause I'm quite an android noob.
I wan't to try to build a custom rom, but how do I get started?
As far as I know there are 2 ways:
1) Take an existing rom (either stock or custom) and mod it.
2) Start from scratch.
The 2nd method is of course the most interesting (but probably also the hardest) method.
So say we take that method.
First of all I think android basically consists of 2 parts, being the kernel + all the rest.
You can take a kernel from a working rom, which may be moddified, but can you also build the original kernel from the source? For getting that to work on my device I'll probably need the drivers, but how? Extract it from the latest official rom? And how to add them?
Samsung (yes I have a samsung s5660 aka gio) also uses the rfs filesystem, would it be possible to use ext4 and does the kernel need to be adapted to that?
And how do you make the rom flashable for odin?
A lot of questions, I know, but isn't there a step to step guid for doing this kind of things?
Thanks
yes, its possible to create an odin flashable rom with ext4 as default filesystem. and yes, obviously the kernel need to support ext4.
read this thread, particularly the first post.
http://forum.xda-developers.com/showthread.php?t=1202049
Dear Android Hackers!
Please consider helping if you have some spare time and good will.
The device is Samsung Galaxy Player 4.2 (mine is North America version from the US)
Product code: YP-GI1
Android: Gingerbread 2.3.6
Kernel: 2.6.35.7
There is no special section in XDA for this device, so we (the owners of such devices and others who are trying to help) were discussing the matters of rooting here: http://forum.xda-developers.com/showthread.php?t=1715461&page=999
We have tried all the publicly available exploit-based rooting methods, none works, the device release date is April 2012, and there is no Android Gingerbread Local Privilege Escalation exploit released after that date if I am not wrong, and all the old ones are patched as it comes out...
Disclaimer: I'm not a developer, and everything I know I've learned in the last month, so please not laugh if I'm telling something stupid
So, as I understand the options are:
1.
Solution: Find a new exploit, get root, install SuperSU, profit
Problem: There is no publicly available exploit that I'm aware of
2.
Solution: Create an update.zip package with SuperSU and BusyBox, install it in the Recovery Mode
Problem: We need a genuine Samsung signing key to bypass the signature checking
3.
Solution: Get the stock rom, inject SuperSU and BusyBox, flash using Heimdall or Odin
Problem: There is no stock rom available, where do you people get them ha?
4.
Solution: Port CWM to our device, install it, then install and update.zip with SuperSU and BusyBox
Problem: I don't know how to create a CWM rom for my device
So, can anybody help with anything please? THANK YOU!
Up.. Anybody?
There hasn't been a leak of the firmware?
If there's no exploit for you to use, it's going to be hard.
And there probably aren't many people working on GB root exploits.
If you can get the kernel or system partition firmware file it would be easy to do.
Wish I had more help for you.
Did it ship with this version, or did it take an update?
If it took an update you might have hope. PM me if it did, I prolly won't see this thread again.
D
.
dsb9938 said:
There hasn't been a leak of the firmware?
If there's no exploit for you to use, it's going to be hard.
And there probably aren't many people working on GB root exploits.
If you can get the kernel or system partition firmware file it would be easy to do.
Wish I had more help for you.
Did it ship with this version, or did it take an update?
If it took an update you might have hope. PM me if it did, I prolly won't see this thread again.
D
.
Click to expand...
Click to collapse
Thanks for your interest.
No, there were no updates, it is the stock firmware.
The source code of the kernel is available at Samsung's site. And I have dumped the contents of the /system partition (except for several config files, see below):
Code:
$ /data/local/tar -czf /sdcard/external_sd/system.tar.gz /system
tar: removing leading '/' from member names
tar: can't open '/system/etc/bluetooth/audio.conf': Permission denied
tar: can't open '/system/etc/bluetooth/auto_pairing.conf': Permission denied
tar: can't open '/system/etc/bluetooth/input.conf': Permission denied
tar: can't open '/system/etc/bluetooth/main.conf': Permission denied
tar: can't open '/system/etc/dbus.conf': Permission denied
tar: error exit delayed from previous errors
So here is the /system:
http://depositfiles.com/files/e0odb9gvt
password: XDA-DEV
P.S.
Also PM'ed you this post
dsb9938 said:
There hasn't been a leak of the firmware?
If there's no exploit for you to use, it's going to be hard.
And there probably aren't many people working on GB root exploits.
If you can get the kernel or system partition firmware file it would be easy to do.
Wish I had more help for you.
Did it ship with this version, or did it take an update?
If it took an update you might have hope. PM me if it did, I prolly won't see this thread again.
D
.
Click to expand...
Click to collapse
any way you could help?
You will need two devices. There are a few different approaches, but all will require two devices to get everything.
First option:
Dump all /system partition contents. This can be tough without busybox, and without root it will likely be incomplete. (Edit: Looks like you have this.)
Assuming the 4.2 uses ext4 - use http://forum.xda-developers.com/showthread.php?t=1081239 to rebuild an Odin-flashable image from the dump. Without root access, the dump will likely be incomplete but at least hopefully bootable. (Based on the posts above, my guess is that Bluetooth will be busted.)
Once booted, use dd to dump the stock kernel image
Use initramfs repacking tools (these vary by device...) to change default.prop of the stock kernel so that it is debuggable and insecure (ADB sessions have root)
Flash this image into another device to get a full and complete /system dump (including the ones you couldn't dump above).
Second option:
Copy individual files from the initramfs of a running system including scripts
Get kernel source
Build a kernel using the manually dumped initramfs (basically, everything in / that isn't a mount point)
Flash this kernel to get a clean /system dump
Root-inject the /system dump (see above) and flash that on another device to get the stock kernel
It sucks that US devices never seem to have stock firmware images available on release like international devices do.
I can't help you beyond this, everything else is device-specific.
I'm not too experienced with this, but if you you can compile the system.img you might be able to root it. Pm me if you need more specifics, I remember a friend doing this with his motorola charm.
Edit: Heres a nand upload, you should be able to get it from here. Just extract it with yaffs2
http://forum.xda-developers.com/showthread.php?p=30320175&postcount=53
flapflip22 said:
I'm not too experienced with this, but if you you can compile the system.img you might be able to root it. Pm me if you need more specifics, I remember a friend doing this with his motorola charm.
Edit: Heres a nand upload, you should be able to get it from here. Just extract it with yaffs2
http://forum.xda-developers.com/showthread.php?p=30320175&postcount=53
Click to expand...
Click to collapse
No recent device uses raw NAND, and thus yaffs2 doesn't apply.
The problem is getting clean kernel and system dumps without root access - the best you'll do usually is a partial system dump that is hopefully bootable, can be root-injected, and then flashed to a device to get clean kernel dumps. With the kernel dump, you can build an insecure kernel, flash it to a second device, and get the factory image.
In the case of Player 4.2 - there is a POSSIBILITY an insecure international device kernel will boot well enough to get a clean system dump. I know Player 5.0 initramfs was identical, and the only difference between international and USA kernels was the touchkey map. So an international kernel would boot on USA devices but would have broken touchkeys.
Have you checked for rom on sammobile.com. If anyone can provide original firmware are those guys. You can also request it on their forum.
Sent from my HTC One S using xda app-developers app
Entropy512 said:
No recent device uses raw NAND, and thus yaffs2 doesn't apply.
The problem is getting clean kernel and system dumps without root access - the best you'll do usually is a partial system dump that is hopefully bootable, can be root-injected, and then flashed to a device to get clean kernel dumps. With the kernel dump, you can build an insecure kernel, flash it to a second device, and get the factory image.
In the case of Player 4.2 - there is a POSSIBILITY an insecure international device kernel will boot well enough to get a clean system dump. I know Player 5.0 initramfs was identical, and the only difference between international and USA kernels was the touchkey map. So an international kernel would boot on USA devices but would have broken touchkeys.
Click to expand...
Click to collapse
can u explain this a bit more? what are touch keys exactly? sorry ima noob but we are still cant find anything. if you could post your ideas on the thread http://forum.xda-developers.com/showthread.php?t=1715461 that would be helpful thanks!
Entropy512 said:
You will need two devices. There are a few different approaches, but all will require two devices to get everything.
First option:
Dump all /system partition contents. This can be tough without busybox, and without root it will likely be incomplete. (Edit: Looks like you have this.)
Assuming the 4.2 uses ext4 - use http://forum.xda-developers.com/showthread.php?t=1081239 to rebuild an Odin-flashable image from the dump. Without root access, the dump will likely be incomplete but at least hopefully bootable. (Based on the posts above, my guess is that Bluetooth will be busted.)
Once booted, use dd to dump the stock kernel image
Use initramfs repacking tools (these vary by device...) to change default.prop of the stock kernel so that it is debuggable and insecure (ADB sessions have root)
Flash this image into another device to get a full and complete /system dump (including the ones you couldn't dump above).
Second option:
Copy individual files from the initramfs of a running system including scripts
Get kernel source
Build a kernel using the manually dumped initramfs (basically, everything in / that isn't a mount point)
Flash this kernel to get a clean /system dump
Root-inject the /system dump (see above) and flash that on another device to get the stock kernel
It sucks that US devices never seem to have stock firmware images available on release like international devices do.
I can't help you beyond this, everything else is device-specific.
Click to expand...
Click to collapse
I tought of the 2nd option but I miss actually the init.rc, init.hugo.rc and init and recovery files. Someone that tried to help me said that he can't do it. Maybe alice you can make a dump of this for me so I can build an insecure kernel. (hopefully)
good nice.....
Sorry, I was offline the last 3 days.
Entropy512, thank you very much for detailed description of the available options.
Assuming the 4.2 uses ext4 - use http://forum.xda-developers.com/show....php?t=1081239 to rebuild an Odin-flashable image from the dump. Without root access, the dump will likely be incomplete but at least hopefully bootable. (Based on the posts above, my guess is that Bluetooth will be busted.)
Once booted, use dd to dump the stock kernel image
Click to expand...
Click to collapse
I don't understand this part. Wouldn't I just rewrite the stock image when flashing the dumped one? And what is the point of flashing the dumped image without modifications? (or you just didn't write about the needed modifications, e.g. injecting the su binary there?). And should I deodex the /system/app/ and /system/framework directories before creating the new image or no modifications are needed? And if it's preferable to deodex, how do I do that in Linux? Thank you!!
Added:
Meanwhile, I've created a system.img with injected su and superuser.apk, not deodexed, here - http://forum.xda-developers.com/showpost.php?p=31345895&postcount=418
1. Search google and xda...
2. Sign zip with signapk or some other signing tool...
3. Try sams firmware or extract your rom... search for how to in guide in my signature(create custom rom)
4. Search if someone have already ported it on your device or use build.clockworkmod.com
Sent from my GT-S7500 using xda premium
The following is a reasonable format that is suggested when posting a ROM. We expect your ROM post to look somewhat professional and easy to understand.
1. Requirements (bootloader version, radio version etc)
2. State that it's from an official manufacturer or source base (stock ROM or AOSP-like source).
3. Thread shows a clear overview of changes made, in a way that users can see what has changed when new versions are updated.
4. Explicit installation instructions.
5. ROMs need to identify what kernel they are using. If 100% stock then they must state that.
6. If custom kernel you must provide a link to the kernel source. This is required by GPL. Stock (untouched) kernels can link to the manufacturers source (if available). If you use somebody's kernel, link to their source.
7. At least 2-4 images (screen-shots) 1 of which must be of system/device info. Do not use photo hosts thay deluge users with ads and popups when they select the image. You can either attach the images, or use a hosting service such as photo-bucket for example.
8. Links to downloads. A link to a direct download is preferred. Linking to external website home pages are not allowed, it must be linked to the Downloads page. Also use of "ad-driven" (adfly for example) or "commercial" sites are mostly not allowed. Registration on some sites "may" be allowed, but is subject to XDA Moderation approval.
9. Credits for sources used. Very important.
10. Keep your "asking for donations to a limit. You already have a "Donate" button.
Simply posting a link to some download site "here it is, download it", is not allowed.
Any questions, please feel free to contact any moderator.
Thank You
Moderation Team
Q&A for [ROM]CM11S 44S F2FS with AK077 - XNPH44S
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM]CM11S 44S F2FS with AK077 - XNPH44S. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Hello.
I just installed this ROM, works fine( even if I haven't noticed 'visible' gains in terms of app load time ) but I can't revert back to ext4. I'll stay in F2FS so it's okay but if I reformat all to ext4 and flash for example the Calkuin 44S 'normal ext4' ROM, I have an error in my Philz recovery.
Also, I lost 4K points Antutu with same AK 0.77 kernel settings ( 48K in ext4, 43K in F2FS )
ManuBBXX said:
Hello.
I just installed this ROM, works fine( even if I haven't noticed 'visible' gains in terms of app load time ) but I can't revert back to ext4. I'll stay in F2FS so it's okay but if I reformat all to ext4 and flash for example the Calkuin 44S 'normal ext4' ROM, I have an error in my Philz recovery.
Also, I lost 4K points Antutu with same AK 0.77 kernel settings ( 48K in ext4, 43K in F2FS )
Click to expand...
Click to collapse
Hi,
I have not had this problem.I take it you are using the format system, then cache, then data and data/media to ext4 using philz. You can also use the wipe to install a new rom to see if that helps.I use the latest philz touch.
So long story short Deliveroo Sunmi V2 device i want to make a android 7 system image for its chipset (mt6739) and archtitiure (armeabi-v7) and i complied it from source, added in the /vendor files from the stock image files that ive pulled from the device with SP Flash Tool (even longer story) and since its a device with stock Firmware files that not stock android instead a very heavily modded version of android 7.1 to restrict usesage and for the company to control the devices remotely. Ive read init.rc files in both stock boot.img and system.img as well as all the instructions from the kernal to start Android (because thats been modified for their additions to the os) and ive tried to change the code in the many of init files to link the two paritions together so android can boot, but after a week of mounting, resading, comparing, editing, unmounting and reflashing non-stop im at a loss, and i really need some help ans this isnt your normal smartphone with ner genetic files and such
Thread closed!
[Read Before Posting]QUESTIONS DO NOT BELONG IN GENERAL
Hello Everybody, In order to attempt to keep this forum neat and tidy the moderation team is asking you to post your questions into the Questions and Answers (Q&A) forum and not into the General section. You can find the Q&A forum by clicking...
forum.xda-developers.com