Trying to install cyanogen mod.
First I tried to s-off before unlocking the bootloader (which I later learned was a mistake).
I tried everything except facepalm in the following order: (moonshine, rumrunner, firewater).
For firewater I was able to root/temp root via Minimal ADB and Fastboot as well as Weaksauce.apk.
None of those worked, but thankfully none of them bricked the device, however there has been some problems since then.
When I realized I should have been trying to unlock the bootloader this whole time, I tried SuperCID.apk from the soure.zip found in the development sticky thread.
That also failed.
Details about the phone:
Motherboard replaced ~3 months ago.
HTC sent the phone back to me running software number 1.15.605.4 710RD (Android 4.1.1)
While attempting root/s-off/unlock bootloader the SIM was installed but the phone was not activated and was in airplane mode.
I do not have OEM cable however ADB recognizes the device being attached so I don't think that is an issue.
Problems that have developed:
Since tinkering around the boot times have extended dramatically with some funny behavior at initial startup.
The battery is draining noticeably quicker.
I factory reset the phone and booting has gotten a little smoother, no battery improvement.
Aside from those 2 problems the phone functions perfectly.
I'd really like to be rid of the stock rom and all of its bloat apps, so if there is another way to get a CM ROM I'd be damn happy.
Also, any information on what I may have funked up when trying moonshine/rumrunner/firewater would be greatly appreciated.
Did you ever figure this out? I have been unable to unlock my bootloader too.
Yes!
gabezermeno said:
Did you ever figure this out? I have been unable to unlock my bootloader too.
Click to expand...
Click to collapse
I was able to figure it out after HOURS or even days of confusion.
In my case the problem I was having, was using the incorrect unlock/s-off method for the my corresponding firmware.
I upgraded via Verizon updates from firmware 1.XX to 2.XX until I eventually got 3.6 (it took multiple updates to get there). Once I had 3.6 I used the RUMRUNNER method to unlock and s-off (it was quite easy once it I had adb and fastboot commands all figured out).
Good luck.
Related
Good ghod what a state I've managed to get myself into: I've been unlocking/re-locking my phone (ROM: OTA ICS, S-On, Unlocked, Rooted) for right at a year now, but, during the recent OTA update push, I managed to get it into a state where it will no longer unlock. My (long, sorry) story follows...
I started receiving the recent OTA push two or three weeks ago. The problem is that I'd renamed the HTClinkifydispacher apk and odex files, and added a couple of things to /system/app/build.prop so the update would fail. Why was this such an immediate problem? Because I use my phone for an alarm clock and would wake up on random days to see it booted to recovery---after having overslept. Grrr.
Being the impulsive guy that I am, rather than just ask here how to stop the f$*kin' update, I found and saved the OTA.zip file to my sdcard, fixed the two problems I was having, re-locked the bootloader, and booted to recovery. Next, I *thought* I picked the OTA zip file to install... but I was wrong.
For at least one reason (I wanted to install a kernel with tun.ko installed so I could use a VPN network connection), I had a copy of SebastianFM's 1.4 overclocked kernel zip on my sdcard and mistakenly picked *it* instead of the OTA zip (hey, the fonts are small in Amon Ra). Well, that install failed, and, when I saw what I'd done, I thought "uh oh," so I rebooted the phone fully to see if I'd done any damage. None was apparent. So I moved on, once again re-booting into recovery and (this time successfully) installing the OTA zip.
Woo-hoo!
I thought I was golden, but I was wrong: Using my original unlock code and an up-to-date copy of the Android SDK on my linux box, I tried to reflash the unlocktoken partition using the fastboot command. My cursor froze/still freezes at something like "[0kb downloaded]..." It's almost like I've lost permission to write to that partition in the bootloader.
After the first sixteen times of trying various re-flashes of the August OTA, I thought "Gee, maybe it's something to do with the firmware," and since doing something is almost always worse than doing nothing (yes, that's what I meant to say), I did the only thing I could do: I flashed the Global Update RUU zip from October that I got off of Android Police's site. It's a great ROM; unfortunately, I still cannot unlock my bootloader.
In anticipation of some possible questions, let me add that
(1) I've factory reset any number of times;
(2) When I did the flashes, I immediately re-flashed a second time to ensure that the flashes took;
(3) When I connect my USB cable, I see "Fastboot USB" light up in the fastboot section of HBOOT.
(4) When I issue any other fastboot command, such as "fastboot devices" or "fastboot get_identifier_token", I get responses from the phone.
(5) Even though I have my original Unlock_code.bin file from HTCdev, I went through the whole unlock process from that site (sent a new identifier token; got the Unlock_code.bin back; tried "fastboot flash unlocktoken Unlock_code.bin") on two other occasions. Interestingly, the identifier_tokens would vary, but any new Unlock_code.bin files have all been identical---if the md5sum hash can be trusted to distinguish them.
Can anyone out there in expert-land help me figure out how to re-unlock my bootloader?! !? Beer can be involved.
Many thanks for your patience and kind consideration...
cheers,
john
Hey All,
So, I'd like to first say thanks to all of you who read and considered throwing in an opinion on how I might move forward with my little problem.
Secondly, I have some followup from HTC, which spawns a followup question. Please read on...
Since my OP, I have been in a back and forth with HTC about what I did to my phone that has left me unable to re-unlock it. Their answer, in a nutshell, was that I'd accepted the update while my phone had a 3rd-party recovery on it. Guilty as charged, I did; Amon Ra 3.15.
More specifically, they wrote: "If any portion of this check fails due to the stock recovery not being present, the update may load but the security sector will not authenticate. This may be blocking the re-unlock."
If you're like me, you'll note that there are a couple of "may"s in those two sentences that have left me wondering if they're just giving me a stock "I really don't know what the hell happened to your phone" answer.
So just to satisfy my curiosity, has anyone else out there ever had a problem flashing OTAs while having a 3rd-party recovery on their phones?
thanks again,
john
There's a couple threads about the recent OTA, one in General and one in this section. People posted about their various experiences, you might find some useful info in those.
I wonder if you can s-off at this point and fix your issue? I don't know if you need to be unlocked to s-off, I know you end up locked, but if not, that would give you the freedom to flash what you want without needing to be "unlocked".
feralicious said:
There's a couple threads about the recent OTA, one in General and one in this section. People posted about their various experiences, you might find some useful info in those.
Click to expand...
Click to collapse
Yes, I've looked through them and had no luck finding anything relevant to my case.
feralicious said:
I wonder if you can s-off at this point and fix your issue? I don't know if you need to be unlocked to s-off, I know you end up locked, but if not, that would give you the freedom to flash what you want without needing to be "unlocked".
Click to expand...
Click to collapse
The phone has to be unlocked to do the s-off thing.
thanks,
john
Update: Problem Solved!
Hey All,
As the post title states, I finally did get this sorted out.
The solution? Borrowing a windows 7 computer, downloading the HTC device drivers, fastboot and adb, and then merely running the 'fastboot flash' thing. Like I'd done a thousand times already on my linux system. Sheesh.
Thanks to all who read or contributed to this thread...
cheers,
john
Hey guys. Need a big hand here. So I have a HTC One on contract from Three in the UK.
I rooted the phone and all that jazz and decided on putting a custom ROM on my device.
However while in TWRP I wiped the phone and seemingly all the contents on it, including TWRP.
Now I have a bricked phone that boots into recovery/ the bootloader only. I've tried flasing
RUU files on but it fails with the error code 140? I don't know much about this I'm quite a noob.
In recovery the information is as follows:
*** TAMPERED ***
*** RELOCKED ***
*** SECURITY WARNING ***
M7_UL PVT SHIP S-ON RH
HBOOT- 1.54.0000
RADIO-4A. 17. 3250. 14
OpenDSP-v31.120.274.0617
OS-2.24.401.0
eMMC-boot 2048MB
Please help me. I've read through wonderful guides by other patrons on this website but nothing seems to work.
I'm at my wits end.
Thank you in advance for any help.
I know very little about this, but just to brainstorm (and confirm a few basic facts):
When you rooted originally, did you use HTC's bootloader unlocker or a different method to unlock the bootloader?
How are you flashing ROMS? Are you doing everything through the phone (example, using one-touch-root apps) or are you using the Android Debug Bridge?
The bootloader typically comes with options to reboot, boot into recovery, factory reset, etc. Can you confirm that these options have disappeared (or never existed in the first place)?
My knee-jerk reaction is that you didn't use an HTC bootloader unlocker and, therefore, the HTC GUU detects a bootloader mismatch and aborts. Therefore, you need to see if there's a way to flash a stock HTC bootloader (which, I can tell you from experience, is usually a one-way-trip to super-bricking) or see if the bootloader you already have installed can be unlocked through the ADB.
In my very limited experience and understanding of Android, it's generally pretty difficult to wipe the recovery partition from within the phone - one generally as to flash it from ADB or screw with the bootloader in some way to wipe it. I wonder, therefore, whether the recovery partition is just fine but maybe the bootloader is throwing a fit because it's not the HTC default.
I'm sure you've tried or thought of all of this, but since nobody else is stepping up, I thought I'd help brainstorm a bit and keep the thread fresh.
Borden Rhodes said:
I know very little about this, but just to brainstorm (and confirm a few basic facts):
When you rooted originally, did you use HTC's bootloader unlocker or a different method to unlock the bootloader?
How are you flashing ROMS? Are you doing everything through the phone (example, using one-touch-root apps) or are you using the Android Debug Bridge?
The bootloader typically comes with options to reboot, boot into recovery, factory reset, etc. Can you confirm that these options have disappeared (or never existed in the first place)?
My knee-jerk reaction is that you didn't use an HTC bootloader unlocker and, therefore, the HTC GUU detects a bootloader mismatch and aborts. Therefore, you need to see if there's a way to flash a stock HTC bootloader (which, I can tell you from experience, is usually a one-way-trip to super-bricking) or see if the bootloader you already have installed can be unlocked through the ADB.
In my very limited experience and understanding of Android, it's generally pretty difficult to wipe the recovery partition from within the phone - one generally as to flash it from ADB or screw with the bootloader in some way to wipe it. I wonder, therefore, whether the recovery partition is just fine but maybe the bootloader is throwing a fit because it's not the HTC default.
I'm sure you've tried or thought of all of this, but since nobody else is stepping up, I thought I'd help brainstorm a bit and keep the thread fresh.
Click to expand...
Click to collapse
I unlocked the bootloader originally by getting a specific code from HTC and using it through the command prompt I think. I can go into the bootloader and it has all the fastboot, recovery, factory reset business there. Trying factory reset does nothing. I've downloaded HTC toolkit 2.2 and I tried initially pushing ROMS to flash to TWRP, but it would never detect my phone. Then I stupidly did a full wipe through TWRP and now that's disappeared. All that's left is the bootloader now. I've tried forcing RUU updates through the HTC toolkit but it always fails. So does running the normal RUU process. I can't seem to find the correct one for Three UK. The most I've been able to do is re-lock the bootloader and I'm running out of ideas. Thank you for your reply. I feel so helpless!.
If I've read your message correctly, you are doing everything through the HTC toolkit and not through the Android SDK. Frankly, I don't know how the former works. Especially if the HTC Toolkit isn't detecting your phone, you may want to run over to http://developer.android.com/sdk/ and fetch the SDK for your system and set it up. You don't need the ADT Bundle, just the SDK Tools link at the bottom. This may make it easier for other, more knowledgeable people debug your phone, since they all use the SDK. The weaponry you'll be using is all in the <sdk install location>/tools directory, so get a command prompt window pointed there (by the by, are you using Windows, Mac or Linux?)
If you already have your SDK up, or once you do, you'll want to get familiar with the fastboot command, described in this post: forum.xda-developers.com/showthread.php?t=2277112 . What we want to do is see whether we can flash a new recovery ROM.
As long as you don't attempt to flash over the bootloader, you shouldn't super-brick your phone. Based on the message in your original post, your bootloader may have relocked itself. If your first attempt at installing a new recovery ROM doesn't work, then you'll have to use the procedure you used originally to unlock your bootloader. If you've forgotten how to do that, then these instructions (which assume you're using the SDK) should help: http://wiki.cyanogenmod.org/w/Install_CM_for_m7.
You're currently using TWRP, which I've personally found buggy. Until you have a functioning phone again, you may want to use ClockworkMod (CWM) Recovery instead: http://www.clockworkmod.com/rommanager. It has fewer features, but at least they work properly. If flashing ROMs over fastboot is new to you, there are plenty of guides on the Interwebs to help you. I'll also try to walk you through it if you let me know where you're getting stuck. The critical thing, considering that there are many types of HTC One, is to make sure that you flash the ROM that exactly matches your phone. If you flash the wrong ROM, you probably won't break your phone any more than it is, but let's try not to test that theory. If you're not positive which phone you have, say so and we'll help you find out.
Let us know once you have CWM on your phone or where you got stuck. The advantage of using the SDK, too, is that you can copy and paste the output right back to the forum.
I hope I understood everything correctly. Let me know if I haven't.
Good evening,
I am reaching out to all developers and android enthusiasts here on XDA as I am completely stuck at this point. This post may get a little bit long winded but I wouldn't post if I didn't legitimately need the assistance.
So here is my situation. I have an ATT HTC ONE and I originally rooted this phone thinking that it would improve the devices battery life as I've experienced with any other android device that I've rooted. All my Samsung devices respond miraculously to rooting and couldn't imagine not having a rooted android. Well after a few short weeks I found myself in need of unrooting the device and restoring back to stock(for personal reasons). Upon attempting to relock the bootloader and then reflash stock firmware back to the device I was successful at getting the bootloader relocked but somehow managed to completely delete all;the System partition on the device. I CAN still however boot the phone into the bootloader(into fastboot,recovery, etc) I have TWRP recovery installed on the device but now the phone says that its got 0mb of storage on the phone. Ive spent countless hours trying to figure out how to get the phones original firmware back on the device with absolutely no luck. My current Hboot version is 1.55 and i have S-ON as well. Can someone point me in the direction of a thread where I can some how recreate the system(and other neccessary partitions) to restore the firmware?? Does HTC have anything like KIES that Samsung has where i can reflash my phone?
COrootking4life said:
Good evening,
I am reaching out to all developers and android enthusiasts here on XDA as I am completely stuck at this point. This post may get a little bit long winded but I wouldn't post if I didn't legitimately need the assistance.
So here is my situation. I have an ATT HTC ONE and I originally rooted this phone thinking that it would improve the devices battery life as I've experienced with any other android device that I've rooted. All my Samsung devices respond miraculously to rooting and couldn't imagine not having a rooted android. Well after a few short weeks I found myself in need of unrooting the device and restoring back to stock(for personal reasons). Upon attempting to relock the bootloader and then reflash stock firmware back to the device I was successful at getting the bootloader relocked but somehow managed to completely delete all;the System partition on the device. I CAN still however boot the phone into the bootloader(into fastboot,recovery, etc) I have TWRP recovery installed on the device but now the phone says that its got 0mb of storage on the phone. Ive spent countless hours trying to figure out how to get the phones original firmware back on the device with absolutely no luck. My current Hboot version is 1.55 and i have S-ON as well. Can someone point me in the direction of a thread where I can some how recreate the system(and other neccessary partitions) to restore the firmware?? Does HTC have anything like KIES that Samsung has where i can reflash my phone?
Click to expand...
Click to collapse
Yes HTC has a RUU (Rom Update Utility) You posted in the AT&T forums so I'm going to assume you need the AT&T RUU
You can download it directly from HTC Here
The RUU requires s-off or Relocked bootloader
you relock it with this command
fastboot oem lock
fastboot reboot-bootloader
I've tried that before the ruh fails BC the phone shows no operating system. I've tried several different ones. The one thing that I see in relation to all the ruu threads all say you should see a os version in the current field and in dont. Unless there's some other order of operations Im not aware of when trying to use them.
Sent from my GT-N7105 using XDA Free mobile app
I've solved this without an RUU. I will post a "SOLVED" thread in the development page.
Sorry for the delay folks
COrootking4life said:
Good evening,
I am reaching out to all developers and android enthusiasts here on XDA as I am completely stuck at this point. This post may get a little bit long winded but I wouldn't post if I didn't legitimately need the assistance.
So here is my situation. I have an ATT HTC ONE and I originally rooted this phone thinking that it would improve the devices battery life as I've experienced with any other android device that I've rooted. All my Samsung devices respond miraculously to rooting and couldn't imagine not having a rooted android. Well after a few short weeks I found myself in need of unrooting the device and restoring back to stock(for personal reasons). Upon attempting to relock the bootloader and then reflash stock firmware back to the device I was successful at getting the bootloader relocked but somehow managed to completely delete all;the System partition on the device. I CAN still however boot the phone into the bootloader(into fastboot,recovery, etc) I have TWRP recovery installed on the device but now the phone says that its got 0mb of storage on the phone. Ive spent countless hours trying to figure out how to get the phones original firmware back on the device with absolutely no luck. My current Hboot version is 1.55 and i have S-ON as well. Can someone point me in the direction of a thread where I can some how recreate the system(and other neccessary partitions) to restore the firmware?? Does HTC have anything like KIES that Samsung has where i can reflash my phone?
Click to expand...
Click to collapse
Sorry for the sluggish delay, due to some scheduling conflicts and other hurdles came into play but nevertheless Im posting my solved post now. head over to the ATT HTC ONE ANDROID DEVELOPMENT FORUM TO FIND THE POST LABELED "SOLVED"
Hello. Thanks in advance for your time and advice.
I've got a brand new HTC One M8, AT&T, firmware says 4.4.2 with no available updates.
I want to create an initial backup. I'm a computer technician, and just dabbling in Android, and it's important for me to make a "clone" of my phone before I proceed to wreck things. (This is a replacement phone, the last one had a hardware issue... I swear... I managed to install ViperOne onto it, for a week before the screen faded to white and died.)
I assume I'll need root access to make a proper backup. I also assume I should use Nandroid. I've not used the app before, but I'm sure I can figure it out. As far as root goes, I previously used Hasoon2000's HTC One 2014 (M8) All-In-One Toolkit, which worked well, as far as I could tell. (It's a visual basic program with scripts to download drivers, register at htcdev, get token id, submit it, unlock bootloader, flash recovery, and lots of nice ADB commands. Is this a good option to use? I hear many people use S-Off, but I don't really see a need... ?
So, I assume I'll need a new token ID from HTC, as the previous one I got corresponds to the old, malfunctioning phone.
After it's unlocked, I'd use the toolkit to grant perm root. That would be a great place to be for now. I plan to wait until the 4.4.4 update is pushed, then worry about installing a new rom.
Am I on the right track?
For the AT&T version (and most the major US carrier versions) we are lucky enough to have RUUs. So really, no need to backup the stock configuration. If you like, grab the RUUs and save them to your computer so you have them ready if and when it is needed.
Nandroid isn't a specific app, its just a generic term for a backup made with recovery. The custom recovery is your choice: TWRP, Clockworkmod, Philz.
Just a personal opinion, I would actually strongly recommend against using the toolkit for a couple reasons: most importantly using the toolkit robs you of an important learning opportunity. Doing the steps "manually" is a key way to learning your way around fastboot/adb. Doing the steps manually isn't that hard, and shortcutting the process with the toolkit really doesn't gain you much. Another key issue, is the toolkit introduces an additional point of failure. In fact, I've seen folks have trouble doing some of the steps with the toolkit; where doing the steps "manually" worked without a hitch. And the toolkit hasn't been updated for a long time, and will install an obsolete version of TWRP recovery, which in itself can cause issues.
If you used the toolkit before, you can certainly use it again. This is likely the path of "least" resistance, the the "easy" way to do things. But I wouldn't necessarily call it the "best" way to do it. If you don't already know your way around adb, I would do the steps manually. Since you have a background in computers, you will probably even find the manual process more enjoyable.
Yes, you would need to unlock the bootloader again via HTCDev.com, as the unlock bin code in based on the phone's unique IMEI.
The process would be as simple as unlocking the bootloader using HTCDev.com (very easy, the website is self-explanatory). Use fastboot to install custom recovery. Then to gain root, just flash SU or SuperSU in recovery. If you need a step-by-step guide, there is an excellent one here: http://forum.xda-developers.com/showthread.php?t=2799796
But also be aware that once the 4.4.4 OTA rolls out, you will need to return to stock recovery, and also restore any system files modifed by root, in order to install the OTA.
Thanks, redpoint73
Exactly the answer I was looking for. The guide looks great. Looks like there's a lot of useful information about reverting to stock, too. I guess I'll have a go at it now, as opposed to waiting for the update. Like you say, it's good to know things. Thanks much.
@redpoint73
Now I'm only asking cause I don't know everything. Couldn't those who have S-off just RUU the update once available instead of reverting to complete stock state(no root,no custom recovery, locked Bootlaoder)?
AT&T HTC ONE M8
jball said:
@redpoint73
Now I'm only asking cause I don't know everything. Couldn't those who have S-off just RUU the update once available instead of reverting to complete stock state(no root,no custom recovery, locked Bootlaoder)?
Click to expand...
Click to collapse
Absolutely. In fact S-off is not even required to run an RUU intended for your version (AT&T). If s-on, the added step of relocking the bootloader is all that is needed to run the RUU.
HTC seems to have gotten better about releasing the RUUs promptly. In fact, the previous (ill fated) 4.4.3 update saw the RUU and OTA roll out on the same day. Although this hasn't always been the case. On past devices, the RUUs were not released for weeks (sometimes longer) after the OTA started to roll out. And many folks don't want to wait that long.
Also, relocking the bootloader is not required to OTA, only to RUU.
Hey so here's my situation:
Installed the CM Nightly on my AT&T One M9, didn't like it, so I tried to revert to stock. I didn't want to pay $25 to S-OFF so I just tried installing various RUUs, but none would work. I read somewhere that I needed to relock my bootloader in order for the RUUs to work, so I did that, and now my phone just boots to Recovery Mode. I've tried installing AT&T RUU 2.6.502.16 (which didn't work because my phone is on a more recent firmware) and reinstalling 2.11.502.18/flashing its 0PJAIMG.zip (which didn't work because it's apparently broken). I've even tried installing T-Mobile's 2.11.531.19 RUU, which of course didn't work because my CID doesn't match and I can't change it because I'm S-ON.
I realize I went about this very badly almost from the start--no stock backup in TWRP, etc. This is my first Android phone so I've been learning this as I go and I was a bit sloppy.
I'm pretty sure I'm screwed, at least until a new update comes out or the current AT&T RUU is fixed, but I'm wondering if there's something else I can try. Any ideas? Thanks.
StageProps said:
Hey so here's my situation:
Installed the CM Nightly on my AT&T One M9, didn't like it, so I tried to revert to stock. I didn't want to pay $25 to S-OFF so I just tried installing various RUUs, but none would work. I read somewhere that I needed to relock my bootloader in order for the RUUs to work, so I did that, and now my phone just boots to Recovery Mode. I've tried installing AT&T RUU 2.6.502.16 (which didn't work because my phone is on a more recent firmware) and reinstalling 2.11.502.18/flashing its 0PJAIMG.zip (which didn't work because it's apparently broken). I've even tried installing T-Mobile's 2.11.531.19 RUU, which of course didn't work because my CID doesn't match and I can't change it because I'm S-ON.
I realize I went about this very badly almost from the start--no stock backup in TWRP, etc. This is my first Android phone so I've been learning this as I go and I was a bit sloppy.
I'm pretty sure I'm screwed, at least until a new update comes out or the current AT&T RUU is fixed, but I'm wondering if there's something else I can try. Any ideas? Thanks.
Click to expand...
Click to collapse
I do not have this phone... but...
I would go thru the bootloader unlock process again... reflash twrp...
And then probably flash the viper ROM... since it's modified stock