Related
hi there i got the new [9/28 build] for htc touch pro2. i installed 2 times right now because when i want to boot it...it says andboot/ doesnt exist.
i got riddin of all the android files before i installed it.
btw cant find the default of start file...
greetings
double check where your haret.exe is
Also, don't use the startup utility. I've found it's still not right... a few times it corrupted my startup.txt, and the update portion is still very broken.
screenshot
or maybe its the system.ext2 that i have to rename?
look i dont have it..in the attachment
you rename the "startup.txt" to "default text". so when it gets to that haret screen, just press run and itll work.
you mite have to do it after a fresh install if your startup.txt if its size is at a 0.
am i a noob
mmm k but like ive shown on the attachment screenshot...i dont have a "startup.txt" i got system.ext2 file
cheers
peruwan said:
mmm k but like ive shown on the attachment screenshot...i dont have a "startup.txt" i got system.ext2 file
cheers
Click to expand...
Click to collapse
That's you're problem then. You need a startup.txt... it kinda tells haret where everything is & how to set the system up basically...
There should be a STARTUPS folder. Grab the startup for your device, put it where you run haret from.
arrrghhh said:
That's you're problem then. You need a startup.txt... it kinda tells haret where everything is & how to set the system up basically...
There should be a STARTUPS folder. Grab the startup for your device, put it where you run haret from.
Click to expand...
Click to collapse
have you seen the screenshot on my last message i dont have such thing...i still got the backup from the older build is that a problem to copy paste?
peruwan said:
have you seen the screenshot on my last message i dont have such thing...i still got the backup from the older build is that a problem to copy paste?
Click to expand...
Click to collapse
I've seen your magical screenshot dude. I can't really see if that's the root of the SD or what, so that's why I mentioned a STARTUPS folder. Babijoee's builds used to have 'em, I think reef removed it so it wouldn't confuse people... You can reuse an old startup, just make sure that it's setup correctly. If it's not, it could cause issues. Which is why you may want to start over, why the heck do you not have a startup.txt?!?
theres no STARTUP file nor STARTUP folder in the root thats why ive shown the andboot/ ... ye there was a STARTUP file before i installed this build...
what kinda setup information should i put i got this one from the old
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2292
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=240 msmts_calib=0x9f.0x39a.0x35c.0x78 7x00.a11=500 msmvkeyb_toggle=off pmem.extra=1 force_cdma=0 gsensor_axis=2,1,3 pm.sleep_mode=2 acpuclock.oc_freq_khz=716800 rel_path=andboot hw3d.force=1 physkeyboard=rhod100_uk htc_hw.force_cdma=0 "
boot
peruwan said:
theres no STARTUP file nor STARTUP folder in the root thats why ive shown the andboot/ ... ye there was a STARTUP file before i installed this build...
what kinda setup information should i put i got this one from the old
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2292
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=240 msmts_calib=0x9f.0x39a.0x35c.0x78 7x00.a11=500 msmvkeyb_toggle=off pmem.extra=1 force_cdma=0 gsensor_axis=2,1,3 pm.sleep_mode=2 acpuclock.oc_freq_khz=716800 rel_path=andboot hw3d.force=1 physkeyboard=rhod100_uk htc_hw.force_cdma=0 "
boot
Click to expand...
Click to collapse
So you didn't want to go with a clean new build huh...? It looks OK, you've got the force_cdma command in there 2x for some reason... but I assume since they're both set to 0 that'll be fine. Make sure physkeyboard is set correctly. Other than that, it looks OK.
arrrghhh said:
So you didn't want to go with a clean new build huh...? It looks OK, you've got the force_cdma command in there 2x for some reason... but I assume since they're both set to 0 that'll be fine. Make sure physkeyboard is set correctly. Other than that, it looks OK.
Click to expand...
Click to collapse
i did a clean start i got ridding of everything. ye its ok thats in uk...i live in holland tho but its the same thing i guess
peruwan said:
i did a clean start i got ridding of everything. ye its ok thats in uk...i live in holland tho but its the same thing i guess
Click to expand...
Click to collapse
Alright... is it working now?
arrrghhh said:
Alright... is it working now?
Click to expand...
Click to collapse
nope still sayin the same message...i copy and paste it weird tho
peruwan said:
nope still sayin the same message...i copy and paste it weird tho
Click to expand...
Click to collapse
That may be your problem.
Just start completely over at square one. Format your SD and start with a clean new build - don't reuse anything. Something's obviously been buggered, and this is just a much easier method to fix it than actually trying to troubleshoot what you broke
arrrghhh said:
That may be your problem.
Just start completely over at square one. Format your SD and start with a clean new build - don't reuse anything. Something's obviously been buggered, and this is just a much easier method to fix it than actually trying to troubleshoot what you broke
Click to expand...
Click to collapse
Listen to arrrghhh,dude. Like he said you've obviously fudged it somewhere. Just uninstall it, delete all folders and start over from scratch. Maybe you should hard reset your device back to factory standards also. This might solve all you whoas
right..
dude it wasnt that obviously....now it wont even start the android project after clickin it it says a error.NET COMPACT FRAMEWORK IS INSTALLING ON YOUR SD CARD(which isnt?) IF THAT DOENST HELP? INSTALL IT AGAIN.
well what now? error code is: 2147479552 (80001000).
probably i need to install again the .net framework...but in cab version and the good version
cheers
peruwan said:
dude it wasnt that obviously....now it wont even start the android project after clickin it it says a error.NET COMPACT FRAMEWORK IS INSTALLING ON YOUR SD CARD(which isnt?) IF THAT DOENST HELP? INSTALL IT AGAIN.
well what now? error code is: 2147479552 (80001000).
probably i need to install again the .net framework...but in cab version and the good version
cheers
Click to expand...
Click to collapse
Don't use the cab bro... make it unnecessarily complicated IMHO. Plus, it's slow and fosters ignorance!!
ok which one should i download?? can you give me the link 2 download the framework for my device before ill destroy it
btw i downloaded the [10/4] update now i got 2 of those apps which i cant open
dont know why it created 2 android after the update cab.
peruwan said:
ok which one should i download?? can you give me the link 2 download the framework for my device before ill destroy it
btw i downloaded the [10/4] update now i got 2 of those apps which i cant open
dont know why it created 2 android after the update cab.
Click to expand...
Click to collapse
Well you can try to use the cab, but you seem to be having issues with it. So just download the rar... it's in the same location as the cab dude. Reef's site offers both the cab and rar installers on the same page..
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!
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!
Introduction
Here's a repackage and repost of my modified Random Boot Animation script. This was originally conceived by Nighthound many moons ago and was long abandoned. I picked it up and modified it for my Kang-o-rama ROM and the Optimus 2x.
And here it is for you Galaxy Nexus pleasure!
What it Does
There are various apps out there that can achieve the same result but this is a simple script that uses a random number generator to swap in a random boot animation each time you boot. The script runs one just before the animation and never again until you boot the next time.
You can have any number of animations that will randomise and you can also set a flag to have just one run without needing to delete the others.
How it Works
The script executes on startup, generates a random number, assigns this number to a boot animation stored in /data/local/bootanimations/, copies that animation to /data/local/bootanimation.zip and let's Android take over from there. Android will automatically prefer /data/local/bootanimation.zip to the one stored by your ROM in /system/media/.
You just put any valid boot animation in /data/local/bootanimations/ - calling it what you wish - and the script will do the rest. You should not try and call all of your boot animations "bootanimation.zip" - you need to give them a unique name.
Installation
Upon installing the script will automatically back up any custom animation you have in /data/local/ to /data/local/bootanimations/CustomAnimBackup.zip and this animation will be among those randomly selected.
Download one of the files below
Flash from recovery
Reboot and enjoy
Hit 'Thanks' below
System Requirements
This script will run on any custom Galaxy Nexus ROM with init.d support (which is most).
Notice
Some boot animations are distributed within another zip archive. You need to extract the bootanimation.zip file from that archive and rename it before you put it in the bootanimations directory.
Downloads
Update 08 July 2014
The script, in install.zip format has been attached to this post.
Single Animation Flag
If you want to view a single animation only you can do so without moving or changing any of the other files.
Simply Create a file called "bootanimation.use" in /data/local/bootanimations/. In this file place a single line with the filename of the boot animation you want to use. For example:
Code:
CustomAnimBackup.zip
When you want to revert to random animations again delete "bootanimation.use" from the directory.
Oh this is very cool! Will test it out shortly. Thanks.
I rather enjoy bootanimations. Thank you for this lovely script!
This script will run on any custom Galaxy Nexus ROM with init.d support (which is most).
Click to expand...
Click to collapse
Does this mean it doesn't work on rooted stock?
zombieflanders said:
Does this mean it doesn't work on rooted stock?
Click to expand...
Click to collapse
Correct. You need a custom kernel at minimum and a /system/etc/init.d/ directory.
djmcnz said:
Correct. You need a custom kernel at minimum and a /system/etc/init.d/ directory.
Click to expand...
Click to collapse
I'm on bigxie build 8 and Franco kernel - and this didn't work for me
I flashed the zip with animations and nothing seem to have happened
dhruvraj said:
I'm on bigxie build 8 and Franco kernel - and this didn't work for me
I flashed the zip with animations and nothing seem to have happened
Click to expand...
Click to collapse
That's odd. It does log what's happening at boot, know how to get a logcat?
djmcnz said:
That's odd. It does log what's happening at boot, know how to get a logcat?
Click to expand...
Click to collapse
Don't but would love to know. Some app? Script? Or cmd on terminal emulator?
Sent from my Galaxy Nexus using XDA App
dhruvraj said:
Don't but would love to know. Some app? Script? Or cmd on terminal emulator?
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
Via adb, it's quite easy:
adb logcat > log.txt
Will save the log to log.txt
Turn phone off, plug in, type command, start phone, wait till boot completes, ctrl+c to stop logging. Attach file here.
Remember to boot a few time first, just to make sure you're not getting random animations.
Thanks a lot mate!
Its attached
Also attached, are the screenshots (available at http://forum.xda-developers.com/showthread.php?t=1446531) that I am having a seperate problem with, not sure if you would know but just checking with you.
My screen is all screwed up when it boots, if I stop the launcher and restart it seems to be okay though. Any pointers to what it could be because (if it is glaringly visible in the log file) ?
dhruvraj said:
Thanks a lot mate!
Its attached
Also attached, are the screenshots (available at http://forum.xda-developers.com/showthread.php?t=1446531) that I am having a seperate problem with, not sure if you would know but just checking with you.
My screen is all screwed up when it boots, if I stop the launcher and restart it seems to be okay though. Any pointers to what it could be because (if it is glaringly visible in the log file) ?
Click to expand...
Click to collapse
Okay, it doesn't look like your ROM executes init.d scripts... which is required.
Is it this ROM: http://forum.xda-developers.com/showthread.php?t=1372376
If so that one's a little too close to stock... if you want to run a stock ROM that has init.d support I suggest a free MCR (MoDaCo) ROM.
Can't help with the crazy display sorry...
Very interested in this, but have a scrub question... so all I do is download then flash through cwm and I 'm all set?
Sent from my LTE GNex
Lizard King said:
Very interested in this, but have a scrub question... so all I do is download then flash through cwm and I 'm all set?
Sent from my LTE GNex
Click to expand...
Click to collapse
Correct as long as you're running a custom rom with init.d support.
If not, it will do no damage, it just won't work.
Just flashed... works flawlessly... awesome mod
Sent from my LTE GNex
I'm ok AOKP Milestone2 with franco kernal #12. works great! genius!
gaetawoo said:
I'm ok AOKP Milestone2 with franco kernal #12. works great! genius!
Click to expand...
Click to collapse
I'm on the same ROM and kernal and having difficulty with the script. Did you just copy the animation file to just /data/local/bootanimations or to /system/media as well?
- I ran the script
- Copied the few bootanimations I downloaded to /data/local/bootanimations
- Rebooted
- Black screen
raniosman said:
I'm on the same ROM and kernal and having difficulty with the script. Did you just copy the animation file to just /data/local/bootanimations or to /system/media as well?
- I ran the script
- Copied the few bootanimations I downloaded to /data/local/bootanimations
- Rebooted
- Black screen
Click to expand...
Click to collapse
When you say you "ran" the script, do you mean you flashed it in CWM? Hope so.
Other than that your steps are correct... nothing needs to go in /system/
The script logs to logcat... if you can get a boot logcat I can tell you if it's initiating.
djmcnz said:
When you say you "ran" the script, do you mean you flashed it in CWM? Hope so.
Other than that your steps are correct... nothing needs to go in /system/
The script logs to logcat... if you can get a boot logcat I can tell you if it's initiating.
Click to expand...
Click to collapse
Yea, I meant ran it on CWM. Phone is rooted and has the CWM recovery. Using AOKP Milestone2 custom rom with the franco kernal #12
But all I get is a blank black screen after the 'Google' word until the phone reaches the lock screen. None of the bootanimations are loading.
Trying it with the bootanimations:
ITCrowd, DoctorWho, and TheRoosevelt-Sharp-ICS
raniosman said:
Yea, I meant ran it on CWM. Phone is rooted and has the CWM recovery. Using AOKP Milestone2 custom rom with the franco kernal #12
But all I get is a blank black screen after the 'Google' word until the phone reaches the lock screen. None of the bootanimations are loading.
Trying it with the bootanimations:
ITCrowd, DoctorWho, and TheRoosevelt-Sharp-ICS
Click to expand...
Click to collapse
Okay, I'll need a log really to see what's happening... perhaps it's permissions on the /data/local/bootanimations directory.
if you can do this:
Code:
adb logcat > boot.log
From phone off all the way to home screen and attach it here I can look at it for you.
raniosman said:
Yea, I meant ran it on CWM. Phone is rooted and has the CWM recovery. Using AOKP Milestone2 custom rom with the franco kernal #12
But all I get is a blank black screen after the 'Google' word until the phone reaches the lock screen. None of the bootanimations are loading.
Trying it with the bootanimations:
ITCrowd, DoctorWho, and TheRoosevelt-Sharp-ICS
Click to expand...
Click to collapse
See my comment above as well but I have a question... did you create the /data/local/bootanimation directory yourself?
If so, delete it (copy the contents elsewhere temporarily) and reboot the phone. If the directory is re-created the script is firing. Then copy the files back in a reboot... that will fix any problems with the permissions that exist.
If the dir is not re-created automatically I'll need the log.