Ok. i have compiled own kernel, but it didnt boot, just stuck on samsung logo.
then i have downloaded rumirand kernel r14 source, from rumirand, compiled succesful, but the same, didnt boot, stuck on samsung logo.
Anyone have a ideas?
Im using:
System: Ubuntu 10.04 on virtual box machine, which one is on windows 8
Compiler: ARM-2009q3
.config file: from SGP5.0's config.gz
flashing: Via CWM, using rumirand r14.zip with replaced Zimage and signed with apk-tool
Arlicc said:
Ok. i have compiled own kernel, but it didnt boot, just stuck on samsung logo.
then i have downloaded rumirand kernel r14 source, from rumirand, compiled succesful, but the same, didnt boot, stuck on samsung logo.
Anyone have a ideas?
Im using:
System: Ubuntu 10.04 on virtual box machine, which one is on windows 8
Compiler: ARM-2009q3
.config file: from SGP5.0's config.gz
flashing: Via CWM, using rumirand r14.zip with replaced Zimage and signed with apk-tool
Click to expand...
Click to collapse
Did you add the initramfs (initrd) in the kernel?
zaclimon said:
Did you add the initramfs (initrd) in the kernel?
Click to expand...
Click to collapse
yea, those from rumirad source.
Arlicc said:
yea, those from rumirad source.
Click to expand...
Click to collapse
and you specify them in your defconfig?
zaclimon said:
and you specify them in your defconfig?
Click to expand...
Click to collapse
in .config, not defconfig, but i think its the same, without define them in .confing, i wasnt able to compile kernel.
Arlicc said:
in .config, not defconfig, but i think its the same, without define them in .confing, i wasnt able to compile kernel.
Click to expand...
Click to collapse
Oh ok I see what you did. You pulled the config.gz (it can work but I prefer using the defconfig) from the device itself. Try doing this. In your arch/arm/config folder modify the rj_eur_defconfig for your initramfs path then follow his instructions here:
https://github.com/rumirand/GalaxyPlayer5-kernel/blob/master/README
Then compile and try to flash again.
zaclimon said:
Oh ok I see what you did. You pulled the config.gz (it can work but I prefer using the defconfig) from the device itself. Try doing this. In your arch/arm/config folder modify the rj_eur_defconfig for your initramfs path then follow his instructions here:
https://github.com/rumirand/GalaxyPlayer5-kernel/blob/master/README
Then compile and try to flash again.
Click to expand...
Click to collapse
difference beetwen those two files is:
Code:
from config.gz:
CONFIG_BT_BNEP=y
CONFIG_BT_BNEP_MC_FILTER=y
CONFIG_BT_BNEP_PROTO_FILTER=y
Code:
from rumarid:
CONFIG_BT_BNEP is not set
BNEP is enabled on .config from SGP5.0's config.gz with r14 rumarid's kernel
BNEP isnt enabled on rumarid rj_eur_defconf, from his source.
bluetooth BNEP can make bootloop ?, its just define, and he has enabled it in r14 by "menuconfig"
I didnt get bootable kernel yet, what im doing wrong
Sent from my GT-I9000 using XDA
Related
CLOCKWORKMOD-RECOVERY FOR GALAXY S II (AT&T)
Click to expand...
Click to collapse
for use with Stock ROMs​
I'll update it every time something important has changed, like CWM changes or kernel updates from samsung.
It's built from samsung kernel sources + teamhacksung initramfs template.
Instructions
Power your device off
Boot into Download-Mode using Volume Up + Volume Down + Power
Hit Volume Up to accept the warning
Start Odin
Choose "SGH-I777_ClockworkMod-Recovery_X.X.X.X.tar" as PDA (no repartition)
Connect your Phone
Start flashing
After reboot you can easily root your device using SuperOneClick
Usage
Volume Up + Power brings your Phone into Recovery Mode.
VolUp + VolDn = Highlight Up/Dn
Power = toggles menus off/on
Home = Select
Back = Back
Download
Testing - 5.0.2.3: http://www.multiupload.com/QQKN7NJAFT (md5: 4fb905992461586966ee1a7991206e93)
Don't forget to thank koush for his awesome work on ClockworkMod / ROMManager.
INITRAMFS TEMPLATE FOR DEVELOPERS
Click to expand...
Click to collapse
Here's a initramfs template you can use as a base for your haxx0ry:
https://github.com/teamhacksung/clockworkmod_galaxys2att_initramfs
It's KG1 initramfs + ClockworkMod Recovery and necessary modifications to make it work.
Instructions
git clone https://github.com/teamhacksung/clockworkmod_galaxys2att_initramfs gingerbread
remove hidden directorys from your cloned repo like .git
use it as your initramfs source
To make sure to include fresh modules (vermagic) use a buildscript like this:
build.sh (inside your kernel dir)
Code:
#!/bin/bash
INITRAMFSDIR=/home/user/android/samsung/galaxys2att_initramfs
TOOLCHAIN=/home/user/android/cyanogenmod/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin/arm-eabi-
make c1_rev02_usa_att_defconfig
make -j8 CROSS_COMPILE=$TOOLCHAIN CONFIG_INITRAMFS_SOURCE="$INITRAMFSDIR"
cp drivers/bluetooth/bthid/bthid.ko $INITRAMFSDIR/lib/modules/
cp drivers/net/wireless/bcm4330/dhd.ko $INITRAMFSDIR/lib/modules/
cp drivers/samsung/j4fs/j4fs.ko $INITRAMFSDIR/lib/modules/
cp drivers/scsi/scsi_wait_scan.ko $INITRAMFSDIR/lib/modules/
cp drivers/samsung/vibetonz/vibrator.ko $INITRAMFSDIR/lib/modules/
make -j8 CROSS_COMPILE=$TOOLCHAIN CONFIG_INITRAMFS_SOURCE="$INITRAMFSDIR"
Example updater-script: http://pastebin.com/RXqiVTMv
Kernel Sources: http://opensource.samsung.com
greets
codeworkx
It is vol up+down and power to get into recover
Can't wait till I get one today! Great work!
Sent from my SGH-I897 using XDA App
Also running root now too ty!
jivy26 said:
Also running root now too ty!
Click to expand...
Click to collapse
Are the buttons working like described?
Yes they are working fine no issues. Root with superoneclick was fairly straight forward as well.
jivy26 said:
Yes they are working fine no issues. Root with superoneclick was fairly straight forward as well.
Click to expand...
Click to collapse
I wish it was that easy for me. Coming from the iPhone jailbreaking scene, this stuff is like jibberish. They need a "rooting the gsII for dummies."
brock.higdon said:
I wish it was that easy for me. Coming from the iPhone jailbreaking scene, this stuff is like jibberish. They need a "rooting the gsII for dummies."
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1285894
brock.higdon said:
I wish it was that easy for me. Coming from the iPhone jailbreaking scene, this stuff is like jibberish. They need a "rooting the gsII for dummies."
Click to expand...
Click to collapse
jivy26 said:
http://forum.xda-developers.com/showthread.php?t=1285894
Click to expand...
Click to collapse
:doh:
I leave the general forum for 5 minutes. Haha
Can someone who has flashed this and NOT flashed anything else get a system dump for us?
CodeworkX check pm dropbox link is in there
Sent from my SAMSUNG-SGH-I777 using xda premium
jivy26 said:
CodeworkX check pm dropbox link is in there
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
Thank you very much.
edit: nvm, someone else did it
brock.higdon said:
Explain a little further because I am not real bright but I may can help. I followed the "easy root" instructions in the general forum. Have not done anything else since.
Click to expand...
Click to collapse
He is trying to help Devs. All he needs to do is boot into CWM goto backup and backup. After its complete boot into phone then upload system img to dropbox and pm codeworkx(if they need more sources).
With Working CWM Recovery we can flash root
Download Here
drop the file on your SD card and "choose 'su-3.0-efgh-signed.zip' file to flash" from CWM recovery (flash file from sd - choose zip - YES- reboot system)
IRC = #sgs2-att on irc.freenode.net
Looks like you guys will have a rooted system image before I can even get to the store!
Could you PM me a link to the system dump so I can start looking at it?
Entropy512 said:
Looks like you guys will have a rooted system image before I can even get to the store!
Could you PM me a link to the system dump so I can start looking at it?
Click to expand...
Click to collapse
Sent
Sent from my SAMSUNG-SGH-I777 using xda premium
jivy26 said:
Sent
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
Thanks. I have, in theory, a stock rooted Heimdall-flashable image now.
Less than an hour until my AT&T store opens - hopefully they give me some sort of FAN discount.
BTW, one small question (already PMed you this) - what is the partition size of /system?
Entropy512 said:
Thanks. I have, in theory, a stock rooted Heimdall-flashable image now.
Less than an hour until my AT&T store opens - hopefully they give me some sort of FAN discount.
BTW, one small question (already PMed you this) - what is the partition size of /system?
Click to expand...
Click to collapse
Should be:
BOARD_SYSTEMIMAGE_PARTITION_SIZE := 536870912
codeworkx said:
Should be:
BOARD_SYSTEMIMAGE_PARTITION_SIZE := 536870912
Click to expand...
Click to collapse
512M right on the dot.
This means that in theory, Fenny and I have flashable stock and stock rooted images now. We'll know in a few hours. My AT&T store doesn't open for 45 more minutes and I'm not sure what discounts I may have available. If I get the right deal, I'll flash from my laptop, dump kernel, and upload the kernel from Panera.
I searched and saw a somewhat similar problem but their phone booted, mine does not, but i can get it into cwm but even after trying a nandroid backup and flashing a different ROM it still doesn't boot, it just loops back to the logo..
Is there anything I can do?
Any help appreciated..
Thanks!
justinblaine23 said:
I searched and saw a somewhat similar problem but their phone booted, mine does not, but i can get it into cwm but even after trying a nandroid backup and flashing a different ROM it still doesn't boot, it just loops back to the logo..
Is there anything I can do?
Any help appreciated..
Thanks!
Click to expand...
Click to collapse
Somehow you corrupted param.lfs. It can be downloaded separately and flashed with heimdall in my return-to-stock thread.
I downloaded the file on your post and extracted with 7zip but i have windows 7 but i also have ubuntu on here, your instructions are for using linux and heimdall, will that work on ubuntu?
http://forum.xda-developers.com/showthread.php?t=1286432
That's the thread I'm referencing
Thanks Entropy, you're awesome
EDIT: Ok nevermind I didn't realize i could use on windows
Thanks Entropy, I flashed it using ODIN which is linked in your thread, you're a lifesaver!
justinblaine23 said:
I downloaded the file on your post and extracted with 7zip but i have windows 7 but i also have ubuntu on here, your instructions are for using linux and heimdall, will that work on ubuntu?
http://forum.xda-developers.com/showthread.php?t=1286432
That's the thread I'm referencing
Thanks Entropy, you're awesome
EDIT: Ok nevermind I didn't realize i could use on windows
Click to expand...
Click to collapse
Ubuntu = Linux
(FYI I do all of my development on an Ubuntu machine)
Yea i know it's linux but wasn't sure if it had to be a specific build of linux since there's many out there, but I got it all fixed, thanks again!
If I didn't need MS office for school I'd never even Run Win 7, Linux is awesome!
justinblaine23 said:
Thanks Entropy, I flashed it using ODIN which is linked in your thread, you're a lifesaver!
Click to expand...
Click to collapse
didn't work
nikhilppatel said:
didn't work
Click to expand...
Click to collapse
If you're looking for help, you'll need to post details about your issue.
I have this issue also, I downloaded the param.lfs file and I was wondering where do I put it in ODIN? Thanks.
Edit: Followed the links until I got to the right tar package to use with ODIN, Thanks to this thread I got headed in the right direction.
i 've got an amaze 4g t-mobile recently.it works perfectly.but then,i updated to ICS through OTA...
Everything work fine except Wifi,i cant turn on wifi at all.It only show error when i try to turning on ...
I did search the whole forums,trying everthing i can do..unlock boot loader/rooted/s-off/flash 4EXT recovery/flash many cook rom (android revolution,fastrom,energy rom..),kernel(ruby-faux123 v007/v008/v015/v016..)
finally i reverted back to Stock GB with "PH85IMG_Ruby_TMOUS_1.43.531.3_Radio_1.08.550L.19DC_30.66.550L.08D_release_228638_signed".
but wifi still shows ''error'' at all,when i try to turning on hotspot ,the phone force to reset .
currently:
Stock GB:2.3.4
Sense:3.0
Kernel:2.3.35.13 build 144#1
Baseband:1.08.550L.19DC_30.66.550L.08D
Buildnumber:1.43.531.3
Bootloader unlocked and s-off.
Hoping there is anyone else can understand my bad english and help me .
Since you're s-off try updating back to ics via the most recent file in the stock ruu thread and see if it resolves it.
sent from a smooth place where my fingers trace across the screen to see your face and make you scream!
thanks sir
i try to flashing this kernel into my stock GB:Amaze-EKF-009b-sense.zip
hope it works
ronaldinho_07 said:
thanks sir
i try to flashing this kernel into my stock GB:Amaze-EKF-009b-sense.zip
hope it works
Click to expand...
Click to collapse
Kernel won't change much, but the wifi drivers being present in the kernel just might help, let me know your results.
Dark Nightmare said:
Kernel won't change much, but the wifi drivers being present in the kernel just might help, let me know your results.
Click to expand...
Click to collapse
as you have said,i just flashed the above kernel (Amaze-EKF-009b-sense.zip) into stock GB,but wifi error is still there
after that,i updated to ICS via RUU and flashed this kernel from here : http://forum.xda-developers.com/showthread.php?t=1362759 (at #5)
Nothing changes.
at the first time,i have flashed the Amaze ICS(v015) kernel via 4EXT touch recovery,flashed kernel successfully .
(http://forum.xda-developers.com/showthread.php?t=1359951)
but i think i go wrong somewhere,because the following instruction said:
CWM Flash Instructions: (NO LONGER SUPPORTING CWM METHOD DUE TO HTC's STUPID S-ON UNLOCK!!!)
1. Copy file to SDcard
2. Reboot to CWM recovery
3. Flash the Zip file (if you noticed an error, Flash the same file the 2nd time)
4. Reboot, Done!
i read carefully the second way
Easy Kernel Flasher Instructions:
1. download the above file (via phone directly or to a PC)
2. unzip to a folder then depends on PC or Linux
[ Windows ] open command prompt window and type Flash.bat
[ Linux ] open terminal window and type ./Flash.sh (make sure permission is set to 755 for the Flash.sh)
3. Let the script complete!
,downloaded the kernel,extracted into a folder on my pc.
but i dont see any "Flash.bat'' and dont know how to flash it.
but in the folder that i've just extracted.i found two file:
wl12xx.ko and wl12xx_sdio.ko
putting the whole folder modules into the this kernel (http://forum.xda-developers.com/showthread.php?t=1362759) and run flash.bat...
after flashing,both wifi and bluetooth broken
when i try to turning them on,they turn off instantly
//sorry sir for the bad english
Try to run my AIO tool, which can be found here: http://forum.xda-developers.com/showthread.php?t=1762936
If that doesn't work, more likely than not, it's a hardware issue, as my AIO tool will install a MOSTLY stock RUU with a stock kernel. If that doesn't work, I strongly doubt anything else would work either.
Make sure you follow the directions for the tool.
Keylogger_0 said:
Try to run my AIO tool, which can be found here: http://forum.xda-developers.com/showthread.php?t=1762936
If that doesn't work, more likely than not, it's a hardware issue, as my AIO tool will install a MOSTLY stock RUU with a stock kernel. If that doesn't work, I strongly doubt anything else would work either.
Make sure you follow the directions for the tool.
Click to expand...
Click to collapse
thanks sir,i'll try
btw,i try to flashing faux123-kernel via CWM recovery,but i's aborted
then,i force to flash faux123-kernel via 4EXT touch recovery and succeed
but i still cant turn on wifi,it just says error
can anyone give me an advise,pls
That memory block is probably damaged.
sent from a galaxy you'll never see.
do you think it's related to wifi hardware issues
ronaldinho_07 said:
do you think it's related to wifi hardware issues
Click to expand...
Click to collapse
It could be that as well, did you call tmo and tell em about it?
Dark Nightmare said:
It could be that as well, did you call tmo and tell em about it?
Click to expand...
Click to collapse
i cant do that because i live in vietnam sir
btw,when i was in a custom rom with fraux's kernel.it would just stay in dim grey and say "turning wifi on" and freeze there for a while,then saying "Error''
but,when i tried to copying "wlan12xx.ko,wlan12xx_sdio.ko" from Fraux kernel to Amaze stock kernel modules folder.Flashed it.
then,i turned it on and the wifi turned off itself instantly without saying error
there was wifi error same here :
http://forum.xda-developers.com/showthread.php?t=1796358
thanks for your helps sir :good:
ronaldinho_07 said:
i cant do that because i live in vietnam sir
btw,when i was in a custom rom with fraux's kernel.it would just stay in dim grey and say "turning wifi on" and freeze there for a while,then saying "Error''
but,when i tried to copying "wlan12xx.ko,wlan12xx_sdio.ko" from Fraux kernel to Amaze stock kernel modules folder.Flashed it.
then,i turned it on and the wifi turned off itself instantly without saying error
there was wifi error same here :
http://forum.xda-developers.com/showthread.php?t=1796358
thanks for your helps sir :good:
Click to expand...
Click to collapse
Did you try the fix permissions someone mentioned?
sent from a galaxy you'll never see.
Dark Nightmare said:
Did you try the fix permissions someone mentioned?
sent from a galaxy you'll never see.
Click to expand...
Click to collapse
yes.i did sir
now,i try to reverting to stock GB 2.3.4 again
i've call to a store near my house,they said that if amaze's wifi chip were as same as hd2's wifi chip,the cost would be about $35
ronaldinho_07 said:
yes.i did sir
now,i try to reverting to stock GB 2.3.4 again
i've call to a store near my house,they said that if amaze's wifi chip were as same as hd2's wifi chip,the cost would be about $35
Click to expand...
Click to collapse
Hmmm...doubt it's the same but ill Google the hardware to see if it's replaceable.
sent from a galaxy you'll never see.
Dark Nightmare said:
Did you try the fix permissions someone mentioned?
sent from a galaxy you'll never see.
Click to expand...
Click to collapse
Dark Nightmare said:
Hmmm...doubt it's the same but ill Google the hardware to see if it's replaceable.
sent from a galaxy you'll never see.
Click to expand...
Click to collapse
thanks so much
nice day sir,and i have to go to bed ,it's 3h40 AM in vietnam
//updated.
after flashing many times,problem solved
Necro'd.
Dark Nightmare said:
Hmmm...doubt it's the same but ill Google the hardware to see if it's replaceable.
Click to expand...
Click to collapse
Anyone have any info as to how or where to repair the wifi chip on the amaze? I'm having the same problem and am quite certain that is it hardware issue as the problem started after dropping the phone and without flashing or changing anything, fixing permissions and flashing stock RUU's, kernels, etc of no help. Hoping that something is possible, would be great if it was as simple as a loose ribbon cable...
Dark Nightmare said:
Did you try the fix permissions someone mentioned?
sent from a galaxy you'll never see.
Click to expand...
Click to collapse
Hello,
Here is my situation. I got S-off, SuperCID, unlocked on my HTC amaze unbranded version. Then got ICS stock RUU to run.
The wifi, bluetooth worked fine. However, I have to compile the kernel for this exact version (matched radio, baseband kernel, etc). I downloaded the source from HTCdev (the one with TI WLAN sources), and compiled it. Then I got the zImage repacked so that it can run on the device. Then I see that the wifi, bluetooth shows "error".
The kernel build "readme.txt" located me to the kernel object files such as wl12xx.ko. So I planned to push them in to the device with command "adb push wl12xx.ko /system/lib/modules" but failed. I got super user permission ("adb shell", "su") but still cannot get the kernel objects to the device with adb command. Is there a way to handle this?
My final objective is to get the compiled kernel (with no wifi, bluetooth error) running.
PS. Doesn't actually matter if it is GB or ICS.
Thank you in advance.
spencerjang said:
Hello,
Here is my situation. I got S-off, SuperCID, unlocked on my HTC amaze unbranded version. Then got ICS stock RUU to run.
The wifi, bluetooth worked fine. However, I have to compile the kernel for this exact version (matched radio, baseband kernel, etc). I downloaded the source from HTCdev (the one with TI WLAN sources), and compiled it. Then I got the zImage repacked so that it can run on the device. Then I see that the wifi, bluetooth shows "error".
The kernel build "readme.txt" located me to the kernel object files such as wl12xx.ko. So I planned to push them in to the device with command "adb push wl12xx.ko /system/lib/modules" but failed. I got super user permission ("adb shell", "su") but still cannot get the kernel objects to the device with adb command. Is there a way to handle this?
My final objective is to get the compiled kernel (with no wifi, bluetooth error) running.
PS. Doesn't actually matter if it is GB or ICS.
Thank you in advance.
Click to expand...
Click to collapse
It's easier if you swap the neccesary files with faux kernel zip and flash it from recovery or make your own flashable zip.. That way the modules and zimage get flashed without having to use adb
Sent from my HTC_Amaze_4G using XDA Premium 4 mobile app
ravike14 said:
It's easier if you swap the neccesary files with faux kernel zip and flash it from recovery or make your own flashable zip.. That way the modules and zimage get flashed without having to use adb
Sent from my HTC_Amaze_4G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Oh, I downloaded faux's kernel I believe version 31 (from a dropbox someone linked). and failed to flash from sd card! Any suggestions?
spencerjang said:
Oh, I downloaded faux's kernel I believe version 31 (from a dropbox someone linked). and failed to flash from sd card! Any suggestions?
Click to expand...
Click to collapse
Why it failed? The error?
Sent from my HTC_Amaze_4G using XDA Premium 4 mobile app
Just letting you know, ill start porting TWRP tonight. I need to sync the entire cm9 repo first so it will take a while.
Dunno IF and when it will be finished. Il integegrate it with my kernel. But I will also release it to the public so they can include it in their own kernels. At least thats the plan.
Try putting it in jb kernel. It may fix recovery glitch
Sent from my Ray with the FORCE
MrTapa said:
Try putting it in jb kernel. It may fix recovery glitch
Sent from my Ray with the FORCE
Click to expand...
Click to collapse
what's the significant difference between this one and CWM? what about the update script?
thetrisatria said:
what's the significant difference between this one and CWM? what about the update script?
Click to expand...
Click to collapse
u can read about here:
some info:http://www.xda-developers.com/androi...pdated-to-2-2/
main thread: http://forum.xda-developers.com/show....php?t=1416118
teamwin site: http://www.teamw.in/project/twrp2
@thomas1991_12 - will support u in near future
Good luck man! Hope it works...I tried with ChampionSwimmer's JB AOKP build, but I stopped because the TWRP Tut says it won't work with a userdebug build and that is the only version that is currently compiling for the ray.
mericon has it working on xperia S....http://forum.xda-developers.com/showthread.php?t=1858283
justmpm said:
mericon has it working on xperia S....http://forum.xda-developers.com/showthread.php?t=1858283
Click to expand...
Click to collapse
Hmm didnt know that. thanks. CM9 is syncing now, takes forever.
stuff is not progressing too well. Ive compiled twrp with cm9, integrated in flykernel ramdisk tried to boot in recovery. Got a purple led behind home then black scree n for 10 seconds then phone shuts down..
thomas1991_12 said:
stuff is not progressing too well. Ive compiled twrp with cm9, integrated in flykernel ramdisk tried to boot in recovery. Got a purple led behind home then black scree n for 10 seconds then phone shuts down..
Click to expand...
Click to collapse
I tried to compile with aokp and I am facing a mountain of compile errors.....looks like it cant find somethings, so maybe an easy fix....will try tommorrow after some sleep
justmpm said:
I tried to compile with aokp and I am facing a mountain of compile errors.....looks like it cant find somethings, so maybe an easy fix....will try tommorrow after some sleep
Click to expand...
Click to collapse
I only had one compile error. with the images it trys to pull frorm res. starting with firmware_error png or something. But that can easily be resolved removing the #PRODUCT_COPY_FILES from recovery resources in msm7x30.mk (msm7x30-common folder).
thomas1991_12 said:
I only had one compile error. with the images it trys to pull frorm res. starting with firmware_error png or something. But that can easily be resolved removing the #PRODUCT_COPY_FILES from recovery resources in msm7x30.mk (msm7x30-common folder).
Click to expand...
Click to collapse
Thanks, I will try again tonight...I had a lot of those png errors...mine started off with two files that couldn't be found in bin (or maybe sbin), I don't really remember...but will be easy to track down. Did you edit init.rc? I hunted around for it last night but since there wasn't a call for it Boardconfig.mk I didn't worry about it too much then...but now I am wondering if it still needs to be edited in order for the dynamic linking to work.
justmpm said:
Thanks, I will try again tonight...I had a lot of those png errors...mine started off with two files that couldn't be found in bin (or maybe sbin), I don't really remember...but will be easy to track down. Did you edit init.rc? I hunted around for it last night but since there wasn't a call for it Boardconfig.mk I didn't worry about it too much then...but now I am wondering if it still needs to be edited in order for the dynamic linking to work.
Click to expand...
Click to collapse
Im struggling with init.rc too.
Positive point is, i got it booting using all the files from the twrp ramdisk in stead of my own (so init.rc from twrp ramdisk too). But it had major graphical problems, unusable. So im trying a bit more right now..
Graphical problems fixed. Its not responding to any touch now..
I cant get touch to work. I just generates random touches. I think twrp has some issues recognizing the touch screen and is using something else as touch, dont know what.. Maybe ALS. Anyway here is the default ramdisk, latest TWRP compiled. So other devs can try to integrate it in their ramdisks. Ask you favorite kernel developer to try to integrate it.
Please report back if anyone got it working, i can compile a version without logging then.
Also a experimental boot.img with flykernel, for you who want to see what i mean. it DOESNT work. Only boots to twrp recovery. Testing purposes
You can press and hold the middle log button to see whats going on.
thomas1991_12 said:
I cant get touch to work. I just generates random touches. I think twrp has some issues recognizing the touch screen and is using something else as touch, dont know what.. Maybe ALS. Anyway here is the default ramdisk, latest TWRP compiled. So other devs can try to integrate it in their ramdisks. Ask you favorite kernel developer to try to integrate it.
Please report back if anyone got it working, i can compile a version without logging then.
Also a experimental boot.img with flykernel, for you who want to see what i mean. it DOESNT work. Only boots to twrp recovery. Testing purposes
You can press and hold the middle log button to see whats going on.
Click to expand...
Click to collapse
I was able to compile it tonight from CM10. I probably won't pack it into a kernel tonight....what did you decide to do about init.rc. I checked the ramdisk and it doesn't contain the code for dynamic linking....drats...
justmpm said:
I was able to compile it tonight from CM10. I probably won't pack it into a kernel tonight....what did you decide to do about init.rc. I checked the ramdisk and it doesn't contain the code for dynamic linking....drats...
Click to expand...
Click to collapse
I tried it with different combinations. Original init.rc TWRP wouldnt even boot. init.rc CM9 created with TWRP upon compilation booted, and i tried to combine my own with the one compiled by cm9, that booted too. But as I said, touch isnt working properly...
Btw you will need these build flags to avoid graphics problem:
DEVICE_RESOLUTION := 480x854
RECOVERY_GRAPHICS_USE_LINELENGTH := true
TARGET_RECOVERY_PIXEL_FORMAT := "BGRA_8888"
thomas1991_12 said:
I tried it with different combinations. Original init.rc TWRP wouldnt even boot. init.rc CM9 created with TWRP upon compilation booted, and i tried to combine my own with the one compiled by cm9, that booted too. But as I said, touch isnt working properly...
Btw you will need these build flags to avoid graphics problem:
DEVICE_RESOLUTION := 480x854
RECOVERY_GRAPHICS_USE_LINELENGTH := true
TARGET_RECOVERY_PIXEL_FORMAT := "BGRA_8888"
Click to expand...
Click to collapse
Crap....I had two out of three....I left the last one out because the CM10 thread in the Xperia S section was saying that this pixel format
wasn't properly supported so it defaults to RGB565..... Anyway...not that big of a deal...as long as it compiles...
Thanks a lot!
justmpm said:
Crap....I had two out of three....I left the last one out because the CM10 thread in the Xperia S section was saying that this pixel format
wasn't properly supported so it defaults to RGB565..... Anyway...not that big of a deal...as long as it compiles...
Thanks a lot!
Click to expand...
Click to collapse
I didnt use a pixel format flag myself neither in the beginning but colors and graphics were incorrect after adding those two it showed up the way it should.. Let me know what problems you have after compiling.
thomas1991_12 said:
I didnt use a pixel format flag myself neither in the beginning but colors and graphics were incorrect after adding those two it showed up the way it should.. Let me know what problems you have after compiling.
Click to expand...
Click to collapse
I have gotten to the point where I can get a frozen black screen....I will play around with it some more tonight....so far I have learned a lot which
makes it worth the "failed" effort....thanks for your help!
justmpm said:
I have gotten to the point where I can get a frozen black screen....I will play around with it some more tonight....so far I have learned a lot which
makes it worth the "failed" effort....thanks for your help!
Click to expand...
Click to collapse
Yeah been there too. Thats a init.rc problem most likely. Try to use the entire ramdisk of TWRP with all it files, it should then boot in twrp.
thomas1991_12 said:
I cant get touch to work. I just generates random touches. I think twrp has some issues recognizing the touch screen and is using something else as touch, dont know what.. Maybe ALS. Anyway here is the default ramdisk, latest TWRP compiled. So other devs can try to integrate it in their ramdisks. Ask you favorite kernel developer to try to integrate it.
Please report back if anyone got it working, i can compile a version without logging then.
Also a experimental boot.img with flykernel, for you who want to see what i mean. it DOESNT work. Only boots to twrp recovery. Testing purposes
You can press and hold the middle log button to see whats going on.
Click to expand...
Click to collapse
@thomas1991_12: I think that the problem with the screen might be the screen calibration....over the week end I tried a new version of the aroma installer and it was a complete mess. The new version isn't supposed to need screen calibration, but it still does on the Ray....anyway, it turns out that amarullz got the code for the "universal" calibration from TWRP (https://github.com/amarullz/AROMA-Installer/commit/ea100b05c16ac0deaba42a4cc744d5a6b04ce9c8).....so maybe your wonky twrp recovery can be fixed by calibrating the screen. Iriijo also reported some touchscreen issues with twrp and I am not sure how far he took it.
Wechy77 found a fix for the problem with aroma: http://forum.xda-developers.com/showpost.php?p=33269911&postcount=1128
If you want to see if the screen issues are the same you can get aroma installer from here: http://forum.xda-developers.com/showpost.php?p=21755937&postcount=2
Forgive me if this is the wrong place for this. I followed a few different guides on xda and managed to build a cwm recovery from source. I can fastboot boot into my recovery image and it works fine, makes backups etc. But when i fastboot flash the .img and reboot into recovery it boots to a black screen. Im just not sure where to start in diagnosing the issue. I managed to get a few other issued solved like DTB and malformed fstab, but im stumped here. It might be something silly i did or didnt do. This is for a new device the lg ls740. I can post the recovery.img or the split files from unmkbootimg it it helps, thanks!
I'm having the same issue
Sent from my LGLS740 using XDA Free mobile app
notreal456789 said:
I'm having the same issue
Sent from my LGLS740 using XDA Free mobile app
Click to expand...
Click to collapse
because you were using my recovery, the recovery that doesnt work right! Im asking here for help on what i need to do differently before i compile it.
Ya I figured that out lol ; ) and sorry..I think?I mean, didn't mean to upset you?
Sent from my LGLS740 using XDA Free mobile app
danhalen1 said:
Forgive me if this is the wrong place for this. I followed a few different guides on xda and managed to build a cwm recovery from source. I can fastboot boot into my recovery image and it works fine, makes backups etc. But when i fastboot flash the .img and reboot into recovery it boots to a black screen. Im just not sure where to start in diagnosing the issue. I managed to get a few other issued solved like DTB and malformed fstab, but im stumped here. It might be something silly i did or didnt do. This is for a new device the lg ls740. I can post the recovery.img or the split files from unmkbootimg it it helps, thanks!
Click to expand...
Click to collapse
I think it's because of a brightness problem. You need to enable brightness permanently. For enabling it you need to follow these steps:
1.Unpack your builded recovery(with kitchen)
2.Place "qrdsys.sh" in /ramdisk/sbin/<here>
3.Add the following line into init.rc:
"service qrdtrd /sbin/sh /sbin/qrdsys.sh
oneshot"
4.Repack and flash
Source I got this from: https://github.com/dhinesh77/device_micromax_a57
Get the "qrdsys.sh" file from here: https://github.com/dhinesh77/device_micromax_a57/blob/cm-10.1/recovery/qrdsys.sh
Thanks to dhinesh77 :good:
Try it, if it don't work, report it to me.
GeekyDroid said:
I think it's because of a brightness problem. You need to enable brightness permanently. For enabling it you need to follow these steps:
1.Unpack your builded recovery(with kitchen)
2.Place "qrdsys.sh" in /ramdisk/sbin/<here>
3.Add the following line into init.rc:
"service qrdtrd /sbin/sh /sbin/qrdsys.sh
oneshot"
4.Repack and flash
Source I got this from: https://github.com/dhinesh77/device_micromax_a57
Get the "qrdsys.sh" file from here: https://github.com/dhinesh77/device_micromax_a57/blob/cm-10.1/recovery/qrdsys.sh
Thanks to dhinesh77 :good:
Try it, if it don't work, report it to me.
Click to expand...
Click to collapse
Thanks for the reply, i just tried it here this morning and i still have the same black screen result. Thanks for your help!
danhalen1 said:
Thanks for the reply, i just tried it here this morning and i still have the same black screen result. Thanks for your help!
Click to expand...
Click to collapse
No problem. Actually I thought it would fix it!
Well, what about you try to monitor your screen through ADB to your desktop?
If the recovery works, but has graphical issues, it should show there. If not, it's actually not booting or either not working.
Maby? We haveto zero out the recovery?? Just like the laf partition to access fastboot?
Sent from my LGLS740 using XDA Free mobile app