HTC Holiday - At&t Vivid
***RELOCKED***
HBOOT-1.85.0024
S-ON RL
CID: CWS_001
Version Installed:
3.26.502.54 710RD
Kernel Version:
3.0.16-gea0e914
[email protected] #1
Baseband:
3.02.4740.14_34.22.701040.19L
Build:
3.25.502.54 CL302737
Issue:
I am trying to return to stock so I can sell this phone. I RELOCKED it using the "fastboot oem relock" and got the famous error message that it failed with "too many links". But it still shows that it is relocked.
When running the RUU with the phone booted it errors out with error 155. When I try and run it through fastboot it just sits on "Sending" and doesn't go anywhere. I had it sit for 12 hours yesterday and it didn't budge.
I've tried these two files, which are the exact same I know...
htc_vivid_att_RUU_3.26.502.56_US.exe
RUU_HOLIDAY_ICS_35_S_Cingular_US_3.26.502.56_Radio_3.02.4740.14_34.22.701040.19_release_246712_signed.exe
I need to re-flash something to it, whenever the damn thing boots up (even after a factory reset) it says "Updating Android". And it says it every time. I can't sell a phone that does that.
I have tried to unlock and lock again. It's been while since I have done this, but I thought it had something to do with the error while re-locking, or the HBOOT version.
I've read some other places that I need to get S-OFF first to be able to return to stock, WTF, unless something has change, I've never had to do that before with this device to return to stock.
**EDIT**
I just tried to go into the recovery to see if there was one still installed and it flashed back to the fastboot screen and now says ***SECURITY WARNING*** under the relock. I have not seen that before.
Squeaky369 said:
HTC Holiday - At&t Vivid
***RELOCKED***
HBOOT-1.85.0024
S-ON RL
CID: CWS_001
Version Installed:
3.26.502.54 710RD
Kernel Version:
3.0.16-gea0e914
[email protected] #1
Baseband:
3.02.4740.14_34.22.701040.19L
Build:
3.25.502.54 CL302737
Issue:
I am trying to return to stock so I can sell this phone. I RELOCKED it using the "fastboot oem relock" and got the famous error message that it failed with "too many links". But it still shows that it is relocked.
When running the RUU with the phone booted it errors out with error 155. When I try and run it through fastboot it just sits on "Sending" and doesn't go anywhere. I had it sit for 12 hours yesterday and it didn't budge.
I've tried these two files, which are the exact same I know...
htc_vivid_att_RUU_3.26.502.56_US.exe
RUU_HOLIDAY_ICS_35_S_Cingular_US_3.26.502.56_Radio_3.02.4740.14_34.22.701040.19_release_246712_signed.exe
I need to re-flash something to it, whenever the damn thing boots up (even after a factory reset) it says "Updating Android". And it says it every time. I can't sell a phone that does that.
I have tried to unlock and lock again. It's been while since I have done this, but I thought it had something to do with the error while re-locking, or the HBOOT version.
I've read some other places that I need to get S-OFF first to be able to return to stock, WTF, unless something has change, I've never had to do that before with this device to return to stock.
**EDIT**
I just tried to go into the recovery to see if there was one still installed and it flashed back to the fastboot screen and now says ***SECURITY WARNING*** under the relock. I have not seen that before.
Click to expand...
Click to collapse
First of all, I must say, THANKS for posting so many details! That makes it much easier to fully understand your issue. I wish everyone would be so concise.
Next, these are errors I have never seen.. This Security Warning is news to me... I wonder if you should maybe try to re-flash the original HBOOT... That is the most risky of all flashes, so I'd maybe wait for someone who has experienced this issue to pipe up before attempting it.
It sounds to me that HBOOT is where your problem lies though. I hope someone else can be of more help on this issue.
ess.boyer said:
First of all, I must say, THANKS for posting so many details! That makes it much easier to fully understand your issue. I wish everyone would be so concise.
Next, these are errors I have never seen.. This Security Warning is news to me... I wonder if you should maybe try to re-flash the original HBOOT... That is the most risky of all flashes, so I'd maybe wait for someone who has experienced this issue to pipe up before attempting it.
It sounds to me that HBOOT is where your problem lies though. I hope someone else can be of more help on this issue.
Click to expand...
Click to collapse
Thank you! I've been around this site for around 4 years now and it's EXTREMELY annoying when searching for answers when someone just posts:
"i cant flash"
Or whatever...
As for the actual issue, that's what I was thinking. There was something awhile back I thought I had read about that version of the HBOOT being an issue. So, hopefully someone around here can help out. I searched for it but I couldn't find anything. So either I am thinking of another phone or it's just lost in the depths of the unknown.
Squeaky369 said:
Thank you! I've been around this site for around 4 years now and it's EXTREMELY annoying when searching for answers when someone just posts:
"i cant flash"
Click to expand...
Click to collapse
Amen to that!
As for the actual issue, that's what I was thinking. There was something awhile back I thought I had read about that version of the HBOOT being an issue. So, hopefully someone around here can help out. I searched for it but I couldn't find anything. So either I am thinking of another phone or it's just lost in the depths of the unknown.
Click to expand...
Click to collapse
I think your best bet may be to just try reflashing the HBOOT. Check Hasoons All-in-one tool kit as I believe it contains the original HBOOT and the one that comes with the S-OFF tools. If it's not there, you should be able to find it somewhere around the forum. Maybe there's a link in the superguide.
Hopefully with a fresh HBOOT, you can get locked, and the RUU will work again. I have flashed the RUU a few times, and each time for me, relocking the bootloader worked fine.
It's worth a whirl.
http://forum.xda-developers.com/showthread.php?t=1416836
SECOND OPTION (PH39IMG.zip flash)
- Put this file for AT&T or this file for Rogers on a microSD card as is (it should be named PH39IMG.zip)
- Power down the phone, insert microSD and boot back into bootloader (power button + vol down)
- It should automatically find the zip file and flash the stock image (this includes recovery, system, everything stock.)
- If you returned to stock because of a bug or issue, and want to root again, make sure to go back and follow the steps PRECISELY to perm root, flash CWM, flash a ROM, flash a kernel, etc. Remember, flash ROM IMMEDIATELY after flashing the kernel
Click to expand...
Click to collapse
ess.boyer said:
Amen to that!
I think your best bet may be to just try reflashing the HBOOT. Check Hasoons All-in-one tool kit as I believe it contains the original HBOOT and the one that comes with the S-OFF tools. If it's not there, you should be able to find it somewhere around the forum. Maybe there's a link in the superguide.
Hopefully with a fresh HBOOT, you can get locked, and the RUU will work again. I have flashed the RUU a few times, and each time for me, relocking the bootloader worked fine.
It's worth a whirl.
Click to expand...
Click to collapse
Ripped the original HBOOT out of the RUU that I had from HTC.
When I try and flash though I get this:
---------------------------------------------------------------------------------------------------------
C:\Android>fastboot flash hboot hboot.nb0
sending 'hboot' (1023 KB)... OKAY [ 0.297s]
writing 'hboot'... FAILED (remote: not allowed)
finished. total time: 0.614s
---------------------------------------------------------------------------------------------------------
I don't need to be S-OFF to flash the HBOOT do I? I unlocked the bootloader again, so that is not what is causing the issue.
Brand New said:
http://forum.xda-developers.com/showthread.php?t=1416836
Click to expand...
Click to collapse
That's the first thread I went through when starting this
I have actually been looking for the PH39IMG.zip file for At&t because that's how I used to do this...
But the file in that link isn't there anymore. It seems that every search I do and find where someone has posted it, it's been removed because of copyright infringement or some other stupid political BS.
Got it.
Created my own PH39IMG.zip using the RUU I got from HTC and got the HBOOT updated and everything returned to stock.
Thank you for the assistance everyone.
Ha! Rocking! Glad you're back up and running.
Squeaky369 said:
Got it.
Created my own PH39IMG.zip using the RUU I got from HTC and got the HBOOT updated and everything returned to stock.
Thank you for the assistance everyone.
Click to expand...
Click to collapse
I am having the exact same issue. Any chance you could share that PH39IMG.zip you made or explain how you did it?
I'll be putting the links up for the PH39IMG.zip in the next hour or so
---------- Post added at 11:36 AM ---------- Previous post was at 11:30 AM ----------
For both AT&T and Rogers Ripped straight from the RUU
So today I turned on my phone and I have noticed that there is about an inch in depth line across the screen which isn't picking up touches anymore, so I rung HTC and it's going in for an in warranty repair on Monday. Of course, I need to convert it completely back to stock, but the only problem is I converted it to a Google Edition, changing the CID and, more importantly, the MID. I followed this thread when doing it originally, but I wanted to know if anyone knows if I can flash the same ENG HBOOT onto my GE phone and not have it brick on me? Then I can change my MID and CID back and flash the EU RUU for my phone and send it in on Monday with no issues...hopefully.
Or is there an easier way? Will they check the MID? I changed it to PN0712000 from PN0710000 and CID to GOOGL001 from HTC__001. If I just changed the CID and left the MID, would it matter? Would I still get OTA's on the stock Sense ROM on that MID?
Thanks in advance.
EDIT: So of course I've tried flashing an RUU in the meantime, but I can't. I've tried 2 of those .exe ones but they both fail, I'm assuming because of my changed model ID. I can't find an unencrypted one either that I can change the headers of so I can flash it...ugh. This is becoming a massive pain the bumholey.
RUU's fail because of MID? I thought if you have s-off any RUU would work? I need to know this too cause I might have to RUU and send in for warranty.
I don't know. But I've gone back to complete stock now, great! Of course, there's another problem FFS.
WiFi now doesn't work at all, it just says error. Fabulous. This only happened once it did a system update to the 1.29 update. Now it's asking me to update to 2.24, but I don't have enough data left on my usage to download it to see if it'll fix it, so now I don't know what to do. I've tried Googling this issue, and it appears as though some people might have had it, but I can't find a solution or anything. HALP!
EDIT: I reflashed the RUU and the WiFi is working again. I'm going to try the update again and see if it causes WiFi to not work again, if so then...I don't know what I'll do. Flash OTA's through CWM and see if it fixes it...?
EDIT2: And this time the WiFi works fine. Something must have happened the first time...but all's working fine now. Hooray! Apart from the screen, which is why I'm sending it back to HTC...
May I ask You how did You manage to go back to stock ROM? I'm on stock 4.3 GE Now. I've got S-OFF and bootloader locked. When I go to the fastboot mode and start the RUU (exe file) goes fine, but half way through (when It's moving the ROM to the internal memory) error shows up saying there are some (no specific details) problems that I can fix, but when I do all 4 fixing steps it doesn't help.
I've taken the stock Sense RUU from here
http://www.androidruu.com/index.php?developer=M7
M7/RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed.exe
I'd love to know how you accomplished this, I've got the same issue going on so I need to revert back to stock using an RUU, but it keeps failing.
can you give us the breakdown of how you did it?
Could somebody please help with a few brief answers in case I mess something up? I'm new to HTC/S-OFF concept.
I bought a used sprint htc one that I wish to return completely to stock in fear previous owner messed something up, and to start from scratch (SU can't install busybox).
The phone has been unlocked, and rooted, no S-OFF, Hboot 1.56 OTA updated to 4.06.651.9 stock. (don't need to edit hboot, or show "locked" again through S-OFF, just normal "relocked", and stock everything else. I know I need to relock bootloader, and stock recovery anyways)
Is an official RUU for 4.06.651.9 (slash .4) the only way to return to stock completely? I don't want/need S-OFF (currently available through Firewire for Sprint on 1.56) unless necessary.
Can I S-OFF, and then S-ON afterwards?
What is the difference between an official RUU vs pushing this stock firmware (4.06.651.9) or .4 through fastboot? Do I need to S-OFF and go to an earlier firmware, and THEN, go to the newest like some people suggest because of the radio?
What has the radio to do with going back to an earlier firmware, and then upgrading?
Is there a way to "freeze" the OTA software upgrade like it's possible on other non HTC devices?
Sorry to bother guys, I have read many threads, but I'm not so clear on these questions
ianthomas said:
Could somebody please help with a few brief answers in case I mess something up? I'm new to HTC/S-OFF concept.
I bought a used sprint htc one that I wish to return completely to stock in fear previous owner messed something up, and to start from scratch (SU can't install busybox).
The phone has been unlocked, and rooted, no S-OFF, Hboot 1.56 OTA updated to 4.06.651.9 stock. (don't need to edit hboot, or show "locked" again through S-OFF, just normal "relocked", and stock everything else. I know I need to relock bootloader, and stock recovery anyways)
Is an official RUU for 4.06.651.9 (slash .4) the only way to return to stock completely? I don't want/need S-OFF (currently available through Firewire for Sprint on 1.56) unless necessary.
Can I S-OFF, and then S-ON afterwards?
What is the difference between an official RUU vs pushing this stock firmware (4.06.651.9) or .4 through fastboot? Do I need to S-OFF and go to an earlier firmware, and THEN, go to the newest like some people suggest because of the radio?
What has the radio to do with going back to an earlier firmware, and then upgrading?
Is there a way to "freeze" the OTA software upgrade like it's possible on other non HTC devices?
Sorry to bother guys, I have read many threads, but I'm not so clear on these questions
Click to expand...
Click to collapse
... oh man so many questions and believe me this is the best way to go by it
long story short you can just factory reset your device and it will be like stock out of the box.
Now though you dont need it but here is the link to RUU if you really wanna do it but it wont make a difference if you are not experiencing any hiccups. but for this RUU to run you need to relock your botloader via fastboot.
http://forum.xda-developers.com/showthread.php?t=2658910
you are in a good position to gain s-off as you are already unlocked so go get it. folow rumrunner.us
if you get s-off 1st then no need to lock your bootloader. RUU runs irrespective of bootloader status if device is s-off.
and yes you can s-on after s-off.
hope this helps ...
Devilish_Angel said:
... oh man so many questions and believe me this is the best way to go by it
long story short you can just factory reset your device and it will be like stock out of the box.
Now though you dont need it but here is the link to RUU if you really wanna do it but it wont make a difference if you are not experiencing any hiccups. but for this RUU to run you need to relock your botloader via fastboot.
http://forum.xda-developers.com/showthread.php?t=2658910
you are in a good position to gain s-off as you are already unlocked so go get it. folow rumrunner.us
if you get s-off 1st then no need to lock your bootloader. RUU runs irrespective of bootloader status if device is s-off.
and yes you can s-on after s-off.
hope this helps ...
Click to expand...
Click to collapse
I really appreciate your help . I'm still a little stuck though. When you say:
"long story short you can just factory reset your device and it will be like stock out of the box."
If by that you mean to Factory Reset through the privacy options of any Android phone, then this is a big NO-NO for me from previous expirience with many other non HTC phones that would soft brick if I did that on a rooted phone. Maybe it works on HTC's, but it seems too easy to be true So I would rather not risk it, and go the RUU way if possible,
"Now though you dont need it but here is the link to RUU if you really wanna do it but it wont make a difference if you are not experiencing any hiccups. but for this RUU to run you need to relock your botloader via fastboot.
http://forum.xda-developers.com/showthread.php?t=2658910"
I was going to try that RUU, even though it's for 4.06.651.4, and I have 4.06.651.9. I was going to assume it works on all 4.0's firmwares on S-ON, and that I need S-OFF to go back to earlier firmwares? The info out there is very vague on this, but since I'm S-ON, I will risk it, since it seems the most I would get out of that in S-ON maybe a softbrick.
"you are in a good position to gain s-off as you are already unlocked so go get it. folow rumrunner.us"
The rumrunner threads seem to say it doesn't work on Hboot 1.56. So far I only read a few threads with people saying only Firewire works on Hboot 1.56, but again, others say it doesn't, and the info it's very vague. I will try S-OFF if I have to though
"and yes you can s-on after s-off."
This one does seem dangerous. The only credible info I found on it was from a popular dev in these threads saying NOT to be quoted about using this command because he wasn't sure either:
fastboot oem writesecureflag 3
Click to expand...
Click to collapse
So the info was vague/unclear again, so I will take a leap of faith with S-OFF if I have to, and report back anything else I find
ianthomas said:
I really appreciate your help . I'm still a little stuck though. When you say:
"long story short you can just factory reset your device and it will be like stock out of the box."
If by that you mean to Factory Reset through the privacy options of any Android phone, then this is a big NO-NO for me from previous expirience with many other non HTC phones that would soft brick if I did that on a rooted phone. Maybe it works on HTC's, but it seems too easy to be true So I would rather not risk it, and go the RUU way if possible,
"Now though you dont need it but here is the link to RUU if you really wanna do it but it wont make a difference if you are not experiencing any hiccups. but for this RUU to run you need to relock your botloader via fastboot.
http://forum.xda-developers.com/showthread.php?t=2658910"
I was going to try that RUU, even though it's for 4.06.651.4, and I have 4.06.651.9. I was going to assume it works on all 4.0's firmwares on S-ON, and that I need S-OFF to go back to earlier firmwares? The info out there is very vague on this, but since I'm S-ON, I will risk it, since it seems the most I would get out of that in S-ON maybe a softbrick.
"you are in a good position to gain s-off as you are already unlocked so go get it. folow rumrunner.us"
The rumrunner threads seem to say it doesn't work on Hboot 1.56. So far I only read a few threads with people saying only Firewire works on Hboot 1.56, but again, others say it doesn't, and the info it's very vague. I will try S-OFF if I have to though
"and yes you can s-on after s-off."
This one does seem dangerous. The only credible info I found on it was from a popular dev in these threads saying NOT to be quoted about using this command because he wasn't sure either:
So the info was vague/unclear again, so I will take a leap of faith with S-OFF if I have to, and report back anything else I find
Click to expand...
Click to collapse
... well you are the 1st one to experience problems after factory reset . usually it happens other way round. i cant remember how many times i have rooted how many phones of how many makes and never ever have i encountered any problems after resets. factory resets are done to rectify any harm done to the device OS by the user, apps, kernels, mods or something else. it brings the phone back to original stock out of the box state.
by the experiences i have with the phones you just need to reset it and if you are really adamant to RUU, you can.
as for the s-off is concerned, there is no harm trying rumrunner or firewater. they do no harm even if they fail. a lot of people including me have gained s-off with hboot 1.56. if rumrunner doesnt work for you try fire water and if that too fails, flash ARHD 41 and then try rumrunner ...
S-OFF - do it!
Devilish_Angel said:
... well you are the 1st one to experience problems after factory reset . usually it happens other way round. i cant remember how many times i have rooted how many phones of how many makes and never ever have i encountered any problems after resets. factory resets are done to rectify any harm done to the device OS by the user, apps, kernels, mods or something else. it brings the phone back to original stock out of the box state.
by the experiences i have with the phones you just need to reset it and if you are really adamant to RUU, you can.
as for the s-off is concerned, there is no harm trying rumrunner or firewater. they do no harm even if they fail. a lot of people including me have gained s-off with hboot 1.56. if rumrunner doesnt work for you try fire water and if that too fails, flash ARHD 41 and then try rumrunner ...
Click to expand...
Click to collapse
Take it from me, one who has replaced his One 3 times- twice being directly my fault, get S-OFF. If I could go back in time and slap younger me in the face, I would. Instead, I will tell you this- get S-OFF. It doesn't take a ton of work, and you will never find a reason to regret it. Plus, RootLinux has an HBOOT flasher in the Development forums if you really want everything to LOOK stock. Once you're S-OFF, you don't have to relock the bootloader to flash an RUU, another perk.
slyest12 said:
Take it from me, one who has replaced his One 3 times- twice being directly my fault, get S-OFF. If I could go back in time and slap younger me in the face, I would. Instead, I will tell you this- get S-OFF. It doesn't take a ton of work, and you will never find a reason to regret it. Plus, RootLinux has an HBOOT flasher in the Development forums if you really want everything to LOOK stock. Once you're S-OFF, you don't have to relock the bootloader to flash an RUU, another perk.
Click to expand...
Click to collapse
... well buddy you quoted the wrong guy . never mind. this is exactly what i was telling him to get s-off to make things easier. appreciate your help though ...
ianthomas said:
Is there a way to "freeze" the OTA software upgrade like it's possible on other non HTC devices?
Sorry to bother guys, I have read many threads, but I'm not so clear on these questions
Click to expand...
Click to collapse
It's my understanding that the OTA only works on bone stock phones.
slyest12 said:
It's my understanding that the OTA only works on bone stock phones.
Click to expand...
Click to collapse
Edited for clarity or the lack there of.
Or bone stock rooted Roms, however you have to flash stock recovery first if s-on, how about with s-off?
Little story to tell:
A day or two ago I got a notification of an ota*.9* to be exact, I tried installing it knowing it wouldn't cause I was rooted. I like to flash back to my stock Rom and update the apps and stuff so I get get the stock feel back without losing much from my daily driver Roms.
Anyways, there is a thread in the forums about installing this update, I tried it and wiped my phone minus the stock Rom, everything was gone even backups. The thread suggested to me to download this app sort of like flashify to flash stock recovery. After flashing stock recovery, well I had or think I had stock recovery cause I had to reinstall twrp, that's when I found out I wiped the heck out of my phone.
I had to start from scratch without a stock Rom cause what ever I did, my stock Rom was borked somehow, everything was gone, I couldn't "repair" missing stuff* like the weather/widget couldn't stick on the home screen. I had to make a sense six Rom my "stock" Rom while gathering more info on RUU and being s-off.
What I thought was this, I'd have to relock boot loader to do a RUU, which I didn't want to do, cause I am thinking I will lose root and have to htcdev again. But I'm s-off'd and now knowing that I won't need to relock bootloader, I have a question.
How do I EXACTLY go about RUU with s-off if I don't have to "oem lock"?
I s-off'd mainly to change boot splash and use a modded hboot to show its "not" rooted, I knew I don't have to htcdev again while s-off, but I was hoping to not come to that point, then this ota thing happened.
Sorry for a long post and prolly going way off topic, but s-off and RUUs or having to flash stock recovery in order to install an ota is confusing to me.
1. Can I RUU without relocking bootloader with s-off?
2. Can I install an ota update without flashing stock recovery with s-off?
3. Last thing, what are the steps to update my stock Rom, while being s-off?
Lol, nice hijack buddy, but it just so happens I have the same question
I got frustrated about a continuous brick while on S-ON, so I decided to S-OFF on my Hboot 1.56, and turns out, only Firewater was able to give me S-OFF. The process was very simple!!!
http://firewater-soff.com/
But even with S-OFF, I still soft brick or get into a bootloader bootloop while trying to install any non stock ROMS:
[Q] Bootloader Bootlopp soft brick on Viper 5.8.0 and other ROMS
I stopped trying more crazy things... I learned no to use TWRP 2.7 in my case, and use older versions, or PhilzTouch, but I still can't figure out how to either OTA update to .9, or install the Viper ROM correctly.
My guess is the same as yours... I shouldn't push a Stock odex ROM through fastboot, or ADB sideload through recovery. Having S-OFF means being able to use the RUU tool WITHIN a stock ROM itself, BUT BEFORE doing so, maybe it's best to flash a stock recovery, or this firmware file:
[Guide][How-to] Run 4.06.651.4 RUU on any windows without any problem..!!
That I guess it's the same found here (MD5 match "Full Firmware from RUU (fastboot flashable)"):
[RUU][Firmware]Sprint HTC One | 4.06.651.4 | Encrypted | Decrypted | Stock Rooted ROM
Anyways, before trying to do any of that, I will try to simply run the RUU from within the stock ROM, and hope the RUU flashes a firmware that contains a stock recovery as well (and maybe more?), so that maybe that's all I need to install the .9 OTA properly through the stock ROM, and after that, try and get the Viper ROM installed properly.
Will report back whatever I can find.
More useful posts:
[Tutorial][Rescue]Sprint HTC One users that flash GSM roms on their CDMA devices.
[ROM] Bad Boyz Sprint ONE ROMz | 4.4.2 | KitKat | Deodexed | myHUB | Updated 2/23/14
[HOW TO] ADB Sideload/Push if you Wipe Internal Storage And have no ROM to Flash
[Tutorial][Resource][Root]Unlock-Recovery-SuperSU for HTC One(M7)-Sprint-m7wls The all in one folder put togheter by BD619 in this post is pretty handy.
EDIT: Actually I will report back in my other question too, since this thread was supposed to be about RUU, and S-OFF, which I resolved through Firewater under Hboot 1.56.
Sorry for the hijack mang!!
Good info here though.
I tried flashing the stock Rom that's on post #2 on the ruu thread but I still get the ota nagging, and data is slow for some reason, that Rom is really wonky for me.
At the moment I'm using a sense 6 Rom and viper Rom 5.8, and data with those are well enough to say I can browse normally on 3g.
Anyways so what is being said is that we would have to just run the ruu though desktop and it should have stock bootloader so we can take the .9 ota. And then after its done we can just flash any custom recovery after that?
Is there really no way to just bypass the its, like how we can bypass hfa?
v1ral said:
Sorry for the hijack mang!!
Good info here though.
I tried flashing the stock Rom that's on post #2 on the ruu thread but I still get the ota nagging, and data is slow for some reason, that Rom is really wonky for me.
At the moment I'm using a sense 6 Rom and viper Rom 5.8, and data with those are well enough to say I can browse normally on 3g.
Anyways so what is being said is that we would have to just run the ruu though desktop and it should have stock bootloader so we can take the .9 ota. And then after its done we can just flash any custom recovery after that?
Is there really no way to just bypass the its, like how we can bypass hfa?
Click to expand...
Click to collapse
... There is a way to bypass hfa if you don't know yet ...
Devilish_Angel said:
... There is a way to bypass hfa if you don't know yet ...
Click to expand...
Click to collapse
I only know about deleting or modifying the "xxxOmad.apks" in the /system/app/ areas. Is there another way?
v1ral said:
I only know about deleting or modifying the "xxxOmad.apks" in the /system/app/ areas. Is there another way?
Click to expand...
Click to collapse
... here you go. download the attached zip file. flash the rom, boot the rom until you see hfa then restart device in recovery and flash the below file. when its done restart the device normally and guess what ???? no hfa ...
slyest12 said:
Take it from me, one who has replaced his One 3 times- twice being directly my fault, get S-OFF. If I could go back in time and slap younger me in the face, I would. Instead, I will tell you this- get S-OFF. It doesn't take a ton of work, and you will never find a reason to regret it. Plus, RootLinux has an HBOOT flasher in the Development forums if you really want everything to LOOK stock. Once you're S-OFF, you don't have to relock the bootloader to flash an RUU, another perk.
Click to expand...
Click to collapse
I forgot to thank you for your advise, which I took, and I don't regret There is a tiny little fine print about this though: " you don't have to relock the bootloader to flash an RUU"... That is not mentioned in the guides I read, and I will try to clarify in my noob post.
v1ral said:
Edited for clarity or the lack there of.
Or bone stock rooted Roms, however you have to flash stock recovery first if s-on, how about with s-off?
Sorry for a long post and prolly going way off topic, but s-off and RUUs or having to flash stock recovery in order to install an ota is confusing to me.
1. Can I RUU without relocking bootloader with s-off?
2. Can I install an ota update without flashing stock recovery with s-off?
3. Last thing, what are the steps to update my stock Rom, while being s-off?
Click to expand...
Click to collapse
It is confusing for me too, but one of my theories was right, and I felt like a dunce once I figured it out, and I think you figured it out too...
Anyways, the HTC one will be for my brother, so I had limited access to it, and finally did more tests on it to figure things out.
I will try and answer your questions to my best of knowledge, but please keep in mind this is a noob/guinea pig point of view that is still asking questions, and I may be wrong on some things, so bear with me, but this has worked for me:
===========================================================================
Being on a Sprint HTC ONE with Hboot 1.56, originally on stock 4.06.651.4 , and S-OFF thanks to Firewater (other methods failed for me). I would recommend getting S-OFF now (to whoever else this may help).
OK v1ral, as far as I know, the ability to flash the 4.06.651.4 RUU WITHOUT having to relock the bootloader is from WITHIN the stock ROM itself, NOT from fastboot or anywhere else.
TIP: When unlocking the bootloader, simply save the .BIN file HTCDEV sends you, and save the command used to unlock for quick unlocking and relocking, just in case.
However you have to flash stock recovery first if s-on, how about with s-off?
You don't have to flash a stock recovery, because the RUU itself does that for you, regardless of S-ON or S-OFF. The only condition is having to relock the bootloader if S-ON BEFORE running the 4.06.651.4 RUU from WITHIN the stock ROM you're in, but obviously that is not necessary if S-OFF.
Can I RUU without relocking bootloader with s-off?
As far as I know, yes. that is the perk of having S-OFF.
Can I install an ota update without flashing stock recovery with s-off?
As far as I know (please correct me), the RUU itself flashes a stock recovery anyways, or at least that's one of the messages it gives while working. Keep reading for the info on how to install the OTA properly in my case.
Last thing, what are the steps to update my stock Rom, while being s-off?
OK, here we go, there is a very important, and easy missing detail nobody mentions in the guides I read, and the reason I was soft bricking with any rom.
How to OTA update from 4.06.651.4 to 4.06.651.9 properly, regardless of being S-ON, or S-OFF, and avoid bootloader bootloop for noobs
First off, If you're already in trouble, and can't install a stock rom, in a bootloop, or don't know how to adb sideload a rom into your device, etc... PM me to try and help you out of it, and start off in a stock room. That may take more time.
Moving on, assuming you're already in a stock rom, or any 'working' rom for that matter, meet these requierements first:
Make sure you never installed HTC Sync before, EVER. Have proper drivers installed, and a correct ADB online connection to your phone is important. I'm just assuming you didn't lazy out, and know how to research the drivers in here already. I just need you to run the command
ADB devices
Click to expand...
Click to collapse
and get a correct online connection between your phone, and PC. Another thing is not to use usb 3.0, or the frontal usb inputs on your PC, and use the back inputs just in case...
And even MORE important tip, is to never... EVER... use cheap low quality or damaged usb cables. I learned this the hard way hard bricking 2 phones in my old LG LGNPST days (LGNPST is another type of flashing tool for LG devices).
Having a damaged usb cable may be really dangerous, specially if your'e S-OFF
Having an al in one folder with the tools to work is pretty convenient, and user BD619 gathered one in his thread
He may not always have the latest version of the TWRP or CWM/PhilzTouch recoveries in it, but you can easily get them in this forum obviously.
TIP: TWRP is the recommended recovery on this device, version 2.7.0.3 didn't work for me, but the new 2.7.0.4 seems better for me, but I still can't mount an OTG drive to it, so you may have to learn how to push/adb sideload ROMs or files into it like this.
OK, from WITHIN your stock ROM, run this 4.06.651.4 RUU first (you only need to relock bootloader prior to running it if you're S-ON):
http://forum.xda-developers.com/showthread.php?t=2658910
It doesn't matter if you're already on firmware 4.06.651.4, run it anyways (it will flash a stock recovery, and more), reboot, and
THEN relock your bootloader, regardless of being S-ON or S-OFF
That was the little detail I was missing, and should've figured out before...
After relocking the bootloader, reboot back in, and THEN, and only then, you can download and install the 4.06.651.9 update from within the Software Update option.
After updating properly to 4.06.651.9, it is then that you can unlock the bootloader back again, flash TWRP, and root with it, or get ROMS already rooted without hiccups.
Finally, if I'm wrong on any of the small details in this, please correct me, but it was what worked for me at least.
Devilish_Angel said:
... here you go. download the attached zip file. flash the rom, boot the rom until you see hfa then restart device in recovery and flash the below file. when its done restart the device normally and guess what ???? no hfa ...
Click to expand...
Click to collapse
Lol, what I meant to put is ota not about hfa.. I have stopped hfa on all the new flashed roms I get by renaming/deleting some files in the system/app.
Does that link work for all roms?
v1ral said:
Lol, what I meant to put is ota not about hfa.. I have stopped hfa on all the new flashed roms I get by renaming/deleting some files in the system/app.
Does that link work for all roms?
Click to expand...
Click to collapse
... It should. Moreover it is far more easy to flash a simple zip than mounting the file system, finding files and then deleting some and renaming some ? ...
So about 6 months ago a friend wanted to root his sprint m8, i had a tmobile one at the time and rooted it and s-off'd it successfully so i did his phone for him, however firewater didn't work for s-off and he didn't want to pay the 25 for sunshine. fast forward to yesterday and he wanted to go back to stock to turn in his phone for an upgrade, so i tried to restore his stock nandroid, but he deleted it. so then i attempted to relock the bootloader and flash the ruu. The ruu failed, and now im stuck in fastboot, twrp is gone, so i can't get a backup restored. I'm hoping their is some other way i can can return his phone to stock. I feel stuck and out of my depth, so i'm hoping someone can help, thanks.
jwalters1123 said:
So about 6 months ago a friend wanted to root his sprint m8, i had a tmobile one at the time and rooted it and s-off'd it successfully so i did his phone for him, however firewater didn't work for s-off and he didn't want to pay the 25 for sunshine. fast forward to yesterday and he wanted to go back to stock to turn in his phone for an upgrade, so i tried to restore his stock nandroid, but he deleted it. so then i attempted to relock the bootloader and flash the ruu. The ruu failed, and now im stuck in fastboot, twrp is gone, so i can't get a backup restored. I'm hoping their is some other way i can can return his phone to stock. I feel stuck and out of my depth, so i'm hoping someone can help, thanks.
Click to expand...
Click to collapse
You say the RUU failed...
Any error message?
As much info as you can give would be better.
Yeah it boots into the black screen with silver htc logo and it starts to run and then the error pops up and says "Error 1555 unknown error the rom update utility cannot update your android phone. please get the correct rom update utility and try again."
jwalters1123 said:
Yeah it boots into the black screen with silver htc logo and it starts to run and then the error pops up and says "Error 1555 unknown error the rom update utility cannot update your android phone. please get the correct rom update utility and try again."
Click to expand...
Click to collapse
Sounds like you are trying to use an older RUU.
The latest can be found here.
http://forum.xda-developers.com/showthread.php?t=2729173
BD619 said:
Sounds like you are trying to use an older RUU.
The latest can be found here.
http://forum.xda-developers.com/showthread.php?t=2729173
Click to expand...
Click to collapse
No, that's where I initially got the first RUU, when it failed i tried to use an older one and the same thing happened. I used this one. http://dl3.htc.com/application/RUU_..._NV_SPCS_1.52_003_release_426232_signed_2.exe Which was the very top one for sprint, non hk. and I locked the bootloader again so it would work.
jwalters1123 said:
No, that's where I initially got the first RUU, when it failed i tried to use an older one and the same thing happened. I used this one. http://dl3.htc.com/application/RUU_..._NV_SPCS_1.52_003_release_426232_signed_2.exe Which was the very top one for sprint, non hk. and I locked the bootloader again so it would work.
Click to expand...
Click to collapse
If the phone is s-on you cannot flash an older RUU.
Make sure you drivers are installed correctly.
Make sure you are using a USB2 port.
Post the info from bootloader please...really just the hboot version.
Post a copy of getvar all also please.
BD619 said:
If the phone is s-on you cannot flash an older RUU.
Make sure you drivers are installed correctly.
Make sure you are using a USB2 port.
Post the info from bootloader please...really just the hboot version.
Post a copy of getvar all also please.
Click to expand...
Click to collapse
ok so hboot version says 3.19.0.0000, i am on a usb 2.0 port, i am not sure how to paste my copied text from the cmd prompt into this box so i just pasted it to a .txt file and attached that and it has all the getvar all info. thanks for the help.
Everything is current according to the getvar...go ahead and remove it as it contains the imei #
The latest RUU should work.
Maybe try downloading Sync Manager to update the drivers or try a different PC/usb port.
Low and behold i was in a 3.0 port lmao... smh... so you just saved me beating my head against the wall for god knows how much longer, thanks for the help, the ruu is working fine now:fingers-crossed: