Related
Hi all and happy nex year, first post ever here !
Your forums think im too noob to post this on devemopment section lol .
i have a Samsung Galaxy SII X from telus model SGH-t989D (t989dtlkj3) with 2.6.35.11 kernel. After all coverage about Carrier IQ i found your rom Telus SGH-T989D Stock, Rooted, Lightly Tweaked, 100% [CIQ Free] I was impressed in the work you do on this roms, and i just wanna tell you that i learn a lot from your work.
After read a bit on the subject i got the concusion that you can open a ssh session on your phone and type
Code:
cd /
find / -name '*iq*'
That in my case return
Code:
/system/xbin/uniq
/sys/devices/virtual/tty/[B]sdio_tty_ciq_00[/B]
/sys/devices/virtual/input/input0/uniq
/sys/devices/virtual/input/input2/uniq
/sys/devices/virtual/input/input4/uniq
/sys/devices/virtual/input/input5/uniq
/sys/devices/virtual/input/input7/uniq
/sys/devices/virtual/input/input8/uniq
/sys/devices/virtual/input/input9/uniq
/sys/devices/virtual/input/input10/uniq
/sys/devices/i2c-5/5-0025/input/input6/uniq
/sys/devices/i2c-6/6-0055/pm8058-keypad/input/input1/uniq
/sys/devices/i2c-6/6-0055/pm8058-pwrkey/input/input3/uniq
/sys/class/tty/[B]sdio_tty_ciq_00[/B]
/dev/[B]sdio_tty_ciq_00[/B]
After read your post Here and some source code read HERE i can tell that i have some kind of Carrier IQ on my phone right !!! But wait if i understand correcly, its like some services that are autostarted in the kernel at boot time.
In your ROM we can find a file named boot.img and im pretty sure its the kernel [CIQ Free] right ? i see in your updater-script that you use something like this for the updating the kernel
Code:
assert(package_extract_file("boot.img", "/tmp/boot.img"),
write_raw_image("/tmp/boot.img", "/dev/block/mmcblk0p8"),
delete("/tmp/boot.img"));
My question is: can i update/flash ONLY my kernel using a command like flash_image for update my kernel (/dev/block/mmcblk0p8) to your CIQ Free boot.img ?
something like this ssh on phone and type
flash_image boot /sdcard/boot.img ???
Thank for the help
MrWarLock said:
My question is: can i update/flash ONLY my kernel using a command like flash_image for update my kernel (/dev/block/mmcblk0p8) to your CIQ Free boot.img ?
something like this ssh on phone and type
flash_image boot /sdcard/boot.img ???
Thank for the help
Click to expand...
Click to collapse
If I've read the thread for Mr. X's ROM, it seems as though he has included his CIQ-free recompiled kernel with it. So when you flashed the ROM, it also flashed the kernel. So if I understand what you're trying to say, you want to flash the CIQ-free kernel over itself?
I quickly looked through the contents of a flashable kernel (faux 6u) and what you're saying seems to be true. The kernel does seem to be the boot.img file seeing as how the flashable .zip file contains that file, a couple of scripts, a .so file, and a binary.
Sent from my SGH-T989D
So when you flashed the ROM, it also flashed the kernel. So if I understand what you're trying to say, you want to flash the CIQ-free kernel over itself?
Click to expand...
Click to collapse
i dont have flashed or use odin/CWM for install this Rom (My phone are allready rooted). I just wanna know if i can take the boot.img that are the kernel free CIQ (thats file are in the Mr X Rom) and install it to my phone via ssh
Like i said, can i use a command like flash_image ?
Thanks for any help/tips
MrWarLock said:
i dont have flashed or use odin/CWM for install this Rom (My phone are allready rooted). I just wanna know if i can take the boot.img that are the kernel free CIQ (thats file are in the Mr X Rom) and install it to my phone via ssh
Like i said, can i use a command like flash_image ?
Thanks for any help/tips
Click to expand...
Click to collapse
You can install any kernel you like but it wont disable the ciq located in rom, you have to remove the apps, libraries and if you want to go as far as i did, edit the system framework extensively as well as some apks.
Fully reading my threads would have informed you on what i had edited as i has posted actively about what i found and where.
Hi
The development of this ROM has been suspended at the moment due to my busy and conflicting schedule. However, fellow developer krabappel2548 is working on an AOSP ROM too. You may like to check out his work on the XDA Forums and on Facebook. I would like to thank all members of the XDA community for your generous assistance and kind support.
I am new to Android development and have recently gotten myself a brand new Xperia S. After browsing through many forums and websites, I have discovered that our Xperia S was once an experimental device of the AOSP. However, I have noticed that there are hardly any AOSP ROMS built for our device. As I'm having a break now, I have some free time on my hands so I thought why not have a go at building an AOSP ROM for our device. So, I present to you XDantheManX Jellybean, a vanilla AOSP ROM for our Xperia S.
Basically, I downloaded the Android sources from the official repository, cloned the Xperia S AOSP repository, included the software binaries for Xperia S from Sony Mobile and built an Android system for our device. I will be uploading my sources onto a GitHub repository for all to contribute in the near future.
WARNING! This is an unstable PRE-ALPHA release. I will not be held responsible if you brick your device.
DOWNLOAD XDantheManX Jellybean 4.2.1 (Unflashable)
DOWNLOAD XDantheManX Jellybean 4.1.1 (Recommended)
DOWNLOAD XDantheManX Jellybean 4.1.1 (Flashable CWM Zip)
Pre-requisites
- Unlocked bootloader. Instructions here.
- Installed fastboot driver for Xperia S if using Windows.
- Android SDK
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Installation instructions
1. Download XDantheManX Jellybean (CWM flashable zip) and flash using CWM Recovery.
2. Flash a CM10 kernel eg. FXP/NOVA of your choice.
Bugs
Report bugs here!
At present, we have issues with compiling the ROM and getting it to boot because:
- Sony's Github device files are in the progress of being modified for Android 4.2
- Therefore, we are unable to create a fully-working 4.1 ROM
- We are also unable to create a fully-working 4.2 ROM as the migration has not been completed.
So, we're stuck somewhere in the middle :/
- Fastboot flashing method is stuck on system.img for 4.1.2
Please post any bugs on this thread and inform me if it is working/not working. PM me if you require any assistance or would like to work together in developing this ROM.
Let's work together to improve this ROM! :highfive:
Hit the Thanks :good: button if this made your day!
Good luck man, it's good to see a AOSP ROM for our device
That is really nice. I look forward to test this on my device soon. Good job man :good:
EDIT: Why such a complicated way of installing this? Can't it be a little bit more user-friendly? Like install ROM with CWM, and maybe flash the kernel with fastboot?
And both links lead to AOSP 4.1.2. No link for JB 4.2.1.
Felimenta97 said:
That is really nice. I look forward to test this on my device soon. Good job man :good:
EDIT: Why such a complicated way of installing this? Can't it be a little bit more user-friendly? Like install ROM with CWM, and maybe flash the kernel with fastboot?
And both links lead to AOSP 4.1.2. No link for JB 4.2.1.
Click to expand...
Click to collapse
Link to JB 4.2.1 fixed!
I'm still quite new to this and am not sure how to create a flashable CWM zip. Could you teach me how please? Thanks.
Thx for supporting XS and this community
I will try it soon
Sent from my Xperia S using xda app-developers app
XDantheManX said:
Link to JB 4.2.1 fixed!
I'm still quite new to this and am not sure how to create a flashable CWM zip. Could you teach me how please? Thanks.
Click to expand...
Click to collapse
I don't know how to do that, sorry
I never did anything with that instalation method, and even being quite a experienced user, I'm scared of that
Try asking help for championswinner (AOKP dev) or Krabappel (KA ROM dev).
XDantheManX said:
Link to JB 4.2.1 fixed!
I'm still quite new to this and am not sure how to create a flashable CWM zip. Could you teach me how please? Thanks.
Click to expand...
Click to collapse
try this - [GUIDE] How to make a cwm recovery flashable zip - http://forum.xda-developers.com/showthread.php?t=1721680
First 4.2.1 for our device...
Thank you so much...
As it is a pre alpha ,i wanted to ask are the basic things working like mobile data ,wifi ,bluetooth, camera etc etc??
Edit:- First Vanilla 4.1.2 for our device as 4.2.1 has some problems....
Sent from my iPhone 6 using Key Lime Pie
ap030993 said:
First 4.2.1 for our device...
Thank you so much...
As it is a pre alpha ,i wanted to ask are the basic things working like mobile data ,wifi ,bluetooth, camera etc etc??
Sent from my iPhone 6 using Key Lime Pie
Click to expand...
Click to collapse
especially the Wi-Fi, the CM10 rom never seems to read the MAC from my telephone and gives it a MAC adress build in the rom itself, since me and my father both had cm10 we had had same MAC, the wifi gives ip's based on MAC so that conflicted a lot. (thus i went back to CM9.1)
does this rom read the actual telephone's MAC adress?
This way of installing is the same as the way in which Sony released the ICS beta for the 2011 line. It's totally safe, don't worry
Update: Receiving error when executing first command in instructions?
fareeed said:
This way of installing is the same as the way in which Sony released the ICS beta for the 2011 line. It's totally safe, don't worry
Click to expand...
Click to collapse
If you say so, I will do it. To go back, the only thing is installing a kernel with a recovery and go back, right? Kinda confused.
Felimenta97 said:
If you say so, I will do it. To go back, the only thing is installing a kernel with a recovery and go back, right? Kinda confused.
Click to expand...
Click to collapse
Doesn't seem to flash throws out errors when trying to execute the first command,
Code:
fastboot flash userdata out/target/product/lt26/userdata.img
Yeah to return just flash kernel with recovery and restore your nandroid or w/e
fareeed said:
Doesn't seem to flash throws out errors when trying to execute the first command,
Code:
fastboot flash userdata out/target/product/lt26/userdata.img
Yeah to return just flash kernel with recovery and restore your nandroid or w/e
Click to expand...
Click to collapse
Ok. And you're saying that the first command line isn't working?
Felimenta97 said:
Ok. And you're saying that the first command line isn't working?
Click to expand...
Click to collapse
Yeah, I think fastboot flash userdata userdata.img may work. Not too sure, best off waiting for the dev to reply I think.
fareeed said:
Yeah, I think fastboot flash userdata userdata.img may work. Not too sure, best off waiting for the dev to reply I think.
Click to expand...
Click to collapse
fareeed said:
This way of installing is the same as the way in which Sony released the ICS beta for the 2011 line. It's totally safe, don't worry
Update: Receiving error when executing first command in instructions?
Click to expand...
Click to collapse
Are you using the 4.1.2 or 4.2.1 build? I would recommend using the 4.1.1 build.
Apologies for my mistake in the instruction. I stated to move the extracted files to the Android SDK Tools folder where fastboot resides. Therefore, since both files reside in the same directory, to flash userdata.img, the code should be:
Code:
fastboot flash userdata userdata.img
Hope the flashing is successful now! :fingers-crossed:
I built this ROM following the instructions on the Sony Xperia S AOSP Github as I have a powerful machine and wanted to develop an AOSP ROM for the community. However, I have yet to test it as I currently have a locked bootloader, having gotten it recently. Nevertheless, I am planning to unlock it in the near future though as software development has always been my passion and the I am planning to use the Xperia S to test and develop more software, such as Firefox OS, which I'm very interested in at the moment.
Do you know if unlocking the bootloader will void my warranty, and to what extent? Thanks.
XDantheManX said:
Are you using the 4.1.2 or 4.2.1 build? I would recommend using the 4.1.1 build.
Apologies for my mistake in the instruction. I stated to move the extracted files to the Android SDK Tools folder where fastboot resides. Therefore, since both files reside in the same directory, to flash userdata.img, the code should be:
Code:
fastboot flash userdata userdata.img
Hope the flashing is successful now! :fingers-crossed:
I built this ROM following the instructions on the Sony Xperia S AOSP Github as I have a powerful machine and wanted to develop an AOSP ROM for the community. However, I have yet to test it as I currently have a locked bootloader, having gotten it recently. Nevertheless, I am planning to unlock it in the near future though as software development has always been my passion and the I am planning to use the Xperia S to test and develop more software, such as Firefox OS, which I'm very interested in at the moment.
Do you know if unlocking the bootloader will void my warranty, and to what extent? Thanks.
Click to expand...
Click to collapse
I will flash 4.2.1 just for a quick try and such.
About unlocking bootloader, the theory is that they still should fix your device if no hardware harm due overclocking or anything like that happened, but most stores don't fix it just because being unlocked. Also it breaks Download Music Info from Walkman and Bravia Engine on Stock ICS (it's a bug).
ERROR while flashing the second part:
If I type "fastboot flashall" it gives me:
"error: neither -p product specified nor ANDROID_PRODUCT_OUT set"
What should I do?
I already flashed userdata.img...
Even after flashing ramdisk.img, the system got stuck on flashing boot.img, so I stopped, tried to flash the dual.elf (dual boot kernel) and failed. I rebooted the phone (Had to do so, fastboot command didn't worked) and I still have dual boot recovery. Restoring backup now. Hope not to have any problems with the userdata.img thing.
Felimenta97 said:
I will flash 4.2.1 just for a quick try and such.
About unlocking bootloader, the theory is that they still should fix your device if no hardware harm due overclocking or anything like that happened, but most stores don't fix it just because being unlocked. Also it breaks Download Music Info from Walkman and Bravia Engine on Stock ICS (it's a bug).
ERROR while flashing the second part:
If I type "fastboot flashall" it gives me:
"error: neither -p product specified nor ANDROID_PRODUCT_OUT set"
What should I do?
I already flashed userdata.img...
Even after flashing ramdisk.img, the system got stuck on flashing boot.img, so I stopped, tried to flash the dual.elf (dual boot kernel) and failed. I rebooted the phone (Had to do so, fastboot command didn't worked) and I still have dual boot recovery. Restoring backup now. Hope not to have any problems with the userdata.img thing.
Click to expand...
Click to collapse
Thanks for testing out the ROM, @Felimenta97! There have been some reported problems with flashing the boot.img for Android 4.2.1 and I was not sure if they have been addressed yet, therefore I did not recommend to flash it. However, Bjorn Andersson, the lead developer on Sony Xperia S AOSP has stated that Sony will be addressing these problems in a future update of their Github repositories. I will then rebuild 4.2.1 again after the update.
userdata.img is flashed as the /data partition on the ROM. Therefore, if you wipe the data partition using your recovery, your phone should be working fine after the restore.
I will be unlocking my bootloader and testing the ROMs soon, during which I will try to address the reported errors. Are you able to get a working BRAVIA Engine/ BRAVA Engine 2 on the stock/custom ROM after unlocking the bootloader? Have you tried flashing 4.1.2? Thanks!
XDantheManX said:
Thanks for testing out the ROM, @Felimenta97! There have been some reported problems with flashing the boot.img for Android 4.2.1 and I was not sure if they have been addressed yet, therefore I did not recommend to flash it. However, Bjorn Andersson, the lead developer on Sony Xperia S AOSP has stated that Sony will be addressing these problems in a future update of their Github repositories. I will then rebuild 4.2.1 again after the update.
userdata.img is flashed as the /data partition on the ROM. Therefore, if you wipe the data partition using your recovery, your phone should be working fine after the restore.
I will be unlocking my bootloader and testing the ROMs soon, during which I will try to address the reported errors. Are you able to get a working BRAVIA Engine/ BRAVA Engine 2 on the stock/custom ROM after unlocking the bootloader? Have you tried flashing 4.1.2? Thanks!
Click to expand...
Click to collapse
I get it, I think... Anyway, I will wait for it then. I didn't tried the 4.1.2 because it isn't exactly what I want. I kinda want to check what is working on 4.2, the new things etc. I have 4.1.2 on PA, so I'm happy with it
But I can try flashing 4.1.2 for testing if you want. Btw, what I have to do with that kernel file?
About BRAVIA, it's a bug related to ICS and bootloader. No one knows how to make it work on Stock ROMs. Some say Bravia is working on PAC (AOSP based) ROM. I'm not sure about it, though.
Felimenta97 said:
I have 4.1.2 on PA, so I'm happy with it
But I can try flashing 4.1.2 for testing if you want. Btw, what I have to do with that kernel file?
About BRAVIA, it's a bug related to ICS and bootloader. No one knows how to make it work on Stock ROMs. Some say Bravia is working on PAC (AOSP based) ROM. I'm not sure about it, though.
Click to expand...
Click to collapse
Thanks @Felimenta97! I would love it if you could test 4.1.2 to check if there are any problems with the flashing.
You may disregard the kernel file. I had included it as it was output when I built the ROM. After further reading, I understand that the kernel has been merged together with ramdisk.img into boot.img so I'm clueless to the file's purpose at the moment too.
Is PA 4.1.2 working well as a ROM for daily use? Thanks for your assistance!
XDantheManX said:
Thanks @Felimenta97! I would love it if you could test 4.1.2 to check if there are any problems with the flashing.
You may disregard the kernel file. I had included it as it was output when I built the ROM. After further reading, I understand that the kernel has been merged together with ramdisk.img into boot.img so I'm clueless to the file's purpose at the moment too.
Is PA 4.1.2 working well as a ROM for daily use? Thanks for your assistance!
Click to expand...
Click to collapse
I'm using it more as a test ROM and backup ROM. I'm the PA, Dark PA and PAC main tester, so...
But yes, PA works fine for me. One of the best AOSP ROMs so far.
I will test it now.
I started making my ROM with Android Kitchen and I dumped system folder from ftf file.
But I cannot find META-INF and boot.img to use for ROM.
I tried using MIUI v4 META-INF and boot.img but I get status 6 error while installing ROM. By Kitchen's FAQ it means something is up with update-script. So, I need to find stock boot.img for latest ICS Arc S firmware and associated META-INF with update-script.
I searched for those files for more than 8 hours, still can't find them.
I hope if anyone posts them that I could be able to normally install ROM without a problem.
Thank you in forward.
Err, there is no stock boot.img. All stock kernels are provided in the stock firmware packages also known as FTF files.
Depending on what you need it for, you can download the source code(, make the modifications) and compile it yourself.
Hmmm, how am I going to make custom ROM without boot.img if it is needed(or is it?).
I can't get any other custom kernel because I want to make ROM for locked bootloader phone.
Do you know what should I do to complete ROM if i can't have stock boot.img?
A_B_E_D said:
Hmmm, how am I going to make custom ROM without boot.img if it is needed(or is it?).
I can't get any other custom kernel because I want to make ROM for locked bootloader phone.
Do you know what should I do to complete ROM if i can't have stock boot.img?
Click to expand...
Click to collapse
For roms built on stock Rom, u shouldnt have any kernel inside the flashable zip
Sent from my LT18i
Sahaab said:
For roms built on stock Rom, u shouldnt have any kernel inside the flashable zip
Sent from my LT18i
Click to expand...
Click to collapse
Yeah, that's what I though after someguyfromhell wrote a post and I made a new zip without boot.img and deleted write_raw_image line from update-script.
Right now I am searching for solution to other problem(some folders and files are not showing up on my sdcard while viewing it in Windows, so I have no space to drop ROM in there, will try when I fix this).
Thank you both for replies, will try to fix this soon.
A_B_E_D said:
Hmmm, how am I going to make custom ROM without boot.img if it is needed(or is it?).
I can't get any other custom kernel because I want to make ROM for locked bootloader phone.
Do you know what should I do to complete ROM if i can't have stock boot.img?
Click to expand...
Click to collapse
If you are going to do a ROM for locked bootloaders, then there is no boot.img needed at all. Locked bootloader means stock kernel, means no boot.img.
Also, it is not needed. Some ROM developers supply their own kernels together with the ROM, however it is not a requirement.
Is there an way to port a gsm rom (jb like sphlong or omega) to cdma? I tried Curtis's guide by i found myself stuck and it wouldn't boot properly. What i got stuck on was the boot.img part of it. Here's the guide
http://forum.xda-developers.com/showthread.php?t=2362137
Can someone possibly explain how to get the boot.img to work, i cant understand what its saying
Dbzavatar said:
Is there an way to port a gsm rom (jb like sphlong or omega) to cdma? I tried Curtis's guide by i found myself stuck and it wouldn't boot properly. What i got stuck on was the boot.img part of it. Here's the guide
http://forum.xda-developers.com/showthread.php?t=2362137
Can someone possibly explain how to get the boot.img to work, i cant understand what its saying
Click to expand...
Click to collapse
use the boot image from your base ROM.
If you're S-ON use fastboot to flash it.
MameTozhio said:
use the boot image from your base ROM.
If you're S-ON use fastboot to flash it.
Click to expand...
Click to collapse
One more thing, the modules from the base ROM's boot.img has to be added to the GSM rom, right?
Yes add the modules from the base rom boot img. Be sure the boot img you use is from a compatible and same version cdma rom. In other words,if the rom you are converting is 4.1+ use a cdma boot.img that is meant for 4.1+ roms. If the rom is 4.0,use a cdma 4.0 based boot.img along with its modules. Be aware that some roms just do not respond as expected even if you make these changes. It is trial and error finding roms that will convert as expected.
Thanks!!
Curtis1973 said:
Yes add the modules from the base rom boot img. Be sure the boot img you use is from a compatible and same version cdma rom. In other words,if the rom you are converting is 4.1+ use a cdma boot.img that is meant for 4.1+ roms. If the rom is 4.0,use a cdma 4.0 based boot.img along with its modules. Be aware that some roms just do not respond as expected even if you make these changes. It is trial and error finding roms that will convert as expected.
Click to expand...
Click to collapse
I tried to redo the conversion with the sphlonge rom and while flashing, i got
assert failed: getprop('ro.product,device")
does this mean i cant flash it since its primou?
Dbzavatar said:
I tried to redo the conversion with the sphlonge rom and while flashing, i got
assert failed: getprop('ro.product,device")
does this mean i cant flash it since its primou?
Click to expand...
Click to collapse
change the line in updater-script to primoc
I have an SM-807T tablet, which has very little available for it so far and i need a selinux permissiveable kernel. Being seasoned in programming linux and compiling i attempted to create my own, so i got the correct source code from samsung, changed the selinux flag and compiled, no problems. Everything compiled correctly, so i got the stock boot.img tore it apart, replaced the kernel and put it back together. attempted to flash it and it got stuck in an infinite loop. Backtrack, thanks to some stellar members here in an earlier thread i got ahold again of the stock kernel and restored my tablet, fast forward a few more days i still cant get it to work, only thing i can find is people saying that when you compile the kernel you need to replace the drivers on the ramdisk... i understand that however it seems that this kernel all modules are self contained. Can anyone direct m on what i may be doing wrong? i can provide any information that may be needed, i just dont know what could be required so i hope the explanation itself can surfice until someone can let me know what kind of information i need to post.
Thank you.
Are you compiling a kitkat or lollipop kernel and is your boot loader and current Rom compatible with that kernel?
Have you looked at the kernel logs?
ashyx said:
Are you compiling a kitkat or lollipop kernel and is your boot loader and current Rom compatible with that kernel?
Have you looked at the kernel logs?
Click to expand...
Click to collapse
Thank you for the reply, It is a kitkat kernel as it is the only available version, lollipop source has not been released yet. My rom version is the same of the source
KOT49H.T807TUVU1ANK SuperSkillRom Build
T807TUVU1ANK source code.
also what kernel logs are you referring too, are there logs in the android os that may be logging the restart error?
the baseband version is T807TUVU1BOE1, is it possible that could be causing my issue?
ashyx said:
Have you looked at the kernel logs?
Click to expand...
Click to collapse
I missed this part the first read What kernel logs are you referring to, compile logs or logs in the android os that might be logging the error? If it is the later, where exactly would i find those?
In an android terminal such as adb or recovery. su then cat /proc/last_kmsg > /sdcard/last_kmsg
This has to be done immediately after the last boot.
ashyx said:
In an android terminal such as adb or recovery. su then cat /proc/last_kmsg > /sdcard/last_kmsg
This has up be done immediately after the last boot.
Click to expand...
Click to collapse
Thank you for that, i found what happened though im still at a loss at how to fix it. My linux knowledge stops at things i haven't encountered before.
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
is the panic line. I will attach the whole log if you think there might be more helpful information in there.
Which config did you use when building and where did you get the ramdisk from?
ashyx said:
Which config did you use when building and where did you get the ramdisk from?
Click to expand...
Click to collapse
the ramdisk used was the boot.img from my rom i am using, superskill v1
the config i used to compile was chagalllte_usa_tmo_00_defconfig.
Ceirnos said:
the ramdisk used was the boot.img from my rom i am using, superskill v1
the config i used to compile was chagalllte_usa_tmo_00_defconfig.
Click to expand...
Click to collapse
When you say from the Rom do you mean the boot.img was included with it or you pulled it from the device itself?
ashyx said:
When you say from the Rom do you mean the boot.img was included with it or you pulled it from the device itself?
Click to expand...
Click to collapse
Included with it, should i have pulled from the device instead? i had figured it would have been the same after the flash.
Again I thank you for your time and patience helping me with this.
Ceirnos said:
Included with it, should i have pulled from the device instead? i had figured it would have been the same after the flash.
Again I thank you for your time and patience helping me with this.
Click to expand...
Click to collapse
No it shouldn't make a difference. I think your problem is with the ram disk. Did you build the kernel with the ramdisk or just repack it and did you change anything?
If it's a repack, have you tried to repack the working kernel with the same ramdisk to make sure its not something to do with the way you are repacking the kernel with the ramdisk?
ashyx said:
No it shouldn't make a difference. I think your problem is with the ram disk. Did you build the kernel with the ramdisk or just repack it and did you change anything?
If it's a repack, have you tried to repack the working kernel with the same ramdisk to make sure its not something to do with the way you are repacking the kernel with the ramdisk?
Click to expand...
Click to collapse
The simplest things cause the biggest headaches, upon your advice i tried repacking the working kernel and it did not work. i attempted a different method and no i have a working permissive-able kernel. Thank you very much. I will rebuild it into a stock boot.img as well an test it out in order to allow the SM-T807T users who dont want to mess with compiling a more flexible kernel as well.
Your help was invaluable as i dont think i would have considered my repacking method to be the fault.
No worries, glad you got it sorted.