[rom] [01.07.14] Desire X DEODEXED Stock ROM 2.20.401.6 Jelly Bean Sense 4+ - HTC Desire X

Anyone can use this ROM as his base for Custom ROMs without asking for permission as long as they include credits wherever it is posted​
DEODEXED Stock Jelly Bean with Sense 4+ build 2.20.401.6 for Desire X​
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
neXus PRIME for the JB TWRP Recovery
Chainfire for the SuperSU
doiutzu for testing the updater-script and other tests
And anyone directly / indirectly contribute for this ROM​
DEODEXED stock ROM
hTC update build 2.20.401.6 (with Heartbleed fix)
Android Jelly Bean 4.1.1 (JRO03C)
Sense 4+
Kernel: 3.4.0-g2b619a5
rooted with SuperSU
Pre-installed Busybox
init.d support
Unlocked bootloader & Custom Recovery fixed for Jelly Bean
Recommended TWRP Recovery by neXus PRIME (http://forum.xda-developers.com/showpost.php?p=36714573&postcount=2)
For hboot 1.25.0002 (JB hboot)
Put the 2.20.401.6_Dodexed.zip on your sdcard
Make sure you already have the TWRP for JB hboot installed (NOT the stock recovery)
fastboot flash the attached boot.img for S-On DX (which comes with init.d feature)
Reboot to recovery
Make a full wipe is recommended but you can always try a dirty flash if your current ROM is stock (odex or deodexed)
Install the 2.20.401.6_Deodexed.zip as how you normally install a custom ROM
Reboot once completed and you are done

---

Old version 2.20.401.5_Deodexed.zip
http://sourceforge.net/projects/others/files/DX/2.20.401.5_Deodexed.zip/download

---

*DELETED*

---

*DELETED*

---

I still can't remove apps from system.I think something's wrong with my phone.

---

CrysiZ said:
I still can't remove apps from system.I think something's wrong with my phone.
Click to expand...
Click to collapse
Use Aroma File Manager. I've removed almost all google aps successfully. Rebooted several times and they do not appear again

---

CrysiZ said:
I still can't remove apps from system.I think something's wrong with my phone.
Click to expand...
Click to collapse
Which ROM ?
As mentioned before, you need a ROM with a properly installed busybox, root and init.d support.
See Part 1 : http://forum.xda-developers.com/showpost.php?p=40359126&postcount=250
See Part 2 & 3 : http://forum.xda-developers.com/showpost.php?p=40359148&postcount=251

---

And still can't edit build.prop

---

secthdaemon said:
And still can't edit build.prop
Click to expand...
Click to collapse
On my Deodexed ROM ?

---

ckpv5 said:
On my Deodexed ROM ?
Click to expand...
Click to collapse
Yes. Made changes via Build Prop Editor app, allowed changes via SuperSU, rebooted and no changes been applied

---

secthdaemon said:
Yes. Made changes via Build Prop Editor app, allowed changes via SuperSU, rebooted and no changes been applied
Click to expand...
Click to collapse
Here are the screenshots of build.prop editing that I made on a fresh installed deodexed ROM
I made changes to "ro.config.htc.enableCOTA=1" to "ro.config.htc.enableCOTA=0" with Root Explorer (you can see build.prop.bak is created after saving the changes.
And make a reboot, after reboot the "ro.config.htc.enableCOTA" still show 0 and the build.prop.bak is still there

---

Init.d seems not to be working
C:\Android>adb reboot recovery
C:\Android>adb push 12_test /system/etc/init.d/12_test
27 KB/s (57 bytes in 0.002s)
C:\Android>adb shell chmod 0755 /system/etc/init.d/12_test
C:\Android>adb reboot
C:\Android>adb shell cat /data/local/tmp/test.log
/system/bin/sh: cat: /data/local/tmp/test.log: No such file or directory
You can try this one.
hm...tried to to make changes with root explorer, rebooted, and all changes are gone and no bak file

---

secthdaemon said:
Init.d seems not to be working
C:\Android>adb reboot recovery
C:\Android>adb push 12_test /system/etc/init.d/12_test
27 KB/s (57 bytes in 0.002s)
C:\Android>adb shell chmod 0755 /system/etc/init.d/12_test
C:\Android>adb reboot
C:\Android>adb shell cat /data/local/tmp/test.log
/system/bin/sh: cat: /data/local/tmp/test.log: No such file or directory
You can try this one.
Click to expand...
Click to collapse
init.d is working fine... you can find zipalign.log in /data
BTW.. which boot.img that you are using ? the one that you posted ?
I gotta go now... will check later and update post #3 when I'm home.

---

ckpv5 said:
init.d is working fine... you can find zipalign.log in /data
BTW.. which boot.img that you are using ? the one that you posted ?
I gotta go now... will check later and update post #3 when I'm home.
Click to expand...
Click to collapse
Nope, I'm using your boot.img

---

secthdaemon said:
Nope, I'm using your boot.img
Click to expand...
Click to collapse
It works for me and others too that helped me.... so no idea why it is not working for you
So.. you don't have zipalign.log in /data folder ?

---

I'm gonna reflash your rom and boot.img just in case, I'll write about results.

---

secthdaemon said:
Use Aroma File Manager. I've removed almost all google aps successfully. Rebooted several times and they do not appear again
Click to expand...
Click to collapse
I can remove system apps and edit build.prop with aroma without disabled wp. So what? Why do i need this boot.img?
Sent from my HTC Desire X using xda premium

---

micu13 said:
I can remove system apps and edit build.prop with aroma without disabled wp. So what? Why do i need this boot.img?
Sent from my HTC Desire X using xda premium
Click to expand...
Click to collapse
You don't have to and you don't need the boot.img when you are comfortable doing all these stuff in recovery
Most people prefer to do things not in recovery as most people use recovery just to do nandroid backup/restore and flashing zips. That is why flar2 comes out with a workaround not only for DX but also on other devices such as
HTC One - http://forum.xda-developers.com/showthread.php?t=2235085 & http://forum.xda-developers.com/showthread.php?t=2233665

---

secthdaemon said:
I'm gonna reflash your rom and boot.img just in case, I'll write about results.
Click to expand...
Click to collapse
Let us know the result... as I'm afraid it is the JB hboot thing as I can't test it as I'm on ICS hboot.
If yes.. then we may need the kernel source then only Dev like neXusPRIME and atis112 can do their magic.
Ahh... how I wish I am on JB hboot then I can test a lot of things

---

ckpv5 said:
Which ROM ?
As mentioned before, you need a ROM with a properly installed busybox, root and init.d support.
See Part 1 : http://forum.xda-developers.com/showpost.php?p=40359126&postcount=250
See Part 2 & 3 : http://forum.xda-developers.com/showpost.php?p=40359148&postcount=251
Click to expand...
Click to collapse
Yes,on your deodex rom