Related
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.
Hey guys,
im a bit of a moron and decided to update my desire s to 2.3.5 from 2.3.3 using the file RUU_Saga_S_HTC_Europe_2.10.401.5_Radio_20.4801.30.0822U_3822.10.08.04_M_release_219480_signed
i have a deisre s from three (UK) which i s-off'ed myself.
the updated completed fine, but crashed when it reboted, now my desire freezes at the htc logo screen, if i press the volume down button and try to go to recovery i get a red triangle and exclamtion mark.
any ideas please?
thank you
chairmanmeow1 said:
Hey guys,
im a bit of a moron and decided to update my desire s to 2.3.5 from 2.3.3 using the file RUU_Saga_S_HTC_Europe_2.10.401.5_Radio_20.4801.30.0822U_3822.10.08.04_M_release_219480_signed
i have a deisre s from three (UK) which i s-off'ed myself.
the updated completed fine, but crashed when it reboted, now my desire freezes at the htc logo screen, if i press the volume down button and try to go to recovery i get a red triangle and exclamtion mark.
any ideas please?
thank you
Click to expand...
Click to collapse
Which method did you use to gain s-off, revolutionary? What is your current hboot?
I'm suggesting it's still 6.XXXX, downgrade your hboot and run the ruu again.
Recovery isn't present cause a ruu puts you back to stock, there is only a fault at the revolutionary hboot, it can't be overwritten with standard methods, look at the index thread, there is a downgrade tutorial.
Swyped from my Desire S
Tectas said:
Recovery isn't present cause a ruu puts you back to stock
Click to expand...
Click to collapse
could he try and install fastboot drivers and flash a new hboot/rom/custom recovery or would what the RUU has done render my solution useless..
correct me if i'm wrong...
Zachary
anonymous_1997 said:
could he try and flash a custom recovery through fastboot and flash a new hboot/rom or would what the RUU has done render my solution useless
Click to expand...
Click to collapse
He can do that if his hboot hasn't changed, but as i understand it, he wants the ruu.
But another option would be to run the ruu without attached device. Don't close the first window. Search for the rom.zip. Copy it into any other folder. Open it and remove everything except the system.img & boot.img. Rename the rom.zip to PG88IMG.zip and flash it from bootloader or flash the system.img and boot.img itself with fastboot. But I don't know if this is what he wants, cause only the system is changed, but not recovery or bootloader.
Hi, i did use revolutionary to s-off, wanted to get rid off the ****ty three branded rom, my
hboot is 6.98.1002
radio 3822.10.08.04_M
can i downgrade the hboot without being able to boot into the phone?
i just want to get it working again, dont mind not having 2.3.5
The easiest way would be to flash a custom recovery image with fastboot (such as clockworkmod), after that download another hboot from here or here.
Extract the hboot.img.
Reboot to recovery. Open a terminal and type
Code:
adb devices
adb push hboot.img /sdcard/hboot.img (be sure you're in the folder where hboot.img is on your harddrive)
adb shell
dd if=/dev/block/mmcblk0p18 of=/sdcard/backup.img (backup your alpharev hboot )
dd if=/sdcard/hboot.img of=/dev/block/mmcblk0p18 (flash new hboot )
exit
Reboot to bootloader, there should be 0.98.2000 or 2.00.2002 instead of 6.98.1002, after that you can run every ruu you want, but don't forget, after running a ruu your bootloader is back to s-on.
---------- Post added at 02:25 PM ---------- Previous post was at 02:20 PM ----------
Oh btw, why you want to use the ruu and not a custom 2.3.5 rom with sense 3 or 3.5, there are as many out there.
Tectas said:
He can do that if his hboot hasn't changed, but as i understand it, he wants the ruu.
But another option would be to run the ruu without attached device. Don't close the first window. Search for the rom.zip. Copy it into any other folder. Open it and remove everything except the system.img & boot.img. Rename the rom.zip to PG88IMG.zip and flash it from bootloader or flash the system.img and boot.img itself with fastboot. But I don't know if this is what he wants, cause only the system is changed, but not recovery or bootloader.
Click to expand...
Click to collapse
ok gotcha..thanks for clearing that up
---------- Post added at 12:34 PM ---------- Previous post was at 12:28 PM ----------
Tectas said:
Reboot to recovery. Open a terminal and type
Code:
adb devices
adb push hboot.img /sdcard/hboot.img (be sure you're in the folder where hboot.img is on your harddrive)
adb shell
dd if=/dev/block/mmcblk0p18 of=/sdcard/backup.img (backup your alpharev hboot )
dd if=/sdcard/hboot.img of=/dev/block/mmcblk0p18 (flash new hboot )
exit
Click to expand...
Click to collapse
didnt know you could backup your hboot good info probably should do that next time i flash a hboot... last one i did was a eng s-off from revolutionary's pvt ship s-off
Since you're revolutionary s-off, you could flash 4ext or clockworkmod recovery, and then flash a custom rom. The official Ruu tries to install latest hboot with new partitioning table (/system and /system/lib are now separated). As revolutionary hboot can't be replaced by ruu, it can't work. Just either flash a custom rom, or flash eng hboot over revolutionary, search for "engHBOOToverARX" in desire s forums. I used that method to get rid of revolutionary hboot.
Sent from my HTC Desire S with Virtuous Affinity
download ANDROID FLASHER and 4EXT recovery.zip from the 4EXT thread. Open the ZIP and extract the recovery.img, and flash using ANDROID FLASHER. Then, open recovery and format cache. DONE
thanks for the help guys
i downloaded the fastboot drivers and the android flasher program also cynogen 7.1 stable build
i run the program with my phone in fstboot and then tick recovery or bootloader?
Recovery, and select the recovery.img from the 4ext recovery.zip. You can find it in the thread.
Sent from my iPod touch using Tapatalk
thanks
all is well again, i have cynogenmod 7.1 running
Hey ,
ok.. everything went fine Now my Desire S is S-off'ed and is rooted
(a big thanx to all who helped me here )
Now, I have a few questions before flashing the ENG HBOOT & installing the touch recovery (4EXT):
- Which zip file version of ENG HBOOT should I flash?
Got 2 zip files here: one of them is named "PG88IMG(ENG 0.98.2000)" and is having "engHBOOToverARX.img" named IMG file.
Other one is named "PG88IMG" and is having "hboot_0.98.0000_361a7ba6_0310.img" named IMG file.
I checked their size and MD5; size is same but their MD5 hashes are different.
Please suggest, which one to go for? Or should I flash a newer version of ENG HBOOT? the 2.00.xxx ? Which ones better? :|
- Flashing this ENG HBOOT is it equivalent to flashing a new radio?
-Will I need to format any partitions, cache,...anything? I am not going to install any custom ROM for now, so I need my applications and their data..everything intact (just being noob here )
--
UPDATE:
I have successfully installed 4EXT recovery but when I check my filesystem info it says that except the SD Card all of my partitions are already ext4! is that possible? i din't converted them. by default all phone partitions as EXT4? wow :O and my SD Card is shown as fat32 partition (its ok).
Anyways.. :|
--
- I am thinking to install the 4EXT touch recovery, found it comfortable instead of pressing volume/power keys again and again. (and offcourse donate to the dev; great job there..keep it coming! )
- Do I need to convert to EXT4 partition type? How can I check my existing partition type? well of which partition are we talking about here?..the internal memory or the SD card partition type? noob*
- Can somebody give me some short steps of how to install 4EXT without bricking my phone..as I am worried a bit now to move forward
Click to expand...
Click to collapse
S-off'ing and rooting was a walk in the park (thx devs for making it sooo..easy)
Regards,
sky770
sky770 said:
ok.. everything went fine Now my Desire S is S-off'ed and is rooted
Click to expand...
Click to collapse
Congrats SKy770! Welcome to the elite S-OFF club! (Just joking!)
sky770 said:
Which zip file version of ENG HBOOT should I flash?
Got 2 zip files here: one of them is named "PG88IMG(ENG 0.98.2000)" and is having "engHBOOToverARX.img" named IMG file.
Other one is named "PG88IMG" and is having "hboot_0.98.0000_361a7ba6_0310.img" named IMG file.
I checked their size and MD5; size is same but their MD5 hashes are different.
Please suggest, which one to go for? Or should I flash a newer version of ENG HBOOT? the 2.00.xxx ? Which ones better? :|
Click to expand...
Click to collapse
If you've used revolutionary, you're Hboot should now be RVL v6.98.1000?
The engHBOOToverARX is a modified v0.98 bootloader, which *pretends* to be v6.98.2000. This allows you to overflash the RVL hboot. The easiest method is to use fastboot.
To flash, extract the file on your computer to get the xxxxx.img. Boot into Fastboot mode (Vol- and power), click fastboot, plug in USB cable. and type the code:
Code:
fastboot flash hboot xxxxx.img
This should take like a second or less. Reboot into hboot to check.
Alternatively you can use the hboot update interface by placing the P88IMG.zip file on SD card, and when you boot into hboot it will ask you whether you want to update (click yes obviously). I personally don't like this method as people tend to forget to delete the .zip file and may be at risk of repeatedly flashing your hboot.
I don't know whether flashing v0.98 or v2.00 straight without going through v6.98.2000 would work? Try it?
the ENG v0.98 should work with most ROMs. I think v2.00 is only needed for some newer ROMs which require a /data/lib partition (better search round for which ROMs need it).
Tbh, never found any problems with v0.98, so I've stuck to it ever since I first rooted it. Don't think there is any real life benefits of one over the other (except obviously if your ROM doesn't work with v0.98).
sky770 said:
- Flashing this ENG HBOOT is it equivalent to flashing a new radio?
Click to expand...
Click to collapse
Yes and no. It's similar that radio updates can also be applied via fastboot or the hboot PG88IMG.zip interface...
But effectively you're flashing different things. BOTH GIVES YOU RISK OF BRICKING YOUR PHONE. So the tip is if it ain't broke, don't fix it!
sky770 said:
Will I need to format any partitions, cache,...anything? I am not going to install any custom ROM for now, so I need my applications and their data..everything intact (just being noob here )
Click to expand...
Click to collapse
Generally its a good idea to at least wipe the partition if you've messed with hboot. So its a good idea to backup before you mess around with your phone.
THis can be done through 4EXT easily. (the wipe/format settings)
sky770 said:
- I am thinking to install the 4EXT touch recovery, found it comfortable instead of pressing volume/power keys again and again. (and offcourse donate to the dev; great job there..keep it coming! )
- Do I need to convert to EXT4 partition type? How can I check my existing partition type? well of which partition are we talking about here?..the internal memory or the SD card partition type? noob*
Click to expand...
Click to collapse
Well, ext4 isn't strictly necessary... your phone will work on ext3, but if you've heard about the infamous Desire S eMMC problem, then ext4 gives you a little more protection.
(the problem I think is that on overloading the cache partition, say updating all market apps, the phone hangs... people intuitively do a battery pull which corrupts the /cache partition. There is a small risk of frying your memory if you quickly reinsert your battery back after you've battery pulled it, so its generally advised to wait 10 seconds after battery pull before putting battery back in.)
Ext4 supports write-back journaling so should be less susceptible to this...
to convert to ext4, use 4EXT convert tools (NOT wipe/format!)
sky770 said:
- Can somebody give me some short steps of how to install 4EXT without bricking my phone..as I am worried a bit now to move forward
Click to expand...
Click to collapse
Download the .apk file and install. You need to be rooted and S-OFF'd. It will then ask you to update, click yes. Then install the latest version (1.005 RC3?)
DOne.
anchemis said:
If you've used revolutionary, you're Hboot should now be RVL v6.98.1000?
The engHBOOToverARX is a modified v0.98 bootloader, which *pretends* to be v6.98.2000. This allows you to overflash the RVL hboot. The easiest method is to use fastboot.
Click to expand...
Click to collapse
Well, after using revolutionary I have HBOOT v.6.98.1002.
So should I use:
the Other one is named "PG88IMG" and is having "hboot_0.98.0000_361a7ba6_0310.img" named IMG file.
Click to expand...
Click to collapse
?
But as the name of the file suggests its 0.98.0000 and NOT 0.98.2xxx. *now am confused*
Well I extracted the "hboot_0.98.0000_361a7ba6_0310.img" file from the zip available here
and thx for clearing up my 4EXT doubt (so i am assuming that for 4EXT I don't have to re-format my partition(s)..simply install, convert partitions to ext4 and voila! )
the eMMC fried chip prob? yep..I saw that somewhere around here in forums :O *shrugs*
UPDATE:
I have successfully installed 4EXT recovery but when I check my filesystem info it says that except the SD Card my all my partitions are ext4 only! is that possible? :O and my SD Card is shown as fat32 partition (its ok).
Anways..
Hi guys,
I just tried flashing my HBOOT with the ENG HBOOT file available here
using the PG88IMG.zip method.
But the HBOOT said "bypassed".. now what is that? :O though I am able to boot into my stock ROM (thank god I din't bricked my phone phewff).
Now how can I work this one out to have 0.98.xxx ENG HBOOT?
Any help/suggestions would be appreciated.
Regards,
sky770
sky770 said:
Hi guys,
I just tried flashing my HBOOT with the ENG HBOOT file available here
using the PG88IMG.zip method.
But the HBOOT said "bypassed".. now what is that? :O though I am able to boot into my stock ROM (thank god I din't bricked my phone phewff).
Now how can I work this one out to have 0.98.xxx ENG HBOOT?
Any help/suggestions would be appreciated.
Regards,
sky770
Click to expand...
Click to collapse
Looks the RVL v6.98 hboot is bypassing (aka blocking) hboot flashes.
Did you try the fastboot method?
Try flashing the ENGHBOOToverARX.img first.
You should get hboot v0.98.2000? (just ignore it, as it is 0.98.xxxx in reality)
After you've done that. Flash ENG 0.98.xxxx
---------- Post added at 02:15 PM ---------- Previous post was at 02:07 PM ----------
sky770 said:
Well, after using revolutionary I have HBOOT v.6.98.1002.
Click to expand...
Click to collapse
Yes, sorry, my brain isn't functioning today...
The reason why you're 'bypassing' is that when you flash using the PG88IMG method, your hboot will detect / compare the version numbers.
As RVL 6.98.1002 (despite being 0.98 in disguise) is greater than 0.98.xxxx, it will not flash it.
the EngHBOOToverARX.img has version number 6.98.2000, which allows you to overflash the RVL 6.98.1002. This version I think also allows 'downgrade' flashing, so you can revert back to ENG 0.98.xxxx
anchemis said:
Looks the RVL v6.98 hboot is bypassing (aka blocking) hboot flashes.
Did you try the fastboot method?
Try flashing the ENGHBOOToverARX.img first.
You should get hboot v0.98.2000? (just ignore it, as it is 0.98.xxxx in reality)
After you've done that. Flash ENG 0.98.xxxx
---------- Post added at 02:15 PM ---------- Previous post was at 02:07 PM ----------
Yes, sorry, my brain isn't functioning today...
The reason why you're 'bypassing' is that when you flash using the PG88IMG method, your hboot will detect / compare the version numbers.
As RVL 6.98.1002 (despite being 0.98 in disguise) is greater than 0.98.xxxx, it will not flash it.
the EngHBOOToverARX.img has version number 6.98.2000, which allows you to overflash the RVL 6.98.1002. This version I think also allows 'downgrade' flashing, so you can revert back to ENG 0.98.xxxx
Click to expand...
Click to collapse
yeah.. we're on the same page now
I just tried flashing the 6.98.200 (engHBOOToverARX.img) but my HBOOT just ignored it after saying.. "parsing.." and nothing else.
So, right now my HBOOT is still sitting on 6.98.1002
Both times I'd tried I did it using the PG88IMG.zip method (i.e. just copied my file onto the root of SD Card and tried flashing it with HBOOT/Bootloader)
Regards,
sky770
sky770 said:
yeah.. we're on the same page now
I just tried flashing the 6.98.200 (engHBOOToverARX.img) but my HBOOT just ignored it after saying.. "parsing.." and nothing else.
So, right now my HBOOT is still sitting on 6.98.1002
Both times I'd tried I did it using the PG88IMG.zip method (i.e. just copied my file onto the root of SD Card and tried flashing it with HBOOT/Bootloader)
Regards,
sky770
Click to expand...
Click to collapse
Fastboot it?
0. Delete the PG88IMG.zip file to stop it causing you trouble.
1. Extract the .img file from the .zip file (so you get the engHBOOToverARX.img)
2. Plug phone to computer and get phone into FASTBOOT USB mode, get to hboot (vol- + power), then scroll to fastboot, it should say fastboot usb.
3. Get the android sdk tools.
4. Use the command line type:
Code:
fastboot flash hboot engHBOOToverARX.img
[\code]
whatever that .img file is called.
5. See the result? (if successful, you should get v6.98.2xxx)
6. Install ENG 0.98.xxxx the same way.
anchemis said:
Fastboot it?
0. Delete the PG88IMG.zip file to stop it causing you trouble.
1. Extract the .img file from the .zip file (so you get the engHBOOToverARX.img)
2. Plug phone to computer and get phone into FASTBOOT USB mode, get to hboot (vol- + power), then scroll to fastboot, it should say fastboot usb.
3. Get the android sdk tools.
4. Use the command line type:
Code:
fastboot flash hboot engHBOOToverARX.img
[\code]
whatever that .img file is called.
5. See the result? (if successful, you should get v6.98.2xxx)
6. Install ENG 0.98.xxxx the same way.[/QUOTE]
Well, I got the procedure described [URL="http://forum.xda-developers.com/showpost.php?p=17481836&postcount=2"]here[/URL]. Confirmed. They are exactly the same as you have pointed out in the above post :)
Now, my HBOOT version is 6.98.2000 (PG8810000)
so..whats next? should I repeat the same steps for the 0.98.xxx ENG HBOOT; extracting and using the "hboot_0.98.0000_361a7ba6_0310.img" file?
:D
Regards,
sky770
Click to expand...
Click to collapse
and....Voila
My HBOOT says version 0.98.2000 (PG8810000) after second flash from 6.98.2000 (PG8810000). Also, Revolutionary's logo has also been removed from the top of Bootloader
I will be writing and attaching a small slightly modified batch file script using which noobs can easily change their HBOOT version.
I hope that small contribution could make XDA a better place for noobs (not to mention the enormous help I got here )
Regards,
sky770
sky770 said:
and....Voila
My HBOOT says version 0.98.2000 (PG8810000) after second flash from 6.98.2000 (PG8810000). Also, Revolutionary's logo has also been removed from the top of Bootloader
I will be writing and attaching a small slightly modified batch file script using which noobs can easily change their HBOOT version.
I hope that small contribution could make XDA a better place for noobs (not to mention the enormous help I got here )
Regards,
sky770
Click to expand...
Click to collapse
Congrats!
I bet you're fingers are now itching for a custom ROM...
Yeah, perhaps someone should write an article about how to flash S-OFF / hboots. The guides on the index are a bit old now.
anchemis said:
Congrats!
I bet you're fingers are now itching for a custom ROM...
Click to expand...
Click to collapse
Itching..? am frigging wanting to flash Fallout's latest RC *greedy me*
but will give it a break for now
anchemis said:
Yeah, perhaps someone should write an article about how to flash S-OFF / hboots. The guides on the index are a bit old now.
Click to expand...
Click to collapse
Already done..check this out
Regards,
sky770
hoping that my thread here is made a sticky :|
maybe somebody of you could help me out in spreading this thread
Thanks & Regards,
sky770
sky770 said:
Itching..? am frigging wanting to flash Fallout's latest RC *greedy me*
but will give it a break for now
Click to expand...
Click to collapse
I've been eyeing up the CM9 alpha progress... and it's been pretty stable so far!
Can't wait to get rid of sense!
anchemis said:
I've been eyeing up the CM9 alpha progress... and it's been pretty stable so far!
Can't wait to get rid of sense!
Click to expand...
Click to collapse
Yep..CM's always been one of my fav ROM to look forward to since I have been thinking to get a droid. Now it looks like I have something to build my turf on
Heres hoping that CM9 gets rock solid stability
Regards,
sky770
sky770 said:
Yep..CM's always been one of my fav ROM to look forward to since I have been thinking to get a droid. Now it looks like I have something to build my turf on
Heres hoping that CM9 gets rock solid stability
Regards,
sky770
Click to expand...
Click to collapse
It is so far despite being an alpha...
So long as you can put up with:
1. No FM radio
2. minor bugs
3. Camera only up to 4MPx
anchemis said:
It is so far despite being an alpha...
So long as you can put up with:
1. No FM radio
2. minor bugs
3. Camera only up to 4MPx
Click to expand...
Click to collapse
waiting for official ICS sources
fm radio? meeh..SKY.FM ftw!
anchemis said:
Fastboot it?
0. Delete the PG88IMG.zip file to stop it causing you trouble.
1. Extract the .img file from the .zip file (so you get the engHBOOToverARX.img)
2. Plug phone to computer and get phone into FASTBOOT USB mode, get to hboot (vol- + power), then scroll to fastboot, it should say fastboot usb.
3. Get the android sdk tools.
4. Use the command line type:
Code:
fastboot flash hboot engHBOOToverARX.img
[\code]
whatever that .img file is called.
5. See the result? (if successful, you should get v6.98.2xxx)
6. Install ENG 0.98.xxxx the same way.[/QUOTE]
excuse me :P
can i still do this if i already installed custom rom
[ROM][27 APR] [Reaper V3.0 | GB 2.3.7] [Reaper Kernel V1.2][FTL Launcher][UCS]]
?? thx for the answer
Click to expand...
Click to collapse
Hello people. Just one question. I searched on google and here on xda how to do it but still Im not sure how to do it. I have HTC Desire S, S-OFF with 2.00.002 hboot version and 4.0.4. android version. How do I permanetly root? The official 4.0.4 is kinda laggy, at least for me. I tried few methods but still nothing.. And, I found few methods like for 0.98 hboot or 2.3.5. android but my phone isnt that so Im not sure will it work. Thanks im advance
chorba69 said:
Hello people. Just one question. I searched on google and here on xda how to do it but still Im not sure how to do it. I have HTC Desire S, S-OFF with 2.00.002 hboot version and 4.0.4. android version. How do I permanetly root? The official 4.0.4 is kinda laggy, at least for me. I tried few methods but still nothing.. And, I found few methods like for 0.98 hboot or 2.3.5. android but my phone isnt that so Im not sure will it work. Thanks im advance
Click to expand...
Click to collapse
Is your bootloader unlocked? If so then flash a custom recovery and flash a custom ROM, they all tend to be pre-rooted.
Sent from my Desire S using xda app-developers app
You're already S-OFF so you don't need to worry about most steps in guides.
I assume you have a custom recovery? You can just flash one of the superuser/superSU zip packages. (Desire S uses ARM).
You may also need to flash busybox.
My good gentlemen,
he says the phone is s off already
If you want to ROOT your phone (my case: Desire S , Mfc date: 2011-July ). This is the procedures i learned from China Android forums, at least it works on Me.!!
Make Sure your Hboot is 2.00.0002
Prepare 2 files first: Superuser-3.0.7-efghi-signed.zip and su-bin-3.0.3.2-efghi-signed.zip
(you should find those on the internet)
First:
Recovery --> install Superuser-3.0.7-efghi-signed.zip from SDcard, and Reboot;
Second:
Recovery --> Install su-bin-3.0.3.2-efghi-signed.zip from SDcard Again and Reboot.
Usually, your phone should be Rooted.!!
Have Fun
Thanks for answers Well, the only thing I wanna do is flash a custom rom, and I dont know do I need rooted device for that? If I dont, what do I need? And, how can I check is my bootloader unlocked? And, where can I find a custom recovery? Can anyone link me please? Thanks ^^
I learned few things on my old Desire but this seems little complicated If isnt a probem, can anyone give me a step by step guide what I have to do to start flashing custom roms or something? I'd appreciate it. Thanks in advance
chorba69 said:
Thanks for answers Well, the only thing I wanna do is flash a custom rom, and I dont know do I need rooted device for that? If I dont, what do I need? And, how can I check is my bootloader unlocked? And, where can I find a custom recovery? Can anyone link me please? Thanks ^^
I learned few things on my old Desire but this seems little complicated If isnt a probem, can anyone give me a step by step guide what I have to do to start flashing custom roms or something? I'd appreciate it. Thanks in advance
Click to expand...
Click to collapse
Reboot to bootloader and check the first and second lines of text there...
first states < unlocked > if it was unlocked
second at the end: s-off.... or s- on
If your device realy was: s- off,
then your bootloader does not perform check of a signature,
so, in human language means: you may flash anything you want
custom recovery: clockworkmod or 4ext,
you may find in index thread for desire s...
here is the link
http://forum.xda-developers.com/showthread.php?t=1146601
there you can find tutorials about flashing, rooting etc, etc...all you`ll need
here is another link to the help thread, where you may ask questions if you
stumbled somewhere, along the way
http://forum.xda-developers.com/showthread.php?t=2143855
one more thing: when choosing roms, you should only flash roms for your device
htc desire s ( that`ll save you headaches )
Erm.. Just checked and it says bootloader is locked :/ It is S-OFF but locked. How can I unlock it? On HTCdev or? Thanks
chorba69 said:
Erm.. Just checked and it says bootloader is locked :/ It is S-OFF but locked. How can I unlock it? On HTCdev or? Thanks
Click to expand...
Click to collapse
I`ve never had stock s-off device ( always had to do it myself )
but if you phone was never rooted before and its security flag is set to s- off,
then i think its bootloader will never check manufacturer`s signature
Try this:
download from the market or from 4ext thread (index thread )
< 4ext recovery updater > and from within that application,
try to install recovery ( you`ll need it anyway )
if that`ll turn out to be succesful, then your phone is ready for the ride...
Go to the thread from the second link ( help thread )
and ask there whether device that is s- off, needs its bootloader to be unlocked
in order to be ready to flash custom roms...
To unlock bootloader you may try comand ( not sure if that would work for you )
fastboot oem unlock
issued to you phone through comand prompt ...
Prior to this action you should set up ADB on your pc,
and of course install the drivers for your device...
Says this what I attached. What now?
chorba69 said:
Says this what I attached. What now?
Click to expand...
Click to collapse
Ok then...
you have to flash recovery via fastboot
1. download and set up adb and drivers for you phone ( and install them )
2. download recovery ( clockworkmod or 4ext )
3.extract < recovery_xxxyyy.img > from the zip file- if you downloaded it zipped...
4.rename file to < recovery.img > and place it in the folder
where you`ve placed ADB
5.open command prompt and issue command:
cd c:\name of the folder with ADB [ enter ]
6. reboot your phone to bootloader and wire it to you pc
7. issue command:
fastboot devices
if your device has been recognised( list of devices attached xxxyyy05321...)
you`ll see your phone`s ID
8. issue command:
fastboot flash recovery recovery.img
9. reboot bootloader, and from its option choose recovery
10. from recovery you may flash < superuser.zip >
if you just want your current rom rooted
or via recovery you may flash custom rom...
Alright mate thanks a lot. Im gonna try that as soon as I come home. Just one thing more, any chance of bricking my device? While doing that.
chorba69 said:
Alright mate thanks a lot. Im gonna try that as soon as I come home. Just one thing more, any chance of bricking my device? While doing that.
Click to expand...
Click to collapse
To be honest, when fiddling with phone`s system, bootloader etc..
however small- there is always a chance that you may manage to brick it,
but i`ve been followiing the above mentioned procedures- and many others before me,
many times, and it was always working without a problem,
it was tested and shared, first by the great ones among us,
so one may call them safe to perform,
but you should always remember to be careful,
and better read or ask twice, before doing something you do not fully understand
Ok just to make sure Im doing everything alright.
First, nothing to do with bootloader? Unlock or something?
Next, I create new folder on my pc on C partiton (because of cmd prompt you've said?), download adb and phone drivers and place them in the folder. Then install the drivers. Afterwards, download recovery and place it in the folder with adb and phone drivers and rename to recovery.img. Next, I reboot phone in bootloader and flash recovery. Then I have to reboot in bootloader again, how to? Phone will turn off so I can reboot in bootloader or what? Then I go in recovery, flash superuser.zip for rooted phone and afterwards flash custom rom. Thats it?
chorba69 said:
Ok just to make sure Im doing everything alright.
First, nothing to do with bootloader? Unlock or something?
Next, I create new folder on my pc on C partiton (because of cmd prompt you've said?), download adb and phone drivers and place them in the folder. Then install the drivers. Afterwards, download recovery and place it in the folder with adb and phone drivers and rename to recovery.img. Next, I reboot phone in bootloader and flash recovery. Then I have to reboot in bootloader again, how to? Phone will turn off so I can reboot in bootloader or what? Then I go in recovery, flash superuser.zip for rooted phone and afterwards flash custom rom. Thats it?
Click to expand...
Click to collapse
In bootloader, there is an option to reboot it,
While in fastboot usb mode, bootloader is the first option,
go into it (power button )....
There you can also find < recovery > option....
@chorba69
Go here and find the zip download link (here), extract to same folder as fastboot/adb (and optionally md5 check).
Reboot your phone into Fastboot (reboot to bootloader and if there is an option "fastboot", choose it, else you're already there)
Connect by USB (see the "+files" in my signature if you need windows drivers so your computer understands it's an android phone)
Open a command prompt window (hold shift, right click in the folder, open command prompt..)
Code:
fastboot flash recovery recovery.img
Wait for flash, if you see a message like "waiting for device", your phone isn't connected, you're on the wrong screen on your phone or your computer doesn't have the drivers installed.
Reboot back into bootloader
vol up/down, power button to choose Recovery
You now have a custom recovery (and you're viewing it), now you just have to select your zip from sdcard to flash it (this time the zip is the superuser/whatever).
Backups save phone's lives!
I'm curious about the first line of your hboot (after locked/unlocked/relocked)? e.g. mine is "SAGA PVT ENG S-OFF", if yours says "SAGA PVT SHIP S-OFF" then you're "radio s-off" and can do things like change your phones CID (let it use any network). If it's ENG S-OFF and not pre owned, then you're very lucky indeed (and some people might want more info about/a copy of your hboot)!
Paulie, I attached the image as you can see. Says it's PVT SHIP S-OFF. Do I need to do something before flashing recovery and superuser/rom etc? Or it's not important? Whats the difference anyways between PVT and ENG? And thanks ^^
Mhm. Just tried to flash recovery but recieved this message (attached). Im on FASTBOOT USB screen on phone and in the right directory on pc. Do I need to set up adb or something? Or what do I have to do now?
PVT is expected there, SHIP seems to mean "this version is for general release" whereas "ENG" signifies that it is an ENGineering version.
chorba69 said:
Mhm. Just tried to flash recovery but recieved this message (attached). Im on FASTBOOT USB screen on phone and in the right directory on pc. Do I need to set up adb or something? Or what do I have to do now?
Click to expand...
Click to collapse
I'm surprised you got this error. S-OFF should've meant you had no problem. Instead, you can try using the PG88IMG.zip method. Place the file in the root directory of your phone's SD card, reboot to bootloader and it should detect it and ask you if you want to apply the update.
Remember to delete/rename/move this zip file after it's done, as you'll not be able to use your bootloader normally whilst it is detected.
If you still get another error message, let us know!
Please be careful with the file below.
P88IMG.zip MD5: 729f7b435eadf6321ffc36d1da6a0f83
recovery.img MD5: b81b154d1381c9a7f23be39b645be38b
paulie-uk said:
PVT is expected there, SHIP seems to mean "this version is for general release" whereas "ENG" signifies that it is an ENGineering version.
I'm surprised you got this error. S-OFF should've meant you had no problem. Instead, you can try using the PG88IMG.zip method. Place the file in the root directory of your phone's SD card, reboot to bootloader and it should detect it and ask you if you want to apply the update.
Remember to delete/rename/move this zip file after it's done, as you'll not be able to use your bootloader normally whilst it is detected.
If you still get another error message, let us know!
Please be careful with the file below.
P88IMG.zip MD5: 729f7b435eadf6321ffc36d1da6a0f83
recovery.img MD5: b81b154d1381c9a7f23be39b645be38b
Click to expand...
Click to collapse
Hmm. So after I put that file on SD card, I have to flash it or flash the recovery.img? Or just when I put it and enter bootloader it will automatically start flashing the recovery?
Recently I tried out a custom rom on my T-mobile branded One S, but I want to revert back to stock in order to do a S-OFF.
Before flashing the custom rom I ran the latest official t-mobile firmware, non rooted, original recovery, h-boot 2.16 and radio 1.15, S-ON. I unlocked the phone with an HTC-dev unlock token, flashed TWRP recovery and flashed a custom rom but left the phone S-ON.
Now I want to revert back to stock so I can do a S-OFF (which is needed for certain roms). I picked a RUU corresponding my CID t-mob101, in this case the only one I could find was:
Code:
RUU_Ville_U_TMO_DE_1.77.111.5_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_259421_signed.exe
I wanted to try this one, but the download link is dead:
Code:
RUU_Ville_U_ICS_40_S_TMO_DE_2.38.111.10_Radio_1.09 es.50.02.07_2_10.09d.50.04L_ver2_release_287723_si gned.exe
I flashed back the original recovery, relocked the phone and tried to run the RUU. However when running the RUU I get an 155 error, which means the RUU isn't corresponding to my CID?
Does this mean i'm out of any options reverting to stock? I don't have a nandroid backup..
Thanks in advance!
Try Magio Rom and do S-off > then flash RUU. It works for me with hboot 2.16
First: S-off using facepalm follow this:
1) update your android sdk by clicking android sdk manager and then update from there.
2) after the update finished, shut down your computer and then turn it on again.
3) turn off your phone, just leave it off for like 5 minutes then go to recovery, wipe cache and dalvik cache, then fix permissions then reboot to system.
4) using ONLY the oem htc usb cable, plug in your phone to a usb 2.0 port.
5) just before doing anything else, first check if your phone is recognized by typing "adb devices", there you should see your devices' serial number if it's recognized correctly.
6) then proceed to the steps of facepalm.
Just remember to NOT do the fastboot flash firmware again after error 92. Then after finishing "fastboot oem boot", your computer should then recognize again your phone, then you could proceed to the last three commands.
This is how i managed to have s-off using facepalm. At first i was really frustrated of that error 99, but a little reading and searching won't hurt you.
Take note that the steps i just said may or may not be required to do so, and i don't know if all these steps are really necessary but i just want to share to you guys that have had the same problem as mine. Good luck guys. Hope this helps.
Click to expand...
Click to collapse
hongha_222 said:
Try Magio Rom and do S-off > then flash RUU. It works for me with hboot 2.16
Click to expand...
Click to collapse
Do I need superCID?
And what RUU is needed in step 5 of the facepalm S-OFF
mk13139 said:
Do I need superCID?
And what RUU is needed in step 5 of the facepalm S-OFF
Click to expand...
Click to collapse
not RUU / PJ4010000-OneS.zip
I think you don't need Supercid. Just try Magio first
hongha_222 said:
not RUU / PJ4010000-OneS.zip
I think you don't need Supercid. Just try Magio first
Click to expand...
Click to collapse
Ok thank you for your help, I will try it out soon!
However in the facepalm thread it says you do need supercid... And for supercid you do need to be S-OFF? That's strange..
When I have S-OFF, I can flash any ROM without boot.img and any RUU right?
mk13139 said:
Ok thank you for your help, I will try it out soon!
However in the facepalm thread it says you do need supercid... And for supercid you do need to be S-OFF? That's strange..
When I have S-OFF, I can flash any ROM without boot.img and any RUU right?
Click to expand...
Click to collapse
Magio rom don't need s-off. You might be stuck at supercid and s-off with hboot 2.16 !!! Try it first to do supercid and s-off
When you have s-off, you can flash any Rom with boot.img and RUU.
hongha_222 said:
Magio rom don't need s-off. You might be stuck at supercid and s-off with hboot 2.16 !!! Try it first to do supercid and s-off
When you have s-off, you can flash any Rom with boot.img and RUU.
Click to expand...
Click to collapse
Hey bro, I was in the same situation as you was. Flashing magio rom brought no luck. Instead of searching for RUU, which I simply cannot get I downloaded the nandroid backup 3.16.111.7 from that awesome guy over at this post http://forum.xda-developers.com/showthread.php?t=2192964&page=2
Copy that to your phone (the backup is big, but google drive is fast, I've downloaded it as fast as 12MB/s) and restore the backup. Note that you need to put the backup into /sdcard/TWRP/BACKUPS/ <your device serial> /
If you dont have <your device serial> folder in BACKUPS, just do a backup of something small, it will appear there.
So restore the backup, boot into the rom you just restored, enable android debugging and run moonshine (HTC One S TMO_DE for 3.16.111.10) - it works flawlessly on the backup of 3.16.111.7.
NOTE: After restoring the backup, you may need to flash original kernel boot.img. All I did was download Bulletproof kernel 1.1 and flash the boot.img in fastboot. If the bootloader is locked, just unlock it by the steps below.
So now you're s-off hopefully, and you can boot into fastboot to get SuperCID (command fastboot oem writecid 11111111), and the bootloader may actually get locked now (or it may not...)
If your bootloader is locked, head on to htcdev and unlock it (you will need new unlock_code.bin, the old one wouldn't work).
After unlocking, just flash your favorite recovery (I use TWRP 2.4.1.0) and voila, you can mount your sdcard or adb sideload the rom zip. You may need to format external sd and then mount your sdcard, then windows will ask to format it, which is good and then you can copy the rom zip.
Hope this helped you, because I was struggling for 3 days with a non-working phone.
m4te said:
Hey bro, I was in the same situation as you was. Flashing magio rom brought no luck. Instead of searching for RUU, which I simply cannot get I downloaded the nandroid backup 3.16.111.7 from that awesome guy over at this post http://forum.xda-developers.com/showthread.php?t=2192964&page=2
Copy that to your phone (the backup is big, but google drive is fast, I've downloaded it as fast as 12MB/s) and restore the backup. Note that you need to put the backup into /sdcard/TWRP/BACKUPS/ <your device serial> /
If you dont have <your device serial> folder in BACKUPS, just do a backup of something small, it will appear there.
So restore the backup, boot into the rom you just restored, enable android debugging and run moonshine (HTC One S TMO_DE for 3.16.111.10) - it works flawlessly on the backup of 3.16.111.7.
NOTE: After restoring the backup, you may need to flash original kernel boot.img. All I did was download Bulletproof kernel 1.1 and flash the boot.img in fastboot. If the bootloader is locked, just unlock it by the steps below.
So now you're s-off hopefully, and you can boot into fastboot to get SuperCID (command fastboot oem writecid 11111111), and the bootloader may actually get locked now (or it may not...)
If your bootloader is locked, head on to htcdev and unlock it (you will need new unlock_code.bin, the old one wouldn't work).
After unlocking, just flash your favorite recovery (I use TWRP 2.4.1.0) and voila, you can mount your sdcard or adb sideload the rom zip. You may need to format external sd and then mount your sdcard, then windows will ask to format it, which is good and then you can copy the rom zip.
Hope this helped you, because I was struggling for 3 days with a non-working phone.
Click to expand...
Click to collapse
Wait all of this would work on hboot 2.16? I have the same problem im s-on but super cid.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Edit: I have an htc one s by rogers so would it matter if i use the nandroid i dont have a tmo htc one s
cyberusman said:
Wait all of this would work on hboot 2.16? I have the same problem im s-on but super cid.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Edit: I have an htc one s by rogers so would it matter if i use the nandroid i dont have a tmo htc one s
Click to expand...
Click to collapse
I was on HBOOT 2.15 (from JB OTA). With that hboot, you can not get SuperCID only by altering it in mmcblk0p4, so I had to do s-off first. If you have SuperCID, why dont you try facepalm s-off method? http://forum.xda-developers.com/showthread.php?t=2155135
Please help. I'm confused. I have HBOOT 2.15
I'm S-ON.
I can't get supercid, because mmcblk0p4 is write protected or something. (I followed exactly the steps but it just doesn't stick)
And I can't S-OFF because for that I need Supercid. But you say you can S-OFF without having supercid?
Sent from my One S using xda app-developers app
rolo143 said:
Please help. I'm confused. I have HBOOT 2.15
I'm S-ON.
I can't get supercid, because mmcblk0p4 is write protected or something. (I followed exactly the steps but it just doesn't stick)
And I can't S-OFF because for that I need Supercid. But you say you can S-OFF without having supercid?
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
Have you tried my instructions that are on this page? http://forum.xda-developers.com/showpost.php?p=46939498&postcount=7
I haven't. Can I use that method and install the backup doesn't matter which firmware version I have?
Sent from my One S using xda app-developers app
m4te said:
Hey bro, I was in the same situation as you was. Flashing magio rom brought no luck. Instead of searching for RUU, which I simply cannot get I downloaded the nandroid backup 3.16.111.7 from that awesome guy over at this post http://forum.xda-developers.com/showthread.php?t=2192964&page=2
Copy that to your phone (the backup is big, but google drive is fast, I've downloaded it as fast as 12MB/s) and restore the backup. Note that you need to put the backup into /sdcard/TWRP/BACKUPS/ <your device serial> /
If you dont have <your device serial> folder in BACKUPS, just do a backup of something small, it will appear there.
So restore the backup, boot into the rom you just restored, enable android debugging and run moonshine (HTC One S TMO_DE for 3.16.111.10) - it works flawlessly on the backup of 3.16.111.7.
NOTE: After restoring the backup, you may need to flash original kernel boot.img. All I did was download Bulletproof kernel 1.1 and flash the boot.img in fastboot. If the bootloader is locked, just unlock it by the steps below.
So now you're s-off hopefully, and you can boot into fastboot to get SuperCID (command fastboot oem writecid 11111111), and the bootloader may actually get locked now (or it may not...)
If your bootloader is locked, head on to htcdev and unlock it (you will need new unlock_code.bin, the old one wouldn't work).
After unlocking, just flash your favorite recovery (I use TWRP 2.4.1.0) and voila, you can mount your sdcard or adb sideload the rom zip. You may need to format external sd and then mount your sdcard, then windows will ask to format it, which is good and then you can copy the rom zip.
Hope this helped you, because I was struggling for 3 days with a non-working phone.
Click to expand...
Click to collapse
When you had this problem were you on hboot 2.16? I have super cid but when i try to flash the zip file for face palm s-off it gives me error 99 unkown fail