Hello all, I used the htc unlock method, but I am not able to flash a different radio version.
Does anyone know how to do that?
(Just booting into bootloader does not do the trick like it would normal unlock methods)
Thanks.
Anyone?
Sent from my PG86100 using XDA App
have you tried the commands
adb reboot bootloader
fastboot boot recovery.img
and flashing the radios from fastboot? or FlashimageGUI (which probably will not work for radios)
I have been wondering this myself. I have not heard of any methods that have come up to allow this recently. Same thing goes for splash images as I havent seen any method for those.
I have an idea of how it may be possible though. Perhaps someone else with a bit more knowledge can chime in to let us know if it is possible or not.
Anyhow.
Being officially unlocked I don't believe that ROOT is an issue like it is on an unofficial method. I know typically you would NOT accept an OTA to prevent the loss of ROOT. However, being an officially unlocked device, I am not sure if it matters.
I know that when I unlocked my device I had to manually unlock it, then I installed my recovery, then I simply flashed SU to it. My thought is that you can take the OTA. If the OTA doesn't work, you may have to re-lock the device, then run the OTA. But I believe the OTA would be safe. Once OTA completed, then flash your unlock token again, put recovery back on, then flash SU again.
Or I believe you could also wait for the new RUU instead of an OTA. Put on stock ROM, re-lock, run RUU, re-unlock, install recovery, flash SU.
The problem is that you may not be able to flash back to the previous radio once you are done.
Any thoughts on this?
UPDATE: I recently (like two minutes ago) learned that an RUU will not update a radio. I was under the impression that they did. Since it will not, I guess the RUU method will not work. Still curious about the OTA method though.
From the HTCDev Q and A:
HTCDev said:
Why is my security still on (S-On) after I have unlocked my bootloader?
Your device is shipped with Security on (S-ON) to protect your system software configuration (such as the bootloader, radio, boot, recovery, system and others). After you have unlocked the bootloader, however, you will have lifted the restrictions on boot, recovery and system. This means you can customize boot, recovery and system images on your phone as you desire. You can easily see that you have successfully unlocked the bootloader by looking at the top of the screen when entering the bootloader screen. Security is left on to protect things like the radio, and SIM lock.
Click to expand...
Click to collapse
yousefak said:
From the HTCDev Q and A:
Click to expand...
Click to collapse
Well, yeah. The S stays on to protect the radio.
But the S would be on regardless if you never rooted to begin with, but an OTA would allow the radio to update. So, my thought is that you can potentially take an OTA with the HTC unlock method and get the new radio.
If it were me, I would save my titanium file to my PC (just as a precaution), I would re-lock my device using fastboot oem lock, then I would run the RUU that matches my current software version. This would return me to stock/unrooted. At this point you should be able to accept an OTA. The OTA updates your radio/software/etc. Once you update, flash the unlock token again, then flash the superuser binary back onto the phone. Now, this would be contingent that HTC doesn't go back on their word and they dont push an OTA that prevents you from unlocking the phone.
Now, Ill admit I am not a developer, so I am not an expert, but it is my understanding that once it is unlocked putting root on the phone is pretty straight forward. You don't have to come up with a root method such as revolutionary, etc. It should simply allow Superuser because it is unlocked. If this is not the case, then Ill admit that my thought process is flawed. However, if it is the case, then why not return to stock, take an OTA, unlock, re-root, use titanium? Like I said, may not be able to return to previous radio, but why would you anyhow?
mildlydisturbed said:
have you tried the commands
adb reboot bootloader
fastboot boot recovery.img
and flashing the radios from fastboot?
Click to expand...
Click to collapse
Can someone tell me how exactly to accomplish the above?
I ran these commands and the it said "Installing update..." but the radio remains the same.
Thanks again.
Related
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
Hi everyone.
I'm S-off, SuperCID, 4.16.401.9 firmware, and I re-locked my bootloader while troubleshooting an adb problem.
Is there a simple fastboot command that'll unlock my bootloader again?
I can flash recoveries via the Flashify app, but I can't do much via adb anymore.
Thanks!
How did you unlock it the first time? HTC Dev Im assuming,should still have the unlock token bin file...thats run from bootloader via fastbootusb command...This should be in Questions and Answer forum...??
BBEgo said:
Hi everyone.
I'm S-off, SuperCID, 4.16.401.9 firmware, and I re-locked my bootloader while troubleshooting an adb problem.
Is there a simple fastboot command that'll unlock my bootloader again?
I can flash recoveries via the Flashify app, but I can't do much via adb anymore.
Thanks!
Click to expand...
Click to collapse
Wonders_Never_Cease said:
How did you unlock it the first time? HTC Dev Im assuming,should still have the unlock token bin file...thats run from bootloader via fastbootusb command...This should be in Questions and Answer forum...
Click to expand...
Click to collapse
That's weird.... I thought I posted this in the Q&A forum. I was just in there looking for it and I thought it'd gotten deleted or something. Oh well.
Mods, please feel free to correct my goof.
I didn't use HTCDev to unlock. I just did Sunshine and it handled everything. S-off, unlock, and root - Talk about painless! After that I installed a custom recovery (Philz) and I was off to the races.
So I decided to SuperCID my phone so I can install whatever I want. No problem.
Then I tried to install 5.0.1 firmware (4.16.1540.8) so I could run SkyDragon, but the firmware posted on page 1 in the thread would not install- 4.16.1540.8
Kept giving me "FAILED (REMOTE:24 parsing android-info fail)"
I was able to install 4.16.401.9 with no major headaches, once I found a sensible upgrade path. That one is working fine, but I don't understand why 4.16.1540.8 would not install.
After googling the error, I found a post from Scotty a while back that said the phone wanted to see a stock recovery, locked. So I thought I'd throw the old recovery back on and do the 'fastboot oem lock' command . I didn't think it would impact the phone's operation since it is S-off. Well, the command worked, but I still wasn't able to flash the dang firmware I wanted to my phone.
So now I'm S-off, locked bootloader, PhilZ recovery (put it back on with Flashify), SuperCID, on Lollipop, and I guess everything is ok. But I still don't understand why the phone wouldn't take the firmware.
Any ideas? Thanks in advance.
If you ran sunshine on it,you can run it again i believe on that same device. It should unlock it again,if not then can try htcdev as it also uses fastboot to unlock as long as you can get adb to show needed code.
BBEgo said:
After googling the error, I found a post from Scotty a while back that said the phone wanted to see a stock recovery, locked. So I thought I'd throw the old recovery back on and do the 'fastboot oem lock' command . I didn't think it would impact the phone's operation since it is S-off. Well, the command worked, but I still wasn't able to flash the dang firmware I wanted to my phone.
Click to expand...
Click to collapse
In the past (at least on my One X EVITA) my understanding was that s-off meant that all security was bypassed. Meaning that bootloader check was effectively bypassed.
This isn't the case for the M8. From what I can tell a LOCKED bootloader still prevents you from flashing anything that isn't signed (anything "unofficial") even if s-off.
However, having an UNLOCKED bootloader doesn't seem to affect anything while s-off. Meaning you can do things like RUU when UNLOCKED (which normally needs to be LOCKED or RELOCKED if s-on).
In short, I don't ever recommend relocking the bootloader if s-off on this device. There isn't any reason to, as far as I can tell. Meaning, having an UNLOCKED bootloader doesn't prevent you from doing anything. However, a RELOCKED bootloader does (even when s-on) prevent some things.
FOUND THE RECOVERY (See below)
Right now my goal is to go back to stock to flash the OTA Update. I am running my nandroid back up I first made when which is the 4.4.4 w/ Software # 1.58.502.1. and right now I have TWRP as my recovery.
Also can someone confirm something for me. This nandroid I am running is rooted obviously and has SuperUser on it. If I go back to the stock recovery can I still do the OTA update even though SuperUser is there and the phone is unlocked?
Also in order to get the stock recovery back on the phone I need to use ABD and the windows command prompt method correct?
Thanks
found this link and was able to find the stock recovery finally. I clicked "Non-WWE- Recovery Images" Ten on the site it opens I clicked the more recoveries folder at the top and 1.58.502.1 was the first one.
http://forum.xda-developers.com/showthread.php?t=2701376
Now the only thing I need to know is if going back to stock recovery will allow me to update to OTA even though there is SuperUser on my device and even though I am rooted and unlock (S-on)
magicbumm328 said:
found this link and was able to find the stock recovery finally. I clicked "Non-WWE- Recovery Images" Ten on the site it opens I clicked the more recoveries folder at the top and 1.58.502.1 was the first one.
http://forum.xda-developers.com/showthread.php?t=2701376
Now the only thing I need to know is if going back to stock recovery will allow me to update to OTA even though there is SuperUser on my device and even though I am rooted and unlock (S-on)
Click to expand...
Click to collapse
As long as the ROM is stock (nothing modified by root) and stock recovery, you can update by OTA (root okay, unlocked bootloader okay).
Another option, just relock the bootloader and run the 4.4.4 RUU. It saves you from all the hassle (finding stock ROM and stock recovery), plus installing 2 OTAs. Only reason to do it the way you are, is to keep user data (RUU wipes phone) and it also saves you from having to relock.
redpoint73 said:
As long as the ROM is stock (nothing modified by root) and stock recovery, you can update by OTA (root okay, unlocked bootloader okay).
Another option, just relock the bootloader and run the 4.4.4 RUU. It saves you from all the hassle (finding stock ROM and stock recovery), plus installing 2 OTAs. Only reason to do it the way you are, is to keep user data (RUU wipes phone) and it also saves you from having to relock.
Click to expand...
Click to collapse
Well I do have the stock ROM. Idk if it having super user on it counts as being modified by root though? If not then its fine. And as mentioned I found the stock recovery as well.
The only reason I was looking to do it this way was because I do not really know what RUU is or how to do any of it. Idk how difficult it would be to relock the boot loader then figure out the RUU thing. Idk what the differences are between that and my phone being rooted as it is now are. I'll have to see if there is a thread that explains this RUU thing to me.
Thanks for the help and suggestion too btw
magicbumm328 said:
Well I do have the stock ROM. Idk if it having super user on it counts as being modified by root though? If not then its fine.
Click to expand...
Click to collapse
SuperUser is same as root, and is fine.
When I say "modifed by root" that often is when a user deletes "bloatware" they don't want, or adds apps, or modifies apps in the system partition.
If you didn't explicitly do any of those things, you should be fine. You will know this is the problem when you install the OTA, as the install will fail with the error message that the "system has been modified".
magicbumm328 said:
The only reason I was looking to do it this way was because I do not really know what RUU is or how to do any of it. Idk how difficult it would be to relock the boot loader then figure out the RUU thing. Idk what the differences are between that and my phone being rooted as it is now are. I'll have to see if there is a thread that explains this RUU thing to me.
Click to expand...
Click to collapse
RUU = ROM update utility
RUU is super easy, you don't really need much guidance to use it. LOCKED or RELOCKED bootloader is required to run it (UNLOCKED if okay if you have s-off). PC required, and the RUU will wipe the phone (so backup any personal data you want to keep, into your PC, cloud, etc.). Aside from those points, RUU is a self-explanatory executable (.exe) program that runs from your PC, and simple to use.
Relocking the bootloader is accomplished easily with a single fastboot command (after connecting phone to PC and booting into fastboot mode): fastboot oem lock
This is also assuming you did the bootloader unlock yourself, and therefore have fastboot/adb setup on your computer.
Running the RUU itself (after relocking the bootloader) is very easy. Boot into OS (some folks have better success being booted into fastboot mode, but I think the RUU is designed to run when booted into OS), connect to PC, then just run the RUU executable on your PC. The RUU executable will then just guide you what you need to do. Its mostly automated, you just need to confirm a few dialogue screens, etc. The RUU will reboot the phone a couple times, install the needed files automatically, and that's really it.
However, since you seem confidant you already have a stock ROM and corresponding stock recovery, I suppose the RUU doesn't gain you too much. But if you hadn't done those steps already, it often saves folks the hassle of tracking down the right stock ROM and recovery for their CID and current firmware. RUU in my opinion is a cleaner install, as it installs a complete stock image (not just updating piecemeal, like an OTA often does).
Also, since OTAs typically need to be installed in sequence, you will probably need to OTA to 2.23 software, than another OTA to 3.42 software. As RUU is a complete image, it would get you to 3.42 software in one fell swoop.
One other thing to note, is that if you are for some reason not connected to AT&T's network (using another carrier, another country, etc.) you will not get any OTAs on the AT&T branded device. AT&T oddity here, most other version will still OTA, even when not connected to a specific carrier. In contrast the AT&T RUU is able to be downloaded and run by anyone with an internet connection and PC (regardless of country, carrier, etc.). I'm under the assumption that most folks on this forum section are on AT&T's network, although I know that some are not (you haven't stated either way).
RUU links are included on my Index thread under heading "RUUs": http://forum.xda-developers.com/showthread.php?t=2751432
Aside from wiping the phone (OTA keeps user data, but you may end up wiping anyway if you run into bugs after OTA), the other downside to RUU is that you need to relock the bootloader. Then you need to unlock the bootloader again (via the HTCDev.com site, or alternately sunshine) if you want to install custom recovery, install custom ROMs, root, etc.
So the choice is really yours (RUU versus OTA). I'm just giving it as an alternative.
Hey Everyone! So i will be receiving my M8 i got used in the mail on monday and i'm doing some research because it is softbricked due to no OS being installed. It is (presumably) S-Off with Bootoader locked and "possibly" no custom recovery. What i'm planning to do is once the battery is charged completely.
-Connect it to my PC (windows)
-Power into fastboot
-Run the stock AT&T RUU and get everything running and up to date.
From there i will be unlocking the bootloader, custom recovery, root, and all the good stuff.
I'm just wanting to know from the way more knowledgeable folks then i when it comes to this stuff, is if this is the proper procedure. Is there anything else i should do first or after? Any help will be great! I'll know more tomorrow night on if recovery is installed or not, but i'm going with the opinion that there is no custom recovery, as i feel this would be harder.
any help would be GREATLY appreciated!
I agree with the above described approach. Especially since its not clear what the previous owner did (appears previously bootloader unlocked, s-off, then possibly a botched return to stock attempt?) its good to run the AT&T RUU to return to a full stock "baseline" image to all partitions.
Since you are going to run RUU, it doesn't matter whether custom recovery is currently installed or not. The RUU will install the stock recovery image.
After RUU, unlock the bootloader via HTCDev.com. Then install current version TWRP and flash SuperSU 2.46 to obtain root (older versions SuperSU won't work on Lollipop - common mistake).
redpoint73 said:
I agree with the above described approach. Especially since its not clear what the previous owner did (appears previously bootloader unlocked, s-off, then possibly a botched return to stock attempt?) its good to run the AT&T RUU to return to a full stock "baseline" image to all partitions.
Since you are going to run RUU, it doesn't matter whether custom recovery is currently installed or not. The RUU will install the stock recovery image.
After RUU, unlock the bootloader via HTCDev.com. Then install current version TWRP and flash SuperSU 2.46 to obtain root (older versions SuperSU won't work on Lollipop - common mistake).
Click to expand...
Click to collapse
Thank you so much Redpoint! I only have a small amount of knowledge with this area. I've sideloaded an OS over ADB due to a mistake i made with no OS on an old tablet, but never had to deal with possibly stock recovery with a locked bootloader, so knowing my approach will presumably work is a real relief.
Thank you again!!!:good::fingers-crossed:
Hello, so I've been trying for a while to unlock my bootloader and at this point I'm quite confused. For whatever reason the power button + volume down combo nation does not load my phone into the bootloader from the off state. Instead it boots my phone regularly. This itself is is not a problem because I can boot it into the bootloader using adb. But inside the bootloader I can move up and down using the list but can't use my power button to select anything. I've also tried booting into recovery and the volume and the power button to choose works fine. I'm just confused at this point and a little frustrated because all I would like to do is install paranoid android, and have not had any problems with past devices. Any help would be appreciated! Thank you.
That is some strange behavior, I agree.
Its been a long while since I unlocked the bootloader, so I don't completely remember what is required. I assume you need to use the vol and/or power buttons to select to unlock; and that is your main problem?
If so, that is a tough one. One thought is to RUU to stock, to eliminate the possibility of some software glitch causing your problem.
Otherwise, plan B is to use sunshine to s-off, than unlock the bootloader. Not sure if that would work, and its an expensive experiment to try ($25). But if it does work, s-off is a nice thing to have. Not expressly needed to flash ROMs, of course. But s-off does allow some other nice tricks, like being able to flash radios, modified hboots, change CID/MID, and removed the requirement to relock the bootloader to RUU.
redpoint73 said:
That is some strange behavior, I agree.
Its been a long while since I unlocked the bootloader, so I don't completely remember what is required. I assume you need to use the vol and/or power buttons to select to unlock; and that is your main problem?
If so, that is a tough one. One thought is to RUU to stock, to eliminate the possibility of some software glitch causing your problem.
Otherwise, plan B is to use sunshine to s-off, than unlock the bootloader. Not sure if that would work, and its an expensive experiment to try ($25). But if it does work, s-off is a nice thing to have. Not expressly needed to flash ROMs, of course. But s-off does allow some other nice tricks, like being able to flash radios, modified hboots, change CID/MID, and removed the requirement to relock the bootloader to RUU.
Click to expand...
Click to collapse
I think I've seen RUU before but for whatever reason I couldn't find it for my phone. Would it make any difference that the phone is AT&T, because from what I've seen people who have the AT&T smartphone tend to run into problems, just not mine.
EDIT: I just took a look at sunshine and am confused, is it an android app that does the s-off? Sorry for what I assume are common knowledge. Looking at sunshine, running 5.1.1 it looks like I need to have to bootloader unlocked to root the phone.
Jkaspar said:
I think I've seen RUU before but for whatever reason I couldn't find it for my phone.
Click to expand...
Click to collapse
All AT&T RUUs are linked on my Index thread: http://forum.xda-developers.com/showthread.php?t=2751432
Be aware that you can only run the RUU version same or higher than what is on the phone (no "downgrading" unless you have s-off).
Jkaspar said:
Would it make any difference that the phone is AT&T, because from what I've seen people who have the AT&T smartphone tend to run into problems, just not mine.
Click to expand...
Click to collapse
There isn't any reason why ATT would be any harder to bootloader unlock than any other version M8, if that is what you mean.
Jkaspar said:
EDIT: I just took a look at sunshine and am confused, is it an android app that does the s-off? Sorry for what I assume are common knowledge. Looking at sunshine, running 5.1.1 it looks like I need to have to bootloader unlocked to root the phone.
Click to expand...
Click to collapse
Yes, sunshine is an app that will s-off the phone, and then also has the option to unlock the bootloader without HTCDev.com (which is fairly trivial once s-off, think it can also by done via adb commands).
Latest Android version for the ATT M8 is 5.0 (.1 or .2, I can't remember exactly).
I'm not sure which versions will work with sunshine without prior root. But you can always install the sunshine app, and it will tell you whether it can s-off or not (and you won't be charged any $ unless it can s-off).
If you do need root before sunshine, some folks have had luck with towelroot (might be temp root, I can't recall). But yes, it complicates what is already just an idea, and not a sure fix by any means.
Sunshine from what I just tried requires root to be installed for the current android I am on. I also just tried using towelroot and it said that my phone was not supported. I am currently in school but I will try the RUU when I get a chance.
Okay so I did the RUU and it worked fine. Booted into the boot loader and nada. Still no luck with the power button. Choosing in recovery still works however. Is there a way to do it purely using adb commands?
You have to unlock with fastboot commands
Like to the screen where it gives me an option to either unlock the bootloader or not? I can get there fine, I just can't choose the yes I want to unlock option.
Jkaspar said:
Like to the screen where it gives me an option to either unlock the bootloader or not? I can get there fine, I just can't choose the yes I want to unlock option.
Click to expand...
Click to collapse
No, that requires button response from the phone
Right which is my main problem