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.

MT4G - root or upgrade then htcdev unlock

i downgraded to 2.2.1 from 2.3.4 because htc sense was force closing.
i have tried rooting but to no avail. i do have a bad emic chip.
i now am either going to update back to 2.3.4 and htc dev unlock and get rid of bloatware or i simply try to keep rooting and flash and hope i dont brick my phone.

NEVER EVER EVER unlock with HTC DEV! And try using ./gfree for FroYo, supposing you haven't updated to 2.3.4.

why not use htcdev
i can try gfree but the bad emmc chip apprently bricks your phone or is timebomb

For the EMMc chip: it is not. My brother had a bad chip. He flashed like there was no tomorrow. The only reason why he doesn't have the phone right now is because he traded it for an iPhone...-__-
HTCDev: It makes it harder because then when you flash a ROM, you must manually flash the boot.img to flash the whole ROM. I don't know the details, but that is just what I heard.

invasion2 said:
For the EMMc chip: it is not. My brother had a bad chip. He flashed like there was no tomorrow. The only reason why he doesn't have the phone right now is because he traded it for an iPhone...-__-
HTCDev: It makes it harder because then when you flash a ROM, you must manually flash the boot.img to flash the whole ROM. I don't know the details, but that is just what I heard.
Click to expand...
Click to collapse
The adb part is true, the reasoning though is HTC dev unlock only unlocks part of the bootloader, I'm not sure about the specifics but I know it unlocks the recovery partition which allows you to flash cwm
Sent from my HTC Glacier using xda premium

Nicgraner said:
The adb part is true, the reasoning though is HTC dev unlock only unlocks part of the bootloader, I'm not sure about the specifics but I know it unlocks the recovery partition which allows you to flash cwm
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
HTCDev unlocks the boot partition (and possibly recovery partition too) for fastboot flashing ONLY. It doesn't unlock them for anything else. So even though it lets you install recovery, you can't flash kernels (boot.img) from it - you HAVE to do it from fastboot.
For non-frequent-flashers, that are familiar enough with their PC to set up fastboot environment, this solution might be good enough.
I don't like it, because I prefer to have the ability to do things fully from the phone.

Jack_R1 said:
HTCDev unlocks the boot partition (and possibly recovery partition too) for fastboot flashing ONLY. It doesn't unlock them for anything else. So even though it lets you install recovery, you can't flash kernels (boot.img) from it - you HAVE to do it from fastboot.
For non-frequent-flashers, that are familiar enough with their PC to set up fastboot environment, this solution might be good enough.
I don't like it, because I prefer to have the ability to do things fully from the phone.
Click to expand...
Click to collapse
Jack R1 is absolutely right...I made the mistake of doing it the HTC way, and I have to flash the boot.img with fastboot. But to add to that, I also have been trying to reverse what the HTC method has done, and alot of the methods are not working properly. So plz listen to them and DO NOT unlock via HTC. Its way to easy doing it xda way, something I learned after the fact...
Sent from my Black Ice'd Glacier using Tapatalk

S-off with HTC Dev tool?

Just got my Sensation back from repair, so now it's already on 4.03 ICS. I remember from before there was some discussion of the new HBOOT version not being about to S-off. However, HTC offers the unlock tool. Just wondering if it's a bad thing to do using their unlock tool or does it matter?

Look at the S-OFF guides for 1.2x.xxxx HBOOTs.
The wire trick is a pain but does work.
EDIT: meant to say that I believe you don't need the HTC unlock thing now. I used it but......

newr said:
Just got my Sensation back from repair, so now it's already on 4.03 ICS. I remember from before there was some discussion of the new HBOOT version not being about to S-off. However, HTC offers the unlock tool. Just wondering if it's a bad thing to do using their unlock tool or does it matter?
Click to expand...
Click to collapse
S-OFF and htcdev tool are two different things
htcdev tool only disables write protection on recovery partition - allowing you to flash custom recovery.
S-OFF unlocks all partitions including boot partition which means you can flash ROMs without flashing boot.img manually or needing to have 4EXT SmartSync on.
In short the htcdev tool is misnamed because it does not unlock the bootloader - only unlocks recovery

