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.
Related
I have successfully custom flashed Sense 3.0 with 2.3 gingerbread for my incredible S phone. It only took 3 long days. I am very happy but what now? I want this to be my permanent ROM. Is there anything else that I am recommended to do now? I was reading about how you can make your phone almost like a stock phone meaning S-OFF and Unroot. Not too sure if that is necessary. What do you guys think?
please provide more info..
what Custom Rom are you on and how did you flash Sense 3.0.
there's a lot of threads hear and your initial details really don't provide much useful information.
I am on Virtuous Unity 1.27.0 Sense 3.0 based on Pyramid, I flashed it through 4EXTRecovery_v2.1.0_RC1_vivo.
I also had to flash a radio file to my ROM afterwards. I did that through the SDK software. Instructions from here: http://wiki.cyanogenmod.com/wiki/HTC_Incredible_S:_FAQ Here is a list of Radio files for your specific provider/region : http://forum.xda-developers.com/showpost.php?p=12870734&postcount=1
I S-OFF'd my phone through Alpha RevX..there is also a you tube tutorial on how to do it. If anyone has anymore questions on how to do it then msg me!
So now what is left to do?????? Any other procedures? Besides flashing more Roms!
saying the custom rom, radio, cwm would have been enough information. anyways i see that you're new so it's all good.
so the question is, What do you want to do with your phone. after customizing it, are you okay with performance? no bugs? What do YOU want to do with your phone?
I want to permanantly make it my OS. Is that possible? I posted all of that because when I was figuring out how to do this I found that other peoples solutions helped me out alot tee hee
guys I think this belongs in "General"
IncredibleSlover said:
I want to permanantly make it my OS. Is that possible? I posted all of that because when I was figuring out how to do this I found that other peoples solutions helped me out alot tee hee
Click to expand...
Click to collapse
What do you mean 'permanently make it my OS'? That ROM will stay on your phone as long as you want it, until you decide you want to flash a different one. There's no need to go trying to lock it down again after flashing it, that's a pointless exercise.
Dude you're S-OFF and rooted now, there is nothing else to do other than installing custom ROMs or flashing radios(if needed) Virtious Unity is now your ROM, if you want to revert back to what the phone came with, you will need to flash a official RUU.
Awesome thanks for the reply
hussainmushahid said:
Dude you're S-OFF and rooted now, there is nothing else to do other than installing custom ROMs or flashing radios(if needed) Virtious Unity is now your ROM, if you want to revert back to what the phone came with, you will need to flash a official RUU.
Click to expand...
Click to collapse
Hi, I need the S-ON. everywhere let me just advise'll update RUU, but I did and I still have the S-OFF. You know how to solve it? I need back guarantee.
thank you very much.
exnerjan said:
Hi, I need the S-ON. everywhere let me just advise'll update RUU, but I did and I still have the S-OFF. You know how to solve it? I need back guarantee.
thank you very much.
Click to expand...
Click to collapse
you need to go S-ON again? you used alpharevx? If so, just flash the whole official RUU and you will be S-ON again since it would also flash the bootloader.
hussainmushahid said:
you need to go S-ON again? you used alpharevx? If so, just flash the whole official RUU and you will be S-ON again since it would also flash the bootloader.
Click to expand...
Click to collapse
That is a common misconception. Apparently AlphaRevX's HBOOT prevents a RUU from overwriting it. There have been several posts about running an RUU on an AlphaRevX S-OFF IncS and the ROM does indeed update, but the device is still S-OFF and AlphaRevX HBOOT is still in place.
doctorsax said:
What do you mean 'permanently make it my OS'? That ROM will stay on your phone as long as you want it, until you decide you want to flash a different one. There's no need to go trying to lock it down again after flashing it, that's a pointless exercise.
Click to expand...
Click to collapse
Awesome man, thats what I wanted to hear
hussainmushahid said:
Dude you're S-OFF and rooted now, there is nothing else to do other than installing custom ROMs or flashing radios(if needed) Virtious Unity is now your ROM, if you want to revert back to what the phone came with, you will need to flash a official RUU.
Click to expand...
Click to collapse
You mean I wont be able to recover my old settings if I have restored it?
I dont care really if I cant. Is it because I am now 2.3 gingerbread????
Well it doesnt matter because I love this new ROM and will be keeping it forever
uh oh this is bad. no more warranty for my phone :s
tpbklake said:
That is a common misconception. Apparently AlphaRevX's HBOOT prevents a RUU from overwriting it. There have been several posts about running an RUU on an AlphaRevX S-OFF IncS and the ROM does indeed update, but the device is still S-OFF and AlphaRevX HBOOT is still in place.
Click to expand...
Click to collapse
and know how to do it to the S-ON? Please.
tpbklake said:
That is a common misconception. Apparently AlphaRevX's HBOOT prevents a RUU from overwriting it. There have been several posts about running an RUU on an AlphaRevX S-OFF IncS and the ROM does indeed update, but the device is still S-OFF and AlphaRevX HBOOT is still in place.
Click to expand...
Click to collapse
I haven't tried it myself so I guess you're true, when I flashed the stock RUU I flashed it without the bootloader file (unzip,delete,zip) as stated in a thread regarding keeping S-OFF when installing stock RUU. A guy has found the solution to going S-ON again in his thread in the general discussion section.
hussainmushahid said:
I haven't tried it myself so I guess you're true, when I flashed the stock RUU I flashed it without the bootloader file (unzip,delete,zip) as stated in a thread regarding keeping S-OFF when installing stock RUU. A guy has found the solution to going S-ON again in his thread in the general discussion section.
Click to expand...
Click to collapse
Yes I saw that this morning. Basically AlphaRevX has a special HBOOT you can 'downgrade' with that you must flash and then using the special HBOOT you can flash an official HTC HBOOT. End result is S-OFF and you have a standard HTC HBOOT.
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
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
Hello, I have unlocked, rooted and changed the CCID of my HTC one phone, but a message now appears during the boot process. It appears in red writing under the HTC logo, any ideas how I could removed it. I have used the search function, but I am having a mare of a day, and cant seem to find the answer, so I do apologise if this has been posted before.
the text says
"This build is for development purposes only. Do not distribute outside of HTC without HTC's written permission. Failure to do so may lead to legal action"
I used the unlock guide in this forum.
Sorry if this a stupid question.
You need to be S-OFF I believe
JamDonot said:
Hello, I have unlocked, rooted and changed the CCID of my HTC one phone, but a message now appears during the boot process. It appears in red writing under the HTC logo, any ideas how I could removed it. I have used the search function, but I am having a mare of a day, and cant seem to find the answer, so I do apologise if this has been posted before.
the text says
"This build is for development purposes only. Do not distribute outside of HTC without HTC's written permission. Failure to do so may lead to legal action"
I used the unlock guide in this forum.
Sorry if this a stupid question.
Click to expand...
Click to collapse
Im not sure but with latest firmware..this message doesnt show up
You are getting the message because you unlocked your bootloader.
bigdaddy619 said:
You are getting the message because you unlocked your bootloader.
Click to expand...
Click to collapse
Hello, I have s-offed, and removed the tampered message. I take it that message will always appear and there is no way to remove it?
EddyOS said:
You need to be S-OFF I believe
Click to expand...
Click to collapse
No even i have S-OFF One..had this message when i am on stock hboot (1.44)
later after upgrading to hboot 1.54,it disappered it seems
JamDonot said:
Hello, I have s-offed, and removed the tampered message. I take it that message will always appear and there is no way to remove it?
Click to expand...
Click to collapse
You can remove it with a hex edited hboot or with the Moonshine hboot
Just be careful to flash the correct hboot
bigdaddy619 said:
You can remove it with a hex edited hboot or with the Moonshine hboot
Just be careful to flash the correct hboot
Click to expand...
Click to collapse
Yeah, I got confused with what revone removes and that message on the splash isn't that - thanks for correcting me
Harish_Kumar said:
No even i have S-OFF One..had this message when i am on stock hboot (1.44)
later after upgrading to hboot 1.54,it disappered it seems
Click to expand...
Click to collapse
Sorry for the noob question, but its been a while since I modded my phone, been running a nexus 4 for a bit playing with it. Is there a simple procedure to upgrade the hboot.
JamDonot said:
Sorry for the noob question, but its been a while since I modded my phone, been running a nexus 4 for a bit playing with it. Is there a simple procedure to upgrade the hboot.
Click to expand...
Click to collapse
With S-OFF you can flash hboot in RUU mode
find your appropriate hboot and flash it
use these commands
adb reboot bootloader
fastboot oem rebootRUU
fastboot flash zip hbootfilename.zip
fastboot reboot
JamDonot said:
Sorry for the noob question, but its been a while since I modded my phone, been running a nexus 4 for a bit playing with it. Is there a simple procedure to upgrade the hboot.
Click to expand...
Click to collapse
It's not a good idea to update your hboot
Why you ask? Because HTC adds patches to them which may or may not be something we want.
Harish_Kumar said:
With S-OFF you can flash hboot in RUU mode
find your appropriate hboot and flash it
use these commands
adb reboot bootloader
fastboot oem rebootRUU
fastboot flash zip hbootfilename.zip
fastboot reboot
Click to expand...
Click to collapse
Thank you for your amazing replies, most helpful. Can I ask one final question, and again I apologise for the noobness of it, where do I go about locating the correct hboot for my phone.
JamDonot said:
Thank you for your amazing replies, most helpful. Can I ask one final question, and again I apologise for the noobness of it, where do I go about locating the correct hboot for my phone.
Click to expand...
Click to collapse
I think they will be in the "Android Development Section" i am not sure though
Anyways why are you so concerned about this message? as someone is suggesting its not safe to flash hboot..better avoid doing it
If you get back to completely stock by flashing RUU..this messsage will automatically disappear
hey yall I been searching and reading all forums on going back to stock. theres only regular sprint htc m8 version and nothing on the hk edition so I can get the new ota and remain on stock. ive lost my back up file when I upload a custom rom. ive tried a bunch of things like using ruu and that but kept getting an error like a 32 and a 99. I cant get the s-on to turn off to get more. idk if im doing something wrong or what but im hoping someone can shine some light this way and help me out. yes I tired the sunshine apk but it pops up need based rom etc. so.........
You have to relock to use an RUU when you're still S-ON, and you must make sure that you're using an HK RUU.
Captain_Throwback said:
You have to relock to use an RUU when you're still S-ON, and you must make sure that you're using an HK RUU.
Click to expand...
Click to collapse
not to seem stupid but this is a learning process for me coming from iphone to android. so when u say relock u mean bootloader? n do I need to have original recovery. and when I do the ruu im using fastboot it wont cuz me to have an error again right?
Jeffymclovin said:
not to seem stupid but this is a learning process for me coming from iphone to android. so when u say relock u mean bootloader? n do I need to have original recovery. and when I do the ruu im using fastboot it wont cuz me to have an error again right?
Click to expand...
Click to collapse
Yes, relock the bootloader (fastboot oem lock). That'll prevent the error 92 or whichever it was. It doesn't matter what recovery is on there, as the RUU will overwrite it with stock.
Captain_Throwback said:
Yes, relock the bootloader (fastboot oem lock). That'll prevent the error 92 or whichever it was. It doesn't matter what recovery is on there, as the RUU will overwrite it with stock.
Click to expand...
Click to collapse
ok im gonna give that a try right now
Captain_Throwback said:
Yes, relock the bootloader (fastboot oem lock). That'll prevent the error 92 or whichever it was. It doesn't matter what recovery is on there, as the RUU will overwrite it with stock.
Click to expand...
Click to collapse
ok I relocked the bootloader and fastboot the Sprint_HTC_One_M8_Harman_2.16.654.4_RUU it still wouldn't let me go any further {failed<remote: 12 signature verify fail>} is what I got
Jeffymclovin said:
ok I relocked the bootloader and fastboot the Sprint_HTC_One_M8_Harman_2.16.654.4_RUU it still wouldn't let me go any further {failed<remote: 12 signature verify fail>} is what I got
Click to expand...
Click to collapse
Did you review the instructions on how to flash it? I believe you extract the 0P6BIMG.zip from the larger zip file, and put it on your external SD.
Captain_Throwback said:
Did you review the instructions on how to flash it? I believe you extract the 0P6BIMG.zip from the larger zip file, and put it on your external SD.
Click to expand...
Click to collapse
yea it would kinda help if I read the instructions the right way lol I finally got it back to normal I greatly appreciate it my man but do got one more thing tho the s-on am I able to use firewater to get it off now or use sunshine apk cuz I was also having issues with that too
Jeffymclovin said:
yea it would kinda help if I read the instructions the right way lol I finally got it back to normal I greatly appreciate it my man but do got one more thing tho the s-on am I able to use firewater to get it off now or use sunshine apk cuz I was also having issues with that too
Click to expand...
Click to collapse
You can try Firewater, but most likely you'll need to use SunShine.