some help pls?
That depends on what you are trying to do. You can use fastboot commands in bootloader-fastboot mode; which will still work even if OS and recovery are not accessible. But anything more (such as adb, storage access) you will need at least recovery.
What is the current condition of the phone, what were you trying to do, or want to do, etc.?
redpoint73 said:
That depends on what you are trying to do. You can use fastboot commands in bootloader-fastboot mode; which will still work even if OS and recovery are not accessible. But anything more (such as adb, storage access) you will need at least recovery.
What is the current condition of the phone, what were you trying to do, or want to do, etc.?
Click to expand...
Click to collapse
Thanks for willingness to help,i was already solving the problem.I went to a specialized server,and they repair it.
morrientes99 said:
Thanks for willingness to help,i was already solving the problem.I went to a specialized server,and they repair it.
Click to expand...
Click to collapse
That's too bad. You probably spent money to fix something we could have helped you with, for free.
redpoint73 said:
That's too bad. You probably spent money to fix something we could have helped you with, for free.
Click to expand...
Click to collapse
was not so bad..i was also replacing the battery and usb connector,so now looks like new..unfortunately they didnt install Android 7.0,but im afraid to try to do it
morrientes99 said:
unfortunately they didnt install Android 7.0,but im afraid to try to do it
Click to expand...
Click to collapse
Sounds like you haven't modded the phone before? No need to be afraid in my opinion. You won't brick (or otherwise damage) the device by unlocking the bootloader, installing custom recovery, and flashing a custom ROM. And the process is almost entirely reversible, with the slight exception of the fact that the bootloader will only ever say UNLOCKED or RELOCKED; versus LOCKED (stock condition). But this is almost entirely irrelevant, as RELOCKED is functionally the same as LOCKED, aside from the possibility that RELOCKED voids the warranty (indicates the phone was bootloader unlocked) but the huge majority of M8 devices don't have warranty at this point, as the phone is going on 3 years old.
Just be sure to properly read and understand the process before you start, don't use outdated methods, backup any personal data before bootloader unlock, and be sure to make a backup of your current stock ROM before flashing the new ROM. Also understand how to recover from problems, such as restoring a TWRP backup, etc.
Do the necessary due diligence before you start, and modding the phone will go just fine.
Related
Hey guys,
I'm kinda new to the HTC/Android world, found this community a damn good place to find support.. But now I've hit a road block.
Basically, I've been eager to root from day 1 of getting my first htc handset, I came across from jailbreak and loved the fact of customizability with Android.
So I had the Google play edition(I think, all geared towards Google) running Kit Kat 4.4.4. Love it, big Google user so this all tied together lovely.
Here is the Situation.
I found a video on youtube, cannot provide URL as I'm in work at the moment, but it was root guide from scratch. Fresh windows OS, seemingly a phone fresh out the box.. you get the idea.
I used the Hasoon2000 tool to root the device. Installed ADB etc on my pc, signed up as a a dev, got the Key for device, sent in and received my .bin file. I got up to actually rooting my device, well pleased and happy. Using TWRP via Hasoon2000.
But here is where **** hits the fan.
The device needed to update, It took me back to 4.4.2 but Im unsure on how to get back to most up to date OS and keep the root.
But when I reboot to install this, it goes into TWRP. no other way around this.
Queried this on another forum, decided to continue to be patient... but no replies, in the mean time I restored my apps and have a fiddle, see what the root function can do for myself.
I installed "Freedom 1.0.6" and a program called "Market Share"- Hate iAP, some games are ridiculously priced for the smallest of things, I just wanted to sandbox plague inc. ;(
Now the device is stuck in a boot loop, phone starts up, see the home screen for a bout 40 seconds/ one minute.. Some times I unlock the device and it goes back to flash screen then.. others I boot an app and its slides away once more.
This happened close to 15x before I left for work this morning and I imagine its just going to repeat this and run the battery - I tried to stop this loop by going into TWRP and possibly choosing to boot system this way may of stopped it.. but when I was on the boot screen with those options.. It said Tampered at top of screen and S-On- which has scared me quite a bit..
What the hell has happened!?
I'm desperate to know and don't want to have this damn thing bricked! Please help.. try explain like I'm 5, as said I'm new to a lot of this! >.<
first off, if the screen comes on, its not bricked.
esenfur said:
But here is where **** hits the fan.
The device needed to update, It took me back to 4.4.2 but Im unsure on how to get back to most up to date OS and keep the root.
But when I reboot to install this, it goes into TWRP. no other way around this.
Click to expand...
Click to collapse
Do you mean you accepted an official OTA? I think that is what you are saying. You should not be accepting OTAs on a phone that has been bootloader unlocked, custom recovery, etc. unless you know exactly what you are doing and what the result will be (which is clearly not the case).
Stock recovery is needed to install an OTA. That is why it keeps going to TWRP, then it doesn't find stock recovery and reboots, hence the loop you are stuck in. Try to find the OTA file and delete it.
redpoint73 said:
first off, if the screen comes on, its not bricked.
Do you mean you accepted an official OTA? I think that is what you are saying. You should not be accepting OTAs on a phone that has been bootloader unlocked, custom recovery, etc. unless you know exactly what you are doing and what the result will be (which is clearly not the case).
Stock recovery is needed to install an OTA. That is why it keeps going to TWRP, then it doesn't find stock recovery and reboots, hence the loop you are stuck in. Try to find the OTA file and delete it.
Click to expand...
Click to collapse
Thank you for fast response.
Official OTA - being that the phone its self said "Update the OS" - I just accepted this, hit download and began install as a reboot- didnt spot implications. As said, noob, followed a tut. If it highlighted DO NOT UPDATE or.. IF U WANT UPDATE NOW FOLLOW THIS- Great, but nothing of the sort?
Is the OTA file basically the .exe for the OS- so find it and delete it.. although I dont have enough time to navigate and establish where the file actually is located!
Or do you have any links to tutorials I could possibly follow?
Side note- when this loop started I deleted
esenfur said:
Or do you have any links to tutorials I could possibly follow?
Click to expand...
Click to collapse
This is really your main issue. By following a YouTube video and using a Toolkit, you've failed to actually learn anything or gain any real understanding or knowledge. Do yourself a favor and ditch the tutorials and videos (and toolkit for that matter) and do it the old fashioned way . . . by reading. Videos and step-by-step guides do you no good when things go south (as you've now discovered). And with the prior proper knowledge (usually not gained by following tutorials) this whole mess probably would have never happened in the first place.
A cardinal rule of Android phone modding: DO NOT accept/download/install OTAs (official OS updates) on a modded device unless you know what you are doing, and what the result will be. If in any doubt, simply DO NOT do it.
esenfur said:
Is the OTA file basically the .exe for the OS- so find it and delete it.. although I dont have enough time to navigate and establish where the file actually is located!
Click to expand...
Click to collapse
.exe file is Windows specific. You are looking for a zip file, and it typically starts with "OTA". Don't remember where its saved to, so you will have to search for it. If you can't keep the phone running long enough to do so, mount the memory on your computer and search that way.
Deleting the OTA file worked for me on a past device, although one M8 user in the same position said deleting the file didn't get him out of the loop. Flashing your ROM again, or wiping the internal memory (backup any important personal data first) might be options for you.
redpoint73 said:
you've failed to actually learn anything or gain any real understanding or knowledge.
Click to expand...
Click to collapse
Ive seen quite a fair few ratings for Hasoon2000 and decided to go with it..
redpoint73 said:
Videos and step-by-step guides do you no good when things go south (as you've now discovered).
Click to expand...
Click to collapse
agreed.. theres FAR much more I need to learn.. its scary haha.
redpoint73 said:
DO NOT accept/download/install OTAs (official OS updates)
Click to expand...
Click to collapse
taken on board. I know with my jailbreaks in past it has been a pain, assumed Android would be alot more stable to over write- due to functionality of OS and unlocked features.
I was being generic when I said .exe- basically the installer..
I returned from work to see phone stopped looping.. i could stop the install and deleted the file ASAP.. but now what.. Phone is still bugging me to update, lost the root(got a checker).. so whats the correct procedure!?
I am confused to what you are trying to accomplish at this point, is it to install a OTA, or a recovery? What exactly is going down here?
Me personally to take an OTA is to relock bootloader, install stock recovery, and make sure CID matches. I am S-Off so bootloader means very little, but you can unlock and relock at will when you are S-Off. You will not lose S-Off accepting an OTA.
Try to re-flash the ROM, with stok ROM, using TWRP and clean install. It should work.
hack14u said:
I am confused to what you are trying to accomplish at this point, is it to install a OTA, or a recovery? What exactly is going down here?
Me personally to take an OTA is to relock bootloader, install stock recovery, and make sure CID matches. I am S-Off so bootloader means very little, but you can unlock and relock at will when you are S-Off. You will not lose S-Off accepting an OTA.
Click to expand...
Click to collapse
I am trying to update the phone, root and then some..
What file am I looking for and how do I flash a ROM on a M8
esenfur said:
I am trying to update the phone, root and then some..
What file am I looking for and how do I flash a ROM on a M8
Click to expand...
Click to collapse
First of all once the bootloader is unlocked you don't have to relock it to get OTA.
As I undersand you have done the following:
1) Unlock using HTCDev-Method
2) flashed a custom revocery (TWRP in your case)
3) flashed a supersu too!?
To install the OTA means loosing root acces. Thus you have to re-root it after the OTA is done. The other problem ist that STOCK OTAs don't work with a custom recovery. Meaning you would have to flash a stock recovery first, install the OTA second (as long as you didn't change anything an just root), and re-root third.
Let's have a look which stock recovery you would need:
1) reboot to bootloader
2) connect the phone to you PC and open cmd in you adb/fastboot folder
3) enter "fastboot getvar all"
4) paste this information here (but DELETE the IMEI and SERIAL NUMBER before posting!!)
As soon as we know which stock recovery you need we will go on.
esenfur said:
Ive seen quite a fair few ratings for Hasoon2000 and decided to go with it..
Click to expand...
Click to collapse
I'm not saying there is anything "wrong" with the toolkit, per se. For the most part, it does what its intended to do.
But it also shortcuts the learning process, and facilitates folks rooting the phone without gaining the proper knowledge. This is a dangerous thing.
This is just my opinion. But I strongly believe it. If you can't accomplish these things without a toolkit, you shouldn't be rooting your phone in the first place.
Others use the toolkits, and love them. They are more than entitled to have their own opinion. But when things go south, the toolkits aren't going to help; and those folks don't have the proper knowledge and they come running here. So you tell me what is the "best" way to root the phone?
esenfur said:
I was being generic when I said .exe- basically the installer..
Click to expand...
Click to collapse
I already figured this was probably the case. But I found it better to provide the exact information on what file to delete; rather than leaving it open to the possibility of you and/or others being misinformed.
esenfur said:
Phone is still bugging me to update, lost the root(got a checker).. so whats the correct procedure!?
Click to expand...
Click to collapse
Sounds like you still have TWRP installed, so just flash SU or SuperSU to gain root.
After that, you can use Titanium Backup or similar app to find the update process and freeze it, to stop the update notifications.
Don't remember the exact process (this is where searching and reading comes in for you) but its something like "drm..." or "updater".
I have this situation before,what i do is find the right stock recovery and flash..after ota done flash back custom recovery..?
esenfur said:
I am trying to update the phone, root and then some..
What file am I looking for and how do I flash a ROM on a M8
Click to expand...
Click to collapse
At this point after seeing this, I would suggest you take some time and start reading. All of your answers are here in the forums. Knowledge is power and within the pages of this site you will find everything you need.
To take the OTA find a stock recovery, to flash ROM's find the one you like and flash via your favorite recovery.
Helo Guyz!!
I bought a new HTC One m8 a couple of days ago. I've made a call when I bought it, so the sim card was working earlier. I rooted it using "HTC M8 ALL IN ONE V2.0" yesterday so that I can restore the apps+app data via Titanium BackUp from my old Xperia Z. Just turned on my Rooted M8 and it doesn't recieve signals. It shows an icon with a simcard followed by an exclamation mark. Tried my brother's sim, no change!! Made a Factory reset(It didn't Unroot) still no change.
Please help me Guyz!!! Thanks.
I might have unlocked the bootloader while rooting as it was a necessary step in the TUT(All in one tool).
Kunnu2592 said:
Helo Guyz!!
I bought a new HTC One m8 a couple of days ago. I've made a call when I bought it, so the sim card was working earlier. I rooted it using "HTC M8 ALL IN ONE V2.0" yesterday so that I can restore the apps+app data via Titanium BackUp from my old Xperia Z. Just turned on my Rooted M8 and it doesn't recieve signals. It shows an icon with a simcard followed by an exclamation mark. Tried my brother's sim, no change!! Made a Factory reset(It didn't Unroot) still no change.
Please help me Guyz!!! Thanks.
I might have unlocked the bootloader while rooting as it was a necessary step in the TUT(All in one tool).
Click to expand...
Click to collapse
Unlocking the bootloader wouldn't affect your device in any means except factory resetting it.
Maybe the tool you used changed the radio? That's the only thing I can think of. Try flashing a different radio
Kunnu2592 said:
I might have unlocked the bootloader while rooting as it was a necessary step in the TUT(All in one tool).
Click to expand...
Click to collapse
You don't even know if you unlocked the bootloader? This is one of the big reasons why toolkits and step-by-step tutorials are a bad idea. You are modding your phone with absolutely no understanding of the primary concepts, or what you have even done with your phone. Although the no signal issue doesn't seem related to your lack of knowledge, I'd still recommend you slow down and do more learning and research before messing with the phone anymore, unless you want to risk permanent damage to the device.
Also, all a factory reset does is wipe user data, and doesn't affect the system in any way.
As mentioned in the previous response, simply unlocking the bootloader should not have resulted in no signal.
Are you presently s-on or s-off? You should list step by step what you've done to the phone. Still on the stock ROM, or otherwise? Did you try to restore any system data with Titanium? How precisely did you root the phone after unlocking the bootloader? What recovery and version?
redpoint73 said:
You don't even know if you unlocked the bootloader? This is one of the big reasons why toolkits and step-by-step tutorials are a bad idea. You are modding your phone with absolutely no understanding of the primary concepts, or what you have even done with your phone. Although the no signal issue doesn't seem related to your lack of knowledge, I'd still recommend you slow down and do more learning and research before messing with the phone anymore, unless you want to risk permanent damage to the device.
Also, all a factory reset does is wipe user data, and doesn't affect the system in any way.
As mentioned in the previous response, simply unlocking the bootloader should not have resulted in no signal.
Are you presently s-on or s-off? You should list step by step what you've done to the phone. Still on the stock ROM, or otherwise? Did you try to restore any system data with Titanium? How precisely did you root the phone after unlocking the bootloader? What recovery and version?
Click to expand...
Click to collapse
Sorry brother. I thought I was clear. Here is what I did to my phone. I followed this up. Get token, submit it, download a file which was sent via email and use it to unlock the bootloader. Root it at last using the perm root command in the tool itself.
http://forum.xda-developers.com/showthread.php?t=2699065
I haven't done anything to the phone after rooting it. No titanium restores.. Nothing. I would want to relock the bootloader want to relock the bootloader using the same tool. Is it safer? Does it makes it normal again? Do I get my warranty then? Does it wipes all the data if I lock bootloader after restoring my apps with titanium backup?
Please help guyz!!
Kunnu2592 said:
I would want to relock the bootloader want to relock the bootloader using the same tool. Is it safer? Does it makes it normal again? Does it wipes all the data if I lock bootloader after restoring my apps with titanium backup?
Click to expand...
Click to collapse
Nothing you did should have caused the no signal issue (simply unlocking the bootloader and rooting shouldn't have caused that). So its hard to say what would fix it.
You can try to re-install the stock ROM. Or try to relock the bootloader and see what happens.
Kunnu2592 said:
Does it wipes all the data if I lock bootloader after restoring my apps with titanium backup?
Click to expand...
Click to collapse
Not sure, but I believe relocking the bootloader will wipe data. So backup anything important before doing so.
redpoint73 said:
Nothing you did should have caused the no signal issue (simply unlocking the bootloader and rooting shouldn't have caused that). So its hard to say what would fix it.
You can try to re-install the stock ROM. Or try to relock the bootloader and see what happens.
Not sure, but I believe relocking the bootloader will wipe data. So backup anything important before doing so.
Click to expand...
Click to collapse
Okay bro... I would try that and be bck!!
ThanQ ?
brichardson1991 said:
Unlocking the bootloader wouldn't affect your device in any means except factory resetting it.
Maybe the tool you used changed the radio? That's the only thing I can think of. Try flashing a different radio
Click to expand...
Click to collapse
Idk what Radio is and how to change it. Is it some code that makes the signal receiver work? I just followed a guide and didn't miss any steps. Please enlighten me about it so that I could try something out. ThanQ brother.
Kunnu2592 said:
Idk what Radio is and how to change it. Is it some code that makes the signal receiver work? I just followed a guide and didn't miss any steps. Please enlighten me about it so that I could try something out.
Click to expand...
Click to collapse
You didn't answer my question whether you were S-off or S-on. But as you didn't mention it in the steps you performed, you are probably still s-on. That being the case its also likely the radio wasn't modified by anything you did (s-off is needed to write to the radio partition); and on the same note, you can't do anything to that partition now unless you s-off.
I'd go with my previous recommendations for now, and see how that goes before doing more.
Maybe a silly question, but toggling airplane more or rebooting the phone doesn't have any affect on the no signal condition?
Maybe it's not making proper contact in the tray? Tried to remove it and readjust it a bit and put it back? I recall someone mentioning a similar problem months ago and when I read up on it it seemed to be a problem with the Hox as well where they used to put some tape on the back of the sim and put it back in the tray. They did this to "thicken" it a bit so it can get pressed down properly on the circuitry?
Just throwing out my 2cents here...
BerndM14 said:
Maybe it's not making proper contact in the tray? Tried to remove it and readjust it a bit and put it back? I recall someone mentioning a similar problem months ago and when I read up on it it seemed to be a problem with the Hox as well where they used to put some tape on the back of the sim and put it back in the tray. They did this to "thicken" it a bit so it can get pressed down properly on the circuitry?
Just throwing out my 2cents here...
Click to expand...
Click to collapse
That's certainly worth exploring as well. It seems like too much a coincidence that this issue occurred right after unlocking the bootloader and rooting. But on the other hand, its odd as such modifications should not have caused the no signal issue.
redpoint73 said:
That's certainly worth exploring as well. It seems like too much a coincidence that this issue occurred right after unlocking the bootloader and rooting. But on the other hand, its odd as such modifications should not have caused the no signal issue.
Click to expand...
Click to collapse
Heh, to quote one of my favourite quotes from xxxHolic: There is no such thing as a coincidence in this world, there is only the inevitable.
Could be radio though as well. I went to do a search for this issue and found some of the old threads where they flashed radios, restored the nandroid backup etc.
But perhaps that's something that the OP can look into as well and learn some stuff.
htc one m8 sim card error site:forum.xda-developers.com In google returned many results.
[Q] Sim Card detection Error (m8)
HTC One (M8) Won't recognize Sim Card
etc etc...
brichardson1991 said:
Unlocking the bootloader wouldn't affect your device in any means except factory resetting it.
Maybe the tool you used changed the radio? That's the only thing I can think of. Try flashing a different radio
Click to expand...
Click to collapse
redpoint73 said:
Nothing you did should have caused the no signal issue (simply unlocking the bootloader and rooting shouldn't have caused that). So its hard to say what would fix it.
You can try to re-install the stock ROM. Or try to relock the bootloader and see what happens.
Not sure, but I believe relocking the bootloader will wipe data. So backup anything important before doing so.
Click to expand...
Click to collapse
It is S-on. My brother have the same phone and when I checked for his radio version in boot loader screen, Its something like "INVALID_VER_INFO" but my device shows a version number "RADIO-1.19.21331147A1.09G". We've bought both phones recently. His phone is untouched where as I messed up my device just for the apps and app data. I fee terrible now. Please help me to undo everything. I guess I cant even take it to the HTC service center as it says "TAMPERED" and "RELOCKED" banners on top of the bootloader screen.
I've used up all my savings on this device and it seems its wasted now.
Pease help me guyz... :crying:
Kunnu2592 said:
We've bought both phones recently. His phone is untouched where as I messed up my device just for the apps and app data. I fee terrible now. Please help me to undo everything.
Click to expand...
Click to collapse
You've been given several suggestions to try at this point, and haven't indicated whether you attempted them or not.
You can cry all you want. But if you fail to even try to help yourself, we can't help you either.
Kunnu2592 said:
I guess I cant even take it to the HTC service center as it says "TAMPERED" and "RELOCKED" banners on top of the bootloader screen.
Click to expand...
Click to collapse
If you are talking about a warranty claim, warranty doesn't cover damage done by mods you performed. When you chose to unlock the bootloader and root the phone, you accepted all responsibility for any damage that might occur. This is the game we play. If you can't afford to repair or replace the phone in the event of permanent damage done by mods you did; then you shouldn't be modding it in the first place.
If you are talking about paying HTC to fix it, they will still do it if its been tampered. They will likely replace the mainboard and charge you for it.
But honestly, I think your condition can be fixed by software; and sending to HTC is not necessary. But you have to be willing to put in the effort.
redpoint73 said:
You've been given several suggestions to try at this point, and haven't indicated whether you attempted them or not.
You can cry all you want. But if you fail to even try to help yourself, we can't help you either.
If you are talking about a warranty claim, warranty doesn't cover damage done by mods you performed. When you chose to unlock the bootloader and root the phone, you accepted all responsibility for any damage that might occur. This is the game we play. If you can't afford to repair or replace the phone in the event of permanent damage done by mods you did; then you shouldn't be modding it in the first place.
If you are talking about paying HTC to fix it, they will still do it if its been tampered. They will likely replace the mainboard and charge you for it.
But honestly, I think your condition can be fixed by software; and sending to HTC is not necessary. But you have to be willing to put in the effort.
Click to expand...
Click to collapse
Hieee bro..
I've relocked the bootloader and it doesn't help. There was no change. I tried to place a thin paper on back of the sim card to make a better connection. It still doesn't work. It now says TAMPERED and RELOCKED(after relocking the bootloader). I installed a stock firmware and it didn't solved the problem too.
I read endless posts but found nothing that can help the situation. Just waiting for help from my thread.
I want to try restoring my brother's backup. But is it possible to make a complete system backup to flash into my device without rooting? I don't want to mess his device too....
Thank you.
Kunnu2592 said:
I want to try restoring my brother's backup. But is it possible to make a complete system backup to flash into my device without rooting? I don't want to mess his device too....
Click to expand...
Click to collapse
Nope.
Nor will doing so yield anything that isn't already easily available here (so don't bother unlocking bootloader and rooting his phone just to help your own situation, its a waste of time): http://forum.xda-developers.com/showthread.php?t=2701376
Restore the appropriate stock ROM, and see if that helps.
redpoint73 said:
Nope.
Nor will doing so yield anything that isn't already easily available here (so don't bother unlocking bootloader and rooting his phone just to help your own situation, its a waste of time): http://forum.xda-developers.com/showthread.php?t=2701376
Restore the appropriate stock ROM, and see if that helps.
Click to expand...
Click to collapse
Yeahhh bro.. Ua right. I'll try a Stock Rom again and will be bck wid the result.
Thanks for ua help
The question is pretty much straight
Why does HTC S-On the devices when they allow us to unlock bootloader?
HTC says that the main idea of unlocking bootloader is that you can unleash our own phone.
Why can't they just S-OFF the devices when unlocking the bootloader ?
Can anyone fill me in
Thanks
MJ999 said:
The question is pretty much straight
Why does HTC S-On the devices when they allow us to unlock bootloader?
HTC says that the main idea of unlocking bootloader is that you can unleash our own phone.
Why can't they just S-OFF the devices when unlocking the bootloader ?
Can anyone fill me in
Thanks
Click to expand...
Click to collapse
S-off opens up access to pretty much everything and so allows more control. With that are the risks of totally bricking your device. Staying S-on still gives you some protection from mucking things up and the freedom to flash roms/recoveries/kernels.
I agree though, as people are responsible for their actions and so must know the consequences of modding their devices, they should just give another level of access to remove s-off. The warranty is void once you unlock the bootloader anyway.
More info around s-off/NAND/partitions etc:
http://forum.xda-developers.com/showthread.php?t=2619392
gsmyth said:
S-off opens up access to pretty much everything and so allows more control. With that are the risks of totally bricking your device. Staying S-on still gives you some protection from mucking things up and the freedom to flash roms/recoveries/kernels.
Click to expand...
Click to collapse
Now I simply voided my phone's warranty without any use.
Damn it HTC.
MJ999 said:
Now I simply voided my phone's warranty without any use.
Damn it HTC.
Click to expand...
Click to collapse
How did you unlock it? Do you have s-off?
MJ999 said:
Now I simply voided my phone's warranty without any use.
Damn it HTC.
Click to expand...
Click to collapse
Use sunshine to get s-off.
MJ999 said:
The question is pretty much straight
Why does HTC S-On the devices when they allow us to unlock bootloader?
HTC says that the main idea of unlocking bootloader is that you can unleash our own phone.
Why can't they just S-OFF the devices when unlocking the bootloader ?
Can anyone fill me in
Thanks
Click to expand...
Click to collapse
You can still unleash some of your phone by just unlocking, which is probably why they gave the option. You can still flash a custom recovery, you can still root, you can still flash custom ROMs.
S-OFF you can flash different firmwares, you can resize partitions, you can convert to other models. Why would the majority want these? And by the looks of some of these threads, why would even some of the majority of "flashers" need it? Root + Custom Recovery + Custom ROM should be enough to satisfy most.
S-ON then just protects the phone from more serious changes that might lead to more serious damage if *you* don't know what *you're* doing.
BerndM14 said:
You can still unleash some of your phone by just unlocking, which is probably why they gave the option. You can still flash a custom recovery, you can still root, you can still flash custom ROMs.
S-OFF you can flash different firmwares, you can resize partitions, you can convert to other models. Why would the majority want these? And by the looks of some of these threads, why would even some of the majority of "flashers" need it? Root + Custom Recovery + Custom ROM should be enough to satisfy most.
S-ON then just protects the phone from more serious changes that might lead to more serious damage if *you* don't know what *you're* doing.
Click to expand...
Click to collapse
This
When you are S-on/BL locked, your carrier (or HTC/Google) is your system administrator. The carriers take this a bit further, and even manage some of your apps. In a lot of ways, you are a guest on the system, even though you "own" it. However, assuming you just want to use it to make phone calls and post to facebook, for most people this is fine. (my wife's phone isn't even rooted)
When you are BL unlocked, you take over some parts of that sysadmin job, and can now replace parts of the operating system and manage your own apps. You can also disable external control of your device by rooting and turning off certain services. However, the truly critical stuff, the stuff that could keep your phone from booting, are outside of your control. You are now no longer a guest, but you aren't exactly an owner either.
When you S-off, you are taking on the job of being the system administrator entirely. You are 100% responsible for what happens to your phone. Your '44, your Magnum rounds, your foot. Be careful.
gsmyth said:
How did you unlock it? Do you have s-off?
Click to expand...
Click to collapse
I unlocked my bootloader.
No, I don't have S-OFF
KJ said:
Use sunshine to get s-off.
Click to expand...
Click to collapse
BerndM14 said:
You can still unleash some of your phone by just unlocking, which is probably why they gave the option. You can still flash a custom recovery, you can still root, you can still flash custom ROMs.
S-OFF you can flash different firmwares, you can resize partitions, you can convert to other models. Why would the majority want these? And by the looks of some of these threads, why would even some of the majority of "flashers" need it? Root + Custom Recovery + Custom ROM should be enough to satisfy most.
S-ON then just protects the phone from more serious changes that might lead to more serious damage if *you* don't know what *you're* doing.
Click to expand...
Click to collapse
I know about it, but I just want the H/K Mod, I don't think I need to spend 25 bucks for just the mod.
If anything better comes up, I will try sunshine
and during the meantime some devs might also find another way to S-Off hopefully.
But @BerndM14 don't you think HTC should have asked to you choose S-On or S-OFF when unlocking the bootloader or so ?
MJ999 said:
I unlocked my bootloader.
No, I don't have S-OFF
I know about it, but I just want the H/K Mod, I don't think I need to spend 25 bucks for just the mod.
If anything better comes up, I will try sunshine
and during the meantime some devs might also find another way to S-Off hopefully.
But @BerndM14 don't you think HTC should have asked to you choose S-On or S-OFF when unlocking the bootloader or so ?
Click to expand...
Click to collapse
You wont' hear any arguments from me about that, I've made a post about that ages ago in which I stated that manufacturers should give you the option to have your phone rooted, unlocked and in HTC's case S-OFF, if it's a warranty issue then why not just a bit more for warranty purposes, but we still need the choice. Will they ever do something like that? I doubt they'll do anything like that any time soon but it would be nice and I've said so a long time ago already.
Especially as far as development on the devices are concerned. I don't see why they would share the Kernel source to allow developers to develop for the phone while at the same time expecting the developer to just hack away at the device in order to get the necessary permissions to develop for the device!
BerndM14 said:
You wont' hear any arguments from me about that, I've made a post about that ages ago in which I stated that manufacturers should give you the option to have your phone rooted, unlocked and in HTC's case S-OFF, if it's a warranty issue then why not just a bit more for warranty purposes, but we still need the choice. Will they ever do something like that? I doubt they'll do anything like that any time soon but it would be nice and I've said so a long time ago already.
Especially as far as development on the devices are concerned. I don't see why they would share the Kernel source to allow developers to develop for the phone while at the same time expecting the developer to just hack away at the device in order to get the necessary permissions to develop for the device!
Click to expand...
Click to collapse
Thank the GPL for that last one. Android is essentially a very custom distro of Linux, and the Linux community has already shown that they will go after violators. It's how the Linksys WRT54G became the WIFI router to own. IOW, they release it because they have to, but they don't have to make it easy, or usable.
We have seen with the Samsung and LG devices that it is possible to lock down a device fully such that it won't boot anything that isn't cryptographically signed. They will do as little as necessary to comply with the license, without giving us the ability to actually use that knowledge. After all, what good is kernel source if you don't have a signing key the CPU will accept?
That is the primary reason I chose the M8. It was one of the few flagship phones that is still able to be fully owned.
I've always had my devices rooted and running a custom rom or at least a custom kernel or something of the sort "But" ever since I got my pixel about a year ago I haven't felt the need to root at all, stock rom is just perfect and so battery life and I don't see a reason to.
However I was just thinking that now with locked bootloader if for any reason my phone gets bricked then I'm probably [email protected]*t out of luck because I won't be able to flash a factory image to bring the phone back to life.
Should I unlock my bootloader just in case the worse does happen or is there another workaround for such a situation?
Getting bricked is the direct result of flashing images.
nabbed said:
Getting bricked is the direct result of flashing images.
Click to expand...
Click to collapse
I could not disagree more. There are countless threads of individuals taking OTAs and running into boot loop. Additionally I have read through multiple threads where individuals were simply using their phone to play a game, text, phone call etc and the phone shuts off and goes into a loop.
The users with an unlocked bootloader were able to salvage the device. Users without a locked bootloader looked for a RMA.
To the OP- I personally will never own an Android device with a constantly locked bootloader. The safety net of being able to factory reset and flash stock images is something I've always cherished and do not wish to get rid of.
There are security risks to having an unlocked BL. If an Android savvy criminal were to steal your device they could do a lot of damage with obtaining personal information. For me, I'm much more worried about my phone going in to boot loop than I am some criminal being able to take my phone from me.
Sab3elbromba said:
Should I unlock my bootloader just in case the worse does happen or is there another workaround for such a situation?
Click to expand...
Click to collapse
if for any reason, something did get corrupted on your phone with a lockedbootloader and it tripped verified boot. you would be locked out, no course of action but to get an RMA... so if u plan on tinkering with your phone or just would like a failsafe, at least with an unlocked phone. you would be able to flash firmware, etc...
just remember, not to relock your bootloader; unless your phone is running stock firmware and is wiped.... otherwise you will trip verified boot and brick it...
nabbed said:
Getting bricked is the direct result of flashing images.
Click to expand...
Click to collapse
no, it's not. getting a bricked phone is pretty much always because the person did something ill advised or dumb... like relocking their bootloader running custom firmware...
so a diect result of user error, nothing to do with flashing images.
i have an option of buying a soft bricked m8, that says tampered relocked, unknown history of what was done to it, but im thinking have a go at trying to get it running again, i cannot get past any of the screens it's s-on as well, cannot go into phone settings, so i cannot do anything there.
http://img.photobucket.com/albums/v476/charvel_375/htc m8 broke.jpg?t=1515544191
So what is the question? Do you want to know if it's worth the risk/effort of buying? If we think it can be recovered? Or what exactly to do to recover it?
sorry i should have been more specific, answer.. can it be fixed, if so how, as i said i cannot get into the phone settings, i dont know if USB debugging is checked.
bluefender said:
can it be fixed, if so how, as i said i cannot get into the phone settings, i dont know if USB debugging is checked.
Click to expand...
Click to collapse
You typically don't need debugging enabled, to get the phone running. You don't need debugging to use fastboot, and it's fastboot that is critical to get the phone running.
Whether or not the phone can be fixed, is not definite with the information provided so far. A lot of times, no boot just means the ROM is corrupt or otherwise damaged, which is fairly easy to fix by a tool called RUU. Or alternately by unlocking the bootloader, putting custom recovery TWRP on the phone, and using that to flash a stock ROM or custom ROM.
"Tampered" and "relocked" (versus "locked") means that the previous owner did at least try to do some mods (unlocked bootloader, custom recovery, custom ROM and/or root). Whether those attempted mods resulted in the current condition is another question we can't answer (only the previous owner can answer). It could be as simple as a botched root attempt, such as wrong version TWRP or wrong version SuperSU (also easily fixed). Or it could be the simple act of the previous owner locking the bootloader, which by definition renders the phone unable to boot (again, RUU is one possible solution) and the person just didn't know that.
On the other hand, it's possible that the current condition is caused by a hardware failure, such as emmc failure, and you won't be able to flash a ROM, and the phone is pretty much shot (needs new motherboard, etc.). But there is really no way of determining hardware vs. software failure without trying to recover it. Although my gut tells me, this is a pretty easy software fix, and that the current condition is mostly a matter of the previous owner lacking the proper knowledge.
What are the conditions of the sale? Are you buying it "as is" whether you can fix it or not? Or is the person going to let you mess with it, before decided whether to buy it? If you fix it easily, is there a possibility they change their mind, and going to want to keep it?
thanks for the info, buying as is, owner puts his arms up and says no idea, buy as is no returns, possible guilt of not rooting correctly ? who knows.
bluefender said:
buying as is, owner puts his arms up and says no idea, buy as is no returns, possible guilt of not rooting correctly ? who knows.
Click to expand...
Click to collapse
That would be my guess, not rooted correctly, or tried to return to stock, and botched it.
The bet, if I had to make one, would be that it can be recovered (software issue). But as I said, no sure bet there. Might be worth a chance, depending on how much he is charging, and how much that amount of money means to you.
in the end i passed on it, as found out the phone has been doing the rounds, internal chip was dead iv been told.