Jonny said:
In short the htcdev tool is misnamed because it does not unlock the bootloader - only unlocks recovery
Click to expand...
Click to collapse
only recovery ? isn't it recovery,system,boot and data partitions ?

ganeshp said:
only recovery ? isn't it recovery,system,boot and data partitions ?
Click to expand...
Click to collapse
Boot partition? no because you have to manually flash a boot.img with htcdev
system partition write protection is controlled by the OS and disabled by rooting - rooting allows the end user to give certain programs write permission. As to whether the recovery can access system and data partitions without unlocking the bootloader, I believe it can because stock recovery can overwrite system and data using OTA files controlled by a similar updater-script that we use in custom ROMs

Jonny said:
Boot partition? no because you have to manually flash a boot.img with htcdev
system partition write protection is controlled by the OS and disabled by rooting - rooting allows the end user to give certain programs write permission. As to whether the recovery can access system and data partitions without unlocking the bootloader, I believe it can because stock recovery can overwrite system and data using OTA files controlled by a similar updater-script that we use in custom ROMs
Click to expand...
Click to collapse
If boot partition is locked then you can't even flash boot.img via bootloader using fastboot flash command.. I think it has some issue getting flashed from recovery.. That's all
First to get root itself you require write permission on system partition.. That means at the end you require system partition unlocked.
The stock recovery can only flash signed stuff.. Thus a signature check is made.. (at the end unlocking of partitions is nothing but removing sign checking of whatever we flash)
Iirc the FAQ of htc-dev mentioned about what partitions are unlocked.... And those are what I mentioned
Sent from my HTC Sensation 4G using xda premium

[Q] What are the advantages of S-off?

I've been reading a little on this S-off thing and was wondering what its purpose actually is and what the advantages are from doing it? I know I was able to flash my HTC Vivid without it so what is it really used for? Thank you in advance.

Answer...
phrotac said:
I've been reading a little on this S-off thing and was wondering what its purpose actually is and what the advantages are from doing it? I know I was able to flash my HTC Vivid without it so what is it really used for? Thank you in advance.
Click to expand...
Click to collapse
See: What Is S-OFF & How To Gain It On HTC Android Phones With unrevoked forever
In a nutshell, S-OFF means that the NAND portion of the device is unlocked and can be written to. The default setting for HTC’s devices is S-ON, which means that neither can you access certain areas of the system nor can you guarantee a permanent root. Furthermore, signature check for firmware images is also ensured by the S-ON flag.
Click to expand...
Click to collapse
---------- Post added at 11:01 PM ---------- Previous post was at 10:58 PM ----------
Basically, if you are going to be installing custom ROMs, you probably want to set s-off so you can flash unsigned ROMs.

Very interesting. Thank you for responding That gives me something to think about.

In short. S-OFF allows you to change pretty much everything. Your CID, firmware (radio, hboot etc) and most important thing probably, allows you to flash older RUUs
Sent from my HTC Sensation XE with Beats Audio using Tapatalk 2

If you are going to be changing roms, themes, etc, then leave it off. If not then turn in back on.

kdub83 said:
If you are going to be changing roms, themes, etc, then leave it off. If not then turn in back on.
Click to expand...
Click to collapse
I found the perfect ROM from WCX but I never had to use a wire on it though. Is HTCdev the reason why? I'm just trying to figure out this whole s-off thing because I saw a video where someone used a piece of insulated wire and was wondering why. I'm sorry if I wasn't clear enough with my questions earlier... My bad.

