Database Develop

[Q] Cant flash 3805.06.03.03_M radio

Hi, I cant get this radio to flash on my mates Inc S (it worked fine on mine). He has s-off (xtc clip method), latest recover, root etc, but when I flash using PG32IMG hboot method I get 'Incorrect model ID' or something like that. Also tried same thing using a goldcard. Also tried fastboot method as per post 1 ARHD1.1.0 thread. No success
Any ideas please ?

gudge said:
Hi, I cant get this radio to flash on my mates Inc S (it worked fine on mine). He has s-off (xtc clip method), latest recover, root etc, but when I flash using PG32IMG hboot method I get 'Incorrect model ID' or something like that. Also tried same thing using a goldcard. Also tried fastboot method as per post 1 ARHD1.1.0 thread. No success
Any ideas please ?
Click to expand...
Click to collapse
If this is a Candanian IncS, then the model id in the PG32IMG.Zip file needs to be changed.
http://forum.xda-developers.com/showthread.php?t=1145246

tpbklake said:
If this is a Candanian IncS, then the model id in the PG32IMG.Zip file needs to be changed.
http://forum.xda-developers.com/showthread.php?t=1145246
Click to expand...
Click to collapse
Actually its a UK device, but only about a week or so out of the shop, unlike mine which is a few months old and an older hboot version . The engineering hboot in the link you mentioned may be the answer, thanks for the pointer.
Cheers

If you use alpharevx for S-OFF maybe this post can help you installing new radio :
[GUIDE] How to flash a radio [for Alpharevx S-OFF]

Neolight78 said:
If you use alpharevx for S-OFF maybe this post can help you installing new radio :
[GUIDE] How to flash a radio [for Alpharevx S-OFF]
Click to expand...
Click to collapse
thanks, the link is also to ENG hboot, I think this will be the answer, will try it and post back outcome.
Thanks all for the guidance.

find out one method in ARHD 1.1.0,dload the radio file,open and read it.

