• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Testers for 4.2.2

D

Deleted User

Guest
Hello guys, I am a dev for CodefireX, a wonderful android ROM. In my spare time I have gotten my kernel ready for the design 4g and now have codefire for you guys. I would like to know who's interested in testing and letting me know what's broken. I would like to state I don't have the device so I don't even know if it will boot. Anyways, post here if your willing to test. I need to do this privately at first so that I know it will boot. After that thread will change to release and be open for download.

Thanks guys!
 
I am on boost , running twitch-kingdom (Leedroid tweaks) & 2Fasts v5 kernel ...
Would be glad 2 test , I am just a noob , but I will try ! And thank you 4 your contribution 2 our phone
 
Okay guys, I'm firing off a new build (the one I built earlier I forgot to put in my download folder, yeah I know I'm smart! ;) ) I will send each of you a private message with a download link in it. If it boots, and works for the most part, I'll post the link here and update the OP. Thank you all for helping me support this very worthy device. I would put it hand and hand with my One V.
 
I have PM'd all of the testers. I will be waiting on there reply. No more beta testers will be accepted since I will release it as long as it boots.
 
Status 0 error using CWM 5.0.2.7. Unable to apply the update.
Trying CWM 6... Same.
I checked out the script and it looks like it will work (compared with CM-unofficial script). Perhaps an update-binary problem?
 
Id say it is the update binary if you can try a known working one id apprecate it. Dont got the device, or I'd do it :)

PS pulling the recovery.log would help me a ton :)
 
Replaced with update-binary from evervolv. The script runs clean!
Formatting data and cache, then rebooting.
Upon boot I get the HTC logo, then a black screen. It kicks off a reboot and goes back to recovery. Damn. Likely a kernel issue.

Out of runway for tonight. I've dropped /proc/last_kmsg here if you'd like a look at it, and will be happy to help some more tomorrow.

Thanks a TON!

(EDIT: When I looked at the kmsg file, it looks like it never flashed the boot.img. I tested by going back to stock /system only. Sure enough, it booted and works. I'll see what's up with that when I get a chance tomorrow unless someone else gets to it first.)
 
LouZiffer said:
Replaced with update-binary from evervolv. The script runs clean!
Formatting data and cache, then rebooting.
Upon boot I get the HTC logo, then a black screen. It kicks off a reboot and goes back to recovery. Damn. Likely a kernel issue.

Out of runway for tonight. I've dropped /proc/last_kmsg here if you'd like a look at it, and will be happy to help some more tomorrow.

Thanks a TON!

(EDIT: When I looked at the kmsg file, it looks like it never flashed the boot.img. I tested by going back to stock /system only. Sure enough, it booted and works. I'll see what's up with that when I get a chance tomorrow unless someone else gets to it first.)
Click to expand...

I don't know if this is true to your device or not, but it is for mine. You must use fastboot to flash the kernel. This means extract your boot.img from the zip then boot to fastboot from recovery right after the rom flash and use fastboot flash boot boot.img. This should flash the boot.img, and is needed on alot of htc devices due to lockdowns
 
simonsimons34 said:
I don't know if this is true to your device or not, but it is for mine. You must use fastboot to flash the kernel. This means extract your boot.img from the zip then boot to fastboot from recovery right after the rom flash and use fastboot flash boot boot.img. This should flash the boot.img, and is needed on alot of htc devices due to lockdowns
Click to expand...

boot.img can be flashed from CWM on this phone. Other scripts use the same method of extracting the file to mmc block 0 partition 22 that you're using. I'm not clear on why it didn't yet. Would have tried manually, but I'm out of time for tonight and needed to restore my backup to use the phone. Hopefully another tester rotates in with some time in the meantime. At least we know a different update-binary <- is needed.

I'm on contract with this for another year and it's one of those phones that "just works" - zero quirks or issues at all, so will use every scrap of time that I have available to help get a later version of Android on it.
 
Kernel should be 3.0.64 version. I keep my kernels up to date. I am curious if it flashed though. It may have resulted back to the prebuilt kernel
 
Got the boot.img flashed manually this morning, Simon. (Along with applying the .zip, which does update /system and performs the rest as it should.) We're closer, but it's boot looping. Here's the latest last_kmsg. I've done a cursory look and see the kernel panic in there. Posting it first before looking closer.

Here also is the recovery.log after applying the .zip.
 
Okay panic on init gave me an idea. I'm only available on weekends but try to flash the evervolv 4.2 kernel
 
Whats the latest on this? I've tried everything twice and can't even get it to fully install. Replaced the boot.img and update binary and still nothing.
 
ok so i swapped out the boot.img, update binary and modules for the evervolv ones. correct me if im wrong, but updating hte modules should update the kernel, right? im still pretty new to this so bare with me...
 
You must log in or register to reply here.
Back
Top Bottom