You might have seen this in the desire subforum already,
here's the confirmation: S-OFF HBOOT with fastboot features is also coming for Legend!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Coming soon to a topic in your neighbourhood!
WANT! Give me now. I care not for my grammar in this post. That is the degree to which I WANT THAT NOW!!!
I am aware that this might be a noob question but what does this S-OFF HBOOT with fastboot features enable???
Chaotick said:
I am aware that this might be a noob question but what does this S-OFF HBOOT with fastboot features enable???
Click to expand...
Click to collapse
Search the forums. This has been asked for a million+1 times now. You should be able to find enough information on security/s-on/s-off.
Chaotick said:
I am aware that this might be a noob question but what does this S-OFF HBOOT with fastboot features enable???
Click to expand...
Click to collapse
I guess a few people will wonder the same question...so...
S_OFF is another way of saying "security off"...which means that nand is unlocked and so is the bootloader.
This basically means that you can mod the system while booted. S_ON means security on...nand is locked and so is bootloader.
Therefore your phone’s security level can be set to S-OFF, thus bypassing a standard security feature which checks the signatures of firmware images before flashing them.
I *think* with nand unlocked we can apply metamorph themes, but that I am not 100% sure of myself....I sure hope so though!!
c_man said:
I guess a few people will wonder the same question...so...
S_OFF is another way of saying "security off"...which means that nand is unlocked and so is the bootloader.
This basically means that you can mod the system while booted. S_ON means security on...nand is locked and so is bootloader.
Therefore your phone’s security level can be set to S-OFF, thus bypassing a standard security feature which checks the signatures of firmware images before flashing them.
I *think* with nand unlocked we can apply metamorph themes, but that I am not 100% sure of myself....I sure hope so though!!
Click to expand...
Click to collapse
Security is actually a flag set in Radio NVRAM.
HBOOT acts according to this flag being set to on or off. That means, locking NAND, checking signatures. Then there's engineering bootloaders.
ENG bootloaders ignore the security flag, and act like the phone is S-OFF, thereby disabling the nand lock and signature checks. As an added feature, it also allows for flashing images directly using fastboot, e.g.: fastboot flash boot boot.img. It also offers a feature (for developers) to test kernels, by doing 'fastboot boot boot.img' which does not actually write anything, but just boots the downloaded kernel image.
The HBOOT we will release will be very (if not 100%) close to ENG bootloaders.
It ignores the security flag in radio NVRAM (we can't set this, yet), and it allows for the extended fastboot features listed above.
This does mean, that if an OTA overwrites the installed patched HBOOT, the security-ignore and extended fastboot features are lost.
This differs from Radio S-OFF, whereas this would survive any OTA/RUU.
The intended effect however, is the same.
ieftm said:
Security is actually a flag set in Radio NVRAM.
HBOOT acts according to this flag being set to on or off. That means, locking NAND, checking signatures. Then there's engineering bootloaders.
ENG bootloaders ignore the security flag, and act like the phone is S-OFF, thereby disabling the nand lock and signature checks. As an added feature, it also allows for flashing images directly using fastboot, e.g.: fastboot flash boot boot.img. It also offers a feature (for developers) to test kernels, by doing 'fastboot boot boot.img' which does not actually write anything, but just boots the downloaded kernel image.
The HBOOT we will release will be very (if not 100%) close to ENG bootloaders.
It ignores the security flag in radio NVRAM (we can't set this, yet), and it allows for the extended fastboot features listed above.
This does mean, that if an OTA overwrites the installed patched HBOOT, the security-ignore and extended fastboot features are lost.
This differs from Radio S-OFF, whereas this would survive any OTA/RUU.
The intended effect however, is the same.
Click to expand...
Click to collapse
appreciated the time to explain... thanks man!
[noob question] does this mean we'll be able to do the "fastboot oem unlock" like in the nexus one and just install custom ROMs after that without having to go through the whole messy goldcard/downgrade/root procedure?
(wait, let me guess... we'll need to be rooted to get this S-OFF thing working, wont we?)
ieftm said:
You might have seen this in the desire subforum already,
here's the confirmation: S-OFF HBOOT with fastboot features is also coming for Legend!
Coming soon to a topic in your neighbourhood!
Click to expand...
Click to collapse
Something for me to alpha test too??
Any more news for this?
the_canuck said:
[noob question] does this mean we'll be able to do the "fastboot oem unlock" like in the nexus one and just install custom ROMs after that without having to go through the whole messy goldcard/downgrade/root procedure?
(wait, let me guess... we'll need to be rooted to get this S-OFF thing working, wont we?)
Click to expand...
Click to collapse
Yes, you will need to have root. But you should view this as something for the 'future'. You will be able to install ROMs, even RUU's (as long as you delete the HBOOT update in it) without a problem.So after the initial root access, you're good to go. Besides, unrEVOked will have a one-click solution for that.
TheGrammarFreak said:
Any more news for this?
Click to expand...
Click to collapse
No ETA will be given. Just wait it out while we make it safe to use.
Is it the new version of unrevoked forever, or a separate project?
Sent from my HTC Legend using XDA App
ieftm said:
Yes, you will need to have root. But you should view this as something for the 'future'. You will be able to install ROMs, even RUU's (as long as you delete the HBOOT update in it) without a problem.So after the initial root access, you're good to go. Besides, unrEVOked will have a one-click solution for that.
Click to expand...
Click to collapse
the day unrEVOked starts working for the Legend will be a glorious day indeed.
Firecold said:
Is it the new version of unrevoked forever, or a separate project?
Sent from my HTC Legend using XDA App
Click to expand...
Click to collapse
Separate project. My understanding of this is that it's a different, not quite as good, method of achieving the same thing. Correct me if I'm wrong though, of course.
---------------------------------------------------------
I'll wait it out. Thank you so much for doing this though.
TheGrammarFreak said:
Separate project. My understanding of this is that it's a different, not quite as good, method of achieving the same thing. Correct me if I'm wrong though, of course.
---------------------------------------------------------
I'll wait it out. Thank you so much for doing this though.
Click to expand...
Click to collapse
I see you got your legend overclocked and I just wanted to hear if you could sort of quick-guide me trough it, last time my phone keept repbooting for like 2 hours.
So if you could help me out a bit i would appreciate it very much
copponex said:
I see you got your legend overclocked and I just wanted to hear if you could sort of quick-guide me trough it, last time my phone keept repbooting for like 2 hours.
So if you could help me out a bit i would appreciate it very much
Click to expand...
Click to collapse
I've PM'd you, this is kind of an inappropriate thread. I really hope you have already done some research on the matter.
It is my understanding that S-Off for now is only compatible with Custom ROMs? Without Froyo available I am kind of hesitant to install one on our rooted Legend, as long as Froyo is still a possibility
What do you mean? If FroYo is available in the future, there will be RUU available too (most possibly). So you have nothing to worry about flashing, just be sure not to apply any full OTA update or OTA update that you don't know what exactly is in it.
Thanks but you misunderstood. Just heard that S-Off will not work on Legend Stock ROM, which I will keep until Froyo is out. I think there will be a S-Off Update compatible with Stock, too. But of course we have to get S-Off in the first place - I have it for Desire.
It depends on what do you mean by stock. If you mean RUU or full OTA then yes. But why in the love of <put here your preffered_messiah> should you ever install full RUU except when returning the phone? For your system to be fully operational, you need just boot.img and system.img from that RUU. Flashing full new RUU will most probably lock you out.
Related
Hi!
I've got a Nexus One with HBOOT 0.33 and S-OFF. I guess it's a developer version. I'm wondering if anyone with S-OFF tried updating to HBOOT 0.35 and if their phones remained S-OFF or of they lost it. Not sure about updating just yet, but my boot partition has some bad blocks, so I guess I could benefit from it. Please let me know.
wrong section
Sorry, mods, please move this to the correct sub-forum.
I have S-ON since I updated to 0.35, but I still can flash ROMs etc.. whats the difference between S-ON and S-OFF if I still can flash ROMs and the AMON_RA Recovery still works?
[email protected] said:
I have S-ON since I updated to 0.35, but I still can flash ROMs etc.. whats the difference between S-ON and S-OFF if I still can flash ROMs and the AMON_RA Recovery still works?
Click to expand...
Click to collapse
You can relock the bootloader.
Not sure about "wrong section". My personal advise: If you haven't realized or felt the need for S-OFF its not really important, devices have a short life time, make sure you don't waste too much time on this subject as it is really for system developers.
Warranty theoretically expires by unlocking the boot loader, as for real life I haven't heard yet of a single "rejection" by HTC due an unlocked boot loader.. except if you brick your screen by dropping the device etc.
Hope this helps.
Well, I guess I'm just proud of having an S-OFF version of the phone, but no real use for it. I'll leave it for now, I guess and will let you know the result if I do update it.
completely pointless, however I think I'd feel the same ;-)
(Now sitting at a real keyboard, easier to type)
RunTimeWorld is correct, these devices do have a short life time, so it would be a shame to wast it on waiting for an answer/explanation of a small thing like S-OFF on a Nexus One. However, I figured it like this: Seeing as I can run Kang-o-Rama with IR's kernel properly on my current HBOOT/Radio config, I'm not changing it until I need to. I see that my phone frequently is checking (and finding) the HBOOT update, but we'll just see when CM7 is closer to release. All that 0.35 would profit me would be a smaller recovery partition but a larger boot partition. If I need to flash a larger kernel, I'll definitely switch.
Mine remained S-OFF after updating to .35
Rusty! said:
Mine remained S-OFF after updating to .35
Click to expand...
Click to collapse
Sounds reassuring.
Exactly how did you update to 0.35? Using the official zip file downloaded from the Google servers or through the Korean OTA/RUU?
Via the recent 2 part OTA update (not Korean).
Aha, so I guess I'll just try it then.
Success
Here's the result, for you other Nexus One owners with S-OFF. Like i said, it's pretty much only for personal pride, but it's still nice to see my phone didn't loose it's "Developer phone" status when upgrading the HBOOT.
I believe the 'developer' ones say "ENG S-OFF", not "SHIP S-OFF"... ours are freaks and probably just a mistake by HTC.
Well, I guess you could be right. Mine was bought second hand in late May 2010 from a person who's mother (the actual previous owner) works for the Swedish telecommunication company Ericsson. One can only guess that she got it at some Google event or something similar. Anyway, I'm quite pleased to have something special.
Hello all,
This morning I decided to clear data/wipe as I wanted to install a new rom, but once I did that the device would not boot up anymore. Yes it was S-Off using the Alpharevx. After I saw that it would not boot up I thought I would try to restore it with the rom that I was using before the S-off (Sasktel Froyo). After flashing the rom I have been stuck in the bootloader with the msg ***Security Warning*** and not been able to fix it since.
I have extracted the rom.zip out of all the stock roms and renamed them PG32IMG but none of them would work... I googled to see if anyone else has had an issue like this and found that an HTC Thunderbolt went through the same thing and all you have to do is flash it with the firmware the phone came with. My Incredible S is from Bell Canada and I cannot find that RUU anywhere...
Can anyone please help me because I really don't know anything else that I can do... I am lost.
I am going to post the image of the bootloader so you guys can see what I am talking about...
Thanks for all your help, I appreciate it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
did you use an goldcard while flashing the PG32IMG.zip? because you will need this
I used a goldcard to flash the Sasktel rom initially, now when I try to flash Sasktel again it says "Main Version is older!". How can I do now when I am in the bootloader?
Is there the stock rom from Bell out by any chance?
When flash new recovery ,do not plug your device in USB.
Sent from my HTC Incredible S using XDA App
^ I have already tried that numerous times still no luck.
I don't understand why it will not boot up with Sasktel rom...
EDIT: Is there any way when the phone is in bootloader for Alpharevx to detect it so I can S-Off again? I believe that if I can S-off the phone again I can flash the other ROMs and install Clockwork again... Is that possible?
Anyone any idea?
try get a hold of one of the devs from alpharev, this goes beyond limits for this sections mate ;/
Hawkysoft said:
try get a hold of one of the devs from alpharev, this goes beyond limits for this sections mate ;/
Click to expand...
Click to collapse
Yes I already have, they have told me that the only way of fixing it is with an XTC clip. Luckily there is someone in my area willing to meet .
Thanks for your help.
An XTC clip is the best option for you...
You cant down grade an S-ON Phone with the goldcard !!! so i dont see ny options for ur case !! u should go with the words of the alpharevx developers !!!
__________________________________________________
[Status] Rooted S-OFF
[Recovery] 4EXTRecovery v 1.0.6 (A CWMR 4.0.0.2 Mod)
[ROM] CyanogenMod cm-7.1.0-RC0
[Theme] CyanogenMod
[Radio] 3805.04.03.22_M
[Hboot] 1.09.1000
[Case] Seidio Innocase Case
Contact the devs from alpha revx
please ask them for help,im sure they ll help u out , they have helped me a lot , one small request they might be busy so its better to ask before pinging them again and again...)...
http://webchat.freenode.net/?channels=alpharevx
telectroguy said:
please ask them for help,im sure they ll help u out , they have helped me a lot , one small request they might be busy so its better to ask before pinging them again and again...)...
http://webchat.freenode.net/?channels=alpharevx
Click to expand...
Click to collapse
Hey thanks for the help...
I met up with someone that tried to S-Off my phone with the XTC clip and that didn't even work. I think the only way to fix the phone is just wait it out until Bell releases their gingerbread update...
The phone has a froyo Rom but it is stuck with a gingerbread radio. That is why the original froyo Rom you went back to will not work. (Can't downgrade from gingerbread radio to froyo radio) Only option is to some how get a gingerbread Rom on your phone.
I don't think you can flash your phone with an RUU the normal way.(goldcard way)
Check this thread out. Info about flashing an RUU for the a Canadian Incredible S.
http://forum.xda-developers.com/showthread.php?p=15166814
Sent from my HTC Incredible S using XDA Premium App
I have the same problem is there a solution to this?
neo-X said:
I have the same problem is there a solution to this?
Click to expand...
Click to collapse
You have to flash the stock RUU the phone came with originally. That is the only way to fix it.
EDIT: Resolved, pm me if you want help claudiujer
neo-X maybe you should share the solution how you did it?
Hawkysoft said:
neo-X maybe you should share the solution how you did it?
Click to expand...
Click to collapse
I flashed the 6.03.03 radio in gu1dry's thread, but they are actually ruu's (i didn't know) and the "main version" in that ruu was 1400 (ieftm has now pointed it out to gu1dry). I then tried to be smart and downgrade to the optus rom which was a lower version which of course failed half way through but by that time it was too late.
I was however very lucky that the higher version RUU_Vivo_Gingerbread_S_HTC_WWE_2.30.405.1 was posted in Football's thread, so i decide to give it all one last shot. So i ran that ruu with a goldcard and i worked.
Claudiu, i can't reply to your PM for some reason. so just reply here (I think you've disabled PM's)
Claudiu, from command prompt run "fastboot getvar all" with your phone connected while in fastboot this will tell you what main version you are running, you are going to have to get an ruu that is higher than this version, otherwise it won't work.
neo-X said:
I flashed the 6.03.03 radio in gu1dry's thread, but they are actually ruu's (i didn't know) and the "main version" in that ruu was 1400 (ieftm has now pointed it out to gu1dry). I then tried to be smart and downgrade to the optus rom which was a lower version which of course failed half way through but by that time it was too late.
I was however very lucky that the higher version RUU_Vivo_Gingerbread_S_HTC_WWE_2.30.405.1 was posted in Football's thread, so i decide to give it all one last shot. So i ran that ruu with a goldcard and i worked.
Claudiu, i can't reply to your PM for some reason. so just reply here (I think you've disabled PM's)
Claudiu, from command prompt run "fastboot getvar all" with your phone connected while in fastboot this will tell you what main version you are running, you are going to have to get an ruu that is higher than this version, otherwise it won't work.
Click to expand...
Click to collapse
So all you did was run the RUU_Vivo_Gingerbread_S_HTC_WWE_2.30.405.1 and it worked?
I have done that so many times and it hasn't worked because I have the Bell IncS. I will try to flash the radio though and hopefully I will get something different...
ClaudiuJer said:
So all you did was run the RUU_Vivo_Gingerbread_S_HTC_WWE_2.30.405.1 and it worked?
I have done that so many times and it hasn't worked because I have the Bell IncS. I will try to flash the radio though and hopefully I will get something different...
Click to expand...
Click to collapse
So you've tried to run the RUU_Vivo_Gingerbread_S_HTC_WWE_2.30.405.1 ruu with a goldcard?
Did it fail, what was the the error message?
neo-X said:
So you've tried to run the RUU_Vivo_Gingerbread_S_HTC_WWE_2.30.405.1 ruu with a goldcard?
Did it fail, what was the the error message?
Click to expand...
Click to collapse
Actually I have't tried it yet because the download link is not working... Where did you download it from?
I have been looking around but i can't find my RUU.
I want to return my phone back to stock, since i can't update my phone while rooted.
Also my experience with this is seriously 0 (buddy of mine rooted this), so i'm sorry if i might sound stupid.
I have downloaded all the Ruu files from the return back to stock forum here and non of them worked.
My software number is: 1.29.111.11
Thanks in advance
Whose the carrier?
caster62003 said:
Whose the carrier?
Click to expand...
Click to collapse
T-mobile
Alright, now that I have a clear mind and actually read your question completely...
When you tried the previous RUUs before, did they fail during flash or did Android not function correctly when you got in?
If the RUU flash failed, you more than likely still have an unlocked bootloader, which was required during the root process and the RUU does not like, so it fails.
Considering your knowledge on Android/HTC One, I'm going to point you here, download the Toolkit, extract it to somewhere... Note: I am not affiliated with the development of the Toolkit, I have used it before and IMO it is a great program, very HTC One noob friendly.
On your phone make sure USB Debugging is enabled, then, launch the Toolkit -> On the left hand side, under Basic ADB, click Bootloader. Your phone will turn off, then get into the Bootloader.
At the top, it should say Unlocked, if it does, you need to relock the bootloader, now on the right hand side of the Toolkit, check the checkbox under Agreement which will then enable the Re-lock button, click that (DO NOT CLICK S-On), Your phone will reboot to Android, Once back, click the Bootloader button again Under Basic ADB. This time instead of Unlocked, it will say Relocked. Now try running the RUU again, this time it should work.
Once the RUU flash is done, you should be all set to get going again.
caster62003 said:
Alright, now that I have a clear mind and actually read your question completely...
When you tried the previous RUUs before, did they fail during flash or did Android not function correctly when you got in?
If the RUU flash failed, you more than likely still have an unlocked bootloader, which was required during the root process and the RUU does not like, so it fails.
Considering your knowledge on Android/HTC One, I'm going to point you here, download the Toolkit, extract it to somewhere... Note: I am not affiliated with the development of the Toolkit, I have used it before and IMO it is a great program, very HTC One noob friendly.
On your phone make sure USB Debugging is enabled, then, launch the Toolkit -> On the left hand side, under Basic ADB, click Bootloader. Your phone will turn off, then get into the Bootloader.
At the top, it should say Unlocked, if it does, you need to relock the bootloader, now on the right hand side of the Toolkit, check the checkbox under Agreement which will then enable the Re-lock button, click that (DO NOT CLICK S-On), Your phone will reboot to Android, Once back, click the Bootloader button again Under Basic ADB. This time instead of Unlocked, it will say Relocked. Now try running the RUU again, this time it should work.
Once the RUU flash is done, you should be all set to get going again.
Click to expand...
Click to collapse
Sorry for answering a bit late, but i had exams. Anyway i found some instructions here and i've followed the instructions but i've been stuck at step 10
for the last hour it's been looking like this...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
what is it that i'm doing wrong here?
Edit: i kept retrying the steps and i got a bit further, but now after i type fastboot flash zip firmware.zip i get this fail
TM-87 said:
Sorry for answering a bit late, but i had exams. Anyway i found some instructions here and i've followed the instructions but i've been stuck at step 10
for the last hour it's been looking like this...
what is it that i'm doing wrong here?
Edit: i kept retrying the steps and i got a bit further, but now after i type fastboot flash zip firmware.zip i get this fail
Click to expand...
Click to collapse
that's normal you have to issue "fastboot flash zip firmware.zip" twice!
so now IMMEDIATELY do it again, DO NOT REBOOT
the second flash should come back with success
nkk71 said:
that's normal you have to issue "fastboot flash zip firmware.zip" twice!
so now IMMEDIATELY do it again, DO NOT REBOOT
the second flash should come back with success
Click to expand...
Click to collapse
Ok i've tried doing fastboot flash zip firmware.zip again, but now i get this message
I have retried making this file again by redownloading everything, but i keep getting this unkown error...
TM-87 said:
Ok i've tried doing fastboot flash zip firmware.zip again, but now i get this message
I have retried making this file again by redownloading everything, but i keep getting this unkown error...
Click to expand...
Click to collapse
"cannot load" just means the filename (ie "firmware.zip") is wrong. check your folder for the correct name.
nkk71 said:
"cannot load" just means the filename (ie "firmware.zip") is wrong. check your folder for the correct name.
Click to expand...
Click to collapse
Thanks that worked, i've run the fastboot flash zip firmware.zip twice now and it worked both times. atleast that's what it said, when i rebooted the phone i still had superSU isn't that stuff supposed to be gone?
TM-87 said:
Thanks that worked, i've run the fastboot flash zip firmware.zip twice now and it worked both times. atleast that's what it said, when i rebooted the phone i still had superSU isn't that stuff supposed to be gone?
Click to expand...
Click to collapse
Nope, superSU should still be there. You only upgraded firmware, nothing to do with ROM or SU.
Sent from my HTC One using Tapatalk
nkk71 said:
Nope, superSU should still be there. You only upgraded firmware, nothing to do with ROM or SU.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
.... So then ... how do i unroot / return to stock i followed instructions on youtube and they said i needed the RUU file so that's when i stumbled onto this problem and now that i've found the solution ... i still have no idea how to get rid of the twrp and superSU off my phone ....
I just want to return the phone back to how i bought it, since after the rooting thing i couldn't update since it would just return to twrp when trying to instal the update....
TM-87 said:
.... So then ... how do i unroot / return to stock i followed instructions on youtube and they said i needed the RUU file so that's when i stumbled onto this problem and now that i've found the solution ... i still have no idea how to get rid of the twrp and superSU off my phone ....
I just want to return the phone back to how i bought it, since after the rooting thing i couldn't update since it would just return to twrp when trying to instal the update....
Click to expand...
Click to collapse
It's not the root preventing the update from what I can tell. What you need is to flash stock recovery over twrp
Sent from my HTC One
gusto5 said:
It's not the root preventing the update from what I can tell. What you need is to flash stock recovery over twrp
Sent from my HTC One
Click to expand...
Click to collapse
So i need to put this RUU.zip onto my phone and flash it via twrp?
TM-87 said:
So i need to put this RUU.zip onto my phone and flash it via twrp?
Click to expand...
Click to collapse
Sorry mate, kind a lost track of what you want to achieve. Can you please explain.
Also post a "fastboot getvar all" (remove IMEI and s/n before posting)
nkk71 said:
Sorry mate, kind a lost track of what you want to achieve. Can you please explain.
Also post a "fastboot getvar all" (remove IMEI and s/n before posting)
Click to expand...
Click to collapse
Again sorry for the late reply, still busy with my exams. Anyway, what i want to do is return the phone back like before i rooted the phone/ remove twrp, superSu and all that. Right now i can't update my phone and i'm still on JB 4.1. Each time i try to download and instal the update it keeps going to twrp.
Here's my "fastboot getvar all"
Bump
no one knows a solution?
TM-87 said:
no one knows a solution?
Click to expand...
Click to collapse
You probably need to get S-Off, if you want to go back to 100% stock. whats the date of your bootloader?
nkk71 said:
You probably need to get S-Off, if you want to go back to 100% stock. whats the date of your bootloader?
Click to expand...
Click to collapse
Where does it show the date of the bootloader?
TM-87 said:
Where does it show the date of the bootloader?
Click to expand...
Click to collapse
in bootloader , the attached screen, we need to see if you are patched 1.44 hboot or unpatched; unpatched will be dated before June 2013
Hi guys,
I got a second hand HTC One M8 Sprint and can keep it if I make it work. I spent the whole night reading forums and trying to flash custom ROMs but end up stuck in bootloader. Is it "just" soft bricked and I need to flash the RUU? I only tried flashing ROMs (ARHD,Viper,BadBoyz,ICE), I'm scared I might give him the final blow if I mess up the firmware.
I would appreciate it if somebody can help me fix the phone (and reward you with beer money to say thanks)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
My Friend Just got one in the same condition from the Craiglist and her's was NOT S-OFF so your good to go.
FYI ((((( In order the flash the stock RUU it has to be RELOCKED )))))
I would recommend TWRP 3.0 at least for recovery.
I have used Philz in the past with my older phones and its worked well but Now I use TWRP because the text is so small its hard to see at times and I seem to touch the wrong thing on the list.
Maybe its my age catching up to me but Me personally like the TWRP because it user and touch friendly Recovery.
I would also recommend using the ((( Hasoon2000's HTC One 2014 (M8) All-in-one Toolkit )))
I have used the Squabbi's HTC One (M8) Toolkit- 2.0.0.1 and had many problems with it. ( Screen Freeze,Program lockup, adb commands NOT working, output token Not good,side load did not work for me either so I only had one choice was to try the older software and terminal window OLD SCHOOL WAY took me longer but in the end the older software worked.
Please I do NOT knock someone's else's software because I am sure it works well for most people it just did not work for me.
These guys on here put a lot of time and effort into there software and many of them only get money from donations but others use advertisements
I have been here from the very beginning of XDA but never really contributed in the past but am doing a little more now to help others if I can.
The problem with the new software maybe my machine i am running Windows 7 Pro 64Bit 24gigRam/Samsung240 SSD
Dale
Thank you Dale for the quick and kind reply. I sent you a PM, please take a look when you get the time.
If somebody here could guide me through the steps of fixing it via Skype, I would return the favor with a paypal donation. Thank you in advance
@zxhwk are you sure the phone has to be relocked in order to flash RUU? I know that s-off makes that irrelevant on other HTC phones, so that could be the case with M8 too
dey tuuk ur juurbs
Ohh Donkeykong, second reply pa vec netko od nasih Imas li ti mozda vremena i volje pomoci mi da sredim mob? (writing in Croatian)
DemesHTC said:
Ohh Donkeykong, second reply pa vec netko od nasih Imas li ti mozda vremena i volje pomoci mi da sredim mob? (writing in Croatian)
Click to expand...
Click to collapse
PMed [emoji6]
dey tuuk ur juurbs
donkeykong1 said:
@zxhwk are you sure the phone has to be relocked in order to flash RUU? I know that s-off makes that irrelevant on other HTC phones, so that could be the case with M8 too
dey tuuk ur juurbs
Click to expand...
Click to collapse
Yes POSITIVE it has to be RELOCKED in order to run the stock RUU
I still have all the original Stock RUU KitKat in my archives and even the original BadBoyz Rom Version 1
---------- Post added at 01:43 PM ---------- Previous post was at 01:32 PM ----------
DemesHTC said:
Thank you Dale for the quick and kind reply. I sent you a PM, please take a look when you get the time.
If somebody here could guide me through the steps of fixing it via Skype, I would return the favor with a paypal donation. Thank you in advance
Click to expand...
Click to collapse
In the mode you have right now its easy to flash it
All you have to do is COPY the ROM you would like on the phone to a Micro SD card and then place sd card in phone and boot into recovery mode .
Then do a complete wipe of everything including internal storage so you can do a CLEAN flash.
After wipe use back button to go back to main screen and choose INSTALL ZIP ( make sure you choose external SDCARD ) where you put the Rom and choose it and follow instructions on screen when done and all worked well it will ask to reboot .
If it did NOT work it will tell you that there is NO OS so you will have to try againif still Not working then relock and run the STOCK RUU and from that point its pretty easy to do connect phone to PC and connect to HTC site and get NEW TOKEN STRING and unlock bootloader again and then flash new recovery then choose rom you like.
There are many threads here that show you step by step on how to flash from a stock phone. But your in a much better position than a stock one Most of the work has already been done for you just a simple flash is all you have to do as I have stated earlier in the post.
PSSSSSSSSSSSS: MAKE SURE YOU HAVE POWER CONNECTED TO PHONE and BATTERY IS at LEAST 50 % before FLASHING
Dale
At the risk of sounding rude - you're wrong about relocking bootloader with s-off for RUU flashing. You need to relock the bootloader only if your phone is s-on. For s-off it doesn't matter
http://venomroms.com/ruu/
This proves I'm right
dey tuuk ur juurbs
donkeykong1 said:
At the risk of sounding rude - you're wrong about relocking bootloader with s-off for RUU flashing. You need to relock the bootloader only if your phone is s-on. For s-off it doesn't matter
http://venomroms.com/ruu/
This proves I'm right
dey tuuk ur juurbs
Click to expand...
Click to collapse
I never mentioned about having the S-OFF or ON while flashing the STOCK RUU just the BootLoader has to be RELOCKED so I do not know where you get that from
This is one of the main reasons I have NOT helped very many people on the forum because people assume things in the postings and try and prove a point or something while they ask for your help on the other hand. As stated in this posting I NEVER mentioned anything about FLASHING while having (( S-OFF or S-ON )) Just RELOCKING BOOTLOADER so have a NICE day I will fade bad out again like I was before. First time I try and help this is what happens ( No Thank You )
zxhwk said:
I never mentioned about having the S-OFF or ON while flashing the STOCK RUU just the BootLoader has to be RELOCKED so I do not know where you get that from
Click to expand...
Click to collapse
OK. I thought you will think I'm rude. Thing is - his phone is s-off, and he can flash ay kind of RUU without locking or relocking his bootloader. That means he can even flash unsigned RUUs and downgrade his firmware which is not possible with s-on. If security flag is on, i.e. s-on then, and only then you need to relock bootloader in order to flash RUU, and you can flash only signed RUUs, and you can't downgrade your firmware. You got some things mixed up, sorry
dey tuuk ur juurbs
donkeykong1 said:
OK. I thought you will think I'm rude. Thing is - his phone is s-off, and he can flash ay kind of RUU without locking or relocking his bootloader. That means he can even flash unsigned RUUs and downgrade his firmware which is not possible with s-on. If security flag is on, i.e. s-on then, and only then you need to relock bootloader in order to flash RUU, and you can flash only signed RUUs, and you can't downgrade your firmware. You got some things mixed up, sorry
dey tuuk ur juurbs
Click to expand...
Click to collapse
Go ahead and take over I am telling you it will NOT FLASH STOCK RUU when BOOTLOADER is UNLOCKED S-off or S-on has no bearings on flashing. except the Radio
I was just trying to help I am NOT here to tell anyone about the simple things they should already know like the Signed RUU downgrading and such.
If they are willing to flash a phone then I am sure they have read all of this and should not have to spell those simple things out that is COMMON SENSE
zxhwk said:
Go ahead and take over I am telling you it will NOT FLASH STOCK RUU when BOOTLOADER is UNLOCKED S-off or S-on has no bearings on flashing. except the Radio
Click to expand...
Click to collapse
I thought I was rude, but you take the flag my friend.
Over and out
dey tuuk ur juurbs
OP if you are trying to use one of the last 2-3 RUU's you will need to flash the matching firmware first then the RUU should run fine.
Try installing any of the roms you tried with TWRP v3, make sure you wipe Data partition (cache and dalvik should wipe with rom install)
Flash the recovery from the bootloader
I'm also curious why the release date shows 27 Jan on bootloader(it should say 7 Jan unless I used the wrong ruu), what firmware did you flash ?
Thank you guys for the replies and useful tips, I'm currently in touch with @donkeykong1 and we are working on it. I will keep you updated and post the solution once we fix it, so anybody else with the same problem can find it in the future.
@Vcek - I didn't flash any firmware myself, I got it already bricked and just tried flashing ROMs ((ARHD,Viper,BadBoyz,ICE). It run the instalation, but after it was all done and the phone rebooted it still was stuck in the bootloader (I even left it 30min alone since I read somewhere that it might take longer to boot after flashing the ROM).
@Sloth @zxhwk - Thank you for the tips guys, I hope we will figure it out and flash that bastard
SOLUTION: We flashed the RUU over fastboot with UNLOCKED bootloader and the phone is working again!
Thank you all for your help and I hope this thread will help save more bricked phones in the future
zxhwk said:
My Friend Just got one in the same condition from the Craiglist and her's was NOT S-OFF so your good to go.
FYI ((((( In order the flash the stock RUU it has to be RELOCKED )))))
I would recommend TWRP 3.0 at least for recovery.
I have used Philz in the past with my older phones and its worked well but Now I use TWRP because the text is so small its hard to see at times and I seem to touch the wrong thing on the list.
Maybe its my age catching up to me but Me personally like the TWRP because it user and touch friendly Recovery.
I would also recommend using the ((( Hasoon2000's HTC One 2014 (M8) All-in-one Toolkit )))
I have used the Squabbi's HTC One (M8) Toolkit- 2.0.0.1 and had many problems with it. ( Screen Freeze,Program lockup, adb commands NOT working, output token Not good,side load did not work for me either so I only had one choice was to try the older software and terminal window OLD SCHOOL WAY took me longer but in the end the older software worked.
Please I do NOT knock someone's else's software because I am sure it works well for most people it just did not work for me.
These guys on here put a lot of time and effort into there software and many of them only get money from donations but others use advertisements
I have been here from the very beginning of XDA but never really contributed in the past but am doing a little more now to help others if I can.
The problem with the new software maybe my machine i am running Windows 7 Pro 64Bit 24gigRam/Samsung240 SSD
Dale
Click to expand...
Click to collapse
BTW, an s-off phone does NOT need to be locked to flash an ruu. Only an s-on phone needs that done. I probably a couple dozen ruu (stock and custom) threads posted on xda.
The newer phones even allow a s-off but locked phone to flash recovery directly without any tricks. (M8 s-off but locked requires an ruu mode zip)
BTW, your friend with the s-on phone...if you can't get it sorted I have a Java card that can s-off any HTC phone.
Sent from my SM-T810 using Tapatalk
Hi there this is my first post so excuse me if i'm unclear about stuff. if you need any info just gimme a shout and i can find it for you!
I have an M7 on O2 (UK), I've had it pretty much since it release in 2013.
Upon getting the phone i immediately rooted whilst on Android Version 4.4.3, it's the Sense Version too (i don't know if that's relevant or not).
Anyway it's been a while since this, and i've lost a lot of the knowledge i had on Android & Rooting etc.
I'm looking to un-root my phone to get the OTA Updates which have been alerting my (very annoying) since 2013!
Last week i began watching tutorials and reading up, a few days in and i gave it my first attempt..
I first re-locked my Bootloader successfully and then tried using the RUU Software but was unlucky with numerous versions (i'm still unsure about how to find the RIGHT one). After hours & hours i was at and end and couldnt seem to find the right one for my phone and i gave up.
Since "re-locking" my Bootloader i've been facing an issue where every time i power up or restart my phone it boots in the Bootloader's Fastboot mode, from here i have to navigate to 'reboot'... the phone then restarts and this time round i get my usual home screen.
I'm unsure as to what direction to go now as i'm scared i will brick my phone, i guess i have 2 options;
A. Continue to try and return to stock and then decide if i wish to re-root (probably not)
B. Unlock the Bootloader once again (only this will wipe my phone, and i can't find the original stock rom thus leading to a brick i expect?)
Hope someone can help, any questions please do not hesitate to ask!
gemodubz said:
Hi there this is my first post so excuse me if i'm unclear about stuff. if you need any info just gimme a shout and i can find it for you!
I have an M7 on O2 (UK), I've had it pretty much since it release in 2013.
Upon getting the phone i immediately rooted whilst on Android Version 4.4.3, it's the Sense Version too (i don't know if that's relevant or not).
Anyway it's been a while since this, and i've lost a lot of the knowledge i had on Android & Rooting etc.
I'm looking to un-root my phone to get the OTA Updates which have been alerting my (very annoying) since 2013!
Last week i began watching tutorials and reading up, a few days in and i gave it my first attempt..
I first re-locked my Bootloader successfully and then tried using the RUU Software but was unlucky with numerous versions (i'm still unsure about how to find the RIGHT one). After hours & hours i was at and end and couldnt seem to find the right one for my phone and i gave up.
Since "re-locking" my Bootloader i've been facing an issue where every time i power up or restart my phone it boots in the Bootloader's Fastboot mode, from here i have to navigate to 'reboot'... the phone then restarts and this time round i get my usual home screen.
I'm unsure as to what direction to go now as i'm scared i will brick my phone, i guess i have 2 options;
A. Continue to try and return to stock and then decide if i wish to re-root (probably not)
B. Unlock the Bootloader once again (only this will wipe my phone, and i can't find the original stock rom thus leading to a brick i expect?)
Hope someone can help, any questions please do not hesitate to ask!
you can also contact me here [email protected]
Click to expand...
Click to collapse
Post the output of "fastboot getvar all" (hide your imei and sn)
alray said:
Post the output of "fastboot getvar all" (hide your imei and sn)
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
gemodubz said:
Click to expand...
Click to collapse
If you want to return to stock, you can use the 7.18.206.51 ruu (its the latest version for your phone)
Instructions as post #1, ruu at post #2:
http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
Once the RUU flashed you can unlock the bootloader again and re-root. Be sure to use the latest version of supersu.
alray said:
If you want to return to stock, you can use the 7.18.206.51 ruu (its the latest version for your phone)
Instructions as post #1, ruu at post #2:
http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
Once the RUU flashed you can unlock the bootloader again and re-root. Be sure to use the latest version of supersu.
Click to expand...
Click to collapse
Thanks a bunch man! Please could you tell me how you found the specific RUU for my phone?
Please could you tell me the method you used to locate the RUU as i had so much trouble before, i was wondering if there is an easy way find the correct RUU (by looking for certain codes etc) ?
alray said:
If you want to return to stock, you can use the 7.18.206.51 ruu (its the latest version for your phone)
Instructions as post #1, ruu at post #2:
http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
Once the RUU flashed you can unlock the bootloader again and re-root. Be sure to use the latest version of supersu.
Click to expand...
Click to collapse
won't unlocking the bootloader after flashing RUU just wipe the phone again?
gemodubz said:
won't unlocking the bootloader after flashing RUU just wipe the phone again?
Click to expand...
Click to collapse
Unlocking will wipe user data only.
Sent from my HTC One using XDA Labs
alray said:
Unlocking will wipe user data only.
Sent from my HTC One using XDA Labs
Click to expand...
Click to collapse
So would that be my media files like photos, music, apps etc?
gemodubz said:
So would that be my media files like photos, music, apps etc?
Click to expand...
Click to collapse
Exactly
Sent from my HTC One using XDA Labs