[ROOT] How To Root Rogers HTC One X Qualcomm S4 (for Windows, Mac and Linux)

Search This thread
By:
Advanced…
paulobrien

paulobrien

Senior Member
Nov 6, 2003
5,276
7,321
Norwich
www.MoDaCo.com
AS MY EVITA IS CURRENTLY BOOTLOADER LOCKED, THIS SUPERBOOT IS FOR TEST PURPOSES ONLY. USE AT YOUR OWN RISK!

Superboot is a boot.img that when booted, will root your device the first time you boot (installing su and the superuser APK). No need to flash any partitions, no need to mess around with ADB, no messing with the contents of your data partition, no overwriting the shipped ROM on your device, just boot the boot image using the instructions below and you're done!

Download
  • Superboot r2 - DOWNLOAD - MD5: 39a02275706d4b034c3c185b5b9b1a82
The superboot image is also 'insecure', allowing you to use 'adb remount' as well as having full ADB root access to your device until such time as you reboot after running this process (it's a non permanent ADB root as it's a 'fastboot boot' and not a 'fastboot flash' but it IS a permanent root in all other regards!).

How to use Superboot - Windows, Linux and OSX
  • Ensure your bootloader is unlocked using the htcdev unlock process
  • Download the Superboot zip file above and extract to a directory
  • Put your device in bootloader mode - Turn off the phone then turn on with the 'volume down' button pressed to enter the bootloader, then press the power button again to enter fastboot.
  • WINDOWS - double click 'install-superboot-windows.bat'
  • MAC - Open a terminal window to the directory containing the files, and type 'chmod +x install-superboot-mac.sh' followed by './install-superboot-mac.sh'
  • LINUX - Open a terminal window to the directory containing the files, and type 'chmod +x install-superboot-linux.sh' followed by './install-superboot-linux.sh'
P

PS Details on how to donate should you wish to do so are in the download topic at MoDaCo.
 
Last edited:
  • Like
Reactions: navsidhu700, JonnyPJohnston, zakhir_n and 19 others
J

JSLEnterprises

Senior Member
Apr 26, 2011
1,349
1,360
Buenos Aires
Superboot confirmed working.
manually install superuser in /superboot/ and delete the folder afterwards and update su binary (or the toast will hang)


now care to share your repack methods?

I was just about to try using the same method xperia users were using for their ics builds... and then you posted your superboot... beaten too the punch. Cheers at getting it though.
 
Last edited:
paulobrien

paulobrien

Senior Member
Nov 6, 2003
5,276
7,321
Norwich
www.MoDaCo.com
JSLEnterprises said:
Superboot confirmed working.
manually install superuser in /superboot/ and delete the folder afterwards and update su binary (or the toast will hang)


now care to share your repack methods?

I was just about to try using the same method xperia users were using for their ics builds... and then you posted your superboot... beaten too the punch. Cheers at getting it though.
Click to expand...
Click to collapse
The folder disappears on the next reboot.

P
 
sk806

sk806

Senior Member
Jan 30, 2005
1,973
1,441
Rye, New York
JSLEnterprises said:
time to start up on a rom. ;D

... hopefully we'll have a cwm port by the time I've finished v1.0
Click to expand...
Click to collapse

so the 1.73 Rogers RUU is the shipping firmware for the Evita, is that everyone's understanding? The AT&T is also the same, except for branding, correct? I am going to use the boot.img from the Rogers 1.73 release in porting the recovery. Please let me know if you know there is something amiss. thanks.

Steve
 
  • Like
Reactions: sabesh
J

JSLEnterprises

Senior Member
Apr 26, 2011
1,349
1,360
Buenos Aires
sk806 said:
so the 1.73 Rogers RUU is the shipping firmware for the Evita, is that everyone's understanding? The AT&T is also the same, except for branding, correct? I am going to use the boot.img from the Rogers 1.73 release in porting the recovery. Please let me know if you know there is something amiss. thanks.

