[buttrrfly s]soff and unlocked suddenly lost - HTC Butterfly S

Well, I am stuck in such a weird situation now.
I used Rom Manager yesterday to try to install cwm recovery and failed to make any change. After doing it, I entered boatloader (I was originally s off and unlocked), and found that it has become s-on and locked. And I found another strange thing happened at the same time, although the security lock was seemed to be locked back. I still could overwrite my cid become supersid(I used "fastboot own readcid" and confirmed this), but can't do anything like flashing hboot or custom recovery...... until I unlock boatloader via HTC dev than I could flash recovery again. And I found that when I command "fastboot oem readsecureflag" , I suggested "secure_flag:0"(s off) but not "secure_flag:3"
And firewater s off is not useable for me. It will pop out "there isn't helluva....."
With hboot1.55 rumrunner is not useable for me either
Plz help me by these problems, thanks a lot

Related

[Q] [UPDATE WITH SOLUTION] RUU 155 Error with HTC ONE Developer Edition

I am having an issue that I have not seen before and could not find any resolve thru XDA or Google. I am attempting to restore the 64G Developer Edition with the RUU from HTC Dev and I keep getting the 155 error. I even have attempted to install thru CWM the .zip. Still no avail.
I am currently rooted, and have CWM installed. The device is obviously Bootloader unlock. What I was able to find is that it possibly could be a issue that it is bootloader unlocked as some posts suggest to have you bootloader locked to install RUU, but that is obviosely not a posibility with the dev ed.
So what am I doing wrong, or what is the issue. I have confirmed that I was using the correct RUU.
Help Appreciated
UPDATE
Ok, I figured out how to avoid the RUU 155 error. It seems that HTC for some dumb reason, although for a unlocked developer edition, we still have to lock the bootloader to utilize the RUU. Here are the steps I have done.
Although it is straight forward and easy to do, issues could always arise. I do not take any responsibility if things go wrong. Educate yourself first before attempting anything. If you do not know what you are doing, then don't do it.
Before Starting.
Make sure you have the latest HTC Drivers. You can use hasoon2000 HTC All-In-One Toolkit to complete that. That can be found at HTC One All-In-One Toolkit
Get the appropriate RUU from HTC Dev
1. Lock your bootloader through by booting into hoot and then going into fastboot and issuing the command fasboot oem lock.
2. Once locked, reboot your system.
3. Open RUU and follow onscreen instructions.
Notice, this will delete all of the files on the system so do this on your own cognition
4. Let the RUU do its thing. If you get an error during the process, such as 152, simply try again. I had it happen once. The phone was stuck on the black HTC screen with four triangles with exclamation points in each corner. If this happens you will not be able to reboot your phone. Simply relaunch RUU and it should reinstall it. If you get error 155 again, then you have not re-locked your bootloader.
3.Once you have successfully reinstalled the rom, you have to register with the HTC Dev to re-unlock your bootloader if that is what you want. The easiest to do this I found was by using the HTC One All-In-One Toolkit. It is a great tool and will help you with majority of things that I have mentioned above, including locking your bootloader. Follow the steps on the toolkit and you'll be all set. The Toolkit can be found here HTC One All-In-One Toolkit
If you found this helpful, click thanks. Also hit thanks to hasoon2000 for creating the toolkit.
Gotta re lock your bootloader
fastboot oem lock
I got relock it even though it came unlocked? How would I unlock it again since I don't have the tokens from HTC development, or is the ruu gonna do that by itself.
Sent from my HTC One using Tapatalk 2
I was having same issues as OP. After using the lock command, the update got longer. The black HTC screen even got as far as a progress bar. Well I now got ERROR 152 saying I should get the correct RUU. I am sure I have the right one, because there is only ONE developer edition RUU file from htcdev.com
Problem now is, I have the black HTC screen with warning signs on each corner.
One thing I saw on a video is you are supposed to restore to the same version? I had updated OTA Z(1.29.1540.16) to the latest which I cant get an RUU for. The RUU available is 1.29.1540.3 no other available. What do I do now? HTC One Dev Edition stuck on black screen with warning signs on all corners.
All I can see now is a scren that says:
***TAMPERED***
***RELOCKED***
bunch of numbers and letters in green and
RUU in orange
schn1tt3r said:
I was having same issues as OP. After using the lock command, the update got longer. The black HTC screen even got as far as a progress bar. Well I now got ERROR 152 saying I should get the correct RUU. I am sure I have the right one, because there is only ONE developer edition RUU file from htcdev.com
Problem now is, I have the black HTC screen with warning signs on each corner.
One thing I saw on a video is you are supposed to restore to the same version? I had updated OTA to the latest which I cant get an RUU for. What do I do now? HTC One Dev Edition stuck on black screen with warning signs on all corners.
Click to expand...
Click to collapse
When I was doing it, the first time I got the 152 error. I simply just redid it and it accepted it on the second try. Trying relaunching RUU that you have and try the install again. That's at least how it worked with me.
Bosnazmaj said:
When I was doing it, the first time I got the 152 error. I simply just redid it and it accepted it on the second try. Trying relaunching RUU that you have and try the install again. That's at least how it worked with me.
Click to expand...
Click to collapse
Did you get that black HTC screen with warning signs on each corner? I am re-running the RUU, hope it works or I just lost $650.
EDIT: You used RUU_M7_UL_JB_50_BrightstarUS_WWE_1.29.1540.3.exe right? Were you already OTA updated? I wonder why htcdev web says BrightstarUS for the dev edition instead of something else...
EDIT2: Its on that black screen with loading thing again... still exclamation marks on every corner... hope this works or else it won't be a nice first experience with Android coming from iOS lol and I've jailbroken and tinkered on those devices for so long.
---------- Post added at 08:31 PM ---------- Previous post was at 08:21 PM ----------
Yeah 2nd attempt the same error 152. I just lost $650 right?
The green bar goes all the way to the end, it sends it all, but it doesnt reboot. It just gets error. What else can I try? Device isnt even 3 days old.
Did it a third time, after Updating Radio, thats where the error appears.
schn1tt3r said:
Did you get that black HTC screen with warning signs on each corner? I am re-running the RUU, hope it works or I just lost $650.
EDIT: You used RUU_M7_UL_JB_50_BrightstarUS_WWE_1.29.1540.3.exe right? Were you already OTA updated? I wonder why htcdev web says BrightstarUS for the dev edition instead of something else...
EDIT2: Its on that black screen with loading thing again... still exclamation marks on every corner... hope this works or else it won't be a nice first experience with Android coming from iOS lol and I've jailbroken and tinkered on those devices for so long.
---------- Post added at 08:31 PM ---------- Previous post was at 08:21 PM ----------
Yeah 2nd attempt the same error 152. I just lost $650 right?
The green bar goes all the way to the end, it sends it all, but it doesnt reboot. It just gets error. What else can I try? Device isnt even 3 days old.
Did it a third time, after Updating Radio, thats where the error appears.
Click to expand...
Click to collapse
What was the software version that it came with. Was it with the most recent one? I think 1.29.401.16 one?
Bosnazmaj said:
What was the software version that it came with. Was it with the most recent one? I think 1.29.401.16 one?
Click to expand...
Click to collapse
It came with the .3 and I did OTA to .16
The RUU you can get online from their web is only .3
===============================
Ok so... that black HTC screen accepts "fastboot" commands.
I downloaded the .ZIP version of the Developer Edition OS.
I went in command prompt, I typed
fastboot reboot-bootloader
fastboot oem rebootRUU
fastboot flash zip PN07IMG_M7_UL_JB_50_BrightstarUS_WWE_1.29.1540.3.zip
****GOT AN ERROR*****
Code:
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
.... so again:
fastboot flash zip PN07IMG_M7_UL_JB_50_BrightstarUS_WWE_1.29.1540.3.zip
10 minutes later
fastboot reboot
Oh my was I happy to see the white HTC Startup.
I also have same phone de it shouldnt be tamperd relocked it should be only relocked
Sent from my HTC One using xda app-developers app
I find it funny now far Computer OS's have come and yet we always have to go back to good old DOS Command Prompt to fix things.
BTW, my phone now has bootloader RELOCKED due to the fastboot oem lock command, should I send the phone back just like that or unlock bootloader before sending it back?
I guess to Unlock bootloader again, I have to follow same instructions as if it were an AT&T version right? Did you UNLOCK yours again OP?
U sending it back to HTC?
Sent from my HTC One using Tapatalk 2
Bosnazmaj said:
U sending it back to HTC?
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
Yes, that is the reason I was doing all this restoring. I had ROOTed it to install AdAway. Ads is the only major drawback when compared to iOS (this is my first Android). When you see a gray image on my phone, there are 3 sort of water drops. Like between the touch screen and LCD.
Well, I am exchanging it actually. I like the HTC One a lot. It has a tiny gap, but I dont care about that much, the weird discoloration on the sceen, though, I do mind.
That makes sense.
Sent from my HTC One using Tapatalk 2
Bosnazmaj said:
I am having an issue that I have not seen before and could not find any resolve thru XDA or Google. I am attempting to restore the 64G Developer Edition with the RUU from HTC Dev and I keep getting the 155 error. I even have attempted to install thru CWM the .zip. Still no avail.
I am currently rooted, and have CWM installed. The device is obviously Bootloader unlock. What I was able to find is that it possibly could be a issue that it is bootloader unlocked as some posts suggest to have you bootloader locked to install RUU, but that is obviosely not a posibility with the dev ed.
So what am I doing wrong, or what is the issue. I have confirmed that I was using the correct RUU.
Help Appreciated
UPDATE
Ok, I figured out how to avoid the RUU 155 error. It seems that HTC for some dumb reason, although for a unlocked developer edition, we still have to lock the bootloader to utilize the RUU. Here are the steps I have done.
Although it is straight forward and easy to do, issues could always arise. I do not take any responsibility if things go wrong. Educate yourself first before attempting anything. If you do not know what you are doing, then don't do it.
Before Starting.
Make sure you have the latest HTC Drivers. You can use hasoon2000 HTC All-In-One Toolkit to complete that. That can be found at HTC One All-In-One Toolkit
Get the appropriate RUU from HTC Dev
1. Lock your bootloader through by booting into hoot and then going into fastboot and issuing the command fasboot oem lock.
2. Once locked, reboot your system.
3. Open RUU and follow onscreen instructions.
Notice, this will delete all of the files on the system so do this on your own cognition
4. Let the RUU do its thing. If you get an error during the process, such as 152, simply try again. I had it happen once. The phone was stuck on the black HTC screen with four triangles with exclamation points in each corner. If this happens you will not be able to reboot your phone. Simply relaunch RUU and it should reinstall it. If you get error 155 again, then you have not re-locked your bootloader.
3.Once you have successfully reinstalled the rom, you have to register with the HTC Dev to re-unlock your bootloader if that is what you want. The easiest to do this I found was by using the HTC One All-In-One Toolkit. It is a great tool and will help you with majority of things that I have mentioned above, including locking your bootloader. Follow the steps on the toolkit and you'll be all set. The Toolkit can be found here HTC One All-In-One Toolkit
If you found this helpful, click thanks. Also hit thanks to hasoon2000 for creating the toolkit.
Click to expand...
Click to collapse
Thank you. This was very helpful.
Glad I could help
Sent from my HTC One using Tapatalk 2
schn1tt3r said:
It came with the .3 and I did OTA to .16
The RUU you can get online from their web is only .3
===============================
Ok so... that black HTC screen accepts "fastboot" commands.
I downloaded the .ZIP version of the Developer Edition OS.
I went in command prompt, I typed
fastboot reboot-bootloader
fastboot oem rebootRUU
fastboot flash zip PN07IMG_M7_UL_JB_50_BrightstarUS_WWE_1.29.1540.3.zip
****GOT AN ERROR*****
Code:
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
.... so again:
fastboot flash zip PN07IMG_M7_UL_JB_50_BrightstarUS_WWE_1.29.1540.3.zip
10 minutes later
fastboot reboot
Oh my was I happy to see the white HTC Startup.
Click to expand...
Click to collapse
THANK YOU MAN!!!!!!!! You just saved me. I had the same problem except I had OTA .17 and trying to flash .16. My device was all jacked up but it's back to original.
Bosnazmaj said:
I am having an issue that I have not seen before and could not find any resolve thru XDA or Google. I am attempting to restore the 64G Developer Edition with the RUU from HTC Dev and I keep getting the 155 error. I even have attempted to install thru CWM the .zip. Still no avail.
I am currently rooted, and have CWM installed. The device is obviously Bootloader unlock. What I was able to find is that it possibly could be a issue that it is bootloader unlocked as some posts suggest to have you bootloader locked to install RUU, but that is obviosely not a posibility with the dev ed.
So what am I doing wrong, or what is the issue. I have confirmed that I was using the correct RUU.
Help Appreciated
.........
Click to expand...
Click to collapse
Bosnazmaj - thank you for this wonderful write-up & knowledge. I have a Dev edition myself. Sometime ago, I got into charging issues. Initially, assuming it to be software issues, I thought I'd run the RUU. So, like you, I too figured out that I have to lock my bootloader. Ran the RUU....long story short, found out that I have to give my phone for repairs (turned out to be a hardware issue).
So, the point I am trying to make is that, if we unlock the bootloader, certain apps (like flashlight, sound recorder etc) seems to get deleted. While this, on it's own, might not sound too alarming....the problem is, if these apps are not present, then the OTA does not & will not get applied as the OTA says that these apps have to be present. I am not sure how to unlock the bootloader without losing any apps.
Any knowledge / information on this is MOST appreciated.
Actually I used titanium backup to back those apps that disappear during root before I unlocked anything. Then once I rooted and unlocked I just restored them back with titanium and all was fine. But in reality you don't want to so an ota when you are rooted as you might loose root.
Sent from my HTC One using Tapatalk 2
Can't you re-unlock the phone using following command without going through the HTCDev website mess?
Code:
fastboot oem unlock
Just a heads up. I was able to return to stock using the RUU without locking the bootloader. It took a while to figure it out.
I went from ARHD 31 to A stock rom (m7_stock_dev_1.29.1540.16_signed_052313.zip) found on an old thread, also had to find a stock recovery that would work (i think it was the one liked in the ARHD thread) and used the revone S-off method, then applied the latest RUU from the htc dev site .and it installed and the bootloader remained unlocked.
I had to get this thing ready for someone who bought it. They asked if i could return it to stock with S-off. It was a pain in the but, but got it working

