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.
I've had a lot of trouble upgrading to KitKat. After attempting to flash different image files for stock recovery/boot/system, I found it impossible to completely unroot the phone using the instructions posted because the phone kept re-rooting itself. Finally, I S-offed, wrote superCID, used the Telus RUU, applied the OTA downloaded to the phone, changed the CID back to GLOBA001 (my carrier is WindMobile). And finally! I know I relocked and unlocked the bootloader somewhere in the process, but I can't quite remember when.
Now, before I even think of re-rooting the phone or installing a custom recovery, I'd like to create a backup of the stock boot, recovery, and system. I tried running
Code:
fastboot boot openrecovery-twrp-2.7.1.1-zaracl.img
using the special KitKat TWRP. There's a message about boot.img being downloaded successfully but the phone reboots to a black screen.
I know that TWRP 2.7.1.0 downloaded from their website worked fine on my phone before I ran the RUU . So I'm not sure that the new TWRP is incompatible with my phone.
If I wanted to use adb instead, I'd need to root the phone before being able to pull the stock recovery, boot, and system images using adb shell. If I have to resort to rooting, is there any way to do so without flashing a custom recovery first? If there is, I might be able to unroot the phone afterward and make it stick. (Delete the supersu apk and su binary, right?)
I remember that the first time my phone attempted to download and apply the OTA automatically, my phone wiped itself. It was a lot of hard work to get it back to a usable state, but it was my own fault for not having a proper backup. I'd like to avoid making that mistake again, and have a stock backup handy on my computer in case there are carrier updates for my phone in the future.
To re-iterate, possible to back up stock everything without root? If not, possible to root without installing custom recovery?
You can no longer boot into a custom recovery, you have to actually flash it.
As far as having the stock recovery and boot, those are actually inside the OTA so you can pull it from there.
Since you'll have the stock recovery already, you can flash TWRP and use that to backup boot and system.
When you need to go stock, just use TWRP to restore your backup and then manually flash the stock recovery.
Since you made the device S-OFF, I recommend that if you need to lock/unlock the bootloader that you use the commands in this thread versus using the htcdev method as that wipes the /data/preload/ folder (as part of its normal /data wipe) which includes a few stock apps.
I had already re-locked the bootloader using the HTCdev method after the upgrade and before starting the thread. Do you think the potential loss of apps would cause any future OTAs to fail? If so, I don't mind re-doing the RUU (no important data on the phone right now). If not, I'll proceed with flashing TWRP.
Thanks for the tip on the alternate unlock method. I'll use that method the next time I need to re-unlock the bootloader.
EveKnight75 said:
I had already re-locked the bootloader using the HTCdev method after the upgrade and before starting the thread. Do you think the potential loss of apps would cause any future OTAs to fail? If so, I don't mind re-doing the RUU (no important data on the phone right now). If not, I'll proceed with flashing TWRP.
Thanks for the tip on the alternate unlock method. I'll use that method the next time I need to re-unlock the bootloader.
Click to expand...
Click to collapse
Locking the bootloader won't do anything, it's only unlocking using the htcdev token that causes the data wipe. So if you haven't unlocked using the htcdev method since running the RUU you will still have the 2 - 3 apps.
I don't know if the /data/preload/ folder is a requirement for a successful OTA update or not but I checked inside my OTA zip for my phone and it does include the 3 items stored there for the VM variant.
The unlock was AFTER the RUU. I ran the RUU, then used the OTA to upgrade to KitKat, then unlocked the bootloader again. However, I didn't notice any apps disappearing and the OTA zip for Wind also has a /data/preload folder.
*Shrugs* Seems good enough to me. TWRP, here I come!
needing wind stock stuck with wind awsy amd wont connect
I have an unlocked desire 601 it finds only wind away I'm trying to get a backup of the stock Rom to flash it does anyone k ow if there any around or even a back up I can use to try to get my phone working on wind home
jayjsteez said:
I have an unlocked desire 601 it finds only wind away I'm trying to get a backup of the stock Rom to flash it does anyone k ow if there any around or even a back up I can use to try to get my phone working on wind home
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2804427
needing help for s-off
EveKnight75 said:
I had already re-locked the bootloader using the HTCdev method after the upgrade and before starting the thread. Do you think the potential loss of apps would cause any future OTAs to fail? If so, I don't mind re-doing the RUU (no important data on the phone right now). If not, I'll proceed with flashing TWRP.
Thanks for the tip on the alternate unlock method. I'll use that method the next time I need to re-unlock the bootloader.
Click to expand...
Click to collapse
hey i have unlocked desire 601 but only says wind away and wont connect ive knoticed the wind version is the same as the other versions but im wondering do i need the wind rom in order for it to pick up the wind home i cant seem to find anywhere online the wind rom and everytime i try to s-off it saysfailed and ive followed everything is there any insite you could give me to help me with this issue if its fixable again my phone says wind away but wont connect to it and i need to get it working as its my only device and carrier i use thx
---------- Post added at 11:29 PM ---------- Previous post was at 11:16 PM ----------
EveKnight75 said:
I had already re-locked the bootloader using the HTCdev method after the upgrade and before starting the thread. Do you think the potential loss of apps would cause any future OTAs to fail? If so, I don't mind re-doing the RUU (no important data on the phone right now). If not, I'll proceed with flashing TWRP.
Thanks for the tip on the alternate unlock method. I'll use that method the next time I need to re-unlock the bootloader.
Click to expand...
Click to collapse
hey i have unlocked desire 601 but only says wind away and wont connect ive knoticed the wind version is the same as the other versions but im wondering do i need the wind rom in order for it to pick up the wind home i cant seem to find anywhere online the wind rom and everytime i try to s-off it saysfailed and ive followed everything is there any insite you could give me to help me with this issue if its fixable again my phone says wind away but wont connect to it and i need to get it working as its my only device and carrier i use thx
-Duir- said:
You can no longer boot into a custom recovery, you have to actually flash it.
As far as having the stock recovery and boot, those are actually inside the OTA so you can pull it from there.
Since you'll have the stock recovery already, you can flash TWRP and use that to backup boot and system.
When you need to go stock, just use TWRP to restore your backup and then manually flash the stock recovery.
Since you made the device S-OFF, I recommend that if you need to lock/unlock the bootloader that you use the commands in this thread versus using the htcdev method as that wipes the /data/preload/ folder (as part of its normal /data wipe) which includes a few stock apps.
Click to expand...
Click to collapse
I don't understand how you can pull the stock recovery from the OTA. I thought OTA's are immediately installed, instead of stored untill you want to install it? So, how do you backup the stock recovery?
It is saved until you want to install. When it go finishes Downloading, just choose install later. And you will be able to copy it into other storage devices and extract files and what not. I'm not sure if it stores in internal or external I'm 80% sure external sd if you have one.
Sent from my HTC0P4E1 using XDA Free mobile app
Due to a bug, I have been able to get root on my OnePlus 2 running Oxygen 2.1.1 without a wipe.
DISCLAIMER: This may not give you root on yours, and obviously it may also loose you data, so don't do it unless you know you can cope with that. YMMV, but I've documented here for posterity how to do it!
I had unlocked the bootloader previously, because my device is an import, so it is possible, though unlikely that it simply doesn't wipe on an unlock after re-lock (OTA locks bootloader).
The basic steps are :
Encrypt your device
Unlock the bootloader (this won't wipe because of encryption!)
Boot TWRP
use adb to push SuperSu to your device and then flash it
Then you will have root. Step by step instructions below.
Note that TWRP currently doesn't support encryption on our devices, so you'll have to use something other than that to back up your data if you want to use a custom rom. This simply gives you rooted stock Oxygen.
After rooting :
Code:
$ adb shell
[email protected]:/ $ su
[email protected]:/ # id
uid=0(root) gid=0(root) context=u:r:init:s0
Step 1: Encrypt your device.
This is irritating but fairly simple. You have to have fully charged your device AND keep it plugged in, and it takes ~50 minutes to complete. It's the standard android encryption, so follow any guide for this, such as https://support.google.com/nexus/answer/2844831?hl=en-GB
Step 2: Unlock the bootloader.
Again, this is well documented - here's a guide : http://forum.xda-developers.com/oneplus-2/general/guides-how-to-guides-beginners-t3146568 - The important thing is that if you're encrypted, this does not do a wipe, in my experience.
Step 3: Boot TWRP
Download TWRP from https://dl.twrp.me/oneplus2/ and save it somewhere you can find it later - I'm going to assume you're on linux and have saved it in ~/Downloads/TWRP.img
Reboot into bootloader mode (Power and Volume up) and start TWRP by issuing the following command (substituting your path to twrp) :
Code:
~$ fastboot boot Downloads/twrp-2.8.7.0-oneplus2.img
Step 4: Root it!
This is a bit tricky because once you're encrypted you can't access the SDCard, so you need a bit of magic to flash the zip.
First, do the swipe to enable modifications, then in mount, tick the /system option.
Then, on your PC, download SuperSU's .zip update from https://download.chainfire.eu/696/supersu/ (similar to above, assuming same download location) and use adb push to put it on the device in /tmp :
Code:
adb push Downloads/UPDATE-SuperSU-v2.46.zip /tmp/su.zip
Next, from the main TWRP menu, select Install. Navigate up (you start in sdcard that is empty) and into tmp, then select the su.zip file in there.
Swipe to install the zip - TWRP will complain because it can't access /data, but handily, /data is not needed to root!
Select Reboot, and viola, you have SuperSU and root! Now you can install Titanium Backup and back up your device.
Cool, perhaps renaming the title like "Unlock and root without wiping" could make more sense?
ranyardm said:
I had unlocked the bootloader previously, because my device is an import, so it is possible, though unlikely that it simply doesn't wipe on an unlock after re-lock (OTA locks bootloader).
Click to expand...
Click to collapse
OTAs don't re-lock the bootloader though...
If you've unlocked it previously, it'll stay unlocked unless you boot into fastboot mode and do a "fastboot oem lock".
Spannaa said:
OTAs don't re-lock the bootloader though...
If you've unlocked it previously, it'll stay unlocked unless you boot into fastboot mode and do a "fastboot oem lock".
Click to expand...
Click to collapse
Not true I'm afraid. The OP2 OTA to 2.1.0 did indeed relock the bootloader. I know this because I would never want to lock the bootloader, and I'm on a Chinese OP2 which came with masses of spyware, so to install clean 2.0.1 I had to unlock the bootloader originally (they managed to get the spyware into the recovery image!). Anyway, it's irrelevant to this thread how the bootloader got relocked, I just documented this fiddly way of getting an unlocked bootloader with root on a locked OP2.
ranyardm said:
Not true I'm afraid. The OP2 OTA to 2.1.0 did indeed relock the bootloader. I know this because I would never want to lock the bootloader, and I'm on a Chinese OP2 which came with masses of spyware, so to install clean 2.0.1 I had to unlock the bootloader originally (they managed to get the spyware into the recovery image!). Anyway, it's irrelevant to this thread how the bootloader got relocked, I just documented this fiddly way of getting an unlocked bootloader with root on a locked OP2.
Click to expand...
Click to collapse
Maybe my post should have said "OTAs don't re-lock the bootloader since 2.1.0"
Anyway, if your method works then great :good:
There's another way to do it here.
Can everyone who's done this attest that the data indeed doesn't get wiped?
cheekrox said:
Can everyone who's done this attest that the data indeed doesn't get wiped?
Click to expand...
Click to collapse
I'd also be very happy to have this confirmed by another party!
Confirmed. Data does NOT get wiped.
cheekrox said:
Confirmed. Data does NOT get wiped.
Click to expand...
Click to collapse
Confirmed on 2.2.0 or still on 2.1.X?
Can confirm, this still works on 2.2.0.
i didnt try this tutorial, but when i rooted my phone, my data didnt got wiped either.
will root on 6p running android n dev preview wipe phone?
Any chance this works also on 1+1? I'm desperate for a way to root without unlocking so I can install titanium/nandroid and do a full proper backup before wiping clean (battery life is utter crap). Running latest stock 6.01 COS. Never unlocked, never wiped since 15R.
Thanks!
anyone tried this on OOS 3 ?
Yeah, bump!
Now my OP2 is on Oxygen 3.0.2, and Android 6.0.1 - stock.
My phone had always been (bootloader) unlocked and rooted, since the day after I got it.
But to get the new OTA update to Oxygen 3, I tried a different method this time, where some people said you can do a temporary un-root, get the stock OTA update, and then re-root.
I followed their instructions, but I can't re-root as simple and easy as they said.
Before the process, I didn't do a nandroid backup because my sdcard doesn't have room :-|
So now I need to re-root without losing data.
And I've tried helium before, many times, and it never works for me.
Any other ideas, or has anyone tried this encryption trick yet with Oxygen 3?
Thanks!
tried it on oos 3.1:
everything worked until a bootloop at the last restart.
also twrp asked me to unlock the phone, i did that.
what to do now?
Did anyone ever have any success with this approach on 3.1?
LoL How do you boot/flash TWRP on locked bootloader?
aIecxs said:
LoL How do you boot/flash TWRP on locked bootloader?
Click to expand...
Click to collapse
Lol, you can't.
For the life of me I cant root it and I have an sd card id love to save apps to...... I do have a laptop. So app or laptop is fine. Any help is appreciated thank you
I was able to unlock the boot loader through htcdev website bout as far as I got though
I second that. I can find hundreds of sites, videos , and downloads about rooting the 626, but I have a 625 and there is nothing. Help! Want to root my 625
Htc dev
crypto spook said:
I was able to unlock the boot loader through htcdev website bout as far as I got though
Click to expand...
Click to collapse
I've never had trouble with HTC DEV and I can't seem to figure out how to get my Cricket HTC 625 into fastboot mode.
Any advice?
collatz said:
I've never had trouble with HTC DEV and I can't seem to figure out how to get my Cricket HTC 625 into fastboot mode.
Any advice?
Click to expand...
Click to collapse
If you can't get it via button combo then use enable USB Debugging and use adb: adb reboot bootloader
For adb and fastboot: http://forum.xda-developers.com/showthread.php?t=2317790
Rooting via Kingroot supposedly works once the bootloader is unlocked as mentioned here: http://forum.xda-developers.com/htc-desire-c/help/sowftware-update-t3255022
They didn't mention which software update it was on, but knowing Cricket and HTC, they probably never released but the original one so might be worth a try. Keep in mind that there does not seem to be an RUU to restore the phone if something goes wrong so proceed at your own risk.
Rooting is possible
Queen_Haze said:
For the life of me I cant root it and I have an sd card id love to save apps to...... I do have a laptop. So app or laptop is fine. Any help is appreciated thank you
Click to expand...
Click to collapse
It can be done by following HTCdev inductions. I did but it took a few tries to unlock the bootloader. After that any progress will root it. Even Kingroot. But there is no recovery for that device. So it's editing your stock rom. So stay backed up. The twrp 626S recovery will flash to it, I been playing with it but can't say if any rom will flash successfully yet. so my words should only be taken as offering my personal experience not as any professional advice
freeatlast34 said:
It can be done by following HTCdev inductions. I did but it took a few tries to unlock the bootloader. After that any progress will root it. Even Kingroot. But there is no recovery for that device. So it's editing your stock rom. So stay backed up. The twrp 626S recovery will flash to it, I been playing with it but can't say if any rom will flash successfully yet. so my words should only be taken as offering my personal experience not as any professional advice
Click to expand...
Click to collapse
Thank you I wish I would have seen this sooner though.. I sat on it and cracked the screen and my digitizer dont stand a chance lol oh well.:crying:.
Root htc 625 .. use twrp for the HTC desire 626s as it works with the 625 as well.. First unlock bootloader, I downloaded java (offline) version and it worked fine, then HTC manager. Then I downloaded the usb drivers for the phone(may not be needed). Then adb and fastboot (not from HTC link, found it on Google which worked much faster to download. Noe after bootloader unlocked kingroot will root it or flash the twrp img using command prompt, just type flash recovery and the name of the twrp file.. now I had to type - flash recovery twrpblablabla.img. img, so I had to add *.img at the end so it had the twrp name which ended in .img and then i had to add another - .img ..... not sure why but I was messing around and that's what got it flashed. Then I flashed superU using twrp recovery.. now I did root with kingroot after bootloader was good but that's cause the whole (.img) thing. I went back after and got the adb command to do it the way I wanted to at first.. plus rooted another HTC 625 that way..
Any questions message me I will help and can send links to the files needed.. Mau. Thing was using twrp for 626s and the .img added at the end so it looked like twrp3.2.1.img.img )
May have had a space before the last .img , can't remember so if it don't work for you try that. Help needed just ask I will be glad to help as it took me a long time to get the right info and actually do it.
Anyone have j727U and got twrp on it let me know, I will pay.