Database Develop

downgrade hboot

Anyone an idea how to downgrade hboot version ?
I have update the firmware to 2.17.401.1 with a newer hboot.
Sadly this new hboot is not yet supported with cm10.1 roms so i want to downgrade.
So is there a way to revert back to the stock firmware without wipe ?

c0de1 said:
Anyone an idea how to downgrade hboot version ?
I have update the firmware to 2.17.401.1 with a newer hboot.
Sadly this new hboot is not yet supported with cm10.1 roms so i want to downgrade.
So is there a way to revert back to the stock firmware without wipe ?
Click to expand...
Click to collapse
If you have S-OFF you can flash it through fastboot. Do you need the 1.44.0000 or the 1.43.0000?

c0de1 said:
Anyone an idea how to downgrade hboot version ?
I have update the firmware to 2.17.401.1 with a newer hboot.
Sadly this new hboot is not yet supported with cm10.1 roms so i want to downgrade.
So is there a way to revert back to the stock firmware without wipe ?
Click to expand...
Click to collapse
It's possible but I wouldn't mess around with HBOOTs, just wait until it is supported. It only takes one bad flash to fully brick your phone.

MacHackz said:
It's possible but I wouldn't mess around with HBOOTs, just wait until it is supported. It only takes one bad flash to fully brick your phone.
Click to expand...
Click to collapse
Not dangerous if he used original stock hboot 1.44.0000. I would not trust a modded hboot.

Rex2369 said:
Not dangerous if he used original stock hboot 1.44.0000. I would trust a modded hboot.
Click to expand...
Click to collapse
It is dangerous, if anything happens to the PC or cable mid flash or the flash fails for any reason then it's bricked. It's not likely but it could happen

Thanks for the replies folks, i have managed to downgrade from 1.54 to 1.44 (all stock untamperd versions)
But still doesn't for example pac 3.1 rom the touchpanel not
Maybe i must go lower to 1.43 ?
But what about the rest of the package (firmware.zip contains more than just the hboot) Must i fully downgrade or is just the hboot enough ? and is the 1.43 compatible with 2.17 jb 4.2.2 roms?
Lol i can wait, but when is the google edition available?

c0de1 said:
Thanks for the replies folks, i have managed to downgrade from 1.54 to 1.44 (all stock untamperd versions)
But still doesn't for example pac 3.1 rom the touchpanel not
Maybe i must go lower to 1.43 ?
But what about the rest of the package (firmware.zip contains more than just the hboot) Must i fully downgrade or is just the hboot enough ? and is the 1.43 compatible with 2.17 jb 4.2.2 roms?
Lol i can wait, but when is the google edition available?
Click to expand...
Click to collapse
The touch panel was part of the drivers in the firmware.zip for 2.17, it had nothing to do with the hboot. Not sure if anyone still has the old ones for you to use

c0de1 said:
Thanks for the replies folks, i have managed to downgrade from 1.54 to 1.44 (all stock untamperd versions)
But still doesn't for example pac 3.1 rom the touchpanel not
Maybe i must go lower to 1.43 ?
But what about the rest of the package (firmware.zip contains more than just the hboot) Must i fully downgrade or is just the hboot enough ? and is the 1.43 compatible with 2.17 jb 4.2.2 roms?
Lol i can wait, but when is the google edition available?
Click to expand...
Click to collapse
Now did you downgrade 1.44 from 1.54 ?

Try installing the 1.28 RUU that may downgrade the touch panel firmware.

maxal said:
Now did you downgrade 1.44 from 1.54 ?
Click to expand...
Click to collapse
What do you mean?, yes i have downgrade the hboot from 1.54 to 1.44
just used:
- fastboot reboot bootloader
- fastboot oem rebootRUU
- fastboot flash zip yourhboot.zip
- reboot reboot-bootloader
o yeah you MUST have S-OFF to do this with fastboot!