S-OFF
Hi - I've had HTC devices since the Eris way back in 2010 - currently running the Rezound. Hopefully I can shed some more light.
When I first got the Rezound I was coming over from an S-OFF Eris... if you wanted to flash something custom, you'd go to htcdev.com and use their "unlock bootloader" tool. Once you ran that and followed a few other steps, you are reverted to stock and your bootloader now has a little warning "unlocked" in the text at the top. This was in January 2012, and ROMs back then came with 2 things - the ROM and a Kernel. You had to flash the kernel separatley (and via the bootloader as opposed to a custom recovery), as S-ON (even unlocked) still won't let you write to certain places (in the case of the kernel, its the boot partition).
We got S-OFF several months later (the thing using the wire trick). In S-OFF - custom recovery can write to all areas of the device - no more need for any separate files, you just flash a ROM in custom recovery and everything is set up the way it should be. Added bonus - no need to unlock the bootloader from htcdev... so no "unlocked" warning message.
Here was my S-OFF process:
1. Run the official RUU exe to get your device back to stock with a Locked bootloader (backup any files on the SDCard first!).
2. Perform the wire trick
3. Flash a custom recovery and proceed with flashing ROMS
Let me know if I can clarify anything...

Basically allows you to flash RADIOS that have not been signed by HTC
Sent from my Galaxy Nexus using xda premium

Ryan Kasper said:
Hi - I've had HTC devices since the Eris way back in 2010 - currently running the Rezound. Hopefully I can shed some more light.
When I first got the Rezound I was coming over from an S-OFF Eris... if you wanted to flash something custom, you'd go to htcdev.com and use their "unlock bootloader" tool. Once you ran that and followed a few other steps, you are reverted to stock and your bootloader now has a little warning "unlocked" in the text at the top. This was in January 2012, and ROMs back then came with 2 things - the ROM and a Kernel. You had to flash the kernel separatley (and via the bootloader as opposed to a custom recovery), as S-ON (even unlocked) still won't let you write to certain places (in the case of the kernel, its the boot partition).
We got S-OFF several months later (the thing using the wire trick). In S-OFF - custom recovery can write to all areas of the device - no more need for any separate files, you just flash a ROM in custom recovery and everything is set up the way it should be. Added bonus - no need to unlock the bootloader from htcdev... so no "unlocked" warning message.
Click to expand...
Click to collapse
Thank you very much. That DOES explain it very well.
Ryan Kasper said:
Here was my S-OFF process:
1. Run the official RUU exe to get your device back to stock with a Locked bootloader (backup any files on the SDCard first!).
2. Perform the wire trick
3. Flash a custom recovery and proceed with flashing ROMS
Let me know if I can clarify anything...
Click to expand...
Click to collapse
Are you saying I can make my bootloader say LOCKED again? I thought I could only make it say UNLOCKED or RELOCKED now that I've unlocked it. That is so awesome. And then the s-off will give me permanent root?

