Database Info

[ThinkTank] Rebrand the unbrandable SLCD

This thread is supposed to become a HowTo eventually. In fact I will write it like a HowTo, but with some remarks and questions in between, as I have not tried the procedure (still on unrooted stock rom atm). I just thought I post this here anyway, as it might be helpful for someone.
Until all the questions are answered and someone succeded to rebrand, consider this thread as a think tank, with some of the thinking already done
So what is this all about? There often is the question how to flash the correct stock rom for warranty purposes. This is an easy task if the correct RUU is available. Unfortunately the recent SLCD desires often lack a corresponding RUU. If you flash the 2.1 ruu that rebrands an amoled, you will end up with a black screen, making an ota update nearly impossible.
But now S-Off is in the wild, there might be a workaround for that. There are just some things that have to be considered first... Things that I am not sure of will be marked in red. I will explain some more details on the explicit steps when the principle is confirmed working. If you dont have a clue how to perform those steps right now, it might be better to wait for the more detailed version.
As always: Do this at your own risk.
[UPDATE]
Some advances have been made here thanks to Hummelchen, who volunteered to try this procedure on his desire. It was a T-Mobile germany branded Amoled device, but care was taken to ensure that this procedure also works on SLCD without going through a phase where the screen stays black. Nonetheless, a final test still has to be done.
I updated the HowTo, but better wait until Hummelchen has confirmed it, as he was the one who tried it.
Prereqs:
- A desire to rebrand with S-Off
- fastboot and a zip-sign tool ready to run
- A RUU that corresponds to your carrier (that would normally break your display)
- The froyo OTA package that updates from the software version included in the RUU
Rename the ota_update to 'update.zip' and copy it to the root of your sd on the phone (better not forget that)
Extract the rom.zip from the RUU (double check CID in android-info.txt, compare with http://forum.xda-developers.com/showthread.php?t=631519) by running the RUU (without phone connected) and fetching the file out of your temp folder
extract the zip and delete the hboot file and the recovery
Extract OTA, extract the firmware.zip within the OTA and copy the included recovery.img into the same directory where the rest of the RUU files are
(maybe not really needed: edit android-info.txt like here)
zip, sign
boot into fastboot
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip <your_signed_zip>
Don't try to boot into the system now. As the kernel does not have SLCD drivers, all will be black
Instead boot into recovery and apply the OTA -> you will end up on a totally debranded/unrooted/s-on desire!
Thanks go to Hummelchen, who came up with lots of ideas and the guts to just try it on his own device. Also to ieftm for a little support on fastboot commands.
mblaster
For TMobile Germany/UK/CzechRep./Netherlands (according to the CID info in the OTA and base ROM) users, Hummelchen has prepared something nice:
Hummelchen said:
Okay, here is it: CustomRUU
# MD5
9ff8adf8c2471c3e2d085203d4923904 customRUU.zip
# SHA1
b5c3e174af3a797ed4f500d573794db74c595d35 customRUU.zip
I didn't found another way as fastboot. But if this RUU works, we could write a simple script to install it.
This customRUU comes without Hboot. So everyone could test it without risk.
This is the way:
1. Go to fastboot (the script could send: adb reboot-bootloader)
2. type: fastboot erase cache
3. type: fastboot oem rebootRUU
4. type: fastboot flash zip customRUU.zip
5. type: fastboot reboot
The phone will reboot to T-Mobile Stock rom.
-----------------------------------------------------
Now the way to do it on other roms (don't tested) with hboot.
1. Strip the rom.zip from your 2.1 RUU and extract it to your favorite folder.
2. delete recovery and hboot.
3. Open the OTA.zip, open the firmware.zip which is in it and extract the recovery.img to the first folder.
4. Open android-info.txt and delete hbootpreupdate:2. Save it!
5. Now zip the files in the first folder and use the commands above.
6. Now you have a S-Off Hboot and the new recovery. You should be able to flash the OTA.zip with your recovery. This OTA will overwrite your Hboot.
That's it
Click to expand...
Click to collapse

Has anyone tested?
Sent from my HTC Desire using XDA App

At least no one reported back. Seems like the interest in this topic is not too great.

I've found a RUU on T- Mobile AT to rebrand a SLCD Desire (froyo). It's the solution for my problem.
Sent from my HTC Desire using XDA App

A little question: I’ve i use the RUU_Bravo_TMO_UK_1.21.110.4_Radio_32.36.00.28U_4.06.00.02_2_release_127570_signed.exe the SLCD will brick (HBOOT 0.80). Could i use Fastboot to flash the Update.zip with Froyo without root (HBOOT 0.93)?
So i have to go to the bootloader and press „Power“, plug it to my notebook an send a „fastboot flash update.zip“ ? Could it work?
If this works, i will get a rebranded SLCD desire

Hummelchen said:
A little question: I’ve i use the RUU_Bravo_TMO_UK_1.21.110.4_Radio_32.36.00.28U_4.06.00.02_2_release_127570_signed.exe the SLCD will brick (HBOOT 0.80). Could i use Fastboot to flash the Update.zip with Froyo without root (HBOOT 0.93)?
So i have to go to the bootloader and press „Power“, plug it to my notebook an send a „fastboot flash update.zip“ ? Could it work?
If this works, i will get a rebranded SLCD desire
Click to expand...
Click to collapse
No, you will loose S-OFF since it will flash an unpatched HBOOT. Hence fastboot will be as good as useless.

Dragooon123 said:
No, you will loose S-OFF since it will flash an unpatched HBOOT. Hence fastboot will be as good as useless.
Click to expand...
Click to collapse
Also No . I think you can't even fastboot flash a .zip file. €: OK, just ReadTFM ... Fastboot flash update update.zip seems to work. But as stated, don't do it.
You will have to unpack the zip and flash the images manually (skipping hboot obviously).
@Hummelchen: Do you have a german TMo Desire? €: OK, just noticed the flag below your avatar...

mblaster said:
@Hummelchen: Do you have a german TMo Desire? €: OK, just noticed the flag below your avatar...
Click to expand...
Click to collapse
Yes. My Amoled Desire have a stucking pixel and TMo will send a SLCD. I hate the hard way
Sent from my HTC Desire using XDA App

Hummelchen said:
... the SLCD will brick (HBOOT 0.80) ...
Click to expand...
Click to collapse
Hummelchen said:
Yes. My Amoled Desire has a stucking pixel ...
Click to expand...
Click to collapse
Do you want to rebrand a SLCD or AMOLED Desire
Because with AMOLED you can just install the Eclair RUU and apply the OTA update...

My next desire will be an SLCD one. But I don't want to root as long as there's no easy way back.
Sent from my HTC Desire using XDA App

Hummelchen said:
My next desire will be an SLCD one. But I don't want to root as long as there's no easy way back.
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
That's why I started this thread here. In theory my plan should work, but i am quite reluctant to test it myself just for the kicks. I am also on a german T-Mobile Desire.
€: I just had a nice idea, I just need to know if the current custom recoveries are able to apply a patched/resigned or even an unpatched OTA-update.zip.
This would allow the following:
1) Extract the rom.zip from the RUU (the one that would break slcd), unzip it, delete the hboot and recovery, zip again, fastboot flash update rom.zip -> everything but hboot and recovery are stock
2a) Boot into recovery and flash the ota.zip file and be stock/unrooted/s-on OR
2b) remove the firmware.zip from the ota.zip (also remove 'write_firmware_image("PACKAGE:firmware.zip", "zip");' from the updater script), zip, sign, flash from recovery. Manually fastboot flash boot/radio/rcdata from the omitted firmware.zip. This will bring you to a stock/unrooted system, but with s-off hboot and a custom recovery. This has the advantage, that you can make an actual nandroid of a stock system without root files sticking around. From there you can play around with your system as you like and always unroot in 2 simple steps by restoring the stock nandroid and fastboot flashing the firmware.zip (removing custom recovery and hboot from the phone).
I am just not sure if the custom recoveries handle the ota packages as intended (with all the file patching going on there), but i think there is no reason why it should not work.