Steve
Click to expand...
Click to collapse

Yep. And a few missing apk's. Comparing the two. The proprietary carrier apps, plus amazon, boot and down annimations, security certs, gps.conf, minor variance in the build.prop, and the /cid and /mns default.xml's are pretty much the only varying things that I've noticed so far ... Also an xml in /framework/services.jar. If you replace the at&t services.jar with the one from the rogers version, you'll have the selectable 3g/hspa+ or 3g/hspa+/LTE auto options that are not available to at&t users (turn off lte use)

... These are just preliminary comparisons.

If you want to revert to stock boot and down animations just edit /system/customization/mns/default.xml amd change the file names at the bottom. Eg. Rogers_bootanimation.zip to hTC_bootup_one.zip. rogers included their own animations and left the stock ones in resource folder as well. So its pretty easy to debrand & debloat the rogers version.
 
Last edited:
D

danada

Senior Member
Apr 20, 2012
83
23
Toronto
sk806 said:
so the 1.73 Rogers RUU is the shipping firmware for the Evita, is that everyone's understanding? The AT&T is also the same, except for branding, correct? I am going to use the boot.img from the Rogers 1.73 release in porting the recovery. Please let me know if you know there is something amiss. thanks.

Steve
Click to expand...
Click to collapse

The 1.73 Rogers RUU is indeed the shipping firmware for Rogers phones. The AT&T version has slight differences (no LTE Toggle, tethering), though these shouldn't cause an issue.

~dan
 
sk806

sk806

Senior Member
Jan 30, 2005
1,973
1,441
Rye, New York
danada said:
The 1.73 Rogers RUU is indeed the shipping firmware for Rogers phones. The AT&T version has slight differences (no LTE Toggle, tethering), though these shouldn't cause an issue.

~dan
Click to expand...
Click to collapse

Thanks. I will check the partitions info on that and use for build.

I am going to start build now. Will let you know how it goes. I should be getting my ATT One X tomorrow, so I will test (unless there are some brave souls out there...;)).

Steve
 
J

JSLEnterprises

Senior Member
Apr 26, 2011
1,349
1,360
Buenos Aires
danada said:
The 1.73 Rogers RUU is indeed the shipping firmware for Rogers phones. The AT&T version has slight differences (no LTE Toggle, tethering), though these shouldn't cause an issue.

~dan
Click to expand...
Click to collapse

Lte toggle = services.jar (/system/framework) & settings.apk (/system/app)

also, deleting TetheringGuard.apk from the AT&T unit will enable the tethering ability.
 
Last edited:
  • Like
Reactions: jamesolo
sk806

sk806

Senior Member
Jan 30, 2005
1,973
1,441
Rye, New York
JSLEnterprises said:
Yep. And a few missing apk's. Comparing the two. The proprietary carrier apps, plus amazon, boot and down annimations, security certs, gps.conf, minor variance in the build.prop, and the /cid and /mns default.xml's are pretty much the only varying things that I've noticed so far ... Also an xml in /framework/services.jar. If you replace the at&t services.jar with the one from the rogers version, you'll have the selectable 3g/hspa+ or 3g/hspa+/LTE auto options that are not available to at&t users (turn off lte use)

... These are just preliminary comparisons.

If you want to revert to stock boot and down animations just edit /system/customization/mns/default.xml amd change the file names at the bottom. Eg. Rogers_bootanimation.zip to hTC_bootup_one.zip. rogers included their own animations and left the stock ones in resource folder as well. So its pretty easy to debrand & debloat the rogers version.
Click to expand...
Click to collapse

Thanks. This doesn't look like anything that would affect boot.img, good to know. Hope ATT won't mind if I brick my device tomorrow, lol.
 
R

Red5

Guest
You guys are doing a fantastic job for both Rogers and AT&T users! Thanks!
 
B

bongd

Senior Member
Jun 20, 2010
1,533
170
Great job, guys!

