Hi Everyone,
I'm working on integrating strongswan into Android (for IKEv2 Support); I managed to get the Samsung kernel sources from the Samsung OpenSources website, retrieve the initramfs from the original kernel (that I extracted from /dev/block/bml7), recompile it with some modifications (required by strongswan), and flash it back to the device using heimdall. My new custom kernel works like a charm.
I then tried getting the Samsung android sources and adding them to the Android sources, and modified them to integrate Strongswan into it. After compiling all, I find myself with a system.img, a ramdisk.img and a userdata.img... But I don't know how to flash the Android OS back to the GT-P1000 device.
Would you have any ideas how to flash my new firmware into the p1000? Is userdata the dbdata, and system the factoryfs? I might get a bit confused...
Any help would be appreciated.
Kind regards,
Related
Hi all,
I've been putting different ROMS on my i9000 for a while now.
I got a new phone and my wife wants to use my i9000 to read her work mail. It needs an app that somehow does not want to install on stock 2.3.6. giving the "There was a problem parsing the package" error. Reading on the internet I understand that this error might come from not allowing installing from unknown sources or that the android version is too old for the app. I have allowed installing from unknown sources so I'm guessing the 2.3.6 android version is too old for the app.
So here's my question, I think I know the answer but not 100% sure. Is it possible to install a newer custom android rom on the i9000 without rooting? Or installing the ROM and somehow unrooting?? I'd prefer SlimBean or SlimKat, as clean as possible...
Hope to hear some positive news from you guys.
remichi said:
Hi all,
I've been putting different ROMS on my i9000 for a while now.
I got a new phone and my wife wants to use my i9000 to read her work mail. It needs an app that somehow does not want to install on stock 2.3.6. giving the "There was a problem parsing the package" error. Reading on the internet I understand that this error might come from not allowing installing from unknown sources or that the android version is too old for the app. I have allowed installing from unknown sources so I'm guessing the 2.3.6 android version is too old for the app.
So here's my question, I think I know the answer but not 100% sure. Is it possible to install a newer custom android rom on the i9000 without rooting? Or installing the ROM and somehow unrooting?? I'd prefer SlimBean or SlimKat, as clean as possible...
Hope to hear some positive news from you guys.
Click to expand...
Click to collapse
System is too old for this .apk package. Root itself is just included as "su" binary, so unless ROM has it implemented, it will not be here (95% of ROMs have it). No point to avoid root if flashing custom ROM. However you can "unroot" by deleting a few files (/system/xbin/su and /system/app/Superuser.apk or /system/priv-app/Superuser.apk).
devloz said:
System is too old for this .apk package. Root itself is just included as "su" binary, so unless ROM has it implemented, it will not be here (95% of ROMs have it). No point to avoid root if flashing custom ROM. However you can "unroot" by deleting a few files (/system/xbin/su and /system/app/Superuser.apk or /system/priv-app/Superuser.apk).
Click to expand...
Click to collapse
Thanks Devloz. So if I flash SlimICS for example, I can delete the files you mentioned and it should not be rooted anymore? Will give it a try.
I have a few questions
1. Which Defaut Kernel, and where can I download it? I have SM-N7505 Baseband version N7505XXUDOK5 but I had originally N7505XXUCNG5, last year it bricked and I had it worked on it works now but I really dont want the russian kernel os, and the base kernel seems to be Russian which I want to remove and set to the correct base original stock kernel os or Samsung Kernel and Android Lolipop or Marshmallow. Not really interested in putting other os or over doing it... just want to root so I can delete and setup the system how I want without blocking and system stops.
2. I am familiar with ADB and Odin but need to root through Linux as this is my OS.
3. I have looked through many roots here but none are specific to my needs so help is much appreciated. I would even setup a remote for a tech who is willing to help me out.
4. My biggest issue is how to properly extract and what files to extract and upload to my phone to root it
I hope this is clear. I have international calling and will call or connect with anyone who is wiling to help me out.
Any help is very much appreciated
Cheers!
Hello all!
I'm trying to play with Linux kernel source code for various reasons: e.g. add new feature to netfilter.
But i got problems even with pure "vanilla" kernel!
What i've do:
downloaded Google source code for Linux kernel
built it
copy to <rom_src_root>/device/google/coral-kernel (replacing old one)
make bootimage
adb reboot bootloader
fastboot boot <rom_src_root>/out/target/product/coral/boot.img
Touchscreen and Wi-Fi don't work at all.
I moved touchscreen driver to drivers/staging, make it compile, and after that touchscreen began to work.
So, how one can debug kernel with complete ROM flashing?
Do fastboot requires fully monolithic kernel, or i am doing smth wrong?
P.S. My first post here, don't sure where to place such kind of question
Hi!, I know this is from a while ago. Sorry sorry for disturbing you with this.
I'm facing the same issue.
Did you happen to find a solution for this?
eraxillan said:
Hello all!
I'm trying to play with Linux kernel source code for various reasons: e.g. add new feature to netfilter.
But i got problems even with pure "vanilla" kernel!
What i've do:
downloaded Google source code for Linux kernel
built it
copy to <rom_src_root>/device/google/coral-kernel (replacing old one)
make bootimage
adb reboot bootloader
fastboot boot <rom_src_root>/out/target/product/coral/boot.img
Touchscreen and Wi-Fi don't work at all.
I moved touchscreen driver to drivers/staging, make it compile, and after that touchscreen began to work.
So, how one can debug kernel with complete ROM flashing?
Do fastboot requires fully monolithic kernel, or i am doing smth wrong?
P.S. My first post here, don't sure where to place such kind of question
Click to expand...
Click to collapse
As a beginner when it comes to cooking ROMs, I want to learn how do you build a custom ROM on the example on my phone (Motorola Moto E5 XT1944-2 Nora). However, it's very hard, if not impossible, to find a tutorial for this phone, as the phone's default kernel seems to be complex (forced encryption) compared to other phones.
How can I extract vendor, deivce and kernel files from my phone? I do understand what vendor and kernel files are, but what are device files? Are they remaining partitions on my phone excluding private ones like userdata?
If I knew could compile how to build a custom ROM exactly for this device, I would be thankful for your support.
bump
Hello
How can I flash SW_BINARIES_FOR_XPERIA_ANDROID_11_4.14_V9A_YOSHINO.ZIP over the stock version?
Software binaries for AOSP Android 11.0 – Kernel 4.14 – Yoshino (latest) - Sony Developer World
developer.sony.com
Tried to understand the official manual from here but can't understand where can I get the rest of the img files (boot, system...) - https://developer.sony.com/develop/...-aosp-android-android-11-0-0/#tutorial-step-8
You don't want to combine the AOSP binaries and stock. Those files are meant for pure AOSP builds that don't use the Sony vendor files. Most recent XZ1c ROMs start from stock, so would break if you changed to OEM files.
So if you were doing another ROM, you could go into fastboot and flash this partition and any others from the ROM, or maybe do some of the others from recovery. (e.g. some ROMs might come with their own rather than TWRP.)
Perhaps better question is to ask what you're trying to do with them here.
tonsofquestions said:
You don't want to combine the AOSP binaries and stock. Those files are meant for pure AOSP builds that don't use the Sony vendor files. Most recent XZ1c ROMs start from stock, so would break if you changed to OEM files.
So if you were doing another ROM, you could go into fastboot and flash this partition and any others from the ROM, or maybe do some of the others from recovery. (e.g. some ROMs might come with their own rather than TWRP.)
Perhaps better question is to ask what you're trying to do with them here.
Click to expand...
Click to collapse
Hey @tonsofquestions ! I just want to upgrade to Android 11 And I assume it's not LineageOS (Which already tried but wants another OS to try)
It depends on the ROM, not the Android version. The Lineage 18.1 ROM is Android 11, and is based on stock.
Compare that to something like this one https://forum.xda-developers.com/t/g8441-xz1c-lilac-aospextendedrom-oreo.3859656/ which says it's AOSP, and has a step in the instructions to download and install the OEM files.
I also don't think there are many non-Lineage ROMs for 11. Maybe Havoc, but that's still stock-based. Which specific ROM do you want to try?
tonsofquestions said:
It depends on the ROM, not the Android version. The Lineage 18.1 ROM is Android 11, and is based on stock.
Compare that to something like this one https://forum.xda-developers.com/t/g8441-xz1c-lilac-aospextendedrom-oreo.3859656/ which says it's AOSP, and has a step in the instructions to download and install the OEM files.
I also don't think there are many non-Lineage ROMs for 11. Maybe Havoc, but that's still stock-based. Which specific ROM do you want to try?
Click to expand...
Click to collapse
Want to flash this Android 11 img, and not quite know how....
Probably by following the instructions in the thread.
But if you don't include a link to the image, it's impossible to be any more specific.