[RECOVERY] TWRP 2.6.3.0 touch recovery [2013-09-16]

[kaos420]

Re: [RECOVERY][EVO4GLTE] TWRP 2.4.1.0 with on-screen keyboard! [2013-2-1]

So I figured I would share. I updated to 2.4.1 I have as getting random reboots in the middle of rom installs. It got so bad my phone stated boot lopping. Would not even load recovery. Go to splash screen and reboot then. Thankfully bootloader was still accessible. I flashed back to 2.3.1 all my issues are fixed. Be careful will 2.4.1

Sent from magical jelly bean.

 

[Socrguru]

Try backing up your sd and the formating it threw your pc. Also when you have your sd in your pc or laptop look for a trash folder. You might have one that's full. Last time I helped a member with that error that what was causing it.

#Root-Hack_Mod*Always=LTE

I actually just started wiping by using a Superwipe script and flashing the ROM in the same install session... for some reason, that worked. I did put in a new SD card after getting the phone up and running (32GB Class 10 ) and haven't had any issues since yesterday.

 

[mrrogers1]

Re: [RECOVERY][EVO4GLTE] TWRP 2.4.1.0 with on-screen keyboard! [2013-2-1]

I actually just started wiping by using a Superwipe script and flashing the ROM in the same install session... for some reason, that worked. I did put in a new SD card after getting the phone up and running (32GB Class 10 ) and haven't had any issues since yesterday.

I'd just like to warn anyone with wiping issues, if the recovery is acting, what I like to call "wonky", don't keep trying to wipe using it. That CM issue you were having, I had on the last recovery series 2.3.0.0) upgrade, I keep trying to wipe with the recovery (I always use a Superwipe script but thought it was causing the flash issues with CM) and as it wasn't working right, it actually wiped my ext_sd. They fixed and updated the recovery so that (hopefully) would never happen ever again but it was a mounting issue in the recovery.....

Sent from my EVO LTE using Tapatalk 2!

THE TRUTH ABOUT ASSAULT WEAPONS

 

[Soundwavblike04]

Re: [RECOVERY][EVO4GLTE] TWRP 2.4.1.0 with on-screen keyboard! [2013-2-1]

Sorry for this noob question but how do you downgrade from 2.4.1.0?

Sent from my SPH-L900 using xda premium

 

[scottspa74]

Re: [RECOVERY][EVO4GLTE] TWRP 2.4.1.0 with on-screen keyboard! [2013-2-1]

Just DL an earlier version from their website linked in OP. Then fastboot flash it from PC or if you search way back in the thread (or click the paperclip icon in threads list) you can likely find a PJ75IMG of an earlier version to put on ext SD and flash thru bootloader.

From my Evo LTE, yup.

 

[Dees_Troy]

So, I messed around a bit with a ROM that was failing to install correctly with TWRP 2.4.1.0 and it seems that our troubles lie with a combination of the new kernel and the way that zips format /system. If I revert the kernel change then touch won't work with those that have installed the latest tp.img from HTC. The other solution is to have ROM makers change their zips to use:
run_program("/sbin/mke2fs", "-t", "ext4", "-m", "0", "/dev/block/mmcblk0p35");
instead of
format("ext4", "EMMC", "/dev/block/mmcblk0p35");

I'm not really sure what the best solution is for this problem though.

 

[Captain_Throwback]

So, I messed around a bit with a ROM that was failing to install correctly with TWRP 2.4.1.0 and it seems that our troubles lie with a combination of the new kernel and the way that zips format /system. If I revert the kernel change then touch won't work with those that have installed the latest tp.img from HTC. The other solution is to have ROM makers change their zips to use:
run_program("/sbin/mke2fs", "-t", "ext4", "-m", "0", "/dev/block/mmcblk0p35");
instead of
format("ext4", "EMMC", "/dev/block/mmcblk0p35");

I'm not really sure what the best solution is for this problem though.

Getting people to change their zips is a tall order, but if it's the only way for the recovery to work, it should be doable.

Anyone that's S-OFF can obviously downgrade their touch panel, since that's the only way that non-Sense ROMs will be runnable at this point anyway.

But for the S-ON folks, I'm not sure the best way to go, as they have fewer options. Once we have kernel source, will this still be an issue, or will a workaround likely be possible then?

 

[Dees_Troy]

The ROM that I was testing was MeanBean-v30-jewel-ltevo.zip. Further test reveals that this particular zip is using an older ICS-based update-binary. I built a new update-binary in CM10.0 which devs can find here. I further updated the updater-script slightly to use this:

format("ext4", "EMMC", "/dev/block/mmcblk0p35", "0", "/system");

The ROM installed fine after updating the update-binary in META-INF/com/google/android folder and making the updates to the format command that are required by the newer updater-binary. To me this is my recommended path, that developers update their updater-binary and scripts to JB methods. If you're lazy, you can use the call to mke2fs instead:

run_program("/sbin/mke2fs", "-t", "ext4", "-m", "0", "/dev/block/mmcblk0p35");

As an additional side note (and a pet peeve of mine), this ROM also does not unmount system before it performs the format command. This is unsafe and may cause problems with installing the zip. This line should come before the command to format:

unmount("/system");

So ROM devs, while you're updating things, make sure you unmount system before you format it please.

 

[Captain_Throwback]

