Hi folks!
Until such time as an official ClockworkMod recovery is available, I have created an interim (non official) ClockworkMod Touch release. Please note that the One X doesn't seem to enable access to USB when booted as recovery (proven by flashing the recovery partition with the insecure boot), so you will not be able to use ADB etc. at this time.
INSTALL AND USE AT YOUR OWN RISK!
Your bootloader must be unlocked via htcdev.com to install this.
To use, either flash via fastboot ('fastboot flash recovery r1-modaco-recovery-clockwork-touch-endeavoru.img') or boot directly ('fastboot boot r1-modaco-recovery-clockwork-touch-endeavoru.img').
MOD EDIT: warning!!! old recovery with charging issues and NO USB Mount use latest recovery from here or TWRP
I have also uploaded the stock recovery should you wish to flash it (e.g. for OTA).
Enjoy!
DOWNLOAD - MD5: f47ebe81400c00ddefc0499d2a18b9fd
DOWNLOAD - MD5: 4af6f2b658d2e13f72e928a72fcde9cd
P
PS If you find this useful, details on how to donate should you wish to do so are available in the MoDaCo topic.
You are the man!
What works actually?
I did a backup and restore, I imagine most of the functions should work. The lack of USB (and therefore ADB) is annoying (i'm investigating), but that aside you should do all the stuff you need to.
Obviously it's a quick hack-up so use with care!
P
paulobrien said:
I did a backup and restore, I imagine most of the functions should work. The lack of USB (and therefore ADB) is annoying (i'm investigating), but that aside you should do all the stuff you need to.
Obviously it's a quick hack-up so use with care!
P
Click to expand...
Click to collapse
Awesome news. Anything on s-off yet ?
Sent from my HTC One X using xda premium
paulobrien said:
I did a backup and restore, I imagine most of the functions should work.
Click to expand...
Click to collapse
that is the most important thing to know
Stock recovery download added should you wish to revert.
P
Thanks Paul, that sounds really good!
The best would be if the Revolutionary team would now release the S-OFF tool which supports our device..
paulobrien said:
I did a backup and restore, I imagine most of the functions should work. The lack of USB (and therefore ADB) is annoying (i'm investigating), but that aside you should do all the stuff you need to.
Obviously it's a quick hack-up so use with care!
P
Click to expand...
Click to collapse
hey Paul in the ICS kernel there is a difference in the USB gadget... so there is different way to activate ADB... i will get to work on it...
but i need the mkbootimg parameters to repack the zImage and ramdisk...
BTW i will be working on my own version of touch recovery
here is a video of it workign on another of my supported devices...
Yeah, it's not that - a fully working boot image that's OK in boot mode doesn't give you USB in recovery mode. Very odd.
P
paulobrien said:
Yeah, it's not that - a fully working boot image that's OK in boot mode doesn't give you USB in recovery mode. Very odd.
P
Click to expand...
Click to collapse
hmmm let me have a go at it... right now i am struggling with a pathetic net connection as my main internet line is down...
can u give me the complete mkbootimg repack command?
DooMLoRD said:
hmmm let me have a go at it... right now i am struggling with a pathetic net connection as my main internet line is down...
can u give me the complete mkbootimg repack command?
Click to expand...
Click to collapse
Blank command line, base 0x10000000, pagesize 0x800. I don't use mkbootimg directly as it's all scripted up.
P
paulobrien said:
Blank command line, base 0x10000000, pagesize 0x800. I don't use mkbootimg directly as it's all scripted up.
P
Click to expand...
Click to collapse
thanks i will give it a shot... i work with kernels so i prefer using mkbootimg directly
Thanks Paul .
Ps I really liked your last review on the oneX
Paul,
link for signed recovery (the second one) doesn't works ...
paulobrien said:
Blank command line, base 0x10000000, pagesize 0x800. I don't use mkbootimg directly as it's all scripted up.
P
Click to expand...
Click to collapse
hey paul i finally got it working... but there is a correction..
pagesize has to be specified to 2048
then it boots atleast for me
2048 = 0x800 hex!
P
paulobrien said:
2048 = 0x800 hex!
P
Click to expand...
Click to collapse
ya i know but the mkbootimg binaries i tried didnt accept pagesize in HEX
quick query paul, as of now we need to fastboot flash boot.img to gain root as for some reason we cannot fastboot boot a boot img.
if we can fastboot boot a recovery image can we then install a prerooted rom using the booted recovery without needing to unlock the bootloader
bagofcrap24 said:
quick query paul, as of now we need to fastboot flash boot.img to gain root as for some reason we cannot fastboot boot a boot img.
if we can fastboot boot a recovery image can we then install a prerooted rom using the booted recovery without needing to unlock the bootloader
Click to expand...
Click to collapse
for fastboot boot bootloader needs to be unlocked
DooMLoRD said:
for fastboot boot bootloader needs to be unlocked
Click to expand...
Click to collapse
ah well suppose it was worth asking, didnt know that.
Coming from a nexus one "fastboot oem unlock" was the first thing that i did with it so never new it needed to be unlocked to boot, thought it was only to flash
So, here we go - I really liked the new CyanogenMod logo they outlined here. So, I made a boot logo (pre-bootanimation) with it. It is simpler than stock, unobtrusive and quite amazing.
Just flash this zip in recovery, and whala! Profit!
Here's a sneak peek -
image
You should actually be using these boot.img tools:
http://forum.xda-developers.com/showthread.php?t=2073775
And maybe the dd binary from your zip. I could make an example for you.... But my time is limited.
I've been searching for one with no luck, I've tried unpacking the boot.img and can't find one in there, if I'm not mistaken, that's where it was on the OG Pixel phones, never owned one though so not too sure.
Have you looked in the factory restore package? It's typically a separate file.
Sent from my Pixel XL using Tapatalk
On pixels there isn't a recovery image, recovery is part of boot img
cwalker0906 said:
On pixels there isn't a recovery image, recovery is part of boot img
Click to expand...
Click to collapse
Thanks, just figured that one out, this is going to take me some getting used to.
I am still very new to the whole A/B slot boot slot coming from a Nexus 6p. How do I flash a DU rom with gapps/kernel/vendor img/supersu in which order of the slots to flash (A or B)?
I also tried to flash the factory img but seems to get me into a boot loop too. Kindly enlightening me on that.
Thanks!
Unknownkj said:
I am still very new to the whole A/B slot boot slot coming from a Nexus 6p. How do I flash a DU rom with gapps/kernel/vendor img/supersu in which order of the slots to flash (A or B)?
I also tried to flash the factory img but seems to get me into a boot loop too. Kindly enlightening me on that.
Thanks!
Click to expand...
Click to collapse
You've got some reading to do my friend. Start here...https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
Your correct in that it's a little more difficult than flashing our ol 6p's, however, it's not that difficult either. Most all the rom threads have instruction in the OP for flashing procedures. Just take your time, read everything thoroughly, and you'll be fine :good:
Hey all! So I'm still way back in the Stone age on my Nexus 6 shamu. I'm thinking of getting a new pixel device but the things that have changed seem so daunting to me.
Quick questions:
1) when you install a rom, does it go into both system partitions? How does that work? Devices before this dual partition stuff we're straight forward.
2) Is it even worth it to flash stock images with hand typed commands? Or is the flash all script the life saver here?
3) the recovery is now merged with the boot partition, is there any more of quirks like this with a pixel?
4) Does encryption follow suit from the older Nexus devices where it's forced by the boot?
Thanks guys! I'm really thinking of moving on to the new way of using Android on a new flagship device [emoji41]
H4X0R46 said:
Hey all! So I'm still way back in the Stone age on my Nexus 6 shamu. I'm thinking of getting a new pixel device but the things that have changed seem so daunting to me.
Quick questions:
1) when you install a rom, does it go into both system partitions? How does that work? Devices before this dual partition stuff we're straight forward.
2) Is it even worth it to flash stock images with hand typed commands? Or is the flash all script the life saver here?
3) the recovery is now merged with the boot partition, is there any more of quirks like this with a pixel?
4) Does encryption follow suit from the older Nexus devices where it's forced by the boot?
Thanks guys! I'm really thinking of moving on to the new way of using Android on a new flagship device [emoji41]
Click to expand...
Click to collapse
1. If you flash a ROM zip in TWRP, assuming you are on "partition" or slot 'A', the ROM will be flashed to slot 'B'. You don't need to do anything yourself, it just happens on its own. You do need to flash the TWRP zip file again if you were wanting to keep TWRP recovery on your device.
2. Don't know what you mean by hand-typed commands, but I simply run the flash-all file to both slots whenever I want a clean upgrade. Most people get away with flashing it to one slot though.
3. Yes the recovery now resides in boot. You just have to flash the TWRP zip, a custom kernel and Magisk for root in that order to get things working properly!
4. Not too sure about this one, sorry!
rickysidhu_ said:
1. If you flash a ROM zip in TWRP, assuming you are on "partition" or slot 'A', the ROM will be flashed to slot 'B'. You don't need to do anything yourself, it just happens on its own. You do need to flash the TWRP zip file again if you were wanting to keep TWRP recovery on your device.
2. Don't know what you mean by hand-typed commands, but I simply run the flash-all file to both slots whenever I want a clean upgrade. Most people get away with flashing it to one slot though.
3. Yes the recovery now resides in boot. You just have to flash the TWRP zip, a custom kernel and Magisk for root in that order to get things working properly!
4. Not too sure about this one, sorry!
Click to expand...
Click to collapse
Cool thanks! So the device chooses which slot it's gonna boot from by itself then? I'd imagine the bootloader controls that yeah? Does this mean the slot switches for every flashed file or only if it's a full rom package?
H4X0R46 said:
Cool thanks! So the device chooses which slot it's gonna boot from by itself then? I'd imagine the bootloader controls that yeah? Does this mean the slot switches for every flashed file or only if it's a full rom package?
Click to expand...
Click to collapse
As far as I know, it's only for ROM flashes or taking OTA updates when on stock. I'm pretty sure the bootloader does it but I've never manually switched slots unless I wanted a super clean/fresh upgrade. Other than that no manual switching; it's not really hard at all once you get the hang of it!
2) If you mean what I think you mean -- manually inputting fastboot commands for every/all .img files -- Deuces script actually does this! You can even look (or edit, if you are unaware) at the "code" and see 20+ fastboot flash commands. It's a really great modified version of the flash-all script and has helped a whole bunch of users.
3) there aren't many "quirks" I would say, but it does cause a bit of misunderstanding with users coming from other devices onto the Pixels. When coming from root and custom recovery (mostly for OTA updating), they get confused as to resetting it back to stock believing there is a recovery partition to flash and not really bothering with the boot image/partition. I came from the Galaxy S5, so I never got used to that type of thing and am now knowledge-based that recovery goes with the boot image/partition.
4) I'm going to go out on a limb here and attempt to answer this; hopefully I'm understanding it correctly. I believe the device does encrypt from boot. At the very least TWRP (custom recovery) MUST load in any security method you employ to decrypt and properly read the contents of the phone's file system. I can't imagine there being a "process" or "state" that's after turning on the device but before the boot and/or recovery is evoked (other than the "unlocked bootloader" warning, of course).
These are just my assumptions -- if anyone knows better or "righter":silly:, please feel free to correct me -- but in any case, I hope this helps....