Can get s-off or unlock bootloader, no matter what I do.
bootloader 1.16.0000
Even tried htcdev: http://s4.postimg.org/ewu7iwr5o/Untitled.jpg
you're sure it's a Incredi4G? ... if so, the bootloader version seems incorrect and/or unknown (to me at least) ... as the latest one we have is 1.15.0000 (or at best the engineering 1.15.1111) after the 2.17.605.2 RUU to ICS4.0.4 (the latest 2014-OTA 2.19.605.2 didn't change/touch the hboot)
EDIT: just in case ... could u plz upload a photo from the bootloader showing all the version infos? thx
kimba99 said:
you're sure it's a Incredi4G? ... if so, the bootloader version seems incorrect and/or unknown (to me at least) ... as the latest one we have is 1.15.0000 (or at best the engineering 1.15.1111) after the 2.17.605.2 RUU to ICS4.0.4 (the latest 2014-OTA 2.19.605.2 didn't change/touch the hboot)
EDIT: just in case ... could u plz upload a photo from the bootloader showing all the version infos? thx
Click to expand...
Click to collapse
I'd have to check it out later(The Version). I even tried the factory ruu exe and it gives me a bootloader error.
It is the htc incredible lte.
Just none of the scripts work for it.
I'll post up a picture later, im in school.
My mistake its 1.16.0000 Bootloader.
Image here: http://s10.postimg.org/jj6szhihk/20140319_114901.jpg
kimba99 said:
you're sure it's a Incredi4G? ... if so, the bootloader version seems incorrect and/or unknown (to me at least) ... as the latest one we have is 1.15.0000 (or at best the engineering 1.15.1111) after the 2.17.605.2 RUU to ICS4.0.4 (the latest 2014-OTA 2.19.605.2 didn't change/touch the hboot)
EDIT: just in case ... could u plz upload a photo from the bootloader showing all the version infos? thx
Click to expand...
Click to collapse
the ota didi not change the boot loader BUT i just got a replacement form vz it also had 1.16.
mine didi geth s-off wiht rumrunner it just took more than one try
dcooterfrog said:
the ota didi not change the boot loader BUT i just got a replacement form vz it also had 1.16.
mine didi geth s-off wiht rumrunner it just took more than one try
Click to expand...
Click to collapse
WOW ... interesting to see, that they actually DID create a new(er) hboot for our Dinc4G ... from the time-frame it fits the testing of the 2014-OTA nearly perfectly!
maybe that was/is the hboot prepared for the ... long intended JB4.1 updated ... but in the end they decided to _not_ roll out the full upgrade, but rather only a smaller bug-fix OTA.:crying: so for the regular user, there simply was no _need_ for new(er) hboot (yet?! )
@dcooterfrog: good to know that rumrunner S-OFF also works on 1.16 ... (i just assume that we won't see the ENG-1.16 (1.16.1111) anytime soon in the wild out there )
kimba99 said:
WOW ... interesting to see, that they actually DID create a new(er) hboot for our Dinc4G ... from the time-frame it fits the testing of the 2014-OTA nearly perfectly!
maybe that was/is the hboot prepared for the ... long intended JB4.1 updated ... but in the end they decided to _not_ roll out the full upgrade, but rather only a smaller bug-fix OTA.:crying: so for the regular user, there simply was no _need_ for new(er) hboot (yet?! )
@dcooterfrog: good to know that rumrunner S-OFF also works on 1.16 ... (i just assume that we won't see the ENG-1.16 (1.16.1111) anytime soon in the wild out there )
Click to expand...
Click to collapse
i was surprised that it let me flash the 1.15.1111 over 16 but it did
dcooterfrog said:
i was surprised that it let me flash the 1.15.1111 over 16 but it did
Click to expand...
Click to collapse
i assume: due to being s-off ... your dinc4g didn't mind accepting the older hboot ^^
kimba99 said:
i assume: due to being s-off ... your dinc4g didn't mind accepting the older hboot ^^
Click to expand...
Click to collapse
Yep. With s-off you can flash *anything* without any safeguards. When writing the regawmod plug-in, I went back and forth between several hboot versions.
Related
Hey guys i just got the 3d today and have it rooted. I installed 1 or 2 updates already but still had 1.4. But im curious as to what update exactly changes my hboot to 1.5. can any one help?
DO NOT OTA UPDATE YOUR PHONE! You do not want the HBOOT 1.5 it will make your life difficult. Stick with your bootloader and if you want to UG do it via a custom ROM.
jrockisme said:
Hey guys i just got the 3d today and have it rooted. I installed 1 or 2 updates already but still had 1.4. But im curious as to what update exactly changes my hboot to 1.5. can any one help?
Click to expand...
Click to collapse
The RUU for software verison 2.08 should also update hboot to version 1.5.
Probably best not to load this version unless you're up for an adventure! The
RUU software version 2.08 which also contains Hboot 1.5 patches all previously used exploits. Meaning, a new exploit will have to be developed and released in order to achieve the same unlocked access on Hboot 1.5 as was available for previous versions of Hboot.
Hope that helps answer your question!
divedr said:
DO NOT OTA UPDATE YOUR PHONE! You do not want the HBOOT 1.5 it will make your life difficult. Stick with your bootloader and if you want to UG do it via a custom ROM.
Click to expand...
Click to collapse
ahh, its not too bad. Granted i wish i had 1.30 or 1.40 but ADB & Fastboot aren't too bad.
joeykrim said:
The RUU for software verison 2.08 should also update hboot to version 1.5.
Probably best not to load this version unless you're up for an adventure! The
RUU software version 2.08 which also contains Hboot 1.5 patches all previously used exploits. Meaning, a new exploit will have to be developed and released in order to achieve the same unlocked access on Hboot 1.5 as was available for previous versions of Hboot.
Hope that helps answer your question!
Click to expand...
Click to collapse
That doesnt answer my question but it does answer which RUU i need to download for my Hboot version. But thanks for that one!
jrockisme said:
That doesnt answer my question but it does answer which RUU i need to download for my Hboot version. But thanks for that one!
Click to expand...
Click to collapse
Wait I am confused, do you want to have hboot 1.5? If so why?
Sent from my PG86100 using xda premium
jrockisme said:
Hey guys i just got the 3d today and have it rooted. I installed 1 or 2 updates already but still had 1.4. But im curious as to what update exactly changes my hboot to 1.5. can any one help?
Click to expand...
Click to collapse
joeykrim said:
The RUU for software verison 2.08 should also update hboot to version 1.5.
Probably best not to load this version unless you're up for an adventure! The
RUU software version 2.08 which also contains Hboot 1.5 patches all previously used exploits.
Click to expand...
Click to collapse
jrockisme said:
That doesnt answer my question but it does answer which RUU i need to download for my Hboot version. But thanks for that one!
Click to expand...
Click to collapse
If your question, as I read your post was, "what update exactly changes my hboot to 1.5" and you're on the Sprint version of the EVO 3D, then my answer above is correct. Software version 2.08.651.2 contains an update to bootloader version 1.5.
Perhaps I'm wrong in assuming you're on the Sprint device and perhaps you're using a GSM version. I'm not familar with the history of the GSM software versions, but I'm sure somebody else can post up to help clarify. Not sure where else the miscommunication could have occured.
Off the top of my head and to reiterate:
There have only been four updates for the EVO 3D from Sprint for their CDMA version of the EVO 3D.
1.11.651.2, 1.13.651.7, 2.08.651.2 an 2.08.651.3 (no leak RUU yet, only OTA, minor system software/kernel changes, no updated bootloader/radio).
If you're interested in gaining the ability to answer this question yourself, the hboot version is generally listed in the hboot file name of the image provided inside the firmware.zip of the RUU rom.zip (often renamed as PG86IMG.zip) included inside the RUU .exe. Hboot file name is generally, Hboot1.4_signed.img or something similar.
Also, if you feel adventurous, you could open the hboot img in a hex editor and search for the string containing the version number! Thats an adventure I don't take very often.
To obtain the extracted rom .zip files, renamed as PG86IMG.zip files or the original RUU .exe files for any of these software versions which have been leaked online, goo-inside.me keeps a reliable collection: http://www.goo-inside.me/shooter/ruu .
Allowing EVO 3D users to revert back to any previous software version or update to the recent versions.
Hope that helps answer your question with more detail/insight or help anybody coming across this post that might have the same/related questionand resolve any miscommunication! Money back guarantee!
SketchyStunts said:
ahh, its not too bad. Granted i wish i had 1.30 or 1.40 but ADB & Fastboot aren't too bad.
Click to expand...
Click to collapse
Agreed, a little more of a pain but also makes you learn things other people may not be savvy on! Great opinion man!
joeykrim said:
Off the top of my head and to reiterate:
There have only been four updates for the EVO 3D from Sprint for their CDMA version of the EVO 3D.
1.11.651.2, 1.13.651.7, 2.08.651.2 an 2.08.651.3 (no leak RUU yet, only OTA, minor system software/kernel changes, no updated bootloader/radio).
If you're interested in gaining the ability to answer this question yourself, the hboot version is generally listed in the hboot file name of the image provided inside the firmware.zip of the RUU rom.zip (often renamed as PG86IMG.zip) included inside the RUU .exe. Hboot file name is generally, Hboot1.4_signed.img or something similar.
Click to expand...
Click to collapse
I am sure I know the answer, cause if it were this easy we wouldn't have so many *****ing about 1.5, but if the RUU installs the bootloader, would it be possible to use an RUU of 1.11 or 1.13 to get the older bootloader?
Bob
ParrSt said:
I am sure I know the answer, cause if it were this easy we wouldn't have so many *****ing about 1.5, but if the RUU installs the bootloader, would it be possible to use an RUU of 1.11 or 1.13 to get the older bootloader?
Bob
Click to expand...
Click to collapse
No, it won't work. I believe the install will fail and cancel itself.
ParrSt said:
I am sure I know the answer, cause if it were this easy we wouldn't have so many *****ing about 1.5, but if the RUU installs the bootloader, would it be possible to use an RUU of 1.11 or 1.13 to get the older bootloader?
Bob
Click to expand...
Click to collapse
Short answer: No and I think the exact error people receive is "Main version is older". As far as I recall, main version information is stored in the misc partition.
We've had a few threads on this, usually the title or key phrase is "downgrading" the bootloader.
Essentially, the HTC EVO Shift was able to have the bootloader downgraded two different ways after two different releases, but neither method will work for hboot 1.5.
If you're interested in a longer semi technical explanation, I've quoted my previous posts below for convenience.
http://forum.xda-developers.com/show...88&postcount=2
the shift didn't have all the partitions nand write locked like the EVO 3D does.
1st time around: shift didnt 'have nand write lock on the hboot partition, hence being able to temp root and directly flash eng hboot to the hboot partition.
2nd time around: shift didn't have the nand write lock on the misc partition, hence being able to temp root and flash a lower version to the misc partition then hboot would allow a downgraded version of software to be loaded.
esseentially it seems as if htc was doing the bare minimum to protect the shift from being unlocked/rooted as all these methods were known and some were used on the HTC EVO prior to the shift software releases.
this has been covered a few times on the forums, but i hope rehashing old ideas/attempts might spark new ones! sometimes it only takes a slight tweak to an old method for it to bypass a patch and work! hope that helps!
Click to expand...
Click to collapse
hi s-off my phone when the hboot was 1.49.0007
but after the ics update i re(s-on) my phone for the new ics update
but now the hboot is 1.53.0007 and can't make it s-off(Update sucks nothing special)
1_tried using unlimited.io but didn't work made an error my guess because it's ics
2_tried using GB ROM(Leedroid) didn't work
used fastboot flash boot boot.img still no luck (restarts every 5 seconds)
3_PG86IMG.zip fails (Main version is Older)
4_last shooter ruu error 140
Any advice? thank you
If you accepted an official OTA update, then you are likely now stuck in Hboot1.5-Hell. (I made this mistake many moons ago.)
You can try one of the many methods to downgrade your HBoot, but I don't know how that works with the official ICS update.
Sorry.
thanks for answering
hope there will be a solution soon
not much of a problem still can flash any ICS ROM Unless Sense 4.0
but if there are any other ideas please help
friend.evil said:
hi s-off my phone when the hboot was 1.49.0007
but after the ics update i re(s-on) my phone for the new ics update
but now the hboot is 1.53.0007 and can't make it s-off(Update sucks nothing special)
1_tried using unlimited.io but didn't work made an error my guess because it's ics
2_tried using GB ROM(Leedroid) didn't work
used fastboot flash boot boot.img still no luck (restarts every 5 seconds)
3_PG86IMG.zip fails (Main version is Older)
4_last shooter ruu error 140
Any advice? thank you
Click to expand...
Click to collapse
What error code did you get?
Sent from my PG86100 using xda premium
error 140 Bootloader version error
This may sound dumb like a dumb question but do you see super user in your apps?
Sent from my PG86100 using xda premium
That error could mean the update put your bootloader to stock I'm not certain of what your capable of doing at the moment but I do know to unlock the bootloader for hboot 1.5 you had to use the HTC unlock method and maybe you'll have to use it. I'm not an expert so this may not be the case but keep in mind you said your hboot is at a different value than previous to me it would only make sense to use the HTC method to unlock reestablish root the use the wire trick to get s-off. If you try this I wish you success. Sorry if this seems lacking but if I find something out I'll make sure you know
Sent from my PG86100 using xda premium
sorry non of that works
anyways
thanks for trying to help
friend.evil said:
sorry non of that works
anyways
thanks for trying to help
Click to expand...
Click to collapse
Did u tried the pg86img gingerbread with goldcard ?
Or the official pg86img with changed older hboot ?
Sent from my HTC EVO 3D X515m using xda premium
friend.evil said:
hi s-off my phone when the hboot was 1.49.0007
but after the ics update i re(s-on) my phone for the new ics update
but now the hboot is 1.53.0007 and can't make it s-off(Update sucks nothing special)
1_tried using unlimited.io but didn't work made an error my guess because it's ics
2_tried using GB ROM(Leedroid) didn't work
used fastboot flash boot boot.img still no luck (restarts every 5 seconds)
3_PG86IMG.zip fails (Main version is Older)
4_last shooter ruu error 140
Any advice? thank you
Click to expand...
Click to collapse
1_ you tried unlimited.io and it didn't work? Thats surprising to me.
2_ have you tried booting recovery from fastboot and flashing a gb rom? Fastboot boot recovery yourrecovery.img
3_ You can run an older ruu if you change your main version, but it still won't lower your hboot, your phone says its version "x.x.x.x" and the ruu is lower so it won't flash.
4_ you will never be able to lower your hboot unless you use a downgrade method like unknownforces brick/downgrade. If you put a lower hboot in the newest ruu, it won't run because you've broken the HTC signature. Id try the wire trick again if I were you.
Question, why did you s-on? I've taken ota's with s-off and as soon as I see the new hboot I just reflash the engineering hboot.
I have ~ the same problem as friend.evil, although he says he can run roms with Sense < 4, (if i understood correctly) while i can not.
I did try the lastest GB (provided by anryl) PG86IMG, with no luck (device always stuck in boot loop), but i do not have any goldcard (nor could i find one for evo 3d, but i did not google for it that much)
I am not sure about what you (anryl) mean by « official pg86img with changed older hboot ? » ?
Would an ICS RUU solve the problem ? I will probably also try to downgrade hboot if no other suggestions pops up =S
(More context: http://forum.xda-developers.com/showpost.php?p=28076870&postcount=231 )
espace.ariane said:
I have ~ the same problem as friend.evil, although he says he can run roms with Sense < 4, (if i understood correctly) while i can not.
I did try the lastest GB (provided by anryl) PG86IMG, with no luck (device always stuck in boot loop), but i do not have any goldcard (nor could i find one for evo 3d, but i did not google for it that much)
I am not sure about what you (anryl) mean by « official pg86img with changed older hboot ? » ?
Would an ICS RUU solve the problem ? I will probably also try to downgrade hboot if no other suggestions pops up =S
(More context: http://forum.xda-developers.com/showpost.php?p=28076870&postcount=231 )
Click to expand...
Click to collapse
I don't mean to be insensitive but if you s-on'd and then took a new ota then youve got a problem on your hands. An older ruu with an older hboot will do you no good as it won't flash unless you change your main version, and even if you do that it won't flash an older hboot, just an older system (gb). You should go ahead and check in to downgrading.
wikdNoob said:
I don't mean to be insensitive but if you s-on'd […].
Click to expand...
Click to collapse
(It has always been s-on)
espace.ariane said:
(It has always been s-on)
Click to expand...
Click to collapse
Gotcha, well you should consider downgrading to get s-off. It's much more trouble free than s-on. Are you gsm or cdma?
NVM, dumb question, lol, if you took an ics ota then you're gsm
Edit... After reading your post in the link provided, is say that an ics ruu would fix u up. I'm cdma so I wouldn't know where to find it at.
Thanks for you suggestions… But still, i don't understand why downgrading should be necessary : why would flashing a rom, stock or not be a problem for the bootloader ? Can we not write to system or flash the boot partition anymore (from fastboot, using fastboot flash boot boot.img ?) in 1.53.0007 ?
(And indeed, gsm forgot to mention, sry)
espace.ariane said:
Thanks for you suggestions… But still, i don't understand why downgrading should be necessary : why would flashing a rom, stock or not be a problem for the bootloader ? Can we not write to system or flash the boot partition anymore (from fastboot, using fastboot flash boot boot.img ?) in 1.53.0007 ?
Click to expand...
Click to collapse
You might be on to something there, some hboots don't accept commands that others do. I would think that if you changed your main version and then ran a gb pg86img, it would get you back to gb but it won't change your hboot.
Have you tried booting a recovery from fastboot with fastboot boot recovery.img?
You can't use radios, ruu's, or the juop s-off method with 1.53. It's like having a locked/unlocked boatloader.
Sent from my extremely under rated EVO 3d with a shiny aluminum bezel like the EVO 4g LTE on, you guessed it, Sprint!
kiewee3 said:
You can't use radios, ruu's, or the juop s-off method with 1.53. It's like having a locked/unlocked boatloader.
Sent from my extremely under rated EVO 3d with a shiny aluminum bezel like the EVO 4g LTE on, you guessed it, Sprint!
Click to expand...
Click to collapse
Sent from my HTC EVO 3D X515m using xda premium
the problem in JuopunutBear is that it keeps waiting for the device
tells me to check if adb and fast drivers are installed but i am positive they are
Is there a possibility for a GB ROM to work on hboot 1.53.0007?
Not my first time around the block I did this with hboot 1.5 the only thing i can think of is HTCDEV.com sent me a F**ked up file.
fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.156s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.000s]
finished. total time: 0.156s
and WTF nothing happens no menu pops up to unlock or anything
I sent in the full and correct no space unlock code to htcdev.com
This is iratating
I had the same thing happen. No clue how to make it work. Earlier hboot maybe...
Sent from my PG86100 using xda premium
Did you take the OTA?
Even if you didn't, I had the same problem.
What I had to do to fix it is run the RUU.
http://forum.xda-developers.com/showpost.php?p=30106576&postcount=20
Then do the HTC unlock crap again. It will then work.
You'll know because your phone will display a pop-up asking you if you want to unlock or not.
Didn't take the ota..
Sent from my PG86100 using xda premium
I would try it anyways. Can't hurt.
Im having the same problem. I am trying to root my Wife Evo 3D Sprint and when I push the unlock tocken, I dont get the splash screen on the phone to perform the unlock. After I type the command, the phone just sits there.
She did take the OTA and is on HBoot 1.58.
I cant get any of the RUUs to work because the boatloader and all the software on the phone is newer and the RUUs just fail on start.
hypersonicx said:
Im having the same problem. I am trying to root my Wife Evo 3D Sprint and when I push the unlock tocken, I dont get the splash screen on the phone to perform the unlock. After I type the command, the phone just sits there.
She did take the OTA and is on HBoot 1.58.
I cant get any of the RUUs to work because the boatloader and all the software on the phone is newer and the RUUs just fail on start.
Click to expand...
Click to collapse
Have you tried the 2.89 RUU that was linked in post #3 above? I flashed it after using virus's firmware upgrade and taking the Sprint ICS OTA and it still ran fine for me. It should be the same as the OTA, but I have more confidence in the RUU.
ramjet73
halfaddict said:
Not my first time around the block I did this with hboot 1.5 the only thing i can think of is HTCDEV.com sent me a F**ked up file.
fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.156s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.000s]
finished. total time: 0.156s
and WTF nothing happens no menu pops up to unlock or anything
I sent in the full and correct no space unlock code to htcdev.com
This is iratating
Click to expand...
Click to collapse
FOUND SOLUTION..............
You have to download the RUU that matches the HTC Software on your phone. Go to settings > about > scroll down to Software Version and google search the RUU that matches.
Enable USB Debugging and let phone sit at home screen.
Run the RUU exe from withing windows on your PC wait for it to finish and and it will wipe phone in the process.
After it is done, boot to fastboot and run the HTC Unlock Token command again and this time you will get the prompt on the cell phone screen.
I spent 6 hours plus trying to root my wife phone wile tetherd from my Epic Touch GS2.
Samsung side of the world is a WHOLE lot easier. Everything is done within Oden for Samsung devices.
Anyway, there you go guys!
hypersonicx said:
FOUND SOLUTION..............
Click to expand...
Click to collapse
That's what I was recommending, except you don't have to relock your bootloader before running the RUU and unlock it after if you are S-OFF. And here's the downloads for the current RUU so others don't have to Google it.
Glad it worked for you.
ramjet73
apperantely people didnt read the htcdev website while unlocking. it clearly states it doesnt work properly unless on a 2.17.651.5 rom
htcdev.com said:
HTC has identified a known issue that may be experienced by some users with a Sprint EVO 3D that shipped with version 2.08.651.2, even if it was updated to a newer software version via FOTA. When attempting to unlock, a blank screen appears on the device after step 12 in the instructions and the process does not complete. As a workaround for users who experience this issue, we suggest you upgrade the ROM to 2.17.651.5 first via OTA then download and install the RUU from the table below to fix the issue before attempting the unlock process. This issue will also be fixed in the ICS update scheduled for EVO 3D.
Click to expand...
Click to collapse
t3project said:
apperantely people didnt read the htcdev website while unlocking. it clearly states it doesnt work properly unless on a 2.17.651.5 rom
Click to expand...
Click to collapse
That's odd, because the OP of this thread stated that it failed with hboot 1.5, which would indicate that he was already on the 2.17.651.5 build.
In any case, it appears that HTC unlock wants a pure stock configuration, so running either the 2.17 or 2.89 RUU before flashing the token should work.
ramjet73
ramjet73 said:
That's odd, because the OP of this thread stated that it failed with hboot 1.5, which would indicate that he was already on the 2.17.651.5 build.
In any case, it appears that HTC unlock wants a pure stock configuration, so running either the 2.17 or 2.89 RUU before flashing the token should work.
ramjet73
Click to expand...
Click to collapse
no, he stated he could unlock with 1.5 but couldn't unlock with 1.58.
hypersonicx said:
Im having the same problem. I am trying to root my Wife Evo 3D Sprint and when I push the unlock tocken, I dont get the splash screen on the phone to perform the unlock. After I type the command, the phone just sits there.
She did take the OTA and is on HBoot 1.58.
Click to expand...
Click to collapse
t3project said:
no, he stated he could unlock with 1.5 but couldn't unlock with 1.58.
Click to expand...
Click to collapse
And 1.58 is the stock bootloader of the official Sprint ICS build, which is where HTC said it would be fixed. Of course it depends on how he got the 1.58 bootloader but the OTA should have been fine, and at least one person said they had problems unlocking after taking the OTA.
ramjet73
ramjet73 said:
And 1.58 is the stock bootloader of the official Sprint ICS build, which is where HTC said it would be fixed. Of course it depends on how he got the 1.58 bootloader but the OTA should have been fine, and at least one person said they had problems unlocking after taking the OTA.
ramjet73
Click to expand...
Click to collapse
yea, they said it should be but it isnt. i cannot unlock mine either on 1.58 after installing the firmware updates but im already s-off so i just went back to the eng 1.04hboot since my current rom doesnt depend on 1.58 atm.
t3project said:
yea, they said it should be but it isnt. i cannot unlock mine either on 1.58 after installing the firmware updates but im already s-off so i just went back to the eng 1.04hboot since my current rom doesnt depend on 1.58 atm.
Click to expand...
Click to collapse
The firmware updates don't update you 100% to the 2.89 build. You need to flash the 2.89 RUU to do that, as has already been pointed out in this thread, and for some reason the HTC unlock appears to work after that. I really don't know what the difference is between taking the OTA and flashing the RUU is, but they should be the same.
For someone like you that is already S-OFF, you could always flash the JuopunutBear 1.58.5858 bootloader if you need to run the 2.89 kernel and get most of the benefits of the ENG bootloader. However, that bootloader will not work properly with GB and AOSP ROM's.
ramjet73
i know this man!!! lol
t3project said:
i know this man!!! lol
Click to expand...
Click to collapse
t3project said:
apperantely people didnt read the htcdev website while unlocking. it clearly states it doesnt work properly unless on a 2.17.651.5 rom
Click to expand...
Click to collapse
That's good. Now you also know that flashing the 2.89.651.2 RUU.exe will let you do the HTC unlock with the 1.58 bootloader.
ramjet73
t3project said:
yea, they said it should be but it isnt. i cannot unlock mine either on 1.58 after installing the firmware updates but im already s-off so i just went back to the eng 1.04hboot since my current rom doesnt depend on 1.58 atm.
Click to expand...
Click to collapse
I concur. I'm not a novice when it comes to unlocking bootloaders & rooting phones. I've unlocked more bootloaders through htcdev.com than I can count & this gentleman is absolutely right! HTC really needs to get it together! Samsung devices are so much easier to work with. You don't run into these stupid little problems with Samsung phones. Usually, what goes for one Samsung device goes for all!
I digress, but anyhow, I'm well aware that reinstalling the operating system on an EVO 3D via an RUU will allow the token that you get from htcdev.com to work, and I have used this fix several times in the past on the last Gingerbread OS (Software version 2.17.651.5), but here's my issue. I have an EVO 3D with S-ON & a LOCKED bootloader that was updated over the air to ICS & when I go to unlock the bootloader via htcdev.com, nothing happens & HTC claimed that this issue would be fixed with the ICS update, but guess what? It wasn't!
Nonetheless, you would think that reinstalling the ICS operating system (Software version 2.89.651.2) on the phone via an RUU or a PG86IMG file would work. Neither one works for me! Every time I go to run the ICS RUU, it throws back a 170 USB connection error & this is crazy because the RUU that I have for the last Gingerbread OS (Software version 2.17.651.5) never throws back any type of errors! It has worked on every single EVO 3D that I have had to use the fix on! I have tried running the ICS RUU several times and have used several different USB cables & have had no success whatsoever.
So what I did from here is requested for someone from the XDA community to create a PG86IMG for me so that I could see about reinstalling the ICS OS on the phone through the bootloader (Shout outs to Karl! He came through on this right away. Karl you are the man!). Unfortunately, when I go to use the PG86IMG file, it does all of this loading & appears as if it's going to work but ultimately goes back to the HBOOT home screen & doesn't give me an option to install the f'n operating system! This sh*t blows & I am all out of ideas as to what to do from here. I am basically stuck.
On anther note, I tried to use the ICS RUU that I have on another EVO 3D with no success, but I was successfully able to reinstall the ICS operating system on this same EVO 3D via the PG86IMG file that Karl provided. What in the world is going on here?! If anyone can offer any helpful advice, I'd certainly appreciate it. Thanx in advance. (On a side note this other EVO 3D that I was able to reinstalled the ICS OS on via the PG86IMG file has an UNLOCKED bootloader & is S-OFF. I don't know if this makes any difference, but I thought I'd share this anyway.)
RioSoul said:
Nonetheless, you would think that reinstalling the ICS operating system (Software version 2.89.651.2) on the phone via an RUU or a PG86IMG file would work. Neither one works for me! Every time I go to run the ICS RUU, it throws back a 170 USB connection error & this is crazy because the RUU that I have for the last Gingerbread OS (Software version 2.17.651.5) never throws back any type of errors! It has worked on every single EVO 3D that I have had to use the fix on! I have tried running the ICS RUU several times and have used several different USB cables & have had no success whatsoever.
Click to expand...
Click to collapse
The 170 error means that the RUU.exe can't find your phone. Make sure the phone is in "fasboot USB" mode in the bootloader, then try running "fastboot devices" from the PC directory you used to root your phone. It should come back with a serial number that starts with "HT". If it doesn't, you may have a problem with the USB port on your phone, although it probably won't go into fastboot USB mode in the bootloader if that is the case. If you get the serial number, try running the RUU.exe again from there. If you get a 17x error with the RUU.exe, usually restarting it will get past that error as long as you have the proper connectivity to the phone.
ramjet73
achppr who
Confirmed, this worked for me. Thanks for your help! :good:
I bought 3d evo a year ago and I tempered with it at first to root. I could not root it but it was s-off. Anyways , this whole time I thought I was getting updates and such because I was receiving update notifications and downloading them, and phone was restarting afterwards , so I thought everything was ok. Then, recently I checked software versions in settings and I was shocked. My phone was exactly the same as the first day. Then I tried to do a hard factory reset from settings. It did not work. Tried again from the bootloader menu, it did not reset again. There was a method by relocking it at first and using RUU's to make it back to original state. I relocked it but RUU file did not work , i think it was incompatible and gave an error.
Here are the version numbers in settings:
Android version - 2.3.4
HTC Sense - 3.0
Software - 1.20.468.6
This is the bootloader screen:
*****Relocked*****
****Security Warning*****
S- On
Hboot 1.49.0018 Emm-boot Oct 3-2011
I have a phone which can not revert to original state and can not apply any updates. Hboot version is an issue I always see guides about 1.50.
Do I have to start over and S-off first ? I have tried everything, putting pc86img.zip file to sd card , it reads during bootloader but does not ask to update. I tried sprint ruu file from windows but it did not work either. Need directions because I am really pissed off. Please help. Thanks.
bro i'm pretty sure that thats a gsm phone. please dont try to flash any cdma(sprint) stuff on it.
Normally I would have directed you to a thread containing gsm RUU's but apparently the new hosting site is down. Keep checking here though
http://forum.xda-developers.com/showthread.php?t=2094402
A word of warning: If you update using the RUU you will have the new hboot 1.53 and it is only possible to achieve s-off on that hboot with the wire trick. Whereas your current hboot can make use of flashmaniac's tool to downgrade and s-offf using revolutionary
EM|NEM said:
bro i'm pretty sure that thats a gsm phone. please dont try to flash any cdma(sprint) stuff on it.
Normally I would have directed you to a thread containing gsm RUU's but apparently the new hosting site is down. Keep checking here though
http://forum.xda-developers.com/showthread.php?t=2094402
A word of warning: If you update using the RUU you will have the new hboot 1.53 and it is only possible to achieve s-off on that hboot with the wire trick. Whereas your current hboot can make use of flashmaniac's tool to downgrade and s-offf using revolutionary
Click to expand...
Click to collapse
thanks man, I looked around and found stock a rom suitable for my region.And it worked. Now I'm updating to android 4
Hi guys, I have the 02 UK version of the HTC ONE X+
I install custom rom and now not finding any that work 100percent I am trying to get back to stock
Found several RUU files one specific for 02 and when running the RUU it says sending and then error message pops up on the program and the phone reboots.
Any ideas? And it doesnt have to be an 02 ruu just one that works.
My info is
Unlocked
ENRC2B_U PVT SHIP S-ON RL
HBOOT-1.35.0000
CPLD-None
MICROP-None
RADIO-3.1204.168.32
Thanks
you must relock bootloader to execute the latest RUU
skdubg said:
you must relock bootloader to execute the latest RUU
Click to expand...
Click to collapse
Hi Yeah I have had it relocked and tried executing the RUU but still no luck.
i have the exact same issue. reason is, last time i used the RUU to get back to stock rom, i used the phone on stock rom for a while and updated my phone to the latest build which updated the HBoot to version 3.5.000 but the currently available RUUs are not compatible with the HBOOT v3.5 so we have to wait for the new RUUs
problem for me is that i have sold the phone and didnt want to send the phone out with a custom rom but time is running out im afraid.
mjenabi2 said:
i have the exact same issue. reason is, last time i used the RUU to get back to stock rom, i used the phone on stock rom for a while and updated my phone to the latest build which updated the HBoot to version 3.5.000 but the currently available RUUs are not compatible with the HBOOT v3.5 so we have to wait for the new RUUs
problem for me is that i have sold the phone and didnt want to send the phone out with a custom rom but time is running out im afraid.
Click to expand...
Click to collapse
So I have to wait for newer RUU to come out for my HBOOT. Thats not too bad if thats all it is.
I have the exact same problem with my O2 UK One +, does anyone have any idea on when these new RUU's will be available? is it possible to downgrade the HBOOT to an older version that will allow the current RUU's to work?
what about ADB sideloading a flashable .zip of the stock firmware? would that work (if we have a flashable zip) or would it kick back an error?
Thanks.
downgrade hboot works only at S-OFF state
OK, is that possible on this phone? it was on my old HTC Magic, although it was hard work!!!!!
no S-OFF at this time for tegra3
Ok, not looking good then, so is there no way for me to get back to a stock rom now? very tempted to recycle the phone and get another one.....
moon-unit said:
I have the exact same problem with my O2 UK One +, does anyone have any idea on when these new RUU's will be available? is it possible to downgrade the HBOOT to an older version that will allow the current RUU's to work?
what about ADB sideloading a flashable .zip of the stock firmware? would that work (if we have a flashable zip) or would it kick back an error?
Thanks.
Click to expand...
Click to collapse
i have a solution for you.
i have a nandroid back up of my phone, you'd need to flash the boot.img in that and then use clockmod recovery to restore the phone to that nandroid and after that flash a stock recovery, relock the bootloader then use OTA updater on the phone to get it uptodate.
it takes a lot more work than just using the RUU, but they arent available right now, so that's what i did because i sold my phone so wanted it to be back to its original state for the new owner
i have the exact phone, mine was locked to O2 as well. i bet you bought it off that guy on ebay for £400?
pm me if you are interested and i will upload the stuff for you.
Found my backup..
here we go...
skdubg said:
you must relock bootloader to execute the latest RUU
Click to expand...
Click to collapse
sweet jebus... so simple, yet I didn't think of that! (I'm pretty new to this whole ROM flashing thing...)
Thanks for that simple suggestion!
skdubg said:
you must relock bootloader to execute the latest RUU
Click to expand...
Click to collapse
I accidentally missed a step when flashing a custom ROM onto my HOX+, and now it hangs at the HTC quietly brilliant screen every time. I know that all I need to do is re-lock the bootloader and use the most recent RUU, but I cannot get my computer to detect my phone to re-lock the bootloader. Is there another way to re-lock the bootloader? If not, what should I do?
mjenabi2 said:
i have a solution for you.
i have a nandroid back up of my phone, you'd need to flash the boot.img in that and then use clockmod recovery to restore the phone to that nandroid and after that flash a stock recovery, relock the bootloader then use OTA updater on the phone to get it uptodate.
it takes a lot more work than just using the RUU, but they arent available right now, so that's what i did because i sold my phone so wanted it to be back to its original state for the new owner
i have the exact phone, mine was locked to O2 as well. i bet you bought it off that guy on ebay for £400?
pm me if you are interested and i will upload the stuff for you.
Click to expand...
Click to collapse
Kool can you send me your back up?
Mjenabi2 can u please share the backup of your phone if is possible.
Thanks a lot
Htc one x plus
So i have a relocked HTC one X+ and i need to know the RUU that i need..
ENCRC2B_U PVT SHIP S-OFF RL
RADIO 3.1204.171.33