The ROM that I was testing was MeanBean-v30-jewel-ltevo.zip. Further test reveals that this particular zip is using an older ICS-based update-binary. I built a new update-binary in CM10.0 which devs can find here. I further updated the updater-script slightly to use this:

format("ext4", "EMMC", "/dev/block/mmcblk0p35", "0", "/system");

The ROM installed fine after updating the update-binary in META-INF/com/google/android folder and making the updates to the format command that are required by the newer updater-binary. To me this is my recommended path, that developers update their updater-binary and scripts to JB methods. If you're lazy, you can use the call to mke2fs instead:

run_program("/sbin/mke2fs", "-t", "ext4", "-m", "0", "/dev/block/mmcblk0p35");

As an additional side note (and a pet peeve of mine), this ROM also does not unmount system before it performs the format command. This is unsafe and may cause problems with installing the zip. This line should come before the command to format:

unmount("/system");

So ROM devs, while you're updating things, make sure you unmount system before you format it please.

I think this is a product of Android Kitchen using an outdated update-binary. Maybe someone can find dsixda and see if he can make that minor update to the kitchen so that all the ROMs built by it will use the latest binary and parameters.

 

[scottspa74]

Re: [RECOVERY][EVO4GLTE] TWRP 2.4.1.0 with on-screen keyboard! [2013-2-1]

@Dees_Troy
I just wanna shout a real loud thanks for your work on this device and for looking into this.
Thanks!!! :thumbup:

From my Evo LTE, yup.

 

[mcwups1]

Re: [RECOVERY][EVO4GLTE] TWRP 2.4.1.0 with on-screen keyboard! [2013-2-1]

Downloaded newest version and now I can't get into the recovery. It freezes at splash screen then reboots.
On Decks 10.1 and downloaded from goo manager.

 

[il Duce]

Re: [RECOVERY][EVO4GLTE] TWRP 2.4.1.0 with on-screen keyboard! [2013-2-1]

Dees_Troy thanks for figuring it out.

Telling rom devs to fix this is EXACTLY the way to go.

It takes like 2 minutes to change a binary and a couple lines.

Awesome work!

 

[steal25]

The ROM that I was testing was MeanBean-v30-jewel-ltevo.zip. Further test reveals that this particular zip is using an older ICS-based update-binary. I built a new update-binary in CM10.0 which devs can find here. I further updated the updater-script slightly to use this:

format("ext4", "EMMC", "/dev/block/mmcblk0p35", "0", "/system");

The ROM installed fine after updating the update-binary in META-INF/com/google/android folder and making the updates to the format command that are required by the newer updater-binary. To me this is my recommended path, that developers update their updater-binary and scripts to JB methods. If you're lazy, you can use the call to mke2fs instead:

run_program("/sbin/mke2fs", "-t", "ext4", "-m", "0", "/dev/block/mmcblk0p35");

As an additional side note (and a pet peeve of mine), this ROM also does not unmount system before it performs the format command. This is unsafe and may cause problems with installing the zip. This line should come before the command to format:

unmount("/system");

So ROM devs, while you're updating things, make sure you unmount system before you format it please.

Thank you, We will implement and test these fixes right away.

 

[Kisakuku]

So now that the touch panel and failed install issues are squared away, any insight about the color cast in Aroma and the 5 second delay after initiating a reboot?

 

[eyeballer]

So now that the touch panel and failed install issues are squared away, any insight about the color cast in Aroma and the 5 second delay after initiating a reboot?

Color issues are because Aroma needs to be updated to run with the new HTC kernel, HTC changed color formats (now RGBX 8888 instead of RGB 565).

Not sure we have any idea about the reboot lag...

 

[exSD]

So I'm unable to use any of the touchscreen buttons on 2.3 in recovery. How do I downgrade my touchpanel firmware?

Edit - Nevermind. Just upgraded to 2.4 through Goo.

 

[thatotherguy..]

Re: [RECOVERY][EVO4GLTE] TWRP 2.4.1.0 with on-screen keyboard! [2013-2-1]

Isn't there a way to flash recovery threw bootloader?

Sent From My White cricKet LTEvo

 

[scottspa74]

Re: [RECOVERY][EVO4GLTE] TWRP 2.4.1.0 with on-screen keyboard! [2013-2-1]

Yeah there there is, but it needs to have the androidinfo.txt file in the zip. Search this thread for other PJ75IMG zips, remove the included recovery IMG and replace with the version you want. At least, that's my understanding. Also, I believe their site has the PJ75IMGs available.

Sent from my EVO using xda premium

 

[volk9029]

Re: [RECOVERY][EVO4GLTE] TWRP 2.4.1.0 with on-screen keyboard! [2013-2-1]

Isn't there a way to flash recovery threw bootloader?

Sent From My White cricKet LTEvo

Go to this link, scroll all the way down. There's PJ75img to flashed through recovery. I don't think it's the last one though.
http://teamw.in/project/twrp2/98

Sent from my lair.

 

[ohmarni]

Unable to wipe using 2.4.1.0

I apologize if this has already been discussed, but I did a search and didn't find anything. Wiping is simply not working for me. Well, somehow I managed to wipe out my SD card's internal files, but other than that, no wiping. I tried factory reset, wipe system, cache, dalvik-cache before installing the latest version of MeanBean and Milestone SuperJelly. Just not happening. Has anyone else had this problem? Know of a fix? I'd be very appreciative.