[HTC EVO 3D] therealeasterbunny:
Hi all,

I'm having a bit of trouble and have spent the past three days trying to get KitKat (LiquidSmooth 3.2) on my HTC EVO 3D (GSM - I think!) phone, here in the UK ("England").

Also, before I started poking my phone, I knew nothing of how to flash EVO3D or Android phones in general, but I am not new to the hacking scene in general as I am a computer programmer with over 30 years tinkering experience from the days of the Commodore PET EPROMS through to poking Raspberry PIs and making computer games for all kinds of operating systems over the years so have a bit of IT knowledge.

But this thing is pecking my head and I'm determined to get it to work by fair means or foul.

A bit of background as I know "its not working - HELP!" doesn't help the cause haha....

I bought my phone off eBay over 12 months ago and it has worked flawlessly ever since with Ice Cream Sandwich. Then my kids said "Hey, get Pokemon Go!" - but min reqs I believe are Android 4.4 - so a bit of research told me I could get Liquid Smooth v3.2 for my EVO3D as a custom ROM. Cool! Or so I thought.

Before I started fiddling last Saturday my EVO 3D status was:

***LOCKED***

SHOOTER-U PVT SHIP S-ON RL

HBOOT-1.53.0007

RADIO-11.25.3504.06_M

OpenDSP-v02.6.0.2226.00.0202

eMMC-boot

May 22 2012,01:06:07

Android version 4.0.3

HTC Sense 3.6

Software number 3.28.401.1

Then I started to tinker. I delved into the world of:

S-ON and S-OFF

Dalviks, cache, system.

ROMs.

Liquismooth, Cyanogen, Rooting, TWRP, Ext4, HBOOT versions, Yoda, Flashboots, CWM, PhilzRecovery etc.

I have watched a bucket load of videos on youtube, surfed various sites and done bucket loads of updates, applied CWM, TWRP, PhilzTouch recovery and am now reasonably familiar with the whole process of getting things done.

In the process I have soft bricked my phone and recovered it with some of the above recovery tools so I am now back up and running with IceCream Sandwich. I can make calls and the phone seems to be fine. However I have not managed to get on LiquidSmooth.

I do have the ROM for it, and it is the NIGHTLY GSM rom. I have edited the ZIp file with 7Zip, and opened up the updater-script file and confirmed that the ROM is for the GSM version of the EVO 3D as I can see it checks for the device being a SHOOTERU:

assert(getprop("ro.product.device") == "shooteru" || getprop("ro.build.product") == "shooteru");

But, when I try to apply the ROM ZIP file I get the forever infuriating STATUS 7 error. (I have tried to apply the ROM with all links of recovery ROMs and all versions. but alas, STATUS 7.

So, I thought to myself, take out the ASSERT and reflash. Which it did! "SUCCESSFUL!"

YAY!

but no.

On reboot it just froze at boot up screen. So I put it back to ICS to check phone was recoverable and yes it was.

So .. I thought ... "Hey, if its failing the SHOOTERU check (STATUS 7 = ROM not for this phone), why don't I ask the phone to report what it thinks it is? (After all it should be SHOOTER-U right? Because that's what it says then I boot up in recovery mode.

But no.

I modified updater-script with some code to report out what version the phone reports as. My code I input before the ASSERT line was:

ui_print("RO PRODUCT DEVICE is ...");
ui_print(getprop("ro.product.device"));
ui_print(" ");
ui_print("RO BUILD PRODUCT is ...");
ui_print(getprop("ro.build.product"));
ui_print(" ");

... and lo and behold, the phone is reporting itself as SHOOTER, not SHOOTER-U!

So, this is why the recovery tools are all saying "STATUS 7".

So, the question, ("finally!" I hear you cry!) ...

Why is my EVO 3D GSM phone, displaying SHOOTER-U on Recovery boot screen (the first white screen you see when pressing [Vol-]+[Power]), but then in the updater script, when you try to apply the ROM, it says the phone is returning the string SHOOTER from the getprop("ro.product.device") and getprop("ro.build.product") function calls?

And, is there a fix?

Phone now restored and working on ICS with:

PG86IMG_3.28.401.1.zip

yodas_ICS_deodex.zip

Current phone status on recovery boot:

*** UNLOCKED ***

SHOOTER-U PVT SHIP S-ON RL

HBOOT-1.53.0007

eMMC-boot

May 22 2012,01:06:07

But curious: no RADIO or OPENDSP information now?

Many thanks for listening. I hope you can help.