Related
Hi Guys, have a nice day.
I want to learn something about s-off to s-on. Is this possible ? A device which s-off and then make it s-on ? If Possible how could we do this ?
Thank for helps now
alibalter said:
Hi Guys, have a nice day.
I want to learn something about s-off to s-on. Is this possible ? A device which s-off and then make it s-on ? If Possible how could we do this ?
Thank for helps now
Click to expand...
Click to collapse
Yes you can S-ON after you S-OFF with revone: fastboot oem writesecureflag 3 to S-ON again
Yeah, just make sure you have a stock hboot before doing so. You may want to also lock the bootloader first.
alibalter said:
Hi Guys, have a nice day.
I want to learn something about s-off to s-on. Is this possible ? A device which s-off and then make it s-on ? If Possible how could we do this ?
Thank for helps now
Click to expand...
Click to collapse
really don't do this, you will regret it later...
godutch said:
really don't do this, you will regret it later...
Click to expand...
Click to collapse
why will i regret after it ?
alibalter said:
why will i regret after it ?
Click to expand...
Click to collapse
A better question is why would go from s-off to s-on anyway? You might mess up later and wish you still had s-off so you could fix it.
Sent from my HTC One using xda premium
BenPope said:
Yeah, just make sure you have a stock hboot before doing so. You may want to also lock the bootloader first.
Click to expand...
Click to collapse
can i change my hboot ? is this possible ?
alibalter said:
why will i regret after it ?
Click to expand...
Click to collapse
Read the last 6 pages or so of the revone thread.
alibalter said:
can i change my hboot ? is this possible ?
Click to expand...
Click to collapse
With S-OFF, yes.
If you have an unsigned hboot and then S-On, you'll probably brick your phone.
S-on: you only can flash roms and kernels
S-off: you will also be able to update hboot, and firmware, flash splashscreens and remove red warning text from splashscreen and change radio
You may find this thread useful
http://forum.xda-developers.com/showthread.php?t=2265618
ineedone said:
S-on: you only can flash roms and kernels
S-off: you will also be able to update hboot, and firmware, flash splashscreens and remove red warning text from splashscreen and change radio
Click to expand...
Click to collapse
You can still flash radios with S-on. Agree with the others, you'll regret going S-on unless you need to return the phone under warranty.
Sent from my HTC One using xda app-developers app
farang4u said:
You can still flash radios with S-on. Agree with the others, you'll regret going S-on unless you need to return the phone under warranty.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Agreed, my mistake thanks for correcting
Thanks everybody for helps.
Now i need another thing. Last thing. I know i'm a bit noob.
I flashed a custom kernel. I want to go back stock kernel. How can i do this ? How can i find stock boot.img ?
alibalter said:
Thanks everybody for helps.
Now i need another thing. Last thing. I know i'm a bit noob.
I flashed a custom kernel. I want to go back stock kernel. How can i do this ? How can i find stock boot.img ?
Click to expand...
Click to collapse
get a stock ROM(insertcoin android revolution, etc.), open up the zip and extract the boot.img from the zip file, put it in your Android SDK folder (probably C:/Android), then boot into bootloader, connect USB and get into fastboot mode, and fastboot flash boot boot.img in a command prompt from your Android SDK folder. Backup with your custom recovery and you MIGHT need to wipe data and reinstall ROM (most probably not). You'll know you need to wipe data if you get a bootloop after flashing the Stock Kernel. Just backup before, that's a great rule of thumb
royoshukrun said:
get a stock ROM(insertcoin android revolution, etc.), open up the zip and extract the boot.img from the zip file, put it in your Android SDK folder (probably C:/Android), then boot into bootloader, connect USB and get into fastboot mode, and fastboot flash boot boot.img in a command prompt from your Android SDK folder. Backup with your custom recovery and you MIGHT need to wipe data and reinstall ROM (most probably not). You'll know you need to wipe data if you get a bootloop after flashing the Stock Kernel. Just backup before, that's a great rule of thumb
Click to expand...
Click to collapse
Thank you my friend I got it
htc one with 2.24.401.2 built and 1.54 hboot
tried flash recovery pulled out from cmw back up
tried 2.24.401.1 ota ruu wwe dint work
getting signature fail always please i wan just unroot
htc one m7 said:
htc one with 2.24.401.2 built and 1.54 hboot
tried flash recovery pulled out from cmw back up
tried 2.24.401.1 ota ruu wwe dint work
getting signature fail always please i wan just unroot
Click to expand...
Click to collapse
I am in exactly the same boat
here is my setup
HBOOT: 1.54.0000
OS: 2.24.401.1
Looking for the correct RUU to flash. any help is appreciated
winwiz said:
I am in exactly the same boat
here is my setup
HBOOT: 1.54.0000
OS: 2.24.401.1
Looking for the correct RUU to flash. any help is appreciated
Click to expand...
Click to collapse
this will be my last and first HTC to root
i had gs3 i flash a home rom any second i wanted im searching for that RUU from 1 month ago i dint find it
htc customer services and htc dev both sucks
htc one m7 said:
this will be my last and first HTC to root
i had gs3 i flash a home rom any second i wanted im searching for that RUU from 1 month ago i dint find it
htc customer services and htc dev both sucks
Click to expand...
Click to collapse
I realised that I took a nandroid backup of the original firmware, so I have been successful in returning to stock.
When I boot to the bootloader, I see TAMPERED AND UNLOCKED. I guess this is to to a custom recovery and also unlocked bootloader. Any ideas how I can get this back to normal? Am I then back to stock fully?
winwiz said:
I realised that I took a nandroid backup of the original firmware, so I have been successful in returning to stock.
When I boot to the bootloader, I see TAMPERED AND UNLOCKED. I guess this is to to a custom recovery and also unlocked bootloader. Any ideas how I can get this back to normal? Am I then back to stock fully?
Click to expand...
Click to collapse
me i have my stuck rom running also nandroid pulled by cmd
but no chance for me
There is NO way for you to remove the tampered flag or change relocked to locked if you are on Hboot 1.54, no S-Off available which is what you need. If you are on a lower Hboot then you can S-Off and remove the flag and return to 100% stock.
There are also NO 2.24 RUU's so don't bother trying to find one.
It amuses me that somebody would never buy another HTC phone because they don't know what to do. Other phones can be unlocked , rooted, flashed, by pure noobs who don't know what they're doing. The One requires you to learn a little and do some reading to know what to do, when you've done that you'll find it isn't hard at all.
Why are you so desperate to go back to stock? If you just want the stock experience, flash a stock rom.
If you're trying to hide the fact that you rooted and unlocked in order to return/sell it, you can't really complain that you're having problems trying to deceive people. Sorry.
Had either of you done any research and reading prior to rooting, your problems would have been apparent.
AllAboutTheCore said:
There is NO way for you to remove the tampered flag or change relocked to locked if you are on Hboot 1.54, no S-Off available which is what you need. If you are on a lower Hboot then you can S-Off and remove the flag and return to 100% stock.
There are also NO 2.24 RUU's so don't bother trying to find one.
It amuses me that somebody would never buy another HTC phone because they don't know what to do. Other phones can be unlocked , rooted, flashed, by pure noobs who don't know what they're doing. The One requires you to learn a little and do some reading to know what to do, when you've done that you'll find it isn't hard at all.
Click to expand...
Click to collapse
thanks next time when i need a root i will get s-off before that .now my chance is getting s-off wich is not available now
if u dint tell me dont search i would search for ever XD
iElvis said:
Why are you so desperate to go back to stock? If you just want the stock experience, flash a stock rom.
If you're trying to hide the fact that you rooted and unlocked in order to return/sell it, you can't really complain that you're having problems trying to deceive people. Sorry.
Had either of you done any research and reading prior to rooting, your problems would have been apparent.
Click to expand...
Click to collapse
i just want to get updates from htc
AllAboutTheCore said:
There is NO way for you to remove the tampered flag or change relocked to locked if you are on Hboot 1.54, no S-Off available which is what you need. If you are on a lower Hboot then you can S-Off and remove the flag and return to 100% stock.
There are also NO 2.24 RUU's so don't bother trying to find one.
It amuses me that somebody would never buy another HTC phone because they don't know what to do. Other phones can be unlocked , rooted, flashed, by pure noobs who don't know what they're doing. The One requires you to learn a little and do some reading to know what to do, when you've done that you'll find it isn't hard at all.
Click to expand...
Click to collapse
Noobs are what this thread is for. Why are you flaming and complaining in a Q&A thread anyway? If you're not going to help, get out of the way and flame on elsewhere.
htc one m7 said:
i just want to get updates from htc
Click to expand...
Click to collapse
Then you should've left the phone stock
htc one m7 said:
htc one with 2.24.401.2 built and 1.54 hboot
tried flash recovery pulled out from cmw back up
tried 2.24.401.1 ota ruu wwe dint work
getting signature fail always please i wan just unroot
Click to expand...
Click to collapse
Try a factory reset, but don't use the backup to restore settings. It might be a hassle, but it should uninstall SU, and if you don't restore those settings, it should be unrooted. Just go to play store and reinstall the apps you had before. They should be saved under your account. I hope this helps.
Edit: Another possibility would be to install an all in one toolkit, and have that unroot the phone for you. I'm not 100% sure it would work with 1.54, though. There are two good ones here and here.
Edit: Yet another possibility would be to flash hboot 1.44 and then run the RUU again.
Edit: Finally, have you tried unrooting through the SU app itself?
kibmikey1 said:
Try a factory reset, but don't use the backup to restore settings. It might be a hassle, but it should uninstall SU, and if you don't restore those settings, it should be unrooted. Just go to play store and reinstall the apps you had before. They should be saved under your account. I hope this helps.
Edit: Another possibility would be to install an all in one toolkit, and have that unroot the phone for you. If you used the revone method to root, it should take care of it. I'm not 100% sure it would work with 1.54, though. There are two good ones here and here.
Edit: Yet another possibility would be to flash hboot 1.44 and then run the RUU again.
Click to expand...
Click to collapse
I've personally managed to get it back to stock, and even got an OTA update. The only issue I have is that in the bootloader it's saying TAMPERED and RELOCKED
I guess there is not much I can do about this,
Any above all, thank you for your help. You have been helpful unlike the others with a snobbish attitude
winwiz said:
I've personally managed to get it back to stock, and even got an OTA update. The only issue I have is that in the bootloader it's saying TAMPERED and RELOCKED
I guess there is not much I can do about this,
Any above all, thank you for your help. You have been helpful unlike the others with a snobbish attitude
Click to expand...
Click to collapse
You could run the all in one toolkit and remove the tampered and relocked flags.
---------- Post added at 02:06 AM ---------- Previous post was at 01:17 AM ----------
iElvis said:
Why are you so desperate to go back to stock? If you just want the stock experience, flash a stock rom.
If you're trying to hide the fact that you rooted and unlocked in order to return/sell it, you can't really complain that you're having problems trying to deceive people. Sorry.
Had either of you done any research and reading prior to rooting, your problems would have been apparent.
Click to expand...
Click to collapse
This thread is open for questions like these. Flame on elsewhere.
kibmikey1 said:
Try a factory reset, but don't use the backup to restore settings. It might be a hassle, but it should uninstall SU, and if you don't restore those settings, it should be unrooted. Just go to play store and reinstall the apps you had before. They should be saved under your account. I hope this helps.
Edit: Another possibility would be to install an all in one toolkit, and have that unroot the phone for you. I'm not 100% sure it would work with 1.54, though. There are two good ones here and here.
Edit: Yet another possibility would be to flash hboot 1.44 and then run the RUU again.
Edit: Finally, have you tried unrooting through the SU app itself?
Click to expand...
Click to collapse
unrooting thrrough su app dint work and that tool kit s wont work for 1.54 hboot im so unlucky
htc one m7 said:
unrooting thrrough su app dint work and that tool kit s wont work for 1.54 hboot im so unlucky
Click to expand...
Click to collapse
If your phone was 2.24 out of the box and you never went s-off, you don't need a ruu because your firmware would not have changed. So you just need to restore stock recovery and stock system files, then relock. Flash a stock rom, flash stock recovery in fastboot, and unroot through the superuser app. Then relock in fastboot.
The AIO toolkits will not help with relocked and tampered on 1.54 because they require s-off, which is not available on that hboot. Also, factory reset won't unroot you; it may remove the superuser.apk but will not remove root access.
kibmikey1 said:
Noobs are what this thread is for. Why are you flaming and complaining in a Q&A thread anyway? If you're not going to help, get out of the way and flame on elsewhere.
Click to expand...
Click to collapse
Who's flaming and complaining, and I did help ... I wouldn't help you now but that's another story. As for noobs, If you can't be bothered to read and search then that says something about you. For starters, even though you were wrong (and not the OP) I did help, I have also spent more time helping on here than I have posting anything else, so if you don't like it, you know what you can do.
You might want to give correct advice aswell, if he's on Hboot 1.54 then he'd need S-Off to flash an older Hboot, which he cannot do. Thanks
iElvis said:
If your phone was 2.24 out of the box and you never went s-off, you don't need a ruu because your firmware would not have changed. So you just need to restore stock recovery and stock system files, then relock. Flash a stock rom, flash stock recovery in fastboot, and unroot through the superuser app. Then relock in fastboot.
The AIO toolkits will not help with relocked and tampered on 1.54 because they require s-off, which is not available on that hboot. Also, factory reset won't unroot you; it may remove the superuser.apk but will not remove root access.
Click to expand...
Click to collapse
when i red your reply it seemed too easy but no
stuck recovery when you mean that ''fastboot flash recovery recovery.img'' pulled from nandroid back up ? yes ur right i manged to do that it was succesful but no change even a systim rom is not available getting signature failure 'seems promising yah
i know my thing is hard but it shouldnt be like that right im runing a rom now 4.3 im fine with it but i really want to F*** htcdev members :v
I mean stock recovery, which you can pull from the firmware file for your phone. Find the recovery.img file in the zip and use that.
Stop trying to flash ruus and firmware packages in fastboot; you may screw up your phone doing it.
Just get a stock rom that correspond to the firmware package from the development forum and flash in custom recovery. Then flash the stock recovery in fastboot. Once that's done, you should be able to get OTAs.
iElvis said:
I mean stock recovery, which you can pull from the firmware file for your phone. Find the recovery.img file in the zip and use that.
Stop trying to flash ruus and firmware packages in fastboot; you may screw up your phone doing it.
Just get a stock rom that correspond to the firmware package from the development forum and flash in custom recovery. Then flash the stock recovery in fastboot. Once that's done, you should be able to get OTAs.
Click to expand...
Click to collapse
if you want to help me help me now
i have my reovery.img and it flashes perfectly
how to get stuck rom ?
you mean the file with date it is bout 1.8GB named 2013-08-27.19.58.35 that i should put it in supfic folder do i can flash it with recovery cwm ?
since i have my back up and since it is S-on i wont mind flashing any thing
Hi
My HTC One keeps rebooting into the bootloader every time i turn it on, but if i say reboot, it boots up normally.
I decided to unlock my bootloader and the root the device, but i regret after unlocking the bootloader, so i decided to lock it. But now it just says "relocked" and "security warning". The reason it annoys me, is that i can't install the latest OTA update, because it just reboots into bootloader, and when i say "reboot" it boots up normally and the update is NOT installed.
What do you think i should do?
BTW, sorry if my english isn't perfect...
FML1234 said:
Hi
My HTC One keeps rebooting into the bootloader every time i turn it on, but if i say reboot, it boots up normally.
I decided to unlock my bootloader and the root the device, but i regret after unlocking the bootloader, so i decided to lock it. But now it just says "relocked" and "security warning". The reason it annoys me, is that i can't install the latest OTA update, because it just reboots into bootloader, and when i say "reboot" it boots up normally and the update is NOT installed.
What do you think i should do?
BTW, sorry if my english isn't perfect...
Click to expand...
Click to collapse
Are you still using a custom recovery? You have to flash stock recovery for OTAs.
Cant help you in detail but...
-you can change "Unlocked" to "Locked" with revone S Off
-it seems like you dont have any rom installed... you should flash a stock nandroid backup.. you can found it in the general forum.
nkk71 said:
Are you still using a custom recovery? You have to flash stock recovery for OTAs.
Click to expand...
Click to collapse
Yes, and it is S-OFF, so nothing wrong there either. Should i run an ruu? And if so should where can i find the right one? BTW, it doesn't say "security warning".
FML1234 said:
Yes, and it is S-OFF, so nothing wrong there either. Should i run an ruu? And if so should where can i find the right one? BTW, it doesn't say "security warning".
Click to expand...
Click to collapse
Well custom recovery won't let you get OTA. But your are S-Off :good: excellent.
So first thing I would do, is use revone to get rid of "TAMPERED" and change "RELOCKED" to "LOCKED".
Keep S-Off !!
And finally run your RUU, that would reflash hboot, stock recovery, stock radio, stock ROM... all back to stock, and you should receive the OTAs.
(Remember keep S-Off, cause once you receive the OTA it has an updated hboot which will not allow you to S-Off again)
kehi said:
Cant help you in detail but...
-you can change "Unlocked" to "Locked" with revone S Off
-it seems like you dont have any rom installed... you should flash a stock nandroid backup.. you can found it in the general forum.
Click to expand...
Click to collapse
It is "relocked", and i have the stock rom, the problem is that whenever i run out of juice, and boot it back up, it boots into the bootloader.
nkk71 said:
Well custom recovery won't let you get OTA. But your are S-Off :good: excellent.
So first thing I would do, is use revone to get rid of "TAMPERED" and change "RELOCKED" to "LOCKED".
Keep S-Off !!
And finally run your RUU, that would reflash hboot, stock recovery, stock radio, stock ROM... all back to stock, and you should receive the OTAs.
(Remember keep S-Off, cause once you receive the OTA it has an updated hboot which will not allow you to S-Off again)
Click to expand...
Click to collapse
But my HBOOT is 1.54 and revone doesn't support that
FML1234 said:
But my HBOOT is 1.54 and revone doesn't support that
Click to expand...
Click to collapse
Are you still S-Off? If yes, then you can downgrade your hboot to 1.44 no problem. You can either use a RUU or look if you can find an hboot image to flash using fastboot.
nkk71 said:
Are you still S-Off? If yes, then you can downgrade your hboot to 1.44 no problem. You can either use a RUU or look if you can find an hboot image to flash using fastboot.
Click to expand...
Click to collapse
No, i am not, i thought i was sorry, but thanks a lot for the help. Where can i find the right RUU? I already have one, but it is not the right one.
FML1234 said:
No, i am not, i thought i was sorry, but thanks a lot for the help. Where can i find the right RUU? I already have one, but it is not the right one.
Click to expand...
Click to collapse
There are plenty of RUUs here: http://www.androidruu.com/?developer=M7
if you can't find one for your CID, just change it to SuperCID for the duration of the process; remember you'll only need to downgrade to be able to run revone successfully, after that you can reflash whatever ROM, firmware, etc you choose.
EDIT: nevermind the above, i misread and thought you still had s-off. my bad.
EDIT 2: did you at least flash back stock recovery? if you're still on custom recovery that will cause problems.
nkk71 said:
There are plenty of RUUs here: http://www.androidruu.com/?developer=M7
if you can't find one for your CID, just change it to SuperCID for the duration of the process; remember you'll only need to downgrade to be able to run revone successfully, after that you can reflash whatever ROM, firmware, etc you choose.
EDIT: nevermind the above, i misread and thought you still had s-off. my bad.
EDIT 2: did you at least flash back stock recovery? if you're still on custom recovery that will cause problems.
Click to expand...
Click to collapse
Yes, i have stock recovery.
FML1234 said:
Yes, i have stock recovery.
Click to expand...
Click to collapse
Ok, so I misunderstood a bit.
Back to the original problem:
The reason it annoys me, is that i can't install the latest OTA update, because it just reboots into bootloader, and when i say "reboot" it boots up normally and the update is NOT installed.
Click to expand...
Click to collapse
If I understand correctly after downloading the OTA, you try to install it. The OTA will reboot into bootloader during that process. Correct?
Can't really think of a reason it's doing that, but if it is try going to "recovery" from the bootloader menu not "reboot", and see if it starts installing.
nkk71 said:
Ok, so I misunderstood a bit.
Back to the original problem:
If I understand correctly after downloading the OTA, you try to install it. The OTA will reboot into bootloader during that process. Correct?
Can't really think of a reason it's doing that, but if it is try going to "recovery" from the bootloader menu not "reboot", and see if it starts installing.
Click to expand...
Click to collapse
I'll try that and tell you if it works.
nkk71 said:
Ok, so I misunderstood a bit.
Back to the original problem:
If I understand correctly after downloading the OTA, you try to install it. The OTA will reboot into bootloader during that process. Correct?
Can't really think of a reason it's doing that, but if it is try going to "recovery" from the bootloader menu not "reboot", and see if it starts installing.
Click to expand...
Click to collapse
It didn't work Guess im gonna wait until S-OFF is available on HBOOT 1.54 and then do it.
FML1234 said:
It didn't work Guess im gonna wait until S-OFF is available on HBOOT 1.54 and then do it.
Click to expand...
Click to collapse
Sorry to hear that. Maybe you can post a video, so that we can follow your steps.
Anyway, wish you good luck
Sent from my HTC One using xda app-developers app
nkk71 said:
Sorry to hear that. Maybe you can post a video, so that we can follow your steps.
Anyway, wish you good luck
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
I might consider doing that. I'm pretty newish to rooting and stuff like that, but i'll try
So I was running stock rooted and decided to run the Google Play Edition rom the latest one. It isnt in a bootloop but when I get to the home screen the screen is black, blinks for a second and goes back to being a black screen. Was wondering if I should just let the phone die and see if I could still boot in recovery and maybe flash a backup. But as of now I dont have a phone and would appreciate someones help.
Are you S-ON? If so, did you fastboot flash the boot.img?
Also if you're S-ON, you should S-OFF immediately to avoid these types of situations in the future .
Captain_Throwback said:
Are you S-ON? If so, did you fastboot flash the boot.img?
Also if you're S-ON, you should S-OFF immediately to avoid these types of situations in the future .
Click to expand...
Click to collapse
I guess I should add instructions to my guide on how to fastboot flash kernels, huh?
Quick question, Cap. Is fastboot flashing the kernel only required for GPE when S-on, or is it AOSP in general? Reason I ask is I haven't seen much mention of it elsewhere.
Edit: Guide updated with instructions for S-on kernel flashing. Hit the second link in my sig.
Magnum_Enforcer said:
I guess I should add instructions to my guide on how to fastboot flash kernels, huh?
Quick question, Cap. Is fastboot flashing the kernel only required for GPE when S-on, or is it AOSP in general? Reason I ask is I haven't seen much mention of it elsewhere.
Edit: Guide updated with instructions for S-on kernel flashing. Hit the second link in my sig.
Click to expand...
Click to collapse
The only time fastboot flashing the kernel should ever be necessary is if the device is S-ON.
S off
Captain_Throwback said:
Are you S-ON? If so, did you fastboot flash the boot.img?
Also if you're S-ON, you should S-OFF immediately to avoid these types of situations in the future .
Click to expand...
Click to collapse
I did some research I found that I should be s off but cant seem to find a way to do it. I tried the firewater way but that didnt seem to work, I heard people saying that it only works for GSM devices. Could you direct me to the source of where I can S off my device? Thanks
brothernc said:
I did some research I found that I should be s off but cant seem to find a way to do it. I tried the firewater way but that didnt seem to work, I heard people saying that it only works for GSM devices. Could you direct me to the source of where I can S off my device? Thanks
Click to expand...
Click to collapse
Firewater works on all M8 variants, but some devices aren't compatible. SunShine S-OFF works on all M8s.
Captain_Throwback said:
Firewater works on all M8 variants, but some devices aren't compatible. SunShine S-OFF works on all M8s.
Click to expand...
Click to collapse
Alright well yeah that one didnt work on my device and I tried it like 5 times. Also once Im s off....... I wanted to just go over the process so I dont mess anything up, when you said flashboot flash the boot.img what exactly did you mean? Sorry if I am asking a stupid question.
brothernc said:
Alright well yeah that one didnt work on my device and I tried it like 5 times. Also once Im s off....... I wanted to just go over the process so I dont mess anything up, when you said flashboot flash the boot.img what exactly did you mean? Sorry if I am asking a stupid question.
Click to expand...
Click to collapse
While S-on you need to fastboot flash the boot.img. Hit the second link in my sig and read down to the portion on S-on kernel flashing. Once S-off you can just flash like normal and ignore the info above.
Sent from my HTC M8
Magnum_Enforcer said:
While S-on you need to fastboot flash the boot.img. Hit the second link in my sig and read down to the portion on S-on kernel flashing. Once S-off you can just flash like normal and ignore the info above.
Sent from my HTC M8
Click to expand...
Click to collapse
So I if I fastboot flash the boot img while im s off I would have no reason to s off?
brothernc said:
So I if I fastboot flash the boot img while im s off I would have no reason to s off?
Click to expand...
Click to collapse
Update: I flashed the kernel through fastboot and it worked sorta I got to the welcome screen where it asks me my language but then keeps boot looping. Any idea.
brothernc said:
So I if I fastboot flash the boot img while im s off I would have no reason to s off?
Click to expand...
Click to collapse
There are other reasons to S-off. Perhaps you should read the entire Hboot guide I wrote for the M8, not just the portion regarding flashing kernels while S-on.
Magnum_Enforcer said:
There are other reasons to S-off. Perhaps you should read the entire Hboot guide I wrote for the M8, not just the portion regarding flashing kernels while S-on.
Click to expand...
Click to collapse
Alright so i fixed the issue, when I flashed the rom without doing a full wipe, then flashing the SU that seemed to do the trick. Not 100% sure why but it works perfectly fine with no issued. Thanks for all your help.
Hello guys im new to the forum so sorry for any mistakes I make. Im trying to unbrick an HTC One M7 (S - ON). By using the command 'fastboot getvar version-main' I found out that the image required by the phone is 1.27.206.1 . I have searched for days but I cant seem to find the correct RUU. I did find it in a thread on XDA forum but the link was broken. Can anyone help me? If the RUU is not available is there any other way to unbrick the device?
Thanks in Advance!
FIXED: Read the summary below
I was able to find the correct RUU but the files available were incomplete. So with a lot of help from clsA and nkk71 I was able to find an alternative solution. The solution was to download the Android Revolution HD rom for HTC One and use ADB SIDELOAD to transfer the file in the internal storage From there on it was a piece of cake!
metalmouth22 said:
Hello guys im new to the forum so sorry for any mistakes I make. Im trying to unbrick an HTC One M7 (S - ON). By using the command 'fastboot getvar version-main' I found out that the image required by the phone is 1.27.206.1 . I have searched for days but I cant seem to find the correct RUU. I did find it in a thread on XDA forum but the link was broken. Can anyone help me? If the RUU is not available is there any other way to unbrick the device?
Thanks in Advance!
Click to expand...
Click to collapse
Try this one >>
http://www.androidruu.com/getdownlo...8_10.38r.1157.04L_release_353143_signed_2.exe
Alt download
http://www.htc1guru.com/dld/ruu_m7_..._10-38r-1157-04l_release_353143_signed_2-exe/
Didnt work
Thank you clsA for replying. I downloaded and launched the .exe file. Unfortunately it give me ERROR 158 - Image Error. What should i do now?
metalmouth22 said:
Thank you clsA for replying. I downloaded and launched the .exe file. Unfortunately it give me ERROR 158 - Image Error. What should i do now?
Click to expand...
Click to collapse
download it again and check the MD5 of your downloaded file
clsA said:
download it again and check the MD5 of your downloaded file
Click to expand...
Click to collapse
Whats MD5 and how to check it? Sorry im kind of new to all this
metalmouth22 said:
Whats MD5 and how to check it? Sorry im kind of new to all this
Click to expand...
Click to collapse
Did you ask Google ?
http://www.droidviews.com/check-md5sum-of-a-file-on-windows-mac-and-linux/
I got it im going to check it right now. I just wanted to confirm something. When I download an RUU isnt it necessary that the image number is same. Like my image is 1.27.206.1 so shouldnt i use an RUU with the same image?
metalmouth22 said:
I got it im going to check it right now. I just wanted to confirm something. When I download an RUU isnt it necessary that the image number is same. Like my image is 1.27.206.1 so shouldnt i use an RUU with the same image?
Click to expand...
Click to collapse
with S-ON, you'll need an RUU which is same or higher version for your MID+CID, which can be inferred from the .206. = O2 UK
you have 1.27.206.1, so you need and RUU which is higher (or equal) to 1.27.206.1; the 1.27.xxx.1 would refer to the actual software version information, the .xxx. indicates the carrier-branded, region, etc. if the version is greater or equal to 1.27.xxx.1 and the .xxx. is 206 then you can run it.
PS: you'll also need a locked/relocked bootloader with s-on, for the ruu to work
nkk71 said:
with S-ON, you'll need an RUU which is same or higher version for your MID+CID, which can be inferred from the .206. = O2 UK
you have 1.27.206.1, so you need and RUU which is higher (or equal) to 1.27.206.1; the 1.27.xxx.1 would refer to the actual software version information, the .xxx. indicates the carrier-branded, region, etc. if the version is greater or equal to 1.27.xxx.1 and the .xxx. is 206 then you can run it.
PS: you'll also need a locked/relocked bootloader with s-on, for the ruu to work
Click to expand...
Click to collapse
nkk71 you are a life saver thank you so much, its all clear now. I searched htc1guru.com and saw that only one link applies to me which clsA pointed out. Its an .exe file and im having MD5 issues. other than that im good to go. Im just trying to find a solution to the MD5 issue.
metalmouth22 said:
nkk71 you are a life saver thank you so much, its all clear now. I searched htc1guru.com and saw that only one link applies to me which clsA pointed out. Its an .exe file and im having MD5 issues. other than that im good to go. Im just trying to find a solution to the MD5 issue.
Click to expand...
Click to collapse
use a download manager
EDIT: if you ever think/thought/will think of S-OFF, now would be the time i guess
nkk71 said:
use a download manager
EDIT: if you ever think/thought/will think of S-OFF, now would be the time i guess
Click to expand...
Click to collapse
Use a download manager for the .exe file? any suggestions? (sorry for the irritating questions)
Haha yeah your right but actually im repairing this phone for a friend. But ill still go ahead and turn S-OFF
metalmouth22 said:
Use a download manager for the .exe file? any suggestions? (sorry for the irritating questions)
Haha yeah your right but actually im repairing this phone for a friend. But ill still go ahead and turn S-OFF
Click to expand...
Click to collapse
s-off will be harder to achieve once you update to a 4.xx RUU
as for download managers, there are plenty, if you want a free (and pretty decent one), i usually use FireFox + DownThemAll add-in
nkk71 said:
s-off will be harder to achieve once you update to a 4.xx RUU
as for download managers, there are plenty, if you want a free (and pretty decent one), i usually use FireFox + DownThemAll add-in
Click to expand...
Click to collapse
I used Internet Download manager and again downloaded the .exe but Its still not working. I have downloaded it multiple times and it even passed the MD5 test. However, when i check the properties of the .exe the size and size on disk are different from each other. They are different only by 300 to 400 KB, does this have anything to do with the problem im having?
metalmouth22 said:
I used Internet Download manager and again downloaded the .exe but Its still not working. I have downloaded it multiple times and it even passed the MD5 test. However, when i check the properties of the .exe the size and size on disk are different from each other. They are different only by 300 to 400 KB, does this have anything to do with the problem im having?
Click to expand...
Click to collapse
if the MD5 check passed (ie the file you downloaded gives an MD5 hash = 4961fdbbadba53c9640f3638f56faec1) then the file is good.
but the 4.xx RUUs are known to be very sensitive to PC configuration, USB ports, etc. so you should try it with a plain vanilla setup of Windows 7 + USB2 port.
Though (just a thought), why not flash a custom recovery and ROM to get your device back to life, (and possibly even S-OFF).... how did you brick it anyway?
can you also post a "fastboot getvar all" (excluding IMEI and s/n)
nkk71 said:
if the MD5 check passed (ie the file you downloaded gives an MD5 hash = 4961fdbbadba53c9640f3638f56faec1) then the file is good.
but the 4.xx RUUs are known to be very sensitive to PC configuration, USB ports, etc. so you should try it with a plain vanilla setup of Windows 7 + USB2 port.
Though (just a thought), why not flash a custom recovery and ROM to get your device back to life, (and possibly even S-OFF).... how did you brick it anyway?
can you also post a "fastboot getvar all" (excluding IMEI and s/n)
Click to expand...
Click to collapse
I think you are right, something is wrong with that file.
If there is any other way to get this thing going please let me know. It's actually a friend's phone and i think he bricked it while installing a rom.I ran the command, this is what i got.
metalmouth22 said:
I think you are right, something is wrong with that file.
If there is any other way to get this thing going please let me know. It's actually a friend's phone and i think he bricked it while installing a rom.I ran the command, this is what i got.
Click to expand...
Click to collapse
why don't you go ahead and:
1- unlock bootloader
2- flash custom recovery
3- flash custom ROM
4- get s-off
5- enjoy
how does that sound?
nkk71 said:
why don't you go ahead and:
1- unlock bootloader
2- flash custom recovery
3- flash custom ROM
4- get s-off
5- enjoy
how does that sound?
Click to expand...
Click to collapse
That sounds good ! Just need to confirm that the bootloader on this phone is relocked not locked. do i need to visit htcdev and follow the protocol to unlock it? secondly by custom recovery you mean CWM or TWRP? I already have TWRP on the phone.
metalmouth22 said:
That sounds good ! Just need to confirm that the bootloader on this phone is relocked not locked. do i need to visit htcdev and follow the protocol to unlock it? secondly by custom recovery you mean CWM or TWRP? I already have TWRP on the phone.
Click to expand...
Click to collapse
to unlock (with s-on), yes you'd need to HTCdev again, BUT if you already have TWRP installed, i recommend you flash the following ROM:
http://forum.xda-developers.com/showpost.php?p=48955645&postcount=251
you can either push it or sideload it to TWRP, once it boots up, use revone to s-off
http://forum.xda-developers.com/showthread.php?t=2314582
revone will also allow to unlock bootloader
once you have s-off, the options are almost limitless, but please remember to flash only things meant for your phone/modelid ... flashing a wrong hboot for example will end up bricking your phone (not trying to scare you but don't think just cause you have s-off, you can now flash an HTC M8 firmware/hboot)
nkk71 said:
to unlock (with s-on), yes you'd need to HTCdev again, BUT if you already have TWRP installed, i recommend you flash the following ROM:
http://forum.xda-developers.com/showpost.php?p=48955645&postcount=251
you can either push it or sideload it to TWRP, once it boots up, use revone to s-off
http://forum.xda-developers.com/showthread.php?t=2314582
revone will also allow to unlock bootloader
once you have s-off, the options are almost limitless, but please remember to flash only things meant for your phone/modelid ... flashing a wrong hboot for example will end up bricking your phone (not trying to scare you but don't think just cause you have s-off, you can now flash an HTC M8 firmware/hboot)
Click to expand...
Click to collapse
So if i use the rom from the first link i will not have to unlock the bootloader? If thats the case then great ill get on it. Thanks a lot nkk71 and sorry for being a pain =P
metalmouth22 said:
So if i use the rom from the first link i will not have to unlock the bootloader? If thats the case then great ill get on it. Thanks a lot nkk71 and sorry for being a pain =P
Click to expand...
Click to collapse
as long as you already have custom recovery on your phone, it should work (honestly, i've never tried, but it should work)
one of the reasons for HTCdev unlock, is to get a custom recovery on your phone (which you cannot do with S-ON and locked/relocked bootloader)
good luck