I'm at work and can't install the USB drivers to operate my device in the Bootloader/Fastboot but you can be damned sure that I'm eager to go home and flash this!!! Been waiting so impatiently for root and you guys did the trick. Thanks so much :)
 
You must log in or register to reply here.

Similar threads

kennethpenn
  • Locked
[ROOT] One Click HTC One X (AT&T/Rogers/Others) (Win/Mac/Linux)
Replies
870
Views
773K
orangekid
orangekid
h8rift
[ROM][4.1.2] CyanogenMod 10 for HTC One XL
Replies
8K
Views
2M
exad
exad
h8rift
[ROM][4.2.2][NIGHTLIES] CyanogenMod 10.1 for HTC One XL
Replies
4K
Views
773K
TonyStark R.I.P.
TonyStark R.I.P.
Turge
  • Poll
[ROM][SEP 22] Team Venom ViperXL 4.2.0 | Sense 5 | Venom Tweaks | OTA Updates
Replies
19K
Views
2M
T
Tmobilefan906
D
[ROOT] HTC One X AT&T 2.20 Firmware - X-Factor root exploit
Replies
584
Views
358K
J
jerryspring

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 22
    paulobrien
    paulobrien
    AS MY EVITA IS CURRENTLY BOOTLOADER LOCKED, THIS SUPERBOOT IS FOR TEST PURPOSES ONLY. USE AT YOUR OWN RISK!

    Superboot is a boot.img that when booted, will root your device the first time you boot (installing su and the superuser APK). No need to flash any partitions, no need to mess around with ADB, no messing with the contents of your data partition, no overwriting the shipped ROM on your device, just boot the boot image using the instructions below and you're done!

    Download
    • Superboot r2 - DOWNLOAD - MD5: 39a02275706d4b034c3c185b5b9b1a82
    The superboot image is also 'insecure', allowing you to use 'adb remount' as well as having full ADB root access to your device until such time as you reboot after running this process (it's a non permanent ADB root as it's a 'fastboot boot' and not a 'fastboot flash' but it IS a permanent root in all other regards!).

    How to use Superboot - Windows, Linux and OSX
    • Ensure your bootloader is unlocked using the htcdev unlock process
    • Download the Superboot zip file above and extract to a directory
    • Put your device in bootloader mode - Turn off the phone then turn on with the 'volume down' button pressed to enter the bootloader, then press the power button again to enter fastboot.
    • WINDOWS - double click 'install-superboot-windows.bat'
    • MAC - Open a terminal window to the directory containing the files, and type 'chmod +x install-superboot-mac.sh' followed by './install-superboot-mac.sh'
    • LINUX - Open a terminal window to the directory containing the files, and type 'chmod +x install-superboot-linux.sh' followed by './install-superboot-linux.sh'
    P

    PS Details on how to donate should you wish to do so are in the download topic at MoDaCo.
    View
    2
    paulobrien
    paulobrien
    I will post the details tomorrow, sorry it's getting late here and i've had a helluva day!

    P
    View
    2
    sk806
    sk806
    ohcanada said:
    this is my friend's rogers one x print out

    shell@android:/ $ cat /proc/emmc
    cat /proc/emmc
    dev: size erasesize name
    mmcblk0p23: 000ffa00 00000200 "misc"
    mmcblk0p22: 00fffe00 00000200 "recovery"
    mmcblk0p21: 01000000 00000200 "boot"
    mmcblk0p33: 67fffc00 00000200 "system"
    mmcblk0p30: 00140200 00000200 "local"
    mmcblk0p34: 0ffffe00 00000200 "cache"
    mmcblk0p35: 97fffe00 00000200 "userdata"
    mmcblk0p26: 01400000 00000200 "devlog"
    mmcblk0p28: 00040000 00000200 "pdata"
    mmcblk0p36: 27be00000 00000200 "fat"
    mmcblk0p31: 00010000 00000200 "extra"
    mmcblk0p17: 02d00000 00000200 "radio"
    mmcblk0p18: 00a00000 00000200 "adsp"
    mmcblk0p16: 00100000 00000200 "dsps"
    mmcblk0p19: 00500000 00000200 "wcnss"
    mmcblk0p20: 007ffa00 00000200 "radio_config"
    mmcblk0p24: 00400000 00000200 "modem_st1"
    mmcblk0p25: 00400000 00000200 "modem_st2"


    Here's mount:

    shell@android:/ $ mount
    mount
    rootfs / rootfs ro,relatime 0 0
    tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
    devpts /dev/pts devpts rw,relatime,mode=600 0 0
    proc /proc proc rw,relatime 0 0
    sysfs /sys sysfs rw,relatime 0 0
    /dev/block/mmcblk0p33 /system ext4 ro,relatime,user_xattr,barrier=1,data=ordered 0 0
    /dev/block/mmcblk0p35 /data ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered,noauto_da_alloc 0 0
    /dev/block/mmcblk0p34 /cache ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0
    /dev/block/mmcblk0p26 /devlog ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0
    /sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
    none /acct cgroup rw,relatime,cpuacct 0 0
    tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
    tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
    none /dev/cpuctl cgroup rw,relatime,cpu 0 0
    /dev/block/mmcblk0p17 /firmware_radio vfat ro,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=i
    so8859-1,shortname=lower,errors=remount-ro 0 0
    /dev/block/mmcblk0p18 /firmware_q6 vfat ro,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8
    859-1,shortname=lower,errors=remount-ro 0 0
    /dev/block/mmcblk0p19 /firmware_wcnss vfat ro,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=i
    so8859-1,shortname=lower,errors=remount-ro 0 0
    tmpfs /data/secure/data tmpfs rw,relatime,mode=755,gid=1000 0 0
    DxDrmServerIpc /data/DxDrm/fuse fuse.DxDrmServerIpc rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other 0 0
    htcfs /data/htcfs fuse.htcfs rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other 0 0
    /dev/block/vold/179:36 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,
    allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
    /dev/block/vold/179:36 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=
    0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
    tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
    /dev/block/dm-0 /mnt/asec/com.spryfox.tripletown-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,
    codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
    Click to expand...
    Click to collapse

    awryter said:
    dev: size erasesize name
    mmcblk0p23: 000ffa00 00000200 "misc"
    mmcblk0p22: 00fffe00 00000200 "recovery"
    mmcblk0p21: 01000000 00000200 "boot"
    mmcblk0p33: 67fffc00 00000200 "system"
    mmcblk0p30: 00140200 00000200 "local"
    mmcblk0p34: 0ffffe00 00000200 "cache"
    mmcblk0p35: 97fffe00 00000200 "userdata"
    mmcblk0p26: 01400000 00000200 "devlog"
    mmcblk0p28: 00040000 00000200 "pdata"
    mmcblk0p36: 27be00000 00000200 "fat"
    mmcblk0p31: 00010000 00000200 "extra"
    mmcblk0p17: 02d00000 00000200 "radio"
    mmcblk0p18: 00a00000 00000200 "adsp"
    mmcblk0p16: 00100000 00000200 "dsps"
    mmcblk0p19: 00500000 00000200 "wcnss"
    mmcblk0p20: 007ffa00 00000200 "radio_config"
    mmcblk0p24: 00400000 00000200 "modem_st1"
    mmcblk0p25: 00400000 00000200 "modem_st2"
    Click to expand...
    Click to collapse

    Excellent. Thanks.

    Now I'm gonna finish up the BoardConfig.mk and build this thing...
    View
    2
    J
    JSLEnterprises
    time to start up on a rom. ;D

    ... hopefully we'll have a cwm port by the time I've finished v1.0
    View
    2
    sk806
    sk806
    JSLEnterprises said:
    time to start up on a rom. ;D

    ... hopefully we'll have a cwm port by the time I've finished v1.0
    Click to expand...
    Click to collapse

    I'm working on one today...
    View

New posts