****ORIGINAL POST****(REWARD CLAIMED ALREADY)
So here's the deal. I was running cm10 a few days ago and was having a lot of issues with 3g/4g not working and things just being buggy in general. So i decided i wanted to go back to stock since the new jb update was released. I was s-on so i knew it would be a little tricky. So here's what i did. I installed the stock rooted version of the rom, flashed boot.img and all that got the latest stock rom working fine. However, I was still getting really weird issues with 3g/4g dropping and not connecting (even when areas with good signal) so i looked at my radios (which i can't recall ever updating) and decided they would require an update. Since i was s-on this can only be done through the ruu which essentially takes you back to stock but i was ok with this.
So here's what i did today:
relocked my bootloader following this video exactly: http://youtu.be/5yS7yy4XVA4
after i did this the phone may or may not have been stuck in bootloader loop i'm not sure since then i decided to apply the ruu right after.
following this video: http://www.youtube.com/watch?v=NChdbyaHy3k
now the phone only boots into the bootloader heres all this info:
****Tampered****
****Relocked****
***Security Warning***
Jewel Pvt ship s-on rl
hboot-2.09.0000
radio-1.05.11.0606
opendsp-v25.1.0.32.0405
eMMC-boot
Oct 18 2012, 15:4620
FASTBOOT
So i'm offering $15 via paypal to anyone who can help me out step by step to get my phone working again. I just want it to be completely stock running the latest. I tried running, and re running the ruu and everything goes through says its complete but i'm still stuck in the boot loop PAY
****UPDATES****BEWARE OF RUUUUUUUUUUUU
So it seems a lot of people have been having issues with this RUU and have been running into similar problems. Basically the ruu is updating everyones hboot to 2.09 and skipping over the radios. So its come to the conclusion that you should avoid applying the ruu or use it only as a last resort(brick). If you want stock jb then simply install the stock rooted rom. For now it seems the only thing we can do is wait for a method that will give us s-off for 2.09 and allow us to update the radios, or a newer ota/radio update from htc.
for more info/updates on the ruu situation see here http://forum.xda-developers.com/showthread.php?t=2089509
Try running the ruu again while in fastboot.
Sent from my EVO using xda premium
Which hboot were you on previously? I it looks like the ruu updated your hboot, but it didn't update your radios or anything else. Since it appears you can get into fastboot mode, I would plug your phone into a usb port and try to flash the ruu using fastboot. Look for a post by bigdaddy in the Android development stickies. It may help you. One of your problems will be you have some of the current firmware bits installed but not all of them. Which means you risk a hard brick if you to to revert to an older version. There was a post a while back where someone had a hboot flashable pj75img.zip that HTC sent him. That way you could put it on your sdcard and run it from hboot. If I pop can find it I will post a link.
Sent from my A500 using Tapatalk
---------- Post added at 10:20 PM ---------- Previous post was at 10:05 PM ----------
Here is the post with a link to the pj75img.zip. Download it, put it on the root of your sdcard, boot your phone into the bootloader, let it find the file and select yes to install it.
https://www.dropbox.com/s/k8llst3qjb0pn73/PJ75IMG.zip
Sent from my A500 using Tapatalk
Was it really necessary to offer money??
Send a message to captain throwback, he'll help you if you can be helped. And there are others too who would do it for free...
Good luck to you
Yep happens to me every time I relock my bootloader. Either (1) run ruu and let it finish. Or (2) use the htcdev sife to unlock your bootloader.
Sent from my EVO using xda app-developers app
alright brahs so a quick update
i got some help from a nice guy in the irc chat (so the paypal reward is gone) however i still have a few questions.
as soon as i unlocked via htc dev unlock the phone sprang back to life. twrp was back in recovery the stock rooted rom was still there (super su still intact). However my hboot has been updated so the ruu did do something. However my radios are still not updated so how do i go about doing so?
rollerpig said:
alright brahs so a quick update
i got some help from a nice guy in the irc chat (so the paypal reward is gone) however i still have a few questions.
as soon as i unlocked via htc dev unlock the phone sprang back to life. twrp was back in recovery the stock rooted rom was still there (super su still intact). However my hboot has been updated so the ruu did do something. However my radios are still not updated so how do i go about doing so?
Click to expand...
Click to collapse
Relock bootloader. Run the Jelly RUU 3.15. Unlock boot loadr (htc) load TRWP and make a backup..H boot will be downgraded in time. It will take some time just not now there is nothing
Sigh...
I am in the EXACT same boat.
Unfortunately the radios go completely biserko running anything jelly bean.
Fortunately I am able to unlock at will and run whatever ROM I want though... just not run it well at all.
Current status in my bootloader for the lurkers:
*** TAMPERED ***
*** RELOCKED ***
*** Security Warning ****
JEWEL OVT SHIP S-ON RL
HBOOT-2.09.0000
RADIO-1.05.11.0606
OpenDSP-v25.1.0.32.0405
eMMC-boot
Oct 18 2012,15:46:20
The 3.15 RUU completes supposedly "successfully" when ran with the phone in fastboot, however it completes in record time. What takes 10 minutes in the videos takes but maybe 3 minutes on my phone. Sigh.
Gonna flash ICS and continue to lurk. If anyone finds a fix for this please update this thread as I'm subscribed.
As clarification to lurkers...
UB2NOZ said:
Relock bootloader. Run the Jelly RUU 3.15. Unlock boot loadr (htc) load TRWP and make a backup..H boot will be downgraded in time. It will take some time just not now there is nothing
Click to expand...
Click to collapse
Relocked bootloader.
Ran Jelly RUU 3.15
Unlocked bootloader
Made my backup in TWRP
Not sure what the point of that backup is though, the ROM doesn't get updated by the RUU. As soon as I re-unlock I am able to boot right into my previous rom.
I've tried a complete wipe then ran the RUU, same result, except obviously I just had to reload a ROM afterwards.
Flashed an ICS ROM then ran my RUU thinking maybe it was verifying the current ROM version, still no joy.
The RUU goes through it's process, all be it faster than what one would think it should, and finishes saying it successfully completed. But it never actually updates the ROM.
I'm adding tags so others can find the thread as it took awhile to sort through and find this particular issue.
TAGS:
Bootloader HBOOT 2.09 Boot Loader Loop Security Warning Radio-1.05.11.0606 Firmware 3.15
I think what's happening is, when running the ruu, part of the process is it checks your current hboot and firmware to verify it isn't installing an older software. Since some how you partially upgraded with that first ruu attempt. Any future ruu attempts reads your hboot and decides you've already upgraded firmware and skips or stops the rest of the installation. You may be out of luck until HTC comes out with a new ota that upgrades hboot or someone comes up with a method to flash radios in recovery with s-on. You may want to just brick your phone and take it to sprint and see if they will exchange it. A tech looking at should be able to see that the upgrade failed and you only have a partial upgrade.
Sent from my A500 using Tapatalk
Brick the phone as a solution.... Sigh...
cruise350 said:
I think what's happening is, when running the ruu, part of the process is it checks your current hboot and firmware to verify it isn't installing an older software. Since some how you partially upgraded with that first ruu attempt. Any future ruu attempts reads your hboot and decides you've already upgraded firmware and skips or stops the rest of the installation. You may be out of luck until HTC comes out with a new ota that upgrades hboot or someone comes up with a method to flash radios in recovery with s-on. You may want to just brick your phone and take it to sprint and see if they will exchange it. A tech looking at should be able to see that the upgrade failed and you only have a partial upgrade.
Sent from my A500 using Tapatalk
Click to expand...
Click to collapse
Yeah, I don't see Sprint exchanging with a Tampered and Unlocked mark on the phone; may just wait until an s-off method for hboot 2.09 is found, but attempting an exchange may be worth a look.
It's really frustrating how HTC is so hell bent on locking the radios down the way they do. Oh well, that's the mistake I made for not going with a Nexus or something more developer friendly. I knew going in HTC was a proprietary jail of sorts, if you dance in the fire you gotta expect that at some point it's going to burn. Real pisser.
Thanks for the help everyone. If a solution is discovered please PM me or update the thread.
tankerkevo said:
Yeah, I don't see Sprint exchanging with a Tampered and Unlocked mark on the phone; may just wait until an s-off method for hboot 2.09 is found, but attempting an exchange may be worth a look.
It's really frustrating how HTC is so hell bent on locking the radios down the way they do. Oh well, that's the mistake I made for not going with a Nexus or something more developer friendly. I knew going in HTC was a proprietary jail of sorts, if you dance in the fire you gotta expect that at some point it's going to burn. Real pisser.
Thanks for the help everyone. If a solution is discovered please PM me or update the thread.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2081631 this sign good things coming to 2.09 hboot
Sent from my EVO using xda premium
just a few updates. the phone is working but just ****ed up in general. Randomly reboots everyone once in a while. sometimes text messages take forever to send. won't connect to 4g and google music is unable to stream/function properly. So i hoping all this is related to the radios and once i can achieve s-off (shouldn't be long now) i'll be able to update radios and things should work better. until then is there anything i can do to improve the performance? i'm guessing not.
rollerpig said:
just a few updates. the phone is working but just ****ed up in general. Randomly reboots everyone once in a while. sometimes text messages take forever to send. won't connect to 4g and google music is unable to stream/function properly. So i hoping all this is related to the radios and once i can achieve s-off (shouldn't be long now) i'll be able to update radios and things should work better. until then is there anything i can do to improve the performance? i'm guessing not.
Click to expand...
Click to collapse
I hate to be a debbie downer, but...
I wouldn't put too much stock in the latest dirtyracun s-off technique.
The first step in Dirty Racun requires you to stock the phone with the official RUU. In our case the 3.15 RUU.
Well, for the folks in our position the official HTC 3.15 RUU doesn't actually do a damn thing.
Per their instructions:
Download the RUU for your current HBOOT and put it in your DirtyRacun folder:
This step is REQUIRED even if you are on Stock RUU already!
RUU 1.22.651.3 - HBOOT 1.15
MD5 0fde3633b4fe22123d49ea66615b57ff
RUU 2.13.651.1 - HBOOT 1.19
MD5 3c6dbe048b7cfa09fd8f31a1d65ddb51
RUU your device (with your phone in fastboot):*
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip RUU.zip
Now unless they are using a modified RUU, I don't see this technique working in our case. That said, as soon as I get home I'm going to grab the ROM out of the EXE temp folder and try flashing it this way as I haven't done it yet:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip ROM.zip
Every time I've tried flashing I've used the Windows EXE which hasn't had any problems discovering the device while it's in fastboot usb, but trying this way may fix it, I'll let the thread know in a few hours.
Fail blog time
So I ran the flash through a terminal, at least I got a more verbose error:
***NOTE The RUU.zip used here is the PJ75IMG.zip from this thread, just renamed:
http://forum.xda-developers.com/showthread.php?t=2067921
[email protected]:/home/user/Downloads# fastboot oem lock
...
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642032 (0x1FDDFD70)
FAILED (status read failed (No such device))
finished. total time: 5.944s
[email protected]:/home/user/Downloads# fastboot erase cache
erasing 'cache'...
OKAY [ 0.115s]
finished. total time: 0.115s
[email protected]:/home/user/Downloads# fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.068s]
finished. total time: 0.068s
[email protected]:/home/user/Downloads# fastboot flash zip RUU.zip
sending 'zip' (659905 KB)...
OKAY [ 25.722s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 22 loading zip info fail)
finished. total time: 85.132s
For good measure I ran the flash a second time with the same "remote: 22 loading zip info fail" result:
[email protected]:/home/user/Downloads# fastboot flash zip RUU.zip
sending 'zip' (659905 KB)...
OKAY [ 25.271s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 22 loading zip info fail)
finished. total time: 83.659s
So far the bottom line is, if you ran the latest RUU, have s-on, your hboot is at 2.09 and radio at 1.05, welcome to the SOL club.
I've received several PMs from peeps who are suffering the same deal, and everytime I check the forum there's another member joining our not so elite club.
:crying:
Bummers.
I'll donate another $20 to rollerpigs fund if we can get this fixed before the next OTA... :silly: Just kidding, but seriously...
As always any help from the cloud will get stacks of kudos.
---------- Post added at 07:52 AM ---------- Previous post was at 07:19 AM ----------
To verify the image from the other thread, I just ran the same thing on my Windows partition using the rom_01.zip from the RUU EXE, and as anticipated got the same result.
Just got a new Evo LTE yesterday. Unlocked, but can't get S-off following the infamous YouTube video. Relocked then tried RUU. I have the same problem. RUU runs faster then it should. Was 2.13 and when I ran 2.13, it would say I had 2.13 installed. Doesnt work. Tried 3.15. Checks RUU image and says 3.15 is installed on my phone. Huh??? Reboot phone and still running ICS. Can't flash it back to stock. Going to try PJ75IMG. Maybe I will be lucky enough for it to brick and I can take it back to Sprint.
Maybe when Dirty Racun is for hboot 2.09 is released to the public soon, the ruu they provide to flash before you run their process may fix you guys up. Don't know. I think for the mean time people should stop running the ruu to try to upgrade and take the ota instead. The OP should try to change the title of this thread to something more informative like: "help, I ran the 3.15 RUU to upgrade my phone and it screwed up my phone, DO NOT RUN THE RUU BEFORE READING THIS"
Unbelievable how HTC has taken such a nasty stance on enabling people to tweak these phones. I have been using Sense since windows mobile, but all these hoops are not worth the hassle.
PS I am in the same boat. The 3.15RUU file updated the bootloader but NOT the Rom. On reboot the stock sprint Rom was still there along with all settings email etc. P.S. Also followed qbking77 youtube videos except went with the latest RUU instead of the one I had installed.
Op should change thread title to warn others. Problem with these forums is that there is SO much information its impossible to know what is important without spending hours reading.
Thoughts :
What if we were to unlock the bootloader again (I used RegawMOD and install TWRP, then run the older RUU with the earlier HBOOT version wouldn't that work? Does TWRP recovery overwrite the stock HBOOT? I was under the impression that it did, but now I am not too sure.
PS check this out folks:
http://www.pocketables.com/2013/01/...&utm_campaign=Feed:+GoodAndEvo+(Good+and+EVO)
Pretty much summing it all up.
http://www.pocketables.com/2012/12/...es-for-rooted-s-on-htc-evo-4g-lte-owners.html
No
I believe the current HBOOT 2.09 is what is validating the RUU being flashed. So if you try to flash an earlier RUU the current HBPOOT 2.09 halts you in your tracks.
As far as MeanBean, yeah it looks to be shaping up to be a great ROM. Unfortunately any JB ROM installed on antiquated and unflashable radio firmware isn't likely to function well. I've flashed an old stock ICS ROM and it seems to be faring well as far as radios and battery life. The only radio I've noticed dropping is WIFI but it recovers rather quickly. To be honest, I remember stock having that issue previously, so my phone is basically in the status it was in October.
I'm kicking myself, I never should have ran HTCs RUU. Hopefully this was an unintentional move by HTC and they provide updated version signatures in a soon to be released RUU to fix the issue they have caused. If not, I see them going the way of Nokia, superior quality but the geeks advise others away from it. The only non technical people I know that have an HTC cell are either the people I recommended to buy one or people who were referred by other geeks.
When it comes to Android you don't want to piss off the geeks... When you ask a non-geek why they bought a specific Android phone 90% of the time they say "because my geek friend recommended it" and that's a true reality.
The problem is, people are using the ruu improperly. A ruu is not meant to update the phone to the next version of software. It is for returning a phone back to factory condition. The ruu you flash is supposed to correspond to your current hboot and firmware. That is why you are supposed to take the ota to upgrade not run a ruu. I believe if you would have started with a pj75img.zip, which is an update file you would have been alright. Now that the hboot has upgraded all future attempts at running the ruu are failing. I am afraid you maybe out of luck on fixing this until the next ota that updates hboot and radio comes out.
Sent from my A500 using Tapatalk
Related
I'm having a real problem trying to relock and RUU my phone and could use some help.
I reboot into fastboot to relock.
Code:
D:\Android>fastboot oem lock
...
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = 134086000 (0x7FDFD70)
FAILED (status read failed (Too many links))
finished. total time: 0.936s
While still in fastboot, I run the RUU exe and it fails every time while updating signature with an error 140 - bootloader version error.
My image version is 2.01.605.11 and the RUU is 1.02.605.6
I've found several threads where people had this issue, but they were either able to get it to work, or the question was not answered.
Any thoughts? Thanks!
Gear_Up said:
I'm having a real problem trying to relock and RUU my phone and could use some help.
I reboot into fastboot to relock.
Code:
D:\Android>fastboot oem lock
...
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = 134086000 (0x7FDFD70)
FAILED (status read failed (Too many links))
finished. total time: 0.936s
While still in fastboot, I run the RUU exe and it fails every time while updating signature with an error 140 - bootloader version error.
My image version is 2.01.605.11 and the RUU is 1.02.605.6
I've found several threads where people had this issue, but they were either able to get it to work, or the question was not answered.
Any thoughts? Thanks!
Click to expand...
Click to collapse
you updated your mainver that RUU will not let you downgrade to the older RUU. Either have to find the fix the mainver post ( where your hex editing the file ) which is potentially dangerous or wait till the updated RUU is released.
The relock error is fine and the RUU error means you installed a kernel that updated your mainver.
Depending on what your purpose is, if you only want to install the radios try looking at this: http://forum.xda-developers.com/showpost.php?p=21867954&postcount=61 Just make sure to reflash your ROM/Kernel after installing the firmware.zip
If you really need to get back to pure stock with an RUU, you'll have to change your mainver: http://forum.xda-developers.com/showthread.php?t=1467099 Be very careful using this method as you can easily brick your phone. After updating your mainver you should be able to run the RUU.
Oh, crap!
I'm that guy. Sorry about this. I am running CleanROM 1.6 and I thought that didn't update the mainver...
Slinks off the board and blames this on the flu induced fever I'm suffering from...
Gear_Up said:
Oh, crap!
I'm that guy. Sorry about this. I am running CleanROM 1.6 and I thought that didn't update the mainver...
Slinks off the board and blames this on the flu induced fever I'm suffering from...
Click to expand...
Click to collapse
Hehe, clean rom is based on the OTA just doesn't include the radio, but yes that updated your mainver.
Did you ever get this figured out. I'm running into the same issue. I followed the other suggestion and changed my mainver, but still get an error 140.
Is this because I'm on hboot 2.11 and the ruu is 2.10. Will I need to wait for a new ruu based on the ota.
My main goal is to take the phone back to stock with relocked bootloader, either the new ota or the previous version.
Any help would be appreciated.
Tried following the instructions on this site to flash the latest HTC firmware and I could not install it from 4EXT. Renamed the file to PG86IMG.zip and flashed it from fastboot but hit an error. Tried to run the RUU for my radio version and every single one has hit an error (Update Failed! Main Version is older!).
The phone was originally HBOOT 1.40 S-OFF but it is now HBOOT 1.57 with s-on (which I did). I want to return the phone back to stock and start fresh but I really don't know how. Can I return back to HBOOT 1.40 or do I have to flash to the latest 1.50 and downgrade?
I'm really stumped by this one and any help would be greatly appreciated.
I'm as new to the forums as you, but I did a little messing and reading around. In order to return your phone to the same way you bought it, you need to downgrade hboot to version 1.4 and then run the RUU.exe of your firmware version (I'm not sure which version it is for your phone, it was 2.17.651.5 for me but I got my phone with hboot 1.5). The downgrade thread is here [it's very tricky to brick it, make sure the light is a solid faint red (NOT BLINKING) in order to do it successfully]. Hopefully someone else can tell you which RUU version to use (to run before the downgrade if you get the *Security Warning* in hboot, as well as the one to use after in order to return to the way you were when you got the phone). I just downloaded all the RUU's and ran them all until one worked.
LesbianSeagull said:
Tried following the instructions on this site to flash the latest HTC firmware and I could not install it from 4EXT. Renamed the file to PG86IMG.zip and flashed it from fastboot but hit an error. Tried to run the RUU for my radio version and every single one has hit an error (Update Failed! Main Version is older!).
The phone was originally HBOOT 1.40 S-OFF but it is now HBOOT 1.57 with s-on (which I did). I want to return the phone back to stock and start fresh but I really don't know how. Can I return back to HBOOT 1.40 or do I have to flash to the latest 1.50 and downgrade?
I'm really stumped by this one and any help would be greatly appreciated.
Click to expand...
Click to collapse
Hi, did you unlock and root your phone using the HTC method?
If so I think I may be able to help.
koty2012 said:
Hi, did you unlock and root your phone using the HTC method?
If so I think I may be able to help.
Click to expand...
Click to collapse
I think it was the Revolutionary method. Can't remember for sure since I did it quite a long time ago.
LesbianSeagull said:
I think it was the Revolutionary method. Can't remember for sure since I did it quite a long time ago.
Click to expand...
Click to collapse
Pm me your email, and if you'd like I could email you the RUU I have and you could see if it'll work. I'll walk you through it. You have gmail right?
Bizarre1 said:
I'm as new to the forums as you, but I did a little messing and reading around. In order to return your phone to the same way you bought it, you need to downgrade hboot to version 1.4 and then run the RUU.exe of your firmware version (I'm not sure which version it is for your phone, it was 2.17.651.5 for me but I got my phone with hboot 1.5). The downgrade thread is here [it's very tricky to brick it, make sure the light is a solid faint red (NOT BLINKING) in order to do it successfully]. Hopefully someone else can tell you which RUU version to use (to run before the downgrade if you get the *Security Warning* in hboot, as well as the one to use after in order to return to the way you were when you got the phone). I just downloaded all the RUU's and ran them all until one worked.
Click to expand...
Click to collapse
Just tried that, but I got the same HBOOT error message and I couldn't start the update in order to brick.
LesbianSeagull said:
Just tried that, but I got the same HBOOT error message and I couldn't start the update in order to brick.
Click to expand...
Click to collapse
Since you got that error, you need to flash the 2.08 or 2.17 RUU.exe to get rid of it. Try running the RUU while in the fastboot menu, and make sure you have the HTC drivers installed on your computer.
Have you tried both RUUs to no avail?
*Edit: I believe the drivers will install if you install HTC sync. Unfortunately I cant post the link to it, but just do a Google for HTC Evo 3D drivers. It's on HTC's website
koty2012 said:
Pm me your email, and if you'd like I could email you the RUU I have and you could see if it'll work. I'll walk you through it. You have gmail right?
Click to expand...
Click to collapse
PM'd and thanked
Bizarre1 said:
Since you got that error, you need to flash the 2.08 or 2.17 RUU.exe to get rid of it. Try running the RUU while in the fastboot menu, and make sure you have the HTC drivers installed on your computer.
Have you tried both RUUs to no avail?
Click to expand...
Click to collapse
Tried both
Code:
RUU_Shooter_S_Sprint_WWE_2.08.651.2_Radio_0.97.10.0808_NV_SPCS_1.31_003_release_208230_signed
RUU_Shooter_S_Sprint_WWE_2.17.651.5_Radio_1.06.00.1216_NV_NV_spcs_1.42_release_233304_signed
Both of which gave me the same error. the RUU connects over fastbootusb but halts at a specific point in the install, so I assume I have the right HTC drivers. I can find the install point in question if that would help.
Tried both
Code:
RUU_Shooter_S_Sprint_WWE_2.08.651.2_Radio_0.97.10.0808_NV_SPCS_1.31_003_release_208230_signed
RUU_Shooter_S_Sprint_WWE_2.17.651.5_Radio_1.06.00.1216_NV_NV_spcs_1.42_release_233304_signed
Both of which gave me the same error. the RUU connects over fastbootusb but halts at a specific point in the install, so I assume I have the right HTC drivers. I can find the install point in question if that would help.
Click to expand...
Click to collapse
That's really strange. Just to make sure you have the right drivers, go to Control Panel and then to Device Manager and see if your phone is there. It should be under "Android USB devices" or the like. Also, is USB debugging on before the going into hboot?
*Edit: Some more little things, HTC Sync should be uninstalled from your computer, and your phone should be locked.
LesbianSeagull said:
Tried following the instructions on this site to flash the latest HTC firmware and I could not install it from 4EXT. Renamed the file to PG86IMG.zip and flashed it from fastboot but hit an error. Tried to run the RUU for my radio version and every single one has hit an error (Update Failed! Main Version is older!).
The phone was originally HBOOT 1.40 S-OFF but it is now HBOOT 1.57 with s-on (which I did). I want to return the phone back to stock and start fresh but I really don't know how. Can I return back to HBOOT 1.40 or do I have to flash to the latest 1.50 and downgrade?
I'm really stumped by this one and any help would be greatly appreciated.
Click to expand...
Click to collapse
Did you flash the vm firmware ??
#Root-Hack_Mod*Always\
laie1472 said:
Did you flash the vm firmware ??
#Root-Hack_Mod*Always\
Click to expand...
Click to collapse
I used the instructions and download links from androidadvices(dot)com/update-htc-evo-3d-cdma-leaked-ics-403-firmware/. Reading the instructions now I see that I didn't put the phone into USB recovery mode. I can't get back into the ROM to do so and I can't get into my recovery either.
Your currently on hboot 1.57 and thats your your getting an update fail since 2.17 RUU has hboot1.50 Im not sure their is a way to downgrade this firmware unless you try the downgrade method for hboot 1.50 but that could maybe cause in a permanent brick.
iTzLOLtrain said:
Your currently on hboot 1.57 and thats your your getting an update fail since 2.17 RUU has hboot1.50 Im not sure their is a way to downgrade this firmware unless you try the downgrade method for hboot 1.50 but that could maybe cause in a permanent brick.
Click to expand...
Click to collapse
I'm trying that now. Hopefully it works!
So I tried bricking the phone using Unknownforce's method but everytime I would try and flash the 2.17 PG86IMG file in fastboot I get the same Hboot Version error. I also tried the Shooter_ICS_35_S_Sprint zip by renaming it to PG86IMG and and flashing in fastboot (since it has the matching hboot version), but I get a CID incorrect error. I'm trying to unlock my bootloader by using the HTC method in order to change the CID, but when I do so it gives me this in terminal.
Code:
C:\rootevo3dnew>fastboot flash unlocktoken unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.151s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.008s]
finished. total time: 0.159s
C:\rootevo3dnew>fastboot oem writecid htc__001
...
(bootloader) shooter_init_sd, SD card already power on
(bootloader) sdcc_init_memory_device done
(bootloader) [FAT_ERROR] fat_open_file: can not find SMART_IO.CRD
(bootloader) [JAVACARD_ERR] SMART_IO.CRD cann't find
OKAY [ 0.198s]
finished. total time: 0.198s
My bootloader still says it's locked but the unlock_code.bin in ADB looks like it's working. Can anyone tell me what is happening? This is the only thing holding me back from downgrading and it's frustrating
LesbianSeagull said:
So I tried bricking the phone using Unknownforce's method but everytime I would try and flash the 2.17 PG86IMG file in fastboot I get the same Hboot Version error. I also tried the Shooter_ICS_35_S_Sprint zip by renaming it to PG86IMG and and flashing in fastboot (since it has the matching hboot version), but I get a CID incorrect error. I'm trying to unlock my bootloader by using the HTC method in order to change the CID, but when I do so it gives me this in terminal.
Code:
C:\rootevo3dnew>fastboot flash unlocktoken unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.151s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.008s]
finished. total time: 0.159s
C:\rootevo3dnew>fastboot oem writecid htc__001
...
(bootloader) shooter_init_sd, SD card already power on
(bootloader) sdcc_init_memory_device done
(bootloader) [FAT_ERROR] fat_open_file: can not find SMART_IO.CRD
(bootloader) [JAVACARD_ERR] SMART_IO.CRD cann't find
OKAY [ 0.198s]
finished. total time: 0.198s
My bootloader still says it's locked but the unlock_code.bin in ADB looks like it's working. Can anyone tell me what is happening? This is the only thing holding me back from downgrading and it's frustrating
Click to expand...
Click to collapse
Hey sorry I so abrubtly had to go earlier, did you try again to flash the cwm.img? If you can get into backup and restore I feel as if you might be able to just go back to the previous hboot and ROM you had , not making any promises though.
koty2012 said:
Hey sorry I so abrubtly had to go earlier, did you try again to flash the cwm.img? If you can get into backup and restore I feel as if you might be able to just go back to the previous hboot and ROM you had , not making any promises though.
Click to expand...
Click to collapse
Just gave it another shot, but I got the same error:
Code:
C:\rootevo3dnew>fastboot flash boot cwm.img
sending 'boot' (4832 KB)...
OKAY [ 1.130s]
writing 'boot'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.928s
EDIT: Also tried running the 2.17 RUU again and it fails after attempting a signature check as well.
LesbianSeagull said:
Just gave it another shot, but I got the same error:
Code:
C:\rootevo3dnew>fastboot flash boot cwm.img
sending 'boot' (4832 KB)...
OKAY [ 1.130s]
writing 'boot'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.928s
EDIT: Also tried running the 2.17 RUU again and it fails after attempting a signature check as well.
Click to expand...
Click to collapse
I believe you don't flash that as boot. You flash cwm.img (clock work mod) as a recovery. Try
C:\rootevo3dnew>fastboot flash recovery cwm.img
*Edit: make sure your cwm.img is in your C:\rootevo3dnew folder.
Then after that, boot into the bootloader and go to recovery to access clockwork mod. See if you have any backups (which will save you a TON of pain by putting you back on hboot 1.4 with whatever former ROM you backed it up with)
Sent from my Evo 3D using XDA
Bizarre1 said:
I believe you don't flash that as boot. You flash cwm.img (clock work mod) as a recovery. Try
C:\rootevo3dnew>fastboot flash recovery cwm.img
*Edit: make sure your cwm.img is in your C:\rootevo3dnew folder.
Then after that, boot into the bootloader and go to recovery to access clockwork mod. See if you have any backups (which will save you a TON of pain by putting you back on hboot 1.4 with whatever former ROM you backed it up with)
Sent from my Evo 3D using XDA
Click to expand...
Click to collapse
Tried it, still gave me the signature verification error. I think it's because the bootloader is locked.
bump
Is there anything else I can try???
I know someone on XDA has to have a solution to this...
LesbianSeagull said:
Is there anything else I can try???
I know someone on XDA has to have a solution to this...
Click to expand...
Click to collapse
You have to be unlocked to flash the recovery image. Does it not say its unlocked at the top of HBOOT after using the HTC method?
Sent from the mobile paperweight itself!
I have been trying to root my 3d for liek 2 days now and have searched every where and tried ever trick i can find. No matter what i cannot seem to figure out what is going on.
I am hboot 1.58 S-ON i keep getting an error that the RUU i have is not the right one i have downloaded 3 different ones and all say the same thing i have read many thread and tried many ways to root this thing. I relock before using RUU but no matter what i get this message. It also will not flash any recovery, It just gets stuck at "sending"
i have the right drivers and everything. my computer sees my phone when i type "fastboot devices". any help would be so great.
lulzy1 said:
I have been trying to root my 3d for liek 2 days now and have searched every where and tried ever trick i can find. No matter what i cannot seem to figure out what is going on.
I am hboot 1.58 S-ON i keep getting an error that the RUU i have is not the right one i have downloaded 3 different ones and all say the same thing i have read many thread and tried many ways to root this thing. I relock before using RUU but no matter what i get this message. It also will not flash any recovery, It just gets stuck at "sending"
i have the right drivers and everything. my computer sees my phone when i type "fastboot devices". any help would be so great.
Click to expand...
Click to collapse
Based on your bootloader version, it sounds like you have a Sprint Evo 3D. I have a guide here that should help you get the the right RUU flashed, then get root and S-OFF.
ramjet73
ramjet73 said:
Based on your bootloader version, it sounds like you have a Sprint Evo 3D. I have a guide here that should help you get the the right RUU flashed, then get root and S-OFF.
ramjet73
Click to expand...
Click to collapse
your guide is the first guide I tried with no luck.. and yes im sprint
lulzy1 said:
your guide is the first guide I tried with no luck.. and yes im sprint
Click to expand...
Click to collapse
Then you need to give more specifics. If you can post the header information displayed in your bootloader here, and give the text of the error messages you are getting when you try to flash the RUU contained in the download, that will make it easier to help.
Also, please issue the following commands from fastboot and post the output here:
fastboot getvar cid
fastboot getvar mainver
ramjet73
Definitely post up the information ramjet73 is asking for.
Btw ramjet, you are quick. You always beat me to it!
Also curious if you are running the Ruu while booted up or from fastboot?
This seems blaringly obvious but if you are s-on, did you relock the bootloader?
Sent from my PG86100 using Tapatalk 2
ramjet73 said:
Then you need to give more specifics. If you can post the header information displayed in your bootloader here, and give the text of the error messages you are getting when you try to flash the RUU contained in the download, that will make it easier to help.
Also, please issue the following commands from fastboot and post the output here:
fastboot getvar cid
fastboot getvar mainver
ramjet73
Click to expand...
Click to collapse
bootloader header
***unlocked*** (currently, as I relock it to run RUU)
SHOOTER XC SHIP S-ON RL
HBOOT-1.58.0000
eMMC-boot
C:\Users\lulzyl\Desktop\QADERSO\Root>fastboot getvar cid
cid: SPCS_001
finished. total time: -0.000s
C:\Users\lulzyl\Desktop\QADERSO\Root>fastboot getvar mainver
mainver: SPCS_001
finished. total time: 0.005s
My battery is too low to run RUU right and im about to go to sleep I will update with the exact wording tomorrow but it says that Do not have the right RUU for my device. and if i am remembering correctly it says error 155 but I cant be 100% positive.
what i am using is RUU_Shooter_ICS_35_S_Sprint_WWE_2.89.651.2_Radio_1.09.00.0706__NV_NV_SPCS_1.43_release_271101_signed
Brian706 said:
Also curious if you are running the Ruu while booted up or from fastboot?
This seems blaringly obvious but if you are s-on, did you relock the bootloader?
Click to expand...
Click to collapse
He said in the OP that "I relock before using RUU but no matter what i get this message", but that's why I want to see his bootloader info and the text of the message he is getting.
I always recommend starting the RUU.exe with the phone in "fastboot usb" mode, but in theory it should work even if he is booted into Android.
Let's see what he has to say.
lulzy1 said:
C:\Users\lulzyl\Desktop\QADERSO\Root>fastboot getvar mainver
mainver: SPCS_001
finished. total time: 0.005s
Click to expand...
Click to collapse
That mainver doesn't look right. I should be 2.89.651.2 if you are on hboot 1.58. If that's really the current mainver it would explain why you can't flash the RUU. I have no idea how that could have been changed without flashing something with an incorrect android-info.txt in a PG86IMG.zip file, which requires S-OFF, or someone setting the mainver incorrectly via ADB. Did you get the phone new or used?
Please verify that is correct, and if it is, it will need to changed before the RUU will take.
Also, when you try to run the RUU.exe again make sure the phone is in fastboot USB mode.
ramjet73
I will rerun the comand later to make sure, I always run it from fastboot usb. Also i got the phone as an insurance replacement. sprint sucks so bad there is no telling if the phone is actually new or not
ok.. update I redid your command this morning and got what you were looking for.
C:\Users\lulzy\Desktop\QADERSO\Root>fastboot getvar mainver
mainver: 2.89.651.2
finished. total time: 0.000s
here is what RUU continues to give me no matter if im in fastboot usb or just the home screen
ERROR [155]: UNKNOWN ERROR
The ROM Update Utility cannot update your android phone.
Please get the correct ROM Update Utility and try again.
This is using the one you have in your RUU file ramjet and when this happens i get the black HTC screen but it has no loading bar and nothing in all the corners
lulzy1 said:
here is what RUU continues to give me no matter if im in fastboot usb or just the home screen
ERROR [155]: UNKNOWN ERROR
The ROM Update Utility cannot update your android phone.
Please get the correct ROM Update Utility and try again.
This is using the one you have in your RUU file ramjet and when this happens i get the black HTC screen but it has no loading bar and nothing in all the corners
Click to expand...
Click to collapse
So your CID and mainver look OK.
The 155 error usually means your current bootloader is unlocked.
Try relocking your your bootloader, then remove and and replace the battery and start the bootloader. Since your bootloader is currently unlocked, the status should show as "*** RELOCKED ***". Make sure it does and that you are connected to your PC in "fastboot usb" mode, then try it again.
If that doesn't work, you can try downloading just the RUU.exe from here. It's the same one that is in the QADERSO .zip file, but it's worth a try.
ramjet73
during my previous attempt it was relocked, anytime i try running RUU from fastboot it says it cant run because my battery is too low (i have 93% battery and i dont get the warning if i run from the home screen) i cannot run RUU from fastboot because this is all i ever see even after re downloading
lulzy1 said:
during my previous attempt it was relocked, anytime i try running RUU from fastboot it says it cant run because my battery is too low (i have 93% battery and i dont get the warning if i run from the home screen) i cannot run RUU from fastboot because this is all i ever see even after re downloading
Click to expand...
Click to collapse
The battery low indicator in fastboot mode sounds like a hardware problem to me. If your battery isn't charging correctly it may be a problem with your cable or USB port. Many people have gotten the RUU.exe to flash successfully by changing to a different cable and/or PC, but if you can't do that I suggest fully charging the battery with the A/C adapter that came with the phone before trying to flash the RUU.exe again.
Flashing the RUU.exe with the phone in Android mode may be masking the problem, but something is not right with your hardware.
ramjet73
all done!! different computer and cord works.
Thanks alot
How do you relock the hboot? I'm getting the same error. Thanks.
"fastboot OEM lock"
Phone:
Sprint HTC EVO 3D
Root & S-Off(JBear)
HBoot: JBear 1.58.5858
Firmware: 2.89.651.5
Radio: 1.09.00.0706
Rom: FroZenROM Ep 2.1
Kernel: AnthraX 2.7.0
Recovery: TWRP 2.3.3.0
SDCard: San Disk 64GB Extreme Class 10 UHS-1 (Low External Storage Wizard? Uninstall)
i need help
i need some help fixing my phone i rooted it had it working well for about 2 hours changed somthing now im stuck on the htc green and white sceen
my bootloader says relocked ive been trying to follow the guides but nothing seems to work, right now the phone is in the bootloader as thats all ive been able to access i have a virgin mobile evo 3d with hboot 1.58..can somebody please help me? or is my phone screwed?
Your phone is not screwed
What did you change? I'm guessing you either flashed a rom that's incompatible with your current hboot or you are s-on and need to flash the kernel separately.
What recovery do you have installed?
Brian706 said:
Your phone is not screwed
What did you change? I'm guessing you either flashed a rom that's incompatible with your current hboot or you are s-on and need to flash the kernel separately.
What recovery do you have installed?
Click to expand...
Click to collapse
thanks for the response but i actually managed to fix it yesterday. idk what i changed but i was using the clockworld recovery but it wouldnt install the stock shooter file so i used 4ext and its all bueno now except it boots as a sprint phone now but whatever i can deal with that
Glad you got it!
I'd stick with 4ext. I have heard cwm doesn't play well with this device but have not experienced it first hand.
Yea I won't be putting that back on my phone now I have a question I believe I have the vmobile stock shooter on my pc I need to fast boot that to get my splash screen and stuff back right? Cause right now when I turn it on it says sprint
I have read pages and pages from the Android Development forum for the HTC Evo 4G LTE and I can't seem to find a solution that works for me because going S-OFF or re-locking bootloader and loading RUU does not seem feasible for my situation.
The phone has custom recovery (TWRP) and we successfully loaded Viperboy's deodexed 3.15 stock ROM.
Baseband is 1.02.12.0427 (super outdated)
This phone was bought second hand and is a HTC dev unlocked phone, S-ON
I would like to update the baseband to 1.12.11.1200 and update the firmware to 3.16
Caveats: I don't have access to the phone, my friend can reload custom ROMs through TWRP, but beyond that I don't think we can go through Dirty Racun and S-Off, I don't know how we can easily check the HBOOT version to determine if the HBOOT version is 1.12
What would happen if we accepted the Sprint OTA? Are we SOL with the baseband because we are S-ON?
Is there any way we can get on MeanBean 3 or stock rooted 3.16?
Any advise would be greatly appreciated.
I wouldnt accept the OTA update to 3.16
I actually did just that when I relocked my phone on Saturday and had all sort of problems after that. Now, I'm not too sure you would even be able to install the update being that your phone is unlocked *citation needed*.
http://forum.xda-developers.com/showthread.php?t=2135670 - talks about the 3.16 OTA problems
thanks, I've definitely advised my friend to stay away from the OTA and disregard it. I think we are experiencing call/wifi issues due to the old baseband. I wonder what are the next possible steps to move forward from here...
BaconMunch said:
thanks, I've definitely advised my friend to stay away from the OTA and disregard it. I think we are experiencing call/wifi issues due to the old baseband. I wonder what are the next possible steps to move forward from here...
Click to expand...
Click to collapse
1. Stay on this baseband and deal with it.
2. Relock and RUU your way up to 3.15 (stay away from 3.16)
3. S-off and Flash a couple full firmware zips.
Sadly I think those are your only option. And to check your hboot just boot into bootloader. Hold volume down when powering on.
tilltheend714 said:
1. Stay on this baseband and deal with it.
2. Relock and RUU your way up to 3.15 (stay away from 3.16)
3. S-off and Flash a couple full firmware zips.
Sadly I think those are your only option. And to check your hboot just boot into bootloader. Hold volume down when powering on.
Click to expand...
Click to collapse
Thanks, I think that seems realistic, I'm concerned that if I relock through HTCDev, I read that some email/password might go to the original seller of the phone (ebay) for confirmation code, so I don't want to get stuck halfway
I am definitely crossing my fingers for HBoot v1.12, to confirm, once I check my version in the bootloader, I guess I can escape without taking any of the menu options (checking YouTube, I'll just go to recovery, enter TWRP, reboot, system).
BaconMunch said:
Thanks, I think that seems realistic, I'm concerned that if I relock through HTCDev, I read that some email/password might go to the original seller of the phone (ebay) for confirmation code, so I don't want to get stuck halfway
I am definitely crossing my fingers for HBoot v1.12, to confirm, once I check my version in the bootloader, I guess I can escape without taking any of the menu options (checking YouTube, I'll just go to recovery, enter TWRP, reboot, system).
Click to expand...
Click to collapse
Relocking the phone is done through fastboot on the computer. Nothing to do with HTC. And Dev unlocked means you get an unlock token from HTC to the email that you signed up with. So if you make your own account on HTC dev and request a token, it should send nothing to the other owner.
And sorry, but I don't understand what you mean by having Hboot 1.12. You mean only flashing the radio through recovery? If that's what you mean than I can't help with that. Not sure how that works or if there are problems with that.
great news! I had someone take screen shots of the HBoot (v.1.12.0000) and TWRP (v2.2.1) menu
Bootloader shows:
Code:
*** TAMPERED ***
*** UNLOCKED ***
JEWEL PVT SHIP S-ON RL
HBOOT-1.12.0000
RADIO-1.02.12.0427
OpenDSP-v25.1.0.32.0405
eMM-boot
So as far as I know, I'm going to make sure there's nothing wrong with the TAMPERED, and then I can flash 1.12.11.1210 through Captain_Throwbacks Radio Only zip and then looks for a 3.16 custom firmware compatible with S-On since I'm on build number 3.15.651.16 CL124461.
I'd appreciate anyone to chime in if I'm going down a bad path here. Cheers!
BaconMunch said:
great news! I had someone take screen shots of the HBoot (v.1.12.0000) and TWRP (v2.2.1) menu
Bootloader shows:
Code:
*** TAMPERED ***
*** UNLOCKED ***
JEWEL PVT SHIP S-ON RL
HBOOT-1.12.0000
RADIO-1.02.12.0427
OpenDSP-v25.1.0.32.0405
eMM-boot
So as far as I know, I'm going to make sure there's nothing wrong with the TAMPERED, and then I can flash 1.12.11.1210 through Captain_Throwbacks Radio Only zip and then looks for a 3.16 custom firmware compatible with S-On since I'm on build number 3.15.651.16 CL124461.
I'd appreciate anyone to chime in if I'm going down a bad path here. Cheers!
Click to expand...
Click to collapse
You've indeed unlocked the bootloader properly but this only let's you flash recoveries and custom roms. You have to S-OFF the phone to update firmware via bootloader. You're other option would be to RUU which would upgrade the firmware and software and that CAN be done with S-ON, however there is a problem with the update which disables touch input so you should either wait for a dev to make custom 3.16 rom and forget about the firmware OR wait for a fix from HTC and run that RUU whenever it comes out.
xlxcrossing said:
You've indeed unlocked the bootloader properly but this only let's you flash recoveries and custom roms. You have to S-OFF the phone to update firmware via bootloader. You're other option would be to RUU which would upgrade the firmware and software and that CAN be done with S-ON, however there is a problem with the update which disables touch input so you should either wait for a dev to make custom 3.16 rom and forget about the firmware OR wait for a fix from HTC and run that RUU whenever it comes out.
Click to expand...
Click to collapse
Thanks xlxcrossing! I messaged Captain for a a recovery flash for the baseband only and he said my approach is no good either. So seems like I have to RUU to get off 1.12 anyways since LazyPanda is not supported and DirtyRacun starts at 1.15
So I am looking at the UNLIMITED.IO site now
step 1) relock via fastboot
step 2) RUU 1.15 or 1.19 (so this means my firmware/software/hboot will be updated as well?)
From here if I stop, I will be S-ON so I can...
option 1) RUU 2.09 and stay on 3.15
option 2) unlock bootloader from HTCDev and stay S-ON
option 3) unlock bootloader from HTCDev and DirtyRacun S-OFF (which actually seems like a very simple process once unlocked)
BaconMunch said:
Thanks xlxcrossing! I messaged Captain for a a recovery flash for the baseband only and he said my approach is no good either. So seems like I have to RUU to get off 1.12 anyways since LazyPanda is not supported and DirtyRacun starts at 1.15
So I am looking at the UNLIMITED.IO site now
step 1) relock via fastboot
step 2) RUU 1.15 or 1.19 (so this means my firmware/software/hboot will be updated as well?)
From here if I stop, I will be S-ON so I can...
option 1) RUU 2.09 and stay on 3.15
option 2) unlock bootloader from HTCDev and stay S-ON
option 3) unlock bootloader from HTCDev and DirtyRacun S-OFF (which actually seems like a very simple process once unlocked)
Click to expand...
Click to collapse
My advice is get s-off it will save alot of headaches down the road
Sent from my PoS MoPho
BaconMunch said:
Thanks xlxcrossing! I messaged Captain for a a recovery flash for the baseband only and he said my approach is no good either. So seems like I have to RUU to get off 1.12 anyways since LazyPanda is not supported and DirtyRacun starts at 1.15
So I am looking at the UNLIMITED.IO site now
step 1) relock via fastboot
step 2) RUU 1.15 or 1.19 (so this means my firmware/software/hboot will be updated as well?)
From here if I stop, I will be S-ON so I can...
option 1) RUU 2.09 and stay on 3.15
option 2) unlock bootloader from HTCDev and stay S-ON
option 3) unlock bootloader from HTCDev and DirtyRacun S-OFF (which actually seems like a very simple process once unlocked)
Click to expand...
Click to collapse
Sent you a PM
The advice is free....the bandwidth, not so much
Just wanted to say thank you all for the support and advice.
I finally walked my friend over gtalk and successfully achieved S-OFF after relock, 1.15 RUU, unlock with HTC DEV, dirtyracun
Then updated full firmwares incrementally to 3.16
Then while trying to load MeanBean, realized we lost TWRP (and possibly root, need to confirm), I can only guess that went away with the RUU? That's not really documented anywhere unless that's a known thing.
TWRP installation via goomanager failed (maybe due to lack of root), I was able to find TWRP v2.3.1 bootloader, installed that and installed MeanBean 3.0.4
I think that makes us up to date, however we will likely install SuperSU via TWRP once we customize and ensure the phone is running smoothly.
Thanks again all!
Super su is included with the ROM
Sent from my EVO using xda premium
Hello all,
I've become sick of the blinding white HTC splash screen on boot-up.
I did some research and found two methods of flashing a new splash screen:
* fastboot flash splash1 splash1.img
* rename zip to PH98IMG.zip and flash through bootloader
I also read up on the proper image format/size, and used a zip file that other Rezound users have used, which I acquired via this thread: http://forum.xda-developers.com/showthread.php?t=1586434&highlight=splash+screens
Unfortunately, neither of the above methods works. Using fastboot returns the following error:
sending 'splash1' (1800 KB)...
OKAY [ 0.443s]
writing 'splash1'...
FAILED (remote: not allowed)
finished. total time: 0.769s
Flashing through the bootloader results in the bootloader stopping at "Update gift" and then booting itself into recovery, with no change to the splash screen. I even tried to install via recovery (using TWRP 2.5.0.0) and the install failed.
I've google searched for this problem and the only thing I have found that might be relevant (read on other phones' forums, not specific to the Rezound) is that my HBOOT version is wrong or does not allow extended boot commands because it is not the Engineering HBOOT. However, from what I can tell, this Engineering HBOOT may have problems with newer radios and I've also heard that flashing older HBOOTs can brick your phone. I am S-OFF via the juopunutbear wire trick.
Any advice? I'd love to stop the retina burn. Thanks for any help that can be provided.
*** UNLOCKED ***
VIGOR PVT SHIP S-OFF RL
HBOOT-2.28.0000
RADIO-2.23.10.0123r/2.23.10.0124r
OpenDSP-v14.6.0.7708.00.0507
eMMC-boot
Sep 20 2012,17:40:22
Flyhalf's CM10.1 ROM, 6/14 build
TWRP 2.5.0.0
Post the zip file and I'll take a look.
tigerxchaos said:
Hello all,
I've become sick of the blinding white HTC splash screen on boot-up.
I did some research and found two methods of flashing a new splash screen:
* fastboot flash splash1 splash1.img
* rename zip to PH98IMG.zip and flash through bootloader
I also read up on the proper image format/size, and used a zip file that other Rezound users have used, which I acquired via this thread: http://forum.xda-developers.com/showthread.php?t=1586434&highlight=splash+screens
Unfortunately, neither of the above methods works. Using fastboot returns the following error:
sending 'splash1' (1800 KB)...
OKAY [ 0.443s]
writing 'splash1'...
FAILED (remote: not allowed)
finished. total time: 0.769s
Flashing through the bootloader results in the bootloader stopping at "Update gift" and then booting itself into recovery, with no change to the splash screen. I even tried to install via recovery (using TWRP 2.5.0.0) and the install failed.
I've google searched for this problem and the only thing I have found that might be relevant (read on other phones' forums, not specific to the Rezound) is that my HBOOT version is wrong or does not allow extended boot commands because it is not the Engineering HBOOT. However, from what I can tell, this Engineering HBOOT may have problems with newer radios and I've also heard that flashing older HBOOTs can brick your phone. I am S-OFF via the juopunutbear wire trick.
Any advice? I'd love to stop the retina burn. Thanks for any help that can be provided.
*** UNLOCKED ***
VIGOR PVT SHIP S-OFF RL
HBOOT-2.28.0000
RADIO-2.23.10.0123r/2.23.10.0124r
OpenDSP-v14.6.0.7708.00.0507
eMMC-boot
Sep 20 2012,17:40:22
Flyhalf's CM10.1 ROM, 6/14 build
TWRP 2.5.0.0
Click to expand...
Click to collapse
Can you flash the ph98img of vinylfreaks modified hboot version 2.27 and retry your splash change ?
gr8nole said:
Post the zip file and I'll take a look.
Click to expand...
Click to collapse
Hey, thanks for replying, I've been out most of the day.
@gr8nole: Attached is the file I used. I renamed it to PH98IMG.zip, then PC36IMG.zip (because I read on another thread that it would work regardless of HBOOT version) and no luck from either one. I tried two separate zip files as well in case one of them was messed up in some way (I included the second one in attachments, it has a (2) on the end at current but the name was correct when I actually tried to flash it).
@dottat: I did some searching but couldn't find any useful locations for vinylfreak's HBOOT download, just a bunch of instances of it showing up in signatures. Do you have a download link for it? Also, is there a potential for this to brick my phone?
Thanks!
Well, the first one worked fine on my phone (also hboot 2.28). Since you are soff, maybe try re-flashing the latest firmware again. The only other difference is I am still locked.
gr8nole said:
Well, the first one worked fine on my phone (also hboot 2.28). Since you are soff, maybe try re-flashing the latest firmware again. The only other difference is I am still locked.
Click to expand...
Click to collapse
I'll give that a try. Do you mean re-flashing the whole latest RUU? I got these HBOOT/radio versions from a zip file that they were extracted into without the rest of the RUU.
Sent from my ADR6425LVW using xda app-developers app
tigerxchaos said:
I'll give that a try. Do you mean re-flashing the whole latest RUU? I got these HBOOT/radio versions from a zip file that they were extracted into without the rest of the RUU.
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
I was just referring to the firmware only, not the whole ruu.
Here is the eng 2.27 hboot link...I haven't seen anyone have problems with it on the newer radios.
http://forum.xda-developers.com/showthread.php?p=30457963
gr8nole said:
I was just referring to the firmware only, not the whole ruu.
Here is the eng 2.27 hboot link...I haven't seen anyone have problems with it on the newer radios.
http://forum.xda-developers.com/showthread.php?p=30457963
Click to expand...
Click to collapse
Got it sorted out.
I had created a backup .zip for use in recovery via Titanium Backup. It placed the zip on the root of my SD card. (update.zip)
Bootloader was seeing update.zip before PH98IMG.zip and was acting on it first, which would send it to recovery without loading the splash update zip.
I removed the update.zip file and the bootloader properly saw the PH98IMG.zip and flashed it without issue.
Thanks again for all your help!