Hmm... I could reroot my Amoled desire and test it
If hboot and recovery not affected i can flash the whole ruu on fail, right?
Edit: I've extracted the Rom.zip, deleted hboot and recovery and created a signed update.zip
Sent from my HTC Desire using XDA App

Would be interesting to see the result. I think as long as you can enter the bootloader (the one from alpharev) you cant really screw it up, as you can always install a recovery or system via fastboot. I think the RUU also only depends on a working hboot.
So if you are careful with that hboot (and remove it from the ota also), you should be fine (I hope...).
Might be that you need a goldcard for flashing the RUU to get back to stock afterwards, but I am not sure of that.
It would be great if you tried that, as it would make sure that there is a way back to stock for SLCD owners without a friendly RUU. Please report back if you have been brave enough to try.

ok, i've done it. I S-off'ed my Desire and try to flash the rom.zip of the T-mobile RUU without Hboot and recovery.
Flashing the system.img didn't work because it needs the original Hboot. Fastboot says: File is to large. Same on Recovery.
Flashing boot.img works, but without system... It seems the 0.80 Hboot has another patitionsize as 0.93. That's stupid.

Thats strange. The system image of the TMO RUU (I think i have downloaded the newer one of the 2 available) is only 222 MB. Standard size for Data is 258 MB, so it should fit in withut problems. I am quite sure that all the official hboots have the same partition size.
Did you by chance install an alpharev hboot with modded partition table, like the N1 table (149 MB) or the modded Sense Table (180 MB)?
Did you try to flash only the system.img via fastboot flash system instead of fastboot flash update zipfile.zip?
BTW: Thanks for trying.

Thats strange. The system image of the TMO RUU (I think i have downloaded the newer one of the 2 available) is only 222 MB. Standard size for Data is 258 MB, so it should fit in withut problems. I am quite sure that all the official hboots have the same partition size.
Click to expand...
Click to collapse
Hm.. Strange
Did you by chance install an alpharev hboot with modded partition table, like the N1 table (149 MB) or the modded Sense Table (180 MB)?
Click to expand...
Click to collapse
I had it originally. I start the Iso, S-Off and after that i try to flash the rom.zip.
Did you try to flash only the system.img via fastboot flash system instead of fastboot flash update zipfile.zip?
Click to expand...
Click to collapse
I try:
- Fastboot update rom.zip
- Fastboot flash system system.img
- Fastboot update system.zip (pack it with 7zip)
I also try to flash the rom.zip and the system.zip with clockworkmod recovery
Nothing works... :/

You could try a 'fastboot erase system -w' before flashing. This clears /system /data and /cache. Perhaps it helps.
€: Come to think about it this really makes sense. I guess the flashing routine checks how much space is free, as it perhaps does not necessarily delete the existing files on the partition. I don't know how the flashing process works, but maybe it is more similar to a file copy operation than a linux 'dd'.

mblaster said:
You could try a 'fastboot erase system -w' before flashing. This clears /system /data and /cache. Perhaps it helps.
Click to expand...
Click to collapse
It didn't work. Tested 2 mins ago

Seems like this problem is more or less known.
http://forum.xda-developers.com/showpost.php?p=8596521&postcount=38
Maybe we could ask ieftm for some help. €: Sent him a message.

Another thought: Did you use 'fastboot update filename.zip' or 'fastboot flash update filename.zip'? I've seen both syntaxes and they might do something different. Perhaps just try the one you didn't use.

[Q]Hboot update: from 6.98.xxxx to 2.00.2002

