Related
Hello,
This morning I was in the market ( My Apps) and i chose Update all option. Loads of apps started to download, and after few minutes my phone froze. So i removed the battery and since then I', stuck in the bootloader menu:
AlphaRev
SAGA PVT SHIP S-OFF RL
HBOOT-6.98.1002
RADIO-38.03.02.14_M
eMMC-boot
Mar 10 2011, 14:58:38
I can't do factory reset or access recovery. At some point I have successfully ran RUU, problem is I'm on UK O2 but being complete idiot I installed 3's ROM. Even the 3's ROM don't boot up. I can't run RUU anymore, because every time RUU is trying to reboot into boot loader it get stuck.
So,
I got phone from O2 that has a 3 logo (its stuck on it),
I have S-OFF phone so it probably voided the warranty.
Can anyone think of any solution please?
Thanks in advance for your help guys.
If you need more info please let me know.
Marcin
There are at least 5 similar topics, one is mine (same thing happened to me). Use search.
Does adb works yor you ?
yeap I have also created a topic on this.
I had to send mine back to HTC to fix.
What I would like to know is, if you send it back to HTC, would they notice the s-off and charge you money?
What ROMs were you all on? I got a similar problem on stock ROM after XTC Clip S-OFF, but a battery pull fixed it. I guess this only happens with S-OFF stock ROMs, so switch to avoid this.
No, adb doesn't see my phone....
mpolak83 said:
No, adb doesn't see my phone....
Click to expand...
Click to collapse
Remember with adb you need to be in Fastboot not Hboot! Very important. Cab you get into Fastboot?
InfernalByte said:
Remember with adb you need to be in Fastboot not Hboot! Very important. Cab you get into Fastboot?
Click to expand...
Click to collapse
When I run Adb devices it doesn't list my phone...so it doesn't work i suppose....
If I send my phone to HTC for repair will they accept it or will charge me because of S-OFF??
I just need my phone to be in the state so I can send it to HTC...I need to at least get rid off 3 logo and S-OFF...
mpolak83 said:
I just need my phone to be in the state so I can send it to HTC...I need to at least get rid off 3 logo and S-OFF...
Click to expand...
Click to collapse
Try flashing the eng hboot by PB88IMG method, and then try and run the correct RUU. That's my best idea.
InfernalByte said:
Try flashing the eng hboot by PB88IMG method, and then try and run the correct RUU. That's my best idea.
Click to expand...
Click to collapse
I have tried that, but I got the error that I can't roll back to older version of hboot.
I have just booked my phone for repair.. I'm gonna act stupid. I'll tell them that my friend installed something on my phone etc. Probably won't work... I will let you know what they said.
HTC gave me some terms and conditions to read and one of the says:
2.3 NonWarranty chargeable Repair Service
a) Repair of a Device that is
In-Warranty but which needs to be repaired including the following or similar
reasons shall be classified as a NonWarranty chargeable Repair Service:
1) Accidental damage. Accidental damage to the Device, such as dropping it
on the ground or in water. 2) Broken Liquid Crystal Display (hereinafter
known as “LCD”). 3) Damaged Sync or Charger Connector. 4) Damage
caused by liquid entering the Device, or other misuse due to the failure of the
Customer to follow the instructions properly. 5) Failure of the Customer to
upgrade the software according to the procedures outlined under the
warranty terms card of the Device. 6) Downloading illegal software onto the
Device. 7) Where the fault is caused by downloading illegal software onto the Device
or other accidental damage, the Customer shall be required to pay for spare
parts, labour, diagnosis and software refurbishment along with shipping and
handling charges.
Is S-OFF classified as illegal software?
Everything except RUU is illegal software...
Bubaaak said:
Everything except RUU is illegal software...
Click to expand...
Click to collapse
So I'm busted?
It's 50:50
Sent from my HTC Desire S using Tapatalk
Bubaaak said:
Everything except RUU is illegal software...
Click to expand...
Click to collapse
Wrong.
Its not illegal but you have probably invalidated your warranty. The thing is HTC have to bother to check your phone for custom software and a lot of the time they do.
Quick update.
I have sent my phone to HTC for repair under warranty yesterday. I have checked the status today, and it says "We are repairing your phone" So it looks like HTC don't check if the phone was rooted or have S-OFF
I've done the same i tried to flash a ruu image that was the wrong one i followed a thread on how to get s-on again just so i knew i could. I got s-on but now my phone is stuck on bootloader and is not recognised by the pc Please let me know how you get on and if you get charged as i will be doing the same i think.
InfernalByte said:
Wrong.
Its not illegal but you have probably invalidated your warranty. The thing is HTC have to bother to check your phone for custom software and a lot of the time they do.
Click to expand...
Click to collapse
Aren't custom Sense ROMs illegal ?
Coz Sense is HTC Proprietary framework.
goatimus said:
I've done the same i tried to flash a ruu image that was the wrong one i followed a thread on how to get s-on again just so i knew i could. I got s-on but now my phone is stuck on bootloader and is not recognised by the pc Please let me know how you get on and if you get charged as i will be doing the same i think.
Click to expand...
Click to collapse
You have to go to fastboot
Sent from my HTC Desire S using Tapatalk
UPDATE
=========
I just wanna say that tomy1986.nt is the man!!!! If you have a bricked device send it to this guy, worth the money! He fixed my device within an hr! It wouldn't power on at all!
http://forum.xda-developers.com/member.php?u=4116958
Dropped it off at his house and he worked his magic!
=========
Ok got an HTC One X..... ran the RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio_0.24p.32.09.06_10.130.32.34_release_signed_With_Partial.exe to update the device after running "fastboot oem lock" and the program said it had completed successfully, the phone turned off and never came back on. I unplugged the device and attempted to turn it on, no lights, no nothing.
The only thing that happens is if I plug it into my computer I hear the sound you hear when a driver is attempting to install. The HTC drivers are indeed on my computer.
Any hope for unbricking this thing or am I screwed?
Thanks!
Do you have the One X (Endeavor) or the One XL (Evita)?
Sent from my Evita
I have the one x but my understanding was the roms were interchangeable. It's the AT&T One X.
You're just a bit mixed up with your terminology. Your phone is the the at&t One X / HTC One XL (Evita), the HTC One X is the Endeavor.
Being that the at&t One X and HTC One XL are the same phone (Evita), the ROMs are the same. But HTC One X (Endeavor) ROMs are not for our phone and can brick it if flashed.
Was your phone second hand? Do you know if it had SuperCID? And whether it is s-on or s-off? If it has SuperCID and is s-on, running an RUU causes a brick.
Does the phone show up as QHSUSB_DLOAD in device manager on pc when you connect it? If so you have a brick, and still need to get a jtag repair done.
Sent from my Evita
If the phone was S-on and SuperCID, you have a true hard brick. As timmaaa mentioned, if you get QHSUSB_DLOAD when you connect to PC, this pretty much confirms it.
Sounds like either you, or the original owner unlocked the bootloader, since you went through the step of relocking it (or at least you suspected it may be unlocked). So my guess is that you are another victim of the S-on + SuperCID + Jellybean RUU/OTA combo.
http://forum.xda-developers.com/showthread.php?t=2181929
Actually I only used evita roms/ruu's.
Here is exactly what I did:
1) Rooted / S-OFF / Flashed Recovery / Unlocked Bootloader / Super CID 111111111 (how many ever 1's)
2) Locked Bootloader and refreshed with 2.20 RUU which was successful
3) Rebooted phone, enabled debugging
4) Ran 3.18 RUU (AT&T One X) and it said successful.
5) Device powered off and i waited, never came back on so i unplugged it
6) Makes driver noise when plugging to pc but does not power on visually, no lights etc
I found a guy locally who can try the jtag.
You could try charging it for a few hours and try holding power + volume down to see if it boots. Every now and again these phones have a power management issue where it loses power (or thinks it does) completely.
If that doesn't work it looks like you might be one of the very unlucky people who has had an RUU brick their phone for no apparent reason.
Sent from my Evita
ssconceptz said:
Here is exactly what I did:
1) Rooted / S-OFF / Flashed Recovery / Unlocked Bootloader / Super CID 111111111 (how many ever 1's)
Click to expand...
Click to collapse
Ok, so it wasn't the combo of S-on, SuperCID and Jellybean RUU that caused the brick then.
But any flashing of hboot has some small possibility of bricking the phone, if everything does not go exactly right (such as corrupt RUU file). You can look into the unbricking thread in General:
http://forum.xda-developers.com/showthread.php?t=1966850
You can see if you can enumerate the partitions with Linux. If the parititions can't be found, JTAG is your next option.
Nobody has been able to unbrick this way from the S-on, SuperCID, RUU combo, that I know of. But your case is slightly different, so maybe you still have a chance.
---------- Post added at 11:18 AM ---------- Previous post was at 11:13 AM ----------
timmaaa said:
You could try charging it for a few hours and try holding power + volume down to see if it boots. Every now and again these phones have a power management issue where it loses power (or thinks it does) completely.
Click to expand...
Click to collapse
Yes, its a good idea to try that.
Although the fact it went dark right after running the RUU, doesn't have me very hopeful.
Yeah I'm not hopeful at all either, but it's worth a try.
Sent from my Evita
timmaaa said:
Yeah I'm not hopeful at all either, but it's worth a try.
Click to expand...
Click to collapse
Absolutely! Always good to try the easy stuff first, before resorting to more drastic measures.
Thanks for the tips. Will try the unbrick hardware method, if doesn't work maybe i'll find a busted up device and use this one for parts.
I just wanna say that tomy1986.nt is the man!!!! If you have a bricked device send it to this guy, worth the money! He fixed my device within an hr! It wouldn't power on at all!
http://forum.xda-developers.com/member.php?u=4116958
Dropped it off at his house and he worked his magic!
i got this pm and i thot it was worth everyone to see. while i do not recomend turning any device s on,a verizon device that is not unlockable via htcdev is of much more importance,as the only thing that can rescue it is a new enough,signed RUU.
it really is not worth the risk,i promise.
nicholi2789 said:
scotty1223 said:
nicholi2789 said:
Hey there, Sorry to bother you with a PM like a noob, but I just have a quick question for you. I have just received a Certified like new replacement M8 from Verizon because my original one had a manufacturer defect. My original one was S-OFF, rooted, with custom recovery and the latest firmware (1.55.605.2) from Verizon. I'm trying to get it back to as close to stock as possible so Verizon doesn't try and say I modified it and mak me pay for it. I already un-rooted it, flashed stock recovery, and took the latest OTA so my radios match my software version. Then I followed this thread: http://forum.xda-developers.com/showthread.php?t=2708571
to re-lock the bootloader and set the lock status flag. It says locked again in fastboot.
The only thing I have left is the S-OFF that displays in fastboot. I'm trying to find a way to reset that, or at least modify it so it shows S-ON. That way if by some weird chance a Verizon employee boots it to fastboot it will show completely stock and S-ON.
Now i've found this thread: http://forum.xda-developers.com/showthread.php?t=2475216 for resetting the S-OFF flag. I posted in it and asked if it would work on the M8 and nobody could give me an answer. XDA member brymaster5000 told me to ask you and that you could provide an answer.
So finally, my question is, will this fastboot command "fastboot oem writesecureflag 3" work to set my M8 back to S-ON? I know it works on the M7 but nobody can tell me for sure on the M8.
Thanks alot for your time.
Nick
Click to expand...
Click to collapse
I would very strongly recommend that you do not turn s on. Phones came s off ,so leaving out that way is not an issue.
Turning s on may open a can of worms that you cannot recover from,and then you're paying for a phone for sure.
As long as your stock rom, recovery and locked you're good to go
Sent from my HTC One VX using Tapatalk
Click to expand...
Click to collapse
What do you mean phones came s-off? Verizon sent people m8s that already were s-off? It just seems like a super obvious indication that the device was modified. Your not the first person that has said that going back to s-on is a bad idea, so I will listen and not tempt fate. But iam curious, What can happen by doing that command that could cause such problems? And don't stock RUUs return you to s-on? Or do they just reset everything else but s-off?
Click to expand...
Click to collapse
before any phone is released,batches are sent off to testers and these devices are always s off. i have owned several factory s off devices,and there is no way of proving the phone you have did not come this way. further, large phone resellers are able to use factory htc diagnostic files to clear security data(sim lock,s off,cid/mid),wich again is a legitimate reason a phone is s off.finding s off in the bootloader is not by any means a "super obvious" indication of having been messed with.
turning the phone s on could cause the tampered flag to reset(we dont completely understand all the things that trip it) or you could end up locked into bootloader with a security warning if the boot,system or recovery are not stock enough. either of these things ARE super obvious indicators that you have messed with it,and tried to hide it.
in the case of the security warning,the only course of action is to:
1)run a signed ruu(wich must meet many criteria since youre now s on)
or
2)re-unlock the bootloader. as you know,using htcdev to unlock is not possible with vzw
an ruu does not change/update the partition where the secutity flag lives and thus will NOT turn you s on.
Thanks for the write up, this should help some users decide. Wish it was as easy as flashing a pit file in Odin . That's one of the main reasons I've yet to root/s-off. HTC devices still confuse me xD
Sent from my HTC6525LVW using Tapatalk
wtoj34 said:
Thanks for the write up, this should help some users decide. Wish it was as easy as flashing a pit file in Odin . That's one of the main reasons I've yet to root/s-off. HTC devices still confuse me xD
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
Agreed great write up... in reference to rooting the m8 it is very easy with weak sauce app I also find the s-off to be easier as well compared to Sammy devices using Odin. with my s4 like with the m8 there was no need for a pc for root but weak sause app is easier then using commands in a terminal emulator. Just my two sense.
thunderbls said:
Agreed great write up... in reference to rooting the m8 it is very easy with weak sauce app I also find the s-off to be easier as well compared to Sammy devices using Odin. with my s4 like with the m8 there was no need for a pc for root but weak sause app is easier then using commands in a terminal emulator. Just my two sense.
Click to expand...
Click to collapse
You have missed the point... If you are locked into the bootloader with a security warning and s-on, you can not use weak sauce and firewater
Sent from my HTC One VX using Tapatalk
People need to realize that verizon reps and techs see hundreds of phones, they don't know the details of every device. The security and bootloader status is obvious to us because it's our device and we know everything about it. To a samsung person they won't know WTF your talking about.
Scotty, Would one be able to save their device if they had S-Off, modified the CID, then used HTCDev to get their unlock token before embarking on an endeavor to re-lock the phone? In theory would they be able to use the unlock token even after the CID was changed back and the security flags turned on?
l7777 said:
Scotty, Would one be able to save their device if they had S-Off, modified the CID, then used HTCDev to get their unlock token before embarking on an endeavor to re-lock the phone? In theory would they be able to use the unlock token even after the CID was changed back and the security flags turned on?
Click to expand...
Click to collapse
Not really... More later
Sent from my HTC One VX using Tapatalk
scotty1223 said:
Not really... More later
Sent from my HTC One VX using Tapatalk
Click to expand...
Click to collapse
Yes, I misinterpreted the comment as general ease of use which makes me look like an idiot given the reason for the response.... my apologies and note to self read xda after nap lol.
l7777 said:
Scotty, Would one be able to save their device if they had S-Off, modified the CID, then used HTCDev to get their unlock token before embarking on an endeavor to re-lock the phone? In theory would they be able to use the unlock token even after the CID was changed back and the security flags turned on?
Click to expand...
Click to collapse
Not really... More later
Sent from my HTC One VX using Tapatalk
Click to expand...
Click to collapse
the prollem is that the vzw cid/mid are blocked(by vzws request ) at htcdev. changing the cid and/or mid will let you get an unlock_code.bin that will officially unlock the bootloader,but this token is only good while the phone contains these same parameters. i.e., you cant get yourself a token,then change the cid and mid back to stock and have the "safety net" of a token in case of a catastrophic security warning. cid,mid,esn,etc must all stay same in order for the token to continue working.
Q:"well,what if i just leave the cid/mid at something different?"
A:that may work,but it may set the tampered flag if the phone realizes that those partitions no longer match. since the cid and mid live in write protected partitions,its also possible what once s is on and the phone starts checking things in its boot sequence,that the processor may freak out,and go into a "do not boot" mode when signitures do not match what they should. (read "do not boot" as: pretty affective hard brick only recoverable by jtag)
plus,even if the phone did boot,and did not set the tampered flag, the phone is not stock,and may fail OTAs or have other issues that may affect users the phone is sent back out to,or may give it away that you have modified it.
the fact is,that these phones are not checked very well,as was said above. the chance of it being noticed that the s off phone is even different than others is slim to none,and it is quite possible that the phone will make it back out into the wild as a refurb without any sort of refurbishing process. if you thot all phones were hooked to a master computer that completely reset things,checked hardware,flashed the newest firmware,and reset things like supercid,simlock and s off,youd be mistaken. due to this fact,it is my strong opinion that patched hboots(displaying incorrect info of locked and s on),or incorrect cid/mids are extremely unethical and should never be sent in to fraud htc or the carriers,espeically since it may affect other users. returning the phone to a stock,locked s-off state is honest,and will not affect a future users esperince. the device will OTA and funtion normally and the unsavy user will never even know they have a device that is special
hope that cleared it up some.
also,sorry if either of my replies earlier were rude,they were not intended to be,im only able to text to speech short replies while im at work.
scotty1223 said:
the prollem is that the vzw cid/mid are blocked(by vzws request ) at htcdev. changing the cid and/or mid will let you get an unlock_code.bin that will officially unlock the bootloader,but this token is only good while the phone contains these same parameters. i.e., you cant get yourself a token,then change the cid and mid back to stock and have the "safety net" of a token in case of a catastrophic security warning. cid,mid,esn,etc must all stay same in order for the token to continue working.
Q:"well,what if i just leave the cid/mid at something different?"
A:that may work,but it may set the tampered flag if the phone realizes that those partitions no longer match. since the cid and mid live in write protected partitions,its also possible what once s is on and the phone starts checking things in its boot sequence,that the processor may freak out,and go into a "do not boot" mode when signitures do not match what they should. (read "do not boot" as: pretty affective hard brick only recoverable by jtag)
plus,even if the phone did boot,and did not set the tampered flag, the phone is not stock,and may fail OTAs or have other issues that may affect users the phone is sent back out to,or may give it away that you have modified it.
the fact is,that these phones are not checked very well,as was said above. the chance of it being noticed that the s off phone is even different than others is slim to none,and it is quite possible that the phone will make it back out into the wild as a refurb without any sort of refurbishing process. if you thot all phones were hooked to a master computer that completely reset things,checked hardware,flashed the newest firmware,and reset things like supercid,simlock and s off,youd be mistaken. due to this fact,it is my strong opinion that patched hboots(displaying incorrect info of locked and s on),or incorrect cid/mids are extremely unethical and should never be sent in to fraud htc or the carriers,espeically since it may affect other users. returning the phone to a stock,locked s-off state is honest,and will not affect a future users esperince. the device will OTA and funtion normally and the unsavy user will never even know they have a device that is special
hope that cleared it up some.
also,sorry if either of my replies earlier were rude,they were not intended to be,im only able to text to speech short replies while im at work.
Click to expand...
Click to collapse
Excellent info, I wondered if the unlock token was tied to the cid/mid. My personal preference is once the phone is unlocked it stays that way. It's my device and I'll take the responsibility for whatever happens to it barring some kind of hardware defect.
l7777 said:
Excellent info, I wondered if the unlock token was tied to the cid/mid. My personal preference is once the phone is unlocked it stays that way. It's my device and I'll take the responsibility for whatever happens to it barring some kind of hardware defect.
Click to expand...
Click to collapse
I agree completely.
Sent from my HTC One using Tapatalk
scotty1223 said:
I agree completely.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Anyone at the point of "return" should at least trying running my RUUish zip from boot loader before even thinking about relocking or s-on.
?. Glad to see you throwing some support over here
Sent from my Nexus 7 using Tapatalk
dottat said:
Anyone at the point of "return" should at least trying running my RUUish zip from boot loader before even thinking about relocking or s-on.
?. Glad to see you throwing some support over here
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Lol I try and throw support wherever its needed
So far, no m8 ruus yet. Hopefully some start popping up.
As far as I'm concerned,back to stock sequence is this:
While still rooted:
-return cid/mid to.stock
-reset tampered
-lock bootloader
Then:
-run release keys ruu
-collect underpants
-???
-proffit!
When ruu is not available,restore stock boot,system and recovery from backups.
After that's done allow phone to ota to current
Not sure why folks try and make it more complex than that
Sent from my HTC PG09410 using Tapatalk 2
How do you reset tampered?
scotty1223 said:
Lol I try and throw support wherever its needed
So far, no m8 ruus yet. Hopefully some start popping up.
As far as I'm concerned,back to stock sequence is this:
While still rooted:
-return cid/mid to.stock
-reset tampered
-lock bootloader
Then:
-run release keys ruu
-collect underpants
-???
-proffit!
When ruu is not available,restore stock boot,system and recovery from backups.
After that's done allow phone to ota to current
Not sure why folks try and make it more complex than that
Sent from my HTC PG09410 using Tapatalk 2
Click to expand...
Click to collapse
Paulb787 said:
How do you reset tampered?
Click to expand...
Click to collapse
Search this forum for a thread. I'm at work, I can't link it at the moment
Sent from my HTC One VX using Tapatalk
scotty1223 said:
So far, no m8 ruus yet. Hopefully some start popping up.
Not sure why folks try and make it more complex than that
Sent from my HTC PG09410 using Tapatalk 2
Click to expand...
Click to collapse
sorta?
For those who stay s-off and have issues I put together an ruu of sorts that includes the ota firmware that will get users out of a sticky situation. ?
Between the two of us we can probably fix most software problems as long as users stay s-off once s-off!!!
Sent from my Nexus 7 using Tapatalk
Ha, it's funny that you posted our PM conversation. It's kinda embarrassing but at least I asked someone who knew before just doing it, messing it up, then screaming to the forums for help. And while i am by no means a beginner Android power user, HTC devices are just a little bit different than the Samsung devices I am used to. Though there is alot of good information in this PM conversation that alot more people should know. Glad it could be of use! And thanks for taking the time to reply to my PMs Scotty. I appreciate that.
nicholi2789 said:
Ha, it's funny that you posted our PM conversation. It's kinda embarrassing but at least I asked someone who knew before just doing it, messing it up, then screaming to the forums for help. And while i am by no means a beginner Android power user, HTC devices are just a little bit different than the Samsung devices I am used to. Though there is alot of good information in this PM conversation that alot more people should know. Glad it could be of use! And thanks for taking the time to reply to my PMs Scotty. I appreciate that.
Click to expand...
Click to collapse
I didn't mean to embarrass you. They were good questions I thot everyone should read. I should have asked you,and can edit them if you wish.
Sent from my HTC PG09410 using Tapatalk 2
scotty1223 said:
I agree completely.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Nah I wasn't really embarrassed. Haha. I just meant that it's slightly embarrassing that I knew so little about HTC devices, but not a big deal or anything. You were right to post it though, there is some good information there that will do lots of people good.
dottat said:
sorta?
For those who stay s-off and have issues I put together an ruu of sorts that includes the ota firmware that will get users out of a sticky situation. ?
Between the two of us we can probably fix most software problems as long as users stay s-off once s-off!!!
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Definately a great rescue resource. I just want to make sure that folks understand that since it is unsigned,it will do them no good if they are s on,and stuck in bootloader with a security warning.
As you said,they must stay s off to benefit.(further supporting the point of this thread- don't turn s on)
Sent from my HTC PG09410 using Tapatalk 2
I was going to relock/S-On my defective M8 before returning it. I didn't have time though, and ended up just sending back only wiped and un-rooted, although I don't think /system was 100% stock. VZW sent me a text:
VZW FREE MSG: Thank You! The defective device you recently returned has been received by Verizon Wireless.
Click to expand...
Click to collapse
That was several weeks ago, haven't heard a thing since. I'm assuming they didn't care it was unlocked, or they are very slow at processing the devices.
I Relocked my HTC ONE M8 watching this video titled "How to Unroot the HTC One M8 Complete Guide". At the time didn't know "M8 All In One Kit" was block by Verizon but everything seem to go so smooth just like video. When I went back to bootloader to see if "S-OFF" change back to "S-ON" and it did but RADIO and OpenDSP showed "INVALID_VER_INFO", while OS is blank.
I would show a picture of my bootloader but at the time can't because being new user can't post links.
My version is 1.55.605.2
My Recovery: Stock
Here's Bootloader Picture
{
"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"
}
Can anyone give me feedback about my situation?
Heroxgxdeal said:
Can anyone give me feedback about my situation?
Click to expand...
Click to collapse
does it boot?
Sent from my SM-T320 using Tapatalk
Heroxgxdeal said:
I Relocked my HTC ONE M8 watching this video titled "How to Unroot the HTC One M8 Complete Guide". At the time didn't know "M8 All In One Kit" was block by Verizon but everything seem to go so smooth just like video. When I went back to bootloader to see if "S-OFF" change back to "S-ON" and it did but RADIO and OpenDSP showed "INVALID_VER_INFO", while OS is blank.
I would show a picture of my bootloader but at the time can't because being new user can't post links.
My version is 1.55.605.2
My Recovery: Stock
Click to expand...
Click to collapse
Im guessing you may need to RUU... but somewhere I read you need to be SOFF for that...
dottat said:
does it boot?
Sent from my SM-T320 using Tapatalk
Click to expand...
Click to collapse
yes it does
Heroxgxdeal said:
yes it does
Click to expand...
Click to collapse
Ok so from here what are you looking to do ? Sell it? Return it ? Why did you back to a on?
sandm4n said:
Im guessing you may need to RUU... but somewhere I read you need to be SOFF for that...
Click to expand...
Click to collapse
Yeah you need to be S-OFF for RUU, I was wondering if Firewater doesn't work for me anymore because of Radio, etc is missing from bootloader.
dottat said:
Ok so from here what are you looking to do ? Sell it? Return it ? Why did you back to a on?
Click to expand...
Click to collapse
I was going wait for 4.4.3 OTA to come on M8 (Verizon) then sell it to friend, knowing nothing was wrong with the phone.
Heroxgxdeal said:
I was going wait for 4.4.3 OTA to come on M8 (Verizon) then sell it to friend, knowing nothing was wrong with the phone.
Click to expand...
Click to collapse
Try to s off again. There's nothing wrong with you selling it to a friend with it s offed
..Being S-On.. you are stuck in the sense that we do not have a signed RUU for you to flash.
Your best bet is to try to re S-OFF your device, if you are able to do this, you can simply run the RUU, fix your device, and then go back to S-ON.. if you want, and then keep, sell it, what ever.
If you can't get it to S-OFF...
you may be stuck
andybones said:
..Being S-On.. you are stuck in the sense that we do not have a signed RUU for you to flash.
Your best bet is to try to re S-OFF your device, if you are able to do this, you can simply run the RUU, fix your device, and then go back to S-ON.. if you want, and then keep, sell it, what ever.
If you can't get it to S-OFF...
you may be stuck
Click to expand...
Click to collapse
Sorry for the late response, i'll try to re S-OFF my device and tell you if it worked. Wish me luck
andybones said:
..Being S-On.. you are stuck in the sense that we do not have a signed RUU for you to flash.
Your best bet is to try to re S-OFF your device, if you are able to do this, you can simply run the RUU, fix your device, and then go back to S-ON.. if you want, and then keep, sell it, what ever.
If you can't get it to S-OFF...
you may be stuck
Click to expand...
Click to collapse
After doing the Adb method for couple times to get S-off, I had no success. I did get to paste the last command " /data/local/tmp/firewater" few times but it never progress to "Agree to Terms and Conditions you are prompted with" part.
Do you have any tips you can tell me to use adb method/weaksauce method.
Heroxgxdeal said:
After doing the Adb method for couple times to get S-off, I had no success. I did get to paste the last command " /data/local/tmp/firewater" few times but it never progress to "Agree to Terms and Conditions you are prompted with" part.
Do you have any tips you can tell me to use adb method/weaksauce method.
Click to expand...
Click to collapse
Honestly, you have to post way more specifics for us to be able to chime in....
Best would be to take screen shots of your cmd window so we can see the commands you put in and the return.
In lieu of that, post your specific commands, which option in the firewater instructions you followed etc.
The more specific , the better....
I went to S-ON and had the same issue.
What I did was keep the device with S-ON and flashed the firmware.zip from the OTA. Since its signed you can flash it while being S-ON.
This didn't fix it so I decided to send it back to VZW with the invalid version in hboot.
The last thing I wanted to do though was to get the developer options out of settings. So I turned off developer options and then cleared the data on Settings.
So now that developer options was hidden again I just let the device charge to 100%.
I figured I'd check the versions in hboot one last time and to my surprise it was correct.
I'm not sure what fixed it but I went from S-OFF to S-ON with invalid versions displaying to S-ON with valid versions displaying.
berndblb said:
Honestly, you have to post way more specifics for us to be able to chime in....
Best would be to take screen shots of your cmd window so we can see the commands you put in and the return.
In lieu of that, post your specific commands, which option in the firewater instructions you followed etc.
The more specific , the better....
Click to expand...
Click to collapse
Sorry for the late response, this time I got all the way to first bottle open that you can see below. Whats next that I can do?
C:\Android>adb reboot
C:\Android>adb wait-for-device push firewater /data/local/tmp
2625 KB/s (4522136 bytes in 1.682s)
C:\Android>adb shell
[email protected]_m8wl:/ $
C:\Android>adb shell
[email protected]_m8wl:/ $ chmod 755 /data/local/tmp/firewater
chmod 755 /data/local/tmp/firewater
[email protected]_m8wl:/ $ su
su
[email protected]_m8wl:/ # /data/local/tmp/firewater
/data/local/tmp/firewater
==================== firewater S-OFF 8.0.6.26 ===========================
firewater S-OFF comes with NO WARRANTY (express or implied)
and NO GUARANTEE OF FITNESS for any particular task.
We have made every effort we can to make this a safe process for users
however the authors disclaim any liability for damage to your phone
or other materials or devices used during this process.
The entire risk of running firewater S-OFF lies with you, the user.
By using this software you acknowledge and accept that the authors
are not liable for any loss, material or otherwise howsoever caused.
firewater S-OFF may not be rehosted, repackaged, one-clicked, etc.
support is available @ #firewater on the freenode and andirc networks
support is much faster there vs. posting helpme threads on xda etc
Do not operate a motor vehicle after interacting with firewater
Do not inhale firewater or allow firewater to come in contact with eyes
firewater is best served at extremely cold temperatures
firewater has been known to cause temporary lapses in judgement
DO NOT TAUNT FIREWATER, YOU'VE BEEN WARNED
=========================================================================
Do you understand the implications of these warnings?
(Yes/No)
yes
yes
Type 'Yes' or 'No'
(Yes/No)
Yes
Yes
!!If firewater hangs for more than 2 minutes or device enters qhusb mode, ho
!!If firewater hangs for more than 2 minutes or device enters qhusb mode, ho
!!If firewater hangs for more than 2 minutes or device enters qhusb mode, ho
ld power for 60 seconds !!
=========================================================================
preparing, one moment
The first bottle is open
chugging..........
********** whelp, this sucks, firewater can not work on your device **********
********** no amount of reflashing, retrying, or ruuing will fix... **********
********** DO NOT COME TO IRC ASKING FOR UPDATES OR ETAS!!!!!! **********
********** if we are able to fix this issue, it will be announced **********
********** bye bye.....sorry it didn't work out. **********
[email protected]_m8wl:/ #
Heroxgxdeal said:
Sorry for the late response, this time I got all the way to first bottle open that you can see below. Whats next that I can do?
C:\Android>adb reboot
C:\Android>adb wait-for-device push firewater /data/local/tmp
2625 KB/s (4522136 bytes in 1.682s)
C:\Android>adb shell
[email protected]_m8wl:/ $
C:\Android>adb shell
[email protected]_m8wl:/ $ chmod 755 /data/local/tmp/firewater
chmod 755 /data/local/tmp/firewater
[email protected]_m8wl:/ $ su
su
[email protected]_m8wl:/ # /data/local/tmp/firewater
/data/local/tmp/firewater
==================== firewater S-OFF 8.0.6.26 ===========================
firewater S-OFF comes with NO WARRANTY (express or implied)
and NO GUARANTEE OF FITNESS for any particular task.
We have made every effort we can to make this a safe process for users
however the authors disclaim any liability for damage to your phone
or other materials or devices used during this process.
The entire risk of running firewater S-OFF lies with you, the user.
By using this software you acknowledge and accept that the authors
are not liable for any loss, material or otherwise howsoever caused.
firewater S-OFF may not be rehosted, repackaged, one-clicked, etc.
support is available @ #firewater on the freenode and andirc networks
support is much faster there vs. posting helpme threads on xda etc
Do not operate a motor vehicle after interacting with firewater
Do not inhale firewater or allow firewater to come in contact with eyes
firewater is best served at extremely cold temperatures
firewater has been known to cause temporary lapses in judgement
DO NOT TAUNT FIREWATER, YOU'VE BEEN WARNED
=========================================================================
Do you understand the implications of these warnings?
(Yes/No)
yes
yes
Type 'Yes' or 'No'
(Yes/No)
Yes
Yes
!!If firewater hangs for more than 2 minutes or device enters qhusb mode, ho
!!If firewater hangs for more than 2 minutes or device enters qhusb mode, ho
!!If firewater hangs for more than 2 minutes or device enters qhusb mode, ho
ld power for 60 seconds !!
=========================================================================
preparing, one moment
The first bottle is open
chugging..........
********** whelp, this sucks, firewater can not work on your device **********
********** no amount of reflashing, retrying, or ruuing will fix... **********
********** DO NOT COME TO IRC ASKING FOR UPDATES OR ETAS!!!!!! **********
********** if we are able to fix this issue, it will be announced **********
********** bye bye.....sorry it didn't work out. **********
[email protected]_m8wl:/ #
Click to expand...
Click to collapse
You could try the Sunshine method to S-Off your device or you could read through my previous post in this thread.
I had this same issue and somehow was able to get the version info to display correctly.
scuccia said:
You could try the Sunshine method to S-Off your device or you could read through my previous post in this thread.
I had this same issue and somehow was able to get the version info to display correctly.
Click to expand...
Click to collapse
I'm going to try the Sunshine method after I get the $25 payment to pay for the license. I can't flash anymore because i'm on stock recovery, I wanted to know what you meant by
scuccia said:
then cleared the data on Settings.
Click to expand...
Click to collapse
. Do you mean factory reset?
Heroxgxdeal said:
Do you mean factory reset?
Click to expand...
Click to collapse
No, I went into App Manager, opened up the settings application and clicked on clear data. I then let the phone charge to 100%.
I also flashed the firmware.zip RUU from the OTA. You can do this while you're locked and S-On because its signed by HTC.
I have no idea what fixed it but I would try flashing the firmware.zip and then boot up into Android and let it sit for a while.
If that doesn't work then you could try clearing data on Settings and let it sit for a while again. I don't think that will do anything though, that's just what I did.
I'm finally S-OFF again using the Sunshine method,thank you very much to everyone that help me.
Hi there,
I hope someone can help me here. I have a k2u variant at 4.2.2 which is bootloader unlocked through htcdev. I flashed the latest TWRP. Then rooted the phone through flashing the zip for root. So far so good.
But things did not go well when I tried to get S-OFF. I followed the instructions on rumrunner website. Installed the drivers, usb debugging enabled, Su rights given etc. All security, firewalls virus programs disabled.
But when I run the rumrunner, it keeps giving me FATAL: please download updated package at....
I tried it on windows 7, xp and ubuntu. But nothing changes.
Does anyone have any idea where I can go from here to solve this issue.
By the way, I used the latest universal rumrunner package on their website.
You covered almost all point, which come to my mind.
Only thing i think, if you are running stock kernel?
People have the same issue. Its a server issue on rumrunner.us somebody needs to report the issue
Child's Play said:
People have the same issue. Its a server issue on rumrunner.us somebody needs to report the issue
Click to expand...
Click to collapse
@beaups
Can you take a look?
http://forum.xda-developers.com/showthread.php?p=54527533
u can try again now
Child's Play said:
http://forum.xda-developers.com/showthread.php?p=54527533
u can try again now
Click to expand...
Click to collapse
Cool... I will try it when I get back home. Thanks guys...
thearif said:
Cool... I will try it when I get back home. Thanks guys...
Click to expand...
Click to collapse
I guess it is victory... As I see S-OFF İn the bootloader. But it did not go all the way up to pouring 3..... Below is how far it went...
Code:
==================== rumrunner S-OFF 0.5.0 ==============================
rumrunner S-OFF comes with NO WARRANTY (express or implied)
and NO GUARANTEE OF FITNESS for any particular task.
We have made every effort we can to make this a safe process for users
however the authors disclaim any liability for damage to your phone
or other materials or devices used during this process.
The entire risk of running rumrunner S-OFF lies with you, the user.
By using this software you acknowledge and accept that the authors
are not liable for any loss, material or otherwise howsoever caused.
Do you understand the implications of this warning?
(Yes/No)
Yes
Dear User: We will expect that YOU:
(1) Know how to use ADB and FASTBOOT binaries
---- [Yes, use these tools to test USB connection BEFORE running rumrunner] ----
(2) Realize that rumrunner S-OFF cannot support every CUSTOM rom in this world
(3) Understand that irc support IS NOT A GENERAL HELPDESK
(4) Are able to identify and download the CORRECT package for YOUR device
(5) Know how to enable USB-debugging on YOUR device (Yes, do that now)
(6) Understand that you may NOT repack or redistribute rumrunner S-OFF
Ok?
(Yes/No)
Yes
!! Do NOT for any reason taunt, unplug, drop, eat or pet your device !!
Please wait....
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (6/120)
Waiting
Test 2: Booting device
Waiting for ADB (18/120)
must ferment longer...
must sanitize, skunky rum is nasty
hold please..............................................
[************************************************************]
Rebooting into bootloader (again)
Waiting for fastboot (6/120)
Waiting for ADB (18/120)
must ferment longer...
chilling..................
smells lovely in here....
bottles are packed, here we go, shhhhhh....
pouring (1)................
pouring (2)...
WTF: What are you doing?
Also I got this red info text in boot which states I have a built for development purposes or something in that order on the boot splash screen (the first one)
So you think I am good to go???
And thanks again.
If your bootloader states S-off, you are S-off.
This is new info to me. I was unaware that rumrunner worked off a server? Or am I misunderstanding the conversation here?
Sent from my C525c using Tapatalk
You've got it right, it needs a working internet, otherwise it will fail.
It was/is also the case on moonshine, firewater & sunshine.
old.splatterhand said:
You've got it right, it needs a working internet, otherwise it will fail.
It was/is also the case on moonshine, firewater & sunshine.
Click to expand...
Click to collapse
Hahaha, nice I never knew this. Well then, looks like I lucked out back when I first S-Off my device. I just happen to be connected to the internet and didn't even realize it was a necessity .
Sent from my C525c using Tapatalk