Are you saying I can make my bootloader say LOCKED again? I thought I could only make it say UNLOCKED or RELOCKED now that I've unlocked it. That is so awesome. And then the s-off will give me permanent root?
Click to expand...
Click to collapse
Yup! Once you are S-OFF you will be back on the stock bootloader that reads "locked". There are a variety of HBOOTS (AKA Bootloaders) you can flash (well - there are for my device currently...). For the Rezound right now I have a variety of them with different verbages in the title (example - "locked S-ON", "Rezound") - or you can simply leave it at the stock HBOOT though you will not be able to flash, say a custom recovery, using fastboot in the bootloader via a terminal emulator (you have to use the PH98IMG.zip method in the bootloader)... Also the devs that made the wire trick available offer their own hboot "juopunutbear" - this one allows fastboot recovery flashing... - here for the vivid http://unlimited.io/jb_holiday.htm
Also - be VERY careful when updating the bootloader - it is a very common way to brick the device... I always check the MD5Sum before copying to SD and flashing.
And regarding permanent root - absolutely. Flash SuperSU from custom recovery (the zip version available here - http://forum.xda-developers.com/showthread.php?t=1538053

Ryan Kasper said:
Yup! Once you are S-OFF you will be back on the stock bootloader that reads "locked". There are a variety of HBOOTS (AKA Bootloaders) you can flash (well - there are for my device currently...). For the Rezound right now I have a variety of them with different verbages in the title (example - "locked S-ON", "Rezound") - or you can simply leave it at the stock HBOOT though you will not be able to flash, say a custom recovery, using fastboot in the bootloader via a terminal emulator (you have to use the PH98IMG.zip method in the bootloader)... Also the devs that made the wire trick available offer their own hboot "juopunutbear" - this one allows fastboot recovery flashing... - here for the vivid http://unlimited.io/jb_holiday.htm
Also - be VERY careful when updating the bootloader - it is a very common way to brick the device... I always check the MD5Sum before copying to SD and flashing.
And regarding permanent root - absolutely. Flash SuperSU from custom recovery (the zip version available here - http://forum.xda-developers.com/showthread.php?t=1538053
Click to expand...
Click to collapse
This information is golden. Thank you very much

tinky1 said:
In short. S-OFF allows you to change pretty much everything. Your CID, firmware (radio, hboot etc) and most important thing probably, allows you to flash older RUUs
Sent from my HTC Sensation XE with Beats Audio using Tapatalk 2
Click to expand...
Click to collapse
Awesome! I have a couple more questions still *scratches head in confusion*...
Once I S-Off, can I reverse it if needed?
and
<Ignore this part... I found the information LOL>
What is an RUU? I have googled it and I can't find anything about it (maybe I'm just too tired or something)

phrotac said:
Awesome! I have a couple more questions still *scratches head in confusion*...
Once I S-Off, can I reverse it if needed?
Click to expand...
Click to collapse
Yup - here is how I'd do it if I had to for my device - http://forum.xda-developers.com/showthread.php?t=1612937 - careful if you do and read any warnings (brick opportunities again)

Hi,
It is possible, if I install custom rom, some function will not work without S-OFF?
The phone was routed and unlokced but it was S-ON.

[Q] Need info about bootloader mode and other stuff

Hi im new to htc and bootloader and all this stuff.
when i had galaxy s2 i knew everything about it. (download, recovery)
so here is what i need to know:
1.can i create a NAND backup of a stock rom and restore to it if i have s-on?
2.what doe's ***tampered*** in bootloader mode means?
3.when i flash a custom rom and i extract the boot.img do i have to remove it from the zip file itself?
Thanks for any HELP!!!!

LSGio said:
Hi im new to htc and bootloader and all this stuff.
when i had galaxy s2 i knew everything about it. (download, recovery)
so here is what i need to know:
1.can i create a NAND backup of a stock rom and restore to it if i have s-on?
2.what doe's ***tampered*** in bootloader mode means?
3.when i flash a custom rom and i extract the boot.img do i have to remove it from the zip file itself?
Thanks for any HELP!!!!
Click to expand...
Click to collapse
1. No, if you have S-ON you can't create a NAND backup as you don't have a custom recovery.
2. ***TAMPERED*** means that an app or apps have gone into your /system/ partition, thereby triggering the tampered flag. You can remove this message by running a HTC RUU.
3. No, you first flash the zip file with the boot.img inside, then flash the boot.img in the bootloader. fastboot flash boot boot.img

1.i do have a custom recovery which i flashed with all in one kit. (i was able to flash it because i unlocked the bootloader but i dont know what s-off means and also supercid)
so can i do a nand backup of a stock rom and restore to it?
and i also wanted to know how to s-off and what are the differences between s-off and supercid?

LSGio said:
1.i do have a custom recovery which i flashed with all in one kit. (i was able to flash it because i unlocked the bootloader but i dont know what s-off means and also supercid)
so can i do a nand backup of a stock rom and restore to it?
and i also wanted to know how to s-off and what are the differences between s-off and supercid?
Click to expand...
Click to collapse
Then yes you can make a backup and restore later. Just always full wipe, cache and dalvik cache wipe.
As far as flashing kernels/boot.img, if you are < hboot 1.13 then just flash via recovery. If your hboot is > or = to hboot 1.13tjen flash via fastboot or flash img GUI (available in the play store and in various threads).
And as of right now there is no s-off for the one s.
Sent from a baked One S
If I've helped hit the thanks button

LSGio said:
1.i do have a custom recovery which i flashed with all in one kit. (i was able to flash it because i unlocked the bootloader but i dont know what s-off means and also supercid)
so can i do a nand backup of a stock rom and restore to it?
and i also wanted to know how to s-off and what are the differences between s-off and supercid?
Click to expand...
Click to collapse
S-Off means you have full access to all firmware partitions of the phone (I think, correct me if Im wrong). You can unlock the boot loader to gain access to the relevant partitions to flash a custom ROM even with S-ON.
The phone CID just represents the region it is from. For example HTC_TMOUS is for the One S used on the US T-Mobile network. When the phone checks for updates, it only downloads the one's relevant to the CID. SuperCID is 111111111 and represents the "developer" region you can download or run any update on a One S with super CID.

KACE321 said:
S-Off means you have full access to all firmware partitions of the phone (I think, correct me if Im wrong). You can unlock the boot loader to gain access to the relevant partitions to flash a custom ROM even with S-ON.
The phone CID just represents the region it is from. For example HTC_TMOUS is for the One S used on the US T-Mobile network. When the phone checks for updates, it only downloads the one's relevant to the CID. SuperCID is 111111111 and represents the "developer" region you can download or run any update on a One S with super CID.
Click to expand...
Click to collapse
Is that means that if i have supercid i can run any ruu?
if this is the meaning so how do i supercid my one s?

LSGio said:
Is that means that if i have supercid i can run any ruu?
if this is the meaning so how do i supercid my one s?
Click to expand...
Click to collapse
fastboot oem writecid 11111111

usaff22 said:
fastboot oem writecid 11111111
i have 2 questions:
1.how many 1's do i have to write
2.can i get back to my cid and how?
Click to expand...
Click to collapse

Yes, you can make nand backups and restore them if you have a custom recovery. You don't need to have s-off for that but you do need to have your bootloader unlocked. Depending on your hboot version, restoring a nand backup will not restore your boot image. (1.09 and below will, 1.13 and up won't.) We do now have the means to downgrade hboot tho.
You get the *tampered* line if your recovery is unsigned. When you use a custom rom, you will most likely also get a red warning text over your boot splash. It's normal.
You have to extract the boot image from the rom zip and flash it in fastboot before you boot the new rom. This may even be before you flash the new rom. You can leave the rom zip unchanged and flash it in recovery.
-Jobo

if ill do a nand it will back up the boot img but wont restore it because of my hboot version?
Oh and one more thing when i rooted my htc with the supersu zip than after 2 days it asked for mksh premissions and than when i rebootedy phone it was stuck in recovery and then i fixed it with a wipe but how can i prevent this from hapenning and why does it hapenned?
Sent from my HTC One S using xda app-developers app

LSGio said:
if ill do a nand it will back up the boot img but wont restore it because of my hboot version?
Click to expand...
Click to collapse
Correct. On old hboots, pretty much everything except sbl and hboot is writable in recovery or even while fully booted. On newer hboots, most is read-only. Boot image can be flashed in fastboot but radio and other stuff can not.
LSGio said:
Oh and one more thing when i rooted my htc with the supersu zip than after 2 days it asked for mksh premissions and than when i rebootedy phone it was stuck in recovery and then i fixed it with a wipe but how can i prevent this from hapenning and why does it hapenned?
Click to expand...
Click to collapse
The mksh root request is a known thing. You can search the forums for it to read some opinions. As far as I know not yet properly explained why it happens but harmless. It is not related to getting stuck in recovery, altho I have no idea what caused that for you.

touch of jobo said:
Correct. On old hboots, pretty much everything except sbl and hboot is writable in recovery or even while fully booted. On newer hboots, most is read-only. Boot image can be flashed in fastboot but radio and other stuff can not.
The mksh root request is a known thing. You can search the forums for it to read some opinions. As far as I know not yet properly explained why it happens but harmless. It is not related to getting stuck in recovery, altho I have no idea what caused that for you.
Click to expand...
Click to collapse
can you please tell me how can i download an ruu that matches my stock rom. cause when i get to the filefactory server it tells me that i need to buy premium because the file is larger than 500MB.
and the link to the ruu downloads is from this thread:
http://forum.xda-developers.com/showthread.php?t=1543588
if youll go to the first page and click the (ville S4) link you will see a list of ruu's but i can't download them because the size of them is larger han 500mb and i need premium.