Hello guys! I do know that I should ask this question in "GUIDE: new hboot 2.00.2002 for sense3.0 adnroid 2.3.5" thread but you know I can't do it because I do not have enough posts.
To admins: if you find my question useful then please replace this post to the appropriate forum thread.
Finally my question:
I have Desire S, it was S-Off'ed by Revo, then Rooted and now I have 6.98.1002 Hboot (and I'm using Proxuser's Desire S Gingerbread 2.3.5 with Sense 3.0 {v0.5} ROM).
All I want now is to upgrade my bootloader to 2.00.2002 and then to flash a new stock kernel.
Although we have a detailed manual by Biglsd and Mihaibuda, I can't perform it.
As manual says, I should
b1)In cmd run the following commands (after each command press enter):
adb devices
adb shell
su
Click to expand...
Click to collapse
but after "su" I have this issue:
and I think smth is going wrong because if i try then to flash new hboot using
"dd if=/sdcard/hboot.img of=/dev/block/mmcblk0p18"
adb tells me that it can not find file or directory.
May be someone knows what's the problem?
PS. I have read all "GUIDE: new hboot 2.00.2002 for sense3.0 adnroid 2.3.5" thread and found there a jorgen2009's way to update hboot http://forum.xda-developers.com/showpost.php?p=17059447&postcount=63. But this way is only for those guys who have old HBOOT ENG S-OFF. Or I'm mistaken?

Did you copy the hboot.img to your sdcard? It's not necessary to write the su command. Write directly the two dd commands. I did the whole process last night successfully...

Alex_whatever, thank you man for your answer. I have just performed flashing new Hboot. Of course I copy hboot.img to the root directory of my sdcard before I start the whole procedure. And as people in "GUIDE: new hboot 2.00.2002 for sense3.0 adnroid 2.3.5" thread told, once I see a "#" symbol in cmd, I'm a superuser. So it is not necessary to write "su" as u tell me. But the problem was in incorrect sdcard mounting. After I mounted /sdcard via appropriate menu in recovery I am able to access it via "dd" comands.

Messengerskiller said:
But the problem was in incorrect sdcard mounting.
Click to expand...
Click to collapse
Oh, ok i got it! I hadn't any sdcard mount issue. That's why i asked if you copy the hboot.img to the sdcard..

Ok, Alex_whatever, may be you tell me how did you flash kernel after flashing new hboot (if you did it)?
If I put htc-kernel-2.6.35.10-g71.blablabla.zip into the root directory of sdcard, then boot in recovery then choose "install zip from sdcard" and choose copied zip, it does flash it, but after this htc does not boot. It only boots in recovery again and again if I try to "reboot system now" from recovery.
So what's the problem now?

Did you make a backup of your rom before hboot flash? Because after the hboot flash you have to wipe all the partitions and restore the rom. Then you flash the kernel and in the end you have to flash PG88IMG.zip via bootloader. You must copy PG88IMG.zip to your sdcard.
If you didn't a backup, wipe the partitions and flash the rom again. Then flash the kernel and finally flash PG88IMG.zip.

