Database Develop

[MINI-GUIDE] Roadmap to a Custom ROM!

Roadmap to Custom ROM​
1.Unlock Bootloader from htcdev.com.
2.Flash a multi hboot recovery.
3.Root using the permanent root solution flashed via recovery, found here.
4.Flash S-OFF Hboot from unlimited.io.
5.Flash custom ROM with no problems.
To check your Unlock Token, Flash Recovery and S-OFF you should use the tool provided by me here .

This is the easiest guide to follow.. I'm also using this step to install custom Rom on my SXL before I got One X.. I'm also don't get it.. why people don't use unlimited.io trick.. it easier for me.
BTW.. it good to see a new dev for sxl.. it a good device.. but lack of developer.. wish you good luck with your project.
Sent from my HTC One X using Tapatalk 2

Agreed.
I've flashed on a lot of devices and the SXL guides are all a bit random.
The info is out there but sometimes you need to dig a lot to find it.
And a lot are out of date.
Hope this becomes the go-to guide for everyone and hope to see some dev work happening.
I think its time to move on for me..... getting flash withdrawal.

Prof Peach said:
Agreed.
I've flashed on a lot of devices and the SXL guides are all a bit random.
The info is out there but sometimes you need to dig a lot to find it.
And a lot are out of date.
Hope this becomes the go-to guide for everyone and hope to see some dev work happening.
I think its time to move on for me..... getting flash withdrawal.
Click to expand...
Click to collapse
I'm just getting familiar with the forum and the device (almost 4 days since i bought it).
Soon enough if i have time (back2school), i will try to work on CM9 or CM10, depends, CM9 seems the obvious road to take as some work was previosly made by [vertigo], and some fixes are needed (he said that are kernel related), so i think i will try to fix his CM9 rather than port it again form scratch.
As for CM10, i think the best road to take is to compile AOSP JB from source and edit the kernel so it likes the jelly flavour.
If everything works as intedend, in a couple of months we should see both CM9 and JB/CM10 up and going.
(The worst thing is that i will surely need help, i think i can find around the forum, some testers already enrolled to the call to arms thread, so maybe we can build up a team., i really like this device )

I will say that some of the guides are if you were on a GB rom, and then installing a custom rom wasn't so easy, but since the upgrade to ICS it has become a lot easier, although I had noticed that it is easier to softbrick the phone if you don't flash the chinese boot.img and then chinese rom. Also s-off isn't essential for flashing custom roms...

[vertigo] said:
I will say that some of the guides are if you were on a GB rom, and then installing a custom rom wasn't so easy, but since the upgrade to ICS it has become a lot easier, although I had noticed that it is easier to softbrick the phone if you don't flash the chinese boot.img and then chinese rom. Also s-off isn't essential for flashing custom roms...
Click to expand...
Click to collapse
Well, i'm fairly new to this device, but from what i've learned, the chinsese rom is optional if you have s-off, as s-off let's you to access all the partitions, system and other things you need.
Maybe i'm wrong, that's why i've started this thread, i think this is easier, and softbricking a phone with Android seems almost impossible to me...as i said, to me

Yeah I know the chinese rom is optional, but as I said from my point of view, once I'd flashed the chinese rom, I didn't manage to softbrick the phone where as before when I was trying various ports I managed to softbrick it a few times. Just my opinion and what I'd noticed with my device...
As for s-off mine (although broken) is still s-on and I've never felt the need to make it s-off. Again just my opinion

[vertigo] said:
Yeah I know the chinese rom is optional, but as I said from my point of view, once I'd flashed the chinese rom, I didn't manage to softbrick the phone where as before when I was trying various ports I managed to softbrick it a few times. Just my opinion and what I'd noticed with my device...
As for s-off mine (although broken) is still s-on and I've never felt the need to make it s-off. Again just my opinion
Click to expand...
Click to collapse
Well, i know what youre pointing at, i was just wandering when i first read te forum, why on earth should i install a Chinsese ROM when i will change it anyways for a new ROM...so the boot.img is a different one in the custom one, and other things.
I'm not so expeirenced with S-Off/On, as this is my first HTC phone i have and changed ROM (not too many HTC's in my area), but from what i've read online, S-Off is the best road to take to ensure you don't softbrick your phone, as you have the real "Full Control" over the Device and the ROM parts you can flash, like you, this is my opinion, a begginers opinion

Double Post because reedited thread

