System_Extractor is unpacking nougat roms, but unable to repack. can anyone help me out repacking roms?
(only help if u have working formula, i have tried several methods/software found on this forum/other sites. repacking doesn't work)
Related
I have Just one thing I can't figure out when porting a rom. Its the config for the kernel when I unpack it I know I am suppose to get the zimage and replace with the kernel I am porting to and rename the .rc files and replace lib files.But when i recompiile it and flash it to my device.It gets stuck on the android logo after rle image boot.Can someone please help me out since I seem to be the only one porting or making a roms for the samsung Repp sch-r680 at the moment. Also I can't seem to figure out how to overclock a kernel ether or find anything on google and believe me I search over like 50 google next results and nothing.I ant a totally Noob ether I have already made a custom rom for the repp with init.d support and found another way to root it using my clockwork mod that I ported over to it.I also added busy box and su to the cwm for adb support.
samsungcrasher said:
I have Just one thing I can't figure out when porting a rom. Its the config for the kernel when I unpack it I know I am suppose to get the zimage and replace with the kernel I am porting to and rename the .rc files and replace lib files.But when i recompiile it and flash it to my device.It gets stuck on the android logo after rle image boot.Can someone please help me out since I seem to be the only one porting or making a roms for the samsung Repp sch-r680 at the moment. Also I can't seem to figure out how to overclock a kernel ether or find anything on google and believe me I search over like 50 google next results and nothing.I ant a totally Noob ether I have already made a custom rom for the repp with init.d support and found another way to root it using my clockwork mod that I ported over to it.I also added busy box and su to the cwm for adb support.
Click to expand...
Click to collapse
I have a repp that I'm interested in working on. I've never ported a rom, but I understand Linux and some Android, and I don't mind staring at a terminal all day. I'd like to get something aosp working on it.
Let me know if you're still working on this phone.
I know this is a bit scarce, but I need help with a kernel. Why? Because I unfortunately don't have a
computer at the moment (much less Ubuntu suite), just my trusty GT-i9505. Also, I have a few
questions.
First of all, this is the guide I am following:
[GUIDE] Use aircrack-ng on android phone using Wireless USB Adapter
http://forum.xda-developers.com/showthread.php?t=2338179
This guide is aimed towards amateur kernel builders,
and the suggested ROM for use with this is Cyanogen Mod. Although, the post does mention that he was able to use his stock touchwiz ROM. He mentions he was able to do it with a few minor adjustments (along with the kernel and .md5 file):
I got this to work on my stock Samsung TouchWiz ROM by making a few adjustments:
- Get the kernel from Samsung: http://opensource.samsung.com/
- Change the lines in the .config file of the kernel below ## Samsung Rooting ... from =y to =n using nano
- To get boot.img, download the ...tar.md5 firmware matching your current firmware from http://www.sammobile.com/firmware/, rename .tar.md5 to .tar, and extract the boot.img. You cannot use mkbootimg here, only abootimg, as this boot.img has a special ramdisk address!
Click to expand...
Click to collapse
I would love to do this with my current TouchWiz ROM, (not stock) Samy Deluxe ROM- Operation Ivy
Any help/luck doing this? Thanks in advance
Bump
Bump. Let me also add that I can give the source to the kernel (of the ROM I have).
Really all that needs to be done is to rebuild that kernel (and follow the steps of course to the guide I'm using).
I have a TP Link tl-wn722n USB Wireless adapter, so I need to have the module/driver installed into that kernel.
The name of the kernel is 3.4.100-GoogyMax3_TW-v1.1.3
Here's the link to the kernel: http://forum.xda-developers.com/attachment.php?attachmentid=2895862&d=1407942420
I downloaded my kernel and looked inside of the zip file and don't seem to find a ".config" file as mentioned in the guide, but did see a boot.img so I don't believe there's a need to download the .md5 file:
I got this to work on my stock Samsung TouchWiz ROM by making a few adjustments:
- Get the kernel from Samsung: http://opensource.samsung.com/
- Change the lines in the .config file of the kernel below ## Samsung Rooting ... from =y to =n using nano
- To get boot.img, download the ...tar.md5 firmware matching your current firmware from http://www.sammobile.com/firmware/, rename .tar.md5 to .tar, and extract the boot.img. You cannot use mkbootimg here, only abootimg, as this boot.img has a special ramdisk address!
Click to expand...
Click to collapse
Any help at all would be greatly appreciated.
Bump... again...
Hi guys I'm a aspiring developer. Very new to android development. I do have a pretty good handle on the basics, but I'm learning as I go.
Anyway I was wondering if anyone here has been able to deodex the stock MM for the LG G5 H830 (T-Mobile) Varient?
I tried SuperR's Kitchen to deodex which was successful in booting, but upon reaching the initial setup screen I'm greeted with LG Keyboard. GP Services has stopped over and over.
Things I've tried (with SuperR's Kitchen):
1. Not Zipaligning after deodex (problem remains).
2. Both oat2dex as well as smali deodex options.
3. Building with SuperR's booting to Windows. Extracting with 7zip. Deodexing with IOIO Deodexer tool. Rezipping with 7 zip. Flashing results in not making it past T-Mo BootAnimation. The led lights up, but it doesn't play the T-mo jingle.
I would like to deodex/zipalign to the theme the rom in the future, but I'm at a loss. Thanks to anyone who can be of help.
Some more info.
Device:LG G5 H830
Android Version: MM 6.0.1
Build number: 10A
Rom Modded with: SuperR's Kitchen (Donate Version)
Starting files: System.img, Boot.img pulled from device.
Perm type: Set Metadata.
Note the reason I'm asking here is because the Developer of the kitchen has requested no one ask for help in the thread for deodexing unless they have a fix. Thanks guys/gals.
I m facing the same problem and came over this thread.. Tried various deodexers but always ended in bootloop.. A clue would be highly appreciated!
Cheers
Is there a simple way of finding all proprietary/vendor files for porting CM or other AOSP based ROMs?
My phone is running Android 5.1 and I wanted to port CM12.1 to it but having trouble finding these proprietary files, similar devices use different files and I can't seem to understand how people who ported ROMs for them found their list of files for proprietary-blobs.txt
Hello,
First of all, this is my first post in the forum and my first time trying to compile an Android kernel.
My intention was to port Nethunter for my tablet, Samsung SM-T580 (Galaxy Tab A6 10.1 only wifi).
I have successfully compiled the original kernel offered by samsung and i have ended up with a file called Image, a file called Image.gz and a dts folder
I have extracted the original rom boot.img with mkbootimg_tools and i see a kernel file, a ramdisk folder, a ramdisk.packed file and a dt.img
For what i have found is that this must be a non standard thing, the way samsung manages this, and despite i have seen various guides on compiling samsung kernels, i haven't found anyone doing it straight from samsung sources.
I think that the dt.img part is solved with the dtbTool, but i haven't been able to figure out what to do with Image and Image.gz to get the kernel and ramdisk.
¿Can someone give me a lead on this? ¿Is it doable? ¿Should i look for other kernel instead?
Its been long time ago... But did you manage to compile the kernel?