Seems like I'm an amazing noob. F##k yeah.
My mother used to ask me "baby, don't you forget to make a backup before?" and I always answered "of course yes!". So I have a nandroid backup and it's quite nice, isn't it? (=
Although everything seems to be clear I forget about PG88IMG.zip. Brickwall wants to meet my head, I know. So I boot in recovery, wipe everything, do nandroid backup, then flash kernel, than try to flash PG88IMG.zip via recovery and of course it tells me that process aborted.

Ok. Let's sum up.
All the things one should know to update his/her hboot seems to be clear.
Then to flash new kernel one should flash kernel's zip from recovery and then flash lib.img (PG88IMG.zip) via bootloader.
If it were written in "GUIDE: new hboot 2.00.2002 for sense3.0 adnroid 2.3.5" thread, it would be manу times easier for noobs like me to upgrade their htc.
Thank you, Alex_whatever , anyway.

Messengerskiller said:
My mother used to ask me "baby, don't you forget to make a backup before?" and I always answered "of course yes!". So I have a nandroid backup and it's quite nice, isn't it?
Click to expand...
Click to collapse
Hahahah... Don't worry man! You can always reflash your rom. After the kernel flash remember to reboot to bootloader and follow the on-screen instructions to flash the PG88IMG.zip.
Cheers.

[GUIDE][07/01] Flashing ICS FIRMWARE 3.12 base img files.

DISCLAIMER. Do it at your own risk.. I am not responsible for bricks....bla bla bla, usual stuff.
If in doubt-STAY AWAY!
Q/A First.
Do I HAVE to flash this FW? - YES, if you want to flash ICS 4.0.3 based rom. If not, it just won't boot. Latest firmware works with previous (2.3.4,2.3.5,4.0.1) roms.
Do I NEED SuperCID? - YES, it will help in case you need to revert and if your CID is not on the update.zip list
Will I lose S-OFF? - NO
Can I use this FW with earlier builds? - YES
Will I lose fastboot commands like flash splash1? - Yes
Is it safe? Never 100% but no fails so far. Flash at your own risk
Can I revert to previous hboot, like 1.17? Yes, make sure you are superCID.
Any disadvantages? None so far
Any advantages? More optimised fw/drivers for ICS. Users report faster ROM operation.
Why does it say ***LOCKED*** in bootloader? Because hboot is locked (don't panic)
Can I go back to **REVOLUTIONARY**? Yes, flash 1.17 HBOOT at the bottom of OP.
HOW TO
0. Make sure you are S-OFF and superCID. Check HERE
1. Download zip from HERE Credits to rmk40, this is FW I used).
2. Do nandroid backup.
3. Copy/paste PG58xxxxx to the root of your microSD
4. Make sure MD5 match!!! MD5 checker I use HERE
4. Make sure MD5 match again!!!
4. And once again, make sure MD5 match.
5. Reboot into bootloader (if you don't know how to do it, don't do any of that at all)
6. microSD will be scanned and will ask you if you want to update, press +vol for YES
7. Follow onscreen instructions.
8. Now just pull sd card out if you don't have microSD reader or delete PG58xxxx if you do. PG58 will prevent you from going into recovery if phone sees it.
9. Reboot into bootloader-go to recovery
10. Put your SD card back in
11. Reboot or flash new rom
12. You are done. Just delete that PG58 file so it doesn't stop you getting into recovery again.
REVERT TO 1.17 HBOOT
ziggy1001 said:
Direct link with MD5
http://forum.xda-developers.com/showpost.php?p=20681060&postcount=22
Click to expand...
Click to collapse
Paste on root of SD card, make sure MD5 matches. Repeat update from bootloader (steps 1-12 from above) and you should be done.
If anyone has anything to add, feel free.
Remember, if you flash RUU, then process is slightly different and will most likely involve unlocking via HTCDEV (haven't really looked into it)

This is for all Sensation's, right?

aNYthing24 said:
This is for all Sensation's, right?
Click to expand...
Click to collapse
Indeed. Mike provided img files from both RUUs. I'm pretty sure it's safe to mix and match, since we ran 1.73 RUUs on normal Senny, but wouldn't recommend risking it just in case. But there is always a brave one ... LOL Who is it gonna be this time?

I've already followed the steps as in mike1986's thread and all went well, but what is the benefit of reverting to 1.17 HBOOT?

piplewis said:
I've already followed the steps as in mike1986's thread and all went well, but what is the benefit of reverting to 1.17 HBOOT?
Click to expand...
Click to collapse
Advanced fastboot commands

nice work on the thread mate, do you want to include a note that mikes files will update the radio too, just make sure everyone is clear on what is updates

Does it improve performance noticeably? I'm just a bit overwhelmed, sorry.

Hawke84 said:
nice work on the thread mate, do you want to include a note that mikes files will update the radio too, just make sure everyone is clear on what is updates
Click to expand...
Click to collapse
So there will be no possibility of downgrading the radio?...our i have to revert to 1.17 to flash older radios?
I have 10.56 and i m satisfied with it...

jjdoctor said:
So there will be no possibility of downgrading the radio?...our i have to revert to 1.17 to flash older radios?
I have 10.56 and i m satisfied with it...
Click to expand...
Click to collapse
You can still do it via PG58 update, but not via fatboot flash radio radio_image_name.img

I want to try this so bad, but I am scared as heck! What do we need to know before doing this? Such as, what do we risk other than an all out brick? Will we be able to go back to what we have now?
Matt

tinky1 said:
Find 1.17 HBOOT in PG58xxxx in THIS THREAD (provided by ziggy1001)
)
Click to expand...
Click to collapse
Direct link with MD5
http://forum.xda-developers.com/showpost.php?p=20681060&postcount=22

Looks like it worked for me. I am restoring a ROM right now. After that, ill revert back to the previous bootloader. So far, so good!
So now, where do you guys see the improvements?
Matt

I just tried to flash it but it have me CID error... I used supercid by this method
http://forum.xda-developers.com/showthread.php?t=1192630
What could be wrong?

jjdoctor said:
I just tried to flash it but it have me CID error... I used supercid by this method
http://forum.xda-developers.com/showthread.php?t=1192630
What could be wrong?
Click to expand...
Click to collapse
I am getting ready to flash it, but I did supercid by the method in the sticky-noted post near the top of the Sensation forums.
[Guide] to Installing S-off, Unlocking, ClockWork, Root, SuperCID & S-on

jjdoctor said:
I just tried to flash it but it have me CID error... I used supercid by this method
http://forum.xda-developers.com/showthread.php?t=1192630
What could be wrong?
Click to expand...
Click to collapse
Does your bootloader screen show **locked** in pink color ?

hsnmz said:
Does your bootloader screen show **locked** in pink color ?
Click to expand...
Click to collapse
Yes it shows Locked in pink... My hboot is now 1.20
My radio didn't upgrade... I still have 10.56....
I flashed it over Ultimite ROM... i thought it will erase my ROM but nothing changed....:-/
It flashed everything but showed cid error in last one... I don't know what was it....
So now i have to go back to 1.17, supercid using adb and fish 1.20 again?
I supercid using terminal emulator... I guess that didn't work...

jjdoctor said:
I supercid using terminal emulator... I guess that didn't work...
Click to expand...
Click to collapse
Wait, what?!
You tried to SuperCID via Terminal Emulator, while the phone was running? oO
What's wrong with following the instructions in the stickied guide and using adb?

Never in my life i used adb stuff... :-/
never tried to learn it either... But i guess i have to learn it now..
Now tell me what to do?
should i download hboot 1.17, flash it and then reflash 1.20 after supercid?

jjdoctor said:
Never in my life i used adb stuff... :-/
never tried to learn it either... But i guess i have to learn it now..
Now tell me what to do?
should i download hboot 1.17, flash it and then reflash 1.20 after supercid?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1192300 this is the thread I have followed time and time again with success step 4 is to do cid

is this firmware just relevent to ics roms or can it be used on 3.0/3.5 roms??????

[HBOOT] | 29-05-2012 | 7.00.1002 | Reengineered 2.00.002

Ok guys too many people having issues with new rom sense 4 not booting up...
So here is a renegineered hboot 2.00.002...
After this all roms including all sense4 versions and even russian roms will work with no issues...
Old roms will continue to work as well with no problems
This should be used only by people having hboot starting with 6.98...
People with hboot 2.00.002 don't need this...
People with hboot starting with 0.98 can either flash 2.00.002 or this hboot...
Steps :
1. Download attachment and copy to root of sd card (i.e not inside any folder)
2. Reboot into bootloader
3. Select bootloader
4. The attachment will be auto detected and updated within 5-7 sec max.
5. Now go to recovery again select format all partitions except sd card if you dont want to flash a new rom else wipe cache and dalvik cache if you wnat to just update hboot and continue with old rom (Remember next time you flash a new rom select format all partitions except sd card from recovery).
* Formatting all partitions except sd card from recovery is recommended after hboot upgrade !
6. Don't forget to delete the attachment from the sd card.
7. Done
Tested well and works perfect !
Also fastboot commands work except for the 1 to change id...everything else works as it should and you can always revert back with no issues
HBoot Download
md5 : d44d182207a69c16f5272604c00665e6

Why don't you post how to revert to old hboot and S-on (in case is needed)...that will be a usefull post

I'll do it now One question - does this give you Eng S-OFF too??
Edit: vampire36, just noticed something - we both joined xda on the same day Not that it means anything at all, just an interesting detail.
Sent from a device waiting for the Kernel 3 source code. WAKE UP HTC !!!!!

shrome99 said:
I'll do it now One question - does this give you Eng S-OFF too??
Edit: vampire36, just noticed something - we both joined xda on the same day Not that it means anything at all, just an interesting detail.
Sent from a device waiting for the Kernel 3 source code. WAKE UP HTC !!!!!
Click to expand...
Click to collapse
Ohhh thats cool and interesting
S-off well it keeps the state as it..so if its S-off remains S-off...

.sh4d0w. said:
Why don't you post how to revert to old hboot and S-on (in case is needed)...that will be a usefull post
Click to expand...
Click to collapse
Okies will look into it...and will need to test the method before posting
But will do something about it

Could you please explain what the issues and differences are?
Is this to do with system.lib?
Thanks in advance
Swyped from my DesireS

Well, i tried to flash the full Sense 4 port for 3 hours yesterday, but it always led to a black screen, since the system partition got filled up and the updater-script was trying to mount the lib partition, which wasn't there. This fixes these errors by adding a lib partition. It will be a problem in all future ROMs, so I'm flashing this now....

And what will be the advantage of this over the 2.00.2002 one? Besides the flashing procedure which was by adv for the eng 2.0.2002
Sent from my HTC Desire S

I will try it.
Does it can be helpful with Google Maps compass?
My Google Maps compass didn't work on all Android4.0 roms....;'(

I tried this Hboot, but i ran into troubles.
First of all the phone rings before it goes into the bootloader... never happend.
When i start the rom, the same.
The cam is also broken. The cam pic looks wierd...
Maybe I done something wrong?
Edit:
Now I went back to this one:
PG88IMG-OLD-RADIO-20.28b.30.0805U_38.03.02.11
Everything works fine again.

ben_pyett said:
Could you please explain what the issues and differences are?
Is this to do with system.lib?
Thanks in advance
Swyped from my DesireS
Click to expand...
Click to collapse
shrome99 said:
Well, i tried to flash the full Sense 4 port for 3 hours yesterday, but it always led to a black screen, since the system partition got filled up and the updater-script was trying to mount the lib partition, which wasn't there. This fixes these errors by adding a lib partition. It will be a problem in all future ROMs, so I'm flashing this now....
Click to expand...
Click to collapse
I guess shrome answered it...though we can always change the updater script but it will be a pain to do each time...So this way you don't have to worry about it...partition is added and ics roms i guess will go this way...

datoml said:
I tried this Hboot, but i ran into troubles.
First of all the phone rings before it goes into the bootloader... never happend.
When i start the rom, the same.
The cam is also broken. The cam pic looks wierd...
Maybe I done something wrong?
Click to expand...
Click to collapse
These are rom issues due to new partition and nothing to do with hboot...you can just do a clean install of the rom...and then check
As i have said do foramt all partition except sd card and then flash the rom...all will be well

Is this an updated of the eng 2.00.2002?
Or it s older

vampire36 said:
These are rom issues due to new partition and nothing to do with hboot...you can just do a clean install of the rom...and then check
As i have said do foramt all partition except sd card and then flash the rom...all will be well
Click to expand...
Click to collapse
I went no back to this hboot:
PG88IMG-OLD-RADIO-20.28b.30.0805U_38.03.02.11
Everything works well again.
Before I clean my phone again, what will be the benefits with this new hboot?

if people remove the lines in updater-script to flash files to /system/lib partiton, and remove in the boot.img > init.rc the lines to mount lib partition there's actually no need to upgrade your HBOOT. you'll even ruin your camera pictures... Lol i really need to downgrade my hboot but cant really find a good tutorial
if you flash SenseMOD FlashONE and use the F1 kernel located on our website, you wont have any problems with older HBOOTs

djpbx said:
if people remove the lines in updater-script to flash files to /system/lib partiton, and remove in the boot.img > init.rc the lines to mount lib partition there's actually no need to upgrade your HBOOT. you'll even ruin your camera pictures... Lol i really need to downgrade my hboot but cant really find a good tutorial
if you flash SenseMOD FlashONE and use the F1 kernel located on our website, you wont have any problems with older HBOOTs
Click to expand...
Click to collapse
Well i guess there are many who still don't know porting stuff and other details...so that will be a pain for them...
About camera pictures...you need to do a clean install after flashing hboot...so that all libs are now at same place...no issues

datoml said:
I went no back to this hboot:
PG88IMG-OLD-RADIO-20.28b.30.0805U_38.03.02.11
Everything works well again.
Before I clean my phone again, what will be the benefits with this new hboot?
Click to expand...
Click to collapse
Your confusing thats the older radio not hboot...
hboot and radio are different...radio that you flashed will have affect on the network...not camera pictures
hboot affect the system partition schema
Check your hboot version by rebooting into recovery...if the zip has no parts of hboot...it will still be v7

kylon said:
Is this an updated of the eng 2.00.2002?
Or it s older
Click to expand...
Click to collapse
Its same...just modified and reengineered as they say

I have revolutionary hboot. Can I install this ENG 2.00.002 hboot?

Also 2.00.2002 is eng.
I would like to know if this in an updated version
Are there any differences?

[MISC] Flashing ENG HBOOT | Rolling back to S-ON - The Noob Way

Hi all
I noticed that many of us while trying to flash HBOOT's brick our devices as there is no single thread and no single unified noob proof solution for flashing Revolutionary's S-Off 'ed+ Rooted Desire S all the way from HBOOT version 6.98.1xxx to 0.98.2000 (PG8810000).
Hope this helps..
Ok, less talking; more work
This Thread will help you if:
- if you want to change your HBOOT version to 0.98.2000 (PG8810000)
- if you want to S-On your previously S-Off 'ed Desire S as to make use of warranty (as there is no way of making a S-Off device having Revolutionary's HBOOT v.6.98.1002 -to- S-on again without flashing the HBOOT again).
- AFAIK, if you want to flash an RUU (read ROM Update Utility AKA the stock ROM installer) you won't be able to do it you are S-off 'ed using revolutionary method. So for doing that again you need to have the HBOOT version as something like 0.98.xxxx or 6.98.2000 (experts need your comments on this one)
This guide won't be telling you of how to make it S-on again (though theres a link to youtube step-by-step video tutorial of how to do it in the update section below; Do NOT ignore the video's ending ) but just of how you can go ahead with changing your Revolutionary's default flashed HBOOT version 6.98.10xx -to- v.6.98.2000 and then -to- v.0.98.2000 (PG8810000).
For more updated info please refer to "UPDATE" section below:
UPDATE:
Regarding the "Returning to Stock/making your phone S-ON" issue:
ok..I have not tried this but this right here guides you of how to S-ON and return your phone to total* factory like condition by installing an RUU thereby removing just everything..revolutionary, CWM..u name it; just like a real stock phone
But pls note that using an RUU (read ROM Update Utility AKA the stock ROM installer) will erase all your data! as you are flashing a stock RUU
And for this you need to change your HBOOT to 6.98.2000 (PG8810000) (as in the video linked above) OR to 0.98.2000 (PG8810000); so thats one of the other advantages of my guide..
Hope this helps..
Also, a lot of good folks here have been asking/suggesting me over why this method..? and why not the "dd commands method" / adb command(s) method? (all manually )
ok here's my take on this
Click to expand...
Click to collapse
Prerequisites:
- you need an HTC Desire S phone
- HBOOT version 6.98.1xxx (how to check HBOOT version? just read step#4 & step#5 to find out your HBOOT version)
- S-OFF and Root 'ed using Revolutionary (also known as AlphaRevX; its the old name 'duh)
- your data cable and a working PC with HTC Fastboot Drivers installed (get them here)
- make sure you don't have HTC Sync software installed (check it in Add/Remove Programs found in Control panel of your PC); if it is then please remove it before starting with the following process!!!
WARNING:
DO NOT..I REPEAT AGAIN..DO NOT DISCONNECT IN-BETWEEN THE FLASHING PROCESS(Step#6 onwards) OR YOU MAY DAMAGE (READ "BRICK") YOUR PHONE IN A VERY BAD WAY!
Instructions:
1- download and extract the attached zip file in a empty folder (make sure NOT to touch/merge any of its contents)
2- make sure USB debugging is switched "ON" in your phone's: application settings menu >> development settings
3- also make sure that fastboot mode is switched "OFF" in your phone's: Power settings menu and by default your phone is configured to switch to charging mode when the cable is connected (JUST DO NOT CONNECT IT YET)
4- Now, reboot your phone into bootloader mode by first switching off your phone and then press the Power button and the volume down key simultaneously.
5- you should be able to see white screen with things like Revolutionary on top, S-OFF, HBOOT ... 6.98.10xx etc.
6- now go into the fastboot mode and then just connect you phone until the "fastboot" turns into "usb fastboot" OR "fastboot usb" either of these
7- now go inside the extracted folder named "FlashENGHBOOT698"
8- click on bat file named "Click This" and sit back
9- a black screen should popup as soon as you click on the bat [email protected] step#8 and you should see "OKAY" at the end of successful flash but it would be too quick so keep on lookout
10- select reboot on the bootloader's menu
11- reboot back to bootloader's menu to check if HBOOT's version has been changed to 6.98.2000
12- repeat the process from step 8 BUT make sure this time you go inside the other folder named "FlashENGHBOOT098" (notice the ZERO before 98)
13- follow the steps upto step#11 to check if the HBOOT's version has been changed to 0.98.2000 (PG8810000)
Voila!
Note:
This is just a compilation and a slightly edit of the batch file code to flash the second flash Image for the 0.98.2000 HBOOT All credits goes to the following people:
Credits: (Yay!! time for beer)
Would like to thank Maarten for his post and tool here
lgl0 for all his valuable info here
DesireFanatics for his step-by-step tutorial video here
Last but not the least anchemis for sticking and guiding me all the way
And to all those who have helped me here and here.
Disclaimer:
I won't be responsible for any damages done to your phone. Please attempt/flash with caution. though this method has been tested personally by me and is working fine; have also tested rebooting my phone so as to make sure bootloader does not give up on me.

MODS pls sticky this thread as newbie/newcomers really won't get it the first time they look at the [index] @ XDA
And this right here is the solution for Flashing their HBOOTs almost painlessly
Regards,
sky770
- Reserved for future use -

great guide, just have one question, currently I am using reengineered 2.00.002 hboot - 7.00.1002, my phone was s offed by revolutionary, will it work as well?

esideboi said:
great guide, just have one question, currently I am using reengineered 2.00.002 hboot - 7.00.1002, my phone was s offed by revolutionary, will it work as well?
Click to expand...
Click to collapse
:|..*gulp*
ok..as am a newbie so I would be needing experts in here
btw..have you gone through the Index/threads? coz thats what i did

esideboi said:
great guide, just have one question, currently I am using reengineered 2.00.002 hboot - 7.00.1002, my phone was s offed by revolutionary, will it work as well?
Click to expand...
Click to collapse
You have the latest hboot. If you don't want to s-on and unroot your phone again there is no need for you to downgrade the hboot (afaik )
Edit: accidentally pressed thanks.. never mind

sky770 said:
Hi all
I noticed that many of us while trying to flash HBOOT's brick our devices as there is no single thread for flashing Revolutionary's S-Off 'ed+ Rooted Desire S to 0.98.2000 (PG8810000).
Hope this helps..
Ok, less talking; more work
This Thread will help you if:
- if you want to change your HBOOT version to 0.98.2000 (PG8810000)
- if you want to S-On your previously S-Off 'ed Desire S as to make use of warranty (as there is no way of making a S-Off device having Revolutionary's HBOOT v.6.98.1002 -to- S-on again without flashing the HBOOT again).
- AFAIK, if you want to flash an RUU (umm noob translation for this would be original stock ROM?) you won't be able to do it you are S-off 'ed using revolutionary method. So for doing that again you need to have the HBOOT version as something like 0.98.xxxx or 6.98.2000 (experts need your comments on this one)
This guide won't be telling you of how to make it S-on again but just of how you can go ahead with changing your Revolutionary's default flashed HBOOT version 6.98.10xx -to- v.6.98.2000 and then -to- v.0.98.2000 (PG8810000)
Prerequisites:
- you need an HTC Desire S phone
- HBOOT version 6.98.1xxx (how to check HBOOT version? just read step#4 & step#5 to find out your HBOOT version)
- S-OFF and Root 'ed using Revolutionary (also known as AlphaRevX; its the old name 'duh)
- your data cable and a working PC with HTC Fastboot Drivers installed (get them here)
- make sure you don't have HTC Sync software installed (check it in Add/Remove Programs found in Control panel of your PC); if it is then please remove it before starting with the following process!!!
WARNING:
DO NOT..I REPEAT AGAIN..DO NOT DISCONNECT IN-BETWEEN THE FLASHING PROCESS(Step#6 onwards) OR YOU MAY DAMAGE (READ "BRICK") YOUR PHONE IN A VERY BAD WAY!
Instructions:
1- download and extract the attached zip file in a empty folder (make sure NOT to touch/merge any of its contents)
2- make sure USB debugging is switched "ON" in your phone's: application settings menu >> development settings
3- also make sure that fastboot mode is switched "OFF" in your phone's: Power settings menu and by default your phone is configured to switch to charging mode when the cable is connected (JUST DO NOT CONNECT IT YET)
4- Now, reboot your phone into bootloader mode by first switching off your phone and then press the Power button and the volume down key simultaneously.
5- you should be able to see white screen with things like Revolutionary on top, S-OFF, HBOOT ... 6.98.10xx etc.
6- now go into the fastboot mode and then just connect you phone until the "fastboot" turns into "usb fastboot" OR "fastboot usb" either of these
7- now go inside the extracted folder named "FlashENGHBOOT698"
8- click on bat file named "Click This" and sit back
9- a black screen should popup as soon as you click on the bat [email protected] step#8 and you should see "OKAY" at the end of successful flash but it would be too quick so keep on lookout
10- select reboot on the bootloader's menu
11- reboot back to bootloader's menu to check if HBOOT's version has been changed to 6.98.2000
12- repeat the process from step 8 BUT make sure this time you go inside the other folder named "FlashENGHBOOT098" (notice the ZERO before 98)
13- follow the steps upto step#11 to check if the HBOOT's version has been changed to 0.98.2000 (PG8810000)
Voila!
Note:
This is just a compilation and a slightly edit of the batch file code to flash the second flash Image for the 0.98.2000 HBOOT All credits goes to the following people:
Credits: (Yay!! time for beer)
Would like to thank Maarten for his post and tool here
lgl0 for all his valuable info here
Last but not the least anchemis for sticking and guiding me all the way
And to all those who have helped me here and here.
Disclaimer:
I won't be responsible for any damages done to your phone. Please attempt/flash with caution. though this method has been tested personally by me and is working fine; have also tested rebooting my phone so as to make sure bootloader does not give up on me.
Click to expand...
Click to collapse
you have not mentiond the dd commands tut. this is used because of the re engineerd hboot 7.00.1002 upgrade people are doing, u cannot use any other method to get another hboot to your device after using 7.00.1002 hboot. as no fastboot and using the PG88IMG method just gets bypassed. so the only way is the dd commands. please add this to your guide thanks

If i pass your guide, will my phone be s-on or s-off?
Is it possible to apply this hboot version after? Or can i apply this hboot version right now?
Currently im on hboot-6.98.1002.
Hope someone will guide me real quick. Thanks!

@muselmann88 : 1. The bootloader is Eng S-off!
2. You're now with the Revolutionary Hboot and there is no reason to change. As long as you're using the dd commands to directly write the bootloader partition every bootloader can be uploaded. I haven't had any problems with this method.

marioemp2k7 said:
@muselmann88 : 1. The bootloader is Eng S-off!
2. You're now with the Revolutionary Hboot and there is no reason to change. As long as you're using the dd commands to directly write the bootloader partition every bootloader can be uploaded. I haven't had any problems with this method.
Click to expand...
Click to collapse
I read that i'll have boot problems with sense 4 roms, isn't that correct?
Could you please list the dd commands that i'll succeed in writing the bootloader to the partition.

How about other eng hboot?
Sent from my HTC Desire S using XDA

muselmann88 said:
I read that i'll have boot problems with sense 4 roms, isn't that correct?
Could you please list the dd commands that i'll succeed in writing the bootloader to the partition.
Click to expand...
Click to collapse
I have PM you mate i have sent u everything u need to get yourself on the new eng hboot with that new eng hboot u can use ANY Rom without any problems

The hboot version that should be overwritten by "dd" command is 6.98.1002.
All the others are perfectly rewritten by a RUU or PG88IMG with a higher version.
Only Revolutionary (not AlpharevX) hboot has write protection. There is not only version check in that process

Thanks to the OP!
Just got a Desire S and so far done this little lot:
I've downgraded the ROM to 1.28 to get HBOOT 0.98
S-OFF'ed using Revolutionary.
Installed 4EXT Recovery 1.0.0.5 Touch RC3
Flashed VanillaICE ROM
and just followed this guide to get off the Revolutionary HBOOT and to the ENG HBOOT 0.98.2000.
And it worked flawlessly!
Thanks again!
EDIT: and somewhere in that lot I have also updated the radio to the latest one from the Radio thread!

htc-phones said:
you have not mentiond the dd commands tut. this is used because of the re engineerd hboot 7.00.1002 upgrade people are doing, u cannot use any other method to get another hboot to your device after using 7.00.1002 hboot. as no fastboot and using the PG88IMG method just gets bypassed. so the only way is the dd commands. please add this to your guide thanks
Click to expand...
Click to collapse
Hi,
The fastboot method gets bypassed if we try to flash it by directly picking up the *.zip file from SD Card's root (that good 'ol PG88IMG.zip method).
Using the above method (my method at post#1) we are just literally pushing it through fastboot>>adb>>phone to get it flashed.. no questions asked from phone's side
srry abt the newbie/layman terms answer but this is how it actually works
Also regarding, the "dd commands" are never meant to be used for "noobs" as they are quite dangerous...more..more dangerous than to use fastboot instead of directly using adb commands.
Just because dd commands method exist doesn't mean we should go to that extent to brick our phone (a noob can easily do that while sipping beer and typing some command as bik instead of blk)
And hence I would not like newbie(s) coming in here, bricking their phones and stalking me
UPDATE:
Excerpt taken from here
There are actually two levels of S-OFF. The Bootloader (HBoot) and the Radio. Getting S-Off on the HBoot gives us everything we need, but doesn't actually turn off the @secuflag which is set in the radio. What it is possible to do is to flash a HBoot that believes the Radio is set to S-OFF, as the HBoot is responsible for setting that flag. Once the HBoot on the phone is S-OFF, we can write to all the partitions and basically do whatever we want, but it is possible to go one step further. Flashing a radio that is S-OFF and actually setting the @secuflag off gives 100% total access to every part of the phone and it's software, as it becomes network unlocked allowing to you to use any SIM and also allows you to flash a ROM from any carrier (known as Super CID). It also makes it nigh on impossible to permanently loose root no matter what you flash. Once you have radio S-OFF, it makes it much easier to flash new HBoots and ROMs even if you flash something that is locked down tight.
Setting the Radio to S-Off is not necessary, and gaining S-OFF on the HBoot is more than most people will ever need. Radio S-Off is just the last step of the puzzle, but it is worth noting the only points you can permanently brick your phone is flashing a radio or a HBoot, if either of these go wrong you will end up with a shiny expensive paper weight so there is risk involved.
Click to expand...
Click to collapse
So pls pls suggest newbie(s) to flash with caution :|

muselmann88 said:
If i pass your guide, will my phone be s-on or s-off?
Is it possible to apply this hboot version after? Or can i apply this hboot version right now?
Currently im on hboot-6.98.1002.
Hope someone will guide me real quick. Thanks!
Click to expand...
Click to collapse
As it looks to me, if you're running hboot-6.98.1002 already then you must have used revolutionary's tool to S-off your phone.
Therefore you are eligible to use the above guide to re-flash your hboot.
Infact you're having the same hboot version as I had after using revolutionary.
changing your hboot version to 0.98.2000 (PGI880000) will make sure that you can flash any RUU (official stock ROM) so that you could be s-off again
Though I am still getting working on it to have a simple 1-click solution for this too for ya noobs
Also, make sure you're rooted (though I would like some expert to comment on this; but AFAIK root is needed to flash the *.img file over fastboot; just search around forum as to be sure.)
Do it now! and you won't regret..
Regards,
sky770

marioemp2k7 said:
@muselmann88 : 1. The bootloader is Eng S-off!
2. You're now with the Revolutionary Hboot and there is no reason to change. As long as you're using the dd commands to directly write the bootloader partition every bootloader can be uploaded. I haven't had any problems with this method.
Click to expand...
Click to collapse
I would not really recommend using "dd commands" please see my reply over here
Regards,
sky770

muselmann88 said:
I read that i'll have boot problems with sense 4 roms, isn't that correct?
Could you please list the dd commands that i'll succeed in writing the bootloader to the partition.
Click to expand...
Click to collapse
Sense 4 requires you to have umm... HBOOT version 2.xxx and above? (experts?) anyways.. that cannot be categorized as "problem" its just another "prerequisite" for sense 4 based ROMs though am not sure if its an "official prerequisite" or a non official non
Also, please read my post abt dd commands here.
Regards,
sky770

Dreamtheater2003 said:
How about other eng hboot?
Sent from my HTC Desire S using XDA
Click to expand...
Click to collapse
Can take some time here to try some custom(s) ROMs first
Anyways, now that am here on XDA lets get started..
Regards,
sky770

htc-phones said:
I have PM you mate i have sent u everything u need to get yourself on the new eng hboot with that new eng hboot u can use ANY Rom without any problems
Click to expand...
Click to collapse
any ROM?
you sure about RUU (stocks) ??
if yes then plz forward tht PM to me too pls
Regards,
sky770

amidabuddha said:
The hboot version that should be overwritten by "dd" command is 6.98.1002.
All the others are perfectly rewritten by a RUU or PG88IMG with a higher version.
Only Revolutionary (not AlpharevX) hboot has write protection. There is not only version check in that process
Click to expand...
Click to collapse
aha! Right on point
And thats one more reason I won't really..really recommend using dd commands to a noob/newcomers just for flashing from 6.98.10xx -over to-0.98.2000 (PGI880000).
Regards,
sky770