Hi Lexmazter,
Thanks for making this guide, it is easy to follow. But I'm stuck at a small point and face below response; -
>>>>>>>>>>>>>>'fastboot' is not recognized as an internal or external command, operable program or batch file.<<<<<<<<<<<<<
Please let me know where did I do wrong? Thanks.
My steps were: -
factory reset
root via DooMLoRD_v4_ROOT
titanium backup worked and restore all apps and settings
unclocked the bootloader from htcdev.
all data gone, no more, like factory reset again
superuser app still exist, didn't root again
booted and rooted as you said
connect PC to phone via USB in charge mode only.
run your tool
doing select 5 Flash HBOOT S-OFF Unprotected (via adb) - choose hg hi both failed - but face above message 3 repeat lines.
reboot to bootloader FASTBOOT, >>>>>USB<<<<< appear
UNLOCK at top also appear
then select 4 Flash Recovery. (via fastboot) - then choose rei reg both failed - but face above message. 1 line.
Hope can teach me, thank you very much in advance.
And I'm sure I didn't do something right before hand.

cx5 said:
Hi Lexmazter,
Thanks for making this guide, it is easy to follow. But I'm stuck at a small point and face below response; -
>>>>>>>>>>>>>>'fastboot' is not recognized as an internal or external command, operable program or batch file.<<<<<<<<<<<<<
Please let me know where did I do wrong? Thanks.
My steps were: -
factory reset
root via DooMLoRD_v4_ROOT
titanium backup worked and restore all apps and settings
unclocked the bootloader from htcdev.
all data gone, no more, like factory reset again
superuser app still exist, didn't root again
booted and rooted as you said
connect PC to phone via USB in charge mode only.
run your tool
doing select 5 Flash HBOOT S-OFF Unprotected (via adb) - choose hg hi both failed - but face above message 3 repeat lines.
reboot to bootloader FASTBOOT, >>>>>USB<<<<< appear
UNLOCK at top also appear
then select 4 Flash Recovery. (via fastboot) - then choose rei reg both failed - but face above message. 1 line.
Hope can teach me, thank you very much in advance.
And I'm sure I didn't do something right before hand.
Click to expand...
Click to collapse
Extract the contents of the archive in C:/ and try again, it is most likely because you are running from a folder that has spaces (" ").

Thanks for replying so quickly, some questions before sleep tonight.
I moved the folder to c:\xmtool and run as administrator as usual. But without connecting the phone, and select 5 flash H boot. The 3 repeat message appear still. Hahah, may be I want to test in theory.
Anyway, reading more more other post and try again this weekend.
Thanks !!!! many of your post and reply has been insightful.

[Q] N00b has done his best to kill Three HTC one (the n00b is me)

This is a great example of how to make a mess of things with a combination of a little knowledge and not paying attention. Here's the background:
UK 1.28 One Stock + Root. No other mods. I needed to install Busybox so I could install Screen Standby # Root. Apparently, the marketplace apps are unable to install due to the System folder protection. I found a .zip to install using TWRP (Sprint_One_Root_Disable_System_Write_Protection_1.29.651.10.zip) and you can already see where I've gone wrong. I looked for a generic/EU version of this zip but this was the only one I could find so off I went. Naturally this didn't work and my phone now won't boot. At least I can get to TWRP still so I presume all is not lost. Looking at my /system directory, there's nothing in it apart from the /bin folder (also empty). From further reading I guess I need to find a stock kernel and use ADB push to push boot.img and then fastboot to install. So my questions are:
1) Is this the correct way to fix this problem? I'd rather rescue this system as I've got everything the way I like it. No, I hadn't done a backup. Yes, I'll sort that as soon as I've fixed it.
2) Can somebody point me in the direction of the stock kernel for my device?
3) How was I supposed to install BusyBox? (I still need to get Screen Standby # Root installed!)
Many thanks for your help in advance.

ShadowTD said:
This is a great example of how to make a mess of things with a combination of a little knowledge and not paying attention. Here's the background:
UK 1.28 One Stock + Root. No other mods. I needed to install Busybox so I could install Screen Standby # Root. Apparently, the marketplace apps are unable to install due to the System folder protection. I found a .zip to install using TWRP (Sprint_One_Root_Disable_System_Write_Protection_1.29.651.10.zip) and you can already see where I've gone wrong. I looked for a generic/EU version of this zip but this was the only one I could find so off I went. Naturally this didn't work and my phone now won't boot. At least I can get to TWRP still so I presume all is not lost. Looking at my /system directory, there's nothing in it apart from the /bin folder (also empty). From further reading I guess I need to find a stock kernel and use ADB push to push boot.img and then fastboot to install. So my questions are:
1) Is this the correct way to fix this problem? I'd rather rescue this system as I've got everything the way I like it. No, I hadn't done a backup. Yes, I'll sort that as soon as I've fixed it.
2) Can somebody point me in the direction of the stock kernel for my device?
3) How was I supposed to install BusyBox? (I still need to get Screen Standby # Root installed!)
Many thanks for your help in advance.
Click to expand...
Click to collapse
Flash a kernel form here. http://forum.xda-developers.com/showthread.php?t=2255160

SmiLey497 said:
Flash a kernel form here. http://forum.xda-developers.com/showthread.php?t=2255160
Click to expand...
Click to collapse
That's brilliant. Given I can only get to my bootloader or TWRP and don't have a USB OTG cable, will that work with TWRP's 'sideload' functionality? If not, how would I install it using fastboot?
<edit> Just tried it using TWRP sideload and I get a 'No MD5 file found' and 'Zip signature verification failed. Any suggestions?
<edit2> Changed to CWM and that seemed to install correctly but the phone still refuses to boot. There's a few errors in CWM that seem to indicate it can't mount System - could this be the problem? I never S-OFF'd before I got in to this mess.
Thanks!

Anyone else? I've got a USB OTG cable on its way and what I hope is the correct Nandroid backup to restore, but I've not given up hope on bringing the current build back to life.

Right, well, things are certainly brighter than yesterday. USB OTG cable arrived, restored Nandroid backup for UK Three 1.28. Phone comes back to life. Brilliant. Set about getting back to where I was and sorting out the Busybox problem. I installed:
HTC Preloaded apps via CWM
Team Seven Sense Kernel v4 stable
Installed Busybox via a market app and things are looking excellent. Apart from the camera app not working. Oh hell. 'Unable to start camera' after about 10-20 seconds of a black screen with camera controls.
Figured this might be a cache or permissions issue so I went back to recovery and cleared cache, dalvik cache and repaired permissions. Clear the app data as well from Settings. No dice. The only thing I didn't delete is the user data as I was hoping to not lose the pictures I've got on there. Everything else is brilliant so I hope somebody can help me fix this!
Thanks again.

Please help. Phone stuck in purgatory [Resolved]

Okay, so being the wise person that I am, I decided that it would be a good idea to get the 4.2.2 sense update a few days/weeks before my carrier (Rogers) pushes it. I'll write it step by step, in case anyone can help me
- I started by making an ADB Backup, rooting the phone, and installing twrp recovery. No issues there
- When the phone started back up, I tried to restore my data, but the adb backup kept getting stuck on "com.Android.contacts" or something similar, so I decided I might as well try getting S-Off so I could change CID and get the 4.2.2 update.
- I used Revone, but it kept failing (error code -1). I posted in that thread about it, but I decided that in the mean time, I would just factory reset my phone.
I stupidly clicked "format" in twrp!
Now, my phone is on twrp with no OS. I tried downloading the rogers rom from HTC Dev, but it was a Zip file, and it won't install. I restarted the phone, and now I can't push anything to it. It says "error: device not found" when I try push the European 1.28 RUU (which I'm not sure if that would even work, because of CID/MID differences since the phone isn't S-Off.
Any help would be greatly appreciated :crying:

Okay, So I finally got the European RUU to push to the phone, only to realize that it's a ".exe" that can't be flashed from twrp. I have no access to a PC

WhatsAUsername said:
Okay, So I finally got the European RUU to push to the phone, only to realize that it's a ".exe" that can't be flashed from twrp. I have no access to a PC
Click to expand...
Click to collapse
Just flash any stable ROM in the meantime so you can at least boot the phone. Download ARHD, push the zip to your phone, and flash that.

I really don't understand all these people changing CIDs to force updates, especially when they go back to s-on afterward. You're locking your phone into a potentially problematic configuration. I helped another guy this morning who did it and then couldn't boot up but couldn't fix anything because he went back to s-on and locked bootloader.
If you want 4.2.2, do it the right way: S-off, flash firmware, flash rom. If you want stock, there are stock roms. All of this can be done on a Mac.

iElvis said:
I really don't understand all these people changing CIDs to force updates, especially when they go back to s-on afterward. You're locking your phone into a potentially problematic configuration. I helped another guy this morning who did it and then couldn't boot up but couldn't fix anything because he went back to s-on and locked bootloader.
If you want 4.2.2, do it the right way: S-off, flash firmware, flash rom. If you want stock, there are stock roms. All of this can be done on a Mac.
Click to expand...
Click to collapse
Well, I flashed CM 10.1, and finally managed to get S-Off. Now my issue is trying to go back to stock HTC Firmware. I can only get the RUU, which obviously doesn't work on Mac. Even If could extract the Zip, I have twrp recovery. How would I go back to a stock recovery that would allow me to get the OTA? I'm really upset about this whole thing. I mean, come on. HTC should've provided a Mac utility that allows users to go back to stock completely. I understand that they give you warnings about doing this kind of stuff, but I should be able to play around with my device and still be able to get it back to a functional factory state. I got iOS 7, and it was incredibly easy to go back. I've upgraded my Blackberry Z10 a 100 times with firmware from all over the world with no issues. I've also never had to deal with this S-crap stuff on my Nexus 4. It's just frustrating for end users.
Anyways, rant aside, would you happen to know how I can go back to a full factory state? I'm on CM 10.1 right now with twrp recovery.

WhatsAUsername said:
Well, I flashed CM 10.1, and finally managed to get S-Off. Now my issue is trying to go back to stock HTC Firmware. I can only get the RUU, which obviously doesn't work on Mac. Even If could extract the Zip, I have twrp recovery. How would I go back to a stock recovery that would allow me to get the OTA? I'm really upset about this whole thing. I mean, come on. HTC should've provided a Mac utility that allows users to go back to stock completely. I understand that they give you warnings about doing this kind of stuff, but I should be able to play around with my device and still be able to get it back to a functional factory state. I got iOS 7, and it was incredibly easy to go back. I've upgraded my Blackberry Z10 a 100 times with firmware from all over the world with no issues. I've also never had to deal with this S-crap stuff on my Nexus 4. It's just frustrating for end users.
Anyways, rant aside, would you happen to know how I can go back to a full factory state? I'm on CM 10.1 right now with twrp recovery.
Click to expand...
Click to collapse
Without a PC to run the RUU, I'm not sure. You can flash stuff, but if you want to be out of the box stock, you need a RUU.

I finally managed to get my phone to work. In case anyone comes across this, I'll write down what I did.
I had too many problems to list. From not being able to access adb on the phone, to the phone's memory being partitioned incorrectly, to the point where even a recovery like twrp couldn't format or access it in order to flash anything ("Unable to mount internal storage").
The solution to all problems (and if you're a Mac user like I am, this is disheartening), is that you'll need to run RUU on a PC. When doing this, you'll likely run into a few error messages.
Error 170: Make sure the device is in fastboot mode before plugging it in (hold power and volume down on boot, and select fastboot with the power button). You can make sure that the computer can see it by going to your device manager in windows, and make sure that it says "My HTC" under "Android Device." If it has a cryptic name with an exclamation mark, or you can't see it by using "fastboot devices" command, you'll continue to get that error.
Error 171: This error kept occuring when the computer could no longer see the phone after the process had already begun. The reasons this happens are many (ie your USB wire or drive might be faulty), but to me, it was because the phone was not going back to the bootloader on its own, and the computer eventually gave up. To solve this, start RUU.exe and WAIT BESIDE IT. You will come across 2 points where it says waiting for bootloader. Have your computer's device manager open, and hold the phone's power button until you see that the "Android Device" or "My HTC" disappears and reappears. RUU should continue when that happens. Again, you will have to do this twice! If you don't, RUU gives up on the phone as it does not go into the bootloader by itself, and will eventually give you an error.
For anyone going through this, just realize that as long as you can get into the bootloader, there's always a way to get it to work. At times, I thought my phone was completely bricked, but no matter what issue you have (including unable to access the phone's internal memory), you can always solve it if you can get into the bootloader. With that said, this process will erase everything on your phone, unfortunately. Everything is done at your own risk, so please don't blame those who are trying to help you. Good luck, and remember to always post your solution online, if you start a topic discussing the issue. I came across many people with the same issue who never came back with their solution!

Edit the title to solved

Not that it has happened to me but I think you could have just sideloaded a custom Rom from twrp and flashed that.

a box of kittens said:
Edit the title to solved
Click to expand...
Click to collapse
I tried, but I'm unable to do it. Due to the low post count, perhaps? :S
godutch said:
Not that it has happened to me but I think you could have just sideloaded a custom Rom from twrp and flashed that.
Click to expand...
Click to collapse
That was one of the first things I tried. It kept coming back with "unable to mount internal storage" or something like that, as I noted earlier. It was really weird, I couldn't format, mount, or do anything to my storage with tarp, and I couldn't get adb to see the phone. A lot of people have the issue with the One X, but I couldn't find a solution anywhere. I think what made the whole thing trickier than it needed to be is the fact that I changed my CID/MID, and in that guide, it is explained that you have to reboot the phone yourself in RUU, but I didn't realize not doing so would result in errors. I kept thinking it was because my device wasn't being seen in adv, so I was trying to get it to boot into any ROM for that to happen, and the inability to flash anything due to the internal storage error really complicated things. It's good to know that even this can be resolved, as I had all but convinced myself that I was dealing with a brick. I hope anyone coming across this issue in the future can benefit from my ordeal.

WhatsAUsername said:
I tried, but I'm unable to do it. Due to the low post count, perhaps? :S
Click to expand...
Click to collapse
Click edit on the OP, then Go Advanced. You should be able to edit the title at the top.

iElvis said:
Click edit on the OP, then Go Advanced. You should be able to edit the title at the top.
Click to expand...
Click to collapse
Done. Thanks!

WhatsAUsername said:
That was one of the first things I tried. It kept coming back with "unable to mount internal storage" or something like that
Click to expand...
Click to collapse
That's normal since android 4.1 because the sd card is not a fat partition anymore, did you follow this guide?: http://forum.xda-developers.com/showthread.php?t=2325853

[Q] HTC One Sprint M7WLS softbricked, don't know what else to do.

With the new 4.3 OTA I thought I might be good to delve into updating my phone today. That was around Noon, it's now 9PM, and I just don't know where else to turn. I know where I screwed up a few things and I feel like I've tried everything. Hopefully you guys will have some helpful suggestions, if not I guess I'll have to bite the bullet.
I'm a noob at rooting. I did root my HTC Evo Shift a year or two ago. Put CM 7.something on it, but I really wasn't happy with the performance so I just RUU'd back to stock and haven't messed with it since. I did leave it rooted for some root required apps though.
I rooted my HTC One a couple months ago using this method:
On gizmodo how-to-root-your-nexus-htc-one-or-samsung-galaxy-s4-990847878 (can't link it because I just signed up)
With 4.3 out I thought I would be able to find a modified update and keep my phone Stock rooted or try InsertCoin or something. My first mistake, I believe, was thinking that root was fine without S-Off.
I've got Drivers and Android SDK on my Win7 machine (I have a Mac and Fedora box if anyone knows any solutions using those OS's). I have on the phone TWRP 2.5.0.0, root, S-On. I try to upgrade to TWRP 2.6.0.0 and that doesn't work so well. I read somewhere that the M7WLS doesn't like that build, and I should try 2.6.0.1, I just strait to 2.6.3.0.
Read some articles on TWRP, watched some videos, so I go to do factory data wipe, cache wipe, dalvik cache wipe, and I do system wipe thinking I need to do that too. Whenever I reboot I basically stop at the HTC splash screen. Mistake number two, I have no OS now.
I hunt down a recovery.img from a site that is supposedly offical Sprint, flash it, try to do a factory restore, no good.
I try getting it back to stock with this:
How to Unroot / Unbrick the HTC One M7: Back to Stock by C4Etech
youtube.com C0G0hKY4P9Y
fastboot oem rebootRUU
fastboot flash zip <rom>.zip
I get errors whether locked or unlocked. I still have S-On and I'm guessing that's why I'm getting signature validation errors.
I try TWRP and ClockworkMod 6.0.4.3 to see if I can mount to my PC, no go.
Fastboot devices recognizes the M7WLS so after more reading I'm going to try ADB sideload. ADB devices does not see my phone. HT Sync is already installed, I remove it and try HTCDriver_4.2.0.001, no go. I remove it and try Universal_Naked_Driver_0.73, still nothing on adb devices. Whether TWRP or ClockworkMod Recovery I can't side seem to sideload.
I go to the store and pick up a cable:
Staples.com Belkin-4-Ports-USB-20-External-Flex-Hub product_IM1QZ5590 (Can't link)
Put
insertcoin-m7-4.0-4.zip AND
Guru_Reset_M7_Sprint_1.29.651.10.zip
on a USB stick, but the phone doesn't recognize it so I can load from either recovery.
I'm sure I've missed a few things in there. Right now I'm sunk, I'm tired, and suggestions are appreciated.

Try buy a USB to go and put a Rom on a Memory stick them using TWRecovery flash the Rom if you have any questions feel free to ask

Demo3827 said:
Try buy a USB to go and put a Rom on a Memory stick them using TWRecovery flash the Rom if you have any questions feel free to ask
Click to expand...
Click to collapse
Thanks for the input Demo. I actually connected it to OSX and the adb devices came right up so I was able to do a rom side load. Thanks again though.

your welcome
pwjohnston79 said:
Thanks for the input Demo. I actually connected it to OSX and the adb devices came right up so I was able to do a rom side load. Thanks again though.
Click to expand...
Click to collapse
your welcome =] anytime :good:

[Q] ART failed and now I have no phone.

I tried turning on ART instead of dalvik, and it messed up my phone. So I wiped it, no backups, and now suddenly my .zip for the ROM is corrupt and can't be used to flash the ROM, so I essentially have a paperweight. I can't ADB sideload (I've tried), I can't ADB Push (tried) I tried flashing with fastboot to system and it failed, and I don't know what else to do. I can't mount to USB storage to copy the thing over and I don't know of any other method.
Specs:
1.44 hboot
was previously running the newest ecliptic 4.4/5.5 ROM
newest philz touch recovery.
When I go to reboot my phone from recovery, it tells me I don't have root access anymore.
How do I fix this, and why is it so hard?

thelonewizard said:
. . . How do I fix this, and why is it so hard?
Click to expand...
Click to collapse
First, in the future, read before leaping -- it's well known that ART cannot work with a Sense based ROM -- it's totally broken and it will surely do bad things. If you want to know why it's so hard -- it's because your device is totally screwed up now.
First, your /system partition is probably trashed -- so that's why PhilZ says you have no root access -- you don't, there's nothing worthwhile at all on your /system partition.
Before you go too far, please tell us all what your firmware versions -- look for the 'OS-???????' on your bootloader screen. That will dictate with RUU you will want to use if necessary.
There's a couple choices:
1) *if* the ART mess didn't totally screw up your internal storage, you have a shot at loading a ROM and moving forward (see if you can look at the internal storage in PhilZ, to go 'backups restore' menu, and try to load from /sdcard -- hopefully it can see the file system, if not -- you better RUU so see below):
a) Place a valid ROM (my suggestion is use benny3's stock, rooted ROM so you get to a place of sanity) on a exFAT, ext4 or ntfs formated USB stick;
b) Boot into recovery (PhilZ is apparently working for you -- whew!):
c) Plug your OTG cabled USB stick in to the device (PhilZ will mount the USB drive);
d) Use PhilZ to 'wipe to load new rom' in the menus;
e) Load the ROM from /mnt/storage/usb.
2) *if* the ART mess screwed you totally, you'll have to RUU back to stock:
http://forum.xda-developers.com/showthread.php?t=2277892 -- Start with Q16 in that FAQ.
We can help -- don't rush. Also, plug your device in, PhilZ will charge the thing and you want it charged reasonably before you get started.

