Related
I have successfully custom flashed Sense 3.0 with 2.3 gingerbread for my incredible S phone. It only took 3 long days. I am very happy but what now? I want this to be my permanent ROM. Is there anything else that I am recommended to do now? I was reading about how you can make your phone almost like a stock phone meaning S-OFF and Unroot. Not too sure if that is necessary. What do you guys think?
please provide more info..
what Custom Rom are you on and how did you flash Sense 3.0.
there's a lot of threads hear and your initial details really don't provide much useful information.
I am on Virtuous Unity 1.27.0 Sense 3.0 based on Pyramid, I flashed it through 4EXTRecovery_v2.1.0_RC1_vivo.
I also had to flash a radio file to my ROM afterwards. I did that through the SDK software. Instructions from here: http://wiki.cyanogenmod.com/wiki/HTC_Incredible_S:_FAQ Here is a list of Radio files for your specific provider/region : http://forum.xda-developers.com/showpost.php?p=12870734&postcount=1
I S-OFF'd my phone through Alpha RevX..there is also a you tube tutorial on how to do it. If anyone has anymore questions on how to do it then msg me!
So now what is left to do?????? Any other procedures? Besides flashing more Roms!
saying the custom rom, radio, cwm would have been enough information. anyways i see that you're new so it's all good.
so the question is, What do you want to do with your phone. after customizing it, are you okay with performance? no bugs? What do YOU want to do with your phone?
I want to permanantly make it my OS. Is that possible? I posted all of that because when I was figuring out how to do this I found that other peoples solutions helped me out alot tee hee
guys I think this belongs in "General"
IncredibleSlover said:
I want to permanantly make it my OS. Is that possible? I posted all of that because when I was figuring out how to do this I found that other peoples solutions helped me out alot tee hee
Click to expand...
Click to collapse
What do you mean 'permanently make it my OS'? That ROM will stay on your phone as long as you want it, until you decide you want to flash a different one. There's no need to go trying to lock it down again after flashing it, that's a pointless exercise.
Dude you're S-OFF and rooted now, there is nothing else to do other than installing custom ROMs or flashing radios(if needed) Virtious Unity is now your ROM, if you want to revert back to what the phone came with, you will need to flash a official RUU.
Awesome thanks for the reply
hussainmushahid said:
Dude you're S-OFF and rooted now, there is nothing else to do other than installing custom ROMs or flashing radios(if needed) Virtious Unity is now your ROM, if you want to revert back to what the phone came with, you will need to flash a official RUU.
Click to expand...
Click to collapse
Hi, I need the S-ON. everywhere let me just advise'll update RUU, but I did and I still have the S-OFF. You know how to solve it? I need back guarantee.
thank you very much.
exnerjan said:
Hi, I need the S-ON. everywhere let me just advise'll update RUU, but I did and I still have the S-OFF. You know how to solve it? I need back guarantee.
thank you very much.
Click to expand...
Click to collapse
you need to go S-ON again? you used alpharevx? If so, just flash the whole official RUU and you will be S-ON again since it would also flash the bootloader.
hussainmushahid said:
you need to go S-ON again? you used alpharevx? If so, just flash the whole official RUU and you will be S-ON again since it would also flash the bootloader.
Click to expand...
Click to collapse
That is a common misconception. Apparently AlphaRevX's HBOOT prevents a RUU from overwriting it. There have been several posts about running an RUU on an AlphaRevX S-OFF IncS and the ROM does indeed update, but the device is still S-OFF and AlphaRevX HBOOT is still in place.
doctorsax said:
What do you mean 'permanently make it my OS'? That ROM will stay on your phone as long as you want it, until you decide you want to flash a different one. There's no need to go trying to lock it down again after flashing it, that's a pointless exercise.
Click to expand...
Click to collapse
Awesome man, thats what I wanted to hear
hussainmushahid said:
Dude you're S-OFF and rooted now, there is nothing else to do other than installing custom ROMs or flashing radios(if needed) Virtious Unity is now your ROM, if you want to revert back to what the phone came with, you will need to flash a official RUU.
Click to expand...
Click to collapse
You mean I wont be able to recover my old settings if I have restored it?
I dont care really if I cant. Is it because I am now 2.3 gingerbread????
Well it doesnt matter because I love this new ROM and will be keeping it forever
uh oh this is bad. no more warranty for my phone :s
tpbklake said:
That is a common misconception. Apparently AlphaRevX's HBOOT prevents a RUU from overwriting it. There have been several posts about running an RUU on an AlphaRevX S-OFF IncS and the ROM does indeed update, but the device is still S-OFF and AlphaRevX HBOOT is still in place.
Click to expand...
Click to collapse
and know how to do it to the S-ON? Please.
tpbklake said:
That is a common misconception. Apparently AlphaRevX's HBOOT prevents a RUU from overwriting it. There have been several posts about running an RUU on an AlphaRevX S-OFF IncS and the ROM does indeed update, but the device is still S-OFF and AlphaRevX HBOOT is still in place.
Click to expand...
Click to collapse
I haven't tried it myself so I guess you're true, when I flashed the stock RUU I flashed it without the bootloader file (unzip,delete,zip) as stated in a thread regarding keeping S-OFF when installing stock RUU. A guy has found the solution to going S-ON again in his thread in the general discussion section.
hussainmushahid said:
I haven't tried it myself so I guess you're true, when I flashed the stock RUU I flashed it without the bootloader file (unzip,delete,zip) as stated in a thread regarding keeping S-OFF when installing stock RUU. A guy has found the solution to going S-ON again in his thread in the general discussion section.
Click to expand...
Click to collapse
Yes I saw that this morning. Basically AlphaRevX has a special HBOOT you can 'downgrade' with that you must flash and then using the special HBOOT you can flash an official HTC HBOOT. End result is S-OFF and you have a standard HTC HBOOT.
Hi all,
I'm having issues trying to restore the latest Telstra RUU and I'm hoping someone will be able to give me a hand with this.
I originally unlocked the bootloader, flashed a CWM recovery, custom ICS ROM, and all was working fine.
I've decided to go back to stock Telstra release but every time I try running the RUU I get an error message saying ERROR [140]: BOOTLOADER VERSION ERROR.
From what I've read, this relates to the bootloader being newer then that included in the RUU. I'm not sure how accurate this is though so if someone could confirm, that would be great. If I do need to downgrade the bootloader, where do I get it from?
The RUU's I've tried flashing are from here: http://www.filefactory.com/f/002b74e0f4775869/
- RUU_HOLIDAY_SENSE3_5_Telstra_WWE_2.27.841.6_Radio_3.01.4720.09_34.06.701020.02_release_231121_signed.exe
- RUU_HOLIDAY_ICS_35_S_Telstra_WWE_3.25.841.4_Radio_3.02.4740.09_34.20.701040.19_release_246698_signed.exe
Neither of these work and both show the same error as indicated above.
HOLIDAY PVT SHIP S-ON RL
HBOOT-1.85.0029
eMMC-boot
Mar 15 2012, 17:16:42
If anyone can provide any assistance getting this phone back to stock Telstra release it would be greatly appreciated. I've been working on it for almost 6-8 hours now and seem to be going around in circles.
Thank you! :good:
You need to relock your boot loader to run an ruu
Sent from my HTC PH39100 using xda premium
Sorry, I forgot to mention that. The bootloader has been relocked.
What hboot do you have currently?
Sent from my HTC PH39100 using xda premium
As above, HBOOT-1.85.0029.
I've managed to flash Velocity² "Nightly Build 5" which is as close to stock as I can get for the time being. Phone is working fine.
I can't seem to find any information at all regarding updating the HBOOT though, and what small information I do come across, it doesn't make a whole lot of sense. I don't even know if 1.85.0029 is the latest. Whether I need to upgrade/downgrade it before the RUU will work which some information I've found seems to suggest.
You shouldn't have to change the hboot to be able to run the ruu. Did you unlock your bootloader again to flash the new Rom?
Sent from my HTC PH39100 using xda premium
I did unlock the bootloader again to flash the new rom, only becasue the RUU wouldn't flash. I've tried flashing the RUU with the bootloader locked and unlocked even though I know it needs to be locked. I've tried flashing the RUU while using both a GB rom and an ICS rom - just incase it makes it difference - it didn't.
I've never had this much trouble flashing an RUU before - it's ridiculous.
You cannot flash an RUU with a lower main version or lower hboot version than what is currently on your phone unless you are S-OFF.
kgs1992 said:
You cannot flash an RUU with a lower main version or lower hboot version than what is currently on your phone unless you are S-OFF.
Click to expand...
Click to collapse
What do you mean by main version?
HBOOT version is 1.85.0029. How can tell if the RUU is lower? If I need to upgrade or downgrade the hboot, where do I find the info on this?
I have read that if the hboot is lower then that of the RUU I wont be able to run it but I could never find any information about how to upgrade/downgrade hboot nor how to tell what version the RUU is.
Nucleotide said:
What do you mean by main version?
HBOOT version is 1.85.0029. How can tell if the RUU is lower? If I need to upgrade or downgrade the hboot, where do I find the info on this?
I have read that if the hboot is lower then that of the RUU I wont be able to run it but I could never find any information about how to upgrade/downgrade hboot nor how to tell what version the RUU is.
Click to expand...
Click to collapse
Main version is the software number.
The one you see in Settings > About > Software Information.
The number should be on the RUU that you downloaded, it's the first set of numbers. for example: 3.25.841.4
How did you go with this, I am in the exact same boat. I want to sell my phone but not with this rom.
I was never able to install the stock Telstra RUU. Could never figure it out. After countless hours and at one stage thinking I'd bricked it, I gave up. I ended up sticking with this ROM (http://forum.xda-developers.com/showthread.php?t=1653317) which hasn't been too bad really.
I would still really love to restore it to factory but in all honesty I don't think it will ever happen.
I managed to extract the boot.img file from the RUU and am having a crack at building the ROM myself. If all is successful I will upload it to my dropbox account and link it.
androidlurv said:
I managed to extract the boot.img file from the RUU and am having a crack at building the ROM myself. If all is successful I will upload it to my dropbox account and link it.
Click to expand...
Click to collapse
That would be awesome. Very interested to know how you get on. :good:
Nucleotide said:
That would be awesome. Very interested to know how you get on. :good:
Click to expand...
Click to collapse
I guess no one ever found out how to fix it? I'm screwed because I can't even flash a new rom as mine cant read my internal_sd
Drunkllamajr said:
I guess no one ever found out how to fix it? I'm screwed because I can't even flash a new rom as mine cant read my internal_sd
Click to expand...
Click to collapse
I was never able to fix it. Still running a custom ROM to this day. I tried for hours to restore the RUU but could never get it to work. :crying:
Nucleotide said:
I was never able to fix it. Still running a custom ROM to this day. I tried for hours to restore the RUU but could never get it to work. :crying:
Click to expand...
Click to collapse
Same here I'm now running Holics 1.3 very similar to stock with some nice addons etc
just s-off and then use that RUU
I can't find the RUU's any more. They have gone from File Factory. I've pretty much given up on trying to restore this to factory. I can't even find up to date information on how to S-OFF - and from memory it's got to be done via hardware hack of some sort? Not real keen on that idea.
That said, I'm looking at flashing CyanogenMod 10 4.1.2 ROM which I'd be more then happy with.
RUU
You might be looking for this http://forum.xda-developers.com/showthread.php?t=2094150&highlight=ruu. I was having the same problem and what I did was find the exact/the same version of the RUU and the version of my phone.
htc one with 2.24.401.2 built and 1.54 hboot
tried flash recovery pulled out from cmw back up
tried 2.24.401.1 ota ruu wwe dint work
getting signature fail always please i wan just unroot
htc one m7 said:
htc one with 2.24.401.2 built and 1.54 hboot
tried flash recovery pulled out from cmw back up
tried 2.24.401.1 ota ruu wwe dint work
getting signature fail always please i wan just unroot
Click to expand...
Click to collapse
I am in exactly the same boat
here is my setup
HBOOT: 1.54.0000
OS: 2.24.401.1
Looking for the correct RUU to flash. any help is appreciated
winwiz said:
I am in exactly the same boat
here is my setup
HBOOT: 1.54.0000
OS: 2.24.401.1
Looking for the correct RUU to flash. any help is appreciated
Click to expand...
Click to collapse
this will be my last and first HTC to root
i had gs3 i flash a home rom any second i wanted im searching for that RUU from 1 month ago i dint find it
htc customer services and htc dev both sucks
htc one m7 said:
this will be my last and first HTC to root
i had gs3 i flash a home rom any second i wanted im searching for that RUU from 1 month ago i dint find it
htc customer services and htc dev both sucks
Click to expand...
Click to collapse
I realised that I took a nandroid backup of the original firmware, so I have been successful in returning to stock.
When I boot to the bootloader, I see TAMPERED AND UNLOCKED. I guess this is to to a custom recovery and also unlocked bootloader. Any ideas how I can get this back to normal? Am I then back to stock fully?
winwiz said:
I realised that I took a nandroid backup of the original firmware, so I have been successful in returning to stock.
When I boot to the bootloader, I see TAMPERED AND UNLOCKED. I guess this is to to a custom recovery and also unlocked bootloader. Any ideas how I can get this back to normal? Am I then back to stock fully?
Click to expand...
Click to collapse
me i have my stuck rom running also nandroid pulled by cmd
but no chance for me
There is NO way for you to remove the tampered flag or change relocked to locked if you are on Hboot 1.54, no S-Off available which is what you need. If you are on a lower Hboot then you can S-Off and remove the flag and return to 100% stock.
There are also NO 2.24 RUU's so don't bother trying to find one.
It amuses me that somebody would never buy another HTC phone because they don't know what to do. Other phones can be unlocked , rooted, flashed, by pure noobs who don't know what they're doing. The One requires you to learn a little and do some reading to know what to do, when you've done that you'll find it isn't hard at all.
Why are you so desperate to go back to stock? If you just want the stock experience, flash a stock rom.
If you're trying to hide the fact that you rooted and unlocked in order to return/sell it, you can't really complain that you're having problems trying to deceive people. Sorry.
Had either of you done any research and reading prior to rooting, your problems would have been apparent.
AllAboutTheCore said:
There is NO way for you to remove the tampered flag or change relocked to locked if you are on Hboot 1.54, no S-Off available which is what you need. If you are on a lower Hboot then you can S-Off and remove the flag and return to 100% stock.
There are also NO 2.24 RUU's so don't bother trying to find one.
It amuses me that somebody would never buy another HTC phone because they don't know what to do. Other phones can be unlocked , rooted, flashed, by pure noobs who don't know what they're doing. The One requires you to learn a little and do some reading to know what to do, when you've done that you'll find it isn't hard at all.
Click to expand...
Click to collapse
thanks next time when i need a root i will get s-off before that .now my chance is getting s-off wich is not available now
if u dint tell me dont search i would search for ever XD
iElvis said:
Why are you so desperate to go back to stock? If you just want the stock experience, flash a stock rom.
If you're trying to hide the fact that you rooted and unlocked in order to return/sell it, you can't really complain that you're having problems trying to deceive people. Sorry.
Had either of you done any research and reading prior to rooting, your problems would have been apparent.
Click to expand...
Click to collapse
i just want to get updates from htc
AllAboutTheCore said:
There is NO way for you to remove the tampered flag or change relocked to locked if you are on Hboot 1.54, no S-Off available which is what you need. If you are on a lower Hboot then you can S-Off and remove the flag and return to 100% stock.
There are also NO 2.24 RUU's so don't bother trying to find one.
It amuses me that somebody would never buy another HTC phone because they don't know what to do. Other phones can be unlocked , rooted, flashed, by pure noobs who don't know what they're doing. The One requires you to learn a little and do some reading to know what to do, when you've done that you'll find it isn't hard at all.
Click to expand...
Click to collapse
Noobs are what this thread is for. Why are you flaming and complaining in a Q&A thread anyway? If you're not going to help, get out of the way and flame on elsewhere.
htc one m7 said:
i just want to get updates from htc
Click to expand...
Click to collapse
Then you should've left the phone stock
htc one m7 said:
htc one with 2.24.401.2 built and 1.54 hboot
tried flash recovery pulled out from cmw back up
tried 2.24.401.1 ota ruu wwe dint work
getting signature fail always please i wan just unroot
Click to expand...
Click to collapse
Try a factory reset, but don't use the backup to restore settings. It might be a hassle, but it should uninstall SU, and if you don't restore those settings, it should be unrooted. Just go to play store and reinstall the apps you had before. They should be saved under your account. I hope this helps.
Edit: Another possibility would be to install an all in one toolkit, and have that unroot the phone for you. I'm not 100% sure it would work with 1.54, though. There are two good ones here and here.
Edit: Yet another possibility would be to flash hboot 1.44 and then run the RUU again.
Edit: Finally, have you tried unrooting through the SU app itself?
kibmikey1 said:
Try a factory reset, but don't use the backup to restore settings. It might be a hassle, but it should uninstall SU, and if you don't restore those settings, it should be unrooted. Just go to play store and reinstall the apps you had before. They should be saved under your account. I hope this helps.
Edit: Another possibility would be to install an all in one toolkit, and have that unroot the phone for you. If you used the revone method to root, it should take care of it. I'm not 100% sure it would work with 1.54, though. There are two good ones here and here.
Edit: Yet another possibility would be to flash hboot 1.44 and then run the RUU again.
Click to expand...
Click to collapse
I've personally managed to get it back to stock, and even got an OTA update. The only issue I have is that in the bootloader it's saying TAMPERED and RELOCKED
I guess there is not much I can do about this,
Any above all, thank you for your help. You have been helpful unlike the others with a snobbish attitude
winwiz said:
I've personally managed to get it back to stock, and even got an OTA update. The only issue I have is that in the bootloader it's saying TAMPERED and RELOCKED
I guess there is not much I can do about this,
Any above all, thank you for your help. You have been helpful unlike the others with a snobbish attitude
Click to expand...
Click to collapse
You could run the all in one toolkit and remove the tampered and relocked flags.
---------- Post added at 02:06 AM ---------- Previous post was at 01:17 AM ----------
iElvis said:
Why are you so desperate to go back to stock? If you just want the stock experience, flash a stock rom.
If you're trying to hide the fact that you rooted and unlocked in order to return/sell it, you can't really complain that you're having problems trying to deceive people. Sorry.
Had either of you done any research and reading prior to rooting, your problems would have been apparent.
Click to expand...
Click to collapse
This thread is open for questions like these. Flame on elsewhere.
kibmikey1 said:
Try a factory reset, but don't use the backup to restore settings. It might be a hassle, but it should uninstall SU, and if you don't restore those settings, it should be unrooted. Just go to play store and reinstall the apps you had before. They should be saved under your account. I hope this helps.
Edit: Another possibility would be to install an all in one toolkit, and have that unroot the phone for you. I'm not 100% sure it would work with 1.54, though. There are two good ones here and here.
Edit: Yet another possibility would be to flash hboot 1.44 and then run the RUU again.
Edit: Finally, have you tried unrooting through the SU app itself?
Click to expand...
Click to collapse
unrooting thrrough su app dint work and that tool kit s wont work for 1.54 hboot im so unlucky
htc one m7 said:
unrooting thrrough su app dint work and that tool kit s wont work for 1.54 hboot im so unlucky
Click to expand...
Click to collapse
If your phone was 2.24 out of the box and you never went s-off, you don't need a ruu because your firmware would not have changed. So you just need to restore stock recovery and stock system files, then relock. Flash a stock rom, flash stock recovery in fastboot, and unroot through the superuser app. Then relock in fastboot.
The AIO toolkits will not help with relocked and tampered on 1.54 because they require s-off, which is not available on that hboot. Also, factory reset won't unroot you; it may remove the superuser.apk but will not remove root access.
kibmikey1 said:
Noobs are what this thread is for. Why are you flaming and complaining in a Q&A thread anyway? If you're not going to help, get out of the way and flame on elsewhere.
Click to expand...
Click to collapse
Who's flaming and complaining, and I did help ... I wouldn't help you now but that's another story. As for noobs, If you can't be bothered to read and search then that says something about you. For starters, even though you were wrong (and not the OP) I did help, I have also spent more time helping on here than I have posting anything else, so if you don't like it, you know what you can do.
You might want to give correct advice aswell, if he's on Hboot 1.54 then he'd need S-Off to flash an older Hboot, which he cannot do. Thanks
iElvis said:
If your phone was 2.24 out of the box and you never went s-off, you don't need a ruu because your firmware would not have changed. So you just need to restore stock recovery and stock system files, then relock. Flash a stock rom, flash stock recovery in fastboot, and unroot through the superuser app. Then relock in fastboot.
The AIO toolkits will not help with relocked and tampered on 1.54 because they require s-off, which is not available on that hboot. Also, factory reset won't unroot you; it may remove the superuser.apk but will not remove root access.
Click to expand...
Click to collapse
when i red your reply it seemed too easy but no
stuck recovery when you mean that ''fastboot flash recovery recovery.img'' pulled from nandroid back up ? yes ur right i manged to do that it was succesful but no change even a systim rom is not available getting signature failure 'seems promising yah
i know my thing is hard but it shouldnt be like that right im runing a rom now 4.3 im fine with it but i really want to F*** htcdev members :v
I mean stock recovery, which you can pull from the firmware file for your phone. Find the recovery.img file in the zip and use that.
Stop trying to flash ruus and firmware packages in fastboot; you may screw up your phone doing it.
Just get a stock rom that correspond to the firmware package from the development forum and flash in custom recovery. Then flash the stock recovery in fastboot. Once that's done, you should be able to get OTAs.
iElvis said:
I mean stock recovery, which you can pull from the firmware file for your phone. Find the recovery.img file in the zip and use that.
Stop trying to flash ruus and firmware packages in fastboot; you may screw up your phone doing it.
Just get a stock rom that correspond to the firmware package from the development forum and flash in custom recovery. Then flash the stock recovery in fastboot. Once that's done, you should be able to get OTAs.
Click to expand...
Click to collapse
if you want to help me help me now
i have my reovery.img and it flashes perfectly
how to get stuck rom ?
you mean the file with date it is bout 1.8GB named 2013-08-27.19.58.35 that i should put it in supfic folder do i can flash it with recovery cwm ?
since i have my back up and since it is S-on i wont mind flashing any thing
Hey all , minutes ago the 4.4 update was downloaded via OTA on my converted GPE htc one. I pressed install and when it went to recovery i get the error message "set metadata recursive" error , and the device dosnt even boot anymore. Any ideas what might be the problem ?
Izzymane said:
Hey all , minutes ago the 4.4 update was downloaded via OTA on my converted GPE htc one. I pressed install and when it went to recovery i get the error message "set metadata recursive" error , and the device dosnt even boot anymore. Any ideas what might be the problem ?
Click to expand...
Click to collapse
Sounds like you have a custom recovery? If so try stock GE recovery
Sent from my HTC One using Tapatalk
Nah I have the android guy with a red exclamation mark
Wow.. That's a lot of people with same issue.
SaHiLzZ said:
Wow.. That's a lot of people with same issue.
Click to expand...
Click to collapse
I have the exact same problem. I can get into the stock recovery but my device is not recognized in fastboot or adb
I got the same error when attempting to sideload 4.4 on my phone which I had previously converted to 4.3 GPE (rooted) using the instructions in the developer's forum. Guess it's time to do a full reflash.
I guess doing a full reflash is not gonna fix it. I would suggest flashing the stock recovery again and give it another shot.
Izzymane said:
I guess doing a full reflash is not gonna fix it. I would suggest flashing the stock recovery again and give it another shot.
Click to expand...
Click to collapse
are you guys s-on or s-off, newest 4.4 seems to bootloop with S-On devices!!
nkk71 said:
are you guys s-on or s-off, newest 4.4 seems to bootloop with S-On devices!!
Click to expand...
Click to collapse
I'm s-off with rumrunner
Then why not flash the full 4.4 RUU zip from GPE conversion thread?
SaHiLzZ said:
Then why not flash the full 4.4 RUU zip from GPE conversion thread?
Click to expand...
Click to collapse
True but I prefer OTA's , they just make more sense
Izzymane said:
I'm s-off with rumrunner
Click to expand...
Click to collapse
seems like lots of issues with 4.4,
from @makbil:
It seems only s-off, 4.4 compatible recovery and a clean flash are required. If all 3 are not met -> bootloop
Click to expand...
Click to collapse
EDIT: just noticed you're supposed to be 100% stock (converted), so the above quote shouldnt apply to you, i guess, sorry
could someone list the correct things to do to make a clean conversion?
thnaks
I'm also S-off with rumrunner, H-boot 1.54.
Flashed the RUU for 4.4 and all is fine. Luckily I backed up the data I cared about beforehand, just in case.
HTC ONE (M7) Sprint
hboot 1.57
s-on
unlocked
recently used guru reset to go back to stock rom, worked fine until I tried to update the phone and get stuck on boot screen. loaded up twrp again and sideloaded another guru reset... did the same thing, worked until i did an update and gets stuck at boot screen when update is complete.
What kind of update are you talking about?
Sent from my HTC One using Tapatalk
ota android update
OTAs don't work with TWRP.. But I'm really not sure what is going on with your phone. Maybe just flash a ROM that's already up to date?
Sent from my HTC One using Tapatalk
guru reset installs stock rom and recovery. used the latest one available. right now i'm just going to try to get s-off and run a ruu.
Just tried again one more time to see... it seems to take the first update just fine, and only bricks on update 4.06.651.9
Mud3 said:
Just tried again one more time to see... it seems to take the first update just fine, and only bricks on update 4.06.651.9
Click to expand...
Click to collapse
What is your fastboot getvar all (minus serial no and imei)
What guru reset have you been using?
Did you ever fix this, I am having the same problem.
bigpedro36 said:
Did you ever fix this, I am having the same problem.
Click to expand...
Click to collapse
The reason it fails is because the guru reset is too old, it doesn't contain major system files, only radio and recovery plus the Rom zip file, therefore your hboot remains on the latest, probably 1.57, now when the ota comes and tries to update your hboot to 1.56 from the old Rom files that the reset put on there, it fails because you can't back flash an s-on device, s-off is the only answer unless you can find a newer reset Rom.
My HBoot is actually 1.6.. and im having trouble finding anything that will make 1.6 into s-off .
bigpedro36 said:
My HBoot is actually 1.6.. and im having trouble finding anything that will make 1.6 into s-off .
Click to expand...
Click to collapse
Have you tried sunshine s-off ? Not sure if it supports 1.6 yet though but it's worth a try, you only pay if it can s-off your phone after its run some tests. But that's my point, your on the latest hboot and the ota files are assuming you on something like 1.54 (estimate) and trying to update it, fails because you already have a newer hboot.
Seanie280672 said:
Have you tried sunshine s-off ? Not sure if it supports 1.6 yet though but it's worth a try, you only pay if it can s-off your phone after its run some tests. But that's my point, your on the latest hboot and the ota files are assuming you on something like 1.54 (estimate) and trying to update it, fails because you already have a newer hboot.
Click to expand...
Click to collapse
Cool I got S-off now. I'm trying to OTA again and will go from there.
bigpedro36 said:
Cool I got S-off now. I'm trying to OTA again and will go from there.
Click to expand...
Click to collapse
Not sure if the ota will work, you may have to just grab a full Sprint ruu and just run that which will back flash everything.
Seanie280672 said:
Not sure if the ota will work, you may have to just grab a full Sprint ruu and just run that which will back flash everything.
Click to expand...
Click to collapse
The OTA worked.. Thanks a ton.. you explained exactly what the problem was.