Guys be careful when flashing radios, because i flashed 6.03.03 from gu1dry's thread and then tried to run a lower version ruu and broke the software on the phone. Now i need to use xtc clip to revive.
post by ieftm
"gu1dry, could you please adjust your RUU zips to include a lower mainversion?
preferably something really low like 1.00.0000.0.
Some of these zips have:
mainver: 2.21.1400.8
Which might spell trouble for people that attempt at flashing a RUU afterwards (as they're left with a broken RUU and a high mainversion).
Thanks"
Just make sure you ask all q's before playing with stuff like this it will avoid what i am facing. Just want to help

neo-X, pitty your on the other side of the world, you could have borrowed mine. Thanks for the warning though, I think I will re flash the new radio using the link from post 1 of ARHD to be safe.

Resolved my mates problem by flashing ENG hboot, then the new radio flashed ok. I don't understand why it was necessary to do this ENG hboot thing, since I did not have this problem with my own inc s. Must be something to do with latest stock hboot I guess. One other word of warning, after installing the ENG hboot his phone would not boot past the first HTC boot screen, but was able to go into custom recovery, wipe then flash ARHD rom, then booted up all OK.

Thanks gudge...luckily i got it working, just needed to flash the new higher version ruu that was just released
Sent from my HTC Incredible S using XDA Premium App

A system update is available

Hi guys
I have the Sensation and the Flyer so these days I was too busy trying to S-OFF them and to gain perm root. (no luck yet) During this time my Incredible S was turned off this means I have been away from my Incredible S for a month now.
Today I turned my Incredible S on and I saw that there is a new System update :
A SYSTEM UPDATE IS AVAILABLE
SYSTEM UPGRADE 2.30.405.1 (30.17MB)
My Incredible S has been S-OFF`ed since April by XTC CLIP and I have been on the stock Rom due to some errors on the customs roms like ( no harware backlight etc.)
My question is if I apply this update will I loose my S-OFF ?
Secondly If I loose S-OFF will XTC CLIP bring my S-OFF again ?
Thanks
DC

I got that this morning.... but then it vanished when i checked again

i think if you're s-off already you won't lose it. and you have the xtc clip anyways, worse comes to worst you can use it again.
i read that if you upgrade to this versoin on stock and try alpharevx, you won't be able to s-off it

i dont "think", i am 100% sure you will not lose your s-off
why? cuz i have tested every possible way to s-on again my phone..including OTA...

You will lose your S-off only when you overwrite bootloader.
I s-off my phone using AlphaRev but wanted to test a few things in full stock so installed my stock GB RUU to S-on my phone again.
After that I S-off again.
It will not s-on unless you run an RUU and overwrite bootloader. Even if you get it s-on accidentaly there its possible to s-off from any state So you shouldn't have any problem installing this OTA. This OTA doesn't have a bootloader (I assume you already on GB ). Froyo to GB OTA had a new bootloader in it.
Let me know if you face any problem s-offing and I'll assist you.
Sent from my HTC Incredible S using XDA App

ehsan76 said:
You will lose your S-off only when you overwrite bootloader.
I s-off my phone using AlphaRev but wanted to test a few things in full stock so installed my stock GB RUU to S-on my phone again.
After that I S-off again.
It will not s-on unless you run an RUU and overwrite bootloader. Even if you get it s-on accidentaly there its possible to s-off from any state So you shouldn't have any problem installing this OTA. This OTA doesn't have a bootloader (I assume you already on GB ). Froyo to GB OTA had a new bootloader in it.
Let me know if you face any problem s-offing and I'll assist you.
Sent from my HTC Incredible S using XDA App
Click to expand...
Click to collapse
The OP has a XTC Clipped IncS that is S-OFF. This is not dependent on a patched HBOOT like AlphaRevX is; this is Radio S-OFF and will not be affected, even by running a RUU.

Ok I did the update but ,
I am getting an error installing the update 2.30.405.1
My current software is 2.12.405.7
Here is the video of the error .....
http://www.youtube.com/watch?v=mc8DPq6XlkA
Any ideas why ?
Maybe I might have installed another region RUU in April, but can't remember now.

doublecheese said:
Ok I did the update but ,
I am getting an error installing the update 2.30.405.1
My current software is 2.12.405.7
Here is the video of the error .....
http://www.youtube.com/watch?v=mc8DPq6XlkA
Any ideas why ?
In order to install the OTA, you need to replace ClockworkMod recovery with the recovery.img file from the 2.12.405.7 ROM.zip.
Maybe I might have installed another region RUU in April, but can't remember now.
Click to expand...
Click to collapse
I tried this last night and actually got a progress bar and it got about 1/3 of the way and then I got a red triangle with a !. I know that the radio I have installed is newer than the one in the 2.12.405.7 ROM.zip, so that may be my problem. Anyway, I'm going to pass on the OTA and just go ahead and flash the 2.30 ROM.zip using ClockworkMod instead.

tpbklake said:
The OP has a XTC Clipped IncS that is S-OFF. This is not dependent on a patched HBOOT like AlphaRevX is; this is Radio S-OFF and will not be affected, even by running a RUU.
Click to expand...
Click to collapse
^^
This
RADIO S-OFF via XTC Clip is permanent as of right now.
AlphaRevX S-OFF method is reversible with a RUU.

tpbklake said:
The OP has a XTC Clipped IncS that is S-OFF. This is not dependent on a patched HBOOT like AlphaRevX is; this is Radio S-OFF and will not be affected, even by running a RUU.
Click to expand...
Click to collapse
doublecheese said:
Ok I did the update but ,
I am getting an error installing the update 2.30.405.1
My current software is 2.12.405.7
Here is the video of the error .....
http://www.youtube.com/watch?v=mc8DPq6XlkA
Any ideas why ?
Maybe I might have installed another region RUU in April, but can't remember now.
Click to expand...
Click to collapse
@tpbklake: Sorry I don't have any idea how XTC chip works as I bought Incredible S after a software s-off method had been confirmed
@doublecheese: Download the WWE_2.30.405.1 RUU from this link and try running it directly from your PC or use this guide to install it from boot-loader. Don't forget to take a Nandroid backup before upgrade
You wont need GoldCard in your case as you have WWE Incredible S and you are installing a WWE Rom on it
Hope this will help
Ehsan

You can't do ota updates when you have a custom recovery installed..

Guten tag Madmaxx82
If I just flash the WWE 2.30.405.1 RUU instead , would I loose my S-OFF ?
Sorry man it's been quite time I don't follow the IS forums.

yesterday i did updates into new version, nothing special, only my phone performance bit faster. and battery performance is same for me. but i think updates are always worthwhile.

doublecheese said:
Guten tag Madmaxx82
If I just flash the WWE 2.30.405.1 RUU instead , would I loose my S-OFF ?
Sorry man it's been quite time I don't follow the IS forums.
Click to expand...
Click to collapse
Since you are S-OFF'd using the XTC Clip, you will be safe to flash the 2.30 RUU and still have S-OFF after the process.

tpbklake said:
Since you are S-OFF'd using the XTC Clip, you will be safe to flash the 2.30 RUU and still have S-OFF after the process.
Click to expand...
Click to collapse
Thanks man if Ioose S-OFF. I'll XTC CLIP it again anyway .....

Im S-OFF with a XTC-Clip and is running stock 2.12.405.7 ROM.
Can anybody confirm 100% that i don't loos S-OFF if i upgrade to 2.30.405.1?
Im a bit nervous becaus i don't have access to a XTC-Clips any more.

jkolner said:
Im S-OFF with a XTC-Clip and is running stock 2.12.405.7 ROM.
Can anybody confirm 100% that i don't loos S-OFF if i upgrade to 2.30.405.1?
Im a bit nervous becaus i don't have access to a XTC-Clips any more.
Click to expand...
Click to collapse
I took the 2.30.405.1 RUU and extracted the ROM.zip and then made a rooted ROM using the HTC Android Kitchen and flashed that on my clipped Inc S, so now I'm running GB 2.30.405.7 and still S-OFF. You can always go that route if you don't want to risk running the stock RUU.

jkolner said:
Im S-OFF with a XTC-Clip and is running stock 2.12.405.7 ROM.
Can anybody confirm 100% that i don't loos S-OFF if i upgrade to 2.30.405.1?
Im a bit nervous becaus i don't have access to a XTC-Clips any more.
Click to expand...
Click to collapse
I own my own XTC CLIP and a S-OFF Incredible S , I can confirm that you will NOT loose S-OFF after the OTA . How I know ? Because I did the risk and apply the OTA myself ... But S-OFF remains there solid as rock !!!!
But you will loose your root and then you have to do what EHSAN76 suggested to me....... This is how I get my IS rooted again.
HERE IS THE LINK TO THAT THREAD

[Q] Unable to install latest Telstra RUU

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.

[Q] going to stock fail... need 2.24.401.1 nandroid

I got myself in a bit of a dead zone here.
I have my HTC one. Its HTC__001 WWE Europe. It OTA upgraded to 2.24.401.1.
When I saw that you can convert to a GPE I really wanted to check it out specially after users reported success in getting OTA updates. But I quickly realized I needed S-Off and thats not available yet.
I decided to at least take it to a test drive with ARHD GPE 3.0. I downloaded the latest RUU for my device (1.28.401.7) thinking I would need that to get back to stock. I went and unlocked the bootloader at HTC dev. Flashed CWM recovery and flashed ARHD GPE 3.0. Played around with it for a bit and now when I needed to go back to stock.
RUU.exe file got stuck at updating signature then returned 155 unknown. I realized maybe its attempting to downgrade the bootloader so i looked around for a 2.24.401.1 RUU but its not available yet.
I looked at Nandroid backups and found 1.28.401.7 HTC__001 but its UK unbranded. When I restored this version it loaded up but my touch screen didnt work at all. I flashed back ARHD to get touch capability back.
So my question is... Any chance anyone can nandroid backup the stock 2.24.401.1 i need? How can I go to stock now? Am I stuck with custom roms untill atleast s-off or HTC decides 2.24.401.1 RUU should be made available?
Thanks!

+1

Are you s off?? Downgrade your hboot to 1.44 and then flash the ruu for your device....
Sent from my HTC One using xda premium

No unfortunately im s-on... Funny how being a good boy and being s-on HTC rewards me with no option to go back to stock...
Sent from my HTC One using xda app-developers app

LOL............ I am in same postion . want to go back to stock for updates but cant !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

http://forum.xda-developers.com/showthread.php?t=2224752 ... Flash ROM, install stock recovery, relock bootloader, done. The official firmware will be about soon no doubt so you will be able to fastboot it and have the newest base, stock and all before HTC release it in whatever region.
Obviously you'll need S-Off for Hboot 1.54 if/when it happens in order to remove the tampered flag and change relocked back to locked but what I mentioned above is the closest you'll get without being able to run an RUU.

AllAboutTheCore said:
http://forum.xda-developers.com/showthread.php?t=2224752 ... Flash ROM, install stock recovery, relock bootloader, done. The official firmware will be about soon no doubt so you will be able to fastboot it and have the newest base, stock and all before HTC release it in whatever region.
Obviously you'll need S-Off for Hboot 1.54 if/when it happens in order to remove the tampered flag and change relocked back to locked but what I mentioned above is the closest you'll get without being able to run an RUU.
Click to expand...
Click to collapse
You cant s-off on hboot 154 yet. Unless I am mistaken.
Like op says we need a nandroid of firmware think that's only way until ruu is releasee ; (
Sent from my GT-I9100 using xda app-developers app

ipmanwck said:
You cant s-off on hboot 154 yet. Unless I am mistaken.
Like op says we need a nandroid of firmware think that's only way until ruu is releasee ; (
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
2 things:
1) I'll quote what I said, I never said S-Off was available .. "Obviously you'll need S-Off for Hboot 1.54 if/when it happens"
2) What I said above for going to stock is a way of doing it, a Nandroid is not the only way.

AllAboutTheCore said:
http://forum.xda-developers.com/showthread.php?t=2224752 ... Flash ROM, install stock recovery, relock bootloader, done. The official firmware will be about soon no doubt so you will be able to fastboot it and have the newest base, stock and all before HTC release it in whatever region.
Obviously you'll need S-Off for Hboot 1.54 if/when it happens in order to remove the tampered flag and change relocked back to locked but what I mentioned above is the closest you'll get without being able to run an RUU.
Click to expand...
Click to collapse
I actually did this and Im running it right now without problems...
But Im not sure id be getting OTAs as the bootloader main ver still says 2.24.401.1 and not 2.24.401.8. I dont think Mike made a 2.24.401.1 available.
Its a bit disappointing. Im fine with having my bootloader tampered and relocked and s-on as long as I got stock running like it should be. i dont understand why HTC gives you the option to unlock ur bootloader to play around with custom firmware but not allow you to go back to stock. im guessing the RUU is on the way but I have my doubts... Just like s-off.
Sent from my HTC One using xda app-developers app

ossman said:
I actually did this and Im running it right now without problems...
But Im not sure id be getting OTAs as the bootloader main ver still says 2.24.401.1 and not 2.24.401.8. I dont think Mike made a 2.24.401.1 available.
Its a bit disappointing. Im fine with having my bootloader tampered and relocked and s-on as long as I got stock running like it should be. i dont understand why HTC gives you the option to unlock ur bootloader to play around with custom firmware but not allow you to go back to stock. im guessing the RUU is on the way but I have my doubts... Just like s-off.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Nah, the stock firmware for 2.24.401.8 is not available yet, only a customised one which would require S-Off anyway. The method I mentioned is the only way at the moment to get as close to stock as possible without being able to go S-Off and flash an older RUU. When Mike gets hold of the stock firmware to post, I'm sure he will ... I can't see any 2.24 RUU's being available seeing that HTC are pushing for a 4.3 release by the end of September, so I'd wait anyways, unless you need to return your device for warranty purposes of course.
As for you getting OTA updates ... I haven't installed the .8 ROM but it shouldn't affect it as the base you are on is still an older base than what you'd be trying to update to but I'm not 100% on that as I haven't flashed it as my device is away for repair lol. I would imagine that the 2.24.401.8 firmware would be about soon enough and then you would be able to revert to stock with the newest base but obviously as you said yourself, without S-Off you wouldn't be able to wipe any trace of you flashing and modding.
I think HTC only allow you to unlock your bootloader because they can void so many warranties that way and bill for repairs lol ... Maybe I'm being cynical but I do agree that they could provide a stock RUU for people to return to stock, without all the hassle of S-Off or waiting months before any suitable RUU is available but sometimes you have to just suck it up and live with what we have lol

ossman said:
I got myself in a bit of a dead zone here.
I have my HTC one. Its HTC__001 WWE Europe. It OTA upgraded to 2.24.401.1.
When I saw that you can convert to a GPE I really wanted to check it out specially after users reported success in getting OTA updates. But I quickly realized I needed S-Off and thats not available yet.
I decided to at least take it to a test drive with ARHD GPE 3.0. I downloaded the latest RUU for my device (1.28.401.7) thinking I would need that to get back to stock. I went and unlocked the bootloader at HTC dev. Flashed CWM recovery and flashed ARHD GPE 3.0. Played around with it for a bit and now when I needed to go back to stock.
RUU.exe file got stuck at updating signature then returned 155 unknown. I realized maybe its attempting to downgrade the bootloader so i looked around for a 2.24.401.1 RUU but its not available yet.
I looked at Nandroid backups and found 1.28.401.7 HTC__001 but its UK unbranded. When I restored this version it loaded up but my touch screen didnt work at all. I flashed back ARHD to get touch capability back.
So my question is... Any chance anyone can nandroid backup the stock 2.24.401.1 i need? How can I go to stock now? Am I stuck with custom roms untill atleast s-off or HTC decides 2.24.401.1 RUU should be made available?
Thanks!
Click to expand...
Click to collapse
i got an nandroid backup for you fully stock unrooted : https://mega.co.nz/#!AUZGkKwC!EAfhUXYAgjpAR42jGzG_mhzWJjwcs1j7R_tm_HPMDAo

soft brick every time i update stock rom

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.