[Q] HELP HTC One M7

I am a noob and tried to sim unlock my HTC one from Sprint and really messed things up, I erased the OS and no longer have TWRP access.
Let me start from the beginning, I have an HTC One (M7) by Sprint. I wanted to sim unlock it so I could use it with another carrier. I successfully unlocked the boot loader through htcdev. I then successfully rooted the device. Then I was stuck on trying to unlock the sim. I think I was unsuccessful because I had upgraded to Android 4.3, but not sure.
To make a long story short I kept messing with it and accidentally erased my OS while trying to use rumrunner. I had access to TWRP, which I had installed earlier, but as of today I no longer have access to TWRP, it just does not load anymore. I can still load into the boot loader usb section of my phone that’s about it.
I also relocked the boot loader because I read somewhere in another forum that I was supposed to do so.
So as of now my HTC one is Bootloader locked, S-ON, HBOOT 1.55.
ADB won’t recognize my HTC at all, I have another HTC (Different model) and ADB recognizes it so I know I have the drivers installed correctly, but it wont read the HTC One.
I tried using fastboot to flash a new ROM, and TWRP recovery but no luck, it stops at bootloader (Signature verify fail). So I can’t even push anything to the phone.
Can anyone please help? If you need anymore info please let me know.
arc209 said:
I am a noob and tried to sim unlock my HTC one from Sprint and really messed things up, I erased the OS and no longer have TWRP access.
Let me start from the beginning, I have an HTC One (M7) by Sprint. I wanted to sim unlock it so I could use it with another carrier. I successfully unlocked the boot loader through htcdev. I then successfully rooted the device. Then I was stuck on trying to unlock the sim. I think I was unsuccessful because I had upgraded to Android 4.3, but not sure.
To make a long story short I kept messing with it and accidentally erased my OS while trying to use rumrunner. I had access to TWRP, which I had installed earlier, but as of today I no longer have access to TWRP, it just does not load anymore. I can still load into the boot loader usb section of my phone that’s about it.
I also relocked the boot loader because I read somewhere in another forum that I was supposed to do so.
So as of now my HTC one is Bootloader locked, S-ON, HBOOT 1.55.
ADB won’t recognize my HTC at all, I have another HTC (Different model) and ADB recognizes it so I know I have the drivers installed correctly, but it wont read the HTC One.
I tried using fastboot to flash a new ROM, and TWRP recovery but no luck, it stops at bootloader (Signature verify fail). So I can’t even push anything to the phone.
Can anyone please help? If you need anymore info please let me know.
Click to expand...
Click to collapse
You have to unlock the bootloader again, flash twrp recovery then sideload a rom.
+1 on the unlock
and get the recovery specifically for SPRINT, it's different than the GSM HTC One, you'll also have to flash a "close to stock" ROM to be able to use the SIM unlock code. no need to be locked!
and remember to get a close-to-stock ROM for SPRINT!!!

