Finally managed to build a zImage, but now trying to build a *.nbh file with it. I've git both bootenv, tinboot, and also the latest kernel commit for 2.6.32.
Compressed initrd.lzma down to 1.1MB (original initrd.lzma was about 950KB, but with it, still got the error), and my zImage is 1.9MB, but I continue to get this error whenever I run this:
Code:
./compilekaiser
Code:
tinboot.S: Assembler messages:
tinboot.S:142: Error: attempt to move .org backwards
./arm-none-eabi-objcopy: 'tinboot.o': No such file
cat: tinboot: No such file or directory
=== yang v1.1: Yet Another NBH Generator
=== (c) 2008 Pau Oliva Fora - pof @ XDA-Developers
[] Output NBH file: KAISIMG-PANEL3-320-TILT4-FROYO.NBH
[] Input files: output.nb
[] Input types: 0x400
[] SignMaxChunkSize: 64
[] Device: KAIS****
[] CID: 11111111
[] Version: 1.0.MARTIN
[] Language: WWE
[] 0x400 --> output.nb
Done!
I've done some searches, and found that I have to decrease the size of my initrd, but not sure what else to strip from it, and also my zImage is base built, and the size really doesn't change whenever I change any options in menuconfig.
Ok, the original question of this thread has been solved, but a new question...
I used the vogue.config file provided from the git, but everytime I flash the kernel, it just shows a black screen?
Is there anything I'm doing wrong, or better yet, any developer able to provide their .config file that they know works, so I can take a look what I'm configuring incorrectly and correct it?
Krazy-Killa said:
Ok, the original question of this thread has been solved, but a new question...
I used the vogue.config file provided from the git, but everytime I flash the kernel, it just shows a black screen?
Is there anything I'm doing wrong, or better yet, any developer able to provide their .config file that they know works, so I can take a look what I'm configuring incorrectly and correct it?
Click to expand...
Click to collapse
I use the default vogue config, then I use tinboot but I use the initrd.lzma from bootenv since sometimes people update that and forget to update tinboot. Then, after I have an image, I use atools to edit. I always resize the NAND partitions so that /system is almost completely full, and set /system and /data to auto so I can experiment with sdcard /data without reloading the kernel. I could probably find a way to set those in the build so I don't need to run atools, but I just use what I know works.
I haven't used my own kernel build since February 10. I have been using l1q1d's experimental kernel. I have seen kernel updates since then but haven't even checked to see what they are.
n2rjt said:
I use the default vogue config, then I use tinboot but I use the initrd.lzma from bootenv since sometimes people update that and forget to update tinboot. Then, after I have an image, I use atools to edit. I always resize the NAND partitions so that /system is almost completely full, and set /system and /data to auto so I can experiment with sdcard /data without reloading the kernel. I could probably find a way to set those in the build so I don't need to run atools, but I just use what I know works.
I haven't used my own kernel build since February 10. I have been using l1q1d's experimental kernel. I have seen kernel updates since then but haven't even checked to see what they are.
Click to expand...
Click to collapse
Thanks! Using the default initrd.lzma did the trick. Now if only the bootenv git was updated with this compressed initrd. xD
Currently using a custom kernel I built. Made some changes to yaffs2, mtd, and NAND configuration. Had a crash on initial boot, did a soft reset and phone came back with no corruption, and my "bad block 160" went away. I'm currently testing it for 24hrs, then if all goes well, I'm going to go a week and report back.
Though currently I have no bluetooth, as the module isn't loading.. Will look into that, and try and see if it's build related, and if the module can be loaded manually.
if you use the bluetooth as module it doesn't works, probably because it doesn't enable on boot the correct hardware part. You need to select it as built-in.
l1q1d said:
if you use the bluetooth as module it doesn't works, probably because it doesn't enable on boot the correct hardware part. You need to select it as built-in.
Click to expand...
Click to collapse
Currently bluetooth is not my concern, though I did get it running, by loading the modules manually using 'modprobe', but I have no idea how well the bluetooth subsystem works in its current state, but it does turn on, and do a search of nearby devices.
My main concern is my NAND configuration. So far no issues as of yet, but will know more when 1.5days elapses. Had an issue last night with the phone app crashing with acore failing, but coming back after rebooting the phone with no data loss.
Gmail app also crashed, but after 2 crashes it reloaded (possibly some data loss), and started re-syncing my email.
Besides those two, no real issues yet.
Krazy-Killa said:
Besides those two, no real issues yet.
Click to expand...
Click to collapse
What have you changed, just options in the defconfig?
scooter1556 said:
What have you changed, just options in the defconfig?
Click to expand...
Click to collapse
Enabled yaffs ECC support, but forced it to use the same ECC as the NAND driver. Enabled NAND ECC support inside the driver itself, as well as other changes.
Also left block refreshing, background processing, and left force chunk erase check enabled.
Had to disable EXT2, and EXT4 file system support to decrease kernel size, but for my case, don't need them as I'm using full NAND install anyways.
Currently approaching 18hrs, with no issues, installed more apps with no issues with corruption, still getting random FCs with core apps, but they re-enable afterwards (Most likely isolated, so not a real concern at the moment). Once i approach 18hrs, I'll do a safe reboot, and see what happens there.
My bad block 160 came back, but that's the only bad block that has returned, no new ones as of yet.
I'm hoping to concentrate my efforts on working on cpu scaling, whether it be using CPUFreq, or a kernel hack... I'm actually interested in knowing how Myn got his Rogue Tools to adjust the CPU Scale dynamically. As I'm thinking (though horrible at coding), of writing a kernel module to dynamically adjust the CPU core based on activity of the core.
If you ask Myn nicely he might send you a link to his sources. I believe he modified the kernel parameter in /sys or /proc (I always get those two confused). I know that the battery parameters with which i am most familiar can be modified dynamically that way.
Sent from my Android on HTC Kaiser using XDA App
n2rjt said:
If you ask Myn nicely he might send you a link to his sources. I believe he modified the kernel parameter in /sys or /proc (I always get those two confused). I know that the battery parameters with which i am most familiar can be modified dynamically that way.
Sent from my Android on HTC Kaiser using XDA App
Click to expand...
Click to collapse
I'll most likely contact Myn first chance I get. Been busy with family matters as of late.
Built a new kernel yesterday morning, and showing promise. Phone goes into a very deep sleep now (literally have to wait 5-10 seconds for the phone to respond like when a PC wakes from suspend), and actually shows improvement in battery life while in sleep mode but massive increase in battery usage when phone is waking, so may have to change how the phone sleeps.
Phone stability has increased as well. Despite the slow time it takes to wake, the phone has yet to crash, or slow down performance wise.
NAND is also showing improvement. Did a soft reset last night, phone restarted without problem, and no loss of data or any yaffs tragedy errors. Still installing apps at the moment. Data partition is at 45MB out of 101MB.
Free RAM is at 35MB while on home screen.
Currently using Radio 1.70.19.09, and HardSPL 3.56.
If all goes well, tonight I may post my kernel flavor as well.
*EDIT* Anyway that the bootenv git repo be updated with what's being used in initrd.lzma file?
Something went wrong?
I'm eager to test the kernel you have prepared.
Sent from my CyanogenMod Kaiser/Kaiser using XDA App
tiagoclc said:
Something went wrong?
I'm eager to test the kernel you have prepared.
Sent from my CyanogenMod Kaiser/Kaiser using XDA App
Click to expand...
Click to collapse
Currently running into a problem with the acore being corrupted, which doesn't make since as it's in /system.
I'm testing out having CompCache running but not JIT, as each time acore gets messed up the JIT was enabled.
If all goes well tomorrow, I may post the updated kernel and and androidupdate.tgz file with modules.
n2rjt said:
I use the default vogue config, then I use tinboot but I use the initrd.lzma from bootenv since sometimes people update that and forget to update tinboot. Then, after I have an image, I use atools to edit. I always resize the NAND partitions so that /system is almost completely full, and set /system and /data to auto so I can experiment with sdcard /data without reloading the kernel. I could probably find a way to set those in the build so I don't need to run atools, but I just use what I know works.
Click to expand...
Click to collapse
And now, I haven't been able to build a kernel that fits for quite a while.
The initrd.lzma is larger than I remember:
bootenv: 1011446 bytes
tinboot: 1011027 bytes
bootenv/initrd, smallest I can pack it is 1012491 bytes.
And zImage is 2006008 bytes.
I tried to make a smaller initrd.lzma by replacing all the duplicate files with symbolic links. That resulted in 1012491 bytes. I tried using hard links, but ended up with 1582661 bytes. I even tried unpacking the tinboot/initrd.lzma and repacking it, but no success.
n2rjt said:
If you ask Myn nicely he might send you a link to his sources. I believe he modified the kernel parameter in /sys or /proc (I always get those two confused). I know that the battery parameters with which i am most familiar can be modified dynamically that way.
Click to expand...
Click to collapse
An extract from RogueTools source code:
String outputFreq = "echo \"" + strFreq
+ "\" > /sys/module/clock_7x00/parameters/a11\n";
Can parted be moved from initrd to the android rom?
That saves a ton of space, and allows all to fit.
NO, parted is needed for atools - sd partitioner, i change both the 2.6.25 and the 2.5.32 to lzma initrd for it.
n2rjt said:
And now, I haven't been able to build a kernel that fits for quite a while.
The initrd.lzma is larger than I remember:
bootenv: 1011446 bytes
tinboot: 1011027 bytes
bootenv/initrd, smallest I can pack it is 1012491 bytes.
And zImage is 2006008 bytes.
I tried to make a smaller initrd.lzma by replacing all the duplicate files with symbolic links. That resulted in 1012491 bytes. I tried using hard links, but ended up with 1582661 bytes. I even tried unpacking the tinboot/initrd.lzma and repacking it, but no success.
An extract from RogueTools source code:
String outputFreq = "echo \"" + strFreq
+ "\" > /sys/module/clock_7x00/parameters/a11\n";
Click to expand...
Click to collapse
I haven't had a problem with repacking initrd.lzma. I've kept mine below 975KBs, which is perfect for me.
Also as far as using what Rogue Tools uses, I've determined it wouldn't be a good system to code, as it requires to phone to sleep first before the new clock settings take effect.
I'll continue to look into the cpu coding, to find why scaling is not being recognized by the kernel. For now, I'm going to try and downclock the cpu core to 250MHz to see how much of a difference I get in battery life, but I suspect I won't get much since the voltage isn't being changed.
Krazy-Killa said:
Ok, the original question of this thread has been solved, but a new question...
I used the vogue.config file provided from the git, but everytime I flash the kernel, it just shows a black screen?
Is there anything I'm doing wrong, or better yet, any developer able to provide their .config file that they know works, so I can take a look what I'm configuring incorrectly and correct it?
Click to expand...
Click to collapse
Hi! Could you share what you did to slove the problem "tinboot.S:142: Error: attempt to move .org backwards".Thank you in advance.
Kernel plus initrd are too large if you get that message. First be sure your initrd is built with hardlinks to busybox. If that is still too large try fewer kernel features. For me, the standard kernel and bootenv fit. What sizes are the zImage and initrd.lzma files for you?
Sent from my Android on HTC Kaiser using XDA App
Man I need to read up on all the new Linux stuff... I'm so far behind I'm getting lost.
Personally I want to pack initrd and everything else into a package along with a singular build (current 2.2 8/25/2011) and just make one install package for everything. That way I can pack the install, updates and kernel into one kaisimg.
Keep up the good work guys!!!
The starting idea is wrong!
The multiple file: the nbh for kernel and initrd and the tgz file are setted up for large compatibility (multiple device use them). So creating a nbh only for kaiser is a bad idea.
Also you need to create a nbh for every single parameter in atools (like screen, keyboard, panel) it's crazy!
Related
I am just about to release my new barebones build with a lot of new features but one thing is killing me. I cannot get superuser to work anymore with the latest build and the latest kernel. Rogue tools won't overclock without SU working and that just totall kills the speed of my build =(. The build is based off scoot's release 5 and I am using the latest kernel with and without the module update SU is unaffected. Everything else works though.
What have you changed from the build i sent you that might effect it? Does it work for you with the original build? Things to check are the sysinit.rc, make sure it calls userinit.sh on startup, and also check your userinit.sh in the /bin directory and make sure the su fix is still present in the file Otherwise, try opening the super user app and downloading the latest su binary file, if it fails to install then you most likely have partition permission issues.
I did edit userinit to enable the odex script. I am gonna check that now.
Ok I am pretty sure that was it. how do I add this line to userinit to have it be proper then? /system/bin/odex.sh
aceoyame said:
Ok I am pretty sure that was it. how do I add this line to userinit to have it be proper then? /system/bin/odex.sh
Click to expand...
Click to collapse
You'd need to put it in sysinit.rc like this :
service odex /system/bin/odex.sh
So put that line right at the end then? Or is there a special format it has to go in. Sorry, I have just never had to edit this particular file before lol.
aceoyame said:
So put that line right at the end then? Or is there a special format it has to go in. Sorry, I have just never had to edit this particular file before lol.
Click to expand...
Click to collapse
At the end is fine, you will see some similar lines in there, you may want to add some options such as :
console
user root
oneshot
I don't know what the structure of the odex script is so i don't know which options you will need to get it to run properly but these are the most likely, just experiment and see
I've always put it at the end, after the su fix just as "/system/bin/odex.sh" and nothing else. What does service do? will it run it continuously or just with different permissions?
I would say its more likely that something's gone wrong while you edited userinit.sh, and now it can't be executed.
did you edit it in windows? you may have /n/r line endings now instead of /n
if you did it in linux it may be a permissions problem
fixed! I used the userinit from my old barebones. Something changed in the update. The two looked totally different.
THIS IS FOR TESTING ONLY. DO NOT ATTEMPT TO INSTALL THIS IF YOU DON'T KNOW HOW TO GET INTO BOOTLOADER MODE AND FLASH A ROM FROM THE SD CARD.
Announcements
We are currently replacing Tinboot with LK for boot. This will give us fastboot and many other enhancements and fixes to make our device more like a native Android device. This has already fixed some issues with GSM phones, sleep modes, and a few other things. The current issue being worked on is the power button not working (possible GPIO issue).
Introduction
This thread tracks the most recent NAND development. A huge thanks to [ACL] and WoZZeR999 for dedicating time to NAND development for us, and again, thanks to Jonpry, PHH, stinebd, and the rest of #htc-linux for their contributions. It's truly amazing what these guys have done for us, so be sure to show them your appreciation :wink:
The original NAND boot testing thread can be found here:
http://forum.ppcgeeks.com/tp2-andro...und-test-7-single-nbh-serialno-tilt2-fix.html
File Repository
Autobuild files can be found here: Index of /files/
The LK directory will contain the latest LK Bootloader and boot image code.
The rhodium_nand directory contains the latest kernels
The XDAndroid directory contains the latest OS files and updates (including the root update)
Note: We often disable autobuild when extremely experimental code is submitted, so this may not always be up to date but should be more stable than content we post in the threads.
Latest Files
LK Bootloader: http://htcdevs.wirelesstcp.net/files/LK/RHODIMG_NORECOVERY.NBH
Recovery Image: http://htcdevs.wirelesstcp.net/files/LK/recovery.img
05-22 Kernel: http://htcdevs.wirelesstcp.net/files/rhodium_nand/20110522_175721-kernel-update.zip
FRX06 OS Files: http://htcdevs.wirelesstcp.net/files/xdandroid/FRX6/update.zip
Optional - FRX06 Root: http://htcdevs.wirelesstcp.net/files/xdandroid/opt_updates/Root-Update.zip
Installation Procedure
Obtain Install Files
You need 4 files to get NAND up and running:
LK Bootloader NBH
Recovery.img
Kernel
OS Files
Install Directions
1) Set up your computer to use fastboot: http://forum.xda-developers.com/showthread.php?t=532719
2) Flash your phone with the LK Bootloader NBH
3) Copy recovery.img to your fastboot/adb folder
4) Open bash/command prompt and run fastboot flash recovery recovery.img
5) If successful, type fastboot reboot, and hold the Power Button as your phone boots
6) Your phone should boot into recovery, and there you can apply the various update.zip files in this order:
- FRX06 Update.zip
- Kernel-Update.zip
- Root-Update.zip
To navigate in recovery, use volume up/down (or up/down on keyboard) to change selection, then use End Call key (or Enter on keyboard) to make a selection.
Here's a video from ACL
http://www.youtube.com/watch?v=4r4o2CCKwvU
Work in Progress
Panel init/power down
No data on first boot
Youtube app has issues
GSM can boot with no rild arguments (no data)
Not Working at all
Camera
No bluetooth
No 3.5mm headphone jack
Frequently Asked Questions
What is NAND booting?
NAND booting uses code on the NAND to boot directly into Android without having Windows Mobile on the device. Currently, zImage and initrd.gz are stored on the internal NAND while the modules, rootfs, ext2, and data are stored on the SD card.
How do I setup NAND boot?
First, you need to download the Update Utility (CustomRUU) and the latest package. Extract the NBH to the same folder as the Update Utility and flash like you would a custom ROM. Put the included modules on the SD card (modules must be from the same package as the NBH) along with the modified rootfs.img (see first post) and system.ext2 from http://xdandroid.com/wiki/Main_Page (you can use system.ext2 from BLAZN, but XDAndroid will be better for testing)
Why don't my changes to Startup.txt work/How do I change boot options?
Because we are booting without Haret, Startup.txt is not used. Any changes to Startup.txt will have no effect. If there is a boot option you need enabled, you can either compile a new tinboot with those changes or let me know and I can compile one for you.
Where are the Android files stored and how do I update them?
Modules, rootfs.img, and system.ext2 must be stored under /andboot on the SD card. Every update will require flashing a new NBH (contains zImage) and replace the old modules file with the new one. Sometimes deleting the data.img file is necessary between builds if you experience major problems.
Wifi or other devices aren't working after an update...
The modules and zImage are a pair and must always be updated together. If you only flash the NBH but don't replace the modules file on the SD card, you will get a mismatch on the modules preventing the drivers from loading.
My battery drained and now my phone is stuck in a boot cycle! AHHHHHH!
Don't worry about it. You have two quick and easy options. First, unplug the USB cable, then remove the battery, then put the battery back in, and plug the USB cable back in. Now let it charge for 5 minutes, then turn it on, and you should be good to go. If it still does not work, unplug the USB cable, then remove the battery, then put the battery back in, attempt to enter bootloader mode and plug the USB cable back in as soon as the bootloader screen comes up. Now you can charge it for 5 minutes and restart back into Android (where you should continue charging).
Project Status
What is currently being worked on?
Battery life (up to about 9 hours now)
Backlight control (Dimming works and backlight can be turned off, but re-initializing is causing issues)
What is working?
Phone
Data
Sound
GPS
Keyboard
Wifi
Hardware 3d
What is NOT working?
Camera
Bluetooth
3.5mm headphone jack
Heh, only a matter of time before this thread made it over onto XDA. Thanks Nate
testing
has anybody here tested yet and if so... please note the outcome of the testing i would like to test but i would need more elaborate install instructions so that it is done right the first time ...also a couple of links are not working
ksper6986 said:
has anybody here tested yet and if so... please note the outcome of the testing i would like to test but i would need more elaborate install instructions so that it is done right the first time ...also a couple of links are not working
Click to expand...
Click to collapse
Thanks for the heads up. The copy/paste from PPCG killed some of the links. They should be working now
And this does work great. You can find the thread over at PPCGeeks here: http://forum.ppcgeeks.com/tp2-andro...esting-12-11-panel-power-off-now-working.html
First of all i want to thank all devs who are involved in the NAND Booting Section. I think i will test this in the next days but i must ask some questions first to do it .
1. So, do i need to do the Task 29 or is it just in case of problems.
2. Am i able to flash WinMob back if i'm failing?
yes u can go back to windows. infortunately i have been following all the steps correctly and it loads up the with letters showing its working and then i get a black screen so i think im stuck at boot any help. can someone tell me what im doing wrong. the files are in sd card/ andboot
Bieka said:
First of all i want to thank all devs who are involved in the NAND Booting Section. I think i will test this in the next days but i must ask some questions first to do it .
1. So, do i need to do the Task 29 or is it just in case of problems.
2. Am i able to flash WinMob back if i'm failing?
Click to expand...
Click to collapse
Task29 is just recommended to make sure everything is nice and clean. It makes troubleshooting much easier because it ensures nothing weird is being read from the internal nand.
You can easily flash back to WinMo by starting the phone in bootloader mode and flashing. Unfortunately, you will not be able to do the ActiveSync connection through USB and flash that way.
kabu said:
yes u can go back to windows. infortunately i have been following all the steps correctly and it loads up the with letters showing its working and then i get a black screen so i think im stuck at boot any help. can someone tell me what im doing wrong. the files are in sd card/ andboot
Click to expand...
Click to collapse
You should have three files in /sdcard/andboot: rootfs.img, system.ext2, and modules (don't rename the modules). Now flash the NBH and it should generate the data.img, and you should be good to go. It should be loaded in under 10 minutes, so if it isn't, I would check the contents of the memory card. Also note the card must be FAT32 formatted and have not be partitioned.
The panel power on/down is apparently fixed for some panels but not others. ACL and bzo have been working together on this and found that there are several different panels being used in our phones, and ACL is working on a patch to fix up the panels that aren't functioning perfectly.
mcnutty said:
RootFS
A custom rootfs.img is required to automatically configure the keyboard. You can override the automatic keyboard by creating a .kb file in your andboot folder. Accepted inputs are: rhod500.kb, rhod400.kb, rhod210.kb, and tilt2.kb
Click to expand...
Click to collapse
What about the rhod100? I have a modified rootfs.img for correct german keylayout in haret version of xdandroid. Can i use that too or do i need to delete all other .kb's? And is it even possible to get a working rhod100 keyboard? I know many questions but i think this should be BEFORE i get lost .
Bieka said:
What about the rhod100? I have a modified rootfs.img for correct german keylayout in haret version of xdandroid. Can i use that too or do i need to delete all other .kb's? And is it even possible to get a working rhod100 keyboard? I know many questions but i think this should be BEFORE i get lost .
Click to expand...
Click to collapse
Ahh yess the custom keyboard and how to create it. This threw me for a bit too and when i realized that all I had to do was open up notepad and then do a saveas rhod400.kb, I laughed at myself.
yep that easy a blank text file with the correct name and you are good to go
Well now that the thread is over on xda I tried again but still to no avail even tried two different SD cards both end with it booting but freezing at SMD: ch 0 OPENING -> OPENED. Pretty sure I have everything setup correctly three files in andboot folder on sdcard renamed rootfs to just rootfs.img but left the other two files. By the way this is on a tilt2.
Thordim said:
Ahh yess the custom keyboard and how to create it. This threw me for a bit too and when i realized that all I had to do was open up notepad and then do a saveas rhod400.kb, I laughed at myself.
yep that easy a blank text file with the correct name and you are good to go
Click to expand...
Click to collapse
Does that mean i just had to rename my rhod100_de.kb file to a rhod400 or something? That would be TO Easy ... ok i always think around corners ))
Bieka said:
Does that mean i just had to rename my rhod100_de.kb file to a rhod400 or something? That would be TO Easy ... ok i always think around corners ))
Click to expand...
Click to collapse
Actually, I didn't account for the non-US variants when creating the rootfs. I have some other modifications that I'm testing for the rootfs at the moment, so I will be sure to add the other variants back in for at least the KB overrides. I will need help with a variable for the automatic detection to work properly.
If anyone has any of the non-US variants, it would be extremely helpful for you to flash to NAND, hook up to ADB, and run "cat /sys/class/htc_hw/machine_variant" and let me know what yours is.
wifi
i want to start off by saying this is an amazing project.
But my problem is that wifi is not working for me. When i try to start wifi, it immediately says "error." I have done many flashes and used task29. i was just wondering if anyone else had this issue.
mcnutty said:
Actually, I didn't account for the non-US variants when creating the rootfs. I have some other modifications that I'm testing for the rootfs at the moment, so I will be sure to add the other variants back in for at least the KB overrides. I will need help with a variable for the automatic detection to work properly.
If anyone has any of the non-US variants, it would be extremely helpful for you to flash to NAND, hook up to ADB, and run "cat /sys/class/htc_hw/machine_variant" and let me know what yours is.
Click to expand...
Click to collapse
I will do that for you in the next days. Before Christmas it's a turbulent time for me. As soon as i can get the Time for it i will flash to nand and follow your instructions. If i need help, can i PM you?
Cheers
I'm using Neopeek's rom instead..how can i set it up? since this rom doesnt use the system.ext2 file
getting calibration without visible points to touch aka the boxes. also, boot ani glitches out on screen with a "solid" animation, and video glitchs on the bottom half of the screen. sits here indefinately.... still waiting..... haha
update: loads to lockscreen, so far can't get screen to stay on??? strange
update2: got it working, but keeps turning screen off immediately... any ideas>?
hmm, i have been trying this and i feel like i have everything right
tilt2.kb, rootfs.img, modules, and system.ext in an andboot folder in my storage card and then, a nbh with the same name as the module in a folder with customRUU.exe. I flash and then it gets to the linux boot screen, after a couple lines go by, the screen fades out and dies and restarts. My battery says 88 percent when i flash back to windows, anybody know what could be going wrong?
HTC Sense
will it only recognize only an ext2 or will it recognize squashfs.
blitzer320 said:
Well now that the thread is over on xda I tried again but still to no avail even tried two different SD cards both end with it booting but freezing at SMD: ch 0 OPENING -> OPENED. Pretty sure I have everything setup correctly three files in andboot folder on sdcard renamed rootfs to just rootfs.img but left the other two files. By the way this is on a tilt2.
Click to expand...
Click to collapse
I'm on the rhod210 (T-Mobile), and I've been having this exact issue. Any ideas?
btw, this is my first post here, but I've been reading and following this project for quite a long time. You guys are great! Thanks for all the work you do!
NOTE: Due to the fact that the Jellybean build went smoother and we all want the latest candy anyway, I've scrapped this effort. Get your candy at: http://forum.xda-developers.com/showthread.php?t=1867579
DISCLAIMER: This is a test build. It works for me, and I spent a good bit of time cleaning up the rough edges and fixing a few silly things, but for all I know it will make zombie worms run out of your tab resulting in your untimely death without warning. If you're not comfortable hacking a Galaxy-series android, probably best to wait for the official update from Samsung and be a good compliant end user and update with Kies... If the death star ever lets the ICS update out, that is.
As Cyanogen likes to say on his work in progress repos: MAY EAT YOUR CAT
ALSO: This is wholly unsupported and I have no affiliation with the Cyanogenmod team. If you bug them for help with this, they will send a laser-equipped triangle-shaped monolith of a hovercraft to your location and decimate anything in your general vicinity with insane force and completely reckless abandon. Well, maybe not, but you get the idea. Don't piss off superman.
First, the bad.. I'm going to start a list of what seems broken:
- Camera. Tablet reboots on snapping photo, preview is 90 degrees off.. weird.
- Google Talk: Looks related to the camera problem. All seems to center around some camera effects issue. Talk.apk from the original honeycomb image does work, so if you need google talk, just swap it out.
Taking what I learned from building CM10 for this device, I grabbed the CM9 tree, which is supposedly final now, and built that too. This time, I'm dropping a flashable .zip, since CM9 is "solid" and won't be updated any more. That doesn't mean this is perfect, as Cyanogenmod is only the android framwork -- The dirty low level bits still come from the OEM, and samsung hasn't released those yet, but.. It's good enough for me, so... Maybe it is for you too!
Since AT&T is still jerking around with the official ICS update, worried about their pathetic "value added" software instead of dropping a clean build, there's no official, fully regression tested radio/RIL combo... So I've yanked the RIL from the Note, a very similar device. It seems to work, but may or may not get LTE at first -- Might stick in HSPA mode a bit, might get LTE, it's a little flaky. May work better in your area, may also depend on network conditions. I'm not completely up to speed on cellular tech so the cryptic debug output doesn't say much to me. However, unlike my work with Jellybean, at least the stock radio works on ICS... For me. If you flash this, please share your 3G/4G experience, and be sure to indicate which carrier and area you are in, if you don't mind.
In Settings, Wireless/Network, More..., Mobile Networks... There is a network mode option. Be sure that is set to LTE/GSM, not GSM. In ICS, this setting actually seems to work - In Jellybean, it does nothing.
WiFi should work without any effort, bluetooth too, and it has the phone app, so you can voice call. Video playback works, audio works, GPS works, and I didn't run into troubles with about 10-15 of the more popular apps from the market.
Tether works, and I changed the tether service to hand out the google DNS server (8.8.8.8/8.8.4.4) to clients, because AT&T's DNS tends to be annoyingly slow.
I also noticed stagefright (a video rendering library, among other things) refused to play anything besides the base-quality x264 videos, so I commented out the retarded bailout (return with unspecified error) in stagefright.so, because all the better-quality youtube videos just refused to play with no reason, just a generic error (what a POS) - So have fun watching HD videos on youtube, although some of the top-quality ones (1080) are a bit on the tough side for the GPU to render. Ah well, beats a non-sensical error.
Samsung did already release the 3.0.8 ICS kernel, for the SHV-140, which is the same hardware with a different radio.. That kernel, in it's .config, has an option for the SGH-i957, so I built that and stuffed resulting kernel binary into boot.img, and packed that into the zip. boot.img also enables early ADB, so you can adb shell into it even if the framework completely shats itself, which it sure did before I got the proper production-level Adreno 220 drivers straight from qualcomm into the build. So the main advantage of this build over jellybean right now is an official Samsung kernel built from their unmodified source code and official release Qualcomm GPU driver binaries.
I also changed apns-conf.xml to use the proper "Broadband" APN for AT&T LTE data-only, as is usually sold with these tablets.
To get this going, start with TWRP recovery -- if you don't have it already, visit that thread in this forum and get yourself hooked up, drop the zip in /sdcard, boot into recovery and..
1) Make a complete TWRP backup before you do anything further! (of course)
2) Wipe -> Factory Reset
3) Wipe -> System
4) Install the .zip I'm about to link you to
5) Reboot, receive bacon.
http://d-h.st/W3X
I've not tested everything and anything, and some things may not be fixable until we get the binary bits from Samsung when they drop ICS officially for this device. However, please report any problems you have here. If I can find time to reproduce and fix, you might get lucky
Enjoy! Honeycomb got boring long ago!
Appreciate all the work. I'll hopefully have time to flash tomorrow. Looking forward to dumping honeycomb.
really glad to see developement picking up for this tab!
I never use the camera or the 4G. I'm gonna flash this in the am. Thanks!
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Flashed and currently running this build. Looks stable enough so far, a couple of FC's but definitely manageable. I know this far fetched but once CM9 gets more stable, will we be able to start porting cm9 based roms? Or can we only port roms created for devices with similar CPU/structures/etc?
Sent from my SAMSUNG-SGH-I957 using xda premium
This is great, thanks for the build. Working great for a 1st edition. From a few minutes playing with it, I noticed that vibrate doesn't work nor does MTP (drivers refuse to install). Not deal breakers and I'm going to use this as my main OS - much better than honeycomb.
I can confirm that this is working very well on rogers, havent tested all functions but my tablet is now 10 times better, currently running Apex launcher. Dont forget to flash gapps for ics....
Something is up with package manager, can't install xda app
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Confirming difficulty with package manager, for both side loading and loading from the Google Play App. However, if I load from the Google Play website the installation works.
Other than that I'm very impressed by the quality and stability of what you've built here - many thanks.
My package installer seems to work just fine.
70ish apps from the play store installed fine, and a dozen or so non market apps.
Ive had some good success with this rom and my apps are installing as well. I do have a situation where I tried using an update to rom manager and it seemed to have broke my recovery and I cant get it back! I would like to try using twrp and how do I install it? I would flash through odin but I don't have the file :crying:
cottageboy said:
Ive had some good success with this rom and my apps are installing as well. I do have a situation where I tried using an update to rom manager and it seemed to have broke my recovery and I cant get it back! I would like to try using twrp and how do I install it? I would flash through odin but I don't have the file :crying:
Click to expand...
Click to collapse
Yikes! Never good when you lose recovery, that's a bad place to be. I'm assuming you have a working image on the device that isn't locked down? IE the CM9 image and/or a rooted honeycomb image is still functional?
Recovery image at:
https://dl.dropbox.com/u/69488769/twrp_recovery_SGHI957_2.2.1.5.img
From a shell, either via adb or via the terminal, just dd (block copy) the image to the recovery partition
dd if=twrp_recovery_SGHI957_2.2.1.5.img of=/dev/block/mmcblk0p22
That should solve that
dan-htc-touch said:
Something is up with package manager, can't install xda app
Click to expand...
Click to collapse
I'm getting an "Error Processing Purchase" on the xda FREE app?? logcat shows google's server returns HTTP/500
Code:
E/Volley ( 8075): [386] BasicNetwork.performRequest: Unexpected response code 500 for https://android.clients.google.com/fdfe/purchase
HTTP 500 = Server Error
Looks like a problem others have had and may relate to the app caching information it shouldnt?
http://code.google.com/p/android/issues/detail?id=30039
also,
http://forum.xda-developers.com/showthread.php?t=1695519
After clearing the play store's DB, the google services framework database, and removing/readding my google account, the error went away.
Then I got another vague error, which the following text from logcat explained:
I/PackageHelper( 3428): Size of container 5 MB
E/PackageHelper( 3428): Failed to create secure container smdl2tmp1
D/VoldCmdListener( 157): asec create smdl2tmp1 5 fat {} 10012
E/Vold ( 157): Error creating imagefile (Read-only file system)
E/Vold ( 157): ASEC image file creation failed (Read-only file system)
W/Vold ( 157): Returning OperationFailed - no handler for errno 30
E/DefContainer( 3428): Failed to create container smdl2tmp1
Click to expand...
Click to collapse
Anyone know anything about how to configure the ASEC location? I've never delved into ASEC and probably need to configure something in the image to account for handling ASEC transactions.
... Looks like I'll need to tweak a few things in the initial ramdisk to get the asec mountpoint correctly set. Good grief, the freaking thing wants to set up a loopback block device on a tmpfs partition to install an application. That's pretty sad... /hacking it
I'm confused. How do I log into my Google account? Where's "my files" folder?
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
ZX6Chris said:
I'm confused. How do I log into my Google account? Where's "my files" folder?
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
You need to flash gapps for ICS for your Google account and apps.
The "my files" app does not exist on AOSP. You will need to download another file explorer.
Excellent work so far!
Snappy and mostly stable it seems.
Clicking on storage under settings causes a FC, the camera is derpy as stated in the op, and an occasional YouTube derp as stated in the op.
No hapatic at all either.
3g/hspa+/4g lte all working perfectly here.
Thanks!!
neubauej said:
Clicking on storage under settings causes a FC
No hapatic at all either.
Click to expand...
Click to collapse
Interesting, I'll check into that, thanks for that!
It Appears haptic feedback works with the keyboard, and on the home screen softbuttons. immvibed is running and doesn't register any complaints -- atleast that's how it is on my tab. does it not work at all for you?
storage FC: It's looking for /storage/sdcard1, the secondary SD card, which doesn't exist, and it has no error handling for this condition, so it explodes with java exception and the Settings process thus dies.. I believe I just need to yank that definition (for non-existent sdcard1) out of the xml for this package and rebuild, will try that next build!
Figured out the package manager issues, needed to mount tmpfs on both /mnt/secure and /mnt/asec and open up the permissions. That's unfortunately an initial ramdisk (root filesystem) hack, which means a new boot image.
attached. if you're not sure what to do with this, probably best to wait until i roll a few more fixes into a fresh flashable zip.. Otherwise, block copy to mmcblk0p8, reboot.
Been fighting with the camera issue, not having much progress there.
Thanks for the feedback, folks!
when im in my file explorer, where do I find the recovery portion?
im assuming that I put the img file there and using terminal emulator run your commands (do i have to type su first)?
nrvate said:
Yikes! Never good when you lose recovery, that's a bad place to be. I'm assuming you have a working image on the device that isn't locked down? IE the CM9 image and/or a rooted honeycomb image is still functional?
Recovery image at:
https://dl.dropbox.com/u/69488769/twrp_recovery_SGHI957_2.2.1.5.img
From a shell, either via adb or via the terminal, just dd (block copy) the image to the recovery partition
dd if=twrp_recovery_SGHI957_2.2.1.5.img of=/dev/block/mmcblk0p22
That should solve that
Click to expand...
Click to collapse
cottageboy said:
when im in my file explorer, where do I find the recovery portion?
im assuming that I put the img file there and using terminal emulator run your commands (do i have to type su first)?
Click to expand...
Click to collapse
There is no recovery partition to find in root explorer.
Just put the image file in your root directory (/sdcard).
Type "su" enter then the command.
I don't remember if you need to do it as a superuser, but it will certainly work if you are.
cottageboy said:
when im in my file explorer, where do I find the recovery portion?
im assuming that I put the img file there and using terminal emulator run your commands (do i have to type su first)?
Click to expand...
Click to collapse
The recovery emmc partition is /dev/block/mmcblk0p22. The dd command block copies the recovery image (twrp_recovery_SGHI957_2.2.1.5.img) from the filesystem to the emmc partition. if= specifies the image to read from, of= specifies the device to write the image to.
The recovery image is a raw partition image.
You will need to be root to do this.
If you're not comfortable operating on the command line, dan offered a apk to do this: http://db.tt/DXtF5iB6 -- from his TWRP thread @ http://forum.xda-developers.com/showthread.php?t=1697610
Finally got time to flash cm9. Block copied the fixed boot image. Running great. Amazing for a first build. Like a new tablet. Thanks!
Hi. I just finished installing CyanogenMod 11 on my Galaxy Nexus. I also put the DirtyV-SR kernel on as well. Everything seems to be working fine. I then learned about a custom edit of the DirtyV kernel by Nephilim that seems to be popular. I have no idea how to change the settings manually though. Luckily in the DirtyV post there is a link to a script by the user "buscher" that supposedly does the changes for you. I followed the instructions and put the script in the System/etc/init.d folder, removed the .txt extension on the script, and changed it's permission settings (I think I changed the permissions correctly). I'm using an app called SManager to do this BTW. When I try to launch the script I get a syntax error. Here is a screen shot of said error...
i.imgur. com/ b5jAVe3. jpg
(Added spaces so I could post the link)
Link to DirtyV thread: http://forum.xda-developers.com/galaxy-nexus/development/kernel-dirtyv-t2613655
Link to buscher's post with the script: http://forum.xda-developers.com/gal...nel-dirtyv-t2613655/post50202995#post50202995
Does anyone have any idea what im doing wrong? Or perhapsna different way to use Nephilims version of DirtyV?
Thx
I've never used any of the scripts you're talking about, but normally that syntax error means that there's a coding error in the script file that the interpreter doesn't know how to handle. I looked at the script in that thread and I can't see anything that would jump out as being problematic, so there's a chance something may have happened when you downloaded the script or copied it to the device.
I'd say you should try downloading the script again directly on your device, and make sure you're clicking the "Download" button on the Mediafire page with the script instead of doing a "save link as" or anything similar from the forum thread. You may even want to open it up in a text editor app and compare it to the version online to make sure that the file matches.
Alright so I redownloaded it and got it to run this time. My problem now is that it seems some of the required directories for the script don't exist on my phone for some reason.
Here's a new screenshot of the errors
http:// i.imgur. com /mjBjQ88. jpg (again had to add spaces)
It's probably safe to ignore those errors, they probably come from that script being older than the latest kernel version you're running it against. Basically, Linux kernels create a whole bunch of files and folders in /sys that control certain kernel settings. By writing a value to specific files, you can change those settings. Those two errors are the result of the script trying to change two settings files that don't exist anymore, possibly because they were removed in a newer version of the kernel. The rest of the script should run without problems and make the rest of the changes.
just wanted to say, there is no need for script manager to run that script.
remove the .txt
put it in /etc/init.d folder/dir
set all perms(i.e rwxrwxrwx)
then just reboot
it will automatically run and set everything in the script when the device boots.
also
if you want to set those things from nephilim thread, use the app called trickster mod(or Synapse, though trickster might be less overwhelming for someone new to setting these things)
enjoy
any questions feel free to ask
Q&A for [KERNEL][AOSP/CAF][NOV 16] Glitch for Flo/Deb - r303
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [KERNEL][AOSP/CAF][NOV 16] Glitch for Flo/Deb - r303. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Root not working
Hello!
First of all :good: :good: :good: I am using your kernel more or less since I own the Nexus 7 (2013) in combination with Multirom and some custom ROMs, installed as secondary. It is working like a charm and I never saw any problems on "KK".
With "L" root is not (yet?) working for me. This might however been caused by the way of using it. I have two scenarios: 1.) "L" as secondary ROM and 2.) "L" as primary ROM. For both cases I used Tassadar's build. For the latter I copied the installed secondary ROM to the primary slot. With Tassadar's kernel I have root. When installing GlitchKernel root is gone. By flashing Tassadar's boot.img I regain root. As far as I can say right now this -- regaining root -- does not work for the secondary ROM.
To have it said: I also tried flashing GlitchKernel and Chainfire's SuperSU directly afterwards before rebooting with no effect. One thing I haven't tried is to NOT inject Multirom after flashing your kernel.
It would be great if you could help. If there is anything I could/should test, let me know!
Finally, my prayers are also with you!!!
Best Regards,
tungdil
@tungdil
Hello tungdil,
I'll start by asking what revision of Glitch are you running ?
r300 didn't come with root support out of the box, and it is required to flash a root-enabled boot.img (the ramdisk in it to be exact) prior to flashing r300 to enable the rooting technique of your choice (SELinux Permissive (potentially with system R/W access) or just Chainfire's partial root "trick"). Lollipop's security enhancements are modifying how root works for us (users), so until some kind of standard takes place I did want to wait and see.
However, considering many users didn't find that easy (either to understand or to find what boot.img to get for what result), I did release r303. This new revision comes with various ramdisk patches you can enable through Aroma to get anything from Chainfire's partial root to full root with SELinux Permissive, system partition R/W access and PIE bypassing (it will obviously lower Lollipop security though).
I'm using this new revision on primary and secondary roms using MultiROM with no rooting issue.
If you're running r300, get the r303 update. If you're already on r303, what apps are you running that won't get root access ? You may want to use more patches to "open the can".
Have a nice day !
Tk-Glitch said:
@tungdil
Hello tungdil,
I'll start by asking what revision of Glitch are you running ?
r300 didn't come with root support out of the box, and it is required to flash a root-enabled boot.img (the ramdisk in it to be exact) prior to flashing r300 to enable the rooting technique of your choice (SELinux Permissive (potentially with system R/W access) or just Chainfire's partial root "trick"). Lollipop's security enhancements are modifying how root works for us (users), so until some kind of standard takes place I did want to wait and see.
However, considering many users didn't find that easy (either to understand or to find what boot.img to get for what result), I did release r303. This new revision comes with various ramdisk patches you can enable through Aroma to get anything from Chainfire's partial root to full root with SELinux Permissive, system partition R/W access and PIE bypassing (it will obviously lower Lollipop security though).
I'm using this new revision on primary and secondary roms using MultiROM with no rooting issue.
If you're running r300, get the r303 update. If you're already on r303, what apps are you running that won't get root access ? You may want to use more patches to "open the can".
Have a nice day !
Click to expand...
Click to collapse
Hello Tk-Glitch!
Thanks a lot for your feedback! My feeling is I am doing something wrong because you wrote you don't have problems using it with MultiROM. But let me answer your questions:
Actually I tried both r300 and r303 using the following sequence:
"install" with TWRP (or delete and inject if it is the secondary ROM) the boot.img which is packaged with Tassadar's lrx21p_flo.zip. Note: I do have root afterwards
Flash GlitchKernel, reconfigure everything in the Aroma installer. Usually I don't use permissive mode or PIE Patch but have tried it as well with no success
Reboot, which results in not having root.
For the primary ROM: Re-install the Tassadasr's boot.img; which results in having root again.
That means, I start with a situation where root is working (btw. Kernel: 3.4.0-g0356b90-00001-gd0e79e3 [email protected] #240)! Yesterday I have also updated the bootloader to 04.04 with no effect. Just right now I tried it again and after flashing Glitch-N7-r303.zip (leaving all options as is but selecting PIE patch and permissive mode) the Kernel is: 3.4.0-Glitch-N7-AOSP-r303 [email protected] #1, dated 16.11.14 08:08:49 PST but I don't have root.
The following "apps" are not working AFWall+, MultiROM Manager, Reboot Menu Widget, and su itself if directly "called" from within Terminal Emulator. Just to have it said: ES File Explorer also won't work, but that's because it needs at least the PIE patch. The log of SuperSU tells, for example for AFWall+:
Code:
iptables v1.4.20: can't initialize iptables table ... : Permission denied
When I try launching su from the Terminal, SuperSU will ask to confirm root access even if I previously allowed root acces permanently. If I allow root nothing happens and the Terminal is "dead". The same applies for the other apps. I also tried this via an adb shell with the same effect, i.e. from the adb shell with root I'll see:
Code:
[email protected]:/ $ whoami
whoami: unknown uid 2000
1|[email protected]:/ $ su
[email protected]:/ #
and without
Code:
[email protected]:/ $ whoami
whoami: unknown uid 2000
1|[email protected]:/ $ su
i.e. the shell will not return.
Anything else I could test or check?
Best regards,
tungdil
Solved
Hello Tk-Glitch,
I "just" saw that Chainfire released an update to SuperSU (Beta 2.23) and ... that did it for both, primary and secondary ROM. I was on SuperSU Beta 2.19 before. My installation procedure for 2.23 was as follows:
Start with root NOT working for the primary ROM and working for the secondary ROM
For primary ROM use a TWRP queue for flashing GlitchKernel r303 and SuperSU Beta 2.23, and for the secondary ROM first flash GlitchKernel and then SuperSU
reboot and ... :good:
Notes:
currently not using the PIE patch when installing Glitch kernel, i.e. no root for ES File Explorer. All other apps I mentioned above do have root!
the same installation procedure did not work with SuperSU 2.19
Best regards!
tungdil
@tungdil
Hi again tungdil,
It's nice you got it sorted, though it convinces me something must be wrong with your installation process. Latest SuperSU is able to mod the ramdisk to enable root support (pretty similar to what Glitch r303 is supposed to do), so yes it works, though the question is why didn't it work with r303 for you ?
It may very well be an error on my side (I'll verify that), though it worked for me and most it seems, as you're the only one to encounter the issue since r303 release, or at least to talk about it. I checked my secondary ROM to be sure, but I'm indeed running SuperSU 2.19 on it.
By the way, injecting multirom shouldn't be required with Glitch, and leaving it checked will only lead to multirom detecting it's not needed and skip the injection (so basically you don't have to worry about it).
If you're okay, let me ask a few questions :
- Do you have screen timeout disabled in TWRP ? And if you don't, are you able to hit the reboot button after Glitch install ?
- What ROM are you running ?
- Could you please install r303 and save the installation log for me ?
- Could you please copy the /fstab.flo content from a ROM you got Glitch installed to for me?
- Why to use "delete and inject" for secondary ROM instead of "classic" install ?
Thank you !
Hello Tk-Glitch,
thanks a lot for your feedback and giving me the chance to learn something. I'll be happy to supply additional information:
- Do you have screen timeout disabled in TWRP ? And if you don't, are you able to hit the reboot button after Glitch install ?
Click to expand...
Click to collapse
The screen timeout in TWRP is not disabled but set to 300, and it is possible to hit the reboot button (or do something else before rebooting).
- What ROM are you running ?
Click to expand...
Click to collapse
As mentioned I am using the ROM which Tassadar has packaged (lrx21p_flo.zip).
- Could you please install r303 and save the installation log for me ?
Click to expand...
Click to collapse
Yes! I did a fresh install, i.e. added another secondary ROM and stored the LOG. Note: I didn't touch the "options" during install so everything was as preset. After GlitchKernel I flashed SuperSU 2.19 and verified via adb shell that root is not working.
Contents of the log (mr_update.zip.log.txt):
Code:
AROMA Installer version 2.70RC2
(c) 2013 by amarullz xda-developers
ROM Name : Glitch kernel
ROM Version : N7-AOSP
ROM Author : Tk-Glitch
Device : Nexus 7 (2013)
Start at : Wed Nov 19 21:24:46 2014
installing samsung updater extensions
Installing Glitch kernel...
Extract: /tmp/buildconfig.sh
Extract: /tmp/busybox
Extract: /tmp/compatibility.sh
Extract: /tmp/compatibility2.sh
Extract: /tmp/glitch-settings.conf
Extract: /tmp/systemcheck.sh
Cleaning up
about to run program [/tmp/systemcheck.sh] with 1 args
Installing system files for real.
Extract: /system/bin/fstrim
Extract: /system/etc/init.d/99glitchsetup
about to run program [/tmp/buildconfig.sh] with 1 args
about to run program [/tmp/busybox] with 4 args
Fluxi's MSM Hotplug enabled
Renaming binaries...
/system/bin/mpdecision -> mpdecision_bck
/system/bin/thermald -> thermald_bck
about to run program [/tmp/compatibility.sh] with 1 args
Extract: /tmp/abootimg
Extract: /tmp/cmdline.cfg
Extract: /tmp/edit_ramdisk.sh
Extract: /tmp/edit_ramdisk_permissive.sh
Extract: /tmp/fstab.tmp
Extract: /tmp/glitch.zImage
Extract: /tmp/max_oc.sh
Extract: /tmp/restore.sh
Extract: /tmp/sepolicy.tmp
Applying init settings
about to run program [/tmp/busybox] with 4 args
32768+0 records in
32768+0 records out
16777216 bytes (16.0MB) copied, 0.472290 seconds, 33.9MB/s
about to run program [/tmp/abootimg] with 6 args
writing boot image config in /tmp/bootimg.cfg
extracting kernel in /tmp/zImage
extracting ramdisk in /tmp/initrd.img
about to run program [/tmp/max_oc.sh] with 1 args
about to run program [/tmp/edit_ramdisk.sh] with 1 args
2372 blocks
CIF hack found!
about to run program [/tmp/abootimg] with 9 args
reading config file /tmp/cmdline.cfg
reading kernel from /tmp/glitch.zImage
reading ramdisk from /tmp/initrd.img
Writing Boot Image /tmp/boot.img
Glitching your device...
about to run program [/tmp/busybox] with 4 args
32768+0 records in
32768+0 records out
16777216 bytes (16.0MB) copied, 0.952729 seconds, 16.8MB/s
Finished!
script result was [Finished!]
Installer Sucessfull (Status 0)
End at : Wed Nov 19 21:24:49 2014
- Could you please copy the /fstab.flo content from a ROM you got Glitch installed to for me?
Click to expand...
Click to collapse
Yes, of course. Here we go ... Note: I compared this fstab.flo with a version from a secondary ROM which has root. They are in fact identical!
Code:
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,barrier=1 wait
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 noatime,nosuid,nodev,barrier=1,data=ordered,nomblk_io_submit,errors=panic wait,check
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 noatime,nosuid,nodev,barrier=1,data=ordered,nomblk_io_submit,errors=panic wait,check,encryptable=/dev/block/platform/msm_sdcc.1/by-[CODE]
name/metadata
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 nosuid,nodev,barrier=1,data=ordered,nodelalloc wait
/dev/block/platform/msm_sdcc.1/by-name/boot /boot emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/recovery /recovery emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/misc /misc emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/sbl1 /sbl1 emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/sbl2 /sbl2 emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/sbl3 /sbl3 emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/tz /tz emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/rpm /rpm emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/aboot /aboot emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/sbl2b /sbl2b emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/sbl3b /sbl3b emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/tzb /tzb emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/rpmb /rpmb emmc defaults defaults
/dev/block/platform/msm_sdcc.1/by-name/abootb /abootb emmc defaults defaults
[/CODE]
- Why to use "delete and inject" for secondary ROM instead of "classic" install ?
Click to expand...
Click to collapse
Since Tassadar's boot image was working for me this was the easiest way. Just extract boot.img from lrx21p_flo.zip and use "delete and inject" for exchanging the boot image. Note: While writing this post I verified what I found yesterday, i.e. after flashing GlitchKernel and SuperSU 2.19 I do not have root. Flashing SuperSU 2.23 enables root. Reflashing Glitch and 2.19 leads to no-root again.
Best regards,
tungdil
Additional Information
Hello TK-Glitch,
it's me again
I did some further "research" in my secondary "L- ROMs" (the one I created for providing the information above and the one that does have SuperSU 2.23 installed and has root). I had a more detailed look on the boot images. In both cases your kernel is installed. I pulled the boot images using adb and unpacked them using unpackbootimg and then also unpacked the ramdisk. Binary the two images are not identical since the Glitch kernel configuration was slightly different:
Code:
console=ttyHSL0,115200,n8 androidboot.hardware=flo user_debug=31 msm_rtb.filter=0x3F ehci-hcd.park=3 l2_opt=1 vdd_uv=1 max_oc0=1728000 max_oc1=1728000 max_oc2=1728000 max_oc3=1728000 min_clock=384000 abc
v.s.
Code:
console=ttyHSL0,115200,n8 androidboot.hardware=flo user_debug=31 msm_rtb.filter=0x3F ehci-hcd.park=3 l2_opt=3 vdd_uv=3 max_oc0=1890000 max_oc1=1890000 max_oc2=1890000 max_oc3=1890000 min_clock=162000 abc
but I could not see any difference in the RAMdisk and the other main components dspite the fact that SuperSU 2.19 was used in one case and 2.23 in the other.
[EDIT] After reading TK-Glitch's next Post I realized that I made a mitsake and picked a wrong boot image when trying to compare so the following is wrong:
Tassadar's boot image is, of course, very different. One thing that I saw (because I remembered that SuperSU 2.23 "...fixes a number of SELinux policy issues...") is the difference in selinux-version. In Tassadar's image I find:
Code:
Android/aosp_flo/flo:5.0/LRX21M/scott11042320:userdebug/test-key
while your selinux_version says:
Code:
google/razor/flo:5.0/LRX21P/1570855:user/dev-keys
[/EDIT]
Maybe I am wrong but I think my problem was caused by the combination of Tassadar's build of the ROM and the Glitch kernel and, I was just lucky that the latest Beta of SuperSU helped curing it.
Best regards,
tungdil
Latest glitch and lollipop stock
I can't unlock many times the screen I have enable the swipe options
@tungdil
Thank you for your patience and researches tungdil !
The files SuperSU 2.23 would modify are most likely init.rc and sepolicy I guess. These are the two only files Glitch is potentially patching in the extracted ramdisk(from the current boot.img) when using root settings (fstab.flo is for F2FS partition mounting). Glitch doesn't come with its own ramdisk to enhance compatibility and will instead extract the current one, patch it with the options you've selected then repack it with the Glitch zImage in a new boot.img that'll be flashed at the end of the Aroma installer script. The selinux_version you have came either with the rom's default kernel or the previous kernel you flashed, not from Glitch itself.
I did ask in my previous post what ROM you were using because I thought you weren't using the same one both as internal and secondary. I may be right in thinking they're not the same when I'm looking at your selinux_version files content if you didn't switch kernels. You know what you did anyway.
It could indeed very well be something in Tassadar's build or some ramdisk changes he made breaking my patches. I didn't test his rom thinking that after an AOSP built rom and the official Google image were both getting root for me after applying Glitch it would work for every other AOSP based Lollipop roms. I may have been wrong.
I'll check Tassadar's build and search for a fix. Thanks again tungdil !
Hi again, Tk-Glitch!
Thanks for your comments! I appreciate having the chance to learn something.
.. the selinux_version you have came either with the rom's default kernel or the previous kernel you flashed, not from Glitch itself.
Click to expand...
Click to collapse
Oh, I see! I should have had a closer look at your flashable zip. After doing so, and looking into what "I found" I had to realize I made a mistake in picking the wrong boot image for the analysis (I have multiple secondary ROM's installed) In fact the selinux_version is, of course, the same (google/razor/flo:5.0/LRX21P/1570855:user/dev-keys) before and after flashing Glitch kernel.
I did ask in my previous post what ROM you were using because I thought you weren't using the same one both as internal and secondary
Click to expand...
Click to collapse
They should be the same (as mentioned forget about selinux-version I guess it was just too late yesterday night).
I tried to explain how I installed the ROM in my first post: "... For both cases [secondary and primary ROM] I used Tassadar's build. For the latter [primary] I copied the installed secondary ROM to the primary slot [using TWRP] ...".
If there is anything else I could do to help let me know! I'd be more than happy.
Best regards,
tungdil
@tungdil
I can understand better now, thanks for the confirmation.
My english is pretty limited to be honest so I may be understanding things wrong sometimes. I can also feel that I'm not able to express fully what I'd like to from time to time. It can be another limiting factor in some cases where my explanations or questions could be unclear for someone speaking better than I am.
I didn't find the time yet to check for Tassadar's build so I'm not in need for more for now. I'll get back to you as soon as I've made some progress on the matter - even if it's just to keep you informed - as it could also help someone else.
Thank you for your support and dedication.
Have a nice day tungdil
W.O.W
Thank you for this kernel!! It turns my adreno 320 to adreno 330
I'm on Lollipop (stock,rooted) and I'm having ghost touches with the latest version of glitch installed. I had an older version installed when I was on PA 4.6 but I did not have this issue. Any solutions?
Hey @Tk-Glitch,
First of all i want to say thank you for this wonderful Kernel .
I'm using the r307 Glitch Kernel in combination with Stock 5.0.2 rooted Rom.
The perfomance ist just awesome, unfortunately the battery is draining to quick compare to stock Kernel.
I would to ask what setup you're running and which settings you use. With CPU 1700mhz and GPU 450mhz i hardly reach 4-5 hours Sot of normal web browsing. Could you or anybody recommend me your personel settings.
Thank you in advance .
pranauk said:
I'm on Lollipop (stock,rooted) and I'm having ghost touches with the latest version of glitch installed. I had an older version installed when I was on PA 4.6 but I did not have this issue. Any solutions?
Click to expand...
Click to collapse
Strange to say the least since you didn't have issues previsouly. I've seen ghost touches on a friend's N7 and the only true fix was unplugging and replugging the display cable on the motherboard. BTW, ghost touches are almost always linked to the bad manufacturing of the N7.
I don't have any myself, on both r306 and r307, but my tab was never affected.
pk-sanja said:
Hey @Tk-Glitch,
First of all i want to say thank you for this wonderful Kernel .
I'm using the r307 Glitch Kernel in combination with Stock 5.0.2 rooted Rom.
The perfomance ist just awesome, unfortunately the battery is draining to quick compare to stock Kernel.
I would to ask what setup you're running and which settings you use. With CPU 1700mhz and GPU 450mhz i hardly reach 4-5 hours Sot of normal web browsing. Could you or anybody recommend me your personel settings.
Thank you in advance .
Click to expand...
Click to collapse
My battery is lasting much longer since Lollipop, so you may want to check for wakelocks.
These days I'm using 1.7GHz CPU, 600MHz GPU, -75mV on each CPU step, -100mV on each GPU step, ondemand governor, Glitchy L2/cache OC, and S2W/DT2W disabled.
Hope it helps !
@Tk-Glitch
Thank you for your answer Tk-Glitch, i will check the wakelocks.
And thank you for sharing your setup,
i will test it in my device. May you share how much mw Volt you need for 1,7Ghz and how i undervolted -100mw on GPU in all steps?
pk-sanja said:
@Tk-Glitch
Thank you for your answer Tk-Glitch, i will check the wakelocks.
And thank you for sharing your setup,
i will test it in my device. May you share how much mw Volt you need for 1,7Ghz and how i undervolted -100mw on GPU in all steps?
Click to expand...
Click to collapse
Of course mate.
My CPU needs 1.025V for 1.7GHz (PVS 3). For the GPU, I did make the GPU undervolting selectable (for all steps at once) in Aroma. You can tweak the values in the glitch script (init.d) if needed.
@Tk-Glitch
I see very nice , mine does 1050mV in 1,7Ghz not much differenc. Ups my mistake i thought the GPU undervolting in Aroma Installer is behaving like the CPU undervolting, only for the lowest Frequenz.
Thank you very much for you time, at home i will do a full factory reset and flash your kernel of top with the settings.
Have a nice day Tk-Glitch.
@pk-sanja
My pleasure.
Have a nice day as well pk-sanja