tdhite said:
... 2) *if* the ART mess screwed you totally, you'll have to RUU back to stock:
http://forum.xda-developers.com/showthread.php?t=2277892 -- Start with Q16 in that FAQ.
We can help -- don't rush. Also, plug your device in, PhilZ will charge the thing and you want it charged reasonably before you get started.
Click to expand...
Click to collapse
The 1.29 RUU worked. How do I now unlock it so I can go back to custom ROMs? I assumed the command would be "fastboot oem unlock" but that fails when I try it. I assume this is due to me having lost root rights, but I obviously don't know what I'm talking about. I just want to go back to the Ecliptic ROM. I had no issues right up until I decided to try ART.

thelonewizard said:
. . . I obviously don't know what I'm talking about. . . .
Click to expand...
Click to collapse
So be careful (and throw some thanks button hits around when folks help you out -- not just me, not the point -- it matters to all folks around here to help ).
As for re-rooting, same FAQ page link I gave you above, Q4 -- read that whole FAQ before you do much more so you know where to look next time. A little reading may save you serious pain down the road. Good luck!

tdhite said:
So be careful (and throw some thanks button hits around when folks help you out -- not just me, not the point -- it matters to all folks around here to help ).
As for re-rooting, same FAQ page link I gave you above, Q4 -- read that whole FAQ before you do much more so you know where to look next time. A little reading may save you serious pain down the road. Good luck!
Click to expand...
Click to collapse
Thank you for all the help. I got back to my ROM with minimal data loss, and I'm not touching ART until HTC makes it official. I really appreciate the help, and you'll notice a couple new "Thanks" in your meter.