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.
Related
Hi there
First, I know that it might be a stupid question, but I'm new to Android.
I've read about the official unlocking method HTC offers and yesterday I tried it out, worked all fine.
But what has changed? What can I do now which I couldn't before? I don't get it! Can I flash ROMs now? How?
I can only see that it now says "UNLOCKED" at the top of the bootloader. Also, I've read about Clockwork-Mod and TW and so on, so I tried to "install" Clockwork-Mod. Failed. Now it crashes when trying to open "Recovery" in bootloader.
But main question: What can I do now, with unlocked phone?
Thanks! And don't laugh about my English... I've tried my best
Install TWRP recovery, there is a sticky in the dev section. Then you can indeed flash ROMs however since you are s-on still you will have to flash a bit differently. Search the dev section for joeykrim's flash image gui. It has all the instructions you need to flash a custom rom.
A little further explaination, since you are still s-on the kernels don't flash correctly unless you flash using fastboot or joeys gui. If you don't flash this way you can end up in a bootloop or have broken wifi and 4g etc.
3VO Sent
luckyluke02 said:
Hi there
First, I know that it might be a stupid question, but I'm new to Android.
I've read about the official unlocking method HTC offers and yesterday I tried it out, worked all fine.
But what has changed? What can I do now which I couldn't before? I don't get it! Can I flash ROMs now? How?
I can only see that it now says "UNLOCKED" at the top of the bootloader. Also, I've read about Clockwork-Mod and TW and so on, so I tried to "install" Clockwork-Mod. Failed. Now it crashes when trying to open "Recovery" in bootloader.
But main question: What can I do now, with unlocked phone?
Thanks! And don't laugh about my English... I've tried my best
Click to expand...
Click to collapse
New to Android ... One of these days I should put together a guide from start to finish.
Here are a few more details in addition to the great answer already provided in the above post. A link to my applciation, Flash Image GUI, which makes loading custom kernels a little bit simplier and possible without a computer attached to the device.
There are basically three partitions we look to commonly customize on the Android device, boot, recovery and system. Of course, there are times when we customize or upgrade other partitions but they aren't as common or as required.
Boot holds the booting kernel.
Recovery holds the recovery kernel and recovery binary.
System holds the android system.
On many HTC devices, some or all of these partitions are locked by the bootloader which is essentially a very low level write protection.
The s-off revolutionary method removes write protection on all partitions.
The HTC unlock method removes write protection on some partitions and also depends on the mode the device is booted into. This is the first time HTC has made an official unlock method through their stock bootloader. Who knows if they will improve it in the future by unlocking all partitions or if they still stick to their current model.
Hope that helps a bit more background/history to the context! Good luck!
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
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.
I am rooted, have TWRP, am running stock sense 6 with 4.4.2, s-on. I want to completely get rid of anything and everything including the root. Is there a foolproof, simple way to do that? Just a heads up I am not very good at any of this, installing an RUU or anything of the like is way out of my level. All im asking is a simple breakdown of what I have to do. I also have a Mac, so some options seem to be crossed out for me.
RUU is not above your head. Especially if you unlocked the bootloader, rooted, etc. yourself. Even if not, the RUU is a tool issued by HTC for "regular" folks (with no knowledge whatsoever of modding phones) to recover their devices in various situations.
RUU is easy:
- Relock the bootloader with the command: fastboot oem lock
- Connect the phone to PC
- Run the RUU, and the RUU program leads you through the rest.
I know you said you have a Mac, but surely you have a friend or family member with a PC that you can use for a half hour.
Honestly, IMO opinion its still easier than returning to stock by other methods, which would require:
- Finding the right stock ROM or stock nandroid for your firmware number
- Putting the stock ROM on the phone and flash with TWRP
- Find the right stock recovery for your stock ROM
- Flash using fastboot
- Relock the bootloader (depending on how "full stock" you want to go)
- Additionally, if you intend to update to current OS (Lollipop) you then need to install 4.4.4 and 5.0 OTAs to get fully current. RUU will update everything at one time.
With the above method, finding the right files is the potential pitfall; and one where many folks have trouble. So in addition to just having more steps, there is also much more potential for having problems with those steps (making the process even more time consuming and stressful).
On another note, you haven't given any background why you want to return to "stock". Once a phone is rooted, I seldom recommend going back to stock, with the exceptions of:
- You are selling or giving the phone away (you should still tell the buyer that the phone was previously modded)
- The phone was rooted by a previous owner, you have no intent to use such features, and just want to return to a fully stock condition
- You are suffering some issue that you think a return to stock will resolve (RUU is better in this case)
redpoint73 said:
RUU is not above your head. Especially if you unlocked the bootloader, rooted, etc. yourself. Even if not, the RUU is a tool issued by HTC for "regular" folks (with no knowledge whatsoever of modding phones) to recover their devices in various situations.
RUU is easy:
- Relock the bootloader with the command: fastboot oem lock
- Connect the phone to PC
- Run the RUU, and the RUU program leads you through the rest.
I know you said you have a Mac, but surely you have a friend or family member with a PC that you can use for a half hour.
Honestly, IMO opinion its still easier than returning to stock by other methods, which would require:
- Finding the right stock ROM or stock nandroid for your firmware number
- Putting the stock ROM on the phone and flash with TWRP
- Find the right stock recovery for your stock ROM
- Flash using fastboot
- Relock the bootloader (depending on how "full stock" you want to go)
- Additionally, if you intend to update to current OS (Lollipop) you then need to install 4.4.4 and 5.0 OTAs to get fully current. RUU will update everything at one time.
With the above method, finding the right files is the potential pitfall; and one where many folks have trouble. So in addition to just having more steps, there is also much more potential for having problems with those steps (making the process even more time consuming and stressful).
On another note, you haven't given any background why you want to return to "stock". Once a phone is rooted, I seldom recommend going back to stock, with the exceptions of:
- You are selling or giving the phone away (you should still tell the buyer that the phone was previously modded)
- The phone was rooted by a previous owner, you have no intent to use such features, and just want to return to a fully stock condition
- You are suffering some issue that you think a return to stock will resolve (RUU is better in this case)
Click to expand...
Click to collapse
What you said about how infuriating it is finding the right files and all is what motivated me to want to start anew, maybe I will keep root then. I read up some guides online and have a better understanding of how RUUs work now. I only have one question left, how would I input the command to relock the bootloader? I understand you have to go into the command prompt window, but do i just type it in? I thought I had to navigate to my phone through it somehow. Hopefully that made sense in some way.
xeamless said:
I only have one question left, how would I input the command to relock the bootloader? I understand you have to go into the command prompt window, but do i just type it in? I thought I had to navigate to my phone through it somehow. Hopefully that made sense in some way.
Click to expand...
Click to collapse
You still haven't provided any background on whether you rooted the phone yourself. If you did, you should already have fastboot setup on your computer; as you would have needed it to issue the bootloader unlock command. So open the command prompt, than you need to change directory to whatever folder your fastboot files (fastboot.exe if on a PC) are located. Then simply type the command.
If you don't have fastboot setup on your computer, that is a different story, and you would need to do so (can give details if you indicate that is the case).
redpoint73 said:
You still haven't provided any background on whether you rooted the phone yourself. If you did, you should already have fastboot setup on your computer; as you would have needed it to issue the bootloader unlock command. So open the command prompt, than you need to change directory to whatever folder your fastboot files (fastboot.exe if on a PC) are located. Then simply type the command.
If you don't have fastboot setup on your computer, that is a different story, and you would need to do so (can give details if you indicate that is the case).
Click to expand...
Click to collapse
So I followed everything you said and it all worked out! Thanks
xeamless said:
So I followed everything you said and it all worked out! Thanks
Click to expand...
Click to collapse
Sweet, glad it worked out for you. You're quite welcome.
I got this phone off a friend, and I have a opportunity to trade my M8 for a M9 plus cash. The problem is that the guy won't trade without the phone being completely stock with no root or any signs.
I've searched quite a bit on this forum for answers and everything is for older versions of Android. I can't find what RUU I would need or if it's even available. I seen a guide and tutorial from theunlckr, but it's from mid 2014.
I'm looking for a complete guide from start to end that will put this phone back to stock. This would be my first time and I don't know jack about what to do when it comes to this stuff. I'm very computer savvy so it shouldn't be a issue.
The info is following when I boot into recovery:
First off, the HTC logo will appear saying it's property of HTC and something about developers in red.
Software Status : Modified
Unlocked
M8_UL_CA PVT SHIP S-ON
HBOOT-3.19.0.0000
[email protected]
OPENDSP-v47.2.2-00564-M8974_FO.1024
OS-4.28.502.1
eMMC-boot 2048MB
4/20/15
There is also a Team Win application or recovery when I choose to do a factory reset.
Please if someone can help, I need to do this soon.
rlockwich said:
I've searched quite a bit on this forum for answers and everything is for older versions of Android. I can't find what RUU I would need or if it's even available.
Click to expand...
Click to collapse
You want the Lollipop (Android 5.0.2) AT&T RUU (software number 4.28) which is linked on my Index thread at the top of the General AT&T M8 forum section: http://forum.xda-developers.com/showthread.php?t=2751432
Relock the bootloader (command: fastboot oem lock) then just run the RUU (Windows executable).
rlockwich said:
I got this phone off a friend, and I have a opportunity to trade my M8 for a M9 plus cash. The problem is that the guy won't trade without the phone being completely stock with no root or any signs.
Click to expand...
Click to collapse
What "completely" stock means is a bit complicated (and may vary depending on the person). You can relock the bootloader and run the RUU. Everything will be stock, except that the phone will say RELOCKED in bootloader instead of UNLOCKED (which is the factory condition).
The only way to make it say LOCKED is to s-off by sunshine ($25) then change the flag to LOCKED. Then go back to s-on. But IMO, its not worthwhile to spend money to sell/trade a phone; and not worth the money, time and effort for something that is very minor.
Functionally, there is no difference between RELOCKED and LOCKED. The only reason anyone would care, is if they want to make a warranty claim with HTC. In that case, they may deny any claim anyway, since there is already a record of the bootloader being unlocked via HTCDev.com (tracked by the phone's IMEI). Not even sure if the warranty (1 year from purchase) would be valid, anyway for a device that has changed hands 2 times.
I would recommend you ask the buy/trade partner if RELOCKED bootloader is okay. Otherwise, find someone else to trade with.
rlockwich said:
First off, the HTC logo will appear saying it's property of HTC and something about developers in red.
Click to expand...
Click to collapse
This, and TWRP recovery will be gone once you RUU.
RUU will re-image the entire phone to stock factory (Lollipop) condition. So it will be stock ROM, stock recovery, no root, etc.
You should also remove your SD card (if one is inserted), then go into phone settings and wipe all storage, to make sure the internal storage/virtual SD is wiped of your personal data.
Will this make him be able to do OTA updates for when 5.1 comes?
rlockwich said:
Will this make him be able to do OTA updates for when 5.1 comes?
Click to expand...
Click to collapse
Yes. The only requirements for OTA are stock ROM and stock recovery, which post-RUU state satisfies both.
Note that OTA updates for the AT&T version are only available when connected to AT&T's network. So if the buyer is asking if he will get OTAs, and he happens to be using another carrier, the answer is NO. And in that case, the RUU for the next update is his best option.
It was a success! Thank you for taking the time to help me out. I really appreciate everything you've done!
Do you think it's necessary to wipe from the settings in backup/restore after doing the RUU?
I read somewhere that there are files left behind from the root, after unrooting....does the RUU wipe all of this away, so there won't be a need to do a 2nd reset after the RUU completes?
rlockwich said:
Do you think it's necessary to wipe from the settings in backup/restore after doing the RUU?
I read somewhere that there are files left behind from the root, after unrooting....does the RUU wipe all of this away, so there won't be a need to do a 2nd reset after the RUU completes?
Click to expand...
Click to collapse
Can never remember for certain; but I think RUU just wipes user data, and normally leaves internal storage intact. Not just files used for root, but personal files, too. So you will want to make sure internal storage is wiped.
Therefore, I do recommend going to Backup & Reset in Settings, pick Reset phone in order to make sure internal storage is wiped.