Quote:
Originally Posted by fishingmedic
Alright, just tried this again, put a brand new clean FRX04 build w/ the latest rootfs that was just released last night and this kernel, let it boot, and just sit for a few, at which time, without me touching it, it booted back to winmo. Before I do anything further (like run the freaking phone over with my truck...) do you want me to attempt to get a log on it or will one have not even been created as I'm not sure exactly how far the process went?
Edit: I changed a couple of things in the startup.txt and played around with it a bit and giving it another shot. Maybe I should try with the actual package first, then after it boots, go back to winmo, swap in the new rootfs and test kernel?
Edit part 2: Still reboots back to winmo and reboots back before I can get a log or anything. forget it, I just threw it at my neighbor, I'm going back to a freaking flip phone... lol. I'm gonna try booting just FRX04 out of the box and then make changes with rootfs and kernel.
So far so good with clean FRX04...
|
Fish, seems like you have been getting a lot of resets to WinMo issue lately, with Tiad8's build and FRX04. Hmmm... I had that issue the first time I tried FRX04 with 1253 OC'ed on first boot but it works fine after the first boot. I'm currently using FRX04, with 2/9 rootfs, and this kernel OCed at 614Mhz and it's pretty solid. Got the panel 14 type in my dmesg. When my phone goes to sleep, I still have to press the button several times to really wake it up. I'm using an app called nolock because I can't stand the slider to unlock screen that occurs everytime my phone wakes up; saves me a couple precious seconds so I can use my phone right away
.
arrrghhh, besides ADB, DroidExplorer or the other debugging methods you guys are using, is there a way we can set up a telnetd or sshd daemon with which we log into? The builtin terminal is good but the lack of some keys (>, |, tab, etc) makes it hard to play with (I guess I can use manekineko's rootfs with the added key functions).