Electronic Punk said:
Try installing the 1.28 RUU that may downgrade the touch panel firmware.
Click to expand...
Click to collapse
okay and this will wipe my phone clean i think ?
or is it also posible with fastboot without wipe?

c0de1 said:
What do you mean?, yes i have downgrade the hboot from 1.54 to 1.44
just used:
- fastboot reboot bootloader
- fastboot oem rebootRUU
- fastboot flash zip yourhboot.zip
- reboot reboot-bootloader
o yeah you MUST have S-OFF to do this with fastboot!
Click to expand...
Click to collapse
Thanks but I don't have s-off, I tried but I think the new hboot may not work with revone.

c0de1 said:
okay and this will wipe my phone clean i think ?
or is it also posible with fastboot without wipe?
Click to expand...
Click to collapse
It will, I don't believe I saw 1.28 decoded so there is no seperate firmware.zip - an ota might have one but I haven't seen the touchpanel firmware in an OTA.

Electronic Punk said:
It will, I don't believe I saw 1.28 decoded so there is no seperate firmware.zip - an ota might have one but I haven't seen the touchpanel firmware in an OTA.
Click to expand...
Click to collapse
Do you know by change what the steps are to return to stock when i have unlocked hboot and s-off ?

I guess relock and then flash the ruu right from the bootloader.

If you have s-off then we can make a firmware.zip that contains the 1.44.0000 hboot and corresponding tp_SYN3202.img touch panel firmware. I've attached one built for the 1.29.1540.16 Dev Edition RUU files.
Just make sure that the modelid, cidnum, and mainver in android-info.txt of the zip match what's already on your phone (can get these values from the hboot screen) and change android-info.txt if you have to.
Code:
modelid: PN0712000
cidnum: BS_US001
mainver: 1.29.1540.16
btype:1
aareport:1
DelCache:1
hbootpreupdate:3
Then flash as mentioned in the earlier post, using 'fastboot oem rebootRUU' and 'fastboot flash zip firmware.zip'.

cschmitt said:
If you have s-off then we can make a firmware.zip that contains the 1.44.0000 hboot and corresponding tp_SYN3202.img touch panel firmware. I've attached one built for the 1.29.1540.16 Dev Edition RUU files.
Just make sure that the modelid, cidnum, and mainver in android-info.txt of the zip match what's already on your phone (can get these values from the hboot screen) and change android-info.txt if you have to.
Code:
modelid: PN0712000
cidnum: BS_US001
mainver: 1.29.1540.16
btype:1
aareport:1
DelCache:1
hbootpreupdate:3
Then flash as mentioned in the earlier post, using 'fastboot oem rebootRUU' and 'fastboot flash zip firmware.zip'.
Click to expand...
Click to collapse
I have done that, now i will test it !

c0de1 said:
I have done that, now i will test it !
Click to expand...
Click to collapse
It works like a charme, thank you so much !

MacHackz said:
It is dangerous, if anything happens to the PC or cable mid flash or the flash fails for any reason then it's bricked. It's not likely but it could happen
Click to expand...
Click to collapse
But anything you do to mod the HTC One is dangerous then of course if those scenarios you mention happens. But like you said highly unlikely.

Rex2369 said:
But anything you do to mod the HTC One is dangerous then of course if those scenarios you mention happens. But like you said highly unlikely.
Click to expand...
Click to collapse
Nah, only a hboot or possibly a radio flash can cause a brick like that, nothing else on your One is dangerous and irreversible

Wanting to convert my Telus HTC one (m7_ul) to a GPE

Hello friends, I have an S-OFF HTC One that I am finally considering converting to full GPE Edition. I was on Bigxie's 4.4 rom (http://forum.xda-developers.com/showthread.php?t=2341395) I was wondering what is the safest way to do this (if there's a thread on these forums I would GREATLY appreciate being linked) and I also have a few questions.
1) I understand that ALL my data will be erased. What is the best way to backup my data?
2) I have changed my CID to superCID but I was wondering if the conversion would work for my Canadian Telus HTC One (m7_ul) It picks up HSPA
(http://mobility.telus.com/en/AB/htc_one/index.shtml) <- link with all the details about my phone
3) *This one's a big one for me* Can I convert my phone to a GPE edition whilst having a custom recovery?

