Hello all,
So I've read all threads I could, I googled everything I could, but still no deal. When I try to downgrade to DREAIMG.nbh I get Model ID Incorrect!
And when I try to flash recovery directly, I get:
Code:
$ sudo ./fastboot flash recovery recovery.img
sending 'recovery' (4602 KB)...
OKAY [ 1.729s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 3.111s
My question is: is there a way to downgrade with fastboot? What if I try fastboot update DREAIMG.nbh?
I had it rooted already, but the speaker broke, took it somewhere to be fixed, but they ended up changing "all the insides". I don't remember it was this difficult to root it the last time, but it was a couple of years ago. This is the current phone booting in fastboot:
Code:
DREAM PVT 32B Ship S-on
HBoot-1.38.0000 (DREA20000)
CPLD-4
RADIO-2.22.16.19
Feb 28 2009, 18:40:30
And this is the about phone:
Code:
Build number
1.58.901.3 PLAT-1.0_gms-141395 CL#15959 release-keys
Firmware version:
1.1
Baseband version:
62.41s.20. 13u_2.22.16.19
Kernel version:
2.6.25-deb9915c
Herbert2and18-2 #11
Build number:
1.58.901.3 plat-1.0_gms-141395 CL#15959 release-keys
What else can I try? I'm comfortable with fastboot and would prefer to do everything in there. Do I really need to downgrade to install a new recovery? Is there another recovery I could try with this model?
Its not hard, and if your speaker broke they didn't need to change anything but the speaker. It looks like they gave you either a new phone or changed out the motherboard. Is this a rogers g1 by chance? Or who is it branded to on the splash screen?
Sent from my HTC Vision using xda premium
It's an Italian TIM branded. It was TIM branded on the splashscreen before and so is this "new" version. Yeah, it should be just replace the speakers, but it took them a lifetime, it came not working and they had to fix it again. So they seem to have changed the motherboard. That was in Italy.
One thing I don't understand. If I do
Code:
fastboot boot recovery.img
it loads up the recovery. But I can't do
Code:
fastboot flash recovery recovery.img
and it gives me that signature failure. Why?
BTW, I also tried the goldcard thing without success...
Anything else I could try?
Well you have s-on right, I don't believe you can flash anything in fastbbot. Hboot should load and flash the .nbh files, a signature fail probably means you have a bad copy. Check the md5 sums or download and flash another one. Maybe even try orange.nbh
Sent from my HTC Vision using xda premium
The S-On is your weakness in this, try to search in the threads to solve this, and try matching your Radio/HBOOT with Orange/Rogers dream, and I think you still have the standard Radio/HBOOT.
So I suppose I can't go wrong with the .nbh file, right?
I can try the orange one, or the rc29, and if it's the wrong version it will simply fail, without bricking the device?
(The G1 is old, but I still love this keyboard).
Ok, done!
The trick was to get a recovery installed. I had to use that flashrec app. Once that was done everything else was easy. I can't paste links yet, so here's some quick notes for any future visitors:
get Flashrec.apk. search the forums or google
get latest amon_ra recovery
Put them both on the sd card. Run the app on the phone (from some file browser app). Put /sdcard/amon_ra_recovery_filename_whatever.img instead of the webaddress it may have as default. Flash.
Once the custom recovery is in place you can proceed with DangerSPL on the wiki as normal, as with newer radios and SPL's.
Yeah, you're right. Another option is to flash it from Terminal Emulator - It's just like Command Prompt, but for your phone. Nice work finding it out for yourself!
Related
I just need clarification if you will.
I wish to downgrade my radio from 2.22.23.02 back to 2.22.19.26I. Is it just the same process as flashing the radio to upgrade? also is there only one version on of the earlier radio? Here's my Bootloader :
UK Vodafone
sapphire PVT 32B ship s-on g
HBOOT- 1.33.0004 (SAPP100000)
CPLD-10
RADIO -2.22.23.02
Thanks in advance.......
Yup, just apply it like you would an upgrade and you'll be fine
Well, I cant downgrade the radio via recovery, and fastboot gives me the old chesnut of :
FAILED (remote: signature verify fail)
Does this mean I'm going to have to flash an engineering SPL? Thought this wasn't necessary with the magic?
Can anyone help please?
Lemmy120 said:
Well, I cant downgrade the radio via recovery, and fastboot gives me the old chesnut of :
FAILED (remote: signature verify fail)
Does this mean I'm going to have to flash an engineering SPL? Thought this wasn't necessary with the magic?
Can anyone help please?
Click to expand...
Click to collapse
Try a different file, sounds like the one you got may have been corrupt.
Tried downloading the radio from a different location and flashing via recovery and fastboot still no joy. What to do?scared to flash an eng spl really.
*Bump*
I'm still at a loss with this
If you are installing custom anything, you should DEFINITELY have an engineering SPL.
So can anyone tell me how to do this?
Should I just flash the custom spl then downgrade the radio or what? I have read extensively but cant really find the answer
Have you tried this:
http://forum.xda-developers.com/showthread.php?t=625886
You should flash the radio/spl through fastboot, not recovery. If this doesn't work tell us what error you get.
I cant downgrade the radio via recovery, and fastboot gives me the old chesnut of
FAILED (remote: signature verify fail)
I'm sorry I don't know what that would cause that other than a corrupt file.
Hello
I have researched alot but didn't get my answer. There are alot of threads on this but still no luck.
I have a bell htc incredible S that came with s-off. I rooted through alpharx and flashed a custom rom of core droid.
Rom: http://forum.xda-developers.com/showthread.php?t=1096056
Everything works great except there is no call sound. I am trying to update the radio provided in the link above but I keep getting "model id incorrect" error.
Idk if I am flashing it properly or missing something in the process. Can someone please help I am new to this.
I put PG32IMG.zip file into K:\PG32IMG.zip and ran through Fastboot.
Thanks in advance
humm
umer215 said:
Hello
I have researched alot but didn't get my answer. There are alot of threads on this but still no luck.
I have a bell htc incredible S that came with s-off. I rooted through alpharx and flashed a custom rom of core droid.
Rom: http://forum.xda-developers.com/showthread.php?t=1096056
Everything works great except there is no call sound. I am trying to update the radio provided in the link above but I keep getting "model id incorrect" error.
Idk if I am flashing it properly or missing something in the process. Can someone please help I am new to this.
I put PG32IMG.zip file into K:\PG32IMG.zip and ran through Fastboot.
Thanks in advance
Click to expand...
Click to collapse
try this thread
http://forum.xda-developers.com/showthread.php?t=1129014&highlight=radio
maybe your flashing a froyo radio on ginger bread?>
^^^^ thanks
I am flashing a GB radio and I already looked at that link but still no luck. Idk if I have a radio s-off. How to check that? I was on froyo before I got custom coredroid and I never touched radio.
AlphaRevX doesn't give you radio S-OFF, that's why you're having problems.
doctorsax said:
AlphaRevX doesn't give you radio S-OFF, that's why you're having problems.
Click to expand...
Click to collapse
Can u please post a link on how to get radio s-off? I searched around but couldnt find any. My phone is unlocked tho.
umer215 said:
Hello
I have researched alot but didn't get my answer. There are alot of threads on this but still no luck.
I have a bell htc incredible S that came with s-off. I rooted through alpharx and flashed a custom rom of core droid.
Rom: http://forum.xda-developers.com/showthread.php?t=1096056
Everything works great except there is no call sound. I am trying to update the radio provided in the link above but I keep getting "model id incorrect" error.
Idk if I am flashing it properly or missing something in the process. Can someone please help I am new to this.
I put PG32IMG.zip file into K:\PG32IMG.zip and ran through Fastboot.
Thanks in advance
Click to expand...
Click to collapse
Hi i to have a Bell HTc incredible S, and could not flash a new radio, and could not get methods already outlined to work, so i did this method...
go here http://forum.xda-developers.com/showthread.php?t=1070348, follow this guide to install eng hboot then,
extract radio.img
Copy radio.img to a location where fastboot can find it. (wherever adb is)
Boot your phone into fastboot mode (power on while holding down the volume key)
Connect your phone via usb to your pc/mac/...
fastboot devices (to make sure that fastboot "sees" your phone)
fastboot flash radio radio.img
Code:
D:\SDK>adb shell
# busybox md5sum /sdcard/vivo_enghboot.img
busybox md5sum /sdcard/vivo_enghboot.img
b1829cfb7cf5d462660a58aa5449d27c /sdcard/vivo_enghboot.img
# dd if=/sdcard/vivo_enghboot.img of=/dev/block/mmcblk0p18
dd if=/sdcard/vivo_enghboot.img of=/dev/block/mmcblk0p18
2048+0 records in
2048+0 records out
1048576 bytes transferred in 0.552 secs (1899594 bytes/sec)
# reboot bootloader
reboot bootloader
D:\SDK>fastboot flash radio radio.img
sending 'radio' (25472 KB)...
OKAY [ 5.347s]
writing 'radio'...
OKAY [ 4.844s]
finished. total time: 10.194s
That's what I'm saying - your phone has an unlocked HBOOT (bootloader) but the radio is still locked. There is at least one thread on the forum here explaining how to flash a radio manually. Radio S-OFF can only be achieved using a hardware solution like an XTC clip, as far as I know.
test this out?
doctorsax said:
That's what I'm saying - your phone has an unlocked HBOOT (bootloader) but the radio is still locked. There is at least one thread on the forum here explaining how to flash a radio manually. Radio S-OFF can only be achieved using a hardware solution like an XTC clip, as far as I know.
Click to expand...
Click to collapse
can some one test out ali3nfr3ak method is it possible with soft ware S-OFF to manually flash a radio
^^^
I tried but I keep getting "permission denied" error when I enter "su" and I cant get a # sign in the process of Ship S-OFF to ENG S-OFF.
I am new to this forums so I cant post in the development section.
I cant get Ship S-off to ENG-Soff. I also have a question
If I get ENG S-OFF, will my phone become a Radio S-OFF. How do I check if my phone is Radio S-off or Radio S-on?
Thanks guys
umer215 said:
^^^
I tried but I keep getting "permission denied" error when I enter "su" and I cant get a # sign in the process of Ship S-OFF to ENG S-OFF.
I am new to this forums so I cant post in the development section.
I cant get Ship S-off to ENG-Soff. I also have a question
If I get ENG S-OFF, will my phone become a Radio S-OFF. How do I check if my phone is Radio S-off or Radio S-on?
Thanks guys
Click to expand...
Click to collapse
Ok so either the rom u r using does not have root permissions, or maybe you are not allowing root permissions on your phone when you type "su" in adb shell, ... what i mean is, after typing "su" in adb shell, on your phone a popup should appear asking for root permissions. U need ROOT permissions and busybox installed to flash eng-boot.
MY phone came shipped to me with s-off, i didnt use an xtc clip.
ali3nfr3ak said:
Ok so either the rom u r using does not have root permissions, or maybe you are not allowing root permissions on your phone when you type "su" in adb shell, ... what i mean is, after typing "su" in adb shell, on your phone a popup should appear asking for root permissions. U need ROOT permissions and busybox installed to flash eng-boot.
MY phone came shipped to me with s-off, i didnt use an xtc clip.
Click to expand...
Click to collapse
Hey bro thanks for ur help
ur method is amazing. Now finally i got Eng S-off and GB radio 20.2804.30.085AU_3805.04.03.22_M. currently, I am using froyo so I have no call sound that means I have got a GB radio and I just need to put back coredroid rom.
Thanks again
jul644 said:
can some one test out ali3nfr3ak method is it possible with soft ware S-OFF to manually flash a radio
Click to expand...
Click to collapse
yes his method did work sorry for the other post
umer215 said:
Hey bro thanks for ur help
ur method is amazing. Now finally i got Eng S-off and GB radio 20.2804.30.085AU_3805.04.03.22_M. currently, I am using froyo so I have no call sound that means I have got a GB radio and I just need to put back coredroid rom.
Thanks again
Click to expand...
Click to collapse
Sweet. Nice one, well done.
once you have flashed the radio, there is no need for the "eng-hboot" so if you were feeling confident...
download the attached zip.
extract and place hboot_1.13.0000_CRC_8a731c6e_0401.img [MD5=C0845E6348123828F918FDB48B74F349] in the same place you put the radio.img
Boot your phone into fastboot mode (power on while holding down the volume key)
Connect your phone via usb to your pc/mac/...
fastboot devices (to make sure that fastboot "sees" your phone)
fastboot flash hboot hboot_1.13.0000_CRC_8a731c6e_0401.img
Code:
C:\Users\Administrator>d:
D:\>cd sdk
D:\SDK>fastboot devices
HT15GTA00*** fastboot
D:\SDK>fastboot flash hboot hboot_1.13.0000_CRC_8a731c6e_0401.img
sending 'hboot' (1024 KB)...
OKAY [ 0.411s]
writing 'hboot'...
OKAY [ 0.421s]
finished. total time: 0.832s
Will flashing ENG HBOOT onto a AlphaRevX'd S-OFF phone cause it to go back to S-ON?
charch said:
Will flashing ENG HBOOT onto a AlphaRevX'd S-OFF phone cause it to go back to S-ON?
Click to expand...
Click to collapse
Well that i do not know %100. I wouldnt think so tho. I cannot test this for you as I didnt need to use AlphaRevX to s-off
It kinda worries me though... If I get ENG HBOOT and it returns to S-ON then would there be a way to S-OFF it again? Or would I be stuck forever?
Sent from my HTC Incredible S using XDA App
charch said:
It kinda worries me though... If I get ENG HBOOT and it returns to S-ON then would there be a way to S-OFF it again? Or would I be stuck forever?
Sent from my HTC Incredible S using XDA App
Click to expand...
Click to collapse
Well there is only one way to find out, All I can say is that my phone came with s-off, flashing the eng-hboot did not return me to s-on, the eng-boot is an engeering hboot so i dont see that it would return to s-on
EDIT: this from your other thread..
vimfreak said:
Flashing RUU will return S-ON.
I've S-OFF my phone with alpharevx and then flashed official GB RUU - phone was S-ON again.
However its not a big deal since you can use alpharevx trick again - phone will be S-OFF again (worked for me)
Click to expand...
Click to collapse
It depends on whether or not it checks if the hardware is S-OFF or not... Because if it does then Im screwed... But Ive looked at the Desire Z forum and they soft mod S-OFF and are able to install ENG HBOOT S-OFF... But... If it does happen to fail, since Im already rooted, wouldnt I be able to flash a HBOOT from the Optus rom or something?
EDIT: yes, but AlphaRevX relies on the stock HBOOTs to operate...
EDIT 2: did some research... ENG HBOOT is unlocked by nature... Apparently its impossible for it to revert you to S-ON xD thanks for your help
Sent from my HTC Incredible S using XDA App
works
i can confirm that this works here was my log
PHP:
C:\AndroidSDK\platform-tools>fastboot devices
HT13RTA05966 fastboot
C:\AndroidSDK\platform-tools>fastboot flash radio radio.img
sending 'radio' (25472 KB)... OKAY [ 5.328s]
writing 'radio'... OKAY [113.161s]
finished. total time: 118.490s
C:\AndroidSDK\platform-tools>
thos 118 seconds were scary
jul644 said:
i can confirm that this works here was my log
PHP:
C:\AndroidSDK\platform-tools>fastboot devices
HT13RTA05966 fastboot
C:\AndroidSDK\platform-tools>fastboot flash radio radio.img
sending 'radio' (25472 KB)... OKAY [ 5.328s]
writing 'radio'... OKAY [113.161s]
finished. total time: 118.490s
C:\AndroidSDK\platform-tools>
thos 118 seconds were scary
Click to expand...
Click to collapse
Was your phone S-OFF out of the box or did you use AlphaRevX?
EDIT: I decided to risk it and install ENG HBOOT... IT WORKED! Installing the Optus RUU!
I bought my phone about a mount ago.. in store have told to me that phone is s-on and official and i believed in it(( After official update from htc it stoped working. Work only recovery and -revolutionary-.
this is info in it:
info frm revolutionary
"vivo pvt ship s-off rl
hboot-6.13.1002
radio-3805.06.03.03_M
eMMC-boot
apr 1 2011, 18:34:39"
phone info
imei: 358000045678255
s/n: HT1A2TD03837
old OS: android 2.3.3
could anyone help me with this.. sry for my bad eng..
Ertey said:
I bought my phone about a mount ago.. in store have told to me that phone is s-on and official and i believed in it(( After official update from htc it stoped working. Work only recovery and -revolutionary-.
this is info in it:
info frm revolutionary
"vivo pvt ship s-off rl
hboot-6.13.1002
radio-3805.06.03.03_M
eMMC-boot
apr 1 2011, 18:34:39"
phone info
imei: 358000045678255
s/n: HT1A2TD03837
old OS: android 2.3.3
could anyone help me with this.. sry for my bad eng..
Click to expand...
Click to collapse
The OTA update cannot be applied to a phone that was S-Off with Revolutionary. You should be able to pull the battery to reboot into Recovery mode and restore your backup to get going again.
official 2.3.5 with revolutionary S-OFF won't boot. Why don't give a try on ARHD 2.1 by mike?
keroro430 said:
official 2.3.5 with revolutionary S-OFF won't boot. Why don't give a try on ARHD 2.1 by mike?
Click to expand...
Click to collapse
i try it but it just don't want to setup.. in recovery then i want to install via sd card it says about signature and i can not turn it off in standart recovery(( in revolutionaty it don't setup too..
Same problem....
Can somebody tell WTF should I do to get the new frimware???? PLEASE HELP!
It is simple - restore S-ON and everything will be OK. Search this forum - there was nice manual to do that. Had this "fun" 2 days ago...
Which Recovery you are using? Give a try to 4EXTRecovery. And now, what is your Incs Bootloader version?
i tried to bring back s-on:
C:\ADB>fastboot flash hboot rom.zip
sending 'hboot' (257756 KB)...
OKAY [ 43.328s]
writing 'hboot'...
FAILED (remote: image error! (Platform check fail))
finished. total time: 43.328s
HBOOT now is 6.13.9999
and how could i setup new recovery when my phone is brick..
i want to write a recovery cwm, but..
C:\android-win-tools>fastboot flash recovery cwm.img
sending 'recovery' (3696 KB)... OKAY [ 1.328s]
writing 'recovery'...
about an hour i see this.. that a problem with it =\
You must go back to S-ON and everything is OK!!!
How to go back to S-ON..............
nikolaet said:
How to go back to S-ON..............
Click to expand...
Click to collapse
Please do not hijack a thread and then ask a question that isn't even relavent to the topic.
You need to search this forum and next time definitely give more information such as I used [fill in the blank] method to S-Off my IncS. What is the procedure I can use to get back to S-On?
Follow this beautiful guide go back to S-ON, tried myself AMD it works flawlessly..
http://forum.xda-developers.com/showthread.php?t=1359555
You should have the hboot version which you had previously..
Read carefully you will gain s-on..
After s-on run the RUU sense 3 exe file which you have downloaded but don't install from pc.. before doing this procedure you should make a goldcard.. search for that in google .. once you make a gold card, put the extracted file of that RUU from temp folder ( I guess you know how to do that ) , name it PG32IMG.zip and reboot your phone by pressing volume down+power phone will search for that file and follow on screen procedure.. it will install sense 3.0.. and your phone will start working again.. don't panic...
Info about making goldcard found here though it says for desire hd it works for incredible s too..
http://www.addictivetips.com/mobile/how-to-make-gold-card-for-htc-desire-hd/
PS : you have to make a gold card so your phone does not give you a signature error.. I was stuck with the same problem after updating the latest release but now my phone is working perfectly again..
Sent from my HTC Incredible S using Tapatalk
Nvr flash or ota update without fully reseaech.
Sent from my HTC Incredible S using XDA App
HTC Holiday - At&t Vivid
***RELOCKED***
HBOOT-1.85.0024
S-ON RL
CID: CWS_001
Version Installed:
3.26.502.54 710RD
Kernel Version:
3.0.16-gea0e914
[email protected] #1
Baseband:
3.02.4740.14_34.22.701040.19L
Build:
3.25.502.54 CL302737
Issue:
I am trying to return to stock so I can sell this phone. I RELOCKED it using the "fastboot oem relock" and got the famous error message that it failed with "too many links". But it still shows that it is relocked.
When running the RUU with the phone booted it errors out with error 155. When I try and run it through fastboot it just sits on "Sending" and doesn't go anywhere. I had it sit for 12 hours yesterday and it didn't budge.
I've tried these two files, which are the exact same I know...
htc_vivid_att_RUU_3.26.502.56_US.exe
RUU_HOLIDAY_ICS_35_S_Cingular_US_3.26.502.56_Radio_3.02.4740.14_34.22.701040.19_release_246712_signed.exe
I need to re-flash something to it, whenever the damn thing boots up (even after a factory reset) it says "Updating Android". And it says it every time. I can't sell a phone that does that.
I have tried to unlock and lock again. It's been while since I have done this, but I thought it had something to do with the error while re-locking, or the HBOOT version.
I've read some other places that I need to get S-OFF first to be able to return to stock, WTF, unless something has change, I've never had to do that before with this device to return to stock.
**EDIT**
I just tried to go into the recovery to see if there was one still installed and it flashed back to the fastboot screen and now says ***SECURITY WARNING*** under the relock. I have not seen that before.
Squeaky369 said:
HTC Holiday - At&t Vivid
***RELOCKED***
HBOOT-1.85.0024
S-ON RL
CID: CWS_001
Version Installed:
3.26.502.54 710RD
Kernel Version:
3.0.16-gea0e914
[email protected] #1
Baseband:
3.02.4740.14_34.22.701040.19L
Build:
3.25.502.54 CL302737
Issue:
I am trying to return to stock so I can sell this phone. I RELOCKED it using the "fastboot oem relock" and got the famous error message that it failed with "too many links". But it still shows that it is relocked.
When running the RUU with the phone booted it errors out with error 155. When I try and run it through fastboot it just sits on "Sending" and doesn't go anywhere. I had it sit for 12 hours yesterday and it didn't budge.
I've tried these two files, which are the exact same I know...
htc_vivid_att_RUU_3.26.502.56_US.exe
RUU_HOLIDAY_ICS_35_S_Cingular_US_3.26.502.56_Radio_3.02.4740.14_34.22.701040.19_release_246712_signed.exe
I need to re-flash something to it, whenever the damn thing boots up (even after a factory reset) it says "Updating Android". And it says it every time. I can't sell a phone that does that.
I have tried to unlock and lock again. It's been while since I have done this, but I thought it had something to do with the error while re-locking, or the HBOOT version.
I've read some other places that I need to get S-OFF first to be able to return to stock, WTF, unless something has change, I've never had to do that before with this device to return to stock.
**EDIT**
I just tried to go into the recovery to see if there was one still installed and it flashed back to the fastboot screen and now says ***SECURITY WARNING*** under the relock. I have not seen that before.
Click to expand...
Click to collapse
First of all, I must say, THANKS for posting so many details! That makes it much easier to fully understand your issue. I wish everyone would be so concise.
Next, these are errors I have never seen.. This Security Warning is news to me... I wonder if you should maybe try to re-flash the original HBOOT... That is the most risky of all flashes, so I'd maybe wait for someone who has experienced this issue to pipe up before attempting it.
It sounds to me that HBOOT is where your problem lies though. I hope someone else can be of more help on this issue.
ess.boyer said:
First of all, I must say, THANKS for posting so many details! That makes it much easier to fully understand your issue. I wish everyone would be so concise.
Next, these are errors I have never seen.. This Security Warning is news to me... I wonder if you should maybe try to re-flash the original HBOOT... That is the most risky of all flashes, so I'd maybe wait for someone who has experienced this issue to pipe up before attempting it.
It sounds to me that HBOOT is where your problem lies though. I hope someone else can be of more help on this issue.
Click to expand...
Click to collapse
Thank you! I've been around this site for around 4 years now and it's EXTREMELY annoying when searching for answers when someone just posts:
"i cant flash"
Or whatever...
As for the actual issue, that's what I was thinking. There was something awhile back I thought I had read about that version of the HBOOT being an issue. So, hopefully someone around here can help out. I searched for it but I couldn't find anything. So either I am thinking of another phone or it's just lost in the depths of the unknown.
Squeaky369 said:
Thank you! I've been around this site for around 4 years now and it's EXTREMELY annoying when searching for answers when someone just posts:
"i cant flash"
Click to expand...
Click to collapse
Amen to that!
As for the actual issue, that's what I was thinking. There was something awhile back I thought I had read about that version of the HBOOT being an issue. So, hopefully someone around here can help out. I searched for it but I couldn't find anything. So either I am thinking of another phone or it's just lost in the depths of the unknown.
Click to expand...
Click to collapse
I think your best bet may be to just try reflashing the HBOOT. Check Hasoons All-in-one tool kit as I believe it contains the original HBOOT and the one that comes with the S-OFF tools. If it's not there, you should be able to find it somewhere around the forum. Maybe there's a link in the superguide.
Hopefully with a fresh HBOOT, you can get locked, and the RUU will work again. I have flashed the RUU a few times, and each time for me, relocking the bootloader worked fine.
It's worth a whirl.
http://forum.xda-developers.com/showthread.php?t=1416836
SECOND OPTION (PH39IMG.zip flash)
- Put this file for AT&T or this file for Rogers on a microSD card as is (it should be named PH39IMG.zip)
- Power down the phone, insert microSD and boot back into bootloader (power button + vol down)
- It should automatically find the zip file and flash the stock image (this includes recovery, system, everything stock.)
- If you returned to stock because of a bug or issue, and want to root again, make sure to go back and follow the steps PRECISELY to perm root, flash CWM, flash a ROM, flash a kernel, etc. Remember, flash ROM IMMEDIATELY after flashing the kernel
Click to expand...
Click to collapse
ess.boyer said:
Amen to that!
I think your best bet may be to just try reflashing the HBOOT. Check Hasoons All-in-one tool kit as I believe it contains the original HBOOT and the one that comes with the S-OFF tools. If it's not there, you should be able to find it somewhere around the forum. Maybe there's a link in the superguide.
Hopefully with a fresh HBOOT, you can get locked, and the RUU will work again. I have flashed the RUU a few times, and each time for me, relocking the bootloader worked fine.
It's worth a whirl.
Click to expand...
Click to collapse
Ripped the original HBOOT out of the RUU that I had from HTC.
When I try and flash though I get this:
---------------------------------------------------------------------------------------------------------
C:\Android>fastboot flash hboot hboot.nb0
sending 'hboot' (1023 KB)... OKAY [ 0.297s]
writing 'hboot'... FAILED (remote: not allowed)
finished. total time: 0.614s
---------------------------------------------------------------------------------------------------------
I don't need to be S-OFF to flash the HBOOT do I? I unlocked the bootloader again, so that is not what is causing the issue.
Brand New said:
http://forum.xda-developers.com/showthread.php?t=1416836
Click to expand...
Click to collapse
That's the first thread I went through when starting this
I have actually been looking for the PH39IMG.zip file for At&t because that's how I used to do this...
But the file in that link isn't there anymore. It seems that every search I do and find where someone has posted it, it's been removed because of copyright infringement or some other stupid political BS.
Got it.
Created my own PH39IMG.zip using the RUU I got from HTC and got the HBOOT updated and everything returned to stock.
Thank you for the assistance everyone.
Ha! Rocking! Glad you're back up and running.
Squeaky369 said:
Got it.
Created my own PH39IMG.zip using the RUU I got from HTC and got the HBOOT updated and everything returned to stock.
Thank you for the assistance everyone.
Click to expand...
Click to collapse
I am having the exact same issue. Any chance you could share that PH39IMG.zip you made or explain how you did it?
I'll be putting the links up for the PH39IMG.zip in the next hour or so
---------- Post added at 11:36 AM ---------- Previous post was at 11:30 AM ----------
For both AT&T and Rogers Ripped straight from the RUU
Greetings,
Going through some boxes the other day I found my old HTC One M9, which I had previously unlocked and flashed with various different ROMs.. Basically, this was the first device I ever actually tried any custom ROMs. That said, it's been so long, I don't have any of my old files left and I don't remember exactly what I did.
At this moment in time, the device is booting and running Xiaomi MIUI 8 (Android 6), but I'm unable to get into TWRP (constant bootloop) and I can't flash a new recovery image.
After a "fastboot reboot bootloader", I see the following details:
Code:
*** UNLOCKED ***
M7_UL PVT SHIP S-OFF RH
CID-11111111
HBOOT-1.54.000
RADIO-4T.36.3218.06
OpenDSP-v26.120.274.0202
OS-
eMMC-boot 2048MB
Apr 28 2015,09:16:24.0
When I try flash "twrp-3.3.1-1-hima.img", I get the following:
Bash:
> fastboot flash recovery twrp-3.3.1-1-hima.img
Sending 'recovery' (21852 KB) OKAY [ 2.072s]
Writing 'recovery' FAILED (remote: 'image update error')
fastboot: error: Command failed
I'm hoping to flash LineageOS from this thread, either 16.0 (as per the thread details) or the 17.1 or 18.1 available in the linked repository, but I can't do so until I get the recovery partition sorted out.
Please can someone help me fix whatever it was that I broke here..?
---
Please note: originally, I accidentally posted this in the M9 forum. I'm now creating this to replace that thread...
There was a suggestion to just try flashing the boot image first, and effectively worry about recovery later. So I will jump on that, as soon as I have this annoying "no permissions" issue with fastboot. But I do want to post this here in the meantime, just in case somebody has any other bright ideas.
..and I just realised I was trying to use the "hima" recovery, which is the codename for the One M9. I'm really out of the Android flashing game these days..
Suffice to say, this is somewhat embarrassing. Let me go try this again, using the proper files this time. I'll update things again soon..
So guess what, with the correct files, things actually flash.. Amazing how that works hey?
Anyways, after all that, I got it sorted. Flashing LineageOS now.
Nice to see some good old HTC One M7 posts these days haha