Closed GoogleCodeExporter closed 8 years ago
It seems that kernel does not boot. adb shell complains: error: device not found
when phone displays HTC logo and nothing more. I tried R9 as well. Is problem in Hboot version or perhaps S-ON?
Original comment by xhejt...@gmail.com
on 19 Sep 2012 at 9:00
OK, the problem seems to be in this:
The problem with this on an s-on phone is that the boot partition is unwritable
in recovery mode so it fails to update. There is a workaround where you can
edit the updater-script file in the flashable zip so it doesn't attempt to
flash the boot partition and delete the temp dir, so the user can then flash it
manually through fastboot, but if you're at a level to do this, it's much
easier to just s-off and avoid the hassle.
Maybe worth of put this in FAQ that *unlocked s-on* phone is incompatible with
this rom as is and extra workaround is needed.
Original comment by xhejt...@gmail.com
on 21 Sep 2012 at 11:25
So, steps to get it work:
1) Download jellytime zip
2) extract boot.img from the zip
3) Put jellytime.zip on sdcard
4) reboot into recovery
5) do full backup
6) wipe data/cache
7) install jellytime.zip from sdcard
8) reboot into hboot
9) select fastboot
10) attach phone to PC
11) do on PC: fastboot flash boot boot.img (that boot.img extracted from
jellytime.zip)
12) do on PC: fastboot reboot
it boots jellytime rom.
But beware, clockwork recovery is unable to restore boot.img!! If you want to
restore your previous system, you need to restore it via clockwork recovery and
then boot into fastboot and flash boot.img separately. as in steps 11 and 12,
using backedup boot.img from step 5. You can find it on sdcard if using
clockworkmod recovery.
Original comment by xhejt...@gmail.com
on 21 Sep 2012 at 6:08
Original comment by MonsterBandit04
on 25 Sep 2012 at 3:38
I'm having the same issue with JellyTime_42_Release_6.1.
After flashing the boot.img from JellyTime I get a black screen after the white
HTC screen and afterwards it boots into clockworkmod recovery.
The only thing missing from post #3 is step 12) do on PC: fastboot reboot ...
instead I triggered the reboot from the phone... should this make a difference?
Is there any other known issue
Original comment by Joerg.Wo...@gmail.com
on 14 Mar 2013 at 10:47
Original issue reported on code.google.com by
xhejt...@gmail.com
on 18 Sep 2012 at 9:09