[Q] Can't Unlock Bootloader

I'm having a bit of a problem with the htc one running kitkat 4.4.2 Google Edition and S-OFF
I've been trying to unlock the bootloader all day but nothing....
I'm doing the right CMD commands and its even saying that i have flashed the unlock_code to the phone but my phone freeze for 5 sec and then resume (in fastboot).
CMD is saying that the flash was okay but nothing on my phone happens.
And could it depend on what version of Android SDK i have.
I would really appreciate it if you could help me with this problem
Have you gone to HTC Dev page and followed the instructions?
Is it a real GPE or a converted one?
have you tried "fastboot oem unlock" ?
Do you have root?
you could try this: http://forum.xda-developers.com/showthread.php?t=2475914

[Q] Return to Stock without ADB

Hey there,
my phone is broken, it won't load or do anything on the usb port while the system is up, when the phone is off/fastboot or recovery it seems to charge (very slow) and i have no problems accessing it through fastboot or adb.. but even when the battery is fully charged i cannot use it for more than an hour or so before its discharged again..thats what my problem startet with, over the night the phone won't charge and i couldn't use ADB etc while the OS was up...
i think it is a hardware problem, the last thing i did was updating the firmware, but after that i used the phone like 2 weeks or, without problems and changing anything......
first i thought about it could be a bug with the new firmware, so i downgraded to an old stock version and update it through OTA to the latest version but nothing changed..
then i thought of sending it in and i tried to lock my bootloader and restore everything before doing this but the only way to access the phone via adb was in recovery, so i did that and S-ONed the phone and locked the bootloader, not thinking about that i cannot restore the old recovery with locked BL.
since i knew that i am kind of an idiot, not thinking about what exactly i did at this point i thought i pay my rent by buying SunShine an S-On it again (i didn't find another way to root/unlock BL since i was on last HTC-Android version). and replace the recovery with the original one
now i have my phone with stock recovery and everything but i cannot lock/s-off the bootloader again because i have no adb access.
Does anyone have an idead how i can prepare my phone for sending it in?
I thought about rooting stock firmware, replace recovery with stock recovery, write a script that locks the bootloader execute it after replacing recovery and unroot the phone from within SuperSU. then S-OFF it again.
I guess this should work, but since i didn't think about everything the first time i thought i might ask here if someone has a better idea.
smokey_joe said:
Hey there,
my phone is broken, it won't load or do anything on the usb port while the system is up, when the phone is off/fastboot or recovery it seems to charge (very slow) and i have no problems accessing it through fastboot or adb.. but even when the battery is fully charged i cannot use it for more than an hour or so before its discharged again..thats what my problem startet with, over the night the phone won't charge and i couldn't use ADB etc while the OS was up...
i think it is a hardware problem, the last thing i did was updating the firmware, but after that i used the phone like 2 weeks or, without problems and changing anything......
first i thought about it could be a bug with the new firmware, so i downgraded to an old stock version and update it through OTA to the latest version but nothing changed..
then i thought of sending it in and i tried to lock my bootloader and restore everything before doing this but the only way to access the phone via adb was in recovery, so i did that and S-ONed the phone and locked the bootloader, not thinking about that i cannot restore the old recovery with locked BL.
since i knew that i am kind of an idiot, not thinking about what exactly i did at this point i thought i pay my rent by buying SunShine an S-On it again (i didn't find another way to root/unlock BL since i was on last HTC-Android version). and replace the recovery with the original one
now i have my phone with stock recovery and everything but i cannot lock/s-off the bootloader again because i have no adb access.
Does anyone have an idead how i can prepare my phone for sending it in?
I thought about rooting stock firmware, replace recovery with stock recovery, write a script that locks the bootloader execute it after replacing recovery and unroot the phone from within SuperSU. then S-OFF it again.
I guess this should work, but since i didn't think about everything the first time i thought i might ask here if someone has a better idea.
Click to expand...
Click to collapse
You have stated a lot of things but most of them are contradictory.
What is the status of your phone? Locked or Unlocked?
Are you S-ON or S-OFF?
What recovery do you have on the phone? Stock or Custom?
What specifically are you trying to accomplish?
If you have stock rom, stock firmware with stock recovery, bootloader is locked and you are S-ON then you are back to stock. However, if your bootloader states "Tampered" and/or "Relocked" then the service facility will know that you tampered with the phone. To remove those items:
Unlock bootloader
Follow the steps in nkk71's SuperGuide in my signature on:
--Gain S-OFF
--Custom recovery
--Removing "Tampered" & "Locked"
--Install stock firmware
--Gain S-ON
majmoz said:
You have stated a lot of things but most of them are contradictory.
What is the status of your phone? Locked or Unlocked?
Are you S-ON or S-OFF?
What recovery do you have on the phone? Stock or Custom?
What specifically are you trying to accomplish?
If you have stock rom, stock firmware with stock recovery, bootloader is locked and you are S-ON then you are back to stock. However, if your bootloader states "Tampered" and/or "Relocked" then the service facility will know that you tampered with the phone. To remove those items:
Unlock bootloader
Follow the steps in nkk71's SuperGuide in my signature on:
--Gain S-OFF
--Custom recovery
--Removing "Tampered" & "Locked"
--Install stock firmware
--Gain S-ON
Click to expand...
Click to collapse
thanks for your reply.
i guess i was to confused to see that i can remove the tampered and unlocked flags, then restore the stock bootloader and then s-off the phone...i thought i have to remove tampered/unlocked and then s-on the phone in the same step....i guess i have no problem when i can do it like that

S-ON with no system on! how to get out?!

Hello.. how are ya devs
I've asked this last night numerously and ended up with headaches.. yes.
I accidentally wiped EVERYTHING from my htc one and I have S-ON so I basically can't flash a firmware.. So I spent the last night looking at my beautiful blank white screen.. How do I fix it please? I'd appreciate a help..
Quick Help (might work 4 you)
Hey buddy,
I got myself a M7 working again by letting it get set back to stock from a RUU.exe which fit to my phone.
It was S-On and with an UNlocked bootloader.
At first is to say that I cant provide any guarantee for the workability of my solution, neither will I take any responsibiliry in case you mess your mess up even more
But here is how I went on the case:
I just got myself this quick installer here to set up my PC for adb and fastboot commands!
Second you will need the HTC Drivers ("Solo Driver Installer) and a working USB Cable of course
After connecting Phone I started my Phone into bootloader and swiched to the "fastboot" mode! I used the Windows "CMD" command tool to find out which Baseband version i need, by typing fastboot devices and fastboot getvar all. The second command gives you the needed infomation about your Baseband!
After finding out, find your fitting RUU.exe right here and load that 1,6 GB file
At last all you need is to make sure that your bootloader is (RE-)LOCKED, because else the RUU.exe wont work!
A simple fastboot lock oem will do the thing! Afterwards your Phone should be able to get reflashed with the Stock ROM and stuff that comes by the RUU! NOTE: Unlocking your Bootloader requires a working OS as far as i know, and cant be done by another "Fastboot oem UNlock" command
This link is describing the same procedure in case you're unsure..
Greetings, a happy owner of a working HTC M7

Categories

Resources