Related
I have re-written the ICS camera HAL module to be a thin wrapper for the gingerbread libcamera.so and hence it will only work with the 2.6 kernel. The advantage is that getting to gingerbread level functionality should be quick Creating a new thread because there is a slight chance that this will work for all qualcomm devices with existing libcamera.so files (with slight mods ofcourse )
http://www.mediafire.com/download.php?wjf035mz2vzunw4
Here is a zip file which contains the new camera HAL module. README file accompanying it has instructions on the locations for the files. If you already have the previous version of camera HAL working, all you have to do is replace camera.qsd8k.so and libcamera.so with the ones in the zip file.
What works:
1) Preview works.
2) Taking a picture works pretty well.
3) Size of picture is no longer huge.
4) Software zoom works.
5) Most of the other knobs like focus, file size etc. seemed to work as well in my testing.
6) Pretty stable as far as I can see
Not working yet:
Video and other fancy stuff.
If people have requests for other qualcomm devices after having tried the HAL included in the zip file, kindly include the following information.
1) logcat from having used the HAL module.
2) build.prop
3) libcamera.so from gingerbread ROM for the device.
4) liboemcamera.so from gingerbread ROM.
Currently known to work on the following devices:
1) Nexus One.
2) HTC Desire
3) HTC HD2
Enjoy and thanks for all the feedback.
Updates:
02/09/2012
Working barcode scanner mode
Flashable zip file (should work with texasice's ROMs)
http://www.mediafire.com/?w4fu0u05qtxq3tu
01/30/2012
Working Panorama mode
Flashable zip file (should work with texasice's ROMs)
http://www.mediafire.com/?5r599m5jg5yfaqn
Known issues:
Sometimes screen has some garbage while in Panorama mode viewfinder. Quitting completely from the app and restart or invoking Gallery from inside the app and returning back to camera app should mostly fix it.
Video enabled version:
Fastboot compatible images compiled from evervolv base:
For Stock hboot :
http://www.mediafire.com/?wdlip7h6necetia
For HBoot(s) supporting larger /system partition
http://www.mediafire.com/?f6rz3sz2r97qln0
Source code is now available at
https://github.com/rapmv78/
Your upload doesn't include a HAL, and from your instructions I am not sure if you are implying to use the HAL and the GB libcamera and liboemcamera, or the ones included.
please show me what i have to type in adb to push these files? (sorry i'm noob)
is camera.qsd8k.so not included?
sorry for my english..
Sorry wrong link. Now updated. Please re-download. And yes the files need to pushed through adb.
One step closer!
Thank you!
twistedumbrella said:
Your upload doesn't include a HAL, and from your instructions I am not sure if you are implying to use the HAL and the GB libcamera and liboemcamera, or the ones included.
Click to expand...
Click to collapse
Link fixed. The files included in the zip are the ones to be used. The generic libs part is only for people with non nexus one devices and would want help enabling camera on them. Hope this clarifies better.
Is the code specific to qsd8 or just a generic wrapper function? On most "newer" devices you are looking at msm7x30, but generic qsd8 code, much like the gralloc, would still work with a rename.
Sent from my ADR6400L using Tapatalk
rapmv78 said:
Sorry wrong link. Now updated. Please re-download. And yes the files need to pushed through adb.
Click to expand...
Click to collapse
if i have installed the previous version, is it right what i have to type in adb?
Code:
adb remount
adb push libcamera.so /system/lib/libcamera.so
adb push camera.qsd8k.so /system/lib/hw/camera.qsd8k.so
adb reboot bootloader
fastboot flash boot boot-new.img
fastboot reboot
please help, i don't know what to do..
thanks..
mulerokeh said:
if i have installed the previous version, is it right what i have to type in adb?
Code:
adb remount
adb push libcamera.so /system/lib/libcamera.so
adb push camera.qsd8k.so /system/lib/hw/camera.qsd8k.so
adb reboot bootloader
fastboot flash boot boot-new.img
fastboot reboot
please help, i don't know what to do..
thanks..
Click to expand...
Click to collapse
If you have previously working camera, you can skip flashing the boot-new.img file. It is there for people who do not have existing ics camera hal. Rest looks fine to me.
twistedumbrella said:
Is the code specific to qsd8 or just a generic wrapper function? On most "newer" devices you are looking at msm7x30, but generic qsd8 code, much like the gralloc, would still work with a rename.
Sent from my ADR6400L using Tapatalk
Click to expand...
Click to collapse
It is just a wrapper, but is dynamically linked with the libcamera.so file. So, if kernel change does not change structs and constants, things will work fine with a rename as you suggest. Otherwise it will not.
Maybe you should ask @charnsingh_online help for video, as he already works on 720p for N1
rapmv78 said:
It is just a wrapper, but is dynamically linked with the libcamera.so file. So, if kernel change does not change structs and constants, things will work fine with a rename as you suggest. Otherwise it will not.
Click to expand...
Click to collapse
So what were the kernel changes?
twistedumbrella said:
So what were the kernel changes?
Click to expand...
Click to collapse
There are none in this hal, that is why it works. What I was intending to say was that if MSMx30 kernel uses different size structs/constants it will not work.
rapmv78 said:
There are none in this hal, that is why it works. What I was intending to say was that if MSMx30 kernel uses different size structs/constants it will not work.
Click to expand...
Click to collapse
That is why I asked if it was generic code or specialized to qsd8. If the kernel code was not edited, that will be irrelevant because the source is not built (at least not by anyone other than CAF) using an inline kernel.
twistedumbrella said:
That is why I asked if it was generic code or specialized to qsd8. If the kernel code was not edited, that will be irrelevant because the source is not built (at least not by anyone other than CAF) using an inline kernel.
Click to expand...
Click to collapse
The hal code itself is generic, but it depends on libcamera.so, which inturn depends on kernel structs and constants to match the running kernel for successful control ioctls/pmem etc.
Can confirm this works on HTC Desire exactly as mentioned in OP.
Sent from my HTC Desire using XDA App
I tried it with (Texas)Ice ICS ROM and network not work. Failed to load driver! Need flash another kernel?
sucon said:
I tried it with (Texas)Ice ICS ROM and network not work. Failed to load driver! Need flash another kernel?
Click to expand...
Click to collapse
it works for me, but sometimes not responding after take 2 or 3 photos..
but great work!!
Sent from my Nexus One using xda premium
sucon said:
I tried it with (Texas)Ice ICS ROM and network not work. Failed to load driver! Need flash another kernel?
Click to expand...
Click to collapse
Works both fine with texasice ICS!
I decided to make my first custom rom. The main difference over klin1344's klassic is the fact that we can customize what we want with the aroma installer. As of now, there's no customised interface (and there will not be. Consider this like WT Ho's rom for the 5.0).
I stop working on it because I want to try something other than stock. Also thanks for your consideration for this rom. (I will continue the maintenance of it though)
Features:
- Stock 2.3.6 XXKPQ
- Rooted
- Busybox
- Deodexed
- Zipaligned
- Aroma installer: An interactive installer
- Multiple bootanimations.
- Choice between TW 3.0, TW 4.5, Go launcher EX, Xperia S launcher
- Possibility to install DSP manager and voodoo app (for sound enchance)
- Features the CWM 5.0.2.7 (Intl Only. Kernel based from steve's 3.0) (V.1.0)
- US users will recieve the latest klin's R2 custom kernel* (V.1.0).
- Intl and US compatibility in a single zip. (v.2.0)
- SuperSU (v.3.0)
Changelog:
Code:
[B]V.3.0 (Vita) FINAL [/B]
- Deodexed and Zipaligned
- SuperSU is used instead of SuperUser
- Updated Google Play Store, Maps and Youtube app (Can play 720p) (It's real this time)
- Possibility to add Antutu Cpu Master Free (For Overclock)
[B]V.2.0 (Radiance)[/B]
- Name changed only to Renaissance
- Possibility to chose the device type (Thanks to dark_valor's Terra Silent)
- New Honeycomb bootanimation
- Possibility to add terminal to the rom
[B]v.1.0 (Etincelle)[/B]:
- Initial Release.
Download:
1.0
Intl: Intl Renaissance 1.0 Download
US: US Renaissance 1.0 Download
2.0: Renaissance 2.0 Download
3.0: Renaissance 3.0 Download
If you want there's the Xperia S Wallpapers: Xperia S Wallpapers Download
If there's a problem with antutu, install the apk here: Cpu Master Apk Download
If there's a problem with terminal reinstall it.
Instructions:
1. Boot into Cwm
2. Backup
3. Wipe data (BEFORE IT IS MANDATORY)
4. Run renaissance-device.zip
5. Follow the instructions.
6. Reboot
7. Enjoy!
If you do like please hit thanks button. If you have problem with installation, Send me .log file in aroma. If it's problem with the rom please let me know.
Thanks to:
amarullz: for Aroma installer
Klin1344, SteveS and stratosk for the kernel related things.
WT Ho for his base for aroma installer. (and help too )
GO Dev Team , Fr4gg0r and ra3al for their launcher
Dark_balor for his kernel (terra silent)
Jackpal for the terminal emulator
Antutu for the CPU Master
As this is the last version, If you want to use something in the rom (porting) ask me first.(Mostly for Aroma)
These are the possible implementations (suggestions)
- Deodex
- Performance tweaks
- More customisation options
- Better compatibility with apps (Like deviceID hack)
reserved again
screenshots please?
EcHoFiiVe said:
screenshots please?
Click to expand...
Click to collapse
Oh sorry about that. I will put them tomowrrow. (that depends which screenshots you want?)
Is ext4 enabled for data and dbdata? From stock its stuck at rfs.
Wheatly said:
Is ext4 enabled for data and dbdata? From stock its stuck at rfs.
Click to expand...
Click to collapse
Well I didin't enable ext4 so data and dbdata will be stuck at rfs. Sorry about that.
Does the CWM 5 in the kernel I gave you work well? Because when I gave it to you there seemed to be a lot of errors... But if it does, I'll probably apply those changes back to my kernel again and update to cwm 5 because it allows easier converting to ext4. Also, did stratosk give you permission because I used his cwm recovery files from his sources. (just making sure, so he doesn't come and flame me for porting cwm5 from his sources without permission)
Sent using Tapatalk
When you sent it to me back then it wasn't working well. So I fixed the errors on it (I did send a PM for you for testing). I do got permission from stratosk (that's why I put him in the thanks section.) I think I have the US kernel in my mediafire account. I'll upload it so both devices will have justice.
zaclimon said:
When you sent it to me back then it wasn't working well. So I fixed the errors on it (I did send a PM for you for testing). I do got permission from stratosk (that's why I put him in the thanks section.) I think I have the US kernel in my mediafire account. I'll upload it so everyone will have justice.
Click to expand...
Click to collapse
Ok thanks. But how exactly did you fix it? I didn't flash the kernel you gave me but where are your sources? (the Linux kernel is GPL licensed, so it's mandatory to have a source )
Sent using Tapatalk
Never mind for now I will just extract the initrd from your kernel and use git to track the changes from the one I sent to you.
But really, you need to provide a source if you release a kernel, as per the GPL license.
Sent using Tapatalk
From which release of the Klin rom you based yours ?
If it's from the R5, did you had the font that were missing ?
Is it supercharged ?
For the kernel I'm also curious to know what are the change you have done
Dark_Balor said:
From which release of the Klin rom you based yours ?
If it's from the R5, did you had the font that were missing ?
Is it supercharged ?
For the kernel I'm also curious to know what are the change you have done
Click to expand...
Click to collapse
He based it off stock rom. Tomorrow I'll figure out how he fixed cwm 5.0.2.7 from his initramfs.
Sent using Tapatalk
klin1344 said:
Never mind for now I will just extract the initrd from your kernel and use git to track the changes from the one I sent to you.
But really, you need to provide a source if you release a kernel, as per the GPL license.
Sent using Tapatalk
Click to expand...
Click to collapse
I had the source before but my ubuntu 12.04 bugged with my old computer (nvidia problem) so I downloaded 11.04 but I forgot to do a backup.
zaclimon said:
I had the source before but my ubuntu 12.04 bugged with my old computer (nvidia problem) so I downloaded 11.04 but I forgot to do a backup.
Click to expand...
Click to collapse
If you can extract the initramfs then that's basically your source because cwm is only an initramfs change.
But again, how did you do it? Surely you remember what changes you did? It sounds like a minor tweak because you sent me your kernel a matter of hours after I sent you mine.
Btw, you know that you can downgrade ubuntu without losing data right? Ndiswrapper wasn't working on 12.04 so I put my 11.04 disc in and was able to install without losing all my personal files.
Sent using Tapatalk
klin1344 said:
If you can extract the initramfs then that's basically your source because cwm is only an initramfs change.
But again, how did you do it? Surely you remember what changes you did? It sounds like a minor tweak because you sent me your kernel a matter of hours after I sent you mine.
Btw, you know that you can downgrade ubuntu without losing data right? Ndiswrapper wasn't working on 12.04 so I put my 11.04 disc in and was able to install without losing all my personal files.
Sent using Tapatalk
Click to expand...
Click to collapse
I made some changes to the init.rc and lpm.rc I think.
Screenshots like Homescreen, App drawer, Notification place thingy, and settings.
EcHoFiiVe said:
Screenshots like Homescreen, App drawer, Notification place thingy, and settings.
Click to expand...
Click to collapse
Because it is a stock rom (with multiple apps) I won't put screenshots. Once 2.0 will be released (UI modifications) I will put them. You can backup and try it?
zaclimon said:
When you sent it to me back then it wasn't working well. So I fixed the errors on it (I did send a PM for you for testing). I do got permission from stratosk (that's why I put him in the thanks section.) I think I have the US kernel in my mediafire account. I'll upload it so both devices will have justice.
Click to expand...
Click to collapse
zaclimon said:
I made some changes to the init.rc and lpm.rc I think.
Click to expand...
Click to collapse
Ok, I just used git to check your initramfs for your INTL kernel, and lpm.rc is exactly the same as my source, and in init.rc it's also the exact same thing as my source for the CWM 5.0.2.7 beta (not on github anymore), except that you forgot a '/' in enabling bootanimation support.
So I'm confused. When I gave you my kernel, there seemed to be many errors because I was screwing with my partition filesystems, and also got a lot of "md5 mismatches" when trying to convert, so I decided to stop and work on other things. You got it working, and you claimed that you "fixed the errors in init.rc and lpm.rc" without proof with a proper source when you CHANGED NOTHING AT ALL. You probably just got lucky with CWM restoring and no md5 mismatches like I had. So you're releasing a kernel with a CWM 5 port that I completely did, and claiming that YOU fixed most of the errors and got it working when proof shows that all you did was download my source before I deleted it and simply compiled them with SteveS's one click compiling script.
And since you don't have a Github account or a source of any sort, you thought you could get away with tricking everybody that you "fixed the CWM errors", when the work was originally done by me. You changed nothing at all. It was not my intention to flame you, but seriously, I am disapointed . I'm really discouraged and very tempted to just take down all my work for the Galaxy Player and just keep all the development to myself. Maybe that's why precious devs keep leaving XDA because people just use someone else's work and package it as their own. Learn to give proper credit to other people, and if you really didn't make something, don't act or say that you did.
Ok, I'm done. Really needed to vent.
klin1344 said:
Ok, I just used git to check your initramfs for your INTL kernel, and lpm.rc is exactly the same as my source, and in init.rc it's also the exact same thing as my source for the CWM 5.0.2.7 beta (not on github anymore), except that you forgot a '/' in enabling bootanimation support.
So I'm confused. When I gave you my kernel, there seemed to be many errors because I was screwing with my partition filesystems, and also got a lot of "md5 mismatches" when trying to convert, so I decided to stop and work on other things. You got it working, and you claimed that you "fixed the errors in init.rc and lpm.rc" without proof with a proper source when you CHANGED NOTHING AT ALL. You probably just got lucky with CWM restoring and no md5 mismatches like I had. So you're releasing a kernel with a CWM 5 port that I completely did, and claiming that YOU fixed most of the errors and got it working when proof shows that all you did was download my source before I deleted it and simply compiled them with SteveS's one click compiling script.
And since you don't have a Github account or a source of any sort, you thought you could get away with tricking everybody that you "fixed the CWM errors", when the work was originally done by me. You changed nothing at all. It was not my intention to flame you, but seriously, I am disapointed . Maybe that's why precious devs keep leaving XDA because people just use someone else's work and package it as their own. Learn to give proper credit to other people, and if you really didn't make something, don't act or say that you did.
Ok, I'm done. Really needed to vent.
Click to expand...
Click to collapse
ok don't go blaming me BECAUSE IT GOT ERRORS when YOU sent it to me. I corrected some errors but I can't remember which ones is it. I can't get lucky if EVERY of my backups works(Because I got errors for md5 mismatch as well too). It is sure that your init files are the same because I used some of the text you used when you were building YOUR R1 kernel. (so basically I used some of your sources) but you were always complaining about ext4 not working so you gave up on CWMR5.0. and when I said I've fixed them you didin't tested it. DON'T GO COMPLAINING IF YOU DIDIN'T EVEN TESTED IT. (also check all the init files to be sure and also check the thanks it is `kernel related things`.) -___-
EDIT: If you want all the credits. You can have them. I should have said that you made all the changes but the problem was that you gave up on CWMR5.0 so I was like (The kernel works now but I won't release it because you already have your custom kernel with CWMR3.)
Hey guys, we have here a kernel built from the kernel source HTC released on 8/29/12 for Vigor. This kernel is a modified version of what came in the Official 3.14.605.12 ICS OTA except it is built from HTC's kernel source release. What else can I say?
Bugs:
-?
Current features:
Perflock Disabled
Fast charge enabled using any power source - Thanks to Chad, I used his commits as a reference
Download:
Link Removed
Download Global OTA Compatible Version (Thanks to MicroMod for making it happen
Link Removed
Install:
Place zip on sd
Reboot to recovery (I use amon)
Install from zip
Select the zip file
The file will flash and then the phone will reboot to hboot
Once there, simple press power to select bootloader
Accept the update
It will install
Reboot your phone
????
Enjoy
Don't forget to go delete the PH98IMG.zip from your SD Card after boot.
Disclaimers:
I won't be responsible for what you flash on your phone or any damge that could be caused. Always use caution when modifying any part of your device.
Credits:
Thank con247 for the auto kernel flasher.
Thanks Chad for all your awesome kernel knowledge.
My Github for this kernel:
Link Removed
/// Info for new devs \\\
How to disable perflock in an HTC kernel through source
Simple, open you source. Open the arch/arm/configs. Find the file vigor_defcofig. Find the following lines:
Code:
CONFIG_PERFLOCK=y
CONFIG_PERFLOCK_BOOT_LOCK=y
Change them to:
Code:
# CONFIG_PERFLOCK is not set
# CONFIG_PERFLOCK_BOOT_LOCK is not set
Perflock is now disabled. Build your source
Changing the kernel name
Open the scripts folder in the root of your source. Find and open the file makecompile_h. Find the lines:
Code:
echo \#define LINUX_COMPILE_BY \"`echo $LINUX_COMPILE_BY | $UTS_TRUNCATE`\"
echo \#define LINUX_COMPILE_HOST \"`echo $LINUX_COMPILE_HOST | $UTS_TRUNCATE`\"
Edit how you want:
Code:
echo \#define LINUX_COMPILE_BY \"`echo wildstang83`\"
echo \#define LINUX_COMPILE_HOST \"`echo vigor-ics`\"
Enjoy
Is this a sense kernel? I know...but noobs should have heads up.
Sent from my HTC Rezound using xda premium
I'm going to keep count of the flood of kernels that are sure to come.
This is #1
Anyway will download tomorrow, way too tired right now
Sent from my Nexus 7 using Tapatalk 2
What makes this different from the stock ones?
apophis9283 said:
What makes this different from the stock ones?
Click to expand...
Click to collapse
As far as I know, absolutely nothing. I could be wrong though. Some of you that remember the Incredible or Thunderbolt will remember how the kernel that was in the ota for those devices and the kernel source released after the ota were different. HTC had added in minor fixes to the kernel source release that was not in the ota. I don't know if that is the case here, just a thought though.
It's not different. Lmao read the title. Looking forward to see what come from this, stang
Sent from my ADR6425LVW using Tapatalk 2
antp121 said:
It's not different. Lmao read the title. Looking forward to see what come from this, stang
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Exactly, we can assume this kernel is no different from the one in the OTA. Unless of course someone else can prove otherwise.
wildstang83 said:
As far as I know, absolutely nothing. I could be wrong though. Some of you that remember the Incredible or Thunderbolt will remember how the kernel that was in the ota for those devices and the kernel source released after the ota were different. HTC had added in minor fixes to the kernel source release that was not in the ota. I don't know if that is the case here, just a thought though.
Click to expand...
Click to collapse
Is that Kernel still perflocked?
Not totally familiar with what could be different between stock and custom built stock from source.
Quantumrabbit said:
Is that Kernel still perflocked?
Not totally familiar with what could be different between stock and custom built stock from source.
Click to expand...
Click to collapse
If built as is from source, I'd say yes. Give the devs some times, you'll see them come out with perflock removed.
mjones73 said:
If built as is from source, I'd say yes. Give the devs some times, you'll see them come out with perflock removed.
Click to expand...
Click to collapse
Right, this kernel was not intended to be custom in anyway whatsoever. It is simply a kernel built from source. I know I like stock things, I'm sure others do as well.
i honestly love you wild stang. and neo and mbobino.
Nice work stang
Sent from my ADR6425LVW
I got a stock build with PERFLOCK disabled building right now. I'll upload that to the OP in just a minute.
I love you
Sent from my Nexus 7 using Tapatalk 2
Perflock disabled version added to OP.
Will this work with sense 4 roms?
i guess with perflock disabled, we could underclock? or at least change the governors and stuff using cpu controller apps?
apophis9283 said:
Will this work with sense 4 roms?
Click to expand...
Click to collapse
in theory, yes. would i attempt it? not quite yet.
antp121 said:
in theory, yes. would i attempt it? not quite yet.
Click to expand...
Click to collapse
Should be fairly simple to insure a Sense 4 version. Just grab a sense 4 boot.img like newtoroots or whatever, open it up in android kitchen and drop in the zimage from my kernel's zip. Repackage the boot.img and fastboot flash it. ant, you should try it
wildstang83 said:
Should be fairly simple to insure a Sense 4 version. Just grab a sense 4 boot.img like newtoroots or whatever, open it up in android kitchen and drop in the zimage from my kernel's zip. Repackage the boot.img and fastboot flash it. ant, you should try it
Click to expand...
Click to collapse
sounds a little bit difficult for an end user just like me with no idea about dev things
Sent from my ADR6425LVW using xda premium
Any devs working on a stock Read and Write kernel? so we can finally get rid of all the ATT bloat without it coming back? Or are we just waiting for kernel source?
Fidelio_o said:
Any devs working on a stock Read and Write kernel? so we can finally get rid of all the ATT bloat without it coming back? Or are we just waiting for kernel source?
Click to expand...
Click to collapse
It's available, somebody just needs to use a hex editor to make the module load with whatever kernel version AT&T uses.
http://forum.xda-developers.com/showthread.php?t=2230341
flar2 said:
It's available, somebody just needs to use a hex editor to make the module load with whatever kernel version AT&T uses.
http://forum.xda-developers.com/showthread.php?t=2230341
Click to expand...
Click to collapse
Was there only the one string for the kernel version towards the top? If so - here it is for kernel 3.4.10-g3de55a2
Note: not a flashable zip... the module is inside, just couldn't attach it as a .ko
homeslice976 said:
Was there only the one string for the kernel version towards the top? If so - here it is for kernel 3.4.10-g3de55a2
Note: not a flashable zip... the module is inside, just couldn't attach it as a .ko
Click to expand...
Click to collapse
Not sure what am supposed to do with the module
Sent from my HTC One using xda premium
I flashed Android Revolution 7.0 and none of the apps I delete or any of the bloat he deleted came back.
Sent from my HTC One using XDA Premium HD app
Ramdisk Hijack - what is it?
- We are trying to load a custom ramdisk in order to be able to load a non-Sony based ROM on a locked bootloader using 2nd-init. This is a work in progress.
How can I help?
- My source code is here: https://github.com/keiranFTW/huashan_ramdisk-hijack also, you will find how to install this on there too.
You'll probably wonder why I'm trying to hack the stock ramdisk in - because my phone is my only device, I also need to use it as a phone. Once I can fix things this way I can move to using CyanogenMod Ramdisk.
Progress? CyanogenMod is currently booting on the phone but there are lots of non-working features.
This is not a ROM, do not install this unless you know what you are doing.
On completion I will give you this in form of an update.zip
#keiran
Any developers willing to help me out here?
I am busy with personal work, will check this out later... FYI you can't boot everything on same kernel... Specific kernel patches are required for some ROMs... Without those patches crucial rom features may not work...
Sent from my C6902 using xda app-developers app
DooMLoRD said:
I am busy with personal work, will check this out later... FYI you can't boot everything on same kernel... Specific kernel patches are required for some ROMs... Without those patches crucial rom features may not work...
Sent from my C6902 using xda app-developers app
Click to expand...
Click to collapse
I know this, and some of these kernel patches can be loaded as a module or even the ROM source code edited to suit the needs of the stock kernel.
Edit: I have had many people asking me if kexec could work, and the answer is no, probably not. Why? Because it requires a in-kernel patch as well as a module and so it is not possible to get it to work as we cannot flash a new kernel.
I have an idea and I'll start to merge changes soon
Sent from my C5303 using Tapatalk
I am not experienced in kernel dev but maybe i can contribute in limited extent.
Unluckily, i also got "NO" in bootloader unlockable and very dissappointed to see that.
I hope someone will be able to find an alternative.
Have you looked at this?
http://www.xda-developers.com/android/locked-bootloader-xperia-s-and-want-cm10-no-problem/
Work in peace...
OP
can you link me to some good references about chroot? I got the basic understanding, want to try it on linux on my laptop.
Closest analogy i can draw is the linux live cd, which runs the OS live without installation. If thats the case, and if we succeed in this process, we could use some partition to dump cm and run it from there.
But lets not get too far, im still in infancy stage.
Regards
Yasir
finally Got the basics of what you are doing... You are essentially doing the same thing letama atis112 and company did to run cm10 usng stock kernel, but hijacked stock ramdisk to run cm ramdisk.... Seems a good idea but will only work for CM10 (4.1 based) and later when locked bootloader gets 4.3, we could get cm10.2 as well. If you are doing the same thing they did, then hopefully it will work soon. If its something different, then wish u luck, ill keep tracking ur progress.
Yes, he is trying to have it done the same way as letama, atis and others with one minor difference - we don't have pre_hwconfig.sh, so he's trying with chargemon. Older ramdisk Keiran's github worked fine, but after some commits he made it doesn't boot. When I try with older ramdisk and newest step2.sh, everything except sdcard works fine. I have an idea - what if we kill every process with every possible way(killall5, pkill,etc) and then start it manually, by calling them from /system/bin? Maybe it's the way.
Some offtop here:
Maybe the kernel from leak works on locked BL's? If DooM haven't changed anything in it - it's very possible. Maybe someone with 4.3 leak on their phone would try locking the bootloader?(Of course only if that person knows how to unbrick, if something goes wrong).
MrSteve555 said:
Yes, he is trying to have it done the same way as letama, atis and others with one minor difference - we don't have pre_hwconfig.sh, so he's trying with chargemon. Older ramdisk Keiran's github worked fine, but after some commits he made it doesn't boot. When I try with older ramdisk and newest step2.sh, everything except sdcard works fine. I have an idea - what if we kill every process with every possible way(killall5, pkill,etc) and then start it manually, by calling them from /system/bin? Maybe it's the way.
Some offtop here:
Maybe the kernel from leak works on locked BL's? If DooM haven't changed anything in it - it's very possible. Maybe someone with 4.3 leak on their phone would try locking the bootloader?(Of course only if that person knows how to unbrick, if something goes wrong).
Click to expand...
Click to collapse
I assume you have the same issue of unlockable BL? anyways, i am waiting for 4.3 so that after playing with, we can try and run cm10.2 at least... + miui
I've redone your work, and i can succesfully hijack ramdisk...
I've CM booted up, but:
1. graphical glithes (i know the solution)
2. no baseband
3. no sdcard (inner, external)
But it's improvement
Source: https://github.com/dh-harald/hijack-ramdisk-huashan
dh.harald said:
I've redone your work, and i can succesfully hijack ramdisk...
I've CM booted up, but:
1. graphical glithes (i know the solution)
2. no baseband
3. no sdcard (inner, external)
But it's improvement
Source: https://github.com/dh-harald/hijack-ramdisk-huashan
Click to expand...
Click to collapse
If my girlfriend would let me and I was near you I would kiss you right now :*
Jokes aside, I think I might be able to fix SD card and the rest
Sent from my C5303 using Tapatalk
I dont think any processes with late_start class are working... This would explain SD and also network.
Try:
/system/bin/sdcard /data/media /mnt/shell/emulated 1023 1023
/system/bin/qseecomd
/system/bin/secchand
Anything really..
When I was hijacking ramdisk before but loading the stock ramdisk just for testing I also lost network as well as sdcard, and I'm sure that I lost WiFi too. A possible solution would be *not* to stop these services maybe?
Sent from my C5303 using Tapatalk
New source code is at: https://github.com/keiranFTW/huashan_ramdisk-hijack
- Updated to work with Android 4.3
- Using 2nd-init instead of chroot
- Recovery included (not sure if working)
#keiran
hijack
Hy
I modified the hijack source and recompiled the cm10.2 was.
hijack
dev tree
vendor blobs
I made a new thread on xda.
bagyusz said:
Hy
I modified the hijack source and recompiled the cm10.2 was.
hijack
dev tree
vendor blobs
I made a new thread on xda.
Click to expand...
Click to collapse
Hey,
Thanks, your changes have helped a lot, so I have expanded on them to make it possible to integrate into AOSP more easily. I also use /system/bin/chargemon instead of system/bin/wipedata, it is earlier in boot process.
I also might want to note that you are not killing all processes, you need awk {'print $2'} instead of awk {'print $2'}
But yeah, great work.. you did what many others couldnt.
My repositories:
dev tree
vendor blobs
hijack
Feel free to add pull requests, and i can add you to the repository if you like.
Keiran
If only this could be done in other devices, as I also have a locked Xperia, but it's a Live Walkman. Unfortunately it also has the Unlock Bootloader: "NO", so if could also be ported to other devices it would be great. Not forcing or pushing you, but trying something more updated than 4.0.4 would be great
is this...?
@KeiranFTW & @bagyusz
sick work guys way to not never give up and accomplish what was thought to not be possible goes without saying one of the best development breakthroughs this year!
hey, in either of your opinions would this in some way be portable to our locked as **** bls on S4 Verizon and AT&T? We havent had ASOP capabilities or 4.4 for that matter yet and everyone is stuck on safestrap 4.3 stock kernels. Any help on this would be much appreciated. Its either trying to port this method or trying that new AnyKernel2.0 today not trying to hard brick heh
msm7x27
KeiranFTW said:
.
Click to expand...
Click to collapse
would this method work on any msm7x27 after pointing partitions ?? @KeiranFTW
deleted.
I still don't know what you're talking about. eace
Sent from my C5303 using Tapatalk
concerning hijack
KeiranFTW,
i am sorry to bother you with what may or may not be a 4 square dev question(s).
can i attempt something similar without building custom kernel? ( i read evrything i can but, lack funds for proper hardware so am limited.)
can i alter the insmod-ing of kernel modules to come as close to the beginning of the boot process as possible and have hardware functional in spite of slaying zygote/android userspace ?
this thread http://forum.xda-developers.com/showthread.php?t=1937328 outlines a means to
mount?load? a loop device from init.rc
my thought is as i have a gt-p5210 x86 device it might be possible to fire up (no matter how ugly)
a livecd or straight forward ext4 linux.img.
I would be interested in any insight/ideas you may have toward that end.
thank you for your time.
m