Related
Ok so this is what i did
i installed stock recovery and locked bootloader using this TUT http://forum.xda-developers.com/showthread.php?t=2470340&highlight=unlock+bootloader
everything went good had some issue with update and nandroided back to original took the updates everything good to this point now on 4.3
I am still s off boot loader shows locked now my problems started
tried to unlock using same TUT as above won't go
made sure debug was checked
adb does not see my device but fastboot does
tried to fastboot flash recovery no go says remote not allowed
tried to fastboot flash boot image no go says remote not allowed
I think it has to do with boot loader being locked but without adb how do I unlock any help would be appreciated
update
I have removed and reinstalled the latest drivers I can see phone in windows and browse it no problems.
I reinstalled adb and rumrunner for my version .15 do i need to ruu something?
any help appreciated
bregga said:
I have removed and reinstalled the latest drivers I can see phone in windows and browse it no problems.
I reinstalled adb and rumrunner for my version .15 do i need to ruu something?
any help appreciated
Click to expand...
Click to collapse
This isn't gonna be what you want to hear probably.
You should not have relocked your bootloader before taking the OTA.
In my opinion, you should not have taken the OTA at all.
I made rooted stock roms, so that 3,000 people didnt have to do the stock rom, recovery, restore boogie.
This also reduces the risk of these types of mishaps.
The bootloader does not need to be relocked to take an ota.
You now have a locked bootloader and are on an OTA version which does not yet have a Rumrunner version.
If you cannot get your unlock token to take, you are SOL until Rumrunner updates.
You said you grabbed the version for .15, well that is what you were on prior to the OTA, you are now on 2.10.605.1 as far as I know.
If I am wrong, someone else correct me. Maybe I am missing something here...it has been a long day.
EDIT:
Sounds like you got it somewhat worked out.
A rooted boot.img would help your adb situation, such as the one I put in the stock rooted roms.
another update
I ran ruu and installed rumrunner hboot and flashed a twrp recovery both went fine using fastboot commands and i have a custom recovery again
and root but still cant adb its weird I have never had a issue with adb before
santod040 said:
This isn't gonna be what you want to hear probably.
You should not have relocked your bootloader before taking the OTA.
In my opinion, you should not have taken the OTA at all.
I made rooted stock roms, so that 3,000 people didnt have to do the stock rom, recovery, restore boogie.
This also reduces the risk of these types of mishaps.
The bootloader does not need to be relocked to take an ota.
You now have a locked bootloader and are on an OTA version which does not yet have a Rumrunner version.
If you cannot get your unlock token to take, you are SOL until Rumrunner updates.
You said you grabbed the version for .15, well that is what you were on prior to the OTA, you are now on 2.10.605.1 as far as I know.
If I am wrong, someone else correct me. Maybe I am missing something here...it has been a long day.
EDIT:
Sounds like you got it somewhat worked out.
A rooted boot.img would help your adb situation, such as the one I put in the stock rooted roms.
Click to expand...
Click to collapse
I had no problem taking the OTA myself.
I posted how i did it earlier here step 2: http://forum.xda-developers.com/showpost.php?p=48677845&postcount=2
I am kinda lost on a few things as to why you should not take the OTA if a can flash superuser after wards?
carm01 said:
I had no problem taking the OTA myself.
I posted how i did it earlier here step 2: http://forum.xda-developers.com/showpost.php?p=48677845&postcount=2
I am kinda lost on a few things as to why you should not take the OTA if a can flash superuser after wards?
Click to expand...
Click to collapse
I'm not saying that you can't take the OTA. Obviously you can, I posted roms made from it, right?
I did say there is no need to relock.
I'm not gonna go over it a bunch as to why it's just not a wise idea for the common user.
But you must have noticed the flood of users getting confused, and/or stuck when trying to do so.
It's not that hard to do it successfully, no.
Is it really necessary to go through that, when the same thing can be had by simply flashing the firmware and rooted rom?
I guess my point isn't so much that you can't take the OTA, as much as it is, why? It's a bad habit for a rooted user to get into honestly.
Why go through that? You can flash the stock rooted firmware and rom and not have to do the hokey pokey and turn yourself around.
But maybe I see it differently, I don't know.
santod040
I locked the bootloader because in the threads it says it needs to be locked to take update.
in the TUT it also states that
"this thread will let you unlock your bootloader without htcdev,or let you change your hboot watermark from relocked or locked back to stock."
Thought it spoofed the software to make it think it was locked oh well no biggie I thought if bootloader was unlocked or relocked ota's would fail like mine was getting error 410
santod040 I have been looking at your roms and "i'm not trying to kiss your but" they look nice and get good reviews but I wanted to stay stock
nusense is the one i was really looking at hard but like i said wanted to run stock
I can wait for a new rumrunner no problem there and if it never gets done oh well I am now rooted and have twrp installed and kitkat next month "well the way verizon is everyone else will have kitkat and we will have to wait a month or so before we get it"
and i have not seen anyone else say that adb does not work with 4.3 update that is why I was asking about it to see if anyone else had a issue with adb not working after update and what if anything they did to get it back without adb rumrunner is not going to work for me anyway
bregga said:
I locked the bootloader because in the threads it says it needs to be locked to take update.
in the TUT it also states that
"this thread will let you unlock your bootloader without htcdev,or let you change your hboot watermark from relocked or locked back to stock."
Thought it spoofed the software to make it think it was locked oh well no biggie I thought if bootloader was unlocked or relocked ota's would fail like mine was getting error 410
santod040 I have been looking at your roms and "i'm not trying to kiss your but" they look nice and get good reviews but I wanted to stay stock
nusense is the one i was really looking at hard but like i said wanted to run stock
I can wait for a new rumrunner no problem there and if it never gets done oh well I am now rooted and have twrp installed and kitkat next month "well the way verizon is everyone else will have kitkat and we will have to wait a month or so before we get it"
and i have not seen anyone else say that adb does not work with 4.3 update that is why I was asking about it to see if anyone else had a issue with adb not working after update and what if anything they did to get it back without adb rumrunner is not going to work for me anyway
Click to expand...
Click to collapse
I can understand wanting to stay stock.
I was just suggesting flashing a pure stock rooted rom.
As I said though, relocking was not necessary.
Hello fellow TMO brethren....
I just got the M8 maybe a week ago... I was busy and had to wait before I could pull up XDA and start reading about this phone (getting root, etc.). Before this, I unfortunately allowed a few updates (2 maybe?) to install, which I believe will prevent me from using Firewater for S-Off... but no big deal....will get sunshine when I need it. However, though firewater won't work, I had no problem using HTCDev to unlock the bootloader (didn't know of towelroot at the time), flashing TWRP 2.8.0.1, and installing SuperSU....so I am currently rooted with stock Rom...
Further...I have not touched any applications. And although I have unlocked the bootloader using HTCDev, my calculator and flashlight are still available. I have read in this M8 general forum that the flashlight and calculator are deleted when you unlock the bootloader using HTCDev... This did not happen to me. Does anyone know if this is this just a T-Mobile thing? or has this changed for all carriers?
Anyway, I am now getting notice for yet another update...So I might as well install it. As we all know, I need to re-flash the stock recovery to get the OTA. Here is where I am confused. My current firmware is 2.22.531.5. I don't know what firmware I had a week ago when the phone was purchased.
This was the info on the bootloader screen yesterday, immediately prior to unlocking the BL or rooting the phone:
[btw, can someone tell me how to do a info dump from the bootloader?? is it just an option I missed?]
*** LOCKED ***
M8_UL PVT SHIP S-ON
HBOOT-3.18.0.0000
Radio-1.19.213311491.03G
OpenDSP-v38.2.2-00542-M8974.0311
OS-2.22.531.5
eMMC-boot 2048MB
Jul 16 2014,03:33:24.0
1. My first question is what version of the stock recovery do I use?? On the page that contains the stock recoveries, it only shows these two:
Stock Recovery - 1.12.531.19
Stock Recovery - 1.57.531.7
2. Secondly, and I am really irritated about this.... but I never went and accepted the Google Drive free 65GB promo offered by HTC. When I start google drive it states it cannot determine the user (or something like that). I read elsewhere that this is because I unlocked the bootloader. I will do whatever it takes to get HTC to give me this because I think it is pretty low that they would invalidate the offer to anyone who has unlocked the bootloader pursuant to their website, their instructions, and their so-called "open atitude". Obviously I can re-lock the bootloader, but I do not know if that will matter. Plus... if they say that I requested a token .bin file to unlock, I can say that I changed my mind and decided not too. OR, I can get Sunshine, get s-off, and use the s-off ability to relock the bootloader. Does anyone have any advice on any of this?
3. Any general advice from anyone based on the info above??? (lI don't want to foreclose any other options by upgrading or whatever... ).
Thank you very much in advance!
P
NB: Wanted to mention that last night I was about to use Titanium to freeze and/or uninstall some crap software I didn't want, and to that end, disabled Amazon, Facebook, Facebook for HTC, and Kid Zone (and uninstalled Amazon MP3, which is not a system app). Just an FYI... disabling one (or more) of these apps (maybe Kid Zone?) prevented Wifi calling from functioning correctly...it would not let me call and every in-call received while on wifi calling went straight to VM. I have renabled the above apps to get wifi-calling working again, but also because I want to install this update and figured that disabling/freezing any original stock apps might cause problems. I will look around for a thread on safely deleting apps after I get this udpate...
Try this for getting your drive space.
http://forum.xda-developers.com/showthread.php?t=2708571
Its now 100GB so its definitely worth a shot. As for getting back to stock for an update you can always use a RUU since relocking your bootloader will drive space then unlocking it again after will cause a factory reset anyway. Back up everything that isnt already, relock with the instructions from the thread I linked, run a ruu to get back to stock, update the system, then unlock your bootloader again with your unlock code bin file.
phil.culler said:
Try this for getting your drive space.
http://forum.xda-developers.com/showthread.php?t=2708571
Its now 100GB so its definitely worth a shot. As for getting back to stock for an update you can always use a RUU since relocking your bootloader will drive space then unlocking it again after will cause a factory reset anyway. Back up everything that isnt already, relock with the instructions from the thread I linked, run a ruu to get back to stock, update the system, then unlock your bootloader again with your unlock code bin file.
Click to expand...
Click to collapse
OK... that sounds like great info.... But to confirm though... I need S-off to relock bootloader. This is because I am essentially going back to factory default lock (without dealing with HTC at all). And by doing this, and then flashing the RUU (backing up everything first of course), I will be back to square one stock. For one, this will make it tough for HTC to claim I unlocked the bootloader (minimizing potentially any dispute over Google Drive promo). Then I would get any/all outstanding updates. I guess if I need S-off, then I would need to get sunshine, so I could just let that app re-unlock the bootloader. instead of using the .bin file (presuming I need s-off)?
Sorry... just confused as to when and for what specifically I need S-off (as your link emphasizes this).
Thanks a lot!!!!:good:
syntropic said:
OK... that sounds like great info.... But to confirm though... I need S-off to relock bootloader. This is because I am essentially going back to factory default lock (without dealing with HTC at all). And by doing this, and then flashing the RUU (backing up everything first of course), I will be back to square one stock. For one, this will make it tough for HTC to claim I unlocked the bootloader (minimizing potentially any dispute over Google Drive promo). Then I would get any/all outstanding updates. I guess if I need S-off, then I would need to get sunshine, so I could just let that app re-unlock the bootloader. instead of using the .bin file (presuming I need s-off)?
Sorry... just confused as to when and for what specifically I need S-off (as your link emphasizes this).
Thanks a lot!!!!:good:
Click to expand...
Click to collapse
It looks like you will need S-Off to factory lock the bootloader. S-Off allows you to make changes to otherwise protected areas of the file system. To clarify, I haven't tried this method myself as I haven't had a need to factory relock my device yet. I ran full stock for months before I rooted. As for HTC knowing whether or not you unlocked your bootloader, if you used the HTCDEV method then they have record of you receiving an unlock token from them but if they go into bootloader for any reason and see Locked instead of Relocked they shouldnt give you any trouble I would think. I believe you can also reset it to S-On but again I've never tried and I'm not sure its entirely safe. You'll have to look into that.
I'm done with these issues that my phone is having. It keeps locking up no matter what ROM I use or how little apps I have installed. Something has got to be wrong with my phone and it's time to bring it back to TMO for repair/replacement.
I found this link on HTC to download the RUU: http://www.htc.com/us/support/rom-downloads.html#tmobile
My question is, would this be enough to bring my phone back to stock so that they don't know I've rooted it?
Edit: Also, I just remembered about my bootloader being s-off/unlocked. Would this make a difference or would the RUU set everything back like it should?
Edit again: I found this thread: http://forum.xda-developers.com/showthread.php?t=2735235
So, would I be able to follow his instructions but change the CID to t-mob010 instead of the ones he has listed?
Nobody? I could really use some input on this, I don't want to brick my phone. I have to do this today, I can't take the lockups anymore.
There is a thread dedicated to returning your device to stock. It's intended for European users, but the instructions apply equally well to US users.
The first step is running the RUU, then locking (not relocking) the bootloader using adb commands. Reference http://forum.xda-developers.com/showthread.php?t=2708571 (for instructions on locking your bootloader)
Note that you can run the RUU without locking your bootloader if you are S-off. Once you are back to bone stock (recovery + OS), you can then go back S-on if you are concerned about the warranty, though I strongly advise AGAINST this in general.
Also, you may find that simply re-running the RUU will clear up your issue. I'd run it for a few days after restoring the phone before assuming a hardware fault.
jshamlet said:
There is a thread dedicated to returning your device to stock. It's intended for European users, but the instructions apply equally well to US users.
The first step is running the RUU, then locking (not relocking) the bootloader using adb commands. Reference http://forum.xda-developers.com/showthread.php?t=2708571 (for instructions on locking your bootloader)
Note that you can run the RUU without locking your bootloader if you are S-off. Once you are back to bone stock (recovery + OS), you can then go back S-on if you are concerned about the warranty, though I strongly advise AGAINST this in general.
Also, you may find that simply re-running the RUU will clear up your issue. I'd run it for a few days after restoring the phone before assuming a hardware fault.
Click to expand...
Click to collapse
Yes, I did find that post and am planning on following those instructions. However, you've confused me. According to that thread, they say to lock the bootloader first and then install the RUU; but you said the opposite. Which is it?
http://forum.xda-developers.com/showthread.php?t=2735235
Also, why are you against turning back S-on? I had planned on it because I don't want to take the chance of TMO or HTC having a problem.
ned4spd8874 said:
Yes, I did find that post and am planning on following those instructions. However, you've confused me. According to that thread, they say to lock the bootloader first and then install the RUU; but you said the opposite. Which is it?
http://forum.xda-developers.com/showthread.php?t=2735235
Also, why are you against turning back S-on? I had planned on it because I don't want to take the chance of TMO or HTC having a problem.
Click to expand...
Click to collapse
You are S-off, which means you do NOT have to lock the bootloader first. Most instructions for running an RUU assume you are S-on, however, which does require your bootloader to be locked. It's one of the checks that is disabled by S-off.
Also, S-off is getting harder to obtain, so unless there is a pressing reason to go S-on, it's safer to remain S-off. Warranty support could be that pressing reason.
Time to turn back S-on. Even after the RUU, it's still very buggy. Locking up, slow, lag, etc. Time to bring it back to TMO.
Anyone know what that will work? I do have the warranty service on it. So will they just replace my phone with a refurb M8, will it be sent out, what can I expect?
ned4spd8874 said:
Time to turn back S-on. Even after the RUU, it's still very buggy. Locking up, slow, lag, etc. Time to bring it back to TMO.
Anyone know what that will work? I do have the warranty service on it. So will they just replace my phone with a refurb M8, will it be sent out, what can I expect?
Click to expand...
Click to collapse
If you think your phone has bad hardware, then yeah, at this point you need to go ahead and S-on with the assumption that you will get a refurb - especially now that the M9 has been out a while. Who knows what you will get, though. You might even luck out and get a "new old stock" device with 4.4.2. Or, the refurb place could RUU it up to the latest. It's purely the luck of the draw.
Well this sucks. Can't get adb to recognize my phone in recovery. I can when it's booted into the system, but not recovery or the bootloader....
What a pain this is becoming!!!!!!!!!!!! I'm even trying to get into shell when the phone is booted up and sure I can do that, but I can't su! The binary isn't installed. So, what now I have to f'ing install a different ROM, s-on it and then ruu again????
So I f'ed up and turned S-ON by mistake before I did the commands to clear the bootloader modified messages. And now I can't get S-OFF for the life of me! Sunshine can't get root it says, SuperSU is installed and says a binary needs updating, but when I click on it, it just freezes and won't update the binary. I tried pushing it down via zip/bootloader but that doesn't help. I ran a root checker and it says my phone is rooted, but nothing is working like I expect it to.
I'm still running the stock ROM from the RUU, could that be the issue? Do I have to install a different ROM before I can S-OFF and then RUU again? This is such a pain!!!
ned4spd8874 said:
So I f'ed up and turned S-ON by mistake before I did the commands to clear the bootloader modified messages. And now I can't get S-OFF for the life of me! Sunshine can't get root it says, SuperSU is installed and says a binary needs updating, but when I click on it, it just freezes and won't update the binary. I tried pushing it down via zip/bootloader but that doesn't help. I ran a root checker and it says my phone is rooted, but nothing is working like I expect it to.
I'm still running the stock ROM from the RUU, could that be the issue? Do I have to install a different ROM before I can S-OFF and then RUU again? This is such a pain!!!
Click to expand...
Click to collapse
If you are still bootloader unlocked, install TWRP, restore an appropriate nandroid backup for your device, root that install, and re-run Sunshine.
If you are bootloader locked, restart the phone into bootloader mode and select the RUU option. Then, re-run the RUU. If your bootloader is locked, it should run and restore everything to stock. Note that if you updated to Lollipop, you may have to use Kingroot to get temp root. I meant to suggest you RUU down to the original version (4.4.2) prior to going S-on and forgot - sorry about that.
jshamlet said:
If you are still bootloader unlocked, install TWRP, restore an appropriate nandroid backup for your device, root that install, and re-run Sunshine.
If you are bootloader locked, restart the phone into bootloader mode and select the RUU option. Then, re-run the RUU. If your bootloader is locked, it should run and restore everything to stock. Note that if you updated to Lollipop, you may have to use Kingroot to get temp root. I meant to suggest you RUU down to the original version (4.4.2) prior to going S-on and forgot - sorry about that.
Click to expand...
Click to collapse
Bootloader is still unlocked, but even after installing a couple different ROMs, sunshine just won't work. Says it's incompatible. It says to flash a stock sense or near stock rom. I'm on SkyDragon right now...
I'm at a loss. Anyone have a industrial shredder?
ned4spd8874 said:
Bootloader is still unlocked, but even after installing a couple different ROMs, sunshine just won't work. Says it's incompatible. It says to flash a stock sense or near stock rom. I'm on SkyDragon right now...
I'm at a loss. Anyone have a industrial shredder?
Click to expand...
Click to collapse
There are probably some T-mobile nandroid backups around here somewhere. Get one, put it on an SD card, and use TWRP to flash it. Unfortunately, I only have DevEd and AT&T images.
jshamlet said:
There are probably some T-mobile nandroid backups around here somewhere. Get one, put it on an SD card, and use TWRP to flash it. Unfortunately, I only have DevEd and AT&T images.
Click to expand...
Click to collapse
Things are looking up! Found a ROM called something like Alex V that was stock enough to get SunShine to work. Also, I was using the original version so once I got it to run, it was giving network errors. Once I installed the latest version, that's when I got was able to go S-OFF. So, now I'm S-OFF, the bootloader is saying Official and locked so now I'm going to RUU and throw it in TMO's face!
I would like to root my M8, it has the latest OTA update from HTC which is Android 6.0. I have the developer edition, from what I've heard, the bootloader is already unlocked right?
I've seen some guides but most of them are outdated or they are meant to be used with Android 4.4.4.
I must say I'm not an expert when talking about phones, so is there a step by step guide to root an M8 with marshmallow? I would really appreciate any help.
The bootloader screen will indicate the bootloader status (LOCKED, UNLOCKED or RELOCKED) near the top of the screen.
In general, the process is:
1) Unlock the bootloader by HTCDev.com (if its not already unlocked).
2) Fastboot flash TWRP 3.0 custom recovery: https://twrp.me/devices/htconem8gsm.html
3) Backup your stock ROM in TWRP - lots of folks have been running into bootloop or no boot after trying to root (but probably usually when trying to use an obsolete version TWRP and/or SuperSU - but it never hurts to be safe and have a backup).
4) In TWRP, flash SuperSU v2.76 to root: https://download.chainfire.eu/969/SuperSU/UPDATE-SuperSU-v2.76-20160630161323.zip
redpoint73 said:
The bootloader screen will indicate the bootloader status (LOCKED, UNLOCKED or RELOCKED) near the top of the screen.
In general, the process is:
1) Unlock the bootloader by HTCDev.com (if its not already unlocked).
2) Fastboot flash TWRP 3.0 custom recovery: https://twrp.me/devices/htconem8gsm.html
3) Backup your stock ROM in TWRP - lots of folks have been running into bootloop or no boot after trying to root (but probably usually when trying to use an obsolete version TWRP and/or SuperSU - but it never hurts to be safe and have a backup).
4) In TWRP, flash SuperSU v2.76 to root: https://download.chainfire.eu/969/SuperSU/UPDATE-SuperSU-v2.76-20160630161323.zip
Click to expand...
Click to collapse
Thanks for the answer. Just one more question. My bootloader is already unlocked, but it says "S-ON" under "UNLOCKED", will that be a problem?
Sporting123 said:
Thanks for the answer. Just one more question. My bootloader is already unlocked, but it says "S-ON" under "UNLOCKED", will that be a problem?
Click to expand...
Click to collapse
Nope, that is just fine. S-on is perfectly okay for most mods, such as root, and flashing ROMs.
You only need s-off to do some very specific things, such as flashing modified hboots, manually flashing radio, changing CID&MID, downgrading by RUU, etc.
I have a simple doubt regarding flashing twrp. Does this means I can flash twrp through adb without getting root access to get root access.I usually root my devices using kingroot,works perfect for my old phone micromax.It also works for my htc one m8 when it was kitkat.But after I update to marshmallow Kingroot doesn't work for it,tried many times.If you could answer my question I would be very thankfull
hriatahriatpuia said:
I have a simple doubt regarding flashing twrp. Does this means I can flash twrp through adb without getting root access to get root access.
Click to expand...
Click to collapse
You don't need root to install TWRP, if that is what you mean. You just need an unlocked bootloader.
Thanks a lot,have already unlocked the bootloader.
redpoint73 said:
You don't need root to install TWRP, if that is what you mean. You just need an unlocked bootloader.
Click to expand...
Click to collapse
I've unlocked the bootloader but apparently I need to know which ver of twrp to use for my carrier ....no idea what to do there so I can't just flash the latest SuperSU from here? and how do I back up my stuff in case I mess up? Please help me i'm lost here
Hmz27 said:
I've unlocked the bootloader but apparently I need to know which ver of twrp to use for my carrier ....no idea what to do there so I can't just flash the latest SuperSU from here? and how do I back up my stuff in case I mess up? Please help me i'm lost here
Click to expand...
Click to collapse
what carrier ? if you are on gsm just flash TWRP 3.0.2-0 from official website
https://twrp.me/devices/htconem8gsm.html
after you flash TWRP recovery you will find option to backup it's too easy to understand how it works ( just check the partitions you want to backup and confirm your choices by sweep to proceed the process )
after you make a backup flash the latest supersu.zip from here ( choose TWRP installable.zip )
https://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
Hmz27 said:
I've unlocked the bootloader but apparently I need to know which ver of twrp to use for my carrier ...
Click to expand...
Click to collapse
I think you're looking at some really outdated info or guide. TWRP hasn't been carrier specific for about 2 years; with Verizon and Sprint being the only ones you had to look out for. But TWRP was unified long ago (so Sprint/Verizon no longer requires a different TWRP version). You'll see from ahmed's link, that it specifies "All variants" of the M8. The exception would be if you have an M8s; and maybe another oddball variant or two (which are really different hardware). But as long as its a true "M8" the TWRP version linked by ahmed will work.
If you have any doubts or concerns about the M8 version, connect the phone to your computer, reboot to fastboot mode and do command fastboot getvar all and post the results so we can take a look (delete IMEI and serial number before posting).
Hmz27 said:
no idea what to do there so I can't just flash the latest SuperSU from here?
Click to expand...
Click to collapse
No, you can't flash SuperSU without first flashing TWRP. Why would threads/guides tell you to do something that isn't necessary, if you can just skip it?
Simply put, you can only flash official "signed" files from the stock recovery. You need a custom recovery like TWRP to flash SuperSU.
Hmz27 said:
and how do I back up my stuff in case I mess up?
Click to expand...
Click to collapse
Once you install TWRP, you can use it to create a backup of your stock unrooted ROM and user data. And its highly recommended to do so, before you flash SuperSU. Not only will this give you an easy way to revert/recover if something goes wrong with the root attempt; but you will also have a backup of your stock, unrooted ROM if you ever want it.
There are other ways to backup your data, but that depends on what "stuff" you are talking about (as that vague description doesn't tell us what you actually want to backup). For instance, for files, photos, etc. you can just copy and paste them to your computer as a backup.
Hello , I'm new to the whole thing guy and I want to unlock my bootloader in order to install custom rom , I looked in the fourm and I'v found an old method with all in one tool kit but I don't think it will work on my android version 6.0 would someone kindly guide me and tell me what do I need to do ? thanks .
Monzer_ said:
Hello , I'm new to the whole thing guy and I want to unlock my bootloader in order to install custom rom , I looked in the fourm and I'v found an old method with all in one tool kit but I don't think it will work on my android version 6.0 would someone kindly guide me and tell me what do I need to do ? thanks .
Click to expand...
Click to collapse
If the method is firewater, it no longer works.
fireguy85 said:
If the method is firewater, it no longer works.
Click to expand...
Click to collapse
I'm not sure what are you talking about since I'm new to the whole thing I believe that firewater has something to do with S-off which is something I couldn't do because all the guides says download firewater and the links takes me to sunshine which i believe cost me money to do ? sorry correct me if I'm wrong but I'm just a newbie beside I don't need s-off right ? what does that have to do with my problem ?
Monzer_ said:
I'm not sure what are you talking about since I'm new to the whole thing I believe that firewater has something to do with S-off which is something I couldn't do because all the guides says download firewater and the links takes me to sunshine which i believe cost me money to do ? sorry correct me if I'm wrong but I'm just a newbie beside I don't need s-off right ? what does that have to do with my problem ?
Click to expand...
Click to collapse
Firewater was an all-in-one kit used to unlock bootloader and achieve s-off. The guys that created this went on to create Sunshine, leaving firewater project behind, so any guides from 2014 are likely obsolete. Unlocking the bootloader is as simple as going to htcdev.com, making an account and following the instructions there-it's super easy. S-off isn't necessary for most.
fireguy85 said:
If the method is firewater, it no longer works.
Click to expand...
Click to collapse
fireguy85 said:
Firewater was an all-in-one kit used to unlock bootloader and achieve s-off. The guys that created this went on to create Sunshine, leaving firewater project behind, so any guides from 2014 are likely obsolete. Unlocking the bootloader is as simple as going to htcdev.com, making an account and following the instructions there-it's super easy. S-off isn't necessary for most.
Click to expand...
Click to collapse
yes that what I have done exactly I'v unlocked the bootloader this way then used the all in one kit to root but then couldn't s-off as the guide I was following said download firewater and the links take me to sunshine . I don't know much further have not tried sunshine yet and now my rom seems ok after I re-flashed it awesome rom btw still little curious about s-rom but this one will do just fine I'v been using stock for ages .
Monzer_ said:
yes that what I have done exactly I'v unlocked the bootloader this way then used the all in one kit to root but then couldn't s-off as the guide I was following said download firewater and the links take me to sunshine . I don't know much further have not tried sunshine yet and now my rom seems ok after I re-flashed it awesome rom btw still little curious about s-rom but this one will do just fine I'v been using stock for ages .
Click to expand...
Click to collapse
Firewater and the AIO (all-in-one) toolkit are 2 different things. Firewater is an (obsolete) s-off method. May have also contained a temp root, and some other things (can't remember exactly, it's been 2 years - and doesn't matter anyway - see more below). But firewater is not typically referred to as a "toolkit" or "all-in-one" (never seen it referred to that way, actually).
All-in-one toolkit (there are a couple) is a PC for unlocking the bootloader, root, and several other things (may have had a link for firewater, don't remember - again it's irrelevant for reasons below).
The toolkits are not recommended. They haven't been updated in a long time, and therefore use very obsolete files for TWRP and SuperSU (when applicable). You will have issues flashing many ROMs with old TWRP (and I'm surprised you haven't yet). Plus, you will probably find in bootloader and fastboot getvar, that the OS number is now blank (known bug in old versions of TWRP). I would suggest flashing the current version TWRP 3.1.1 using fastboot, to prevent issues moving forward. Current TWRP is fully compatible with current ROMs - but will not fix the bug of OS number being blank (need to flash firmware or RUU to fix that - but it's just a minor thing).
Firewater doesn't work, no matter what you do. It required an online server component, which the devs took offline over 2 years ago. Sunshine ($25 US) is the only current s-off method. But be aware, that most folks don't need s-off. S-off isn't needed to root, flash custom ROMs, and most other mods. s-off is only needed for very specific things, such as manually flashing radios, changing CID/MID, and some other things.
redpoint73 thank you so much for such a help truly gentleman much appreciate it .
It appears you can no longer use the usual method to unlock the bootloader. I just got this phone the other day in fantastic condition as a gift.
HTCDev told me there was an error or try again later. I'll upload screenshots later.
Not true... I used www.htcdev.com to unlock the bootloader of my HTC One M8 today.
I have this phone, with Android 6.0 and bootloader locked. However it has become practically unusable as it regularly powers off by itself, most likely due to lack of storage (there's only 0.6 GB left...). I've already uninstalled all of my few (useful) apps, I have no media on it whatsoever, but it is just filled up with bloatware that is pre-installed and gets re-installed automatically and that I thus cannot get rid of. I don't want to buy a new phone (it's in good condition) but from reading on the internet I understand that the only option is to unlock and root it, and put an oem on it exempt of all of these useless apps.
So my questions are, is this really the only option and if so is it still possible on this old machine to unlock the bootloader, and to get the right - clean - software for it somewhere?
I registered at HtC dev. There's a page that walks you through the unlocking process. So I should be able to do that part, if what FlexMcMurphy said in July last year still is true... For the rest, I'm quite new to this process but there are pages here on XDA that describe rooting and flashing. I'm ready to give it a try, but could use help if stuck.
Any reply/help would be wonderful !
Thank you in advance.
Judith
Hey everyone, so I am pretty sure I bricked my HTC10.
To Start off my specs are the HTC 10 Unlocked version
htc_pmewl
CID: BS_US001/BS_US002
MID: 2PS650000
OS: 1.80.617.1
OpenDSP: 18.2.8996.00524_0321
(orignially Stock ROM)
I was trying to reset everything to stock settings before I returned the phone (Unrooting, Locked Bootloader, Stock Recovery, etc) and everything was going fine until after I rewrote the S-OFF flag to S-ON (I'm pretty sure it happened there, maybe when I relocked the bootloader?). Now I don't have a ROM, the CID and MID's are missing on the fastboot (download-mode) page. The Bootloader is relocked, and I have a stock recovery.
I tried going here to get the RUU's and everything to fix what I had done. However the RUU.exe gives me a error 120 Low Battery when I run it (Even though I have a fully charged battery). I tried going to a different PC to run the RUU, but the RUU never runs past the initial install.
I also tried re-unlock the bootloader so I could reinstall TWRP and flash that way. Unlocking went fine, but when I try to flash the twrp img via fastboot I get an error (9 RU_SECURITY_FAIL recovery and bootloader isn't BL_UNLOCKED).
I'm really at my wits end here. I haven't actually done anything this stupid in all of my customizing my M8, S6, Razr or all my tablets so I honestly don't know what to do. If you guys could throw me a lifeline I'd be grateful.
Thanks
Have you tried doing a factory reset using the stock recovery?
See if you can get a system.img to flash manually. If you can get an OS boot you should be able to fix your device.
tkoreaper said:
Have you tried doing a factory reset using the stock recovery?
Click to expand...
Click to collapse
Using the adb shell command (recovery --wipe_data)? Yeah I've tried that, but I get a device not found error. adb isn't working right now, however I am still able to get fastboot commands, and the phone recognizing them at least. Otherwise, no I haven't what would I need to do?
@tw1tch175 is right. Try to find an untouched system image first and try to flash it in download mode.
Could you in addition tell a bit more about what you did to reset the device to stock instead of flashing a RUU in the first place prior to writing secureflag 3!? And further more what did you do prior to it, did you flash unsigned firmware, or one of the "no red text on boot" aboot provided here!?
Sent from my HTC 10 using XDA Labs
Are you making sure you are in download mode for fastboot commands. Also double check your driver in the device manager.
Edit: woops re-read, and he meant use the UI in the factory recovery to reset
5m4r7ph0n36uru said:
@tw1tch175 is right. Try to find an untouched system image first and try to flash it in download mode.
Could you in addition tell a bit more about what you did to reset the device to stock instead of flashing a RUU in the first place prior to writing secureflag 3!? And further more what did you do prior to it, did you flash unsigned firmware, or one of the "no red text on boot" aboot provided here!?
Sent from my HTC 10 using XDA Labs
Click to expand...
Click to collapse
Sure. I originally ran the factory wipe/reset via the ROM (Which was the stock rom). Then after that I booted up into the download mode, tried relocking the bootloader with fastboot oem lock. I also flashed the stock recovery for my model. Once I saw that I had the stock recovery on, the bootloader was locked, and everything else, I tried to do a twrp restore and relock it, but it wasn't working so I said "Screw it" and rewrote the secureflag, rebooted and...yeah everything was gone.
The only thing I did before all of this was when I got the phone unlock the bootloader, SOFF, Custom Recovery, and sideload super SU for root. The only "unofficial" radios/firmware/etc I had was the Verizon Radio on my phone.
Other than that I kept it clean. I'm looking for an image now to try that.
tw1tch175 said:
Are you making sure you are in download mode for fastboot commands. Also double check your driver in the device manager.
Edit: woops re-read, and he meant use the UI in the factory recovery to reset
Click to expand...
Click to collapse
Yes. I just figured that out while searching haha. I did go through and use the UI, but I had no luck. I am looking for an img like you said but I am not having luck so far. Is there one of the Stock guide on my original post?
Ok so for ALL HTC the only proper way to s-on is to use fastboot/download and for oem writesecureflag 3, you should NEVER EVER EVER us echo/dd /hexeditor to go s-on.
For 2016+ phones, you should use sunshine or another tool to go from unlock/relocked to lock, do NOT use anything not designed for the phone in question, or attempt to do it manually. I can only vouch for SunShine's capability to safely change the bootloader status, I can't vouch for any other method or tool. I know SunShine does it right.
See http://forum.xda-developers.com/htc-10/how-to/psa-htc-10-s-off-s-lock-unlock-t3371264 for my PSA on the subject.
If the phone won't flash with a proper RUU, well you need to find someone with a EMMC write tool to rewrite all your firmware, this is probably going to run $100-200.
bob3rt said:
Hey everyone, so I am pretty sure I bricked my HTC10.
To Start off my specs are the HTC 10 Unlocked version
htc_pmewl
CID: BS_US001/BS_US002
MID: 2PS650000
OS: 1.80.617.1
OpenDSP: 18.2.8996.00524_0321
(orignially Stock ROM)
I was trying to reset everything to stock settings before I returned the phone (Unrooting, Locked Bootloader, Stock Recovery, etc) and everything was going fine until after I rewrote the S-OFF flag to S-ON (I'm pretty sure it happened there, maybe when I relocked the bootloader?). Now I don't have a ROM, the CID and MID's are missing on the fastboot (download-mode) page. The Bootloader is relocked, and I have a stock recovery.
I tried going here to get the RUU's and everything to fix what I had done. However the RUU.exe gives me a error 120 Low Battery when I run it (Even though I have a fully charged battery). I tried going to a different PC to run the RUU, but the RUU never runs past the initial install.
I also tried re-unlock the bootloader so I could reinstall TWRP and flash that way. Unlocking went fine, but when I try to flash the twrp img via fastboot I get an error (9 RU_SECURITY_FAIL recovery and bootloader isn't BL_UNLOCKED).
I'm really at my wits end here. I haven't actually done anything this stupid in all of my customizing my M8, S6, Razr or all my tablets so I honestly don't know what to do. If you guys could throw me a lifeline I'd be grateful.
Thanks
Click to expand...
Click to collapse
bob3rt said:
Sure. I originally ran the factory wipe/reset via the ROM (Which was the stock rom). Then after that I booted up into the download mode, tried relocking the bootloader with fastboot oem lock. I also flashed the stock recovery for my model. Once I saw that I had the stock recovery on, the bootloader was locked, and everything else, I tried to do a twrp restore and relock it, but it wasn't working so I said "Screw it" and rewrote the secureflag, rebooted and...yeah everything was gone.
The only thing I did before all of this was when I got the phone unlock the bootloader, SOFF, Custom Recovery, and sideload super SU for root. The only "unofficial" radios/firmware/etc I had was the Verizon Radio on my phone.
Other than that I kept it clean. I'm looking for an image now to try that.
Click to expand...
Click to collapse
So as I thought. You indeed flashed - at least parts - of an unofficial firmware. Prior to relocking the bootloader with SunShine, as well as setting S-ON you should've taken care that ALL its stock. A simple factory reset in the ROM settings wasn't enough.
I'd guess that the wrong radio led to a problem when booting with stock recovery of your ROM, relocked bootloader and secureflag set to S-ON.
If I saw it correctly all RUUs for your device are *.exe files. Best would be to extract the ROM.zip from this exe, using 7zip, rename it to 2PS6IMG.zip, place it on an external SDCard (formatted extFAT or FAT32) and reboot to download mode, to give it a shot.
Hope this will help.
Edit: ... nvm... @jcase ninja'd me. Wanted to post the exact same link.
Sent from my HTC 10 using XDA Labs
5m4r7ph0n36uru said:
So as I thought. You indeed flashed - at least parts - of an unofficial firmware. Prior to relocking the bootloader with SunShine, as well as setting S-ON you should've taken care that ALL its stock. A simple factory reset in the ROM settings wasn't enough.
I'd guess that the wrong radio led to a problem when booting with stock recovery of your ROM, relocked bootloader and secureflag set to S-ON.
If I saw it correctly all RUUs for your device are *.exe files. Best would be to extract the ROM.zip from this exe, using 7zip, rename it to 2PS6IMG.zip, place it on an external SDCard (formatted extFAT or FAT32) and reboot to download mode, to give it a shot.
Hope this will help.
Edit: ... nvm... @jcase ninja'd me. Wanted to post the exact same link.
Sent from my HTC 10 using XDA Labs
Click to expand...
Click to collapse
Ah gotcha. That makes sense. Wouldn't have been the only thing that slipped my mind. I lost access to my Steam authenticator too. I was able to get the zip from the exe file like you said, after I put that on an SD card and boot to download mode do I just fastboot flash zip?
If there's one thing I remember when using Sunshine to go S-OFF on two different HTC 10's it was that it mentioned something about going S-ON and how something wasn't guaranteed, I forget what exactly, but if I remember correctly I understood it as you shouldn't go back to S-ON because it wasn't guaranteed to work or something like that. Anyone know what I'm talking about?
tkoreaper said:
If there's one thing I remember when using Sunshine to go S-OFF on two different HTC 10's it was that it mentioned something about going S-ON and how something wasn't guaranteed, I forget what exactly, but if I remember correctly I understood it as you shouldn't go back to S-ON because it wasn't guaranteed to work or something like that. Anyone know what I'm talking about?
Click to expand...
Click to collapse
That is in regards to wiping data, earlier versions of sunshien wiped data on all htc 10 going s-off, thats not the issue here. Issue here is he improperly set the phone lock/s-on. Gotta use sunshine to set it locked, and fastboot to set s-on.
Hey Everyone just wanted to give an update since yesterday evening.
Just wanted to give out some props to @5m4r7ph0n36uru . Following his advice of extracting the Rom.zip from RUU .exe I was able to run it in download mode and loaded up an OS on the phone. So Now I am unbricked! Yay. I had to find out how to do that using process monitor and everything, but it was a success. and I can breathe easy. Thankfully doing that was easier that doing the Database call handler stuff from today at work XD
Thankfully my lesson is learned and I'll flash correctly to full stock next time. Thank you all for your help in the matter.
bob3rt said:
Hey everyone, so I am pretty sure I bricked my HTC10.
To Start off my specs are the HTC 10 Unlocked version
htc_pmewl
CID: BS_US001/BS_US002
MID: 2PS650000
OS: 1.80.617.1
OpenDSP: 18.2.8996.00524_0321
(orignially Stock ROM)
I was trying to reset everything to stock settings before I returned the phone (Unrooting, Locked Bootloader, Stock Recovery, etc) and everything was going fine until after I rewrote the S-OFF flag to S-ON (I'm pretty sure it happened there, maybe when I relocked the bootloader?). Now I don't have a ROM, the CID and MID's are missing on the fastboot (download-mode) page. The Bootloader is relocked, and I have a stock recovery.
I tried going here to get the RUU's and everything to fix what I had done. However the RUU.exe gives me a error 120 Low Battery when I run it (Even though I have a fully charged battery). I tried going to a different PC to run the RUU, but the RUU never runs past the initial install.
I also tried re-unlock the bootloader so I could reinstall TWRP and flash that way. Unlocking went fine, but when I try to flash the twrp img via fastboot I get an error (9 RU_SECURITY_FAIL recovery and bootloader isn't BL_UNLOCKED).
I'm really at my wits end here. I haven't actually done anything this stupid in all of my customizing my M8, S6, Razr or all my tablets so I honestly don't know what to do. If you guys could throw me a lifeline I'd be grateful.
Thanks
Click to expand...
Click to collapse
Hello,
Just to inform that if I try to run RUU.exe from PC when the phone is in bootloader menu, I get battery low error. However, if I "boot to download mode" in the bootloader menu, I can run the RUU.exe from the computer without any error.