The short and sweet of it is:
1. S-OFF
2. Change CID (needed) & MID (if needed)
3. Flash 4.4 GPE conversion RUU file from http://forum.xda-developers.com/showthread.php?t=2358781
You should either copy off your data locally or sync with google.
Custom recovery will be over written when you run the zip file in step 3. You can re-flash it after the process, but why would you want to?

SaHiLzZ said:
The short and sweet of it is:
1. S-OFF
2. Change CID (needed) & MID (if needed)
3. Flash 4.4 GPE conversion RUU file from http://forum.xda-developers.com/showthread.php?t=2358781
You should either copy off your data locally or sync with google.
Custom recovery will be over written when you run the zip file in step 3. You can re-flash it after the process, but why would you want to?
Click to expand...
Click to collapse
Will I be able to get OTA? That's pretty much my whole reason as to why I am doing this.
Also, will I still be able to root my phone with superSU?

SineandCosine said:
Will I be able to get OTA? That's pretty much my whole reason as to why I am doing this.
Click to expand...
Click to collapse
With correct GPE CID and MID you will be good to receive ota. You will not receive OTA if you keep super cid.
reboot your phone in fastboot usb
Code:
fastboot getvar all
Check your MID is PN0712000 and your CID is GOOGL01 (probably not bcause super cid) TELUS normally have CID PN0712000 so you should be fine.
If you need to change CID:
Code:
fastboot oem writecid GOOGL01
fastboot reboot-bootloader
confirm correct cid change:
Code:
fastboot oem readcid
then run the GPE 4.4 ruu.exe (can be found here: http://www.htcdev.com/devcenter/downloads)

Council ngtThe
alray said:
With correct GPE CID and MID you will be good to receive ota. You will not receive OTA if you keep super cid.
reboot your phone in fastboot usb
Code:
fastboot getvar all
Check your MID is PN0712000 and your CID is GOOGL01 (probably not bcause super cid) TELUS normally have CID PN0712000 so you should be fine.
If you need to change CID:
Code:
fastboot oem writecid GOOGL01
fastboot reboot-bootloader
confirm correct cid change:
Code:
fastboot oem readcid
then run the GPE 4.4 ruu.exe (can be found here: http://www.htcdev.com/devcenter/downloads)
Click to expand...
Click to collapse
One final question, I flashed the RUU and everything went well. However, I noticed that I still had Root access. I used the pre-rooted RUU zip http://forum.xda-developers.com/showthread.php?t=2358781&nocache=1 Can I get the OTA update to 4.4.2 without messing up my phone? Do I have to remove root?

Might as well flash the non-rooted RUU..

SaHiLzZ said:
Might as well flash the non-rooted RUU..
Click to expand...
Click to collapse
Alright, thank you. Honestly, most of my issues came from me being nervous of ruining my phone, but I am now on GPE and I can't thank you guys enough.

Awesome, jsut don't S-ON..

SaHiLzZ said:
Awesome, jsut don't S-ON..
Click to expand...
Click to collapse
I really have no intention to. However, I have noticed that Android System is taking 70% of my battery. Is this a normal thing? If it isn't, how can I reduce this number?

[Q] Going back to Stock ATT

hello everyone,
i recently changed my ATT HTC to International version with Mid-PN0710000 and CID- HTC_J15 and i would like to go back to stock ATT, im currently running 4.3, S-OFF,unlocked and HBOOT-1.55.. i should change my CID and MID to ATT and then what ??

biopl said:
hello everyone,
i recently changed my ATT HTC to International version with Mid-PN0710000 and CID- HTC_J15 and i would like to go back to stock ATT, im currently running 4.3, S-OFF,unlocked and HBOOT-1.55.. i should change my CID and MID to ATT and then what ??
Click to expand...
Click to collapse
and then go there: http://forum.xda-developers.com/showthread.php?t=2541082
Best guide on how to return stock.
hope it help

alray said:
and then go there: http://forum.xda-developers.com/showthread.php?t=2541082
Best guide on how to return stock.
hope it help
Click to expand...
Click to collapse
thanks for quick reply.... downgrading Hboot, will it work on any S-off device??

biopl said:
thanks for quick reply.... downgrading Hboot, will it work on any S-off device??
Click to expand...
Click to collapse
yes
But before downgrading hboot, check what RUU are available for ATT. I think there is a 3.xx.502.x RUU that works with hboot 1.55

alray said:
yes
But before downgrading hboot, check what RUU are available for ATT. I think there is a 3.xx.502.x RUU that works with hboot 1.55
Click to expand...
Click to collapse
RUU M7 UL JB43 SENSE50 MR Cingular US 3.17.502.3 Radio 4A.19.3263.13 10.38j.1157.04 Release 334235 Signed 2
this RUU.exe should be good ryt ?

biopl said:
RUU M7 UL JB43 SENSE50 MR Cingular US 3.17.502.3 Radio 4A.19.3263.13 10.38j.1157.04 Release 334235 Signed 2
this RUU.exe should be good ryt ?
Click to expand...
Click to collapse
yes that's the one and on a side note theirs a decrypted version RUU.zip of it that will work with your current MID and CID with a small alteration to the android-info.txt
http://www.htc1guru.com/dld/ruu-zip-m7_ul_jb43_sense50_mr_cingular_us_3-17-502-3-decrypted-zip/
Instructions for Flashing RUU Zip Files:
Download the RUU.zip file and place in your ADB/fastboot folder. I would recommend renaming the zip file to something simple like ruu.zip.
Boot your phone into the bootloader by holding the power and vol up/down buttons at the same time until you see the bootloader screen or if you have your phone booted you can use the ADB command:
adb reboot-bootloader
Now use these fastboot commands:
fastboot oem rebootRUU
Should see the Silver HTC logo. Now issue this command to flash your phone using the ruu.zip file:
fastboot flash zip ruu.zip
Now the first time you issue a command to flash firmware/ruu in fastboot it only prepares the flash. You have to issue the exact command again:
fastboot flash zip ruu.zip
The green status bar usually does not reach the 100% mark. When the output in the command window is complete, you can reboot:
fastboot reboot
**Notes about the RUU.zip method. You still need to have the proper CID for the RUU. You can run the RUU.zip with super CID, but you will have to lock your bootloader first. If you are running the RUU.zip as base to downgrade all your firmware because you are going to then going to restore a stock Nandroid so the RUU might not be made for your MID, so you may need to edit the android-info.txt inside the ruu.zip to include your MID or CID.
Click to expand...
Click to collapse

clsA said:
yes that's the one and on a side note theirs a decrypted version RUU.zip of it that will work with your current MID and CID with a small alteration to the android-info.txt
http://www.htc1guru.com/dld/ruu-zip-m7_ul_jb43_sense50_mr_cingular_us_3-17-502-3-decrypted-zip/
Click to expand...
Click to collapse
i have changed my cid and mid to ATT, now just i need to run RUU.exe ryt ?

biopl said:
i have changed my cid and mid to ATT, now just i need to run RUU.exe ryt ?
Click to expand...
Click to collapse
yes

biopl said:
i have changed my cid and mid to ATT, now just i need to run RUU.exe ryt ?
Click to expand...
Click to collapse
do NOT try going S-On with that hboot version!

nkk71 said:
do NOT try going S-On with that hboot version!
Click to expand...
Click to collapse
i dont plan to

biopl said:
i dont plan to
Click to expand...
Click to collapse
:good::good:

nkk71 said:
:good::good:
Click to expand...
Click to collapse
I don't understand .. the only time it is safe to go s-on is after flashing the signed ruu
why are you saying different ?
Keep in mind I'm on the side of never going s-on for any reason!

clsA said:
I don't understand .. the only time it is safe to go s-on is after flashing the signed ruu
why are you saying different ?
Keep in mind I'm on the side of never going s-on for any reason!
Click to expand...
Click to collapse
hboot 1.55 introduced an interesting patch, when going from S-Off to S-On, after a few reboots it comes back with "tamper detected - rebooting", and then TAMPERED is back in bootloader.
NB: i cannot confirm this to be 100% true, but i've seen more than a few posts that confirm, even after a full signed ruu etc etc etc, this has happened.
only way to avoid it was to go s-on before updating to 1.55 (hence my guide says to downgrade to lowest version)

Which CID gets the fastest OTA?

My CID is htc_001 and it sucks i allways get ota updates very slow compared to the other cids, so my question is to which cid should i change in order to get the fastest ota updates?
And another question, i flashed TWRP and rooted my phone, i still can get ota updates?
Again sorry for my noobish questions and my bad english.

You will need to be fully stock to get OTA's, recovery, no missing apps, stock rom etc.
and as for CID, well at a guess I would say super cid would get the updates first, however, recently ive heard its very dependant on your operator, country and whether you brought your phone or its on contract.
Im in the UK and on CID HTC__001 too, I read today that HTC are releasing the sense 6 update to UK customers somewhere around the 11th June, so Wednesday. im all ready for it, just got to flash stock recovery.

Seanie280672 said:
You will need to be fully stock to get OTA's, recovery, no missing apps, stock rom etc.
and as for CID, well at a guess I would say super cid would get the updates first, however, recently ive heard its very dependant on your operator, country and whether you brought your phone or its on contract.
Im in the UK and on CID HTC__001 too, I read today that HTC are releasing the sense 6 update to UK customers somewhere around the 11th June, so Wednesday. im all ready for it, just got to flash stock recovery.
Click to expand...
Click to collapse
So all i need to do to get updateds is to flash stock recovery? (i can keep the root, right?)
How can i flash the stock recovery?

Num_Lock said:
So all i need to do to get updateds is to flash stock recovery? (i can keep the root, right?)
How can i flash the stock recovery?
Click to expand...
Click to collapse
Code:
fastboot flash recovery recovery.img

alray said:
Code:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Ok... do I need a file or something? can you explain more detailed?
I'm sorry for being noob it's just I'm used to samsung phones development and the htc development is different with new stuff (s off unlocking ruu and whatever) so i need you to explain me more detailed.
Thank you.

Num_Lock said:
Ok... I need a file or something? can you explain in more details?
I'm sorry for being noob it's just I'm reguler to samsung phones development and the htc development is different with new stuff (s off unlocking ruu and whatever) so i need you to explain me more detailed.
Thank you.
Click to expand...
Click to collapse
you need the stock recovery file (recovery.img) from the same version firmware of your phone. i.e if you phone is on 4.19.401.1 and you want to update to 5.20.401.1, you need the recovery.img file from the 4.19.401.1 firmware.
also read this: http://forum.xda-developers.com/showpost.php?p=52894276&postcount=9

alray said:
you need the stock recovery file (recovery.img) from the same version firmware of your phone. i.e if you phone is on 4.19.401.1 and you want to update to 5.20.401.1, you need the recovery.img file from the 4.19.401.1 firmware.
also read this: http://forum.xda-developers.com/showpost.php?p=52894276&postcount=9
Click to expand...
Click to collapse
OK and one more thing, i need to s off to change my cid?

Num_Lock said:
OK and one more thing, i need to s off to change my cid?
Click to expand...
Click to collapse
yes you need s-off, and if you change your cid, it must match your sw version! some software version only have a unique compatible cid and other have many compatible cid. i.e .401 sw version can use many different cid: HTC__001, HTC__Y13, HTC__032, HTC__203 etc etc..... but .502 version can only use one cid: CWS__001
to change cid:
Code:
fastboot oem writecid YOUR_CID [COLOR="Green"]<---- in most cases, start with HTC in capital letter, 2 underscores and 3 digits, always 8 characters total.[/COLOR]
i.e:
Code:
fastboot oem writecid HTC__001
you can read your actual cid with this command:
Code:
fastboot oem readcid

alray said:
yes you need s-off, and if you change your cid, it must match your sw version! some software version only have a unique compatible cid and other have many compatible cid. i.e .401 sw version can use many different cid: HTC__001, HTC__Y13, HTC__032, HTC__203 etc etc..... but .502 version can only use one cid: CWS__001
to change cid:
Code:
fastboot oem writecid YOUR_CID [COLOR="Green"]<---- in most cases, start with HTC in capital letter, 2 underscores and 3 digits, always 8 characters total.[/COLOR]
i.e:
Code:
fastboot oem writecid HTC__001
you can read your actual cid with this command:
Code:
fastboot oem readcid
Click to expand...
Click to collapse
I want to change to supercid, it supports my version? and with s off i can still get ota right?

Num_Lock said:
I want to change to supercid, it supports my version? and with s off i can still get ota right?
Click to expand...
Click to collapse
on some sw version, you will not receive ota update with supercid. supercid is used to bypass cid check when installing some rom/ruu.
for s-off question, read the link i have posted at post #6

alray said:
on some sw version, you will not receive ota update with supercid. supercid is used to bypass cid check when installing some rom/ruu.
for s-off question, read the link i have posted at post #6
Click to expand...
Click to collapse
In my version i will get ota updates with supercid?
Thanks for your help i really appreciate it.

Num_Lock said:
In my version i will get ota updates with supercid?
Thanks for your help i really appreciate it.
Click to expand...
Click to collapse
idk, refer to the android-info.txt of the ota.zip and you'll see all supported cid.

USA developers edition get ota first every time
from HTC One

Htc One AT&T trying to upgrade to lollipop using official RUU - get error 155

Have a Htc One (AT&T, but unlocked) and it is running Android 4.4.2 . I see there is an update for lollipop in form of the RUU officially from HTC (7.23.502.9).
http://www.htc.com/us/support/htc-one-att/news/
I attempted to install it but get an error 155.
Using Windows 10.
Drivers are installed.
Tried several RUU's but with same result. Tried it on 2 laptops (both windows 10), have no accesss to windows 7 or windows xp at the moment to try anything else.
Attaching a screenshot of the bootloader screen of my phone.
Any help is appreciated.
Thank you,

BorisZX6R said:
Have a Htc One (AT&T, but unlocked) and it is running Android 4.4.2 . I see there is an update for lollipop in form of the RUU officially from HTC (7.23.502.9).
http://www.htc.com/us/support/htc-one-att/news/
I attempted to install it but get an error 155.
Using Windows 10.
Drivers are installed.
Tried several RUU's but with same result. Tried it on 2 laptops (both windows 10), have no accesss to windows 7 or windows xp at the moment to try anything else.
Attaching a screenshot of the bootloader screen of my phone.
Any help is appreciated.
Thank you,
Click to expand...
Click to collapse
Your phone need to be at least on hboot 1.57 (6.xx.502.x) to use a 7.xx.502.x RUU.
Since your phone is S-OFF you can esiliy update your firmware and flash the RUU.
Btw, are you still using the AT&T network ? If not, it would be the right time to flash a de-branded ruu version (like 7.19.401.51) to get rid of at&t's bloatware...

alray said:
Your phone need to be at least on hboot 1.57 (6.xx.502.x) to use a 7.xx.502.x RUU.
Since your phone is S-OFF you can esiliy update your firmware and flash the RUU.
Btw, are you still using the AT&T network ? If not, it would be the right time to flash a de-branded ruu version (like 7.19.401.51) to get rid of at&t's bloatware...
Click to expand...
Click to collapse
Thank you for your time and response. I will think about what RUU is best for me. I am currently on the T-Mobile network with this phone and so far there is no indicator that will change anytime soon. I will try and post my response.
Thank you again!

alray said:
Your phone need to be at least on hboot 1.57 (6.xx.502.x) to use a 7.xx.502.x RUU.
Since your phone is S-OFF you can esiliy update your firmware and flash the RUU.
Btw, are you still using the AT&T network ? If not, it would be the right time to flash a de-branded ruu version (like 7.19.401.51) to get rid of at&t's bloatware...
Click to expand...
Click to collapse
Unfortunately I am still hunting for an RUU that will bring the hboot to version 1.57. All the ones I tried either fail with error 155 or they leave me on the same version of hboot. Trouble finding an appropriate RUU... If you know where I can get one that will upgrade the hboot to 1.57 please guide me in the right direction.
Thank you!

BorisZX6R said:
Unfortunately I am still hunting for an RUU that will bring the hboot to version 1.57. All the ones I tried either fail with error 155 or they leave me on the same version of hboot. Trouble finding an appropriate RUU... If you know where I can get one that will upgrade the hboot to 1.57 please guide me in the right direction.
Thank you!
Click to expand...
Click to collapse
You don't need to flash a RUU to update your hboot, just update your firmware (flash a firmware.zip) like this one. Make sure that your CID and MID are listed in the android-info.txt file, if not, edit the android-info.txt file so your CID and MID are listed (Better to use notepad++).
Code:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot-bootloader
Then you can flash a 7.xx.xxx.x RUU (don't forget that your CID and MID must match the RUU you want to flash (You can easily change your CID and MID when S-OFF)

alray said:
You don't need to flash a RUU to update your hboot, just update your firmware (flash a firmware.zip) like this one. Make sure that your CID and MID are listed in the android-info.txt file, if not, edit the android-info.txt file so your CID and MID are listed (Better to use notepad++).
Code:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot-bootloader
Then you can flash a 7.xx.xxx.x RUU (don't forget that your CID and MID must match the RUU you want to flash (You can easily change your CID and MID when S-OFF)
Click to expand...
Click to collapse
Thank you very much, I will attempt to do this and I will post my results once I had a chance to try it.
One more thing, isn't having a super CID an advantage?! Is 11111111 a super CID?!
Thank you!

BorisZX6R said:
Thank you very much, I will attempt to do this and I will post my results once I had a chance to try it.
One more thing, isn't having a super CID an advantage?! Is 11111111 a super CID?!
Thank you!
Click to expand...
Click to collapse
Yes, supercid is 11111111 so your CID isn't a problem. Just make sure that your MID also match the ruu you want to use (or change it if needed). If you MID is still the original, it should be PN0712000 so you can either use an AT&T or Developer Edition RUU (x.xx.1540.x). Otherwise if you want to use the WWE version (x.xx.401.x) You'll have to change your MID to PN0710000.

alray said:
You don't need to flash a RUU to update your hboot, just update your firmware (flash a firmware.zip) like this one. Make sure that your CID and MID are listed in the android-info.txt file, if not, edit the android-info.txt file so your CID and MID are listed (Better to use notepad++).
Code:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot-bootloader
Then you can flash a 7.xx.xxx.x RUU (don't forget that your CID and MID must match the RUU you want to flash (You can easily change your CID and MID when S-OFF)
Click to expand...
Click to collapse
It worked. For a moment the output in the command window seemed like it was giving errors (unfortunately it was very late and I did not copy the output) but in the end I realized it updated the hboot and I was able to flash a different RUU.
Thank you for all your help!